|
Problem(Abstract) |
You can have a problem if you use an automation tool that
automatically starts your node agent after a nightly IPL.
The node agent starts completely, and you might receive messages
indicating initialization is complete. If you manually start the
Deployment Manager server the next morning, the server appears to
initialize completely; however, when attempting any action using the
administrative console (for example, starting or stopping a server), you
receive a message stating that "...the node agent on node xxxxxx is not
active." |
|
|
|
Cause |
The startup order of WebSphere® Application Server for
z/OS® v5 servers affects your ability to use certain servers. |
|
|
Resolving the
problem |
Reverse the order in which you start the servers.
Start the Deployment Manager server first, then start the node
agent.
|
|
|
|
|
|
|