DB2 - L

  • 1.  z/OS v12 Applying maintenance strategy

    Posted Oct 08, 2021 07:36 AM

    Our production Db2 is at V12R1M500, code, cat & function.

     

    Test subsystems (5 of them) now at M509 code & cat, M500 function level.

     

    I have been asked not to roll this into production until next year.

    My research to date shows no way to undo the catalog catmaint and clearly states code level must match highest function ever used and highest catalog level, so no way for me to regress.

     

    My understanding is that we can prevent new functions from hitting production, holding all at M500, what risks are there that something else works in test and will not work in production, or worse still, cause an issue that brings production down ?

     

    I am considering rebuilding those lower levels at M500...

     

    Email Signature 2021



  • 2.  RE: z/OS v12 Applying maintenance strategy

    Posted Oct 09, 2021 08:38 PM
    First thing is that while the code level must be at least as high as the catalog (catmaint) level,
    it can be higher. In fact it is recommended to *not* catmaint to a new level when that code
    level is applied. Wait until you are happy with the latest maintenance, and only then do the
    catmaint. Specifically because this allows you to revert to your previous maintenance/code
    level if there are any problems.

    Similarly the catalog level must be at least as high as the highest function level, but it can be
    higher.

    Ditto function level wrt SQLLEVEL (DSNHDECP).

    Does your question imply that you have not been applying maintenance to production - hence
    keeping its code level at M500? I'd suggest that this would create the the possibility that
    something "works" in test because a PTF has fixed a problem, and it will fail in production
    because the PTF is missing.

    James Campbell

    On 8 Oct 2021 at 11:35, Mark Vickers via Internationa wrote:

    > Our production Db2 is at V12R1M500, code, cat & function.
    >
    > Test subsystems (5 of them) now at M509 code & cat, M500 function level.
    >
    > I have been asked not to roll this into production until next year.
    > My research to date shows no way to undo the catalog catmaint and clearly states code level must match highest function ever used and highest catalog level, so no way for me to regress.
    >
    > My understanding is that we can prevent new functions from hitting production, holding all at M500, what risks are there that something else works in test and will not work in production, or worse still, cause an issue that brings production down ?
    >
    > I am considering rebuilding those lower levels at M500...
    >
    >
    >

    --
    This email has been checked for viruses by AVG.
    https://www.avg.com




  • 3.  RE: z/OS v12 Applying maintenance strategy

    Posted Oct 11, 2021 12:58 PM

    Thanks James,

    That confirms my thoughts, so unless we are needing some new function or PTFs in production, I am going to keep them all at the same level.

     

    Thanks,

    Mark.