1 | Handle | Input | Binary(4) |
2 | Request Identifier | Input | Char(53) |
3 | Send buffer | Input | Char(*) |
4 | Length of send buffer | Input | Binary(4) |
5 | Reply type | Input | Char(10) |
6 | Wait time | Input | Binary(4) |
7 | Error code | I/O | Char(*) |
The Send Reply (QNMSNDRP) API, an SNA/Management Services Transport API, sends a reply to a request that was received from a source application. Single or multiple replies may be sent for a particular request. The received request must have indicated that a reply is expected.
Multiple replies are sent by calling the Send Reply (QNMSNDRP) API one or more times. To send multiple replies, the reply type parameter is set to incomplete until the last reply is sent, when it is set to complete.
If the wait time is 0, then an entry is placed on the data queue when the operation is complete. If multiple replies are sent without waiting (wait time equals 0), multiple entries are placed on the data queue.
The same mode name used with the Send Request (QNMSNDRQ) API is used for the reply. See the Send Request (QNMSNDRQ) API for more information about sending a request.
The unique identifier for this application.
The request identifier of the corresponding request. The request identifier is returned when the original request is received.
*PRV | The last request identifier used (for example, the one specified on the Receive Data (QNMRCVDT) API). |
The data being sent.
The size of the data being sent. The send buffer can range in size from 0 through 31739.
The type of data being sent:
*RPYCPL | The last or only reply (the reply is complete). |
*RPYINCPL | Additional replies will be sent (the reply is incomplete). |
The amount of time the application waits for the send operation to complete.
-1 | Waits for the send operation to complete or for a condition such that the operation cannot complete (for example, a communications failure). |
0 | The application does not wait for the operation to complete. |
1-99999 | The number of seconds the application waits. |
The structure in which to return error information. For the format of the structure, see Error Code Parameter.
Message ID | Error Message Text |
---|---|
CPF24B4 E | Severe error while addressing parameter list. |
CPF3C90 E | Literal value cannot be changed. |
CPF3CF1 E | Error code parameter not valid. |
CPF7AC0 E | &3.&4 cannot receive data at this time. |
CPF7AC1 E | Reply cannot be sent. |
CPF7ADC E | Internal processing error. |
CPF7ADD E | Operation did not complete. |
CPF7ADF E | Session failure. Cannot send data at this time. |
CPF7AD2 E | Send buffer length value &3 not valid. |
CPF7AD5 E | Reply type value &3 not valid. |
CPF7AEC E | Wait time &3 not between -1 and 99999. |
CPF7AE2 E | Handle &1 not found. |
CPF7AE6 E | Communication with control point &3.&4 failed. |
CPF7AE9 E | Request identifier not valid. |
CPF9872 E | Program or service program &1 in library &2 ended. Reason code &3. |
Top | Network Management APIs | APIs by category |