IBM Support

PM33869: SQL, UNDEFINED COLUMN NAME

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Per PMR 70160,379,000 - SQL, undefined column name
    
    ================================================================
    Date reported: 02/01/2011
    
    Severity: high
    
    Users Affected:
     All IMU users of MU V3.2
    
    Problem Description:
     SQL is returning "RJCP419.PROV_MSTR_T IS AN UNDEFINED NAME'
     for SQL SELECT * FROM PROV_MSTR_T WHERE PROV_TAX_ID = ?
     when running in Dynamic SQL mode, but program does not
     terminate.
    
    Problem Summation
     This is a user error. Bad SQL statement because there is no
     table name specified, thus
     IMU used the TSO user name (owner ID) to compensate for the
     missing table.
    
     Note that it is the user's responsibility to check SQLCODE when
     doing controlled SQL.
    
    Problem Conclusion:
    
     The user corrected this problem by adding the DB2 table name to
     the column name.
     i.e., SELECT *  FROM LCTEST.PROV_MSTR_T WHERE PROV_TAX_ID = ?
     solved the problem.
    
     Logic was added to FSSQLER2 (Dynamic SQL error handler) to
     terminate the run with RC=16 when PREPARE, DESCRIBE or OPEN
     statements fail.
    
    
    
    
    Impacted Modules in SFSYLOAD:
    
     FSSQLER2 alias of FSYQLER2
    ================================================================
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMU v3.2 Users                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: SQL is returning "RJCP419.PROV_MSTR_T   *
    *                      IS AN UNDEFINED NAME' for SQL SELECT *  *
    *                      FROM PROV_MSTR_T WHERE PROV_TAX_ID = ?  *
    *                      when running in Dynamic SQL mode, but   *
    *                      program does not terminate.             *
    ****************************************************************
    * RECOMMENDATION: Apply PTF.                                   *
    ****************************************************************
    

Problem conclusion

  • Original error was caused by user failing to include the DB2
    table name.
    
    Logic was added to FSSQLER2 (Dynamic SQL error handler) to
    terminate the run with RC=16 when PREPARE, DESCRIBE or OPEN
    statements fail.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM33869

  • Reported component name

    MIGRATION UTILI

  • Reported component ID

    5697N4400

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-01

  • Closed date

    2011-04-19

  • Last modified date

    2011-05-02

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

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

Modules/Macros

  •    FSYQLER2
    

Fix information

  • Fixed component name

    MIGRATION UTILI

  • Fixed component ID

    5697N4400

Applicable component levels

  • R320 PSY UK66901

       UP11/04/21 P F104

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSY4B9","label":"IBM Migration Utility for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"320","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
27 October 2020