These days, most enterprises limit access to sensitive data to only those users who need to see this information to do their jobs. In the meantime, security features have evolved over the past few DB2 releases.
Posted: March 21, 2017 |
Prior to DB2 12, the DB2 bind command allowed you to specify either a list of database request modules (DBRM) using the member keyword or a list of packages using the PKLIST (package list) keyword. However, IBM, which deprecated the member keyword option in DB2 10, has removed it entirely from DB2 12. So any migration to DB2 12 should include taking the steps needed to rebind all plans without the member keyword.
Posted: March 14, 2017 |
DB2 11 introduced a powerful feature that provides monitoring capabilities using DB2 profile tables. With these tables, you can monitor the use of system resources by distributed applications as well as set special registers values for the remote application without having to change application code.
Posted: March 07, 2017 |
Recently while presenting a DB2 12 technical workshop, I discussed pre-migration requirements. One important consideration is the need to ensure that the current DB2 11 active logs are not greater than 4 GB. When the active logs are greater than 4 GB, DB2 11 will startup without a problem and ignore the portion of the log greater than 4GB; however, DB2 12 will not start when in V12R1M100 function mode.
Posted: February 28, 2017 |
I recently spent two weeks at the IBM Silicon Valley Lab (SVL) learning all about DB2 12 for z/OS. During the second week, I met with customers who participated in the DB2 12 Early Support Program (ESP). It was very exciting to learn first-hand from the developers who worked on DB2 12, and it was also nice to hear all the positive feedback from the customers. Having this level of access is one of the best things about my job with IBM. I feel very fortunate.
Posted: February 21, 2017 |
During a migration, DB2 12 will automatically rebind any package bound in DB2 9 and earlier versions. The automatic rebind results in a new package, while the previous package copy is automatically discarded. However, to ensure plan stability, a BIND should be done manually, because auto rebind won't copy the original package to the previous one. So if a regression in access path occurs, the REBIND SWITCH option is not available.
Posted: February 16, 2017 |
One big change in DB2 12 is the new install SYSOPR authority. Using install SYSOPR instead of SYSADM allows systems programmers to install or migrate DB2 without having access to user objects and user data.
Posted: February 07, 2017 |
The REORG utility is one of the most important tools in the DBA toolbox. Traditionally, the REORG table space or index utility is used to reorganize the data to improve access performance as well as reclaim fragmented space.
Posted: January 31, 2017 |
In my career as a DBA, I’ve done a lot work working around table space size limits. Managing this involves resizing, rebalancing, adding partitions, and much more. With this perspective, I can assure you that the dramatically increased partition sizes allowed in DB2 12 are a big deal.
Posted: January 24, 2017 |
I don't need to tell you that a career working with DB2 for z/OS is never boring. DB2 for z/OS continues to evolve at an ever-increasing pace. To help you keep up with all these changes, IBM has delivered a new Redbook, "DB2 12 for z/OS Technical Overview."
Posted: January 17, 2017 |