Previous Topic

Next Topic

Book Contents

Book Index

Messages IOA500 through IOA5xx

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

IOA555S OID=orderId INSUFFICIENT STORAGE. INCREASE THE REGION SIZE

Explanation: There was insufficient memory to perform a task.

The action that could not be performed accompanies this message. It may vary depending on the environment in which the message was issued.

Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter or exit one of the screens.

IOA5A0W mediaName - DEVICE num - CONNECT ERROR. STORAGE MACHINE: st.maName, SUBSYSTEM: smName, RC: rc

Explanation: The IOASMON monitor, migration job, or the CTVCLMIG utility failed to connect to the Filetek storage machine because the CONNECT function failed.

The probable cause for this failure is that the maximum number of connections to the storage machine was reached.

The variables in this message are:

If an IOASMON monitor fails, the monitor continually retries to connect until it succeeds, or until the device task is brought down. If a migration job or CTVCLMIG failed, it terminates with errors.

Corrective Action: Check the return code of the CONNECT function against the Filetek documentation, and correct the problem accordingly. This might require reducing the number of active device tasks to reduce the number of connections to the storage machine. If a migration job or CTVCLMIG failed, rerun the job or utility.

IOA5A1E mediaName - DEVICE num - ERROR ALLOCATING FILE fileName, RC: rc

Explanation: The migration job failed to allocate a file in the Filetek storage machine because the CREATOPEN function failed.

The variables in this message are:

The migration job skips the bad file, and processes the next file.

Corrective Action: Check the return code of the CREATEOPEN function against the Filetek documentation, and correct the problem accordingly.

IOA5A2E mediaName - DEVICE num - ERROR IN CLOSE. FILE fileName, RC: rc

Explanation: The migration job failed to close a file in the Filetek storage machine because the CLOSE function failed.

The variables in this message are:

The migration job skips the bad file, and processes the next file.

Corrective Action: Check the return code of the CLOSE function against the Filetek documentation, and correct the problem accordingly.

IOA5A3I mediaName - DEVICE num - EMSG msgText, RC: rc

Explanation: This information message is issued when a message is received from the Filetek storage machine subsystem.

The variables in this message are:

Corrective Action: No action is required.

IOA5A4E mediaName - DEVICE num - EMSG FAILED. RC: rc

Explanation: The IOASMON monitor, migration job, or the CTVCLMIG utility failed to receive a message from the Filetek storage machine because the EMSG function failed.

The variables in this message are:

The IOASMON monitor, migration job, or the CTVCLMIG utility continues processing.

Corrective Action: Check the return code of the EMSG function against the Filetek documentation, and correct the problem accordingly.

IOA5A5E mediaName - DEVICE num - ERROR IN DISCONNECT TO STORAGE MACHINE: st.ma.-name,SUB SYSTEM smName, RC: rc

Explanation: The IOASMON monitor, migration job, or the CTVCLMIG utility failed to disconnect from the Filetek storage machine because the DISCONNECT function failed.

The variables in this message are:

The connection remains active. In the case of a migration job, or the CTVCLMIG utility failure to disconnect, the job or utility terminate with errors.

Corrective Action: Check the return code of the DISCONNECT function against the Filetek documentation, and correct the problem accordingly. In the case of failure of a migration job or the CTVCLMIG utility, rerun the job or utility correspondingly.

IOA5AIE MEDIANM mediaName - DEVICE device_num - ERROR READING FILE fileName, RC: rc

Explanation: The migration job failed to read from a FileTek storage machine because the READ-RECORD function failed.

The variables in this message are:

The migration job skips the bad file, and processes the next file.

Corrective Action: Check the return code from the READ-RECORD function in the FileTek documentation. Correct the problem accordingly.

IOA5D0E mediaName - DEVICE deviceName - ERROR IN ACCESS TO OAM. RC = rc REASON CODE = rsn

Explanation: IBM macro OSREQ was unable to carry out ACCESS for the specified OAM.

The variables in this message are:

