Previous Topic

Next Topic

Book Contents

Book Index

Messages IOA900 through IOA9xx

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

IOA913S OPEN OF DDNAME "SYSPRINT" FAILED

Explanation: The opening of a print file failed.

Possible causes are:

The program stops executing.

Corrective Action: Correct the JCL and submit again.

IOA915S ERROR OPENING SYSPRINT

Explanation: An error was detected during an attempt to open the file referenced by the SYSPRINT DD statement.

The file referenced by the SYSPRINT DD statement is not opened.

Corrective Action: Check the system job log, and correct the problem accordingly. Rerun the job.

IOA946S ERROR OPENING SYSPRINT

Explanation: The IOADII utility detected an error when opening the file referenced by the SYSPRINT DD statement.

The file referenced by the SYSPRINT DD statement is not opened.

Corrective Action: Check the system job log, and correct the problem accordingly. Rerun the job.

IOA951S RELEASE OF LOG FILE NOT SUPPORTED BY THIS RELEASE OF IOA.

Explanation: Release of Log file is not supported by this release of IOA

This could be due to one of the following:

Access to the IOA Log is prevented. An “OPEN OF LOG FILE FAILED” message will appear.

Corrective Action: Correct the allocation of your Log file (the DALOG DD statement).

IOA952S OPEN OF IOA LOG FILE FAILED

Explanation: Open of IOA Log file failed (the DALOG DD statement). Possible causes are:

Termination of the requested function.

Corrective Action: Look on the computer log or job log SYSOUT for additional messages that clarify the reason for the failure. Then, correct the JCL for the job, or the allocations of the CLIST.

IOA954S IOA LOG FILE - WRITE ERROR

Explanation: I/O error while writing to IOA Log file. Possible causes are:

Corrective Action: Check the contents of the computer log for additional messages which may clarify the situation, or logon again.

IOA957S FILE ALLOCATED TO DDNAME "ddName" IS NOT YOUR IOA LOG

Explanation: The data set described by the specified DD statement is not the IOA Log file of this IOA installation. It is an IOA Log file, but it is of a different QNAME. It belongs to another IOA installation.

Corrective Action: Correct the JCL for the job or CLIST.

IOA958S FILE ALLOCATED TO DDNAME "ddname" IS NOT AN IOA LOG

Explanation: The data set described by the specified DD statement is not an IOA Log file.

Corrective Action: Correct the JCL for the job or CLIST.

IOA959S IOA LOG FILE IS FORMATTED. IOABLG PROBABLY ABENDED

Explanation: The IOABLG program, which formats the IOA Log file, probably abended.

Corrective Action: Check the IOA Log format job output to see why the IOABLG program abended. Delete the file and recreate it using the INCONTROL Installation and Customization Engine (ICE).

IOA95AE UNABLE TO SYNCRONIZE THE LOG FILE

Explanation: Internal synchronization of the Log file failed, probably because another process in the same address space has been holding the Log file for a long time. A record might be missing in the IOA Log file.

The Log operation fails.

Corrective Action: Take a dump of the failing address space. When the dump completes, stop and restart it to release the internal lock. Have your system programmer call your IOA representative for assistance.

IOA960S MISSING INPUT PARAMETERS

Explanation: No input parameters were specified for utility IOADUL.

The IOADUL utility ends with a return code of 32.

Corrective Action: Rerun the IOADUL utility using valid input parameters. See the IOADUL utility in the INCONTROL for z/OS Utilities Guide for valid parameters.

IOA963S FORMATTING IOA LOG - WRITE I/O ERROR

Explanation: An I/O error occurred while formatting the IOA Log file. This error may occur when there is incompatibility between the definition of the Log file in the Installation Parameters (IOAPARM) and the JCL SPACE and DCB parameters.

The utility stops executing with a condition code of 08.

Corrective Action: Correct either the JCL or the Installation Parameters.

IOA964I FORMATTING OF IOA LOG FILE STARTED

Explanation: This information message indicates that the IOA Log file format process has started.

Corrective Action: No action is required.

IOA965I FORMATTING OF IOA LOG FILE ENDED

Explanation: This information message indicates that the IOA Log file format process has terminated normally.

Corrective Action: No action is required.

IOA966S IOA LOG FILE WAS NOT BUILT

Explanation: Formatting of the IOA Log file failed.

Corrective Action: Look in the job log or SYSPRINT for error messages that describe the type of error.

IOA9A0I action OF IOA LOG STARTED

Explanation: This information message is a normal start message of the IOACPLOG utility. IOACPLOG is used to copy the contents of the IOA Log to another IOA Log file or to a sequential file. The actions COPYTOSEQ and COPYTOLOG are currently supported.

Corrective Action: No action is required.

IOA9A1I action OF IOA LOG ENDED

Explanation: This information message is a normal termination message of the IOACPLOG utility. IOACPLOG is used to copy the contents of the IOA Log to another IOA Log file or to a sequential file. The actions COPYTOSEQ and COPYTOLOG are currently supported.

Corrective Action: No action is required.

IOA9A2S action OF IOA LOG ENDED WITH ERRORS.

Explanation: The IOACPLOG utility failed to copy the IOA Log file. IOACPLOG is used to copy the contents of the IOA Log to another IOA Log file or to a sequential file. The actions COPYTOSEQ and COPYTOLOG are currently supported.

The IOACPLOG utility ended with a condition code of 08 or 12.

Corrective Action: Check the preceding error messages in the job log or in the SYSPRINT sysout, correct the problem, and rerun the job.

Parent Topic

IOA messages