Messages CTM900 through CTM9xx

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.

CTM901E INVALID OPTION (TRY "Y", "N", "R" OR BLANK)

Explanation: The user entered an invalid value into a field which may only contain Y, N, R or blank.

Corrective Action: Correct the input field and press Enter.

CTM902E INVALID OPTION (TRY "Y", "N" OR BLANK)

Explanation: The user entered an invalid value into a field which may only contain Y, N, or blank.

Corrective Action: Correct the input field and press Enter.

CTM903E "FORCE" CODE MUST BE ALONE.

Explanation: Another code is entered with the FORCE code in the same ON PGMST statement. No other code may be specified with FORCE in the same ON PGMST statement.

Corrective Action: Remove any other code from the current statement and put it in a different ON PGMST statement or remove the FORCE code.

CTM904E "FORCE" CODE VALID ONLY ON ANYSTEP

Explanation: The step name is not ANYSTEP. When the code is FORCE, the step name in an ON PGMST statement must be ANYSTEP.

Corrective Action: Correct the step name or remove the FORCE code.

CTM905E "FORCE" CODE NOT VALID WITH PROC

Explanation: There is data in the PROC field, but the code is FORCE. When the code is FORCE, the PROC field in an ON PGMST statement must be empty and the step name must be ANYSTEP.

Corrective Action: Clear the PROC field or remove the FORCE code.

CTM906S ACCUMULATION STOPPED BECAUSE OF A REQUEST FROM USER EXIT 005

Explanation: The CTMX005 Control-M user exit issued a return code to stop the run of the CTMJSA utility.

The utility stops executing with a condition code of 12.

Corrective Action: Check for messages from the user exit that will clarify the reason.

CTM907E "FORCE" CODE NOT VALID IN MULTIPLE ON STATEMENTS

Explanation: The FORCE code is in an ON PGMST statement that is connected by AND or OR to another ON PGMST statement. When the code is FORCE, no other ON PGMST statement may have an AND or OR relationship with it.

Corrective Action: Separate the ON PGMST statement containing it from other ON PGMST statements or remove the FORCE code.

CTM908E INVALID DO ACTION FOR "FORCE" CODE

Explanation: Invalid DO actions follow an ON PGMST statement that has a code of FORCE. When the code is FORCE, only COND, FORCEJOB, SET VAR and SHOUT actions are allowed.

Corrective Action: Remove the invalid DO actions from the ON PGMST statement containing the FORCE code and put them in a separate statement or remove the FORCE code.

CTM909E JOB LEVEL CODES VALID ONLY ON ANYSTEP

Explanation: A job level code was specified for a specific job step or range of steps in the job scheduling definition. Examples of job level codes are: JNRUN, JLOST, OK, and NOTOK. Job level codes relate to the overall result of the entire job execution, not to specific steps. They can only be specified with ON PGMSTEP ANYSTEP.

Corrective Action: Do not specify job level codes for specific steps or step ranges.

CTM90AE ON +EVERY IS VALID ONLY FOR CNNNN, SXXX, UNNN, FLUSH, SNRUN AND *****

Explanation: An ON step value of ON PGMSTEP +EVERY can only be specified with codes C nnnn, S xxx, U nnn, FLUSH, SNRUN and *****.

Corrective Action: Correct the Step value or the Codes value in the job scheduling definition to a valid combination.

CTM90BE "SNRUN" CODE NOT VALID ON ANYSTEP

Explanation: Code SNRUN is not valid for an ON PGMSTEP ANYSTEP statement.

Corrective Action: Correct the Step value or the Codes value in the job scheduling definition to a valid combination.

CTM911S IOA LOG FILE - WRITE ERROR

Explanation: I/O error while writing on IOA Log file.

Possible causes are:

• The file allocated to the DALOG DD statement is not the IOA Log file.
• The file allocated to the DALOG DD statement is the IOA Log, but it is of a different version of Control-M.
• Real I/O error on the IOA Log.

Corrective Action: Check the contents of the computer log for additional messages which may clarify the picture.

