Synapta Services Builder for CICS Manager Help Graphic

Configuration: Logging/Tracing Page

Configuration options, necessary to efficiently run tasks and log information for your run-time servers, are set on three separate pages; Systems, Mappings, and Logging/Tracing. Use the options on the Logging/Tracing page to select the types of events you want to log and make other necessary configuration decisions. You can log errors, warnings, and debug information for all system events.

When you configure event logging, you can view events in MCS, log events to a local file, and configure tracing for troubleshooting events containing large amounts of data.

Event Logging:   Select the event type and the location of where you want events to be recorded. By making these selections event logging is enabled. Logging and tracing are turned off by default.

Event Types:  Select the types of events you want to record. Choose from errors, warnings, and information.

This option...
Does this...
Errors All error events are logged. Error events include invalid partner LUs and input XML parsing errors.
Warnings All warning events are logged. Warning events alert you to possible problems and are similar to information events.
Information All other events are logged such as the progress or current status of task execution. Since large amounts of information will be logged, selecting this option may affect performance and typically should be used for debugging purposes only.

Log Events to MCS:  Select this option to have events sent to the configured MCS server. With this option selected, you can view events in the MCS View Events pane.

Log Events to Local File:  Select this option to log events to a specifed local file. You do not have to log events to MCS to log events to a local file.

Log File:  The name of the local file where events will be written.

Max File Size (MB):  The maximum file size of the local file where events will be written. When the maximum size is reached, the file is cleared and subsequent events are written to the newly empty file. The default file size is 2 MB.

Backup File Before Reset:  Select this option to create a backup file when the maximum file size is reached instead of clearing the file. With this option selected, after the log file reaches its maximum file size, a backup file is created by appending .bak to the file name. This backup file stores the previously accumulated events and a new log file is opened.

Tracing:   Create a trace file to provide information regarding tasks running on the configured run-time server. Select the check boxes for the types of trace you want to create.

Enable COMM - Transaction Trace:  A trace of the actual transaction data that users of the run-time server send and receive.

Enable General Trace:  A trace of events which 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.

Trace File:  The name of the trace file where the trace entries will be written. For example, IMStrace.log

Retrieve Trace File:  Click this button to retrieve the trace information from the run-time server, and create a file which you can view in MCS. When you click the button subsequent times, the log file is overwritten by the current available run-time server information.

The IMStrace.log has no size limit and will consume hard drive space unless you reset it occasionally. You can reset the log file by finding and deleting IMStrace.log from the server where the run-time server (Runtime Service for IMS) is installed.

Save Configuration:  Click this to save your configuration. After saving your configuration, you must re-start your run-time computer.

Configurations are saved in one of two locations:

In this location
Then this
Remote The run-time server must be running for the configuration file to be updated. The remote configuration file (.cfg) is saved to the install location of the run-time server in the following location: install_directory/Attachmate/EAI/CICSServer/Config,
Local If the run-time engine is not running, then the modified configuration file (.cfg) is saved locally to: ..\HTTPEngine\webapps\mcs\resources\connector_cics\<specified_runtime_server>

Note When the runtime server is running and a locally-saved configuration is also available, you are prompted to choose which configuration file you want to modify before you can edit a configuration. If there is no configuration file available, you are asked if you want to use a default configuration. See Server Configuration Files for more information.
Related Topics
bullet Configuring Event Logging and Tracing
bullet Logging and Tracing
bullet Server Configuration Files
bullet Synapta Services Builder for CICS Manager Help Links