Installation guide

Installing the AlphaNET Software Page 3-11
AlphaNET Installation Guide, Revision 05
Why Use Type 2 Connections?
Type 2 connections provide substantially higher performance than the standard Type 1 connections. With
Type 1 connections, all communication between the connecting terminal and the host computer go
through a single job, VTSER. This makes VTSER a bottleneck when multiple connections are in effect,
slowing down communication. With Type 2 connections, most of the communication takes place directly
between the connecting terminal and its spawned job on the host, freeing up VTSER for improved
performance.
In addition to improved performance, Type 2 connections also provide 8-bit character support and the use
of the AMOS command line editor.
Type 2 Virtual Terminal Restrictions
The most important point to keep in mind when defining the enhanced Type 2 virtual terminal
connections is that they are “real jobs” that count against the licensed number of jobs allocated in your
AMOS operating system. Every TRMDEF statement in your system initialization command file that
defines the use of a physical port represents a real job. Make sure the number of enhanced virtual
terminal connections you define in the special TRMDEF and ETHZON statements (when added to your
existing real jobs) does not cause you to exceed the number of licensed jobs in your AMOS operating
system.
If there are more enhanced virtual terminal connections defined than your AMOS port license supports,
no TCBs will be allocated for enhanced virtual terminal connections.
The number of jobs defined in the JOBS statement at the top of your system initialization
command file must be equal to, or greater than, the total number of jobs you wish to support at
any given time. This includes all real jobs, which includes enhanced virtual terminal connections,
plus all PSEUDO jobs.
If you define five (for example) as the number of Type 2 virtual terminal connections for your computer,
any virtual terminal connections beyond five will use the standard, non-enhanced Type 1 connections.
TRMDEF Statement (Type 2 CONECT Support)
The purpose of this special TRMDEF statement is to allocate a pool of Terminal Control Blocks (TCBs)
to be used by jobs “spawned” by VTSER in response to a remote connection request issued by
CONECT. Note that this is applicable only when using Ethernet as a network transport device.
The TRMDEF command line syntax for allocating TCBs is:
TRMDEF #count Inwidth,Inbuffer,Outbuffer,Editor=#-of-recall-buffers
Example:
TRMDEF #10 100,100,100,EDITOR=10