CTM912S ERROR IN CONTROL-x INSTALLATION PARAMETERS - INVALID DAYTIME

Explanation: Invalid format of the DAYTIME Control- x installation parameter. DAYTIME is the start time of the Control-M work day in your installation. Valid formats are +hhmm or -hhmm.

For more details see the section that describes installation parameters in the chapter for the appropriate products in the INCONTROL for z/OS Installation Guide.

The requested function terminates.

Corrective Action: Call your system programmer to correct the DAYTIME parameter in the CT xPARM member.

CTM913S OPEN OF DDNAME "SYSPRINT" FAILED

Explanation: The opening of the print file failed. Possible causes are:

• The DD statement SYSPRINT is missing.
• The data set described by the DD statement SYSPRINT cannot be accessed for sequential write.

The program stops executing.

Corrective Action: Correct the JCL and submit again.

CTM914S ERROR IN IOA INSTALLATION PARAMETERS - INVALID DATETYP

Explanation: Highlighted, unrollable message.

The DATETYP IOA Installation Parameter is invalid. DATETYP is the type of date format used in the installation. Valid formats are:

• A - mmddyy
• W - ddmmyy
• J - yymmdd

For more details, see the section that describes how to set IOA installation parameters in the IOA chapter of the INCONTROL for z/OS Installation Guide.

The requested function stops.

Corrective Action: Call your system programmer to correct the DATETYP parameter in the IOAPARM member.

CTM916W PROGRAM pgm WAITING FOR resourceName

Explanation: One of the IOA monitor internal programs detected an IOA resource in use by a TSO user or batch job. This message normally appears a few times a day.

The variables in this message are:

• pgm - the name of the internal program that is waiting for the resource that is in use
• rname - the name of the resource that is in use

Valid values are:

The message is displayed on the operator console.

Corrective Action: The user response depends on the circumstances, as follows:

• If the message appears many times every few seconds, the file may be hung. This situation must be resolved by determining which program is holding the specified rname. Look for the IOA QNAME that is specified in the IOA Installation Parameter and take appropriate corrective action.
• If pgm is CTMFRM/CTDFRM and the rname is CONTROLM/CONTROLD, some possible reasons are:
  • there are several Control-M/D monitors running with the same QNAME
  • there is a user daily job running that has a date control record in which columns 60 through 65 are not blank, meaning that it is acting as the Control-M/D New Day procedure and therefore Control-M/D has been enqueued
  • the Control-M/D New Day procedure was started externally (manually) rather than being started by the monitor, and as a result waits for the monitor to be suspended

  Take appropriate corrective action.

• If the program name pgm is CTMJES and the resourceName is JES_SSRQ, then Control-M (in its postprocessing phase) has called the JES2 interface using IEFSSREQ (a JES2 subsystem request) and is waiting for some function to be executed by JES2, but the execution of that function is being delayed in JES2. If the message persists in this situation, prepare the Control-M monitor full output and contact BMC Customer Support.

CTM918S INSUFFICIENT MEMORY TO RUN CONTROL-x

Explanation: Highlighted, unrollable message.

More memory is required for the INCONTROL monitor.

The specified monitor will shut down.

Corrective Action: Increase the REGION size of the specified monitor.

CTM919S INTERNAL ERROR IN CONTROL-M MONITOR

Explanation: Highlighted, unrollable message.

An internal error occurred in the Control-M monitor.

The Control-M monitor abends with the user abend 0008.

Corrective Action: Try to start the Control-M monitor again. In any case, prepare the dump and contact BMC Customer Support.

CTM91ES ENVIRONMENT ERROR. CONTROL-M MONITOR INITIALIZATION ABORTED.

Explanation: The Control-M monitor detected an environment initialization error at startup.

Control-M monitor initialization is aborted.

Corrective Action: Verify that Control-M is fully installed, and notify the INCONTROL administrator.

CTM91FS CONTROL-M NOT FULLY INSTALLED. MONITOR INITIALIZATION ABORTED.

