Table Of Contents
Operating the Cisco Workload Agent for OS/390
Starting the Cisco Workload Agent for OS/390
Stopping the Cisco Workload Agent for OS/390
Performing an Orderly Shutdown
Display Agent Database Information
Agent Database Display Command
Operating the Cisco Workload Agent for OS/390
This chapter describes how to operate the Cisco Workload Agent for OS/390, including:
•
Starting the Cisco Workload Agent for OS/390
•
Stopping the Cisco Workload Agent for OS/390
Starting the Cisco Workload Agent for OS/390
Step 1
Review NSPWGO, updated during the installation process, and verify that the configuration member is specified correctly. See the "Allocating NSPWGO" section on page 2-18 for more details.
Step 2
Submit job NSPWGO to execute the Cisco Workload Agent for OS/390.
Step 3
Messages are issued indicating that the Cisco Workload Agent for OS/390 initialized successfully.
The following example shows sample display output for starting an Cisco Workload Agent for OS/390:
IEF403I WLA - STARTED - TIME=12.35.32NSPW0001I 1 Cisco Workload Agent for OS/390 1.0.0B started on Wed Feb 23 17:35:33 2000NSPW0002I 1 Copyright (C) 2000 Cisco Systems, Inc.NSPW0003I 1 Cisco Workload Agent for OS/390 JobID:WLA ASCB:F9AE80 ASID:22 ICAG:212A8NSPW0004I 1 Cisco Workload Agent for OS/390 CPU:9672 SYSID=MVS001 MVS:SP6.0.8NSPW0020I 1 Cisco Workload Agent for OS/390 initialization startingNSPW0030I 22 Processing of Exec Parms started 824NSPW0031I 22 Parm:"CNFG=AGENT"NSPW0038I 22 Exec Parm Processing Completed SuccessfullyNSPW0040I 21 Processing of Config file:AGENT started 825NSPW0048I 21 Processing of Config file:AGENT completed successfullyNSPW0040I 23 Processing of Config file:MAP started 826NSPW0048I 23 Processing of Config file:MAP completed successfullyNSPW0021I 1 Cisco Workload Agent for OS/390 initialization successfulStopping the Cisco Workload Agent for OS/390
Step 1
Issue the operator command P jobname from the operator's console, where jobname is the identifier of the batch job or task to be stopped.
Step 2
Messages are issued indicating that the Cisco Workload Agent for OS/390 stopped successfully.
The following example shows sample display output for stopping an Cisco Workload Agent for OS/390:
P WLANSPW0053I 1 "STOP" command requested by OperatorNSPW0051I 1 Cisco Workload Agent for OS/390 Termination in progressNSPW0052I 1 Cisco Workload Agent for OS/390 Termination CompleteUsing Operator Commands
The following is a list of operator commands you can use to control the Cisco Workload Agent for OS/390 and display information regarding the status of WLM registration.
Use the standard operator modify `F' and stop `P' interfaces to communicate with the Cisco Workload Agent for OS/390.
Performing an Orderly Shutdown
This command directs the Cisco Workload Agent for OS/390 to stop a job.
P jobname
Syntax Description
Examples
The following example stops job NSPWGO:
P NSPWGODisplay Agent Database Information
This command displays the Agent database information. Keyword parameters are not required.
F jobname,WLM, [Group=[groupname|group_mask|*]|Port=[port_number,count=number_of_ports|*]]
Syntax Description
Defaults
Group default: * (display information for all groups)
Port default: * (display information for all ports)
Count default: 1 (display information for the single port specified)
Create a WLM Registry
This command creates a WLM registry (a database that contains system configuration information) and allows legacy applications and TCP/IP stacks to participate in load balancing. HOST, GROUP, and SERVICE uniquely identify a registration to the WLM and to the Cisco Workload Agent for OS/390. The groupname keyword must be configured in the Service Mapping Configuration member.
![]()
Note
Registering for applications running on OS/390 systems other than the current system allows those applications to participate in load balancing, but distorts the WLM weights slightly. Instead, register on the system where the application is running for accurate WLM weighting.
F jobname,REGister,[HOSt=host_name,[IP=(ipaddr)]],[GROup=groupname],[SERvice=ins tance]
Syntax Description
Examples
The following example shows sample display output for creating a WLM registry:
F WLA,REGISTER,HOST=MVS001,GROUP=WEB,SERVICE=MVS001NSPW0068I 13 Operator Command:REGISTER,HOST=MVS001,GROUP=WEB,SERVICE=MV865F WLA,WLMNSPW0310I 14 Display DFP Agent WLM 868NSPW0311I 14 Cluster:80.80.254.3 VIPA:80.80.254.3NSPW0312I 14 Group:WEB Port:80NSPW0313I 14 Host:MVS001NSPW0314I 14 Protocol:TCP Instance:MVS001 Netid:NSPW0315I 14 WLM Wt:01 DFP Wt:00NSPW0312I 14 Group:TN32702 Port:24NSPW0312I 14 Group:TN3270 Port:23NSPW0313I 14 Host:MVS001NSPW0314I 14 Protocol:TCP Instance:mvs001 Netid:NSPW0315I 14 WLM Wt:01 DFP Wt:00NSPW0312I 14 Group:FTP Port:21NSPW0319I 14 End DFP Agent DisplayNSPW0068I 13 Operator Command:WLM Completed Successfully 869NSPW0052I 1 Cisco Workload Agent for OS/390 Termination CompleteDeregister a WLM Registry
This command deregisters a WLM registry previously specified with a Register command. HOST, GROUP, and SERVICE uniquely identify a registration to the WLM and to the Cisco Workload Agent for OS/390.
![]()
Note
If a deregister is not performed when the Cisco Workload Agent for OS/390 stops, OS/390 automatically deregisters with the WLM.
F jobname,DERegister,[HOSt=host_name], [GROup=groupname],[SERvice=service_name]
Syntax Description
Examples
The following example shows sample display output for deregistering a WLM registry:
F WLA,DEREGISTER,HOST=MVS001,GROUP=WEB,SERVICE=MVS001NSPW0068I 13 Operator Command:DEREGISTER,HOST=MVS001,GROUP=WEB,SERVICE=875External Tracing
This command toggles external log tracing on or off.
F jobname,LOGTRACE={OFF|ON}
Syntax Description
Using Debugging Tools
The following sections describe the diagnostic tools for use with the Cisco Workload Agent for OS/390:
•
Agent Database Display Command
LOGTRACE Command
You can enable the LOGTRACE feature by editing the Cisco Workload Agent for OS/390 configuration file, or by using the LOGTRACE command. When LOGTRACE is on, it generates two logs, SYSPRINT, which contains logging messages, and SYSOUT, which contains error messages.
SYSPRINT records both normal and error events. SYSPRINT reports on initialization, application and stack registration and deregistration with the WLM, timer pops, socket-related events, Services Manager connection and disconnection, error events with the protocol manager, and operator commands and their output.
SYSOUT records only error conditions. Error messages are displayed with a time stamp prefix.
See the "External Tracing" section for command syntax and other details.
Agent Database Display Command
The Agent Database Display command (F jobname WLM) lets you know which applications and stacks are currently registered with the WLM and are currently participating in load balancing.
See the "Display Agent Database Information" section for command syntax and other details.
SVC Dumps
An SVC dump provides a representation of the virtual storage for the system when an error occurs. SVC dumps are created for ABEND events, and are used to help solve problems. For more information about SVC dumps, refer to OS/390 V2R5.0 MVS Diagnosis: Tools and Service Aids, SY28-1085.