The system terminates any activity with OAM.

Corrective Action: Refer to IBM documentation. Consult either the OAM Programmer’s Reference or the DFSMSdfp Diagnosis Reference.

IOA5D1E mediaName - DEVICE deviceName - ERROR IN UNACCESS TO OAM. RC = rc REASON CODE = rsn

Explanation: IBM macro OSREQ was unable to carry out UNACCESS for the specified OAM.

The variables in this message are:

Corrective Action: Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material for an explanation of the return and reason codes.

IOA5D2W WARNINIG RECEIVED DURING READ OF 1ST BLOCK - collName RC=rc REASON CODE=rsn

Explanation: IBM macro OSREQ requested a RETRIEVE of the first object in collection collName. OSREQ returned a warning.

The variables in this message are:

Corrective Action: Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material for an explanation of the return and reason codes.

IOA5D3E ERROR DURING READ OF 1ST BLOCK - collName RC=rc REASON CODE=rsn

Explanation: IBM macro OSREQ was unable to carry out a RETRIEVE of the 1st object in the collection collName.

The variables in this message are:

Migration stops.

Corrective Action: Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material for an explanation of the return and reason codes.

IOA5D4W WARNING IN QUERY - objName collName RC=rc REASON CODE=rsn

Explanation: IBM macro OSREQ requested QUERY on object objName in collection collName and issued a warning.

The variables in this message are:

Corrective Action: Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material for an explanation of the return and reason codes.

IOA5D5E ERROR DURING QUERY - objNamecollName RC=rc REASON CODE=rsn

Explanation: IBM macro OSREQ was unable to QUERY object objName in collection collName.

The variables in this message are:

The system action depends on who issued the message, as follows:

Corrective Action: Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material for an explanation of the return and reason codes.

IOA5D6E INCOMPLETE OAM FILE - oamfil

Explanation: A migration job detected an incomplete OAM file. During most multistage migrations, OAM file oamfil migrates from OAM to another media. However, the migration job detected that oamfil was incomplete.

In this message, oamfil is the name of the incomplete OAM file.

The file does not migrate.

Corrective Action: Check oamfil in OAM, and attempt to determine the cause.

IOA5D7W WARNING IN DELETE - objName collName RC=rc REASON CODE= rsn

Explanation: IBM macro OSREQ requested DELETE for object objName in collection collName, and produced a warning return code.

The variables in this message are:

Corrective Action: Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material for an explanation of the return and reason codes.

IOA5D8E ERROR IN DELETE - objName collName RC=rc REASON CODE= rsn

Explanation: IBM macro OSREQ was unable to DELETE object objName in collection collName.

The variables in this message are:

The system terminates any activity associated with file collName. If this error occurs during migration, the collName is not migrated.

Corrective Action: Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material for an explanation of the return and reason codes.

IOA5D9E ERROR FROM DB2 SYNC . RC=rc REASON CODE=rsn

Explanation: DB2 SYNC service generated an error during processing, after updating OAM data. If the update of OAM was successful, DB2 performs a DB2 SYNC after each action that updates the OAM data. ABORT is performed if the update fails.

The variables in this message are:

Current activity stops.

Corrective Action: Refer to DB2 documentation for an explanation of the return code and the reason code in the message. Determine the status of files in OAM after the migration. Verify that all updates were correctly performed in OAM.

IOA5DBW WARNING IN STORE - objName collName RC=rc REASON CODE=rsn

Explanation: The message relays a warning message returned from IBM macro OSREQ. IBM macro OSREQ was called with a request to STORE object objName in collection collName.

The variables in this message are:

Corrective Action: See IBM documentation for an explanation of the return and reason codes in this message. Use OAM programmer reference material, or DFSMSdfp diagnosis reference material.

IOA5DCE ERROR IN STORE - objName collName RC=rc REASON CODE=rsn

Explanation: There was a request to STORE object objName in collection collName. However, IBM macro OSREQ returned an invalid return code.

The variables in this message are:

Migration for file collName halts. In the next migration run, when the migration program discovers that the collection was not completed, all migrated objects are deleted, and the migration for this file is retried.

Corrective Action: Refer to IBM documentation for an explanation of the return and reason codes in this message. Use OAM programmer reference material, or DFSMSdfp diagnosis reference material.

IOA5DDW WARNING IN RETRIEVE - objName collName RC = rc REASON CODE = rsn

Explanation: The user requested that IBM macro OSREQ RETRIEVE object objName in collection collName. A warning code was returned by the macro.

The variables in this message are:

Corrective Action: Refer to IBM documentation for an explanation of the return code and the reason code specified in this message. Use OAM programmer reference material, or DFSMSdfp diagnosis reference material.

IOA5DEE MEDIANM - DEVICE taskId - ERROR IN RETRIEVE - objName collName RC=rc REASON CODE = rsn

Explanation: IBM macro OSREQ was unable to RETRIEVE object objName in collection collName.

The variables in this message are:

The system action depends on who issued the message, as follows:

Corrective Action: Record the return code and reason code and refer to IBM documentation. Refer to OAM programmer reference material, or DFSMSdfp diagnosis reference material.

IOA5DFI MEDIANM DEVICE deviceName - DB2 MSG RECEIVED - db2msg

Explanation: This information message relays a message returned from DB2 while processing IBM macro OSREQ.

The variables in this message are:

Corrective Action: Refer to IBM documentation for an explanation of DB2 messages.

IOA5DGS OAM IS NOT ACTIVE IN SYSTEM

Explanation: IBM OAM software was not active. Control-V attempted to initiate a connection to OAM.

The system terminates the action attempted by Control-V.

Corrective Action: Activate OAM.

IOA5DJE DB2 TABLES CORRUPTED - COLLECTION MATCHED AN OLD OBJECT objName collName

Explanation: An IBM OAM utility attempted to store an object over a different object with the same name. During migration to OAM, an OAM utility detected an object with the same name but different content. OAM DB2 tables may have been deleted by the user, and objects in the deleted tables may be connected to new collections. Message MIG5CUE immediately follows this message.

The variables in this message are:

The system stops migration for objName collName. DB2 undoes migration actions performed for this collection. A LOCATE Failed Error message is issued for the OAM migrated file.

Corrective Action: Consult your DB2 administrator. Check and fix the DB2 tables.

IOA5E3I CLIP_ID=clipId

Explanation: This information message is issued for each Centera clip created during Control-V migration to the EMC Centera storage system.

The variable in this message is:

Corrective Action: No action is required.

IOA5E4E CENTERA INIT ERROR: RC=rc, REASON CODE=rsn

Explanation: Connection to EMC Centera cannot be established. This message is followed by message IOA5E9I, which issues the Centera pool value used for connection.

The variables in this message are:

IOA Archive Server skips the reading of data from Centera and continues processing with reading data from other media.

Corrective Action: Refer to EMC Centera documentation for a description of the received reason code.

Check the pool value printed in the accompanying MIG5E9I message. If the IP addresses are not correct, update them in parameters POOL1-POOL4 in the IOASPRM member.

Restart the IOA Archive Server after the reason for the problem is eliminated.

IOA5E6E CENTERA READ ERROR: RC=rc,REASON CODE=rsn,DSN=dsn,BLN=blk,L=len

Explanation: An error was detected while reading a block from the EMC Centera clip. This message is followed by message IOA5E31, which issues the problematic Centera clip name.

The variables in this message are:

The migrated dsn dataset is not read.

Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.

IOA5E8E CENTERA TERMINATE ERROR- RC=rc, REASON CODE= rsn

Explanation: An error was detected during termination of the EMC Centera device.

The variables in this message are:

The EMC Centera connection is not terminated.

Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.

IOA5E9I POOL=pool

Explanation: This information message follows message IOA5E4E.

In this message, pool represents the pool value specified in parameters POOL1-POOL4 in the IOASPRM member.

Corrective Action: No action is required.

Parent Topic

IOA messages