Job in background

hi everybody
ive written a program to run in background, which uploads a text file from application server and creates accounting documents
It also deletes the text file after processing
however, when i run the program in background, the text file is not deleted but when i run it in foreground, its deleted
Anybody knows why?

TRY TO CHECK EXCEPTION AS FOLLOWS;
DATA myref    TYPE REF TO CX_SY_FILE_OPEN.
DATA err_text TYPE string.
TRY.
    DELETE DATASET W_file.
    CATCH cx_sy_file_open INTO myref.
      err_text = myref->get_text( ).
ENDTRY.
write err_text.
OR YOU CAN CHECK CX_SY_FILE_AUTHORITY EXCEPTION

Similar Messages

Error while running a job in background

Hi,
I got the following error message while running the job in background.
"Step 001 started .
Control Framework: Fatal error - GUI cannot be reached.
ABAP/4 processor: RAISE_EXCEPTION
Job cancelled"
What is the reason for this error and how to correct it?

ALV Grid control is based on the custom controls on the screen. When the program is scheduled in background, it tries to create GUI related front-end objects and hence the error u201CFatal Error u2013 GUI cannot be reachedu201D. This type of problem is common with all the programs that use the ALV grid control to display the output.
Solution:
Whenever we execute this type of programs in background, we should be passing a blank docking container instead of the custom container as parent to our grid control.
The docking container doesnu2019t need any of the custom controls on the screen; instead it attaches an area to any or all of the four edges of the screen (top, left, right or bottom). The behavior of the areas in the container is determined by the sequence in which they are initialized. Docking Containers are attached to the screen from the inside out. This means that when you create a second container, it is attached to the edge of the screen, and the container that was already there is pushed outwards.
Let us modify the standard program (by taking a copy of it) to enable it to execute it in background.
Following modifications have to be made:
·        Define a docking container in the program
data: or_doc type ref to cl_gui_docking_container .
·        At the time of creating a custom container, check if the program is being executed in background or foreground. If the program is scheduled in background, then create a docking container instead of custom container.
if cl_gui_alv_grid=>offline( ) is initial.
    create object or_custom_container
           exporting container_name = c_container.
create object or_grid
         exporting i_parent = or_custom_container.
else .
create object or_grid
         exporting i_parent = or_doc .
endif .
Now test executing the program in background. The report would be generated.

Submit a job in background

Hi,
We have a query regarding submission of Jobs in background. If we use JOB_OPEN,JOB_CLOSE in our executable program to submit a job to run this proram with a transaction code and also schedule this job in background using SM36 the what will be the effect?

Hi pankaj,
1. If the program only display some data,
and does not update anything,
then nothing will go wrong.
2. Both programs will run independently of each other,
in background.
regards,
amit m.

Schedule job in background and ftp the data to non-sap system

Hello All,
I have a requirement where in i have to write a program(with selection screen) to download 2 files into application server(frequency: end of each day i.e daily at 23:59), and then in turn i need to put those two files into FTP server using FTP script.
i guess my flow of the code should be
1. write the program with selection screen and
2. get the data from corresponding tables and put it into internal tables.
3. then i have download the data into application server
my question is : how i will schedule the job in background to download the data into application server daily? using job_open, job_submit, job_close?
4. then how i need to move the files from application server to FTP server using FTP SCRIPT?
Also my doubt is once i execute the program ONLY, the background job is triigred (because i wrote job_open, job_submit and job_close inside my program). then how will i input the data into screen daily and download the data into application server in background automatically???? i am confused ...
Please help me to solve the above issues
thanks
sangeetha

