Multiple configuration


The multiple configuration uses two or more OPERTUNE systems on one MVS system. You might define one OPERTUNE to control a test subsystem and another to control a production system. You can authorize certain users for the test OPERTUNE and others for the production OPERTUNE. (However, an alternative is to define only one OPERTUNE for both subsystems and then limit user access through the subsystems instead of through OPERTUNE.)

A multiple configuration is also useful if you need to separate the OPERTUNE logs of multiple subsystems. In this scenario, you can designate one OPERTUNE for one set of subsystems and a separate OPERTUNE for another set of subsystems.

Information
Example

For example, assume you are user TSOA and you have designated OPTA as the host OPERTUNE. To modify DB2A, DB2B, or DBSA, you can select OPERTUNE A/APPLA as the target OPERTUNE. To modify DBSB or DB2C, you can select OPERTUNE B/APPLB as the target OPERTUNE.

Multiple OPERTUNEs on an MVS system

image2018-12-19_11-0-11.png

The host defaults to an active OPERTUNE when you begin a session. If more than one OPERTUNE is active, the host defaults to the host OPERTUNE of your previous session if that OPERTUNE is active. If that OPERTUNE is inactive, a selection menu is presented

If you want to use a multiple configuration, you can use the procedure in Selecting-a-host-OPERTUNE to set up your host.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

OPERTUNE for DB2 12.1