Does anyone know what do the params "PRED_JOBNAME" & "PRED_JOBCOUNT" in FM JOB_CLOSE do when supplied with a job name & count in the respective field values of the job whcich is executed before the former.
Is the FM JOB_CLOSE specific to some authorization??
The problem that im facing is :
There are in all 2 progs-- 1st main program(module pool) ; 2nd dependent prog (report)
Now associated with each is a job(2jobs in all) which runs in the background.
Functionality of the application :
1st program creates 1st job in the backgrnd(thru Job_open,job_submit,job_close)
and after executing this job, a second report is submitted in the backgrnd as a job(2nd job) using the SUBMIT.... VIA JOB......AND RETURN statement followed by JOB_CLOSE supplying 1st job's name & count to the params PRED_JOBNAME &
The whole scenario is working fine in Development Environment
Problem is in Staging and Production.
<b>Using my login</b> in Staging
After the 1st job is executed successfully,the 2nd job is not created(it is not even not visible at all if u view it thru sm37).
But using another's login(1 particular login only):
It executes as expected : i.e. 1st job executes successfully followed immediately by the 2nd job.
Now once that particular person has executed that program,everyone else can executed that code thereby creating both the jobs.
But why is it that only he can execut that program the first time enabling others to execute it after he has executed.??
<b>Note : The program is not Login specific at any point</b>
This is for sure that there is no Authorization issue,since 2nd job wud have not been created the 2nd time i executed the prog(after the particular person executed it).
What cud be issue?? Any suggestions??
Answers will be rewarded.