PQ88249: POSTINSTALLER SHELL SCRIPT, PQ84492.SH, COMPLETES IN ERROR 04/04/30 PTF PECHANGE

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
The shell script, 
PQ84492.sh, introduced in W502005 may complete
in error.


PQ84492.sh is suppose to scan security.xml for "safkeyring:///"
and if not found and MD18076 (which sets "///") shows applied it
will rerun MD18076. For some reason the path name contains a
directory for cell SY1 instead of cell variable name $WAS_CELL
so it scans the wrong directory path:

"<WebSphere_Config_Directory>/cells/SY1/security.xml"
instead of:
"<WebSphere_Config_Directory>/cells/$WAS_CELL/security.xml"

i.e.:
This excerpt shows file not found error and RC=0:
<<< 
PQ84492.sh -  Begin -  Action=apply, Backup directory=
/apps/pt01/zwas/config/AppServer/properties/service/backup/W5020
05/PQ84492, Tue Apr 27 06:18:07 EDT 2004

iconv: FSUM6180 file
"/apps/pt01/zwas/config/AppServer/config/cells/SY1/security.xml"
:
EDC5129I
No such file or directory.

>>> 
PQ84492.sh - End - Return Code = 0, Action=apply, Backup
directory=/apps/pt01/zwas/config/AppServer/properties/service/ba
ckup/W502005/PQ84492,
 Tue Apr 27 06:18:10 EDT 2004

This error is caused due to the fact that the "/SY1/" listed in
the directory does not exist.  It should be the cell variable
name $WAS_CELL, so it is scanning the wrong directory for
security.xml.


PQ84492.sh script was introduced with W502005.  It may complete
in error at W502005, W502006, and W502007.  Please follow the
LOCAL FIX until the official PTF becomes available with the
corrected 
PQ84492.sh script.
Local fix

PQ84492.sh contains the following  :

# MD18076
# MD18076 changes "safkeyring://" to "safkeyring:///"
# If "safkeyring:///" is not found - rerun the script
count=$(iconv -f ISO8859-1 -t IBM-1047
$WAS_HOME/config/cells/SY1/security.xml  | grep -c
"safkeyring:///")

SY1 is hard coded as the cell name, but in general, if a
customer uses their own cell name (other than SY1) they will get
an error.
i.e.:
iconv: FSUM6180 file
"/apps/pt01/zwas/config/AppServer/config/cells/SY1/security.xml"
: EDC5129I No such file or directory.

'SY1' should be replaced by environment variable '$WAS_CELL'.

Customer may edit their current 
PQ84492.sh
OR
may call in to IBM support (or open PMR) to receive a fixed
version of the shell script, 
PQ84492.sh, which basically has
'SY1' replaced with '$WAS_CELL'.
If you need to run this shell script immediately and you are
already at W502005 or higher then in order to make applyPTF.sh
run this corrected version of the shell script you need to
follow the following steps.Incase you are below W502005 then all
you need to do is replace your current script with this one and
then come up in service.
.
You first need to setup to re-run the postinstall script. Go
into the following directory for your WAS_HOME,
/$WAS_HOME/properties/version/applied
.
If you do an 'ls' here you should see all the maintenance levels
you have applied, starting from W501xxx.ptf to W502xxx.ptf. Let
us assume you are W502006, so you should see all the levels
sequentially leading upto W502006.ptf.
.
In the directory
/$WAS_HOME/properties/version
.
You will see the latest maintenance you are at which in the case
of our example is W502006.ptf.
.
We want to run 
PQ84492.sh and this was a postinstall task of
W502005, so you need set these marker files back one level to
W502004 in order to get the postinstall execute 
PQ84492.sh. Here
is what you need to do,
.
1. Go into /$WAS_HOME/properties/version/applied and
   - Rename W502005.ptf to W502005.old
   - Rename W502006.ptf to W502006.old
2. Go into /$WAS_HOME/properties/version and
   - Rename W502006.ptf to W502006.old
   - Copy file /$WAS_HOME/properties/version/applied/W502004.ptf
     to directory /$WAS_HOME/properties/version
     So now in /$WAS_HOME/properties/version you should have
     W502004.ptf
.
3. Go into
   /$WAS_HOME/properties/service/backup/W502005/PQ84492
   If you do an 'ls' here you should see a file called
   defect.applied that is 0 bytes in size. Delete this file.
.
Note: Incase of Deployment Manager ND configuration you need to
execute these steps for ALL you WAS_HOME configurations.
.
At this time you need to start the applyPTF.sh script by
recycling the application server. This should run 
PQ84492.sh and
bring you upto W502006 again. Please contact level 2 incase of
any questions regarding this process.
.
Note: These steps only apply to the local fix for this apar and
should not be used to rerun anything else.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: With the application of Severice level  *
*                      W502005 (PTF UQ86666), during           *
*                      postinstall processing, the postinstall *
*                      shell script 
PQ84492.sh ends with the   *
*                      following error message:                *
*                      <was_home>/config/cells/SY1/security.   *
*                      xml                                     *
*                      EDC5129I No such file or directory      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The path to the security.xml file was coded in the postinstall
script as $WAS_HOME/config/cells/SY1/security.xml instead of
$WAS_HOME/config/cells/$WAS_CELL/security.xml
Problem conclusion

PQ84492.sh was changed to use the environment variable $WAS_CELL
instead of the directory name SY1. In addition, a new
postinstall script has been provided which ensures the
processing of 
PQ84492.sh has occurred successfully.

APAR PQ88249 is associated with SERVICE LEVEL W502008 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ88249
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE YesPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-04-30
Closed date 2004-05-07
Last modified date 2004-05-13

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ88257    UP04/05/13 I 1000

  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


Current web document: swg1PQ88249.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ88249
IBM Group: Software Group
Modified date: May 13, 2004