APAR status
Closed as program error.
Error description
When zpmt.sh runs, it creates a targetRelativeDir with a TIMESTAMP qualifier to try and make it unique. This gets used in the in the HLQ.CNTL(BBOWCFS) dataset as well as others: BPXBATCH SH /usr/lpp/WebSphere/AppServer/V9R0+ /bin/zInvokeCustomizationScript.sh + -sourcePDS BOSS.BOSS0241.ZMPT1.DATA + -targetRelativeDir com.ibm.ws390.pmt.28180157.BBOWCFS + -sourceMembers BBOWCFS + -targetFiles bbowcfs.sh The TIMESTAMP consists of the date/hour/min/sec the time was run: <date>2021-06-28T18:01:57</date> TIMESTMP=28180157 When 2 zpmt jobs are run at the same time, the TIMESTMP value is the same. This APAR will make the TIMESTMP value more unique by adding milliseconds to it.
Local fix
do not run 2 zpmt.sh jobs at the same second
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * * V9.0. * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS * * zpmt.sh did not generate a unique * * directory path for -targetRelativeDir * **************************************************************** * RECOMMENDATION: * **************************************************************** The zpmt.sh is invoked to generate JCL jobs (using the - transfer -allocate parameters) to customize a WebSphere environment. Some of the generated jobs contain invocations of scripts using a generated path name for the -targetRelativeDir parameter. Within this generated name is a "timestamp" value in a form that is unique down to the seconds within a single day. The following is an example where the fourth qualifier is generated from a current "timestamp" value: -targetRelativeDir com.ibm.ws390.pmt.28180157.BBOWCFS If the zpmt.sh is driven concurrently it is possible that the same value will be used for the concurrent sets of output JCL jobs. This would lead to failures in the submission of these sets of customization jobs.
Problem conclusion
Code has been modified in the path that creates the parameter value for the "timestamp" qualifier for zpmt.sh parameter -targetRelativeDir. The change is to make it more unique to significantly reduce the chance of a collision with other invocations of the zpmt.sh script. The fix for this APAR is targeted for inclusion in fix pack 9.0.5.10. For more information, see 'Recommended Updates for WebSphere Application Server': https://www.ibm.com/support/pages/node/715553
Temporary fix
Comments
APAR Information
APAR number
PH39056
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-07-16
Closed date
2021-08-04
Last modified date
2021-08-04
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
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
[{"Line of Business":{"code":"LOB45","label":"Automation"},"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":"900"}]
Document Information
Modified date:
05 August 2021