CA Common Services for z/os

Transcription

1 CA Common Services for z/os Getting Started r11 SP7

2 This documentation (the Documentation ) and related computer software program (the Software ) (hereinafter collectively referred to as the Product ) is for the end user s informational purposes only and is subject to change or withdrawal by CA at any time. This Product may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Product 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 the Documentation for their own internal use, and may make one copy of the Software as reasonably required for back-up and disaster recovery purposes, 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 provisions of the license for the Software are permitted to have access to such copies. The right to print copies of the Documentation and to make a copy of the Software 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 certify in writing to CA that all copies and partial copies of the Product have been returned to CA or destroyed. EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS PRODUCT 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 PRODUCT, 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 this Product and any product referenced in the Documentation is governed by the end user s applicable license agreement. The manufacturer of this Product is CA. This Product is provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (c)(1)(ii), as applicable, or their successors. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Copyright 2006 CA. All rights reserved.

3 Contents Chapter 1: Introduction How the CCS for z/os Solution Works End-to-End Management Business Process Views Comprehensive Unicenter Administration Multilayered Architecture Management Services Event Management Calendars Agent Technology Services Provided by CCS for z/os How the Installation Process Works Getting Help Chapter 2: Planning the Installation Target Libraries Comprehensive View of Storage Requirements Installation Requirements for Each CCS Component CAIRIM/CAISSF CAIENF CAIENF Installation Considerations for etrust CA-ACF2 Users CAIENF Utilities CAIENF/CICS CAIENF/DB CAIENF/CICS SPAWN CAIENF/USS CAICCI CAIVPE CAIVPE Installation Considerations CA-MFLINK Earl Service Easytrieve Service Requirements SRAM Service CA-C Runtime ViewPoint CA PROFILE Contents iii

4 CA-Datacom/TR SVC (Supervisor Call) Event Management Agent Technology Prepare to Install Agent Technology CA-L-Serv Prior Installations of CA-L-Serv XCF Communications Considerations z/os Requirements Virtual Storage Requirements CA-L-Serv SQL Dictionary CA-GSS (System Interfaces) CA-GSS Memory Requirements System Level Memory Primary CA-GSS Memory ISERVE Memory Resource Consumption System Security User IDs CA-GSS User ID IMOD User IDs How CA-GSS Chooses a User ID for an IMOD CA-XPS CAISDI CAISDI Installation Requirements CAECIS Component FMIDs Chapter 3: Installing the Product How You Install CCS for z/os Step 1. Download the Sample JCL Library Step 2. Complete the Installation Worksheet Step 3. Modify the SAMPJCL Member JOBCARD Step 4. Modify the SAMPJCL Member CCSVARS Step 5. Download the PDF Files Step 6. Allocate the Target and Distribution Libraries Step 7. Allocate Private SMP/E Data Sets Step 8. Set Up the Environment to Use SMP DDDEFs Step 9. Set Up the Environment for Event Management Step 10. Set Up the Environment for Agent Technology Step 11. Agent Technology Downloads iv Getting Started

5 Step 12. Event Management Downloads Step 13. Receive CCS for z/os Step 14. Copy Earl Service Options Source Member EARLOPT Step 15. Create a User ID for Agent Technology Step 16. Allocate Agent Technology HFSs Step 17. Set Up Agent Technology DDDEFs Step 18. Run Event Management UCLIN Step 19. Apply CCS for z/os Step 20. Expand the Agent Technology Tarfile Step 21. Set the Userid Mode Bit for Agent Technology Step 22. APF Authorize the CAILIB and CAIPDSE Data Sets Step 23. Define or Upgrade the CAIENF Database Step 24. Create the Links for Event Management Step 25. Complete the Steps Required for Event Management Step 26. Establish Site Defaults for CA-C Runtime Step 27. Allocate the ViewPoint Profile Step 28. Link Edit the Easytrieve IDMS Interface Module Step 29. Allocate, Compile and Copy CA-GSS Step 30. ACCEPT CCS for z/os Chapter 4: Post-Installation Tasks List of Tasks Run the Event Management Install Script How You Complete Repository Tasks Adjust the Repository Tasks Run the CAIRIM proc How You Configure Event Management GUI Tasks Configure the UNIX System Services for Event Management Configure the Web Server Install Java Security Definitions for Event Management Initialize the Java Server How You Configure Optional Event Management Tasks Store and Forward Limiting SAF Eligibility Create an SAF Configuration File Change the SAF Interval Enable Store and Forward for Another Task Set Up the Berkeley syslog daemon Sample syslogd Configuration File Reroute Messages to a Remote Host Contents v

