cancel
Showing results for 
Search instead for 
Did you mean: 

program executing succesfully but failed in background

Former Member
0 Kudos

hi all,

my abaper had made an abap program which picks up the files from application server. this program is executing sucessfully in foreground..but when it is scheduled in background it fails. can you please help .

regards,

Priya

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

HI,

The problem is not yet solved. The program worked on dev and quality server perfectly fine(File is on application server). The difference between these servers and prod server is that prod server has 2 application servers and one central instance. File we want is placed on central instance.

Please guide.

Thanks

Former Member
0 Kudos

Hi,

If I understand your problem correctly, you are running a program or report in background which after running should save a file on the server, correct. It is running fine in dev and quality system but not in production. The reason I could say is since development and quality system are having only central instance and no application instance the program will be running using the background process of central instance storing the file on the path of central instance which you have given in the code.

But coming to production since it is having application instance if you are running the program it can run on any instance (central or application) background process. But in the code you might have given the path of central instance. So, when jobs run in central instance background process it will work, but when it runs in application server background process it fails. You can check the same in SM37 that job is running in which server (executing server).

So, what I would suggest is either schedule the job to run in central instance only i.e. in the Job details mention the target server as central instance then job will run in that server only. Other wise then arrange the same path in application servers also i.e. path which you have given in the code then when job executes in application server also then as path is correct it will work fine.

Hope your understood the issue and this will solve the problem.

Regards,

Sharath

Former Member
0 Kudos

I think Sharath has given explanation very well.

The easier option would be to mention the target server in the job to run only on central instance.

Other option as sharaht said that to share the file system if it is unix across all the app servers so that the file gets picked up from any of the app servers.Thanks.

Former Member
0 Kudos

Hi Priya,

One way is to mentioning the target server which was explained quite well by other Gurus.

Other way is to check the file permissions and NFS setting, gateway/Firewall settings in CI and App server.

You can take help from from your Unix Admin / if it windows then Wintel team to check the Network related configs.

This will help in resolving the issue. Because, everytime functional/Abap team may not remember to define the target server in the background job scheduling.

Even the scheduling should not effect load balancing too.

Thanks,

Jagadish

former_member709110
Active Participant
0 Kudos

-

Edited by: Neelabha Banerjee on Sep 8, 2010 6:30 PM

former_member709110
Active Participant
0 Kudos

Hi Priya,

Did you run your background job on the same server (apps server) where you ran the program in foreground ?

Regards,

Neel