Messages CTR0 through CTR0xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTR001I CONTROL-M/RESTART, REL releaseMaint STARTED FOR JOB jobName

Explanation: This information message is issued by the CONTROLR step to indicate that Control-M/Restart processing of the jobName job started.

Corrective Action: No action is required.

CTR002S INTERNAL ERROR IN CONTROL-M/RESTART MODULE modName

Explanation: The CONTROLR step detected an internal error in one of its modules. This message usually follows messages describing the specific error.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the ABNDTYP Control-M/Restart installation parameter in CTRPARM. The job terminates after the CONTROLR step.

Corrective Action: Have your system programmer call BMC Customer Support.

CTR003I processName OF JOB jobName ENDED SUCCESSFULLY

Explanation: This information message indicates that the Control-M/Restart process for the jobName restarted job (for example, ended OK, abended) is not known at this point.

Corrective Action: No action is required.

CTR004I processName processType OF JOB jobName ENDED

Explanation: When processType is SIMULATION, this information message indicates that Control-M/Restart, working in simulation mode, finished the simulation of the restart (when processName is RESTART) or prevent NCT2 (when processName is NONCAT2) for this job.

When processType is REGISTRATION (and processName is blank), this information message indicates that Control-M/Restart finished the collecting of cross-reference statistics for job - data sets.

The job is terminated after the CONTROLR step.

Corrective Action: No action is required.

CTR005S CONTROL-M/RESTART STEP MUST BE THE FIRST STEP OF THE JOB

Explanation: The CONTROLR step is not the first in this job. The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the ABNDTYP Control-M/Restart installation parameter in CTRPARM. The job terminates after the CONTROLR step.

Corrective Action: Correct the JCL. The CONTROLR step should always be the first one in the job.

CTR006S INTERNAL ERROR - INVALID CONTROL-M/RESTART PARAMETERS

Explanation: The parameters passed to Control-M/Restart in the EXEC statement or in the DAPARMIN DD statement are invalid. The specific errors are generally described in the preceding messages.

Corrective Action: If the job was run manually, correct the parameters in error and resubmit the job. If the job was submitted through the Control-M restart or prevent NCT2 processing, have your system programmer call BMC Customer Support for assistance.

CTR007S SYNTAX ERRORS IN processName CONTROL-STATEMENT(S)

Explanation: One or more of the control statements specified in a Restart or Prevent NCT2 Control Parameters member has an invalid syntax. The specific errors are generally described in the preceding messages.

The member in error is either the $DEFAULT member or the one indicated by the MEMNAME subfield in the PARM field of the Control-M/Restart step. The library is the one allocated to the DACTRCTL DD statement.

Corrective Action: Correct the member in error, and rerun the job.

CTR008I PROCESSING PARAMETERS: parms

Explanation: This information message shows the contents of the parameters passed to the CONTROLR step either through the EXEC statement or in the DAPARMIN DD statement.

Corrective Action: No action is required.

CTR009S processName PROCESSING TERMINATED BY THE USER EXIT exitName. RC= rc

Explanation: The Control-M/Restart User Exit CTRX001 returned a return code which signified to Control-M/Restart to stop process processing.

Corrective Action: No action is required.

CTR010S processName PROCESSING TERMINATED DUE TO AN INVALID RC= rc FROM exitName EXIT. FUNCTION - func

Explanation: Exit exitName was called to perform function. The return code rc passed back to Control-M/Restart was not one of the expected return codes. Each Control-M/Restart exit has a defined set of expected return codes. Exit exitName returned a code which is not in the set of allowed codes.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the ABNDTYP Control-M/Restart installation parameter. The job terminates after the CONTROLR step.

Corrective Action: Correct the exit code in error. Refer to the INCONTROL for z/OS Administrator Guide for a description of exit exitName and the list of expected return codes.

CTR011S UNCONDITIONAL SYSOUT READING IS REQUESTED, BUT ERRORS WERE ENCOUNTERED DURING SYSOUT PROCESSING

Explanation: The CONTROLR step, running with SYSOPT parameter R, encountered errors during sysout processing. The specific errors are generally described in the preceding messages.

Corrective Action: Check the preceding messages and take the recommended steps.

