1 | Operation (FRCSF) | Input | Char(5) |
2 | File system job handle | Input | Char(16) |
3 | Files to force | Input | Char(16) |
Before applications can use the Force Buffered Data (QHFFRCSF) API with your file system, you must:
After that, when an application calls the QHFFRCSF 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 API passes this information to your exit program:
The abbreviation for the operation being performed (FRCSF).
The work area or job identifier for use by the file system.
The following parameter is the same as the parameter for the API.
The QHFFRCSF API performs the standard functions described in Standard HFS API Functions and these additional functions:
You must create an exit program that performs the standard functions described in Standard HFS Exit Program Requirements.
This section lists the messages that the exit program can return to the API.
Message ID | Error Message Text |
---|---|
CPF1F2B E | Write operation not allowed to file opened for read only. |
CPF1F2E E | Range of bytes in file in use. |
CPF1F28 E | Damaged file. |
CPF1F41 E | Severe error occurred while addressing parameter list. |
CPF1F61 E | No free space available on media. |
CPF1F62 E | Requested function failed. |
CPF1F63 E | Media is write protected. |
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. |
CPF1F77 E | Severe parameter error occurred on call to file system. |
Top | Hierarchical File System APIs | APIs by category |