RAMAXCC setting are ignored for ADR triggered jobs

Products

• Jobtrac

Issue/Introduction

Jobs that are triggered via Automatic Dataset Recognition (ADR) or DSN triggers remain in "AWAITING RERUN" status even after the RAMAXCC parameter in the JOBTRA00  was increased.  Jobs are finishing with condition codes that should be acceptable based the value set for RAMAXCC, but the status does not reflect a successful completion.

Cause

The RAMAXCC startup parameter in the JOBTRA00 options member is designed to apply only when a job is added to the schedule manually using the ADD or RUN commands. When a job is initiated automatically via an ADR trigger, Jobtrac defaults the Maximum Condition Code to 0000, regardless of the global RAMAXCC value

Resolution

The RAMAXCC applies when the ADD or RUN command is issued in Jobtrac via the ISPF online command.   When a job is triggered via ADR with the action of RUN, the Maximum CC value is typically observed to be 00, regardless of the RAMAXCC setting in the JOBTRA00 member.  To ensure that ADR-triggered jobs respect specific condition codes, you must define the requirements at the Schedule Control Language (SCL) level:

1. Modify the Trigger Action: Update your ADR table so that the trigger action is a RUN for the schedule containing the job, rather than running the job directly.
2. Update the SCL: Within the SCL definition for the specific event, specify the desired Maximum Condition Code (e.g., 0004) in the CCDE condition field or in columns 72–75.
3. Verify the Configuration: After the next ADR trigger occurs, check the Scheduled Event Detail panel for the job. You should see that the Maximum CC now reflects the value defined in your SCL.
4. Confirm Completion: Verify that the job status now transitions to COMPLETE when it finishes within the specified condition code range.