PH06746: INZI800E UNDULY ISSUED DURING LOGICAL UNLOAD WITH INDEX SCAN FEATURE Z666

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A logical unload with an ORDER clause run in native mode
  completes successfully but the INZI800E message is unduly
  issued. The error message reports an issue such as in the
  following example:
  INZI800E ERROR ACCESSING TO A DATASET. ACTION: ALLOCATE RC:
  0x1708 REASON: 0x2
  DDN: SYSnnn DSN:
  name.of.a.potential.LDS.of.table.clustering.index
  where the indicated data set name corresponds to the name of a
  potential LDS of the clusteringindex associated to the table
  involved in the unload.
  This occurs if
  -  the index scan feature is put into action (the ORDER clause
  is elligible to the index scan feature and the index scan
     feature is enabled)
  -  the last space map of the non-partitioned clustering index
  used by the index scan feature refers to pages thatbelong to
  not existing subsequent LDS.
  In such a case, although the following message is issued:
  IKJ56228I DATA SET ... NOT IN CATALOG OR CATALOG CAN NOT BE
  ACCESSED.
  the unload process continues. Therefore, the mentioned situation
  should not be reported through a misleading INZI800E error
  messsage.
  INZI800E unduly issued during logical unload with index scan
  feature
  PB54446
  
  lines from the output data set for the DISPLAY_PARMLIB/DISPPARM
  feature exceed 80 characters long
  
  PB53815
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of High Performance Unload                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * PH02519:                                                     *
  * A logical unload from image copies run in EXECUTE NO mode    *
  * (i.e. the EXECUTE NO option is                               *
  * specified) fails after having issued messages as follows     *
  *    IKJ56221I DATA SET name.of.an.input.imape.copy.dataset    *
  * NOT ALALLOCATED, VOLUME NOT AVAILABLE+                       *
  *    IKJ56221I VOLUME IS ALLOCATED TO ANOTHER JOB OR USER, TRY *
  * LATER                                                        *
  * and                                                          *
  *     INZI330E DYNAMIC ALLOCATION FAILED.                      *
  *          DSN=name.of.an.input.imape.copy.dataset             *
  *          RC=4, REASON=0x220                                  *
  *          SVC99 MESSAGES ARE REPORTED IN JESMSGL CARD         *
  *     INZI332I DYNAMIC ALLOCATION PARAMETER LIST (SVC99):      *
  * This occurs when the following conditions are fullfiled:     *
  * - the input image copies are dynamically allocated by DB2    *
  * HPU (either COPYDDN LAST_IC or COPYDDN                       *
  * -integer is specified or COPYDDN template_name where         *
  * template_name is the name of a template                      *
  * describing the image copy data set to be used as input)      *
  * - there are at least two UNLOAD command involving image      *
  * copies located on the same volume.                           *
  *                                                              *
  * PH05540:                                                     *
  * An ABENDS0C4 always occurs if the unload statement fulfills  *
  * the set of conditions below:                                 *
  * - the output data contains DATE/TIME data.                   *
  * - the DB2 settings specify LOCAL as the date/time format.    *
  * - if the native mode is used, the output format applicable   *
  * for either DATE/TIME data is                                 *
  * respectively DATE_DB2/TIME_DB2.                              *
  * - if the SQL mode is used, the output format applicable for  *
  * either DATE/TIME data is distinct                            *
  * respectively from  DATE_DB2/TIME_DB2.                        *
  *                                                              *
  * PH06254:                                                     *
  * Fix #1 - Db2 HPU fails after having issued the following     *
  * message:                                                     *
  *      INZU220E THE SETTINGS FOR ssid IN THE PARMLIB ARE       *
  * INCOMPLETE OR ARE MISSING                                    *
  * although the settings for the mentioned Db2 subsystem or     *
  * group attachment name is correct.                            *
  * This occurs if an INFPLIB DD statement is specified to       *
  * allocate the Db2 HPU parmlib and this                        *
  * statement specifies the BUFNO parameter.                     *
  *                                                              *
  * PH06745:                                                     *
  * When an unload specifies a TEMPLATE requesting a file be     *
  * allocated on a tape unit, if no UNCNT                        *
  * option is specified for the TEMPLATE, DB2 HPU uses the       *
  * maximum number of devices specified for                      *
  * the unit as a value for UNCNT. This default choice is meant  *
  * to exploit as much devices as                                *
  * possible. When several TEMPLATE statements share a same tape *
  * UNIT or if a TEMPLATE statement is                           *
  * used several times because it is involved in an unload run   *
  * for several objects selected via a                           *
  * LISTDEF statement, UNCNT must be explicitly specified.       *
  * Otherwise, HPU issues INZI522E reporting                     *
  * the total number of devices assigned to the unit is          *
  * insufficient for the unload. There should be                 *
  * a way to specify the UNCNT value to be used by default.      *
  *                                                              *
  * PH06746:                                                     *
  * Fix #1 - A logical unload with an ORDER clause run in native *
  * mode completes successfully but the INZI800E                 *
  * message is unduly issued. The error message reports a        *
  * missing data set issue such as in the                        *
  * following example:                                           *
  *      INZI800E ERROR ACCESSING TO A DATASET. ACTION: ALLOCATE *
  * RC: 0x1708 REASON: 0x2                                       *
  *      DDN: SYSnnn DSN:                                        *
  * name.of.a.potential.LDS.of.table.clustering.index            *
  * where the indicated data set name corresponds to the name of *
  * a potential LDS of the clustering                            *
  * index associated to the table involved in the unload.        *
  * This occurs if                                               *
  * - the index scan feature is put into action (the ORDER       *
  * clause is elligible to the index scan                        *
  * feature and the index scan feature is enabled)               *
  * - the last space map of the non-partitioned clustering index *
  * used by the index scan feature                               *
  * refers to pages that belong to not existing subsequent LDS.  *
  * In such a case, although the following message is issued:    *
  *      IKJ56228I DATA SET ... NOT IN CATALOG OR CATALOG CAN    *
  * NOT BE ACCESSED.                                             *
  * the unload process continues. Therefore, the mentioned       *
  * situation should not be reported through a                   *
  * misleading INZI800E error messsage.                          *
  * Fix #2 - The output generated for the                        *
  * DISPLAY_PARMLIB/DISPPARM feature contains line which length  *
  *                                                              *
  * exceeds 80 characters which does not meet the feature        *
  * requirements.                                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply the PTF for problem resolution                         *
  ****************************************************************
  

Problem conclusion

• Code has been changed to fix this problem
  

Temporary fix

• PH02519:
  Consider rewriting the UNLOAD commands involving the same volume
  into two separate steps.
  
  Ph05540:
  Check if the format implemented by the involved exit (date/time)
  can be replaced by either one of
  the built-in date/time formats or by a user-defined date, time
  formats offered by Db2 HPU and
  specify this format through an OPTIONS block.
  
  PH06254:
  remove the BUFNO parameter that has no actual interest for the
  allocation of this dataset.
  
  PH06746:
  Just ignore the undue INZI800E message.
  

Comments

• ×**** PE19/08/02 PTF IN ERROR. SEE APAR PH08791  FOR DESCRIPTION
  

APAR Information

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

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

  UI60978

Modules/Macros

• INZ$$PRM INZCHECK INZUTILK INZTSSID
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R510 PSY UI60978

     UP19/01/31 P F901

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.