Explanation: At startup, the Control-M monitor detected that Control-M is not fully installed, and cannot initialize the IOA environment.

Control-M monitor initialization is aborted.

Corrective Action: Verify that Control-M is fully installed, and notify the INCONTROL administrator.

CTM920S AJF SIZE IS NOT EQUAL TO AJFSIZE PARAMETER SPECIFIED IN CTMPARM.

Explanation: Highlighted, unrollable message.

The value of the AJFSIZE parameter in the CTMPARM file used by a Control-M monitor is different from the value of the AJFSIZE parameter in the Active Jobs file (AJF).

The AJF was formatted using an AJFSIZE parameter from a specific CTMPARM file. The Control-M monitor also uses an AJFSIZE parameter from a CTMPARM file, which is not necessarily the same CTMPARM file used to format the AJF. The value of the AJFSIZE parameter used by the Control-M monitor must match the value of AJFSIZE in the AJF.

The Control-M monitor shuts down.

Corrective Action: Ask the INCONTROL administrator to do one of the following:

• Change the value of AJFSIZE in the CTMPARM file used by the Control-M monitor to the value of AJFSIZE in the AJF.
• Reformat the AJF using a CTMPARM file in which AJFSIZE has the same value as the AJFSIZE used by the Control-M monitor.

Once one of these has been performed, restart the monitor.

CTM921I ACCUMULATION OF JOB EXECUTION STATISTICS STARTED

Explanation: This information message is a normal starting message of the CTMJSA utility.

Corrective Action: No action is required.

CTM922I ACCUMULATION OF JOB EXECUTION STATISTICS ENDED WELL

Explanation: This information message is a normal ending message of the CTMJSA utility.

Corrective Action: No action is required.

CTM923S OPEN OF PARAMETERS FILE FAILED. DDNAME "DAJSAIN"

Explanation: Open of parameters file for the CTMJSA utility failed.

This can be due to one of the following:

• The DAJSAIN DD statement missing.
• The data set described by the DAJSAIN DD statement cannot be opened for sequential read.

The utility stops executing with a condition code of 12.

Corrective Action: Correct the JCL of the job and rerun it.

CTM92CS INVALID PARAMETER, VALID PARAMETERS ARE ACT=R/W, TYPE=F/V

Explanation: An invalid parameter was passed to the IOADIG utility.

Valid ACT parameter values are:

• R - Perform a read-only check. Do not correct detected errors.
• W - If an error is detected, correct it.

Valid TYPE parameter values are:

• F - Fixed length records in data file.
• V - Variable length records in data file.

The utility terminates with a return code of 24.

Corrective Action: Rerun the IOADIG utility after setting its parameters to valid values.

CTM92TE SIZE OF CKPJNL FILE DIFFERS FROM SIZE OF AJF -- JOURNALING DISABLED

Explanation: The size of the Active Jobs file (AJF) base image file differs from the size of the production AJF.

The CKPJNL base image file in the AJF is created after New Day processing and is used by the CTMRSTR restore utility. The size of this file must be identical to that of the production AJF.

The Control-M monitor halts processing and waits for instructions as described in message CTML12W.

Corrective Action: Reply C, I, or E to message CTML12W.

CTM92UE ALLOCATION OF FILE fileName FAILED RC rc

Explanation: The Control-M monitor failed to allocate the fileName file. The reason for the failure is described by a return code value of rc.

The Control-M monitor deallocates the file and waits for instructions as described in message CTML12W.

Corrective Action: Reply C, I, or E to message CTML12W. Note the message, including return code, prepare the Control-M monitor full output, and contact BMC Customer Support.

CTM931I CLEAN FOR IOA CONDITIONS FILE STARTED

Explanation: This information message indicates that the IOACLCND utility started.

Corrective Action: No action is required.

CTM932I CLEAN FOR IOA CONDITIONS FILE ENDED

Explanation: This information message indicates that the cleaning of the IOA Conditions file by the IOACLCND utility ended successfully.

Corrective Action: No action is required.

CTM933S FILE ALLOCATED TO DDNAME "DASINC" IS NOT IOA SYNCHRONIZATION FILE

Explanation: The data set described by the DASINC DD statement is not IOA Synchronization file. This message is produced by the IOACLCND IOA utility.

Possible causes are:

• The file allocated to the DASINC DD statement is not the Synchronization file.
• The file allocated to the DASINC DD statement is the Synchronization file, but it is of a different version or of a different IOA installation.

The utility stops executing.

Corrective Action: Correct the JCL for the job.

CTM934E INVALID PARAMETER: - parm

Explanation: An invalid parameter (parm) was passed to the IOACLCND utility.

In this message, parm identifies the invalid parameter.

For a list of valid parameters, see the IOACLCND utility in the INCONTROL for z/OS Utilities Guide.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the parameter line.

CTM935E MISSING PARAMETER AFTER: - parm

Explanation: A subparameter of a parameter of the IOACLCND utility is missing. A subparameter is expected after the parm parameter.

For valid syntax, see the IOACLCND utility in the INCONTROL for z/OS Utilities Guide.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the parameter line.

CTM936E REDUNDANT PARAMETER: - parm

Explanation: There is a redundant parameter in a parameter line for the IOACLCND utility.

For details, see the IOACLCND utility in the INCONTROL for z/OS Utilities Guide.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the parameter line.

CTM937S IOA CONDITIONS FILE WAS NOT CLEANED

Explanation: Result of a previous error in the IOACLRES utility. A previous message should appear, containing the reason for not cleaning the Conditions file.

The utility stops executing.

Corrective Action: Correct the problem and rerun the utility.

CTM939E DATE RANGE IS GREATER THAN ONE YEAR

Explanation: The date range specified in the FROM and TO parameters is greater than one year (the IOACLRES utility). The TO date is greater than the FROM date by more than a year. There is no way to IGNORE more than one year.

The utility will stop executing with a condition code of 08.

Corrective Action: Correct the parameters and rerun.

CTM942S OPEN OF IOA MANUAL CONDITIONS FILE FAILED

Explanation: Open of the IOA Manual Conditions file failed. Possible causes are:

• The DANRES DD statement is missing.
• The file allocated to the DANRES DD statement is not the IOA Manual Conditions file.
• The file allocated to the DANSINC DD statement is the IOA Manual Conditions Synchronization file, but it is of a different version or of a different IOA installation.

Corrective Action: Correct the JCL for the job or the allocations of the CLIST.

CTM943S OPEN OF IOA MANUAL CONDITIONS SYNCHRONIZATION FILE FAILED

Explanation: The IOAFRNRS utility, which is used to allocate and format the file, failed to open the file for formatting.

Possible causes are:

• The DACKPT DD statement is missing.
• There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL, and rerun the job.

CTM944I BUILDING OF IOA MANUAL CONDITIONS FILE STARTED

Explanation: This information message indicates that the IOAFRNRS utility, which is allocates and formats the Manual Conditions file, started.

Corrective Action: No action is required.

CTM945I BUILDING OF IOA MANUAL CONDITIONS FILE ENDED

Explanation: This information message indicates that the IOAFRNRS utility, which allocates and formats the Manual Conditions file, ended normally.

Corrective Action: No action is required.

CTM945W < resource name>/< resource amount> RELEASED BY CTMRLR, WILL BE FREED FROM WORKLOAD < workload name> AFTER JOB ENDS

Explanation: The resource name was released by the CTMRLR utility, and will be freed from the specified workload after the job ends.

Corrective Action: No action is required.

CTM946S IOA MANUAL CONDITIONS FILE WAS NOT BUILT

Explanation: The IOAFRNRS utility failed.

Corrective Action: Look for previous error messages which will describe the type of the error.

CTM947E INSUFFICIENT MEMORY IN CONTROL-M MONITOR - TOO MANY STCS WITH SAME NAME

Explanation:This message is also displayed on the output of the monitor.

There are too many STCs with the same name.

The STC will end NOTOK.

Corrective Action: Purge the unneeded STCs with the duplicate names from the spool.

CTM950S OPEN FAILED FOR DDNAME "DARESF"

Explanation: Open of Control-M Resources file failed (the DARESF DD statement). Possible causes are:

• The DARESF DD statement is missing.
• The data set described by the DARESF DD statement is not the Control-M Resources file.
• The data set described by the DARESF DD statement is the Control-M Resources file of a different version or a different Control-M monitor.

The Control-M monitor shuts down.

Corrective Action: Correct the JCL for the Control-M procedure, and start it again.

CTM955I OID=orderId ORPHAN CONTROL contResource MODE {E | S} WAS AUTOMATICALLY DELETED BY THE MONITOR

Explanation: This information message indicates that the monitor released the contResource Control resource, with the mode Exclusive (E) or Shared (S), because there is no job that controls it.

Corrective Action: No action is required.

CTM956I OID=orderId ORPHAN CONTROL quant-res QUANTITY num WAS AUTOMATICALLY DELETED BY THE MONITOR

Explanation: This information message indicates that the monitor released the specified number (num) of the indicated Quantitative resource (quant-res), because there are no jobs that control them.

Corrective Action: No action is required.

CTM95BE OPEN OF CONTROL-M HISTORY FILE (DDNAME "DAHIST") FAILED. RC=rc

Explanation: The user entered the HISTORY command followed by the name of a History file, but there is an error in opening the specified history file.

Corrective Action: Verify that the specified History file is valid. Contact BMC Customer Support and report the received return code.

CTM95CE CLOSE OF CONTROL-M HISTORY FILE (DDNAME "DAHIST") FAILED. RC=rc

Explanation: The user entered the HISTORY command followed by the name of a History file, but there is an error in closing the specified history file.

Corrective Action: Verify that the specified History file is not being used by another application. Contact BMC Customer Support and report the received return code.

CTM95DE PARAMETER FOR "HIST" COMMAND IS NOT SUPPORTED UNDER ONLINE MONITOR

Explanation: The HISTORY command followed by the name of a History file cannot be used with the online monitor.

Corrective Action: No action is required.

CTM95ES RESOURCE FILE INTERNAL ERROR

Explanation: Severe Control-M internal error in the Resource file.

A snap dump is written to the DATRACE DD statement, and the monitor shuts down.

Corrective Action: Do the following:

1. Send the following to BMC Customer support:
   1. the complete sysout from the Control-M monitor
   2. the Resource file
   3. the CKP file
   4. IOAPARM
   5. CTMPARM
   6. IOA Log file
2. Re-start the Control-M monitor.

CTM95FS INTERNAL ERROR: ACTUAL NUMBER OF BASE SLOTS GREATER THAN RE0BASE#

Explanation: Severe Control-M internal error in the Resource file.

A snap dump is written to the DATRACE DD statement, and the monitor shuts down.

Corrective Action: Do the following:

1. Send the following to BMC Customer support:
   1. the complete sysout from the Control-M monitor
   2. the Resource file
   3. the CKP file
   4. IOAPARM
   5. CTMPARM
   6. IOA Log file
2. Re-start the Control-M monitor.

CTM95GE POST PROCESSING ERROR. INSUFFICIENT FREESPACE FOR 'SET VAR' STATEMENTS

Explanation: Control-M failed to handle a DO SETVAR post processing statement because there was not enough space in the corresponding job record in the AJF. The indicator POST-PROCESSING FAILED is set for the job.

Corrective Action: Contact IOA administrator to consider increasing the FREESPAC= installation parameter in CTMPARM. If it is not suitable or does not help, contact IOA Technical support.

CTM966E RULE-BASED CALENDAR calName NOT FOUND

Explanation: A rule-based calendar (RBC) specified in the advanced scheduling parameters (that is, in a time period of Type 6) in a Workload Policy rule was not recognized. The message is issued to the Control-M monitor, and is followed by message CTMWLGE, which provides more details about the Workload Policy. The Workload Policy rule is ignored.

