PQ79433: CHARACTER LIMIT FOR PARM IN BBO5ACR MAY BE EXCEEDED & IEF642I ERROR MAY RESULT CAUSING SERVER START TO FAIL AFTER W501000.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
IEF642I error may be encountered when bringing up the node agent
or server after performing HOLD ACTIONS of running postInstall
script & regenerating the procs which causes the procs to be
updated with the following line,
.
// PARM='SH &ROOT./&ENV./../../../../../../../bin/applyPTF.sh
inline'
.
The &ROOT and &ENV are replaced with the actual values when the
server or nodeagent are started. If this exceeds 100 characters
the following error results and the server fails to start,
.
IEF642I EXCESSIVE PARAMETER LENGTH IN THE PARM FIELD
Local fix
This local fix may work for some customers.  There are no
side effects if it does not work.  If it does not work, please
undo this change and contact WebSphere L2 Service for further
assistance.
.
Add a WASHOME env var to your procs (BBO5ACR & BBO5DCR), the
default value is,
.
// SET WASHOME='/WebSphere/V5R0M0/AppServer'
.
Replace &ROOT in with &WASHOME in the first 3 occurrences,so it
will be.
.
// PARM='SH &WASHOME./bin/applyPTF.sh inline'
//STDERR   DD PATH='&WASHOME./&FOUT.',
//STDERR   DD PATH='&WASHOME./&FOUT.',
.
Restart the server.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: Post-installer will fail to start if    *
*                      the parm length in BBO5ACR exceeds 100  *
*                      characters.                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Currently, in the dialog generated JCL BBO5ACR, we have the
the following:

//BBO5ACR  PROC ENV=,PARMS=' ',Z=BBO5ACRZ
// SET ROOT='/WebSphere/V5R0M0'
// SET FOUT='properties/service/logs/applyPTF.out'
//APPLY   EXEC PGM=BPXBATCH,REGION=0M,
// PARM='SH &ROOT./&ENV./../../../../../../../bin/applyPTF.sh
         inline'
//STDOUT   DD PATH='&ROOT./&ENV./../../../../../../../&FOUT.',
// PATHOPTS=(OWRONLY,OCREAT,OAPPEND),PATHMODE=(SIRWXU,SIRWXG)
//STDERR   DD PATH='&ROOT./&ENV./../../../../../../../&FOUT.',
// PATHOPTS=(OWRONLY,OCREAT,OAPPEND),PATHMODE=(SIRWXU,SIRWXG)
//BBOCTL  EXEC PGM=BBOCTL,COND=(8,EQ),REGION=0M,TIME=MAXIMUM,
// PARM='TRAP(ON,NOSPIE),ENVAR("_EDC_UMASK_DFLT=007") / &PARMS.'
//BBOENV DD PATH='&ROOT/&ENV/was.env'
// INCLUDE MEMBER=&Z

However, if the expanded PARM (on the fifth line) exceeds
100 characters, then it results with the following error
and the server fails to start,

IEF642I EXCESSIVE PARAMETER LENGTH IN THE PARM FIELD
Problem conclusion
To correct this, the transformer has been updated to create a
link <cell>.<node>.<server>.HOME point to it's WAS HOME.

For example:

/WebSphere/V5R0M0/CELL.NODE.SERVER.HOME ->
         /WebSphere/V5R0M0/AppServer

/WebSphere/V5R0M0/CELL.NODE.SERVER.HOME ->
        /WebSphere/V5R0M0/DeploymentManager

All dialog skeletons using the &ENV and relative path will be
updated to use the new link above to reduce the number of
characters in the PARM field.

With this change the PARM field will not exceed 100 characters.
The new BBO5ACR will look like this:

//BBO5ACR  PROC ENV=,PARMS=' ',Z=BBO5ACRZ
// SET ROOT='/WebSphere/V5R0M0'
// SET FOUT='properties/service/logs/applyPTF.out'
//APPLY   EXEC PGM=BPXBATCH,REGION=0M,
// PARM='SH &ROOT./&ENV..HOME/bin/applyPTF.sh inline'
//STDOUT   DD PATH='&ROOT./&ENV..HOME/&FOUT.',
// PATHOPTS=(OWRONLY,OCREAT,OAPPEND),PATHMODE=(SIRWXU,SIRWXG)
//STDERR   DD PATH='&ROOT./&ENV..HOME/&FOUT.',
// PATHOPTS=(OWRONLY,OCREAT,OAPPEND),PATHMODE=(SIRWXU,SIRWXG)
//BBOCTL  EXEC PGM=BBOCTL,COND=(8,EQ),REGION=0M,TIME=MAXIMUM,
// PARM='TRAP(ON,NOSPIE),ENVAR("_EDC_UMASK_DFLT=007") / &PARMS.'
//BBOENV DD PATH='&ROOT/&ENV/was.env'
// INCLUDE MEMBER=&Z


Here's the length analysis:

// PARM='SH &ROOT./&ENV..HOME/bin/applyPTF.sh inline'

'SH ' = 3 chars
&ROOT. = up to 41 chars (limited by what the user can enter on
the dialog panel)
/&ENV..HOME/= up to 33 chars,  since &ENV.= up to 26 chars
bin/applyPTF.sh inline=  22 chars

Total= 3+ 41+33+22 = 99 chars

Maximum parm string length is less than 100..

APAR PQ79433 is associated with SERVICE LEVEL W502000 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ79433
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-10-09
Closed date 2003-12-07
Last modified date 2006-02-28

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 UQ82900    UP03/12/15 P F312

  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: swg1PQ79433.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 #: PQ79433
IBM Group: Software Group
Modified date: Feb 28, 2006