PQ99401: AUTOMATICALLY STARTING A SERVER WHEN THE NODEAGENT STARTS FAILS IN CERTAIN CONFIGURATIONS

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
After setting a server to be automatically started when the
node agent for that server is started (via the admin console:
Servers > Application Servers > <srvName> > Process Definition >
Control > Monitoring Policy and set Node restart state to
'RUNNING') and setting the node agent process to synchronize
automatically when a server process it governs is started (again
via the admin console: System Administration > Node agents >
<nodeagent> > File Synchronization Service, and check 'Startup
Synchronization'), the server set to automatically start will
not do so.
Local fix
Disable automatic synchronization on startup of server
processes under the node agent via the admin console.  Servers
will still start automatically, but no synchronization will be
done before their initialization.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: WebSphere Application Server fails to   *
*                      start during NodeAgent startup when     *
*                      the NodeSync attribute                  *
*                      syncOnServerStartup is set.             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When NodeSync attribute "syncOnServerStartup" is set then the
NodeAgent will attempt sync node prior to starting a server.
In the case where a NodeAgent is restarting and the policy is
set for it to restart running servers (e.g. restartState=
RUNNING), process discovery between the dmgr and nodeagent may
not be complete by the time the NodeAgent begins launching
processes.
This means that node sync operation will fail and the server
startup will be aborted.
Problem conclusion
This fix will ensure that the NodeAgent is connected to the
Deployment Manager prior to node sync.

APAR PQ99401 is associated with SERVICE LEVEL W502022 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ99401
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 2005-01-12
Closed date 2005-01-21
Last modified date 2005-02-01

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOUBINF          

Publications Referenced

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

Applicable component levels
R500 PSY UQ97067    UP05/01/26 P F501

  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: swg1PQ99401.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 #: PQ99401
IBM Group: Software Group
Modified date: Feb 1, 2005