AutoSys Workload Automation

We have an application that has a zos Manual job in it, watching for the completion of a job out on the mainframe. It completed recently with a non-zero condition code, but didn't present as failed. Is this working as designed? The user wants the job to alert out if it doesn't have a 0 return code.

DJCronin, I don't believe this should be the way things work but unfortunately is the way it works, at least for 12.0 SP2. The z/OS manual job type exit codes section of the job specifically says 'Exit code interpretation (default: 0=success, non-zero=failure)' This can be confusing making you believe that you don't need to put non zero return codes here to make the job failed, however, you do need to. We've ran into a good bit of issues with this until we went back and coded all of our critical z/OS manual job types.

I'm hoping this is fixed in future releases but I do not see it in the 12.1 doc, we will be going to 12.1 for production in a few weeks.

Thank you for the confirmation that it is working as is in your shop. I will pursue the response below from Don Powell.

Hi Denise,

We recently created a fix for this issue for ESP. It has not been published yet. If you would like you or I could open a ticket and we can get you the test APAR. The APAR number is ST05930

Let me know if you have any questions.

Don

Hi Don,

Unfortunately, my shop is dSeries. Any chance the same fix is being developed on that side of the house?

Hi Denise,

Please open a support ticket and we will have a look at it.

Thank you,

Nitin Pande

CA Technologies

Denise, did you end up opening a case with CA on this? I just wanted to be sure they have a look at this so that it will hopefully be addressed in future releases. If you don't plan to open one then I can open one.

Hi Denise, 

Sorry....I missed the boat.....this is a MANUAL job. I was thinking that this was an EXTERNAL job submitted through the z/OS agent. 

Hi DJCronin 

Were you able to find an answer to your question or opened a case with CA Support?

As suggested by Nitin Pande, I have opened a case for review. 01240535.

Awesome! Keep us updated once support finish their review/finding.

Hi DJCronin,

I wanted to followup with you on this and see if the issues was resolved and if possible, could you share the resolutions on Community.

When dSeries or ESP submits a job it adds a step to the job. The step reports back success or failure. In the case of a manual job coming from somewhere else that step is not in the job.  

But  
It can be added to the JCL. Below is an example of my step.  In this case if the job ends with a RC 5 the job fails.  Depending on the system it may need a STEPLIB.  There are several options around the CCCHK statements. 

//ESPCCCHK EXEC X114CCC,GROUP=DP14G      
//PARMS    DD   *                        
CCCHK RC (5) FAIL CONTINUE                   
CCCHK RC (1:4095) OK CONTINUE     

The PROC  X114CCC looks like the one below. 

//ESPCCCHK PROC GROUP=
//*------------------------------------------------------------------
//* The name of this JCL procedure is specified in the
//* optional CCCHKSTP initialization parameter.
//*------------------------------------------------------------------
//* This is the ESPCCCHK step which is inserted into each job
//* whose definition contains one or more CCCHK statement.
//* The name of this step must be ESPCCCHK.
//* Change the STEPLIB statement as required.
//*------------------------------------------------------------------
//ESPCCCHK EXEC PGM=CYBES080,PARM='&GROUP'
//STEPLIB DD DSN=HLQ.CD7YLOAD,DISP=SHR
//SYSIN DD DDNAME=PARMS
//SYSPRINT DD SYSOUT=(,)

NOTE: 
There are two different steps depending on whether Encore is included or not. In this case it needs the one where Encore is not included.