- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - OpenVMS
- >
- LAT problem in dual host vax 4000/505 with VMS 6.2
-
- Forums
-
Blogs
- Hybrid Cloud
- Edge
- Data & AI
- Working in Tech
- AI Insights
- Alliances
- Around the Storage Block
- Behind the scenes at Labs
- Careers in Tech
- HPE Storage Tech Insiders
- Inspiring Progress
- IoT at the Edge
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Russia
- HPE Blog, UK & Ireland
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-08-2008 06:54 AM
07-08-2008 06:54 AM
LAT problem in dual host vax 4000/505 with VMS 6.2
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-08-2008 07:11 AM
07-08-2008 07:11 AM
Re: LAT problem in dual host vax 4000/505 with VMS 6.2
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-08-2008 07:37 AM
07-08-2008 07:37 AM
Re: LAT problem in dual host vax 4000/505 with VMS 6.2
http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1247570
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-08-2008 11:32 PM
07-08-2008 11:32 PM
Re: LAT problem in dual host vax 4000/505 with VMS 6.2
Wim
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-08-2008 11:34 PM
07-08-2008 11:34 PM
Re: LAT problem in dual host vax 4000/505 with VMS 6.2
Wim
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP