My company is on IDMS v16.0 and looking at upgrading to z/OS 2.3. Is anyone in the IDMS arena using v16 with z/OS 2.3; and if so, are there any issues to be aware of?
The first/only thing that comes to mind is the z/os 2.3 AllowUserKeyCSA issue – release 19 has a process to resolve this, can the same be applied to R16 ?????
Also, may I ask what circumstances have forced you to remain on R16 ???
Technology Architect, Database Infrastructure Services
Technology Solution Services
123 East Main Street
Louisville, KY 40202
(502) 476-2538 or 407-7266
Long story for me.... hired-in the company last year in May as the IDMS DBA supporting v16; in June this year a corporate restructuring occurred and lost the IDMS systems programmer/analyst. The systems analyst was in the process of upgrading to 18.5, but very proprietary in their works. I'm not proficient as an IDMS systems analyst, not sure where to begin on resuming with 18.5 upgrade. Management has been made aware and they have been in conversations with CA/Broadcom about either extended support for v16, or upgrade to release 18.5, possibly 19.0 - and I haven't received any further information/notification as to how those conversations are panning-out.
Now we are looking at upgrading to z/OS 2.3 and want to know if IDMS 16 is compatible. I looked on the CA support site for compatibility, and only 18.5 and 19.0 are listed for z/OS compatibility.
I'm wondering if there are any other IDMS shops out there still on v16 and if they have been able to run with z/OS 2.3 without any issues (or needing to apply any PTFs afterwards)?
and to answer why forced to stay on v16...... there are some in-house written DB procedures and programs that still utilize modules from 10.2...... and to re-write programs that use them would be costly for the limited resources and expertise that were lost during the corporate restructuring..... I'm in a whirlwind
IDMS 16.0 went end of support January 2012.
z/OS 2.3 was released 2017 so no testing was done for rel 16.0
as far as AllowUserKeyCSA(NO) I am not aware of any issue specific to z/OS 2.3.
We have been running our CVs in key(4) for several releases and it can certainly be done for any CV regardless of release. It is a z/OS specification.
see Storage Key Considerations for z/OS CSA Subpools - CA IDMS - 19.0 - CA Technologies Documentation
I did confirm that Z/os 2.3 still allows ALLOWUSERCSA(YES) so if you are running in Key 8 you are good for now