JR44235: DDL FOR DATA MOVEMENT SERVICE FAILS TO EXPORT CORRECTLY FOR DB2 IF MONITORING CONTEXT WIDTH IS GREATER THAN 31,900 BYTES

IBM Business Monitor development toolkit V8.0 Refresh Pack 1 (8.0.1)
IBM Business Monitor development toolkit V8.0.1 Fix Pack 1 (8.0.1.1)
IBM Business Monitor V7.5.1 Fix Pack 2 (7.5.1.2)

APAR status

• Closed as fixed if next.

Error description

• When database scripts are exported for a monitor model from
  the administrative console, the DDL files that create the
  database artifacts for the Data Movement Service on DB2 and
  DB2 for z/OS, respectively, are not generated correctly if the
  "width" of the database table for a monitoring context (the
  total width of the columns in the table) is greater than
  31,900 bytes.
  
  Executing the script against the database fails because
  the SQL statement that creates the "reporting" table for the
  monitoring context table (where instance data is moved by the
  Data Movement Service, from the "operational" table) is not
  properly terminated.  An example of such a statement starts as
  shown below:
  
  CREATE TABLE MYMODEL.TGT_MYMC_20121001000000
  
  The CREATE INDEX statement that follows is considered part of
  the CREATE TABLE statement, resulting in a syntax error when
  the statement is executed.
  

Local fix

• Workaround:
  
  1. In the generated J2EE application project (in the monitor
  model editor), open the following files:
  
     root/META-INF/dms/db2/EnableDMS.ddl
     root/META-INF/dms/db2zOS/EnableDMS.ddl
  
  2. Ensure that all CREATE TABLE statements contain ") IN
  DMSTS32K@" (specifically, CREATE TABLE statements for tables
  including "TGT_*" or "ERR_*" in the name.
  
  3. Save the file and export the EAR file.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of WebSphere Business Monitor         *
  *                  Versions 6.2 and 7.0, and IBM Business      *
  *                  Monitor Versions 7.5 and 8.0.               *
  ****************************************************************
  * PROBLEM DESCRIPTION: When database scripts are exported      *
  *                      for a monitor model from the            *
  *                      administrative console, the DDL         *
  *                      files that create the database          *
  *                      artifacts for the Data Movement         *
  *                      Service on DB2 and DB2 for z/OS,        *
  *                      respectively, are not generated         *
  *                      correctly if the "width" of the         *
  *                      database table for a monitoring         *
  *                      context (the total width of the         *
  *                      columns in the table) is greater than   *
  *                      31,900 bytes.                           *
  *                      Executing the script against the        *
  *                      database fails because the SQL          *
  *                      statement that creates the              *
  *                      "reporting" table for the               *
  *                      monitoring context table (where         *
  *                      instance data is moved by the           *
  *                      Data Movement Service, from the         *
  *                      "operational" table) is not             *
  *                      properly terminated.  An example of     *
  *                      such a statement starts as shown        *
  *                      below:                                  *
  *                      CREATE TABLE                            *
  *                      MYMODEL.TGT_MYMC_20121001000000         *
  *                      The CREATE INDEX statement that         *
  *                      follows is considered part of the       *
  *                      CREATE TABLE statement, resulting in    *
  *                      a syntax error when the statement is    *
  *                      executed.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  For DB2 and DB2 on z/OS only, the code that generates the
  database scripts for Data Movement Services imposes an
  unnecessary limitation of 31,900 bytes on the width of the
  monitoring context.  The monitor model editor already ensures
  that no monitoring context for a generated model exceeds the
  width of the tablespace in which the tables are created
  (32,768 bytes).
  This problem has been fixed in IBM Business Monitor Version
  8.0.1.
  

Problem conclusion

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:

Fix information

Applicable component levels

• R620 PSY

     UP

• R700 PSY

     UP

• R750 PSY

     UP