IBM Support

PH19262: OUTPUT FORMAT DEFAULT FOR FIELD EXPLICITLY SPECIFIED BY INTO CLAUSE SHOULD TAKE UPPER LEVEL FORMAT SPECIFICATION INTO ACCOUNT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as duplicate of another APAR.

Error description

  • When an INTO clause explicitly specify a target field (i.e.
    specifies a name), the output format that applies to this field
    is the default format applicable to the data type of the field
    altered by the explicit output format specified for this field.
    As a consequence, the generic format changes specified by a
    REFORMAT clause are ignored for the fields that are explicitly
    named by the INTO clause.
    When the target field must be named explicitly (the column name
    of the target table is different from its counterpat column in
    the source table or the field in question is an SQL expression
    that does not equal to a column name) by the INTO clause, a
    REFORMAT clause specification that matches the data type of this
    field is not taken into account.
    When the INTO clause must be used to specify a format change
    that only apples to a given field and not to all the fields
    having the same data type and a REFORMAT clause is also needed
    to specify generic format changes, the user must write an INTO
    clause where only the fields with specific changes can be name.
    The other fields must not be named in order to ensure the
    REFORMAT clause specifications apply. If the table has a lot of
    columns and the column for which a specific format is needed has
    a rank with a big value, the INTo clause that must specify as
    many commas as there are unchanged columns which is error prone.
    There should be a way request the output format for a field
    specified by the INTO clause is the one specified at a more
    general level than the field level, i.e.
    - REFORMAT clause
    - OPTIONS block at the SELECT level
    - OPTIONS block at the UNLOAD level if FORMAT USER and for any
    FORMAT option if OPALLFMT is set to YES
    - parmlib parameters
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  •  Fix included in APAR PH20621/PTF UI67516.
    

APAR Information

  • APAR number

    PH19262

  • Reported component name

    DB2 HI PERF UNL

  • Reported component ID

    5697F4400

  • Reported release

    510

  • Status

    CLOSED DUA

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-11-15

  • Closed date

    2020-02-03

  • Last modified date

    2020-02-03

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

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

Fix information

Applicable component levels

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

Document Information

Modified date:
12 February 2021