Determining which strategy HATS is using

Follow these steps to determine the strategy being used by HATS:

Turn on traces for HOD Transport and for HATS Runtime. For more information about tracing, see Using the functions in HATS 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 HATS.ear file and has a file name starting with trace.
Look for entries similar to these when HATS performs screen-settling:
```
Text        RUNTIME      runtime.NextScreenBean.getInstance()
	  oiaStatusFlags/isSSCP=x7 false

	Text        RUNTIME      runtime.Fast3270ENSB.<init>()                          
	  Create: Fast3270E: initialConnect=false, ttwOriginal=1200, tStartedWaiting=0, 
                       tLastPSEvent=0, keyToSend=[enter], minimumWait=250
```
The key text, highlighted in bold, is the method name of the first example entry runtime.NextScreenBean.getInstance(), which begins a screen-settling process. The resulting object created in the entry begins with Create:. The strategy object created in this example has its name (Fast3270E) and its Java™ class name (Fast3270ENSB) on the second example trace entry, highlighted in italics.