During the early releases of DB2, enterprises (specifically DBAs) would restrict dynamic SQL from running in their production OLTP environments. This choice stemmed primarily from the likelihood of ad hoc OLAP queries adversely impacting the performance of OLTP applications. Of course, over the next 20-plus years, this issue has been largely mitigated by the widespread adoption of dynamic SQL. Dynamic SQL continues to be a focus of DB2 development, and DB2 12 features an important enhancement in the area of catalog availability.
Posted: April 25, 2017 |
Environmental descriptor manager (EDM) pools contain skeleton application plans and packages, database descriptors, and cached dynamic SQL statements.
Posted: April 18, 2017 |
The recent announcement of IBM Machine Learning on z/OS is significant for a couple of reasons. First, it's another example of IBM's ongoing investment to the mainframe. Beyond that, it's important for anyone who supports software installation, database administration and analytics on z/OS.
Posted: April 11, 2017 |
Designing and sizing table space requires DBAs to make numerous determinations. How many rows per day will be inserted/updated/deleted? How will the data be processed? What is the criteria to determine active versus historical data? How long will the data (active and historical) need to be stored before it will be deleted?
Posted: April 04, 2017 |
Prior to DB2 12 function level V12R1M500, altering column attributes such as data type, precision, scale or length would occur instantly.
Posted: March 28, 2017 |
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 |