Is an IPL required when upgrading the product from R13.5 to R14.0?
Article ID: 263370
Updated On:
Products
Issue/Introduction
Can OPSMVS be upgraded without an IPL from version 13.5 to version 14.0?
I plan on just loading and refreshing the linklist datasets. All runtime dataset members will be updated with the R14.0 versions
I see when release 13.5 started, the following messages appeared:
OPS0310I DYNAMIC EXIT MODULE OPMVACEX ADDED TO EXIT POINT SYS.IEFACTRT
OPS0310I DYNAMIC EXIT MODULE OPMVACEX ADDED TO EXIT POINT SYSJES2.IEFACT
RT
OPS0310I DYNAMIC EXIT MODULE OPMVACEX ADDED TO EXIT POINT SYSSTC.IEFACTR
T
OPS0310I DYNAMIC EXIT MODULE OPMVUTEX ADDED TO EXIT POINT SYS.IEFUTL
OPS0310I DYNAMIC EXIT MODULE OPMVSLEX ADDED TO EXIT POINT CNZ_MSGTOSYSLO
G
would these exits be dynamically updated when we start release 14, or is there manual intervention that has to take place?
Environment
Release : 14.0
Resolution
Can OPSMVS be upgraded without an IPL from version 13.5 to version 14.0?
Yes, OPS/MVS can be upgraded without the need of an IPL.
I plan on just loading and refreshing the linklist datasets. All runtime dataset members will be updated with the R14.0 versions.
Please ensure that all available maintenance has been applied to the new 14.0 region. Also, please carefully review all the topics in the Release Notes section of the R14.0 product documentation:
And in particular, the topics describing New Features, Removed Features, Compatibility and Migration Information. Changes will need to be made accordingly prior to starting the OPS/MVS 14.0 region.
would these exits be dynamically updated when we start release 14, or is there manual intervention that has to take place?
Regarding the dynamic exits, the R13.5 versions do remain loaded once the R13.5 region is shut down, however no changes were made to those exits between R13.5 and R14.0 so no further action is required.
Feedback