CTR012W SYSOUTS FROM PREVIOUS RUNS OF JOB ORDER jobOrder WERE NOT FOUND. READING IS BYPASSED

Explanation: The CONTROLR step, running with SYSOPT parameter C, encountered errors during sysout processing. The specific errors are generally described in the preceding messages.

The CONTROLR step continues processing, but will not uncatalog data sets, perform GDG adjustment, and the like.

Corrective Action: Check the preceding messages and take the recommended steps.

CTR013S JOB jobName IS NON RESTARTABLE

Explanation: Some necessary conditions mandatory for the restart of the job were not met. The specific errors are generally described in the preceding messages.

Corrective Action: Check the preceding messages and take the recommended steps.

CTR014S MISSING CONTROL-M/RESTART REQUIRED PARAMETERS

Explanation: One of the mandatory Control-M/Restart parameters is missing.

Corrective Action: If the job was run manually, correct the parameters in error and resubmit the job. If the job was submitted through Control-M restart or prevent NCT2 processing, have your system programmer call BMC Customer Support for assistance.

CTR015I CONTROL-M/RESTART STEP IS NOT THE FIRST STEP OF THE JOB. ALL STEPS PREVIOUS TO Control-M/RESTART STEP ARE IGNORED

Explanation: This message informs the user that Control-M/Restart was not the first step in the job. Control-M/Restart will ignore all steps prior to Control-M/Restart steps, which means that Control-M/Restart will not analyze any steps prior to the Control-M/Restart step.

Corrective Action: Validate that the steps prior to the Control-M/Restart step were only environment steps or real steps.

CTR017E MISSING PARAMETER IN THE EXCLUDE STATEMENT

Explanation: An obligatory parameter was not specified in the EXCLUDE DSN statement.

Corrective Action: Correct the EXCLUDE DSN statement. Refer to the Control-M/Restart User Guide for the description of the EXCLUDE DSN restart control statement.

CTR018E INVALID DSN LENGTH - CONTROL- stmt

Explanation: The data set name specified in the EXCLUDE DSN control statement has an invalid length.

Corrective Action: Correct the EXCLUDE DSN statement. Refer to the Control-M/Restart User Guide for a description of the EXCLUDE DSN control statement.

CTR019E INVALID TRACE LEVEL VALUE. PLEASE ENTER UP TO EIGHT NUMBERS OF RANGE (1-8), SEPARATED BY COMMAS.

Explanation: An error occurred in the Control-M/Restart step of the job. The user tried specified more than 8 numbers when turning on the trace for that specific job in the Control-M/Restart PARM library, with the TRCREST parameter applied for restart and the TRCNCT2 parameter for NCT2.

Example: In MEMBERNAME in Control-M/Restart PARM library add statement for RESTART and NCT2.

TRCREST 1,2,3,4,5,6,7,8

TRCNCT2 1,2,3

The CONTROLR step terminates with a nonzero condition code or with an abend code, depending on the ABNDTYP Control-M/Restart installation parameter in CTRPARM. The job terminates after the CONTROLR step.

Corrective Action: Correct the member with the member name in the Control-M/Restart PARM library according to the above example.

CTR020W processName CONTROL-MEMBER memName IS EMPTY

Explanation: The process Control-MEMBER was found in the library specified by the DACTRCTL DD statement, but it does not contain any process CONTROL statements.

CONTROLR step continues processing.

Corrective Action: No action is required.

CTR021S MISSING "OPERATION TYPE" PARAMETER

Explanation: The obligatory OPERATION TYPE parameter was not specified in the CONTROLR step parameters.

Corrective Action: If the JCL for the CONTROLR step was created manually, correct the parameters passed to the CONTROLR job step. Refer to the Control-M/Restart User Guide for a description of the CONTROLR step parameters.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR022S INVALID LENGTH OF THE POSITIONAL PARAMETER - parm

Explanation: One of the positional parameters passed to the CONTROLR step has an invalid length.

Corrective Action: If the JCL for the CONTROLR step was created manually, correct the parameters passed to the CONTROLR step. Refer to the Control-M/Restart User Guide for a description of the CONTROLR step parameters.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR023S INVALID PROCESSING MODE - " type"

Explanation: The PROCESSING MODE positional parameter specified in the parameters for the CONTROLR step is not a valid type of restart.

Corrective Action: If the JCL for the CONTROLR step was created manually, correct the RESTART TYPE parameter passed to the CONTROLR job step. See the Control-M/Restart User Guide for the description of the Control-M/Restart PROCESSING MODE parameter.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR024W MISSING " processName CONTROL-MEMBER" NAME PARAMETER

Explanation: The process Control-PARAMETERS member name was not specified in the parameters passed to the CONTROLR step.

CONTROLR step continues processing. The control statements from the $DEFAULT member are used for the current job.

Corrective Action: No action is required.

CTR025S MISSING "RECAPTURE CODES/STEP ADJUSTMENT" PARAMETER

Explanation: The mandatory Recapture Codes or Step Adjustment parameter was not specified in the CONTROLR step parameters.

Corrective Action: Add to the JCL the Recapture Codes or Step Adjustment parameter passed to the CONTROLR job step.

CTR026W MISSING "ORDERID" PARAMETER

Explanation: The ORDERID was not specified in the parameters passed to the CONTROLR step.

If the READ SYSOUT INDICATOR is R, then the CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the ABNDTYP Control-M/Restart installation parameter in CTRPARM. The job terminates after the CONTROLR step. If the READ SYSOUT INDICATOR is not R, processing continues.

Corrective Action: If the JCL for the CONTROLR step was created manually, correct the parameters passed to the CONTROLR job step. See the Control-M/Restart User Guide for a description of the CONTROLR step parameters.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR027S INVALID "RECAPTURE ABEND/CONDITION CODE" INDICATOR - val

Explanation: The Recapture Abend or Condition Code indicator specified in the parameters for the CONTROLR step does not contain a valid value.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the ABNDTYP Control-M/Restart installation parameter in CTRPARM. The job stops after the CONTROLR step stops.

Corrective Action: Correct in the JCL the value of the Recapture Codes or Step Adjustment parameter passed to the CONTROLR job step.

CTR028S MISSING "READ SYSOUT INDICATOR" PARAMETER

Explanation: The obligatory READ SYSOUT INDICATOR parameter was not specified in the CONTROLR step parameters.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP in CTRPARM. The job terminates after the CONTROLR step.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR029S INVALID "READ SYSOUT INDICATOR" - type

Explanation: The value of the READ SYSOUT INDICATOR positional parameter specified in the parameters for the CONTROLR step is not valid.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR030S MISSING "FROM PROCSTEP.PGMSTEP" PARAMETER

Explanation: The obligatory FROM PROCSTEP.PGMSTEP parameter was not specified in the CONTROLR step parameters.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR031S INVALID "PROCSTEP.PGMSTEP" COMBINATION USED

Explanation: The PROCSTEP.PGMSTEP positional parameter passed to the CONTROLR step has an invalid syntax.

If the CONTROLR step has been added to the job by Control-M, contact BMC Customer Support for assistance.

CTR032E REDUNDANT PARAMETER IN THE "EXEC" PARM OF THE RESTART STEP

Explanation: More positional parameters than necessary were specified in the CONTROLR step parameters.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR033S ORDERID IS OBLIGATORY WHEN READ SYSOUT INDICATOR IS SET TO "C" OR "R"

Explanation: Reading of all the sysouts of previous runs of the job was requested, but ORDERID was not specified in the CONTROLR step parameters.

Corrective Action: If the JCL for the CONTROLR step was created manually, correct the CONTROLR step parameters. Refer to the Control-M/Restart User Guide for the description of the Control-M/Restart READ SYSOUT INDICATOR and ORDERID parameters.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR034S INVALID OPERATION TYPE - opn

Explanation: The OPERATION parameter in the PARM field of the CONTROLR step has an invalid value (opn).

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP. The job terminates after the CONTROLR step.

If the CONTROLR step was added to the job by Control-M, notify BMC Customer Support.

CTR035S READ SYSOUT OPTION IS INCOMPATIBLE WITH OPERATION TYPE. NONCAT2 IS PERFORMED WITHOUT SYSOUT PROCESSING

Explanation: The combination of READ SYSOUT and TYPE parameters is invalid. The operation requested was NONCAT2 and the READ SYSOUT requested was one of the codes specifying that SYSDATA is to be read. The Prevent NCT2 function does not use the SYSDATA from previous runs.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP. The job terminates after the CONTROLR step.

Corrective Action: If the JCL for the CONTROLR step was created manually, correct the CONTROLR step parameters. See the Control-M/Restart User Guide for the description of the OPERATION subparameter of the MODE parameter and the READ SYSOUT parameter.

If the CONTROLR step was added to the job by Control-M, notify BMC Customer Support.

CTR036S UNKNOWN DATASET DISPOSITION - val

Explanation: The Control-M/Restart adjustment facility encountered an invalid data set disposition. This message precedes message CTR038I, which describes the data set name.

Corrective Action: Contact BMC Customer Support for assistance.

CTR037S MISSING INPUT DATASET(S). JOB IS NOT EXECUTABLE

Explanation: At least one of the input data sets for the job is missing. It cannot be located. The job may fail during execution. The name of any missing data set is in an earlier part of the CONTROLR step output.

Corrective Action: Look for previous messages that describe data sets that could not be found. One of the following may be done for each data set:

If you want to bypass the checking for this data set, use the Restart Control member and the EXCLUDE DSN statement.
If the data set is needed as input to the job, find out why it is missing, correct the situation, and rerun the job.

CTR038I DSN= dsn DD= ddName STEP= stepName PROCSTEP= procStep

Explanation: This information message details a data set name and its location in the job. The message always appears after another message that describes the actual problem relating to this data set.

Corrective Action: Refer to the previously displayed message in order to determine the problem.

CTR039I processName STEP ADJUSTMENT PERFORMED. NEW processName STEP stepName PROCSTEP processStepName

Explanation: This information message indicates that the Control-M/Restart automatic step adjustment facility for processName ended successfully. The job will be restarted from the specified step and procstep.

Corrective Action: No action is required.

CTR040W "NEW" DISPOSITION IS REQUESTED FOR DATASET, BUT IT IS ALREADY CREATED BY A PREVIOUS STEP OF THE JOB

Explanation: The data set is specified with a NEW disposition although it is created by a previous step of the job and it is not deleted during the step. This could cause a JCL failure during job execution.

Corrective Action: Check the original JCL.

CTR041I DATASET WILL BE SCRATCHED FROM VOLUME volser

Explanation: This information message indicates that the data set will be scratched from the volume to prevent the failure of the job in duplicate data sets on the same volume.

The data set will be scratched from the volume in the execution phase of the CONTROLR step.

Corrective Action: No action is required.

CTR042I DATASET WILL BE UNCATALOGED

Explanation: This information message indicates that the data set will be uncataloged during the catalog adjustment phase in order to prevent the NOT CATLGD 2 error.

The data set will be uncataloged in the execution phase.

Corrective Action: No action is required.

CTR043E DATASET DOES NOT EXIST FOR THE STEP. STEP ADJUSTMENT IS ATTEMPTED

Explanation: A step that should run in the restarted job contains a data set that does not exist. Control-M/Restart will try to perform a step adjustment. It will find a previous step that creates the required data set, and restart the job from that step.

Corrective Action: No action is required.

CTR044I TAPE DATA SET REFERENCES A VOLUME OF A PREVIOUS STEP. STEP ADJUSTMENT IS ATTEMPTED.

Explanation: Control-M/Restart performs step adjustment to resolve the DD card for a tape data set whose volume is specified by a backward reference (VOL=REF in DD card) to a previous step that is not to be executed during Restart.

The message is followed by message CTR038I, which describes the data set name.

Corrective Action: To make Control-M/Restart avoid step adjustment in case of a VOL=REF referring to a step prior to the Restart step, specify the parameter IGNVOLRF = Y in the CTRPARM member. Then Control-M/Restart attempts to resolve the VOLSER and avoids JCL errors without step adjustment.

CTR045S "NEW" DISPOSITION IS REQUESTED, BUT THE SPACE PARAMETER IS NOT SPECIFIED IN THE JCL

Explanation: The CONTROLR step or the job will have to allocate the data set with a NEW disposition, but the space parameter was not specified in the JCL.

For non-SMS environments, the CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP in CTRPARM. The job terminates after the CONTROLR step. Under SMS, the message is not produced.

Corrective Action: Change the disposition of the data set in the JCL, for example from NEW to MOD, and/or add the space parameter.

CTR046W DATASET IS ALREADY CATALOGED BY A PREVIOUS STEP OF THE JOB

Explanation: The data set has to be cataloged, but is already cataloged by a previous step of the job. The message is followed by a CTR038I message that describes the data set name.

Corrective Action: No action is required.

CTR048W "CATALG" DISPOSITION IS SPECIFIED, BUT DATASET IS ALREADY CATALOGED ON OTHER VOLUMES

Explanation: The data set has to be cataloged on a specific volume, but it is already cataloged on another volume. The message is followed by message CTR038I which describes the data set name.

Corrective Action: No action is required.

CTR04AS MISSING INPUT DATA SET dsn

Explanation: An error occurred in the job with a Control-M/Restart step because of missing input data set in the job JCL

The CONTROLR step terminates with a nonzero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP in CTRPARM. The job terminates after the CONTROLR step.

Corrective Action: Check which data set is missing, correct the job JCL, or allocate the missing file, then rerun or restart the job.

CTR050W "UNCATLG" IS REQUESTED FOR DATASET, BUT THE DATASET IS NOT CATALOGED

Explanation: The data set has to be uncataloged, but it is not cataloged. The message is followed by message CTR038I which describes the data set name.

Corrective Action: No action is required.

CTR051E JOB IS NOT AUTHORIZED TO ACCESS DATASET: dsn (DDNAME: ddName)

Explanation: An error occurred in the job with Control-M/Restart step. When the CHKSEC parameter is set to Y in the CTRPARM member in the IOA PARM library, Control-M/Restart calls Security Exit IOASE032 to validate whether the job has authorization to access the data set. This message shows that the problematic job is not authorized to access the data set.

Corrective Action: Consult with your system security administrator, add the correct authorization, and rerun or restart the job.

CTR054S OPEN OF DDNAME ddName FAILED

Explanation: Open of the ddName data set failed. Possible causes are:

The ddName DD statement is missing.
The data set DCB characteristics are not as expected by the CONTROLR step.

Corrective Action: Look in the job log for additional system messages that explain the cause of the failure. If the DD statement is missing, correct the Control-M/Restart procedure.

CTR055S processName OF JOB jobName ENDED WITH ERRORS

Explanation: Errors were detected during Control-M/Restart processing. The specific errors are generally described in the preceding messages.

Corrective Action: Check the preceding messages and take the recommended steps.

CTR056S INVALID LENGTH OF THE EXEC PARM DATA

Explanation: The restart parameters data is longer than 255 characters. This might happen only when Control-M/Restart is called internally by another program.

Corrective Action: Correct the parameters passed to Control-M/Restart.

CTR057S STARTED TASKS PROCESSING IS NOT SUPPORTED YET

Explanation: The CONTROLR step was activated for a started task, and restart of a started task is not supported.

Corrective Action: Do not use Control-M/Restart for started tasks.

CTR059I ANALYZE PHASE STARTED

Explanation: This information message is issued by the CONTROLR step when starting the analyze phase. In this phase Control-M/Restart analyzes what should be done.

Corrective Action: No action is required.

CTR060I EXECUTION PHASE STARTED

Explanation: This information message is issued by the CONTROLR step the execution phase starts. In this phase Control-M/Restart executes the special restart or prevent NCT2 adjustment required (for example, delete data sets, perform GDG adjustments).

Corrective Action: No action is required.

CTR061I EXECUTION SIMULATION PHASE STARTED

Explanation: This information message is issued by the CONTROLR step when starting the execution phase under simulation mode. In this phase Control-M/Restart issues only the messages related to the special restart or prevent NCT2 adjustment required, without actually performing the adjustments.

Corrective Action: No action is required.

CTR062I processType OF JOB jobName STARTED