6 Enable catrapd Initialize the Event Management Servers Install the OPSMVS Exit Customize emstart and emstop Scripts Install Event Management on Multiple Systems Start Repository Address Space and JAVA GUI Agent Technology Tasks Tailor the Profile, Script, and Configuration Files in the HFS System Edit the profile file: /agent/agentworks.profile Execute an Agent Technology Utility Edit the script file: /agent/services/tools/install_mibs Edit the config file: /agent/services/config/aws_orb/quick.cfg Edit the config file: /agent/services/config/aws_sadmin/aws_sadmin.cfg Edit the config file: /agent/services/config/aws_snmp/aws_snmp.cfg Tailor the config file: /agent/services/config/awservices/awservices.cfg Tailor the ENVFILE from the SRCLIB Verify the TCP/IP Network Configuration Build the aws_sadmin Store Files Agent Security Install Agent Technology on Multiple Systems Copy Your Agent Technology Installation Agent Configuration Set Verification Load Library Considerations Start Agent Technology Build and Run the Example Agent (EXAGENT) Compile and Link Online (USS) Compile and Link in Batch Mode (z/os) CAIRIM Tasks CAIRIM Initialization Parameters Customize CAISSF for RACF or RACF-Compatible Products CAS9SAFC/CAS9RACL for CICS 3.x and up Install CAS9RACL Modify and Submit the CAS9CSSF Sample JCL Modify RACF or the RACF-Compatible Product Place the CAISSF Routines in the Common Service Area (CSA) APF Authorize the CAISSF Load Library Start CAIRIM CAIENF Tasks Customize the CAIENF Procedure Symbolics Start CAIENF Customize the ENFSNMPM Procedure Perform the CAIENF/USS Tasks vi Getting Started

7 CAICCI Tasks Configure and Start CAICCI Additional Post-Installation Tasks for CAICCI r Utilize SSL Links Download CCIPCSSL How You Copy CCISSL How You Copy CCISSLGW How You Copy CCIRTARM How You Copy CCIP Start CCISSL Start and Stop CCISSLGW Create and Populate the Key Database Load CAICCI on the Client Platform Download with TCP/IP Download with LU Complete the CAIVPE Tasks Earl Service Task CAECIS Tasks Utilize CAECIS CAICRS References Implement the CAISDI Tasks Chapter 5: Customizing the CA Global SubSystem How the Post-Installation Process Works for CA-GSS Define Subsystem IDs Copy CA-GSS Procs to System PROCLIB Prepare the Started Task PROC Install the IMOD Editor IMOD Editor Problems Install the CA-GSS/ISERVE Operator Control Panel Test the Installation Recompile Under TSO Initialization Parameters Customize CA-GSS for Unicenter CA-Insight for DB Unicenter CA-Jobtrac Customize CA-GSS for Unicenter CA-MIM Customize CA-GSS for Unicenter CA-OPS/MVS Unicenter CA-SYSVIEW Customize CA-GSS for Unicenter CA-View Customize CA-GSS for DB Customize CA-GSS for IDCAMS Contents vii

8 Optional Features GoalNet Defining GoalNet GOALNET Parameter PPOPTION Member: GOALNET Sample LOGMODE Table SAMPJCL Member: YS28MTAB Define GoalNet to VTAM SAMPJCL Member: YS28VTAM ILOG Files Logon Facility Security Define the Logon Facility Upgrading ISETs Chapter 6: Starting CA-L-Serv Update External Security for CA-L-Serv Who Needs to Update? How the Update Tasks are accomplished Usage Notes Implement Security with etrust CA-Top Secret Implement Security with etrust CA-ACF Implement Security with RACF Define CA-L-Serv to VTAM How You Tailor Startup Parameters How You Update the Message Table Copy and Customize the Startup Procedure How You Start CA-L-Serv Verify the Communications Server Installation Communications Server IVP is Not Running Successfully Verify the File Server Installation Chapter 7: Applying Maintenance to CCS for z/os Apply the Maintenance Steps Appendix A: Installation Checklists Checklist for CAIRIM... A 1 Checklist for CAISSF... A 2 viii Getting Started

9 Checklist for CAIENF... A 3 Checklist for CAIENF/CICS... A 4 Checklist for CAIENF/CICS SPAWN... A 5 Checklist for CAIENF/DB2... A 6 Checklist for CAIENF Utilities... A 7 Checklist for CAICCI... A 8 Checklist for CAIVPE... A 8 Checklist for CA-MFLINK... A 9 Checklist for Earl Service... A 9 Checklist for Easytrieve Service... A 10 Checklist for SRAM Service... A 10 Checklist for CA-C Runtime... A 11 Checklist for ViewPoint... A 11 Checklist for Event Management... A 12 Checklist for Agent Technology... A 13 Checklist for CA-L-Serv... A 14 Checklist for CA-GSS... A 14 Checklist for CA-XPS... A 15 Checklist for CAICRS... A 16 Checklist for CAISDI... A 17 Checklist for CAECIS... A 17 Appendix B: Installation and Maintenance Worksheet Installation and Maintenance Worksheet... B 1 Appendix C: Install and Maintain CAICCI r1.1 Perform CAICCI r1.1 Post-Install Tasks... C 2 Review CAICCI r1.1 Maintenance Considerations... C 3 How You Configure the CCITCP and CCITCPGW Started Tasks... C 3 CAICCI on the Client Platform... C 4 Download with TCP/IP... C 4 Download with LU 2... C 5 Index Contents ix

10

11 Chapter 1: Introduction CA Common Services (CCS) is an open, cross-platform enterprise management infrastructure available on over thirty operating system platforms, including z/os. It provides common services and enabling technology for CA IT management solutions. This guide provides you with the necessary information to successfully install, customize, and maintain CCS for z/os. To aid you with the installation, installation checklists and an installation worksheet have been provided in the appendixes. How the CCS for z/os Solution Works CCS for z/os includes distributed services common to all CCS implementations and solutions specific to z/os. It provides a common GUI and event services to create multiple, unified views of resources. This z/os-hosted enterprise management architecture, similar to existing CCS on Windows and UNIX platforms, expands the choice of what and where to manage. It also contains all the essential components and functionality to enable integrated management of z/os. CCS for z/os includes support for applications based on z/os UNIX System Services. CCS for z/os also furnishes the Agent Technology infrastructure to run z/os Agents. CCS for z/os lets you do the following: Integrate your mainframe with other distributed platforms. Manage emerging z/os workloads such as Web servers, Java applications, and UNIX applications. Use existing CA z/os management solutions to create events that can be routed to other enterprise platforms where such events can create desired business outcomes. Achieve enterprise-wide, automated, high-level monitoring and management of critical resources using sophisticated manager/agent technology, together with CA products. Chapter 1: Introduction 1 1

12 End-to-End Management End-to-End Management With CCS for z/os, you can integrate z/os solutions with management solutions on other platforms to achieve enterprise-wide end-to-end management from any remote location and from a single console. The software technology of CCS for z/os lets you run the appropriate hardware platforms and software applications for each aspect of your business and deploy them across many machines while enabling you to manage them as an integrated whole. Business Process Views Business Process Views are user-defined groups of managed objects that represent specific business processes, resource features, geographical locations, organizational structures, or applications. For example, you can create a Business Process View that displays only objects related to the accounting processing and another for payroll. The manufacturing department might have a view showing the servers, networking devices, and segments in various factories and warehouses. CCS for z/os provides the architecture for z/os systems to participate in these views. Comprehensive Unicenter Administration Using CCS for z/os you can have Unicenter components installed on other platforms react to events on the mainframe and conversely have the mainframe react to components on other platforms. Event Management lets you: Monitor and administer different kinds of asynchronous events including SNMP Traps, application events, and system events. See the z/os Event Management console from other Unicenter platforms. See other platform Unicenter Event Management consoles from the z/os Event Management Java GUI. 1 2 Getting Started

13 Multilayered Architecture Multilayered Architecture CCS for z/os is composed of a management layer and a z/os software services layer. The management layer provides a Web-based real-world graphical interface and monitoring of application and system events. The z/os services layer includes a suite of industry standard integration and distributed processing services to unify software applications. Management Services Management services enable integrated administration of all IT resources in your enterprise, including network devices, databases, business applications for desktop systems and mainframes. The various components are described in the following sections. Event Management Event Management is a collection of management components that employ a single, easy-to-use graphical user interface (GUI) to monitor and administer different kinds of asynchronous events including SNMP traps, application events, and system events. Event Management makes it easy for you to collect related messages network-wide for display at a single location or to send them to multiple locations, as needed. The GUI included with Event Management on z/os provides access to the Event Management Console, the management of Message Action records, and the management of calendars. CCS for z/os Event Management augments z/os automation solutions, such as Unicenter CA-OPS/MVS, by providing built-in access to a wide range of distributed events and by allowing actions to be triggered on any CCS equipped platform. CCS for z/os provides event correlation and event processing and is fully integrated with CCS event management facilities on other platforms. CCS for z/os also has several SDK functions, including command line and batch interfaces. You can define specific Event Management policy to do the following: Respond to messages Suppress messages Issue CCS for z/os commands Start other programs or scripts Send information to a network management or automation application such as Unicenter CA-OPS/MVS Forward messages to other managed platforms Issue commands to be executed on other platforms Chapter 1: Introduction 1 3

14 Multilayered Architecture Interpret the results of any action to decide whether additional actions are warranted Event Management can be configured to process messages on individual servers and redirect them to a central server or other servers and, by extension, their consoles. Event Management makes it easy to collect related messages network-wide for display at a single location or to send to multiple locations, as needed. The Event Console Log GUI lets you monitor system events as they occur. All running programs and user processes can direct inquiries and informative messages to this facility. It provides a complete view of processes across the network. Calendars Calendars make it possible to determine a course of action based on when an event occurs. The event not only meets the general criteria; it also meets the date, day, and time criteria established through calendar profiles. The primary function of a calendar can be identified in a naming scheme. CCS for z/os provides facilities to define as many calendars as you require to meet your needs and to store them for easy reference. Note: The use of calendars with Event Management is optional. Agent Technology The Agent Technology infrastructure enables the use of agents for the z/os environment. The agents report to agent managers, which monitor and report the status of your resources and applications. It supports existing prepackaged z/os agents such as the z/os System Agent, CA-IDMS Agent, CA-Datacom Agent, DB2 Agent, and CICS Agent, as well as other agents created to CCS specifications. Agent Technology supports a wide range of platforms and is deployable in traditional client/server, internet, and intranet environments. This versatility enables enterprise-wide monitoring and management of z/os elements and further enhances the ability of z/os environments to participate in a true heterogeneous network. 1 4 Getting Started

15 Services Provided by CCS for z/os Services Provided by CCS for z/os The services provided by CCS for z/os are described in the following list: CAIRIM Prepares your operating system environment for all of your CA applications and starts them. It is the common driver for a collection of dynamic initialization routines that eliminate the need for user SVCs, SMF exits, subsystems, and other installation requirements commonly encountered when installing systems applications. CAICCI Provides CA enterprise applications with a common communications software layer that insulates the applications from dealing with protocol specifics, error recovery, and system connection establishment. CAIENF (Base, CICS, and DB2) Provides comprehensive operating system interfacing services to any of the CA z/os applications, exploiting technologies such as relational database architectures, for the benefit of the entire product line. The level of integration is improved by enabling operating systems and CA software-generated event information to be driven through a standard interface, simplifying multiple product-to-product interfaces and associated maintenance that would otherwise be necessary. CAIENF/CICS SPAWN Provides a communications facility that enables CA applications to start CICS units of work from outside the CICS region. This facility provides a layer that isolates the application software from CICS release dependencies. CAIENF Utilities Provides a collection of facilities that lets you use the services provided by CAIENF. Facilities include an online database query editor, a real-time CAIENF event monitor, and a command for performing CAIENF LISTEN and EXTRACT functions. Note: For more information about these utilities, see the Reference Guide. Management of z/os UNIX System Services (CAIENF/USS) Provides extensions to CCS for z/os that encapsulate and integrate the management of UNIX System Services applications on z/os. This service enables management applications to process system events occurring in the z/os UNIX System Services subsystem. Chapter 1: Introduction 1 5

