Configuring Event Logging and Tracing

To configure event logging
  1. In the MCS left pane, point to Products and then click Services Builder for CICS.

  2. Expand the Runtime Servers tree, expand your run-time server entry, and then click Configure.

  3. From the Configure page, click the Logging/Tracing tab.

    The Logging/Tracing dialog box displays.

  4. Select the types of events you want to log.

    You can choose to log errors, warnings, and all other information.

    Note
    • When you choose to log information, performance may be affected due to the large amount of data that will be logged. You may want to use this option only as needed, to debug a particular problem.

    • To turn off logging to MCS, clear the options on the Logging/Tracing page.

  5. Select the location where you want events to be logged — events can be sent to one or both locations.
    Specify this location
    		To
    Log Events to MCS Send all events to the configured MCS server.

    To view your Event log, open Services, select Events, and then choose View Events from the navigation tree.
    Log Events to Local File Write events to a specified file on the local run-time server. The default file name is cicsevents.log. The file is saved to the same location where the client program is running.

    You can also specify a maximum file size as well as how to handle file back-ups.

  6. Click Save Configuration or proceed to step 4 of the procedure, To Configure Tracing.

    For changes to take effect, you must re-start the run-time after saving any changed configurations.
To configure tracing
  1. In the MCS left pane, point to Products and then click Services Builder for CICS.

  2. Expand the Runtime Servers tree, expand your run-time server entry, and then click Configure.

  3. From the Configure page, click the Logging/Tracing tab.

    The Logging/Tracing dialog box displays.

  4. Select the types of traces you want to create:
    Specify
    		 To trace
    Enable COMM-transaction trace Actual transaction data that users of the run-time server send and receive.
    Enable General Trace Events that pertain to how the run-time server is operating.
    Enable Error Trace Some transactional errors that may not be reported in the non-MCS formatted logging available through the application.

  5. Enter the name of the trace file to which the trace entries will be written.

  6. Click Retrieve Trace File to collect the trace information from the run-time server and create a file that you can view in MCS.

  7. Click Save Configuration.

    For changes to take effect, you must re-start the run-time after saving any changed configurations.
Related Topics
Bullet Logging and Tracing
Bullet Viewing Events
Bullet Configuring Client-side Logging
  Attachmate