Installation considerations

This section discusses options for the installation and servicing of BMC Software products. It can help you determine which product distribution method is appropriate for your site’s installation and maintenance goals.

Installation method selection

The most desirable installation method should suit your product configuration needs while requiring the least amount of time and effort to install your products. To help you choose the best installation method, consider the following items:

• Existing BMC Software products that are installed at your site
• BMC Software products that you plan to trial or add to your data center
• Maintenance level of BMC Software products at your site
• Time and effort that are required for product customization
• Installer’s knowledge of SMP/E procedures and terminology

Before you can install SUPEROPT and make it operational, you must consider the following prerequisites:

• Operating system software requirements for SUPEROPT
• Amount of virtual storage that is required for operation of SUPEROPT
• Amount of DASD storage that is required for installation of SUPEROPT by using the Installation System
• Target system changes that you might need to make before installing and customizing SUPEROPT

Target system changes

Before installing and customizing SUPEROPT, you must make the following target system changes:

• Determine whether your site security system controls access to tape data sets at the data set name level.

If your security system controls access to tape data sets at the data set name level, perform the following actions:

• Define a rule for each data set to provide read access (by first scanning the tape to determine the data set names).
• Execute the installation jobs by using an authority level that is sufficient to provide generic read access.
• If you will perform AutoCustomization, you must ensure write access to the following items:
  • SYS1.PARMLIB
  • JES procedure library (SYS1.PROCLIB or equivalent)
  • previously APF-authorized load library
  • SYS1.VTAMLST (or equivalent) for MAINVIEW Alternate Access

Standard CICS user exits

SUPEROPT uses only standard user exits that CICS provides:

• XKCREQ
• XPCFTCH
• XTCIN
• XTCOUT
• XTCTIN
• XTCTOUT
• XZCIN
• XZCOUT
• XZCOUT1
• XXMATT

Other programs in your CICS system might use one or more of these CICS exits. CICS passes control to the programs in “first enabled, first called” order. If you need the programs to run in a certain order, BMC Software recommends that you use a PLT at CICS startup to specify the order in which the programs will be enabled.

LPA, ELPA, and SVA

If you are running several CICS systems, they can share a copy of the following modules:

• COPOPT
• COPOPT23^a
• COPOPT41^a
• COPOPT51^a
• COPOPT52^a
• COPOPT53^a
• COPOPTXA^a

These modules can also be placed in your link pack area (LPA) if you have MVS.

^a These modules can be placed in the extended link pack area (ELPA).

MRO environments

If your site is using MRO, install SUPEROPT in each terminal-owning region.

To optimize any terminals or printers that are owned by an application region, install the product in this region as well. The Optimizer optimizes data streams when the data streams are being sent to or from the terminal. Optimization does not occur when the data streams are sent between regions.

Transids routed by the CRTE

The Optimizer identifies all your transactions that are routed by the CRTE as TRANSID=CRTE.

Transactions that are routed by using the program control table (PCT) SYSIDNT parameter to specify the remote system name are identified in the normal manner.

CICS autoinstall feature

SUPEROPT functions correctly with the Autoinstall (automatic installation of terminals) feature of CICS/VS 1.7 or later.

SUPEROPT functions correctly with the Autoinstall (automatic installation of terminals) feature of CICS/VS 1.7 or later.

Table Preinstallation Worksheet shows the default number of DTAs for all operating systems. To change the number of DTAs, use option 1.6.3. The new number takes effect immediately.

MVS/ESA, OS/390, and z/OS

No modifications are needed for MVS/ESA, OS/390, or z/OS environments. If you are using the extended architecture (XA) option of CICS, the product performs the following activities:

• Detects these environments dynamically and exploits them
• Automatically places all programs and work areas above the 16 MB line, except for a control program of 266 bytes
• Obtains storage from EDSA if you are using CICS/ESA

BMC Software recommends the storage that is listed in below table, based on an MVS/ESA, OS/390, or z/OS environment (with the XA option of CICS being used) in which all storage that is used by SUPEROPT is obtained from above the 16 MB line. CICS/ESA storage is allocated from the EDSA.

Storage Recommendations for MVS

CICS/ESA

If you are running CICS/ESA, COPINIT must run after the entry for DFHDELIM in the PLT startup.

If you use the CMDSEC=EXTERNAL option or PCT entries, COPSHUT must run before the entry for DFHDELIM in the PLT shutdown.

Customization options

Because data center requirements vary, BMC Software provides several options to help you customize SUPEROPT to meet your needs. These options let you perform the following actions:

• Use the VTAM Netname or CICS Termid to identify terminals for optimizing, and for storing and displaying the optimization statistics
• Exclude from or include for optimization all data streams that are sent to your CRTs or printers
• Control whether data streams that were optimized by the Imaging Optimization technique are sent to your CRTs or printers
• Control whether Input Suppression optimization is used
• Control whether your terminal operators can use the Erase Input key
• Control whether SCS printer optimization is used
• Control the amount of storage that is used by the Optimizer
• Change the number of dynamic terminal areas
• Change these options from the Monitor after you have installed the Optimizer

For in-depth discussions about these options, see Using.