IBM Support

PI93189: WRONG DDLDDN FILE ANALYSIS IF APPEND / LOGGED / COMPRESS / DSSIZE / BUFFERPOOL / MEMBER

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 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
    
    INZC004E INZC004 MSGINZC004E MSGINZC004
    INZI516E INZI516 MSGINZI516E MSGINZI516
    PB51334 Z632
    

Local fix

  • 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.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM DB2 High Performance Unload     *
    *                 z/OS.                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: 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                      *
    *                      pb51334                                 *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    The inzmsgs and inzctrlh modules were changed.The oddlx2y
    module was changed.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI93189

  • Reported component name

    DB2 HI PERF UNL

  • Reported component ID

    5697F4400

  • Reported release

    430

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-31

  • Closed date

    2018-02-19

  • Last modified date

    2018-03-01

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

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

Modules/Macros

  •    INZUTILX
    

Fix information

  • Fixed component name

    DB2 HI PERF UNL

  • Fixed component ID

    5697F4400

Applicable component levels

  • R430 PSY UI53962

       UP18/02/23 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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"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":"4.3.0"}]

Document Information

Modified date:
31 March 2021