Determining contention resolution status
You can determine whether ZIETrans successfully negotiates contention
resolution for a particular TN3270E connection. To examine a ZIETrans
trace to see the results of the negotiation, follow these steps:
- Turn on traces for HOD transport and for ZIETrans runtime. For
more information about tracing, see Using the functions in ZIETrans administrative console. In the
runtime.properties file, the settings are:
trace.HOD.TRANSPORT=2 trace.RUNTIME=7
- View the trace file (typically contained within the logs directory of the ZIETrans.ear file with a file name starting with trace).
- Look for entries together in the trace file, similar to these,
when the connection was started:
The key text, highlighted in bold, isText HOD HOD.() Correlator: HodConn:localhost:localhost:server1:ZIETrans.ear#1 trcmsg: -->TN3270 : Negotiate CMD = DO OPT = TN3270-E Text HOD HOD.() Correlator: HodConn:localhost:localhost:server1:ZIETrans.ear#1 trcmsg: <--TN3270 : Response CMD = WILL OPT = TN3270-E
CMD = DO
andCMD = WILL
whenOPT = TN3270-E
also appears (shown here in bold). If bothCMD = DO
andCMD = WILL
appear, ZIETrans successfully negotiated TN3270E for that particular host connection, and can request contention resolution. IfCMD = WONT
,CMD = DONT
, or both appear, it is likely that the host does not support TN3270E, and ZIETrans cannot request contention resolution. - Look for an entry similar to this one when the connection was
started:
The key text, highlighted in bold, is FUNCTION_STATUS: CR REQUESTED. If this text appears, ZIETrans has requested contention resolution for that particular host connection.Text HOD HOD.() Correlator: HodConn:localhost:localhost:server1:ZIETrans.ear#1 trcmsg: <--TN3270 : FUNCTION_STATUS: CR REQUESTED
- Look for an entry similar to this one when the connection was
started:
The key text, highlighted in bold, is FUNCTION_STATUS: CR ENABLED. If this text appears, ZIETrans has successfully negotiated contention resolution for that particular host connection.Text HOD HOD.() Correlator: HodConn:localhost:localhost:server1:ZIETrans.ear#1 trcmsg: <--TN3270E: FUNCTION_STATUS: CR ENABLED
- Look for entries together similar to these two when ZIETrans performs
screen-settling:
The key text, highlighted in bold, is EnhancedTNServer=true and Create: Fast3270E. If these appear, ZIETrans has successfully negotiated contention resolution and is responding by using the Fast3270E strategy for analyzing outbound data.Text RUNTIME runtime.NextScreenBean.getInstance() isEnhancedTNServer=true Text RUNTIME runtime.Fast3270ENSB.<init>() Create: Fast3270E: initialConnect=false, ttwOriginal=1200, tStartedWaiting=0,tLastPSEvent=0, keyToSend=[enter], minimumWait=250