|
|
|
|
|
This group includes messages for the Control-M/Analyzer product.
Explanation: This information message indicates that the Control-M/Analyzer Runtime Environment has been invoked in modeType mode, and is executing using the identified scope.
The Control-M/Analyzer Runtime Environment can be invoked in STANDALONE mode (as a job step or as a call from a user program), or from within the Control-M or Control-D monitors.
In this message, scope is the type of call used to invoke the environment. Valid values are:
For more information, see the SCOPE parameter in the Control-M/Analyzer User Guide.
Corrective Action: No action is required.
Explanation: This information message indicates that the Control-M/Analyzer Runtime Environment terminated normally.
Corrective Action: No action is required.
Explanation: An internal error occurred while executing the DO command identified in the message. Earlier messages indicate the reason for the error.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Ask your INCONTROL administrator to give the information contained in occurrences of the CTB200S message to BMC Customer Support.
Explanation: Statement DO EXTRACT specified a level (lvl1) which exceeds the highest existing level (lvl2).
The DO EXTRACT level must refer to a preceding WHEN statement in the current sub-block. The WHEN statements of the sub-block are numbered starting from 1. The error occurred because the LEVEL parameter specified a non existing WHEN statement. For more information, see the WHEN statement in the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: The line specified in statement DO EXTRACT must refer to a report line that exists in the current Control-M/Analyzer internal buffers, but it does not. Control-M/Analyzer currently has lines fromline to toline in memory.
Control-M/Analyzer keeps a number of pages from the currently processed report in memory. This is usually sufficient for backward and forward references of WHEN and DO EXTRACT statements.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Ask your INCONTROL administrator to increase the number of pages Control-M/Analyzer stores in memory by changing the RTEBUF parameter in the CTBPARM member.
Explanation: The number of characters to extract that was specified in a DO EXTRACT statement exceeded the maximum number of characters that may be extracted.
A DO EXTRACT statement extracts values that are subsequently stored in a variable. The maximum length that may be extracted is the maximum length of the variable value.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the DO EXTRACT statement and invoke Control-M/Analyzer again.
Explanation: The line specified in a WHEN statement must refer to a report line that exists in the current Control-M/Analyzer internal buffers, but does not. Control-M/Analyzer currently has lines fromline to toline in memory.
Control-M/Analyzer keeps a number of pages from the currently processed report in memory. This is usually sufficient for backward and forward references of WHEN and DO EXTRACT statements.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Ask your INCONTROL administrator to increase the number of pages Control-M/Analyzer stores in memory by changing the RTEBUF parameter in the CTBPARM member.
Explanation: The FROM COL value exceeded the TO COL value in a DO EXTRACT statement. The specified FROM COL value must be less than or equal to the TO COL value.
The variables in this message are:
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the DO EXTRACT statement and invoke Control-M/Analyzer again.
Explanation: This information message indicates that the Control-M/Analyzer Runtime Environment has been invoked using the modeType Group mode.
Corrective Action: No action is required.
Explanation: This information message indicates that the Control-M/Analyzer Runtime Environment has been invoked with the memName rule member (from the lib library).
Corrective Action: No action is required.
Explanation: This information message indicates that the Control-M/Analyzer Runtime Environment has been invoked in Define mode.
In Define mode, Control-M/Analyzer does not perform any balancing activity. All calls to Control-M/Analyzer routines are immediately returned with status END OK and a return code of 0.
For more information, see Define mode in the Control-M/Analyzer User Guide.
Corrective Action: No action is required.
Explanation: The Control-M/Analyzer Runtime Environment was invoked with a rule member that contains invalid syntax.
During execution, all invoked rules are checked (compiled) for valid syntax. Whenever invalid syntax is encountered, an error occurs.
The variables in this message are:
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the specified rule and invoke Control-M/Analyzer again.
Explanation: The Control-M/Analyzer Runtime Environment has insufficient memory to load a rule.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Increase the REGION size and invoke Control-M/Analyzer again. If the problem persists, notify your INCONTROL administrator.
Explanation: This information message accompanies other error messages. It identifies the DO command that was in process when the error specified in the other message occurred.
In this message, cmd is the DO command in process when the error occurred.
Corrective Action: No action is required.
Explanation: This information message is a normal termination message of the Control-M/Analyzer Runtime environment. This message accompanies other normal termination messages.
The variables in this message are:
Corrective Action: No action is required.
Explanation: A non-existing group was specified when the Control-M/Analyzer Runtime Environment was invoked.
The Control-M/Analyzer Runtime Environment must be invoked with an existing group name. Groups can be defined and viewed using the Control-M/Analyzer Online Facility.
For information on the methods that can be used to specify the group under which Control-M/Analyzer is to run, see the Control-M/Analyzer chapter of the INCONTROL for z/OS Administrator Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Specify an existing group and invoke Control-M/Analyzer again.
Explanation: No group name was specified when the Control-M/Analyzer Runtime Environment was invoked.
The Control-M/Analyzer Runtime Environment must be invoked with an existing group name. Groups can be defined and viewed using the Control-M/Analyzer Online Facility.
For information on the methods that can be used to specify the group under which Control-M/Analyzer is to run, see the Control-M/Analyzer chapter of the INCONTROL for z/OS Administrator Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Specify an existing group, and invoke Control-M/Analyzer again.
Explanation: The block identified in the message does not exist in the current rule. The rule contained a reference to a nonexisting block, such as the block specified as a parameter to the DATASTAMP function.
In this message, blk is the non-existing block specified in the rule.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the reference and invoke Control-M/Analyzer again.
Explanation: The column range specified in statement DO EXTRACT referred to columns beyond the record length of the input source.
The variables in this message are:
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Correct the column range or verify that the block refers to the correct input source.
Explanation: This warning message indicates that a WHEN statement was specified with a negative column number when searching for the string identified in the message.
WHEN statement column numbers can be relative to the location of previously found data in previous WHEN statements. The negative column number may be the result of such a reference.
The variables in this message are:
Control-M/Analyzer assumes a column number of 1 and continues execution.
Corrective Action: Make sure that this warning message is not the result of a rule definition error.
Explanation: The length of a WHEN statement search string exceeds the number of characters in the specified column range. Strings specified in the WHEN criteria are compared with the contents of the specified line and column range. The strings must not be longer than the specified column range.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Widen the column range or shorten the string which caused the problem.
Explanation: The FROM LINE value exceeded the TO LINE value in a WHEN statement.
When WHEN statement line numbers are relative to previously found data in previous WHEN statements, the calculated FROM LINE value might be greater than the calculated TO LINE value.
The variables in this message are:
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the reference and invoke Control-M/Analyzer again.
Explanation: The FROM COL value exceeded the TO COL value in a WHEN statement. When WHEN statement line numbers are relative to previously found data in previous WHEN statements, the calculated FROM COL value might be greater than the calculated TO COL value.
The variables in this message are:
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the reference and invoke Control-M/Analyzer again.
Explanation: The FROM LINE value exceeded the TO LINE value in a STOP statement. When STOP statement line numbers are relative to previously found data in previous STOP statements, the calculated FROM LINE value might be greater than the calculated TO LINE value.
The variables in this message are:
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the reference and invoke Control-M/Analyzer again.
Explanation: The FROM COL value exceeded the TO COL value in a STOP statement. When STOP statement line numbers are relative to previously found data in previous STOP statements, the calculated FROM COL value might be greater than the calculated TO COL value.
The variables in this message are:
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the reference and invoke Control-M/Analyzer again.
Explanation: The input data set does not contain lines that match the WHEN criteria.
Corrective Action: Verify that the WHEN criteria and the data source are correctly specified.
Explanation: The Control-M/Analyzer Runtime Environment referenced the database, but could not find a variable matching the user-specified criteria. The user can optionally specify a generation number, date or key for the variable indicated in the message. Either the group or variable does not exist, or a variable generation with the specified generation number, date, or key does not exist, in the database.
The variables in this message are:
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the reference and invoke Control-M/Analyzer again.
Explanation: The specified local, system or AutoEdit variable does not exist in the Control-M/Analyzer Runtime Environment’s memory.
In this message, varName is the variable that did not exist.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the reference and invoke Control-M/Analyzer again.
Explanation: An attempt was made to change the value of the SYSRUNID system variable, using a DO SET or DO EXTRACT statement, after database variables had already been committed.
The SYSRUNID system variable contains the run ID of the current Control-M/Analyzer run. The value of the run ID must be the same for all the database variables committed in this run. Therefore, the run ID cannot be changed during the run after a database variable has been committed.
In this message, runId is the run ID of the current Control-M/Analyzer run.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Remove the problematic DO statement and invoke Control-M/Analyzer again.
Explanation: An attempt was made to set a system variable that cannot be set.
Most system variables, such as SYSDATE and SYSTIME, cannot be set during Control-M/Analyzer execution because they receive their values only from the system. The Control-M/Analyzer User Guide contains a complete list of system variables, and identifies those that the user can set.
In this message, varName identifies the variable that a user tried to set.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: A nonexisting database variable was specified in a DO SET or DO EXTRACT statement. Either the required database variable exists but its name was specified incorrectly, or the required database variable does not exist.
The variables in this message are:
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: If the database variable name was specified incorrectly, correct it and invoke Control-M/Analyzer again.
To create a database variable, either use the Control-M/Analyzer Online facility, or enable the Automatic Variable Creation Facility to dynamically create the nonexisting database variable during the rule’s execution. For information about the Automatic Database Variable Creation facility, see the Control-M/Analyzer User Guide.
Explanation: Control-M/Analyzer encountered an invalid data line while loading an AutoEdit member. AutoEdit member lines must have the format %%VAR=value.
In this message, line identifies the problematic line.
Control-M/Analyzer skips the problematic line, and continues to load the rest of the lines of the AutoEdit member.
Corrective Action: Correct the problematic line, and invoke Control-M/Analyzer again.
Explanation: While writing an AutoEdit member, the maximum number of output lines was exceeded. By default, Control-M/Analyzer can write a maximum of 1000 lines of variables in an AutoEdit member.
The variables in this message are:
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Notify the INCONTROL administrator.
Explanation: A DO GETMEM statement attempted to load the indicated AutoEdit member, but the member was already loaded in the Control-M/Analyzer Runtime Environment memory by a previous DO GETMEM statement. Loaded AutoEdit members remain in memory until unloaded by a DO PUTMEM statement.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: A DO PUTMEM statement attempted to unload the indicated AutoEdit member, but the member is not in the Control-M/Analyzer Runtime Environment memory.
An AutoEdit member cannot be written back to disk unless it exists in memory. An AutoEdit member is placed in memory when it is loaded using a DO GETMEM statement, or when it is created by using a DO ADDSYM statement to add variables to it.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: This information message accompanies other error messages. This message identifies the AutoEdit member that was being processed when the error specified in any other message occurred.
Corrective Action: No action is required.
Explanation: An attempt was made, using a DO ADDSYM statement, to add a variable to the specified AutoEdit member, but the variable already exists in the AutoEdit member. Variables names must be unique within an AutoEdit member.
Control-M/Analyzer ignores the current DO ADDSYM statement and continues processing.
Corrective Action: Check whether the parameters of the DO ADDSYM statement are correct, and proceed accordingly.
Explanation: An attempt was made to add an AutoEdit variable (varName) to a member but the variable already exists in the memName member. An AutoEdit variable can be stored in only one member.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Do one of the following:
Explanation: A DO ADDSYM statement specifies a variable that already exists as a non-AutoEdit variable. The name cannot refer to an existing variable.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Rename either the existing variable or the variable to be added to an AutoEdit member.
Explanation: An invalid variable reference statement was specified.
For information about variable reference statements, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: An error occurred in the module identified in the message when invoked with the reported option.
The variables in this message are:
The Control-M/Analyzer Runtime environment terminates with an error.
Corrective Action: Record the information in the message and notify your INCONTROL administrator.
Explanation: An error occurred while the specified database variable was being committed. Preceding messages provide additional information regarding the error.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Notify the INCONTROL administrator.
Explanation: A DO COMMIT statement is attempting to commit a database variable that was not previously set. A database variable cannot be committed unless it was previously given a value by means of a DO SET or DO EXTRACT statement.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: An error occurred while trying to dynamically create a database variable using the Automatic Variable Creation Facility. Preceding messages provide additional information regarding the error.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Notify the INCONTROL administrator.
Explanation: A database variable could not be committed using option DELETE or NOW because it was passed as an argument to the current block or rule.
In this message, var is the database variable that could not be committed.
When variables are passed as arguments in a DO BLOCK or RULE statement, their values are copied into BARGnn and RARGnn variables and restored upon block or rule completion. Committing a database variable deletes it from the runtime environment. A database variable passed as an argument cannot be committed using the DELETE or NOW option because it would be meaningless to restore its value after it is deleted.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Place the DO COMMIT statement outside the called block or rule.
Explanation: There was insufficient storage to resolve AutoEdit symbols. Subsequent messages provide additional information regarding the error.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Increase the REGION size and invoke Control-M/Analyzer again. If the problem persists, notify your INCONTROL administrator.
Explanation: A variable that could not be resolved was encountered while trying to resolve AutoEdit variables in the specified string. A reference was probably made to a variable that was not previously set, and, therefore, does not exist.
To resolve AutoEdit symbols in a string, the AutoEdit resolve mechanism searches for local or AutoEdit variables with the specified name. The %% operator must not prefix a database variable. To use the value of a database variable in AutoEdit substitution, the value must first be set to a local variable.
In this message, string is the problematic string.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: A %% AutoEdit operator was specified without an attached variable name.
A %% AutoEdit operator cannot stand alone. A variable name must be appended to the %% operator.
In this message, string identifies the string containing the problematic %% operator.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: A syntax error was detected while trying to resolve the specified string. An invalid AutoEdit expression was specified. Control-M/Analyzer cannot continue resolving the AutoEdit symbols in the string.
In this message, string is the problematic string.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: The outcome of the AutoEdit processing of the specified string results in a string that exceeds the maximum allowed length. Subsequent messages indicate the context in which the error occurred.
In this message, string is the problematic string.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the logical error and invoke Control-M/Analyzer again.
Explanation: An nn value greater than 99 was specified for the AutoEdit symbol %%BLANKnn. Subsequent messages indicate the context in which the error occurred.
In this message, string is the problematic string.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: An internal error occurred while trying to resolve AutoEdit symbols in the specified string.
The variables in this message are:
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Do the following:
Explanation: The format specified for variable varName in statement DO PRINT was not long enough to accommodate the value val. The value of the variable was larger than expected, or a minus sign caused the value to occupy more characters than expected.
A sequence of asterisks is printed instead of the variable’s value. The number of asterisks indicates the specified format length.
Corrective Action: Check why the value of the variable did not fit within the varName variable. If necessary, lengthen the format specified for the varName variable.
Explanation: The length specified in the format of the varName variable was less than or equal to the precision.
For numeric data, the precision field specifies the number of digits following the decimal character. If the precision is not zero, the entire figure should include the decimal character in addition to the digits that follow it. Therefore, the total length must be greater than the precision.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Either lengthen the format of the variable or decrease the precision.
Explanation: An invalid group name was found while parsing the dbRefStatement database reference statement.
A group name must be alphanumeric, and may not exceed 20 characters. For more information, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the group name and invoke Control-M/Analyzer again.
Explanation: An invalid variable name was found while parsing the dbRefStatement database reference statement.
The variable name must be alphanumeric and may not exceed 20 characters. For more information, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the variable name and invoke Control-M/Analyzer again.
Explanation: An invalid generation number was found while parsing the dbRefStatement database reference statement.
The generation number must be an integer between 0 and 999. For more information, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the generation number and invoke Control-M/Analyzer again.
Explanation: An invalid key value was found while parsing the dbRefStatement database reference statement.
The key value must be alphanumeric and may not exceed 20 characters. For more information, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the key value and invoke Control-M/Analyzer again.
Explanation: An invalid run ID was found while parsing the dbRefStatement database reference statement.
The run ID must be alphanumeric and may not exceed 20 characters. For more information, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the run ID value and invoke Control-M/Analyzer again.
Explanation: An invalid date was found while parsing the dbRefStatement database reference statement.
The date must be in yymmdd format. For more information, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the date and invoke Control-M/Analyzer again.
Explanation: A duplicate category was found while parsing the dbRefStatement database reference statement.
Valid categories in a database reference statement are group, variable name, generation, date, key, and run ID. No more than one of each of these categories may be specified in a database reference statement. For more information, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the database reference statement and invoke Control-M/Analyzer again.
Explanation: The period character (.) was found in an invalid location while parsing the dbRefStatement database reference statement.
The database reference statement can contain a period only between the group and variable name. For more information, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the database reference statement and invoke Control-M/Analyzer again.
Explanation: A category that is invalid in the current context was found while parsing the dbRefStatement database reference statement.
The validity of categories (components) in the database reference statement is determined by the context in which the statement is used. For example, if a database variable is assigned a value by a DO SET statement, the run ID should not be specified as part of the database reference statement because the run ID is taken from the SYSRUNID system variable. For more information, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the database reference statement and invoke Control-M/Analyzer again.
Explanation: A invalid category identifier was found while parsing the dbRefStatement database reference statement.
Valid category identifiers are:
Category identifiers must always be preceded by the character @. For more information, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the database reference statement and invoke Control-M/Analyzer again.
Explanation: An internal error occurred while parsing the dbRefStatement database reference statement.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: An internal error occurred while parsing the dbRefStatement database reference statement.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: Control-M/Analyzer is unable to load a user routine specified in the CALLUSER command. Before Control-M/Analyzer can call a user routine, it must first load the routine.
Control-M/Analyzer terminates with a runtime error.
Corrective Action: Check that a module with the name modName exists in the STEPLIB library or in the LINKLIST.
Explanation: Control-M/Analyzer attempted to evaluate the expression identified in the message, but the expression syntax was invalid.
For a detailed description of expression syntax, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the syntax error and invoke Control-M/Analyzer again.
Explanation: While evaluating the expression identified in the message, Control-M/Analyzer encountered unbalanced parentheses.
For a detailed explanation of expression syntax, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the syntax error and invoke Control-M/Analyzer again.
Explanation: An internal evaluation error occurred while evaluating the expression identified in the message.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: The expression identified in the message contains a function call that has too many commas. This means that too many arguments are passed to the function.
Each Control-M/Analyzer function has a defined number of arguments. For a description of expression syntax and Control-M/Analyzer functions, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the syntax error and invoke Control-M/Analyzer again.
Explanation: The expression identified in the message contains a function call that has an invalid number of commas. This means that the number of arguments passed to the function is incorrect.
Each Control-M/Analyzer function has a defined number of arguments. For a description of expression syntax and Control-M/Analyzer functions, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the syntax error and invoke Control-M/Analyzer again.
Explanation: An internal evaluation error occurred while evaluating the expression identified in the message.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: The variable specified in the expr expression does not exist. Control-M/Analyzer can not evaluate an expression if one of the variables it contains does not exist.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Correct the expression or create the missing variable.
Explanation: Control-M/Analyzer attempted to evaluate the expression identified in the message (expr), but the expression syntax was invalid.
For a detailed description of expression syntax, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the syntax error and invoke Control-M/Analyzer again.
Explanation: An internal evaluation error occurred while evaluating the expression identified in the message (expr).
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: While evaluating the expression identified in the message (expr), a calculation result that exceeded the maximum size was produced.
Evaluation results are stored in a variable. The length of the evaluation results cannot exceed the maximum allowable length of the value of the variable.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: While evaluating the expression identified in the message (expr), the Control-M/Analyzer Runtime Environment had insufficient memory to continue with the evaluation.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Increase the REGION size and invoke Control-M/Analyzer again. If the problem persists, notify your INCONTROL administrator.
Explanation: The expression identified in the message (expr) contains a reference to a local variable that was not previously set, or to a database variable that does not exist in the Control-M/Analyzer database. The name of the nonexisting variable appears in a preceding message.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: The expression identified in the message (expr) contains a reference to a variable that should, but does not, contain a numeric value.
Some Control-M/Analyzer functions require that numeric arguments be supplied in predefined positions. For a description of expression syntax, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: Control-M/Analyzer encountered an error while evaluating one of the Control-M/Analyzer functions in the expression identified in the message (expr).
Probably one of the arguments passed to the function was incorrect. For a description of expression syntax and Control-M/Analyzer functions, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: The expression identified in the message (expr) required Control-M/Analyzer to divide by 0.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Correct the arithmetic error and invoke Control-M/Analyzer again.
Explanation: The DBINFO or DDINFO function was called with an invalid request.
For more information on the DBINFO and DDINFO functions, see the Control-M/Analyzer User Guide.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Correct the request string.
Explanation: An internal error occurred in the CTBXALC routine.
Control-M/Analyzer terminates with a runtime error.
Corrective Action: Ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: A problem occurred during dynamic allocation of a file.
The variables in this message are:
For more information on the error and information codes, see the IBM manual MVS Programming: Authorized Assembler Services Guide.
Control-M/Analyzer terminates with a runtime error.
Corrective Action: Notify your INCONTROL administrator.
Explanation: The dynamic allocation program abended with the abend code abend.
Control-M/Analyzer terminates with a runtime error.
Corrective Action: For information about the abend, refer to IBM message and code documentation, and correct the problem accordingly. If you need assistance, ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: An internal error occurred. The return code issued is not valid.
Control-M/Analyzer terminates with a runtime error.
Corrective Action: Note the identity of this message and the invalid return code, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: This information message accompanies other messages which indicate a problem. This message indicates the data set name and DD statement associated with any accompanying message.
Corrective Action: No action is required.
Explanation: The specified value is not valid for use as a member name.
Control-M/Analyzer terminates with a runtime error.
Corrective Action: Correct the member name and rerun the rule.
Explanation: An internal error occurred.
Control-M/Analyzer terminates with a runtime error.
Corrective Action: Ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: Control-M/Analyzer was unable to open a sequential file. This message is accompanied by other messages which provide additional information.
Control-M/Analyzer terminates with a runtime error.
Corrective Action: Check the accompanying messages to determine the problem. Resolve accordingly.
Explanation: An abend occurred while performing I/O to a sequential file.
Control-M/Analyzer terminates with a runtime error.
Corrective Action: For information about the abend, refer to IBM message and code documentation and correct the error accordingly. If you need further assistance, ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: An internal error occurred. The return code issued (rc) is not valid.
Control-M/Analyzer terminates with a runtime error.
Corrective Action: Note the identity of this message and the invalid return code, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: This information message accompanies other messages which indicate a problem. This message indicates the data set name and DD statement associated with any accompanying message.
Corrective Action: No action is required.
Explanation: An error occurred while reading data in an ON VSAM statement.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: For the meaning of the return and reason codes, examine your IBM documentation for VSAM programming, and correct the problem accordingly.
Explanation: The VSAM file specified in an ON VSAM statement could not be opened.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: For the meaning of the return and reason codes, refer to your IBM documentation for VSAM programming, and correct the problem accordingly.
Explanation: The first key was greater than the last key in the key range specified in statement ON VSAM.
The variables in this message are:
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Correct the values specified for the FIRSTKEY and LASTKEY parameters as appropriate.
Explanation: An internal error occurred while reading from the spool.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: An internal error occurred while reading from spool.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: This information message accompanies other error messages. This message identifies the sysout that was being processed when the error specified in any other message occurred.
Corrective Action: No action is required.
Explanation: The specified SYSOUT was not found during reading of the SYSOUT. Subsequent messages indicate the exact SYSOUT specification.
For a discussion of Control-M/Analyzer SYSOUT processing methods, see the Control-M/Analyzer chapter of the INCONTROL for z/OS Installation Guide and the Control-M/Analyzer User Guide.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Do the following:
Explanation: The specified operation could not be performed. This message follows a more detailed message that identifies the problem.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Record the information in the accompanying message and consult your INCONTROL administrator.
Explanation: Control-M/Analyzer Runtime environment could not lock a database variable or release a previously locked one.
A database variable is locked by the user accessing it to avoid simultaneous update by other users. Either a variable used in the rule or the whole Control-M/Analyzer database is currently in use.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Schedule the rule execution so that it does not conflict with other rules using the same database variables or with utilities using the entire database.
Explanation: An internal error occurred while processing the IOA log.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: An internal error occurred while processing the IOA Log File.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: An internal error occurred while initializing the Control-M/Analyzer environment.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: An internal error occurred while initializing the Control-M/Analyzer environment.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: An internal error occurred while performing a WTO operation.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: An internal error occurred while performing a WTO operation.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: An internal error occurred while gathering information from the system.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: An internal error occurred while gathering information from the system.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: Control-M/Analyzer could not run because of insufficient storage.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Increase the value of the REGION parameter.
Explanation: The requested member is not found in the library.
Possible causes are:
Rule processing stops and Control-M/Analyzer terminates.
Corrective Action: Correct the library name for the rule or AutoEdit member and rerun the rule.
Explanation: The requested member is not a partitioned data set.
Possible causes are:
Rule processing stops and Control-M/Analyzer terminates.
Corrective Action: Correct the library name for the rule or AutoEdit member, and rerun the rule.
Explanation: The record format of the requested data set name (DSN) is not fixed. Probably the DSN does not refer to the correct file.
Possible causes are:
Rule processing stops and Control-M/Analyzer terminates.
Corrective Action: Ensure that the DSN points to the correct file. If it is already pointing to the correct file, determine why the file does not have a fixed format.
Explanation: The record length of the requested data set is not 80. The probable cause is that the data set name (DSN) does not refer to the correct file.
Possible causes are:
Rule processing stops and Control-M/Analyzer terminates.
Corrective Action: Ensure that the DSN points to the correct file. If it is already pointing to the correct file, determine why the file does not have a record length of 80.
Explanation: The data set is held exclusively by another user.
Possible causes are:
Rule processing stops and Control-M/Analyzer terminates.
Corrective Action: Try again.
Explanation: A Control-M/Analyzer internal error occurred while trying to read a member from a library.
Possible causes are:
Rule processing stops and Control-M/Analyzer terminates.
Corrective Action: Look for additional messages on the IOA Log that may clarify the situation. You or your INCONTROL administrator should refer to IBM message and code documentation for information about the abend, and make corrections accordingly. In any case, your INCONTROL administrator should contact BMC Customer Support.
Explanation: The requested data set name (DSN) is not in the catalog.
Possible causes are:
Rule processing stops and Control-M/Analyzer terminates.
Corrective Action: Ensure that the DSN is cataloged. Rerun the rule.
Explanation: Dynamic allocation for the requested data set name (DSN) failed.
Possible causes are:
Rule processing and Control-M/Analyzer terminates.
Corrective Action: Ask your INCONTROL Administrator to contact BMC Customer Support.
Explanation: Internal error while trying to read a member from a library.
Possible causes are:
Rule processing stops and Control-M/Analyzer terminates.
Corrective Action: Ask your INCONTROL Administrator to contact BMC Customer Support.
Explanation: There is insufficient storage to read a large member from the library.
Possible causes are:
Rule processing stops and Control-M/Analyzer terminates.
Corrective Action: Increase the REGION size or logon size, and try again.
Explanation: A Control-M/Analyzer internal error occurred while trying to read a directory of a library. This message can appear under the Control-M/Analyzer Online Facility.
Rule processing stops and Control-M/Analyzer terminates.
Corrective Action: Ask your INCONTROL Administrator to contact BMC Customer Support.
Explanation: A Control-M/Analyzer internal error occurred while trying to read a member from a library.
Possible causes are:
Rule processing stops and Control-M/Analyzer terminates.
Corrective Action: Ask your INCONTROL Administrator to contact BMC Customer Support.
Explanation: You are trying to save an AutoEdit member which does not exist.
The AutoEdit member is not saved.
Corrective Action: Create the member.
Explanation: You are trying to create an AutoEdit member which already exists.
The AutoEdit member is not created.
Corrective Action: Save the member.
Explanation: The record format of the library to be opened differs from the requested format.
Possible causes are:
Rule processing stops and Control-M/Analyzer terminates.
Corrective Action: Notify your INCONTROL administrator.
Explanation: Internal error while trying to read a member from a library.
Possible causes are:
Rule processing stops and Control-M/Analyzer terminates.
Corrective Action: Ask your INCONTROL Administrator to contact BMC Customer Support.
Explanation: This information message accompanies other messages which indicate the problem.
The variables in this message are:
Corrective Action: No action is required.
Explanation: An internal error occurred while trying to parse the string (string) identified in the message.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: An internal error occurred while trying to parse the string (string) identified in the message. One of the resulting words was longer then the maximum allowable word length.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: Control-M/Analyzer found too many arguments while parsing the argument list of a DO BLOCK, DO CALLUSER or DO RULE statement.
A maximum of 50 arguments can be passed in a DO BLOCK, DO CALLUSER or DO RULE argument list.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Explanation: An internal error occurred while parsing a string.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: The DB2 subsystem could not be connected.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Consult your DB2 administrator.
Explanation: The DB2 subsystem could not be opened.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Consult your DB2 administrator.
Explanation: DB2 issued a warning code.
For the explanation of the warning code, refer to DB2 literature.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Try to correct the error on the information provided by the warning code and the DB2 literature. If necessary, consult your DB2 administrator.
Explanation: DB2 issued a SQL error code.
For the explanation of the warning code, refer to DB2 literature.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Try to correct the error on the information provided by the warning code and the DB2 literature. If necessary, consult your DB2 administrator.
Explanation: None of the arguments specified by the user in the SQL SELECT statement refer to a valid column in one of the selected DB2 tables.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Include at least one column name belonging to one of the selected DB2 tables in the SQL statement in your rule.
Explanation: One of the columns specified in the SQL statement has an unrecognized column type as defined in the DB2 catalog.
Possible causes are:
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Do the following:
Explanation: The DB2 CLOSE THREAD call did not succeed. The DB2 CONNECT, OPEN THREAD and SQL calls succeeded, but the CLOSE THREAD call did not. This indicates either a change in the availability of the DB2 subsystem or an internal error.
Possible causes are:
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Have your DB2 database administrator check the status of the DB2 subsystem identified in the message, and the status of the open threads under it. If necessary, close the thread for CTBDB2 manually.
Explanation: The DB2 DISCONNECT call did not succeed.
Possible causes are:
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Have your DB2 database administrator verify that the DB2 subsystem identified in the message is active.
Explanation: An internal error occurred while reading a CDAM data set.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: An internal error occurred while reading a CDAM data set.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: This information message accompanies other error messages.
In this message cdam_crit identifies the CDAM criteria that were being processed when the error specified in any other message occurred.
Corrective Action: No action is required.
Explanation: The requested CDAM file was not found. The error occurred while attempting to read the requested CDAM file. Subsequent messages indicate the CDAM criteria that were being used when the error occurred.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the errors and invoke Control-M/Analyzer again.
Explanation: An internal error occurred while Control-M/Analyzer was accessing the Rule Activity File.
The variables in this message are:
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Contact your INCONTROL administrator.
Explanation: An internal error occurred while Control-M/Analyzer was accessing the Report file.
The variables in this message are:
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Contact your INCONTROL administrator.
Explanation: Reports cannot be written to the Control-M/Analyzer report file because the file has become full.
The Control-M/Analyzer Runtime Environment continues executing, but a report for the current Control-M/Analyzer invocation is not created.
Corrective Action: Contact your INCONTROL administrator.
BMC recommends that you run the CTBJAFDL Control-M/Analyzer utility periodically, to erase unneeded reports in the report file. For more information about this utility, see the INCONTROL for z/OS Utilities Guide.
Explanation: An internal error occurred while Control-M/Analyzer was accessing the Group file. The error occurred while performing an operation of type option.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Contact your INCONTROL administrator.
Explanation: This warning indicates that a condition cond already exists in the IOA Conditions file. It does not usually indicate a problem.
The SYSRC system variable is set to 4 and processing continues.
The condition is not added to the IOA Conditions file.
Corrective Action: No action is required.
Explanation: This message indicates that the cond condition cannot be deleted because it does not currently exist in the IOA Conditions file. The cond condition was previously deleted or never created.
The condition is not deleted again.
Corrective Action: No action is required.
Explanation: An internal error occurred while Control-M/Analyzer was accessing the Active Balancing file, during an operation of type option.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Contact your INCONTROL administrator.
Explanation: The Control-M/Analyzer Active Balancing file is full and needs to be compressed. It is not possible to order Control-M/Analyzer missions into the file, or run unscheduled Control-M/Analyzer invocations that also need to add an entry to this file.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Contact your INCONTROL administrator.
Run the CTBFRM Control-M/Analyzer utility once a day to compress the Active Balancing file. If the Active Balancing file needs to be compressed more than once a day, it is advisable to enlarge the size of the file.
Explanation: An internal error occurred while Control-M/Analyzer was reading a Control-M SYSDATA data set.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: An internal error occurred while Control-M/Analyzer was reading a Control-M SYSDATA data set.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Collect any information contained in CTB200S messages that precede this message, and ask your INCONTROL administrator to contact BMC Customer Support.
Explanation: This information message follows a more detailed message issued when a problem occurs using ON SYSDATA.
Corrective Action: No action is required.
Explanation: Control-M/Analyzer could not find the requested Control-M/Analyzer SYSDATA data set. The error occurred during an attempt to read the SYSDATA data set of the current job. Either Control-M or Control-M/Restart was not installed or ARCHIVE was not set to Y in the scheduling table.
The Control-M/Analyzer Runtime Environment terminates with an error.
Corrective Action: Correct the error and invoke Control-M/Analyzer again.
Parent Topic |