SNACONTROL START
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| Index |
Syntax
SNACONTROL START;NODE=NodeName
[;LINKTRACE[=[TraceType][,TraceFile]]]
[;NODETRACE[=TraceFile]]
[;ERROPT=ErrorOption]
[;TFILESIZE=NumRecords]
Use
SNACONTROL START can be issued from a session, a job, a program, or in break. Pressing [BREAK] has no effect on this command.
Parameters
- NodeName
Conditionally required. The name of the configured SNA node you want to start. The name can be up to eight alphanumeric characters long; the first character must be alphabetic.
If only one SNA node is configured, this parameter is optional: If you do not include it, the configured node is started. If more than one node is configured, this parameter is required: If you do not include it, a list of all configured nodes is displayed, but no node is started; you can then reissue this command with the appropriate node name.
- TraceType
The kind of link-level tracing to be started:
FULL = Full line tracing: All of the bytes of each link frame are traced.
PARTIAL = Partial line tracing: Only the first 16 bytes of each link frame are traced.
- TraceFile
The name of the disk file that is to contain the trace data. This must be a valid MPE file name or fully qualified MPE file reference. Note that standard MPE file naming conventions apply, with one exception: When link-level tracing is started with this command (SNACONTROL START), its file must be written to the SYS account. If you specify an account other than SYS, an error will occur. If you do not specify an account for a link-level trace file, the file will automatically be written to the SYS account.
If you specify a file that does not exist, NMS builds a new one and opens it to record tracing. If you specify an existing file that NMS does not currently have open to record tracing, NMS will overwrite the file's previous contents; no warning is issued. If you specify an existing file that NMS already has open to record tracing (even if it is recording events from a different subsystem), NMS will record trace events for this subsystem to the file in addition to the events that it is currently recording. This allows you to record tracing events from several subsystems to a single file.
Default: NMTCnnnn.PUB.SYS, where nnnn is a number from 0000 through 9999 and is incremented each time a new file is created.
- ErrorOption
The action to be taken if SNA Transport detects an irrecoverable internal error:
SUB = Terminate SNA Transport. HP e3000 system processing continues.
SYS = System failure. HP e3000 system processing stops. This allows you to dump the system when an irrecoverable internal error has occurred.
Default: SUB
NOTE: Use the SYS option only when requested by your Hewlett-Packard support contact.- NumRecords
The file size, in units of 128-word records, for link-level tracing.
Range: 1-32767 (integer)
Default: 1024
Description
SNACONTROL START starts an SNA node. You also can start link-level tracing (with the LINKTRACE parameter), and SNA Transport node tracing (with the NODETRACE parameter) with this command. Note that SNA Transport intrinsic tracing is started with SNACONTROL TRACEON. Tracing is described in Chapter 5 "SNA Link Troubleshooting" of this manual. You must start the SNA node before starting any SNA services that use the node. If you are using a manual-dial modem, you can begin to dial after this logging message is displayed on the console: Node NodeName ready for activation by host Note that if you are using a manual-dial modem, console logging for SNA Transport logging class CLAS0013 must be enabled (see Chapter 3 "Logging Configuration") so that the above message can be displayed. Also, note that once a node is active, reissuing this command for that node causes an error. For example, if node IBMNODE is already active, and you try to start node tracing for that node by typing SNACONTROL START;NODE=IBMNODE;NODETRACE you will get an error message.
Examples
SNACONTROL START;NODE=IBMNODE;LINKTRACE;ERROPT=SUB The node IBMNODE is to be started. Also, partial (the default) link-level tracing is to be started, and the trace data is to be written to the default trace file (as explained earlier, it will automatically be written to the SYS account). If SNA Transport finds an irrecoverable internal error, SNA Transport is to be terminated, but HP e3000 processing is to continue. (Note that if the ERROPT parameter was not specified, the same action would be taken for an irrecoverable internal error, because ERROPT=SUB is the default.) SNACONTROL START;LINKTRACE=FULL,TF01;NODETRACE The only configured node is to be started. Also, full link-level tracing (written to the file TF01 in the SYS account [as explained earlier]), and node tracing (written to the default file) are to be started. Note that if more than one node was configured, this command would not be valid: A list of configured nodes would be displayed, and the command would have to be reissued with the proper NODE=NodeName parameter included. SNACONTROL START;LINKTRACE=,TF01 The only configured node is to be started. Also, partial (the default) link-level tracing is to be started, and the trace data is to be written to the file TF01 in the SYS account (as explained earlier). Note that if more than one node was configured, this command would not be valid: A list of configured nodes would be displayed, and the command would have to be reissued with the proper NODE=NodeName parameter included. SNACONTROL START;LINKTRACE=;NODETRACE This command is not valid because the equal sign is specified with the LINKTRACE parameter, but no values are specified after it (the equal sign should be included only if one or both of the values after it are specified); an error would occur.|
SNACONTROL AUTODIAL |
SNACONTROL STATUS |