![]() | Programming Guide | ![]() |
Posts an event
post EVENTeventNameTYPEmsgType(message) [postOption]...
EVENTeventName- The event to be posted, where
eventNamecan be up to 31 characters long, but cannot start with a period (.) or sm.TYPEmsgType- Specifies the data type of the message to accompany this event posting, where
msgTypeis one of these values:
JAMFLEX
If
TYPEis not specified, the default isSTRING. For more information on message data types, refer to "Service Messages and Data Types" in JetNet/Oracle Tuxedo Guide.message- Data to accompany the event posting; the message's format must conform to the
TYPE-specified data type.postOption- One or more of the following options:
NOREPLY- The event broker does not wait for replies from subscribers to the event before returning to the posting agent.
NOTIMEOUT- The event posting is not subject to blocking timeouts; however, transaction timeouts remain in effect.
OUTSIDE_TRANSACTION- Execute the event posting operation outside of the current transaction (if issued within a transaction). If you specify this option, transaction-level exception and unload handlers are not executed when their corresponding events are generated.
Oracle Tuxedo
Client, Server
The
postcommand lets a client or server post an event. When an event is posted, the event broker notifies all subscribers of the event. If successful, post sets thetp_returnproperty to the number of notifications dispatched; otherwise, it setstp_returntoTP_FAILURE. For information about the Oracle Tuxedo event broker and configuration requirements, refer to "Event Brokering" in JetNet/Oracle Tuxedo Guide; also refer to your Oracle Tuxedo documentation.
The
postcommand can generate these exceptions: