Back ground job Scheduling

[Former Member]

Hi Experts,

I have normal Zreport, it is working fine in the foreground. Now our requirement is User want schedule the same program in Back ground. So I have created the same program with other name and I have commented the Display section and scheduled in the back ground. If I run it in Back ground it is showing Status as CANCELLED in SM37. What is the problem with this report?

Thanks

kittu

[Former Member]

HI,

Check the joblog in SM37, It will give you the details about what causing the issue, most probably dump.

Thanks

[Former Member]

Hi Sukumar,

I cheecked the Job Log also but It is saying there is no Job Log there....

Thanks

[Former Member]

Did you check ST22 for any dumps?

[Former Member]

Hi Vikram..

I checked the ST22 also for dumps it is saying None of the selected for short dumps

Thanks

[Former Member]

I personally have not come across a situation where there is no job logs or dumps. Either of these 2 places would give you the reason. It can also be because of authorization for running in background. The other possible thing to do here is to debug the job that was cancelled. Use the option JDBG to debug the program from SM37.

[raymond_giuseppi]

Job CANCELLED and no job log, so maybe someone/something "destroyed" the job, ask him or look to system log via SM21.

Regards,

Raymond

[Former Member]

HI,

When you said you commented out the display section,

You don't have to comment out unless you have GUI functions like GUI_UPLOAD or GUI_DOWNLOAD

the display part will go to spool.

Thanks

[Former Member]

Hi Sukumar,

Actually I am not much aware of Back ground jobs, After your suggestion I scheduled a normal Zreport which is giving out put in foreground has been scheduled in the background. But it is also giving the same Status..Any problem with Basis settings??

[Former Member]

Hi,

Do the following

Go to se38 enter your zreport

In the menu program->execute->background

create variant if you have selection screen other execute immediately and go to sm37 and check

[Former Member]

Hi sukumar.,.

I tried this procedure also But no result

[bishwajit_das]

Hi Kittu,

I couldn't identify why the background job status is showing CANCELLED.

But I would like to ask you, if you are following the steps bellow:-

1. Goto SE38 and create the variant with required selection criteria.
2. Then goto SM36 and create a Background Job first.Create a Step and Assign the Report and     Variant. Set the Start Condition (Date & Time ).Save the Job.
3. Monitor the job-status in Tcode SM37.

If its what you are following ,then the status should be successful.

Regards,

Bishwajit.

[Former Member]

Hi Bishwajit..

I followed the same steps... No job log and no Dump..  exist

Thanks

[Former Member]

Hi

can we schedule in back ground a Normal Zreport which running in the foreground ? can ypu send any sample report for back ground scheduling??

[bishwajit_das]

Hi Kittu,

If its possible to give screen shots of the code and the process you are following....then we may sort out your problem.

Regards,

Bishwajit

[Former Member]

Hi..

Can I have ur mail id I can send you the code

[bishwajit_das]

Sorry, its a forum so I want you to share it to all.

[Former Member]

I am guessing this should be a problem with Authorization. did you check su53 for any failed auths?

[Former Member]

HI..

There is no Authorization values over there.

Actually there is

user name    XXXX               Authorization object .........( Blank)

system   XXX                 clientXXXX

date   XXXX                   timeXXXX

instance  XXX        profile parameter auth/new buffering  ...4..

[Former Member]

If this is happening in the development system, write a small test program with just one write statement it and schedule the same in background. If even this fails then its obvious else as Das suggested share the code snippet for us to analyze.

[bishwajit_das]

Hi kittu,

I think , in your case the background job may get cancelled due to either of the following causes:-

1. User and password Issues (Authentication/ Authorization) .
2. Variants are not properly defined.
3. Problem in the program and inputs (Indefinite loops like 1/0).
4. Dependent jobs/ events failure.
5. Lock mechanism congested.

So, check your code and try to resolve it.

Regards,

Bishwajit.

[Former Member]

Hi..

Same program in the fore ground which is giving the result...So may be with authorization problem??

Thanks

[bishwajit_das]

Please close this discussion now...if you have got your answer..

regards,

Bishwajit

[Former Member]

still I didn't get.. If I run it in the fore ground I am getting the result but the same program in the background not working

[Former Member]

did u try to write the test program?

[vigneshyeram]

Hi Kittu,

After going through everyone's reply as i understand it is better to check the code.
Could you please paste your entire code for the analysis.

thanks.

Regards,

Vignesh Yeram