Operating System - OpenVMS
1826498 Members
1663 Online
109692 Solutions
New Discussion

Re: LAT always on ewa interface

 
Sigwarth_1
Occasional Contributor

LAT always on ewa interface

Hi
when we boot our new DS20E the LAT driver is always on the ewa interface. But we want use only one interface (eia0) for DECnetplus, TCP/IP and LAT. We do right now after each (re)boot:
LATCP> delete LINK LAT$LINK
LATCP> create LINK LAT$LINK /DEVICE=EIA0 /STATE=ON
Question: is there another way, to get the LATdriver on the eia interface permanent.
used VMS version 7.3-1 with some patches (issued before dec 2002).
The system disk are from the 3 years old DS20E system; almost the same (beside FW-version,CPU speed,graphics card) and a DE600 (dual port; eia,eib) instead a DE500 (single port); the ewa interface is from KZPCM (dual scsi/net)
Thanks
Erich
8 REPLIES 8
Martin P.J. Zinser
Honored Contributor

Re: LAT always on ewa interface

Hello Erich,

the trivial solution should be to put the commands you quote in a script and execute this in the system startup (after lat$startup ,-).

I will investigate tomorrow if there is a more permanent solution.

Greetings, Martin
Sigwarth
New Member

Re: LAT always on ewa interface

Martin,
that's what are we doing right now. But it's just a work around.
Thank's
Erich
Åge Rønning
Trusted Contributor

Re: LAT always on ewa interface

Define LAT$DEVICE in your sylogicals.com

$define /sys /exec lat$device eia0:

VMS Forever
Lokesh_2
Esteemed Contributor

Re: LAT always on ewa interface

Hi ,

Modify LAT$SYSTARTUP.COM accordingly. This is called by LAT$STARTUP.COM and used to create LAT link among other things...

HTH,
Lokesh
What would you do with your life if you knew you could not fail?
Antoniov.
Honored Contributor

Re: LAT always on ewa interface

Hi Erich,
in LAT$SYSTARTUP.COM HP posted this notice:
$!
$! If you have a system with multiple Ethernet/FDDI controllers, you may want
$! to create a link in this section of LAT$SYSTARTUP.COM before LAT is
$! started.
$!
$! When LAT is started on a system with multiple controllers, and no link is
$! is created, then the LAT driver will pick the first controller from the
$! LAN Data Structures as the default. This controller may not be connected to
$! the wire. LTDRIVER has no way of determining this condition. As a result,
$! it will not display an error message and LAT will hang.
$!
$! To define a link for LAT, do the following:
$! 1. Find out what controller is attached to the Ethernet/FDDI wire.
$! (In this example we will use EXA0)
$! 2. Insert the following command line before LCP SET NODE /STATE=ON command
$! below:
$!
$! LCP CREATE LINK 1ST$LINK /DEVICE=EXA0
$!
$! 3. If you have more then one controller attached to the wire, then
$! repeat the above command line, calling the next controller "2ND$LINK".

HP hints modify LAT$SYSTARTUP.COM to solve your problem.

H.T.H.
Antoniov

Antonio Maria Vigliotti
Sigwarth
New Member

Re: LAT always on ewa interface

Thanks to you all. You are really fast with your responses.
I like the define LAT$DEVICE version: I will test this tomorrow. I will respond.
Thanks again.
Erich
Willem Grooters
Honored Contributor

Re: LAT always on ewa interface

...and don't forget the points ;-)
Willem Grooters
OpenVMS Developer & System Manager

Re: LAT always on ewa interface

Looks like I'll plan a trip to Italy one day :-)

D.
(aka "the return of DTL")