PH00917: POTENTIAL AND INTERMITTENT HANGING OF ANY UNLOAD JOB WAIT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• (HPU 5.1 only) When some concurrent internal tasks are run with
  a specific timing, any unload job can hang (WAIT).
  
  PB53621
  

Local fix

• none but a new run of the unload might be successful
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of High Performance Unload                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * PI99487:                                                     *
  * In case of an abnormal end of the HPU job (such as an abend  *
  * or job cancellation), the object                             *
  * involved in the unload can remain in the RO DB2 restrictive  *
  * state if the parmlib parameter Technique                     *
  * to lock the unloaded tablespace (VUU074/ULLOCKTE) is set to  *
  * START_RO and LOCK YES applies to the                         *
  * job.                                                         *
  *                                                              *
  * PH00452:                                                     *
  * The data is unloaded from the most recent image copy instead *
  * of from an older image copy as                               *
  * specified by a COPYDDN -n option with n greater than 1.      *
  * This occurs if the COPYDDN -n option does not specify any of *
  * the GLOBAL or PARTITIONED suboption and                      *
  * VUU076/ULICTYPE specifies either ANYTYPE or                  *
  * ANYTYPE_CONSISTENT                                           *
  *                                                              *
  * PH00455, PH00725:                                            *
  * During a logical unload specifying an ORDER clause and run   *
  * in native mode, an ABENDS0C4 occurs or                       *
  * the job enters an endless loop.                              *
  * This issue can occur if:                                     *
  * - the index scan feature is in action                        *
  * - the index used by the index scan feature contains          *
  * duplicate keys that are located by links                     *
  * Even if the above mentioned conditions are fulfilled, the    *
  * issue might not occur as the effect of the                   *
  * error depends on the content of the memory at run time which *
  * is not predicitble.                                          *
  *                                                              *
  * PH00823:                                                     *
  * When the LOADDDN option is specified and the target table    *
  * name cannot be determined, not fully                         *
  * compliant LOAD control cards are generated where the INTO    *
  * TABLE clause specifies a table name to be                    *
  * changed before use. This situation is reported by one of the *
  * INZU211I/INZU211W/INZU211E messages.                         *
  * In DB2 HPU versions 4.2, the unknown table name in the INTO  *
  * CLAUSE was replaced by                                       *
  * "????????.????????". From DB2 HPU version 4.3 the unknown    *
  * table name is replaced by the                                *
  * "????????.???????? " substitution string which contains an   *
  * extra blank. As a consequence, the                           *
  * required replacement to be done before using the LOAD        *
  * control cards unexpectedly changes as well                   *
  * which can cause failures of the automated post-processing of *
  * the LOAD control cards.                                      *
  *                                                              *
  * PH00866:                                                     *
  * During a logical unload run in native mode, error messages   *
  * with error code of 227 as follows:                           *
  * 227 * EXPRESSION EVALUATION ERROR * ddname * COLnnn          *
  * are issued and the unload completes with a completion code   *
  * of 8.                                                        *
  * This occurs if the SELECT statement contains non-trivial SQL *
  * expressions which processing requires                        *
  * more than 4 kB.                                              *
  *                                                              *
  * PH00917:                                                     *
  * When some concurrent internal tasks are run with a specific  *
  * timing, any unload job can hang.                             *
  *                                                              *
  * PH01209:                                                     *
  * The number of records to be sorted for an unload from an     *
  * image copy (COPYDDN option) with an ORDER                    *
  * clause is overestimated which causes a useless allocation of *
  * memory or storage ressources and may                         *
  * lead the sort and subsequently the unload to fail.           *
  * This can occur if the following conditions are fulfilled :   *
  * - the target tablespace (specified through the UNLOAD        *
  * statement) involved in the unload is a                       *
  * partition-by-growth table space                              *
  * - the number of partitions of the target table space is much *
  * lower than the maximum number of                             *
  * partitions defined via its MAXPARTITION attribute            *
  * - the more recently created partition contains a significant *
  * number of rows                                               *
  *                                                              *
  * PH01210:                                                     *
  * Fix1 - The data unloaded for an Unload Plus unload           *
  * specifying FORMAT CSV NULLSTRING both at the                 *
  * UNLOAD and the SELECT level contains incorrect null          *
  * indicators.                                                  *
  * Instead of being unload as empty fields, the NULL values are *
  * unloaded with the string set by                              *
  * NULLCHAR in the unload command or by the                     *
  * U_NULLCHAR(string_value) subparameter of the VUU030/ULOPTNS  *
  *                                                              *
  * parmlib parameter.                                           *
  * Fix2 - An unload from the image copies referenced in the DB2 *
  * catalog (COPYDDN LAST_IC or COPYDDN -n                       *
  * option) terminates with a return code 8 after a message      *
  * reported an allocation error as follows has                  *
  * been issued :                                                *
  *                                                              *
  * IEC130I IC00 DD STATEMENT MISSING                            *
  *  INZI800E ERROR ACCESSING TO A DATASET. ACTION: OPEN RC: 0x8 *
  * REASON: 0x0                                                  *
  *  DDN: IC00 DSN:                                              *
  *                                                              *
  * This occurs when the following conditions are fulfilled :    *
  * - the involved table space is a partition-by-growth          *
  * tablespace                                                   *
  * - the image copies for the table space that are referenced   *
  * in the SYSIBM.SYSCOPY table are image                        *
  * copies at the partition level                                *
  * - there is no referenced image copy for at least one         *
  * partition of the object (eg, for a newly                     *
  * created partition that has not been copied yet).             *
  * Fix3 - An ABENDS0C4 occurs during an unload requesting       *
  * graphic/vargraphic data to be unloaded into                  *
  * another data type (including the same data type but with a   *
  * different length) with the DELIMITED                         *
  * format. This occurs only if the data type conversion implies *
  * a data loss and if the CHARACTER_LOSS                        *
  * feature is set to WARNING or REJECT.                         *
  * The ABENDS0C4 symptom dump is as follows:                    *
  *                                                              *
  * IEA995I SYMPTOM DUMP OUTPUT 147                              *
  * SYSTEM COMPLETION CODE=0C4 REASON CODE=00000011              *
  * TIME=08.44.44 SEQ=21219 CPU=0000 ASID=0029                   *
  * PSW AT TIME OF ERROR 077D2001 9FFEAAD6 ILC 6 INTC 11         *
  * ACTIVE LOAD MODULE ADDRESS=1F8DC000 OFFSET=0070EAD6          *
  * NAME=INZUTILK                                                *
  * DATA AT PSW 1FFEAAD0 - E3E0D098 0024E3F0 B0000090            *
  * AR/GR 0: 008C2978/00000000 1: 00000000/20D7D098              *
  * 2: 00000000/20D7BDE8 3: 00000000/1FFEABF0                    *
  * 4: 00000000/20C656B0 5: 00000000/2002C9A8                    *
  * 6: 20C656B0/1FFEAE70 7: E9D3D6C7/20C76050                    *
  * 8: 00000000/1FFEBA38 9: 00000000/00000040                    *
  * A: 00000000/00000022 B: 00000000/20C96000                    *
  * C: 00000000/00000040 D: 00000000/20D7D000                    *
  * E: 00000000/20C76090 F: 01000002/00006904                    *
  * END OF SYMPTOM DUMP                                          *
  * Fix4 - An ABENDS0C4 can occur during a logical unloading     *
  * data in INTERNAL format if it specifies                      *
  * several output dataset for a single unload by specifying     *
  * several ddnames via the OUTDDN option (e,g,                  *
  * OUTDDN(FRSTOUT,SCNDOUT))                                     *
  * Fix5 - After the maintenance for PH00495, the INZU391E       *
  * message is unduly issued twice when                          *
  * attempting to run a logical unload requesting the INTERNAL   *
  * FORMAT in SQL mode.                                          *
  * Fix6 - When an unload put the indexscan feature into action, *
  * unpredictable troubles among the                             *
  * following ones can occur:                                    *
  * - the unloaded rows are not sorted as requested by the ORDER *
  * clause                                                       *
  * - the unload job ends with ABENDS0C4                         *
  * - the unload job ends with ABENDU1114                        *
  * - the indexscan feature is less efficient than expected      *
  * This occurs when the index used by the indexscan feature has *
  * been altered. The entries added to the                       *
  * index after this operation are not correctly retrieved by    *
  * the indexscan feature. Most of the time,                     *
  * this leads the indexscan feature to disregard this entry     *
  * which spoils the interest of the indexscan                   *
  * feature. However, in some rare situations this can lead to   *
  * the other troublebs listed above.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply the PTF for problem resolution                         *
  ****************************************************************
  

