Alpha Microsystems Eagle 100 Instalační příručka stáhnout pdf (Strana 29)

Page 3-12 Chapter Three

AlphaNET Installation Guide, Revision 05

This is similar to the traditional TRMDEF statement. The #10 causes 10 TCBs with associated terminal

buffers to be made available for use by remote job connections.

You can have only one TRMDEF #count statement in your initialization file. If you have more than one,

all of them after the first are ignored.

For best results, the special TRMDEF statement described above should be the last TRMDEF

statement in your system initialization command file.

In AMOS 2.3 and later, each TCB you allocate in this way counts as a user toward your AMOS license.

Therefore, the total number of real terminals defined in your initialization file plus the number of TCBs

defined by TRMDEF #count must be equal to or less than your AMOS user license. If you try to allocate

more TCBs than you have jobs available, you see an error message and only the number of TCBs you

have available under your AMOS license are allocated.

Creating Communication Zone (Type 2 CONECT Support)

In order to support remote connections requested by CONECT, the host computer must have a special

communication “zone” defined in the initialization command file. This zone is part of the interface

between the Ethernet network driver and the spawned jobs created as the result of a CONECT connection

request. To set up this area, an ETHZON statement must be added to the system initialization command

file. The syntax is simply:

ETHZON maxjobs

maxjobs is the maximum number of CONECT connections to be supported at any given time. The

maxjobs number should match the number listed in the special TRMDEF statement described above.

Example:

ETHZON 10

This statement, when added to your system initialization command file, would allocate an Ethernet

communication zone large enough to support a maximum of 10 virtual terminal connections created by a

CONECT request. Make sure you insert the ETHZON statement after the TRMDEF statements and

before the first NETINI command.

TESTING THE NEW INITIALIZATION COMMAND FILE

After making the changes described above, log into DSK0:[1,2] and test your new initialization

command file using the MONTST command. For AMOS/L systems, enter:

MONTST AMOSL.MON,TEST.INI

RETURN

For AMOS/32 systems, enter:

MONTST AMOS32.MON,TEST.INI

RETURN

If the computer doesn’t reboot properly, press your computer’s RESET button to reboot under your

original initialization file. Re-check TEST.INI for mistakes and try again.

1 2 ... 24 25 26 27 28 29 30 31 32 33 34 ... 41 42

Žádné komentáře

Alpha Microsystems Eagle 100 Instalační příručka Strana 29