- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Filesystem and logical names
Operating System - OpenVMS
1752252
Members
4280
Online
108785
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО09-06-2005 01:51 AM
тАО09-06-2005 01:51 AM
Re: Filesystem and logical names
The explanation at the 1st level is that there is a rooted search list logical name SYS$SYSROOT defined that points to the system software root that your system is booted from. This list on the system you did the command is made up of 2 parts: the system specific component which is listed first, and the "common" component which is listed second.
In your case, the 1st element, the system specific component is pointing to physical device osfs1$dka0: with root [sys0]. The "common" element, the 2nd one in the list is pointing to sys$common which translates to "physical" device osfs3$dka0: and root [sys0.syscommon] which may actually translate to the same as root [vms$common] depending on the vintage of your system. It is possible that osfs1$dka0 actually translates to something else (more fundamental). The name osfs3$dka0 may also translate to something more fundamental. If these 2 names are actual physical device names, then you have part of your system files residing on one disk drive and part of them residing on another.
Robert
>>But what it's the explantaion of the following commands? And how do I define logical name in simular ways? Thanks.
OpenVMS> show log sys$sysroot
"sys$sysroot" = "osfs1$dka0:[sys0.]"
= "sys$common:"
1 "sys$common"="os3fs1$dka0:[sys0.syscommon.]
In your case, the 1st element, the system specific component is pointing to physical device osfs1$dka0: with root [sys0]. The "common" element, the 2nd one in the list is pointing to sys$common which translates to "physical" device osfs3$dka0: and root [sys0.syscommon] which may actually translate to the same as root [vms$common] depending on the vintage of your system. It is possible that osfs1$dka0 actually translates to something else (more fundamental). The name osfs3$dka0 may also translate to something more fundamental. If these 2 names are actual physical device names, then you have part of your system files residing on one disk drive and part of them residing on another.
Robert
>>But what it's the explantaion of the following commands? And how do I define logical name in simular ways? Thanks.
OpenVMS> show log sys$sysroot
"sys$sysroot" = "osfs1$dka0:[sys0.]"
= "sys$common:"
1 "sys$common"="os3fs1$dka0:[sys0.syscommon.]
Master you were right about 1 thing -- the negotiations were SHORT!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-06-2005 02:00 AM
тАО09-06-2005 02:00 AM
Re: Filesystem and logical names
RTFM!
Time to go Read The Fine Manuals my friend!
Be on the looked for 'rooted directories' and 'concealed' logical names. Enjoy!
(and don't forget to try the $HELP command)
User guide on directories
http://h71000.www7.hp.com/doc/731FINAL/6489/6489pro_008.html#directs_ch
Users guide on logicals
http://h71000.www7.hp.com/doc/731FINAL/6489/6489pro_026.html#lognames_ch
Guide to files on 'rooted directories'
http://h71000.www7.hp.com/doc/731FINAL/4506/4506pro_018.html#16_rooteddirectorysyntaxapplic
btw... since I am replying anyway, If you do not have pipe, then you may want to use a temporary file. In our example:
$ show log /all /out=logicals.tmp
$ sea logicals.tmp "= ""''f$getsyi(""NODENAME"")'$"
Hein.
Time to go Read The Fine Manuals my friend!
Be on the looked for 'rooted directories' and 'concealed' logical names. Enjoy!
(and don't forget to try the $HELP command)
User guide on directories
http://h71000.www7.hp.com/doc/731FINAL/6489/6489pro_008.html#directs_ch
Users guide on logicals
http://h71000.www7.hp.com/doc/731FINAL/6489/6489pro_026.html#lognames_ch
Guide to files on 'rooted directories'
http://h71000.www7.hp.com/doc/731FINAL/4506/4506pro_018.html#16_rooteddirectorysyntaxapplic
btw... since I am replying anyway, If you do not have pipe, then you may want to use a temporary file. In our example:
$ show log /all /out=logicals.tmp
$ sea logicals.tmp "= ""''f$getsyi(""NODENAME"")'$"
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-06-2005 02:51 AM
тАО09-06-2005 02:51 AM
Re: Filesystem and logical names
"The main purpose of logical names is not to connect, but to seperate. To seperate the knowledge in the application to 'logical' names from the actual implemenation on physical entities."
It depends upon your perspective. If you have a program that does operations on an abstract 'tape' device, you still need to assign (i.e. connect) a real device to the logical name for the program function. Logical names provide the connections that allow you separation applications from physical entities.
It depends upon your perspective. If you have a program that does operations on an abstract 'tape' device, you still need to assign (i.e. connect) a real device to the logical name for the program function. Logical names provide the connections that allow you separation applications from physical entities.
I'm looking for marbles all day long.
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP