Job scheduling problem.

Digvijay Singh · Active User Joined: 20 Apr 2022 Posts: 141 Location: India

Hi all,

I have a problem statement here.

I have one job(A job) which is triggered by rexx and it release one file and that file is triggering one another job (job B) the purpose of that B job is to capture the return code of job A and basis of return code of job A.

what problem i am facing?

When I am executing this flow my B job is not able to capture the A job(A job finished adn file is created in A job that triggred B job) from Savers may be bcz it is not available in the savers yet and this flow is executing this B job .

Points to be noted:
1> This is part of automation task.

2>My A job name is dynamic but i hv used some logic and able to capture the name of the job to get captured in My B job.

3>Problem is the log capturing step in my B job is getting executed right before even the A job is available in savers.

I am trying to add wait step in my B job to wait for 60's and so that it can capture the A job logs but my code reviewer is saying I should not do this since it is not a good practice . I have tested this for few test cases and it worked but they are saying your job might take more time you will have a problem in that situation.

An i can't think of any other way here , Can anyone give any suggest or guide me here.

Thanks in advance.

Rohit Umarjikar · Posted: Tue Jul 19, 2022 3:39 am

Can you try checking after every 30 seconds invterval until you get rc of job A or iteration is 5 times ( whichever is earlier) before erroring out? That would give a range of 30-159 seconds

Digvijay Singh · Active User Joined: 20 Apr 2022 Posts: 141 Location: India

Thank you for reply,

But how even 159 second is not enough if the job is running for more than 159 second.

We dnt know the timing of job it can finish in 0.6 sec or may take more time.

Looking for some dynamic logic here.

one more question is this below scenario is possible in scheduling toll opcp?

If I pass a file with job name can you do something in opcp ..like it should search for that job and if it is available in savers it should trigger another job..?

Thanks for reply

Rohit Umarjikar · Posted: Tue Jul 19, 2022 12:06 pm

How about not triggering the job B from Job A so early and do it at the end step of Job A then you don’t need all these worry ?

Digvijay Singh · Active User Joined: 20 Apr 2022 Posts: 141 Location: India

Still my job A might be running and my step in job B (log capturing step) will start executing and gets finished without capturing the logs.

Can we put or check A job logs any way through rexx or anyway and keep that code in loop untill RC code is not available...?

Rohit Umarjikar · Posted: Tue Jul 19, 2022 1:15 pm

Why would Job A run if there are no more steps in it? You can then make a use of job scheduling feature , and do job as successor to job A

sergeyken · Posted: Wed Jul 20, 2022 11:35 pm

Why not to use the simplest solution, with reservation of the same dataset?

Joerg.Findeisen · Posted: Wed Jul 20, 2022 11:42 pm

Just a remark, sometimes these "WAITING FOR DATASETS" msgs are automated and cause tickets.

It should be (just one '&' here):

sergeyken · Posted: Thu Jul 21, 2022 12:19 am

sergeyken · Posted: Thu Jul 21, 2022 6:03 pm

As a free gift: an example of possible step //WAITING of the //JOBB