Datacom/AD configuration job AXNEW01 ends with CC of 2
Article ID: 419939
Updated On:
Products
Issue/Introduction
While installing the Datacom/AD MUF for our system, we ran the AXNEW01 job to allocate BDAM or EXCP files, and the job ended with a CC of 2, even though the documentation for the job says it should be zero. My wild guess is that CC=1 for VSAM and CC=2 for BDAM, right?
Is this a problem, and how do we deal with it?
Cause
User removed the JOBRC=(LASTRC) parameter from their JOB card.
Resolution
You are right that the CC of 1 is for VSAM, and 2 is for the BDAM/EXCP file organisation. One of these codes will always be used.
In this JCL member as it is shipped, the JOB statement has this parameter:
// JOBRC=(LASTRC)
This says to set the Condition Code for the job based on the last step of the job (which is expected to be zero). You have removed that statement, which then caused the job to default to using the highest CC of any step as the Job CC. If you were to add this JOBRC statement back in to your job and rerun it, you would then see the job has a CC of zero.
As your job ran fine with the EXCP allocations, you can continue on to your next step.
Additional Information
As always, please contact Broadcom support for Datacom if you have further questions.
Feedback
