Starting and Stopping the Application as an MVS Started Task
To start the mainframe application as a started task (an MVS task that is started with a START (S) command), copy theprefix.NSPS301.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 theS NSPOPEN command.
Starting the Application as an MVS Batch Job
To start the mainframe application as a batch job, modify and submit the JCL in prefix.NSPS301.NSPSSAMP(NSPJCL).
Stopping the Application
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.
Mainframe Subtasks
When the mainframe program starts, it starts a number of subtasks simultaneously, depending on the way you configured the mainframe application. Table 5-1 lists the subtasks that can be started.
Table 5-1 Mainframe Subtasks
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
:
Issuing Mainframe Commands
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
Starts and stops tracing in the mainframe subtasks.
:
HELP
The HELP command displays the list of mainframe commands.
Command Syntax
F NSPOPEN,HELP
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 NSP695 SNA Host HELP command processed
INIT
The INIT command starts a mainframe subtask already defined in the NSPPARM configuration file. When you start a subtask, automatic restarts are enabled for that subtask.
Command Syntax
F NSPOPEN,INIT subtask_name
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
KILL
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 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
F NSPOPEN,KILLsubtask_name
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
SHOW ADDR
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
F NSPOPEN,SHOW ADDR
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 MVS 0922F338 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
Table 5-3 SHOW ADDR Fields
Field
Meaning
TNUM
Subtask number.
TASKNAME
Subtask name.
ADDRESS
Address of subtask control block for this subtask.
HEADER
Address of subtask header.
TCB
Task control block address.
SHOW CONN
The SHOW CONN command displays the TCP/IP addresses (or host names) of the client workstations connected via TCP/IP.
Command Syntax
F NSPOPEN,SHOW CONN
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.
Table 5-4 SHOW CONN Fields
Field
Meaning
TNUM
Subtask number.
TASKNAME
Subtask name.
SPECIFIC
TCP/IP port numbers.
CLIENT
IP address of connected workstation.
NO CONNECTION = no workstation connected.
SHOW DLC
The SHOW DLC command displays the MAC, SAP, and RIF data for any switched PU name.
Command Syntax
F NSPOPEN,SHOW DLC PU_name
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:
Table 5-5 describes the fields in the SHOW DLC command output.
Table 5-5 SHOW DLC Fields
Field
Meaning
IBUPC1
PU name.
05DAA011
XID.
400137451088
Local MAC.
04
Local SAP.
0000F64190B36
Remote MAC.
04
Remote SAP.
0A30A0441F42055
RIF data.
SHOW FLOW
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
F NSPOPEN,SHOW FLOW
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 INFLOW OUTFLOW MC
NSP605 1 DISCOVER-0 0 0 0 0 0
NSP605 2 MVS 0 0 2340 2340 3
NSP605 3 PPI 0 0 0 0 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 94 19 0
NSP605 10 SPO-0 0 0 3 3 0
NSP695 SNA Host SHOW command processed
Table 5-6 describes the fields in the SHOW FLOW command output
Table 5-6 SHOW FLOW Fields
Field
Meaning
TNUM
Subtask number.
TASKNAME
Subtask name.
INPUTQ
Number of message buffers queued to the main task by this subtask.
OUTPUTQ
Number of message buffers queued to this subtask for processing.
INFLOW
Number of message buffers processed by this subtask.
OUTFLOW
Number of message buffers sent out by this subtask.
MC
Number of message buffers allocated to this subtask.
SHOW FREEQ
The SHOW FREEQ command displays the number of buffers used and available on the queue for each subtask.
Command Syntax
F NSPOPEN,SHOW FREEQ
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 4000 0
NSP705 1 DISCOVER-0 4000 0
NSP705 2 MVS 1200 0
NSP705 3 PPI 2000 0
NSP705 4 STATUS-0 4000 0
NSP705 5 SERVER-0 2500 0
NSP705 6 SERVER-1 2500 0
NSP705 7 TCP-0 2500 0
NSP705 8 TCP-1 2500 0
NSP705 9 CMD-0 1500 0
NSP705 10 SPO-0 4000 0
NSP695 SNA Host SHOW command processed
Table 5-7 describes the fields in the SHOW FREEQ command output.
Table 5-7 SHOW FREQ Fields
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.
SHOW TASK
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
F NSPOPEN,SHOW TASK
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 10 NSPDSC1
NSP600 2 MVS UP 0 10 NSPCONS2,03000002
NSP600 3 PPI UP 0 10
NSP600 4 STATUS-0 UP 0 10 NSPSTA1
NSP600 5 SERVER-0 DOWN 0 10 NSPLU01
NSP600 6 SERVER-1 DOWN 0 10 NSPLU02
NSP600 7 TCP-0 READY 0 10 6106,6107
NSP600 8 TCP-1 CONNECTED 0 10 6126,6127
NSP600 9 CMD-0 UP 0 10 NSPCONS1,02000002
NSP600 10 SPO-0 UP 0 10 NSPSPO1
NSP695 SNA Host SHOW command processed
Table 5-8 describes the fields in the SHOW TASK command output.
Table 5-8 SHOW TASK Fields
Field
Meaning
TNUM
Subtask number.
TASKNAME
Subtask name.
STATUS
Status of subtask:
INIT—Initialized.
UP—Up and running.
CONNECTED—Client workstation is connected.
RUN—Discover subtask is running.
READY— Discover subtask is ready to run, or TCP is ready for connection.
DOWN—Subtask was taken down by the KILL command or has exceeded the maximum allowable automatic restarts.
DOWNR—Subtask ended and is automatically restarting.
QUIESCE—Subtask is ending but is waiting to free memory.
RESTARTS
Number of current automatic restarts for this subtask.
LIMIT
Maximum number of times subtask can be DOWNR before being DOWN.
SPECIFIC
Information specific to subtask type:
CMD—Name and ID of the extended console.
DISCOVER—VTAM secondary program operator access method control block (ACB) to which the discover subtask is connected.
MVS—Name and ID of the extended console.
PPI—No specific data.
SERVER—LU name.
SPO—VTAM secondary program operator ACB to which the SPO subtask is connected.
STATUS—VTAM secondary program operator ACB to which the status subtask is connected.
TCP—TCP/IP port number opened for each TCP/IP connection to a workstation.
SHOW TRACE
The SHOW TRACE command displays the current settings used for the TRACE command, which is described in the "TRACE" section.
Command Syntax
F NSPOPEN,SHOW TRACE
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
Table 5-9 SHOW TRACE Fields
Field
Meaning
TNUM
Subtask number.
TASKNAME
Subtask name.
NORMAL
Status of the TRACE command without the DETAIL option:
ON—Normal tracing on.
OFF—Normal tracing off.
DETAIL
Status of the TRACE command with the DETAIL option:
ON—Detail tracing on.
OFF—Detail tracing off.
SHOW VERSON
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
F NSPOPEN,SHOW VERSION
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 3.0.1 Copyright 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003 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
Table 5-10 SHOW VERSION Fields
Field
Meaning
TASKNAME
Subtask name.
DATE
Date that the load module for this task was compiled.
TIME
Time that the load module for this task was compiled.
STOP
The STOP command stops the mainframe application and its subtasks.
Command Syntax
F NSPOPEN,STOP
Example
To stop the mainframe application, enter the following command:
F NSPOPEN,STOP
TRACE
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.
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.
INT starts internal tracing. Internal tracing records each entry to and exit from mainframe routines, and records additional debugging information.
subtask_name specifies which 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:
ALL—Starts tracing all subtasks and the main task.
MAIN—Starts tracing just the main task.
DISCOVER—Starts tracing just the DISCOVER subtask.
MVS—Starts tracing just the MVS subtask.
PPI—Starts tracing just the PPI subtask.
PPO—Starts tracing just the PPO subtask.
SERVER-[n]—Starts tracing the SERVER subtasks specified. Use the subtask name SERVER to trace all SERVER subtasks, or use the specific number of the subtask, such as SERVER-2.
SPO-[n]—Starts tracing just the SPO subtasks specified. Use the subtask name SPO to trace all SPO subtasks, or use the subtask's specific number, such as SPO-2.
STATUS—Starts tracing just the STATUS subtask.
TCP- [n]—Starts tracing just the TCP subtasks specified. Use the subtask named TCP to trace all TCP subtasks, or use the subtask's specific number, such as TCP-2.
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:
Remove the F NSPOPEN, from the beginning of the TRACE command.
Put the TRACE command in the NSPPARM file directly after the subtask card for the subtask it is tracing.
Examples
Step 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
Step 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
Step 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:
