PM49130: GEN 'MISSING SEMICOLON AFTER TRIGGERED ACTION' TOKEN = INTO TRIGGER SUBSTR(CHAR(CURRENT TIMESTAMP),25,2) ADB1847E ADB1848W

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DB2 Administration Tool for z/OS GEN function issues a
  message:
  Missing semicolon after triggered action
  
  ADB2PA: The following statement could not be parsed :
  
  CREATE TRIGGER <schema>.<trigger>
  NO CASCADE BEFORE INSERT ON <schema>.<table>
  REFERENCING NEW AS N
  FOR EACH ROW MODE DB2SQL
  BEGIN ATOMIC VALUES SUBSTR(CHAR(CURRENT TIMESTAMP),25,2) INTO
  N.COLUMN ;
  END
  
  Token number =     nn, Token = INTO
  then:
  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>
  If the customer specified a new schema i.e. the
  input parms contain the 'NEWSQLID =' parm the
  messages changes to:
  ADB1847E A parser error occurred for the following trigger. GEN
  cannot completethe request.
              Reason code = 8
              <schema>.<trigger>
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Administration Tool for     *
  *                 z/OS who use the GEN or DDL line             *
  *                 commands to generate DDL for Triggers.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: The DB2 Administration Tool for z/OS    *
  *                      issues the following message when       *
  *                      generating DDL for a Trigger:           *
  *                                                              *
  *                      Missing semicolon after triggered       *
  *                      action                                  *
  *                                                              *
  *                      ADB2PA: The following statement         *
  *                      could not be parsed :                   *
  *                                                              *
  *                      CREATE TRIGGER >schema<.>trigger<       *
  *                      NO CASCADE BEFORE INSERT                *
  *                      ON >schema<.>table><                    *
  *                      REFERENCING NEW AS N                    *
  *                      FOR EACH ROW MODE DB2SQL                *
  *                      BEGIN ATOMIC VALUES SUBSTR              *
  *                      (CHAR(CURRENT TIMESTAMP),25,2) INTO     *
  *                      N.COLUMN ;                              *
  *                      END                                     *
  *                                                              *
  *                      Token number =    nn, Token = INTO      *
  *                      then:                                   *
  *                      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<          *
  *                                                              *
  *                      If the customer specified a new schema  *
  *                      i.e. the input parms contain the        *
  *                      'NEWSQLID =' parm, the messages         *
  *                      changes to:                             *
  *                                                              *
  *                      ADB1847E A parser error occurred for    *
  *                      the following trigger.                  *
  *                      GEN cannot complete the request.        *
  *                                  Reason code = 8             *
  *                                 >schema<.>trigger<           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The DB2 Administration Tool for z/OS considers the VALUES INTO
  clause invalid in the trigger body.
  

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:

  UK76126 UK76125

Modules/Macros

•    ADB2PA
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK76125

     UP12/02/15 P F202

• R720 PSY UK76126

     UP12/02/15 P F202

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.