Previous Topic

Next Topic

Book Contents

Book Index

Messages IOAP00 through IOAPxx

This group includes messages for the IOA (infrastructure) product.

IOAP01I - IOAP2AI Information messages issued by the IOADPT utility to display IOA Access Method file data component attributes as they are in the control record.

Explanation: These messages are issued by the IOADPT utility when FUNC=DB0 is specified.

Corrective Action: No action is required.

IOAP2BI ESTIMATED FREE SPACE num%

Explanation: This information message displays the estimated percentage of free space remaining in an IOA Access Method file.

Corrective Action: No action is required.

IOAP2EW SECONDARY SPACE IS NOT DEFINED FOR THE USER FILE dsn

Explanation: This warning message indicates that the secondary space is not defined for the user file dsn. The message is issued only when the IOADPT utility is run with the FUNC parameter set to CHKSPACE.

The utility continues processing, however, when the utility finishes it ends with a return code of 4.

Corrective Action: Use the following procedure to resolve this issue:

  1. Check the User file definitions in the DEFxxx member
  2. Specify secondary space in the DEFxxx member
  3. Run the IOADBF utility with the FUNC parameter set to CHANGE

IOAP2FW AUTOMATIC ALLOCATION OF NEW EXTENTS IS NOT DEFINED FOR THE USER FILE dsn

Explanation: This warning message indicates that the option to automatically extend the file is not specified for the user file dsn. The message is issued only when the IOADPT utility is run with the FUNC parameter set to CHKSPACE.

The utility continues processing, however, when the utility finishes it ends with a return code of 4.

Corrective Action: Use the following procedure to resolve this issue:

  1. Check the User file definitions in the DEFxxx member.
  2. Specify EXTEND=A in the DEFxxx member
  3. Run the IOADBF utility with the FUNC parameter set to CHANGE

IOAP2GW NUMBER OF EXTENTS FOR THE USER FILE dsn MORE THEN 50

Explanation: This warning message indicates that the number of extents for the specified user file dsn is more then 50. This warning is issued because a large number of extents can adversely impact performance when accessing the user file. The message is issued only when the IOADPT utility is run with the FUNC parameter set to CHKSPACE.

The utility continues processing, however, when the utility finishes it ends with a return code of 4.

Corrective Action: Check the User file definitions in the DEFxxx member. If the reason of for the large number of extents is a small secondary space definition, increase the space values in the DEFxxx member. Then perform a reorganization of the User file reformatting the files with the new SPACE parameters.

IOAP2IW FREE SPACE IN THE USER FILE dsn REACHED THE THRESHOLD CAPACITY

Explanation: This warning message indicates that the free space in the specified user file dsn has reached the threshold capacity and neither the secondary space or the automatically extend option were specified. This warning message is issued when one of the following conditions is true:

The message is issued only when the IOADPT utility is run with the FUNC parameter set to CHKSPACE.

Corrective Action: Check the User file definitions in the DEFxxx member. If the reason of for the large number of extents is a small secondary space definition, increase the space values in the DEFxxx member. Then perform a reorganization of the User file reformatting the files with the new SPACE parameters.

IOAP30I IOAPFSTC UTILITY STARTED

Explanation: This information message indicates that the IOAPFSTC utility, which prints IOA Application Server performance statistic reports, started.

Corrective Action: No action is required.

IOAP31E INVALID PARAMETER: parm

Explanation: The parm input parameter specified for the IOAPFSTC utility is not valid.

The utility stops with return code 16.

Corrective Action: Correct the invalid input parameter in the JCL and resubmit the job. For more information, see the IOAPFSTC utility in the INCONTROL for z/OS Utilities Guide.

IOAP32E REDUNDANT PARAMETER: parm

Explanation: The parm input parameter for IOAPFSTC utility is specified twice although it can only be specified once in this statement.

The utility stops with return code 16.

Corrective Action: Remove the redundant input parameter from the JCL and resubmit the job. For more information, see the IOAPFSTC utility in the INCONTROL for z/OS Utilities Guide.

IOAP33E INVALID LENGTH OF PARAMETER parm

Explanation: The length of the parm input parameter is not available for this parameter.

The utility stops with return code 16.

Corrective Action: Correct the invalid input parameter in the JCL and resubmit the job. For more information, see the IOAPFSTC utility in the INCONTROL for z/OS Utilities Guide.

IOAP34E REQUIRED PARAMETER parm IS NOT SPECIFIED

Explanation: The obligatory parm input parameter is not specified in the input stream for the IOAPFSTC utility.

The utility stops with return code 16.

Corrective Action: Correct the input parameter in the JCL and resubmit the job. For more information, see the IOAPFSTC utility in the INCONTROL for z/OS Utilities Guide.

IOAP35E INCORRECT COMBINATION OF DATEFROM AND DATETO VALUES

Explanation: The end date specified in the parameter DATETO is less than the beginning date specified in the parameter DATEFROM.

The utility stops with return code 16.

Corrective Action: Correct the input parameter in the JCL and resubmit the job. For more information, see the IOAPFSTC utility in the INCONTROL for z/OS Utilities Guide.

IOAP36W PARAMETER parm IS IGNORED FOR FUNCTION=CLEAN

Explanation: This warning message is issued when the parm parameter is specified for FUNCTION=CLEAN in the IOAPFSTC utility input parameters. No additional parameters are processed for FUNCTION=CLEAN. The parm parameter is ignored.

Corrective Action: Check the input parameters specified for the utility. Correct the parameters and resubmit the job if it is necessary. For more information, see the IOAPFSTC utility in the INCONTROL for z/OS Utilities Guide.

IOAP3AW NO PERFORMANCE STATISTIC RECORDS IN PERMANENT USER FILE

Explanation: The IOAPFSTC utility has not found any IOA Application Server performance statistic records in the Permanent User File. This can occur if the statistic collecting is not activated at the site (optional wish WIN102 is set to APPLY=NO).

Corrective Action: If necessary, apply the optional wish WIN102.

IOAP3BI nnnnn PERFORMANCE STATISTIC RECORDS HAVE BEEN READ

Explanation: This information message indicates how many IOA Application Server performance statistic records were read from the Permanent User File during the IOAPFTSC utility run.

Corrective Action: No action is required.

IOAP3CI nnnnn PERFORMANCE STATISTIC RECORDS HAVE BEEN SELECTED

Explanation: This information message indicates how many IOA Application Server performance statistic records have been selected according to selection parameters specified for the utility IOAPFTSC.

Corrective Action: No action is required.

IOAP3DI nnnnn PERFORMANCE STATISTIC RECORDS HAVE BEEN DELETED

Explanation: This information message indicates how many old IOA Application Server performance statistic records have been have been deleted from the Permanent User File during the IOAPFTSC utility run with FUNCTION=CLEAN.

Corrective Action: No action is required.

IOAP3EI IOAPFSTC UTILITY ENDED SUCCESSFULLY

Explanation: This information message indicates the utility IOAPFTSC ended successfully.

Corrective Action: No action is required.

Parent Topic

IOA messages