- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: investigating file version limits
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
тАО04-12-2006 01:57 AM
тАО04-12-2006 01:57 AM
$ set file/attr=vrs:30 login.com;
$ set file/ver=30 login.com;
The first doesn't seem to do anything, while the last sets the version limit to 30, as shown by DIR/FULL.
The real goal is writing a program to read and set the version limit, but that's another question.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2006 02:29 AM
тАО04-12-2006 02:29 AM
Re: investigating file version limits
According to the online HELP, SET FILE/ATTR=VRS:n corresponds to the ACP-QIO File Attribute FAT$W_VERSIONS, and to the XAB$W_VERLIMIT field of the XABFHC for RMS.
According to the I/O Users Reference Manual, FAT$W_VERSIONS only applies to directory files.
The RMS manual states that the XAB$W_VERLIMIT field of the XABFHC is an output field.
So maybe this clarifies why your first command doesn't have any effect.
Regards,
Kris (aka Qkcl)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2006 02:38 AM
тАО04-12-2006 02:38 AM
Re: investigating file version limits
$ set watch file/class=directory
$ set file/ver=30 login.com;
%XQP, Thread #0, Read only directory access (1828,1,0)
%XQP, Thread #0, Directory scan for: LOGIN.COM;0, Status: 00000000
%XQP, Thread #0, Read only directory access (1678,1,0)
%XQP, Thread #0, Directory scan for: LOGIN.COM;0, Status: 00000001
%XQP, Thread #0, Read only directory access (1828,1,0)
%XQP, Thread #0, Directory scan for: LOGIN.COM;0, Status: 00000000
%XQP, Thread #0, Read only directory access (1678,1,0)
%XQP, Thread #0, Directory scan for: LOGIN.COM;0, Status: 00000001
%XQP, Thread #0, Read/write directory access (1678,1,0)
%XQP, Thread #0, Directory scan for: .;0, Status: 00000001
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2006 02:48 AM
тАО04-12-2006 02:48 AM
Solution
However, what did command #1 do? It did something!
Indeed, it changed the revision/modification date. I don't think it did anything else.
Regards,
Kris (aka Qkcl)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2006 02:52 AM
тАО04-12-2006 02:52 AM
Re: investigating file version limits
Hit the submit button too soon.
If you execute command #1 on a directory file, it does what it should, setting the default version limit for the directory to the number specified (note that specifying a zero ( 0 ), turns the default version limit off again).
Regards,
Kris (aka Qkcl)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2006 03:51 AM
тАО04-12-2006 03:51 AM
Re: investigating file version limits
the SET FILE/ATTR=VRS:30 seems to be a noop, if executed against a non-directory file.
A '%SET-I-NOTDIR, file is not a directory' message would have been nice.
SET FILE/VERSION_LIMIT=5 X.DIR against a .DIR file also seems to be a noop.
Volker.