qfg00til.doc, printed on 10/16/2002, at 8:54 am unicenter ... · qfg00til.doc, printed on...

qfg00til.doc, printed on 10/16/2002, at 8:54 AM

Unicenter CA-QuickFetch Runtime Performance Optimizer

Getting Started 2.6

qfg00til.doc, printed on 10/16/2002, at 8:54 AM

This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by Computer Associates International, Inc. (“CA”) at any time.

This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies.

This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed.

To the extent permitted by applicable law, CA provides this documentation “as is” without warranty of any kind, including without limitation, any implied warranties of merchantability, fitness for a particular purpose or noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or indirect, from the use of this documentation, including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage.

The use of any product referenced in this documentation and this documentation is governed by the end user’s applicable license agreement.

The manufacturer of this documentation is Computer Associates International, Inc.

Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

2002 Computer Associates International, Inc. (CA)

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

qfg00toc.doc, printed on 10/21/2002, at 8:50 AM

Contents

Chapter 1: Product Overview What Unicenter CA-QuickFetch Does ............................................ 1-1

Program Loading Without Unicenter CA-QuickFetch .......................... 1-4 Program Loading With Unicenter CA-QuickFetch ............................. 1-5

Unicenter CA-QuickFetch and z/OS Terminology................................. 1-6 How Unicenter CA-QuickFetch Benefits Your System.............................. 1-7 What Are the Advantages of Using Unicenter CA-QuickFetch? ..................... 1-8 What Are the Features of Unicenter CA-QuickFetch? .............................. 1-9

The Unicenter CA-QuickFetch Virtual Storage Area............................ 1-9 Multiple Address Spaces ................................................... 1-10 The Fetch Activity List ..................................................... 1-11 Automatic Update Detection ............................................... 1-12 Automatic Library Management ............................................ 1-13 Protecting and Excluding Members ......................................... 1-13 Support for Clone Libraries................................................. 1-14 Immediate Page-in for Modules............................................. 1-14 Internal Monitoring of Virtual Storage Usage................................. 1-14 A Monitor for Displaying Fetch Statistics .................................... 1-15

What to Read Next ............................................................ 1-16

Contents iii

qfg00toc.doc, printed on 10/21/2002, at 8:50 AM

Chapter 2: Preparing for Installation Operating System Requirements ................................................ 2-1 Contents of Installation Tape.................................................... 2-2 Preparing for Installation ....................................................... 2-2 Licensing Requirements ........................................................ 2-3

Computer Associates LMP .................................................. 2-4 LMP Key Certificate........................................................ 2-4 Specifying the LMP Code ................................................... 2-5

Chapter 3: Installation Previewing the Installation ..................................................... 3-1 Installing Unicenter CA-QuickFetch ............................................. 3-2

Step 1: Copy the QF.CNTL Library from the Tape ............................. 3-2 Step 2: Install the Load Modules ............................................. 3-3 Step 3: Install the Manuals .................................................. 3-4 Step 4: Remove Load Modules from LLA Management (Optional) .............. 3-6 Step 5: Install the AMASPZAP Replacement Program (Optional) ............... 3-7 Step 6: Specify Parameters .................................................. 3-9 Step 7: License Unicenter CA-QuickFetch For Your Site ....................... 3-14 Step 8: Install the QFMON ISPF Panel....................................... 3-14 Step 9: Edit and Copy the Startup Procedure................................. 3-15 Step 10: Set Up the Advantage CA-Roscoe Interface (Optional) ................ 3-15

Test Starting Unicenter CA-QuickFetch ......................................... 3-16 Starting Unicenter CA-QuickFetch Automatically at IPL Time..................... 3-16 Going on From Here .......................................................... 3-17

Index

iv Getting Started

qfg01int.doc, printed on 10/21/2002, at 8:39 AM

Chapter

1 Product Overview

This chapter provides an introduction to Unicenter® CA-QuickFetch® Runtime Performance Optimizer (Unicenter® CA-QuickFetch®) and describes how it reduces the DASD I/O associated with program loading.

What Unicenter CA-QuickFetch Does Unicenter CA-QuickFetch is designed to improve the performance of your z/OS (and OS/390) operating system. Unicenter CA-QuickFetch eliminates a large amount of the I/O that is associated with program loading. Program loading occurs when an application or program requires that a load module be brought into the processor storage. The load modules reside on Direct Access Storage Device (DASD) volumes in partitioned data sets (PDSs), which are also called libraries.

Program Management is the component of z/OS that is responsible for locating modules and loading them from a DASD volume into virtual storage. IBM also refers to this component as Contents Supervision. When an application requires that a load module be brought into processor storage, it issues a macro (LOAD, LINK, XCTL, or ATTACH) that requests the module.

Product Overview 1–1

What Unicenter CA-QuickFetch Does


The following steps describe how Program Management resolves a program load request:

1. Program Management first searches for the module in the Job Pack Area (JPA). The JPA is in the private address space of the user that requested the load module.

2. If the module is not in the JPA, Program Management then initiates a directory search against the JOB/STEP/TASK libraries to find the location of the module.

3. If Program Management does not find the module in the JOB/STEP/TASK libraries, it searches the Link Pack Area (LPA). The LPA resides in both the common service area (CSA) and the extended CSA (ECSA).

4. Finally, if the module is not in the LPA, Program Management issues a directory search against the LNKLST libraries to find the location of the module.

If Program Management locates the requested module in the JPA or the LPA, it does not need to load the module from DASD. If it locates the module in the JOB/STEP/TASK or LNKLST libraries, Program Management issues a fetch request to read the load module and prepare it for execution. If Program Management cannot find the requested load module, the program load fails.

This method of loading modules is inefficient if z/OS must repeatedly load the same modules from DASD. You can create cloned copies of frequently accessed libraries to try to reduce DASD I/O. However, the clone libraries also reside on DASD volumes; therefore they do not reduce the amount of DASD I/O that is required to load modules. They just spread the I/O out across several volumes and paths. Additionally, clone libraries require extra time and attention for maintenance. This can be a costly solution, often requiring the purchase of additional DASD volumes and other I/O hardware resources, such as controllers and channels.

1–2 Getting Started



Placing modules in the LPA can help reduce the I/O problem somewhat; however, it can only maintain reentrant load modules. In addition, if you increase the size of the LPA to hold the load modules, you reduce the amount of virtual storage that is available for other processing. Storing modules in the JPA can help users who repeatedly request a small set of load modules. However, this only partially alleviates the problem because of the strict rules for sharing and reusing modules in the JPA. In addition, if other users access the same load modules, the modules have to be repeatedly read from DASD, because one user cannot access the JPA of another user.

Many system-related programs, such as compilers, sort programs, and TSO command processors are repeatedly loaded from DASD. Often, Program Management has to search several DASD volumes to locate these programs. Also, most applications require the execution of several load modules. Program Management must search for each load module individually. If Program Management must read several of the load modules from DASD, there will be considerable delays.




Program Loading Without Unicenter CA-QuickFetch

The following illustration shows the amount of I/O that is associated with fetching load modules from DASD. Without Unicenter CA-QuickFetch, program loading requires a large amount of DASD I/O.




Program Loading With Unicenter CA-QuickFetch

Unicenter CA-QuickFetch eliminates much of the DASD I/O associated with program loading. It automatically determines what libraries to manage, determines the most frequently requested load modules from these libraries, and maintains copies of the modules in its own virtual storage area. When z/OS receives a request to load one of these modules, Unicenter CA-QuickFetch intercepts the request and satisfies it by moving the load module from its virtual storage area to the address space of the requestor. This “virtual-to-virtual” transfer of load modules is faster and more efficient than loading a module from DASD.

As illustrated below, Unicenter CA-QuickFetch significantly reduces or eliminates the DASD I/O that is associated with program loading. With Unicenter CA-QuickFetch, in-storage program loads replace most of the DASD I/O.

Controller


Unicenter CA-QuickFetch and z/OS Terminology


Unicenter CA-QuickFetch and z/OS Terminology To understand how Unicenter CA-QuickFetch works, you should be familiar with certain Unicenter CA-QuickFetch and z/OS terminology.

Term Explanation

BLDL On z/OS systems, a Build List (BLDL) macro instruction initiates PDS directory searches to determine the location of a requested load module. If the directory search for a module is successful, the BLDL macro instruction returns the directory entry of the module. Program fetch uses this information to determine the location of the module on DASD.

LNKLST library A partitioned data set (or a concatenation of a partitioned data set) that everyone on the system may use. LNKLST libraries contain operating system programs, compilers, TSO command processors, and other programs that many users would access. When the operating system initializes, the LNKLST is defined as the default location for these programs. Specifically, the LNKLST is the default location for the non-resident program load modules.

Private Library Any PDS that is not part of the LNKLST concatenation. Unicenter CA-QuickFetch also considers any LNKLST library accessed outside of the LNKLST concatenation (for instance, a JOB/STEP/TASK concatenation) to be a private library. Private libraries may contain load modules or non-load modules. They contain members that individual users create, edit, move, copy, and delete.

Program Fetch The service that the z/OS Program Management uses to load a module from DASD. The input to program fetch includes the output of a BLDL request (which contains the location of the module on DASD).


How Unicenter CA-QuickFetch Benefits Your System


How Unicenter CA-QuickFetch Benefits Your System

Unicenter CA-QuickFetch increases job throughput on your system and improves user response time. Because Unicenter CA-QuickFetch increases the efficiency of your system, it prolongs the time that your system is useful, allowing you to defer hardware upgrades. It also saves money because it allows your users to be more productive, obtaining better response time. Unicenter CA-QuickFetch provides the following benefits to your z/OS system:

■ Decreased I/O to DASD with libraries. This allows you to allocate your I/O resources to other system functions, such as paging and data base access, which might be impairing the performance of your system.

■ Reduced I/O to critical system libraries.

■ Decreased busy time for certain channels, control units, head-of-strings, and DASD volumes.

■ Reduced program loading from your hardware cache. This allows you to devote the hardware cache to other types of I/O.

■ Reduced virtual storage constraints. This occurs when you remove the program load modules from the Link Pack Area (LPA), and manage them with Unicenter CA-QuickFetch and another Computer Associates product, Unicenter® CA-PMO™ Runtime Performance Optimizer (Unicenter® CA-PMO™).

■ Increased knowledge of program loading activity on your system. Unicenter CA-QuickFetch provides you with online statistics about fetch activity at the system, library, and module level.


What Are the Advantages of Using Unicenter CA-QuickFetch?


What Are the Advantages of Using Unicenter CA-QuickFetch?

You can install Unicenter CA-QuickFetch quickly and easily. It requires no IPL or system modifications, and it calls for little or no operator training. In addition, it offers several advantages over other methods of reducing DASD I/O due to program fetch activity:

■ Unicenter CA-QuickFetch works automatically with all components of z/OS that generate fetch activity, not just a single subsystem such as IMS. It works with all types of programs (reentrant, reusable, and nonreusable) to manage standard load libraries.

■ Unicenter CA-QuickFetch automatically decides what libraries to manage so you spend no time tuning.

■ Unicenter CA-QuickFetch automatically detects updates after module link-edits and purges the old versions of the modules from the virtual storage area. This allows new copies of updated modules to be loaded into the Unicenter CA-QuickFetch storage areas.

■ Unicenter CA-QuickFetch provides an AMASPZAP replacement program that automatically communicates zap updates to Unicenter CA-QuickFetch. Unicenter CA-QuickFetch can then purge the old versions of the zapped modules, and load the new versions when needed.

■ You can run Unicenter CA-QuickFetch in multiple address spaces. This eliminates the problem of having critical applications with different loading frequencies competing for storage.

■ Unicenter CA-QuickFetch supports clone libraries so you do not have to keep multiple copies of load modules in the Unicenter CA-QuickFetch virtual storage area.


What Are the Features of Unicenter CA-QuickFetch?


■ Unicenter CA-QuickFetch provides complete, reliable, automatic update detection. You can discontinue use of the Library Lookaside (LLA) for managing load modules.

■ Unlike Library Lookaside, Unicenter CA-QuickFetch does not allocate a library with DISP=SHR the entire time that it is being managed. This allows for utilities, such as a library compress, to be performed without removing the library from management.


Unicenter CA-QuickFetch offers the following features that help reduce the amount of DASD I/O that is normally associated with program loading.

The Unicenter CA-QuickFetch Virtual Storage Area

Unicenter CA-QuickFetch maintains its own virtual storage area. This area normally occupies one address space; however, you can run multiple Unicenter CA-QuickFetch address spaces if you want to. For details on doing this, see Multiple Address Spaces in this chapter.

By default, Unicenter CA-QuickFetch manages all LNKLST libraries. In addition, it automatically determines which private libraries it should manage based on their loading activity. It then uses a fetch activity list (see The Fetch Activity List in this chapter) to determine which modules from these libraries are accessed most frequently. It can recognize modules with the same name that are in different libraries. It maintains a copy of these modules in its virtual storage area. Unicenter CA-QuickFetch resolves requests for these modules by transferring the modules from its own virtual storage to the virtual storage of the program requestor.




Multiple Address Spaces

Normally, you run Unicenter CA-QuickFetch in a single virtual address space. However, you can run multiple Unicenter CA-QuickFetch address spaces, if necessary. Multiple address spaces are useful if you have several applications with different frequencies of program loading. When you are running a single address space, Unicenter CA-QuickFetch purges the less frequently requested load modules from the virtual storage area so that modules with heavier fetch activity can be loaded. If you run multiple Unicenter CA-QuickFetch address spaces, you can manage different applications in each address space. Each module is competing for storage only with other load modules from the same application.

If you run multiple Unicenter CA-QuickFetch address spaces, each runs independently. There is no communication between address spaces. Each address space maintains its own fetch statistics. You can have different libraries managed in each address space or, you can have different modules from the same library managed in different address spaces. For example, you can place modules that are less than a specified size in one address space, and those greater than that size into a second address space. Each address space also maintains its own fetch activity list to automatically determine the modules from the managed libraries that are accessed most frequently. For more information, see The Fetch Activity List in this chapter.

In addition, Unicenter CA-QuickFetch allows you to set a different virtual storage limit for each address space.




The Fetch Activity List