Problem conclusion

• Code has been changed to fix this problem
  

Temporary fix

• PI99487:
  Consider setting ULLOCKTE to LOCK if applicable to your use
  cases.
  
  PH00452:
  Determine if the image copy to be unloaded is a global or a
  partitioned one and add the GLOBAL or
  the PARTITIONED suboption to the COPYDDN -n option accordingly
  
  PH00455, PH00725:
  Disable the index scan feature by adding the INDEXSCAN NO option
  or reorganize the index involved by
  the index scan feature.
  
  PH00823:
  None, but the need for post-processing can be simply avoided by
  specifying an INTO TABLE clause in
  the related SELECT statement from the unload statement.
  
  PH00866:
  Run the unload in SQL mode by specifying DB2 FORCE or the
  corresponding options for the non-HPU
  native syntaxes.
  
  PH00917: None, but a new run of the unload might be successful.
  
  PH01210:
  Fix1 - Remove the remove FORMAT option specified at unload
  LEVEL.
  Fix4 - Consider requesting only one output file and make a copy
  afterwards.
  Fix6 - Run the REORG utility against the index involved in the
  indexscan feature.
  

Comments

APAR Information

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

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

  UI57811

Modules/Macros

• INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R510 PSY UI57811

     UP18/08/16 P F808

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.