- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Logical names issue
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
тАО06-01-2009 09:05 PM
тАО06-01-2009 09:05 PM
Logical names issue
define/sys/exec ......
it gets deleted at every reboot. could someone help?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2009 09:11 PM
тАО06-01-2009 09:11 PM
Re: Logical names issue
You need to save the definition of the logical(s) in a file that runs during boot.
example, SYS$STARTUP:SYLOGICALS.COM
Hakan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-02-2009 12:54 AM
тАО06-02-2009 12:54 AM
Re: Logical names issue
In addition to Hakan's comments, a note. Please review the documentation on logical names. Not just the section on the DEFINE and ASSIGN commands, but the information in the System Services manual and in the Programming Concepts manual.
All of the OpenVMS manuals are available online at http://www.hp.com/go/openvms
On a general note, the online HELP text is no substitute for having read the relevant manual. While the HELP text contains a summary of the material in the manual, it is of necessity only a summary.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-02-2009 04:00 AM
тАО06-02-2009 04:00 AM
Re: Logical names issue
Bit more information:
SYLOGICALS.COM A file to which you add commands to define your site-specific system logical names.
A systemwide logical name applies to the entire system. It is defined in the system logical name table and can be used by any process in the system. A clusterwide system logical name applies to every node in the
cluster at a system level. It is defined in the clusterwide system logical name table of every node and can be used by any process in the system.
In general, system managers edit the SYLOGICALS.COM command procedure to define site-specific logical names that take effect at system startup.
Regards,
Murali
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-02-2009 07:51 PM
тАО06-02-2009 07:51 PM
Re: Logical names issue
Is there any other file to modify before reboot?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-02-2009 09:14 PM
тАО06-02-2009 09:14 PM
Re: Logical names issue
A definition of a logical must be stored in ANY file the will be run during boot.
SYLOGICALS.COM is accessed early in the boot.
If another definition of the specific logical is made later in the boot, it will be overwritten.
Hakan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2009 02:16 AM
тАО06-03-2009 02:16 AM
Re: Logical names issue
Find where the logical is getting defined.
If possible change it there itself, else try to define your new logical after the start up of the application or Com procedure which defines the logical.
If you are getting confused add the logical definition to the last line of your sys$manager:systartup_vms.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2009 02:24 AM
тАО06-03-2009 02:24 AM
Re: Logical names issue
With all due respect I must strongly disagree with the last paragraph of your most recent post in this thread.
The logical name in question could be defined in a wide variety of places, adding it to the end of SYS$MANAGER:SYSSTARTUP_VMS.COM while it may possibly temporarily resolve the situation, will only add to confusion in the long term.
Amaresh,
Simply adding the name to SYLOGICALS will not define it in the currently running system. The individual define will also have to be executed on the running system.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2009 02:54 AM
тАО06-03-2009 02:54 AM
Re: Logical names issue
I take that.. I was jus trying to give him a work around.
Amaresh,
Sorry to misguide you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2009 08:56 PM
тАО06-03-2009 08:56 PM
Re: Logical names issue
I want to know what steps to be executed so that I need not to redefine the logicals after reboot..
Adding to SYLOGICALS.COM did not work.
Amaresh