|  | BEA eLink TCP for TUXEDO 3.0 Information Center
HOME | SEARCH | CONTACT | PDF FILES | WHAT'S NEW
| TABLE OF CONTENTS | PREVIOUS TOPIC | NEXT TOPIC | INDEX

# Operational Considerations

Operational considerations are permanent limitations on using a feature. The following operational considerations apply to BEA eLink for Mainframe TCP for TUXEDO (hereafter referenced as eLink TCP for TUXEDO):

Note: In the following discussion, a local application program is one that resides within the immediate BEA TUXEDO administrative region. A remote application program is one that resides outside the immediate BEA TUXEDO administrative region.

- BEA eLink TCP for TUXEDO does not support conversational communication.

- BEA eLink TCP for TUXEDO supports only nontransactional communication.

- Local client and server programs which use the `tpsprio()` function set the priority at which service requests are dequeued by eLink TCP for TUXEDO. This does not affect any prioritization on the remote system.

- Local client programs cannot use the `tpbroadcast()` function to send unsolicited messages to remote client programs (and the reverse).

- Local services cannot use the `tpbroadcast()` or `tpnotify()` functions to send messages to remote client programs (and the reverse).

- When local client and server programs use the `tpgprio()` function to determine the priority of a remote service, the priority of a local eLink TCP for TUXEDO requester is returned.

- For background information about these operational considerations, see "Understanding How BEA eLink TCP for TUXEDO Works."

  TABLE OF CONTENTS | PREVIOUS TOPIC | NEXT TOPIC | INDEX