Shut Down
path is severed. The control blocks are released when the user is eventually logged
off. If SNA CCS gets the SEVER and there is a SNARBLOK but the user is not
disconnected, then SNA CCS disconnects the virtual machine associated with the SNARBLOK. To shut down the system, the VM/SP system operator should notify users that the
system is shutting down. If the SNA operator has the proper class, he can force off
any SNA user that did not log off. In this way, VM/VCNA can collect accounting
data for its users and record it in CPo The DISABLE SNA (userid) command can
be used to prevent additional users from logging on. In this way, VM/VCNA can
be stopped without bringing down the VT AM service machine that it is running in.
Any other application in the VTAM service machine may continue to run unaf­
fected.
VM/VCNA Operator Considerations
While it is possible for the operator of the VT AM service machine to disconnect
from a 'local' terminal, extreme care must be exercised. The VM/VCNA operator
must 'SET RUN ON' prior to disconnecting from the 'local' terminal. If the opera­
tor does not do this, unpredictable results occur and a deadlock of the VM/VCNA
is likely.
The operator of the VT AM service machine should never disconnect from the ser­
vice machine and then reconnect from a SNA logical unit, using the same operator
userid that was used for the service machine. That is, the operator must not logon
at a terminal that is managed by the VCNA as the VCNA Operator. SNA CCS Entries in CP Internal Trace Table
Trace Table Entry Formats SNA Console Communications Services (SNA CCS) creates trace table entries in
the CP Internal Trace Table to leave an audit trail of its activities. SNA CCS places an entry in the CP trace table for each inbound transaction; SNA CCS creates a trace table entry for each outbound transaction after going to the
Inter-User Communication Vehicle (lUCV) to communicate the entry to the
VM/VTAM Communications Network Application (VM/VCNA).
The entry identifies the type of lUCY transaction, the SNA user that initiated the
transaction, and the pertinent characteristics of the transaction environment itself.
The transaction can be correlated throughout the system by the use of the CCS and
VCNA path id's and the IUCV message id. These fields can be matched with cor­
responding or similar fields in the IUCV trace elements in CP and VCNA trace
elements in VT AM.
For an error trace, SNA CCS places an entry in the CP trace table for logical errors
and errors on IUCV transmissions. If the WEBLOK that is passed between SNA CCS and VM/VCNA is invalid, the data in the trace element pertains to the inval­
id WEBLOK. The following tables show the formats of trace table entries created by SNA CCS. SNA Virtual Console Communication Services 187

o
8
o 8 o
o
o ACCEPT (00) (VTAM service machine and Logical Unit) CONNECT for Logical
Unit (12)
1 2 3 4 5 6 7
X'16' !TRATNTypl / / / / / / / / ! TRAVCSPA I / / / / / /
TRAUDATA
RECEIVE (04), REPLY (06), SEND lWAY (08), SEND 2WAY (09), LOGIC ERROR in CCS WEBLOK (OB), LOGIC ERROR in VCNA WEBLOK (13)
1 2 3 4 5 6 7
X'16' TRATNTYP TRAMODE TRALGAID TRAVCSPA I TRAVSAPA TRAFUNCT TRACPSAF TRAEDCHR TRACHAR TRAMSGID SEVER (OA) 1 2 3 4 5 6 7
o X'16' ITRATNTypITRAUSER11/ / / / I TRAVCSPA I / / / / / /
8 TRAUDATA
o 8 o REPLY from VCNA (OC) 1 2
X' 16' TRATNTYP TRAMODE
TRAFUNCT TRACPSAF TRAUDITI
3
TRALGAID
TRAUDIT2
4 5 6 7 TRAVCSPA f TRAVSAPA TRAMSGID QUIESCE from VCNA (OD), RESUME from VCNA (OF) o 8 o
X'16'
188 VM/SP System Programmer's Guide
1 2 3 4 ITRATNTypl / / / / / / / / I TRAUDATA
5 6 7 TRAVCSPA I TRAVSAPA