ZCOM C I/F Library Routines
ZSET_RCVR (3X)
| Note: Only one constant value can be specified per call for this field. You |
| cannot logically OR these values in one call |
rzap | ZCOM address of the receiver program. |
NOTES | Usually, an application uses only mode ZcNORMAL to set up itself as the |
| receiver for normal data and status messages. An application uses mode |
| ZcCONTROL only if it needs to receive “control” messages. Control |
| messages are generated by ZCOM protocol modules. You should refer to |
| the specific ZCOM Protocol Manual to determine the “control” messages |
| generated by that protocol, if any. |
| Modes ZcINB_MLTPLX and ZcOUTB_MLTPLX require the terminal to |
| be an inbound and outbound multiplexed terminal, respectively. |
| Otherwise, error ZERTYPE |
| usually set up by defining the proper device type in the TTGEN |
| configuration file (using TERM or LTERM statements). It may also be |
| modified by using zltmx. |
| When inbound multiplexing is enabled for a terminal, an inbound |
| receiver must be set up (using mode ZcINB_MLTPLX) by the |
| multiplexing program, which will be responsible for receiving messages |
| from the terminal and passing them to the “normal receivers” kept in the |
| logical terminal tables. |
| When outbound multiplexing is enabled for a terminal, an outbound |
| receiver must be set up (using mode ZcOUTB_MLTPLX) by the |
| multiplexing program, which will intercept data sent from other |
| programs. The outbound multiplexing program is responsible for passing |
| the correct data onto the physical terminal (using zsend with mode bit |
| ZCOM_ZSEND_NOMX). For more information, see the section on |
| Multiplexing in the Multiprotocol ACC Programmer’s Reference Guide. |
| The ZcADD_SHARED action is not supported for mode |
| ZcOUTB_MLTPLX (outbound multiplexer receiver). |
RETURN VALUE Routine zset_rcvr returns 0 if successful. Otherwise, a
324 | Chapter 4 |