1 | Operation (RTVAT) | Input | Char(5) |
2 | File system job handle | Input | Char(16) |
3 | Reserved | Input | Char(20) |
4 | Path name | Input | Char(*) |
5 | Path name length | Input | Binary(4) |
6 | Attribute selection table | Input | Char(*) |
7 | Length of attribute selection table | Input | Binary(4) |
8 | Attribute information table | Output | Char(*) |
9 | Length of attribute information table | Input | Binary(4) |
10 | Length of data returned | Output | Binary(4) |
Before applications can use the Retrieve Directory Entry Attributes (QHFRTVAT) API with your file system, you must:
After that, when an application calls the QHFRTVAT API, the API calls your exit program and passes it the parameters specified by the application. Your exit program performs the work and returns any data to the API. The API passes the data back to the calling application.
None.
The following shows the input parameters that the API passes to your exit program and the output parameters that the exit program must pass back to the API:
The abbreviation for the operation being performed (RTVAT).
The work area or job identifier for use by the file system.
Reserved for future use. This parameter is set to blanks.
Except as noted, the following parameters are the same as the parameters for the API.
The API removes the file system name before passing the path name to the exit program.
The QHFRTVAT API performs the standard functions described in Standard HFS API Functions. The API does not validate the attribute selection table, the attribute information table, or the length of the attribute information table.
You must create an exit program that performs the standard functions described in Standard HFS Exit Program Requirements and these additional functions:
This section lists the messages that the exit program can return to the API.
Message ID | Error Message Text |
---|---|
CPF1F01 E | Directory name not valid. |
CPF1F02 E | Directory not found. |
CPF1F06 E | Directory in use. |
CPF1F07 E | Authority not sufficient to access directory. |
CPF1F08 E | Damaged directory. |
CPF1F21 E | File name not valid. |
CPF1F22 E | File not found. |
CPF1F26 E | File in use. |
CPF1F27 E | Authority not sufficient to access file. |
CPF1F28 E | Damaged file. |
CPF1F41 E | Severe error occurred while addressing parameter list. |
CPF1F42 E | Attribute information table not valid. |
CPF1F43 E | Attribute name not valid. |
CPF1F45 E | Attribute selection table not valid. |
CPF1F47 E | Buffer overflow occurred. |
CPF1F48 E | Path name not valid. |
CPF1F62 E | Requested function failed. |
CPF1F66 E | Storage needed exceeds maximum limit for user profile &1. |
CPF1F71 E | Exception specific to file system occurred. |
CPF1F73 E | Not authorized to use command. |
CPF1F74 E | Not authorized to object. |
CPF1F75 E | Error occurred during start-job-session function. |
CPF1F77 E | Severe parameter error occurred on call to file system. |
Top | Hierarchical File System APIs | APIs by category |