IBM Support

PI53966: RECEIVE ABEND0C4 WHEN ENTERING SQL FROM FILE MANAGER/DB2 OPTION 4.3 - ENTER, EXECUTE AND EXPLAIN SQL STATEMENTS PANEL

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When SQL is entered from File Manager/DB2 option 4.3 -
    
     Enter, Execute and Explain SQL Statements panel
    
    to select from a view, which was defined with the qualified
    table name in front of each column, receive 0C4 abend
    processing command FMNDB2.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of File Manager DB2 component      *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. ABENDS0C4 after entering a SELECT    *
    *                      statement using the FM/DB2 'Enter,      *
    *                      Execute and Explain SQL' option.        *
    *                      2. ABENDS0C4 module FMN2SQS2 offset     *
    *                      x'220'.                                 *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    1. The failing SELECT statement refers to a view that has
    qualified column names in the definition, eg:
    CREATE VIEW V1 AS SELECT OWNER.NAME.COLNAME1, .. FROM OWNER.NAME
    instead of the simpler:
    CREATE VIEW V1 AS SELECT COLNAME1, .. FROM OWNER.NAME.
    An SQLCODE+203 is received when the view is created.  The code
    that parses the view definition fails when it encounters the
    qualified column names.
    2. The problem occurs with the File Manager DB2 component
    'Enter, Execute and Explain SQL' function.
    The abend occurs after entering an SQL statement that results
    in an SQL error.
    

Problem conclusion

  • File Manager DB2 component has been changed to correct the
    problem.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI53966

  • Reported component name

    FILE MANAGER Z/

  • Reported component ID

    5655W6800

  • Reported release

    C12

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-12-10

  • Closed date

    2016-05-19

  • Last modified date

    2016-06-02

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

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

    PI57693

Modules/Macros

  • FMN0LVL  FMN1LVL  FMN2LVL
    

Fix information

  • Fixed component name

    FILE MANAGER Z/

  • Fixed component ID

    5655W6800

Applicable component levels

  • RC10 PSY UI38029

       UP16/05/26 P F605

  • RC12 PSY UI38032

       UP16/05/26 P F605

  • RC14 PSY UI38034

       UP16/05/26 P F605

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C12","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAV","label":"File Manager for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C12","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
02 June 2016