UFO IOX5033 Error - Most Frequent Abend Codes

Products

• UFO

Issue/Introduction

The UFO IOX5033 error message is displayed for a number of possible IOX abend codes.

IOX5033 E JOB TERMINATED DUE TO ABEND; ABEND CODE = nnnn

 

Environment

Release:
Component: UFO

Resolution

The UFO Reference Manual Messages Release 3.2, section 2.2 IOX Abend Codes, lists the possible 4 digit IOX return codes.

The most frequently occurring abend codes are explained:

1902 The manual says:

Explanation: Data Space files mismatch on date

User Response: Get a dump of the transaction and contact... support.

The likely causes:

• Index and repository data sets are not valid IOX data spaces.
  
  
• Data space was not probably moved or copied via IOXMAINT utility BACKUP and RESTORE functions.
  
  

2422 The manual says:

Explanation: Physical IOX record length less than prefix size

User Response: Get a dump of the transaction and contact...support.

The likely cause:

• Corruption has occurred in a component member.
  Refer to TEC265210 Title: Removing a Corrupt IOX Component in Advantage CA-UFO.
  
  

2423 The manual says:

Explanation: Logical IOX record length less than minimum

User Response: Get a dump of the transaction and contact...support.

The likely cause:

• Corruption has occurred in a component member.
  Refer to TEC265210 Title: Removing a Corrupt IOX Component in UFO.
  
  

2425 The manual says:

Explanation: No more granule, but some size left (Gran # = zero)

User Response: Get a dump of the transaction and contact...support.

The likely cause:

• Corruption has occurred in a component member.
  Refer to TEC265210 Title: Removing a Corrupt IOX Component in UFO.
  
  

2428 The manual says:

Explanation: No length left, but still some granules in chain

User Response: Get a dump of the transaction and contact...support.

The likely cause:

• Corruption has occurred in a component member.
  Refer to TEC265210 Title: Removing a Corrupt IOX Component in UFO.
  
  
  

2429 The manual says:

Explanation: Key on record does not match key on index

User Response: Get a dump of the transaction and contact...support.

The likely cause:

• Corruption has occurred in a component member.
  Refer to TEC265210 Title: Removing a Corrupt IOX Component in UFO.
  
  

NOTE: When only 3 digits (nnn) are displayed in the IOX5033 message, the abend code reflects the occurring operating system abend code, such as B37, 878, etc, and not the IOX abend code.