Instruction manual

Installation Page 4-11
Eagle 450 Installation and Technical Manual, Rev. 00
AlphaTCP Setup
If your Eagle 450 is connected to a network, the AlphaTCP networking software allows any network
user—and any external user who has access to your network—to use the programs and files on the Eagle
450. To use AlphaTCP, which is included with AMOS on the Eagle 450, you must start various
background “server” jobs to handle the network traffic and other tasks, and assign memory for use by
people requesting a connection over the network.
The initialization file setup for using the AlphaTCP networking software can be involved, and in addition
to changing your initialization file, you need to modify the AlphaTCP configuration files at installation,
and possibly when you add new network users.
Configuring your initialization file to make the best use of your resources with AlphaTCP is too lengthy
a process to discuss here. Please see your
AlphaTCP Administrator’s Guide
, DSO-00187-00, especially
chapters 3 and 4, for detailed information and instructions.
When defining the network driver for the Eagle 450, in most situations you should use AM138.LDV for
best performance. In certain circumstances—for example, if you need to perform wildcarded AMOS
copy commands across the network—use AM138.NDV instead.
Changing User Memory
In addition to the operating system itself, the memory of the Eagle 450 is used by:
•
The serial ports on the AM-138 and any added I/O boards
•
Background processes, such as the AlphaTCP server programs
•
People connecting to the computer over the network
Whenever you change any memory allocation, you need to balance all three types of requirements.
You can display the current memory allocations on your computer using the STAT or SYSTAT
command. Neither STAT nor SYSTAT show how much memory is left in the SMEM memory
pool.
The amount of memory for each serial port and background process is set in a SETJOB statement in the
initialization file (except for serial port 0, which usually receives all of the memory not used for any
other purpose). Each network user, however, may be able to request a specific amount of memory when
he or she connects to the computer (depending on the AlphaTCP configuration, network users may be
assigned a memory size automatically). So, rather than assigning memory individually to each job, the
initialization file merely allocates a “pool” of memory for network jobs. When someone connects to the
Eagle 450, memory is taken from this pool and assigned to that network user; when the user disconnects,
the memory is returned to the pool.
The size of this memory pool is set by an SMEM (shared memory) statement in the initialization file.
The memory pool allocated by SMEM is also used for some other purposes, such as spawned MULTI
jobs, but for this discussion we’ll consider that it’s all available for network users.