World of Db2

By Damir Wilder

Damir recently found himself in a situation where he needed to expand (quickly and without downtime) the Db2 Transaction Log space in a customer’s live production database, which had been steadily filling up (for several hours) by a very long and intensive transaction. Also contributing to the log space usage were numerous other (smaller) transactions that were executing during the same time and…

By Iqbal Goralwalla

Earlier this year Db2 pureScale deployments were made available as a bring-your-own-license (BYOL) option through the AWS Marketplace with a pre-packaged template and point/click interface. This significantly simplifies the deployment process. It facilitates setting up a pureScale cluster from what used to be weeks or months to less than an hour. …

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 OMPE V540 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…

Introduction.

Because CICS transactions can execute so quickly, looking at Task History may be the only way to evaluate the performance of a transaction. Often when looking at CICS Task History, it is apparent the transaction spent the bulk of its time in Db2. Or, from Db2 Thread History, you can see a task originated in a CICS Region. In both cases, it can be difficult to determine the exact instance of the thread in Db2 or the Task in CICS.

With IBM Z OMEGAMON for CICS V5.6.0…