Explanation: This information message is issued by the CONTROLR step when starting the simulation (if processType is SIMULATION) or collecting of cross-reference statistics for job - data sets (if processType is REGISTRATION) of a job.

Corrective Action: No action is required.

CTR063S CONTROL-M/RESTART IS NOT APF AUTHORIZED

Explanation: The CONTROLR step is not APF authorized.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP. The job terminates after the CONTROLR step.

Corrective Action: Ensure that the STEPLIB for the CONTROLR step is on the APF authorization list in SYS1.PARMLIB.

CTR064S INVALID FUNCTION CALL func TO MODULE modName

Explanation: Internal Control-M/Restart error. This message is followed by other messages detailing the nature of the error.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP. The job terminates after the CONTROLR step.

Corrective Action: Notify BMC Customer Support.

CTR065S CONTROL-M/RESTART INITIALIZATION FAILED ON PHASE phase

Explanation: Internal Control-M/Restart error. This message is preceded by other messages detailing the nature of the error.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the value set for the ABNDTYP Control-M/Restart installation parameter. The job terminates after the CONTROLR step.

Corrective Action: Examine the preceding messages and take any corrective action associated with those messages. If the problem persists, notify BMC Customer Support.

CTR066I OID= orderId NUMBER OF SKIPPED STEPS nnnn WITH A TOTAL ELAPSED TIME hh.mm CPU TIME mmm MIN ss.cc SEC

Explanation: This information message indicates the elapsed and CPU time saved by skipping the indicated number of steps during the restart. This message is issued to the job syslog during Control-M/Restart step termination.

The variables in this message are:

nnnn - the number of skipped steps
hh.mm - the elapsed time saved, in hours (hh) and minutes (mm)
mmm ss.cc - CPU time saved, in minutes (mmm), seconds (ss) and hundredths of seconds (cc)

Corrective Action: No action is required.

CTR067I SIMULATION MODE WAS FORCED BY INSTALLATION PARAMETERS

Explanation: This information message indicates that the CTRSTAT Control-M/Restart installation parameter was set to ONLY. Control-M/Restart has been configured to issue statistics only, not to perform any actions.

Corrective Action: No action is required.

CTR070S DSN dsn SHOULD BE EXCLUDED, BUT IS NOT FOUND IN THE JOB

Explanation: A specific, non-generic, EXCLUDE DSN statement was specified for the dsn data set, but this data set was not referenced in any of the JCL DD statements in the job.

Control-M/Restart assumes that the data set is referenced in the JCL.

Corrective Action: Check the JCL and remove the EXCLUDE DSN statement. Another solution is to change the EXCLUDE DSN statement to a generic statement.

CTR071W MEMBER member DOES NOT EXIST IN CONTROL-M/RESTART PARM LIBRARY

Explanation: The $EXCLUDE or $KEEP member was not found in the Control-M/Restart PARM library. As both members exist in the PARM library as delivered, the member was renamed or deleted.

Corrective Action: Restore the $EXCLUDE or $KEEP member that was renamed or deleted.

CTR072I DSN dsn IN PROCEDURE processName, STEP stepName, DDNAME ddName HAS BEEN EXCLUDED FROM RESTART DECISION.

Explanation: The DD name that is defined in the $EXCLUDE member was excluded from Control-M/Restart restart processing. The $EXCLUDE member contains the definitions of DD names and data set names to be excluded from Control-M/Restart processing.

Corrective Action: No action is required.

CTR073I DSN dsn HAS BEED EXCLUDED FROM RESTART DECISION.

Explanation: This message informs the user that the data set that was defined in the $EXCLUDE member was excluded from Control-M/Restart restart processing. See message CTR072I.

Corrective Action: No action is necessary.

CTR075S ONLY CONTROLR STEP IS PRESENT IN THE JOB jobName

Explanation: The job contains only the CONTROLR step. This could be the result of the AutoEdit translation or the Control-M submit exit.

Corrective Action: Check the job and find out why there are no other steps in the job.

CTR076S processName WAS REQUESTED FROM PGMSTEP stepName PROCSTEP stepName BUT THE STEP WAS NOT FOUND IN THE JOB

