IBM Support

PK57147: CONCAT OPERATOR IN TRIGGER RESULTS IN DIAGNOSTIC TEXT IN SIGNAL SQLSTATE NOT RECOGNIZED.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The DB2 Object Comparision Tool issues a message:
    Diagnostic text in SIGNAL SQLSTATE not recognized
    
    Error occured when parsing the following stmt :
    CREATE TRIGGER aaaaaaa.aaaaaaa AFTER INSERT ON aaaaaaa.aaaaaaa
    FOR EACH
    STATEMENT MODE DB2SQL BEGIN ATOMIC SIGNAL SQLSTATE '99999'(
    'aaaaaaaaaaa' || 'aaaaaaaa ' ) ; END
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: In  R710 & R720, when user creates a         *
    *                 trigger with SIGNAL SQLSTATE                 *
    *                 diagnostic text containing concat            *
    *                 operator.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: During Source DDL to target DDL/DB2     *
    *                      catalog  compare, when source DDL is    *
    *                      having create trigger. Diagnostic text  *
    *                      in SIGNAL SQLSTATE with concat          *
    *                      operator, results in parsing error      *
    *                      'Diagnostic text in SIGNAL SQLSTATE     *
    *                      not recognized'. This is due to concat  *
    *                      operator not being recognized in        *
    *                      diagnostic text by the parser.          *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    The problem is due to parser expects end of diagnostic text with
    right parenthesis in SIGNAL SQLSTATE and unable to recognize
    concat operator in diagnostic text.
    

Problem conclusion

  • The problem is been fixed both in V7.1 and in  V7.2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK57147

  • Reported component name

    DB2 OBJECT COMP

  • Reported component ID

    5697G6400

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-11-27

  • Closed date

    2008-04-08

  • Last modified date

    2008-05-05

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

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

Modules/Macros

  •    ADB2PA
    

Fix information

  • Fixed component name

    DB2 ADMIN TOOL

  • Fixed component ID

    568851500

Applicable component levels

  • R710 PSY UK35294

       UP08/04/16 P F804

  • R720 PSY UK35295

       UP08/04/16 P F804

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":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
05 May 2008