IBM Support

PI55738: A PHYSICAL UNLOAD (UNLDDN) IN INTERNAL FORMAT (INTERNAL_FORMAT) PRODUCES INCORRECT OUTPUT DATA THAT CANNOT BE LOADED BY DB2 LOAD

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A physical unload (UNLDDN) in internal format (INTERNAL_FORMAT
    option) produces incorrect output data that cannot be loaded by
    the DB2 LOAD utility.
    
    This occurs if the following conditions are fullfilled:
    
        the involved table space is partitionned
        the output data set (UNLDDN) is allocated by the use of a
                                               TEMPLATE statement.
        the DB2 HPU/InfoUnload settings sepcify GBLPARAL = NO
    
    A typical unload statement where this issue occurs is :
    TEMPLATE UNLDDATA DSN ME.MYUNLOAD.OUTPUT.DATA
    UNIT 3390 DISP (NEW,CATLG,CATLG)
    
    UNLOAD TABLESPACE DSN8DA1A.DSN8SA1E
    UNLDDN(UNLDDATA)
    INTERNAL_FORMAT
    
    Attempting to load the data unloaded by DB2 HPU/InfoUnload leads
    to a failure such as that reported by the DB2 LOAD utility by
    the following message :
    
    DSNU334I @ 018 12:17:50.56 DSNURWBF - INPUT FIELD 'RECORD HEADER
    LENGTH FOR FORMAT INTERNAL',
    INVALID FOR 'DSN8A10.EMP',
    ERROR CODE '34'
    
    PB44130
    

Local fix

  • Use logical unload - SELECT * FROM, and FORMAT INTERNAL with
    OUTDDN option.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 High Performance Unload.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: A physical unload (UNLDDN) in internal  *
    *                      fomat (INTERNAL_FORMAT option)          *
    *                      produces incorrect output data that     *
    *                      cannot be loaded by the DB2 LOAD        *
    *                      utility.                                *
    *                      This occurs if the following conditions *
    *                      are fullfilled:                         *
    *                       the involved table space is            *
    *                        partitionned                          *
    *                       the output data set (UNLDDN) is        *
    *                        allocated by the use of a TEMPLATE    *
    *                        statement.                            *
    *                       the DB2 HPU/InfoUnload settings        *
    *                        sepcify GBLPARAL = NO                 *
    *                      A typical unload statement where this   *
    *                      issue occurs is :                       *
    *                      TEMPLATE UNLDDATA DSN                   *
    *                       ME.MYUNLOAD.OUTPUT.DATA                *
    *                       UNIT 3390 DISP (NEW,CATLG,CATLG)       *
    *                       UNLOAD TABLESPACE DSN8DA1A.DSN8SA1E    *
    *                       UNLDDN(UNLDDATA)                       *
    *                       INTERNAL_FORMAT                        *
    *                      Attempting to load the data unloaded    *
    *                      by DB2 HPU/InfoUnload leads to a        *
    *                      failure such as that reported by the    *
    *                      DB2 LOAD utility by the following       *
    *                      message :                               *
    *                      DSNU334I @ 018 12:17:50.56 DSNURWBF -   *
    *                       INPUT FIELD 'RECORD HEADER LENGTH      *
    *                       FOR FORMAT INTERNAL',                  *
    *                       INVALID FOR 'DSN8A10.EMP',             *
    *                       ERROR CODE '34'                        *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    The inzrunh module was changed.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI55738

  • Reported component name

    DB2 HI PERF UNL

  • Reported component ID

    5697F4400

  • Reported release

    420

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-20

  • Closed date

    2016-02-29

  • Last modified date

    2016-04-05

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

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

    UI35745 UI35746

Modules/Macros

  •    INZUTILK
    

Fix information

  • Fixed component name

    DB2 HI PERF UNL

  • Fixed component ID

    5697F4400

Applicable component levels

  • R420 PSY UI35745

       UP16/03/05 P F603

  • R430 PSY UI35746

       UP16/03/05 P F603

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAUUV","label":"IBM Db2 High Performance Unload for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 February 2021