PI58803: LOGICAL UNLOAD WITH ORDER CLAUSE FAILS DURING THE SORT PHASE WITH ABENDU1017 OR ABENDU1009

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A logical unload with an ORDER clause fails during the sort
  phase, thus leading to ABENDU1017 or ABENDU1009, with a message
  meaning one of the records to be sorted is too short to match
  the SORT FIELDS specification such as
  ICE218A 2 112 BYTE VARIABLE RECORD IS SHORTER THAN 262 BYTE
  MINIMUM FOR
  or
  WER027A CONTROL FIELD BEYOND RECORD
  or other messages where the root cause of the failure is not
  This occurs when the following situation occurs:
      the table is stored in a table space in Reordered Row Format
  (RRF)
      the table has at least one variable column
      the INDESCAN feature is used, as shown by the message
  INZX101 index-name INDEX SCAN STARTED, which means that the
  ORDER clause sort-key matches the key of the clustering index of
  the table space
      one of the column of the key of the clustering index is
  located after a variable column in the table definition
      the INDEXSCAN feature does not retrieve all the records to
  be unloaded/sorted (this cannot be checked when the ABEND occurs
  but can be confirmed if the unload with the additional FORCEBRF
  dd is successful by checking the value of the IXSC from the "DB2
  HIGH PERFORMANCE UNLOAD - STATISTICS" table in the DB2 HPU
  SYSPRINTthat would be less than 100%)
  
  PB44677
  

Local fix

• add a FORCEBRF dd card to the DB2 HPU step (a DD DUMMY card is
  allowed) or add the INDEXSCAN NO option to the unload statement.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 High Performance Unload z/OS.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: A logical unload with an ORDER clause   *
  *                      fails during the sort phase, thus       *
  *                      leading to ABENDU1017 or ABENDU1009,    *
  *                      with a message meaning one of the       *
  *                      records to be sorted is too short to    *
  *                      match the SORT FIELDS specification     *
  *                      such as                                 *
  *                                                              *
  *                      ICE218A 2 112 BYTE VARIABLE RECORD IS   *
  *                       SHORTER THAN 262 BYTE MINIMUM FOR      *
  *                      or                                      *
  *                      WER027A CONTROL FIELD BEYOND RECORD     *
  *                      or other messages where the root cause  *
  *                      of the failure is not mentionned such   *
  *                      as                                      *
  *                      CNK526E DB2 SORT FOR Z/OS INTERNAL      *
  *                       ABEND - 1B.                            *
  *                      This occurs when the following          *
  *                      situation occurs:                       *
  *                       the table is stored in a table         *
  *                        space in Reordered Row Format (RRF)   *
  *                       the table has at least one variable    *
  *                        column                                *
  *                       the INDESCAN feature is used, as       *
  *                        shown by the message INZX101          *
  *                        index-name INDEX SCAN STARTED,        *
  *                        which means that the ORDER clause     *
  *                        sort-key matches the key of the       *
  *                        clustering index of the table space   *
  *                       one of the column of the key of the    *
  *                        clustering index is located after a   *
  *                        variable column in the table          *
  *                        definition                            *
  *                       the INDEXSCAN feature does not         *
  *                        retrieve all the records to be        *
  *                        unloaded/sorted (this cannot be       *
  *                        checked when the ABEND occurs but     *
  *                        can be confirmed if the unload with   *
  *                        the additional FORCEBRF dd is         *
  *                        successful by checking the value of   *
  *                        the IXSC from the "DB2 HIGH           *
  *                        PERFORMANCE UNLOAD - STATISTICS"      *
  *                        table in the DB2 HPU SYSPRINTthat     *
  *                        would be less than 100%)              *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  The inzpab module was changed.
  

Problem conclusion

• APPLY the PTF.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

•    INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R420 PSY UI37984

     UP16/05/24 P F605

• R430 PSY UI37985

     UP16/05/24 P F605

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.