LAT problem in dual host vax 4000/505 with VMS 6.2

[pri]

Any one can help me. I am looking after VAX 4000/505 servers working as a dual host.
Recently I observed that by giving command:
Set host/lat (to clent node). It is unable to remote login to client running with ultrix.
It is showing Message:
LAT is disable. Enable it.
But in other server this problem is not there.

Ido not know how to enable it. please help ne.

[RBrown_1]

LAT is started by SYS$STARTUP:LAT$STARTUP.COM.

This command file is normally run by SYS$MANAGER:SYSTARTUP_VMS.COM at boot time. You can search or view this file to confirm the that. It will also show how to run LAT$STARTUP.

This suggests that a problem at boot time prevented SYSTARTUP_VMS from completing, and other things that should have been done at boot time were also missed.

Has this node been recently rebooted? If you are lucky, your boot was logged into SYS$SYSTEM:STARTUP.LOG and you will be able to check it to find out what happened.

Failing that, you are left with one or more of:

: comparing these command files between the working and non-working nodes

: desk-checking the files

: backing out recent changes

: SET VERIFY in SYSTARTUP_VMS (and other files as required) and test reboots.

Once the problem is corrected, it may still be easier to reboot than to manually start everything missed by STARTUP_VMS.

hth

[Hoff]

Would this be the same VAX 4000 model 505 box that's (also?) tossing carrier check failures?

http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1247570

[Wim Van den Wyngaert]

Could LATACP been aborted due to the carrier check problem ? Check with what status it exited in accounting or check for operator messages. There is no log file of the process.

Wim

[Wim Van den Wyngaert]

If possible I would consider a reboot. This would also reset all "bad" counters.

Wim