- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: DECNET default directory problem
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-29-2009 01:42 AM
тАО05-29-2009 01:42 AM
DECNET default directory problem
I have three single nodes in network. From one I can see decnet default directory from the others, but not from himself.
NI21:SYSTEM> dir smni21::
%DIRECT-E-OPENIN, error opening SMNI21::*.*;* as input
-RMS-E-FND, ACP file or directory lookup failed
-SYSTEM-F-NOSUCHNODE, remote node is unknown
I was trying to play with route table, but nothing help. Thanks for the ideas.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-29-2009 01:47 AM
тАО05-29-2009 01:47 AM
Re: DECNET default directory problem
NI21:SYSTEM> dir localhost::
Directory LOCALHOST::SYS$SPECIFIC:[FAL$SERVER]
NET$SERVER.LOG;6 NET$SERVER.LOG;5 NET$SERVER.LOG;4 NET$SERVER.LOG;3
NET$SERVER.LOG;2 NET$SERVER.LOG;1
Total of 6 files.
NI21:SYSTEM> dir 172.23.18.2::
Directory 172.23.18.2::SYS$SPECIFIC:[FAL$SERVER]
NET$SERVER.LOG;6 NET$SERVER.LOG;5 NET$SERVER.LOG;4 NET$SERVER.LOG;3
NET$SERVER.LOG;2 NET$SERVER.LOG;1
Total of 6 files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-29-2009 01:47 AM
тАО05-29-2009 01:47 AM
Re: DECNET default directory problem
The command seems to work correctly if you include username and password:
$ dir piano"system password"::
Regards,
Shilpa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-29-2009 01:48 AM
тАО05-29-2009 01:48 AM
Re: DECNET default directory problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-29-2009 02:16 AM
тАО05-29-2009 02:16 AM
Re: DECNET default directory problem
In DECnet, node 0 (zero) is always "self".
So, what does
$ dir 0::
give you?
If that _IS_ working, (which I would expect), then your local name definition is not (fully) correct.
For setting this correct, we need to know if you are using DECnet IV or DECnet V.
hth
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-29-2009 02:19 AM
тАО05-29-2009 02:19 AM
Re: DECNET default directory problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-29-2009 03:32 AM
тАО05-29-2009 03:32 AM
Re: DECNET default directory problem
So the nodename SMNI21 cannot be resolved by DECnet.
There are multiple ways for DECnet to resolve host names, one of them is the local DECnet registry. Add the node name and DECnet address using MC DECNET_REGISTER.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-29-2009 04:51 AM
тАО05-29-2009 04:51 AM
Re: DECNET default directory problem
NI21:SYSTEM> mc decnet_register show node "*"
Directory Service: Local name file
Node name: LOCAL:.HOME.ASTRO
Phase IV synonym: ASTRO
Node address: 37:2041291266:00-3A:AA-00-04-00-64-E8:21 (58.100)
Node address: 37:2041291266:00-3A:AA-00-04-00-64-E8:20 (58.100)
Node name: LOCAL:.HOME.BETTY
Phase IV synonym: BETTY
Node address: 37:2041291266:00-01:AA-00-04-00-BB-07:21 (1.955)
Node address: 37:2041291266:00-01:AA-00-04-00-BB-07:20 (1.955)
Node name: LOCAL:.HOME.SMNI21
Phase IV synonym: SMNI21
Node address: 37:2041291266:00-CD:00-00-00-00-00-21:21
Node address: 37:2041291266:00-CD:00-00-00-00-00-21:20
Node name: LOCAL:.HOME.VENUS
Phase IV synonym: VENUS
Node address: 37:2041291266:00-01:AA-00-04-00-58-06:21 (1.600)
Node address: 37:2041291266:00-01:AA-00-04-00-58-06:20 (1.600)
Number of nodes reported on: 4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-29-2009 05:19 AM
тАО05-29-2009 05:19 AM
Re: DECNET default directory problem
SMNI21 shows no node number, while BETTY shows 1.955.
Did you try a "dir LOCAL:.HOME.SMNI21::"?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-29-2009 05:25 AM
тАО05-29-2009 05:25 AM
Re: DECNET default directory problem
The key informations is in the output of MC NCL SHOW SESSION CONTROL NAMING SEARCH PATH. What does it say ?
If DECnet-over-IP (using the IP address) works, what happens if you use the FQDN (full IP name including domain name). Can this name be resolved from IP ? Does DIR smni21.domain-name work ?
Volker.