PM76930: CREATE TRIGGER WILL FAIL IF THE FIRST INPUT VALUE IS A SPECIAL REGISTER DURING PARSING USING DDL/GEN, ALT OR OBJECT COMPARE.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 ADMINISTRATION TOOL FOR Z/OS AND DB2 OBJECT COMPARISON TOOL
  FOR Z/OS.
  When the trigger has embedded SQL statements VALUES or VALUES
  INTO and one of the special registers(CURRENT DATE, CURRENT
  TIME, etc.) is used as the input value for the statements, and
  the first input value is a special register, then parsing will
  fail when using DDL/GEN, ALT or Object Compare against the
  trigger.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Administration Tool for     *
  *                 z/OS who use the Generate (GEN) function     *
  *                 to generate DDL for a trigger.               *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR addresses the following       *
  *                      issues:                                 *
  *                                                              *
  *                      1 - When the CREATE TRIGGER statement   *
  *                      has embedded SQL 'VALUES' or 'VALUES    *
  *                      INTO' statements, one of the special    *
  *                      registers (CURRENT DATE, CURRENT TIME,  *
  *                      etc.) is used as the input value for    *
  *                      the statements, and the first input     *
  *                      value is a special register, the parser *
  *                      will fail when using the DDL/GEN, ALT   *
  *                      line commands, or Object Compare        *
  *                      against the trigger:                    *
  *                                                              *
  *                      CREATE TRIGGER                          *
  *                         >trigger-name<                       *
  *                         ...                                  *
  *                         FOR EACH ROW MODE                    *
  *                         DB2SQL                               *
  *                           BEGIN ATOMIC                       *
  *                           ...                                *
  *                           VALUES(value1, value2,..) ;        *
  *                           ...                                *
  *                                                              *
  *                      2 - When the trigger has embedded SQL   *
  *                      statements containing a period-clause,  *
  *                      the parser will fail when using the     *
  *                      DDL/GEN, ALT line commands, or Object   *
  *                      Compare against the trigger:            *
  *                                                              *
  *                      CREATE TRIGGER >trigger-name<           *
  *                        ....                                  *
  *                        FOR EACH ROW MODE DB2SQL              *
  *                          BEGIN ATOMIC                        *
  *                          ...                                 *
  *                          DELETE                              *
  *                            FROM >table-name< ...             *
  *                          END ?                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR addresses the following issues:
  
  1 - Program can not parse all special registers in the CREATE
  TRIGGER statement using the 'VALUES' and 'VALUES INTO' options.
  
  2 - Program can not parse the period-clause in the delete
  statement.
  

Problem conclusion

• Problems have been resolved.
  

Temporary fix

Comments

APAR Information

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

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

  UK90397 UK90398

Modules/Macros

•    ADB2PA
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK90397

     UP12/12/19 P F212

• RA20 PSY UK90398

     UP12/12/19 P F212

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.