16 Services Provided by CCS for z/os CAISDI Provides a set of services that opens Unicenter Service Desk requests from the z/os environment. The requests can be opened directly by CA products or they can be opened on their behalf, depending on the requirements of each specific product using the interface. There are three main components involved in this interface (CAISDI/soap, med, and els). Depending on each individual CA product using CAISDI, one or more of these components will be required. We recommend that you install all three components. In the configuration steps, you may choose to configure only the components you currently need. CAIVPE Provides an inter-product facility used by other CA applications running under Advantage CA-Roscoe, TSO, or CICS. It contains monitor-specific code and lets CA applications run independent of the environment. CAISSF Provides an external security mechanism for controlling and monitoring access to all system and application resource processes. CAISSF is already well integrated into many CA enterprise applications and is also used by other CCS for z/os services. It provides security services for user signon, resource access control, process use control, and recording and monitoring of violation activity. CA LMP Provides a standardized and automated approach to the tracking of licensed software, and is an integral part of CAIRIM. Earl Service Provides a user-friendly report-definition facility with the power of a comprehensive programming system. Earl Service allows you to modify and print the contents and layout of a predefined CA application report using English-like statements. Easytrieve Service Provides a powerful productivity language for both business and information processing professionals containing easy-to-use information retrieval, sophisticated report writing, and comprehensive application development capabilities. The Easytrieve Service is a limited version of the generally available, full-featured product, which lets you modify the contents of an Easytrieve application that is provided with another CA product. If you have Unicenter CA-Easytrieve already installed at your site, you do not need to install the Easytrieve Service from CCS. 1 6 Getting Started

17 Services Provided by CCS for z/os SRAM Service Allows the activation of several sorts concurrently, thereby simplifying the data and logic flow. The incoming data to the sort can be manipulated as desired by the user program in a high-level language without the need for special exit routines. CA-C Runtime Provides a C run time facility that insulates programs from system and release dependencies. CA-L-Serv Provides the CA-L-Serv services that are used by CA products including AllFusion Endevor, Unicenter CA-Bundl, Unicenter CA-Balancing, Unicenter CA-TPX, and Unicenter CA-MIC Message Sharing. These services include centralized logging and messaging facilities, VSAM file management, cross-system communications, and SQL table management. CA-GSS Provides a simplified communication interface that lets various CA products communicate easily, seamlessly, and reliably, allowing quick access to information from various sources. CA-GSS provides connectivity by using a collection of one or more REXX subroutines that are edited, compiled, and executed as a single program. CA-XPS Enables cross-platform scheduling for CA products including Unicenter CA-7, Unicenter CA-Scheduler, and Unicenter CA-Jobtrac. CA-Examine Common Inventory Service Provides a tool for CA Technical Support to collect and report on installed instances of CA products at a particular customer site. This service is useful for troubleshooting problems. ViewPoint Provides an SQL engine for PC based workstation products. Workstation products can use ViewPoint to query z/os product databases without knowledge of the underlying database structure. Chapter 1: Introduction 1 7

18 How the Installation Process Works How the Installation Process Works The recommended approach for installing CCS for z/os follows: Determine the hardware and software requirements. Install CA Common Services for z/os. Carry out the appropriate post-installation tasks for the components you installed. Customize your configuration to meet your needs. Define your Enterprise Management policies. A policy represents a set of rules that outline how and when Enterprise Management tasks are to be performed. Use the CCS for z/os GUI, commands, and configuration files to define your policies. Getting Help For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Technical Support at Getting Started

19 Chapter 2: Planning the Installation This chapter helps you plan your CCS installation by providing the target libraries, and storage and installation requirements. Target Libraries As part of the SMP/E process for CCS for z/os, the following CAI target libraries are updated with specific routines. You can determine the space allocation for each target library by reviewing the system requirements for each service you are installing. Note: For these descriptions, the default names for the CA libraries are used. CAI.CAILIB The CAI Common Authorized Load library contains service-related executable modules. The CAI.CAILIB cannot be a PDSE. No data set in concatenation with CAI.CAILIB can be a PDSE. CAI.PPOPTION The CAI Product Options library contains sample parm members for CCS for z/os. CAI.CAIPROC The CAI Procedure library contains sample procedures for invocation of CCS for z/os and its related utilities. CAI.SAMPJCL The SAMPJCL library contains the sample JCL necessary to install and maintain CCS for z/os. CAI.CAIPDSE The PDSE library contains load modules link edited in program format 3. CAI.CAISRC The Source library contains the source programs used for executing service-related utilities under TSO. CAI.CAIMAC The Macro library contains the macros used in compiling service-related programs. Chapter 2: Planning the Installation 2 1

