The HB_SHOW_TOKEN directive determines whether the state token always appears in the XML output following a transaction. You must issue this directive with the first transaction to include the token in the output. By default, HostBridge automatically determines when to show the token using these rules:
- For pseudo-conversational transactions, HostBridge returns a state token when the transactions include a NEXT TRANID.
- For conversational transactions, HostBridge returns a state token if the task is still running.
There are special instances where you may want to override the HostBridge rules and force the use of state tokens. For example, applications that execute a series of individual transactions may leave a transaction id and data on the screen. When the user hits Enter the data is sent back to the application where the transaction id ties the current transaction to the previous transaction. This is not a true pseudo-conversational transaction and HostBridge would normally not return the state token in the XML document.
Setting HB_SHOW_TOKEN=1 forces HostBridge to return the state token for use with subsequent transactions. Setting HB_SHOW_TOKEN=1 also provides some performance benefits. Following each individual transaction, the 3270 bridge normally tears down the bridge facility for the transaction. This directive allows you to reuse bridge facilities to lower the occurrence of bridge facility initialization and teardown and might keep you from having to fill out an internal user area for the transaction (known as the TCTUA) each time you execute it.
Format: HB_SHOW_TOKEN=value or <hb_show_token>value</hb_show_token>
|0||HostBridge determines when to show the state token|
|1||Always include the state token in the output XML|
Default Value: 0
Example: HB_SHOW_TOKEN=1 or <hb_show_token>1</hb_show_token>