CA File Master Plus Installation Guide

Home , Package (macOS), Zip (file format)

CA File Master™ Plus

Installation Guide Version 9.0.00

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or 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 YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors. Copyright © 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

CA Technologies Product References

This document references the following CA Technologies products: ■ CA ACF2™ (CA ACF2) ■ CA File Master™ Plus (CA File Master Plus) ■ CA Chorus™ Software Manager (CA MSM), formerly CA MSM

Documentation Changes

The following documentation updates have been made since the last release of this documentation: ■ How the Installation Process Works (see page 8)—Changed the description of the installation procedure to correct a content error. ■ Installing Your Product Using CA Chorus Software Manager (see page 13)—Updated this chapter to support the newest version of CA MSM. ■ Installing Your Product From Tape—Removed this chapter. ■ Installing the Graphical User Interface (see page 45)—Added section to support the CA File Master Plus GUI installation.

Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources: ■ Online and telephone contact information for technical assistance and customer services ■ Information about user communities and forums ■ Product and documentation downloads ■ CA Support policies and guidelines ■ Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you can send a message to [email protected].

To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.

Contents

Chapter 1: Overview 7 Audience ...... 7 How the Installation Process Works...... 8

Chapter 2: Preparing for Installation 9 Hardware Requirements ...... 9 Software Requirements ...... 9 CA Common Services...... 9 Security Requirements ...... 10 Storage Requirements ...... 10 Distribution Libraries ...... 10 Target Libraries ...... 11 Other Requirements ...... 12 Concurrent Releases ...... 12

Chapter 3: Installing Your Product Using CA Chorus Software Manager 13 How to Install Your Product Using CA MSM ...... 13 Access CA CSM Using the Web-Based Interface ...... 14 Acquire a New Product ...... 15 Install a Product ...... 16 Maintain the Installed Products ...... 18 Deploy the Product to the Destination System ...... 19 Configure the Deployed Product ...... 20

Chapter 4: Installing Your Product from Pax-Enhanced ESD 23 How to Install a Product Using Pax-Enhanced ESD ...... 23 How the Pax-Enhanced ESD Download Works ...... 24 ESD Product Download Window ...... 25 USS Environment Setup ...... 28 Allocate and Mount a File System ...... 29 Copy the Product Pax Files into Your USS Directory ...... 32 Download Using Batch JCL ...... 33 Download Files to Mainframe through a PC ...... 36 Create a Product Directory from the Pax File ...... 37 Sample Job to Execute the Pax Command (Unpackage.txt) ...... 38

Contents 5

Copy Installation Files to z/OS Data Sets ...... 38 Receiving the SMP/E Package ...... 39 Prepare the SMP/E Environment ...... 40 Run the Installation Job ...... 40 Clean Up the USS Directory ...... 41 Apply Maintenance ...... 42 HOLDDATA ...... 43 Accept the Product ...... 44 Save Materials and Output...... 44

Chapter 5: Installing the Graphical User Interface 45 Install Mainframe Support for the User Interface ...... 45 Install Apache Tomcat ...... 46 Install the TSO Command ...... 46 Modify the Sample JCL Library ...... 47 Update Mainframe Support for the Eclipse User Interface ...... 48 Install the Workstation User Interface ...... 49

Chapter 6: Configuring Your Product 51 Allow Function Commands from ISPF Data Set Lists (Optional)...... 52 Customize Options (Optional) ...... 53 Parameter Descriptions ...... 54 Customize Batch JCL (Optional) ...... 59 Add CA ACF2 Security for z/OS User Considerations (Optional) ...... 59 Customize Wildcard Exit CAWAWDSN (Optional) ...... 60

Chapter 7: Prepare to Start Your CA File Master Plus 61 Allocate PARMLIB Partitioned Data Sets ...... 61 Evaluate the REXX Environment ...... 62 Customize REXX EXEC ...... 63 Add Option Name to an ISPF Menu Panel (Optional) ...... 63 Add ISPF Libraries to TSO LOGON Procedure (Optional)...... 64

Chapter 8: Migration Information 65 Migrate Installation Packages Downloaded External to CA MSM ...... 65

6 Installation Guide

Chapter 1: Overview

This guide describes how to install and implement CA File Master Plus.

This section contains the following topics: Audience (see page 7) How the Installation Process Works (see page 8)

Audience

Readers of this book should have knowledge in the following areas: ■ JCL ■ TSO/ISPF ■ SMP/E ■ Your z/OS environment ■ Your organization's IT environment, enterprise structure, and region structure

You may need to work with the following personnel: ■ Systems programmer, for z/OS and VTAM definitions ■ Security administrator, for library and started task access authority ■ SMS or storage administrator, for DASD allocations

Chapter 1: Overview 7

How the Installation Process Works

CA Technologies has standardized product installations across all mainframe products. Installation uses the following process: ■ Acquisition—Transports the software to your z/OS system. ■ Installation using SMP/E—Optionally creates a CSI environment and runs the RECEIVE, APPLY and ACCEPT steps. The software is untailored. ■ Deployment—Copies the target libraries to another system or LPAR. ■ Configuration—Creates customized load modules, bringing the software to an executable state.

CA MSM provides a web-based interface to make the standardized installation process easier. Using CA MSM, someone with limited knowledge of JCL and SMP/E can install a product.

Note: If you do not have CA MSM, you can download it from the Download Center at the CA Support Online website. Follow the installation instructions in the CA Mainframe Software Manager documentation bookshelf on the CA Mainframe Software Manager product page. The standardized installation process can also be completed manually.

To install your product, do the following tasks: 1. Prepare for the installation by confirming that your site meets all installation requirements (see page 9). 2. Acquire the product using one of the following methods: ■ CA MSM ■ Pax-Enhanced Electronic Software Delivery (ESD) ■ Order a DVD.

3. Install the product based on your acquisition method.

4. Install the CA Common Services using the pax files that contain the CA Common Services you need at your site. All sites should install all CA Common Services contained in the Required CA Common Service bundle.

5. Apply maintenance, if applicable. 6. Deploy your target libraries. 7. Configure your product.

8 Installation Guide

Chapter 2: Preparing for Installation

This section describes what you need to know and do before you install the product.

This section contains the following topics: Hardware Requirements (see page 9) Software Requirements (see page 9) CA Common Services (see page 9) Security Requirements (see page 10) Storage Requirements (see page 10) Other Requirements (see page 12) Concurrent Releases (see page 12)

Hardware Requirements

CA File Master Plus runs on any IBM mainframe that supports z/OS.

The Eclipse Plug In requires approximately 5MB of disk space and approximately 140MB of additional DASD under USS for web server.

Software Requirements

CA File Master Plus operates on any z/OS system with TSO/ISPF 2.1.0 and above and REXX 1.3.0 and above. CA File Master Plus requires LE runtime libraries.

The Eclipse Plug In requires Eclipse 3.6.2 or higher. The product has not been tested for Eclipse 4.x.

CA Common Services

CA File Master Plus exploits the installation of the following CA Common Services for z/OS and OS/390 components: ■ CAI Resource Initialization Manager (CAIRIM) ■ CA License Management Program (CALMP)

These CA Common Services must be installed or maintained at the genlevel indicated on the cover letter for the product.

Chapter 2: Preparing for Installation 9

Security Requirements

To complete the tasks in this guide, you need the following security privileges: ■ Update authority for the SMP/E distribution and target libraries ■ Read authority for the installation files

Storage Requirements

Verify that you have the following storage available: ■ If you install the product with Pax ESD, 130 MB for the downloaded files. ■ For installation and setup: – Installation = 665 cylinders – SMP/E temporary libraries = 318 cylinders

Distribution Libraries

The following table displays estimates of disk space for the distribution libraries required to install CA File Master Plus.

Name Blksize Cyls Dir Blks Description CAI.ADBIMOD 32760 13 120 Load modules CAI.ADBIDATV 32760 243 12 GUI installation CAI.ADBIEXEC 27920 3 20 REXX programs CAI.ADBIJCL 27920 2 12 JCL members CAI.ADBIMAC 27920 2 12 Assembler macros CAI.ADBIMSG0 27920 5 40 ISPF messages CAI.ABDIOPTN 27920 2 12 Option members CAI.ADBIPNL0 27920 45 440 ISPF panels CAI.ADBIPROC 27920 2 12 PROC members CAI.ADBISAMP 27920 2 12 Sample source members CAI.ADBISKL0 27920 2 12 ISPF skeletons CAI.ADBISRC 27920 2 12 Program source members CAI.ADBITBL0 27920 2 12 ISPF tables

10 Installation Guide

Storage Requirements

Name Blksize Cyls Dir Blks Description CAI.ADBIXML 32760 4 12 XML members

Target Libraries

The following table displays estimates of disk space for the target libraries required to install CA File Master Plus. These libraries must be allocated if they do not already exist for some other CA Technologies product in your shop.

Name Blksize Cyls Dir Blks Description CAI.CDBILOAD 32760 20 120 Common load library CAI.CDBIDATV 32760 243 12 GUI installation CAI.CDBIEXEC 27920 3 20 Interpreted REXX library CAI.CDBIJCL 27920 2 12 Common JCL library CAI.CDBIMAC 27920 2 12 Common macro library CAI.CDBIMSG0 27920 5 40 Common ISPF message library CAI.CDBIOPTN 27920 2 12 Common options library CAI.CDBIPNL0 27920 45 440 Common ISPF panel library CAI.CDBIPROC 27920 2 12 Common PROC library CAI.CDBISAMP 27920 2 12 Common sample source library CAI.CDBISKL0 27920 2 12 Common ISPF skeleton library CAI.CDBISRC 27920 2 12 Common program source library CAI.CDBITBL0 27920 2 12 Common ISPF table library CAI.CDBITXML 32760 4 12 Common XML library