20 Target Libraries CAI.CAICICS The CICS Load library contains service-related CICS executable modules. CAI.CAICLIB The CLIST library contains service-related CLISTs. CAI.CAIISPM The ISPF Message library contains service-related ISPF messages. CAI.CAIISPP The ISPF Panel library contains service-related ISPF panels. CAI.CAISYSI The CA-GSS system IMOD library contains source for internal IMODs used by CA-GSS. CAI.CAISAMPI The CA-GSS Sample IMOD library contains sample REXX source. CAI.CAIEVENT The CAISDI/els Event Library. CAI.CAEDIT The CAIENF Utilities Editor library. CAI.CASCRN The CAIENF Utilities Panel library. CAI.VPOINT.DIALOG The ViewPoint Dialog library contains service-related ViewPoint dialogs. CAI.VPOINT.HELP The ViewPoint Help library contains service-related ViewPoint help. CAI.VPOINT.CHOICES The ViewPoint Choices library contains service-related ViewPoint lists. CAI.VPOINT.MESSAGE The ViewPoint Message library contains service-related ViewPoint messages. CAI.VPOINT.PANEL The ViewPoint Panel library contains service-related ViewPoint panels. CAI.VPOINT.SQL The ViewPoint SQL library contains service-related ViewPoint SQL statements. 2 2 Getting Started

21 Target Libraries CAI.VPOINT.TEMPLATE The ViewPoint Template library contains service-related ViewPoint templates. CAI.EXP The Agent Technology Export decks library. CAI.OBJ The Agent Technology Object library containing the CEEUOPT module for the example agent. CAI.SRCLIB The Agent Technology source library. CAI.MIBLIB The Agent Technology MIB source library. Chapter 2: Planning the Installation 2 3

22 Comprehensive View of Storage Requirements Comprehensive View of Storage Requirements The following table lists the minimum storage requirements for each target library, broken down by component. Library Name Block Size Component Blocks Directory Blocks CAI.CAILIB 6144 CAIRIM CAIENF CAIENF Utilities CAIENF/USS CAICCI r1.1 or r2.1 CAIVPE CA-MFLINK Earl Service Easytrieve Service SRAM Service CA-C Runtime ViewPoint CA PROFILE CA-Datacom/TR Event Mgt. Agent Technology CA-L-Serv CA-GSS CA-XPS CAISDI/med CAISDI/els CAECIS CAI.PPOPTION 3120 CAIRIM CAIENF CAIENF Utilities CAICCI r1.1 or r2.1 Earl Service ViewPoint CA-L-Serv CA-GSS CAISDI Getting Started

23 Comprehensive View of Storage Requirements Library Name Block Size Component Blocks Directory Blocks CAI.CAISRC 3120 CAIRIM CAIENF CAIVPE Earl Service CA-C Runtime ViewPoint CA-L-Serv CA-GSS CAI.CAIMAC 3120 CAIRIM CAIVPE Earl Service Easytrieve Service CA-C Runtime ViewPoint CA-Datacom/TR CA-GSS CAISDI/els CAI.CAIPROC 3120 CAIRIM CAIENF Earl Service CA-C Runtime CA-L-Serv CAISDI CAECIS CAI.CAICLIB 3120 CAIENF Utilities ViewPoint CA-GSS CAECIS CAI.CAIISPP 3120 CAIENF Utilities ViewPoint CA-GSS CAECIS CAI.CAICICS 6144 CA-C Runtime Chapter 2: Planning the Installation 2 5

24 Comprehensive View of Storage Requirements Library Name Block Size Component Blocks Directory Blocks CAI.CAIPDSE 6144 Event Mgmt, CAIENF, and CAICCI r1.1 or r CAISDI/soap 100 N/A N/A CAI.CAIEVENT 8000 CAISDI/els CAI.CAEDIT 6144 CAIENF Utilities 15 5 CAI.CASCRN 4104 CAIENF Utilities CAI.CAIISPM 3120 CA-GSS CAECIS CAI.VPOINT.DIALOG 8204 ViewPoint CAI.VPOINT.HELP 4104 ViewPoint CAI.VPOINT.CHOICES 4104 ViewPoint CAI.VPOINT.MESSAGE 4104 ViewPoint CAI.VPOINT.PANEL 4104 ViewPoint CAI.VPOINT.SQL 3120 ViewPoint CAI.VPOINT.TEMPLATE 3120 ViewPoint CAI.CAISAMPI 3600 CA-GSS 39 2 CAI.CAISYSI 3600 CA-GSS CAI.EXP 3200 Agent Technology 7 5 CAI.AGENT.RO.HFS - Agent Technology 30 cyl - CAI.AGENT.RW.HFS - Agent Technology 30 cyl - CAI.DISTSRC Agent Technology CAI.MIBLIB Agent Technology CAI.OBJ 3200 Agent Technology 2 5 CAI.DISTLOAD 6144 Agent Technology CAI.TNGFW.RO.HFS - Event Management 700 cyl - CAI.TNGFW.RW.HFS - Event Management. 200 cyl Getting Started

25 Installation Requirements for Each CCS Component Installation Requirements for Each CCS Component This section lists the installation requirements and distribution libraries required for each CCS component. CAIRIM/CAISSF The CAIRIM service, S910, includes CAIRIM and CAISSF services. Note: For information about non-ca security product support of CAISSF, see the Administrator Guide. CAIRIM has the following installation requirements: CAIRIM supports OS/390 V2R8 and higher. CAIRIM runs on any z/os processor with no special setup or modification required. CAIRIM must be installed into an APF authorized library. The CAIRIM routines can be executed from a STEPLIB concatenation or from a LINKLIST concatenation. CAIRIM is normally installed into the common CAI.CAILIB. It is recommended that the CAILIB be added to the system LINKLIST. Certain CA solutions, such as etrust CA-ACF2 Security, may document this as a requirement for PDS member-level protection. For additional solution-specific information, consult the installation documentation for your solution. SMF recording must be active in the system for any SMF event or data-handling solution routines. The CAIRIM SMF Interceptor component does not require any particular SMF records. If desired, you can suppress all SMF record types as long as the SMF parameters specify that SMF is active. In some cases, a particular CA solution requires that certain SMF records be recorded. This recording is strictly for historical analysis and reporting, not for solution operation or initialization. CAIRIM requires approximately 12 KB of ECSA and 4 KB of CSA. Additional CSA requirements for resident modules vary with each service or product. Consult the installation documentation for your solution for additional solution-specific information. CA LMP requires approximately 22 KB of ECSA. CAISSF requires approximately 1 KB of CSA for the security routine and approximately 2 KB to 4 KB for the respective security translator. CAIRIM uses a small amount of SQA for creating CDE entries approximately 30 bytes per module. Chapter 2: Planning the Installation 2 7

26 Installation Requirements for Each CCS Component CA LMP uses an SVC that is dynamically installed during CAIRIM initialization. You do not need to select an SVC entry for the CA LMP SVC, as it will use the first available unused SVC slot it finds. CAIRIM does not use LPA or ELPA. The distribution libraries required for CAIRIM are shown in the following table: Library Name Block Size Number of Blocks Directories Description CAI.S910.CS910LLD Distribution Load Library CAI.S910.CS910SLD Distribution Source Library CAIENF CAIENF has the following installation requirements: CAIENF supports OS/390 V2R10 and higher. The ID associated with the ENF started task must have a valid OMVS segment defined. CAIENF must be installed into an APF authorized library. LINKLIST is not required; however, it is recommended, to prevent STEPLIB problems. CAIENF runs as a started task. A procedure containing the CAIENF started task JCL must be defined in any PROCLIB data set. The sample provided on the CCS for z/os tape can be tailored to the requirements of the data center. CAIENF supports various control options that can be tailored to meet the requirements of the individual data center. Note: For information about tailoring CAIENF control options, see the Administrator Guide. A database must be allocated and initialized for CAIENF use. The amount of disk space required by CAIENF for its database depends on several factors. You can estimate the space requirements using the following formula: Space in cylinders = (A * B / C) + 10 A = Total number of logged events per day. B = Desired retention period in days. C = Device constant: For 3380, use 3000 For 3390, use Getting Started

27 Installation Requirements for Each CCS Component CAIENF requires common storage for modules and global control blocks. The amount of CSA required varies depending on the configuration of the individual data center; however, 90 KB can be used as a rough estimate. Approximately 50% of the CSA required by CAIENF is allocated in ECSA. The amount of storage that the CAIENF address space requires varies depending on overall system load, recording options, and database service times. The CAIENF address space requires approximately 3-4 MB of private area modules and work areas, as well as an average of 256 bytes for each queued event request. The number of queued event requests can be determined from the ENF STATUS operator command. CAIENF also requires approximately 4 KB in each application address space, although this amount varies depending on application structure. The distribution libraries required for CAIENF are shown in the following table: Library Name Block Size Number of Blocks Directories Description CAI.W110.CW110LLD Distribution Load Library CAI.W110.CW110SLD Distribution Source Library CAI.W110.CW110LPD TRK 50 N/A Distribution Load Library The space allocation for target and distribution libraries includes requirements for CAIENF/CICS, CAIENF/DB2, part of CAIENF Utilities, and CAICCI. CAIENF Installation Considerations for etrust CA-ACF2 Users etrust CA-ACF2 Users must create two logon IDs (LIDs) for CAIENF: LID for the started task LID for use with any batch job that runs the CAIENF database utility CAS9DB If your data center uses the restricted command list facility of etrust CA-ACF2, the LID created for use with the batch jobs must have a command list of CAS9ACMD, which is supplied with CAIENF in the CAIENF load libraries. Any batch job that executes CAS9DB should be submitted to run under the special LID. Use one of the following methods: By coding USER= and PASSWORD= parameters on the jobcard By inserting the following etrust CA-ACF2 control statements immediately after the jobcard: Chapter 2: Planning the Installation 2 9

28 Installation Requirements for Each CCS Component //*LOGONID special_lid //*PASSWORD special_lid_password Note: After the desired jobs have run, remove or comment out this data to prevent unauthorized use of the LID. Examples The following examples show what your JCL might look like if your special LID is defined as CAS9LID and the password is defined as CAS9PASS, using the two methods described previously: Method 1: //JOBNAME JOB (ACCOUNTING INFO), // USER=CAS9LID,PASSWORD=CAS9PASS, // CLASS=... //STEP1 EXEC PGM=CAS9DB... Method 2: //JOBNAME JOB (ACCOUNTING INFO), // CLASS=... //*LOGONID CAS9LID //*PASSWORD CAS9PASS //STEP1 EXEC PGM=CAS9DB... Note: These are examples only. It is suggested that you choose a LID and a password that are different from those used in the examples. CAIENF Utilities CAIENF utilities have the following installation requirements: CA-C Runtime (CF33100) and ViewPoint (CAG3000) SMP functions must be installed. CAIENF SMP functions CW11000 and CW21000 must be installed. All system requirements for CAIENF must be met. If using the CAIENF Utilities ENFC facility, CAIENF/Extract (CW11001) and CAICCI (CW41100 or CW42100) must be installed. All system requirements for CAIENF/Extract and CAICCI must be met. Supports OS/390 V2R10 and higher Getting Started

29 Installation Requirements for Each CCS Component The distribution libraries required for CAIENF Utilities are shown in the following table: Library Name Block Size Number of Blocks Directories Description CAI.W110.CW110ELD Distribution Editor Library CAI.W110.CW110PLD Distribution Panel Library CAIENF/CICS CAIENF/CICS has the following installation requirements: CAIENF/CICS supports all CICS releases from CICS R CAIENF/CICS has a subtask that runs within the CAIENF address space. The primary function of the subtask is to keep track of all CICS regions and to handle operator commands. A procedure containing the CAIENF started task JCL must be defined in any PROCLIB data set. The sample provided on the CCS for z/os tape may be tailored to your data center requirements. CAIENF/CICS supports various control options that can be tailored to meet the individual data center requirements. A database must be allocated and initialized for CAIENF use. An update to the database is required that tells CAIENF that the CAIENF/CICS interface is to be installed. The primary function of the CAIENF/CICS Interface is to provide one common service for handling CICS release dependencies. This alleviates the effects of new CICS releases on CA CICS solutions. The CAIENF/CICS Interface consists of a different set of load modules for each CICS release. These modules are loaded into CSA when CAIENF is started. Optionally, the appropriate load module may be loaded into the CICS Private Area. Each module uses approximately 40 KB of CSA or CICS Private Area, depending on where it is loaded. When a CICS Region is started, CAIENF/CICS checks for the existence of a DDNAME of CENFLIB. If this DDNAME is defined, CAIENF/CICS loads the appropriate modules into the CICS Private Area. If the DDNAME of CENFLIB is not defined, CAIENF/CICS tries to load the modules from STEPLIB. If the modules are found in STEPLIB, they are loaded into the CICS Private Area. Lastly, CAIENF/CICS attempts to find the modules in CSA. To use this feature to apply maintenance on the global CAIENF/CICS modules, enter the ENF REFRESH(CAS9Cxx) control option, where xx is the release of CICS. Chapter 2: Planning the Installation 2 11

30 Installation Requirements for Each CCS Component CAIENF/DB2 CAIENF/DB2 has the following installation requirements: CAIENF/DB2 supports all DB2 releases from DB2 R2.3 and higher. A database must be allocated and initialized for CAIENF use. Note: For more information about CAIENF/DB2, see the Administrator Guide. The load module DSNXAUTH cannot be loaded into LPA; if loaded, an abend will occur when CAIENF/DB2 is initialized. CAIENF/DB2 requires DSNXAUTH to be loaded into the private area so that intercepts can be managed by subsystem (not all subsystems require the intercept). The primary function of the CAIENF/DB2 interface is to handle release dependencies between different levels of DB2. This anticipates and prevents the need for changes to CA DB2 solutions that are otherwise necessary with each new release of DB2. CAIENF/DB2 uses approximately 20 KB of CSA for its own load modules. Additional storage, for units of work data, is obtained from extended CSA whenever possible, although some work storage is obtained from the individual user private area. The amount of extended CSA used is a function of the size and workload of the individual DB2 system. When a DB2 subsystem is started, CAIENF/DB2 gets control and queries CAIENF-based applications for required exit points. Only those exit points actually required are installed. If no exit points are required, only the primary CAIENF/DB2 anchor is installed in the system. This anchor is not accessed again until the DB2 subsystem is terminated. CAIENF/CICS SPAWN CAIENF/CICS SPAWN has the following installation requirements: CAIENF/CICS SPAWN supports all CICS releases from CICS R2.1.2 and higher. CAIENF/CICS SPAWN supports various control options that can be tailored to meet the individual data center requirements. CAICCI is required software and needs to be installed prior to the installation of CAIENF/CICS SPAWN. A database must be allocated and initialized for CAIENF use. Note: For more information about CAIENF/CICS SPAWN, see the Administrator Guide. The primary function of CAIENF/CICS SPAWN is to let CA solutions start CICS units of work from outside the CICS region. The facility provides a layer that isolates the application software from the CICS release. CAICCI is the proprietary communications vehicle that enables this facility Getting Started

