- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Unable to open file getting -SYSTEM-W-BADIRECT...
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
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
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
04-02-2014 07:29 AM
04-02-2014 07:29 AM
Re: Unable to open file getting -SYSTEM-W-BADIRECTORY, bad directory file format.
Than you.
I will try your suggestions and let you know the outcome.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2014 08:24 AM
04-02-2014 08:24 AM
Re: Unable to open file getting -SYSTEM-W-BADIRECTORY, bad directory file format.
btw... my favourite reason to use QIO to access a fiel is to be able to use:
fib.fib$l_acctl = FIB$M_NOLOCK;
>> and resultant-filespec was passed to sys$qiow.
Device and all?
What do you do with the DEVICE from the file-spec?
Do you properly assigne a channel?
Using SYS$PARSE i typically use somthing like:
devnam_desc.addr = nam.nam$l_dev;
devnam_desc.len = nam.nam$b_dev;
if (((status=sys$assign(&devnam_desc,&channel,0,0,0)) & 1) != 1) lib$stop(status);
If you need further help with this then you should answer the general question on whether the target file can be accessed with other methods, and you should trim down your program to the minimum needed to reproduce the issue and attach it?
Perhaps the program is simply mis-managing the filename descriptor and passing a bad string under certain circumstances?
Hein
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2014 01:08 PM
04-02-2014 01:08 PM
Re: Unable to open file getting -SYSTEM-W-BADIRECTORY, bad directory file format.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2014 02:35 PM
04-02-2014 02:35 PM
Re: Unable to open file getting -SYSTEM-W-BADIRECTORY, bad directory file format.
General question - what does RENAME do if you are moving a file between directories and it can't find the source .DIR?
I imagine that RENAME has to alter the directory backlink (ie. the DID) in INDEXF.SYS, then go and modify the two (i.e. old and new) .DIR files. Or does it do this in a different sequence (e.g. add to new .DIR, remove from old .DIR and then change INDEXF.SYS)?
The reason for my question is that I was wondering if the files in the failed directory have known names and RENAME will be able to insert them into a new directory even if the old directory is broken.
Mind you, we've seen nothing about what DUMP/DIRECTORY displayed, or ANALYZE/DISK and I don't think anyone has inquired about errors being logged for that disk...
If this forum is to be a useful resource then solutions or people's stuff-ups should be reported here so that other people can benefit from the knowledge.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2014 06:11 PM
04-02-2014 06:11 PM
Re: Unable to open file getting -SYSTEM-W-BADIRECTORY, bad directory file format.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2014 08:56 PM
04-02-2014 08:56 PM
Re: Unable to open file getting -SYSTEM-W-BADIRECTORY, bad directory file format.
What you might be trying to say but saying badly is that the RENAME will have to access the .DIR file to find the file's FID so that it can locate the entry in INDEXF.SYS.
That would make sense. How else could it get the FID?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2014 11:16 PM
04-02-2014 11:16 PM
Re: Unable to open file getting -SYSTEM-W-BADIRECTORY, bad directory file format.
Accessing file using DIR/full X.Dir or editing the file having no issues.
Some other applications could access the file for backup.
But only some files in the directory having issue with sys$qiow for accessing in my application.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2014 12:40 PM
04-03-2014 12:40 PM
Re: Unable to open file getting -SYSTEM-W-BADIRECTORY, bad directory file format.
>> Accessing file using DIR/full X.Dir
Unfortunate typo when it matters most?
I though we were talkign about accessing a normal file, not a directory !?!
Is this a datafile called .DIR ?
>> or editing the file having no issues.
>> Some other applications could access the file for backup.
I think we have our answer.
Everything can work with the file except the QIO program, which can access other files.
May I respectfully submit there is something broken in that program.
At this point my money would be on a FIB$W_DID contents being hosed/stuck/mismanaged.
>> But only some files in the directory having issue with sys$qiow for accessing in my application.
So what is special about those files? Name-length?
Odd characters?
Version number?
UpperCase / LOWERCASE ?
Admittedly this would all likely lead to 'file-not-found' but still...
Do a DIR/FILE on a file that does not work and see if you can back-translate it.
(xxxx,yy,z)
For example:
write sys$output F$fid("SYS$DISK:",f$file("login.com","FID"))
Or $ DUMP/HEAD/BLOCK=COUNT=1/ID=xxxx sys$disk
Show us some goodies! Actual directory listings, Actual error messages...
maybe the program trashes the return code... wouldn't be the first or the last.
Thank you.
Hein
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2014 08:09 AM
04-10-2014 08:09 AM
Re: Unable to open file getting -SYSTEM-W-BADIRECTORY, bad directory file format.
Hi,
I got output for failed and sucessful files deader dump. (i.e. DUMP/HEAD/BLOCK=COUNT=1/ID=xxxx sys$disk)
I couldn't make any difference between them.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2014 10:42 AM
04-10-2014 10:42 AM
Re: Unable to open file getting -SYSTEM-W-BADIRECTORY, bad directory file format.
- « Previous
-
- 1
- 2
- Next »