Corrective Action: Correct the name of the RBC specified in the Workload Policy rule. Alternatively, define a new RBC with the specified name through the IOA Calendar Facility (Screen 8).

CTM971S OPEN OF CONTROL-M {ACTIVE | HISTORY} JOBS FILE FAILED

Explanation: Either the FORMCKP utility (which allocates and formats the Active Jobs file) or the FORMHST utility (which allocates and formats the Active History file) failed to open the file for formatting.

Possible causes are:

• The DACKPT DD statement (for the Active Jobs file) or the DAHIST DD statement (for the History Jobs file) is missing.
• There is insufficient memory for the job.

The utility ends with a condition code of 08.

Corrective Action: If a DD statement is missing, add the correct DD statement are rerun the job. If the problem is memory, specify a higher value for the REGION parameter.

CTM972I BUILDING OF CONTROL-M {ACTIVE | HISTORY} JOBS FILE STARTED

Explanation: This information message indicates the normal start of the FORMCKP utility or the FORMHST utility. The FORMCKP utility allocates and formats the Active Jobs file. The FORMHST utility allocates and formats the Active History file.

Corrective Action: No action is required.

CTM973I BUILDING OF CONTROL-M {ACTIVE | HISTORY} JOBS FILE ENDED

Explanation: This information message indicates the normal termination of either the FORMCKP utility or the FORMHST utility. The FORMCKP utility allocates and formats the Active Jobs file. The FORMHST utility allocates and formats the Active History file.

Corrective Action: No action is required.

CTM974S Control-M {ACTIVE | HISTORY} JOBS FILE WAS NOT BUILT

Explanation: Either the FORMCKP utility, which allocates and formats the Active Jobs file, or the FORMHST utility, which allocates and formats the Active History file, failed.

Corrective Action: Check the previous error messages which describe the type of error, and correct the problem accordingly.

CTM975S Control-M {ACTIVE | HISTORY} JOBS FILE WRITE ERROR

Explanation: An I/O error occurred while formatting the Control-M Active Jobs file or History Jobs file. This error may be caused by an incompatibility between the installation parameters (CTMPARM) that define the Active Jobs file or History Jobs file, and the JCL SPACE and/or DCB parameters.

The utility stops executing with a condition code of 08.

Corrective Action: Correct either the JCL or the Installation Parameters file.

CTM982S OPEN OF IOA CONDITIONS FILE FAILED

Explanation: The IOAFRRES IOA utility, which is used to allocate and format the IOA Conditions file, failed to open the file for formatting.

Possible causes are:

• The DARESC DD statement is missing.
• There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTM983S OPEN OF IOA SYNCHRONIZATION FILE FAILED

Explanation: The IOAFRRES IOA utility, which is used to allocate and format the Control-M Resources Synchronization file, failed to open the file for formatting.

Possible causes are:

• The DASINC DD statement is missing.
• There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTM984I BUILDING OF IOA CONDITIONS FILE STARTED

Explanation: This information message indicates that the IOAFRRES utility, which allocates and formats the IOA Conditions file, has started.

Corrective Action: No action is required.

CTM985I BUILDING OF IOA CONDITIONS FILE ENDED

Explanation: This information message indicates that the IOAFRRES utility, which allocates and formats the IOA Conditions file, has ended normally.

Corrective Action: No action is required.

CTM986S IOA CONDITIONS FILE WAS NOT BUILT

Explanation: The IOAFRRES utility failed.

Corrective Action: Look for previous error messages that describe the type of error.

CTM988S DATE SHOULD NOT BE GREATER THAN YESTERDAY

Explanation: Invalid date specified for archival or backup (the CTMLGC utility). The archive date should not be greater than yesterday’s date.

The utility stops execution with a condition code of 08.

Corrective Action: Correct the date field.

CTM989S OPEN OF DDNAME "DALOGHIS" FAILED. LOG ARCHIVAL NOT PERFORMED

Explanation: Open of the log archival data set failed (the CTMLGC utility).

