Wonder why WebSphere Application Server address spaces on zOS won't start sometimes with V WLM, RESUME?
SridharTalluri 270002PT0P Visits (7104)
In a WebSphere Application Server zOS environment, workload management stops the creation of new server address spaces when one of the following conditions exist:
The application environment first enters the STOPPING state, then the STOPPED state after all systems in the sysplex have accepted the action.
In STOPPED state, no new servers are created. Any existing server address spaces continue to process work, and workload management is able to accept new work. If there are no existing servers, then workload management rejects any new work requests.
The STOPPED dynamic application environment of the WebSphere Application Server can be started by issuing the VARY WLM RESUME console command.
Now this doesn't start the WebSphere address spaces if there is no new work queued to this application environment.
You will need to issue the WLM QUIESCE and then RESUME for the application environment which in turn causes WLM to start the Application Server address spaces.
WLM mechanics on why this happens..
Also, the MVS Planning: Workload Management manual (SA22-7602-18) also specifies the following to reiterate and confirm the logic.
Many thanks to Dianne Gamarra from WLM for her invaluable insight on this behavior.