Messages CTB900 through CTB9xx

This group includes messages for the Control-M/Analyzer product.

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

Explanation: The user specified an invalid value in a field which may only contain Y (Yes), N (No) or blank.

Corrective Action: Correct the input field and press enter.

CTB912S ERROR IN CONTROL- x INSTALLATION PARAMETERS - INVALID DAYTIME

Explanation: The format of the DAYTIME Control- x Installation parameter is invalid. 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.

CTB913S OPEN OF DDNAME "SYSPRINT" FAILED

Explanation: The opening of a 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.

CTB971I CONTROL-M/ANALYZER UTILITY CTBJAFIG STARTED

Explanation: This information message indicates the normal start of the CTBJAFIG Control-M/Analyzer utility.

Corrective Action: No action is required.

CTB971S ERROR OPENING SYSPRINT

Explanation: This information message indicates that the CTBDBIV Control-M/Analyzer utility failed to open the print file referenced by the SYSPRINT DD statement.

Possible causes are:

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

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTB972I CHECKING OF THE JOB ACTIVITY FILE IN PROGRESS

Explanation: This information message indicates that CTBJAFIG Control-M/Analyzer utility has begun checking the Control-M/Analyzer Rule Activity File.

Corrective Action: No action is required.

CTB973I CHECKING OF THE REPORT FILE IN PROGRESS

Explanation: The CTBJAFIG Control-M/Analyzer utility has begun checking the Control-M/Analyzer report file.

Corrective Action: No action is required.

CTB974I LOGICAL RELATION BETWEEN THE JOB ACTIVITY AND THE REPORT FILES NOW BEING CHECKED

Explanation: This information message indicates that the CTBJAFIG Control-M/Analyzer utility has begun checking the logical relation between the Job Activity and report files.

Corrective Action: No action is required.

CTB975E INVALID INPUT PARAMETER

Explanation: The CTBJAFIG Control-M/Analyzer utility failed to analyze the FILE= name job input statement.

The utility stops executing with a condition code of 12.

Corrective Action: Correct the FILE input parameter and rerun the job.

CTB976S ERROR OPENING SYSPRINT

Explanation: The CTBJAFIG Control-M/Analyzer utility failed to open the print file referenced by the SYSPRINT DD statement.

Possible causes are:

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

The utility stops executing with a condition code of 16.

Corrective Action: Correct the JCL and rerun the job.

CTB977S ERROR OPENING THE JOB ACTIVITY FILE

Explanation: The CTBJAFIG Control-M/Analyzer utility failed to open the Job Activity Data file referenced by the DAJAF DD statement.

Possible causes are:

• The DAJAF DD statement is missing.
• The data set referenced by the DAJAF DD statement is not the Control-M/Analyzer Job Activity Data file.
• An internal error occurred while the Control-M/Analyzer Job Activity Data file was being opened.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the JCL and rerun the job. If an error occurred while opening the file, notify your INCONTROL administrator.

CTB978S ERROR OPENING THE REPORT FILE

Explanation: The CTBJAFIG Control-M/Analyzer utility failed to open the report Data file referenced by the DAREP DD statement.

Possible causes are:

• The DAREP DD statement is missing.
• The data set referenced by the DAREP DD statement is not the Control-M/Analyzer Report Data file.
• An internal error occurred while the Control-M/Analyzer Report Data file was being opened.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the JCL and rerun the job. If an error occurred while opening the file, notify your INCONTROL administrator.

CTB979S INSUFFICIENT STORAGE FOR PROCESSING THE REPORT FILE

Explanation: The CTBJAFIG Control-M/Analyzer utility requires more storage to check the Control-M/Analyzer Report Data file.

The utility stops executing with a condition code of 08.

Corrective Action: Increase the REGION size and rerun the job.

CTB97AS INSUFFICIENT STORAGE FOR PROCESSING THE JOB ACTIVITY FILE

Explanation: The CTBJAFIG Control-M/Analyzer utility requires more storage to check the Control-M/Analyzer Job Activity Data file.

The utility stops executing with a condition code of 08.

Corrective Action: Increase the REGION size and rerun the job.

CTB97BS INSUFFICIENT STORAGE FOR COMPARING THE JOB ACTIVITY AND REPORT FILES

Explanation: The CTBJAFIG Control-M/Analyzer utility requires more storage to check the logical relation between the Control-M/Analyzer Job Activity and Report Data files.

The utility stops executing with a condition code of 08.

Corrective Action: Increase the REGION size and rerun the job.

CTB97CS CORRECTION OF THE JOB ACTIVITY FILE FAILED

Explanation: The CTBJAFIG Control-M/Analyzer utility failed to correct errors detected in the Control-M/Analyzer Job Activity Data file.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB97DS CORRECTION OF THE REPORT FILE FAILED

Explanation: The CTBJAFIG Control-M/Analyzer utility failed to correct errors detected in the Control-M/Analyzer Report Data file.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB97ES CORRECTION OF THE LOGICAL RELATION BETWEEN THE JOB ACTIVITY AND REPORT FILES FAILED

Explanation: The CTBJAFIG Control-M/Analyzer utility failed to correct errors detected in the logical relation between the Job Activity and Report Data files.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB97FS INVALID RECORD TYPE IN THE JOB ACTIVITY FILE

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in the Job Activity Data file. This message is followed by the CTB98FI message which displays the address of the invalid record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB980S INCORRECT NUMBER OF RECORDS IN THE JOB ACTIVITY FILE

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in the Job Activity Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB981S INCORRECT NUMBER OF FREE RECORDS IN THE JOB ACTIVITY FILE

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in the Job Activity Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB982S ERROR IN INFO RECORD:

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in a record in the Job Activity Data file. This message is followed by other messages which display information about the record in error.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB983S ERROR IN INVOCATION RECORD:

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in a record in the Job Activity Data file. This message is followed by other messages which display information about the record in error.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB984S ERROR IN JOB RECORD:

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in a record in the Job Activity Data file. This message is followed by other messages which display information about the record in error.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB985S INVALID RECORD TYPE IN THE REPORT FILE

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in the Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB986S INCORRECT NUMBER OF RECORDS IN THE REPORT FILE

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in the Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB987S INCORRECT NUMBER OF FREE RECORDS IN THE REPORT FILE

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in the Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB988S ERROR IN SECONDARY REPORT RECORD:

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in a record in the Report Data file. This message is followed by other messages which display information about the record in error.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB989S ERROR IN PRIMARY REPORT RECORD:

Explanation: The CTBJAFIG Control-M/Analyzer utility detected an error in a record in the Report Data file. This message is followed by other messages which display information about the record in error.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB98AS INVOCATION RECORD FOR THIS REPORT DOES NOT EXIST

Explanation: While checking the logical relation between the Control-M/Analyzer Job Activity and Report Data files, The CTBJAFIG Control-M/Analyzer utility found a record in the Report Data file, but did not find the corresponding record in the Job Activity Data file.

This message is followed by a message that displays the address of the unmatched record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB98BS REPORT RECORD FOR THIS INVOCATION RECORD DOES NOT EXIST

Explanation: While checking the logical relation between the Control-M/Analyzer Job Activity and Report Data files, the CTBJAFIG Control-M/Analyzer utility found a record in the Job Activity Data file, but did not find the corresponding record in the Report Data file.

This message is followed by a message that displays the address of the unmatched record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB98CI INTEGRITY CHECKING ENDED WITH RETURN CODE rc

Explanation: This information message indicates normal termination of the CTBJAFIG Control-M/Analyzer utility.

Corrective Action: No action is required.

CTB98DE NO JOB RECORDS IN THE JOB ACTIVITY FILE

Explanation: The CTBJAFIG Control-M/Analyzer utility did not check the Job Activity Data file because it did not find any Job records in the file. It is likely that the file is empty.

The utility stops executing with a condition code of 32.

Corrective Action: Check whether or not the file is empty. If the file is empty, there is no problem. If the file is not empty, notify your INCONTROL administrator.

CTB98EE NO PRIMARY REPORT RECORDS IN THE REPORT FILE

Explanation: The CTBJAFIG Control-M/Analyzer utility did not check the Report Data file because it did not find any Primary Report records in the file. It is likely that the file is empty.

The utility stops executing with a condition code of 32.

Corrective Action: Check whether or not the file is empty. If the file is empty, there is no problem. If the file is not empty, notify your INCONTROL administrator.

CTB98FI RBA = rba

Explanation: This information message displays the address of the record when the CTBJAFIG Control-M/Analyzer utility detects a record in error. This message follows the error message which contains details about the error.

Corrective Action: No action is required.

CTB990S INVALID REFERENCE TO THE FIRST ELEMENT IN THE SUB-SEQUENCE

Explanation: A problem occurred while the CTBJAFIG Control-M/Analyzer utility was accessing the Job Activity or Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB991S INVALID REFERENCE TO THE LAST ELEMENT IN THE SUB-SEQUENCE

Explanation: A problem occurred while the CTBJAFIG Control-M/Analyzer utility was accessing the Job Activity or Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB992S INVALID KEY OR BACK-POINTER IN THE SUB-SEQUENCE

Explanation: A problem occurred while the CTBJAFIG Control-M/Analyzer utility was accessing the Job Activity or Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB993S ERROR IN THE RECORD SUB-SEQUENCE

Explanation: A problem occurred while the CTBJAFIG Control-M/Analyzer utility was accessing the Job Activity or Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB994S INVALID BACK-POINTER IN THE RECORD

Explanation: A problem occurred while the CTBJAFIG Control-M/Analyzer utility was accessing the Job Activity or Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB995S INVALID RECORD TYPE IN THE RECORD SEQUENCE

Explanation: A problem occurred while the CTBJAFIG Control-M/Analyzer utility was accessing the Job Activity or Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB996S LOOP DETECTED IN INFO RECORD SEQUENCE

Explanation: The CTBJAFIG Control-M/Analyzer utility detected a loop in the Information record sequence in the Job Activity Data file. This message is followed by the CTB98FI message, which displays the addresses of the records included in the loop.

The utility bypasses the loop and continues normal execution.

Corrective Action: Notify your INCONTROL administrator about the loop.

CTB997S LOOP DETECTED IN INVO RECORD SEQUENCE

Explanation: The CTBJAFIG Control-M/Analyzer utility detected a loop in the Invocation record sequence in Rule Activity File. This message is followed by the CTB98FI message, which displays the addresses of the records included in the loop.

The utility bypasses the loop and continues normal execution.

Corrective Action: Notify your INCONTROL administrator about the loop.

CTB998S LOOP DETECTED IN SECONDARY REPORT RECORD SEQUENCE

Explanation: The CTBJAFIG Control-M/Analyzer utility detected a loop in the Secondary Report record sequence in report file. This message is followed by the CTB98FI message, which displays the addresses of the records included in the loop.

The utility bypasses the loop and continues normal execution.

Corrective Action: Notify your INCONTROL administrator about the loop.

CTB999S INVALID KEY FOUND IN RECORD

Explanation: A problem occurred while the CTBJAFIG Control-M/Analyzer utility was accessing the Job Activity or Report Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB99AS JOB RECORD HAS NO INVOCATION RECORDS

Explanation: No Invocation records were found for the job record in the Job Activity Data file.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB99BI CORRECTION OF JOB ACTIVITY FILE IS IN PROGRESS

Explanation: This information message indicates that the CTBJAFIG Control-M/Analyzer utility has begun correcting the Control-M/Analyzer Job Activity Data file.

Corrective Action: No action is required.

CTB99CI CORRECTION OF REPORT FILE IS IN PROGRESS

Explanation: This information message indicates that the CTBJAFIG Control-M/Analyzer utility has begun correcting the Control-M/Analyzer Report Data file.

Corrective Action: No action is required.

CTB99DI LOGICAL RELATION BETWEEN THE JOB ACTIVITY AND REPORT FILES NOW BEING CORRECTED

Explanation: This information message indicates that the CTBJAFIG Control-M/Analyzer utility has begun correcting the logical relation between the Control-M/Analyzer Job Activity and Report Data files.

Corrective Action: No action is required.

CTB99EI JOB RECORD HAS BEEN DELETED record

Explanation: This information message indicates that the CTBJAFIG Control-M/Analyzer utility deleted the record job record from the Job Activity Data file because the record was in error. This message is followed by other messages that give additional information about the deleted record.

Corrective Action: No action is required.

CTB99FI INVOCATION RECORD HAS BEEN DELETED record

Explanation: This information message indicates that the CTBJAFIG Control-M/Analyzer utility deleted the record invocation record from the Job Activity Data file because the record was in error. This message is followed by other messages that give additional information about the deleted record.

Corrective Action: No action is required.

CTB9A1E INVALID STATEMENT IN CRITERIA DEFINITION

Explanation: The CTBDBVCP Control-M/Analyzer utility failed due to syntax errors in criteria definition input statements.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the input statements and rerun the job.

CTB9A2E INVALID GROUP SPECIFIED IN CRITERIA DEFINITION

Explanation: The CTBDBVCP Control-M/Analyzer utility failed due to error in the GROUP input statement.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the GROUP input statement and rerun the job.

CTB9A3E INVALID VARIABLE NAME SPECIFIED IN CRITERIA DEFINITION

Explanation: The CTBDBVCP Control-M/Analyzer utility failed due to an error in the VARIABLE input statement.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the VARIABLE input statement and rerun the job.

CTB9A4S ERROR OPENING DATABASE

Explanation: The CTBDBVCP Control-M/Analyzer utility was unable to open the Control-M/Analyzer database.

Possible causes are:

• One of the DD statements DIMOD, DIVAR, DOMOD, or DOVAR is missing.
• One of the data sets referenced by the DD statements listed above cannot be opened for sequential read or write.

The utility stops executing with a nonzero return code.

Corrective Action: Correct the problem and rerun the job.

CTB9A5S INSUFFICIENT STORAGE TO RUN CONTROL-M/ANALYZER UTILITY CTBDBVCP

Explanation: The CTBDBVCP Control-M/Analyzer utility requires more storage in order to copy the requested entries from the source Control-M/Analyzer database.

The utility stops executing with a condition code of 12.

Corrective Action: Increase the REGION size and rerun the job.

CTB9A6S ERROR ACCESSING TARGET DATABASE

Explanation: The CTBDBVCP Control-M/Analyzer copy utility was unable to access the target Control-M/Analyzer database.

The utility stops executing with a nonzero return code.

Corrective Action: Notify your INCONTROL administrator.

CTB9A7S ERROR ACCESSING SOURCE DATABASE

Explanation: The CTBDBVCP Control-M/Analyzer copy utility was unable to access the source Control-M/Analyzer database.

The utility stops executing with a nonzero return code.

Corrective Action: Notify your INCONTROL administrator.

CTB9A8I CONTROL-M/ANALYZER UTILITY CTBDBVCP STARTED

Explanation: This information message indicates the normal start of the CTBDBVCP Control-M/Analyzer copy utility.

Corrective Action: No action is required.

CTB9A9I COPY PERFORMED: numVariables VARIABLES, numGroups GROUPS WERE COPIED

Explanation: This information message indicates the normal termination of the CTBDBVCP Control-M/Analyzer copy utility. This message includes statistics.

Corrective Action: No action is required.

CTB9AAI VARIABLE ALREADY EXISTS IN TARGET DATABASE GROUP: grp VARIABLE: varName

Explanation: This information message indicates that the CTBDBVCP Control-M/Analyzer utility did not copy the indicated variable because it already exists in the target database.

The utility continues executing.

Corrective Action: To replace the variable, rerun the job with the REPLACE parameter set to YES.

CTB9ABI GROUP: grp ALREADY EXISTS IN TARGET DATABASE

Explanation: This information message indicates that the CTBDBVCP Control-M/Analyzer utility did not copy the grp group because it already exists in the target database.

The utility continues executing.

Corrective Action: To replace the group, rerun the job with the REPLACE parameter set to YES.

CTB9ACS OPEN OF SYSIN FAILED. CHECK DD CARD "DACMD"

Explanation: The CTBDBVCP Control-M/Analyzer utility could not open the input file (the SYSIN DD statement).

Possible causes are:

• The SYSIN DD statement or the DACMD DD statement is missing.
• The data set referenced by the SYSIN DD statement cannot be accessed for sequential read.

The utility stops executing with a condition code of 36.

Corrective Action: Fix the problem and rerun the job.

CTB9ADE INVALID NUMGEN/FROMGEN/TOGEN STATEMENT DEFINITION

Explanation: The CTBDBVCP Control-M/Analyzer utility could not process the NUMGEN, FROMGEN, or TOGEN input statement.

The utility stops executing with a condition code of 40.

Corrective Action: Correct the input statements and rerun the job.

CTB9AEE FROMGEN/TOGEN RANGE SIZE EXCEEDS NUMBER OF GENERATIONS REQUESTED FOR TARGET VARIABLE

Explanation: The CTBDBVCP Control-M/Analyzer utility was unable to process the input statements. The range of generations requested for copying to the newly created variable, exceeds the total number of generations requested for creation in the target database.

The utility stops executing with a condition code of 44.

Corrective Action: Increase the value specified in input statement NUMGEN= value, or decrease the range specified in statements FROMGEN= value and TOGEN= value. Rerun the job.

CTB9AFS INITIALIZATION ERROR. UNABLE TO CONTINUE PROCESSING

Explanation: The CTBDBVDL Control-M/Analyzer utility failed to initialize processing.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9B0S ERROR OPENING SYSPRINT

Explanation: The CTBDBVCP Control-M/Analyzer utility failed to open the print file referenced by the SYSPRINT DD statement.

Possible causes are:

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

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTB9B1E INVALID STATEMENT IN CRITERIA DEFINITION

Explanation: The CTBDBVDL Control-M/Analyzer utility failed due to one or more errors in the criteria definition input statement.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the input statement and rerun the job.

CTB9B2E INVALID GROUP SPECIFIED IN CRITERIA DEFINITION

Explanation: The CTBDBVDL Control-M/Analyzer utility failed due to error in the GROUP input statement.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the GROUP input statement and rerun the job.

CTB9B3E INVALID VARIABLE NAME SPECIFIED IN CRITERIA DEFINITION

Explanation: The CTBDBVDL Control-M/Analyzer utility failed due to an error in the VARIABLE input statement.

The utility stops executing with a condition code of 16.

Corrective Action: Correct the VARIABLE input statement and rerun the job.

CTB9B4S ERROR OPENING DATABASE

Explanation: The CTBDBVDL Control-M/Analyzer utility is unable to open the Control-M/Analyzer database.

Possible causes are:

• One of the DD statements DIMOD, DIVAR, DOMOD or DOVAR is missing.
• One of the data sets referenced by the DD statements listed above cannot be opened for sequential read or write.

The utility stops executing with a nonzero condition code.

Corrective Action: Correct the problem and rerun the job.

CTB9B5S ERROR OPENING SYSPRINT

