|
|
|
|
|
This group includes messages for the Control-M/Analyzer product.
Explanation: The general system Error Logger detected an error which occurred at a certain location. This message is issued when rare or unexpected errors occur.
The variables in this message are:
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Record the content of this message and consult your INCONTROL administrator.
Explanation: The general system Error Logger detected an error which occurred at the location indicated in the message (name and line). This message is issued when rare or unexpected errors occur.
The variables in this message are:
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Record the content of this message and consult your INCONTROL administrator.
Explanation: The resolved length of the variable name exceeds the maximum valid length. The variable name was specified using AutoEdit symbols.
The variables in this message are:
Control-M/Analyzer terminates.
Corrective Action: Correct the problem and rerun the rule.
Explanation: The resolved length of the library name exceeds the maximum valid length. The library name was specified using AutoEdit symbols in a DO GETMEM, PUTSYM, or ADDSYM statement.
The variables in this message are:
Control-M/Analyzer terminates.
Corrective Action: Correct the problem and rerun the rule.
Explanation: The resolved length of the member name exceeds the maximum valid length. The member name was specified using AutoEdit symbols in a DO GETMEM, PUTSYM, or ADDSYM statement.
The variables in this message are:
Control-M/Analyzer terminates.
Corrective Action: Correct the problem and rerun the rule.
Explanation: The resolved length of the variable exceeds the maximum valid length. The variable was specified using AutoEdit symbols in a DO SET or EXTRACT statement.
The variables in this message are:
Control-M/Analyzer terminates.
Corrective Action: Correct the problem and rerun the rule.
Explanation: This information message indicates that a DO GETMEM statement, but not a DO PUTMEM statement, was requested and performed for an AutoEdit member. This could, but does not necessarily, indicate a problem.
Corrective Action: If this is not what you intended correct the rule.
Explanation: This information message indicates that, because Control-M/Analyzer encountered an error during rule processing, variables not explicitly committed by a DO COMMIT NOW statement will not be committed.
This message follows other messages that describe the error.
Control-M/Analyzer terminates. Variables not explicitly committed by statement DO COMMIT NOW are not committed.
Corrective Action: Using the information provided in the other messages, correct the problem and rerun the rule.
Explanation: The resolved variable name contains embedded blanks. The variable name was specified using AutoEdit symbols. Its resolved value should not, but does, contains embedded blanks.
In this message, varName is the first 20 characters of the problematic variable name.
Control-M/Analyzer terminates.
Corrective Action: Correct the problem and rerun the rule.
Explanation: An attempt was made to pass a variable to a rule, block or user routine without previously initializing the variable.
The variable name may be incorrectly specified in the DO RULE, BLOCK, or CALLUSER statement and the intended variable name was used. Before a variable can be passed to another rule, block, or user routine, or used in a DO RULE, BLOCK, or CALLUSER statement, the variable must be used at least once in the rule.
Control-M/Analyzer terminates.
Corrective Action: Correct the variable name if it is in error. Ensure that the variable name is initialized, that is, specified in a DO SET statement, prior to its usage in a DO RULE or BLOCK or CALLUSER statement.
Explanation: A value extracted by a DO EXTRACT statement for averaging or summing is not numeric. The extracted value must be numeric. This message is accompanied by either the CTB220E message or the CTB221E message.
Control-M/Analyzer terminates.
Corrective Action: Correct the problem and rerun the rule.
Explanation: This message accompanies the CTB219E message and indicates precisely which operation was being attempted when the error occurred.
Control-M/Analyzer terminates.
Corrective Action: Correct the problem and rerun the rule.
Explanation: This message accompanies the CTB219E message and indicates precisely which operation was attempted when the error occurred.
Control-M/Analyzer terminates.
Corrective Action: Correct the problem and rerun the rule.
Explanation: The requested process cannot be applied to the value obtained by the DO EXTRACT statement.
The variables in this message are:
For information about permitted processes and valid input for processes, see the Control-M/Analyzer User Guide.
Control-M/Analyzer terminates.
Corrective Action: Correct the problem and rerun the rule.
Explanation: An attempt was made to use a database variable not previously defined in the database.
Control-M/Analyzer allows you to automatically create new database variables only if the VARCRET parameter in the CTBPARM member is set to Y.
Control-M/Analyzer terminates.
Corrective Action: If the variable name was specified incorrectly, correct it and rerun the rule. To create a new database variable, set the VARCRET parameter in the CTBPARM member to Y and rerun the rule.
Explanation: An attempt was made to set the SYSDBVGENS parameter to a value higher than the maximum allowed.
The SYSDBVGENS parameter determines the number of generations of automatically generated database variables. The maximum number allowed is 1000.
Control-M/Analyzer terminates.
Corrective Action: Correct the problem and rerun the rule.
Explanation: An attempt was made to set the value of the SYSDBVGENS parameter to a nonnumeric value.
The SYSDBVGENS parameter is used to determine the number of generations of automatically generated database variables. Its value must be numeric.
Control-M/Analyzer terminates.
Corrective Action: Correct the problem and rerun the rule.
Explanation: An internal error occurred while processing variables.
Control-M/Analyzer terminates.
Corrective Action: Ask your INCONTROL administrator to call BMC Customer Support.
Explanation: The input variable is not the correct length for the selected DO EXTRACT statement process.
The following DO EXTRACT statement processes require variables with the lengths indicated:
Control-M/Analyzer terminates.
Corrective Action: Correct the problem and rerun the rule.
Explanation: The requested process is unknown to Control-M/Analyzer. The process name was incorrectly specified. The type descriptor BUILT-IN appears in the message only if the process is a BUILT-IN process.
Control-M/Analyzer terminates.
Corrective Action: Correct the process name and rerun the rule.
Explanation: An attempt was made to use a database variable that was one of the following:
Control-M/Analyzer allows you to automatically create new database variables within the group of the current rule if the VARCRET parameter in the CTBPARM member is set to Y.
Control-M/Analyzer terminates.
Corrective Action: If the variable was specified incorrectly, correct it and rerun the rule. Otherwise, predefine the variable and rerun the rule.
Explanation: The Control-M/Analyzer security interface does not permit you to perform the requested operation (opn) on the Control-M/Analyzer database.
Control-M/Analyzer terminates.
Corrective Action: If you think you should be authorized to perform the requested operation, contact your security administrator.
Explanation: The Control-M/Analyzer security interface does not permit you to use the grp group.
Control-M/Analyzer terminates.
Corrective Action: If you think you should be authorized to use the specified group, contact your security administrator.
Explanation: An invalid value (val) was assigned to the varName system variable. The varName system variable can have only certain values.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Consult the Control-M/Analyzer User Guide for information about the varName system variable.
Explanation: The AutoEdit variable or System variable varName was specified as an argument in a DO RULE, BLOCK, or CALLUSER statement.
AutoEdit and System variables may not be passed as arguments to DB2.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Assign the value of the argument in error to a user variable and pass that user variable to DB2 instead.
Explanation: The name (varName) of a variable to be created has the prefix of a variable that the DO SET command cannot create. The DO SET command can create user and AutoEdit variables only. In this case, a prefix was specified which marks another type of variable, for example, a system variable.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Correct the variable name.
Explanation: This message indicates that the Active Balancing file does not contain the missionName mission specified in the call to Control-M/Analyzer.
Control-M/Analyzer terminates.
Corrective Action: Either correct the name of the mission, or order the mission to the Active Balancing file. Rerun the Control-M/Analyzer rule.
Explanation: Control-M/Analyzer was unable to add information to the Active Balancing file. This message usually indicates that the Active Balancing file is full.
Control-M/Analyzer terminates.
Corrective Action: Contact your INCONTROL administrator.
Explanation: Control-M/Analyzer failed to add a record to the file identified in the message because it was full.
The variables in this message are:
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Increase the size of the data set referenced by the dsn DD statement.
Explanation: The dsn Control-M/Analyzer database index file could not be opened. Index files must have a positive key length.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Reformat the data set referenced by the dsn DD statement and rerun the job.
Explanation: The QNAME specified in the dsn Control-M/Analyzer database file was different than the expected QNAME. The version of the Control-M/Analyzer runtime environment is different than the version of the utility which was used to format the file.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Verify that the correct Control-M/Analyzer database was allocated and rerun the job.
Explanation: Control-M/Analyzer could not lock the database file for update.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Check the reason for the conflict and rerun the Control-M/Analyzer job after the current applications have finished running.
Explanation: Control-M/Analyzer failed due to an integrity error in the dsn mirror database file.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Disable the mirror database installed for this particular file. Record the content of this message and report it to your INCONTROL administrator. If the situation allows, the Control-M/Analyzer job can be rerun.
Explanation: An error occurred while performing an operation on the specified file.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Provide the sysout and contents of this message to your INCONTROL administrator.
Explanation: An error occurred while performing the operation on the ddName file.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Record the contents of this message and consult your INCONTROL administrator.
Explanation: The IOADBF load module cannot be found.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Check the concatenated load libraries referenced by the DDNAME STEPLIB statement and rerun the Control-M/Analyzer job.
Explanation: The data component of the dsn Control-M/Analyzer database file was formatted with a positive-length key. Data files must not be keyed.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Reformat the data set referenced by the dsn DD statement and rerun the job.
Explanation: A length of a key or record specified when formatting the file was incorrect. Each Control-M/Analyzer database file must adhere to specific length specifications.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Reformat the data set referenced by the ddName DD statement and rerun the job.
Explanation: The specified ON block cannot be used in the specified environment. ON blocks are restricted to specific environments, as follows:
Control-M/Analyzer terminates.
Corrective Action: Correct the error, and rerun the rule.
Explanation: The record offset (for RRDS files) or the RBA (for ESDS files) specified in the FIRSTKEY or the LASTKEY parameter was not numeric.
The format of the record offset or RBA format is C nnn, where nnn is any 3-digit numeric string.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Set the FIRSTKEY or the LASTKEY parameter to a value in the format C nnn, where nnn is any 3-digit numeric string.
Explanation: The criteria specified in either the FIRSTKEY or the LASTKEY parameter, or both these parameters, of the ON VSAM statement were not in the correct format.
The values of the FIRSTKEY and LASTKEY parameters must be in the format C cccc ,X xxxx ,... for all VSAM file types.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Correct the values of the FIRSTKEY and LASTKEY parameters into the required format.
Explanation: The fileName file specified in an ON statement was not found.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Correct the file name specification. If it includes AutoEdit variable substitution, make sure the variables have valid values.
Explanation: The character specified after BW in a DO EXTRACT statement was not a positive integer.
The n in the BW n process in a DO EXTRACT statement specifies the number of the word to be extracted, and must be a positive integer.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Verify that only a positive integer follows BW in the BW n specification.
Explanation: The number of words in the text to be examined was less than the value of n specified in the BW n process in a DO EXTRACT statement. This message may indicate either an error in specifying the BW n process, or unexpectedly short data.
The SYSRC system variable is set to 4, and processing continues.
Corrective Action: Examine all the following and ensure that they are correct:
Explanation: The SYSEXTUPROC system variable was not assigned a value when the BUPROC process was requested in a DO EXTRACT statement. The BUPROC process in a DO EXTRACT statement requires the SYSEXTUPROC system variable to be defined.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Use a DO SET statement to store the desired user-defined process in the SYSEXTUPROC system variable prior to specifying the BUPROC process.
Explanation: The user-defined combined EXTRACT process name was not in the format BCPROC n, where n is an integer from 1 to 10.
The combined EXTRACT process invokes a sequence of processes specified in the SYSCPROC n system variable. This variable can be defined only when n is an integer from 1 through 10.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Set the combined EXTRACT process name in the format BCPROC n, where n is an integer from 1 through 10.
Explanation: The combined EXTRACT process referred to an undefined system variable (SYSCPROC n).
The combined EXTRACT process BCPROCn invokes a sequence of processes specified in the SYSCPROC n system variable. This system variable must be defined before executing an EXTRACT statement that refers to it.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Set the SYSCPROC n system variable to a sequence of EXTRACT processes or change the reference in the EXTRACT statement to a defined system variable.
Explanation: During a Control-M/Analyzer run, the file referenced by the ddName DD statement could not be opened.
Probable causes are:
Execution continues. If the error occurred during a DO PRINT statement, then output to the file referenced by the ddName DD statement is rerouted to the file referenced by SYSUSERDD statement.
Corrective Action: Correct the JCL and rerun the job.
Explanation: During a Control-M/Analyzer run, the file referenced by the ddName DD statement could not be opened.
Probable causes are:
The Control-M/Analyzer runtime environment ends with an error.
Corrective Action: Correct the JCL and rerun the job.
Explanation: An occurrence specified in the func function was zero or negative.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Specify a positive occurrence value.
Explanation: The word number specified in the WORD function was zero or negative.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Specify a positive word number.
Explanation: The data set entry number specified in the DDINFO function was zero or negative.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Specify a positive data set entry number.
Explanation: The starting occurrence exceeds the ending occurrence in the specified occurrence range.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Set the occurrence range in the func function to begin with the lower occurrence.
Explanation: The number of words in the input string to the WORD function was smaller than the requested word number.
This message may indicate either an error in coding the call to the WORD function or an unexpectedly short input string.
The SYSRC system variable is set to 4 and processing continues.
Corrective Action: Ensure that the parameters of the WORD function are specified correctly.
Explanation: The DD name (ddName) specified in the DDNUM or the DDINFO function was not found.
There is no DD statement with the ddName DD name in the procStep.pgmStep job step.
The SYSRC system variable is set to 4 and processing continues.
Corrective Action: Verify that the parameters specified in the DDNUM or DDINFO function are correct.
Explanation: The number of data sets allocated to the ddName DD statement is less than the requested entry number in the DDINFO function.
The SYSRC system variable is set to 8 and processing continues.
Corrective Action: Specify a smaller data set entry number or verify that the JCL is correct.
Explanation: The MEMLINES function failed to retrieve the number of lines of a member, because ISPF statistics did not exist for the member. The MEMLINES function obtains the member line-count from the ISPF statistics of the member. When the statistics are missing, the MEMLINES function cannot obtain the line-count.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Save the member using ISPF so that statistics for it are created.
Explanation: A DO SET expression could not read a database variable belonging to the grp group, due to group mode differences between the specified group and the current group. Control-M/Analyzer determines if it can read database variables belonging to other groups based on the modes of the groups.
When the current group is in ACTIVE mode, Control-M/Analyzer can read variables belonging to other groups in ACTIVE mode. It cannot read variables belonging to other groups in SIMULATION or DEFINE mode.
When the current group is in SIMULATION mode, Control-M/Analyzer can read variables from other groups in ACTIVE or SIMULATION mode. It cannot read variables belonging to other groups in DEFINE mode.
This message follows the CTB262I message, which specifies the name and mode of the group that Control-M/Analyzer attempted to access in order to read the variable. For more information about group modes, see the Control-M/Analyzer User Guide.
Control-M/Analyzer terminates.
Corrective Action: Ensure that the groups which Control-M/Analyzer attempts to access for a read operation are in an appropriate mode. Invoke Control-M/Analyzer again.
Explanation: The indicated database variable belonging to the grp group could not be set, due to group mode differences between that group and the current group. Control-M/Analyzer determines if it can set database variables belonging to other groups based on the modes of the groups.
When the current group is in ACTIVE mode, Control-M/Analyzer can set variables belonging to other groups that are in ACTIVE mode. It cannot set variables belonging to other groups in SIMULATION or DEFINE mode.
When the current group is in SIMULATION mode, Control-M/Analyzer can set variables belonging to other groups in SIMULATION mode. It cannot set variables belonging to other groups in ACTIVE or DEFINE mode.
This message follows the CTB262I message, which specifies the name and mode of the group that Control-M/Analyzer tried to access to set the variable. For more information about group modes, see the Control-M/Analyzer User Guide.
Control-M/Analyzer terminates.
Corrective Action: Ensure that the groups which Control-M/Analyzer attempts to access for a set operation are in an appropriate mode. Invoke Control-M/Analyzer again.
Explanation: This information message indicates the name and mode of the group that Control-M/Analyzer tried to access for either a read or a set operation.
This message accompanies the CTB260E message or the CTB261E message, issued when the requested operation could not be performed because of mode differences between the group to be accessed and the current group.
Corrective Action: No action is required.
Explanation: No variables were found whose names belong to the specified set. This message is issued by the SUM, HOWMANY, and NEXTVAR functions when no variable names match the name-mask arguments or the database criteria.
The HOWMANY and SUM functions return zero. The NEXTVAR function returns a blank string. The SYSRC system variable is set to 8.
Corrective Action: Verify that this situation is not a result of improper coding or improper input data.
Explanation: One of the variables in the set contains a nonnumeric value. The SUM function expects a name-mask or database criteria that specifies only numeric variables.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Eliminate non-numeric values from the variable set in one of the following ways:
Explanation: The startvar starting variable specified in the NEXTVAR function does not belong to the varset set, or the startvar variable was not found. The startvar starting variable specified in the NEXTVAR function must exist, and it must belong to the identified variable set.
The Control-M/Analyzer runtime environment terminates with an error.
Corrective Action: Verify that the startvar variable is contained in the varset set. Either respecify the criteria or change the startvar variable name.
Explanation: Highlighted, unrollable message.
This information message is activated by the SHOUT facility.
In this message, userId is the user ID of the job order requesting the SHOUT.
Corrective Action: No action is required.
Explanation: This information message indicates that a new Dynamic Destination Table has been loaded by the IOA Runtime environment. This message is also generated when the SHOUT Facility is initialized under the IOA Runtime environment.
Corrective Action: No action is required.
Explanation: Loading of the Dynamic Destination Table by the IOA Runtime Environment failed.
This could be due to one of the following:
If the failure occurs during the initialization of the IOA Runtime Environment, SHOUT notifications will not be controlled by the Dynamic Destination Table.
Corrective Action: Check the MVS Log for the reason for the failure (probably a system abend code). Correct the problem and then run the job again.
Parent Topic |