- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: System permanent logical names
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2008 03:13 AM
тАО12-03-2008 03:13 AM
Re: System permanent logical names
The last thing to do is to add the definition to SYLOGICALS.COM
/Hakan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2008 03:26 AM
тАО12-03-2008 03:26 AM
Re: System permanent logical names
The file is sys$manager:sylogicals.com. But as said, this is the last step.
If you did what you said, it should work.
As it's not working, something is wrong.
1) on a different node ? Note that 1 name can point to many nodes (e.g. cluster alias, lat services)
2) some tricky stuff with logicals (post in attachement show log/tab=*/fu)
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2008 04:50 AM
тАО12-04-2008 04:50 AM
Re: System permanent logical names
Mount/sys
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2008 05:36 AM
тАО12-04-2008 05:36 AM
Re: System permanent logical names
disk$* logicals are working after changing sylogical.com
but
$ define/system/exec AMS$CODE ALPHA$DKB400:[AMS$CODE.]
is not creating permanent logical name. it vanishes after reboot. could you pls give any permanent solution?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2008 05:52 AM
тАО12-04-2008 05:52 AM
Re: System permanent logical names
no logicals are "permanent".
If you want a logical name to survive a reboot, then you must recreate it during the reboot.
For system logical names, the obvious place to put your DEFINE commands is SYLOGICALS.COM, as this gets executed every time the system reboots.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2008 07:30 AM
тАО12-04-2008 07:30 AM
Re: System permanent logical names
I would NOT follow the recommendations to put them preferable into sylogicals.com,
especially those which depend on mounting of disks.
Look into sys$startup:VMS$DEVICE_STARTUP.COM to see what happens (conditionally on FULL or MIN) before and after sylogicals.com.
The right place for disk/volume/mount dependable logicals is somewhere early in systartup_vms, best near the corresponding mount command, which in turn is best in a central command-file called from systartup.
And as said repeatedly, defining (concealed-) device names for mounted volumes should be done through the mount command itself.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2008 07:34 AM
тАО12-04-2008 07:34 AM
Re: System permanent logical names
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2008 08:35 AM
тАО12-04-2008 08:35 AM
Re: System permanent logical names
>>>
If you want a logical name to survive a reboot, then you must recreate it during the reboot.
<<<
For completeness, IF you are in a CLUSTER environment, _AND_ as long as at least one (not necessarily always the same) cluster member is kept running, THEN defining the logical names in LNM$SYS_CLUSTER table WILL make them survive (actually, automatically re-defined) upon node reboot.
(Note, that even then, they will NOT survive a full CLUSTER reboot).
hth
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2008 09:21 AM
тАО12-04-2008 09:21 AM
Re: System permanent logical names
Excellent point re: using the cluster logical name table.
A corresponding cautionary note: While OpenVMS clusters and their facilities do have extremely long uptimes, I caution to have at least a command procedure that reconstitutes (if necessary) the cluster-wide name table (e.g., check whether the name is defined, if not, define it).
It would be rather embarrassing to define a cluster-wide name and then lose it after a decade or two of uninterrupted cluster uptime.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-06-2008 03:04 AM
тАО12-06-2008 03:04 AM