Explanation: The CTBDBVDL Control-M/Analyzer utility failed to open the print file referenced by the SYSPRINT DD statement.

Possible causes are:

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

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTB9B6S I/O ERROR UPDATING DATABASE

Explanation: The CTBDBVDL Control-M/Analyzer utility failed to update the Control-M/Analyzer database.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9B7S I/O ERROR READING DATABASE RECORD

Explanation: The CTBDBVDL Control-M/Analyzer utility failed to read the Control-M/Analyzer database.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9B8I CONTROL-M/ANALYZER UTILITY CTBDBVDL STARTED

Explanation: This information message indicates the normal start of the CTBDBVDL Control-M/Analyzer compression utility.

Corrective Action: No action is required.

CTB9B9I UTILITY CTBDBVDL ENDED: num VARIABLES, num GROUPS WERE DELETED

Explanation: This information message indicates the normal termination of the CTBDBVDL Control-M/Analyzer compression utility. This message includes statistics.

Corrective Action: No action is required.

CTB9BAS ERROR DURING CTBGRP CALL. OPERATION: opn

Explanation: The CTBDBVDL Control-M/Analyzer utility failed to execute the indicated operation on the Control-M/Analyzer Group file.

In most cases, this utility stops executing with a nonzero condition code. However, if the error occurs while deleting a group, processing continues with the next group.

Corrective Action: Notify your INCONTROL administrator.

CTB9BBS ERROR DURING CTBDBV CALL. OPERATION: opn

Explanation: The CTBDBVDL Control-M/Analyzer utility failed to execute the indicated operation on the Control-M/Analyzer database.

The utility continues processing but it will end with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9BCE GROUP FILE CONTAINS NO RECORDS WHICH SATISFY THE SPECIFIED CRITERIA

Explanation: The CTBDBVDL or CTBDBVDL Control-M/Analyzer utility did not delete any records because no records matching the specification were found in the Control-M/Analyzer Group file.

The utility stops executing with a condition code of 04.

Corrective Action: Specify the correct group name or mask in the GROUP input statement and rerun the jobname.

CTB9BDE UNABLE TO DELETE THE REQUESTED GROUP. PLEASE SPECIFY ASTERISK (*) INSTEAD OF THE VARIABLE NAME

Explanation: The CTBDBVDL Control-M/Analyzer utility could not delete the requested record from the Control-M/Analyzer Group file because the specified group still contains variables.

The utility stops executing with a condition code of 20.

Corrective Action: Specify asterisk instead of the variable name in the VARIABLE input statement and rerun the job.

CTB9BEE NO CRITERIA SPECIFIED. UNABLE TO CONTINUE PROCESSING

Explanation: The CTBDBVDL Control-M/Analyzer utility is unable to continue processing because no input statements were specified.

The utility stops executing with a condition code of 28.

Corrective Action: Specify input statements and rerun the job.

CTB9BFS OPEN OF SYSIN FAILED. CHECK DD CARD "DACMD"

Explanation: The CTBDBVDL Control-M/Analyzer utility failed to open the input file referenced by the SYSIN DD statement.

This failure may be due to one of the following:

• The SYSIN DD statement or the DACMD DD statement is missing.
• The data set referenced by the SYSIN DD statement cannot be accessed for sequential read.

The utility stops executing with a condition code of 28.

Corrective Action: Correct the JCL and rerun the job.

CTB9C0I CONTROL-M/ANALYZER ACTIVE BALANCING FILE FORMATTING STARTED

Explanation: This information message indicates that the Control-M/Analyzer Active Balancing file is currently being formatted by the CTBFRM program, which is usually activated as part of the New Day procedure.

Corrective Action: No action is required.

CTB9C1I Control-M/ANALYZER ACTIVE BALANCING FILE FORMATTING ENDED

Explanation: This information message indicates that formatting of the Control-M/Analyzer Active Balancing file by the CTBFRM program ended successfully.

Corrective Action: No action is required.

CTB9C2I PREVIOUS FORMAT RUN FAILED. BACKUP COPY WILL BE USED

Explanation: This information message indicates that the Control-M/Analyzer New Day procedure is currently being rerun after abending which formatting the Active Balancing file.

The Active Balancing file is restored from the Active Balancing Backup file and processing continues normally.

Corrective Action: No action is required.

CTB9C3S OPEN OF CONTROL-M/ANALYZER ACTIVE BALANCING FILE FAILED. DDNAME "DAABF"

Explanation: Open of the Control-M/Analyzer Active Balancing file failed (the DAABF DD statement). This error message is issued by the CTBFRM program, which is usually activated as part of the New Day procedure, and is due to one of the following:

• The DAABF DD statement is missing.
• The data set referenced by the DAABF DD statement is not the Control-M/Analyzer Active Balancing file.

Program execution stops with a nonzero condition code.

Corrective Action: Correct the New Day procedure JCL and rerun the procedure.

CTB9C4S INTERNAL ERROR WHILE PROCESSING ACTIVE BALANCING FILE. FILE NOT FORMATTED

Explanation: Processing of the Control-M/Analyzer Active Balancing file failed. This error message is issued by the CTBFRM program, which is usually activated as part of the New Day procedure.

Program execution stops with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9C5S INTERNAL ERROR FROM THE CTBDBF ROUTINE. RC= rc

Explanation: Processing of the Control-M/Analyzer Active Balancing Backup file failed. This error message is issued by the CTBFRM program, which is usually activated as part of the New Day procedure. It is caused by an error during initialization of the Active Balancing file.

Program execution stops with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9C6S INTERNAL ERROR DURING INITIALIZATION. ACTIVE BALANCING FILE NOT FORMATTED

Explanation: Processing of the Control-M/Analyzer Active Balancing Backup file failed. This error message is issued by the CTBFRM program, which is usually activated as part of the New Day procedure. It is caused by an error during reading of the Control-M/Analyzer parameters.

One of the following may occur, depending on the situation:

• Program execution stops with a condition code of 16 indicating failure to load the CTBINFO routine.
• Program execution stops with a condition code of 20 indicating failure to load the CTBINI routine.
• Program execution stops with some other nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9C7S INSUFFICIENT MEMORY TO FORMAT THE CONTROL-M/ANALYZER ACTIVE BALANCING FILE

Explanation: Insufficient memory is available for the CTBFRM program to format the Control-M/Analyzer Active Balancing file. Clarification program CTBFRM is usually activated as part of the New Day procedure.

The utility stops executing with a condition code of 12.

Corrective Action: Increase the REGION size and rerun the New Day procedure.

CTB9C8S READING OF THE ACTIVE BALANCING BACKUP FILE FAILED

Explanation: An error occurred while reading the Control-M/Analyzer Active Balancing Backup file by the CTBFRM program, which is usually activated as part of the New Day procedure.

The utility stops executing with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9C9S INVALID JOB ID IN ACTIVE BALANCING FILE RECORD: BLOCK= block RECORD= record

Explanation: The CTBFRM program encountered an invalid job ID in a record in the Control-M/Analyzer Active Balancing file. The CTBFRM program is usually activated as part of the New Day procedure.

The record that contains the error is deleted. The utility continues executing with the next record.

Corrective Action: Notify your INCONTROL administrator.

CTB9CAS INVALID ODATE IN ACTIVE BALANCING FILE RECORD: BLOCK= blk RECORD= record

Explanation: The CTBFRM program encountered an invalid ODATE in a record in the Control-M/Analyzer Active Balancing file. The CTBFRM program is usually activated as part of the New Day procedure.

The record that contains the error is deleted. The utility continues executing with the next record.

Corrective Action: Notify your INCONTROL administrator.

CTB9CBS CONTROL-M/ANALYZER DATE CONTROL RECORD IS EMPTY

Explanation: The CTBFRM program encountered an empty Date Control Record. The CTBFRM program is usually activated as part of the New Day procedure.

The problem may be due to one of the following:

• The record referenced by the DACHK DD statement is not the Control-M/Analyzer Date Control Record.
• The contents of the Date Control Record have been manually modified incorrectly.

The utility stops executing with a condition code of 28.

Corrective Action: Depending on the cause of the problem, do one of the following:

• Correct the JCL for the New Day procedure and rerun the procedure.
• Correct the Date Control Record and rerun the New Day procedure.

CTB9CCS OPEN OF CONTROL-M/ANALYZER DATE CONTROL RECORD FAILED. DDNAME "DACHK"

Explanation: The file containing the Control-M/Analyzer Date Control Record could not be opened. This message is issued by the CTBFRM program, which is usually activated as part of the New Day procedure.

The problem may be due to one of the following:

• The record referenced by the DACHK DD statement is not the Control-M/Analyzer Date Control Record.
• the DACHK DD statement is missing.
• An internal error occurred during opening of the file referenced by the DACHK DD statement.

The utility stops executing with a condition code of 32.

Corrective Action: Correct the JCL for the New Day procedure and rerun the procedure.

CTB9CDS INVALID LAST FORMAT DATE IN THE DATE CONTROL-RECORD

Explanation: The last date in the Control-M/Analyzer Date Control Record has an invalid format. The valid format is ddmmyy. This message is issued by the CTBFRM program which is usually activated as part of the New Day procedure.

The problem may be due to one of the following:

• The record referenced by the DACHK DD statement is not the Control-M/Analyzer Date Control Record.
• The contents of the Date Control Record have been manually modified incorrectly.

The utility stops executing with a condition code of 36.

Corrective Action: Depending on the cause of the problem, do one of the following:

• Correct the JCL for the New Day procedure and rerun the procedure.
• Correct the format of the Date Control Record and rerun the New Day procedure.

