March 12, 1990 M20-4, Part II

Change 1

CONTENTS

CHAPTER 14. SNA (SYSTEMS NETWORK ARCHITECTURE) EMULATION SOFTWARE

PARAGRAPH PAGE

14.01
Purpose\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\.....
14-1\
14.02 Reference
Materials\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
14-1\
14.03 Hardware
Requirements\...\...\...\...\...\...\...\...\...\...\...\...\...\...\.....
14-1\
14.04 SNA (Systems Network Architecture) Configuration
Standards\...\...\.... 14-1\
14.05 3274 EMULATOR
SOFTWARE\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
14-2\
14.06 3777-3 EMULATOR
SOFTWARE\...\...\...\...\...\...\...\...\...\...\...\...\...\..... 14-2\
14.07 SNA Startup and Shutdown
Procedures\...\...\...\...\...\...\...\...\...\...\... 14-2\
14.08 Weekly Housekeeping
Procedures\...\...\...\...\...\...\...\...\...\...\...\..... 14-4\
14.09 Printing Through SNA
Emulation\...\...\...\...\...\...\...\...\...\...\...\..... 14-5\
14.10
Troubleshooting\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\.....
14-6

14-i

March 12,1990 M20-4, Part II

Change 1

**CHAPTER 14. SNA (SYSTEMS NETWORK ARCHITECTURE) EMULATION SOFTWARE**

14.01 PURPOSE

This chapter provides information needed by the individuals involved in
the installation, management and monitoring of the VS SNA 3274 and
3777-3 Emulator Software. This chapter provides examples of the standard
SNA configuration parameters and troubleshooting guidelines. Appendix D
contains instructions for the use of 3274 emulation and appendix E
contains instructions for the use of 3777-3 emulation.

14.02 REFERENCE MATERIALS

The following should be maintained for reference. Refer to Wang\'s
Literature Catalog for the most recent version.

a\. VS System Administrators Reference (715-0420)

b\. VS SNA 3274 Emulator System Administrators Guide (800-1333C)

c\. VS SNA 3777-3 Emulator System Administrators Guide (800-1464C)

d\. VS SNA 3274 Emulator Users Guide (800-1332D)

e\. VS SNA 3777-3 Emulator Users Guide (800-1330D)

f\. VS 3274 Emulation Keyboard Map

g\. VAaccess Helpbook for Austin Timeshare users

14.03 HARDWARE REQUIREMENTS

Each VS System that accesses Wang SNA 3274/3777 emulation through the
VADATS network must have the following hardware:

a\. Available port on a serial IOC (and four logical ports)

b\. Telecommunications processor (6554)

c\. 64K Communications Controller (VS-TC) (a 128K communications
controller, VS-TC1, will work, but is not necessary. If using a 128K
board, it must be configured through Genedit as a TCB3 rather than a
TCB1)

d\. RS232 cross-over cable from Wang 6554 to Tymnet mini-engine

e\. Dual coaxial cable from 6554 to CPU (Central Processing Unit)

14.04 SNA CONFIGURATION STANDARDS

Most of the parameters in the SNA configuration have been standardized
by VBA (Veterans Benefits Administration). These standards are necessary
to assist in troubleshooting, and ensure that all local configurations
are done property. The SNA software configuration provided to the
regional offices from ADP Systems Management follows the standards that
have been set for SNA on Wang systems. These basic configurations should
not be modified locally, except for the print mode and print class
specifications. The standard naming conventions identified below should
not be modified by the local system administrator.

14-1

M20-4, Part II March 12, 1990

Change 1

ITEM 3274 3777-3

SNA Configuration file SNASOURC in @ SYSTEM@ SNASOURC in @ SYSTEM@

LOG file name LOG 1 in LOG3274 LOG1 in LOG3777

Log file retention period Five Days Five days

Owner of Record for Files SA\'s Initials SA\'s Initials

Printer Names PR999A, PR999B PR9991, PR999B

(999 is Station Number)

Finename prefix for Host files 3274 3777

Library for Host #3274PRT #3777PRT

Filename prefix for Local files 3274 N/A

Library for Local files 3274LIB N/A

Inbound Logical Devicce Names N/A ISTREADER, 2NDREADER

Outbound Logical Device Name N/A PUNCH1

Filename prefix for Host files N/A PUNC

