To convert the return code

guruji · New User Joined: 13 Apr 2007 Posts: 59 Location: Chennai

Hi,

I've a JCl which render a specific Return code (say XXXX) and fail in one of the business conditions. But I want to change this return code XXXX to 0004 or 0000 and make the job's status as successful run, only in this business condition. In all other conditions, let the job run and render the corresponding Return code.

Is there any option possible for this using an IF condition or so?

Thanks,
Reni

Akatsukami · Posted: Fri Oct 15, 2010 9:53 pm

How will you detect the business condition?

guruji · New User Joined: 13 Apr 2007 Posts: 59 Location: Chennai

Hi Akatsukami,

The return code will be XXXX only in this specific business condition and for that alone I need to set the job's MAXCC as 0004 or 0000, so that I need not manually complete the job.

The condition is nothing but having a member in one of the PDS's used in the jobstep.

Thanks,
Reni.

enrico-sorichetti · Posted: Fri Oct 15, 2010 10:26 pm

the return code of each step is determined <returned> by the program being executed
it cannot be changed in any other way

modify the programs involved in order to return the appropriate return code for what You call <business condition>

Bill Dennis · Posted: Fri Oct 15, 2010 11:54 pm

If you have job scheduling/tracking software it may be customisable to accept COND CODE XXXX as normal completion.

Also, you could insert a prior step to check for the member and set COND CODE 4 (flushing remaining steps).

Phrzby Phil · Posted: Sat Oct 16, 2010 12:04 am

Control-M can if I remember correctly even take actions depending on the RC's of specific jobsteps.

enrico-sorichetti · Posted: Sat Oct 16, 2010 12:21 am

my understanding is that the return code XXXX is an error,
according to some <business condition> it should be accepted as a valid/successful return code

dick scherrer · Posted: Sat Oct 16, 2010 1:19 am

Hello,

Sounds like a "solution" that should be unacceptable. . .

If it is "bad" it is bad. If there is some condition that "trumps" the bad, the code should be changed to deal with the condition at that time - not gotten around later. When the step ends it should set a "bad" rc if there is a problem and a good rc when there is no problem.

Even if it means changing some special/sacred code. . . (At least from what has been posted so far).