Sys2CheckNamedPipe: Difference between revisions
m wrong category |
mNo edit summary |
||
| Line 1: | Line 1: | ||
Check the status of a named pipe (server side). | Check the status of a named pipe (server side). | ||
This function is designed for use by the process that created the pipe (i.e. the server side). Clients which are accessing a named pipe should | This function is designed for use by the process that created the pipe (i.e. the server side). Clients which are accessing a named pipe should use the standard REXX STREAM and/or CHARS functions to determine the pipe's status. | ||
use the standard REXX STREAM and/or CHARS functions to determine the pipe's status. | |||
==Arguments== | ==Arguments== | ||
| Line 11: | Line 9: | ||
String of the format "bytes status", where bytes is the number of bytes currently waiting in the pipe, and status is one of: DISCONNECTED, LISTENING, CONNECTED, or CLOSING. | String of the format "bytes status", where bytes is the number of bytes currently waiting in the pipe, and status is one of: DISCONNECTED, LISTENING, CONNECTED, or CLOSING. | ||
[[Category:RxUtilEx]] | |||
Revision as of 13:45, 26 February 2017
Check the status of a named pipe (server side).
This function is designed for use by the process that created the pipe (i.e. the server side). Clients which are accessing a named pipe should use the standard REXX STREAM and/or CHARS functions to determine the pipe's status.
Arguments
The pipe handle (from Sys2CreateNamedPipe or DosOpen). (REQUIRED)
REXX RETURN VALUE:
String of the format "bytes status", where bytes is the number of bytes currently waiting in the pipe, and status is one of: DISCONNECTED, LISTENING, CONNECTED, or CLOSING.