You are currently on IBM Systems Media’s archival website. Click here to view our new website.

Bookmark and Share

Recent Posts

Deprecated Functions: A Primer

December 20, 2016

When IBM decides to remove a function from DB2 for z/OS (or any DB2 offering), it's generally publicized in in the DB2 for z/OS announcement letter. See the DB2 12 for z/OS announcement letter, for instance.

However, deprecated functions are a different matter. A deprecated function isn't necessarily removed. Deprecated functions are also still supported in DB2--though obviously that support could be discontinued in the future. Notice I did not say "discontinued in a future release." With the introduction of continuous delivery, it's now possible to add or remove new functions through maintenance.  

The IBM Knowledge Center has a current list of DB2 for z/OS deprecated function. I appreciate that this list also has recommended alternatives for each deprecated function. There's also an additional column that notes whether a function has been removed. Now that functions can be removed during normal maintenance, I hope the Knowledge Center will soon note the function level that removes each function.

Here a few deprecated functions that I believe are especially significant:
  • SYNONYMS--I wrote about this being put on the DB2 11 deprecation list, but my understanding is it was later taken off the DB2 11 list. Obviously it's again listed for DB2 12 deprecation list. This is why you should regularly review the list, because when enterprises are using deprecated functions, they need a plan for phasing them out.
  • Basic row format table spaces--This will impact any programs such as utilities that are expecting the data to be in this format. The alternative is that all data will be stored in reordered row format. Programs will need to change to support the new format.
  • Non-Universal Table Space (simple, segmented, partitioned)--I recently said that the future of all table spaces will be UTS. Well, the future is here. Start planning now to convert all existing table spaces to either partition-by-growth (PBG) or partition-by-range (PBG) UTS.

Posted December 20, 2016| Permalink