Lobrary for Host files N/A 3777LIB

14.05 3274 EMULATOR SOFTWARE

a\. The VS 3274 Emulator Software allows a VS system to function as an
IMB cluster controller unit with printers and workstation logically
attached to it. The emulator software enable the VS to communicate with
the IBM host using the SDLC (Synchronous Data Link Control) protocol
convention. The 3274 SNA software allows a VS workstation to emulate an
IBM terminal. When the VS user is attached to the host system, all
processing is being performed on the host. Ussers are able to generate
screen printers and reports that will be queued for printing on local
system.

b\. An example of VBS\'s use of 3274 emulation is in the local access to
CALM (Centralized Accounting for Local Managemnet. The application
allows regional office personnel to eliminate code sheets by directly
inputting information into the Austin database using 3274 emulation.

14.06 3777-3 EMULATOR Software

a\. The VS SNA 3777-3 Emulator software allows file transfer through
RJHE (Remote Job Entry) form the Wang VS to the IBM host. Before the
files can be transferred to the host system, a logon message myst be
sent forn the Wang system to the host system. A procedure has been
developed whihc can be submitted after the SNA link has been brought up.
This procedure, CONNECT in the SYSPROC library, submits the SSCP (System
Service Control Point) logon message through the CONSOLE program the
host system. Once this message is accepted by the host, the line is
available for transfers. The SA can verify that SSCP message has been
accepted by viewing the system status through the SNA CP (Contrl
Facility). The activation level of the line should be data flow idle
when the message has been accepted.

b\. The LPS (Loan Processing System) is an example of one othe the VBA
applaction that utilizes the 3777-3 emulation for the transfer of a file
to the Austin host for processing.

14.07 SNA STARTUP AND SHUTDOWN PROCEDURES

The following guidelines have been established to assist VBA system
adminstrators in the daily operation of the Wang SNA emulator software.
Procedures have been developed by VA Central Office and Transferred to
each station at the time of instatallation for use by the SA.

14-2

March 12, 1990 M20-4, Part II

Change 1

a\. Starting SNA

\(1\) The SNA software requires one background procedure to be running
in the queue at all times in order to establish 3274 and 3777 sessions.
Before the SNA background task can be submitted, the WSN (Wang Systems
Networking) software must be running on the VS. Refer to chapter 3 for
starting WSN on the VS. To start SNA on the VS, perform the following
steps:

\(a\) From the Command Processor, press PF12, Submit a procedure.

\(b\) Enter File=STARTSNA, Library=SYSPROC, Volume=system volume (SI),
press the return key.

\(c\) Verify the procedure has been submitted properly. Check the
procedure queue to see that the STARTSNA procedure is in the queue with
a status of running.

\(d\) From the Command Processor, press PF1 to Run a program. Enter
File=SNACF and press the return key.

\(e\) The next screen will prompt for the PU (Physical Units) name. Each
system has been assigned one link with two Physical Units in the
SNASOURC configuration file. The first PU on the link is for the 3274
emulator software; the second is for the 3777 emulator software. Enter
the first PU name and press the return key.

\(f\) From the mainmenu, press PF11 to Display System Status. The Link
status should be a \'C\' when the link has connected. If the Link
status=\'C\', exit SNACF. If the link has not connected yet, refer to
section 14.10 Troubleshooting.

\(g\) When the line has connected, go to the Command Processor and press
PF12, Submit a procedure. Enter File = CONNECT, Library = SYSPROC,
Volume = system volume (S 1). This procedure will stay in the procedure
queue approximately 45 seconds. This submits a SSCP logon message to the
Austin host to permit the transfer of files using 3777-3 emulation.

\(h\) Verify that the logon message has been accepted by the host
system. From the Command Processor, press PF1 to Run a program. Enter
File=CONSOLE and press the return key.

\(i\) The next screen will prompt for the PU name. Enter the second PU
name that has been assigned to the systems Link.

\(j\) At the Console mainmenu, press PF1 I for session status. The
Activation level of the 6 LUs (Logical Units) configured should say data
flow idle. If the screen shows LU active or any other message, try
submitting the connect procedure again. If this does not correct the
problem, refer to paragraph 14. 10 Troubleshooting.

\(2\) Once both procedures have been submitted, the SA should verify the
connection to the Austin system by running the SNALOGON procedure and
attach to the host. To verify the file transfer capability, a test file,
TEST3777 in library SYSPROC was transferred to each system during the
installation. This file can be submitted to Austin using the RJE
program.

b\. STOPPING SNA

\(1\) The SNA background task must be stopped prior to stopping the WSN
tasks and performing an IPL (Initial Program Load) on the system. Before
cancelling the background procedure, the SA should verify that all users
have properly ended their 3274 emulation sessions and all 3777 file
transfer jobs have completed. The following procedures are step-by-step
instructions for stopping SNA on the system.

\(a\) Ensure that all users have completed their jobs. From the
Operators Console, press PF6, interactive tasks. Verify that none of the
users are running a program named SNATTACH, REMSNA, RJE or CONSOLE.

14-3

M20-4, Part II March 12,1990 Change 1

\(b\) From the Command Processor, press PF12, Submit procedure. Enter
the File=CONEND, Library=SYSPROC, Volume= system volume (SI), press the
return key.

\(c\) From the Command Processor, press PF 1 2, Submit procedure. Enter
the File = STOPSNA, Library = SYSPROC, Volume= system volume (SI), press
the return key.

\(d\) Both procedures will stay in the procedures queue for less than a
minute before they drop out. Once they have both completed, the STARTSNA
procedure should disappear from the queue.

\(2\) Once these steps have been performed, the system can be shut down
following the procedures outlined in chapter 3. If the STARTSNA
procedure does not drop out of the procedure queue after STOPSNA has
been submitted, the procedure can be manually cancelled. From the
Operators Console, press PF7 for non-interactive tasks and position the
cursor on the STARTSNA procedure. Press PF12 to cancel the procedure.

14.08 WEEKLY HOUSEKEEPING PROCEDURES

The SNA emulation software creates two log files that track activity on
the line. These files are defined in the SNA configuration file.
Additionally, user generated prints may accumulate on the system if the
print mode has been set on hold and the print disposition has been set
to keep. To reduce the number of these files on the system, the SA
should delete old prints and purge the log file weekly. The 3274 and
3777 log files must be purged separately, although the procedures are
similar.

a\. To purge the 3274 log file:

\(1\) From the command processor, press PF 1, Run Program and enter
SNACF.

\(2\) At the next screen, enter the PUNAME for the PU configured for
3274.

\(3\) From the Mainmenu, press PF 12, Display Log File.

\(4\) From the Display screen, press PF 15 to print.

\(5\) On the Printlog screen, change PRNTMODE=\'S\' and PURGE=YES and
press the return key to print and purge the log file. The file will
spool to print. If you prefer to hold the print file and release it from
the print queue later, leave PRNTMODE=\'H\'.

\(6\) From the Displog screen, press PF I to return to the Mainmenu.

\(7\) At the Mainmenu, press PF 16 to exit.

b\. To purge the 3777 log file:

\(1\) From the command processor, press PF 1, Run Program and enter
CONSOLE.

\(2\) At the next screen, enter the PUNAME for the PU configured for
3777.

\(3\) From the Mainmenu, press PF 12, Display Log File.

\(4\) From the Display screen, press PF 15 to print.

\(5\) On the Printlog screen, change PRNTMODE=\'S\'and PURGE=YES and
press the return key to print and purge the log file. The file will
spool to print. If you prefer to hold the print file and release it from
the print queue later, leave PRNTMODE=\'H\'.

14-4

March 12, 1990 M20-4, Part II

Change 1

\(6\) From the Displog screen, press PF I to return to the Mainmenu.

\(7\) At the Mainmenu, press PF 16 to exit.

14.09 PRINTING THROUGH SNA EMULATION

Each of the two emulation packages have the ability to generate prints
to a local VS system printer. Through the definition of the Host File
Parameters screens and Local Copy Options, the System Administrator can
decide how prints generated from applications resident on the host
system will be printed locally.

a\. 3274 EMULATION PRINTING

\(1\) When a user accesses the host system using 3274 emulation
software, prints can be generated as either a screen print using the
Local Copy Option or a print file using the Host File option. These
prints return to the system and are created and named using the
parameters from the SNA configuration file. To print screens using the
Local Copy Option:

\(a\) Once a user has logged into the Austin host, prints can be
generated from any of the screens.

\(b\) On the Wang keyboard, the user presses the print key on the
numeric keypad.

\(c\) The message line at the bottom of the screen shows a message \"KBD
PRINTING\" while the print is being created.

\(d\) When the print returns to the VS system, it will be displayed in
the print queue, with the file name prefix 3274 in library 3274 LIB. The
print mode and disposition will be extracted from the configuration
file.

\(2\) To Print files using 3274 emulation:

\(a\) After a user has entered a specific application on the host
system, prints of specific files can be requested through a series of
commands. More specific information is contained in the user guides for
the individual applications.

\(b\) The user must identify the printer name of the printer that has
been configured for the system. For example, the printer name for
station 339 would be PR339A or PR339B.

\(c\) Once the print requests have been made, the files are transfeff ed
back to the VS system. Since these files are considered \"host\" files,
they are named according to the Host File Parameter option in the SNA
configuration.

\(d\) The prints will have a file prefix of 3274 and will reside in the
library #3274PRT. The print mode and disposition will be extracted from
the configuration file.

b\. 3777 PRINTING

\(1\) When files are transferred through 3777 emulation, prints may also
be generated on the VS system. Prints generated from a 3777 transfer or
as output as a result of the transfer, are named according to the
parameters defined in the SNA configuration.

\(2\) All prints as output will reside in the #3777PRT library. The file
may be named through the application that has generated the output, or
may use the prefix 3777. These files will extract the print mode and
disposition from the SNA configuration file.

14-5

M20-4, Part II March 12,1990 Change 1

\(3\) If the print parameters defined in the SNA configuration reflect
local print options, such as a print class of \'D\' and a DP (data
processing) printer on the system as a \'D\' print class scheduled, the
prints generated from the host can spool directly to a printer without
operator intervention. The ability to print also depends on the
configurations at the host system. If there is a problem printing, and
the local configuration has been done properly, the SA may need to
contact the Austin help desk to ensure that the correct printer names
have been configured on the host system.

14.10 TROUBLESHOOTING

a\. The Tymnet transport is used to establish communication sessions
between the local system and the remote IBM host. The troubleshooting
guidelines presented below should be used by the VBA Node Administrators
when identifying and isolating problems on the local system. If problems
exist that cannot be resolved locally, the VBA Network Coordinator
should be contacted for assistance and problem resolution.

b\. Normal Operations following IPL. The TCB1 lights on the front panel
of the 6554 provide an indicator of connectivity between the Wang VS and
the Tymnet mini-engine. Following IPL of the VS, the following LED
(Light Emitting Diode) lights should be displayed on the front panel of
the 6554 cabinet:

LED STATUS AND INTERPRETATION

7 Lit continuously indicating that the TCB1 hardwarc is operating
properly.

8 Blinking rapidly (several) times a second indicating that the
microcode has becn succcssfully downloaded to the TCB1.

c\. Normal Operations During Active Communications Sessions. TCB1 lights
on the front panel of the 6554 should be blinking in the following
manner to indicate normal operations and an active link.

LED STATUS AND INTERPRETATION

1 A slow blink, about once every two seconds.

2, 3, 8 Lit continuously while the link is up and connected.

4, 5, 6 Blinking rapidly at the same time.

d\. Possible Error Conditions and Troubleshooting Guidelines.

\(1\) LED 8 Solid. If LED 8 is solid at any time following IPL, this
indicates that either the TCB1 diagnostics are running or that a TCB1
hardware error has been detected by the diagnostic program. If LED 7 is
flashing the microcode is not loaded to the TCB1 and a hardware problem
is suspected. Before placing a call to Wang Customer Engineering, the
Node Administrator should verify the following:

\(2\) Physical Connectivity Is Correct. Check that the connectors are
solidly attached at both ends of the coaxial cables that connect the VS
to the 6554. In addition, verify that the cross-over cable is coff ectly
attached to the TYMNET mini-engine. Check that the coaxial cables that
run from the CPU are connected to the correct port (as specified in the
GENEDIT file @ CONFIG@).

\(3\) SNA Connectivity Cannot be Established. Run the SNATTACH program
verifying that the coff ect PU name is used. When the session is not
established, the attach screen fig. 14-1 will return with an error
message.

14-6

March 12, 1990 M20-4, Part II

Change 1

\*\*\* MESSAGE 0000 BY ATTACH

INFORMATION REQUIRED BY PROCEDURE JLOGOFF

TO DEFINE INPUT

ACTIVE PROGRAM IS SNATTACH

WANG VS 3270 ATTACHMENT PROGRAM

PLEASE SPECIFY THE FOLLOWING INFORMATION, OR PRESS PF16 TO EXIT.

PU = AR9ACUA\*\*\*\*\*\*\*\*\* PHYSICAL UNIT NAME

LU = 00 LOGICAL UNIT ADDRESS (PU WILL ASSIGN

LU NO. IF TH FIELD IS LEFT ZERO)

MODEL = 002 EMULATED TERMINAL TYPE

KEYBOARD = UPPER SET TO "UPLOW" TO ALLOW LOWER CASE

NUMERIC FIELD LOCK = YES SET TO "NO" TO ALLOW ALPHABETIC

CHARACTERS IN NUMERIC FIELDS.

DETACH = YES SET TO "YES" TO DETACH WORKSTATION

WHEN SESSION TO UNBOUND

LOGON =
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

**Figure 14-1. SNATTACH screen**

\(4\) Link does not connect. If all of the cable connections are in
place, check to see if the STARTNSA procedure is in the queue.

\(a\) Background procedure is not running. Check the procedures queue to
verify that the STARTSNA procedure is not in the queue. If the procedure
is not in the queue or the procedure is in the queue, but the status is
not running, check to see that there is an available initiator. If there
is not one, create it.

\(b\) Background procedure is not running. From the Command Processor,
press PF1 to Run a program. Enter File= SNAMCP, press the return key.
Enter the LINKNAME (as defined in the SNA configuration file) and press
the return key. If the link is connecting, the message SNAMCP EXECUTING
will be displayed. If there is a possible Wang hardware or software
problem, the program will end with a return code. Refer to the 3274
Emulator SNA System Administrators Guide to determine what the code
means.

\(c\) Background procedure is running. If the SNATTACH program still
does not connect, run the SNACF program to determine the status of the
Link. From the Command Processor, Press PF1 to Run a Program. Enter
SNACF in the Program field and press the return key. The next screen
that will appear will prompt for the PU name. Enter the PU name for the
first PU on the Link and press the return key. The SNACF Mainmenu will
appear (fig. 14-2). Press PF11 for System Status. The SYSSTAT screen
appears (fig. 14-3). If the Link has connected, the LINKSTAT=C,
PUSTATE=A, and LUBOUND=# of active workstations at that time. This will
assist the SA in determining if the VS hardware is operating properly.
If the LINKSTAT=P, the connect is pending. This indicates that there may
be a problem with the Tymnet mini-engine or at the host end. The SA
should call the Romney, West Virginia help desk (FTS 8-651-3001) to
determine if the microcode has been properly loaded to the mini-engine.

*NOTE.- If the mini-engine has experienced a power outage, the microcode
may need to be reloaded. This must be done by the Romney help desk.*

14-7

M20-4, Part II March 12,1990

Change 1

06:41:38 04/26/89 From SSCP on Session 9

USSMSG10: AR9AA08 WELCOME TO VTAM VERSION 3 RELEASE 1 FROM AUSTIN

08:15:00 04/26/89 Event recorded by 3270 LU 2

Negative response sent to host - while in SM: Smmain: SM_ss_norm:
Request

rejected -- 082D0000.

09:36:16 04/26/89 Event recorded by LU 3

A negative response to an expedited request has been sent (sense code =

08450000).

\*\*\* Wang VS SNA Control Facility - Version 02.62.00 \*\*\*

MAINMENU Select a function by pressing the appropriate PF key:

\(1\) Reselect PU (11) Display System Status

\(2\) Connect Link (12) Display Log File

\(3\) Disconnect Link

\(4\) Terminate SNAMCP (16) Exit Program

**Figure 14-2. SNACF Mainmenu**

\*\*\* Wang VS SNA Control Facility - Version 02.65.03 \*\*\*

SYSSTAT Link Status ........................ LINKSTAT = C

PU state ............................ PUSTATE = A

Number of LU's Bound .......... LUBOUND = 2

LU states

