FTP command in background job

hi all,
I am using a program which sends file via FTP. When I run it in foreground it works fine. But in background it gives error i.e. 'Invalid FTP Handle'.
I am using the following function modules for FTP:
1. 'FTP_CONNECT'
2. 'FTP_R3_TO_SERVER'
3. 'FTP_DISCONNECT'
4. 'RFC_CONNECTION_CLOSE' (destination SAPFTP)
Please advise. Thanks.
Regards,
FS

Try this code :
CALL FUNCTION 'HTTP_SCRAMBLE'
EXPORTING
SOURCE = p_pass
sourcelen = l_dstlen
key = l_key
IMPORTING
destination = p_pass.
CALL FUNCTION 'FTP_CONNECT'
EXPORTING
user = p_user
password = p_pass
host = p_host
rfc_destination = 'SAPFTPA'
IMPORTING
handle = l_hdl
EXCEPTIONS
not_connected = 1
OTHERS = 2.
CALL FUNCTION 'FTP_COMMAND'
EXPORTING
handle = l_hdl
command = 'cd XXXR' "This is the remote location not the local location
compress = 'N'
TABLES
data = lt_data
EXCEPTIONS
command_error = 1
tcpip_error = 2.
CALL FUNCTION 'FTP_COMMAND'
EXPORTING
handle = l_hdl
command = l_cmd "l_cmd contains put <filename>
compress = 'N'
TABLES
data = lt_data
EXCEPTIONS
command_error = 1
tcpip_error = 2.
CALL FUNCTION 'FTP_DISCONNECT'
EXPORTING
handle = l_hdl.

Similar Messages

  • MDMGX download to ports as background job without FTP?

    Hello everybody,
    is it possible to use MDMGX as a background job to download directly into the mdm ports without FTP?
    If I try to download as a local download (in background job) I get the error message: "Cannot open dataset for batch download of file: No such file or directory. Message no. MDM_GX_MSG031"
    Any advice?
    Regards,
    Axel

    Hello Alex,
    As said in the above post MDMGX is used to extract the reference data from ECC. This data can be extracted to the local system as well. You need to specify the FTP server and MDM Root of the system on which the MDM server is Installed, by doing so the data extracted will be placed in the respective folders created under the given root in MDM. PI is not required for this since the output is in the required XML format
    Please go through the below link
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0740b31-a934-2b10-2e95-af2252991baa?QuickLink=index&overridelayout=true&30296699350032
    http://wiki.sdn.sap.com/wiki/display/SAPMDM/MDMGenericExtractor
    Hope this helps
    Rgds,
    Prasad
    Edited by: Prasad Tuttagunta on Feb 28, 2012 12:28 PM

  • External commands fail in Background Jobs on Application server

    Hi,
    We are having problems with jobs that include External Commands. The jobs run successfully if on the Central Instance. But if they run on either of the two Application Server's it fails with 'Unable to connect to Target Host' error message.
    I can run the External Commands from SM49 on both AS's. But as soon as its run in background it fails.
    I have read the rfcexec.sec file needs to be in the .\work directory on the application so I have this in place.
    This is what gets written to dev_w0 when the failure occurs :
    M  *****************************************************************************
    M  *
                                                                                    M  *  LOCATION    SAP-Gateway on host <APP_SERVER> / sapgw75
    M  *  ERROR       timeout during allocate
    M  *
                                                                                    M  *  TIME        Fri May 30 11:20:34 2008
    M  *  RELEASE     640
    M  *  COMPONENT   SAP-Gateway
    M  *  VERSION     2
    M  *  RC          242
    M  *  MODULE      gwr3cpic.c
    M  *  LINE        1795
    M  *  DETAIL      no connect of TP sapxpg from host <CENTRAL_INSTANCE.domain>
    M  *              after 22 sec
    M  *  COUNTER     483
    M  *
                                                                                    M  *****************************************************************************
    M
                                                                                    A  RFC 1446  CONVID 48742194
    A   * CMRC=27 DATA=0 STATUS=0 SAPRC=242 ThSAPECMINIT
    A  RFC> ABAP Programm: SAPLCRFC (Transaction: )
    A  RFC> User: <USERNAME> (Client: 300)
    A  RFC> Destination: %_TCPIP_%1 (handle: 2, , )
    A  RFC SERVER> RFC Server Session (handle: 1, 48741194, {C4A35AF0-2F4C-4E36-98C3-9999A6FE99D7})
    A  RFC SERVER> Caller host: iblonc4306_P75_75
    A  RFC SERVER> Caller transaction code:  (Caller Program: RSBTCXPG)
    A  RFC SERVER> Called function module: SXPG_STEP_COMMAND_START                                
    I'd really appreciate any suggestions on how to fix this issue??
    Thanks,
    Kye

    Hi Siddhesh,
    Thank you for your prompt response. I'm confident all of the prerequisites are set correctly.
    I have enabled the trace on SAPXPG but its only writing to the log dev_cp and dev_xpg when the command is executed successfully.
    For example, if I use SM49 to run the External command from one of the Application Servers dev_cp & dev_xpg  are updated and the command completes successfully. However if I run the job (that has the external command as a single step) from SM37 it fails and doesn't log anything to dev_cp or dev_xpg??
    Is this normally how the trace would work?
    Thanks again,
    Kye

  • Background job with FTP

    Hi,
    I have devloped a program which takes the required data in internal table and places the file in FTP.
    When i execute it manually, the file gets placed properly, but when i schedule the program in background, the program gets executed but the file dow

    Hi,
    You Must be using RFC destination as SAPFTP, when you see go to SM59 -> TCP/IP -> SAPFTP & double click on SAPFTP, go to  Technical Setting tab, you have 4 option in Activation Type. Select Start on Application Server Option and then save the setting. Now test the Background job.
    Regards
    Sanjeev Pallan

  • Monitoring of File in FTP Server generated by background job in ECC system

    Hi,
    There is a background job in ECC system, which generates a file in FTP server. However the issue is that even if the background job is successfully executed, there are instances where the file is not generated in FTP server. Is there any way by which we can monitor such file in FTP Server?
    Regards
    Nishu Shah

    Hi,
    I guess this is not a solman question. Anyway, how do you perform the FTP?? custom code?
    Cheers,
    Diego.

  • Background job and file transfer

    Hello
    I am looking for a way to transer a file that is created in an overnight background job on our R/3 Enterprise (Basis 6.20) to an ITS server within the same network. As no one is logged in at the time of creation of the file I cannot use the usual gui_controls. I cannot find an FM that will initiate a login on a Windows server and transfer a file. Should I script it on the AIX host? Has anyone done this before? Any ideas?
    Thanks for your interest and answers.
    Harry

    Will it be possible for you to try with the Function Modules FTP_CONNECT, FTP_COMMAND, and FTP_DISCONNECT.
    I could see more explanations in these links.
    FTP upload
    /people/thomas.jung3/blog/2004/11/15/performing-ftp-commands-from-abap
    Need to send data as files from SAP to other systems.
    Regd: Funxn Module  FTP_CONNECT
    rgds
    TM.

  • Creating a Step for Background Job from within ABAP Program

    Step-1: I have a Report in ECC, which is scheduled as Background Job, which writes the file to the Application Server(UNIX)
    Step-2:  Trigger a Unix Command to ftp the file to other server.
    Both Step-1 & Step-2 can be done from SM36. 
    Another Scenario:
    Users can run the report in background from SE38 or using the transaction code for the report, In this case we want to call the external command.
    Instead of calling the External Command as below in the report, I want to create a Step from within the program when it is scheduled in background mode.
    CALL 'SYSTEM' ID 'COMMAND' FIELD lc_unixcom.    [ Here lc_unixcom has the External Command ].
    Any ideas??? Appreciate help.

    Hi,
    For submitting a report step, you may use either SUBMIT ... VIA JOB ... or JOB_SUBMIT function module.
    For external commands, this should be done only by calling JOB_SUBMIT function module.
    Sandra

  • It has an error when run a program in background job

    Dear Expert,
    we have a program
    when run it in background,it has a error "Error during import of clipboard contents" but when run it normally(run in front workbench se38 or run the t-code),everything is ok.i've used typingJDBG in the command box to debuge the background job,there has no error.
    whould you like to tell me what had happen? thanks a lot!
    addition: the program used a function ALSM_EXCEL_TO_INTERNAL_TABLE
    Thanks & Regards,
    Kerry
    Edited by: Kerry Wang on Aug 24, 2009 2:12 PM
    Edited by: Kerry Wang on Aug 24, 2009 2:14 PM
    Edited by: Kerry Wang on Aug 24, 2009 2:14 PM

    Hi,
      You cannot use FMs to get data directly from the presentation server when program is executed in the backgroud.
    Check the thread : GUI_DOWNLOAD
    Regards,
    Himanshu

  • Program works but background job for that program fails....

    I have a requirement where I have to collect the details of the purchase order and put the details in XML file format and FTP the XML file to an external third party FTP Server.
    To realize this I developed a report program which follows following logic.
    1)     First I collected the PO details by calling the BAPI BAPI_PO_GETDETAIL1.
    2)     Then using the following link "/people/r.eijpe/blog/2005/11/10/xml-dom-processing-in-abap-part-i--convert-an-abap-table-into-xml-file-using-sap-dom-approach
    I converted these PO details to the XML file format that the third party people accept.
           In the code I used u201CCALL METHOD cl_gui_frontend_services=>gui_downloadu201D and in this process first the XML file is generated and is getting stored on my deskytop.
    3)     Then I called HTTP_SCRAMBLE, FTP_CONNECT, FTP_COMMAND , FTP_DISCONNECT and RFC_CONNECTION_CLOSE.
    This works perfectly well and each time I execute the report the file is getting FTPu2019ed to the third party FTP server.
    Now I tried to schedule a batch job for this and the batch job fails with follwing errors
    02/25/2009 15:08:47 Error in Control Framework
    Message Class  = FES         
    Message Number = 022  
    Message Type   = E
    02/25/2009 15:08:47 Job cancelled after system exception ERROR_MESSAGE 
    Message Class  = 00        
    Message Number = 564  
    Message Type   = A                
    Can some one tell me what is going wrong. My report works perfect in front end but fails if I try to schedule a background job for it in SM36.
    Can you please tell me whatz going wrong with batch job? Any Help is highly appreciated.
    Regards,
    JEssica SAm

    Robert...Thanks for the reply...
    I am using follwing code
    l_xml_size = l_ostream->get_num_written_raw( ).
        CALL METHOD cl_gui_frontend_services=>gui_download
          EXPORTING
            bin_filesize = l_xml_size
            filename     = FILEPATH
            filetype     = 'BIN'
          CHANGING
            data_tab     = l_xml_table
          EXCEPTIONS
            OTHERS       = 24.
        IF sy-subrc <> 0.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                     WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    Now what changes should i make..where should i store my XML file then instead of my desktop?
    and whih Function Module should i Use..

  • Background Job processing

    After writing a report, I used this Function Module “LIST_TO_ASCI” to copy my report to an internal table (DOWNTAB) because I’ll use that internal table to download a text file on the server using dataset.
    Here is my code:
    FORM DL_REP_SERVER.
       DATA: ABAP_LIST LIKE ABAPLIST OCCURS 1,
            MV_FILE2 LIKE RLGRAP-FILENAME.
      DATA: BEGIN OF DOWNTAB OCCURS 1,
              LINE(150),
            END   OF DOWNTAB.
      CLEAR: MV_FILE2.
      MV_FILE2 = ‘J:/Downloads/Report.txt’.
      CALL FUNCTION 'LIST_TO_ASCI'
           EXPORTING
                LIST_INDEX         = SY-LSIND
           TABLES
                LISTASCI           = DOWNTAB
                LISTOBJECT         = ABAP_LIST
           EXCEPTIONS
                LIST_INDEX_INVALID = 1
                OTHERS             = 2. 
      OPEN DATASET MV_FILE2 FOR OUTPUT IN TEXT MODE.
      IF SY-SUBRC <> 0.
        IF SY-SUBRC = 8.
          MESSAGE E037 WITH 'File could not be opened'.
        ELSE.
          MESSAGE E037 WITH 'Error occurs in downloading the file'.
        ENDIF.
      ENDIF.
      LOOP AT DOWNTAB.
        TRANSFER DOWNTAB TO MV_FILE2.
      ENDLOOP.
      CLOSE DATASET MV_FILE2.
    ENDFORM.                    " DL_REP_SERVER
    My big problem is this, when I’m running my program ordinarily (not as background job), I’m getting all the pages downloaded correctly but when I run it as background job (using SM36), I’m only getting the last page of my report being downloaded. Definitely, I can’t debug it because it’s in background. I can’t figure out why. Hope that I stated my problem clearly. Any help would be greatly appreciated. Thanks.

    You can debug batch jobs by going to 'SM37', type in 'JDBG' in the
    command line ( no '/' ), put the cursor on the job and press enter - will
    take you to the job in debug mode.
    You can do this only after the job has finished execution. This will simulate the exact background scenario with the same selection screen values as used in the job also sy-batch will set to 'X'.
    So type in the transaction code 'JDBG' and place your cursor on the job after It has finished. It will take you to a SAP program in debug mode. Step through this program which is about 10 lines, after this your program will be executed in the debug mode.
    Steps
    1. Create variant called BACKGROUND for program to be debugged.
    2. Execute ZDEBUGBG (pgm code below) in background for immediate processing.
    3. Execute transaction SM50.
    4. Select process that runs ZDEBUGBG.
    5. Goto 'Program/Session' 'Program' 'Debugging'.
    A se80 debug session will open.
    6. Change variable W_EXIT to 'E'.
    7. Step thru (F6) until ZWBTEST comes up.
    1. Go to Transaction SM66 and find your work porocess.
    Select the line work process is on and click on the Debugging button.
    If this is a custom program, you can put a wait statement in the code to buy yourself sometime.
    2. Go to Transaction SM50. From the tool bar "Program/session"->Program->Debugging.
    goto SM37 and from Program menu(not sure.. try other menu's)
    -->Catchjob . it will goto the active job in debugging mode.

  • Background Job hangs!

    Hello Friends,
    I am encountering a problem with background jobs which has driven me crazy.
    The background job hangs and when I try to debug it using the JDBG command the results are surprising.
    When the program control reaches a particular PERFROM statement, then no matter what command I give (F5, F6 or if I double click on any of the variables) it hangs. When I press F5, it should atleast go in to the corresponding FORM, and hang during some processing or it should go into an infinite loop but this is not the case. The system hangs even when I press F5 on the PERFORM. The FORM routine exists in the program, so that possibility is ruled out.
    Actually the job processes records of a custom table, this problem starts with a particular record and if I skip the processing of this record then it happens with almost all the records after this one. Also, this does not happen every time the job is run, but whenever it does, it starts with a particular record.
    When the system hangs then even if I try to stop the transaction by right clicking on the task bar then it has no effect, the only way to close the session is by using the 'Windows task manager'.
    I tried transaction SM50, but there were no changes on that screen for this particular session indicating that it has hanged.
    Please let me know if you require any more information.
    Thanks and Regards,
    Haseeb.

    Hi,
    Debug it in Sm66.
    kishore.

  • Background Job Scheduling

    Hi,
      I am scheduling a report to run in background.
    In this report it is creating background jobs automatically for different company codes.
    It submits the 1st background job and waits until it finishes.
    Then 2nd job starts in background and continues with other jobs.
    At end it finishes all the jobs and closes.
    Now my problem is.
    1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
    2.       If possible how can we do that.
    What I have written is
    loop at companycode.
    Create job name.
    call fun 'Job_Open'.
    submit xxxx user sy-uname via job job_name numer job_count
    to sap-spool
    spool parameters l_spool_parameter
    without spool dynpro
    with companycode
    with ......
    and return.
    endloop.
    Please help ASAP, urgent.

    hi praveen,
    Job Scheduling Explained
    Definition
    Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the job’s definition. There are several ways to schedule jobs:
    From Transaction SM36 (Define Background Job)
    With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
    Through the background processing system’s own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
    Through an external interface.
    Scheduling Background Jobs   
    Use
    You can define and schedule background jobs in two ways from the Job Overview:
    ·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
    ·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
    Procedure
           1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
           2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
           3.      Set the job’s priority, or “Job Class”:
    ·         High priority:      Class A
    ·         Medium priority: Class B
    ·         Low priority: Class C
           4.      In the Target server field, indicate whether to use system load balancing.
    ·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
    ·         To use a particular application server to run the job, enter a specific target server.
           5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
           6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
           7.      Define the job’s steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
           8.      Save the fully defined job to submit it to the background processing system.
           9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
    Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
    Specifying Job Start Conditions
    Use
    When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
    Procedure
    Choose the Start condition button at the top of the Define Background Job screen.
    Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
    For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
    Once you’ve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
    No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
    Managing Jobs from the Job Overview
    Use
    The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
    Procedures
    To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
    To copy a single existing job, choose Job ® Copy.
    To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
    To repeat a single job, choose Job ® Repeat scheduling.
    To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
    You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
    To review information about a job, choose Job ® Job details. Details displayed can include:
    current job status
    periodicity, or the repetition interval
    other jobs linked to the current job, either as previous or subsequent jobs
    defined job steps
    spool requests generated by the current job
    To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
    To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
    To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
    To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
    To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
    To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
    regards
    karthik
    reward me points if helpfull

  • Background job not updating data for some steps of program

    We have created a custom program and submitting the standard program RPRCCC_READ_KR1025
    which is used for conversion of AMEX credit card files.
    Since this program can update data for 1 company id at a time,we have created a background job
    for that program with 10 steps and 10 variants of data related to 10 different company codes.
    when this job is executed it is not updating data for all the 10 files , sometimes it updates 5,7,etc...
    If we execute the other files which didnt update in job manually they are getting updated.
    All the files executed with that program can be seen in PRTA transaction.
    Regards,
    Gautham.
    Edit: Solved.
    Since the standard program updates the database every time with commit work
    there should be some time until the next database update,so we can use wait command
    after the submit statement which will do the trick.
    Edited by: Gautham Vangaveti on Aug 5, 2010 7:20 PM

    Hi,
    I mean B(Sub Assembly)
    Item Rollup Flag
    A No
    --B                       Yes
    ---B1 No
    ---B2 No
    ---B3 No
    --C                      Yes
    In this case when we run cost rollup by giving item A, Oracle will consider below structure.
    A
    --C
    Regards,
    Sarvottam.

  • Ctrl-c in bash kill openbox started from rc file as background job

    Hi,
    Ctrl-c in bash kill openbox started from rc file as background job.
    strange, isn't it ?

    I want to have openbox in the job list of a bash. as if my xinitrc was "exec xterm" and I manualy enter the "openbox &" commande in the xterm window. I suppose this is a common wish : telling bash to read from file then from keyboard, but that not exactly what bashrc do.
    "ps j" for openbox started in bashrc
    PPID   PID     PGID  SID   TTY       TPGID STAT UID    TIME COMMAND
    1769  1773  1773   845 pts/0     1752 S     1000   0:00 xterm -e bash  --rcfile ~/bin/xsession.sh
           1  1780  1773   845 pts/0     1752 S     1000   0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
    1773  1783  1783  1783 pts/2     1805 Ss    1000   0:00 bash --rcfile ~/bin/xsession.sh
    1783  1795  1783  1783 pts/2     1805 S     1000   0:00 /usr/bin/openbox --startup /usr/lib/openbox/openbox-autostart OPENBOX
    1783  1805  1805  1783 pts/2     1805 R+    1000   0:00 ps j
    "ps j" for openbox started by keyboard or PROMPT_COMMAND
    1718  1722  1722   845 pts/0     1701 S     1000   0:00 xterm -title Login -e bash  --rcfile ~/bin/xsession.sh
           1  1729  1722   845 pts/0     1701 S     1000   0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
    1722  1732  1732  1732 pts/2     1747 Ss    1000   0:00 bash --rcfile ~/bin/xsession.sh
    1732  1744  1744  1732 pts/2     1747 S     1000   0:00 openbox
    1732  1747  1747  1732 pts/2     1747 R+    1000   0:00 ps j
    ps have PGID equal to the bash TPGID, so it is foreground. openbox from PROMPT_COMMAND have his own PGID, so it is background. openbox from bashrc share PGID wish bash ... so if bash do not consume Ctrl-c signal openbox receive it ? I assume it is some things like this, but why ? INVOCATION and JOB CONTROL sections in bash manpage do not seems describe this, so that's a strange behaviour.

  • DYNPRO_SEND_IN_BACKGROUND when submitting a background job, when creating a

    Hi.
    We create sales orders via EDI.   When certain sales orders are created, we execute user exists on the Sales Order save.  During the User Exit, we submit/create (job_open_adk function, the submit command, and the job_close_adk function) a background job. 
    The background, is created and executed successfully, but we get 2
    short dumps everytime.
    The short dump is:
    DYNPRO_SEND_IN_BACKGROUND
    The description is:
    Screen output without connection to user.
    The short dump is for the user WF-BATCH.
    I've used DEBUG and the shortdump occurs on the submit command.
    submit zsd
    to sap-spool
    destination 'null'
    immediately ''
    keep in spool 'X'
    without spool dynpro
    and return
    user l_user via job tbtcjob-jobname
    number tbtcjob-jobcount
    with p_vbeln = l_order
    with p_ebeln = l_po
    with p_uname = l_user.
    Nothing should be displayed on the screen.
    I used 'without spool dynpro' to prevent the 'Print Screen List' window
    from appearing.
    I've put this code into a TEST program. I ran the test program
    myself. (under my ID) The program run perfectly. No
    shortdump.
    Similar code is used in other programs and it works perfectly - no shortdumps.
    The short dump occurs when we use ALE/EDI to create a sales order.
    The short dump has the ID WF-BATCH on it.
    I'm guessing the problem is with the WF-BATCH ID. Are printer setting
    missing on a Work Flow ID?
    Any ideas why the 'without spool dynpro' parameter doesn't work for the
    WF-BATCH ID?
    I've tried searching OSS and I looked at the on-line help/documentation
    on Submit. I saw a recommentation to use the
    fuction 'GET_PRINT_PARAMETERS' to set all of the print parameters. I
    tried this, but still got the short dumps.
    Any suggestion on how I can run the Submit command and not get a short dump?
    thanks,
    Michelle

    Hi,
    Try this notes:
    0100915 RSBDCREO: System hangs or parameters not effective
    0377038 HR-CA-ALE: DYNPRO_SEND_IN_BACKGROUND for HR doc. d
    0105165 Dump "DYNPRO_SEND_IN_BACKGROUND" in prog.SAPMSSY0
    0169303 Warning messages displayed for settlement mass pro
    0428489 VL10: Dump 'DYNPRO_SEND_IN_BACKGROUND' with backgr
    [[http://forums.sdn.sap.com/thread.jspa?threadID=14875|http://forums.sdn.sap.com/thread.jspa?threadID=14875]]
    Regards
    HM

Maybe you are looking for