omegamon (2)

Using take action to invoke predefined command to cancel a thread is available from OMPE’s Tivoli Enterprise Portal (TEP) interface. This requires granting Db2 authority to the user ID of the OMPE started task which for some customers is not desired and considered a security concern.

With APAR PH47423/UI82806 and fixpack 5.4.0-TIV-KD5-FP0025, two new prefixes “DP:” and “D5:” are introduced to pair with the existing cancel thread command. With prefixed command, the cancel thread request issues the command using the Db2 authority of the TEP logon ID. Prefixed cancel thread commands can also be used in a situation take action to automate cancelling threads violating certain Service Level Agreements (SLAs).

The newly added take actions are "Cancel Thread with Db2 Authority" and "Cancel DSG Thread with Db2 Authority".

10895659873?profile=RESIZE_584x 

New “Cancel Thread with Db2 Authority” Take Action

This Take Action is defined with the “DP:” prefix, and it can be used with “Thread Activity” or “Detailed Thread Exception” workspace from any TEP single Db2 node.

10895661299?profile=RESIZE_710x 

New “Cancel DSG Thread with Db2 Authority” Take Action

This Take Action is defined with “D5:” prefix, and it can be used with “Data Sharing Thread Activity” workspace from any TEP DSGROUP node.

10895662458?profile=RESIZE_710x 

Response from the Prefixed Cancel Thread Take Actions

If the TEP logon user ID has the Db2 authority to cancel a thread, the following message will be displayed after the prefixed cancel thread take action is executed:

10895665279?profile=RESIZE_710x

If the logon user ID does not have the Db2 authority to cancel a thread, the following message will be displayed after the prefixed cancel thread take action is executed:

10895665673?profile=RESIZE_710x

The similar responses are also displayed from D5 agent log:

10895683852?profile=RESIZE_710x 

 

 

Prefixed Take Action in Situation

The prefixed cancel thread command can also be used in a situation action where the Db2 thread will be cancelled after situation is triggered.

10895684689?profile=RESIZE_710x

Conclusion

The newly introduced prefixed cancel thread command greatly simplifies the configuration task for DBAs to manage the security aspects regarding Db2 thread cancelling. With the prefixed cancel thread take action, the Db2 authority of the user controls whether particular Db2 thread can be cancelled or not. It is no longer needed to grant Db2 authority to the user ID of the OMPE started task.

 

Read more…