CTB9CES INVALID ORIGINAL SCHEDULING DATE IN THE DATE CONTROL RECORD

Explanation: The original scheduling date in the Control-M/Analyzer Date Control Record has an invalid format. The valid format is ddmmyy. This message is issued by the CTBFRM program, which is usually activated as part of the New Day procedure.

The problem may be due to one of the following:

• The record referenced by the DACHK DD statement is not the Control-M/Analyzer Date Control Record.
• The contents of the Date Control Record have been manually modified incorrectly.

The utility stops executing with a condition code of 40.

Corrective Action: Depending on the cause of the problem, do one of the following:

• Correct the JCL for the New Day procedure and rerun the procedure.
• Correct the format of the Date Control Record and rerun the New Day procedure.

CTB9CFE FORMAT PROGRAM CTBFRM WAS ALREADY RUN TODAY

Explanation: An attempt was made to run the New Day procedure (which executes the CTBFRM format program) twice in the same day. After the CTBFRM program executes successfully, it should not normally be re-executed the same day.

The CTBFRM program stops executing with a condition code of 44. The Active Balancing file is not reformatted. The New Day procedure continues to execute other programs.

Corrective Action: Check the reason that the New Day procedure is being run twice.

CTB9D0S LAST FORMAT DATE GREATER THAN ORIGINAL SCHEDULING DATE IN THECONTROL-M/ANALYZER DATE CONTROL RECORD

Explanation: The last format date is greater then the original scheduling date in the Control-M/Analyzer Date Control Record. This message is produced by the New Day procedure. For more details, refer to the INCONTROL for z/OS Administrator Guide.

The utility stops executing with a condition code of 48.

Corrective Action: Correct the Control-M/Analyzer Date Control Record and run the New Day procedure again.

CTB9D1S OPEN OF IOA LOG FILE FAILED

Explanation: Open of the IOA Log File failed. The message is produced by the New Day procedure.

The failure may be due to one of the following:

• The DALOG DD statement is missing.
• The file referenced by the DALOG DD statement is not the IOA Log File.
• The file referenced by the DALOG DD statement is the IOA Log File, but from a different version or of a different IOA environment.

The utility stops executing with a condition code of 52.

Corrective Action: Correct the JCL and run the New Day procedure again.

CTB9D2S ENQ ON THE ACTIVE BALANCING FILE FAILED

Explanation: The CTBFRM program, which is usually activated as part of the New Day procedure, could not get exclusive control of the Control-M/Analyzer Active Balancing file, because a Control-M/Analyzer job or mission was executing with exclusive control at the same time. Exclusive control is required for file formatting.

The utility stops executing with a condition code of 56.

Corrective Action: Rerun the New Day procedure when the Active Balancing file is free for exclusive control.

CTB9D3S INVALID RC FROM CTBINFO ROUTINE: RC= rc, JOBNAME= jobName

Explanation: The New Day procedure could not detect the status of the indicated job in the Control-M/Analyzer Active Balancing file. The job is not deleted because it may still be executing.

The job is not deleted. The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB9D4S OPEN OF CONTROL-M/ANALYZER ACTIVE BALANCING BACKUP FILE FAILED. DDNAME "DABKP"

Explanation: Open of Control-M/Analyzer Active Balancing Backup file failed (the DABKP DD statement). This error message is issued by the CTBFRM program, which is usually activated as part of the New Day procedure.

Probable causes:

• The DABKP DD statement is missing.
• The data set referenced by the DABKP DD statement is not the Control-M/Analyzer Active Balancing file.

Program execution stops with a nonzero condition code.

Corrective Action: Correct the JCL for the New Day procedure and rerun the procedure.

CTB9D5S INTERNAL ERROR WHILE PROCESSING ACTIVE BALANCING BACKUP FILE. FORMATTING FAILED

Explanation: Processing of the Control-M/Analyzer Active Balancing Backup file failed. This message is issued by the CTBFRM program which is usually activated as part of the New Day procedure.

Program execution stops with a nonzero condition code.

Corrective Action: Notify your INCONTROL administrator.

CTB9D6S ERROR OPENING SYSPRINT

Explanation: An error occurred while opening the print file referenced by the SYSPRINT DD statement. This message is issued by the CTBFRM program which is usually activated as part of the New Day procedure.

The error may be due to one of the following:

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

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTB9D7E THE SIZE OR LRECL PARAMETER OF THE ABFBKP FILE DIFFERS FROM THE ABF FILE

Explanation: The CTBFRM Control-M/Analyzer utility detected that the Control-M/Analyzer file for the ABF backup (ABFBKP) was either not large enough for all the records, or that it did not have the same record length as the ABF file.

The CTBFRM utility stops executing with a condition code of 64.

