Why PTT create another message for the same termination event instead of writing the same TTHxxxxx to the SYSLOG?
search cancel

Why PTT create another message for the same termination event instead of writing the same TTHxxxxx to the SYSLOG?

book

Article ID: 93223

calendar_today

Updated On:

Products

RC Compare for DB2 for z/OS Database Analyzer for DB2 for z/OS Fast Unload for DB2 for z/OS Fast Check for DB2 for z/OS Fast Index for DB2 for z/OS Rapid Reorg for DB2 for z/OS

Issue/Introduction

In View Monitor Options panel when Route termination/warning messages to SYSLOG is changed from N to Y, Why Thread Terminator (PTT) create another message for the same termination event instead of writing the same TTHxxxxx to the SYSLOG?

Environment

Release:
Component: PTT

Resolution

The PTT0001, PTT0002, PTT0003, and PTT0004 messages are written via an Xmanager messaging service. The interface for this service takes the product code (PTT in this case) and a 4-digit number as input parameters and uses these to look up the message template in an internal table. The interface is designed this way because our direction is to have all new messages prefixed with the product code. The TTH messages are not written via the Xmanager messaging service. The code that writes these TTH messages, which is some of the oldest code in PTT, is executed unconditionally immediately after the PTT0001, etc. messages are written conditionally.