- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Rooted logical over decnet
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
тАО05-17-2005 06:48 AM
тАО05-17-2005 06:48 AM
I then defined a rooted logical as follows
$defi/sys/exec/trans=conc newlog nod46::[product.xx.]
Trying to access the directory as newlog:[000000] produces the following:
-RMS-F-DEV, error in device name or inappropriate device type for operation
Can you use rooted logicals over Decnet like I am trying to do?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 06:59 AM
тАО05-17-2005 06:59 AM
Re: Rooted logical over decnet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 07:02 AM
тАО05-17-2005 07:02 AM
Re: Rooted logical over decnet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 07:06 AM
тАО05-17-2005 07:06 AM
Re: Rooted logical over decnet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 07:09 AM
тАО05-17-2005 07:09 AM
Re: Rooted logical over decnet
On node46 there is a local rooted logical pointing into the directory structure he needs to access. We are trying to duplicated that remotely.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 07:11 AM
тАО05-17-2005 07:11 AM
Re: Rooted logical over decnet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 07:14 AM
тАО05-17-2005 07:14 AM
Re: Rooted logical over decnet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 07:18 AM
тАО05-17-2005 07:18 AM
Re: Rooted logical over decnet
$ define/sys/exec newlog node46::rooted_logical:
If it has to be concealed, I do not have an answer. Again, rooted_logical needs to be defined on the remote node.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 03:56 PM
тАО05-17-2005 03:56 PM
Re: Rooted logical over decnet
File specifications must fit the syntax:
A fairly simple rule to help explain this is that everything to the right of the "::" happens on the REMOTE node. Consider that even with DECnet, the remote host doesn't need to be OpenVMS, so the local host just passes the filespec string direct to the remote host without interpretation.
Since "[product.xx.][000000]" is not a valid file specification, there is no way to pass a correct file specification to the other host. In fact the RMS-F-DEV error occurs before DECnet involvement. There is no attempt to make a network connection because a concealed device specification must, by definition, be part of the DEVICE field of a file specification, and therefore cannot contain a node specification.
As Dale has already pointed out, you need to have the rooted logical name defined on the remote host.
>On node46 there is a local rooted logical
>pointing into the directory structure he
>needs to access. We are trying to
>duplicated that remotely.
Good! So, you already have the remote logical name. Your local logical name needs to be defined in terms of the NODE46 logical name. For example, assume the remote logical name is:
$ DEFINE/TRANS=CONCEALED NODE46_ROOT:[PRODUCT.XX.]
You need to define your logical name as:
$ DEFINE NEWLOG NODE46::NODE46_ROOT:
You can then use
$ DIRECTORY NEWLOG:[000000]
or with any other directory specification, exactly the same as you would use the logical name NODE46_ROOT on NODE46.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2005 12:39 AM
тАО05-18-2005 12:39 AM