IBM Security zSecure compatibility for z/OS V2R2 and CICS V5R3
JeroenTiggelman 27000186A5 Visits (10587)
z/OS V2R2 was announced on July 28, 2015 with a planned availability date of September 30, 2015. Toleration fixes have been made available for zSecure 1.13.0, 1.13.1, 2.1.0, and 2.1.1.
The zSecure for z/OS release numbers follow those of z/OS. For complete support of a z/OS release, you generally need the same release of zSecure. However, compatibility fixes are sometimes provided for earlier zSecure releases.
A list of compatibility APARs to date follows below. If later APARs are added, these will be tagged with the fix category IBM.
Specific to zSecure Command Verifier: OA47815
These fixes prevent a.o. the following:
* issues caused by upgrading the RACF database (templates) to the z/OS V2R2 level, which is otherwise not properly recognized;
* error messages issued by the CKRCARLA program when using longer system symbols than were supported prior to z/OS V2R2;
* various issues with zSecure Collect for z/OS due to unexpected conditions.
In addition, APAR OA48761 also provides toleration support for CICS Transaction Server V5R3, without which CICS information will be missing in the CKFREEZE file.
These fixes do not prevent warning messages CKF372I, CKR1400, and CKR1403 (for running on an unsupported operating system) from being issued. You can suppress the messages via the CARLa statement SUPPRESS MSG=(1400,1403) or the CKFCOLL parameter SUPMSG=372 if required. You can also consider using CARLa statement OPTION NOWARNING or CKFCOLL parameter NOWARNINGRC to prevent the program return code for CKRCARLA and CKFCOLL, resp., from returning 4.
Edit: Full support for z/OS V2R2 requires zSecure 2.2.