Receiving error message LAE0095E executing CA Log Analyzer against a table with VARCHAR columns.

Document ID : KB000025196
Last Modified Date : 14/02/2018
Show Technical Document Details

Problem:

Executing a CA Log Analyzer for DB2 for z/OS (PLA) strategy including a table with LONG VARCHAR and/or URID Data
Inclusion Options that are very long and the following error messages are displayed:

LAE0095E TOTAL LENGTH OF SELECTED COLUMNS AND UNIT OF RECOVERY INFORMATION 
   EXCEEDS MAXIMUM SUPPORTED RECORD LENGTH OF 32756. 
LAE0008E SORT TERMINATING.  RETURN/ABEND CODE: 16

This is a calculation table to help determine the maximum space for writing the output load format file:

Fixed Block file               Variable Blocked file 
Max LRECL       32760          Max LRECL         32752 
Max DB2 row   - 32714           Max DB2 row    - 32714 
             --------                          ------- 
                   46                               38 
 
Creator          -  8                             -  8 
Table name       - 18                             - 18 
Stmt type        -  2                             -  2 
             --------                        --------- 
                   18                               10 

*Note: For a fixed record single table APPLY utility LOAD FORMAT file there can only be 18 extra bytes of optional URID data included if a 32K table is selected. For a multi-table APPLY utility LOAD FORMAT file there can only be 10 bytes of optional URID data included if a 32K table is selected. This limits the amount of extra URID data that can be included in a LOAD FORMAT file when the file contains tables with large row lengths.

No LOAD FORMAT file is produced for the table(s) in question.

 

Resolution:

The output file is larger than the MVS LRECL maximum due to the size of the included VARCHAR column(s) plus optional URID Data Inclusion Options. This is causing PLA to error with the LAE0095E TOTAL LENGTH OF SELECTED COLUMNS error message. To resolve the problem, truncate the VARCHAR fields or use DDL File Mapping to create an alternate table definition with a smaller length VARCHAR column to truncate the data.

*Note: When running log extract, you must specify the map name on the Process Log - Table Specifications panel which can be reached by specifying Other Source ==> Y on the Report Source Specifications panel for Source of DB2 Table Info.