Chapter 2: Preparing for Installation 11

Other Requirements

Note the following: ■ CA File Master Plus uses about one megabyte of virtual storage. Users should log on with a region large enough for both CA File Master Plus and other existing ISPF functions. ■ IBM REXX/370 1.3.0 product or the REXX alternate library should be installed with the compiler run-time processor table entry EAGRTPRC included in IRXCMPTM. If the minimum requirement for the REXX alternate library is not met, the REXX alternate library can be downloaded from www.ibm.com/support www.ibm.com/support. ■ A unit type of VIO must be generated in the operating system.

Concurrent Releases

You can install this release of CA File Master Plus and continue to use an older release for your production environment. If you plan to continue to run a previous release, consider the following points: ■ When you install the product into an existing SMP/E environment, this installation deletes previous releases in that environment. ■ For your new release, select different target and distribution zones from where your current release is installed. The new zones use different libraries than your current release. Note: CA MSM installs a product into a new SMP/E environment by default. You can select an existing SMP/E environment from your working set. For more information, see the online help that is included in CA MSM. ■ Define DDDEF entries in your new zones to point SMP/E to the proper libraries for installation. Ensure that they point to the new release libraries.

12 Installation Guide

Chapter 3: Installing Your Product Using CA Chorus Software Manager

How to Install Your Product Using CA MSM

As a system programmer, your responsibilities include acquiring, installing, maintaining, deploying, and configuring CA Technologies mainframe products on your system.

CA MSM is an application that simplifies and unifies the management of your CA Technologies mainframe products on z/OS systems. As products adopt the CA MSM services, you can install your products in a common way according to industry best practices.

This scenario describes the steps for a system programmer to acquire, install, deploy, and configure products and maintenance. Not all tasks may apply to your organization. For example, you may decide not to deploy and configure products. In this case, do not perform the product deployment task and the product configuration task.

Before you use this scenario, you must have CA MSM installed at your site. If you do not have CA MSM installed, you can download it from the Download Center at http://ca.com/support. This web page also contains links to the complete documentation for CA MSM.

You access CA MSM (see page 14) from a web browser.

Note: This scenario applies to the latest version of CA MSM. If you are using an earlier version, see the appropriate bookshelf on the CA Chorus Software Manager product page.

This scenario is a high-level overview of steps that you perform using CA MSM. For more detailed information, use the online help that is included in CA MSM.

Chapter 3: Installing Your Product Using CA Chorus Software Manager 13

How to Install Your Product Using CA MSM

You perform the following tasks to install products and manage them on your system:

1. Acquire a new product (see page 15). 2. Install the product (see page 16).

3. Maintain the installed products (see page 18).

4. Deploy the product to the destination system (see page 19). 5. Configure the deployed product (see page 20).

Access CA CSM Using the Web-Based Interface

You access CA MSM using the web-based interface.

You need the URL of CA MSM from the CA MSM administrator.

Follow these steps: 1. Start your web browser, and enter the access URL. The login page appears. Note: If the Notice and Consent Banner appears, read and confirm the provided information. 2. Enter your z/OS login user name and password. The initial page appears. If you log in for the first time, you are prompted to define your account on the CA Support Online website. Note: For more information about the interface, click the online help link at the top right corner of the page.

3. Click New. You are prompted for the credentials to use on the CA Support Online website.

14 Installation Guide

How to Install Your Product Using CA MSM

4. Specify the credentials, click OK, and then click Next. You are prompted to review your user settings. Note: These settings are available on the User Settings page. 5. Change the settings or keep the defaults, and then click Finish. A dialog opens, which shows the progress of the configuration task. You can click Show Results to view the details of the actions in a finished task.

Important! If your site uses proxies, review your proxy credentials on the User Settings, Software Acquisition page.

Acquire a New Product

Acquisition allows you to download products and product maintenance from the CA Support Online website at http://ca.com/support to a USS directory structure on your system. The products to which your site is entitled and the releases available are displayed in the Available Products section on the Products page.

You perform the following high-level tasks to acquire a product using CA MSM: 1. Set up a CA Support Online account at http://ca.com/support. To use CA MSM to acquire or download a product, you must have a CA Support Online account. If you do not have an account, create one on http://ca.com/support.

2. Determine the CA MSM URL for your site. To access CA MSM (see page 14), you require its URL. You can get the URL from your site CA MSM administrator and log in using your z/OS credentials. When you log in for the first time, you are prompted to create a CA MSM account with your credentials that you use to access http://ca.com/support. This account enables you to download product packages.

3. Log in to CA MSM and go to the Products page to locate the product that you want to acquire. After you log in to CA MSM, you can see the products to which your organization is entitled on the Products tab. If you cannot find the product that you want to acquire, update the product list. CA MSM refreshes the product list through http://ca.com/support using the site IDs associated with your credentials.

Chapter 3: Installing Your Product Using CA Chorus Software Manager 15

How to Install Your Product Using CA MSM

4. Download the product installation packages. After you find your product in the product list, you can download the product installation packages. To do so, use the Update Product Release action. CA MSM downloads (acquires) the packages (including any maintenance packages) from the CA Support Online website.

After the acquisition process completes, the product is ready for you to install or apply maintenance.

Install a Product

CA MSM simplifies and manages SMP/E installation tasks. You can browse and install a product that you acquired and that is available in the product list on the Products page. You can also install the maintenance for the products that are currently installed in a managed SMP/E environment on the driving system.

16 Installation Guide

How to Install Your Product Using CA MSM

You perform the following high-level tasks to install a product using CA MSM:

Chapter 3: Installing Your Product Using CA Chorus Software Manager 17

How to Install Your Product Using CA MSM

1. (Optional) On the Settings tab, click Software Installation under System Settings, and configure base installation settings. 2. (Optional) Click the SMP/E Environments tab, and configure a working set of SMP/E environments.

3. Click the Products tab and select a product that you want to install. Start the installation wizard and review product information.

4. Select an installation type.

5. Review installation prerequisites if any are presented.

6. Take one of the following steps to select an SMP/E environment: ■ Create an SMP/E environment: a. Set up the global zone. b. Create a target zone. c. Create a distribution zone.

■ Use an existing SMP/E environment from your working set: a. Update the global zone. b. Set up the target zone: Create a target zone or use an existing target zone. c. Set up the distribution zone: Create a distribution zone or use an existing distribution zone. Note: If you install a product or its components into an existing target or distribution zone, older versions are deleted from the zone and associated data sets. We recommend that you use new target and distribution zones for this installation so that you can apply maintenance to your current version, if necessary.

7. Review the installation summary and start the installation. 8. (Optional) Review pending tasks for the SMP/E environment where you are installing your product. Continue the installation, if applicable. CA MSM installs the product.

After the installation process completes, check for and install available product maintenance. The product is ready for you to deploy. Sometimes, there are other steps to perform manually outside of CA MSM before continuing.

Maintain the Installed Products

You can migrate existing SMP/E environments into CA MSM to maintain all your installed products in a unified way from a single web-based interface.

You can use CA MSM to maintain a CA Technologies product.

18 Installation Guide

How to Install Your Product Using CA MSM

You perform the following high-level tasks to maintain a product using CA MSM: 1. Verify that CA MSM recognizes the SMP/E environment where your product is installed. If not, migrate the SMP/E environment to CA MSM. During the migration, CA MSM stores information about the SMP/E environment in the database.

2. From the Product tab, download the latest maintenance for the installed product releases. If you cannot find the required release, perform the following steps to download the maintenance: a. Add the release to the catalog manually. b. Update the added release. 3. Apply the maintenance. CA MSM applies the maintenance to your product.

After the maintenance process completes, the product is ready for you to deploy to systems that are defined in the system registry.

Deploy the Product to the Destination System

Deployment is a process of copying SMP/E target libraries to a destination system. The destination system could be the local z/OS system, a remote z/OS system, or a sysplex. You identify the destination system, deployed data set names, and the transport mechanism as part of the deployment process. Deploying a product makes it available for configuration.

Important! Before you deploy a product, set up the destination systems and remote credentials in the system registry.

You perform the following high-level tasks to deploy your products using CA MSM: 1. On the Deployments tab, set up methodologies. Note: You can also set up methodologies when creating a deployment, or use existing methodologies, if you have set up any previously. If you do so, you can skip this step.

2. Start the New Deployment wizard to create a deployment. Complete each of the steps in the wizard. The wizard guides you through choosing deployment settings for your site. At any point, you can save your work and come back to it later.

Chapter 3: Installing Your Product Using CA Chorus Software Manager 19

How to Install Your Product Using CA MSM

3. Deploy: a. Take a snapshot of the deployment. b. Transmit the deployment to a destination system. c. Deploy (unpack) to the mainframe environment. CA MSM deploys the product to the destination system.

After the deployment process completes, the product is ready for you to configure.

Configure the Deployed Product

Configuration is a process of copying the deployed libraries to run-time libraries and customizes the product for your site to bring it to an executable state. You can configure CA Technologies products that you have already acquired, installed, and deployed using CA MSM. You cannot use CA MSM to configure a product unless you have already used CA MSM to deploy the product.

You perform the following high-level tasks to configure your products using CA MSM: 1. Select a configurable deployment on the Deployments tab to view details and products for that deployment. 2. Select a product in the deployment and start the Configuration wizard to create a configuration. Complete each of the steps in the wizard. The wizard has multiple levels of detailed instructions and guides you through choosing configuration settings for your site. At any point, you can save your work and come back to it later. Configurations where you have partially completed the steps in the wizard are listed on the Configurations tab. The steps in the wizard include the following: a. Define a configuration name and select a system for the configuration. b. Select configuration functions and options.

c. Define system preferences.

d. Create target settings. e. Select and edit resources.

3. Build the configuration. The last step of the Configuration wizard lets you build the configuration. If needed, you can edit the configuration and can build the configuration again. Building the configuration closes the wizard and creates a configuration with all your settings.

4. (Optional) Validate the configuration. Validation verifies access to resources that are going to be used when you implement the configuration.

20 Installation Guide

How to Install Your Product Using CA MSM

5. Implement the configuration. You implement a configuration to make your deployed software fully functional. Implementation executes on the destination system, applying the variables, resources, and operations that are defined in the configuration. CA MSM configures the product.

After the configuration process completes, the product is ready for you to use.

Note: When you have completed the procedures in this section, go to Configuring Your Product (see page 51).

Chapter 3: Installing Your Product Using CA Chorus Software Manager 21

Chapter 4: Installing Your Product from Pax-Enhanced ESD

This section contains the following topics: How to Install a Product Using Pax-Enhanced ESD (see page 23) Allocate and Mount a File System (see page 29) Copy the Product Pax Files into Your USS Directory (see page 32) Create a Product Directory from the Pax File (see page 37) Copy Installation Files to z/OS Data Sets (see page 38) Receiving the SMP/E Package (see page 39) Clean Up the USS Directory (see page 41) Apply Maintenance (see page 42) Accept the Product (see page 44) Save Materials and Output (see page 44)

How to Install a Product Using Pax-Enhanced ESD

This section describes the Pax-Enhanced ESD process. We recommend that you read this overview and follow the entire procedure the first time you complete a Pax-Enhanced ESD installation. For experienced UNIX users, the Pax-Enhanced ESD Quick Reference Guide has sufficient information for subsequent installations.

If you prefer not to involve all CA Technologies product installers with z/OS UNIX System Services, assign a group familiar with USS to perform Steps 1 through 4 and provide the list of the unpacked MVS data sets to the product installer. USS is not required for the actual SMP/E RECEIVE of the product or for any of the remaining installation steps.

To install files using Pax-Enhanced ESD, use the following process: 1. Allocate and mount the file system. This process requires a USS directory to receive the pax file and to perform the unpack steps. We recommend that you allocate and mount a file system that is dedicated to Pax-Enhanced ESD and create the directory in this file system. Ensure that all users who will be working with pax files have write authority to the directory.

Chapter 4: Installing Your Product from Pax-Enhanced ESD 23

How to Install a Product Using Pax-Enhanced ESD

2. Copy the product pax files into your USS directory. To download files, choose one of the following options: ■ Download a zip file from CA Support Online to your PC, unzip the file, and then upload the product pax files to your USS file system. ■ FTP the pax files from CA Support Online directly to your USS directory. Note: Perform Steps 3 through 6 for each pax file that you upload to your USS directory.

3. Create a product directory from the pax file. Set the current working directory to the directory containing the pax file, and create a directory in your USS directory by entering the following command:

pax -rvf pax-filename

4. Use the SMP/E GIMUNZIP utility to create z/OS installation data sets. The file UNZIPJCL in the directory that the pax command created in Step 3 contains a sample JCL to GIMUNZIP the installation package. Edit and submit the UNZIPJCL JCL.

5. Receive the SMP/E package. Use the data sets that GIMUNZIP created in Step 4. Perform a standard SMP/E RECEIVE using the SMPPTFIN and SMPHOLD (if applicable) DASD data sets. Also, specify the high-level qualifier for the RELFILEs on the RFPREFIX parameter of the RECEIVE command.

6. Proceed with product installation. Consult product-specific documentation, including AREADME files and installation notes to complete the product installation. 7. (Optional) Clean up the USS directory. Delete the pax file, the directory that the pax command created, all of the files in it, and the SMP/E RELFILEs, SMPMCS, and HOLDDATA data sets.

How the Pax-Enhanced ESD Download Works

Important! To download pax files for the SMP/E installation as part of the Pax-Enhanced ESD process, you must have write authority to the UNIX System Services (USS) directories used for the ESD process and available USS file space before you start the procedures in this guide.

Use the following process to download files using Pax-Enhanced ESD: 1. Log in to https://support.ca.com/, and click Download Center. The CA Support Online web page appears. 2. Under Download Center, select Products from the first drop-down list, and specify the product, release, and genlevel (if applicable), and click Go. The CA Product Download window appears.

24 Installation Guide

How to Install a Product Using Pax-Enhanced ESD

3. Download an entire CA Technologies product software package or individual pax files to your PC or mainframe. If you download a zip file, you must unzip it before continuing. For both options, The ESD Product Download Window (see page 25) topic explains how the download interface works. Note: For traditional installation downloads, see the Traditional ESD User Guide. Go to https://support.ca.com/, log in, and click Download Center. A link to the guide appears under the Download Help heading. 4. Perform the steps to install the product based on the product-specific steps. The product is installed on the mainframe.

ESD Product Download Window

You can download CA Technologies product ESD packages multiple ways. Your choices depend on the size of the individual files and the number of files that you want to download. You can download the complete product with all components, or you can select individual pax and documentation files for your product or component.

Chapter 4: Installing Your Product from Pax-Enhanced ESD 25

How to Install a Product Using Pax-Enhanced ESD

The following illustration shows sample product files. The illustration lists all components of the product. You can use the Download Cart by selecting one or more components that you need, or selecting the check box for Add All to cart. If you prefer to immediately download a component, click the Download link.

26 Installation Guide

How to Install a Product Using Pax-Enhanced ESD

Clicking the link for an individual component takes you to the Download Method page.

Depending on the size and quantity of ordered product files, the Download Method screen could also have these options:

Note: For mainframe downloads using this HTTP method, click the Learn More link.

The HTTP method lets you start downloading immediately. The FTP method takes you to the Review Orders page that displays your order, first in a Pending status changing to Ready when your order has been processed.

Preferred FTP uses the new content delivery network (CDN). Alternate FTP uses the CA Technologies New York-based FTP servers.

Chapter 4: Installing Your Product from Pax-Enhanced ESD 27

How to Install a Product Using Pax-Enhanced ESD

The Create a Zip File option first creates the zip, and when ready, offers the options that the Zip Download Request examples show in the next illustration.

USS Environment Setup

You need a UNIX System Services (USS) directory and a file system with adequate space to perform the following tasks: ■ Receive product pax files from CA Support Online. ■ Perform utility functions to unpack the pax file into MVS data sets that you can use to complete the product installation.

We recommend that you allocate and mount a file system that is dedicated to Pax-Enhanced ESD. The amount of space that you need for the file system depends on the following variables: ■ The size of the pax files that you intend to download. ■ Whether you plan to keep the pax files after unpacking them. We do not recommend this practice.

We recommend that you use one directory for downloading and unpacking pax files. Reusing the same directory minimizes USS setup. You need to complete the USS setup only one time. You reuse the same directory for subsequent downloads. Alternatively, you can create a directory for each pax download.

28 Installation Guide

Allocate and Mount a File System

Important! Downloading pax files for the SMP/E installation as part of the Pax-Enhanced ESD process requires write authority to the UNIX System Services (USS) directories that are used for the ESD process. The USS file system that is used for Pax-Enhanced ESD must have sufficient free space to hold the directory that the pax command created, and its contents. You need approximately 3.5 times the pax file size in free space to download the pax file and unpack its contents. For example, to download and unpack a 14 MB pax file, you need approximately 49 MB of free space in the file system hosting your ESD directory.

Allocate and Mount a File System

You can use the zSeries File System (zFS) or hierarchical file system (HFS) for ESD downloads.

This procedure describes how to perform the following tasks: ■ Allocate a zFS or an HFS. ■ Create a mount point in an existing maintenance USS directory of your choice.

■ Mount the file system on the newly created mount point. Note: You must have either SUPERUSER authority, or the required SAF profile setting to allow you to issue the USS mount command for the file system. ■ Optionally, permit write access to anyone in the same group as the person who created the directory. Important! USS commands are case-sensitive.

Chapter 4: Installing Your Product from Pax-Enhanced ESD 29

Allocate and Mount a File System

Follow these steps: 1. Allocate the file system by customizing one of the following samples to your site requirements: ■ On a zFS, use the following sample:

//DEFINE EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //AMSDUMP DD SYSOUT=* //SYSIN DD * DEFINE CLUSTER ( + NAME(your_zFS_data_set_name) + STORAGECLASS(class) + LINEAR + CYL(primary secondary) + SHAREOPTIONS(3,3) + ) /* //FORMAT EXEC PGM=IOEAGFMT,REGION=0M, // PARM=('-aggregate your_zFS_data_set_name -compat') //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //CEEDUMP DD SYSOUT=* //*

■ On an HFS, use the following sample:

//ALCHFS EXEC PGM=IEFBR14 //CAESD DD DSN=yourHFS_data_set_name, // DISP=(NEW,CATLG,DELETE),UNIT=3390, // DSNTYPE=HFS,SPACE=(CYL,(primary,secondary,1)) The file system is allocated. Note: Ensure that the zFS or HFS data set name that you use conforms to your data set naming conventions for USS file systems. If the allocation of the file system data set fails, it is because of environmental settings not allowing for the allocation. On an HFS, try using the ISPF 3.2 Data Set Utility to allocate your HFS data set.

30 Installation Guide

Allocate and Mount a File System

2. Create a mount point for the file system. This example shows how to create a /CA/CAESD directory in an existing directory, /u/maint. From the TSO OMVS shell, enter the following commands:

cd /u/maint/ mkdir CA cd CA mkdir CAESD Note: This document refers to this structure as yourUSSESDdirectory. The mount point is created.

3. Mount the file system by customizing one of the following samples to your site requirements: ■ On a zFS, use the following sample:

MOUNT FILESYSTEM('your_zFS_data_set_name') MOUNTPOINT('yourUSSESDdirectory') TYPE(ZFS) MODE(RDWR) PARM(AGGRGROW) ■ On an HFS, use the following sample:

MOUNT FILESYSTEM('your_HFS_data_set_name') MOUNTPOINT('yourUSSESDdirectory') TYPE(HFS) MODE(RDWR) The file system is mounted.

4. (Optional) Set security permissions for the directory. You can use the chmod command to let other users access the ESD directory and its files. For example, to allow write access to the ESD directory for other users in your USS group, from the TSO OMVS shell, enter the following command:

chmod -R 775 /yourUSSESDdirectory/ Write access is granted. Note: For more information about the chmod command, see the IBM z/OS UNIX System Services User Guide (SA22-7802).

Chapter 4: Installing Your Product from Pax-Enhanced ESD 31

Copy the Product Pax Files into Your USS Directory

To begin the CA Technologies product installation procedure, copy the product pax file into the USS directory that you set up. Use one of the following methods: ■ Download the product pax files directly from the CA Support Online FTP server to your z/OS system. ■ Download the product pax file from the CA Support Online FTP server to your computer, and upload it to your z/OS system. ■ Download the product file from CA Support Online to your computer. If your download included a zip file, unzip the file, and upload the unzipped pax files to your z/OS system.

This section includes a sample batch job to download a product pax file from the CA Support Online FTP server directly to a USS directory on your z/OS system and sample commands to upload a pax file from your computer to a USS directory on your z/OS system.

Important! The FTP procedures vary due to local firewall and other security settings. Consult your local network administrators to determine the appropriate FTP procedure to use at your site.

Ensure that sufficient free space is available in the USS file system that you are using for Pax-Enhanced ESD to hold the product pax file. If you do not have sufficient free space, error messages similar to the following appear:

EZA1490I Error writing to data set EZA2606W File I/O error 133

When the download finishes, the pax file size in your USS directory matches the value in the Size column for the corresponding pax file on the CA Technologies Products Download window.

More Information:

How the Pax-Enhanced ESD Download Works (see page 24) ESD Product Download Window (see page 25)

32 Installation Guide

Copy the Product Pax Files into Your USS Directory

Download Using Batch JCL

Use this process to download a pax file from the CA Support Product Downloads window by running batch JCL on the mainframe. Use the sample JCL attached to the PDF file as CAtoMainframe.txt to perform the download.

Important! To simplify the Pax-Enhanced ESD process, the PDF version of this guide includes a sample JCL job that you can copy directly to the mainframe. To access this job, click the paper clip icon at the left of the PDF reader. A window displaying attachments opens. Double-click the file to view the sample JCL.

Note: We recommend that you follow the preferred method as described on CA Support Online. This procedure is our preferred download method; however, we do include the procedure to download to the mainframe through a PC in the next section.

Follow these steps: 1. Supply a valid JOB statement. 2. Replace yourTCPIP.PROFILE.dataset with the name of the TCP/IP profile data set for your system. Consult your local network administrators, if necessary. The job points to your profile.

3. Replace YourEmailAddress with your email address. The job points to your email address.

4. Replace yourUSSESDdirectory with the name of the USS directory that you use for ESD downloads. The job points to your USS directory.

5. Locate the product component to download on the CA Support Product Download window. You have identified the product component to download.

6. Click Download for the applicable file. Note: For multiple downloads, add files to a cart. The Download Method window opens.

7. Click FTP Request. The Review Download Requests window displays any files that you have requested to download. Note: We send you an email when the file is ready to download or a link appears in this window when the file is available.

Chapter 4: Installing Your Product from Pax-Enhanced ESD 33

Copy the Product Pax Files into Your USS Directory

8. Select one of the following methods: Preferred FTP Uses CA Technologies worldwide content delivery network (CDN). If you cannot download using this method, review the security restrictions for servers that company employees can download from that are outside your corporate network. Host Name: ftp://ftpdownloads.ca.com Alternate FTP Uses the original download servers that are based on Long Island, New York. Host Name: ftp://scftpd.ca.com for product files and download cart files and ftp://ftp.ca.com for individual solution files. Both methods display the host, user name, password, and FTP location, which you then can copy into the sample JCL. Note: The following links provide details regarding FTP: the FTP Help document link in the Review Download Requests window and the Learn More link available in the Download Methods window.

9. Submit the job. Important! If your FTP commands are incorrect, it is possible for this job to fail and still return a zero condition code. Read the messages in the job DDNAME SYSPRINT to verify the FTP succeeded. After you run the JCL job, the pax file resides in the mainframe USS directory that you supplied.

34 Installation Guide

Copy the Product Pax Files into Your USS Directory

Example: CAtoMainframe.txt, JCL

The following text appears in the attached CAtoMainframe.txt JCL file:

//GETPAX JOB (ACCOUNTNO),'FTP GET ESD PACKAGE', // MSGCLASS=X,CLASS=A,NOTIFY=&SYSUID //********************************************************************* //* This sample job can be used to download a pax file directly from * //* CA Support Online to a USS directory on your z/OS system. * //* * //* When editing the JCL ensure that you do not have sequence numbers * //* turned on. * //* * //* This job must be customized as follows: * //* 1. Supply a valid JOB statement. * //* 2. The SYSTCPD and SYSFTPD JCL DD statements in this JCL may be * //* optional at your site. Remove the statements that are not * //* required. For the required statements, update the data set * //* names with the correct site-specific data set names. * //* 3. Replace "Host" based on the type of download method. * //* 4. Replace "YourEmailAddress" with your email address. * //* 5. Replace "yourUSSESDdirectory" with the name of the USS * //* directory used on your system for ESD downloads. * //* 6. Replace "FTP Location" with the complete path * //* and name of the pax file obtained from the FTP location * //* of the product download page. * //********************************************************************* //GETPAX EXEC PGM=FTP,PARM='(EXIT',REGION=0M //SYSTCPD DD DSN=yourTCPIP.PROFILE.dataset,DISP=SHR //SYSFTPD DD DSN=yourFTP.DATA.dataset,DISP=SHR //SYSPRINT DD SYSOUT=* //OUTPUT DD SYSOUT=* //INPUT DD * Host anonymous YourEmailAddress lcd yourUSSESDdirectory binary get FTP_location quit

Chapter 4: Installing Your Product from Pax-Enhanced ESD 35

Copy the Product Pax Files into Your USS Directory

Download Files to Mainframe through a PC

If you download pax or zip files from CA Support Online to your PC, use this procedure to upload the pax file from your PC to your z/OS USS directory.

Follow these steps: 1. Follow the procedures in How the Pax-Enhanced ESD Download Works (see page 8) to download the product pax or zip file to your PC. If you download a zip file, first unzip the file to use the product pax files. The pax or zip file resides on your PC. 2. Open a Windows command prompt. The command prompt appears.

3. Customize and enter the FTP commands with the following changes: a. Replace mainframe with the z/OS system IP address or DNS name. b. Replace userid with your z/OS user ID. c. Replace password with your z/OS password. d. Replace C:\PC\folder\for\thePAXfile with the location of the pax file on your PC. e. Replace yourUSSESDdirectory with the name of the USS directory that you use for ESD downloads. f. Replace paxfile.pax.Z with the name of the pax file to upload. The pax file is transferred to the mainframe.

Example: FTP Commands

This list is a sample of FTP commands to upload the pax file from your PC to your USS Pax-Enhanced ESD directory:

ftp mainframe userid password bin lcd C:\PC\folder\for\thePAXfile cd /yourUSSESDdirectory/ put paxfile.pax.Z quit exit

36 Installation Guide

Create a Product Directory from the Pax File

Use the sample job attached to the PDF file as Unpackage.txt to extract the product pax file into a product installation directory.

Follow these steps: 1. Supply a valid JOB statement. 2. Replace yourUSSESDdirectory with the name of the USS directory that you use for ESD downloads. The job points to your specific directory. 3. Replace paxfile.pax.Z with the name of the pax file. The job points to your specific pax file. 4. Submit the job. The job runs and creates the product directory.

Note: If the PARM= statement exceeds 71 characters, uncomment and use the second form of UNPAXDIR instead. This sample job uses an X in column 72 to continue the PARM= parameters to a second line.

Chapter 4: Installing Your Product from Pax-Enhanced ESD 37

Copy Installation Files to z/OS Data Sets

Sample Job to Execute the Pax Command (Unpackage.txt)

The following text appears in the attached Unpackage.txt JCL file:

//ESDUNPAX JOB (ACCOUNTNO),'UNPAX ESD PACKAGE ', // MSGCLASS=X,CLASS=A,NOTIFY=&SYSUID //********************************************************************* //* This sample job can be used to invoke the pax command to create * //* the product-specific installation directory. * //* * //* This job must be customized as follows: * //* 1. Supply a valid JOB statement. * //* 2. Replace "yourUSSESDdirectory" with the name of the USS * //* directory used on your system for ESD downloads. * //* 3. Replace "paxfile.pax.Z" with the name of the pax file. * //* NOTE: If you continue the PARM= statement on a second line, make * //* sure the 'X' continuation character is in column 72. * //********************************************************************* //UNPAXDIR EXEC PGM=BPXBATCH, // PARM='sh cd /yourUSSESDdirectory/; pax -rvf paxfile.pax.Z' //*UNPAXDIR EXEC PGM=BPXBATCH, //* PARM='sh cd /yourUSSESDdirectory/; pax X //* -rvf paxfile.pax.Z' //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=*

Copy Installation Files to z/OS Data Sets

Use this procedure to invoke the SMP/E GIMUNZIP utility to create MVS data sets from the files in the product-specific directory.

Follow these steps: 1. Locate and read the product readme file or installation notes, if applicable, which resides in the product-specific directory that the pax command created. This file contains the product-specific details that you require to complete the installation procedure. You have identified the product-specific installation details.

2. Use ISPF EDIT or TSO ISHELL to edit the UNZIPJCL sample job. You can perform this step in one of the following ways: ■ Use ISPF EDIT. Specify the full path name of the UNZIPJCL file. ■ Use TSO ISHELL. Navigate to the UNZIPJCL file and use the E line command to edit the file. The job is edited.

38 Installation Guide

Receiving the SMP/E Package

3. Change the SMPDIR DD PATH to the product-specific directory created by the pax command. Your view is of the product-specific directory.

4. If ICSF is not active, perform the following steps: a. Change the SMPJHOME DD PATH to your Java runtime directory. This directory varies from system to system. Note: The default Java location is the following:

/usr/lpp/java/Java_version b. Perform one of the following steps: ■ Change the SMPCPATH DD PATH to your SMP/E Java application classes directory, typically /usr/lpp/smp/classes/. ■ Change HASH=YES to HASH=NO on the GIMUNZIP parameter. One of the following occurs: ICSF is active, or you are using Java.

5. Change all occurrences of yourHLQ to the high-level qualifier (HLQ) for z/OS data sets that the installation process uses. We suggest that you use a unique HLQ for each expanded pax file to identify uniquely the package. Do not use the same value for yourHLQ as you use for the SMP/E RELFILEs. All occurrences of yourHLQ are set to your high-level qualifier for z/OS data sets.

6. Submit the UNZIPJCL job. The UNZIPJCL job completes with a zero return code. Messages GIM69158I and GIM48101I in the output and IKJ56228I in the JES log are acceptable. GIMUNZIP creates z/OS data sets with the high-level qualifier that you specified in the UNZIPJCL job. You use these data sets to perform the product installation. The pax file and product-specific directory are no longer needed. Note: For more information, see the IBM SMP/E for z/OS Reference (SA22-7772).

Receiving the SMP/E Package

If you are installing the package into a new SMP/E environment, use the sample jobs included with the product to set up an SMP/E environment before proceeding.

At this point, complete the SMP/E RECEIVE using files on DASD that the UNZIPJCL job created. Consult the product sample JCL library that contains a sample job customized to receive the product from DASD. Specifically, you must specify the following values: ■ DASD data set names for SMPPTFIN and SMPHOLD (if applicable) ■ The HLQ that you used in the UNZIPJCL job on the RFPREFIX parameter on the RECEIVE command

Chapter 4: Installing Your Product from Pax-Enhanced ESD 39

Receiving the SMP/E Package

Prepare the SMP/E Environment

The members in this procedure prepare the data sets, initialize the zones, and create the DDDEFs for CA File Master Plus.

For information about the members, see the comments in the JCL.

To prepare the SMP/E environment for your product 1. Customize the macro FMPSEDIT with your site specific information and then copy the macro to your SYSPROC location. The macro is ready to customize your yourhlq.SAMPJCL members. 2. Open the CAI.SAMPJCL member FMP1HOLD in an edit session and execute the FMPSEDIT macro from the command line. SCM1HOLD is customized.

3. Submit SCM1HOLD. This job downloads the error and FIXCAT HOLDDATA from http://ca.com/support http://ca.com/support.

4. Open the CAI.SAMPJCL member FMP2ALL in an edit session and execute the FMPSEDIT macro from the command line. FMP2ALL is customized. The target and distribution data sets are created.

5. Customize and submit the CAI.SAMPJCL member FMP3CSI. This job produces the following results: ■ The CSI data set is defined. ■ The SMPPTS and SMPLOG data sets are allocated. ■ The global, target, and distribution zones are initialized. ■ The DDDEF entries for your product are created.

Run the Installation Job

Submit and run these SAMPJCL members in sequence. Do not proceed with any job until the previous job has completed successfully.

To run the installation jobs 1. Customize and submit the CAI.SAMPJCL member FMP4RECD. CA File Master Plus is received and now resides in the global zone. 2. Customize and submit the CAI.SAMPJCL member FMP5APP. The base function for your product is applied and now resides in the target libraries.

40 Installation Guide

Clean Up the USS Directory

3. Customize and submit the CAI.SAMPJCL member FMP6ACC. The base function for your product is accepted and now resides in the distribution libraries. 4. (Optional) Delete any other data sets except CAI.SAMPJCL created by the UNZIPJCL job. The applicable data sets are deleted.

Clean Up the USS Directory

Important! This procedure is optional. Do not use this procedure until you complete the entire installation process.

To free file system disk space for subsequent downloads after downloading and processing the pax files for your CA Technologies product, we recommend removing the files from your USS directory and deleting unnecessary MVS data sets. You can delete the following items: ■ Pax file ■ Product-specific directory that the pax command created and all of the files in it ■ SMP/E RELFILEs, SMPMCS, and HOLDDATA MVS data sets These data sets have the HLQ that you assigned in the UNZIPJCL job.

Note: Retain non-SMP/E installation data sets such as yourHLQ.INSTALL.NOTES for future reference.

Follow these steps: 1. Navigate to your Pax-Enhanced ESD USS directory. Your view is of the applicable USS directory. 2. Delete the pax file by entering the following command:

rm paxfile paxfile Specifies the name of the CA Technologies pax file that you downloaded. The pax file is deleted.

Chapter 4: Installing Your Product from Pax-Enhanced ESD 41

Apply Maintenance

3. Delete the product-specific directory by entering the following command:

rm -r product-specific_directory product-specific_directory Specifies the product-specific directory that the pax command created. The product-specific directory is deleted.

Note: You can also use TSO ISHELL to navigate to the pax file and product-specific directory, and delete them using the D line command.

Apply Maintenance

CA Support Online has maintenance and HOLDDATA published since the installation data was created. After the maintenance process completes, the product is ready to deploy.

Follow these steps: 1. Check CA Support Online http://ca.com/support for any PTFs and HOLDDATA published since this release was created. If the base release was created recently, no PTFs or HOLDATA will have been published yet. 2. The FMPSEDIT macro was customized in the installation steps. Verify that you still have the values from the base installation. 3. Download the PTFS from CA Support Online http://ca.com/support, or customize the CAI.SAMPJCL member FMP7CARS to download a CA Recommended Service level.

4. To customize FMP7CARS, open the member in CAI.SAMPJCL and execute the FMPSEDIT macro from the command line. 5. Submit FMP7CARS. The job downloads the CARS PTF file. 6. Update the CAI.SAMPJCL member FMP1HOLD SAMPJCL to receive the HOLDDATA file.

7. Submit FMP1HOLD. The job downloads the external HOLDDATA file. 8. Open the SAMPJCL member FMP7RECH in an edit session and execute the FMPSEDIT macro from the command line. FMP7RECH is customized.

42 Installation Guide

Apply Maintenance

9. Submit FMP7RECH. The job receives the external HOLDDATA file. 10. Open the SAMPJCL member FMP7RECP in an edit session and execute the FMPSEDIT macro from the command line. FMP7RECP is customized with your JOB statement, CSI location, and zone names.

11. Customize the FMP7RECP SMPPTFIN and SMPHOLD DD statements to reference the FB 80 data sets for the PTFs and HOLDDATA. 12. Submit FMP7RECP. The PTFs are received.

13. Open the SAMPJCL member FMP8APYP in an edit session and execute the FMPSEDIT macro from the command line. FMP8APYP is customized. 14. Submit FMP8APYP. The PTFs are applied.

15. (Optional) Open the SAMPJCL member FMP9ACCP in an edit session and execute the FMPSEDIT macro from the command line. FMP9ACCP is customized.

16. (Optional) Submit yourHLQ.SAMPJCL member FMP9ACCP. The PTFs are accepted. Note: You do not have to submit the job at this time. You can accept the PTFs according to your site policy.

HOLDDATA

When you apply maintenance, you typically encounter SMP/E HOLDDATA. We use HOLDDATA to notify your SMP/E system of SYSMODs that have errors or special conditions. We support system and external HOLDDATA.

Chapter 4: Installing Your Product from Pax-Enhanced ESD 43

Accept the Product

Member WA85ACC in CAI.SAMPJCL accepts all the components (functional SYSMODS) of CA File Master Plus to the distribution libraries.

Follow these steps: 1. Edit the JCL to conform to your installation standards and the previously completed worksheet. If other CA Technologies products have been installed some of these functions may have already been accepted. If this is the case, a return code of 12 occurs. 2. Remove the failing SYSMODS and resubmit the job. SMP/E users have the option of specifying the operand REDO on the ACCEPT command statement and should expect an SMP return code of 8, which, in this case, is permissible.

3. Submit the job and review the output to verify that the ACCEPT processing ran successfully. 4. If ACCEPT completed with an SMP return code greater than 4, view the output, correct the problem, and resubmit the job.

We strongly recommend that you accept the CA File Master Plus product immediately after you have successfully run the APPLY process. This ACCEPT step provides a backup of the base product on the distribution libraries. This backup is necessary for future SMP/E restores.

Save Materials and Output

Save all installation materials and installation-generated output so that it is available for your own reference and when contacting customer support.

Note: When you have completed the procedures in this section, go to Configuring Your Product (see page 51).

44 Installation Guide

Chapter 5: Installing the Graphical User Interface

This section describes the tasks needed to install the Graphical User Interface.

This section contains the following topics: Install Mainframe Support for the User Interface (see page 45) Update Mainframe Support for the Eclipse User Interface (see page 48) Install the Workstation User Interface (see page 49)

Install Mainframe Support for the User Interface

The CA File Master Plus user interface provides an Eclipse-based graphical interface.

Mainframe support consists of a CA File Master Plus web server to provide interface support to various mainframe CA File Master Plus facilities. This server consists of three files that support running a job in the z/OS UNIX System Services (USS). The CA File Master Plus server requires IBM 31-bit or 64-bit Java 6.0.1 or later.

The installation and customization of CA File Master Plus must be completed before starting the web server because the web server is dependent on the customization of the CAWAFM REXX EXEC. The name of the data set that contains this EXEC must be specified when customizing the CAWAUOPT member.

The CA File Master Plus Eclipse UI uses multiple address spaces for each user session. Each session launches two addresses spaces that are started as soon as the user connects and begins doing work. Another session is initiated each time a user edits a file, which launches an additional two address spaces. For example, a user who is connected to the Testing Tools web server and has two open edit sessions has six address spaces running.

To install mainframe support for the Eclipse UI, complete the following process: 1. Install Apache Tomcat (see page 46) 2. Install tsocmd (see page 46) 3. Modify Sample JCL Library (see page 47)

Chapter 5: Installing the Graphical User Interface 45

Install Mainframe Support for the User Interface

Install Apache Tomcat

To install the CA File Master Plus Eclipse-based user interface, you must have Apache Tomcat installed in your environment. If you do not already have it installed, follow the procedure for installing the base version of Apache Tomcat from CA Common Service for z/OS v14.0 or later. This base is used to implement specific instances for the Testing Tools server. By default, the Apache Tomcat server is installed to /ca/CADeploy/CCS/tpv/tomcat.

Install the TSO Command

The CA File Master Plus web server that supports the Eclipse user interface is dependent on the USS command tsocmd implemented by IBM in V1R12 and later versions of z/OS. If you want to run the web server on z/OS V1R10 or V1R11, IBM provides a V1R12 version of this command at this web page:

http://www-03.ibm.com/systems/z/os/zos/features/unix/bpxa1ty2.html

Scroll down the list of tools to the one entitled "tsocmd (V1R12 version)" and follow IBM’s instructions.

Note: The links provided use ftp: protocol and may not work with some browsers.

Note: The tsocmd tool will not work on versions earlier than V1R10 so you cannot use this server with older versions of z/OS

46 Installation Guide

Install Mainframe Support for the User Interface

Installing this command requires knowledge of USS and how to configure an executable program in USS. The following instructions assume the server has been deployed and the USS directories created.

Follow these steps: 1. Download tsocmd from the IBM web page and copy it in a USS directory that may be available at web server run time CA Technologies suggests using the same directory as the CA executables. Refer to the CAWADPLY member for the value of $SERVER_DIR (the default is /cai/fmp/server). The location of the file must be $SERVER_DIR/bin/CA (default - /cai/fmp/server/bin/CA). This file is a standard IBM text file and should be readable in the ISPF file browser. 2. Change directory to $SERVER_DIR/bin/CA

cd /cai/fmp/server/bin/CA 3. Change the access mode of tsocmd to 755

chmod 755 tsocmd 4. If your site uses PROGRAM CONTROL , you must also set an extended attribute. This is a controlled command and may require special authorization.

extattr +p tsocmd

Modify the Sample JCL Library

Before modifying any of the members specified below, be sure that you have created runtime versions of the specified libraries, either through MSM deployment or configuration, or by manually creating copies of the libraries. Do not make any modifications to SMP/E controlled libraries.

Follow these steps: 1. Modify CDBIJCL data set member CAWAALOC as described within the JCL and execute to successful completion. This job allocates, initializes, and mounts a CA File Master Plus web server instance file system and creates the starting directory within it. 2. Modify CDBIJCL data set member CAWADPLY as described within the JCL and execute to successful completion. This job deploys the CA File Master Plus server components to the file system allocated by the previous step. You may be required to assign a TCP/IP port number while editing CAWADPLY. The default is 51914. Note: If your site uses PROGRAM CONTROL on the CA File Master Plus LOADLIB then some programs must have the equivalent USS extended attribute set. The command to do this is restricted and may need to be done by a system administrator. The command is included in the script performed by CAWADPLY and is highlighted within this text.

Chapter 5: Installing the Graphical User Interface 47

Update Mainframe Support for the Eclipse User Interface

If this is not needed and you do not have restricted privileges, ignore the error generated. This attribute may not be needed but setting it will do no harm.

3. Modify CDBIOPTN data set member CAWAUOPT as described within the member. This file is used as the input to the server, providing product and runtime directory information. 4. Modify CDBIPROC data set member CAWASRVR to your site standards and copy to a system procedure library. This is the JCL used to start the CA File Master Plus server. Note: The owner of the CAWASRVR job requires read access to the following IBM BPX facilities: BPX.DAEMON.HFSCTL, BPX.FILEATTR.APF, BPX.FILEATTR.PROGCTL, and BPX.SERVER. 5. Submit the CAWASRVR procedure to start the server.

Note: Users of the web server must have authorization to use OMVS (USS) services. All server requests from the Eclipse UI are performed using the requesting user’s mainframe credentials; hence, users must have access authorization for the related data sets. 6. Use a browser and access http://host:port/filemaster/status to test if the server is running correctly. The output is an xml file displaying various version values.

Update Mainframe Support for the Eclipse User Interface

You will receive updates to the CA File Master Plus web server and the Eclipse UI interface. The updates are implemented by repeating the deploy step described previously. Use the following steps for a successful update. 1. Stop the web server using the MVS console STOP command 2. When the server has stopped, run the modified CAWADPLY job

3. When the CAWADPLY job has finished restart the server. All updates for the server will be implemented.

All changes for the Eclipse UI are published in the software directory. http://host:port/software.

48 Installation Guide

Install the Workstation User Interface

The web server must be running to install the Eclipse UI software. The install image is available from the web server. Use a web browser and access http://hostname:port/software (substitute your hostname system name and the port defined in CAWADPLY). The web page provides the steps to complete the install process.

You can launch the CA File Master Plus user interface using the shortcut on the Start All Programs dialog, under CA/File Master Plus 9.0.

Note: When you have completed the procedures in this section, go to Configuring Your Product (see page 51).

Chapter 5: Installing the Graphical User Interface 49

Chapter 6: Configuring Your Product

This section describes the minimum configuration tasks needed before CA File Master Plus can be started, customized, and used in your environment.

This section contains the following topics: Allow Function Commands from ISPF Data Set Lists (Optional) (see page 52) Customize Options (Optional) (see page 53) Customize Batch JCL (Optional) (see page 59) Add CA ACF2 Security for z/OS User Considerations (Optional) (see page 59) Customize Wildcard Exit CAWAWDSN (Optional) (see page 60)

Chapter 6: Configuring Your Product 51

Allow Function Commands from ISPF Data Set Lists (Optional)

You can provide function commands to ISPF users on their data set lists even when you are using LIBDEFS through the LIBALLOC = Y statement in the CAWAFM EXEC.

Follow these steps: 1. Allocate the SYSEXEC or SYSPROC DD statements in your TSO procedure. 2. Use the sample JCL in member CAWAFUNJ in CAI.CDBIJCL to copy members to your system’s SYSEXEC and SYSPROC datasets. 3. Use the following REXX EXECs to invoke the commands using an ISPF data set list: ■ FM1 - Browse ■ FM2 - Edit ■ FM31 - Library Utility ■ FM310 - Data Set Compare ■ FM311 - Data Set Reformat ■ FM32 - Data Set Utility ■ FM33 - Copy Utility ■ FM361 - Locate PDS ■ FM362 - Compress PDS ■ FM363 - Update PDS Allocation ■ FM364 - Recover PDS Deleted Members ■ FM37 - VSAM Utility ■ FM38 - Search ■ FM39 - Update ■ FM4 - Print Data Set ■ FM6 - Record Layout

52 Installation Guide

Customize Options (Optional)

The CAWAOPT macro can optionally be used to specify the default processing options for CA File Master Plus batch and online product components. This section provides a description of the CAWAOPT keywords.

Options that are common to both batch and online processing begin with the characters COM_. Batch processing option keywords begin with the characters BAT_ and online processing options begin with ONL_.

Member CAWAOPTJ of CAI.CDBIJCL contains JCL to compile and link the CAWAOPT macro. Valid keywords for the CAWAOPT macro are listed following.

Use the following keywords when you want to change the default:

CAWAOPT BAT_CLOSEIN=Y BAT_CLOSEOUT=Y BAT_COMPDIFF=0 BAT_COMPRC=4 BAT_EMPTYRC=4 BAT_INFILE=SYSUT1 BAT_LAYOUTRC=4 BAT_LINEPAGE=60 BAT_LOADLIB=LOADLIB BAT_NEWFILE=SYSUT1N BAT_NOSELRC=4 BAT_OLDFILE=SYSUT1 BAT_RDW=N BAT_SYNCLIM=50 BAT_TRUNCRC=4 ONL_CLOGDSN=%USERID.FMMVS.CHANGE.%LOGN ONL_CLOGFOR=N ONL_CLOGSPA=(0,0) ONL_CMDCHAIN=Y ONL_CONFDSND=Y ONL_CONFMEMD=Y ONL_CONFPCD=Y ONL_DASDUNIT=SYSDA ONL_MAXCYLS=0 ONL_STORCLAS=name ONL_SYSOUTCX=1 ONL_SYSOUTCL=A

Chapter 6: Configuring Your Product 53

Customize Options (Optional)

Parameter Descriptions

For details of CAWOPT parameter keywords, see the following sections: BAT_CLOSEIN=Y Controls the closing of the input file among multiple commands in the same execution. Valid values are N or Y. When N is specified, the input file is not closed at the end of a command. The next command (in the same batch execution) starts processing the input file from the current record position. When Y is specified, the input file is closed at the end of each command. The operands INFILE, OLDFILE and NEWFILE specify the input files affected by this parameter. The default value is Y. To override this parameter, you can use the CLOSE/NOCLOSE parameter values on the operands INFILE, OLDFILE, and NEWFILE.

BAT_CLOSEOUT=Y Controls the closing of the output file among multiple commands in the same execution. Valid values are N or Y. When N is specified, the output file is not closed at the end of a command, and the next command (in the same batch execution) starts processing the output file from the current record position. When Y is specified, the output file is closed at the end of each command. The OUTFILE operand specifies the output files affected by this parameter. The default value is Y. To override this parameter, you can use the CLOSE/NOCLOSE parameter values on the OUTFILE operand.

BAT_COMPDIFF=0 The maximum number of COMPARE command mismatches allowed before the COMPARE command is prematurely terminated. Valid values are 0 through 99999. The default value is zero. The value zero indicates there is no limit to the number of compare mismatches that can occur during a COMPARE command. To override this parameter, use the operand COMPDIFF on a COMPARE command.

BAT_COMPRC=4 The return code set when, during a COMPARE command, one or more unequal records are encountered. Valid values are 0 through 4095. The default value is 4. To override this parameter, use the operand COMPRC on a COMPARE command.

BAT_EMPTYRC=4 When processing a command and an empty input file is encountered, this parameter controls the return code that is set for the condition/error. Valid values are 0 through 4095. The default value is 4. To override this parameter, use the operand EMPTYRC on a batch command.

54 Installation Guide

Customize Options (Optional)

BAT_INFILE=SYSUT1 The default DDNAME used by the batch commands for the input file. Valid values are any valid DDNAME. The default is SYSUT1. To override this parameter, use the operand INFILE on a batch command.

BAT_LAYOUTRC=4 When the LAYOUTFILE parameter is specified on any command and the record layout data set or member is not found, this parameter controls the return code that is set for this error. Valid values are 0 through 4095. The default value is 4. To override this parameter, use the operand LAYOUTRC operand on a batch command.

BAT_LINEPAGE=60 Controls the number of lines printed per page on the SYSLIST and SYSPRINT data sets. Valid values are 10 through 99. The default value is 60. To override this parameter, use the operand LINEPAGE on a batch command.

BAT_LOADLIB=LOADLIB The default DDNAME used by the batch command LOADINFO for the input file. Valid values are any valid DDNAME. The default is LOADLIB. To override this parameter, use the operand LOAD on a batch command.

BAT_NEWFILE=SYSUT1N The default DDNAME used by the COMPARE command for one of the two files to compare. Valid values are any valid DDNAME. The default is SYSUT1N. To override this parameter, use the operand NEWFILE on a batch COMPARE command.

BAT_NOSELRC=4 When record selection criteria is specified on a batch command and no input records are found that match the selection criteria, this parameter controls the return code that is set for this condition/error. Valid values are 0 through 4095. The default value is 4. To override this parameter, use the operand NOSELERC on a batch command.

BAT_OLDFILE=SYSUT1 The default DDNAME used by the batch COMPARE command for one of the two files to compare. Valid values are any valid DDNAME. The default is SYSUT1. To override this parameter, use the operand OLDFILE on a batch COMPARE command.

Chapter 6: Configuring Your Product 55

Customize Options (Optional)

BAT_RDW=N The default RDW keyword used by batch commands. This option controls the inclusion of the 4-byte record descriptor word of variable-length records in record positions 1 - 4. The first 2 bytes of the RDW contain the record length + the length of the RDW, which is 4. This value is in hex. Bytes 3 and 4 contain low-values. Valid values are Y, N. With RDW(Y), the RDW is made available to the current batch command and its keywords. For example, it is available to move to a specific position within a record, to query its value, or even compare it to another RDW. The RDW is made available to the current command and its keywords. For example, it is available to move to a specific position within a record, to query its value, or even compare it to another RDW. The default is N. To override this parameter, use the RDW operand on the batch command.

BAT_SYNCLIM=50 When two records are found to be unequal during a COMPARE command, this parameter controls the maximum number of records that are read from the OLD and NEW files before a true mismatch (unequal) condition is raised. Valid values are 0 through 999. The default value is 50. To override this parameter, use the SYNCLIM operand on a COMPARE command.

BAT_TRUNCRC=4 Controls the return code set, when one or more records are truncated during a COPY command, for the COPY command that encountered the truncation. Valid values are 0 through 4095. The default value is 4. To override this parameter, use the TRUNCRC operand on a COPY command.

56 Installation Guide

Customize Options (Optional)

ONL_CLOGDSN=%USERID.FMMVS.CHANGE.%LOGN Specifies the name for the Change Log data set used during a CA File Master Plus MVS Edit session. You can use any of the following additional variables to create a unique data set name: ■ %DATE—date of edit session in DYYMMDD format ■ %LOGN—represents the nth log file in Lnnnnnnn format ■ %PREFIX—the prefix for the edit session ■ %SYSNAME—LPAR on which the edit session takes place ■ %TIME—time of the edit session in THHMMSS format ■ %USERID—the user ID of the user making the edits Specify the name of the Change Log DSN using any of these variables with - or instead of - any other valid DSN node name. The default value is %USERID.FMMVS.CHANGE.%LOGN. This value cannot be overridden by a File Master Plus user.

ONL_CLOGFOR=N Specifies whether the Change Log is activated for each CA File Master Plus session. Valid values are Y, N. The default value is N. When set to N, a File Master Plus user can override this value using option 2. When set to Y, this value cannot be overridden.

ONL_CLOGSPA=(0,0) Specifies the primary and secondary cylinder allocations for the Change Log data set. Valid values are Y, N. These values reset any preexisting values each time a user accesses CA File Master Plus when ONL_CLOGFOR=Y. The default value is (0,0). To override this parameter, use CA File Master Plus option 0.5.

ONL_CMDCHAIN=Y Specifies the default for the online ISPF "Use '=' to jump within CA product?" option. Valid values are Y,N. When this parameter is set to Y, an ISPF command of =3.6 would jump to CA File Master Plus option 3.6 to option (the PDS Utility Submenu) instead of ISPF option 3.6. When this parameter is set to N, an ISPF command of =3.6 would jump to the ISPF option 3.6. The default value is Y. To override this parameter, use CA File Master Plus option 0.1.

COM_CODEPAGE=ENGLISH Specifies the default code page for online and batch. Valid values are ENGLISH, CZECH, FRENCH, GERMAN, ITALIAN, SPANISH, or THAI. The default value is ENGLISH.

Chapter 6: Configuring Your Product 57

Customize Options (Optional)

ONL_CONFDSND=Y Specifies the default for the online ISPF "Confirm data set deletes?" option. Valid values are Y, N.. When Y is specified, a confirmation screen is displayed before performing an online delete for any data set. The confirmation screen gives you the opportunity to either proceed with the data set delete or to bypass the delete. When N is specified, online deletes of any data set are performed without confirmation. The default value is Y. To override this parameter, use CA File Master Plus option 0.1.

ONL_CONFMEMD=Y Specifies the default for the online ISPF "Confirm member deletes?" option. Valid values are Y, N. When Y is specified, a confirmation screen is displayed before performing an online delete of any PDS member. The confirmation screen gives you the opportunity to proceed with the member delete or bypass the delete. When N is specified, online deletes of any PDS member are performed without confirmation. The default value is Y. To override this parameter, use CA File Master Plus option 0.1.

ONL_CONFPCD=Y Specifies the default for the online ISPF "Confirm print class and destination?" option. Valid values are Y, N. When Y is specified, a confirmation screen is displayed before requesting print online and before submitting a batch job that requests print. This confirmation screen presents the SYSOUT class and the destination parameters that have been defined using the Print Output Control Parms Screen. When N is specified, print requests are routed to the SYSOUT class and destination defined to the Print Output Control Parms Screen. The default value is Y. To override this parameter, use CA File Master Plus option 0.1.

