ATM Transaction Anayzer User and Installation Guide

Troubleshooting HP NonStop ATM Transaction Analyzer 123
7-2-2 On HP NonStop Server
You can enable tracing in the TLFCONF file for diagnostic purpose. The TLFLOG file is the default log file where
the messages are logged. You can refer to the TLFLOG file to check if there are any error indications. For
example, you can check the collector where the ATM/TA backend is logging the EMS events to identify any
problems. FUP COPY the TLFLOG file in order to check for errors.
Follow the steps listed below to enable tracing in the HP NonStop Server environment.
1. For tracing the errors/messages in the ATM/TA backend Environment, the value of the TRACE parameter
should be specified as PROGRESS or ERROR.
2. TLFLOG is the default Error/Message Log file in the ATM/TA subvolume. You can specify a different name
and the location of the log file by configuring the LOGFILE parameter in the TLFCONF configuration file.
3. For logging the Message to the EMS subsystem, the value for the COLL parameter should be specified in the
TLFCONF configuration file as <Collector> ON. For example, for enabling EMS message collection to the
collector $0, specify the value as: COLL $0 ON.
The EMS messages can be viewed for troubleshooting using Viewpoint. You can also merge the
ATMNRES” EMS Template file for ATM/TA events with normal System template to get the ATM/TA events
in formatted way for viewing violations on NonStop EMS events.
Troubleshooting HP NonStop ATM Transaction Analyzer