Upgrade from 13.0 to 13.5

book

Article ID: 205848

calendar_today

Updated On:

Products

CA OPS/MVS Event Management & Automation

Issue/Introduction

We are looking at upgrading from 13.0 to 13.5.  

There do not seem to be any structural changes for the SYSCHK1 datasets or OPSLOGs, so upgrading to 13.5 and backing out to 13.0 does not require anything special to move between these releases?  

Best Practices indicates:  "Verify your product JES2 offset table corresponds to JES2 on this system." How do we verify? We no longer assemble the OPJ2CB module.

 

Environment

Release : 13.5

Component : OPS/MVS

Resolution

The upgrade from OPS 13.0 to 13.5 should be smooth:

- you can use the same OPSLOG and SYSCHK1 datasets

- going back to OPS 13.0 from OPS 13.5 should not be a problem either, you can still use the same OPSLOG and SYSCHK1 files

The backup of the SYSCHK1 dataset is always a good practice even upgrading or reverting but you should not need to use it.

Regarding the JES2 interface, you just need to make sure you have the required maintenance to support the z/OS release that is currently running. We no longer assemble the OPJ2CB module. Please, visit the OPS compatibility matrix and make sure you apply all required maintenance for the z/OS level and also for other products/interfaces you may use:

https://ftpdocs.broadcom.com/WebInterface/phpdocs/0/MSPSaccount/COMPAT/CLX.HTML

If you have the maintenance required to support the current z/OS release there shouldn't be any concerns regarding the JES2 interface.

Lastly, I have 2 additional recommendations:


1) Apply all maintenance published for OPS 13.5 or at least the HIPER PTFs listed below:

SO14418 08-13-2020 FIX OPS13.5 SMPE INSTALL SCRIPT
SO13923 07-10-2020 PRP RESOLVING SO13296/SO13791 DUE TO S0C4 ABEND
SO13422 06-02-2020 PREVENT EMERGENCY PRODUCT SHUTDOWN
SO10726 11-07-2019 POSSIBLE STORAGE ISSUES WITH SERIALIZEEOT=YES
SO10476 10-30-2019 USING ADDRESS HWS SETATTR NOT SETTING CORRECT VALUE.
SO10450 10-18-2019 POSSIBLE SYSTEM OUTAGE DUE TO LATCH CONTENTION
SO09387 08-13-2019 OPSCPU SHOWS SOME OFFLINE CP'S AS NOTAVAIL
SO06939 01-11-2019 POSSIBLE EMERGENCY PRODUCT SHUTDOWN
SO05680 09-28-2018 POSSIBLE ADDRESS SPACE HANGS DUE TO LATCHES
SO05619 09-25-2018 OPMS MISALIGNED PREVENTING SYSLOGD SERVER START
SO05541 09-19-2018 ABEND S0C3 OPSMMG+6A
SO04989 08-16-2018 VARIOUS PROBLEMS WITH AOF RULE PROCESSING
SO01752 05-01-2018 POSSIBLE SUSPENSION OF SYSTEM TASKS

The above list was created in December, 2020. Visit our support site to check if any new HIPER PTFs have been published:

https://support.broadcom.com/download-center/solution-details-new.html?sku_code=PVLA2.00200&release=13.5

2) A recurrent problem during upgrades is the usage of mixed releases of OPS modules. For example, if you put the OPSAEX module in the LPA, make sure you refresh this module so that the correct release is used when upgrading or reverting. If you don't put this module in the LPA (this is not required) then you just need to pay attention to the LNKLST and/or STEPLIBs. Also pay attention to the libraries allocated to TSO/ISPF to make sure they are from the correct release.

Additional Information

https://techdocs.broadcom.com/us/en/ca-mainframe-software/automation/ca-ops-mvs-event-management-and-automation/13-5/release-notes/migration-information.html