Messages TPM100 through TPM1xx

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

TPM160E mediaName - INTERNAL ERROR IN VOLSER LIST FOR DSN dsn

Explanation: Media mediaName encountered an internal error while trying to access an extent of data set dsn.

The user request is not executed. Depending on internal error severity, one of the following actions occurs:

• Media mediaName terminates. The IOA Archive Server continues processing.
• Media mediaName abends with User Abend 0007. The IOA Archive Server terminates with User Abend 0006. The output includes a dump of the abend.

Corrective Action: Check the IOA Log file and system log for messages describing the error. Contact the system programmer for assistance, if needed. If the problem is not resolved, record the return code and contact BMC Customer Support.

TPM161S mediaName - INTERNAL ERROR ENCOUNTERED - RC=rc

Explanation: Media mediaName encountered an internal error.

The user request is not executed. Depending on internal error severity, one of the following actions occurs:

• Media mediaName terminates. The IOA Archive Server continues processing.
• Media mediaName abends with User Abend 0007. The IOA Archive Server terminates with User Abend 0006. The output includes a dump of the abend.

Corrective Action: Check the IOA Log file and system log for messages describing the error. Contact the system programmer for assistance, if needed. If the problem is not resolved, record the return code and contact BMC Customer Support.

TPM162E mediaName - DSN dsn IS CATALOGED ON MORE THAN 5 VOLUMES

Explanation: An attempt was made to access an extent of the dsn data set which spans more than five volumes.

The viewing of reports from a data set which migrated on more than five volumes is not supported.

The user request is not executed.

Corrective Action: No action is required.

TPM163E mediaName - DSN "dsn" IS SECOND FILE ON MULTI-VOLUME SET

Explanation: IOASMON detected a file that was created as a second file on the second volume of a multi-volume set.

An error during the migration process caused a file to be written as the second file on the second volume of a multi-volume set. This might cause a dead-lock while servicing the retrieval request. To avoid the possibility of a deadlock, the retrieval request is rejected.

The retrieval request is rejected.

Corrective Action: Unmigrate the report, re-decollate and migrate the report again.