Troy Coleman

Troy L Coleman




Bookmark and Share
RSS

Recent Posts

  • New and Changed Subsystem Parameters in DB2 11
    06/20/2017
  • MERGE Statement Enhancements in DB2 12
    06/13/2017
  • DB2 12 Technical Workshops
    06/06/2017
  • DB2 Tools Fix Lists
    05/30/2017
  • Parameter Places Retry Claims on Stopped Objects
    05/23/2017
  • Machine Learning Applications

    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.

    Read More

    Posted: April 11, 2017 |

    Adding a Partition Between Logical Partitions

    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?

    Read More

    Posted: April 04, 2017 |

    DB2 12 Pending Column Alterations

    Prior to DB2 12 function level V12R1M500, altering column attributes such as data type, precision, scale or length would occur instantly.

    Read More

    Posted: March 28, 2017 |

    Using Installation SYSOPR Authority

    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.

    Read More

    Posted: March 21, 2017 |

    Converting DBRMs to Packages in DB2 12

    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.

    Read More

    Posted: March 14, 2017 |

    DB2 12 Enhancements to System Profiles

    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.

    Read More

    Posted: March 07, 2017 |

    DB2 12 Active Logs Greater than 4 GB

    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.

    Read More

    Posted: February 28, 2017 |

    DB2 12 Webinar Series

    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.

    Read More

    Posted: February 21, 2017 |

    DB2 12 Plan Stability with APREUSESOURCE

    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.

    Read More

    Posted: February 16, 2017 |

    Administrative and Install Level Authorities

    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.

    Read More

    Posted: February 07, 2017 |

    Displaying results 11-20 (of 496)
     |<  <  1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10  >  >|