PI93199: ABILITY TO SPECIFY UNLLDTBB IN SYSIN

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• It should be possible to specify the "LISTDEF behaviour for
  table selection" (available through the VUU081/ parmlib
  parameter) at the job level.
  
  PB51640 Z632
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of High Performance Unload                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * PI91711: A syntax error is reported by the INZI503E DDL      *
  * ANALYSING: SYNTAX ERROR AT POS(line, column) message when    *
  * attempting to unload the data from an image copy using the   *
  * DDLDDN feature. This can occur if the DDL provided for the   *
  * DDLDDN feature specifies a CREATE TABLE statement involving  *
  * either of the following clauses:                             *
  *          - IMPLICITLY HIDDEN                                 *
  *          - INLINE LENGTH integer                             *
  *          - GENERATED ALWAYS AS ( ...                         *
  *          - GENERATED AS ( ...                                *
  * PI91755: The request to unload the data from an image copy   *
  * or a set of image copies (COPYDDN option) stops with an      *
  * ABENDS513 if the following conditions are true:              *
  *          - one of the involved image copy is located on tape *
  *          - the data from the image copies must be sorted to  *
  * perform the unload operation, which occurs for either of the *
  * following situations:                                        *
  *            + the LAST_IC or the CHECK option is specified    *
  * and an inline image copy is involved                         *
  *            + the INLINE option is specified                  *
  *            + the COPYTOCOPY option is specified              *
  *            + the MERGE_IIC option is specified               *
  * PI91963: An INZU460I message is irrelevantly issued for an   *
  * unload statement that specifies DB2 FORCE. This message      *
  * actually only applies to an unload where the native mode     *
  * might be involved (i.e. when either DB2 NO or DB2 YES        *
  * applies).                                                    *
  * PI92007: When an unload from an image copy (COPYDDN option)  *
  * specifies the "ORIGINOBID integer" and the "AUTOTAG integer" *
  * options, the field generated for the AUTOTAG option does not *
  * contain the expected value (i.e. the external representation *
  * of the rank of the SELECT statement within the unload        *
  * statement) but the external representation of the OBID       *
  * specified by the ORIGINOBID option. If the unload statement  *
  * also request the LOAD controls cards be generated (LOADDDN   *
  * option), the WHEN clause generated in the LOAD statement is  *
  * always WHEN (1:integer) = X'0000'.                           *
  * PI92008: The LOAD controls cards generated for an unload of  *
  * a table having an encoding scheme different from EBCDIC that *
  * specifies the "AUTOTAG integer" and the LOADDDN options      *
  * specify an incorrect value for the WHEN clause.              *
  * PI92055: The enhancement for RFE83994 (PB44462) that avoids  *
  * the functional redundance of DB2 HPU BIF_COMPATIBILITY       *
  * (subparameter of ULOPTNS) and its DB2 counterpart BIF        *
  * COMPATIBILITY implies abehavior change for DB2 HPU users     *
  * that used to run DB2 HPU with inconsistent settings for BIF  *
  * COMPATIBILIY. For those users, a parameter should allow to   *
  * disable the enhancement done for RFE83994.                   *
  * PI93191: The CPU time and memory consumption of native mode  *
  * unloads involving LOB data has been decreased.               *
  * PI93192: The default SORTCLASS, i.e. *, is used instead of   *
  * the SORTCLASS specified in the Technical Parameters Options  *
  * block.                                                       *
  * PI93193: In DB2 version 10 and later versions, an ABENDU1132 *
  * with reason 8 occurs when attempting to unload a very big    *
  * LOB in native mode.                                          *
  *          A very big LOB is a LOB that requires more than 1   *
  * LOB MAP page in the LOB table space, i.e. which is greater   *
  * than                                                         *
  *          - 26 MB when the page size on LOB TS is 4K.         *
  *          - 52 MB when the page size on LOB TS is 4K.         *
  *          - 104 MB when the page size on LOB TS is 4K.        *
  *          - 208 MB when the page size on LOB TS is 4K.        *
  * PI93194: When the file provided for the DDLDDN feature       *
  * contains the clause "FOR UPDATE" in the free block (e.g.     *
  * PCTFREE 10 FOR UPDATE 10 ), HPU issues error messages such   *
  * as                                                           *
  *          INZI503E DDL ANALYSING: SYNTAX ERROR AT POS(52, 33) *
  *          INZU366I UTILITY RETURN CODE 8 (REASON CODE         *
  * 0x32a00b) and fails with a completion code of 8.             *
  * PI93195: An unload specifying the DDLDDN option can fail     *
  * with various errors among which:                             *
  *          - the following DDL analysis errors reported by the *
  * messages below:                                              *
  *               INZC004E INCOMPLETE OBJECT DEFINITION FOR      *
  * TABLESPACE dbname,tablespace PARTITIONNING INDEX MISSING     *
  *               INZI516E DDL ANALYSING: INVALID DDL            *
  * DEFINITION.                                                  *
  *          - incorrect encoding of the output data             *
  *          These errors can occur if the file provided         *
  * contains one of the following keywords sequences in the      *
  * CREATE TABLE statement:                                      *
  *               - APPEND YES                                   *
  *               - APPEND NO                                    *
  *               - LOGGED                                       *
  *               - NOT LOGGED                                   *
  *               - COMPRESS YES                                 *
  *               - COMPRESS NO                                  *
  *               - DSSIZE integer G                             *
  *               - BUFFERPOOL bpname                            *
  *               - MEMBER CLUSTER                               *
  *               - TRACKMOD YES                                 *
  *               - TRACKMOD NO                                  *
  *               - PAGENUM RELATIVE                             *
  *               - PAGENUM ABSOLUTE                             *
  * PI93198: If SELMSG SYSPRINT or PROCMSG SYSPRINT is specified *
  * in the unload command or in the parmlib, the INZX090 message *
  * (SELMSG case) or the INZX005 message (PROCMSG case) is       *
  * issued right after the preceding message, that is not        *
  * written on a new line, as in the examples below:             *
  *          With SELMSG SYSPRINT:                               *
  *          INZU282I   OUTPUT DDNAME=SYSREC1 10:26:26 INZX090   *
  * DDN SYSREC1  TS SYSTSDBA PART  1 : 1 RECORDS WRITTEN IN      *
  * 00:00:01, UNLOAD DONE.                                       *
  *          With PROCMSG SYSPRINT :                             *
  *          INZU282I   OUTPUT DDNAME=SYSREC1 10:44:44 INZX005   *
  * SYSTSDBA PARTITION NO. 1 IS BEEING READ                      *
  *          10:44:45 INZX009 SYSTSDBA PARTITION NO. 1 READ, 86  *
  * ROWS PROCESSED                                               *
  * PI93199: It should be possible to specify the "LISTDEF       *
  * behaviour for table selection" (available through the        *
  * VUU081/ parmlib parameter) at the job level.                 *
  * PI93731: Some intermittent and rare DB2 HPU jobs end in      *
  * ABENDS0C4 with the following traceback:                      *
  *    6     _inzzpiltWaitForOneTask                             *
  *                      +00000508  5036                         *
  *    7     _inzzpiltWaitForAllTasks                            *
  *                      +0000012A  5105                         *
  *    8     _inzzpiltUnload                                     *
  *                      +00000202  3326                         *
  *    9     _inzzpiltUnloadThread                               *
  *                      +0000018A  1902                         *
  *    10    oenclaveBootXplink                                  *
  *                      +00000100  879                          *
  *    11    CELQPCMM    +00000F80                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply the PTF for problem resolution                         *
  ****************************************************************
  

Problem conclusion

• Code has been changed to fix this problem
  

Temporary fix

• PI91711: Consider removing the clause if it does not affect the
  result
  PI92007: If all the SELECT statements are associated with a
  specific OBID (specified by the ORIGINOBID option), consider
  correcting the LOAD statement by replacing the WHEN (1:integer)
  = X'0000' by "WHEN (1:integer) = 'OBID' whene OBID is the value
  specified by the corresponding ORIGINOBID option. Do the change
  for every SELECT statement for which an ORIGINOBID is specified.
  PI92008: Consider correcting the WHEN clause of the control
  cards by replacing the value searched by the WHEN clause by the
  rank of the corresponding SELECT statement in the unload
  statement.
  PI93193: Run the unload in SQL mode.
  PI93194: Remove the FOR UPDATE clause that has no impact on the
  DB2 HPU processing.
  PI93195: Remove any of the keyword sequences listed above from
  from the CREATE TABLE statements in the DDLDDN file as this does
  not have any impact on the DB2 HPU output.
  

Comments

APAR Information

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

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

  UI53940

Modules/Macros

• INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R510 PSY UI53940

     UP18/02/21 P F802

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.