Skip to Content
Information

This site will undergo a brief period of maintenance on Friday, 18 December at 12:30 AM Central/12:00 PM IST. During a 30 minute window, site availability may be intermittent.

OPERTUNE configurations

You can run OPERTUNE in any of the following configurations:

Configuration

Description

One OPERTUNE system running on one MVS system

Multiple OPERTUNE systems running on one MVS system

OPERTUNE system running on local and remote MVS systems

To understand OPERTUNE configurations, you should be familiar with the following terms:

Term

Definition

Host OPERTUNE

The host OPERTUNE resides on the same MVS as the dialog user. The host is responsible for processing dialog requests, turning them over to the target OPERTUNE, and receiving and displaying results from the target OPERTUNE.

Target OPERTUNE

The target OPERTUNE is responsible for receiving and responding to requests from the host OPERTUNE:

  • The target and the host might be the same OPERTUNE (single configuration)
  • The target might be a different OPERTUNE residing on the same MVS (multiple configuration
  • The target might reside on a different MVS system (remote configuration)

Communication is accomplished through XCF or VTAM if the host and target OPERTUNE are distinct.

Target subsystem

The target subsystem is the Db2 subsystem that is under control of the target OPERTUNE. All Db2 specific requests affect the target subsystem.

Primary and
secondary targets

All OPERTUNE features work with either a target OPERTUNE or a target subsystem. Some features work with only one OPERTUNE or one subsystem (the primary target), while others can work with additional OPERTUNEs or subsystems at the same time (secondary targets):1

  • If a feature works with only one OPERTUNE, the designated primary OPERTUNE receives and responds to the requests. Similarly, if a feature works with only one subsystem, the primary subsystem is affected by requests.
  • If a feature works with only one subsystem, the request affects only the primary subsystem. IF the feature woks with multiple subsystems, the request affects the primary subsystem and all secondary subsystems.2

1 For example, a group profile pertains to one OPERTUNE, but you can issue a free command against multiple subsystems simultaneously.

2 You must have only one primary target OPERTUNE and only one primary target subsystem. You can have as many secondary target OPERTUNEs and secondary target subsystems as you want.

This section contains the following topics:

 

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

OPERTUNE for DB2 12.1