1 | Handle | Input | Binary(4) |
2 | Remote application name | Input | Char(24) |
3 | Request Identifier | Output | Char(53) |
4 | Send buffer | Input | Char(*) |
5 | Length of send buffer | Input | Binary(4) |
6 | Request type | Input | Char(10) |
7 | Post reply | Input | Char(10) |
8 | Wait time | Input | Binary(4) |
9 | Error code | I/O | Char(*) |
The Send Request (QNMSNDRQ) API, an SNA/Management Services Transport API, sends a request to a remote application. The source application program using this API can indicate if a reply should be returned. If request-only data is sent, the source application will not know if the request data was successfully delivered. To confirm delivery, the source application must request a reply.
When the Send Request (QNMSNDRQ) API operation completes, the remote application may or may not be present. When the send request is complete, the request has been sent from the local system. If a reply is expected but the remote application does not exist, an error code is returned on the subsequent receive operation.
If a reply is not expected, the post reply parameter is ignored.
If the wait time is 0, an entry is placed on the data queue when the send request completes. The application should then perform a Receive Operation Completion (QNMRCVOC) to obtain the results of the send operation. It is recommended that a minimum of 30 seconds be used for the wait time. Larger values may be required in some networks.
The current value for the mode name of the application identified by the handle determines which session is used to send the request.
None.
The unique identifier for this application, which was returned by the Start Application (QNMSTRAP) API.
The name of the remote application to which the request is sent. The first 8 characters contain the network ID, the second 8 characters contain the control point name (or the logical unit name may be used), and the third 8 characters contain the application name of the remote application.
The identifier that the system assigned to this request. This identifier must be kept by the application to receive replies to the request (if any).
The data record being sent.
The size of the data record being sent. The send buffer can range in size from 0 through 31739.
The type of data to be sent:
*RQS | This is a request only; no reply is expected. |
*RQSRPY | A reply is expected to this request. |
Whether entries should be put on the data queue when replies to this request arrive.
*NO | Do not place a reply entry on a data queue. |
*YES | Place the reply entry on the data queue associated with the handle. |
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 | 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. |
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. |
CPF7AD6 E | Request type value &3 not valid. |
CPF7AD9 E | Post reply value &3 not valid. |
CPF7AEC E | Wait time &3 not between -1 and 99999. |
CPF7AE0 E | Function requested not supported by remote system. |
CPF7AE1 E | Sign-on to control point &3.&4 denied. |
CPF7AE2 E | Handle &1 not found. |
CPF7AE3 E | Management Services transport operation not permitted. |
CPF7AE5 E | Control point &3.&4 not found. |
CPF7AE6 E | Communication with control point &3.&4 failed. |
CPF7AE7 E | Remote application program &5 not found. |
CPF9872 E | Program or service program &1 in library &2 ended. Reason code &3. |
Top | Network Management APIs | APIs by category |