CICS VR V4.2 or V5.x affected by the June 2015 Leap Second

The overall document on planning for the upcoming LEAP second change for z/OS is Leap Seconds and Server Time Protocol (STP) - What should I do?

As for CICS VR 4.2 and CICS VR 5.x, there are no known problems, actions, or maintenance required related to the additional Leap second to be added in June 2015.

The CICS VR server modules that interface with z/OS logstreams use a common internal macro (?dwwl2sub) to adjust for leap seconds using the CVTLSO value from the CVT so CICSVR relies upon the value in CVTLSO in the LPAR.

CICS VR V5.2 does document that users of the CICS VR file copy notification service macro, CALL DWWCVRN, need to make sure they have no problems related to LEAP seconds. If you write code of your own or use Other Equipment Manufacturer (OEM) code that uses the CICS VR backup service notification macro, the CICS VR interface will adjust for LEAP seconds based on CVTLSO. However, your code or the OEM code must also be aware of LEAP seconds as CICS VR will use CVTLSO to apply them.

If you have not already, you might also want to review the Server Time Protocol Planning Guide IBM Redbook publication.

IBM also documents several resources related to the Server Time Protocol (STP) planning and FAQs under IBM Systems Mainframes Advantages.