Table Of Contents
TSO Diagnostic Commands
Troubleshooting Client and Server FTP3
General Guidelines for Problem Isolation
Resolving Server FTP Problems
Resolving Client FTP Problems
ACTEST
DNRGET
NETSTAT/SYSSTAT
Command Syntax
Dotted Notation IP Address Wildcarding (*)
TSO Command Common Parameters
NETSTAT Diagnostic Commands
ARP
HELP
CNFG
CONN
ROUTE
USER
SYSSTAT Diagnostic Commands
CANC
CHANGE
OSPFMON
Example
Local Commands
PING
RIPQUERY
RPCINFO
Examples
TCPEEP
User Interface
Trace Data Collected
Viewing Trace Data
Trace Operation
TCPEEP Syntax
Useful TCPEEP Commands
Creating a NOWRAP Trace
Stopping Trace
Modify Existing Trace
View Existing Trace
Specifying GROUPS
TCPEEP Examples
Default TCPEEP Command
LNI Level Trace
DATA Output
ICMP Format
TRACE
MVS Component Trace
Trace Address Space
Exit
External Writer
TRACE Command
TRACE Command Reply
TRACE Command Reply Options
Comparing TCPEEP and MVS TRACE Syntax
OPTIONS
JOBNAME
Trace Command Examples
Starting a Trace Instance
Modifying a Trace Instance
Displaying Trace Status
Stopping a Trace Instance
Stopping all Trace Instances
Starting an External Writer
Starting a Trace Instance and connecting an External Writer
Modifying a Trace Instance to connect an External Writer
Modifying a Trace Instance to disconnect an External Writer
Stopping a Trace Instance and Disconnecting an External Writer
Stopping an External Writer
Processing Trace Data
TRACERT
TSO Diagnostic Commands
This chapter describes the diagnostic commands available in Cisco IOS for S/390. The chapter is organized into the following sections.
•
Troubleshooting Client and Server FTP3
Describes guidelines for problem isolation with the Cisco IOS for S/390 FTP compatibility.
•ACTEST
A Customer Support command to debug the Cisco IOS for S/390 commutator.
•DNRGET
A command to query the Domain Name Resolver (DNR).
•NETSTAT/SYSSTAT
The diagnostic command to monitor and manage Cisco IOS for S/390 activity.
•OSPFMON
A command to request information for routes known to OSPF.
•PING
A command to determine if a host is active on the network.
•RIPQUERY
A command to request all routes known by a RIP gateway.
•RPCINFO
A command to query an RPC server to obtain information about program names and program numbers for a specified host.
•TCPEEP
A command to invoke the Cisco IOS for S/390 packet trace program and diagnose remote host communication problems.
•TRACE
Trace command enhancements to collect TCP/IP data and display it on a terminal or send it to an external writer.
•TRACERT
A command to print the route that packets take to get to a network host.
Troubleshooting Client and Server FTP3
This section describes problem isolation in the Cisco IOS for S/390 FTP compatibility feature. Troubleshooting information is divided into server and client. The client is a three-party model; it therefore requires both server and client documentation.
General Guidelines for Problem Isolation
When encountering FTP3 problems, start with the following problem resolution process.
1 Determine the level of maintenance that is running.
2 Enable the DEBUG or TRACE option and rerun the failing command.
3 Run a network trace.
4 Look at the T01LOG job output.
Resolving Server FTP Problems
For incorrect input through FTP, collect the following:
•A description of the action preceding the failure and the condition of the system (such as 100 terabyte transfer).
•The job output of the Cisco IOS for S/390 gateway at the time of failure, including
•the JES log
•any PSNAP data
•T01LOG
•any enabled traces
•A log or screen print of the failing transfer, including any messages.
•Any client software involved, including the name of the vendor, the release number, the direction of transfer, the file format; and the contents (if requested).
•Whether the failure is reproducible or random. If reproducible, obtain a TCPEEP TCP trace.
Resolving Client FTP Problems
For incorrect input through FTP, collect the following information:
•A description of the action preceding the failure and the condition of the system (such as 100 terabyte transfer).
•The job output of the Cisco IOS for S/390 gateway at the time of failure, including
•the JES log
•any PSNAP data
•T01LOG
•any enabled traces
•A log or screen print of the failing transfer, including any messages.
•Turn on the TRACE or DEBUG parameters. The recommended procedure is to run the command in batch mode and save the recorded trace output for problem resolution.
•Any client software involved, including the name of the vendor, the release number, the direction of transfer, the file format; and the contents (if requested).
•Whether the failure is reproducible or random. If reproducible, obtain an TCPEEP TCP trace.
ACTEST
The Telnet command ACTEST invokes the ACTEST parameter and debugging interface to the Cisco IOS for S/390 commutator. A generalized terminal I/O interface implements it. It is generally used only on advice of Customer Support.
To invoke ACTEST
•From Server Telnet, through an ATPUT/ATGET interface, select ACTEST at the Server Telnet command screen (port 23). It requests logon and calls PACCESS to verify privileges.
•From User Telnet (TSO), use VTAMTEST as the remote host name. The path requires a local logon. It is particularly useful when there is a problem with TCP/IP, since no network I/O is required.
This list describes the ACTEST options:
ABEND
|
Abruptly terminates the entire commutator.
|
ACCOM length
|
Lists length (in bytes) of the main control block.
|
ALIST address length
|
Displays storage at address within unprotected areas of the address space for length bytes; tries to print the information as ASCII; specifies address and length in hex.
|
CATV pta_1 pta_2
|
Copies the application transfer vector (PTAATRV) from the PTA at address pta_2 to the PTA at address pta_1.
|
COMMANDS
|
Lists all the commands known to ACTEST.
|
END
|
Terminates the ACTEST ptask normally.
|
EQUATE symbol address length
|
Defines a symbol to be used by LIST.
|
EXECUTE slot
|
Issues the commands saved in slot by the REMEMBER command.
|
FREEZE
|
Issues a PWAIT FREEZE and halts execution of the ACTEST ptask until external action is taken to unblock the ptask.
|
HELP command
|
Displays the syntax for command.
|
LIST address length
|
Displays storage at address within unprotected areas of the address space for length bytes. Tries to print the information as EBCDIC.
|
MODULES mask
|
Lists the loaded modules or ESDs that have names matching mask (* is a wild card character).
|
PATTACH module parms
|
Creates a new control fork to pass control to the indicated module and to pass it the indicated parameter string in the form defined for the EXEC PARM field; each fork is identified by a control block called the Pseudo Task Area (PTA).
|
PDELETE name
|
Removes from storage the module loaded by PLOAD called name.
|
PDETACH pta
|
Destroys the PTA at address pta that was created by PATTACH. Explicitly forces PTA at a given address to exit.
Use this to install a new load module within the running Cisco IOS for S/390 when the old module has been PLOADed by a permanent ptask. Issue PDETACH for the ptask to free the old module, and issue a new PATTACH to bring in the new module.
|
PLOAD name options
|
Loads the program module name into main storage where it stays until you exit from ACTEST. The possible options are: ESD, FETCH, FREE, HOLD, SYS, and USE.
|
PPOST ecb code
|
Marks event ecb complete with the code code.
|
PPOST pta event_list
|
Marks pta as no longer blocked on certain events. Possible events are ATTN, CLOSE, CORE, INPUT, OPEN, OUTPUT, and USER.
|
PSTATUS ANCESTOR pta
|
Lists all ancestors of the PTA at address pta.
|
PSTATUS DESCENDENT pta
|
Lists all descendents of the PTA at address pta.
|
PSTATUS PARENT pta
|
Lists all parents of the PTA at address pta.
|
PSTATUS PROCESS mask
|
Lists all the PTAs that have names matching the mask (* is a wild character).
|
PSTATUS SON pta
|
Lists all sons of the PTA at address pta.
|
PTALIST mask
|
Lists all the PTAs that have names matching the mask along with the status and contents of the registers of the PTA (* is a wild card character).
The command PTA I displays the status of all PTAs whose names begin with I (for example, INPTASK, IMPIN, IMPOUT, etc.). The PTA display formats the dispatchability and semaphore bits in the first word of the PTA and shows the registers at the time of the last P- service call (normally PWAIT).
|
PWAIT integer
|
Suspends the ACTEST ptask to let the commutator dispatch other ptasks (in other words, this lets Cisco IOS for S/390 execute for a time specified by integer). Here integer is in units of 0.01 seconds. To specify a decimal integer, follow the integer with a period.
|
REMEMBER slot command_line
|
Saves the command_line in slot for later execution. The text of command_line is saved and later given to the parse routines by the EXECUTE command. Saved commands can include nested EXECUTE commands. There are sixteen slots numbered 0 - 15.
|
RESOURCE PTA_address mask
|
Displays those resources of the PTA at the specified address that have names matching mask (* is a wild character in mask). If mask is not specified, all resources owned by the PTA display.
Examples
The following example lists the PCOREd areas belonging to the PTA at address 56A00.
RESOURCE 56A00 PCORE or RES 56A00 PC
The following example displays the AEXIT resource for the specified PTA. This includes all the TCP/IP and environmental control blocks.
RES 56A00 AEXIT or RES 56A00 AE
The following example displays all the resources owned by the specified PTA.
|
RUN transfer_initialization_parameters
|
Starts an application program. The module identified by transfer is loaded into core and treated as the Application Transfer Vector (ATRV). The module identified by initialization is then forked by PATTACH (specifying the option that the new ptask is to have no parents) with the ATRV and given the parameters in EXEC PARM form.
|
SHOWREM slot
|
Displays the command line saved in slot by the REMEMBER command.
|
SPOOLDMP ON | OFF
|
Specifies whether ptask SPOOL#4 should take a dump at certain task termination events (open, close, dynamic allocation, etc.). SPOOLDMP entered without any parameters will display the current setting.
|
SRUN pta
|
Makes the PTA at address pta ready to run.
|
START pta
|
Revives the PTA at address pta that was suspended with STOP.
|
STOP pta
|
Suspends the PTA at address pta from running.
|
STORE data
|
Replaces storage with data at the last address displayed with the LIST command.
|
SUBPOOLS
|
Display allocated, used, and free virtual storage in all used subpools above and below the 16MB "line", including totals.
|
SVC99
|
Activates the extended error processing from SVC99. These extended messages will be issued to the master console by the SVC99 error processing facility.
|
SYSDUMP ON | OFF
|
Specifies whether a system dump should be produced for commutator ABEND conditions, in addition to the formatted SNAP dump that is normally produced. The system dump goes to the SYSUDUMP, SYSABEND, or SYSMDUMP data set.
Default: OFF
|
TASKS mask
|
Alternate for the PSTATUS PROCESS mask command. Gives a one line status display for each ptask whose name begins with the string mask. If mask is omitted, the status display lists all current ptasks.
|
VLT ON | OFF
|
VLT tracing. VLT OFF stops VLT tracing; VLT ON starts VLT tracing. Use module AMDUSR to format the GTF records written by the VLT trace.
Default: VLT OFF
|
WHERE address
|
Locates the given address within the current set of loaded modules, if possible, and prints its relative position.
|
XSEC options ON | OFF
|
Activates or deactivates monitoring of selected security events. Those options can also be specified on the SECURITY statement in member IJTCFGxx. The global system security options can be turned on or off by specifying ON or OFF.
•ACEE - Monitors ACEE activity.
•ACSECP -Monitors entry to the security call module that performs all security checking within Cisco IOS for S/390.
•COMMAND - Monitors command authorization calls. The COMMAND option aids in the debugging of COMMAND security problems within Cisco IOS for S/390.
•DATASET - Monitors data set authorization calls. The DATASET option aids in the debugging of DATASET security problems within Cisco IOS for S/390.
•LOGOFF - Monitors departure from the system. The LOGOFF option aids in the debugging of sign-off security problems within Cisco IOS for S/390.
•LOGON - Monitors attempts to gain entry to the system. The LOGON option aids in the debugging of sign-on security problems within Cisco IOS for S/390.
|
DNRGET
The DNRGET TSO diagnostic command invokes the command processor that allows direct queries to be made to the Domain Name Resolver (DNR). DNRGET can issue all sixteen combinations of domain name requests supported by the DNR. Also, the full range of options that the DNR can support can be specified.
Each reply returned by the DNR is formatted and displayed. The format of the returned data is dependent on the type and mode of the request. Any conditional completion codes or error codes are formatted and displayed. Along with these codes, a textual message explaining the code is displayed.
DNRGET executes as a TSO command processor. All messages that are written and done with TPUTs restricting its use to interactive TSO users only. Also, the TSO profile option PROMPT must be set if DNRGET is to prompt for correct operands in the event of an error.
DNRGET can not be invoked with the TSO CALL or TSOEXEC commands. Therefore the LINK data set must either be in your system's link list or in the STEPLIB DD concatenation of your TSO JCL procedure.
If, after invocation, DNRGET waits too long for a reply from the DNR, press PA1 to interrupt its execution without causing any errors.
The syntax of the DNRGET command is as follows:
DNRGET request_type request_mode
request [Block | Noblock] [Copy | Nocopy] [Local | Global] [SIze(count)]
[SYsid(subsystem_id)] [Time(seconds)]
Note At a minimum, you must specify the letters that are capitalized of the request parameters.
Syntax Description
request_type
|
Specifies the type of Domain Name System information that is being requested. These are the valid values:
•HOST—Resolves host names and Internet addresses.
•HOSTINFO—Returns the CPU type and operating system of a host.
•HOSTSERV—Returns which services a host provides.
•NETWORK—Resolves network names and Internet network numbers.
•NS—Returns list of authoritative name servers for domain.
•PROTOCOL—Resolves transport protocol names and Internet protocol numbers.
•ROUTE—Returns mail routing information for a host.
•RPC—Resolves RPC program names and numbers.
•SERVICE—Resolves well known protocol services.
•SOA—Returns start of authority data for a domain.
|
request_mode
|
Specifies the format of the request data. These are the valid values:
•BYALIAS—The request field is a host name ALIAS. This option returns a replacement name for the requested host name.
•BYNAME—The request field is either a host name, network name, protocol name/service name or protocol name. BYNAME is valid with any request type.
•BYVALUE—The request field is either an Internet number in nnn.nnn.nnn.nnn format, a TCP/UDP service number, or a protocol number. BYVALUE is only valid with request types HOST, NETWORK, SERVICE, and PROTOCOL.
|
request
|
Specifies the data that the Domain Name Resolver used as input. Its format is dependent on the request_type and request_mode arguments. These are the valid values:
•Block | Noblock—Block specifies that a response is not returned until either the request has completed or the time or retry limits have been exceeded. Noblock specifies that a response is returned immediately. If the data to complete the request is not in the cache, an error is returned immediately, but the DNR continues to try to resolve the request in order to update the cache.
This argument only applies if Global is specified.
Default: Block
•Copy | Nocopy—Copy specifies that if data to resolve a request is in the DNR cache it uses it to satisfy the request. Nocopy specifies that DNR ignores the data in the cache and queries domain name servers for data to resolve the request.
This parameter only applies if Global is specified.
Default: Copy
•Local | Global—Local specifies that the DNR use only configuration data to resolve requests. Global specifies that the DNR query Domain Name Servers for the necessary data to resolve the request.
Default: Global
•SIze(count)—Specifies the number of entries to be returned by the DNR when the result field has more than one item in the reply. count is the maximum number of entries to be returned. 0 (zero) specifies that the maximum number of entries is determined by the return buffer size, which cannot be dynamically changed.
Default: 0 (zero)
•SYsid (subsysid)—Specifies the subsystem ID of the Cisco IOS for S/390 job or started task in which the DNR is active. subsystem_id is the four character MVS subsystem ID.
Default: ACSS
•Time(seconds)—Specifies the maximum amount of time the DNR is allowed to resolve a request. seconds is the maximum amount to process the request in seconds. 0 (zero) specifies that there is no time limit to resolve the request.
Default: 30 seconds
|
NETSTAT/SYSSTAT
The NETSTAT and SYSSTAT diagnostic commands invoke the user information and operator control interface for Cisco IOS for S/390. The diagnostic commands are used to monitor and manage Cisco IOS for S/390 activity.
The TCP task group must be active. System security adjustments should be made if the new management commands require authorization
Information retrieval is from a running, operational gateway, so commands associated with the NETSTAT facility can originate outside the gateway address space.
Commands can originate from the following.
•The system console operator
•A TSO user
•A remote user via Telnet
NETSTAT commands that interrogate only are unrestricted commands; management commands that result in dynamic modification of internal control blocks or session behavior require authorization, unless the source is the system console operator.
Note SYSSTAT commands entered under TSO are secure based on the TSO userid.
Command Syntax
The external syntax of commands varies slightly, depending on the origin. Operator commands start with some sequence that identifies the target address space.
For example, to request a NETSTAT connection display, use one of the following operator commands:
F jobname,NETSTAT CONN
or
%NETSTAT CONN
where % is the subsystem recognition character.
A remote Telnet user would use the following command:
NETSTAT CONN
A TSO version may include TSO-specific keywords:, as shown by the following
NETSTAT CONN SSID(ABCD)
Dotted Notation IP Address Wildcarding (*)
In most cases where a dotted notation IP address is accepted, wildcarding or omission adheres to the following syntax:
nnn <.nnn | * > <.nnn | * > <.nnn | * >
The usual dotted notation consists of four numeric components, each between 0-255, and separated by a period. For example:
111.112.113.4
If a component is omitted, right to left, it is replaced with 0, so 111.112.113 will be interpreted as a specific IP address of 111.112.113.000, and 111.112 will be interpreted as 111.112.000.000.
If a component is replaced with an asterisk (*), it will be interpreted as a non-specific wildcard. So 111.112.113.* will satisfy any IP address match starting with 111.112.113, and 111.112.* will satisfy any IP address starting with 111.112.
Wildcarding must be applied to an entire component. In other words, 11* is not valid. Both wildcarding and omission must be rightmost in the IP address string. That is, 111.*.113.4 is not valid.
TSO Command Common Parameters
The DDNAME( name ) and SSID( name ) parameters are common to all TSO commands.
NETSTAT CONN DDNAME( ddname ) SSID( subsysname )
DDNAME( ddname )
|
If the standard TSO output definition SYSTSPRT is not appropriate, an output file can be pre-allocated with an LRECL size of 120 bytes. Its DD name can then be used as a parameter to the TSO NETSTAT or SYSSTAT command. This option is particularly useful if archiving is required, and browsing a disk file may be convenient.
If output is directed to a file specified by the DDNAME( name ) parameter, all message lines are date and time stamped.
|
SSID( subsysname )
|
Specifies the subsystem ID.
|
NETSTAT Diagnostic Commands
The NETSTAT diagnostic commands are described following.
ARP
Display the status of devices that have responded to a request or are pending a request. The request status is retrieved from cache.
NETSTAT ARP[IPNAME] [MEDIA( name )] [MSGID | NOMSGID]
Syntax Description
null
|
Display all devices.
|
IPNAME
|
Attempt to resolve the symbolic IP host name. If not resolvable, dotted notation displays.
|
MEDIA( name )
|
Limit the display to a specific media, as defined in TCPCFGxx.
|
MSGID | NOMSGID
|
Controls the display of the 9-character message prefix.
•For Telnet user, NOMSGID is the default; use MSGID to turn on the message display.
•For TSO users, MSGID is the default; use NOMSGID to omit the prefix from the display.
•For operator requests, the prefix is always displayed; this parameter has no effect.
|
The following messages result from the NETSTAT ARP command:
T01NT024I
|
T01NT025I
|
T01NT026I
|
The status is defined as follows:
•Valid - a response was received from a device request
•Dead - the requested device did not respond
•Static - the device is defined in the TCPCFGxx file
•Router - the requested device is a router
•Pending resolution - a request has been made but not response was received
HELP
Displays a summary of the NETSTAT and SYSSTAT commands.
NETSTAT HELP [command] [MSGID | NOMSGID]
Syntax Description
null
|
Display a list of all the NETSTAT commands.
|
command
|
Display a specific command, description and syntax.
|
MSGID | NOMSGID
|
Controls the display of the 9-character message prefix.
•For Telnet user, NOMSGID is the default; use MSGID to turn on the message display.
•For TSO users, MSGID is the default; use NOMSGID to omit the prefix from the display.
•For operator requests, the prefix is always displayed; this parameter has no effect.
|
The following messages result from the NETSTAT HELP command:
CNFG
Display configuration information in one of the following formats.
NETSTAT CNFG [MSGID]
NETSTAT CNFG LNI [CETI | CLAW] [MSGID]
NETSTAT CNFG TCP | UDP | RAW | ALL [MSGID]
Syntax Description
null
|
Display the basic network in an outline form.
|
MSGID
|
Controls the display of the 9-character message prefix.
•For Telnet user, the default is no message. Use MSGID to turn on the message display.
•For TSO users, MSGID is the default; using no message omits the prefix from the display.
•For operator requests, the prefix is always displayed; this parameter has no effect.
|
LNI [CETI | CLAW]
|
Display configuration information from the TCPCFGxx statement. The LNI selection displays Local Network Interface information, and TPI displays Transport Provider Information variables. If the CETI option is selected for a CETI device, then 4 additional messages are displayed. If the CLAW option is selected for a CLAW device, then 3 additional messages are displayed.
|
TCP | UDP | RAW
|
Protocol identifiers, TCP, UDP, and RAW can be used to limit the display to specific protocols, otherwise all protocols are displayed.
|
The following messages result from the NETSTAT CNFG command:
T01NT028I
|
T01NT034I
|
T01NT040I
|
T01NT060I
|
T01NT067I
|
T01NT029I
|
T01NT035I
|
T01NT041I
|
T01NT061I
|
T01NT086I
|
T01NT030I
|
T01NT036I
|
T01NT042I
|
T01NT062I
|
T01NT087I
|
T01NT031I
|
T01NT037I
|
T01NT057I
|
T01NT064I
|
T01NT088I
|
T01NT032I
|
T01NT038I
|
T01NT058I
|
T01NT065I
|
T01NT089I
|
T01NT033I
|
T01NT039I
|
T01NT059I
|
T01NT066I
|
|
CONN
Gives connection summary information for specified connection
NETSTAT CONN
[COUNT] [FULL] [MSGID | NOMSGID] [SEP] [TCP | UDP | RAW]
[LOCPORT(nnn)] [REMPORT(nnn)]
[LOCHOST(ip_addr)] [REMHOST(ip_addr)]
[JOB(name)] [PLU(name)] [SLU(name)] [SESSION(nnn)]
Syntax Description
COUNT
|
Specifies that a one-line connection count be displayed
|
FULL
|
Specifies that the full output be displayed, with no filtering. This can be approximately 23 lines per connection.
|
MSGID | NOMSGID
|
Controls the display of the 9-character message prefix.
•For Telnet user, NOMSGID is the default; use MSGID to turn on the message display.
•For TSO users, MSGID is the default; use NOMSGID to omit the prefix from the display.
•For operator requests, the prefix is always displayed; this parameter has no effect.
|
SEP
|
Specifies that a separator, a single line with an asterisk (*) be placed between connections. This is useful when many connections are being displayed.
|
TCP | UDP | RAW
|
Protocol identifiers. TCP, UDP, and RAW can be used to limit the display to specific protocols, otherwise all protocols are displayed.
|
LOCPORT( nnn )
|
Display one or more sessions, using a local port number (nnn).
|
REMPORT( nnn )
|
Display one or more sessions, using a remote port number (nnn).
|
LOCHOST(ip_addr)
|
Display a connection to a local host. ipaddr is the IP address of the host. The IP address must be entered in dotted notation.
|
REMHOST(ip_addr)
|
Display a connection to a remote host. ipaddr is the IP address of the host. The IP address must be entered in dotted notation.
|
JOB(name)
|
Specifies that the output be filtered for the jobname given.
|
PLU( name )
|
Specifies that the output be filtered for the Primary LU given.
|
SLU( name )
|
Specifies that the output be filtered for the Secondary LU given.
|
SESSION( nnn )
|
Display a session. nnn represents a specific session number.
|
The following messages result from the NETSTAT CONN command:
T01NT063I
|
T01NT054I
|
T01NT055I
|
T01NT056I
|
ROUTE
Displays the routing table entries.
NETSTAT ROUTE [IPNAME] [MSGID | NOMSGID]
Syntax Description
null
|
Display a list of all the NETSTAT commands.
|
IPNAME
|
Attempt to resolve the symbolic IP host name. If not resolvable, dotted notation will display.
|
MSGID | NOMSGID
|
Controls the display of the 9-character message prefix.
•For Telnet user, NOMSGID is the default; use MSGID to turn on the message display.
•For TSO users, MSGID is the default; use NOMSGID to omit the prefix from the display.
•For operator requests, the prefix is always displayed; this parameter has no effect.
|
The following messages result from the NETSTAT ROUTE command:
USER
Displays information about connected users.
NETSTAT USER [SESSION(nnn)] [IPNAME] [MSGID | NOMSGID]
or
NETSTAT USER [REMHOST(ip_addr)] [LOCPORT(nnn)] [IPNAME]
[MSGID | NOMSGID]
Syntax Description
null
|
List all users
|
SESSION( nnn )
|
Limit the display to a specified session.
|
REMHOST(ip_addr)
|
Limit the display to the entries associated with a specific host. The ipaddr can be specified as either dotted notation, or a symbolic string, and an ending asterisk (* can be used as a wildcard indicator. The REMHOST(ip_addr) and LOCPORT( nnn ) options can be used together or separate.
|
LOCPORT( nnn )
|
Limit the display to the entries associated with a specific port.
|
IPNAME
|
Attempts to resolve and display actual hostname instead of IP address.
|
MSGID | NOMSGID
|
Controls the display of the 9-character message prefix.
•For Telnet user, NOMSGID is the default; use MSGID to turn on the message display.
•For TSO users, MSGID is the default; use NOMSGID to omit the prefix from the display.
•For operator requests, the prefix is always displayed; this parameter has no effect.
|
The following messages result from the NETSTAT USER command:
SYSSTAT Diagnostic Commands
The SYSSTAT diagnostic commands include all of the NETSTAT commands, plus the commands CANC and CHANGE. These are described following.
CANC
Cancel a specified session.
SYSSTAT CANC [SESSION(nnn)] [MSGID | NOMSGID]
or
SYSSTAT CANC [TCP | UDP | RAW] REMHOST(ip_addr) | LOCPORT(nnn)
[MSGID | NOMSGID]
Syntax Description
SESSION(nnn)
|
Cancel a specific session number (nnn).
|
TCP | UDP | RAW
|
If cancellation is not by specific session number, one of these protocol identifiers must be specified.
|
LOCPORT(nnn)
|
Cancel one or more sessions, using a local port number. nnn represents a specific port number.
|
REMHOST(ip_addr)
|
Cancel a connection to a remote host. ipaddr is the IP address of the host. The IP address must be entered in dotted notation.
|
MSGID | NOMSGID
|
Controls the display of the 9-character message prefix.
•For Telnet user, NOMSGID is the default; use MSGID to turn on the message display.
•For TSO users, MSGID is the default; use NOMSGID to omit the prefix from the display.
•For operator requests, the prefix is always displayed; this parameter has no effect.
|
Caution Cancellation by a specific session number will only cancel a single session. The other option, cancellation by protocol/IP/port, can terminate multiple sessions.
CHANGE
Change TCP variables.
SYSSTAT CHANGE [CWIND(nnn) SESSION(nnn)] [THRS(nnn) SESSION(nnn)]
[RTT(nnn) SESSION(nnn)] [DEBUG(ON | OFF)] [SESSION(nnn)]
[MSGID | NOMSGID]
Syntax Description
CWIND(nnn) SESSION(nnn)
|
Change the congestion window size for a specified session. Both variables are required.
|
THRS( nnn ) SESSION( nnn )
|
Change the slow start threshold for a specified session. Both variables are required.
|
RTT( nnn ) SESSION( nnn )
|
Change the round trip start time for a specified session. Both variables are required.
|
DEBUG( ON | OFF )
|
Used in TCP connections to produce debugging messages to the T01LOG data set. In order to use this feature, the TCP task group must have the TEST flag set on. An operator command, or startup script, may set this flag, using the command /SET TEST ON TGB(TCP). Similarly the flag may be set off using the command /SET TEST OFF TGB(TCP). Once this flag is on, the individual DEBUG flags of each connection are queried.
Using this method to diagnose TCP problems is not recommended, as large volumes of messages may be produced. These messages are directed to the T01LOG data set. The messages produced are in the range of T01TC9xx.
|
MSGID | NOMSGID
|
Controls the display of the 9-character message prefix.
•For Telnet user, NOMSGID is the default; use MSGID to turn on the message display.
•For TSO users, MSGID is the default; use NOMSGID to omit the prefix from the display.
•For operator requests, the prefix is always displayed; this parameter has no effect.
|
OSPFMON
The OSPFMON (ospf_monitor) TSO diagnostic command can request information for routes known to OSPF.
Note OSPFMON executes as a TSO command processor. All messages that are written are done with TPUTs, restricting its use to interactive TSO users only. OSPFMON is intended to be used as a tool for debugging gateways, not for network management. SNMP is the preferred network management protocol. GateD responds only to OSPFMON requests issued on the same subnet on which GateD is running.
OSPFMON -x subsysid filename
subsysid
|
Four character MVS subsystem ID of the Cisco IOS for S/390 job or started task
Default: ACSS
|
filename
|
Name of a file that has a list of gateways
|
Example
The following is a sample of a list of gateways:
138.42.181.50 gateway1.company.com [password]
138.42.171.64 gateway2.company.com
138.42.181.200 gateway3.company.com
138.42.171.220 gateway4.company.com
138.42.181.3 gateway5.company.com
138.42.224.4 gateway6.company.com
The optional password is specified by the monitorauthkey sub-parameter of the ospf parameter of the GateD configuration file.
Local Commands
Enter OSPFMON for the desired subsystem ID. These commands are supported:
d
|
Show configured destinations
|
h
|
Show history
|
x
|
Exit
|
@ remote_command
|
Use last destination
|
@dest_index remote_command
|
Use configured destination index
|
F filename
|
Write monitor information to filename
|
S
|
monitor information to stdout
|
PING
Use the PING TSO diagnostic command to determine if a host is active on the network. PING sends an ICMP ECHO_REQUEST packet to network hosts to elicit an ICMP ECHO_RESPONSE from the specified host or network gateway. If the host responds, PING replies that the host is alive and then exits. Otherwise, after the timeout expires, PING replies that there was no answer from the host.
If a count is not specified, PING continues to try until it is stopped.
Note PING requires the SAS/C Transient Library modules that are supplied in the LOAD/SASLOAD data set. This library is required in either your LOGON procedure or BATCH job STEPLIB DD.
Source for PING and many BSD socket applications can be obtained via anonymous FTP from Internet host gatekeeper.dec.com.
If, after invocation, PING waits too long for a reply, press PA1 to interrupt its execution (this may produce a dump of system related errors).
PING [-dnqv] [-c count] [-i wait] [-l preload] [-p pattern] [-s packetsize] [-x subsysid]
host
Syntax Description
-d
|
Set the SO_DEBUG socket option
|
-n
|
Show network addresses as numbers (PING normally displays addresses as host names)
|
-q
|
Run PING in quiet mode
|
-v
|
Verbose output; list any ICMP packets received, other than ICMP_RESPONSE
|
-c count
|
Specifies the number of requests to be sent
|
-i wait
|
Specifies the interval between successive transmissions
Default: 1 second
|
-l preload
|
Specifies the count of pings initially sent
|
-p pattern
|
Fill the buffer with pattern
|
-s packetsize
|
Specifies the packet size to be sent
Default: 64 bytes
|
-x subsysid
|
Specifies the subsystem ID of the Cisco IOS for S/390 job or started task; subsysid is the four-character MVS subsystem ID
Default: ACSS
|
host
|
Specifies the host name or IP address
|
RIPQUERY
The RIPQUERY TSO diagnostic command can request all routes known by a RIP gateway by sending a RIP request or POLL command. The routing information in any routing packets returned is displayed numerically and symbolically.
Note The RIPQUERY tool executes as a TSO command processor. All messages are written with TPUTs, which restricts its use to interactive TSO users. The RIPQUERY tool is for debugging gateways, not for network management. SNMP is the preferred network management protocol.
By default, RIPQUERY uses the RIP POLL command for this version of GateD. The RIP POLL command is preferable to the RIP REQUEST command as it is not subject to Split Horizon and/or Poisoned Reverse. See the RIP RFC for more information.
RIPQUERY -x subsysid [-a password] [-d] [-n] [-p] [-r] [-v] [-1] [2] [-w time] routers...
Syntax Description
-x subsysid
|
Four character MVS subsystem ID of the Cisco IOS for S/390 job or started task.
Default: ACSS
|
-a password
|
Authentication password to use for queries. If specified, an authentication type of SIMPLE will be used; otherwise the default is an authentication type of NONE. Authentication fields in incoming packets will be displayed but not validated.
|
-n
|
Prevents the address of the responding host from being looked up to find the symbolic name.
|
-p
|
The RIP POLL command requests information from the routing table. This is the default for some versions of GateD. If there is no response to RIP POLL, try the RIP REQUEST command. GateD responds to a POLL command with all the routes learned via RIP.
|
-r
|
The RIP REQUEST command requests information from the gateway's routing table. All gateways should support RIP REQUEST. If there is no response to the RIP REQUEST command, try the RIP POLL command. GateD responds to a REQUEST command with all routes currently announced on the specified interface. For systems based on BSD 4.3 Reno or earlier, responses to RIP REQUESTs contain information about the interface used to send the reply. To obtain information about a particular host, run RIPQUERY on that host.
|
-v
|
Displays version information about RIPQUERY before querying the gateways.
|
-1
|
Sends the query as a version 1 packet.
|
-2
|
Sends the query as a version 2 packet (default).
|
-w time
|
Specifies the time in seconds to wait for the initial response from a gateway.
Default: 5 seconds
|
routers
|
Router name list.
|
RPCINFO
The RCPINFO command queries an RPC server to obtain information about program names and program numbers for the specified host.
The RPCINFO command is supplied with Cisco IOS for S/390 as a TSO command processor for use on the MVS system. Its usage is similar to the rpcinfo command on UNIX systems. No parameters are positional or case sensitive.
Read Cisco IOS for S/390 Unprefixed Messages and Codes for information about RPCINFO error messages.
RPCINFO [PROTO (protocol)] [HOST(host_name)] [PROG(prog_num)]
[VERS(vers_num)] [PORT(port)] [SYSID(subsystem_id)]
Syntax Description
PROTO( protocol )
|
Specifies the protocol to use, either UDP or TCP.
|
HOST( host_name )
|
Specifies the name of the host where the service is resident.
|
PROG( prog_num )
|
Specifies the RPC program number in decimal.
|
VERS( vers_num )
|
Specifies the version number of the RPC program.
|
PORT( port_num )
|
Specifies the UDP or TCP port where the selected service is registered.
|
SYSID( subsystem_id )
|
Specifies the subsystem ID of Cisco IOS for S/390.
Default: ACSS
|
Examples
•Use this RPCINFO command to dump the portmapper registration tables:
RPCINFO PROTO(protocol) HOST(host_name) PROG(prog_num)
[VERS(vers_num)] [PORT(port_num)]
[SYSID(subsystem_id)]
Use this command to ping an RPC service:
RPCINFO HOST(host_name) [SYSID(subsystem_id)]
Use this command to delete an RPC service registration with the LOCAL portmapper:
RPCINFO DELETE PROG(prog_num) VERS(vers_num) SYSID(subsystem_id)
•The following is a sample command and output for the RPC HOST command to list the services registered on MVS host zeus:
RPCINFO HOST(ZEUS)
RPC105I Thu Feb 07 10:47:10 1991 number vers. protocol port name
RPC106I Thu Feb 07 10:47:10 1991 100000 2 TCP 111 PORTMAPPER
RPC106I Thu Feb 07 10:47:10 1991 100000 2 UDP 111 PORTMAPPER
RPC106I Thu Feb 07 10:47:10 1991 100059 1 UDP 4098
RPC106I Thu Feb 07 10:47:10 1991 100044 1 UDP 4099
RPC106I Thu Feb 07 10:47:10 1991 100005 1 UDP 4100 MOUNTD
RPC106I Thu Feb 07 10:47:10 1991 150001 1 UDP 4101
RPC106I Thu Feb 07 10:47:10 1991 100003 2 UDP 2049 NFS
TCPEEP
TCPEEP is a TSO command that invokes the Cisco IOS for S/390 packet trace program to diagnose remote host communication problems. The TCPEEP real-time trace consists of selected network packet traffic to and from a local host. The TCPEEP command recognizes LNI level traffic and most of the IP-based higher level protocols.
TCPEEP will create a NO WRAP Component Trace Instance and display the output on a TSO terminal or direct it to a dynamically allocated SYSOUT data set. Optionally, it can stop any Component Trace Instance or modify an existing Component Trace Instance or view an existing Component Trace Instance.
Note TCPEEP runs only when the Cisco IOS for S/390 and TRACE address spaces are active.
User Interface
TCPEEP can be run as a TSO command, either from TSO or as a batch TSO.
The JCL to run TCPEEP as a batch job is in SAMP member TCPEEP. Cisco IOS for S/390 TRACE must be up and running before submitting a batch job for TCPEEP.
The following is a sample JCL for running TCPEEP in batch.
//TCPEEP JOB (TCPEEP),'TCPEEP', CLASS=A,MSGCLASS=X
//* Sample JCL to run TCPEEP in batch.
//* Update "trgindx" to reflect your library naming convention
//* Note: The Cisco IOS for S/390 and TRACE address spaces must be running.
//*TCPEEP EXEC PGM=IKJEFT01,DYNAMNBR=50,REGION=4M
//STEPLIB DD DISP=SHR,DSN=trgindx.LINK
//SYSTSPRT DD SYSOUT=*,LRECL=132,BLKSIZE=132,RECFM=FB
TCPEEP TRCSSID(ACTR) GROUPS(NETIF) +
To stop the TCPEEP batch job, issue the MVS STOP command (for example, P jobname).
Trace Data Collected
The trace facility collects the following type of trace data:
•From an application
•TCP/IP address space
Simultaneous tracing of various trace types can be fed into a single trace output.
Note If data is to be collected via the external writer to an external data set, you must use the MVS TRACE command. Read External Writer for more information.
Viewing Trace Data
TCPEEP collects real time data and by default writes to SYSTSPRT. Optionally, it can write to a dynamically allocated SYSOUT data set.
Trace Operation
Each occurrence of the TCPEEP command varies according to the type of environment.
To stop a trace, press the terminal ATTENTION key and enter H at the prompt (null entry will allow trace to continue).
Caution
TCPEEP should be installed in a protected library only. It can be used to display all network traffic through Cisco IOS for S/390, including user IDs and passwords.
TCPEEP Syntax
This section describes the TCPEEP syntax and describes its parameters.
TCPEEP [ASID(asid,...)] [BUFFERS (size, number)] [BUFFTIME (time_out)]
[DATASIZE (record_size)] [DNRSSID (ssid)] [FORMAT(format_options)]
[FULL | SUMMARY] [GROUPS(( group [,'filter')...)] [HALT]
[INSTANCE (instance_ID)] [JOBNAME (jobname,...)] [NOHEADER]
[PEEK (limit)] [SYSOUT (class)] [TRACESIZE (num_records)]
[TRCSSID (ssid)]
Syntax Description
ASID
(asid,...)
|
Specifies the address space identifiers (ASIDs) of address spaces used as a filter for tracing. Events in the ASIDs are recorded by the component trace.
The parameter contains a list of 0 to 16 hexadecimal ASIDs separated by commas. An empty ASID list, ASID=(), turns off filtering by address spaces. In the ASID parameter, list all address spaces to be traced. Address spaces for previous traces are not traced unless listed.
Default: None
|
BUFFERS
(size,number)
|
Specifies the size of the trace buffers in kilobytes and/or the number of buffers. size may be a value between 64 and 1024 with the default being 256. num may be a value between 2 and 128 with the default being 4. BUFFERS is optional and may only be specified whe |