LU [1]{.underline} [2]{.underline} [3]{.underline} [4]{.underline}
[5]{.underline} [6]{.underline} [7]{.underline} [8]{.underline}
[9]{.underline} [10]{.underline} [11]{.underline} [12]{.underline}
[13]{.underline} [14]{.underline} [15]{.underline} [16]{.underline}

N L L S S S S S S S S S S N N N

User F60 L37

LU [17]{.underline} [18]{.underline} [19]{.underline} [20]{.underline}
[21]{.underline} [22]{.underline} [23]{.underline} [24]{.underline}
[25]{.underline} [26]{.underline} [27]{.underline} [28]{.underline}
[29]{.underline} [30]{.underline} [31]{.underline} [32]{.underline}
[33]{.underline}

N N N N N N N N N N N N N N N N N

User

Link State PU State LU State

User

P = Connect Pending I = Inactive N = Not Configured User attached

C = Connected A= Active I = Inactive to a 3270 W/S

W = Disconnect Pending B = Blocked S = SSCP Session \*\*\* = 3289/3777

D = Disconnected L = LU Session attached L

Press (ENTER) TO Update Status or one of the following PF keys:

\(1\) Return to Previous Menu (16) Exit Programs

Figure 14-3. SNACF Link Status Screen

14-8

March 12,1990 M20-4, Part II

Change 1

\(5\) Link connects, but RJE entry does not work. if the STARTSNA task
is running in the queue and 3274 Emulation is working properly, but
files will not transfer using 3777-3 Emulation, the CONNECT procedure in
SYSPROC may not have been submitted or accepted by the host.

\(a\) Try submitting the Connect procedure. From the Command Processor,
press PF12 to Submit a procedure. Enter File=Connect, Library=Sysproc,
Volume=System Volume (S1), then press the return key. This procedure
should send the SSCP logon message to the host. Wait five minutes and
then run the Console program to determine the status of the Link.

\(b\) From the Command Processor, press PF1, to Run a program. Enter
Console in the File field and press the return key. The next screen will
prompt for the PU name. Enter the second of the two names assigned to
the Link. The Console Mainmenu will appear (fig. 14-4). Press PF I 1 for
Session Status. The STATUS screen appears (fig. 14-5). If the Connect
procedure has been submitted and accepted by the host system, the six
LUs configured should have an Activation Level of data flow idle. If the
procedure did not complete properly, the Activation level would show
\"lu active\". If any other message appears in the Activation Level
field, there may be a problem at the host end. Contact the Austin Help
Desk (FTS 8-770-7514) to verify that the host end is configured
properly.

06:41:18 04/26/89 From SSCP on Session 5

USSMSG10: AR9AB05 WELCOME TO VTAM VERSION 3 RELEASE 1 FROM AUSTIN

06:41:19 04/26/89 From SSCP on Session 4

USSMSG10: AR9AB04 WELCOME TO VTAM VERSION 3 RELEASE 1 FROM AUSTIN

06:41:19 04/26/89 From SSCP on Session 3

USSMSG10: AR9AB03 WELCOME TO VTAM VERSION 3 RELEASE 1 FROM AUSTIN

06:41:19 04/26/89 From SSCP on Session 2

USSMSG10: AR9AB02 WELCOME TO VTAM VERSION 3 RELEASE 1 FROM AUSTIN

04/26 \*\*\* Wang VS 3-777-3 RJE Operator Console - Version 02.60.04

MAINMENU Select a function by pressing the appropriate PF key:

\(1\) Send Job (11) Display Session Status

\(2\) Send SSCP Message (12) Display Log File

\(3\) Send LU Message (13) Dump Trace Table

\(14\) Run Program or Procedure

\(5\) Control Readers (15) Manage Print Queue

\(6\) Control Outbound Devices (16) Terminate Program

Figure 14-4. Console Mainmenu

14-9

M20-4, Part II March 12,1990

Change 1

Apr 26, 1989 \*\*\* Wang VS 3777 Emulation - Version 02.60.04 \*\*\*
9:42 am

Session Status

for PU AR9ACUB

Press (ENTER) to update session status.

Sess. Activation State Device File Library Volume

Numb. Level

1 data flow idle

2 data flow idle

3 data flow idle

4 data flow idle

5 data flow idle

6 data flow idle

\(1\) RETURN

Figure 14-5. Console Status

14-10