31 Installation Requirements for Each CCS Component When a CICS region is started, CAIENF/CICS SPAWN checks for the existence of a DDNAME of CENFLIB. If this DDNAME is defined, CAIENF/CICS SPAWN loads the appropriate modules into the CICS Private Area. If the DDNAME of CENFLIB is not defined, CAIENF/CICS SPAWN tries to load the modules from STEPLIB. If the modules are found in STEPLIB, they are loaded into the CICS Private Area. Lastly, CAIENF/CICS SPAWN attempts to find the modules in CSA. CAIENF/USS CAIENF/USS has the following installation requirements: OS/390 V2R10 or higher, with OS/390 UNIX System Services active in full-function mode. Consult your IBM documentation for information about configuring OS/390 UNIX System Services. The ENF address space must run with root privileges under UNIX System Services. The security ID associated with the ENF started task requires: A superuser ID (UID 0), or permission to the IBM Facility resource BPX.SUPERUSER. A valid group ID (GID), home directory, and shell program. Permission to the IBM Facility resource BPX.DAEMON, if you have defined this resource in your installation. Note: For more information, see your security product documentation. For best performance, CAIENF/USS requires that you define a new object to VLF (Virtual Lookaside Facility) as follows: Add an entry to the COFVLFxx member of SYS1.PARMLIB (where xx is the VLF identifier assigned by your systems programmer). Example: CLASS NAME(CAENFU) /* ENF/USS pathname lookup cache*/ EMAJ(PATHCACHE) /* Required major name*/ MAXVIRT(512) /* 512 = 2MB*/ The class name (CAENFU) and major name (PATHCACHE) must be entered exactly as shown. MAXVIRT in the range of 512 to 1024 (representing 2 MB to 4 MB of virtual storage) should suffice for most sites; however, you may want to change MAXVIRT according to the following formula: MAXVIRT = MAXFILEPROC * MAXPROCSYS * 16 MAXFILEPROC and MAXPROC are UNIX System Services configuration parameters found in SYS1.PARMLIB(BPXPRMxx). The CAIENF DCM module CARRDCM0 must be installed using the CAS9DB utility. Chapter 2: Planning the Installation 2 13

32 Installation Requirements for Each CCS Component Note: Products that use the CAIENF/USS component also have a DCM (data collection module). The CAIENF/USS DCM and all product-specific DCMs must be installed to ensure correct operation. See your CA product documentation for details. The distribution library required for CAIENF/USS is shown in the following table: Library Name Block Size Number of Blocks Directories Description CAI.RR21.CRR21LLD Distribution Load Library CAICCI CAICCI has the following installation requirements: CAICCI supports OS/390 V2R10 and higher. CAICCI SSL usage requires z/os V1R3 as a minimum. CAICCI must be installed into an APF authorized library. This library must be the same library that was used for the CAIENF service installation. CAICCI supports various control options, which may be tailored to meet the individual data center requirements. A CAIENF database must be allocated and initialized. An update to the CAIENF database is required that tells CAIENF that CAICCI is to be installed. CAICCI requires 172 KB of ECSA for modules and global control blocks. For each concurrent host program, CAICCI requires an additional 304 bytes of ECSA. The amount of ECSA required varies depending on the individual data center configuration and general activity. An estimate may be achieved by the following formula: 172K bytes + (Number of concurrent host-related programs using CAICCI) * (308 bytes) * (Number of sessions in a multi-cpu environment) Determine the number of concurrent host-related (application) programs using CAICCI from the ENF STATUS,CCIR operator command, which displays the general status of the CAICCI resources. Message CAS9701I displays the number of pending receivers (programs using CAICCI). In a multi-cpu environment, add 258 KB for each CPU defined. The ID associated with the CCITCP, CCITCPGW, CCISSL, and/or CCISSLGW started tasks must have a valid OMVS segment defined Getting Started

33 Installation Requirements for Each CCS Component CAIVPE CAIVPE is used with other CA solutions. The prerequisite system requirements of these solutions meet or exceed the requirements for CAIVPE with respect to the environments and operating systems supported by CAIVPE. The distribution libraries required for CAIVPE r4.2 are shown in the following table: Library Name Block Size Number of Blocks Directories Description CAI.WU42.CWU42LLD Distribution Load Library CAI.WU42.CWU42MLD Distribution Macro Library CAI.WU42.CWU42SLD Distribution Source Library CAIVPE Installation Considerations CAIVPE is an interproduct component used by other CA solutions, such as Advantage CA-Datacom, Advantage CA-Ideal, and others. CA-MFLINK CA-MFLINK provides mainframe services that support mainframe-to-pc communications for other CA solutions. CA-MFLINK has the following installation requirements: CAIVPE r4.2. CA-MFLINK is used with other CA solutions. The prerequisite system requirements of these solutions meet or exceed the requirements for CA-MFLINK with respect to the environments and operating systems supported by CA-MFLINK. The distribution library required for CA-MFLINK is shown in the following table: Library Name Block Size Number of Blocks Directories Description CAI.PC42.CPC42LLD Distribution Load Library Chapter 2: Planning the Installation 2 15

34 Installation Requirements for Each CCS Component Earl Service Earl Service has the following installation requirements: Earl Service supports all OS/390 and higher operating systems. Earl Service requires Unicenter CA-Sort, IBM DF/Sort, or a compatible product with the module name SORT. The distribution libraries required for Earl Service are shown in the following table: Library Name Block Size Number of Blocks Directories Description CAI.EO61.CEO61LLD Distribution Load Library CAI.EO61.CEO61MLD Distribution Macro Library CAI.EO61.CEO61SLD Distribution Source Library Easytrieve Service Requirements Easytrieve Service has the following installation requirements: Easytrieve Service supports all OS/390 (release 2.10 or above) and newer operating systems. Easytrieve Service requires Unicenter CA-Sort, IBM DF/Sort, or a compatible product with the module name SORT. If you have Easytrieve r6.4 already installed at your site, do not install the Easytrieve Service from CCS. All the necessary functionality is present in your installed Easytrieve. SMP/E prevents installation of CCS Easytrieve into the same CSI where the complete Easytrieve product is already installed. If you have Easytrieve r6.3 or lower, install the CCS Easytrieve Service into an SMP CSI where Easytrieve is not already installed. Also, it must be installed into SMP Distribution and Target libraries that are different from those of your production Easytrieve installation. This is necessary because the module names are the same for the two products Getting Started