|
|
|
|
|
This group includes messages for the IOA (infrastructure) product.
Explanation: This information message indicates that the IOADCPY utility has started.
Corrective Action: No action is required.
Explanation: The IOADCPY utility was unable to open the sysprint file.
The IOADCPY utility terminates with a return code of 4.
Corrective Action: Check that the SYSPRINT DD statement exists in the IOADCPY procedure in the PROCLIB library, and that the sysprint file is correctly specified in it. Rerun the IOADCPY utility.
Explanation: The IOADCPY utility was unable to open the input file.
The IOADCPY utility terminates with a return code of 8.
Corrective Action: Check that the DAIN DD statement exists in the IOADCPY procedure in the PROCLIB library, and that it references the undamaged file. Rerun the IOADCPY utility.
Explanation: The file referenced by the DAIN DD statement was not an IOA Access Component file. The name of the file as it appears in the block of the file is not a valid name for an IOA Access Method file.
The IOADCPY utility terminates with a return code of 12.
Corrective Action: Correct the DAIN DD statement in the IOADCPY procedure in the PROCLIB library to reference a file that is the IOA Access Method file. Rerun the IOADCPY utility.
Explanation: The name of the file referenced by DAIN DD statement was too long.
The IOADCPY utility terminates with a return code of 16.
Corrective Action: Correct the file name referenced by the DAIN DD statement in the IOADCPY procedure in the PROCLIB library, and rerun the IOADCPY utility.
Explanation: The IOADCPY utility could not dynamically allocate a file. This message is followed by message IOAG06I that details the file name. The return code specified in the message is that returned by SVC 99.
The IOADCPY utility terminates with a return code of 20.
Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide for a description of the reason of return codes received. After correcting the problem, rerun the utility.
Explanation: This information message details the name of the file that the IOADCPY utility could not dynamically allocate. This message follows message IOAG05E informing of the dynamic allocation error.
Corrective Action: No action is required.
Explanation: The IOADCPY utility ended after detecting one or more errors. This message follows a message or messages that detail the errors that occurred.
Corrective Action: Check for previous messages and correct the problem accordingly. Rerun the IOADCPY utility.
Explanation: This information message indicates that the IOADCPY utility ended without errors.
Corrective Action: No action is required.
Explanation: The IOADCPY utility could not obtain sufficient storage to run.
The IOADCPY utility terminates with a return code of 28.
Corrective Action: Increase the REGION size for the IOADCPY utility and rerun it.
Explanation: The IOADCPY utility could not open the input file.
The IOADCPY utility terminates with a return code of 8.
Corrective Action: Check for messages in the sysout of the IOADCPY utility and in the system log, and correct accordingly. Rerun the IOADCPY utility.
Explanation: The IOADCPY utility discovered that the IOA Access Method file to be used to restore the damaged file was in use.
The IOADCPY utility waits until the file becomes free.
Corrective Action: No action is required.
Explanation: The unit name supplied as a parameter to the IOADCPY utility is invalid.
The dynamic allocation of the IOA Access Method file fails and the IOADCPY utility terminates with an error.
Corrective Action: Check the input parameters to the utility. See the IOAG05E message that follows this error message for the dynamic allocation return code. Correct the parameters accordingly, and rerun the utility.
Parent Topic |