DSNU294I csect-name - LARGEST COMPOSITE RECORD IS TOO BIG FOR REORG WITH SHRLEVEL CHANGE
Explanation
SHRLEVEL CHANGE was specified for a REORG utility job, and the table has a clustering index. However, the largest possible record in the table space, prefixed by the largest key, produces a composite record that is too large to be processed by the SORT component. If the largest possible composite record to be sorted exceeds 32760 bytes in length, which is the maximum record size for a BSAM data set, REORG cannot operate if SHRLEVEL CHANGE is specified.
System action
REORG does not execute.
User response
Execute REORG with SHRLEVEL NONE or REFERENCE and specify SORTDATA NO. If you must use SHRLEVEL CHANGE for the table space, try reducing the size of either the largest record or key field by redefining the table. In some cases, changing a field from LONG VARCHAR to VARCHAR with a specified maximum length might help.
Problem determination
This problem should only occur on a table space with a 32KB page size. Analyze the requirement for maximum data length in VARCHAR and LONG VARCHAR columns to see whether a shorter length can be specified.
Severity
8 (error)