PM72854: DDL / GEN TRIGGER WITH BEGIN ATOMIC REFRESH TABLE RESULTS IN UNEXPECTED TOKEN MESSAGE TOKEN = REFRESH ADB2PA

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DB2 Administration Tool for z/OS' DDL and GEN functions
  issue a message:
  Unexpected token after triggered action(s) - expected keyword is
  'END'
  
  ADB2PA: The following statement could not be parsed :
  
  CREATE TRIGGER >trigger< AFTER INSERT ON >table<
  FOR EACH ROW MODE DB2SQL BEGIN ATOMIC REFRESH TABLE >table<;
  END
  
  Token number =     15, Token = REFRESH
  Unexpected token after triggered action(s) - expected keyword is
  'END'
  
  ADB2PA: The following statement could not be parsed :
  
  CREATE TRIGGER >trigger< AFTER INSERT ON >table<
  FOR EACH ROW MODE DB2SQL BEGIN ATOMIC REFRESH TABLE >table<;
  Token number =     15, Token = REFRESH
  ***
  The GEN output will also contain a message:
  ADB1848W Unformatted DDL will be generated for the following
  trigger because it could not be parsed. Please verify the DDL.
  Reason code = 28
  >schema<.>trigger<
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Administration Tool for     *
  *                 z/OS who issue the DDL line command against  *
  *                 a trigger on panel ADB21J 'Triggers' and a   *
  *                 REFRESH TABLE statement is specified in the  *
  *                 trigger body.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: In DB2 Administration Tool for z/OS,    *
  *                      when using the DDL line command on the  *
  *                      panel ADB21J, DB2 Admin generates the   *
  *                      CREATE TRIGGER DDL statement.  If       *
  *                      there is a REFRESH TABLE statement      *
  *                      defined in the trigger body, a warning  *
  *                      ADB1848W is displayed:                  *
  *                                                              *
  *                      ADB1848W Unformatted DDL will be        *
  *                      generated for the following trigger     *
  *                      because it could not be parsed.         *
  *                                                              *
  *                      followed by the parsing error:          *
  *                                                              *
  *                      ADB2PA: The following statement         *
  *                      could not be parsed :                   *
  *                                                              *
  *                      CREATE TRIGGER >trigger<                *
  *                      AFTER INSERT ON >table<                 *
  *                      FOR EACH ROW MODE DB2SQL                *
  *                      BEGIN ATOMIC REFRESH                    *
  *                      TABLE >table<;                          *
  *                      END                                     *
  *                                                              *
  *                      Token number =     15,                  *
  *                      Token = REFRESH                         *
  *                      Unexpected token after                  *
  *                       triggered action(s) - expected         *
  *                      keyword is 'END'                        *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In DB2 Administration Tool for z/OS, when issuing the DDL line
  command against a trigger on panel ADB21J, DB2 Admin generates
  the CREATE TRIGGER DDL statement.  If there is a REFRESH TABLE
  statement defined in its body, the REFRESH TABLE statement is
  not parsed correctly.
  

Problem conclusion

• Problem has 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:

  UK83260 UK83261

Modules/Macros

•    ADB2PA   ADB2PA3  H0IHA10J H0IHA20J
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK83260

     UP12/11/09 P F211

• RA20 PSY UK83261

     UP12/11/09 P F211

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.