PH32660: WSL CREATE TRIGGER INCORRECT TERMINATION CHARACTER SQLCODE = -104; INTERPRET OF WSL ADBW1 ONCODE = 150 STRINGSIZE TOKENIZE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This APAR addresses two issue:
  
  1) CREATE TRIGGER DDL in a WSL may end with the wrong
  termination character.  When the DDL is executed the run job
  may end with rc=8 and the following error:
  
  DSNT408I SQLCODE = -104, ERROR:  ILLEGAL SYMBOL ";". SOME
           SYMBOLS THAT MIGHT BE LEGAL ARE:
           FOR <END-OF-STATEMENT> NOT ATOMIC
  
  
  2)  Executing line command 'I' (Interpret) on a WSL on panel
  ADBW1 may result in the following message:
  
  IBM0441W ONCODE=150 The STRINGSIZE condition was raised.
  From entry point _Concnvs at compile unit offset >offset< at
  entry offset >offset< at address >address<.
  From entry point TOKENIZE at statement 1100 at compile unit
  offset >offset< at entry offset >offset< at address >address<.
  
  Note: Statement numbers are approximate, and may vary somewhat,
          depending on maintenance applied.
  
  
  Keywords:  SQLCODE104N; ONCODE150; RC08
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 Object Comparison Tool for      *
  *                 z/OS.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Issue 1:                                *
  *                                                              *
  *                      A change to a trigger and its           *
  *                      associated view that results in the     *
  *                      view being dropped and recreated might  *
  *                      result in a work statement list (WSL)   *
  *                      that uses an incorrect delimiter.       *
  *                                                              *
  *                      Issue 2:                                *
  *                                                              *
  *                      ONCODE 150 occurs when interpreting a   *
  *                      WSL.                                    *
  *                                                              *
  *                      Issue 3:                                *
  *                                                              *
  *                      An exclude on a database that is masked *
  *                      results in a warning message number     *
  *                      that was previously used to mean        *
  *                      something else.                         *
  ****************************************************************
  Issue 1:
  
  The following error might occur when running a WSL that
  was created from an alter operation on a trigger combined
  with a change to its associated view that results in a drop
  and recreate of the view:
  DSNT408I SQLCODE = -104, ERROR:ILLEGAL SYMBOL ";".
  SOME SYMBOLS THAT MIGHT BE LEGAL ARE: FOR <END-OF-STATEMENT>
  NOT ATOMIC
  
  
  Issue 2:
  
  The following error might occur when interpreting a WSL that
  was generated from an alter operation on a trigger combined
  with a change to its associated view that results in a drop and
  recreate of the view:
  IBM0441W ONCODE=150 The STRINGSIZE condition was raised.
  From entry point _Concnvs at compile unit offset +00000062
  at entry offset +00000062 at address 274871D2.
  From entry point TOKENIZE at statement 1100 at compile unit
  offset +000014FC at entry offset +000014FC at address 2748343C.
  
  Note: Specific statement lines related to the ONCODE150 error
  might be different depending on the maintenance level.
  
  Issue 3:
  
  In the compare report of an exclude on a database that is also
  masked, message ADB7160W is used. However, this number was used
  previously for a different message. New message ADB7388W has
  been created for the message that inadvertently reused ADB7160W.
  

Problem conclusion

• The problems have been resolved.
  
  Search Keywords: MSGADB7387I, MSGADB7388W, MSGADB7160W
  

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:

  UI74747

Modules/Macros

• ADB2CMF  ADB2CMS  ADB7000
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RC10 PSY UI74747

     UP21/04/06 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.