| Byte |
Definition |
|---|
| Standard |
Enhanced |
|
| 5–6 |
11–12 |
Function number of the completed
asynchronous function (126 or 127). (returned) |
| 7–10 |
13–16 |
Address of the data string of the
completed asynchronous function call. (The application must not reuse
the data string until the request has completed). (returned) |
| 11–12 |
17–20 |
Length of the data string of the
completed asynchronous function call. (returned) |
| 13–14 |
21–24 |
Return code of the completed asynchronous
function call. (returned) |
| Return Code |
Explanation |
|---|
| 0 |
The Get Request
Completion function was successful. |
| 2 |
An error was made in specifying parameters. |
| 9 |
A system error was encountered. |
| 38 |
Requested function was not complete. |
| 42 |
No matching request was found. |
There are some differences between return codes 38 and 42:
- Return code 38
- If a specific request ID and session were requested, both the
session and ID were found but the request is pending (not in a completed
state).
- If a zero request ID and a specific session were requested, the
specified session has pending requests, but they are not satisfied
(complete).
- If a zero request ID and a blank session were requested, pending
requests were found but none were satisfied (complete).
- Return code 42
- If a specific request ID and session were requested, the specific
request ID was not found in either a pending or a completed state.
- If a zero request ID and a specific session were requested, the
specific session contains no pending or completed requests.
- If a zero request ID and a blank session were requested, no pending
or completed requests were found.