Batch job and background job

Hi
what is the difference between a batch job and backgroun job ??
thanks
kumar

hi kumar,
As far as I know
Batch job are the jobs created with sessions. You can process those sessions in SM35. These are not direct update methods.
Where as the background jobs are the jobs running in the background with out user interaction. Once you schedule the job for the background job it will run with out user interaction according to the given schedule.
You can run the batch jobs also in background.

Similar Messages

  • Difference between batch job and Background Job

    Hi Forum,
    Can anyone distinguish between batch job and background job for me please ?
    SK

    Hi,
    Batch Job:
    A batch job is a process that runs in the background, often deferred and unattended, to process data in groups (batch) rather than by individual transactions (e.g. a monthly phone bill rather than a bill for each individual phone call). A batch job executes a sequence of programs and technical instructions that are stored in a command file. Progress and error messages are output to a log file allowing users to determine, at any time, if the batch job completed successfully or identify the cause of the problem. Because batch jobs run in the background they are less visible to the end user.
    In a business-computing context, batch job scheduling implies the automatic execution of background tasks (batch jobs) at pre-determined points in time (e.g. every day at 8pm, midday on Wednesday).
    3 types of batch job scheduling can be distinguished: native, basic and advanced batch job scheduling.
    Most operating systems and some business solutions software come equipped with native batch job scheduling tools that provide a limited service (e.g. Windows Scheduled Tasks, UNIX crontab, SAP CCMS) locally to each installation. However, business processes may span multiple platforms, applications, countries and companies. Their complexity may require much more functional power as provided by basic batch job scheduling including national and regional variations in the working calendar, sequence variations according to the day of the month, triggering of jobs by the successful completion of preceding jobs, elimination of gaps and reduced batch windows. Major benefits of basic batch job scheduling are enhanced productivity, operations reliability and cost-reduction. For e-business applications that require real-time processing, the distance between interactive individual processing and batch processing tends to decrease. Advanced batch job scheduling can handle these advanced requirements: event-driven scheduling for a real-time synchronization with interactive processing, just-in-time scheduling to run operations as soon as possible, cross-platform and cross application services for the entire IT landscape, real-time overall monitoring to track background operations for all applications on all servers.
    The standard benefits of batch job scheduling are drastically amplified when job schedulers can handle the end-to-end automation and monitoring requirements for all background operations.
    To schedule a back ground job follow the below steps:
    1. Use Transaction SM36.
    2. Assign a job name.
    3. Set the job’s priority, or “Job Class”:
    High --- Class A
    Medium --- Class B
    Low ---Class C
    4. Here you can specify,when the job is to start by choosing Start Condition. If you want the job to repeat, or be periodic, check the box at the bottom.
    Else click on the immediate and save this.
    5. Now,define the job’s steps by choosing Step.
    Here you need to give the ABAP program that has been used and the name of the variant thats being used.
    6. Save the fully defined job to submit it to the background processing system.(You need to click save button on the main screen i.e SM36)
    7. 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.
    8. Release the job so that it can run.
    The job, even those scheduled for immediate processing, can not run without first being released.So,do remember to release.
    Hope this helps you.
    Regards,
    Rakesh

  • Difference between Batch jobs and background jobs...

    hi APO Gurus ....
    This may sound a very silly question. What is  the exact difference between a batch run and executing a background job ?

    If i understand correctly  your question is  executing a program (for example) in background and running in a batch jobs.  You can execute a program in background while you are online, go to menu program->execute in background and enter print parameter, schedule parameter. System creates and starts job dynamically. You can check in SM37.  Batchjob is you create job using   SM36 (with program and Variant) define run frequency. System automatically run job in specified frequency.  I my experience, technically both are same, system behaves exactly same. One dynamically creates job other one runs on predefined freq.
    Thanks,
    Niranjan

  • ALV, initialization and background job

    Hi,
    I've got a basic report that is causing some problems.
    On my selection screen there are 2 buttons ,say Button 1 and Button 2. If you click button 1 set gv_var to 'A', click button 2 and gv_var is set to 'B'.
      IF sy-ucomm = 'PB_1'.
        gv_ var = 'A'.
      ELSEIF sy-ucomm = 'PB_2'.
        gv_var = 'B'.
    ENDIF.
    In the initialization section gv_var is initialized to A.
    When I execute this report in the foreground there are no problems. However, when I Execute it in the background gv_var doesn't change. It just stays at the value it was set at in the Initialization section.
    Any ideas?

    Hi,
    Please note that AT USER-COMMAND will not get triggered for background jobs.
    Even your custom defined Menu bar will not be available for Background jobs.
    The reason is: According to SAP system, you have scheduled a job, and the job is run. And if the job status is completed, you will view the output.
    There you cannot capture the Sy-ucomm value, since according to SAP system the job is completed, meaning that the report is run and the output is displayed. No more events can be triggered at that place.
    Which is not the case with foreground mode, since, until you leave the program, the program is still under execution only.
    Best Regards,
    Suresh

  • Differences in Background jobs and Dialog jobs

    Hi everyone,
    I am new to SAP and would like a little clarification regarding what is meant by Background jobs and Dialog jobs/processes. We had a situation at our client location where the system got completely bogged down to the point that it almost froze and many of the process chains were failing in BI. As per the basis team, the jobs were triggered as "dialog jobs" instead of "background" jobs which caused a heavy load on the system.
    What is the difference? What happens when the jobs are run in the background or as dialog? Can both be checked in SM37?
    Points will be awarded
    Thanks.

    **Dialog Work process:** The Dialog work process fulfill all requests for the execution of dialog steps triggered by an active user. The dialog work process are not used for request which take long time and which use more cpu. Every dispatcher requires at least two dialog work processes. The dialog work process default time is 300 secs. If the dialog work process does not respond in this time, it will be terminated. Also dialog work process are multiplexed to handle large no of user request.
    **Background Work process:** The background work processes execute programs that run without user interaction. At least two background work processes are required per SAP system. More than one background work processes can be configured per dispatcher. Usually the background work process are used for carrying jobs that take long time to finish, like client copy, client transport etc.., . There are two types of background work process. They are A type and B type. A type background work process are used for mission critical jobs. Background jobs of priority a have high priority than B type back ground jobs.
    you can check your job using tcode SM50.
    Thanks
    Dhiraj

  • What is the difference between background job and foreground job

    Hi Experts,
    Could you pls tell me
    What is the difference between background job and foreground job
    and where exactly used background jobs...
    Thanks

    Hello,
    Background jobs - without user interaction, scheduled via SM37.
    Foreground jobs - with user interaction (transactions).
    For more information, please read these: [http://help.sap.com/saphelp_nw04/helpdata/en/e4/2adbda449911d1949c0000e8353423/frameset.htm], [http://help.sap.com/saphelp_nw04/helpdata/en/73/69ef5755bb11d189680000e829fbbd/frameset.htm] and [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20cb0b44-8f0b-2a10-2381-ca8162bcb5b2].
    Regards,

  • What is released job and scheduled job?

    Hi BW experts,
    Please let me know what is released job and scheduled job?

    Hi
      <b>Released job</b>:The job has been fully defined, including a start condition. Without a start condition, a job cannot be released.
    Only an administrator or a user with appropriate authorizations for background processing can release a job, preventing unauthorized users from running jobs without approval.
    <b>scheduled job:</b> The job which is scheduled for a particular time and that will come into the queue of jobs to which time it is scheduled.
    U can see these jobs in SM37 tcode

  • Broken jobs and failed jobs

    hi all..
    please tell me difference between broken jobs and failed jobs
    thanks

    Please refer documentation .
    Failed Jobs
    If a job has the status of FAILED in the job table, it was scheduled to run once but the execution has failed. If the job was specified as restartable, all retries have failed.
    If a job fails in the middle of execution, only the last transaction of that job is rolled back. If your job executes multiple transactions, you need to be careful about setting restartable to TRUE. You can query failed jobs by querying the SCHEDULERJOB_RUN_DETAILS views.
    Broken Jobs
    A broken job is one that has exceeded a certain number of failures. This number is set in max_failures, and can be altered. In the case of a broken job, the entire job is broken, and it will not be run until it has been fixed. For debugging and testing, you can use the RUN_JOB procedure.
    You can query broken jobs by querying the SCHEDULERJOBS and SCHEDULERJOB_LOG views.
    Regards
    Renjith Madhavan

  • Creating EXCEL documents and background jobs

    Hi there,
    I was wondering whether the method 'SAVE_DOCUMENT_TO_URL' of the interface 'i_oi_spreadsheet' will work when called in a background job with the intention to store the information somewhere on the SAP servers filepath ...
    If so then I would assume that one needs to install both SAPGUI and MS EXCEL on the server to get it actual working?
    Thx,
    Steven

    Yes it does seem silly that there is check like that.  However have a look at the first perform in the function: Create_Spreadsheet.  Right inside of that form there is another perform for get_spreadsheet_interface.  The following is the very first executable line in this perform:
    * don't do anything in batch, because there is no GUI...
      check sy-batch is initial.
    By exiting at this point, l_iref_spreadsheet will be initial and message e893(ux) will be issued.  Based upon that; the if sy-batch is initial around the SAPGUI_PROGRESS_INDICATOR call can never not be true.

  • Different Subroutines in Background jobs and Dialog jobs

    Hi guys,
    I want to execute some subroutines when the program is running  using a background  job  , and some other subroutines completely different when the user use dialog job ( program -> execute in background ) . I know that sy-batch  = 'X'  in both cases  , but, there is something else to identify them ? , any ideas .
    thank you .

    It will be - he meant that they start the background job from SE38/SA38 not run it online.
    SY-SLSET is a starter point for checking the variant used - dynamic variants are used when you don't pick one from the list.  However, this would not help if the user picked a variant and then scheduled the job dynamically.  Another option is to use function GET_JOB_RUNTIME_INFO in your program.  Assuming your scheduled jobs are named differently, you can check for the condition by checking the name of the running job.  Dynamically created jobs will have the program name as the job name.

  • Mail configuration and background job scheduling for ST22 Data

    Experts,
    I want to know how can i schedule a background job in SAP to extract data from ST22 and send a automated mail for the same?
    Any help will be appreciated, Thanks!!!
    Regards,
    Vinit Pagaria

    You don't need to do that, simply configure CCMS (RZ20) to send you an alert via mail when a dump occurs.
    Read,
    http://help.sap.com/saphelp_nw04/helpdata/EN/90/4e313f8815d036e10000000a114084/frameset.htm
    Regards
    Juan

  • BDC and Background Job

    Hi gurus,
    Is it possible for a BDC to behave like online mode when in run in using background job (SM36)?
    Thanks,
    Andre

    Hi Rimpa,
    Is there a way to call the ATP screen even in Background/schedule job mode? What happens is when I simulte background in SHDB only the message "Availability check was carried out" and the ATP screen does not appear.
    If this is not possible, is there any BAPI or FM that can be used to update the Confirmed Qty in ATP. My requirement is to set confirmed qty to 0.
    Thanks,
    Andre

  • Error message while runing the Synch Job in Background job after Patch Upgd

    Friends
    We are 5.3 GRC CC on Windows 2003 and ECC 6.0  BI 7.0
    We just upgraded the patches to 12 for GRC CC and ran the Synch job in background....
    Eveytime we run the Synch job for Usre Roles and profiles or Batch Risk Analysis in Background, job finishes until 99 percent and then gives "Error" Message...
    Heres is the job history..:
    2010-09-26 13:14:25 Started Incremental Batch Risk Analysis 09262010 started :threadid: 0
    2010-09-26 13:18:06 Failed Error while executing the Job for Object(s) :PPORTELLA:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot i... (see log for details)
    2010-09-26 13:18:14 Failed Error while executing the Job for Object(s) :RCHAPMAN:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot in... (see log for details)
    2010-09-26 13:18:02 Failed Error while executing the Job for Object(s) :OJONES:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot inse... (see log for details)
    2010-09-26 13:19:21 Failed Error while executing the Job for Object(s) :YPATEL:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot inse... (see log for details)
    2010-09-26 13:49:42 Failed Error Job not completed
    Did anyone has the same issue after the patch upgrade ?
    Pranav
    The version info for the GRC CC..
    Version: AC-RAR 5.3_12.0
    Build ID: 05140510

    Hi I do get a error while scheduling Background job in RAR 5.3 , Please help me out...........waiting for your reply
    Apr 13, 2012 7:38:59 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:39:00 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:39:01 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:39:02 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:39:03 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:39:04 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:06 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:39:06 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:07 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:39:07 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:08 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:39:08 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:09 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:39:09 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:10 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:39:10 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:11 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:39:11 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:12 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:39:12 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:13 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:39:13 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:14 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:39:15 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:16 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:40:16 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:17 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:40:17 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:18 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:40:18 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:19 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:40:19 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:20 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:40:20 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:21 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:40:21 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:22 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:40:22 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:23 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:40:23 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:24 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:41:24 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:25 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:41:25 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:26 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:41:26 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:27 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:41:27 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:28 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:41:28 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:29 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:41:29 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:30 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:41:30 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:31 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:41:31 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:42:32 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:42:32 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:42:33 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:42:33 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:42:34 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:42:34 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?dae

  • JOB_CLOSE and Background Job Process a FM

    HI Guys,
    I have my code like this:
    data: jobname like tbtcjob-jobname value
                                 'TESTJOB'.
    data: jobcount like tbtcjob-jobcount,
          host like msxxlist-host.
    data: begin of starttime.
            include structure tbtcstrt.
    data: end of starttime.
    data: starttimeimmediate like btch0000-char1.
    Job open
      call function 'JOB_OPEN'
           exporting
                delanfrep        = ' '
                jobgroup         = ' '
                jobname          = jobname
                sdlstrtdt        = sy-datum
                sdlstrttm        = sy-uzeit
           importing
                jobcount         = jobcount
           exceptions
                cant_create_job  = 01
                invalid_job_data = 02
                jobname_missing  = 03.
      if sy-subrc ne 0.
                                           "error processing
      endif.
    data: lv_weekday type WEEK_DAY.
    CALL FUNCTION 'DATE_TO_DAY'
      EXPORTING
        DATE          = sy-datum
    IMPORTING
       WEEKDAY       = lv_weekday.
    Close job
      starttime-sdlstrtdt = sy-datum.
      starttime-sdlstrttm = SY-UZEIT.
      call function 'JOB_CLOSE'
           exporting
                event_id             = starttime-eventid
                event_param          = starttime-eventparm
                event_periodic       = starttime-periodic
                jobcount             = jobcount
                jobname              = jobname
                laststrtdt           = starttime-laststrtdt
                laststrttm           = starttime-laststrttm
                prddays              = 1
                prdhours             = 0
                prdmins              = 0
                prdmonths            = 0
                prdweeks             = 0
                sdlstrtdt            = starttime-sdlstrtdt
                sdlstrttm            = starttime-sdlstrttm
                strtimmed = 'X'                  "starttimeimmediate
               targetsystem         = host
           exceptions
                cant_start_immediate = 01
                invalid_startdate    = 02
                jobname_missing      = 03
                job_close_failed     = 04
                job_nosteps          = 05
                job_notex            = 06
                lock_failed          = 07
                others               = 99.
      if sy-subrc eq 0.
                                           "error processing
      endif.
    This is the Program I want the Batch Job to Execute a BAPI Function Module in the Place of DATE_TO_DAY function module. Is it Possible ??????
    And also I get an error at the JOB_CLOSE Function Module with SY-SUBRC = 5.
    Can anyone know why this is happening and what should be done to overcome this.
    Thanks & Regards,
    YJR.

    Hi Ravi,
    The below code which has an EXPORT and IMPORT commands
    The IMPORT does'nt work in Background.
    Do I need to do anything else.
    REPORT  ZTEST_LM22.
    DATA: LV_NAME(10) TYPE C.
    LV_NAME = 'HELLO'.
    export lv_name to memory id 'ZNAM'.
    submit ztest_lm22_a.
    REPORT  ZTEST_LM22_A.
    DATA: GV_JOBNAME  TYPE BTCJOB VALUE 'TEST_UNPACK',
          GV_JOBCOUNT TYPE BTCJOBCNT.
    data: lv_date type SYDATUM,
          lv_time type SYUZEIT.
    lv_date = SY-datum.
    lv_time = sy-uzeit.
    CALL FUNCTION 'JOB_OPEN'
      EXPORTING
        JOBNAME          = GV_JOBNAME
        SDLSTRTDT        = lv_date
        SDLSTRTTM        = lv_time
      IMPORTING
        JOBCOUNT         = GV_JOBCOUNT
      EXCEPTIONS
        CANT_CREATE_JOB  = 1
        INVALID_JOB_DATA = 2
        JOBNAME_MISSING  = 3
        OTHERS           = 4.
    IF SY-SUBRC <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    SUBMIT ztest_lm22_b AND RETURN
                                   VIA JOB GV_JOBNAME
                                   NUMBER GV_JOBCOUNT.
    CALL FUNCTION 'JOB_CLOSE'
      EXPORTING
        JOBCOUNT             = GV_JOBCOUNT
        JOBNAME              = GV_JOBNAME
        STRTIMMED            = 'X'
      EXCEPTIONS
        CANT_START_IMMEDIATE = 1
        INVALID_STARTDATE    = 2
        JOBNAME_MISSING      = 3
        JOB_CLOSE_FAILED     = 4
        JOB_NOSTEPS          = 5
        JOB_NOTEX            = 6
        LOCK_FAILED          = 7
        INVALID_TARGET       = 8
        OTHERS               = 9.
    IF SY-SUBRC <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    REPORT  ZTEST_LM22_B.
    DATA: LV_NAME(10) TYPE C,
          GV_NAME(10) TYPE C.
    IMPORT LV_NAME = GV_NAME FROM MEMORY ID 'ZNAM'.
    WRITE: GV_NAME.
    If you see in SM37 the Spool does'nt have this value.
    Could you just run a quick test and see what else should be done...
    Thanks & Regards,
    YJR.

  • Background job for Standard (T-code F.80) and Background Job via Submit (for same standard program) provides separate spool layout

    Hello Experts,
    I am using SUBMIT Program to execute a standard T-code (F.80).
            SUBMIT sapf080 WITH SELECTION-TABLE rspar
                                         AND RETURN.
    When I execute the program in background and compare it with F.80 and execute it in background too, spool layout for both are different.
    For F.80, It is more detailed with every info like doc number, company code and fiscal year with messages, but for my program only messages are displayed in the spool which is getting unconvinient as I don't know for which document number that message was generated.
    Can you please suggest why am I getting 2 different spool layouts for the same program executed in 2 different ways.
    Thanks,
    Ankit Khanna

    Hello,
    Thanks for your replies.
    I have added a list option along with SUBMIT statement to get similar spool layouts.
    Below piece of code will solve the issue.
              DATA list_tab TYPE TABLE OF abaplist.
            SUBMIT sapf080 WITH SELECTION-TABLE rspar EXPORTING LIST TO MEMORY
                          AND RETURN.
            CALL FUNCTION 'LIST_FROM_MEMORY'
              TABLES
                listobject = list_tab
              EXCEPTIONS
                not_found  = 1
                OTHERS     = 2.
            IF sy-subrc = 0.
              CALL FUNCTION 'WRITE_LIST'
                TABLES
                  listobject = list_tab.
            ENDIF.

Maybe you are looking for

  • Stock in Reservation

    Dear Experts, Dear All, request you to suggest how to find the reserved stock. As we are devloping one report the stock in hand by using Stock in Hand= Unrestricted Stock- (Reserved Stock + Receipt Reservation) Please guide us to find Reserved Stock

  • Data Type Enhancement - CE 7.1

    Hello I´m creating a Enterprise Service Enhancement to add a field in the Output of the service. According to SAP documentation, I have to create a Data Type Enhancement and inside it I must select the Data Type to be enhanced (the original one). The

  • What metadata is saved within the Quicktime file from the Browser window?

    I'm wondering if anybody could provide a list which contains the metadata that's saved in relation to the available columns in the browser window in Final Cut. For example, I know if I change a clip's Reel name, that information is saved into the act

  • Idempotency in Enterprise Services

    Hi all, I am looking to implement Idempotency for the custom developed web services. I looked at the help and documents on how to implement and have got the code working partially in the backend ABAP Proxy. Based on the help we need to run the TCODE

  • HT1338 os x 10.5 can't update anything

    My Mac is OS X 10.5.8, and I can not update anything now. How should I do? Should I need upgrade my Mac? Thanks~~