CP6100 I/O Process Programming Manual

CPTEST
SENDNW Command
-----------------------------------------------------------------
| |
| <text> contains additional data needed for the request. |
| Express it as one or more occurrences of any of the |
| following: |
| |
| ^B<hexstring> for a byte value, for example ^B1F |
| |
| ^W<hexstring> for a word value, for example ^1F2D |
| |
| <<astring>> or "<astring>" for an ASCII character string, |
| for example <abcd> or "ABCD". (A string can have |
| either quotation marks or angle brackets as |
| delimiters.) |
| |
| To find out what this field should contain for a given |
| request, consult the manual that describes the protocol. |
| |
-----------------------------------------------------------------
Considerations
1. The SENDNW command issues a request to the protocol task.
The SENDNW command completes before the request is even sent
to the task. The request is completed either by a response
from the protocol or by an error message. In the case of an
error message, CPTEST displays the file system error code.
Responses from the protocol appear on the screen as soon as
they are received (that is, you do not give another command
in order to receive them).
2. If you issue a number of concurrent requests (with SEND or
SENDNW commands) during the same session, make sure each
message has a unique request ID (ReqID). If you issue both
SEND and SENDNW messages, it is critical that no SENDNW
message has the same ReqID as a SEND message, since you use
the ReqID to match each response with the request that
initiated it.
3. Responses to SENDNW have the same format as responses to
SEND, except that responses to the SENDNW command (that is,
nowaited responses) do not include the elapsed time.
4. If you enter hexadecimal digits as the <text>, the text
must be an even number of digits in length, because two
hexadecimal digits are required to represent one byte of
data.
B-24