This group includes messages for the IOA (infrastructure) product.
Explanation: An invalid parameter was passed to IOAZAP on the EXEC statement. The PARM parameter in the JCL EXEC statement was manually modified incorrectly.
The program stops execution with a condition code of 08. All the zaps that follow will be bypassed.
Corrective Action: Restore the original JCL job stream as follows:
Note:
You may run the JCL job stream as often as necessary. If a zap is already applied, it is bypassed.
Explanation: This information message is the normal start message produced by the IOA automatic zap application program.
Corrective Action: No action is required.
Explanation: This information message is the normal termination message produced by the IOA automatic zap application program.
Corrective Action: No action is required.
Explanation: The automatic zap application program failed to open the ddName DD statement. Possible causes are:
The program stops execution with a condition code of 08.
Corrective Action: The JCL was probably modified incorrectly. Restore the original JCL job stream, as follows:
Note:
You may run the JCL job stream as often as necessary. If a zap is already applied, it is bypassed.
Explanation: The AMASPZAP utility reported that an error occurred in the zap.
The program stops execution with a condition code of 08. All zaps that follow are bypassed.
Corrective Action: Check the report produced by the AMASPZAP utility to determine the cause of the problem. The zap was probably modified incorrectly. Restore the original JCL job stream, as follows:
Note:
You may run the JCL job stream as often as necessary. If a zap is already applied, it is bypassed.
If the problem is not due to a user modification of the zap, contact BMC Customer Support for assistance. Your representative will need the report produced by the AMASPZAP utility to resolve the problem.
Explanation: The automatic zap application program found that statement number lineNum in JCL step stepName is not valid. The problem is caused by an incorrect manual modification of the zap.
This message is followed by message IOA015S, which displays the statement in error in the damaged JCL job stream.
The program stops execution with a condition code of 08. All zaps that follow will be bypassed.
Corrective Action: Restore the original JCL job stream as follows:
Note:
You may run the JCL job stream as often as necessary. If a zap is already applied, it is bypassed.
Explanation: The automatic zap application program found that statement number lineNum in JCL step stepName is not valid. The problem is caused by incorrect manual modification of the zap.
This message is followed by message IOA015S, which displays the statement in error in the damaged JCL job stream.
The program stops execution with a condition code of 08. All the zaps that follow will be bypassed.
Corrective Action: Restore the original JCL job stream, as follows:
Note:
You may run the JCL job stream as often as necessary. If a zap is already applied, it is bypassed.
Explanation: Too many statements were added to the zap. Message IOA013I can be used to determine which zap caused the problem.
The program stops execution with a condition code of 08. All zaps that follow will be bypassed.
Corrective Action: Restore the original JCL job stream, as follows:
Note:
You may run the JCL job stream as often as necessary. If a zap is already applied, it is bypassed.
Explanation: This information message indicates that the zap was previously applied, and is being bypassed by the IOA automatic zap application program. This message is preceded by message IOA013I, which can be used to determine which zap was bypassed.
The processing of the rest of the zaps continues.
Corrective Action: No action is required.
Explanation: An attempt to relink a module during maintenance failed at the step indicated in the message.
The job stops processing at the failed step. The cause of the problem is indicated in the job output.
Corrective Action: Check the job output for the cause of the problem, and correct accordingly; then rerun the job. If you cannot correct the problem, notify BMC Customer Support.
Explanation: This information message indicates that the Zap desc was successfully applied.
The processing of the rest of the zaps continues.
Corrective Action: No action is required.
Explanation: This information message indicates that the IOA automatic zap application program, which is executing at step stepName, started to process the zap.
Corrective Action: No action is required.
Explanation: This information message indicates that the IOA automatic zap application program, which is executing at the stepName step, finished successfully.
The processing of the rest of the zaps continues.
Corrective Action: No action is required.
Explanation: Incorrect manual modification of a zap.
In this message, stmt is the statement that was incorrectly modified.
The IOA automatic zap application program ends with errors.
Corrective Action: Refer to previous messages, which describe the type of error.
Explanation: This information message indicates that one of the IOA databases was formatted. The format procedure writes an audit trail message to the IOA maintenance log.
Corrective Action: No action is required.
Explanation: This information message indicates that the IOAZAP utility successfully relinked a module. Occasionally, it is necessary to relink a module for maintenance purposes.
Corrective Action: No action is required.
Explanation: This message indicates that the zap is not required by this installation. IOA maintenance can support various configurations, including enhancement tapes. For this reason, not all zaps supplied are required by your installation.
Corrective Action: No action is required.
Explanation: This error message indicates that IOAZAP maintenance step stepName failed to complete. Possible causes are:
Corrective Action: If possible, correct the error and rerun the step. Otherwise, contact BMC Customer Support.
Explanation: An internal error occurred in CTMAPI.
The following return codes are possible:
Return Code |
Meaning |
---|---|
0 |
Load-Index API ended successfully. |
4 |
Load-Index API ended with warning. |
8 |
Load-Index API ended with error. |
12 |
Load-Index API ended with fatal error. |
Corrective Action: The following table provides troubleshooting guidelines for various possible reason codes. For any other reason code, contact BMC Support.
Reason Code |
Issue |
Corrective Action |
---|---|---|
24 |
Cannot allocate the WLI file. |
Check if the WLI file exists. |
28 |
The Workload Policy does not exist in the WLI file. |
Fix the Workload Policy name and try again. |
32 |
Insufficient storage space; could not allocate memory. |
Add more storage space. |
36 |
Failed to open the WLI file. |
Contact BMC Support. |
48 |
Failed to close the WLI file. |
Contact BMC Support. |
60 |
Failed to read the WLI file. |
Contact BMC Support. |
64 |
Failed to write the WLI file. |
Contact BMC Support. |
96 |
WLI file has invalid format. |
Check the WLI file and try again. |
100 |
WLI file header is invalid. |
Check the WLI file and try again. |
Explanation: Loading of the modName module failed.
Possible causes are:
Execution might stop.
Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.
Explanation: This information message indicates that the CTMHCOP utility successfully created a new History Jobs file from the old one.
Corrective Action: No action is required.
Parent Topic |