Will CA OPS/MVS issue Hyper Notifications when there are changes to JES2control blocks due to a new IBM z/OS release that affects the OPJ2CB module?

Document ID : KB000011586
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

Fix RO92111 says:
To use the JES2 environmental OPSINFO/OPSJES2 functions, you are no longer required to assemble the OPJ2CB module.  All supported releases of JES2 control blocks are delivered with the product, and any new releases of control blocks are delivered in the maintenance stream.

Question:

Will CA OPS/MVS issue Hyper Notifications when there are changes to JES2 control blocks due to a new IBM z/OS release that affects OPJ2CB?

Environment:
OPS/MVS 12.3 or Laterz/OS 2.3 or LaterJES2
Answer:

Updates to OPJ2CB are on a z/OS release boundary. So, when z/OS 2.3 becomes GA, we will publish a new PTF for all supported OPS/MVS releases. This is not considered a Hyper PTF and therefore customers will not get automatic notifications of it. (Customers must sign up to receive Hyper Notification on CA Support Online). When a customer upgrades to a new version of z/OS, they should review the available FIXCAT HOLDDATA link on the z/OS Compatibility Matrix page. Here they will be able to download the available fixes for the particular hardware device, software or function. In this case, any JES2 updates will be in the z/OS updates. This applies to all z/OS based products.


Additional Information:

Hyper Subscriptions - Document ID: TEC317883
http://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.tec317883.html

Proactive Notifications & Hypers
https://support.ca.com/irj/portal?NavigationTarget=navurl://176fc169794fd3e12d5f85c43a648581

We have 3 categories of notification:
1. Critical Alert: Defined as a high impact and/or pervasive software problem that has been determined to be critical to the operation of the product, or major impact to the customer's environment, or may negatively impact a large amount of customers.

2. Advisory: Defined as a moderate or low impact and/or non-pervasive software problem that has been determined to effect the operation of the product in one or more of our customer's environments.

3. Product Update: Defined as informing customers of product news.