Workload management stops
the creation of new server address spaces when one of the following
conditions exist:
- JCL errors in the procedure associated with the application
environment.
- Coding errors in the server code which cause five unexpected terminations
of server address spaces within ten minutes.
- Failure of the server address space to connect to workload management due to
an invalid invocation environment or invalid parameters.
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.
In STOPPED state, you can make changes to libraries, change the
procedure, or make any other changes needed to repair the condition
that caused workload management to
stop the application
environment.
When the problem is resolved, use the resume function to allow workload management to start
new servers. The application
environment enters
the RESUMING state, then the AVAILABLE state after all systems in
the sysplex have accepted the action.
Note: If you want to ensure all servers are restarted after a STOPPED
state, especially after the JCL procedure or libraries have been modified,
you should issue a quiesce function prior to the resume. This ensures
there are no servers remaining active that are using back-level information.