IDMS

Expand all | Collapse all

IDMS and zOS 2.4 considerations

  • 1.  IDMS and zOS 2.4 considerations

    Posted 07-20-2021 02:55 PM
    We will be upgrading to zOS 2.4 (from 2.3) this fall and I am wondering if there are any special things I will need to do.

    I remember 2.3 being a hassle because of AllowUserKeyCSA(NO) and some issues with APF authorized libs for which we had to separate some modules into an APF specific load library.


  • 2.  RE: IDMS and zOS 2.4 considerations

    Posted 07-20-2021 03:02 PM

    We had no issues with IDMS when upgrading to z/os 2.4.

     

    Ian Cameron

    Michigan State University.

     






  • 3.  RE: IDMS and zOS 2.4 considerations

    Posted 07-20-2021 03:12 PM

    I have survived MANY os upgrades – I cannot remember a time when we HAD to modify IDMS because of an OS upgrade – as far as the ALLOWUSERKEYCSA we had the os team keep the option they had to allow us to adjust AT OUR SCHEDULE

     

    But the BEST solution (in my opinion) is to:

     

    Run a RECEIVE HOLDDATA

    Run a fixcat:

    SET BDY(GLOBAL).            

        REPORT MISSINGFIX       

        FIXCAT(*)               

        ZONES(IDMSTGT) NOPUNCH. 

     

    And note any non-applied fixes related to the z/os release you are moving to ...

     

     

     

     

     

    Chris Hoelscher

    Lead Sys DBA

    IBM Global Technical Services on assignmemt to Humana Inc.

    T 502.476.2538  or 502.407.7266

     






  • 4.  RE: IDMS and zOS 2.4 considerations

    Broadcom Employee
    Posted 07-20-2021 03:16 PM
    As long as you are running CVs in KEY(4) as described in  Storage Key Considerations doc  (same thing you would have had to do for AllowUserKeyCSA(NO))  you should be OK.