Explanation: Control-M/Restart was requested to process the job from a specific step, but this step was not found in the job.

Corrective Action: Check the job step names against the restart parameters (against DO IFRERUN in Control-M), or against the manual restart decision. Correct them, and rerun the job.

CTR077S processName WAS REQUESTED TO PGMSTEP stepName PROCSTEP stepName BUT THE STEP WAS NOT FOUND IN THE JOB

Explanation: Control-M/Restart was requested to restart the job until a specific step, but this step was not found in the job.

Corrective Action: Check the job step names against the restart parameters (against DO IFRERUN in Control-M), or against the manual restart decision. Correct it, and rerun the job.

CTR078S "TO" STEP APPEARS BEFORE THE "FROM" STEP IN THE JOB

Explanation: Control-M/Restart was requested to restart the job from a specific step until another step, but the TO step appears in the job before the FROM step.

Corrective Action: Check the job step names against the restart parameters (against DO IFRERUN in the Control-M), or against the manual restart decision. Correct it, and rerun the job.

CTR079S DUPLICATE "FROM/TO" STEP NAMES FOUND IN THE JOB

Explanation: The CONTROLR step found more than one FROM or TO steps in the job, and could not determine the restart step.

Corrective Action: Change the job step names to avoid duplicate step names in the job.

CTR080I CONDITION CODE code WAS RESET FOR STEP stepName

Explanation: This information message indicates that a condition code was reset to zero by Control-M/Restart. Steps in the restarted job can refer to a reset condition code of zero from a step that is not executed in the restarted job. The CONTROLR step can use that condition code to affect the execution of the restarted job.

Corrective Action: No action is required.

CTR081I CONDITION CODE code IS RECAPTURED FOR STEP stepName

Explanation: This information message indicates that a condition code was recaptured by Control-M/Restart. Control-M/Restart captures the condition codes of the steps from the previous run or runs of the job. Steps in the restarted job can refer to a recaptured condition code from a step that is not executed in the restarted job. The CONTROLR step can use that condition code to affect the execution of the restarted job.

Corrective Action: No action is required.

CTR082I OID= orderId RESTARTING FROM STEP stepName TO STEP stepName

Explanation: This information message indicates the Control-M/Restart final restart decision. After all the required adjustments, the restarted job will execute in the specified range of steps.

Corrective Action: No action is required.

CTR083S DATASET ADJUSTMENT PROCEDURE FAILED

Explanation: The restarted job required data set adjustments like uncatalog or scratch a data set. For some reason the adjustment operation failed. This could be because the user exit failed the request, or the operation was failed by the operating system, or because of internal errors in Control-M/Restart.

Corrective Action: If you cannot locate the reason for the failure in previous messages, call BMC Customer Support for assistance.

CTR084E SCRATCH OF DATASET dsn FAILED

Explanation: The data set must be scratched in order to prevent duplicate data set errors, but the scratch operation failed.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on Control-M/Restart installation parameter ABNDTYP in CTRPARM. The job terminates after the CONTROLR step.

Corrective Action: Look in the job log or in the CONTROLR step messages for messages that will clarify the reason for the failure. Correct it, and rerun the job.

CTR085I DATASET dsn SCRATCHED FROM VOL= volser

Explanation: This information message indicates the data set is scratched from the volume in order to prevent duplicate data set errors when the job is restarted.

The data set is scratched from the volume.

Corrective Action: No action is required.

CTR086E "UNCATALG" OF DATASET dsn FAILED

Explanation: The data set must be uncataloged in order to prevent NOT CATLGD 2 situations, but the uncatalog operation failed.

Corrective Action: Look in the job log or in the CONTROLR step messages for messages that clarify the reason for the failure. Correct it, and rerun the job.

CTR087I DATASET dsn HAS BEEN UNCATALOGED

Explanation: This information message indicates that the data set is uncataloged in order to prevent NOT CATLGD 2 situations when the job is restarted.

The data set is uncataloged.

Corrective Action: No action is required.

CTR088E "CATALG" OF DATASET dsn FAILED

Explanation: The data set must be cataloged in order to prevent DATASET NOT FOUND errors when the job is restarted.

Corrective Action: Look in the job log or in the CONTROLR step messages for messages that will clarify the reason for the failure. Correct it, and rerun the job.

CTR089I DATASET dsn HAS BEEN CATALOGED ON VOLUME volser

Explanation: This information message indicates that the data set is cataloged in order to prevent DATASET NOT FOUND errors when the job is restarted.

The data set is cataloged.

Corrective Action: No action is required.

CTR090I CORRECTING REFERENCE OF GDG DATASET TO "dsn" FROM:

Explanation: This information message is followed by message CTR038I which describes the GDG name before adjustments. The GDG bias numbers must be reversed so that the relative references to them, within the restarted job, will refer to the correct generation of the data set.

The reference to the GDG data set is corrected.

Corrective Action: No action is required.

CTR091E REQUESTED VOLUMES vols ARE NOT MOUNTED

Explanation: The volumes containing the data set to be scratched were not mounted.

Corrective Action: Make sure that the listed volumes are mounted, and rerun the job.

CTR092E "SCRATCH" FAILED. RC="rc"

Explanation: An unusual condition was encountered on one or more volumes while scratching a data set.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

CTR093E INVALID VOLUME LIST volList

Explanation: An invalid volume list was used to scratch a data set. This is probably due to an internal error in Control-M/Restart, but it may also happen when attempting to run the job in a computer other than the one in which it abended.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

CTR094I CHANGING VOLUME(S) FOR DATASET TO - volser

Explanation: This information message precedes message CTR038I, which describes the data set name. The data set was cataloged to prevent DATASET NOT FOUND errors, and now resides on another volume. This is done because the data set name in the JCL of the job is not followed by a VOLSER, and the data set was not cataloged in the previous run of the job.

The internal MVS volume reference to the data set is corrected.

Corrective Action: No action is required.

CTR095I func FAILED. RC= rc REASON= rsn

Explanation: This information message indicates that a specified function was not performed for a data set. In the case of a severe error, this message precedes message CTR084E, which indicates the data set name causing the problem.

Corrective Action: No action is required.

CTR096W MODEL DSCB ATTRIBUTES WERE NOT USED FOR dsn. REASON rsn

Explanation: Control-M/Restart could not find MODEL DSCB attributes. While performing a GDG adjustment for a file (dsn), Control-M/Restart checks whether the DD statement for the GDG file refers explicitly to a MODEL DSCB. If so, Control-M/Restart tries to locate this MODEL DSCB. If for some reason the DSCB cannot be located, Control-M/Restart issues this warning message, accompanied by message CTR038I, and continues processing.

Possible values for reason: NOTFOUND or TYPEERR.

Corrective Action: No action is required.

CTR097I NCT2 HAS BEEN PREVENTED FOR DATASET

Explanation: This information message indicates that Control-M/Restart prevented the cataloging of the data set because the data set was already cataloged. This message precedes message CTR038I, which specifies the data set name.

Corrective Action: No action is required.

CTR098S JCL ERROR. DATASET " dsn " HAS A NAME OF ALIAS

Explanation: The JCL for the job contains a DD statement that specifies a data set dsn whose name is the same as the name of an alias in the catalog. A data set name cannot be the same as the name of an alias in the catalog, because it causes a JCL error when the job is run.

The CONTROLR step terminates with a nonzero condition code or with an abend code, depending on CONTROLR installation parameter ABNDTYP. The job terminates after the CONTROLR step.

Corrective Action: Correct the JCL of the job by specifying a unique data set name, and rerun or restart the job.

CTR099S THE FOLLOWING GDG BASE DOES NOT EXIST IN CATALOG ctlg

Explanation: The JCL for the job contains a DD statement that specifies a GDG data set whose GDG base name does not exist in the ctlg catalog. Any GDG data set specified in the job JCL should have a GDG base name defined in the catalog.

The CONTROLR step terminates with a nonzero condition code or with an abend code, depending on CONTROLR installation parameter ABNDTYP. The job terminates after the CONTROLR step.

Corrective Action: Define a GDG base name in the catalog by means of the IDCAMS utility, or correct the JCL of the problematic job. Specify the GDG data set with a GDG base name that exists in the catalog.

Parent Topic

CTR messages