Each Unicenter CA-QuickFetch address space maintains its own fetch activity list in the extended CSA. The primary function of the fetch activity list is to automatically determine the most frequently accessed load modules belonging to libraries that are managed in that address space. The fetch activity list also keeps statistics for all of the modules from the managed libraries. These statistics include the name of the module, fetch count, size, and location on DASD. If the module is loaded in that Unicenter CA-QuickFetch address space, the list also keeps the location of the module in the address space. Unicenter CA-QuickFetch adds an entry for a module to the list on the first fetch request for that module. When the fetch count of the module is high enough, Unicenter CA-QuickFetch loads the module into the managing address space. Unicenter CA-QuickFetch determines the value internally.

Unicenter CA-QuickFetch uses the fetch count to determine if a module should replace the module that has heavier fetch activity. If Unicenter CA-QuickFetch determines that a module should be loaded into the managing address space but there is not enough room, Unicenter CA-QuickFetch may purge one or more modules with less fetch activity to make room for it.

Unicenter CA-QuickFetch adds modules to the bottom of the fetch activity list. However, Unicenter CA-QuickFetch sorts the list frequently to make sure that the names of the most frequently requested modules remain at the top. The less frequently used entries are sorted to the bottom of the list where they are more likely to be replaced with modules that have more fetch activity. If Unicenter CA-QuickFetch deletes a module from the fetch activity list, the module also is deleted from the virtual storage area.

Note: You can protect modules so that Unicenter CA-QuickFetch cannot delete them from the virtual storage area. For more information, see Protecting and Executing Members in this chapter.




Automatic Update Detection

Unicenter CA-QuickFetch automatically detects all standard z/OS updates to modules. When Unicenter CA-QuickFetch receives a fetch request for a load module, it compares the current location of the module in the library (its TTR) with the location that Unicenter CA-QuickFetch is maintaining in the fetch activity list.

Note: The TTR that Unicenter CA-QuickFetch keeps in the fetch activity list is the TTR of the module at the time it was loaded in the virtual storage area.

If the module has been updated since it was loaded into the Unicenter CA-QuickFetch virtual storage area, the TTRs will be different, indicating that the version that Unicenter CA-QuickFetch is maintaining is no longer valid. Unicenter CA-QuickFetch deletes the old version of the module from its virtual storage area. Once the module has sufficient fetch activity, Unicenter CA-QuickFetch loads the updated version of the module into its virtual storage area.

Since the TTR does not change when the AMASPZAP program updates a module, Unicenter CA-QuickFetch provides an AMASPZAP replacement program to communicate zap updates to each Unicenter CA-QuickFetch address space. The AMASPZAP replacement program also detects maintenance updates by SMP/E to an existing module. If you use the Unicenter CA-PMO product, you can use the Unicenter CA-PMO cross-system component to communicate the zap updates to Unicenter CA-QuickFetch address spaces running on other systems. For details, see the chapter “How Library and Module Updates are Handled” in the Unicenter CA-QuickFetch Systems Programmer Guide.




Automatic Library Management

Unicenter CA-QuickFetch automatically determines what libraries to manage, so you do not have to spend time maintaining a list of libraries. As soon as one module in a library has enough activity to benefit from Unicenter CA-QuickFetch, Unicenter CA-QuickFetch begins managing the library. You can specify particular libraries that Unicenter CA-QuickFetch may or may not process, but this is optional.

Protecting and Excluding Members

Unicenter CA-QuickFetch allows you to protect modules in the virtual storage area. It also allows you to exclude members of managed libraries from Unicenter CA-QuickFetch management.

When you protect a module, Unicenter CA-QuickFetch will not delete the module from the virtual storage area to make room for a module with heavier fetch activity. This is helpful if an application requires a large module but the module is not requested often enough to remain loaded in the virtual storage area. Loading the module repeatedly from DASD requires considerable I/O. However, if the module remains loaded in the virtual storage area, Unicenter CA-QuickFetch can load the module more quickly when it is requested.

You also can exclude members of a library that Unicenter CA-QuickFetch manages. When you exclude a module from management, Unicenter CA-QuickFetch does not attempt to resolve fetch requests for that module.




Support for Clone Libraries

Unicenter CA-QuickFetch efficiently manages clone libraries by maintaining only one copy, in virtual storage, of modules belonging to clone libraries. After loading a module from a user-specified clone library into its virtual storage area, Unicenter CA-QuickFetch uses that copy of the module to satisfy fetch requests for any modules with the same name from any user-specified clone library.

Immediate Page-in for Modules

Unicenter CA-QuickFetch offers an immediate page-in feature for resolving fetch requests for modules that are larger than 8 KB. This is particularly beneficial for systems with limited central storage. When Unicenter CA-QuickFetch transfers a module, the pages containing the Unicenter CA-QuickFetch copy of the module must be brought into central storage, unless they are already there. Rather than waiting to access each page of the module sequentially while transferring the module, Unicenter CA-QuickFetch uses the z/OS page service facilities to immediately bring all pages of the module into central storage.

Internal Monitoring of Virtual Storage Usage

Internally, Unicenter CA-QuickFetch is constantly monitoring how its virtual storage is being used to determine the requirements for loading modules into the virtual storage area. For each address space, Unicenter CA-QuickFetch checks the user-specified maximum amount of virtual storage that is available and also checks to see how much virtual storage is in use.




If Unicenter CA-QuickFetch has ample storage, it continues to load modules as usual. However, if it determines that there is not enough virtual storage in an address space, Unicenter CA-QuickFetch adjusts the requirements for loading modules in that address space. If there is not enough virtual storage, Unicenter CA-QuickFetch requires that a module have more fetch requests before it is loaded. When the demand for storage lessens, Unicenter CA-QuickFetch lowers the requirements for loading modules.

Unicenter CA-QuickFetch similarly monitors paging statistics (that is, current Unreferenced Interval Counter (UIC) values) on your system and adjusts its initial loading criteria accordingly. When paging is high, more fetches are required to load a module.

A Monitor for Displaying Fetch Statistics

Unicenter CA-QuickFetch provides a monitor called QFMON, which allows you to see the information for fetch activity on your system. QFMON consists of several different displays. You can execute QFMON under TSO, Advantage™ CA-Roscoe® Interactive Environment (Advantage™ CA-Roscoe®), or as a batch job. QFMON informs you of how often Unicenter CA-QuickFetch is resolving fetch requests, how much virtual storage is being used, the size of the fetch activity list, which libraries Unicenter CA-QuickFetch is managing, performance and cost savings during the peak and current intervals, and so on. There are separate displays for each Unicenter CA-QuickFetch address space. You can use the information on the QFMON displays to determine how to tune Unicenter CA-QuickFetch to best meet the needs of your site.

Note: Monitor statistics are only available while Unicenter CA-QuickFetch is active, since storage used to hold the statistical data is freed at Unicenter CA-QuickFetch termination.


What to Read Next


What to Read Next The contents of the documentation set are summarized below:

■ To understand the operation and benefits of Unicenter CA-QuickFetch, see the chapter “Monitoring Fetch Activity with QFMON” in the Unicenter CA-QuickFetch Systems Programmer Guide. This chapter describes how you use Unicenter CA-QuickFetch to monitor fetch activity. This chapter provides background information that is useful later on.

