IBM Support

PM55247: MISPLACED COMMENT HEADER ('--') NOT STARTING IN COLUMN 1 PRODUCES UNEXPECTED OUTPUT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a comment header, i.e. the two dashes ('--'),
    located within the SELECT statement is misplaced
    (i.e. not starting in column 1), the SELECT evaluation is
    performed in SQL mode with a statement including the unsupported
    comments header.
    As DB2 ignores the part of the statement located after the first
    misplaced comment, if the altered statement is syntaxically
    valid, the unload ends with completion code 0 but produces
    unexpected output.
    
    For example.
    - Two dashes starting in column 1, HPU treats line as comment.
    - Two dashes starting in column 3, HPU incorrectly ignores
      the rest of the SELECT filter starting with this comment line.
    
    PB11395
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 High Performanc Unload.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: No Fix is provided for V320. FIN.       *
    *                                                              *
    *                      When a comment header, i.e. the two     *
    *                      dashes ('--'), located whitin the       *
    *                      SELECT statement is misplaced (i.e.     *
    *                      not starting in column 1), the SELECT   *
    *                      evaluation is performed in SQL mode     *
    *                      with a statement including the          *
    *                      unsupported comments header. As DB2     *
    *                      ignores the part of the statement       *
    *                      located after the first misplaced       *
    *                      comment, if the altered statement is    *
    *                      syntaxically valid, the unload ends     *
    *                      with completion code 0 but produces     *
    *                      unexpected output.                      *
    *                      PB 11395                                *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    olex, inzmain, inzmyacc, inzhyacc, inztyacc, inzoyacc, inztopt
    and inzdyacc modules were changed so that the parser support
    SQL-like comments in the SELECT statement of a logical unload.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM55247

  • Reported component name

    DB2 HI PERF UNL

  • Reported component ID

    5697F4400

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-01-03

  • Closed date

    2012-05-24

  • Last modified date

    2012-06-03

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

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

Modules/Macros

  •    INZRSAVE
    

Fix information

  • Fixed component name

    DB2 HI PERF UNL

  • Fixed component ID

    5697F4400

Applicable component levels

  • R410 PSY UK79049

       UP12/05/30 P F205

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":"320"}]

Document Information

Modified date:
31 March 2021