CA View/Deliver Maintenance strategy on a multi-LPAR Plex

Products

• View

Issue/Introduction

We are implementing maintenance on our CA View/Deliver 14.0 systems in a parallel sysplex with a shared JES2 MAS between two LPARs. 

These two LPARs have shared DASD and View/Deliver runs out of the linklist using the same runtime libraries. 

One of these LPARs is used for development and one is used for production. 

I have been asked to implement the latest View 14.0 maintenance on the development LPAR prior to implementing it in the production LPAR rather than implementing across the whole plex (both LPARs at the same time). 

The only way I know to accomplish this would be to point the development LPAR to different named loadlibs via a JOBLIB or STEPLIB.

In doing this, would it pose any risk to our production LPAR, to be running two different levels of View/Deliver on these two LPARs sharing the same MAS? 

Environment

Release : 14.0

Resolution

As the client is referring to having one maintenance level of View 14.0 in one environment, and a higher maintenance level of View 14.0 in another environment, there would be no problems as the basic functions of the 14.0 release are the same for both environments.

Higher View maintenance will most likely contain additional product functionality, but the basic functionality is the same. 

It is recommended to either use a JOBLIB or STEPLIB, as it is a good way to distinguish what is being used in the corresponding environments.

As well, there are no issues regarding JES2. 

 

.