ONL_DASDUNIT=SYSDA Defines the DASD Unit Name used to allocate workspace data sets required by the CA File Master Plus product. When a DASD Unit Name is specified, these data sets are allocated on volumes associated with the specified unit. Examples of common DASD Unit Name are SYSDA, DASD, and SYSALLDA. To control the volumes on which workspace data sets are allocated, specify either the ONL_DASDUNIT parameter or the ONL_STORCLASS parameter but not both. The default value is SYSDA. To override this parameter, use CA File Master Plus option 0.1.

58 Installation Guide

Customize Batch JCL (Optional)

ONL_MAXCYLS=0 Specifies the number of cylinders for the maximum size of workspace data sets allocated CA File Master Plus. Valid values are 0 through 99999. If 0 is specified, no limit is placed on the size of workspace data sets. The default is 0. To override this parameter, use the 'Size in Cylinders' field on the CA File Master Plus option 0.1 screen.

ONL_STORCLAS=name For SMS-managed workspace data sets, this parameter specifies the SMS Storage Class used to allocate workspace data sets required by the CA File Master Plus product. To control the volumes on which workspace data sets are allocated, specify either the ONL_DASDUNIT parameter or the ONL_STORCLAS parameter but not both. When ONL_STORCLAS is specified, there is no default for ONL_DASDUNIT. To override this parameter, use CA File Master Plus option 0.1.

ONL_SYSOUTC#=1 Specifies the default for the online ISPF Print Output control parameters COPIES= parameter for online print requests. Valid values are 1 through 999. The default value is 1. To override this parameter, use CA File Master Plus option 0.2.

ONL_SYSOUTCL=A Specifies the default for the online ISPF Print Output control parameters SYSOUT class to which online print is routed. Valid values are any valid JES SYSOUT class. The default value is A. To override this parameter, use CA File Master Plus option 0.2.

Customize Batch JCL (Optional)

Member CAWABAT in CAI.CDBIJCL contains sample JCL for invoking the CA File Master Plus batch function. Modify this JCL and use it to run CA File Master Plus batch jobs.

Add CA ACF2 Security for z/OS User Considerations (Optional)

If you use CA ACF2 and the TSO Command Limiting function, add the CA File Master Plus commands to the restricted commands list for any TSO users who use the CA File Master Plus ISPF interface.

Follow these steps: 1. Open member CAWAACF2 in CAI.CDBISAMP. 2. Add the $TSOCMDS statements to all applicable CA ACF2 restricted commands lists.

Chapter 6: Configuring Your Product 59

Customize Wildcard Exit CAWAWDSN (Optional)

Member CAWAWDSN in CAI.CDBIEXEC contains the default disallowed wildcard mask entries. By default, CAWAWDSN disallows any mask that begins with either *, *., **. or a first node that contains all percent signs (%).

When the ISPF component of CA File Master Plus encounters a disallowed wildcard mask, error message CAWA011E displays and the data sets matching the disallowed wildcard mask do not display. Verify that CAWAWDSN is available to the ISPF component of CA File Master Plus.

Valid CAWAWDSN Return Values: NO or YES NO (Default) CA File Master Plus does not process the wildcard mask and displays error message CAWA011E: YES CA File Master Plus processes the wildcard mask and displays the matching data sets.

If the default restrictions meet your site requirements, no action is needed. If the restrictions are not acceptable to your site, customize CAWAWDSN to your site requirements.

Follow these steps: 1. Copy CAWAWDSN from the target cai.CDBIEXEC. 2. Make your changes. 3. Install it as an SMP USERMOD.

60 Installation Guide

Chapter 7: Prepare to Start Your CA File Master Plus

When the following procedures are complete, you are ready to start CA File Master Plus.

This section contains the following topics: Allocate PARMLIB Partitioned Data Sets (see page 61) Evaluate the REXX Environment (see page 62) Customize REXX EXEC (see page 63) Add Option Name to an ISPF Menu Panel (Optional) (see page 63) Add ISPF Libraries to TSO LOGON Procedure (Optional) (see page 64)

Allocate PARMLIB Partitioned Data Sets

Member CAWAALC1 in CAI.CDBIJCL creates the installation default parmlib PDS files for the online component of CA File Master Plus.

Depending on your site requirements, CA File Master Plus users can update all of these data sets.

Follow these steps: 1. Edit the JCL to conform to your installation standards. 2. Submit the job. 3. Review to verify the output.

You successfully allocated the files.

Chapter 7: Prepare to Start Your CA File Master Plus 61

Evaluate the REXX Environment

Member CAWAXREX in the CDBISAMP library is a sample REXX EXEC that evaluates the minimum REXX environment this product requires.

Follow these steps: 1. Modify the INSTPRE variable in the CAWAXREX EXEC to the high-level qualifier of the installed product libraries. 2. From an ISPF command line, issue the command:

TSO EXEC 'hlq.CDBISAMP(CAWAXREX)' The following message appears when the REXX environment meets the minimum requirements:

******************************************************************** *** File Master requires REXX to be at release level x.xx or higher. *** Your current version of REXX is release x.xx date mm/dd/yyyy.

*** Your version of REXX meets the minimum requirements *** for the File Master product.

If there is an environment problem, you receive messages similar to the following indicating the problem:

******** WARNING ******** *** IBM'S REXX Alternate Library is not available on your system. *** Follow the instructions in the Installation Guide to load down the *** REXX Alternate Library.

*** There were no entries in the compiler programming table - IRXCMPTM

*** The EAGRTPRC program in the REXX SEAGALT library is not available *** on the system. 3. If these warning messages appear, download the current REXX alternate library from IBM: a. Go to website www.ibm.com/support. b. Search for REXX Alternate Library under the Search All Support text. A list of products and packages displays. c. Select IBM Alternate Library for REXX on zSeries Version x.x.x for use with z/OS from the list. d. Follow the instructions on the alternate library for REXX downloadable files page.

62 Installation Guide

Customize REXX EXEC

Member CAWAFM in CAI.CDBISAMP is a sample REXX EXEC that: ■ Invokes the Main Menu ■ Optionally allocates the product ISPF data sets for the online component

Follow the instructions in the EXEC to customize it to meet your installation standards.

The CAWAFM REXX EXEC must exist in any data set allocated to SYSEXEC or SYSPROC.

Follow these steps: ■ To allocate the required data sets without using LIBDEFs when invoking CA File Master Plus in TSO: 1. Change the LIBALLOC = Y statement to LIBALLOC = N. 2. Follow the instructions in the step. 3. Add CA File Master Plus ISPF libraries to the TSO logon procedure. ■ Tell the product not to generate a STEPLIB DD statement for any of the online EDIT and SUBMIT JCL options: – Change the STEPLIB = Y statement to STEPLIB = N.

Add Option Name to an ISPF Menu Panel (Optional)

Use the following steps to invoke CA File Master Plus from an ISPF panel using an option name of FM.

Follow these steps: 1. Add this statement to an ISPF menu panel in the processing section of the panel.

)PROC FM,'CMD(%FMDB2EX)', )END 2. Change the option name to an appropriate name for your environment.

Chapter 7: Prepare to Start Your CA File Master Plus 63

Add ISPF Libraries to TSO LOGON Procedure (Optional)

This step is needed only if LIBALLOC in the CAWAFM REXX EXEC was set to LIBALLOC=N. (See Customize REXX EXEC (see page 63).)

Follow these steps: 1. If you specified LIBALLOC=N, concatenate the ISPF libraries to the IBM ISPF libraries in the TSO logon PROC.

The following example shows where to add the ISPF libraries:

//ISPLLIB DD DISP=SHR,DSN= // DD DISP=SHR,DSN=CAI.CDBILOAD //ISPMLIB DD DISP=SHR,DSN=...... // DISP=SHR,DSN=CAI.CDBIMSG0 //ISPPLIB DD DISP=SHR,DSN=...... // DISP=SHR,DSN=CAI.CDBIPNL0 //ISPSLIB DD DISP=SHR,DSN=...... // DISP=SHR,DSN=CAI.CDBISKL0 //ISPTLIB DD DISP=SHR,DSN=...... // DISP=SHR,DSN=CAI.CDBITBL0 //SYSPROC DD DISP=SHR,DSN=...... // DISP=SHR,DSN=CAI.CDBIEXEC The next step is necessary only if the COBOL runtime library required to run CA File Master Plus is not available in your system library concatenation. 2. Add the COBOL runtime library required to run CA File Master Plus to the ISPF load library concatenation. For example:

//ISPLLIB DD DISP=SHR,DSN=...... // DISP=SHR,DSN=cobol.runtime.library

64 Installation Guide

Chapter 8: Migration Information

This section contains the following topics: Migrate Installation Packages Downloaded External to CA MSM (see page 65)

Migrate Installation Packages Downloaded External to CA MSM

If you have acquired product pax files by means other than through CA MSM, you can add information about these product installation packages to CA MSM from the Software Catalog tab.

Migrating these packages to CA MSM provides a complete view of all your product releases. After a package is migrated, you can use CA MSM to install the product.

Follow these steps: 1. Click the Software Catalog tab, and click Insert New Product. Note: A product not acquired from the CA Support Online website does not appear in Software Catalog until you perform this step. An entry is added for the product. 2. Select the product gen level (for example, SP0 or 0110) for which the package applies. The packages for the gen level are listed.

3. Click the Add External Package button. You are prompted to enter a path for the package. 4. Specify the USS path to the package you want to migrate, and click OK. Information about the package is saved in the CA MSM database. Note: To see the added package, refresh the page.

Chapter 8: Migration Information 65