>
sangeetha s k wrote:
How my data in application server will be transfer to another system using above FM? Because i am not passing application server file path in SAP to that FM. Could you please explain ?
So the path name and the file name are always the same? In that case you could simply create a SM49 entry with hard coded file & path name.
An easy example for the COPY command under WINDOWS OS:
Create a command in SM49 called ZCOPY with following data:
Operating System = Windows NT
OS command: cmd
Parameters for os command: /C copy "C:\tmp\my_file.txt" "z:\tmp\my_file_copy.txt"
Additional parameters allowed: (leave blank)
In this case you would call SXPG_COMMAND_EXECUTE by filling this 2 parameters:
     commandname                  = 'ZCOPY'
     operatingsystem               = 'Windows NT'
In the case that the file name and the path are not fixed you would set the following in the SM49 definition:
Additional parameters allowed: X
In this case you would call SXPG_COMMAND_EXECUTE by filling this 3 parameters:
     commandname                   = 'ZCOPY'
     operatingsystem                = 'Windows NT'
     additional_parameters       = params "<== fill in the path and file name during run time into this variable

How to run a job in background programatically after 10 sec

Hi Forum,
Can anyone tell me How to run a job in background programatically after 10 sec..
Thanks in advance

Hi,
Here is the example code
*Submit report as job(i.e. in background)
data: jobname like tbtcjob-jobname value
                             ' TRANSFER TRANSLATION'.
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    " You need to give the Date for execution the Job
            sdlstrttm        = sy-uzeit    " You need to give the Time for execution the Job
       importing
            jobcount         = jobcount
       exceptions
            cant_create_job = 01
            invalid_job_data = 02
            jobname_missing = 03.
if sy-subrc ne 0.
                                       "error processing
endif.
* Insert process into job
SUBMIT zreport and return
                with p_param1 = 'value'
                with p_param2 = 'value'
                user sy-uname
                via job jobname
                number jobcount.
if sy-subrc > 0.
                                       "error processing
endif.
* Close job
starttime-sdlstrtdt = sy-datum + 1.
starttime-sdlstrttm = '220000'.
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            = 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.
Regards
Sudheer

How to delete a job in background programatically after 10 sec

Hi all,
Can anyone tell me how to delete a job in background programatically after the transaction is trigerred in 10 sec.
Yours help will be greatly appreciated
Yathish

Have a look at standard report RSBTCDEL. May be helpful to you.
Best Regards,
Vibha
*Please mark all the helpful answers

[abap] Running job in background

Hi !
When I am running a job in background using the functions :
'JOB_OPEN','JOB_SUBMIT','JOB_CLOSE'.
Eventually the job is in finished status, however
I get the following error popup message :
" classification locked (user username)
you cannot classify the batch
because the batch class is
currently being processed.
Do you want to try to carry out the
classification again ?
Please tell me what's the problem, and how to correct the problem ?.
Thanks
moshe

Most likely you try to change data which is locked by another user to the same time in some cases - depending on what you were doing the locks are created by the same job in a previous step. In both cases there is only one scenario that works - check, resp. wait until the locks are released.
Christian

Downloading the file in our PC , when running the job in Background

Hi,
We have an enquiry for below requirment.
Our client runs some jobs in front end , but as the time taken to execute the JOB is more than 15 minutes , he is getting timeout problem, so we want to run the same program in background.
Generally the output of the report is to download the file into his desktop, so even when he is running
the same job in background he want it to be downloaded into his PC, instead of application servor.
We created a test program similar to the requirment, and ran the job in foreground and the file could easily be downloaded to desktop. Then we ran the program in backgound - The job failed with an error message Codepage could not be determined - Message no. FES025.
My Question is - is it possible to download the file into the desktop while running in background.
Please help me .
Thanks in advance.
Vengal Rao.

Please search the forum. This question has been asked and answered many times before.
Rob

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

Process Steps to schedule the job in background

What are the process Steps to schedule the job in background?
Sai.

You can set up the different step while schedule the back ground job. Each step will have the program name, variant.
You can do his using transaction SM36 -> JOB WIZARD.
Thanks,
Srinivas

How to prvent job in Background during a particular daytime?

Dear all,
I have a urgent requirment to prevent all job in background for mring 7:oo am to evening 7:00 pm.
Is this possible?
if yes then plz suggest me possible way to accomplish my requirment.
Regards
Ricky

I think you can accomplish this in 2 different ways.
1. When you define the job start condition using SM36, you can choose Date/Time option and provide Scheduled start and No start after OR
2. If you choose Operation mode and provide an operation mode (night operation, day operation etc). speak with you basis folks to configure this option.

Running job in background

Hi,
I am using oracle 10.2.0.4 and HP UX .
I want to run job in background .For this i created on sql file "stat.sql"
execute sys.dbms_stats.gather_schema_stats( ownname=>'PRD',cascade=>FALSE,degree=>dbms_stats.default_de
gree, estimate_percent=>100);
and then i created one "statscr.sh" file to run this script.
#!/bin/ksh
sqlplus sys/sys as sysdba
@/home/oracle10/stat.sql
exit
i am running this by
nohup ./statscr.sh >/home/oracle10/stat.log &
But soon it displaying message ...
/home/oracle10 > nohup ./statscr.sh >/home/oracle10/stat.log &
[1] 27188
[1] + Done(126) nohup ./statscr.sh >/home/oracle10/stat.log &
How to check this job is running in backuground or not .. in ps -ef|grep nohup it is not displaying anything .
OR is there any thing wrong in my steps ...
Thanks

Hi,
i missed to reply your part ..
See when i loged in to system .. it is prompted me like
oracle10@n2v4d1/PRD
/home/oracle10 >
i tried by "jobs" but it not showing anyting ...
this is one time activity till now ..i need to run few sql script before starting this job and after finishing this job ...
those scripts are taking less time . so i am doing directly in sql prompt ..
I don't know when previous script will fininsh ,so i am not able to tell time when i can run this script.
can you find any mistake in my shell script or sql script or executing command nohup ...
Thanks

How will you schedule the job in background?

How will you schedule the job in background?

Pls go to this link
http://help.sap.com/saphelp_bw33/helpdata/en/4c/89dc37c7f2d67ae10000009b38f889/frameset.htm
Step by Step
http://help.sap.com/saphelp_nw04/helpdata/en/67/13843b74f7be0fe10000000a114084/content.htm
An example of a complex process:
http://help.sap.com/saphelp_nw04/helpdata/en/3c/63073c52619459e10000000a114084/frameset.htm
process chains
process chains
Process chains
http://help.sap.com/saphelp_bw30b/helpdata/en/ad/6b023b6069d22ee10000000a11402f/frameset.htm
Re: Ho to make a variable mandatory or optional?
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8da0cd90-0201-0010-2d9a-abab69f10045
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/19683495-0501-0010-4381-b31db6ece1e9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/36693695-0501-0010-698a-a015c6aac9e1
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9936e790-0201-0010-f185-89d0377639db
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3507aa90-0201-0010-6891-d7df8c4722f7
Thanks & regards
nath..........

Will it be possible to run several jobs in background at the same time?

Hi!
The new release looks promising. Look forward to hear more in Birmingham.
Just now we have a problem. It have to do with functionality In Toad compared to SQL Developer.
Will it be possible to run several jobs in background at the same time. Toad allows that.
If yes: How can we make that happen?

"Jobs" are always background.
But I take you mean queries. Yes, since v1.5.x you can open an Unshared SQL Worksheet (ctrl-shift-n or the toolbar button).
Have fun,
K.

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 jobs 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 jobs 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

Submit job in background

Hi All
I have a program with selection screen. The selection screen has Job name as one of the parameters. When I press F8 (Execute), this program should get scheduled in the background with the job name taken from selection screen. How to submit a program by itself in background.
Please suggest.
Thanks
Shakir

Hi,
Press F9 from the program itself after entering the selection parameters
Or
Create a selection variant and go to SM36 and give some valid name , program name with variant and save and schedule.
Regards,
Nandha

Job in background

Similar Messages

Maybe you are looking for