|
|
|
|
|
This group includes messages for the Control-O product.
Explanation: This informative message is issued when the CTOFST Statistics Formatting utility starts formatting the Statistics file.
Corrective Action: No action is required.
Explanation: Dynamic allocation of the Statistics file dsn failed with the return code rc and the reason code rsn.
The CTOFST Statistics Formatting utility terminates with a return code of 08.
Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide to determine the cause of the error, and correct the error accordingly. If not successful, contact BMC Customer Support.
Explanation: The SMF ID specified for the CTOFST Statistics Formatting utility does not match the active MVS SMF ID. The SMF ID for the CTOFST utility is specified in the input PARM string. The current MVS SMF ID is specified in IEASMFxx of SYS1.PARMLIB. These SMF IDs should match.
The CTOFST utility terminates with return code of 08.
Corrective Action: Correct the PARM string to reflect the active SMF ID, and rerun the job.
Explanation: The CTOFST Statistics Formatting utility failed to format the Statistics file because the file is allocated to another user. The CTOFST Statistics Formatting utility attempts to allocate the Statistics file with DISP set to OLD.
The utility terminates with a return code of 08.
Corrective Action: Make sure that no user is allocated to the Statistics file, and rerun the job.
Explanation: The CTOFST Statistics Formatting utility could not successfully open the Statistics file.
The utility terminates with a return code of 08.
Corrective Action: Look for previous MVS error messages regarding the opening of the Statistics file. Correct the error and rerun the job.
Explanation: The CTOFST Statistics Formatting utility unsuccessfully attempted to open the Messages file specified in the SYSPRING DD statement. An OPEN request was issued to the Messages file but was unsuccessful. A possible cause is that the SYSPRINT DD statement may not have been specified in the job stream.
The utility terminates with a return code of 08.
Corrective Action: Look for earlier MVS error messages regarding the opening of the Messages file. Correct the error, and rerun the job.
Explanation: The formatting of the Statistics file was unsuccessful.
The CTOFST Statistics Formatting utility terminates with a return code of 08.
Corrective Action: Look for earlier error messages to determine the cause of the error. Correct the error and rerun the job.
Explanation: A WRITE request failed during the formatting of the Statistics file.
The CTOFST Statistics Formatting utility terminates with a return code of 08.
Corrective Action: Delete the Statistics file. Then rerun the job, specifying smfid volser and unit. Earlier MVS error messages regarding the Statistics file may indicate the cause of the error.
Explanation: This information message is issued when the CTOFST Statistics Formatting utility completes with no errors.
Corrective Action: No action is required.
Explanation: The DEFSTAT utility was called with incorrect parameters.
The utility terminates with a return code of 08.
Corrective Action: Correct the parameters and rerun the utility.
Explanation: The CTORSTM Statistics report utility could not open the input file specified in the DAREPIN DD statement.
An OPEN request was issued to the input file, but was unsuccessful. A possible cause of the problem is that the DAREPIN DD statement may not have been specified in the job stream.
The utility terminates with a return code of 08.
Corrective Action: Look for previous MVS error messages regarding the opening of the input file. Correct the error and rerun the job.
Explanation: The CTORSTM Statistics report utility encountered internal error errorText.
The utility terminates with a return code of 08.
Corrective Action: Contact BMC Customer Support.
Explanation: The CTORSTM Statistics report utility could not open the report file specified in the SYSPRINT DD statement.
An OPEN request was issued to the REPORT file, but was unsuccessful. A possible cause of the problem is that the SYSPRINT DD statement may not have been specified in the job stream.
The utility terminates with a return code of 08.
Corrective Action: Look for previous MVS error messages regarding the opening of the report file. Correct the error and rerun the job.
Explanation: The CTORSTM Statistics report utility could not open the Statistics file.
Failure to open the Statistics file may have been caused by one of the following:
The utility terminates with a return code of 08.
Corrective Action: Look for previous MVS error messages regarding the opening of the Statistics file. Correct the error and rerun the job.
Explanation: Dynamic allocation of Statistics file dsn failed with return code rc and reason code rsn.
The CTORSTM Statistics Report utility terminates with a return code of 08.
Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide to determine the cause of the error and correct the error accordingly. If not successful, contact BMC Customer Support.
Explanation: The CTORSTM Statistics file utility could not successfully close the Statistics file.
The utility terminates with a return code of 08.
Corrective Action: If no MVS error messages clarifying the error were issued, this is probably an internal error. In this case, please report it to BMC Customer Support.
Explanation: There was an attempt to insert a row in a Variable database, but no row number is available at the point of insertion. Variable database rows are originally numbered by thousands. Rows added later are assigned numbers in the gaps. This message is generated if a suitable row number is not available at the location where a new row is to be inserted. See the description of the IOA Variable Database facility in the Control-O User Guide for an explanation of how database row numbers are assigned.
The row is not added to the Variable database.
Corrective Action: Renumber the existing rows in the database, as follows:
For more information about the IOADUL and IOADLD utilities, see the INCONTROL for z/OS Utilities Guide.
Explanation: The user is unauthorized to perform the requested insert or update on the variable.
The variable is not created or updated.
Corrective Action: To be authorized to perform the attempted operation, contact your INCONTROL administrator.
Explanation: An attempt was made to create a new variable, but there is insufficient space in the Variables file. New variables cannot be defined until sufficient space is provided.
The new variable is not created.
Corrective Action: Provide more free space in the Variables file. For information about increasing the size of IOA Access Method files and about compressing the data in such files, see the INCONTROL for z/OS Administrator Guide.
Explanation: An attempt was made to create a new column, but there is insufficient space in the Columns file. New columns cannot be defined until sufficient space is provided.
Corrective Action: Provide more free space in the Columns file. For information about increasing the size of IOA Access Method files and about compressing the data in such files, see the INCONTROL for z/OS Administrator Guide.
Explanation: An attempt was made to create a new variable, but there is insufficient space in the Variables database index file. New variables cannot be defined until sufficient space is provided.
The new variable is not created.
Corrective Action: Provide more free space in the Variables database index file. For information about increasing the size of IOA Access Method files and about compressing the data in such files, see the INCONTROL for z/OS Administrator Guide.
Explanation: An attempt was made to create a column, but a column with that name already exists in the database. The column cannot be created, because it already exists. It cannot be saved, because it was specified by means of command Insert.
The Exit Option Window is closed. The database Column Definition screen remains displayed.
Corrective Action: Either specify a database column name that does not currently exist in the database, or use the CANCEL command to exit without saving the database column definition.
Explanation: An error occurred while attempting to update a column in the variable database Column Definition screen.
The variable database column definition is not updated.
Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.
Explanation: An internal error occurred while trying to update the columns definition of the Global Variable database.
The update is not performed.
Corrective Action: Call your INCONTROL administrator.
Explanation: This information message is the normal start message issued during initialization of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.
Control-O or the CMEM monitor detected an environment which supports the MVS OpenEdition interface with Control-O and began initializing the OpenEdition environment.
Corrective Action: No action is required.
Explanation: This information message is the normal start message issued during initialization of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.
Control-O or the CMEM monitor loaded the OpenEdition interface module into storage. This message is issued only for the first Control-O or CMEM monitor in the system.
Corrective Action: No action is required.
Explanation: This information message is the normal start message issued during initialization of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.
The current Control-O or CMEM subsystem has registered itself (meaning, recorded its name) with the OpenEdition interface in order to receive OpenEdition events from the interface.
Corrective Action: No action is required.
Explanation: This information message is the normal start message issued during initialization of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.
OpenEdition support for the current Control-O or CMEM monitor is successfully installed. Control-O or CMEM will trigger rules based on OpenEdition events.
Corrective Action: No action is required.
Explanation: Control-O or CMEM tried to install OpenEdition support but found an incompatible PTF level.
Control-O or CMEM support for OpenEdition events is required for OS/390 version 2.4 and later. The PTF level in MVS is too low to install the OpenEdition interface.
The following system actions occur:
Corrective Action: Install IBM PTF for APAR OW36163, which enables Control-O or CMEM support for OpenEdition.
Explanation: The Control-O or CMEM subsystem could not register with the OpenEdition interface during initialization because Control-O or the CMEM monitor cannot acquire the OpenEdition interface lock, which is required for registration.
Initialization of the OpenEdition interface fails. Initialization of Control-O or the CMEM monitor continues. Control-O or the CMEM monitor will not be able to handle OpenEdition events, such as data set triggering based on FTP transmissions.
Corrective Action: Restart the current monitor. If the problem persists, call your INCONTROL administrator.
Explanation: During initialization of the OpenEdition interface, Control-O or CMEM could not load the OpenEdition support module because Control-O or CMEM monitor could not load the OpenEdition support module in its own private region.
The following system actions occur:
Corrective Action: Determine the cause of the failure using previous messages. Possible causes are:
Explanation: Control-O or CMEM tried to install the OpenEdition interface but an error occurred during initialization of the interface.
The following system actions occur:
Corrective Action: Look for previous messages which explain the cause of the failure. Call your INCONTROL administrator.
Explanation: This information message indicates that Control-O or the CMEM monitor tried to register with the OpenEdition interface but found the subsystem was already registered.
A possible cause is a previous uncompleted termination of CMEM or Control-O.
Initialization of the OpenEdition interface continues.
Corrective Action: No action is required.
Explanation: During Control-O startup, Control-O tried to activate OPENEDITION (UNIX for MVS) support. The attempt failed for one of the following reasons:
The preconditions for using Control-O/ OPENEDITION (UNIX for MVS) are:
The Control-O startup process completes but does not support OPENEDITION.
Corrective Action: If the system is earlier than OS/390 version 2.4, ignore this message. Otherwise, apply IBM APAR OW36163.
Explanation:The Control-O or CMEM subsystem could not register with the OpenEdition interface during initialization because Control-O or the CMEM monitor cannot locate its entry in the INCONTROL internal subsystems table.
The following system actions occur:
Corrective Action: Restart the current monitor. If the problem persists, call your INCONTROL administrator.
Explanation: During initialization of the OpenEdition interface, Control-O or CMEM could not load the OpenEdition support module because Control-O or CMEM monitor could not acquire storage in the Common Service Area (CSA) for the OpenEdition support module.
The following system actions occur:
Corrective Action: Make sure that the CSA has at least 8K of free storage, then restart the Control-O or CMEM monitor.
Explanation: During initialization of the OpenEdition interface, Control-O or CMEM could not load the OpenEdition support module because Control-O or CMEM monitor could not load the OpenEdition support module to the Common Service Area (CSA).
The following system actions occur:
Corrective Action: Use the contents of previous messages to determine the cause of the failure.
Explanation: This information message is the normal message issued during termination of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.
Control-O or the CMEM monitor detected an active OpenEdition interface environment and started its termination procedure.
Corrective Action: No action is required.
Explanation: This information message is the normal message generated during termination of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.
The current Control-O or CMEM subsystem removed itself from the OpenEdition interface in order to stop receiving OpenEdition events.
Corrective Action: No action is required.
Explanation: This information message is the normal message issued during termination of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.
Control-O or the CMEM monitor removed the OpenEdition support module from storage. This message is displayed only during termination of the last Control-O or the CMEM monitor in the system.
Corrective Action: No action is required.
Explanation: This information message is the normal message issued during termination of the CMEM monitor or Control-O when using OS/390 version 2.4 or later.
The OpenEdition interface for the current Control-O or CMEM monitor has been successfully removed.
Corrective Action: No action is required.
Explanation: Control-O or CMEM tried to remove OpenEdition support but encountered an error.
An error occurred during termination of the OpenEdition interface.
Termination of Control-O or the CMEM monitor continues. Warnings may be issued the next time Control-O or CMEM is activated.
Corrective Action: Look for previous messages which explain the cause of the failure. Verify successful initialization the next time Control-O or CMEM is activated.
Explanation: Control-O or the CMEM monitor could not find the OpenEdition interface module during termination.
During termination Control-O or CMEM detected an environment which supports the OpenEdition interface but could not find the OpenEdition support module which should have been installed during initialization.
Termination of Control-O or the CMEM monitor continues. Warnings may be issued the next time Control-O or CMEM is activated.
Corrective Action: Look for previous messages which explain the cause of the failure. Verify successful initialization the next time Control-O or CMEM is activated.
Explanation: Control-O or CMEM could not remove its subsystem name from the OpenEdition interface during termination.
If reason is SUBSYSTEM NOT FOUND, Control-O or CMEM could not find its subsystem name registered with the OpenEdition interface.
If reason is LOCK CANNOT BE OBTAINED, Control-O or the CMEM monitor could not get the OpenEdition interface lock it needs to remove its name.
Termination of Control-O or the CMEM monitor continues. Warnings may be issued the next time Control-O or CMEM is activated.
Corrective Action: Look for previous messages which explain the cause of the failure. Verify successful initialization the next time Control-O or CMEM is activated.
Explanation: The user issued the command F Control-O, REFRESH= parm to refresh the Control-O communication definitions, but the value of parm was invalid.
The valid value of the subparameter is XCF.
Refresh of the Control-O communication definition fails.
Corrective Action: Correct and reenter the command.
Explanation: An error was detected while attempting to refresh the XCF configuration map of Control-O, which defines the MVS image names with which Control-O can work.
Refresh of the Control-O communication definition by the REFRESH command fails.
Corrective Action: Examine the earlier accompanying messages in the Control-O JOBLOG or SYSLOG.
Explanation: An attempt was made to add a DO SMSCLASS or DO SMSMSG in an SMS rule that was not ON. DO SMSCLASS or DO SMSMSG can only be used in ON SMS rules.
The statement is not accepted.
Corrective Action: Delete the DO SMSCLASS or DO SMSMSG statement from the rule.
Explanation: An attempt was made to add a DO SMSCLASS or DO SMSMSG statement in an invalid location in the Control-O rule. DO SMSCLASS or DO SMSMSG can be used only in an ON SMS rule, and only before any WAIT.
The statement is not accepted.
Corrective Action: Delete the DO SMSCLASS or DO SMSMSG from the rule, or move it to a correct location.
Explanation: The Control-O communication function does not support the sharing of AutoEdit variables or TIMEOUT. Therefore, neither SHARELOC nor TIMEOUT can be used in rule definition when the system field is not null.
The action is rejected.
Corrective Action: Correct the DO KSL, DO TSO, or DO SHELL command.
Explanation: An attempt was made to add a DO SMSCLASS with an ID value of 0 or greater than 15. To be valid, an ID value must be from 1 through 15.
The value in the ID field is not accepted.
Corrective Action: Insert a valid ID value in the DO SMSCLASS, from 1 through 15.
Explanation: In a DO RESOURCE statement, an invalid sign was entered in the quantity change field.
Valid values for the quantity change subparameter are:
Corrective Action: Correct the value of the quantity change subparameter by entering a valid sign.
Explanation: In a DO COND statement, an invalid sign was entered in the condition option field.
Valid values for the condition option subparameter are:
Corrective Action: Correct the value of the CONDOPT subparameter by entering a valid sign.
Explanation: In an ON MVALARM statement, an invalid value was entered in the PRIORITY field.
Valid values for the PRIORITY subparameter are (in increasing order of severity):
Corrective Action: Correct the value of the PRIORITY subparameter by entering a valid value.
Explanation: In an ON MVALARM statement, an invalid value was entered in the TYPE field.
Valid values for the TYPE subparameter are:
Corrective Action: Correct the value of the TYPE subparameter by entering a valid value.
Explanation: In an ON RULE statement, an invalid value was entered in the RUNTSEC field.
Valid values for the RUNTSEC subparameter are:
For more information, see the description of the RUNTSEC subparameter in the Control-O User Guide.
Corrective Action: Correct the value of the RUNTSEC subparameter by entering a valid value.
Explanation: A DO statement (action) is not complete. At least one DO statement is required in the Rule Definition. The DO statement specifies actions to be performed after Message or Event Selection criteria are fulfilled.
For DO statement requirements, see the parameter descriptions in the Control-O User Guide or the Control-M for z/OS User Guide.
Corrective Action: Complete at least one DO statement.
Explanation: The field was left blank, but some data are required. The field is obligatory, and it does not have a default value. An entry must be made.
Corrective Action: Enter a value in the field.
Explanation: An invalid descriptor code was entered in the DESC field of the Rule Definition.
DESC is an optional parameter which specifies the message descriptor code. The DESC parameter value (if specified) must be a valid 1- 2 digit descriptor code (00 - 16).
Corrective Action: Enter a valid descriptor code in the DESC field or leave it blank.
Explanation: The ROUTE field of the Rule Definition has an invalid routing code. ROUTE is an optional parameter. The ROUTE parameter value, if specified, must be a valid 1- to 3-digit route code (000-255).
Corrective Action: Enter a valid routing code in the ROUTE field or leave it blank.
Explanation: An invalid range was specified in the COLS subparameter in the ON statement. When specifying a string using the S option in the ON statement, the search for this string may be limited to a specific column range by entering the range in the COLS subparameter.
The format is: COLS fromcol tocol, where fromcol or tocol may be any number from 1- 128, and the fromcol value may not be greater than the tocol value.
Corrective Action: Enter a valid range, or do not enter a search range.
Explanation: The specified fromcol range is greater than the specified tocol range in the COLS subparameter of the ON statement. When specifying a string using the S option in the ON statement, the search for this string may be limited to a specific column range by entering the range in the COLS sub-parameter.
The format is: COLS fromcol tocol, where fromcol or tocol may be any number from 1- 128, and the fromcol value may not be greater than the tocol value.
Corrective Action: Enter a valid search range or do not enter a search range.
Explanation: Only one value was provided for the APPEARED n TIMES IN m MINUTES parameter. While entries in the APPEARED n TIMES IN m MINUTES parameter are optional, values must be specified for both n and m, if this parameter is used.
Valid values are:
Corrective Action: Specify values for both n and m, or do not specify values for either.
Explanation: An invalid ON statement is specified in a Control-O rule. ON statements specify Message or Event criteria that must be met before Control-O triggers a rule.
For more information about ON statements, see the parameter descriptions in the Control-O User Guide.
The statement is ignored.
Corrective Action: Specify a valid ON statement.
Explanation: An invalid scheduling date was entered in the DATE subparameter of the FORCEJOB parameter. The DATE subparameter specifies the scheduling date for the job or jobs.
Valid date formats are:
Corrective Action: Enter a valid date.
Explanation: There is an invalid AutoEdit statement or expression in the DO SET statement. The DO SET statement is used to specify AutoEdit variables that are resolved at runtime.
See the Control-O User Guide for an explanation of the AutoEdit Facility.
Corrective Action: Enter a valid AutoEdit statement.
Explanation: An attempt was made to use the CAPS primary command in BROWSE mode. The CAPS primary command is not valid in BROWSE mode.
The command is not performed.
Corrective Action: No action is required.
Explanation: This information indicates a change in status of CAPS mode (ON or OFF) after entry of the CAPS primary command. The CAPS mode determines whether characters can be entered only in upper case, or also in lower case.
Corrective Action: No action is required.
Explanation: The rule definition contains an invalid evaluation expression of type, where type is IF or WHILE. Probable causes are:
The rule definition is not saved.
Corrective Action: Correct the invalid expression. If necessary, check the return code and reason code in the table in message WTO283E, to determine the reason for the failure.
Explanation:User entered CAPS OFF command, but the user is working at a DBCS terminal.
The command is ignored because DBCS terminals do not support lower case.
Corrective Action: No action is required.
Explanation:User entered a Control-O or CMEM rule and the control program found lower case characters.
CAPS OFF is forced to prevent upper casing by mistake. The user's online profile is not changed when saving and exiting the rule screen.
Corrective Action: No action is required.
Explanation: The ON or DO statement combinations are not valid. When defining or updating a Control-O rule, some statement combinations cannot be used together. In this case, the setting of one statement precludes the desired setting of the other statement. Possibly, the logical check picked up statement combinations that were defined, but not rejected in a previous release.
The rule is not saved.
Corrective Action: Correct the rule so that the statement combinations are valid.
Explanation: The AND/OR/NOT field in the ON statement is invalid. Inappropriate definition of AND, OR, or NOT fields connecting ON statements can create logic problems, such as a rule that is never triggered. Control-O checks each rule to ensure that the combination of ON statements and AND/OR/NOT connectors is logical.
For example,
It is possible that the logic problem was detected in a rule that was defined in a previous Control-O release.
The rule is not saved.
Corrective Action: Correct the ON statement and then save the rule.
Explanation: Values have been entered into two fields that are mutually exclusive, in that only one of the fields can have a value.
In this message, field1 and field2 are the identities of the two fields that are mutually exclusive.
Corrective Action: Enter a value for the field you require, and delete the value in the other field.
Explanation: A value must be set for the DDNAME and JOBNAME fields in ON SYSOUT. These fields may not be left blank or contain only the value * (Asterisk).
The rule is not saved.
Corrective Action: Correct the ON SYSOUT statement, and save the rule.
Explanation: The JOBNAME fields in ON SYSOUT may not be any of the following:
The rule is not saved.
Corrective Action: Correct the JOBNAME field in the ON SYSOUT statement, and then save the rule.
Explanation: An invalid value was found in the DDNAME parameter in the ON SYSOUT statement. The value in the DDNAME parameter in the ON SYSOUT may not be any of the following:
The rule is not saved.
Corrective Action: Correct the value of the DDNAME parameter in the ON SYSOUT statement, and then save the rule.
Explanation: The expression WAIT=YES was defined in a DO KSL, DO TSO, DO SHELL, or DO WAIT statement for a multi-line block that ends with an ENDMSG statement. WAIT mode actions are not allowed in multiline block processing that ended by ENDMSG.
The rule is not saved.
Corrective Action: Delete the expression WAIT=YES, then save the rule.
Explanation: Use of DO EXIT in this situation is not valid. DO EXIT can only be used in one of the following cases:
Rule definition cannot continue until the mistake is corrected.
Corrective Action: Correct the mistake, and continue defining the rule.
Explanation: Exit from the Control-O rule definition failed because a DO EXIT MESSAGE statement is not followed by an ENDMSG statement to indicate the end of the multi-line message processing block. A DO EXIT MESSAGE statement is valid only in a multi-line message processing block, which must be closed by an ENDMSG statement.
The rule cannot be saved.
Corrective Action: Do one of the following:
Explanation: An attempt was made to add a DO EXIT W (while) statement outside of a DO WHILE block. An EXIT W (while) statement is valid only in a DO WHILE block.
The EXIT W statement is rejected.
Corrective Action: Delete the EXIT W statement.
Explanation: The ACS CALL field in an ON SMS statement has an invalid value.
Valid values for the ACS CALL field are:
The value in the ACS CALL field is rejected.
Corrective Action: Correct the ACS CALL field in the ON SMS statement.
Explanation: The DSORG field in an ON SMS statement has an invalid value. Valid values are:
The value in the DSORG field is rejected.
Corrective Action: Correct the DSORG field in the ON SMS statement.
Explanation: The DS-TYPE field in an ON SMS statement has an invalid value. Valid values are:
The value in the DSORG field is not accepted.
Corrective Action: Correct the DS-TYPE field in the ON SMS statement.
Explanation: The ID field in a DO SMSMSG statement contains an invalid value. The value in such a field must be from 1 through 6.
The value is not accepted.
Corrective Action: Specify a valid value (from 1 through 6) in the ID field of the DO SMSMSG statement.
Explanation: The Shell script name contains UPPERCASE symbols.
Corrective Action: To prevent uppercasing by mistake, type CAPS OFF.
Parent Topic |