Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Job Scheduling error

Former Member
0 Likes
787

Hi Experts,

I have a critical requirement. I need to kick off 3 interfaces from 1 report each of which will update the Oracle database.

I've used JOB_OPEN and JOB_CLOSE function modules and using SUBMIT <report> VIA JOB <jobname> NUMBER<jobnumber> AND RETURN. My problem is that these 3 reports are not getting executed, means they are not updating the Oracle database when they are kicked-off from the new program.

But if i run each of them individually with same test data, it runs perfectly and updates the Oracle database. I tried to debug, it returns before going into START-OF-SELECTION event.

Any help will be appreciated

Thanks

Prateek

5 REPLIES 5
Read only

kesavadas_thekkillath
Active Contributor
0 Likes
710

it returns before going into START-OF-SELECTION event.

Any reason found ?

Read only

0 Likes
710

No reason found till now. F1 help on VIA JOB specifies that it will not go in START-OF-SELECTION....

These reports run fine when run individually, but not when kicked off from a 4th program.

Read only

0 Likes
710

are you using job_open for all the three reports ?

Read only

kesavadas_thekkillath
Active Contributor
0 Likes
710

The VIA JOB addition also loads the program accessed in a separate internal mode when the SUBMIT statement is executed and the system performs all the steps specified before START-OF-SELECTION. This means the events LOAD-OF-PROGRAM and INITIALIZATION are triggered and selection screen processing is performed. If the selection screen is not processed in the background when VIA SELECTION-SCREEN is specified, the user of the calling program can eidit it and schedule the program accessed in the background request using the function Place in Job. If the user cancels selection screen processing, the program is not scheduled in the background job. In both cases, execution of the program executed is completed after selection screen processing and the system returns to the calling program due to the AND RETURN addition.

Hope you got it.

Read only

Former Member
0 Likes
710

closed