HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Nam block errors
Operating System - OpenVMS
1827882
Members
1541
Online
109969
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
11-23-2008 04:51 PM
11-23-2008 04:51 PM
Re: Nam block errors
Could the problem be the absence of the top level directory specification?
I notice that Steven S used [*...] as the output specification when restoring in his test of accessing to more than 8 directory levels, which worked fine, but the original problem just had [...]
In the original problem I'd try specifiying the output for the restore operation as gollum:[000000...]*.*;*
I notice that Steven S used [*...] as the output specification when restoring in his test of accessing to more than 8 directory levels, which worked fine, but the original problem just had [...]
In the original problem I'd try specifiying the output for the restore operation as gollum:[000000...]*.*;*
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2008 06:57 AM
11-25-2008 06:57 AM
Re: Nam block errors
John, Steven,
I created a directory tree with eight levels, DKA200:[d1.d2.d3.d4.d5.d6.d7.d8]. I created file test.txt in the lowest directory. I backed-up this tree to saveset test.sav. I then tried to restore the tree to dka300: using various file specifications:
$ set def dka300:[000000]
$
$ backup test.sav/sav [...]
%BACKUP-I-INVDEEPDIR, output directory [000000...] not valid for deepdirectories, try rooted logical
%BACKUP-E-OPENOUT, error opening DKA300:[000000...]TEST.SAV;1 as output-RMS-F-DIR, error in directory name
%BACKUP-I-INVDEEPDIR, output directory [000000...] not valid for deepdirectories, try rooted logical
%BACKUP-E-OPENOUT, error opening DKA300:[000000...]*.*; as output-RMS-F-DIR, error in directory name
$
$
$ backup test.sav/sav [000000...]
%BACKUP-I-INVDEEPDIR, output directory [000000...] not valid for deepdirectories, try rooted logical
%BACKUP-E-OPENOUT, error opening DKA300:[000000...]TEST.SAV;1 as output-RMS-F-DIR, error in directory name
%BACKUP-I-INVDEEPDIR, output directory [000000...] not valid for deepdirectories, try rooted logical
%BACKUP-E-OPENOUT, error opening DKA300:[000000...]*.*; as output-RMS-F-DIR, error in directory name
$
$ backup test.sav/sav [*...]
$
So the only syntax of these three that worked was Steven's.
When I tried to clean these test files up, I found that $DELETE would not delete the eighth directory even with the above syntax. I had to create a rooted logical to get it.
Note that the error message for the first two is not the same as the OP. But I have gotten the RMS-F-RLF error trying to restore eight sub-directories before. Unfortunately, I don't have time right now to hunt for the syntax that caused that error.
I wouldn't be surprised if Jack had a user that recently created that eighth directory. Maybe the "[*...]" syntax will work for him.
Kelly
I created a directory tree with eight levels, DKA200:[d1.d2.d3.d4.d5.d6.d7.d8]. I created file test.txt in the lowest directory. I backed-up this tree to saveset test.sav. I then tried to restore the tree to dka300: using various file specifications:
$ set def dka300:[000000]
$
$ backup test.sav/sav [...]
%BACKUP-I-INVDEEPDIR, output directory [000000...] not valid for deepdirectories, try rooted logical
%BACKUP-E-OPENOUT, error opening DKA300:[000000...]TEST.SAV;1 as output-RMS-F-DIR, error in directory name
%BACKUP-I-INVDEEPDIR, output directory [000000...] not valid for deepdirectories, try rooted logical
%BACKUP-E-OPENOUT, error opening DKA300:[000000...]*.*; as output-RMS-F-DIR, error in directory name
$
$
$ backup test.sav/sav [000000...]
%BACKUP-I-INVDEEPDIR, output directory [000000...] not valid for deepdirectories, try rooted logical
%BACKUP-E-OPENOUT, error opening DKA300:[000000...]TEST.SAV;1 as output-RMS-F-DIR, error in directory name
%BACKUP-I-INVDEEPDIR, output directory [000000...] not valid for deepdirectories, try rooted logical
%BACKUP-E-OPENOUT, error opening DKA300:[000000...]*.*; as output-RMS-F-DIR, error in directory name
$
$ backup test.sav/sav [*...]
$
So the only syntax of these three that worked was Steven's.
When I tried to clean these test files up, I found that $DELETE would not delete the eighth directory even with the above syntax. I had to create a rooted logical to get it.
Note that the error message for the first two is not the same as the OP. But I have gotten the RMS-F-RLF error trying to restore eight sub-directories before. Unfortunately, I don't have time right now to hunt for the syntax that caused that error.
I wouldn't be surprised if Jack had a user that recently created that eighth directory. Maybe the "[*...]" syntax will work for him.
Kelly
- « 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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP