IT06129: DEFAULT SCHEMA NOT AUTOMATICALLY ADDED FOR DEPLOYABLE ESQL

APAR status

• Closed as program error.

Error description

• When using compiled and inlined ESQL, the ESQL compiler in the
  toolkit inserts the default, empty schema into the PATH
  automatically if it is not already present. However, when using
  deployable ESQL, the same processing is not performed by the
  runtime during deployment.
  
  This may result in deployment errors (such as a BIP2558E)
  showing undefined procedures or variables, which do not show
  as a problem in the toolkit.
  

Local fix

• The default schema can be added manually by the user to the
  PATH in the affected ESQL files. This can be achieved by adding
  the empty string "" to the list of schemas in the PATH
  statement.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus V9.0 who are deploying ESQL
  files in broker schemas other than the default, empty broker
  schema.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When using compiled and inlined ESQL (V7.0 and before), the ESQL
  compiler in the toolkit automatically adds the default/empty
  broker schema to the PATH. This allows procedures and modules in
  other broker schemas to resolve procedures in the default/empty
  broker schema without explicitly adding the default/empty broker
  schema to the PATH. The same behaviour is not observed when
  deploying ESQL files to the integration server. No ESQL errors
  are seen in the toolkit, but any procedures in the default/empty
  broker schema cannot be resolved during deployment, and the
  deployment fails.
  
  There are a number of resource name changes between WebSphere
  Message Broker and IBM Integration Bus Version 9.0. For details
  visit
  http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
  tools.mft.doc/bb23814_.htm
  

Problem conclusion

• The product now automatically adds the default/empty broker
  schema to the PATH to match the behaviour of the ESQL compiler
  in the toolkit used for compiled and inlined ESQL.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.0       9.0.0.4
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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

• Fixed component name

  INTEGRATION BUS

• Fixed component ID

  5724J0530

Applicable component levels

• R900 PSY

     UP