Posts an event
- The event to be posted, where
eventNamecan be up to 31 characters long, but cannot start with a period (.) or sm.
- Specifies the data type of the message to accompany this event posting, where
msgTypeis one of these values:
- Data to accompany the event posting; the message's format must conform to the
TYPE-specified data type.
- One or more of the following options:
- The event broker does not wait for replies from subscribers to the event before returning to the posting agent.
- The event posting is not subject to blocking timeouts; however, transaction timeouts remain in effect.
- 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.
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 the
tp_returnproperty to the number of notifications dispatched; otherwise, it sets
TP_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.
postcommand can generate these exceptions:
Exception Severity Cause TP_EVTBROKER_ACCESS_FAILED TP_COMMAND
Unable to access the event broker sever.
There is no current transaction.
An error occurs when posting a transactional event to either a service routine or a reliable queue on behalf of the caller's transaction.
Command syntax is invalid.
TP_INVALID_VARIABLE_REF TP_COMMAND or TP_WARNING
Unable to resolve reference to Panther variable.