Possible causes are:

• The DALOGHIS DD statement missing.
• The DALOGHIS DD statement describes a file which is not in the format of the IOA Log.

The utility stops execution with a condition code of 08.

Corrective Action: Correct JCL for the job. You should run the CTMFRLOG utility to allocate and format an archival file in exactly the same format as the IOA Log.

CTM990I action OF IOA LOG STARTED

Explanation: This information message is a normal message which is issued when starting to backup the IOA Log (the CTMLGC utility).

Corrective Action: No action is required.

CTM991I action OF IOA LOG ENDED

Explanation: This information message is a normal message which is issued when the backup of the IOA Log ends (the CTMLGC utility).

Corrective Action: No action is required.

CTM992W OPEN OF DDNAME "DALOGBKP" FAILED, BACKUP OF IOA LOG NOT TAKEN

Explanation: Open of the data set described by the DALOGBKP DD statement failed.

Possible causes are:

• The DALOGBKP DD statement missing.
• The data set described by the DALOGBKP DD statement cannot be opened for sequential write.

Backup of IOA Log not taken. Processing continues.

Corrective Action: If you want to backup the entire Log file, correct the JCL for the job.

CTM993S OPEN OF DDNAME "DALGCIN" FAILED. LOG ARCHIVAL NOT PERFORMED

Explanation: Open of the data set described by the DALGCIN DD statement failed.

Possible causes are:

• The DALGCIN DD statement missing.
• The data set described by the DALGCIN DD statement cannot be opened for sequential read.

Log archival is not performed.

Corrective Action: Correct the JCL for the job.

CTM994S FILE CONNECTED TO DDNAME "DALGCIN" IS EMPTY

Explanation: The data set described by the DALGCIN DD statement is empty.

Log archival is not performed.

Corrective Action: Correct the JCL for the job.

CTM995S RECORD LENGTH OF DDNAME "DALGCIN" IS NOT 80

Explanation: Record length of data set described by the DALGCIN DD statement must be 80 bytes.

Log archival is not performed.

Corrective Action: Check the contents of data set described by the DALGCIN DD statement.

CTM996S "UNTIL DATE" OF LOG ARCHIVAL IS NOT A VALID DATE

Explanation: Invalid parameter for UNTIL date.

Corrective Action: Correct the UNTIL date parameter of the Log archival utility.

CTM997S NUMBER OF DAYS TO KEEP IN LOG FILE IS NOT NUMERIC

Explanation: Invalid number of days to keep in the Log file.

The number of days to keep in the Log file must be numeric.

Corrective Action: Correct the number of days.

CTM998S ARCHIVAL FILE ALLOCATED TO "DALOGHIS" IS FULL

Explanation: Archival file allocated to the DALOGHIS DD statement is full.

Archival will not be executed.

Corrective Action: No action is required.

CTM999S NOTHING TO DO. NEITHER BACKUP NOR ARCHIVAL IS NEEDED

Explanation: Neither file DALOGHIS nor file DALOGBKP has been opened by the CTMLGC utility.

The utility terminates with a return code of 12.

Corrective Action: No action is necessary.

CTM9B1E SYSTEM LOGGER CONNECT REJECTED, DASD-ONLY LOG STREAM IS ALREADY CONNECTED TO BY ANOTHER LOG STREAM IN THE SYSPLEX

Explanation: The System Logger rejected an attempt to connect to a DASD-only log stream because another log stream in the Sysplex is already connected. Only applications from the same system (LPAR) can connect simultaneously to the DASD-only log streams. If you are using DASD-only log streams, then Control-M, CMEM or Control-O, and IADDC (the CONNECT DIRECT interface) must all be running in the same LPAR.

The attempt to connect is rejected.

Corrective Action: Determine which system you want to connect to the log stream, and rerun the component that failed in the correct system.

If you want all members in a Sysplex to have access to the log stream, use coupling facility log streams rather than DASD-only log streams. For more information, see the description of sysplex configuration parameters in the INCONTROL for z/OS Installation Guide.