This group includes messages for the Control-M/Analyzer product.
Explanation: A required field has not been filled in. The cursor points to the required field.
Corrective Action: Fill in the required field.
Explanation: The value in the field is not the required length. The field must contain num digits.
Corrective Action: Correct the field value.
Explanation: Line/column range data has not been specified.
Corrective Action: Fill in the line/column range.
Explanation: The user attempted to overwrite the ON DATA statement with another ON statement. After an ON DATA statement has been specified, it cannot be overwritten by another ON statement. It can be replaced by an empty ON statement. Then a new ON statement can be defined in its place.
For more information, see the ON DATA statement in the Control-M/Analyzer User Guide.
Corrective Action: Delete the keyword DATA from the ON DATA statement and press Enter. Then define the desired ON statement.
Explanation: The user attempted to overwrite an existing ON statement with an ON DATA statement. After an ON statement is specified, it cannot be overwritten by an ON DATA statement. The ON statement can, be replaced by an empty ON statement. Then an ON DATA statement can be defined in its place.
Corrective Action: Delete the keyword from the ON statement and press Enter. Then define the ON DATA statement.
Explanation: The field contains nonnumeric data. The field must be blank or contain numeric data. If numeric values are used, then no trailing and leading blanks are not allowed.
Corrective Action: Correct the value in the field.
Explanation: The first column in the field contains a numeric value. It should be alphabetic.
Corrective Action: Correct the value in the field.
Explanation: The field contains characters not permitted in a name specification, for example, - s, +, !.
Corrective Action: orrect the name.
Explanation: This information message indicates that the user attempted to open an empty comment line outside of an ON block. A comment line can only be placed within an ON block.
Corrective Action: Open the comment line within an ON block.
Explanation: The value specified at the cursor position must be either + or - . The cursor points to the position requiring the + or - value.
Corrective Action: Correct the value at the cursor position.
Explanation: The value in the field referenced by the cursor has an invalid format.
Corrective Action: Refer to the Control-M/Analyzer User Guide to determine the correct format for the field. Correct the value in the field.
Explanation: The field does not contain a valid value.
Valid values are:
Corrective Action: Correct the value in the field.
Explanation: The field pointed to by the cursor does not contain a valid value.
Corrective Action: Refer to the Control-M/Analyzer User Guide to determine valid values for the field. Correct the value.
Explanation: The maximum number of continuation lines for the line type has been exceeded.
The cursor points to the first extra line.
Corrective Action: Delete the extra line.
Explanation: A DO EXTRACT action was specified within an ON DATA block. This action is not permitted in an ON DATA block.
Corrective Action: Remove the DO EXTRACT statement from the ON DATA block.
Explanation: A DO GOTO action was specified outside an ON DATA block. This action is only permitted within an ON DATA block.
Corrective Action: Remove the invalid DO GOTO statement.
Explanation: The = character is missing from the DO SET statement. The = character is required to separate the variable value from the variable name.
Corrective Action: Correct the DO SET statement.
Explanation: Statement DO SET contains blanks immediately following the = character. The variable value, which follows the = character, cannot contain leading blanks. Trailing blanks are permitted in the variable value.
Corrective Action: Remove the leading blanks in the variable value.
Explanation: The abbreviation specified in the DO/ON line is ambiguous. There is more than one statement type starting with this abbreviation.
Corrective Action: Specify a longer, unique statement name.
Explanation: The value specified is not in a valid format. The value must consist of a 3-digit number preceded by either a + or - character.
Corrective Action: Specify the value using the correct format.
Explanation: An invalid value is specified in the OPT field in the DO SYSOUT statement. The OPT field in the DO SYSOUT statement can accept only the values listed in the message.
Corrective Action: Correct the contents of the OPT field accordingly.
Explanation: An invalid value is specified in the FRM field in the DO SYSOUT statement. The FRM field in the DO SYSOUT statement can accept only the values listed in the message.
Corrective Action: Correct the contents of the FRM field accordingly.
Explanation: A value is specified in the PRM field in the DO SYSOUT. The PRM field in the DO SYSOUT statement must remain empty when the user specifies either R or D in the OPT field.
Corrective Action: Delete the value in the PRM field.
Explanation: The parameter or variable contains invalid characters.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Correct the subsystem parameter or variable specification.
Explanation: The LABEL field on which the cursor is positioned contains a name that already appears in the rule definition.
Corrective Action: Change the label name.
Explanation: The value specified for the field on which the cursor is positioned is invalid.
Corrective Action: Specify either R, L, or leave the field empty.
Explanation: Y or N is not specified in the field on which the cursor is positioned.
Corrective Action: Specify either Y or N.
Explanation: The length specified in the LEN field is invalid.
The length can be only in the range from 1 to 133.
Corrective Action: Specify a value within the range from 1 to 133.
Explanation: The value specified in the PREC field exceeds the value specified in LEN field. The precision cannot be greater than the length.
Corrective Action: Correct the value of the PREC field.
Explanation: No value is specified in the OUTDD or the FORMAT VAR fields. At least one of the OUTDD or the FORMAT VAR fields appearing on the screen must have a value.
Corrective Action: Specify a value in either the OUTDD or the FORMAT VAR fields.
Explanation: value specified for the field on which the cursor is positioned is invalid.
Corrective Action: Specify 1 or 2, or leave the field empty.
Explanation: The value specified for the FILE TYPE field is invalid.
Corrective Action: Specify KSDS, RRDS, or ESDS.
Explanation: The ARG field of a DO RULE, DO BLOCK or DO CALLUSER statement contains one or more blanks in a variable name. Trailing blanks are not allowed in the ARG field of a DO RULE, BLOCK, or CALLUSER statement, and blanks are not allowed in a variable name.
Corrective Action: Correct the invalid variable name.
Explanation: The variable name begins with a non-alphabetical symbol.
Corrective Action: Correct the invalid variable name.
Explanation: The ARG field in a DO RULE, DO BLOCK or DO CALLUSER contains more than 50 arguments. A maximum of 50 arguments can be specified.
Corrective Action: Decrease the number of arguments specified.
Explanation: An attempt has been made to use the D option with other options. Option D cannot be mixed with other options.
Corrective Action: Perform the D option, and then perform other options.
Explanation: User tried to specify more than one Option C or Option I. Multiple occurrences of Option C or Option I are not permitted, nor can these options be specified with other options.
Corrective Action: Perform Option C or Option I alone.
Explanation: The Control-M/Analyzer Online Facility is unable to initialize the C language environment. The C language environment must be initialized when entering the Rule Definition screen.
Corrective Action: Ask your INCONTROL administrator to call BMC Customer Support.
Explanation: The rule could not be compiled because it contains invalid data. The rule was prepared by means of the ISPF editor. Its contents do not conform to Control-M/Analyzer standards.
Compilation error messages are displayed.
Corrective Action: Use the ISPF editor to correct the rule.
Explanation: Errors were detected in the rule definition during the final syntax check. Although the rule was prepared using the Control-M/Analyzer Online Facility, due to an internal error its contents do not conform to Control-M/Analyzer standards.
Error messages from the final syntax check are displayed.
Corrective Action: Use the Control-M/Analyzer Online Facility to correct the rule.
Explanation: The selected member is not a valid Control-M/Analyzer rule member.
The message could result from one of the following:
Corrective Action: Enter a valid Control-M/Analyzer rule. If the specified rule has been incorrectly modified, try to restore it to its original state or correct it.
Explanation: The rule contains invalid data.
The rule contains invalid data. Possible causes are:
Corrective Action: If the contents of the rule have been modified, try to restore the rule to its original state. If you cannot or if this is not the problem, ask your INCONTROL administrator to call BMC Customer Support.
Explanation: Insufficient storage to load the rule member.
Corrective Action: Do one the following:
Explanation: Insufficient storage to display the rule on the ZOOM screen.
Corrective Action: Do one of the following:
Explanation: There is insufficient storage to process the changes to rule parameters in the Zoom screen.
All changes to the rule are ignored. The Rule List screen is displayed.
Corrective Action: Do one, or both, of the following:
Explanation: Another Control-M/Analyzer user is currently working on the rule. Two users cannot work on the same rule simultaneously. The other user may be using the rule either by means of the Control-M/Analyzer Online Facility or by means of the ISPF editor.
Corrective Action: Try again later.
Explanation: The library is empty. Control-M/Analyzer did not build the rule list as no rules were found in the library.
Corrective Action: Specify a new rule name.
Explanation: No value was specified in the RULE field. The RULE field is obligatory.
Corrective Action: Specify the name of the rule member in the RULE field.
Parent Topic |