![[z/OS]](../images/ngzos.gif)
Where to perform WebSphere Application Server operations
Administering WebSphere® Application Server involves the use of both the MVS™ console and the WebSphere Application Server administrative console.
For example:
- Use MVS commands issued from the MVS console to start the base Application Server control region, the network deployment node agent, and the deployment manager.
- In a base Application Server configuration, you must start the first server with an MVS operator command.
- In a network deployment configuration, after the deployment manager and node agent are active, you can use the administrative console to start and stop application servers.
- Workload management starts all servants using Address Space Create (ASCRE).
The following table lists the main Application Server operations
tasks and directs you to information that helps you to perform these
tasks. The Application Server activities and operations can be performed
from:
- A z/OS® MVS console (most operations)
- The Application Server administrative console (some operations)
- Telnet client, such as TeraTerm, Putty, or the Microsoft Windows telnet client
TSO/ISPF resource recovery services (RRS) panels can be used to display units of work for RRS, and units of work for CICS®. See z/OS MVS Programming: Resource Recovery at http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi for more information about using RRS panels.
Task | MVS console | Application Server administrative console | Telnet client | Reference to associated procedure |
---|---|---|---|---|
Start operations | ||||
Starting the Application Server environment and location service daemon | Yes | No | No | See Starting servers. |
Starting a cluster or application server | Yes | Yes | Yes | See Starting clusters, Starting servers, and Using the administrative console. |
Stop operations | ||||
Stopping the location service daemon | Yes | No | No | See Steps for stopping or canceling the location service daemon from the MVS console . |
Stopping a cluster | Yes | Yes | Yes | See Stopping clusters. |
Stopping an application server | Yes | Yes | Yes | See Stopping servers. |
Cancel operations | ||||
Canceling the location service daemon | Yes | No | No | See Steps for stopping or canceling the location service daemon from the MVS console. |
Canceling a cluster | Yes | Yes | Yes | See Stopping clusters. |
Canceling an application server | Yes | Yes | Yes | See Stopping servers. |
Display operations | ||||
Displaying the status of ARM-registered address spaces including clusters and servants | Yes | No | No | See the topic on displaying the status of ARM-registered address spaces. |
Displaying units of work (threads) for DB2® | Yes | No | No | See DB2 Universal Database for z/OS Command Reference athttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi. |
Displaying indoubt units of work (threads) for DB2 | Yes | No | No | See DB2 Universal Database for OS/390® and z/OS Command Reference athttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi. |
Displaying units of work for RRS | No | No | No | See z/OS MVS Programming: Resource Recovery at http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi. |
Displaying units of work for CICS | Yes | No | No | See CICS Operations and Utilities Guide at http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi |
Displaying the status of a cluster | Yes | Yes | Yes | See "Example: Displaying status of clusters" in Display command with examples. |
Displaying the status of a server | Yes | Yes | Yes | See the example for displaying status of a server in Display command with examples. |
Displaying active address spaces | Yes | No | No | See the example for displaying active address spaces in Display command with examples. |
Displaying outstanding replies | Yes | No | No | See the example for displaying active replies in Display command with examples. |
Modify operations | ||||
Getting help for the modify command | Yes | No | No | See the example for getting help for the modify command in Modify command. |
Canceling application clusters and servers | Yes | Yes | No | See Modify command. |
Modifying the Java™ trace string | Yes | Yes | Yes | |
Displaying status | Yes | Yes | No | See Modify command. |
Other Application Server operations | ||||
ARM and restart | Yes | No | No | See the topic on activating automatic restart management. |
Setting up error log streams for different clusters and servants | No | You can associate a log stream with a cluster from the administrative console | No | See Setting up the error log. |
Setting up System Management Facilities recording | Yes | You can turn SMF recording on or off, and then stop and restart the server. | No | See Collecting job-related information with System Management Facility (SMF). |
Shutting down the WebSphere Application Server for z/OS environment | Yes | No | No | See Stopping clusters, Stopping servers, and Steps for stopping or canceling the location service daemon from the MVS console. |
Taking part of a sysplex out of service | Yes | No | No | |
Workload Management | ||||
Displaying the status of a WLM application environment | Yes | No | No | See the topic on handling workload management and server failures. |
Handling workload management and server failures | Yes | No | No See the topic on Handling workload management and server failures. | See the topic on handling workload management and server failures. |
Getting out of the stopped state and back to the available state for an application environment | Yes | No | No | See the topic on handling workload management and server failures. |
Checking and managing the workload management application environment (display, stop/quiesce, restart/resume) | Yes | No | No | See the topic on handling workload management and server failures. See WLM dynamic application environment operator commands. |