Messages CTB100 through CTB1xx

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

CTB101E LINE lineNum: KEYWORD " keywd" IS REQUIRED

Explanation: During rule compilation or runtime an expected key word was missing in the specified line.

Relevant text appears in an accompanying message.

The variables in this message are:

• lineNum - has one of the following meanings:
• If the error occurred during rule compilation, lineNum identifies the line from which keywd was missing.
• If the error occurred during runtime, lineNum identifies the line in the DD name file referenced by the MSUBSTMASK function from which keywd was missing.
• keywd - the missing key word

The system action depends on the point at which the error occurs, as follows:

• If the error occurs during rule compilation, the compiler continues processing at the next block, but issues syntax error messages when it ends.
• If the error occurs during runtime execution, Control-M/Analyzer stops executing and issues an error message.

Corrective Action: Correct all errors in the rule, or in the DD name referenced by MSUBSTMASK, and recompile.

CTB102E LINE lin: KEYWORD " keywd" MUST APPEAR ONCE AND ONLY ONCE IN THIS STATEMENT

Explanation: During rule compilation the keyword keywd was expected to appear once in the line lin. The keyword either was not found or was found more than once in the statement. Relevant text appears in an accompanying message.

The compiler continues processing the next block but terminates with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB103E LINE lin: KEYWORD " keywd" CAN APPEAR ONLY ONCE IN THIS STATEMENT

Explanation: A syntax error was detected during rule compilation. Relevant text appears in an accompanying message. The keyword keywd was expected to appear once in the lin line, but was found more than once in the statement.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct any errors in the rule member and recompile the rule.

CTB104E NUMERIC VALUE EXPECTED

Explanation: A syntax error was detected during rule compilation. Relevant text appears in an accompanying message. The parameter value should be, but is not, numeric.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB105E EXPECTED PARAMETER MISSING IN LINE lin

Explanation: During rule compilation, a required parameter value was missing from the lin line. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB106E PARAMETER STARTING ON LINE lin IS TOO LONG

Explanation: During rule compilation, the length of a parameter that starts on the lin line exceeded the maximum length for this parameter. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB107E KEYWORD " keyName1" CANNOT FOLLOW " keyName2"

Explanation: During rule compilation, keyName1 incorrectly follows keyName2. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB108E KEYWORD EXPECTED IN LINE: lin BEFORE " string"

Explanation: During rule compilation, a keyword was expected in the lin line before the string string, but the keyword was missing from the lin line. The probable cause is misspelling of a keyword. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB109I COMPILATION STARTED

Explanation: This information message indicates that the compiler has started compiling a rule.

Corrective Action: No action is required.

CTB110I COMPILATION COMPLETED SUCCESSFULLY

Explanation: This information message indicates that a rule was compiled without any errors. Warnings may have been issued.

Corrective Action: No action is required.

CTB111I HIGHEST ERROR CODE WAS code

Explanation: This information message indicates the highest error code issued during a rule compilation. The error code is 0 if the rule compiled without warnings. The error code is nonzero if warnings were issued or errors were detected.

Corrective Action: No action is required.

CTB112E STATEMENT line: IS INVALID IN THIS CONTEXT

Explanation: During rule compilation, the statement line was incorrect. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB113I SKIPPING TO NEXT BLOCK

Explanation: This information message indicates that the compiler found a syntax error in the current block and is skipping to the next block before continuing with syntax checking.

Corrective Action: No action is required.

CTB114E MEMORY ALLOCATION FAILED

Explanation: Control-M/Analyzer could not allocate sufficient memory to compile a rule.

Compilation is terminated immediately.

Corrective Action: Increase the REGION size of the job or the TSO session. If this does not help, ask your INCONTROL Administrator to contact BMC Customer Support.

CTB115E DUPLICATE BLOCK NAME blk AT LINE lin

Explanation: During rule compilation, a duplicate block name was found at the line indicated in the message. Block names within a rule must be unique. Relevant text appears in an accompanying message.

The variables in this message are:

• blk - the duplicate block name
• lin - the line in which the duplicate block name was found

The compiler continues processing the next block, but will terminate with syntax errors.

Corrective Action: Do the following:

1. Rename one of the blocks.
2. Correct any other errors in the rule member,
3. Recompile the rule.

CTB116E DUPLICATE LABEL label BEFORE LINE lin

Explanation: During rule compilation, a duplicate label name was found in the line indicated in the message.

Label names within a rule must be unique. Relevant text appears in an accompanying message.

The variables in this message are:

• label - the duplicate label name
• lin - the line in which the duplicate label name was found

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Do the following:

1. Rename one of the labels.
2. Correct any other errors in the rule member.
3. Recompile the rule.

CTB117E UNRESOLVED REFERENCE FOR label IN OR BEFORE LINE lin

Explanation: During rule compilation, a DO GOTO statement references an undefined label or a DO BLOCK statement references a block that does not exist. Relevant text appears in an accompanying message.

The variables in this message are:

• label - the problematic label or block
• lin - the line in or before which either the problematic label was found, or in or before which the problematic block was found not to exist

The compiler terminates with syntax errors.

Corrective Action: Correct errors in the rule member. Recompile the rule.

CTB118E THE MAXIMUM OF num "DO GOTO" STATEMENTS PER RULE HAS BEEN EXCEEDED

Explanation: During rule compilation, the maximum number of DO GOTO statements for a rule was exceeded. Relevant text appears in an accompanying message.

In this message, num is the maximum number of DO GO statements for a rule.

The compiler terminates with syntax errors.

Corrective Action: Do the following:

1. Either reduce the number of DO GOTO statements in the rule, or split the rule into multiple rules.
2. Correct any other errors in the rule member.
3. Recompile the rule.

CTB119E THE MAXIMUM OF num "DO BLOCK" STATEMENTS PER RULE HAS BEEN EXCEEDED

Explanation: During rule compilation, the indicated maximum number of DO BLOCK statements for a rule was exceeded. Relevant text appears in an accompanying message.

In this message, num is the maximum number of DO BLOCK statements for a rule.

The compiler terminates with syntax errors.

Corrective Action: Do the following:

1. Either reduce number of DO BLOCK statements in the rule, or split the rule into multiple rules.
2. Correct any other errors in the rule member.
3. Recompile the rule.

CTB120E LABEL label MUST OCCUR WITHIN THE SAME BLOCK AS THE REFERENCE TO IT

Explanation: During rule compilation, a DO GOTO statement referenced a label outside the block in which it occurs. A DO GOTO statement can only reference labels within the same block. Relevant text appears in an accompanying message.

In this message, label identifies the problematic label.

The compiler continues processing the next block, but terminates with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB121E MAXIMUM LENGTH OF THE PARAMETER OF KEYWORD keyName IS num

Explanation: During rule compilation, the value specified for the keyName keyword exceeded the indicated maximum length. Relevant text appears in an accompanying message.

The compiler continues processing the next block, but terminates with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB122W WARNING: RECURSIVE CALL TO BLOCK: " blk" IN OR BEFORE LINE lin

Explanation: The rule being compiled has a block that calls itself. This is a warning, that there might be a problem.

The variables in this message are:

• blk - the problematic block
• lin - the line in or before which block appears

Corrective Action: Check the rule to verify that it does what you intend it to do.

CTB123E UNEXPECTED END OF SOURCE AFTER LINE lin

Explanation: During rule compilation, there was an unfinished command at the end of the source member, or the source did not contain any blocks. Relevant text appears in an accompanying message.

The compiler terminates with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB124E SYNTAX ERROR ENCOUNTERED IN LINE lin

Explanation: A syntax error occurred during rule compilation or runtime.

In this message, the variable lin has two possible meanings:

• During rule compilation, lin identifies the line in the rule in which the error occurs.
• During runtime, lin identifies the line in the DD name referenced by the MSUBSTMASK function in which the error occurs.

The system action varies according to the stage at which the error occurs, as follows:

• If the error occurs during rule compilation, the compiler continues compiling at the next block, but issues syntax errors when it ends.
• If the error occurs during runtime execution, Control-M/Analyzer stops executing and issues an error.

Corrective Action: Correct all errors in the rule, or in the DD name referenced by MSUBSTMASK, and recompile.

CTB125E NO BLANK CHARACTERS ALLOWED IN PARAMETER: " parm"

Explanation: During rule compilation, the parm parameter contained embedded blanks.

Embedded blanks are not permitted in this parameter. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB126E FIRST CHARACTER MUST BE ALPHABETIC. SYNTAX ERROR IN LINE lin

Explanation: During rule compilation, the first character of the parameter in the lin line should be, but was not, alphabetic. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB127E CHARACTERS MUST BE ALPHANUMERIC. SYNTAX ERROR IN LINE lin

Explanation: During rule compilation, a non-alphanumeric character was found in the parameter in the lin line. The parameter must be alphanumeric. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB128I SRC: " lin"

Explanation: This information message prints rule source lines that are rejected by the compiler. This message accompanies compilation error messages.

Corrective Action: No action is required.

CTB129I SRC: " lin"

Explanation: This information message prints rule source lines that are rejected by the final syntax checker.

Corrective Action: No action is required.

CTB129W EXIT exitName WAS NOT LOADED

Explanation: Control-M failed to load the exitName user exit. Common reasons for failure are:

• The IOA Load library is in the Linklist, and someone has updated the library without performing a refresh for the LLA.
• The last assembly or linkage of the exit failed.
• There is insufficient memory to load the new exit.

Control-M will continue to run, bypassing the exit.

Corrective Action: Check the computer Log for the cause of the failure.

CTB130I INTERNAL ERROR. SHOW THE FOLLOWING INFORMATION TO YOUR LOCAL IOA REPRESENTATIVE.

Explanation: This message indicates that a Control-M/Analyzer internal error occurred.

The rule is not saved.

Corrective Action: Do the following:

1. Perform a screen print of the information shown.
2. Ask your IOA administrator to report the information to BMC Customer Support.
3. Press PF03/PF15 ( END ) to return to the editing screen.
4. Change the rule so that it can be saved.

CTB131I ADDR: info

Explanation: This information message accompanies the CTB130I message.

Corrective Action: Ask your INCONTROL administrator to report the information in this message to BMC Customer Support.

CTB132E ERR: asterisks

Explanation: This information message accompanies the message containing the text of the line in error. This message places an asterisk directly under the error in the text line.

Corrective Action: No action is required.

CTB133E NUMERIC VALUE MUST BE LESS THAN 256

Explanation: During rule compilation, the numeric value indicated in the accompanying message must be less than 256. Relevant text appears in an accompanying message.

The compiler continues processing the next block, but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB134E NUMERIC VALUE MUST BE LESS THAN 4000

Explanation: During rule compilation, the numeric value indicated in the accompanying message should be, but is not, less than 4000. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB135E VALID VALUES FOR URGENCY ARE R, U AND V

Explanation: During rule compilation, the value of the URGENCY parameter in the SHOUT statement was found to be invalid.

Valid values for the URGENCY parameter are:

• R - Regular
• U - Urgent
• V - Very Urgent

Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB136E ABSOLUTE COLUMN NUMBER MUST BE NONZERO

Explanation: During rule compilation, the value zero was specified for a column number. Column number values are absolute and must be greater than zero. Relevant text appears in an accompanying message.

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB137E LINE NUMBER MUST BE RELATIVE

Explanation: During rule compilation, a non-relative line number was specified. Relevant text appears in an accompanying message.

A line number must be relative, and must start with plus (+) or minus (-).

The compiler continues processing the next block but will terminate with syntax errors.

Corrective Action: Correct the errors in the rule member and recompile the rule.

CTB138E SUBSYSTEM ID MUST BE ALPHANUMERIC, @, $, OR #. FIRST CHARACTER MUST NOT BE A DIGIT

Explanation: The subsystem ID contains invalid characters.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Correct the specification of the subsystem ID.

CTB139E VALID VALUES FOR THIS FIELD ARE Y AND N

Explanation: The value of the field in error was neither Y nor N. This field must contain Y for choosing a certain feature or N (or blank) for not choosing it.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Specify Y or N in the field, or leave it blank.

CTB13AE NUMERIC VALUE MUST NOT EXCEED 100

Explanation: The specified value exceeded 100. The value specified in the field in error cannot exceed 100.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Specify a value of 100 or less.

CTB13BE NUMERIC VALUE MUST BE POSITIVE

Explanation: The specified value was zero. The value specified in the field in error cannot be zero.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Specify a positive number for the value.

CTB13CE VALID VALUES FOR DATASTAMP ARE 1, 2, AND BLANK

Explanation: The DATASTAMP parameter contained an invalid value. Valid values for the DATASTAMP parameter are blank, 1 and 2, depending on whether or not a data stamp should be calculated and on the calculation technique that should be used.

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Assign a valid value to the DATASTAMP parameter.

CTB13DE VSAM FILE TYPE MAY BE KSDS, RRDS OR ESDS

Explanation: The VSAM file type specified in statement ON VSAM was invalid.

The TYPE parameter in an ON VSAM statement specifies the VSAM file type. Valid values are:

• KSDS
• RRDS
• ESDS

The Control-M/Analyzer runtime environment terminates with an error.

Corrective Action: Correct the file type specification.