1 | Operation (RDSF) | Input | Char(5) |
2 | File system job handle | Input | Char(16) |
3 | Open file handle | Input | Char(16) |
4 | Data buffer | Output | Char(*) |
5 | Bytes to read | Input | Binary(4) |
6 | Bytes actually read | Output | Binary(4) |
Before applications can use the Read from Stream File (QHFRDSF) API with your file system, you must:
After that, when an application calls the QHFRDSF 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 (RDSF).
The work area or job identifier for use by the file system.
The following parameters are the same as the parameters for the API.
The QHFRDSF API performs the standard functions described in Standard HFS API Functions.
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 |
---|---|
CPF1F2C E | Read operation not allowed to file opened for write only. |
CPF1F2E E | Range of bytes in file in use. |
CPF1F28 E | Damaged file. |
CPF1F35 E | Read file operation failed. |
CPF1F4B E | Value for number of bytes not valid. |
CPF1F41 E | Severe error occurred while addressing parameter list. |
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. |
CPF1F77 E | Severe parameter error occurred on call to file system. |
Top | Hierarchical File System APIs | APIs by category |