HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: f$file_attributes failure
Operating System - OpenVMS
1827808
Members
5165
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
Go to solution
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
04-22-2011 09:55 AM
04-22-2011 09:55 AM
Is there a way around this? A directory command works but is harder to parse.
$!
$! Get the creation date and size.
$!
$ filetime = f$file_attributes(filename, "CDT")
%SYSTEM-W-ACCONFLICT, file access conflict
\PPR$DISK:[PPR.PPR_COMMON.HISTORY]TI_HIST_REPORT.201104221329;1\
$ filesize = f$file_attributes(filename, "EOF")
%SYSTEM-W-ACCONFLICT, file access conflict
\PPR$DISK:[PPR.PPR_COMMON.HISTORY]TI_HIST_REPORT.201104221329;1\
$ if filesize .le. 0 then goto file_loop
$!
$! Get the creation date and size.
$!
$ filetime = f$file_attributes(filename, "CDT")
%SYSTEM-W-ACCONFLICT, file access conflict
\PPR$DISK:[PPR.PPR_COMMON.HISTORY]TI_HIST_REPORT.201104221329;1\
$ filesize = f$file_attributes(filename, "EOF")
%SYSTEM-W-ACCONFLICT, file access conflict
\PPR$DISK:[PPR.PPR_COMMON.HISTORY]TI_HIST_REPORT.201104221329;1\
$ if filesize .le. 0 then goto file_loop
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2011 10:26 AM
04-22-2011 10:26 AM
Solution
Yeah, F$FILE uses SYS$OPEN and thus requires sharing access, as it allows data access.
DIRECTORY (/FULL) uses ACP QIOS just for the attributes.
I consider it a DCL bug to have implemented it this way, but what are we to do?
It should also allow for a list of attributes IMHO, to avoid excessive work, but again that's not how it is.
So for myself I wrote a little C program (attached!) to mimiv F$FILE, but use an ACP QIO to get attributes. Of course is is not integrated as nicely as F$FILE, and is involves an image activation, but it has helped me out!
Code attached, and sample usage below.
Enjoy!
Hein
$ mcr sys$login:f$file sys$login:login.com
Usage: $ mcr f$file "[PRINT,]CDT, EOF, ..." [comment]
Defines F_FILE
$ mcr sys$login:f$file sys$login:login.com ebk,ffb,org
F$FILE -- unsupported attribute requested. Returning
$ mcr sys$login:f$file sys$login:login.com eof,ffb,org
$ show sym *file*
F_FILE = "4|280|SEQ"
$ mcr sys$login:f$file sys$login:login.com print,rat,rfm
CR|VAR
DIRECTORY (/FULL) uses ACP QIOS just for the attributes.
I consider it a DCL bug to have implemented it this way, but what are we to do?
It should also allow for a list of attributes IMHO, to avoid excessive work, but again that's not how it is.
So for myself I wrote a little C program (attached!) to mimiv F$FILE, but use an ACP QIO to get attributes. Of course is is not integrated as nicely as F$FILE, and is involves an image activation, but it has helped me out!
Code attached, and sample usage below.
Enjoy!
Hein
$ mcr sys$login:f$file sys$login:login.com
Usage: $ mcr f$file
Defines F_FILE
$ mcr sys$login:f$file sys$login:login.com ebk,ffb,org
F$FILE -- unsupported attribute
$ mcr sys$login:f$file sys$login:login.com eof,ffb,org
$ show sym *file*
F_FILE = "4|280|SEQ"
$ mcr sys$login:f$file sys$login:login.com print,rat,rfm
CR|VAR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2011 10:36 AM
04-22-2011 10:36 AM
Re: f$file_attributes failure
Btw... if this happens a lot, then you may want to protect your F$FILE with an OPEN first
$OPEN/error=probably_locked/SHARE=WRITE file 'filename
$filetime = f$file_attributes(filename, "CDT")
:
$CLOSE file
:
$probably_locked:
$ status = $STATUS
$ IF status .EQ. %x0800
$ THEN...
:
fwiw,
Hein.
$OPEN/error=probably_locked/SHARE=WRITE file 'filename
$filetime = f$file_attributes(filename, "CDT")
:
$CLOSE file
:
$probably_locked:
$ status = $STATUS
$ IF status .EQ. %x0800
$ THEN...
:
fwiw,
Hein.
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