|
|
|
|
|
his group includes messages for the IOA (infrastructure) product.
Explanation: In the IOA Variables Facility Entry screen (Screen IV), the MODE field contains an invalid value.
The only valid values for the MODE field are:
Corrective Action: Type a valid value in the MODE field.
Explanation: In the IOA Variables Facility Entry screen (Screen IV), the DATABASE field contains a name, but no database nor pool with that name exists.
Corrective Action: Either correct the name in the DATABASE field, or select a database or pool from the list.
Explanation: The user tried to insert a new variable database in the List of Databases - IOA Database Facility screen (Screen IV), and typed a name for the new database in the New Database window, but that database name already exists.
Corrective Action: Type a different new database name.
Explanation: An attempt was made to access a variable database, using the IOA Variables Facility Entry screen (Screen IV), but that database is already in use by another user.
Corrective Action: Try again later.
Explanation: In the New Database Window of the List of Databases - IOA Database Facility screen (Screen IV), one of the following occurred:
The NUMBER OF ROWS field is used to determine the amount of storage space allocated for the variable database. The number inserted in this field must be greater than 1.
Corrective Action: Correct the number in the NUMBER OF ROWS field.
Explanation: An attempt was made to update a column in an existing variable database by typing U (Update) or D (Delete) in the OPT field beside a column name. However, the column name was not found in the database.
Corrective Action: Contact BMC Customer Support.
Explanation: An attempt was made to define a new column in an existing variable database. However, a column with the same values for COLUMN and NUMBER already exists.
Corrective Action: Specify new values for COLUMN and NUMBER.
Explanation: An attempt was made to insert a row into a variable database, but no row number is available at the location where the new row was to be inserted.
Rows in a variable database are originally numbered in thousands. Rows inserted later are assigned numbers in the gaps. For more information on how row numbers are assigned in a variable database, see the Control-O User Guide.
Corrective Action: Renumber the existing rows in the variable database, as follows:
For more information about the IOADUL and IOADLD utilities, see the INCONTROL for z/OS Utilities Guide.
Explanation: An attempt has been made to view the variables in a pool, but the pool does not contain any rows. Such a pool cannot be viewed.
Corrective Action: No action is required.
Explanation: While trying to view the IOAVAR variable database or pool, an invalid variable name was specified.
Corrective Action: Specify a valid variable name.
Explanation: The user is not authorized to perform the operation that was attempted.
Corrective Action: If you consider that you ought to have authority to perform an operation of this type, contact your INCONTROL administrator.
Explanation:An attempt was made to add a new variable into a Variable database by the I or R option in the Variable Database Display screen but the data base is full.
The action is aborted.
Corrective Action: Increase number of rows in the Variable database. It can be done by updating number of rows (For more information, see the INCONTROL for z/OS Administrator Guide, Chapter 2). Another option is to reformat the data base with bigger space parameters. (For more information, see the INCONTROL for z/OS Installation Guide: Installing, Step 7 - Set Global Variables database, and the INCONTROL for z/OS Upgrade Guide, Step 40)
Explanation: An attempt was done to specify value bigger than 65535 for the NUMBER OF ROWS parameter in the option U in the Database List screen.
The action is aborted.
Corrective Action: Specify a valid value and press ENTER to save the database parameters or specify N for the UPDATE field or press the RESET key (PF04) to close the window without saving the database parameters.
Explanation: An attempt was made to enter the Pools List or to view a pool, but the Control-O or CMEM monitor is not active.
To use this function, the Control-O or CMEM monitor must be active.
The request is rejected.
Corrective Action: Start the Control-O or CMEM monitor.
Explanation: An attempt was made to delete a column from a variable database, but the column contains variables.
Corrective Action: Delete all variables from the column, then try again to delete the column.
Explanation: The user attempted to gain access to a variable database or pool, but failed.
Corrective Action: Note the values of rc and func and contact BMC Customer Support.
Explanation: An attempt was made to view the variables in a variable database or pool. However, the database or pool does not contain any columns. Such a database or pool cannot be viewed.
Corrective Action: No action is required.
Explanation: This information message indicates that the IOAGLV utility, which handles IOA global variables, started.
Corrective Action: No action is required.
Explanation: This information message indicates how many IOA Global Variables are read from the pool during the IOAGLV utility run.
Corrective Action: No action is required.
Explanation: An attempt was made to submit the IOAGLV utility but the Control-O or CMEM monitor is not active. The Control-O or CMEM monitor must be active to use this utility.
Corrective Action: Start the Control-O or CMEM monitor, and then resubmit the utility.
Explanation: The IOAGLV utility attempted to access IOA Global Variables from the IOAVAR pool but the access failed.
The utility stops with RC=8.
Corrective Action: Check the return code (rc) and the reason code (rsn). The return and reason codes are described in the tables attached to the API575E message description. Correct the problem and resubmit the utility.
Explanation: The func function cannot be specified for the IOAGLV utility input parameters. The following functions can be specified:
The utility stops with RC=16.
Corrective Action: Correct the input parameters in the JCL and resubmit the job. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.
Explanation: The parm input parameter specified for the IOAGLV utility is not valid.
The utility stops with RC=16.
Corrective Action: Correct the invalid input parameters in the JCL and resubmit the job. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.
Explanation: The mandatory parm input parameter is not specified in the input stream for the IOAGLV utility.
The utility stops with RC=16.
Corrective Action: Correct the input parameters in the JCL and resubmit the job. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.
Explanation: No variables matching the specified path or path prefix were found in the IOA Global Variables pool.
The utility stops with RC=4.
Corrective Action: Check the input parameters in the JCL. Correct the input parameters in the JCL, if necessary, and resubmit the job. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.
Explanation: The length of the parm input parameter exceeds the maximum allowable length for this parameter.
The utility stops with RC=16.
Corrective Action: Correct the invalid input parameters in the JCL and resubmit the job. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.
Explanation: The parm input parameter for the IOAGLV utility is specified twice although it can be specified only once in this statement.
The utility stops with RC=16.
Corrective Action: Remove the redundant input parameters in the JCL and resubmit the job. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.
Explanation: An incorrect line was read from the input dataset, which was specified by the FROM parameter for the IOAGLV utility processing the LOAD function. This warning message is followed by the incorrect line itself.
The incorrect line is skipped and the utility continues processing other lines from the dataset. The utility ends with RC=4 if at least one incorrect line was detected in the dataset.
Corrective Action: Check the input dataset. Fix it and, if necessary, resubmit the utility. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.
Explanation: This information message indicates that the IOAGLV utility added a variable to the IOA Global Variables pool. The variable itself is printed in the next line using the following format: varname=value.
Corrective Action: No action is required.
Explanation: This information message indicates that the IOAGLV utility added a variable to the IOA Global Variables pool. The variable itself is printed in the next line using the following format: varname=value.
Corrective Action: No action is required.
Explanation: This information message indicates how many IOA Global Variables, matching the specified path, are selected during the IOAGLV utility run.
Corrective Action: No action is required.
Explanation: This information message indicates how many IOA Global Paths, matching the specified prefix, are selected during the IOAGLV utility run.
Corrective Action: No action is required.
Explanation: This information message indicates how many variables are added to the IOA Global Variables pool during the IOAGLV utility run.
Corrective Action: No action is required.
Explanation: This information message indicates how many variables are deleted from the IOA Global Variables pool during the IOAGLV utility run.
Corrective Action: No action is required.
Explanation: This information message indicates how many variables are updated in the IOA Global Variables pool during the IOAGLV utility run.
Corrective Action: No action is required.
Explanation: This information message indicates that the IOAGLV utility completed successfully.
Corrective Action: No action is required.
Explanation: Dynamic Allocation of the input dataset (dsname), specified in the FROM parameter for the IOAGLV utility with function LOAD, failed.
The utility stops with RC=8.
For explanations of the return code (rc) and reason code (rsn) displayed as part of this message, see the MVS Programming: Authorized Assembler Services Guide (IBM manual).
Corrective Action: Examine the return and reason codes, take the appropriate corrective actions, and resubmit the utility.
Explanation: The IOAGLV utility, using either the LOAD or SETVAR functions, attempted to add a variable to the IOA Global Variables pool, exceeding the maximum number of variables in the IOAVAR database.
The utility writes from the pool to the database only the variables in the pool that were added or updated before exceeding the maximum limit, and then stops with RC=8.
Corrective Action: Do the following:
Explanation: Multiple specifications of the following functions, or combinations of them are invalid in IOAGLV:
(Only the SETVAR function can be specified multiple times, other functions must be specified singularly.)
Corrective Action: Correct the input parameters in the JCL and resubmit the job. For more information, see the IOAGLV utility in the INCONTROL for z/OS Utilities Guide.
Explanation: No function was specified.
Corrective Action: Correct the input parameters in the JCL and resubmit the job.
Parent Topic |