The changes to CETR are:
The CETR transaction is enhanced to enable you to set special tracing for the following new components:
CETR has new option screens to display and update trace settings for JVMs. Press PF6 on the main screen to access the JVM trace options screens. (Although the JVM trace options are part of the SJ component, they are controlled using the JVM trace options screens, rather than the component trace options screen.) You can use these screens to specify the JVM trace options, using the "free-form" 240-character field, and to specify trace settings for JVMs using the Standard and Special flags. You can then use the Transaction and Terminal Trace screen to switch on these flags for particular transactions. JVM trace can produce a large amount of output, so you should normally activate JVM tracing for special transactions, rather than turning it on globally for all transactions.
The default JVM trace options that are provided in CICS use the JVM trace point level specifications. The default settings for JVM Level 0 trace, JVM Level 1 trace, and JVM Level 2 trace specify LEVEL0, LEVEL1, and LEVEL2 respectively, so they map to the Level 0, Level 1 and Level 2 trace point levels for JVMs. A Level 0 trace point is very important, and this classification is reserved for extraordinary events and errors. Note that unlike CICS exception trace, which cannot be switched off, the JVM Level 0 trace is normally switched off unless JVM tracing is required. The Level 1 trace points and Level 2 trace points provide deeper levels of tracing. The JVM trace point levels go up to Level 9, which provide in-depth component detail. It is suggested that you keep the CICS-supplied level specifications, but if you find that another JVM trace point level is more useful for your purposes than one of the default levels, you could change the level specification to map to your preferred JVM trace point level (for example, you could specify LEVEL5 instead of LEVEL2 for the JVMLEVEL2TRACE option). The default values for JVM trace options can be overridden using the CICS system initialization parameters JVMLEVEL0TRACE, JVMLEVEL1TRACE, JVMLEVEL2TRACE and JVMUSERTRACE.
You can add further parameters to the basic level specifications for JVM Level 0 trace, JVM Level 1 trace, and JVM Level 2 trace, if you want to include or exclude particular components or trace point types at the selected trace levels. If you want to create more complex specifications for JVM tracing which use multiple trace point levels, or if you do not want to use trace point levels at all in your specification, use the JVMUSERTRACE option to create a trace option string that includes the parameters of your choice. "Defining tracing for JVMs" in the CICS Problem Determination Guide has information about the JVM trace options that you can set using the JVM Level 0 trace, JVM Level 1 trace, JVM Level 2 trace, and JVM User trace levels. There is further information about JVM trace and about problem determination for JVMs in the IBM® Developer Kit and Runtime Environment, Java 2 Technology Edition, Version 1.4.2 Diagnostics Guide, SC34-6358, which is available to download from www.ibm.com/developerworks/java/jdk/diagnosis/.
If dynamic LU alias is in operation for the CICS region, and you want to use VTAM® exit tracing to trace the bind flows for an autoinstalled terminal, the NETNAME you specify on the CETR "Transaction and Terminal Trace" panel should be the real network name. If you use the real network name, and there is more than one network using that name with CICS, VTAM exit tracing is activated for each occurrence of the network name. However, if you want to trace terminal activity after the LU alias name is known, specify the LUALIAS name.
[[ Contents Previous Page | Next Page Index ]]