Corrective Action: According to the source of the problem, either reallocate the Control-M/Analyzer ABFBKP file with the LRECL parameter the same as that of the ABF file, or increase the size of the ABFBKP file. Rerun the job.

CTB9E1I INFORMATION RECORD HAS BEEN DELETED record

Explanation: This information message indicates that in correcting the Job Activity Data file, the CTBJAFIG Control-M/Analyzer utility deleted the record Information record from the file because the record was in error. This message is followed by other messages that display additional information about the deleted record.

Corrective Action: No action is required.

CTB9E2I PRIMARY REPORT RECORD HAS BEEN DELETED record

Explanation: This information message indicates that in correcting the Report Data file, the CTBJAFIG Control-M/Analyzer utility deleted the record Primary Report record from the file because the record was in error. This message is followed by other messages that display additional information about the deleted record.

Corrective Action: No action is required.

CTB9E3I SECONDARY REPORT RECORD HAS BEEN DELETED record

Explanation: This information message indicates that in correcting the Report Data file, the CTBJAFIG Control-M/Analyzer utility deleted the record Secondary Report record because the record was in error.

This message is followed by other messages that display additional information about the deleted record.

Corrective Action: No action is required.

CTB9E4I INVOCATION RECORD HAS BEEN CORRECTED record

Explanation: This information message indicates that the CTBJAFIG Control-M/Analyzer utility corrected the record Invocation record in the Rule Activity File because the record had been in error.

This message is followed by other messages that display additional information about the deleted record.

Corrective Action: No action is required.

CTB9E5I REPORT RECORD HAS BEEN DELETED record

Explanation: This information message indicates that in correcting the report file, the CTBJAFIG Control-M/Analyzer utility deleted the record report record from the file because the record was in error.

This message is followed by other messages that display additional information about the deleted record.

Corrective Action: No action is required.

CTB9E6S ERROR DURING THE CORRECTION PROCESS BY ROUTINE CTBCKP

Explanation: An error occurred while the CTBJAFIG Control-M/Analyzer utility was trying to correct a record in the Job Activity Data file.

This message is followed by the CTB9E8S message, which displays the failed operation, and by the CTB9E9I message, which displays the error code.

The CTBJAFIG utility continues executing with the next record.

Corrective Action: Notify your INCONTROL administrator.

CTB9E7S ERROR DURING THE CORRECTION PROCESS BY ROUTINE CTBREP

Explanation: An error occurred while the CTBJAFIG Control-M/Analyzer utility was trying to correct a record in the Report Data file.

This message is followed by the CTB9E8S message, which displays the failed operation, and by the CTB9E9I message, which displays the error code.

The CTBJAFIG utility continues executing with the next record.

Corrective Action: Notify your INCONTROL administrator.

CTB9E8S OPERATION IS: opn

Explanation: While the CTBJAFIG Control-M/Analyzer utility was correcting a record, the operation indicated in the message failed.

This message follows the CTB9E7S or CTB9E6S message.

Corrective Action: Notify your INCONTROL administrator.

CTB9E9I RETURN CODE IS: rc

Explanation: This information message displays the return code for the failed operation indicated in the CTB9E8S message. This message follows the CTB9E8S message.

Corrective Action: No action is required.

CTB9EAS INVOCATION RECORD IS NOT IN SEQUENCE

Explanation: While reading the Job Activity Data file, the CTBJAFIG Control-M/Analyzer utility encountered an Invocation record which does not belong to any Job record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB9EBS INFORMATION RECORD IS NOT IN SEQUENCE

Explanation: While reading the Job Activity Data file, the CTBJAFIG Control-M/Analyzer utility encountered an Information record which does not belong to any Invocation record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB9ECS SECONDARY REPORT RECORD IS NOT IN SEQUENCE

Explanation: While reading the Report Data file, the CTBJAFIG Control-M/Analyzer utility encountered a Secondary Report record which does not belong to any Primary Report record.

The utility continues executing.

Corrective Action: Notify your INCONTROL administrator.

CTB9EDI APPLICATION GROUP grpname

Explanation: This information message indicates the group name from the record deleted by the CTBJAFIG Control-M/Analyzer utility.

Corrective Action: No action is required.

CTB9EEI JOBNAME jobName

Explanation: This information message indicates the job name from the record deleted by the CTBJAFIG Control-M/Analyzer utility.

Corrective Action: No action is required.

CTB9EFI DATE date

Explanation: This information message indicates the date from the record deleted by the CTBJAFIG Control-M/Analyzer utility.

Corrective Action: No action is required.

CTB9F0I TIME time

Explanation: This information message indicates the time from the record deleted by the CTBJAFIG Control-M/Analyzer utility.

Corrective Action: No action is required.

CTB9F1I JOBID jobId

Explanation: This information message indicates the job id from the record deleted by the CTBJAFIG Control-M/Analyzer utility.

Corrective Action: No action is required.