Discussion created by iain.dk.robertson on Aug 6, 2018
Latest reply on Aug 7, 2018 by iain.dk.robertson



We've just found out that as of the next z/OS release, the DIAGxx parm ALLOWUSERKEYCSA is being removed. This will mean that any program running in storage key 8 or above will no longer be able to allocate or update common storage - see https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.e0zm100/BCP_vsm-rsm_userkeyCA_v2r3.htm

We currently run IDMS and CICS in key(8), so will probably change IDMS to run in key(4). The issue we face is that we (1) have some home written code which runs in CICS but reads the IDMS ESE/ERE areas and (2) modify the IDMSINTL interface to both read and update the ERE extension.

Obviously this change is going to cause us some issues, and we're looking at ways round them. Has anyone else run across this situation, and if so what steps did you take to get round the storage key issues?. Running CICS in anything other than key(8) is a non-starter, and a lot of the code that's affected is old code that is thoroughly embedded in out application design, so a wholesale re-write is probably a sub-optimal solution.


Thanks in advance for any comments/suggestions.


Iain Robertson