Product requirements

OPERTUNE requires specific software and system environments.

Software requirements

OPERTUNE requires the following systems and programs:

• z/OS version 1.4 and later and z/OS.e running on 64-bit-enabled architecture
• Db2 UDB for z/OS and OS/390 version 7 or Db2 UDB for z/OS version 8
• TSO/E—any release supported by the supported releases of Db2
• ISPF—any release supported by the supported releases of Db2
• ACF/VTAM version 4.2 or later (if using the VTAM option)
• Db2 Solution Common Code (SCC) version 1.5.00

Special requirements

OPERTUNE must execute from an APF-authorized load library.

Storage estimates

OPERTUNE requires sufficient DASD and CPU storage to operate effectively.

DASD space

DASD space usage summarizes the amount of DASD space that OPERTUNE needs.

DASD space usage

CPU usage

The percentage of CPU usage that OPERTUNE requires depends on the number of command requests received and how frequently OPERTUNE collects sample data. The CPU usage value is usually less than 0.1 percent of the total MVS CPU usage, although the value could range as high as 1 percent if your sample frequency is high.

Virtual storage

The amount of virtual storage used by OPERTUNE depends on a number of factors, some of which you can control through OPERTUNE administration. Most storage allocated by OPERTUNE exploits MVS/XA extended addressing for common and private storage requests. In general, the only storage obtained below the 16-MB address line is storage required for I/O (for example, data control blocks, or DCBs) and save areas.

TSO dialogs

The private virtual storage requirements for TSO dialogs are as follows:

• Above the 16-MB line—550 KB
• Below the 16-MB line—50 KB

OPERTUNE address space

Following Virtual storage requirements summarizes the virtual storage requirements for the OPERTUNE address space.

Virtual storage requirements