BEA Logo BEA Tuxedo Release 8.0

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT

 

   Tuxedo Documentation   |   Setting Up a BEA Tuxedo Application   |   Local Topics   |   Previous Topic   |   Next Topic   |   Contents

 


Specifying How Clients Receive Unsolicited Notification

You can select the default method by which clients receive unsolicited messages by setting the NOTIFY parameter. The client, however, can override this choice when calling tpinit().

Following are four possible methods:

The USIGNAL parameter specifies the signal to be used if SIGNAL-based notification is used. Two types of signals can be generated: SIGUSR1 and SIGUSR2. The default is SIGUSR2. This method has the advantage of immediate notification, but is limited when you are running a native client. In that case, you must have the same user ID as the sending process. Workstation clients do not have this limitation.

Note: This method is not available on all platforms.

Characteristics of the NOTIFY and USIGNAL Parameters

Parameter

Characteristics

NOTIFY

Value of IGNORE means clients should ignore unsolicited messages.

Value of DIPIN means clients should receive unsolicited messages only when they call tpchkunsol() or when they make an ATMI call.

Value of SIGNAL means clients should receive unsolicited messages by signals.

Default is DIPIN

Example: NOTIFY SIGNAL

USIGNAL

Value of SIGUSR1 and SIGUSR2 means notify clients with this type of signal.

Default is SIGUSR2

Example: USIGNAL SIGUSR1


 

 

back to top previous page next page