■ For instructions on installing and tuning Unicenter CA-QuickFetch, see the chapter “Installing Unicenter CA-QuickFetch.” Detailed information about Unicenter CA-QuickFetch parameters and commands are in the Unicenter CA-QuickFetch Systems Programmer Guide.

■ For a detailed description of how Unicenter CA-QuickFetch reduces the DASD I/O associated with program loading, see the following chapters in the Unicenter CA-QuickFetch Systems Programmer Guide: “How Unicenter CA-QuickFetch Works” and “How Unicenter CA-QuickFetch Handles Updates for Libraries and Modules.”

■ For a listing of Unicenter CA-QuickFetch messages and codes, see the Unicenter CA-QuickFetch Message Guide.


qfg02pre.doc, printed on 10/21/2002, at 8:40 AM

Chapter

2 Preparing for Installation

This chapter describes information you need to know before you install Unicenter CA-QuickFetch.

Operating System Requirements Unicenter CA-QuickFetch runs on these operating systems:

■ OS/390—2.10, 2.9

■ z/OS—1.4, 1.3, 1.2, 1.1

■ z/OS.e—1.4, 1.3

For the latest information on supported operating system levels, check the Computer Associates support web site: esupport.ca.com.

Preparing for Installation 2–1

Contents of Installation Tape


Contents of Installation Tape Unicenter CA-QuickFetch is distributed on a standard labeled tape. The Unicenter CA-QuickFetch product consists of the five data sets shown in the following table:

Data Set Number

Data Set Name

Data Set Contents

1 QF.CNTL Installation JCL

2 QF.TGZ Manuals in Adobe PDF format

3 QF.SMPMCS SMP control statements for SMP/E installation of Unicenter CA-QuickFetch

4 CQZ2600.F1 Unicenter CA-QuickFetch SMP JCLIN

5 CQZ2600.F2 Unicenter CA-QuickFetch base load modules

n Used for future service pack maintenance

Preparing for Installation Before you install Unicenter CA-QuickFetch, make sure that your site has the following:

■ Sufficient storage space in the common service area (CSA).

Unicenter CA-QuickFetch requires approximately 12 KB of CSA for SVC intercept routines and other miscellaneous data areas. The amount of extended CSA (ECSA) required is dependent on several variables. You can calculate the approximate ECSA requirement using the following formula: (MLSIZE * 104 bytes) + ((Total # of LNKLST libraries from all “in use” LNKLST sets + NUMADDED + NUMINEL + # of INCLPRVT parameter statements) * 128 bytes) + 8K bytes


Licensing Requirements


Note: An “in use” LNKLST set is either the current set or an active set. A data set that appears in multiple LNKLST sets should be counted once when determining the total number of LNKLST libraries.

■ An authorized library for the load modules.

You must have an authorized library to hold the Unicenter CA-QuickFetch load modules. You may want to use an authorized library that you have allocated for other Computer Associates products or you may want to use one of your LNKLST libraries. To create a new library, add the data set name of the library and volume serial number to the IEAAPFxx list or the PROGxx member in SYS1.PARMLIB. The APF list can be updated dynamically using a SETPROG command. For more information about authorized libraries, see the appropriate IBM documentation.

■ The CAIRIM component of CA Common Services for z/OS and OS/390 (CCS for z/OS and OS/390) installed.

CAIRIM is required for product licensing.

Licensing Requirements Unicenter CA-QuickFetch uses CAIRIM, the Resource Initialization Manager for product license authorization. CAIRIM is a component of CCS for z/OS and OS/390. CAIRIM prepares your operating system environment for Computer Associates z/OS and OS/390 products and components and executes them.

You must use any version of CCS for z/OS and OS/390.

For further details about the features and associated utilities of CAIRIM, see the CCS for z/OS and OS/390 documentation.




Computer Associates LMP

Unicenter CA-QuickFetch requires Computer Associates License Management Program (LMP) to initialize correctly. Computer Associates LMP provides a standardized and automated approach to the tracking of licensed software. Computer Associates LMP is provided as an integral part of CAIRIM.

LMP Key Certificate

Examine the Computer Associates LMP Key Certificate you received with your Unicenter CA-QuickFetch installation or maintenance tape. Your certificate contains the following information:

Term Definition

Product Name

The trademarked or registered name of Unicenter CA-QuickFetch as licensed for the designated site and CPUs.

Product Code A two-character code that corresponds to the Unicenter CA-QuickFetch product.

Supplement The reference number of your license for the particular Unicenter CA-QuickFetch facility in the format: nnnnnn - nnn

This format differs slightly inside and outside North America, and in some cases may not be provided at all.

CPU ID The code that identifies the specific CPU for which installation of Unicenter CA-QuickFetch is valid.

Execution Key

An encrypted code required by Computer Associates LMP for Unicenter CA-QuickFetch installation. During installation, it is referred to as the LMP Code.




Term Definition

Expiration Date

The date your license for Unicenter CA-QuickFetch expires. It is in the format: ddmmmyy, as in 15JAN03.

Technical Contact

The name of the designated technical contact at your site responsible for the installation and maintenance of Unicenter CA-QuickFetch. This is the person to whom Computer Associates addresses all Computer Associates LMP correspondence.

MIS Director The name of the Director of MIS or the person who performs such a function at your site. If the title but not the name of the individual is indicated on the certificate, supply the actual name when correcting and verifying the certificate.

CPU Location The address of the building in which the CPU is installed.

Specifying the LMP Code

You must add the Computer Associates LMP Execution Key provided on the Key Certificate to the CAIRIM parameters to ensure proper initialization of Unicenter CA-QuickFetch. To define a Computer Associates LMP Execution Key to the CAIRIM parameters, modify member KEYS in CAI.PPOPTION.

The statement structure for member KEYS is: PROD(pp) DATE(ddmmmyy) CPU(tttt-mmmm/ssssss) LMPCODE(kkkkkkkkkkkkkkkk)




Parameter definitions are as follows: Parameter Definition pp The two-character Product Code. This

code agrees with the Product Code already in use by the CAIRIM initialization parameters for any earlier versions of Unicenter CA-QuickFetch (if applicable). This is required.

ddmmmyy The Computer Associates LMP licensing agreement Expiration Date.

tttt-mmmm The CPU Type and Model on which Computer Associates LMP is to run (for example, 9672-R46). If the CPU Type, Model, or both, require less than four characters, blank spaces are inserted for the unused characters. This is required.

ssssss The Serial Number of the CPU on which Computer Associates LMP is to run. This is required.

kkkkkkkkkkkkkkkk The Execution Key needed to run Computer Associates LMP. This Computer Associates LMP Execution Key is provided on the Key Certificate shipped with each Computer Associates LMP software solution.

Following is an example of a control statement for the Computer Associates LMP execution software parameter. The Product Code and Execution Key value will be different when you install Unicenter CA-QuickFetch at your site. PROD(IQ) DATE (27JUN02) CPU(9672-R46 /370623) LMPCODE(52H2K06130Z7RZD6)

For a full description of the procedure for defining the Computer Associates LMP Execution Key to the CAIRIM parameters, see the CCS for z/OS and OS/390 documentation.


qfg03ins.doc, printed on 10/21/2002, at 8:47 AM

Chapter

3 Installation

This chapter describes the step-by-step procedure for installing Unicenter CA-QuickFetch.

Previewing the Installation The following list summarizes the steps for installing Unicenter CA-QuickFetch:

1. Copy the QF.CNTL data set from the distribution tape.

2. Install the Unicenter CA-QuickFetch load modules.

3. Install the Unicenter CA-QuickFetch manuals.

4. Remove load modules from LLA Management (optional).

5. Install the Unicenter CA-QuickFetch AMASPZAP replacement program (optional).

6. Specify the necessary parameters.

7. Specify the LMP code for product licensing.

8. Install the QFMON ISPF panel (optional).

9. Tailor and copy the Unicenter CA-QuickFetch start-up procedure.

10. Set up the Advantage CA-Roscoe interface (optional).

Installation 3–1

Installing Unicenter CA-QuickFetch


Installing Unicenter CA-QuickFetch Complete the steps on the following pages to install Unicenter CA-QuickFetch on your operating system.

Step 1: Copy the QF.CNTL Library from the Tape

The installation tape contains a library named QF.CNTL. This library contains all of the JCL members that you will need to install Unicenter CA-QuickFetch. To copy QF.CNTL from the distribution tape, create and submit an IEBCOPY job like the one shown below: //name JOB job statement //STEP1 EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=A //SYSUT1 DD DSN=QF.CNTL,DISP=OLD, // UNIT=TAPE,VOL=SER=QFS260 //SYSUT2 DD DSN=QF.CNTL,DISP=(NEW,CATLG), // UNIT=uuuu,VOL=SER=xxxxxx, // DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160), // SPACE=(TRK,(6,2,10)) //SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(10,10)) //SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(10,10)) //SYSIN DD * COPY INDD=SYSUT1,OUTDD=SYSUT2 //

Once you have copied the QF.CNTL library, you should save its members for future Unicenter CA-QuickFetch maintenance.

Note: You can use the exact JCL that is shown above. However, you have to supply your own job statement on the first line of code, where the words job statement are shown in italics. You also have to supply the appropriate unit information for uuuu, and volume information for xxxxxx.

Before you proceed to the next step, examine the Readme file of the QF.CNTL data set. This Readme contains pending updates to Unicenter CA-QuickFetch documentation, installation tips, and so on.




Step 2: Install the Load Modules

Once you have copied the Unicenter CA-QuickFetch JCL members from the installation tape, install the appropriate load modules. The QF.CNTL library contains the JCL members that you should use to install the load modules.

The members that you have to edit are shown in the following table. The instructions for editing each member are contained in the JCL for that particular member.

If you are: Use these members:

A non-SMP/E installation ALLOCLIB, INSTLINK

An SMP/E installation ALLOCSMP, INSTSMPE

Submit the member that you edited. Make sure that you specify an authorized library for the Unicenter CA-QuickFetch load modules.

Note: If you use TSO and want to use the QFMON online interface, you may want to copy the QFMON member to a LNKLST library for easy access. Alternatively, you may want to use a CLIST.

Installing Maintenance Tapes

Periodically, you will receive maintenance tapes for Unicenter CA-QuickFetch. These tapes contain new Unicenter CA-QuickFetch modules with zaps applied to them. All tapes include any previous maintenance for Unicenter CA-QuickFetch.

If you are an SMP/E user, run the MAINSMPE job to install the modules on the installation tape. Otherwise, run the INSTLINK job to accomplish this. MAINSMPE and INSTLINK are members of the QF.CNTL library. Instructions for editing these jobs before running them are provided within the jobs.

Installation 3–3



Step 3: Install the Manuals

Unicenter CA-QuickFetch manuals are provided in the Adobe Portable Document Format (PDF).

You can view and print the PDF files using the Adobe Acrobat Reader software. The Acrobat Reader, available for most platforms, is freely and easily available from www.adobe.com. When downloading the Reader, check the “with Search” option, which lets you perform searches across multiple books if a search index (.pdx file) is provided.

Note: To obtain a hardcopy of the manuals, print the PDF files.

Installing and Printing the Manuals in PDF Format

The PDF files are packaged on the tape as a compressed archive file with a TGZ file extension. In addition to the PDF files, the .TGZ file contains a .PDX file and associated subdirectories for cross-book searching capabilities.

To install and print the PDF files, follow this procedure:

1. Use the PDFCOPY member found in QF.CNTL to unload the Unicenter CA-QuickFetch PDF data. The job copies the QF.TGZ file from the distribution tape.

2. Move the compressed archive file to a platform that supports the Adobe Acrobat Reader.

Use a binary file transfer program and download the compressed archive file to the target platform. Retain the .TGZ file extension when downloading.




3. Restore the PDF files and directory structure.

Uncompress the archive file on the target platform.

On Windows 9x: Use a Windows decompression utility.

Note: If using WinZip, use Version 7.0 or above.

On Windows NT and 2000: Use a decompression utility:

■ If using WinZip, use WinZip Version 7.0 or above.

■ If using gzip, enter the following at a command prompt: gzip -d archivename.tgz pax -r -f archivename.tar

Note: gzip is a non-standard utility freely and easily available from http://www.gnu.org/software/gzip/gzip.html. The pax (Portable Archive Interchange) utility is standard.

Save the restored files to the drive and directory of your choice.

On UNIX (including z/OS USS and Linux), use one of the following sets of commands: ■ gzip –d archivename.tgz

pax –r –f archivename.tar

Note: gzip is a non-standard utility freely and easily available from http://www.gnu.org/software/gzip/gzip.html. The pax (Portable Archive Interchange) utility is standard.

■ uncompress archivename.tar.z tar xvf archivename.tar

Move the files to the drive and directory of your choice.

4. Start Acrobat Reader to view or print the PDF files.

Installation 3–5



Step 4: Remove Load Modules from LLA Management (Optional)

Since LLA uses the Virtual Lookaside Facility (VLF) to manage frequently requested load modules in a data space, you should avoid using Library Lookaside (LLA) to manage any modules that Unicenter CA-QuickFetch is managing. Once LLA transfers a module to the VLF data space, Unicenter CA-QuickFetch does not receive fetch requests for that module.

You can use one of two methods to remove load modules from the management of LLA:

1. Remove the CLASS control statement that defines LLA to VLF from the COFVLFxx parmlib member. Look for the following CLASS control statement: CLASS NAME(CSVLLA) EMAJ(LLA)

VLF processes the COFVLFxx member at startup; therefore, this member resides in the parmlib that you specified on the //IEFPARM DD statement in the VLF startup procedure.

2. If LLA is the only z/OS component that uses VLF, you can disable VLF using the following command: P VLF

If other z/OS components (such as TSO/E for CLISTS) use VLF, you cannot disable VLF.

You can continue to use LLA to manage your library directories. If you do, you will see the following message shortly after startup: CSV231E LIBRARY LOOKASIDE IS NOT USING VLF. LLA CANNOT DEFINE ITS VLF CLASS. RC=xxxxxxxx,RS=xxxxxxxx.

You also can use the Unicenter CA-PMO product to manage your library directories and reduce the DASD I/O caused by directory searches. Unicenter CA-PMO automatically detects same-system and cross-system update activity and refreshes its in-storage directories. LLA requires you to issue the refresh operator command for an update to take effect.




If you use Unicenter CA-PMO with Unicenter CA-QuickFetch, the Unicenter CA-PMO cross-system component will communicate zap updates detected by the Unicenter CA-QuickFetch AMASPZAP replacement program to Unicenter CA-QuickFetch address spaces running on other systems in your complex.

For more information about using LLA or Unicenter CA-PMO to manage your library directories, see Using LLA to Manage Your Library Directories in the chapter “Tuning for Optimum System Performance” in the Unicenter CA-QuickFetch Systems Programmer Guide.

Step 5: Install the AMASPZAP Replacement Program (Optional)

Unicenter CA-QuickFetch provides an AMASPZAP replacement program that communicates zap updates to Unicenter CA-QuickFetch. This program links to the IBM AMASPZAP program to perform the zap update, then reads the control cards from the SYSIN ddname to determine which modules have been updated.

The AMASPZAP replacement program communicates the updates to all Unicenter CA-QuickFetch address spaces running on the system. If you run the Unicenter CA-PMO product, its cross-system component will communicate the zap updates to Unicenter CA-QuickFetch address spaces on all systems in your complex.

When Unicenter CA-QuickFetch determines that a module has been updated, it purges the old version of the module, and allows the new version to be loaded when it is needed.

The fact that the Unicenter CA-QuickFetch AMASPZAP replacement program is installed is invisible to users. Users that perform zap updates should continue to execute the AMASPZAP program, since Unicenter CA-QuickFetch names its version of the program AMASPZAP and you rename the IBM version.

Installation 3–7



To install the AMASPZAP replacement program, follow this procedure for a non SMP/E installation of Unicenter CA-QuickFetch:

1. Edit the JCL in member QFSSPZAP, follow the directions in the member, and then submit the job for execution.

2. Rename the IBM AMASPZAP program to the name you specified in the QFSSPZAP job.

If, at any time, you change the name of the IBM AMASPZAP program from the name you specified in the QFSSPZAP job, you must rerun the job with the new name.

3. Copy the QFSSPZAP load module from your Unicenter CA-QuickFetch load library to the same LNKLST library containing the IBM AMASPZAP program. Name the copied module AMASPZAP.

4. If you have aliases for the IBM AMASPZAP program, make them aliases for the Unicenter CA-QuickFetch replacement version by editing JCL member ALSSPZAP. Follow the directions in the member, and then submit the job for execution.

To install the AMASPZAP replacement program, follow this procedure for an SMP/E installation of Unicenter CA-QuickFetch:

1. Install Unicenter CA-QuickFetch into the LNKLIST if it is not currently a LNKLST library. The Unicenter CA-QuickFetch load library must be located after SYS1.MIGLIB, where the IBM AMASPZAP resides.

2. Receive and apply USERMOD UMQFZAP to the Unicenter CA-QuickFetch CSI. Member SMPUMOD1 in the QF.CNTL library may be used for this. This USERMOD adds the AMASPZAP alias for QFSSPZAP.

3. Receive and apply the USERMOD to rename AMASPZAP to the IBM CSI. The QF.CNTL member SMPUMOD2 contains a sample for this. Change the USERMOD name to fit your IBM CSI standards. If the operating system (OS) release level is upgraded, all that is required is to re-apply this USERMOD.




4. If you are not going to rename AMASPZAP to the default name of MVSSPZAP, you must apply the USERMOD contained in QF.CNTL member SMPUMOD3.

Note: You cannot put the Unicenter CA-QuickFetch AMASPZAP replacement program into LPA since it is not reentrant. You may leave the IBM AMASPZAP program in LPA; however, all aliases for AMASPZAP must be moved to the LNKLST library with the Unicenter CA-QuickFetch replacement program.

Step 6: Specify Parameters

The QFPARMS member of QF.CNTL, which you copied from the installation tape, contains a list of the Unicenter CA-QuickFetch parameters and their default values. You can edit the default values to meet the needs of your site.

As an alternative to using the QFPARMS member, you can specify your Unicenter CA-QuickFetch parameters in any member of your system PARMLIB, or in any sequential data set where LRECL has a value of 80 and the BLKSIZE has a value that is a multiple of 80. If you are going to use a different data set for your parameters, keep in mind that the Unicenter CA-QuickFetch start-up procedure (explained later in this chapter) assumes that your parameters are in the QFPARMS member of QF.CNTL.

Note: Your parameter data set, whether it is QFPARMS or another data set, can be shared by the same release of Unicenter CA-QuickFetch running on different systems.

The parameters that you need to specify during installation are explained on the next few pages. The names of parameters and their values are shown in uppercase. Terms shown in lower or mixed case represent variables for which you must specify a value.

Installation 3–9



For now, run only one Unicenter CA-QuickFetch address space. Also, use the supplied default values for the virtual storage available (MSLIMIT), the size ranges for the modules that Unicenter CA-QuickFetch manages (MODLIMIT), and the size of the fetch activity list (MLSIZE). You will change these values when you tune Unicenter CA-QuickFetch. For more information, see the Unicenter CA-QuickFetch Systems Programmer Guide.

Parameter Syntax

Follow the general rules, shown below, for creating parameter entries.

Each parameter entry consists of one or more parameters and an appropriate value for each. Parameter entries begin in column 1 and can continue through column 71.

Column Contents

1-4 One of the following:

■ A four-character SMF system ID indicates that this statement is valid for a particular system.

■ Blanks indicate that this statement applies to all systems.

■ An asterisk (*) in column 1 indicates that the statement is to be treated as a comment.

5 A blank.




Column Contents

6-71 One or more parameters and their values. For each line in the data set, start the parameter statements in column 6. Construct the parameter entry in the following way:

■ Separate each parameter and its value with an equals sign (=); that is, parameter=value.

■ If an entry contains more than one parameter, separate them from each other with a comma.

■ If a parameter has options that do not take a value, separate the option with a comma.

■ Do not use blank spaces. Unicenter CA-QuickFetch stops reading a statement when it encounters a blank space. Any information following the blank is treated as a comment.

■ Make sure that each line contains a complete parameter statement. Do not continue a parameter entry from one line to the next. If you have to start a parameter entry on a new line, always begin in column 6.

72 A blank. Each parameter statement must end with a blank space.

A few sample parameter statements are shown below. The first two statements apply to particular systems; the rest apply to all systems. CPU1 EXCPCOST=1.25 CPU2 EXCPCOST=1.50 INCLPRVT=CIC.PROD.LOADLIB MSLIMIT=750 ID=A INCLPRVT=PRODLIB.LOAD NUMINEL=30 ID=B INCLPRVT=RESLIB.LOAD NUMADDED=300 INCLAUTO=USRVK11.*

Installation 3–11



Parameters to Specify at Installation Time

For a detailed explanation of the Unicenter CA-QuickFetch parameters, see the chapter “Using Parameters” in the Unicenter CA-QuickFetch Systems Programmer Guide. There are seven different groups of parameters that you should specify when you install Unicenter CA-QuickFetch. You can specify the parameters in any order.

1. The first set of parameters is for EXCP costs. Specify the following parameters: EXCPCOST=monetary cost MONEYSYM=monetary symbol

2. By default, Unicenter CA-QuickFetch runs in an active mode. You will normally want to use this default: MODE=ACTIVE

However, if you want Unicenter CA-QuickFetch to run in a passive mode, specify the parameter like this: MODE=PASSIVE

3. The next set of parameters address the compatibility of Unicenter CA-QuickFetch with other products. If you use Advantage CA-Roscoe, JES3, or AllFusion™ CA-Panexec®, specify the appropriate values for one or more of the parameters listed below. For more information about compatibility among these products, as well as information about BrightStor™ CA-PDSMAN® PDS Library Management (BrightStor™ CA-PDSMAN®) and eTrust™ CA-ACF2® Security for z/OS and OS/390 (eTrust™ CA-ACF2®), see the chapter “Compatibility with Other Products” in the Unicenter CA-QuickFetch Systems Programmer Guide. PANEXEC=co-exist option USERSVC=SVC number ROSCOE=co-exist option JES3ALLC=allocation option

4. By default, Unicenter CA-QuickFetch automatically decides what private libraries to manage. If you wish, you can restrict the Unicenter CA-QuickFetch management of private libraries by specifying the INCLAUTO or EXCLAUTO parameters.




The EXCLAUTO parameter prohibits Unicenter CA-QuickFetch from managing certain libraries: EXCLAUTO=data set name,VOL=volser

The INCLAUTO parameter defines a set of private libraries that Unicenter CA-QuickFetch can manage automatically: INCLAUTO=data set name,VOL=volser

If you allow libraries with zap updates (including those done with SMP/E) to be eligible for management, make sure that you have installed the Unicenter CA-QuickFetch AMASPZAP replacement program (see Step 5: Install the AMASPZAP Replacement Program in this chapter). If such libraries are used on multiple systems in your complex, use the cross-system component of the Unicenter CA-PMO product to communicate these updates to Unicenter CA-QuickFetch address spaces on other systems.

Note: Specify either INCLAUTO or EXCLAUTO, not both of them.

5. If you have a severe paging problem on your system, you may want to prevent Unicenter CA-QuickFetch from automatically selecting any private libraries for management. If this is the case, specify: EXCLAUTO=*

If you specify EXCLAUTO=*, you must specify what private libraries Unicenter CA-QuickFetch will manage with INCLPRVT parameter statements: INCLPRVT=data set name

In the future, if you want Unicenter CA-QuickFetch to manage additional libraries, see the Unicenter CA-QuickFetch Q7 display. This display provides a list of ineligible libraries that you can make eligible for management using the INCLPRVT parameter or command.

6. If you used the INCLPRVT parameter to specify private libraries that you want Unicenter CA-QuickFetch to manage, you can select for management, exclude from management, or both, particular members of those libraries. Use the following parameters: SMEM=(selected members)

Installation 3–13



EMEM=(excluded members)

7. Specify a user SVC number where Unicenter CA-QuickFetch can place its user SVC routine if any of the following are true:

— Unicenter CA-QuickFetch is coexisting with AllFusion CA-Panexec or eTrust CA-ACF2.

— You have installed the Unicenter CA-QuickFetch AMASPZAP replacement program.

— You have Extended Debugging Controller® (XDC/SE®, Copyright © 2000, Cole Software, LLC) running on your system.

Specify the parameter like this: USERSVC=SVC number

Note: Specify a user SVC if you are running multiple Unicenter CA-QuickFetch address spaces, but run only one address space at this point.

Step 7: License Unicenter CA-QuickFetch For Your Site

Authorization for use of Unicenter CA-QuickFetch is performed through the Computer Associates License Management Program (LMP) facility of the CAIRIM component. CAIRIM is installed as a part of CCS for z/OS and OS/390.

You must install CAIRIM, activate LMP, and code LMP statements. For more information, see Specifying the LMP Code in the chapter “Preparing for Installation” and the CCS for z/OS and OS/390 documentation.

Step 8: Install the QFMON ISPF Panel

To use the QFMON split-screen mode under ISPF, copy member QFSPANEL from the QF.CNTL data set to one of the panel libraries concatenated to your ISPPLIB ddname.




Step 9: Edit and Copy the Startup Procedure

Follow these steps to edit and copy the Unicenter CA-QuickFetch startup procedure:

1. Edit the startup procedure in the PROCQF member of QF.CNTL. Follow the instructions within that member. A sample version of the PROCQF member is shown below: //QFETCH PROC

//*

//* QF.CNTL(PROCQF)

//* SAMPLE QUICK-FETCH STARTUP JCL.

//*

//* BEFORE USING -

//* (1) CALCULATE THE REGION SIZE REQUIRED FOR QUICK-FETCH

//* VIRTUAL STORAGE NEEDED = MSLIMIT + (20% MSLIMIT) + 250K

//* SUPPLY THIS VIRTUAL STORAGE VALUE FOR THE REGION

//* SIZE ON THE QFETCH EXEC STATEMENT.

//* (2) SUPPLY THE QUICK-FETCH LOAD MODULE LIBRARY

//* DSN FOR THE STEPLIB DD STATEMENT.

//* (3) TAILOR THE QFPARM DD TO SUIT YOUR NEEDS.

//* (SEE THE QUICK-FETCH SYSTEMS PROGRAMMER GUIDE).

//* (4) COPY THIS PROC TO THE APPROPRIATE PROCLIB

//* AS NEWNAME QFETCH.

//*

//QFETCH EXEC PGM=QFETCH,REGION=NNNNK,TIME=1440

//STEPLIB DD DSN=CAI.QF.LOADLIB,DISP=SHR

//QFSPARM DD DSN=QF.CNTL(QFPARMS),DISP=SHR

//SYSUDUMP DD SYSOUT=A

2. After editing the PROCQF member, copy it to the PROCLIB library of your system. Use the name QFETCH for simplicity. However, you can select any valid procedure name.

3. Once you have copied the startup procedure, start and tune Unicenter CA-QuickFetch. For details, see the Unicenter CA-QuickFetch Systems Programmer Guide.

Step 10: Set Up the Advantage CA-Roscoe Interface (Optional)

To allow Advantage CA-Roscoe users to use QFMON, follow the instructions in the QF.CNTL member INSTROSC.

Installation 3–15

Test Starting Unicenter CA-QuickFetch


Test Starting Unicenter CA-QuickFetch After you have completed all of the installation steps, start Unicenter CA-QuickFetch to make sure that it really operates the way you expect it to. Here are instructions for starting Unicenter CA-QuickFetch and making sure that it is working properly:

1. Start Unicenter CA-QuickFetch with the following command: S QFETCH

When Unicenter CA-QuickFetch starts up, you will see the following message: QFS001I UNICENTER CA-QUICK-FETCH RUNTIME PERFORMANCE 2.6 SERVICE PACK nn ACTIVE

Repeat the S QFETCH command on all systems that will run Unicenter CA-QuickFetch.

2. Check the status of Unicenter CA-QuickFetch (whether it is active or disabled) by entering the following command: F QFETCH,STAT

Unicenter CA-QuickFetch responds with the following message if it is active: QFS001I UNICENTER CA-QUICK-FETCH RUNTIME PERFORMANCE 2.6 SERVICE PACK nn ACTIVE

Starting Unicenter CA-QuickFetch Automatically at IPL Time

You can have Unicenter CA-QuickFetch start up automatically at IPL time. To do this, add this command to the IPL commands in your SYS1.PARMLIB(COMMNDxx): S QFETCH

The command will take effect during your next IPL.


Going on From Here


Going on From Here If you completed the instructions in this chapter, you have installed and test-started Unicenter CA-QuickFetch.

Take time to become familiar with Unicenter CA-QuickFetch and the QFMON displays. See the chapter “Monitoring Fetch Activity with QFMON” in the Unicenter CA-QuickFetch Systems Programmer Guide. If you have allowed even a few of your critical libraries to be eligible for Unicenter CA-QuickFetch management, you should see a significant improvement in system performance. To ensure that Unicenter CA-QuickFetch is optimizing program loading on your system, however, you will need to make some tuning adjustments. Make these adjustments as soon as possible after you have installed Unicenter CA-QuickFetch.

After you are familiar with Unicenter CA-QuickFetch, continue on to the chapter “Tuning for Optimum System Performance” in the Unicenter CA-QuickFetch Systems Programmer Guide. This chapter provides the information that you need to tune Unicenter CA-QuickFetch to achieve optimum system performance. You will make adjustments such as selecting additional libraries and modules for Unicenter CA-QuickFetch management, determining the appropriate size for your fetch activity list, and providing Unicenter CA-QuickFetch with enough virtual storage.

In addition, that chapter also addresses special tuning concerns such as handling competing applications, protecting and excluding modules, minimizing paging problems, running multiple address spaces, and using LLA to manage your library directories while Unicenter CA-QuickFetch is managing the modules.

Installation 3–17

qfgidx.doc, printed on 10/22/2002, at 12:49 PM

Index

A

Acrobat Reader, 3-4

address spaces for Unicenter CA-QuickFetch, 1-10 running multiple, 1-8, 1-10

Advantage CA-Roscoe interface, 3-15

AllFusion CA-Panexec, 3-12

ALLOCLIB module, 3-3

ALLOCSMP module, 3-3

AMASPZAP replacement program, 1-8, 3-7

authorized libraries, 2-3

automatic private library management, 1-13

automatic update detection, 1-9

B

BLDL directory search, 1-6 what is, 1-6

Build List See BLDL, 1-6

C

CA Common Services for z/OS and OS/390, 2-3

CA LMP, 2-4

CAIRIM, 2-3

Class control statements EMAJ(LLA) statement, 3-6 NAME(CSVLLA) statement, 3-6

CLASS control statements, 3-6

clone libraries managing with Unicenter CA-QuickFetch, 1-14 using to reduce DASD I/O, 1-2 what are, 1-14

commands for Unicenter CA-QuickFetch start command, 3-16

CQZ2600.F1 data set, 2-2

CQZ2600.F2 data set, 2-2

CSA requirements, 2-2

CSA, storage needed for installation, 2-2

Index–1


D

disabling VLF, 3-6

dynamic library management including and excluding libraries, 1-13 what is, 1-13

E

ECSA requirements, 2-2

EMAJ(LLA) statement, 3-6

EMEM parameter, 3-14

excluded modules purpose of, 1-13 what are, 1-13

EXCPCOST parameter, 3-12

F

Fetch Activity List deleting modules from, 1-11 for each address space, 1-11 primary function of, 1-11 sorting, 1-11 statistics, 1-11

fetch count purpose of, 1-11

I

IEBCOPY job for installation, 3-2

immediate page-in feature how it works, 1-14 purpose of, 1-14 what is, 1-14

installation, 3-1 contents of the installation tape, 2-2 gathering information for, 2-2 load modules, 3-3 of manuals, 3-4 preparing for, 2-1 previewing the processes, 3-1 QFMON ISPF panel, 3-14 sample IEBCOPY job, 3-2 starting Unicenter CA-QuickFetch, 3-16 start-up procedure, 3-15 testing the code, 3-16

INSTLINK module, 3-3

INSTROSC member, 3-15

INSTSMPE module, 3-3

J

JES3ALLC parameter, 3-12

Job Pack Area (JPA) problems of, 1-3 storing modules in, 1-3 using to reduce DASD I/O, 1-3

JOB/STEP/TASK libraries, 1-2

L

Link Pack Area (LPA) increasing the size of, 1-3 problems of, 1-3 using to reduce DASD I/O, 1-3

Linux, 3-5

Index–2 Getting Started


LLA EMAJ(LLA) statement, 3-6 NAME(CSVLLA) statement, 3-6 removing load modules from management, 3-6

LMP code, 2-4, 2-5

LMP Key Certificate, 2-4

LNKLST libraries, 1-6

load modules for Unicenter CA-QuickFetch, 3-3

M

MAINSMPE member, 3-3

maintenance tapes contents of, 3-3 installing, 3-3

manuals, installing, 3-4

MODE parameter, 3-12

monitoring the virtual storage area, 1-14

multiple address spaces using for competing applications, 1-10 when to run, 1-10

N

NAME(CSVLLA) statement, 3-6

O

OS/390, 2-1

P

PANEXEC parameter, 3-12

parameter syntax, 3-10

parameters creating a data set for, 3-9 data set requirements, 3-9 EMEM, 3-14 EXCPCOST, 3-12 JES3ALLC, 3-12 MODE, 3-12 MONEYSYM, 3-12 PANEXEC, 3-12 QFPARMS member, 3-9 ROSCOE, 3-12 SMEM, 3-13 specifying during installation, 3-9 syntax for, 3-10 USERSVC, 3-12

PDFCOPY job, 3-4

private libraries contents of, 1-6 LNKLST libraries as, 1-6 what are, 1-6

PROCQF member, 3-15

program fetch, 1-6

program loading DASD I/O associated with, 1-1 with Unicenter CA-QuickFetch, 1-5 without Unicenter CA-QuickFetch, 1-4

Program Management how it works, 1-2 load failures, 1-2 overview, 1-1 problems with, 1-3 program fetch service, 1-6 resolving fetch requests, 1-2

protected modules purpose of, 1-13 what are, 1-13

Index–3


Q

QF.CNTL data set, 2-2

QF.SMPMCS data set, 2-2

QF.TGZ data set, 2-2

QFMON purpose of, 1-15 what is, 1-15

QFPARMS member, 3-9

QFSPANEL member, 3-14

R

removing modules from LLA management, 3-6

ROSCOE parameter, 3-12

S

SMEM parameter, 3-13

start command, 3-16

starting Unicenter CA-QuickFetch automatically at IPL, 3-16 to test code, 3-16

start-up procedure, 3-15

T

terminology, 1-6

test Unicenter CA-QuickFetch code, 3-16

TGZ file extension, 3-4

TTR how Unicenter CA-QuickFetch uses, 1-12 what is, 1-12

U

Unicenter CA-PMO managing library directories with, 1-2

updates automatic detection, 1-12 how Unicenter CA-QuickFetch detects, 1-12

USERSVC parameter, 3-12

V

Virtual Lookaside Facility(VLF) See VLF, 1-1

virtual storage area internal monitoring of, 1-14

virtual-to-virtual transfer, 1-5

VLF data space for managing modules, 3-6 disabling, 3-6 using with LLA, 3-6

Z

z/OS, 2-1

Index–4 Getting Started

qfg00til.doc, printed on 10/16/2002, at 8:54 am unicenter ... · qfg00til.doc, printed on...

Documents