|
This chapter describes how to start, stop, and use the mainframe application. It contains these major sections:
You can start the mainframe application as a batch job or as a started task.
To start the mainframe application as a started task (an MVS task that is started with a START (S) command), copy the prefix.NSPS210I.NSPSSAMP(NSPOPEN) procedure into the started tasks library, modifying the data set names according to the instructions at the top of the job. Start the NSPOPEN procedure from an MVS console with the S NSPOPEN command.
To start the mainframe application as a batch job, modify and submit the JCL in prefix.NSPS210I.NSPSSAMP(NSPJCL).
To stop the mainframe application, enter the following command from the operator console:
F NSPOPEN,STOP
If the application does not stop, enter the command again.
When the mainframe program starts, it also starts a number of subtasks, depending on how you have configured the mainframe application. Table 5-1 lists the subtasks that can be started.
Subtask ID | Purpose | Occurrences |
---|---|---|
DISCOVER | Discovers the PUs and LUs in the network. | 1 |
MVS | Retrieves MVS messages. | 1 |
PPI | Supports the NetView or SOLVE:Netmaster program-to-program interface; lets the workstations receive solicited and unsolicited VTAM messages. | 1 |
PPO | Lets the workstations receive unsolicited VTAM messages. | 1 |
SERVER | Provides LU 6.2 connection to workstations; one occurrence for each workstation connected by LU 6.2. | 0-10 |
SPO | Supports secondary program operators. | 0-15 (0 means that no workstations can enter VTAM commands) |
STATUS | Reports changes in the status of PUs and LUs to the workstations | 1 |
TCP | TCP/IP connection to a workstation; one occurrence for each workstation connected by TCP/IP | 0-20 |
You can enter the mainframe commands shown in Table 5-2 from any defined MVS console or extended MVS console, including NetView and SOLVE:Netmaster.
Command | Description |
---|---|
../../../../../../../lib/help.htm | Displays command help information. |
Starts a defined subtask. | |
Stops a defined subtask. | |
Displays all subtasks memory addresses. | |
Displays the TCP/IP address of each Workstation client connected by TCP/IP. | |
Displays the Media Access Control (MAC), service access point (SAP), and Routing Information Field (RIF) data for a PU name. | |
Displays the number of messages in the input and output queues for each subtask. | |
Displays the number of used and available buffers on the FREE queue for each subtask. | |
Displays the name and status of each subtask. | |
Displays the current settings for the TRACE command. | |
Displays the current version information. | |
Stops the mainframe task and its subtasks. | |
Starts and stops tracing in the mainframe subtasks |
The HELP command displays the list of mainframe commands.
Command Syntax
Example
To display the list of mainframe commands, enter the following command:
F NSPOPEN,help
Sample Output
NSP595 Command Entered: HELP
FILTER ADD msgid - Adds a message filter
FILTER DEL msgid - Deletes a message filter
HELP - Display this list
INIT- Activate a defined subtask
KILL- Terminate a defined subtask
MESSAGES- Control mainframe messages
SHOW ADDR- Display the important memory addresses
of each subtask
SHOW CONN- Display the client information for the
TCP subtasks
SHOW DLC puname- Display the mac, sap, and rif
information for a pu
SHOW FILTER- Display all defined message filters
SHOW FLOW- Display task message flow
information
SHOW FREEQ- Display task free queue
SHOW MESSAGES- Display the MESSAGES value
SHOW TASK- Display all subtasks and their status
SHOW TRACE- Display all subtasks and their traces
SHOW VERSION- Display the compiled date and time
of each subtask, and product version
STOP- Shutdown Sna Host
NSP695SNA Host HELP command processed
The INIT command starts a mainframe subtask that is already defined in the NSPPARM configuration file. When you start a subtask, automatic restarts are enabled for that subtask.
Command Syntax
Where:
subtask_name is the name of the mainframe subtask that you want to start. Use the F NSPOPEN,SHOW TASK command to display a list of subtasks by name.
Example
To start subtask TCP-0, enter the following command:
F NSPOPEN,INIT TCP-0
Sample Output
NSP595 Command entered: INIT TCP-0
The KILL command stops a mainframe subtask. The mainframe application then displays a message to remind you that the automatic restart has been disabled for the subtask that you are killing. The status of the subtask is changed to DOWN. The INPUTQ and OUTPUTQ values are invalid when a subtask is in the DOWN state and should be ignored. You can restart the subtask with the INIT command.
Command Syntax
Where:
subtask_name is the name of the subtask to be killed. Use the F NSPOPEN,SHOW TASK command to display a list of subtasks by name.
Example
To kill subtask TCP-0, enter the following command:
F NSPOPEN,KILL TCP-0
The SHOW ADDR command displays the memory addresses of the internal header control block, subtask control block, and MVS task control block for each mainframe subtask. This command is for problem diagnosis only.
Command Syntax
Example
To display the mainframe subtask memory addresses, enter the following command:
F NSPOPEN,SHOW ADDR
Sample Output
NSP595 Command entered: SHOW ADDR
NSP603 TNUM TASKNAME ADDRESS HEADER TCB
NSP603 0 MAINTASK 00000000 09259E88 00000000
NSP603 1 DISCOVER-0 0922F318 09253E88 008DD6D0
NSP603 2 MVS0922F338 092685C8 008DD388
NSP603 3 PPI 0922F358 0926ADC8 008D6A88
NSP603 4 STATUS-0 0922F378 0928AE88 008D6858
NSP603 5 SERVER-0 0922F398 092B6608 00000000
NSP603 7 TCP-0 0922F3D8 09346608 008BEE88
NSP603 8 TCP-1 0922F3F8 0934A608 008D5E88
NSP603 9 CMD-0 0922F418 0934D5C8 008C0A88
NSP603 10 SPO-0 0922F438 0944AE88 008C0858
NSP695 SNA Host SHOW command processed
Table 5-3 describes the fields in the SHOW ADDR command output.
Field | Meaning |
---|---|
Subtask number. | |
Subtask name. | |
Address of subtask control block for this subtask. | |
Address of subtask header. | |
Task control block address. |
The SHOW CONN command displays the TCP/IP addresses (or host names) of the client workstations that are connected via TCP/IP.
Command Syntax
Example
To display the TCP/IP connections, enter the following command:
F NSPOPEN,SHOW CONN
Sample Output
NSP595 Command entered: SHOW CONN
NSP706 TNUM TASKNAME SPECIFIC CLIENT
NSP706 7 TCP-0 6506,6507 NO CONNECTION
NSP706 8 TCP-1 6516,6517 171.69.163.115
NSP695 SNA Host SHOW command processed
Table 5-4 describes the fields in the SHOW CONN command output.
Field | Meaning |
---|---|
TNUM | Subtask number. |
TASKNAME | Subtask name. |
TCP/IP port numbers. | |
IP address of connected workstation. NO CONNECTION = no workstation connected. |
The SHOW DLC command displays the MAC, SAP, and RIF data for any switched PU name.
Command Syntax
Where:
PU_name is the name of any switched PU.
Example
To display the MAC, SAP, and RIF data for PU IBUPC1, enter the following command:
F NSPOPEN,SHOW DLC IBUPC1
Sample Output
NSP595 Command entered: SHOW DLC IBUPC1
NSP708 IBUPC1 05DAA011 400137451088 04 0000F6419B36 04
NSP710 0A30A0441F42055
NSP695 SNA Host SHOW command processed
Table 5-5 describes the fields in the SHOW DLC command output.
Field | Meaning |
---|---|
IBUPC1 | PU name. |
05DAA011 | |
400137451088 | |
04 | Local SAP. |
0000F64190B36 | Remote MAC. |
04 | Remote SAP. |
0A30A0441F42055 |
The SHOW FLOW command displays information about the messages for each subtask. The output from the SHOW FLOW command is for use by the Cisco TAC.
Command Syntax
Example
To display the messages in the input and output queues, enter the following command:
F NSPOPEN,SHOW FLOW
Sample Output
NSP595 Command entered: SHOW FLOW
NSP605 TNUM TASKNAME INPUTQ OUTPUTQ INFLOWOUTFLOWMC
NSP605 1 DISCOVER-0 0 0 00 0
NSP605 2 MVS 0 0 23402340 3
NSP605 3 PPI 0 0 00 0
NSP605 4 STATUS-0 0 0 26 26 0
NSP605 5 SERVER-0 0 0 0 0 0
NSP605 7 TCP-0 0 0 0 0 0
NSP605 9 CMD-0 0 0 9419 0
NSP605 10 SPO-0 0 0 33 0
NSP695 SNA Host SHOW command processed
Table 5-6 describes the fields in the SHOW FLOW command output.
Field | Meaning |
---|---|
Subtask number. | |
Subtask name. | |
Number of message buffers queued to the main task by this subtask. | |
Number of message buffers queued to this subtask for processing. | |
Number of message buffers processed by this subtask. | |
Number of message buffers sent out by this subtask. | |
Number of message buffers allocated to this subtask. |
The SHOW FREEQ command displays the number of buffers used and available on the queue for each subtask.
Command Syntax
Example
To display the buffer usage, enter the following command:
F NSPOPEN,SHOW FREEQ
Sample Output
NSP595 Command entered: SHOW FREEQ
NSP705 TNUM TASKNAME FREE USED
NSP705 0 MAINTASK 40000
NSP705 1 DISCOVER-0 40000
NSP705 2 MVS 12000
NSP705 3 PPI 20000
NSP705 4 STATUS-0 40000
NSP705 5 SERVER-0 25000
NSP705 6 SERVER-1 25000
NSP705 7 TCP-0 25000
NSP705 8 TCP-1 25000
NSP705 9 CMD-0 15000
NSP705 10 SPO-0 40000
NSP695 SNA Host SHOW command processed
Table 5-7 describes the fields in the SHOW FREEQ command output.
Field | Meaning |
---|---|
TNUM | Subtask number. |
TASKNAME | Subtask name. |
FREE | Number of unused elements in the queue for this subtask. |
USED | Number of used elements in the queue for this subtask. |
The SHOW TASK command displays information about all the defined mainframe subtasks. As shown in Table 5-8, the data in the SPECIFIC column differs for each type of subtask.
Command Syntax
Example
To display the mainframe subtasks, enter the following command:
F NSPOPEN,SHOW TASK
Sample Output
NSP595 Command entered: SHOW TASK
NSP600 TNUM TASKNAME STATUS RESTARTS/LIMIT SPECIFIC
NSP600 1 DISCOVER-0 READY 0 10NSPDSC1
NSP600 2 MVS UP 0 10NSPCONS2,03000002
NSP600 3 PPI UP 0 10
NSP600 4 STATUS-0 UP 0 10NSPSTA1
NSP600 5 SERVER-0 DOWN 0 10NSPLU01
NSP600 6 SERVER-1 DOWN 0 10NSPLU02
NSP600 7 TCP-0 READY 0 106106,6107
NSP600 8 TCP-1 CONNECTED 0 106126,6127
NSP600 9 CMD-0 UP 0 10NSPCONS1,02000002
NSP600 10 SPO-0 UP 0 10NSPSPO1
NSP695 SNA Host SHOW command processed
Table 5-8 describes the fields in the SHOW TASK command output.
Field | Meaning |
---|---|
Subtask number. | |
TASKNAME | Subtask name. |
STATUS | Status of subtask:
|
RESTARTS | Number of current automatic restarts for this subtask. |
LIMIT | Maximum number of times subtask can be DOWNR before being DOWN. |
Information specific to subtask type:
|
The SHOW TRACE command displays the current settings used for the TRACE command, which is described in the "TRACE" section.
Command Syntax
Example
To display the settings for current TRACE commands, enter the following command:
F NSPOPEN,SHOW TRACE
Sample Output
NSP595 Command entered: SHOW TRACE
NSP707 TNUM TASKNAME NORMAL DETAIL
NSP707 0 MAINTASK ON OFF
NSP707 1 DISCOVER-0 OFF OFF
NSP707 2 MVS OFF OFF
NSP707 3 PPI ON OFF
NSP707 4 SEC OFF OFF
NSP707 5 STATUS-0 OFF OFF
NSP707 6 TCP-0 ON OFF
NSP707 7 CMD-0 OFF OFF
NSP707 8 SPO-0 OFF OFF
NSP695 SNA Host command processed
Table 5-9 describes the fields in the SHOW TRACE command output.
Field | Meaning |
---|---|
Subtask number. | |
TASKNAME | Subtask name. |
NORMAL | Status of the TRACE command without the DETAIL option:
|
DETAIL | Status of the TRACE command with the DETAIL option:
|
The SHOW VERSION command displays the version of the CiscoWorks Blue Maps and SNA View Mainframe program that is running and the date and time that each mainframe subtask was compiled. Use this information to verify the level of code running on your system.
Command Syntax
Example
To display the application version, enter this command:
F NSPOPEN,SHOW VERSION
Sample Output
NSP595 Command entered: SHOW VERSION
NSP607 CiscoWorks Blue Maps and SNA View 2.0 Copyright 1996, 1997, 1998 Cisco Systems
NSP608 TASKNAME DATE TIME
NSP600 DISCOVER-0 Oct 15 1997 14:47:04
NSP600 MVS Oct 15 1997 14:47:04
NSP600 PPI Oct 15 1997 14:47:04
NSP600 STATUS-0 Oct 15 1997 14:47:04
NSP600 SERVER-0 Oct 15 1997 14:47:04
NSP600 SERVER-1 Oct 15 1997 14:47:04
NSP600 TCP-0 Oct 15 1997 14:47:04
NSP600 TCP-1 Oct 15 1997 14:47:04
NSP600 CMD-0 Oct 15 1997 14:47:04
NSP600 SPO-0 Oct 15 1997 14:47:04
NSP695 SNA Host SHOW command processed
Table 5-10 describes the fields in the SHOW VERSION command output.
Field | Meaning |
---|---|
TASKNAME | Subtask name. |
Date that the load module for this task was compiled. | |
TIME | Time that the load module for this task was compiled. |
The STOP command stops the mainframe application and its subtasks.
Command Syntax
Example
To stop the mainframe application, enter the following command:
F NSPOPEN,STOP
The TRACE starts and stops tracing for the mainframe main task and its subtasks. When you use the TRACE command to start tracing, the mainframe trace function records internal tracing events.
Command Syntax
[F NSPOPEN,]TRACE {OFF | PATH | INT} {subtask_name | MAIN} [DETAIL]
F NSPOPEN is used when you issue the command from the command line. Omit this if you use the TRACE command from within the NSPPARM member.
OFF stops the specified mainframe tracing.
PATH starts path tracing. Path tracing records each entry to and exit from mainframe routines.
subtask_name specifies the mainframe subtask to trace. You can specify the name of a specific subtask (such as TCP-2) or you can specify just the root portion of a subtask name when several instances of that subtask type exist. For example, you could use the root name TCP to start tracing on all tasks with the same root TCP in their subtask name, or you could use the specific TCP-2 name. The valid subtask names are as follows:
DETAIL includes traces of internal service routines. If you omit this operand, service routines are not traced.
Notes
You can use the TRACE command inside the NSPPARM member, as described below:
Examples
1. To use the TRACE command interactively to start detail tracing of the TCP-1 subtask and all SERVER subtasks, enter the following commands:
F NSPOPEN,TRACE PATH TCP-1 DETAIL
F NSPOPEN,TRACE PATH SERVER DETAIL
2. To use the TRACE command from within the NSPPARM member to start tracing of the DISCOVER subtask, put the following in NSPPARM:
DISCOVER NSPDSC1
TRACE INT DISCOVER
3. To use the TRACE command from within the NSPPARM member to start internal detail tracing of the TCP subtask, put the following in NSPPARM:
TCP 6104 6104
TRACE INT TCP DETAIL
Posted: Thu Sep 9 08:39:41 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.