PK87024: DB2SCRIPTS ON ZOS TO BE FIXED

Fixes are available

APAR status

Closed as program error.

Error description

1. convertToDataSet.sh issues 3 "oget" commands that currently
fail :
tso -t "oget '$CURRENT_DIR/rm_db_cat.ddl' '$USERPDS(RMDDL5)'
CONVERT(YES)"
tso -t "oget '$CURRENT_DIR/fastpurge00.ctl'
'$USERPDS(PURGE00)' CONVERT(YES)"
tso -t "oget '$CURRENT_DIR/fastpurge01.ctl'
'$USERPDS(PURGE01)' CONVERT(YES)"

This due to the fact the 3 ddls are located in the
$CURRENT_DIR/ddl/rm_db_cat.ddl

For this to work fine we should modify convertToDataSet.sh to
point to the right location.

2. On short the issue is that setting the schema name
statement is present only in the ins_metadata.ddl (the script
that adds metadata records in some of the CEI tables). The
tables creation scripts does not contain this statement. So
there is the possibility for a user to create the tables under
the authority of one user to create the tables (in this user's
default schema) and try to insert the metadata in tables that
are set to exist in another schema.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  The issue may be seen by the Websphere      *
*                  Application Server users when configuring   *
*                  the Common Event Infrastructure with a DB2  *
*                  zSeries database in the scenario when       *
*                  Websphere Application Server and DB2        *
*                  database are located on the same machine.   *
****************************************************************
* PROBLEM DESCRIPTION: The problem may be encountered by the   *
*                      Common Event Infrastructure users       *
*                      that configure it with DB2 zSeries      *
*                      database in the particular scenario     *
*                      of Websphere Application Server being   *
*                      installed also on z/OS system. The      *
*                      issue is encountered at the install     *
*                      time when the remove catalog database   *
*                      and the fastpurge procedures are        *
*                      converted to datasets. No fatal error   *
*                      is encountered but the fastpurge        *
*                      procedures are not available at the     *
*                      runtime. The scripts responsible for    *
*                      tables creation were also modified to   *
*                      enforce setting the schema before the   *
*                      tables creation statements              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The script that performs the conversion to DataSets contains
statements that do not point correctly to the files
being loaded and therefore the "oget" command fails. However
only these three statements are affected and the rest of the
statements are correctly loaded and performed. That is this
not a fatal issue leading to a failure of the database process
execution.
convertToDataSet.sh issues 3 "oget" commands that currently
fail :
tso -t "oget '$CURRENT_DIR/rm_db_cat.ddl' '$USERPDS(RMDDL5)'
CONVERT(YES)"
tso -t "oget '$CURRENT_DIR/fastpurge00.ctl'
'$USERPDS(PURGE00)' CONVERT(YES)"
tso -t "oget '$CURRENT_DIR/fastpurge01.ctl'
'$USERPDS(PURGE01)' CONVERT(YES)"
There is a possible in some particular scenarios that tables
are created in a default schema whereas the metadata insertion
process is performed under another schema. If the granted
rights are not compatible the process is failing

Problem conclusion

The code that performs the loading of the DDL/DML to DataSets
was corrected to point to the right location to load the
statements and added the set schema statements in all
necessary places in the scripts, thus ensuring that the tables
and later references to them points to the exact table in the
specific schema where they were created.

APAR PK87024 is currently targeted for inclusion in Service
Level (Fix Pack) 7.0.0.5 of WebSphere Application Server V7.0
for z/OS.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PK87024
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-20
Closed date
2009-06-03
Last modified date
2009-08-03

APAR is sysrouted FROM one or more of the following:

PK85858
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R700 PSY UK48200
UP09/07/27 P F907

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.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK87024: DB2SCRIPTS ON ZOS TO BE FIXED

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY UK48200

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.

Document Information

Share your feedback

Need support?