Specifying transaction and terminal-related trace options

In CETR you can control tracing for particular CICS® tasks by specifying the transaction ID used to start the task, or the ID for the terminal from which the task is to be run. You can set standard or special tracing for the tasks, or suppress tracing for a task. You can also enable z/OS® Communications Server exit tracing and ZCP trace for specific terminal IDs or netnames. If you connect to DB2, note that using CETR on a single transaction generates a new TXDINST and changes the level of trace from standard to special. As a result, a new LOCATE for the DB2TRAN is performed.

• To trace a single transaction using special tracing, perform the following steps:
  1. Enter CETR and set the main system trace flag to OFF.
     This setting turns standard tracing off.
  2. Press PF4 to select the levels of tracing for the required components under the Special heading.
  3. Return to the main CETR display and press PF5.
     You get the following display, with the values of your own system in each of the fields:

      CETR                    Transaction and Terminal Trace            CI41 IYAHZCCV
     
      Type in your choices.
     
      Item                              Choice       Possible choices
     
      Transaction ID              ===>               Any valid 4 character ID
      Transaction Status          ===>               STandard, SPecial, SUppressed
     
      Terminal ID                 ===>               Any valid Terminal ID
      Netname                     ===>               Any valid Netname
      Terminal Status             ===>               STandard, SPecial
      Terminal VTAM Exit Trace    ===>               ON, OFf
      Terminal ZCP Trace          ===>               ON, OFf
     
      VTAM Exit override          ===>  NONE         All, System, None
     
     
      When finished, press ENTER.
     
     
     
     
      PF1=Help      3=Quit      6=Cancel Exits      9=Error List

     Note: VTAM® is now z/OS Communications Server.
  4. Specify the transaction ID that you want to trace and a transaction status of SPECIAL.
  Setting special tracing for a particular transaction means that special flags for each component are used to decide whether a particular trace entry is to be made at any given point in the process of the task.
• To trace the tasks associated with a particular terminal, perform the following steps:
  1. Set the standard component trace flags to level 1 only.
  2. Set the special component trace flags to level 1 and level 2.
  3. Set the trace for the terminal to special.
  In this way, all tasks run from the specified terminal have level 1 and level 2 tracing. All other tasks have level 1 tracing only.
• To set z/OS Communications Server exit tracing in an AOR, enter the applid of the TOR as Netname and enter ON for the Terminal z/OS Communications Server Exit Trace.
  • If you want to trace the bind flows for an autoinstalled terminal in a CICS region where dynamic LU alias is in operation, the NETNAME you specify must be the real network name. If you use the real network name and there is more than one network using that name, the z/OS Communications Server exit tracing is activated for each occurrence of the network name.
  • If you want to trace an autoinstalled terminal when you know the LU alias, specify the LUALIAS name.