IBM Support

PH17278: VALUE OF VUU032/ULMASK NOT DISPLAYED BY THE DISPLAY_PARMLIB/VUU083/DISPPARM

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The value of VUU032/ULMASK parameter is missing
    from the file generated by the feature that consists in
    displaying the values of the parmlib parameters and that is
    requested through the DISPLAY_PARMLIB option or the
    VUU083/DISPPARM parmlib parameter.  (HPU 5.1 only).
    

Local fix

  • na
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of High Performance Unload for z/OS                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * PH13896                                                      *
    * Allow LOCK YES in SQL mode                                   *
    *                                                              *
    * PH15336                                                      *
    * The text of the INZU508I message issued to report that the   *
    * LOCK feature hs been completed is always the following one:  *
    * TABLE creator.table HAS BEEN LOCKED IN SHARE MODE DURING     *
    * UNLOAD PROCESS                                               *
    * which suggests the whole table has been locked while, when   *
    * partial processing of a partitionned table is concerned, the *
    * LOCK operation is done at the partition level and for the    *
    * subset of partitions involved by the unload statement.       *
    * This case where only some partitions of the table space are  *
    * locked should be indicatd by appending the following text to *
    * the above mentioned message.                                 *
    * LIMITED TO UNLOADED PARTITIONS.                              *
    *                                                              *
    * PH17278                                                      *
    * The value of VUU032/ULMASK parameter is missing from the     *
    * file generated by the feature that consists in displaying    *
    * the values of the parmlib parameters and that is requested   *
    * through the DISPLAY_PARMLIB option or the VUU083/DISPPARM    *
    * parmlib parameter.                                           *
    *                                                              *
    * PH17302                                                      *
    * Using inline copies requires an addition keyword and the     *
    * utility also performs a sort.                                *
    *                                                              *
    * Sometimes, especially with bulk unloads there could be many  *
    * objects that may have normal and inline copies as their last *
    * IC.                                                          *
    * We wish to avoid a SORT in these situations as this has      *
    * previously caused abends for some of our largest tables.     *
    * Also,                                                        *
    *                                                              *
    * PH17313                                                      *
    * The SIZE parameter only applies with this syntax             *
    * UNLOAD TABLESPACE dbname.tsname COPYDDN ddname1,INLINE       *
    * DDLDDN ddname SIZE integer                                   *
    * When the image copy comes from a different system there is   *
    * no method to specify the SIZE parameter.                     *
    * Proposed syntax is                                           *
    * UNLOAD TABLESPACE dbname.tsname                              *
    * COPYDDN ddname1,INLINE  SIZE integer                         *
    *                                                              *
    *                                                              *
    * PH17659                                                      *
    * The value of the format- or syntax-dependent parameters,     *
    * such as                                                      *
    * VUU015/ULDATE                                                *
    * VUU071/LOSSCHAR                                              *
    * are not presented/formatted the same way in the Tools        *
    * Customizer's interface and in the INZUTIL and INZDssid       *
    * members of the parmlib that is used by Db2 HPU at run time.  *
    * For example, in the Tools Customizer interface               *
    *                                                              *
    * DATE, format USER (VUU015/ULDATE)                            *
    * DATE, format DSNTIAUL (VUU015/ULDATE)                        *
    * DATE, format DELIMITED (VUU015/ULDATE)                       *
    * DATE, format VARIABLE (VUU015/ULDATE)                        *
    * DATE, format EXTERNAL (VUU015/ULDATE)                        *
    * and the value in the INZUTIL member is formatted as follows  *
    * VUU015/ULDATE =                                              *
    * U(DATE_C),D(DATE_DB2),L(DATE_C),V(DATE_C),E(DATE_DB2)        *
    *                                                              *
    * As the feature that displays the values of the parmlib       *
    * parameters taken fmo the INZUTIL and INZDssid members        *
    * (requsted through the DISPLAY_PARMLIB option or its          *
    * counterpart DISPPARM parmlib parameter), the user cannot     *
    * understand the value displayed for these parameters.         *
    * The format used by the feature that displays the parmlib     *
    * parameter should be explained within the file it produces.   *
    *                                                              *
    * PH17769                                                      *
    * The diagnostic report issued in case of ABEND should provide *
    * more information to help diagnose some hanging situations.   *
    *                                                              *
    * PH17992                                                      *
    * A logical unload (OUTDDN option) run in native mode produces *
    * a VARCHAR data type output field with an incorrect padding   *
    * character. This occurs when the following conditions are     *
    * fulfilled:                                                   *
    * - the padding character applicable to the VARCHAR data type  *
    * is not the blank character encoded in the ccsid of the table *
    * involved in the SELECT statement                             *
    * - at least one of the columns located before the column      *
    * involved in the incorrect output field is not involved in    *
    * the unload                                                   *
    * - the column involved in the output field in error and the   *
    * preceding column are elligible for a Db2 HPU optimized       *
    * processing that requires a complex set of of conditions to   *
    * be satisfied among which:                                    *
    *    + no CCSID conversion is needed                           *
    *    + the previous column is not nullable CHAR or VARCHAR or  *
    * GRAPHIC or VARGRAPHIC column                                 *
    *    + no delimiter or separator is requested for the format   *
    * of both output fields                                        *
    *                                                              *
    * PH18994                                                      *
    * HPU terminates in error (completion code of 8) after having  *
    * issued the following messages:                               *
    *                                                              *
    * INZI666F FATAL ERROR : ODB2CMD UNSUPPORTED DB2VERSION        *
    * INZI174E ERROR WHEN TRYING TO DETERMINE ENFM STATUS.         *
    * INZU366I UTILITY RETURN CODE 8 (REASON CODE 0x21a004)        *
    *                                                              *
    * when the following conditions are fulfilled:                 *
    * - a Db2 group name is specified in the PARM option of the    *
    * EXEC statement used to invoke Db2 HPU.                       *
    * - two members of the data sharing group are on the same      *
    * machine                                                      *
    * - one of the member hosted by the same machine is in version *
    * 12 and the other one is in a prior version                   *
    *                                                              *
    * PH19264                                                      *
    * After the fix for PH16342 is applied, any unload run in SQL  *
    * mode fails after having issued the following error messages: *
    * INZR2009 DB2 ERROR: SET CURRENT APPLICATION COMPATIBILITY    *
    * DSNT408I SQLCODE = 805, ERROR: DBRM OR PACKAGE NAME          *
    * DZCALOC1..INZCRXSQ.1AD59                                     *
    * 7D70121F3F3 NOT FOUND IN PLAN db2_hpu_plan. REASON 03        *
    * DSNT418I SQLSTATE = 51002 SQLSTATE RETURN CODE               *
    * DSNT415I SQLERRP = DSNXEPM SQL PROCEDURE DETECTING ERROR     *
    * DSNT416I SQLERRD = -251 0 0 -1 0 0 SQL DIAGNOSTIC            *
    * INFORMATION                                                  *
    * DSNT416I SQLERRD = X'FFFFFF05' X'00000000' X'00000000'       *
    * X'FFFFFFFF'                                                  *
    * X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION INZU362E  *
    * UNLOAD 00001 FROM TABLESPACE DSNDB06.SYSTSDBA FAILED         *
    * POS(1, 2) RC = 0x144a005                                     *
    *                                                              *
    * PH19265                                                      *
    * An ABENDS0C4 occurs when the FIX_DB2_VER subparameter is     *
    * specified in the value set for the VUU030/ULOPTNS parmlib    *
    * parameter.                                                   *
    *                                                              *
    * PH19457                                                      *
    * Db2 HPU has features that exploit the content of explain     *
    * tables.                                                      *
    * For Advanced reporting/automatization and troubleshooting,   *
    * there should be a way to request InfoUnload/Db2 HPU to       *
    * display the records from the EXPLAIN tables it has taken     *
    * into account.                                                *
    * It should also display the following information:            *
    * SELECT number                                                *
    * EXPLAIN tables read                                          *
    * The exact selection of partition for each select.            *
    *                                                              *
    * PH19459                                                      *
    * The first implementation of (RFE101390 did not meet the      *
    * customer expectation as the object selection was not         *
    * restricted to the criterion on the table or view name        *
    * specified by the user. A new implementation based on a       *
    * dedicated LISTDEFTBV statement is proposed.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply the PTF.                                               *
    ****************************************************************
    Code has been changed to fix this problem.
    

Problem conclusion

  • Apply the PTF.
    

Temporary fix

  • PH17992
    Add the OPTIM_LEVEL 0 option in the GLOBAL otions block to
    disable the optimization process that causes the incorrect
    padding character issue.
    PH18994
    Use the name of a member in the PARM option of the EXEC
    statement used to invoke Db2 HPU.
    PH19264
    If applicable, consider running the unload in native mode.
    

Comments

  • ×**** PE23/11/09 PTF IN ERROR. SEE APAR PH56348  FOR DESCRIPTION
    ×**** PE23/08/14 FIX IN ERROR. SEE APAR PH56348  FOR DESCRIPTION
    ×**** PE23/08/14 FIX IN ERROR. SEE APAR PH56348  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PH17278

  • Reported component name

    DB2 HI PERF UNL

  • Reported component ID

    5697F4400

  • Reported release

    510

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-09-24

  • Closed date

    2019-12-03

  • Last modified date

    2024-01-02

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

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

    UI66755

Modules/Macros

  • INZTDSC  INZSETA  INZSDBA  INZCRXSQ INZSDBE  INZTVAR  INZSETE
    INZ$$PRM INZCRXSM INZQRYV9 INZUTILK INZSDBU  INZSETU
    

Fix information

  • Fixed component name

    DB2 HI PERF UNL

  • Fixed component ID

    5697F4400

Applicable component levels

  • R510 PSY UI66755

       UP19/12/18 P F912

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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"510","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 January 2024