ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Product configuration considerations when cloning an LPAR


Article ID: 237074


Updated On:


OPS/MVS Event Management & Automation


When cloning an LPAR where OPS/MVS is running, is there any customization required from an OPS/MVS perspective on the new LPAR?

The new LPAR will be an exact copy of the old LPAR utilizing the same z/OS version, SMFID, products, datasets, etc.. and will not coexist with the old LPAR. It will be implemented on a separate machine with no connection to the old LPAR.


Release : 13.5

Component : OPS/MVS


As long as the old and new LPAR will not coexist, and the new LPAR is an exact copy of the old LPAR, then OPS/MVS should function on the new LPAR as before without further modification.