| 1 | Receiver variable | Output | Char(*) |
| 2 | Length of receiver variable | Input | Binary(4) |
| 3 | Format name of receiver variable | Input | Char(8) |
| 4 | Request variable | Input | Char(*) |
| 5 | Length of request variable | Input | Binary(4) |
| 6 | Format name of request variable | Input | Char(8) |
| 7 | Error code | I/O | Char(*) |
The Send Request (QzdmSendRequest) API is used to send a request or a message over an OptiConnect path. A maximum of 32KB of data may be transferred in a single send request.
The following restrictions apply:
The receiver variable that is to receive the output control information from the Send Request (QzdmSendRequest) API.
The length of the receiver variable, in bytes. The length of the receiver variable must be at least equal to or greater than the length of the output format.
The format of the information that is returned from the Send Request (QzdmSendRequest) API. The SRRC0100 format is used by this API for the receiver variable. See SRRC0100 Format for more information on the SRRC0100 format.
The request variable structure that describes the input for the Send Request (QzdmSendRequest) API.
The length of the request variable, in bytes. The length of the request variable must be at least equal to the length of the input format, and less than or equal to the maximum length of 4KB.
The format of the information that is provided as input for the Send Request (QzdmSendRequest) API. The SRRQ0100 format is used by this API for the request variable. See SRRQ0100 Format for more information on the SRRQ0100 format.
The structure in which to return error information. For the format of the structure, see Error Code Parameter.
The following table defines the information returned for Format SRRC0100.
| Offset | Type | Field | |
|---|---|---|---|
| Dec | Hex | ||
| 0 | 0 | CHAR(8) | Transaction identifier |
The following table defines the information required for Format SRRQ0100.
| Offset | Type | Field | |
|---|---|---|---|
| Dec | Hex | ||
| 0 | 0 | CHAR(16) | Stream identifier |
| 16 | 10 | CHAR(8) | Path identifier |
| 24 | 18 | BINARY(4) | Maximum response data length |
| 28 | 1C | BINARY(4) | Offset to input descriptors |
| 32 | 20 | BINARY(4) | Number of input descriptors |
| 36 | 24 | BINARY(4) | Offset to output descriptors |
| 40 | 28 | BINARY(4) | Number of output descriptors |
| 44 | 2C | CHAR(4) | Reserved |
| These fields repeat for each input descriptor | PTR(SPP) | Data buffer pointer | |
| BINARY(4) | Data buffer length | ||
| CHAR(12) | Reserved | ||
| These fields repeat for each output descriptor | PTR(SPP) | Data buffer pointer | |
| BINARY(4) | Data buffer length | ||
| CHAR(12) | Reserved | ||
Data buffer length. The length of the data buffer that is used for the input or output data.
Data buffer pointer. The pointer to the input data buffer that is used for input or output data.
Maximum response data length. The maximum length that is allowed for the response data. This field is provided as output on the Receive Request (QzdmReceiveRequest) API and indicates the maximum response data length allowed for the Send Response (QzdmSendResponse) API. If the response data that is sent from the Send Response (QzdmSendResponse) API is larger than the buffer that is provided with the Send Request (QzdmSendRequest) API, not all of the data is received. It is the responsibility of the user's application program to retry the entire transaction by using a larger data buffer size for the Send Request (QzdmSendRequest) API to receive all of the data with the Receive Response (QzdmReceiveResponse) API.
Number of output descriptors. The number of output descriptors that are used. An output descriptor describes where the output data that is to be received from the remote system may be found. The output descriptor consists of a space pointer to a data buffer and the length of the data buffer. A maximum of three output descriptors may be specified. The total length of the output buffers must be equal to the maximum response data length that is specified.
Number of input descriptors. The number of input descriptors that are used. An input descriptor describes where the input data that is to be sent to the remote system may be found. The input descriptor consists of a space pointer to a data buffer and the length of the data buffer. A maximum of three input descriptors may be specified.
Offset to output descriptors. The offset to the output descriptors.
Offset to input descriptors. The offset to the input descriptors.
Path identifier. The OptiConnect path that is used for communications. This field is provided as output on the Open Path (QzdmOpenPath) API.
Reserved. A reserved space for the purpose of aligning pointer values on a 16-byte boundary. This field must be initialized to binary 0.
Stream identifier. The OptiConnect stream that is used for communications. This field is provided as output on the Open Stream (QzdmOpenStream) API.
Transaction identifier. The specific transaction associated with this Send Request. This field is provided as output on the Send Request (QzdmSendRequest) API. This field must then be provided as input on the corresponding Receive Response (QzdmReceiveResponse) API.
| Message ID | Error Message Text |
|---|---|
| CPF24B4 E | Severe error while addressing parameter list. |
| CPF3C1D E | Length specified in parameter &1 not valid. |
| CPF3C21 E | Format name &1 is not valid. |
| CPF3C90 E | Literal value cannot be changed. |
| CPF3CF1 E | Error code parameter not valid. |
| CPF9872 E | Program or service program &1 in library &2 ended. Reason code &3. |
| CPFADF0 E | The OptiConnect QSOC subsystem must be active. |
| CPFADF1 E | OptiConnect communication error. |
| CPFADF3 E | OptiConnect path not valid or closed. |
| CPFADF5 E | OptiConnect API internal error, function code &1, return code &2. |
| CPFADF6 E | Request variable not valid, reason code &1. |
| Top | Communications APIs | APIs by category |