search cancel

START TT PROFILE DBP3DAY BUT PROFILE DBP2DAYSTILL DISPLAYED

book

Article ID: 240725

calendar_today

Updated On:

Products

Detector for DB2 for z/OS Database Management for DB2 for z/OS - Administration Suite Database Management for DB2 for z/OS - Performance Suite Database Management for DB2 for z/OS - Recovery Suite Database Management for DB2 for z/OS - SQL Performance Suite Database Management for DB2 for z/OS - Utilities Suite

Issue/Introduction

This is data sharing group environment with multiple xmanagers running. 

DBP3 resides in AFW1 LPAR and DBP2 resides in AFW2 LPAR.

In PTXMAN1 START TT Profile DBP2DAY was issued as displayed below:

15.51.52 STC24124  PXM0107 MODIFY TEXT = START(TT) PRF(DBP2DAY)

08.00.05 STC24124  PXM0107 MODIFY TEXT = START(TT) PRF(DBP2DAY)

In Thread Terminator  Monitor Profiles Display of DBP3 the current profile displayed is DBP2DAY.

Then In PTXMAN2 START TT Profile DBP3DAY was issued as displayed below:

08.00.05 STC25459  PXM0107 MODIFY TEXT = START(TT) PRF(DBP3DAY)

09.03.53 STC25459  PXM0107 MODIFY TEXT = START(TT) PRF(DBP3DAY)

In Thread Terminator  Monitor Profiles Display of DBP3 the current profile displayed is still DBP2DAY instead of DBP3DAY.

Thread Termination/Dynamic DSNZPARM(PTT) is designed to have only a single thread monitor running under an Xmanager.

Note that there is no limit to the number of DB2 subsystems that can be monitored simultaneously via a single thread monitor. 

Is this how the product is designed?

Environment

Release : 20.0

Component : Thread Terminator

Resolution

Starting the thread monitor with a specified thread monitor profile does not update the "Current Profile" shown on the displays. Only issuing the "S-Set Current Profile" command on the "Thread Terminator Monitor Profiles Display" does that. The idea was that you would set the current profile on the "Thread Terminator Monitor Profiles Display" and then access the "Thread Monitor Operations Menu," where the current profile name would be prefilled. Interpreting "Current Profile" as being the last thread monitor profile that was used during thread monitor startup is not the correct interpretation. The Current Profile is simply the thread monitor profile that will be used if the thread monitor is started via the Thread Monitor Operations Menu. Starting the thread monitor via START(TT) Xmanager modify commands, the "Current Profile" shown has no significance.