CA Deliver™

Installation Guide
Version 12.0
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 © 2012 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 11®
■ CA ACF2™
■ CA Common Services
■ CA Mainframe Software Manager (CA MSM)
■ CA Roscoe®
■ CA Top Secret® for z/OS
■ CA View™

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 11
Audience .................................................................................................................................................................... 11
How the Installation Process Works........................................................................................................................... 11
Installation Considerations ................................................................................................................................. 13
First Time Installation or Upgrade .............................................................................................................................. 14

Chapter 2: Preparing for Installation 15

Hardware Requirements ............................................................................................................................................ 15
Supported Operating Systems ............................................................................................................................ 15
CA Deliver Target Libraries .................................................................................................................................. 15
CA Deliver Distribution Libraries ......................................................................................................................... 16
EBC Distribution Libraries.................................................................................................................................... 17
Software Requirements ............................................................................................................................................. 17
Common Component SYSMODs ......................................................................................................................... 17
CA Deliver Components ...................................................................................................................................... 17
CA Common Services Component ...................................................................................................................... 18
CA Common Services Requirements .......................................................................................................................... 18
CA Common Services Installation Considerations............................................................................................... 18
CAIRIM ................................................................................................................................................................ 18
CA LMP ................................................................................................................................................................ 19
Library Authorization ................................................................................................................................................. 19
Security Requirements ............................................................................................................................................... 20
Storage Requirements ................................................................................................................................................ 20
Other Requirements................................................................................................................................................... 20
SVC Dump Data Sets............................................................................................................................................ 20
JCL Procedures .................................................................................................................................................... 21
Concurrent Releases .................................................................................................................................................. 22
Relationship between Versions of CA View and CA Deliver ....................................................................................... 23

Chapter 3: Installing Your Product Using CA MSM 25

How to Use CA MSM: Scenarios ................................................................................................................................. 25
How to Acquire a Product ................................................................................................................................... 25
How to Install a Product ...................................................................................................................................... 26
How to Maintain Existing Products ..................................................................................................................... 27
How to Deploy a Product .................................................................................................................................... 28
How to Configure a Product ................................................................................................................................ 29

Contents 5
Access CA MSM Using the Web-Based Interface ....................................................................................................... 30

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

How to Install a Product Using Pax-Enhanced ESD .................................................................................................... 31
How the Pax-Enhanced ESD Download Works ................................................................................................... 33
ESD Product Download Window ......................................................................................................................... 33
USS Environment Setup ...................................................................................................................................... 36
Allocate and Mount a File System .............................................................................................................................. 37
Copy the Product Pax Files into Your USS Directory .................................................................................................. 40
Download Using Batch JCL .................................................................................................................................. 41
Download Files to Mainframe through a PC ....................................................................................................... 44
Create a Product Directory from the Pax File ............................................................................................................ 45
Sample Job to Execute the Pax Command (Unpackage.txt) ............................................................................... 46
Copy Installation Files to z/OS Data Sets .................................................................................................................... 46
Receive the SMP/E Package ....................................................................................................................................... 47
How to Install Products Using Native SMP/E JCL ................................................................................................ 48
Prepare the SMP/E Environment for Pax Installation ......................................................................................... 48
Run the Installation Jobs for a Pax Installation ................................................................................................... 50
Clean Up the USS Directory ........................................................................................................................................ 51
Apply Maintenance .................................................................................................................................................... 52
HOLDDATA .......................................................................................................................................................... 53

Chapter 5: Installing Your Product from Tape 57

Unload the Sample JCL from Tape ............................................................................................................................. 58
How to Install Products Using Native SMP/E JCL ....................................................................................................... 59
Prepare the SMP/E Environment for Tape Installation ....................................................................................... 59
Run the Installation Jobs for a Tape Installation ................................................................................................. 61
Apply Maintenance .................................................................................................................................................... 62
HOLDDATA .......................................................................................................................................................... 63

Chapter 6: Installing Your Product from DVD 67

Overview .................................................................................................................................................................... 67
Purpose ............................................................................................................................................................... 67
Audience ............................................................................................................................................................. 67
Frequently Asked Questions ............................................................................................................................... 67
CA Product Documentation ................................................................................................................................ 70
Introduction to Electronic Software Delivery ............................................................................................................. 70
What is Electronic Software Delivery? ................................................................................................................ 70
Pax-Enhanced ESD Procedures ................................................................................................................................... 73
How to Install a Product from a DVD Using Pax-Enhanced ESD .......................................................................... 73

6 Installation Guide
 The Installation Procedure .................................................................................................................................. 73
References .................................................................................................................................................................. 77
IBM Reference Manual ....................................................................................................................................... 77
Common USS Commands.................................................................................................................................... 77

Chapter 7: Starting Your Product 79

How to Complete Deployment With CA MSM ........................................................................................................... 79
How to Complete Configuration With CA MSM ......................................................................................................... 79
Authorize Program Load Libraries ....................................................................................................................... 79
Enter the LMP Code ............................................................................................................................................ 80
Define Security Rules .......................................................................................................................................... 83
Install the ISPF Online Retrieval Option .............................................................................................................. 83
Install the TSO Online Retrieval Option .............................................................................................................. 89
Install the CA Roscoe Online Retrieval Option .................................................................................................... 90
Install the XMS Online Interfaces (Optional)....................................................................................................... 91
How to Configure Without CA MSM .......................................................................................................................... 91
Step 1: Authorize Program Load Libraries ........................................................................................................... 91
Step 2: Enter the LMP Code ................................................................................................................................ 92
Step 3: Define Security Rules .............................................................................................................................. 95
Step 4: Create/Update the Database .................................................................................................................. 95
Step 5: Create the Initialization Parameter Statements ..................................................................................... 96
Step 6: Modify the Skeleton JCL .......................................................................................................................... 96
Step 7: Load the Online Panels and JCL Library................................................................................................... 97
Step 8: Load the Model Banner Pages and Email Format (EFORMAT) members ............................................... 99
Step 9: Add the Start Procedure to PROCLIB .................................................................................................... 100
Step 10: (Optional) Maintain Detail History with JES2 ...................................................................................... 101
Step 11: (Optional) Maintain Detail History with JES3 ...................................................................................... 103
Step 12: Set Up for Multiple CPUs .................................................................................................................... 103
Step 13: (Optional) Construct the Initial Report and Job Data.......................................................................... 105
Step 14: Set Up the Viewing Interface .............................................................................................................. 105
Step 15: (Optional) Install User Exits and Authorization Tables........................................................................ 106
Step 16: (Optional) Install Optional Online Interfaces ...................................................................................... 107
Step 17: (Optional) Install Optional Features .................................................................................................... 107

Chapter 8: Migration Information 109

Migration Considerations ......................................................................................................................................... 109
Upgrading from CA Deliver Release 11.5, Release 11.6, and Release 11.7 ............................................................. 109
Installation Steps for Upgrading to Version 12.0 .............................................................................................. 110
Configuration Steps to Upgrade to CA Deliver Version 12.0 without CA MSM ................................................ 111

Contents 7
Chapter 9: Reverting to a Prior Installation 115
Revert to Release 11.7 ............................................................................................................................................. 115
Reverting to Release 11.6 ........................................................................................................................................ 115
Reverting to Release 11.5 ........................................................................................................................................ 116

Chapter 10: Installing Online Interfaces 117

How to Complete Configuration of the XMS Online Interfaces With CA MSM ........................................................ 117
Define Security Requirements .......................................................................................................................... 117
Install the ISPF/Cross-Memory Online Retrieval Option ................................................................................... 118
Install the TSO/Cross-Memory Online Retrieval Option ................................................................................... 125
Install the VTAM Online Retrieval Option ......................................................................................................... 127
Install the CA Roscoe/Cross-Memory Online Retrieval Option ......................................................................... 131
Install the CICS Pseudo-Conversational Option ................................................................................................ 133
Install the IMS Online Retrieval Option ............................................................................................................. 141
Optional Initialization Parameter Statements .................................................................................................. 146
How to Configure the Online Interfaces Without CA MSM ..................................................................................... 146
Online Interfaces ............................................................................................................................................... 147
Cross-Memory Services Interface (XMS) ........................................................................................................... 147
Cross-Memory Drivers for Interfaces ................................................................................................................ 148
Install the ISPF Online Retrieval Option ............................................................................................................ 149
Install the TSO Online Retrieval Option ............................................................................................................ 155
Install the CA Roscoe Online Retrieval Option .................................................................................................. 155
Install Cross-Memory Services .......................................................................................................................... 157
Install the ISPF/Cross-Memory Online Retrieval Option ................................................................................... 176
Install the TSO/Cross-Memory Online Retrieval Option ................................................................................... 183
Install the VTAM Online Retrieval Option ......................................................................................................... 185
Install the CA Roscoe/Cross-Memory Online Retrieval Option ......................................................................... 189
Install the CICS Pseudo-Conversational Option ................................................................................................ 191
Install the IMS Online Retrieval Option ............................................................................................................. 202
TSO, ISPF, CA Roscoe and Cross-Memory Address Spaces ............................................................................... 206
Multiple Cross-Memory Region Requirements ................................................................................................. 207
Prepare to Start the Cross Memory Task ................................................................................................................. 208
Start the Cross Memory Task ................................................................................................................................... 208

Chapter 11: Installing the Features 209

Change the Date Format Shown on Panels .............................................................................................................. 209
Set Up the CA 11 Interface ....................................................................................................................................... 211
Data Set Attributes ............................................................................................................................................ 211
Data Set Statements ......................................................................................................................................... 212
Syntax of Control Statements in the Data Set ................................................................................................... 212

8 Installation Guide
Set Up CA 11 to Run with CA Deliver........................................................................................................................ 212
Install the Host Command Environment into CA GSS .............................................................................................. 214

Appendix A: Installation Worksheets 215

Installation Worksheet ............................................................................................................................................. 215
Step 1: Global Install Parameters ...................................................................................................................... 215
Step 2: Data Set Qualifiers and SMP Parameters .............................................................................................. 215
Initialization Parameter Worksheet ......................................................................................................................... 216
Started Task Worksheet ........................................................................................................................................... 219
Initialization Parameter ..................................................................................................................................... 219
Job Name Translation Control ........................................................................................................................... 219

Appendix B: Integration with CA OPS/MVS EMA 221

Overview .................................................................................................................................................................. 221
Ensure that CA OPS/MVS Is Enabled for Capturing These Events ............................................................................ 222
CA Deliver Active State Events ................................................................................................................................. 222
CA Deliver Heartbeat Events .................................................................................................................................... 224

Index 227

Contents 9
Chapter 1: Overview
This guide describes how to install and implement CA Deliver.

This section contains the following topics:

Audience (see page 11)
How the Installation Process Works (see page 11)
First Time Installation or Upgrade (see page 14)

Audience
This guide is targeted to the systems programmer who installs, uses, and maintains CA
Deliver.

This guide assumes you are familiar with CA Deliver, CA View, and IBM computer system
terms and concepts. You should also have a working knowledge of MVS online facilities
such as ISPF, because the CA Deliver panels behave in a similar fashion.

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.

Chapter 1: Overview 11
How the Installation Process Works

To install your product, do the following tasks:

1. Prepare for the installation by confirming that your site meets all installation
requirements (see page 15).
2. Use one of the following methods to acquire the product:
■ Download the software from CSO using CA MSM (see page 25).
■ Download the software from CSO using Pax-Enhanced Electronic Software
Delivery (ESD) (see page 31).
■ Order a tape or a DVD.
3. Perform an SMP/E installation using one of the following methods:
■ If you used CA MSM to acquire the product, start the SMP/E step from the
SMP/E Environments tab in CA MSM.
■ If you used ESD to acquire the product, you can install the product in the
following ways:
– Install the product manually.
– Use the Insert New Product option in CA MSM to complete the SMP/E
installation.
■ If you used a tape (see page 57) or DVD, install the product manually.
Note: If a CA Recommended Service (CA RS) package is published for your product,
install it before continuing with deployment.
4. Deploy the target libraries using one of the following methods:
■ If you are using CA MSM, deployment is required; it is a prerequisite for
configuration.
■ If you are using a manual process, deployment is an optional step.
Note: Deployment is considered part of starting your product (see page 79).
5. Configure your product using CA MSM or manually.
Note: Configuration is considered part of starting your product (see page 79).

12 Installation Guide
 How the Installation Process Works

Installation Considerations
Before you begin the installation, you must prepare your system, assemble your
materials, and then follow the installation steps exactly and in order. Use this list as a
guide for the installation process.
1. Be certain that CA Common Services are installed on your system, and that the
required hardware, software, and libraries are prepared.
CA Deliver uses the CAI Resource Initialization Manager CAIRIM portion of the CA
Common Services. CAIRIM prepares the operating system for CA products and
components, and then executes them.
CA DRAS requires the CAIENF (Event Notification Facility) and the CAICCI (Common
Communications Interface) components of the CA Common Services.
Note: For more information about system requirements, see the chapter "System
Requirements".
2. Install CA Deliver using one of these methods:
– CA MSM
– PAX Enhanced ESD
– Product Tape installation
3. Use options and initialization parameters to customize CA Deliver according to the
needs of your site, as follows:
■ Configure your CA Deliver system.
■ Install the online interfaces including the cross-memory and online retrieval
options for ISPF, TSO, VTAM, CA Roscoe Interactive Environment (CA Roscoe),
CICS and IMS.
■ Install the features

More information:

Installing Online Interfaces (see page 117)

Installing the Features (see page 209)

Chapter 1: Overview 13
First Time Installation or Upgrade

First Time Installation or Upgrade

Use the tasks presented in this chapter, and in the Installing Online Interfaces and
Installing Features sections of the "Configuring Your Product" chapter. These tasks are
valid whether you are installing CA Deliver Version 12.0 for the first time or upgrading
from a prior release, as follows:
■ If you are installing for the first time, perform:
All steps in this chapter as indicated, and the tasks in the Installing Online Interfaces
and Installing Features chapters to install the optional online interfaces and
features appropriate for your site.
■ If you are upgrading from a prior release, perform:
All steps as indicated and the tasks in the "Configuring Your Product," "Installing
Online Interfaces" and "Installing Features" chapters as appropriate for your site.
Some steps must be performed exactly as presented; several steps must be
modified according to the instructions in the Upgrading from a Prior Release
section.

Important! Be sure that you retain your previous CA Deliver JCL files and load libraries.

14 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 15)
Software Requirements (see page 17)
CA Common Services Requirements (see page 18)
Library Authorization (see page 19)
Security Requirements (see page 20)
Storage Requirements (see page 20)
Other Requirements (see page 20)
Concurrent Releases (see page 22)
Relationship between Versions of CA View and CA Deliver (see page 23)

Hardware Requirements
Use the tables in this section to estimate the storage required for the target libraries,
the distribution libraries, and the EBC (Extended Base Component) libraries.

Supported Operating Systems

IBM z/OS 1.9 and higher is the minimum software required to run this release of CA
View and meet the performance requirements.

CA Deliver Target Libraries

This table lists the amount of disk space needed to install the target libraries.

Library Name Blksize Tracks Dir Blks Description

CAI.CVDEJCL 27920 69 79 Common JCL library
CAI.CVDELOAD 32760 109 81 Common load library
CAI.CVDEPROC 27920 33 32 Common procedure library
CAI.CVDEOPTN 27920 40 40 Common options library
CAI.CVDESRC 27920 39 39 Common source library
CAI.CVDEMAC 27920 53 55 Common macro library

Chapter 2: Preparing for Installation 15

Hardware Requirements

Library Name Blksize Tracks Dir Blks Description

CAI.CVDECLS0 27920 17 16 Common CLIST library
CAI.CVDEPNL0 27920 33 32 Common ISPF panels library
CAI.CVDETBL0 27920 17 16 Common ISPF table library
CAI.CVDEPENU 27920 69 165 Common online panels (English)
CAI.CVDED133 32718 25 24 Deliver model banner page
library
CAI.CVDEXML 32760 54 32 CA MSM Deployment and
Configuration Services

Important! Do not reblock the libraries listed previously—storage problems might

occur.

CA Deliver Distribution Libraries

This table lists the amount of disk space needed to install the distribution libraries.

Library Name Blksize Tracks Dir Blks Description

CAI.ABRNJCL 27920 69 79 JCL library
CAI.ABRNMOD 32760 55 73 Load library
CAI.ABRNPROC 27920 33 32 Procedure library
CAI.ABRNOPTN 27920 40 40 Options library
CAI.ABRNSRC 27920 39 39 Source library
CAI.ABRNMAC 27920 53 55 Macro library
CAI.ABRNCLS0 27920 17 16 CLIST library
CAI.ABRNPNL0 27920 33 32 ISPF panels library
CAI.ABRNTBL0 27920 17 16 ISPF table library
CAI.ABRNPENU 27920 69 165 Online panels (English)
CAI.ABRNDATA 32718 25 24 Model banner page library
CAI.ABRNXML 32760 54 32 CA MSM Deployment and
Configuration Services

16 Installation Guide
 Software Requirements

EBC Distribution Libraries

This table lists the amount of disk space needed to install the EBC distribution libraries.

Library Name Blksize Tracks Dir Blks Description

CAI.ABROMOD 32760 29 51 Load library
CAI.ABROPROC 27920 33 32 Procedure library
CAI.ABROOPTN 27920 40 40 Options library
CAI.ABROSRC 27920 39 39 Source library
CAI.ABROMAC 27920 53 10 Macro library
CAI.ABROPNL0 27920 33 5 ISPF panels library
CAI.ABROJCL 27920 53 55 JCL library
CAI.ABROXML 32760 54 32 CA MSM Deployment and
Configuration Services

Software Requirements
This section lists the CA Deliver Version 12.0 component SYSMODs.

Common Component SYSMODs

This table lists the Common Component SYSMOD:

The CBROC00 SYSMOD is the EBC common component.

Note: The optional EBC CICS FMID has been incorporated into the EBC common
component FMID in Version 12.0.

CA Deliver Components
This table lists the CA Deliver component SYSMOD:

CBRNC00 is the CA Deliver base product component.

Chapter 2: Preparing for Installation 17

CA Common Services Requirements

CA Common Services Component

This table lists the CA Common Services component.

The CAIRIM component supports CA LMP.

CA Common Services Requirements

We recommend that you maintain CA Common Services at a current maintenance level
to ensure compatibility. For the latest information about maintenance requirements, go
to CA Support Online.

Note: If you intend to use CA MSM for your installation and maintenance tasks, there
might be additional CA Common Service requirements. For more information, see the
Software Requirements section in the CA Mainframe Software Manager Product Guide.

These CA Common Services are used with CA Deliver:

■ CAICCI
■ CAIRIM
■ CA LMP
■ CAISDI Service
■ CA Health Checker Common Service

Note: If other CA products are installed at your site, some of these services might
already be installed.

CA Common Services Installation Considerations

Before you proceed with this installation, be certain that CA Common Services are
installed on your machine.

Note: For more information, see the CA Common Services Getting Started Guide.

CAIRIM
CAIRIM (CAI Resource Initialization Manager) 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 that are commonly encountered when
you install systems software. CAIRIM prepares the operating system for CA products and
components, then executes them.

18 Installation Guide
 Library Authorization

CAIRIM does the following:

■ Obtains SMF data
■ Verifies proper software installation
■ Installs MVS interfaces
■ Starts CA and other vendor's products automatically
■ Provides proper timing and order of initialization

Note: CA Deliver requires CAIRIM to run the required CA LMP.

CA LMP
The CA License Management Program (CA LMP) tracks licensed software in a
standardized and automated way. It uses common, real-time enforcement software to
validate the user's configuration. CA LMP reports on activities related to the license,
usage, and financials of CA Technologies products.

CA LMP features include the following:

■ A Common Key Data Set that can be shared among many CPUs.
■ Check digits that are used to detect errors in transcribing key information.
■ Execution keys that can be entered without affecting any CA Technologies software
products that are already running.
■ No special maintenance is required.

CA Deliver is licensed with an LMP key. Acquire the LMP key using one of these
methods:
■ From your product media
■ With ESD
■ From CA Support

Library Authorization
CA Deliver and the EBC subsystem contain authorized programs. To run successfully,
these programs must be executed from an authorized library. We recommend that you
authorize the CAI Common Load Library (CVDELOAD).

Note: If other CA products have been installed, CVDELOAD may already be authorized.

Chapter 2: Preparing for Installation 19

Security Requirements

To authorize the CVDELOAD library, modify the appropriate member PROGxx in

SYS1.PARMLIB to add an entry for CVDELOAD as follows:

APF ADD DSNAME(CAI.CVDELOAD) VOLUME(xxxxxx)

where CAI.CVDELOAD is the data set name for the CAI Common Load Library, and xxxxxx
is the volume serial number on which it resides. Use MVS system command SET
PROG=xx to activate update to PROGxx.

Security Requirements
For security requirements related to the ability to access data within the CA Deliver
database, see the "Security" chapter in the CA Deliver Reference Guide.

Storage Requirements
Ensure that you have the following storage available:
■ If you are installing with ESD, 80 cylinders for the downloaded files.
■ For installation and setup:
– Installation = 100 cylinders
– SMP/E temporary libraries = 10 cylinders]

Other Requirements
This section describes SVC Dumps and JCL procedures:

SVC Dump Data Sets

CA Deliver issues SVC dumps (SDUMP) for certain types of abends. These dumps are
written to the MVS SYS1.DUMPnn. data sets. Contact your systems programmer to
verify that the data sets are allocated with at least 100 cylinders.

Dump Analysis and Elimination

The SDUMP program supports MVS dump analysis and elimination processing. This MVS
feature eliminates the possibility that duplicate SVC dumps might be written to the
SYS1.DUMPnn. data sets.

20 Installation Guide
 Other Requirements

To use this MVS feature, the SYS1.DAE data set must be allocated and the following
parameter members must be updated in SYS1.PARMLIB:

IEACMDxx
SET DAE = xx

where xx identifies the ADYSETxx. member

ADYSETxx
DAE=START,RECORDS(sss),SVCDUMP(MATCH,UPDATE,SUPPRESS)

where sss is the number of records in SYS1.DAE.

System Dump Parameters

CA Deliver allocates storage from MVS subpool 230.

For this storage area to be dumped correctly, the IEADMRxx. member in SYS1.PARMLIB
should contain the SDATA RGN parameter:

SDATA=(...,RGN,...)

The IEADMPxx. member in SYS1.PARMLIB should contain the SDATA LSQA parameter:

SDATA=(...,LSQA,...)

Important! If these dump parameters are not specified as shown in the previous
example, certain storage areas might be missing from dumps, which can hinder support
efforts.

JCL Procedures
During product installation, the procedures are copied into CBRNPROC, the CAI
Common Procedure Library. These procedures are used later during normal execution of
CA Deliver.

We recommend that you add the CVDEPROC library to the system PROCLIB
concatenation.

Chapter 2: Preparing for Installation 21

Concurrent Releases

Concurrent Releases
You can install this release of CA Deliver and continue to use an older release in another
SMP/E CSI environment. If you plan to continue to run a previous release, consider the
following points:
■ When installing into an existing SMP/E environment, this installation deletes
previous releases in that environment.
■ If you acquired your product from tape or with Pax-Enhanced ESD, select different
target and distribution zones for your new release from where your current release
is installed. The new zones use different libraries than your current release.
Note: CA MSM installs into a new CSI by default.
■ 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.

22 Installation Guide
 Relationship between Versions of CA View and CA Deliver

Relationship between Versions of CA View and CA Deliver

This diagram shows the relationship between multiple versions of CA View and CA
Deliver:

Chapter 2: Preparing for Installation 23

Chapter 3: Installing Your Product Using CA
MSM
These topics provide information to get you started managing your product using CA
MSM. You can use the online help included in CA MSM to get additional information.

Before using these topics, you must already have CA MSM installed at your site. If you
do not have CA MSM installed, you can download it from the Download Center at the
CA Support Online website, which also contains links to the complete documentation for
CA MSM.

Note: The information in this section applies to the latest version of CA MSM. If you are
using an earlier version, see the appropriate bookshelf on the CA Mainframe Software
Manager product page.

How to Use CA MSM: Scenarios

Imagine that your organization has started using CA MSM to simplify the installation of
CA Technologies products and unify their management. You have also licensed a new CA
Technologies product. In addition, you have a number of existing CSIs from previously
installed CA Technologies products.

You can use the following scenarios to guide you through the process:
1. Acquire the new product (see page 25).
2. Install the new product (see page 26).
3. Maintain products already installed in your environment (see page 27).
4. Deploy the product to your target systems (see page 28).
5. Configure the deployed product to your target systems (see page 29).

How to Acquire a Product

The Product Acquisition Service (PAS) facilitates the acquisition of mainframe products
and the service for those products, such as program temporary fixes (PTFs). The PAS
retrieves information about products to which your site is entitled. Then it records these
entitlements in a software inventory that is maintained on your driving system.

You can use the PAS component of CA MSM to acquire a CA Technologies product.

Chapter 3: Installing Your Product Using CA MSM 25

How to Use CA MSM: Scenarios

Follow these steps:

1. Set up a CA Support Online account.
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, you can create one on the CA
Support Online website.
2. Determine the CA MSM URL for your site.
To access CA MSM (see page 30), you require its URL. You can get the URL from
your site's 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 for the CA Support Online website. This account enables you to
download product packages.
3. Log in to CA MSM and go to the Software Catalog page to locate the product that
you want to manage.
After you log in to CA MSM, you can see the products to which your organization is
entitled on the Software Catalog tab.
If you cannot find the product you want to acquire, update the catalog. CA MSM
refreshes the catalog through the CA Support Online website using the site IDs
associated with your credentials for the CA Support Online website.
4. Download the product installation packages.
After you find your product in the catalog, you can download the product
installation packages.
CA MSM downloads (acquires) the packages (including any maintenance packages)
from the CA FTP site.

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

How to Install a Product

The Software Installation Service (SIS) facilitates the installation and maintenance of
mainframe products in the software inventory of the driving system. This facilitation
includes browsing downloaded software packages, managing SMP/E consolidated
software inventories on the driving system, and automating installation tasks.

You can use the SIS component of CA MSM to install a CA Technologies product.

Follow these steps:

1. Initiate product installation and review product information.
2. Select an installation type.
3. Review installation prerequisites if any are presented.

26 Installation Guide
 How to Use CA MSM: Scenarios

4. 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: Either create a target zone or use an existing target
zone.
c. Set up the distribution zone: Either 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 release, if
necessary.
5. Review the installation summary and start the installation.

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 beginning the deployment process.

How to Maintain Existing Products

If you have existing CSIs, you can bring those CSIs into CA MSM so that you can maintain
all your installed products in a unified way from a single web-based interface.

You can use the PAS and SIS to maintain a CA Technologies product.

Follow these steps:

1. Migrate the CSI to CA MSM to maintain an existing CSI in CA MSM.
During the migration, CA MSM stores information about the CSI in the database.
2. Download the latest maintenance for the installed product releases from the
Software Catalog tab.
If you cannot find a release (for example, because the release is old), you can add
the release to the catalog manually and then update the release to download the
maintenance.

Chapter 3: Installing Your Product Using CA MSM 27

How to Use CA MSM: Scenarios

3. Apply the maintenance.

Note: You can also install maintenance to a particular CSI from the SMP/E Environments
tab.

After the maintenance process completes, the product is ready for you to deploy. You
may have to perform other steps manually outside of CA MSM before beginning the
deployment process.

How to Deploy a Product

The Software Deployment Service (SDS) facilitates the mainframe product deployment
from the software inventory of the driving system to the target system. This facilitation
includes deploying installed products that are policy-driven with a set of appropriate
transport mechanisms across a known topology.

You can use the SDS component of CA MSM to deploy a CA Technologies product that
you have already acquired and installed.

Follow these steps:

1. Set up the system registry:
a. Determine the systems you have at your enterprise.
b. Set up remote credentials for those systems.
c. Set up the target systems (non-sysplex, sysplex or monoplex, shared DASD
cluster, and staging), and validate them.
d. Add network information, including data destination information, to each
system registry entry.
2. Set up methodologies.
3. Create the deployment, which includes completing each step in the New
Deployment wizard.
After creating the deployment, you can save it and change it later by adding and
editing systems, products, custom data sets, and methodologies, or you can deploy
directly from the wizard.
Note: If you must deploy other products to the previously defined systems using
the same methodologies, you must create a separate deployment.
4. Deploy the product, which includes taking a snapshot, transmitting to target, and
deploying (unpacking) to your mainframe environment.

After the deployment process completes, the product is ready for you to configure. You
may have to perform other steps manually outside of CA MSM before beginning the
configuration process.

28 Installation Guide
 How to Use CA MSM: Scenarios

More information:

How to Complete Deployment With CA MSM (see page 79)

How to Configure a Product

The Software Configuration Service (SCS) facilitates the mainframe product
configuration from the software inventory of the driving system to targeted z/OS
operating systems.

You can use the SCS component of CA MSM to configure a CA Technologies product that
you have already acquired, installed, and deployed.

Follow these steps:

1. Select a deployed product to configure from the Deployments tab to open the
Create Configuration wizard.
2. Create the configuration, which includes completing each step in the Create
Configuration wizard, including the following:
a. Define a configuration name and select a target system.
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 Create Configuration wizard lets you
build the configuration.
4. Implement the configuration. The implementation process in CA MSM is a
step-by-step process that carefully guides you and provides detailed instructions to
start, stop, and manage the steps of the implementation process.

After the configuration process completes, the product is ready for you to use. You may
have to perform other steps manually outside of CA MSM.

Note: You cannot use CA MSM to configure a product to a staging system.

More information:

How to Complete Configuration With CA MSM (see page 79)

Chapter 3: Installing Your Product Using CA MSM 29

Access CA MSM Using the Web-Based Interface

Access CA MSM Using the Web-Based Interface

You access CA MSM using the web-based interface. Obtain 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, and click the Log in button.
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.
Important! The account to which the credentials apply must have the Product
Display Options set to BRANDED PRODUCTS. You can view and update your account
preferences by logging into the CA Support Online website and clicking My Account.
If you do not have the correct setting, you are not able to use CA MSM to download
product information and packages.
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 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.

30 Installation Guide
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 31)
Allocate and Mount a File System (see page 37)
Copy the Product Pax Files into Your USS Directory (see page 40)
Create a Product Directory from the Pax File (see page 45)
Copy Installation Files to z/OS Data Sets (see page 46)
Receive the SMP/E Package (see page 47)
Clean Up the USS Directory (see page 51)
Apply Maintenance (see page 52)

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.

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 used
for the ESD process.

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 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 31

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 new 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 created by the pax command in Step 3 contains a sample
job to GIMUNZIP the installation package. Edit and submit the UNZIPJCL job.
5. Receive the SMP/E package. For this step, use the data sets created by GIMUNZIP 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 created by
the pax command, all of the files in it, and the SMP/E RELFILEs, SMPMCS, and
HOLDDATA data sets.

More Information:

USS Environment Setup (see page 36)

Allocate and Mount a File System (see page 37)
Copy the Product Pax Files into Your USS Directory (see page 40)
Create a Product Directory from the Pax File (see page 45)
Copy Installation Files to z/OS Data Sets (see page 46)
Receive the SMP/E Package (see page 47)

32 Installation Guide
 How to Install a Product Using Pax-Enhanced ESD

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.
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 33) 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

CA Technologies product ESD packages can be downloaded multiple ways. Your choices
depend on the size of the individual files and the number of files 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 33

How to Install a Product Using Pax-Enhanced ESD

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

34 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 product files ordered, the Download Method
screen could also have these options:

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

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

How to Install a Product Using Pax-Enhanced ESD

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.

The Create a Zip File option first creates the zip, and when ready, offers the options
shown by the Zip Download Request examples in the next screen.

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.

36 Installation Guide
 Allocate and Mount a File System

We recommend that you allocate and mount a file system 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 new directory for each pax download.

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 used
for the ESD process. In the file system that contains the ESD directories, you also need
free space approximately 3.5 times the pax file size 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 SUPERUSER authority to do this.
■ 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 37

Allocate and Mount a File System

Follow these steps:

1. Allocate the file system by customizing one of the following samples to your site's
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_dataset_name) +
STORAGECLASS(class) +
LINEAR +
CYL(primary secondary) +
SHAREOPTIONS(3,3) +
)
/*
//FORMAT EXEC PGM=IOEAGFMT,REGION=0M,
// PARM=('-aggregate your_zFS_dataset_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_dataset_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.

38 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's
requirements:
■ On a zFS, use the following sample:
MOUNT FILESYSTEM('your_zFS_dataset_name')
MOUNTPOINT('yourUSSESDdirectory')
TYPE(ZFS) MODE(RDWR)
PARM(AGGRGROW)

■ On an HFS, use the following sample:

MOUNT FILESYSTEM('your_HFS_dataset_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 39

Copy the Product Pax Files into Your USS Directory

Copy the Product Pax Files into Your USS Directory

To begin the CA Technologies product installation procedure, copy the product's pax file
into the USS directory 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 PC,
and upload it to your z/OS system.
■ Download the product file from CA Support Online to your PC. 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 PC 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 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 33)

ESD Product Download Window (see page 33)

40 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 41

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.

42 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’s statements in this JCL maybe *
//* 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 43

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 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's 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

44 Installation Guide
 Create a Product Directory from the Pax File

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.

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.

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 45

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 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.

46 Installation Guide
 Receive 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.
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 used by the installation process. 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 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 reference guide, SMP/E for z/OS
Reference (SA22-7772).

Receive the SMP/E Package

If you are installing the package into a new SMP/E environment, see the product
documentation and the sample jobs included with the product to set up an SMP/E
environment before proceeding. The sample jobs can be found in YourHLQ.SAMPJCL.

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 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 47

Receive the SMP/E Package

How to Install Products Using Native SMP/E JCL

The following steps describe the process to install products using native SMP/E JCL:
1. Allocate product data sets and SMP/E data sets.
2. Create SMP/E CSI.
3. Receive base functions.
4. Apply base functions.
5. Accept base functions.
6. Configure the product according to your site requirements.

Prepare the SMP/E Environment for Pax Installation

The members used in this procedure prepare the data sets, initialize the zones, and
create the DDDEFs for CA Deliver.

Prior to beginning this procedure, confirm whether your product uses UNIX System
Services (USS). If it does, establishing a hierarchical file system (HFS) may be required as
part of the product installation or required as a feature of the product.

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

Follow these steps:

1. Customize the macro BRNSEDIT with your site-specific information and then copy
the macro to your SYSPROC location. Replace the rightmost parameters for each
ISREDIT CHANGE macro command. Each time you edit an installation member, type
BRNSEDIT on the TSO command line, and press Enter to replace the defaults with
your specifications.
The macro is ready to customize the yourHLQ.SAMPJCL members.
Note: Set the DASD HLQ to the same value specified for yourHLQ for the unzip to
DASD ESD JCL.
Note: The following steps include instructions to execute the BRNSEDIT macro each
time you open a new SAMPJCL member. To edit all SAMPJCL members
simultaneously, read and follow the instructions in the BRNEDALL member.
2. Open the SAMPJCL member BRN1ALL in an edit session and execute the BRNSEDIT
macro from the command line.
BRN1ALL is customized.
Note: When upgrading into an existing CSI, comment out any allocation DD
statements for existing files.

48 Installation Guide
 Receive the SMP/E Package

3. Submit BRN1ALL.
This job produces the following results:
■ The target and distribution data sets for CA Deliver are created.
■ Unique SMPLTS, SMPMTS, SMPSCDS, and SMPSTS data sets for this target zone
are created.
4. If your product requires HFS or if you want to install a feature of the product that
requires HFS, complete the following substeps:
a. Open the SAMPJCL member ccc1ALLU in an edit session and execute the
BRNSEDIT macro from the command line.
Note: All instances of ccc in this section indicate a three-character component
code based on the FMID.
ccc1ALLU is customized.
b. Submit ccc1ALLU.
This job allocates your HFS data sets.
c. Open the SAMPJCL member ccc2MKD in an edit session and execute the
BRNSEDIT macro from the command line.
ccc2MKD is customized.
d. Submit ccc2MKD.
This job creates all directories and mounts the file system.
5. Open the SAMPJCL member BRN2CSI in an edit session and execute the BRNSEDIT
macro from the command line.
BRN2CSI is customized.
Note: When upgrading into an existing CSI, comment out any allocation DD
statements for existing files and delete the CREATCSI step. Change all ADD’s to
REP’s.
6. Submit BRN2CSI.
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.
The DDDEFs for the required SMP/E data sets are created.

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

Receive the SMP/E Package

7. If your product requires HFS or if you want to install a feature of the product that
requires HFS, complete the following substeps:
a. Open the SAMPJCL member ccc3CSIU in an edit session and execute the
BRNSEDIT macro from the command line.
ccc3CSIU is customized.
b. Submit ccc3CSIU.
This job customizes the CSI by adding the DDDEFs associated with the
directory.

Run the Installation Jobs for a Pax Installation

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

Follow these steps:

1. Open the SAMPJCL member BRN3RECD in an edit session, and execute the
BRNSEDIT macro from the command line.
Note: Comment out any unwanted FMIDs.
BRN3RECD is customized.
2. Submit the yourHLQ.SAMPJCL member BRN3RECD to receive SMP/E base functions.
CA Deliver is received and now resides in the global zone.
3. Open the SAMPJCL member BRN4APP in an edit session, and execute the BRNSEDIT
macro from the command line.
Note: Comment out any unwanted FMIDs.
BRN4APP is customized.
4. Submit the yourHLQ.SAMPJCL member BRN4APP to apply SMP/E base functions.
Your product is applied and now resides in the target libraries.
5. Open the SAMPJCL member BRN5ACC in an edit session, and execute the BRNSEDIT
macro from the command line.
Note: Comment out any unwanted FMIDs.
BRN5ACC is customized.
6. Submit the yourHLQ.SAMPJCL member BRN5ACC to accept SMP/E base functions.
Your product is accepted and now resides in the distribution libraries.

50 Installation Guide
 Clean Up the USS Directory

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 created by the pax command 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.
3. Delete the product-specific directory by entering the following command:
rm -r product-specific-directory

product-specific-directory
Specifies the product-specific directory created by the pax command.
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.

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

Apply Maintenance

Apply Maintenance
CA Support Online has maintenance and HOLDDATA published since the installation
data was created. When the maintenance process is complete the product is ready to
deploy.

To apply maintenance
1. Check CA Support Online and download any PTFs and HOLDDATA that has been
published since this release was created. If the base release was created recently,
no PTFs or HOLDATA have been published yet.
2. Transfer the downloaded files to two separate FB 80 sequential data sets. Use one
data set to contain the PTFs and the other to contain the HOLDDATA.
The PTFs and HOLDDATA become accessible to the yourhlq.SAMPJCL maintenance
members.
3. The BRNSEDIT macro has been customized in the installation steps. Verify that you
still have the values from the base install.
4. Open the SAMPJCL member BRN6RECP in an edit session and execute the BRNSEDIT
macro from the command line.
BRN6RECP is customized with your JOB statement, CSI location, and zone names.
5. Customize the BRN6RECP SMPPTFIN and SMPHOLD DD statements to reference the
FB 80 data sets for the PTFs and HOLDDATA.
6. Submit BRN6RECP.
The PTFs and HOLDDATA are received.
7. Open the SAMPJCL member BRN7APYP in an edit session and execute the
BRNSEDIT macro from the command line.
BRN7APYP is customized.
8. Submit BRN7APYP.
The PTFs are applied.
9. (Optional) Open the SAMPJCL member BRN8ACCP in an edit session and execute
the BRNSEDIT macro from the command line.
BRN8ACCP is customized.
10. (Optional) Submit yourhlq.SAMPJCL member BRN8ACCP.
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's policy.

52 Installation Guide
 Apply Maintenance

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.

System HOLDDATA

System HOLDDATA indicates data that is an in-stream part of the SYSMOD, informing
you of special conditions. The following reasons are used with SYSTEM HOLDDATA for
CA Deliver:
ACTION
Indicates that you must perform special processing before or after you apply this
SYSMOD.
AO
Affects automated operations. It changes either the message identifier or the
displacement of a field inside the message.
DB2BIND
Indicates that DBRMs have changed and packages need to be rebound.
DDDEF
Indicates that data sets and DDDEFs are being added or modified.
DELETE
Deletes the SYSMOD load module. You cannot reverse this type of SYSMOD with
the SMP/E RESTORE command.
DEP
Indicates a dependency for this SYSMOD that you must externally verify.
DOC
Indicates a documentation change with this SYSMOD.

DYNACT
Describes the steps to dynamically activate this fix without performing an IPL.

EC
Indicates that this SYSMOD requires a hardware engineering change. An EC hold
SYSMOD usually does not affect the product unless the EC is present on the
hardware device.

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

Apply Maintenance

ENH
Introduces a small programming enhancement. The hold contains the instructions
to implement the enhancement. If no action is needed to implement the
enhancement, give a summary of the enhancement.

EXIT
Indicates that changes delivered by this SYSMOD require reassembly of user exits.

EXRF
Indicates that the SYSMOD must be installed in both the Active and Alternate
Extended Recovery Facility Systems.

IPL
Indicates that an IPL is required for this SYSMOD to take effect. This is used only
when there is no alternative for dynamic activation.

MSGSKEL
Indicates that the SYSMOD contains internationalized message versions which must
be run through the message compiler for each language.

MULTSYS
Apply this SYSMOD to multiple systems for either pre-conditioning, coexistence, or
exploitation.
RESTART
Indicates that after applying this SYSMOD, the site must perform a special restart as
opposed to a routine restart.
SQLBIND
Indicates that a bind is required for a database system other than DB2.
SYSMOD
Indicates that some or all of the elements delivered by this SYSMOD are to be
downloaded to a workstation.

Code a bypass operand on your APPLY command to install SYSMODs that have internal
holds. Code the bypass operand only after you have performed the required action, or if
you are performing the action after the APPLY, if that is appropriate.

54 Installation Guide
 Apply Maintenance

External HOLDDATA

External HOLDDATA is not part of the PTF. It resides in a separate file. It is commonly
used for SYSMODs that have been distributed and later are discovered to cause
problems.

Download the external HOLDDATA from CA Support to a DASD file, and allocate the file
to the SMPHOLD DD statement. To take care of the external HOLDDATA, receive it into
your SMP/E environment. SMP/E receives the HOLDDATA from CA-supplied jobs.

If a SYSMOD has an unresolved hold error, SMP/E does not install it unless you add a
bypass to your APPLY command. You can bypass an error hold in situations that are not
applicable to you. Error holds that are not applicable to you can include a problem that
happens only with a hardware device that you do not have or in a product feature that
you do not use.

When CA publishes a SYSMOD that resolves the hold, the resolving SYSMOD supersedes
the hold error. This action lets you apply the original SYSMOD in conjunction with the
fixing SYSMOD.

A special HOLDDATA class called ERREL exists. We have determined that the problem
fixed by the SYSMOD is more important than the one that it causes. We recommend
that you apply these SYSMODs.

The only manual task is running a REPORT ERRSYSMODS. This report identifies the
following:
■ Any held SYSMODs already applied to your system.
■ Any resolving SYSMODs that are in RECEIVE status.

SMP/E identifies the SYSMOD to apply to correct the situation.

Note: When you have completed the procedures in this section, go to Configuring Your
Product.

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

Chapter 5: Installing Your Product from
Tape
This section contains the following topics:
Unload the Sample JCL from Tape (see page 58)
How to Install Products Using Native SMP/E JCL (see page 59)
Apply Maintenance (see page 62)

Chapter 5: Installing Your Product from Tape 57

Unload the Sample JCL from Tape

Unload the Sample JCL from Tape

To simplify the 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
UnloadJCL.txt file to view the sample JCL job.

Note: The sample JCL to install the product is also provided in the CAI.SAMPJCL library
on the distribution tape.

Follow these steps:

1. Run the following sample JCL:
//COPY EXEC PGM=IEBCOPY,REGION=4096K
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=CAI.SAMPJCL,DISP=OLD,UNIT=unitname,VOL=SER=nnnnnn,
// LABEL=(1,SL)
//SYSUT2 DD DSN=yourHLQ.SAMPJCL,
// DISP=(,CATLG,DELETE),
// UNIT=sysda,SPACE=(TRK,(15,3,6),RLSE)
//SYSUT3 DD UNIT=sysda,SPACE=(CYL,1)
//SYSIN DD DUMMY

unitname
Specifies the tape unit to mount the tape.
nnnnnnn
Specifies the tape volume serial number.
yourHLQ
Specifies the data set prefix for the installation.
sysda
Specifies the DASD where you want to place the installation software.
The SAMPJCL data set is created and its contents are downloaded from the tape.
2. Continue with one of the following options:
■ If you already have set up the SMP/E environment, go to Run the Installation
Jobs for a Tape Installation.
■ If you have not set up the SMP/E environment, go to Prepare the SMP/E
Environment for Tape Installation.

58 Installation Guide
 How to Install Products Using Native SMP/E JCL

How to Install Products Using Native SMP/E JCL

The following steps describe the process to install products using native SMP/E JCL:
1. Allocate product data sets and SMP/E data sets.
2. Create SMP/E CSI.
3. Receive base functions.
4. Apply base functions.
5. Accept base functions.
6. Configure the product according to your site requirements.

Prepare the SMP/E Environment for Tape Installation

The members used in this procedure prepare the data sets, initialize the zones, and
create the DDDEFs for CA Deliver.

Prior to beginning this procedure, confirm whether your product uses UNIX System
Services (USS). If it does, establishing a hierarchical file system (HFS) may be required as
part of the product installation or required as a feature of the product.

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

Follow these steps:

1. Customize the macro BRNSEDIT with your site-specific information and then copy
the macro to your SYSPROC location. Replace the rightmost parameters for each
ISREDIT CHANGE macro command. Each time you edit an installation member, type
BRNSEDIT on the TSO command line, and press Enter to replace the defaults with
your specifications.
The macro is ready to customize your BRN.SAMPJCL members.
Note: The following steps include instructions to execute the BRNSEDIT macro each
time you open a new SAMPJCL member. To edit all SAMPJCL members
simultaneously, read and follow the instructions in the BRNEDALL member.
2. Open the SAMPJCL member BRN1ALL in an edit session and execute the BRNSEDIT
macro from the command line.
BRN1ALL is customized.
Note: When upgrading into an existing CSI, comment out any allocation DD
statements for existing files.

Chapter 5: Installing Your Product from Tape 59

How to Install Products Using Native SMP/E JCL

3. Submit BRN1ALL.
This job produces the following results:
■ The target and distribution data sets for CA Deliver are created.
■ Unique SMPLTS, SMPMTS, SMPSCDS, and SMPSTS data sets for this target zone
are created.
4. If your product requires HFS or if you want to install a feature of the product that
requires HFS, complete the following substeps:
a. Open the SAMPJCL member ccc1ALLU in an edit session and execute the
BRNSEDIT macro from the command line.
Note: All instances of ccc in this section indicate a three-character component
code based on the FMID.
ccc1ALLU is customized.
b. Submit ccc1ALLU.
This job allocates your HFS data sets.
c. Open the SAMPJCL member ccc2MKD in an edit session and execute the
BRNSEDIT macro from the command line.
ccc2MKD is customized.
d. Submit ccc2MKD.
This job creates all directories and mounts the file system.
5. Open the SAMPJCL member BRN2CSI in an edit session and execute the BRNSEDIT
macro from the command line.
BRN2CSI is customized.
Note: When upgrading into an existing CSI, comment out any allocation DD
statements for existing files and delete the CREATCSI step. Change all ADD’s to
REP’s.
6. Submit BRN2CSI.
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.
■ The DDDEFs for the required SMP/E data sets are created.

60 Installation Guide
 How to Install Products Using Native SMP/E JCL

7. If your product requires HFS or if you want to install a feature of the product that
requires HFS, complete the following substeps:
a. Open the SAMPJCL member ccc3CSIU in an edit session and execute the
BRNSEDIT macro from the command line.
ccc3CSIU is customized.
b. Submit ccc3CSIU.
This job customizes the CSI by adding the DDDEFs associated with the
directory.

Run the Installation Jobs for a Tape Installation

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

Follow these steps:

1. Open the SAMPJCL member BRN3RECT in an edit session and execute the BRNSEDIT
macro from the command line.
Note: Comment out any unwanted FMIDs.
BRN3RECT is customized.
2. Submit the yourHLQ.SAMPJCL member BRN3RECT to receive SMP/E base functions.
CA Deliver is received and now resides in the global zone.
3. Open the SAMPJCL member BRN4APP in an edit session and execute the BRNSEDIT
macro from the command line.
Note: Comment out any unwanted FMIDs.
BRN4APP is customized.
4. Submit the yourHLQ.SAMPJCL member BRN4APP to apply SMP/E base functions.
Your product is applied and now resides in the target libraries.
5. Open the SAMPJCL member BRN5ACC in an edit session and execute the BRNSEDIT
macro from the command line.
Note: Comment out any unwanted FMIDs.
BRN5ACC is customized.
6. Submit the yourHLQ.SAMPJCL member BRN5ACC to accept SMP/E base functions.
Your product is accepted and now resides in the distribution libraries.

Chapter 5: Installing Your Product from Tape 61

Apply Maintenance

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 and download 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. Transfer the downloaded files to two separate FB 80 sequential data sets. Use one
data set to contain the PTFs and the other to contain the HOLDDATA.
The PTFs and HOLDDATA become accessible to the yourHLQ.SAMPJCL maintenance
members.
3. The BRNSEDIT macro was customized in the installation steps. Verify that you still
have the values from the base install.
4. Open the SAMPJCL member BRN6RECP in an edit session and execute the BRNSEDIT
macro from the command line.
BRN6RECP is customized with your JOB statement, CSI location, and zone names.
5. Customize the BRN6RECP SMPPTFIN and SMPHOLD DD statements to reference the
FB 80 data sets for the PTFs and HOLDDATA.
6. Submit BRN6RECP.
The PTFs and HOLDDATA are received.
7. Open the SAMPJCL member BRN7APYP in an edit session and execute the
BRNSEDIT macro from the command line.
BRN7APYP is customized.
8. Submit BRN7APYP.
The PTFs are applied.
9. (Optional) Open the SAMPJCL member BRN8ACCP in an edit session and execute
the BRNSEDIT macro from the command line.
BRN8ACCP is customized.
10. (Optional) Submit yourHLQ.SAMPJCL member BRN8ACCP.
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.

62 Installation Guide
 Apply Maintenance

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.

System HOLDDATA

System HOLDDATA indicates data that is an in-stream part of the SYSMOD, informing
you of special conditions. The following reasons are used with SYSTEM HOLDDATA for
CA Deliver:
ACTION
Indicates that you must perform special processing before or after you apply this
SYSMOD.
AO
Affects automated operations. It changes either the message identifier or the
displacement of a field inside the message.
DB2BIND
Indicates that DBRMs have changed and packages need to be rebound.
DDDEF
Indicates that data sets and DDDEFs are being added or modified.
DELETE
Deletes the SYSMOD load module. You cannot reverse this type of SYSMOD with
the SMP/E RESTORE command.
DEP
Indicates a dependency for this SYSMOD that you must externally verify.
DOC
Indicates a documentation change with this SYSMOD.

DYNACT
Describes the steps to dynamically activate this fix without performing an IPL.

EC
Indicates that this SYSMOD requires a hardware engineering change. An EC hold
SYSMOD usually does not affect the product unless the EC is present on the
hardware device.

Chapter 5: Installing Your Product from Tape 63

Apply Maintenance

ENH
Introduces a small programming enhancement. The hold contains the instructions
to implement the enhancement. If no action is needed to implement the
enhancement, give a summary of the enhancement.

EXIT
Indicates that changes delivered by this SYSMOD require reassembly of user exits.

EXRF
Indicates that the SYSMOD must be installed in both the Active and Alternate
Extended Recovery Facility Systems.

IPL
Indicates that an IPL is required for this SYSMOD to take effect. This is used only
when there is no alternative for dynamic activation.

MSGSKEL
Indicates that the SYSMOD contains internationalized message versions which must
be run through the message compiler for each language.

MULTSYS
Apply this SYSMOD to multiple systems for either pre-conditioning, coexistence, or
exploitation.
RESTART
Indicates that after applying this SYSMOD, the site must perform a special restart as
opposed to a routine restart.
SQLBIND
Indicates that a bind is required for a database system other than DB2.
SYSMOD
Indicates that some or all of the elements delivered by this SYSMOD are to be
downloaded to a workstation.

Code a bypass operand on your APPLY command to install SYSMODs that have internal
holds. Code the bypass operand only after you have performed the required action, or if
you are performing the action after the APPLY, if that is appropriate.

64 Installation Guide
 Apply Maintenance

External HOLDDATA

External HOLDDATA is not part of the PTF. It resides in a separate file. It is commonly
used for SYSMODs that have been distributed and later are discovered to cause
problems.

Download the external HOLDDATA from CA Support to a DASD file, and allocate the file
to the SMPHOLD DD statement. To take care of the external HOLDDATA, receive it into
your SMP/E environment. SMP/E receives the HOLDDATA from CA-supplied jobs.

If a SYSMOD has an unresolved hold error, SMP/E does not install it unless you add a
bypass to your APPLY command. You can bypass an error hold in situations that are not
applicable to you. Error holds that are not applicable to you can include a problem that
happens only with a hardware device that you do not have or in a product feature that
you do not use.

When CA publishes a SYSMOD that resolves the hold, the resolving SYSMOD supersedes
the hold error. This action lets you apply the original SYSMOD in conjunction with the
fixing SYSMOD.

A special HOLDDATA class called ERREL exists. We have determined that the problem
fixed by the SYSMOD is more important than the one that it causes. We recommend
that you apply these SYSMODs.

The only manual task is running a REPORT ERRSYSMODS. This report identifies the
following:
■ Any held SYSMODs already applied to your system.
■ Any resolving SYSMODs that are in RECEIVE status.

SMP/E identifies the SYSMOD to apply to correct the situation.

Note: When you have completed the procedures in this section, go to Configuring Your
Product.

Chapter 5: Installing Your Product from Tape 65

Chapter 6: Installing Your Product from
DVD
This section contains the following topics:
Overview (see page 67)
Introduction to Electronic Software Delivery (see page 70)
Pax-Enhanced ESD Procedures (see page 73)
References (see page 77)

Overview

Purpose
Welcome to the CA Electronic Software Delivery (ESD) program using the Pax-Enhanced
ESD process for SMP/E installations for z/OS systems. This guide provides the
information and steps that you need to copy your CA products from the CA products
DVD using the Pax-Enhanced ESD process.

Audience
We created this guide to explain the entire Pax-Enhanced ESD process for novice users.
Each chapter explicitly states the required steps. We strongly suggest that you read this
entire document and follow the procedures the first time you copy a product from a
DVD using the Pax-Enhanced ESD program.

Frequently Asked Questions

This section lists common questions and answers related to the Pax-Enhanced ESD
process.

#1: What is the Pax-Enhanced ESD process?

The enhanced process lets you download software directly to your mainframe and
eliminates the need to download files to tape. We implemented the Pax-Enhanced ESD
process in response to customer requests.

Chapter 6: Installing Your Product from DVD 67

Overview

#2: How is the process different? What has changed?

When using the traditional ESD process, you upload the ESD file to the mainframe and
create a product installation tape using a utility program provided by CA.

The Pax-Enhanced ESD process eliminates the need for a tape and uses superior
compression technology that reduces file transfer times. This process uses a UNIX
portable archive interchange (pax) file. Standard z/OS utilities can read and expand the
file directly to your mainframe system.

#3: Why did CA choose to use and require customers to use UNIX System Services
(USS)?

To improve the CA product installation process for our customers. The following list
details some of the benefits of using the USS pax format to distribute software
packages:
■ Supports all z/OS data types including, VSAM, PDS, PDSE, HFS, and zFS.
■ Allows a large number of MVS data sets to be zipped into a single file that can be
received in a single download.
■ Can be un-packed using standard utilities that are available on every z/OS system.
No additional utilities or licensed products are required.
■ Supports the CA Mainframe Software Manager (MSM). CA MSM makes it faster and
easier to install all CA products from a browser-based user interface and eliminates
many of the complexities and software knowledge of SMP/E, JCL, and other utilities.

#4: Do I need to do anything differently as a result? Are there any new requirements
or any dependencies? Am I required to have an in-depth knowledge of UNIX System
Services (USS) to use the Pax-Enhanced ESD process?

A basic understanding of USS is sufficient if you understand UNIX and follow the steps in
this guide. The appendix in this guide lists and defines common USS commands. In
addition, the appendix lists IBM documents that provide detailed information about
USS.

#5: What can I expect when I transition to the Pax-Enhanced ESD process?

You may experience a slight learning curve the first time you use the enhanced process.
We recommend reading this guide in its entirety before using the Pax-Enhanced ESD
process.

68 Installation Guide
 Overview

#6: Why did CA implement the new process?

We received customer requests to eliminate the need to create an intermediate tape

during the software installation process. Pax-Enhanced ESD supports installation
completely from files on DASD, allowing customers to obtain and benefit from the latest
CA product software releases and updates quickly, and with less manual effort.

In addition, Pax-Enhanced ESD is one of the first deliverables based on our Mainframe
2.0 strategy, which is designed to simplify software installation and other system
administration functions on z/OS. We invite you to visit
http://www.ca.com/mainframe2 to learn more about Mainframe 2.0.

#7: Does CA still provide products and maintenance on cartridge tapes?

Yes. You can still order cartridge tapes. However, we strongly recommend using the
Pax-Enhanced ESD process because it is faster and more secure than the physical tape
delivery method.

#8: Are there software prerequisites for the Pax-Enhanced ESD process?

Yes. The Pax-Enhanced ESD process requires SMP/E 3.4 with IBM APAR IO07810 (or
higher). You can get the latest release of SMP/E from IBM at no charge.

#9: What version of Java do I need?

The Pax-Enhanced ESD process does not require Java. If the Integrated Cryptographic
Services Facility (ICFS) is not active, the GIMUNZIP SMP/E utility requires Java 1.4 or
higher to generate an SHA-1 hash value.

#10: Does this process require a specific version of z/OS?

No. You can use Pax Enhanced-ESD on any supported version of z/OS.

#11: How do I know that the files I'm working with are the most current?

Check the https://support.ca.com/ site. Log in and click Download Center. The product
files on this online site will always be the most up-to-date.

Chapter 6: Installing Your Product from DVD 69

Introduction to Electronic Software Delivery

CA Product Documentation
After completing the procedures in this ESD guide, you are ready to begin the standard
installation procedure. To continue the installation process, see your CA product-specific
documentation.

Each CA product documentation set includes the latest technology available for online
viewing, keyword searching, book marking, and printing. Documentation sets reside in
one repository and are available at the CA Support Online web site. You can view and
download all CA product documentation from this central repository. The following
procedure details how to access product documentation.

To download documentation from Support Online

1. On the Web, go to https://support.ca.com/.
The CA Support Online Web page appears.
2. Click login at the top of the page.
The Log in window opens.
3. Type a registered CA Support Online email address and password, and click Login.
The CA Support Online Web page re-opens, and you are logged into CA Support
Online.
4. Select Documentation located on the left side.
The Documentation Web page opens.
5. In Find a Product Documentation Bookshelf, choose your product from the
drop-down list, and click Go.
The CA product documentation bookshelf web page opens.
6. Locate and view the HTML pages of your product-specific documentation; you can
also view and download the PDF file.

Introduction to Electronic Software Delivery

What is Electronic Software Delivery?

CA supports a Pax-Enhanced ESD process that uses a UNIX portable archive interchange
(pax) file that contains the product package.

The CA Electronic Software Delivery (ESD) process lets you download a product package
in a zip file or compressed individual product components from the CA Support Online
Download Center or from directories on your CA product DVD. This guide explains the
steps to copy pax files from a product DVD. To download pax files from support online,
go to the Download Center on https://support.ca.com/.

70 Installation Guide
 Introduction to Electronic Software Delivery

The steps in this guide provide instructions for SMP/E CA product installation on z/OS
systems.

The pax (see page 72) format provides several advantages for ESD:
■ It supports virtually any file type or data set type, including those for products that
are based on new technology (for example, Java).
■ It supports combining a large number of data sets into a single file to receive in a
single download.
■ It can be unpacked using standard utilities that are available on every z/OS system.
Customers no longer have to install CA-proprietary utility programs or download
additional software to complete the installation process.

The Pax Enhanced ESD process is the foundation on which the CA Mainframe Software
Manager (MSM) was built. CA MSM can perform the required un-packing tasks.

Important! Most CA products have transitioned to the pax format and must be
processed using the Pax-Enhanced ESD process. A small number of products are still
packaged using the traditional ESD format or as legacy .AWS or .CDTAPE files. For
traditional installation downloads, see the Traditional ESD User Guide.

ESD Product Copy from a DVD

The DVD contains folders that include the pax files for the base product and a README
file.

See Check for the Latest Updates (see page 71) for currency information and the Pax
Command (see page 72) for an explanation about how this command works.

Check for the Latest Updates

Important! The files provided for copy from the CA product DVD might not be the most
current.

Go to https://support.ca.com/, log in, and click Download Center. The files on this online
site will always have the most current product updates.

File Types that Might Be Found in a Zip File Package

Important! If your package includes file types other than those types in the following
list, see the Traditional Electronic Software Delivery (ESD) Guide. To access this guide, go
to https://support.ca.com/, log in, and click Download Center. A link to the guide
appears under the Download Help heading.

If you download the product from a CA product DVD, you see one or more files with the
following file types:

Chapter 6: Installing Your Product from DVD 71

Introduction to Electronic Software Delivery

ESD Pax Files:

.pax.Z (see page 72)
Identifies a compressed UNIX file containing product files for the enhanced ESD
process.

Documentation Files:
readme_CA_VIEW_DVD.html or Readme.html
Lists a description of the files and instructions for accessing product installation
documentation. The actual file name may differ based on the product name.

Important! The product-specific directory may also contain an AREADME file that
describes the pax download and installation process for your CA product or
maintenance update. Read the AREADME file before running UNZIPJCL. If your directory
includes install notes, read them before continuing. Failure to read these files impacts
your installation.

The PAX Command

The pax command does the following:

■ Extracts the files and directories packaged within the pax file.
■ Creates a new USS directory in the same directory structure where the pax file
resides.
■ Automatically generates a product and level-specific directory name.
For example, the directory created by CA MIM Resource Sharing - MVS release 11.6,
genlevel 0809 pax is MIM1160809. The remaining samples in this guide show this
sample folder.

Important! Ensure that you have sufficient free space in the USS file system that you are
using for Pax ESD to hold the directory created by the pax command and its contents.
You need approximately 3.5 times the pax file size in free space.

If you do not have sufficient free space, you receive EDC5133I error messages similar to
the following:

pax: FSUM6260 write error on file "MIM116SP2/UNZIPJCL": EDC5133I

No space left on device.

72 Installation Guide
 Pax-Enhanced ESD Procedures

Pax-Enhanced ESD Procedures

How to Install a Product from a DVD Using Pax-Enhanced ESD

This section describes the Pax-Enhanced ESD DVD install process. We recommend that
you read this overview carefully and follow the entire procedure the first time you
complete a Pax-Enhanced ESD installation.

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 used
for the ESD process.

Important! If you prefer not to involve all CA product installers with z/OS UNIX System
Services, assign a group familiar with USS to perform Steps 1 through 3 and provide the
list of the unpacked MVS data sets to the product installer. Be aware that some
products may require USS and/or USS SuperUser authority for additional installation
steps.

More Information:

USS Environment Setup (see page 36)

Allocate and Mount a File System (see page 37)
Copy the Product Pax Files into Your USS Directory (see page 40)
Create a Product Directory from the Pax File (see page 45)
Copy Installation Files to z/OS Data Sets (see page 46)
Receive the SMP/E Package (see page 47)

The Installation Procedure

There are four parts to the installation procedure:
1. Copy the files.
2. Install the files using the pax.z file.
3. Create a product Directory from the Pax File.
4. Complete the installation using your product documentation.

Chapter 6: Installing Your Product from DVD 73

Pax-Enhanced ESD Procedures

Copy the Files

To copy the files
■ Copy the entire product software package to your PC from the CA product DVD.
Note: Do not change the format of the pax.Z file.=

Install the Files Using the pax.Z File

After copying the pax.Z files to your PC, do the following to upload the files from your PC
to your z/OS USS directory.

To install files using the pax.Z file

1. Open a Windows command prompt.
The command prompt appears.
2. Customize and enter the FTP commands with the following changes:
■ Replace mainframe with the z/OS system's IP address or DNS name.
■ Replace userid with your z/OS user ID.
■ Replace password with your z/OS password.
■ Type bin
This sets the transfer type to binary.
■ Replace C:\PC\folder\for\thePAXfile with the location of the pax file on your
PC.
Note: If you specify a location that has blanks or special characters in the path
name, you must enclose that value in double quotation marks.
■ Replace yourUSSESDdirectory with the name of the USS directory that you use
for ESD downloads.
■ Replace paxfile.pax.Z with the name of the pax file to upload.
3. Click Enter.
The pax file is transferred to the mainframe.
The following list is a sample of the FTP commands needed to upload the pax file
from your PC to your USS Pax-Enhanced ESD directory:
FTP mainframe
userid
password

74 Installation Guide
 Pax-Enhanced ESD Procedures

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

Create a Product Directory from the Pax File

Important! The sample job Unpackage.txt (see page 76) simplifies the Pax-Enhanced
ESD process; you can copy this JCL job directly to the mainframe.
To create a product installation directory using the Unpackage.txt sample job
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: After making the changes noted in the job, 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 6: Installing Your Product from DVD 75

Pax-Enhanced ESD Procedures

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

The following is the text for the 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=*

Complete the Installation

At this point, the product has been copied from the DVD onto the PC and the file has
been FTP’d to USS and is now ready to be unpaxed.
To complete the installation
1. Access the Installation Guide in the documentation set for your product.
2. See the "Installing your product from PAX-Enhanced Electronic Software Delivery"
chapter:
In the How to Install a Product Using Pax-Enhanced ESD topic, see the Use the
SMP/E GIMUNZIP Utility step to proceed with the installation.

76 Installation Guide
 References

References

IBM Reference Manual

If you need additional information on UNIX System Services (USS) or SMP/E, see these
IBM reference manuals:
■ SMP/E for z/OS Reference (SA22-7772)
■ z/OS UNIX System Services User's Guide (SA22-7801)
■ z/OS UNIX System Services Command Reference (SA22-7802)

Common USS Commands

This section includes basic definitions for common UNIX System Services (USS)
commands:
cd
Changes directory.
chgrp
Changes ownership of one or more files to a new group ID.
chmod
Changes file permissions.
chown
Changes the file owner. This command changes the owning UID, GID, or both.
diff
Compares file or directory contents. diff -gr dir1/ dir2/ lists files that are different in
dir1 and dir2.
find
Finds files with specified attributes.
grep
Finds text strings in files. For example, grep -i string * scans all files in the current
directory for the specified string. The -i means that the search is not case-sensitive.
iconv
Converts from one character set to another.

Chapter 6: Installing Your Product from DVD 77

References

lp
Directs output to line printer.
ls
Lists the file in a directory.
man
Displays the UNIX help for a command. For example, man chmod displays the UNIX
help for the chmod command.
mkdir
Creates a directory.
mv
Moves or renames one or more files or directories.
nm
Displays the symbol table from an executable file.
rm
Deletes a file or directory.
od
Produces an octal dump of a file. Also does hexadecimal dumps.
ps
Displays information about active processes.
strings
Lists text strings in an executable file.
wall
Sends a message to all logged in users.
whence
Identifies the location of an executable file.
who
Displays the logged on users and information about them.

78 Installation Guide
Chapter 7: Starting Your Product
This section describes what you need to do to start CA Deliver.

This section contains the following topics:

How to Complete Deployment With CA MSM (see page 79)
How to Complete Configuration With CA MSM (see page 79)
How to Configure Without CA MSM (see page 91)

How to Complete Deployment With CA MSM

The topics in this section describe the manual tasks you perform when deploying your
product using CA MSM (see page 28).

How to Complete Configuration With CA MSM

The topics in this section describe the manual tasks you perform when configuring your
product using CA MSM (see page 29).

Authorize Program Load Libraries

All users must perform this step.

To either authorize the program load library or copy the modules to a

system-authorized library, do one of the following:
■ If you want CA Deliver to execute from its own load library, APF-authorize the load
library by adding an entry for CAI.CVDELOAD to member PROGxx of SYS1.PARMLIB.
Note: Use MVS system command SET PROG=xx to activate update to PROGxx.
■ If you do not want to APF-authorize the CA Deliver target library, copy the load
modules in CAI.CVDELOAD to an existing authorized library such as SYS1.LINKLIB or
any other library in the linklist.
Use one of the following methods to copy the load modules:
– ISPF option 3.3
– Member HBRNCAPF of CAI.CVDEJCL
Run this batch job to copy the load modules from CAI.CVDELOAD to
USER.APFLIB.

Chapter 7: Starting Your Product 79

How to Complete Configuration With CA MSM

Important: We recommend that you authorize CVDELOAD rather than copying the
modules. The load modules must reside in an authorized library.

Enter the LMP Code

All users must perform this step.

CA Deliver requires CA LMP (License Management Program), one of the CA Common

Services, to initialize correctly. CA LMP provides a standardized and automated
approach to the tracking of licensed software. Examine the CA LMP Key certificate you
received with your product installation or maintenance cartridge.

80 Installation Guide
 How to Complete Configuration With CA MSM

The LMP Key Certificate

Your LMP Key certificate contains the following information:

Product Name
Signifies the trademarked or registered name of the copy of CA Deliver licensed for
your designated site and CPUs.
Supplement
Signifies the reference number of your license for the particular CA Deliver, in the
format nnnnnn nnn.
This format differs slightly inside and outside North America and, in some cases,
may not be provided at all.
Expiration Date
Signifies the date (MONTH dd, yyyy as in OCTOBER 21, 2009) when your license
expires for the installation and maintenance of the designated CA Deliver.
Technical Contact
Signifies the name of the technical contact at your site who is responsible for the
installation and maintenance of CA Deliver.
This is the person to whom CA addresses all CA LMP correspondence.
MIS Director
Signifies the name of the Director of MIS, or the person who performs that function
at your site.
If the title, but not the individual's name, is indicated on the certificate, you should
supply the actual name when correcting and verifying the certificate.
CPU Location
Signifies the address of the building where the CPU is installed.
Execution Key
Signifies the encrypted code required by CA LMP for CA Deliver initialization.
During installation, this code is referred to as the LMP Code.
Product Code
Signifies the two-character code that corresponds to CA Deliver.
CPU ID
Signifies a code that identifies the specific CPU for which installation of your CA
Deliver is valid.

The CA LMP execution key (provided on the key certificate) must be added to the
CAIRIM parameters to ensure proper initialization of the CA software solution.

Chapter 7: Starting Your Product 81

How to Complete Configuration With CA MSM

Defining the CA LMP Execution Key

To define a CA LMP execution key to the CAIRIM parameters, modify member KEYS in
OPTLIB data set.

Syntax is as follows:

PROD(pp) DATE(ddmmmyy) CPU(tttt-mmmm/ssssss)

LMPCODE(kkkkkkkkkkkkkkkk)

where:
pp
Signifies the two-character product code (required).
For any given CA LMP software solution, this code agrees with the product code
already in use by the CAIRIM initialization parameters for earlier service packs of
the product.
ddmmmyy
Signifies the CA LMP licensing agreement expiration date (required).
tttt-mmmm
Signifies the CPU type and model (for example, 3090-600) on which the CA LMP
software solution will run (required).
If the CPU type and/or model requires less than four characters, blank spaces are
inserted for the unused characters.
ssssss
Signifies the serial number of the CPU on which the CA LMP software solution will
run (required).
kkkkkkkkkkkk
Signifies the execution key needed to run the CA LMP software solution (required).
This CA LMP execution key is provided on the key certificate shipped with each CA
LMP software solution.

This example shows a control statement for the CA LMP execution software parameter.

Note: The CA LMP execution key is invalid and is provided as an example only.

PROD(HV) DATE(21OCT09) CPU(3090-600 /370623)

LMPCODE(52H2K06130Z7RZD6)

For a full description of the procedure for defining the CA LMP execution key to the
CAIRIM parameters, see the installation tasks in the CA Common Services Getting
Started.

82 Installation Guide
 How to Complete Configuration With CA MSM

Multiple LMP Codes

CA Deliver consists of the base product and several components (options) that are
purchased separately. Because each component has its own LMP code, you must supply
an LMP code for each component you purchased.

This table lists the component product codes:

pp Component Description
HV CA Deliver base product
HW CICS online interface
HX IMS/DC online interface
HZ Native TSO online interface
IF CA Roscoe online interface

IJ VTAM online interface

Note: For more information about the components, see Software Requirements in the
chapter "System Requirements."

Define Security Rules

All users must perform this step.

Upgrade Considerations

If you are upgrading, see the chapter "Upgrading from a Prior Release" for information
that applies to this step.

CA Deliver has full external security support that uses security classes. CA Deliver
interfaces with CA Top Secret, CA ACF2, and IBM's RACF and it gives you the ability to
define a security table and use security exits.

Note: For more information about security, see the chapter "Security" in the CA Deliver
Reference Guide.

Install the ISPF Online Retrieval Option

The ISPF online retrieval option runs under the IBM Interactive System Productivity
Facility (ISPF).

Chapter 7: Starting Your Product 83

How to Complete Configuration With CA MSM

This list summarizes the steps required to install the ISPF online retrieval option.
Detailed instructions are in the sections that follow.
1. (Optional) Add STEPLIB Statements
If the load modules were not copied to a linklist library, add STEPLIB DD statements
to the TSO LOGON procedures.
2. Add the Panel and Command Libraries
Add the panel and command table libraries to the TSO LOGON procedures.
3. (Optional) Modify an ISPF Selection Menu to Select Online Retrieval.

(Optional) Step 1: Add STEPLIB Statements

The action you take in this step depends on what you did during the base product
installation—specifically, did you:
■ Authorize the program load library or
■ Copy the modules to a system-authorized library

If the CA Deliver load modules were not copied to one of the libraries in the linklist,
proceed with this step; otherwise go directly to the next step.

Follow these steps:

1. Add STEPLIB DD statements to the TSO LOGON procedures if the load modules are
not in a linklist library.
2. Add a STEPLIB DD statement for the library containing the product's load modules
to the LOGON procedures for those TSO users who are going to be using the ISPF
online retrieval option.

Note: If you have CA View, the CA View load modules must also be either in the linklist
or in a STEPLIB statement with this step.

Step 2: Add the Panel and Command Libraries (ISPF only)

Note: If you are running under SPF, go to Step 3.

If you run CA Deliver under ISPF, proceed with this step.

To add the panel and command libraries to the TSO LOGON procedure:
1. Concatenate the command table library CAI.CVDETBL0 to DD statement ISPTLIB.
2. Concatenate the panel library CAI.CVDEPNL0 to DD statement ISPPLIB.

Note: If you also plan to use RMOSPF (the ISPF interface), and multiple versions of CA
Deliver, concatenate CAI.CVDETBL0 first. Use the CAI.CVDETBL0 from the most current
release.

84 Installation Guide
 How to Complete Configuration With CA MSM

Step 3: (Optional) Modify an ISPF Selection Menu to Select Online Retrieval

If you want to add a selection code for the online retrieval feature to one of the ISPF
selection menus, proceed with this step; otherwise, your detailed instructions for ISPF
are complete.

To define your selection code, use the following command:

PGM(RMOSPF) PARM(high-level-database-name) NEWAPPL(RMO)

Use the value next to the NAME parameter on your Initialization Parameter Worksheet
for PARM (high-level-database-name).

Note: Adding a selection code allows you to select the online retrieval feature in the
same way you would select other ISPF options.

Panel Libraries

The names of the panel libraries vary from site to site and for the different releases of
ISPF. These panel libraries are allocated to the ISPPLIB DD statement under TSO.

Be aware that some installations do not allow direct modifications of IBM panels and
libraries. In this case, you can place the modified panels in user or site-specific libraries
and concatenate them ahead of the IBM libraries.

Ask your system administrator for the specific ISPF panel library that applies to your site
and contains the panel ISR@PRIM.

Note: The selection menus shown in the following examples are part of the program
product ISPF and are copyrighted by IBM.

Example 1

This example shows you how to add selection code R to the primary option menu
ISR@PRIM for ISPF.

The offset lines are the inserted lines.

Chapter 7: Starting Your Product 85

How to Complete Configuration With CA MSM

%----------------------- ISPF/PDF PRIMARY OPTION MENU ------------------------

%OPTION ===>_ZCMD +
% +USERID - &ZUSER
% 0 +ISPF PARMS - SPECIFY TERMINAL AND USER PARAMETERS +TIME -
% 1 +BROWSE - DISPLAY SOURCE DATA OR OUTPUT LISTINGS +TERMINAL -
% 2 +EDIT - CREATE OR CHANGE SOURCE DATA +PF KEYS - &ZKEYS
% 3 +UTILITIES - PERFORM UTILITY FUNCTIONS
% 4 +FOREGROUND - INVOKE LANGUAGE PROCESSORS IN FOREGROUND
% 5 +BATCH - SUBMIT JOB FOR LANGUAGE PROCESSING
% 6 +COMMAND - ENTER TSO COMMAND, CLIST, OR REXX EXEC
% 7 +DIALOG TEST - PERFORM DIALOG TESTING
% 8 +LM UTILITIES - PERFORM LIBRARY ADMINISTRATOR UTILITY FUNCTIONS
% C +CHANGES - DISPLAY SUMMARY OF CHANGES FOR THIS RELEASE
% R +RMOSPF - DELIVER ADMINISTRATION
% T +TUTORIAL - DISPLAY INFORMATION ABOUT ISPF/PDF
% X +EXIT - TERMINATE ISPF USING LOG AND LIST DEFAULTS

%
+ENTER%END+COMMAND TO TERMINATE ISPF.
)INIT
.HELP = ISR00003
&ZPRIM = YES /* ALWAYS A PRIMARY OPTION MENU */
&ZHTOP = ISR00003 /* TUTORIAL TABLE OF CONTENTS */
&ZHINDEX = ISR91000 /* TUTORIAL INDEX - 1ST PAGE */
)PROC
&ZSEL = TRANS( TRUNC (&ZCMD,'.')
0,'PANEL(ISPOPTA)'
1,'PGM(ISRBRO) PARM(ISRBRO01)'
2,'PGM(ISREDIT) PARM(P,ISREDM01)'
3,'PANEL(ISRUTIL)'
4,'PANEL(ISRFPA)'
5,'PGM(ISRJB1) PARM(ISRJPA) NOCHECK'
6,'PGM(ISRPTC)'
7,'PGM(ISPYXDR) PARM(ISR) NOCHECK'
8,'PANEL(ISRLPRIM)'
C,'PGM(ISPTUTOR) PARM(ISR00005)'
R,'PGM(RMOSPF) PARM(RMO.SYSTEM1) NEWAPPL(RMO)'
T,'PGM(ISPTUTOR) PARM(ISR00000)'
' ',' '
X,'EXIT'
*,'?' )
&ZTRAIL = .TRAIL
)END

86 Installation Guide
 How to Complete Configuration With CA MSM

Note:
■ NEWAPPL(RMO) is required and must be specified as shown previously in this
section.
This parameter is used with the command table library concatenation from Step 3
of the ISPF Installation Instructions.
■ NEWAPPL(RMO) allows CA Deliver to correctly interpret commands and program
function key invocation.
If this parameter is not specified, certain PF keys such as the scroll keys may not
function.

Chapter 7: Starting Your Product 87

How to Complete Configuration With CA MSM

Example 3

This example shows you how to add selection code 3.R as a sub-option to the utilities
menu ISPUTIL for ISPF.

The offset lines are the inserted lines.

%----------------------- UTILITY SELECTION MENU --------- -----------
%OPTION ===>_OPT +
% +
% 1 +LIBRARY - LIBRARY UTILITY:
+ PRINT INDEX LISTING OR ENTIRE DATASET
+ PRINT, RENAME, DELETE, OR BROWSE MEMBERS
+ COMPRESS DATASET
% 2 +DATASET - DATASET UTILITY:
+ DISPLAY DATASET INFORMATION
+ ALLOCATE, RENAME, OR DELETE ENTIRE DATASET
+ CATALOG OR UNCATALOG DATASET
% 3 +MOVE/COPY - MOVE OR COPY MEMBERS OR DATASETS
% 4 +CATALOG - CATALOG MANAGEMENT:
+ DISPLAY OR PRINT CATALOG ENTRIES
+ INITIALIZE OR DELETE USER CATALOG ALIAS
% 5 +RESET - RESET STATISTICS FOR MEMBERS OF ISPF LIBRARY
% 6 +HARDCOPY - INITIATE HARDCOPY OUTPUT
% 7 +VTOC - DISPLAY OR PRINT VTOC ENTRIES FOR A DASD VOLUME
% 8 +OUTLIST - DISPLAY, DELETE, OR PRINT HELD JOB OUTPUT
% 9 +SCRIPT/VS - FORMAT,DISPLAY, AND OPTIONALLY PRINT SCRIPT TEXT
% R +RMOSPF - DELIVER ADMINISTRATION

)INIT
.HELP = TU
)PROC
&SEL = TRANS( TRUNC (&OPT,'.')
1,'PGM(ISPUDA) PARM(UDA1)'
2,'PGM(ISPUDA) PARM(UDA1)'
3,'PGM(ISPUMC)'
4,'PGM(ISPUCA)'
5,'PGM(ISPURS)'
6,'PGM(ISPUHC)'
7,'PGM(ISPUVT)'
8,'PGM(ISPUOL) PARM(UOL01)'
9,'PGM(ISPUSC) PARM(SCRPTA)'
R,'PGM(RMOSPF) PARM(RMO.SYSTEM1) NEWAPPL(RMO)'
' ',' '
*,'?' )
)END

88 Installation Guide
 How to Complete Configuration With CA MSM

Install the TSO Online Retrieval Option

The following step is required to install the TSO online retrieval option and is explained
in detail in the next topic.

(Optional) Add STEPLIB DD statements to the TSO LOGON procedures if the load
modules are not in a linklist library.

Step 1: (Optional) Add STEPLIB DD Statements

The action you take in this step depends on what you did during the base-product
installation—specifically, did you:
■ Authorize the program load library or
■ Copy the modules to a system authorized library

If the load modules were not copied to one of the libraries in the linklist:
■ Add a STEPLIB DD statement (for the library containing the load modules) to the
TSO LOGON procedures for those TSO users who are to use the native TSO online
retrieval option.

If the load modules were copied to one of the libraries in the linklist, no STEPLIB DD
statements are required.

Note: If you have CA View, the CA View load modules either must also be in the linklist,
or placed in a STEPLIB statement with this step.

Step 2: (Optional) Add Mount Attributes

Assign the mount attribute to all TSO user IDs authorized to browse SYSOUT directly
from an archival tape. Use the TSO ACCOUNT command to assign the mount attribute as
follows:

ACCOUNT
C (userid) MOUNT
END

Chapter 7: Starting Your Product 89

How to Complete Configuration With CA MSM

Install the CA Roscoe Online Retrieval Option

The CA Roscoe online retrieval option runs as a command processor under
ETSO/Roscoe.

The following steps are required to install the CA Roscoe/Cross-Memory Online

Retrieval Option. Each step is explained in detail in the sections that follow.
1. (Optional) Concatenate the Load Module Library to the ETSOLIB DD statement, if
the load modules were not copied to a linklist library.
2. Add the control statement for the RMOROS command processor to the Eligible
Program List (EPL).
3. Invoke the RMOROS command processor.

Step 1: (Optional) Concatenate the Load Module Library

If the load modules were not copied to a linklist library, concatenate the library that
contains the load modules to the ETSOLIB DD statement in the CA Roscoe startup JCL.

Note: If you have CA View, the CA View load modules must also be either in the linklist
or in an ETSOLIB statement with this step.

Step 2: Add RMOROS Command Process

Add this Eligible Program List control statement to member ETSOPGMS for the CA
Roscoe user with the RO prefix:

Column Contents
1–8 RMOROS
9 Blank
10–12 Number of users allowed to access CA Deliver at one time
13 Blank
14–17 CPU time slice; use 9999 to prevent premature termination
18 Blank
19–24 Maximum memory (in KB) below the 16 MB line
This value can vary depending on size of database and other factors
(0001000 should be adequate).
25 Blank
26–31 Maximum memory (in KB) below the line that CA Deliver can acquire
at one time
Use 999999 so that GETMAINs are not limited.

90 Installation Guide
 How to Configure Without CA MSM

Column Contents
32 Blank
33–38 Maximum memory (in KB) above the 16 MB line
This value can vary depending on the features used (000512 should
be adequate).
39 Blank
40–45 Maximum memory (in KB) above the line that CA Deliver can acquire
at one time
Use 999999 so that GETMAINs are not limited.
46 Blank
47–48 CP to call RMOROS as a TSO command processor
49 Y – Application authorized to issue MODESET SVC
50 Blank
51-52 CP to call EC0XMROS as a TSO command processor
53-255 Ignored

Install the XMS Online Interfaces (Optional)

If you want to install the XMS Online Interfaces to complete configuration with MSM see
the topic How to Complete Configuration of the XMS Online Interfaces with CA MSM in
the chapter Installing the Online Interfaces.

How to Configure Without CA MSM

The topics in this section describe the manual tasks you perform if you are not
configuring your product using CA MSM.

Step 1: Authorize Program Load Libraries

All users should perform this step.

Do one of the following to either authorize the program load library or copy the
modules to a system-authorized library:
■ If you want CA Deliver to execute from its own load library, APF-authorize the load
library by adding an entry for CAI.CVDELOAD to member PROGxx of SYS1.PARMLIB.
Note: Use MVS system command SET PROG=xx to activate update to PROGxx.

Chapter 7: Starting Your Product 91

How to Configure Without CA MSM

■ If you do not want to APF-authorize the CA Deliver target library, copy the load
modules in CAI.CVDELOAD to an existing authorized library such as SYS1.LINKLIB or
any other library in the linklist.
Use one of the following methods to copy the load modules:
– ISPF option 3.3
– Member HBRNCAPF of CAI.CVDEJCL
This batch job can be run to copy the load modules from CAI.CVDELOAD to
USER.APFLIB.

Important: We recommend that you authorize CVDELOAD rather than copying the
modules. The load modules must reside in an authorized library.

Step 2: Enter the LMP Code

All users must perform this step.

CA Deliver requires CA LMP (License Management Program), one of the CA Common

Services, to initialize correctly. CA LMP provides a standardized and automated
approach to the tracking of licensed software.

Examine the CA LMP Key certificate you received with your product installation or
maintenance cartridge.

92 Installation Guide
 How to Configure Without CA MSM

The LMP Key Certificate

Your LMP Key certificate contains the following information:

Product Name
Signifies the trademarked or registered name of the copy of CA Deliver licensed for
your designated site and CPUs.
Supplement
Signifies the reference number of your license for the particular CA Deliver, in the
format nnnnnn nnn.
This format differs slightly inside and outside North America and, in some cases,
may not be provided at all.
Expiration Date
Signifies the date (MONTH dd, yyyy as in OCTOBER 21, 2009) when your license
expires for the installation and maintenance of the designated CA Deliver.
Technical Contact
Signifies the name of the technical contact at your site who is responsible for the
installation and maintenance of CA Deliver.
This is the person to whom CA addresses all CA LMP correspondence.
MIS Director
Signifies the name of the Director of MIS, or the person who performs that function
at your site.
If the title, but not the individual's name, is indicated on the certificate, you should
supply the actual name when correcting and verifying the certificate.
CPU Location
Signifies the address of the building where the CPU is installed.
Execution Key
Signifies the encrypted code required by CA LMP for CA Deliver initialization.
During installation, this code is referred to as the LMP Code.
Product Code
Signifies the two-character code that corresponds to CA Deliver.
CPU ID
Signifies a code that identifies the specific CPU for which installation of your CA
Deliver is valid.

The CA LMP execution key (provided on the key certificate) must be added to the
CAIRIM parameters to ensure proper initialization of the CA software solution.

Chapter 7: Starting Your Product 93

How to Configure Without CA MSM

Defining the CA LMP Execution Key

To define a CA LMP execution key to the CAIRIM parameters, modify member KEYS in
OPTLIB data set.

Syntax is as follows:

PROD(pp) DATE(ddmmmyy) CPU(tttt-mmmm/ssssss)

LMPCODE(kkkkkkkkkkkkkkkk)

where:
pp
Signifies the two-character product code (required).
For any given CA LMP software solution, this code agrees with the product code
already in use by the CAIRIM initialization parameters for earlier service packs of
the product.
ddmmmyy
Signifies the CA LMP licensing agreement expiration date (required).
tttt-mmmm
Signifies the CPU type and model (for example, 3090-600) on which the CA LMP
software solution will run (required).
If the CPU type and/or model requires less than four characters, blank spaces are
inserted for the unused characters.
ssssss
Signifies the serial number of the CPU on which the CA LMP software solution will
run (required).
kkkkkkkkkkkk
Signifies the execution key needed to run the CA LMP software solution (required).
This CA LMP execution key is provided on the key certificate shipped with each CA
LMP software solution.

This example shows a control statement for the CA LMP execution software parameter.

Note: The CA LMP execution key is invalid and is provided as an example only.

PROD(HV) DATE(21OCT09) CPU(3090-600 /370623)

LMPCODE(52H2K06130Z7RZD6)

For a full description of the procedure for defining the CA LMP execution key to the
CAIRIM parameters, see the installation tasks in the CA Common Services Getting
Started.

94 Installation Guide
 How to Configure Without CA MSM

Multiple LMP Codes

CA Deliver consists of the base product and several components (options) that are
purchased separately. Because each component has its own LMP code, you must supply
an LMP code for each component you purchased.

This table lists the component product codes:

pp Component Description
HV CA Deliver base product
HW CICS online interface
HX IMS/DC online interface
HZ Native TSO online interface
IF CA Roscoe online interface

IJ VTAM online interface

Note: For more information about the components, see Software Requirements in the
chapter "System Requirements."

Step 3: Define Security Rules

All users must perform this step.

Upgrade Considerations

If you are upgrading, see the chapter "Upgrading from a Prior Release" for information
that applies to this step.

CA Deliver has full external security support that uses security classes. CA Deliver
interfaces with CA Top Secret, CA ACF2, and IBM's RACF and it gives you the ability to
define a security table and use security exits.

Note: For more information about security, see the chapter "Security" in the CA Deliver
Reference Guide.

Step 4: Create/Update the Database

All new users must perform this step.

Chapter 7: Starting Your Product 95

How to Configure Without CA MSM

Upgrade Considerations

If you are upgrading, see the chapter "Upgrading from a Prior Release" for more
information about how to perform this step.

For new installations, to create the database use the ADDDS and MAKECKPT control
statements in the RMODBASE utility program. Member HBRNADDS of CAI.CVDEJCL
provides a sample set of parameters for this job.

Note: For more information about the RMODBASE utility, see the chapter "Utilities" in
the CA Deliver Reference Guide.

Step 5: Create the Initialization Parameter Statements

All users must perform this step.

Upgrade Considerations

If you are upgrading, see the chapter "Upgrading from a Prior Release" for information
that applies to this step.

For new installations, create the initialization parameter statements for the started task
which can be a member within a PDS. This member is referenced by the RMOPARMS DD
statement of the started task. Member RMOPARMS in CAI.CVDEOPTN provides a
sample initialization parameter member.

Note: For more information about the descriptions of these parameters, see the chapter
"Initialization Parameters" in the Reference Guide.

The data sets for the initialization parameter statements must:

■ Be members in a partitioned data set
■ Have a logical record length of 80 (LRECL=80)
■ Have a block size of any multiple of 80 (for example, BLKSIZE=3200)
■ Have record format FB (RECFM=FB)

Step 6: Modify the Skeleton JCL

All users must perform this step.

Examine the skeleton JCL and make any necessary changes by editing member RMOJCLB
in the CAI.CVDEPENU data set. The following sections explain how to do this editing.

The online task uses the skeleton JCL to submit background bundle jobs.

96 Installation Guide
 How to Configure Without CA MSM

Bundle Output Carriage Control

By default, machine carriage control produces batch bundle output for all banner pages
and reports within the bundle.

If changes are required, the RMOJCLB skeleton JCL can be modified to instruct the batch
bundle program to create batch bundle output with ASA carriage control. You can
specify this option by adding ",ASA" after the database index name variable &IDX on the
PARM field of the EXEC statement for RMOBBP in the skeleton JCL as follows:
//STEP1 EXEC PGM=RMOBBP,
// PARM='&IDX,ASA'

Notes:
■ By default, the beginning of each individual SYSOUT data set within the bundle
contains a no skip ("+") ASA carriage control character. If you want the individual
SYSOUT data sets to start with a skip to top of form ("1") ASA carriage control
character, change the model bundle banner page members to use a "J" carriage
control character instead of a "1" carriage control character.
■ For more details on how to customize model banner pages, see the chapter Model
Banner Pages in the Reference Guide.

Define STEPLIBs

The only change yto make to the skeleton JCL is to the STEPLIB DD statement. If you are
running CA View out of a separate CVDELOAD, the STEPLIB statement has to
concatenate both the CA Deliver and CA View CVDELOADs.

Remove the STEPLIB DD statement if the CVDELOAD (or CVDELOADs) are in your linklist.

Be aware that you must concatenate the CA View load library after the CA Deliver load
library in the STEPLIB statement.

Step 7: Load the Online Panels and JCL Library

All users must perform this step.

Upgrade Considerations

If you are upgrading, see the chapter "Upgrading from a Prior Release" for more
information about this step.

Load the online panel and JCL library members to the database from the CAI.CVDEPENU
data set.

Chapter 7: Starting Your Product 97

How to Configure Without CA MSM

The RMODBASE OLOAD control statement is used to load the panel, message, and
skeleton JCL members in the online library to the database. The online library is defined
with the DD statement RMOOLIB.

Note: The high-level name of the database must have been defined with the NAME
control statement (or the PARM parameter of the EXEC JCL statement).

Syntax:

OLOAD

Member HBRNOLOD of CAI.CVDEJCL provides sample JCL for this job.

Customizing BROWSE and HELP Panels

The CAI.CVDEPENU data set contains the BROWSE and HELP panels; you can modify
them with the following limitations:
Constants:
Constants can be modified and their length can be increased or decreased. The new
text displays as coded.
Variables:
■ Most variables can be moved around the screen as long as the original variable
names are retained
Be aware that the relative position of some variables is critical.
■ The length of a variable can be changed, but be aware that the product pads
the value with blanks (or truncates it) to conform to its internal length.
■ Any variable can be deleted from a panel.
■ An attempt to add a new variable to a screen results in the variable name itself
appearing on the screen, without interpretation.

Customizing Panels for Color and Highlight

CA Deliver supports the display of the following colors:

■ Blue
■ Red
■ Pink
■ Green
■ Turquoise
■ Yellow
■ White

98 Installation Guide
 How to Configure Without CA MSM

CA Deliver supports the following highlight attributes:

■ Blink
■ Reverse video
■ Underscore

Note: For these attributes, the colors used must be red, white, blue, or green.

Define color and highlight attributes on the CA Deliver panels according to the rules
listed in the IBM manual ISPF Dialog Developer's Guide and Reference.

The following hexadecimal characters are reserved and cannot be defined as attribute
statements on a panel:
00
Represents Null character.
0E
Represents Shift out.
0F
Represents Shift in.
40
Represents Blank.
50
Represents Ampersand (&).

Step 8: Load the Model Banner Pages and Email Format (EFORMAT) members
All users must perform this step.

Upgrade Considerations

If you are upgrading, see the chapter "Upgrading from a Prior Release" for more
information about this step.

Review, change, or add model banner page and/or email format members in the model
banner page library.

Note: For more information about model banner page and email format members, see
the chapter "Model Banner Page and Email Format Members" in the Reference Guide.

Load the model banner page and email format members to the database from the
CAI.CVDE133 data set.

Chapter 7: Starting Your Product 99

How to Configure Without CA MSM

The RMODBASE BLOAD control statement is used to load the model banner page and
email format members in the model banner page library to the database. The model
banner page library is defined with the DD statement RMOBLIB.

Note: The high-level name of the database must have been defined with the NAME
control statement (or the PARM parameter of the EXEC JCL statement).

Syntax:

BLOAD

Member HBRNBLOD of CAI.CVDEJCL provides sample JCL for this job.

Step 9: Add the Start Procedure to PROCLIB

All users must perform this step.

Upgrade Considerations

If you are upgrading, see the chapter "Upgrading from a Prior Release" for more
information about this step.

Add the Start Procedure

To add the start procedure to the PROCLIB for the started task:
1. Add the start procedure JCL, located in CBRNSSTC in CAI.CBRNPROC, as member
RMOSTC of SYS1.PROCLIB:
//RMOSTC EXEC PGM=RMOSTC,TIME=1440,REGION=128M
//STEPLIB DD DSN=CAI.CVDELOAD,DISP=SHR
//SYSUDUMP DD SYSOUT=A
//RMOPARMS DD DSN=CAI.CVDEOPTN(RMOPARMS),DISP=SHR
//*RMOJTAB DD DSN=your.rmojtab,DISP=SHR

2. Set the recommended CA Deliver REGION size.

We recommend that you run CA Deliver with a minimum REGION=128M. This
covers the current storage requirements for a daily cycle and can be useful and still
provide a reserve that might be needed when extra storage is required.
Alternately, if you do not want to set the REGION size to 128M, start RMOSTC with
a 128M region and continue with the same value for at least two days to monitor
the processing for two daily cycles.
Bring RMOSTC down and review the IEF374I message in the JOBLOG; this log
provides a high-water mark of the storage use.

100 Installation Guide

 How to Configure Without CA MSM

The REGION value is in K not M, so divide the value nnnK by 1024 to get the value in
M. Round the result up and add at least 5 to the result. This gives you the minimum
region size to use.
For example:
VIRT 540K SYS 296K EXT 40998K SYS 10124K

The storage usage value in this example is 40998K. If you divide this by 1024 you get
a value over 40 (round up the result to 41 and add 5).
The required region in this case is 46M.
3. Do one of the following:
■ If the load modules were copied to an authorized library other than a linklist
library, change the data set name on the STEPLIB DD statements.
■ If the load modules were copied to a linklist library, remove the STEPLIB DD
statements.
4. If you use direct-to-VIEW, and the CA VIEW load library is separate, add it to the
STEPLIB concatenation.
Load module SARPAM in the CA View load library is required for direct-to-VIEW
archival.
5. Change the data set name on the RMOPARMS DD statement to the name of the
card image data set that contains the initialization parameter statements.
RMOPARMS can be a member of a PDS:
//RMOPARMS DD DSN=CAI.CVDEOPTN(RMOPARMS),DISP=SHR

6. The RMOJTAB DD statement is optional; include it when job name translation

control statements are to be input to the started task.
The DD statement that is commented out in the procedure is an example only and
must be changed to point to your rmojtab.
Note: For more information about how to code this table, see the chapter "The
Database" in the Reference Guide.

Step 10: (Optional) Maintain Detail History with JES2

This step is for JES2 sites only. JES3 users should go to the (Optional) Maintain Detail
History with JES3 step.

Detail History is an optional feature of CA Deliver that is activated by setting

HDETAIL=YES in your initialization parameters. More DASD space is required for storing
this historical data than is required for running without it.

Chapter 7: Starting Your Product 101

How to Configure Without CA MSM

If you decide that you would like to maintain detailed historical data with the actual
date and time that reports and bundles are printed, continue with the next section,
Capturing Detailed Historical Data. Otherwise, go to the Set Up for Multiple CPUs step.

Note: Detailed history can consume a considerable amount of DASD space. For more
information, see the description of the basic and detailed history panels in Appendix A
of the Administration Guide.

Capture Detailed Historical Data

Do the following to capture detailed historical data:

1. Determine the following:
■ Do you want to capture detailed historical data?
and:
Do you use impact printers or IBM 3800 printers that are operating in
compatibility mode?
■ Is your printer a local, channel-attached printer?
or:
Do you use APF printers that are driven by IBM's PSF?
2. Do one of the following:
■ If you answered No to both of the conditions in Step 1, go to the Set Up for
Multiple CPUs step.
■ If you answered Yes to either of the conditions in Step 1, assemble and link edit
RMOJ2XIT.
RMOJ2XIT contains the source for EXIT1 and EXIT15, as a member of your JES2
load library (SYS1.LINKLIB).
Note: Apply USERMOD RMOJ2XIT. This USERMOD is located in dataset
CAI.CVDEJCL as member BRNSJ2X.
Add the following JES2 initialization parameters to the JES2 startup initialization
stream:
EXIT1 ROUTINE=RMOJ2X1

EXIT15 ROUTINE=RMOJ2X15

LOAD RMOJ2XIT

■ If you answered Yes to the AFP condition in Step 1, you have to install exit
RMOFSSUX. For more information, see the chapter User Exits in the Reference
Guide.

102 Installation Guide

 How to Configure Without CA MSM

Step 11: (Optional) Maintain Detail History with JES3

This step is for JES3 sites only.

Detail History is an optional feature of CA Deliver; to activate it set HDETAIL=YES in your

initialization parameters.

Note: Storing this historical data requires considerably more DASD space than running
without it does.

If you decide that you want maintain detailed historical data with the actual date and
time that reports and bundles are printed:
■ Assemble the front-end control sections
■ Link edit the sections with the JES3 load modules as shown in the following table:

CA Deliver JES3 User Exit Front-End JES3 User Exit Load USERMOD to Install
Control Sections Modules
RMOJ3X21 IATUX21 BRNSJ321
RMOJ3X23 IATUX23 BRNSJ323

Your JES3 load module library is to appear as the data set name of the L.SYSLMOD DD
statements.

To install these exits, use the USERMODs located in CAI.CVDEJCL. Note that the source
for these exits is located within the USERMOD.

Note: Bring JES3 down then bring it up to turn on the user exits.

If you are driving APF printers with IBM's PSF, install the exit RMOFSSUX. For more
information, see the chapter User Exits in the Reference Guide.

Note: Detailed history can consume a considerable amount of DASD space. For more
information, see the description of the basic and detailed history panels in Appendix A
of the Administration Guide.

Step 12: Set Up for Multiple CPUs

All users must perform this step.

Upgrade Considerations

If you are upgrading, see the chapter "Upgrading from a Prior Release" for information
that applies to this step.

Chapter 7: Starting Your Product 103

How to Configure Without CA MSM

Define ENQs to the System Integrity Product

The product issues ENQs and RESERVEs as necessary to maintain the integrity of its data
sets. CA Deliver uses the primary ENQ (QNAME=RMOSTC) during startup and shutdown
to serialize control block updates.
■ This enqueue is defined as SYSTEM to prevent a second CA Deliver from starting on
this LPAR with the same characteristics. This ENQ does not have to be defined to a
system integrity product.
■ A second ENQ (QNAME=RMOCKPT) is used during the OPEN and CLOSE of the
checkpoint file. This ENQ does not need to be defined to a system integrity product.
■ The RESERVE issued by CA Deliver is normally short-lived but will cause deadlock
conditions unless it is properly defined. The RESERVEs should be converted to global
enqueues; however, if your environment dictates, the reserves do not have to be
converted.

If the CA Deliver database and the checkpoint file are on dedicated volumes with no
other datasets, you do not have to convert RESERVES to global enqueues.

Using RESERVE and ENQ

This table shows how CA Deliver uses ENQ and RESERVE.

QNAME Type Description Integrity Product

Control

RMOSTC ENQ Serializes control block updates NO

during startup and shutdown

RMOCKPT ENQ Serializes the CA Deliver NO

checkpoint during open and
close
RMOUPD RESERVE Serializes the updating of the YES/NO
CA Deliver database (if environment
dictates)

Database Extent Considerations

In a multiple CPU environment, it is possible that processes in each system image are
accessing a database extent. To minimize contention, we recommend:
■ Place each database extent on a dedicated volume.

104 Installation Guide

 How to Configure Without CA MSM

■ Where it is possible, match the size of the volume and the size of the database
extent.
This matching allows each extent to be accessed by its own server (device address).
I/Os for multiple extents are prevented from queuing on the same device address,
which can happen if multiple database extents are allocated on the same device.

Step 13: (Optional) Construct the Initial Report and Job Data
Perform this step if you want to construct initial report and job data in the database
from an existing JCL library. Otherwise, skip this step.

Two utilities, RMOJCL and RMOJCS are supplied with CA Deliver to create report and job
definitions in the database from the job's JCL.

Note: For more information about utilities, see these topics in the chapter "Utilities" in
the Reference Guide:
■ RMOJCL – Automatic Database Construction from JCL
■ RMOJCS – Enhanced Database Construction from JCL

Note: The JCLCheck Common Component is no longer distributed as part of the CA

Deliver Distribution Libraries. We recommend that clients who use the RMOJCS utility
refer to the CA JCLCheck Common Component Installation documentation.

Step 14: Set Up the Viewing Interface

All CA View users must perform this step.

Upgrade Considerations

If you are upgrading, see the chapter "Upgrading from a Prior Release" for information
that applies to this step.

To set up an interface between CA Deliver and CA View, run the SARINIT initialization
utility to add this initialization option to CA View:

EXPRESS=DB.HLQ

Note: For more information about how to execute SARINIT, see the CA View Reference
Guide and the CA View Installation Guide.

Chapter 7: Starting Your Product 105

How to Configure Without CA MSM

Step 15: (Optional) Install User Exits and Authorization Tables

If this is a new installation, skip this step until you have thoroughly tested CA Deliver and
are familiar with the product.

Upgrade Considerations

For each user exit that you have tailored you must update the new CA Deliver skeleton
version and assemble it using the macros in CAI.CVDEMAC.

Note: For more information about how to upgrade, see the chapter "Upgrading from a
Prior Release".

User Exits

CA Deliver contains several optional user exits, most of which can be modified. For more
information about these exits, see the Reference Guide.

CAI.CVDEOPTN contains USERMODs that are used to modify and install these exits.

Exits can also be installed outside of SMP using the NON-SMP JCL contained in
CAI.CVDEJCL.

The exits and their USERMODs are as follows:

Exit Name USERMOD NON-SMP

RMOATHUX BRNSATHX BRNJATHX
RMOBPCUX BRNSBPCX BRNJBPCX
RMOBPTUX BRNSBPTX BRNJBPTX
RMODSCUX BRNSDSCX BRNJDSCX
RMOFSSUX BRNSFSSX BRNJFSSX
RMOJ2XIT BRNSJ2X BRNJJ2X
RMOJCLUX BRNSJCLX BRNJJCLX
RMOOMSUX BRNSOMSX BRNJOMSX
RMOPRBUX BRNSPRBX BRNJPRBX
RMORECUX BRNSRECX BRNJRECX
RMORPTUX BRNSRPTX BRNJRPTX
RMORPUX BRNSRPX BRNJRPUX
RMORRQUX BRNSRRQX BRNJRRQX

106 Installation Guide

 How to Configure Without CA MSM

Exit Name USERMOD NON-SMP

RMOSMFUX BRNSSMFX BRNJSMFX
RMOSUBUX BRNSSUBX BRNJSUBX
RMOUSRUX BRNSUSRX BRNJUSRX
RMOUSTUX BRNSUSTX BRNJUSTX
RMOUSXUX BRNSUSXX BRNJUSXX

Use USERMOD BRNSFSSX in CAI.CVDEJCL to modify user exit RMOFSSUX. However,

RMOFSSUX must be assembled and linked outside of SMP.

Note: For more information about the JCL needed to install this exit, see the CA Deliver
Reference Guide.

Authorization Tables

You can define a separate authorization table for each CA Deliver database.

Note: For more information about how to define and install the authorization tables,
see the Reference Guide.

Step 16: (Optional) Install Optional Online Interfaces

Perform this step if you want to install any of the optional online interfaces; otherwise
go to the next step.

Note: For more information about how to install optional online interfaces, see the
chapter "Installing Online Interfaces."

Step 17: (Optional) Install Optional Features

Perform this step if you want to install any of the optional features; otherwise go to the
next step.

Note: For more information about how to install optional features, see the chapter
"Installing Features."

Upgrade Considerations

If you are upgrading, see the "Upgrading from a Prior Release" chapter for information
about this step.

Chapter 7: Starting Your Product 107

Chapter 8: Migration Information
This section contains the following topics:
Migration Considerations (see page 109)
Upgrading from CA Deliver Release 11.5, Release 11.6, and Release 11.7 (see page 109)

Migration Considerations
Describe what you are migrating and the things to consider when you migrate existing
configuration and data, for example, changes to:
■ Security requirements
■ System parameter usage
■ Data tables

This section contains the information you need to upgrade to CA Deliver Version 12.0
from CA Deliver Release 11.7, r11.6, or r11.5.

For an overview of the changes in this release, see the Release Notes.

Note: If you are upgrading a pre-r11.5 database, the database must be upgraded first to
r11.5, r11.6 or r11.7 with the r11.5, r11.6 or r11.7 utilities, and then to Version 12.0.

Upgrading from CA Deliver Release 11.5, Release 11.6, and

Release 11.7
Use these instructions to upgrade to CA Deliver Version 12.0 from CA Deliver Release
11.5, Release 11.6, or Release 11.7. The instructions consist of the original steps and a
series of modifications.

Chapter 8: Migration Information 109

Upgrading from CA Deliver Release 11.5, Release 11.6, and Release 11.7

To upgrade to Version 12.0, use the steps in these chapters:

■ "Installing Your Product Using CA MSM", "Installing Your Product From
Pax-Enhanced Electronic Software Delivery", or "Installing Your Product From Tape"
■ "Configuring Your Product"
■ "Installing Online Interfaces,"
■ "Installing Features"

The steps must be modified according to the supplementary instructions in the tables in
the following sections:
■ Installation Steps to Upgrade to Version 12.0
■ Configuration Steps to Upgrade to Version 12.0

Be aware that existing Release 11.5, Release 11.6, or Release 11.7 users are going to
install the product using almost the same methods, as new users, with one
exception—instead of creating a database you are going to version your existing
database. This process updates several records in the database and is expected to
execute in a few minutes.

Before upgrading your CA Deliver database, be certain that:

■ The started task from the previous release has been withdrawn from the system by
one of these methods:
– The F RMOSTC,OFF operator command has been entered
– An initial program load of the system was performed
■ All application jobs containing reports that are distributed by CA Deliver are
completed before CA Deliver Version 12.0 is started.
■ All bundles have been completed.

Important! Failure to follow these procedures can result in lost bundles and abends in
your application jobs.

Note: To revert to Release 11.7, r11.6, or r11.5 see the chapter Reverting to a Prior
Installation.

Installation Steps for Upgrading to Version 12.0

To upgrade to Version 12.0, you must perform each installation step exactly as it is
presented in the appropriate Installation chapter, unless the step has upgrade
instructions in the table that follows.

The Step column lists the installation step in the chapter "Installation" and the Upgrade
Instructions column explains what you must do if the step needs to be modified or
replaced.

110 Installation Guide

 Upgrading from CA Deliver Release 11.5, Release 11.6, and Release 11.7

Installation Supplementary Upgrade Instructions

Step
Step BRN1ALL Comment out or delete the allocations for any existing libraries. If you
are upgrading from r11.7, and the panel libraries are sufficiently
allocated, skip this step.
Step BRN2CSI ■ Comment out or delete the allocations for any existing libraries.
■ Comment out or delete the step that creates the CSI.
■ Change all ADD statements to REP statements.
■ If you are upgrading from r11.7, skip this step.
Note: The default middle level qualifier name of the SMP/E CSI has
been removed beginning with release r11.6.
If you are upgrading from a previous release, be sure that the correct,
complete name of your CSI is specified in the PARM= value on the
execute card.
Step No supplementary instructions.
BRN3RECD or Note: Be aware that the default middle level qualifier name of the
BRN3RECT, SMP/E CSI has been removed beginning with release r11.6.
BRN4APP,
If you are upgrading from a previous release, be sure that the correct,
BRN5ACC
complete name of your CSI is specified in the PARM= value on the
execute card.

Configuration Steps to Upgrade to CA Deliver Version 12.0 without CA MSM

To upgrade to Version 12.0, you must perform each installation step exactly as it is
presented in the "Configuring Your Product" chapter unless the step has upgrade
instructions in the table that follows.

The Step column lists the installation step in the "Installation" chapter and the Upgrade
Instructions column explains what you must do if the step needs to be modified or
replaced.

Step Upgrade Instructions

Steps 1-2 No supplementary instructions
Step 3 Define Security Rules
If you modified the RMOATHUX authorization user exit or installed
authorization tables, copy your changes into to the new CA Deliver
skeleton version and assemble them in Step 23.
If you have external security rules, review the "Security" chapter in the CA
Deliver Reference Guide to determine if new security rules are necessary.

Chapter 8: Migration Information 111

Upgrading from CA Deliver Release 11.5, Release 11.6, and Release 11.7

Step 4 Optionally, set the version of your database up to Version 12.0. Version
12.0 provides full compatibility with releases r11.5, r11.6, and r11.7
databases.
If you want to utilize specific Version 12.0 features the database must be
upgraded to Version 12.0.
Note: If you do not want to upgrade your release r11.5, r11.6, or r11.7
database, skip this step.
This step replaces the Create the Database step in the chapter
"Installation." Be aware of the following:
■ Instead of creating a CA Deliver database, you use the VERSION
control statement of the RMODBASE utility to version your database
to Version 12.0. You can tailor and submit CAI.CVDEJCL(HBRNVERS).
■ The high-level name of the database must have been previously
defined with the NAME control statement (or the PARM parameter
of the EXEC JCL statement) for the RMODBASE utility. The format of
the VERSION control statement is:
Version 12.0
For more information, see the RMODBASE Utility section in the chapter
"Database Utilities" in the CA Deliver Reference Guide.
Note: Save your initialization parameter settings; some parameter
settings have been added or eliminated in Version 12.0, and you may
need the original settings if you have to revert to releases r11.5, r11.6, or
r11.7.
Step 5 Create the Initialization Parameter Statements
Follow the instructions in the "Installation" chapter. Some initialization
parameters have been added, changed, or eliminated in Version 12.0.
Be sure to review the initialization parameters presented in the chapter
"Initialization Parameters" in the CA Deliver Reference Guide.
For information about all initialization parameter changes, see the CA
Deliver Release Notes.
Save a copy of your initialization parameters in case you have to revert to
releases r11.5, r11.6, or r11.7.
Step 6 No supplementary instructions

112 Installation Guide

 Upgrading from CA Deliver Release 11.5, Release 11.6, and Release 11.7

Step 7 Load Online Panels and the JCL Library

■ If online panel members were customized in releases r11.5, r11.6, or
r11.7, copy those members to the appropriate Version 12.0 online
library.
■ If the customized panels are maintained in a separate library, load
those online panel members after loading the Version 12.0 panel
members to the database.
Follow the instructions in the "Installation" chapter and load the online
panels to the database. Because some online panels have changed, you
must OLOAD the new panels.
Important! Only perform to the OLOAD of the new panels if the database
has been versioned to Version 12.0.
Step 8 Load the Model Banner Pages
■ If model banner page members were customized or added in
releases r11.5, r11.6, or r11.7, copy those members to the Version
12.0 model banner page library.
■ If the customized banner pages are maintained in a separate library,
load those banner page members after loading the Version 12.0
banner page members to the database.
Follow the instructions in the "Installation" chapter and load the model
banner panels to the database.
Step 9 Add the Start Procedure to PROCLIB
Follow the instructions in the "Installation" chapter and add or adjust the
start procedure in the PROCLIB.
Be sure that STEPLIB points to the new CAI.CVDELOAD.
Steps No supplementary instructions
10-11
Step 12 Set Up for Multiple CPUs
Follow the instructions in the chapter "Installation." If you use a system
integrity product, make the changes needed to accommodate the new CA
Deliver database.
Note: There have been no changes to the way releases r11.5, r11.6, and
r11.7 interact with products of this type, so changes should be minimal.
Be aware of the following:
■ No active tasks can be running that point to the CVDELOAD and
database that are being upgraded.
■ If multiple versions of CA Deliver are running on multiple CPUs and
share the same database, all PROCs, JCL, CLISTS, and so forth, that
access a given CA Deliver database must also be upgraded.
Step 13 No supplementary instructions

Chapter 8: Migration Information 113

Upgrading from CA Deliver Release 11.5, Release 11.6, and Release 11.7

Step 14 Set up the Viewing Interface

Skip this step if the Deliver databases have already been defined to CA
View.
Step 15 Replace or Modify User Exits (Optional)
If you modified any of the CA Deliver user exits perform this step;
otherwise, go to the next step. Note the following:
■ For each user exit that you tailored in release r11.5, r11.6, or r11.7,
you must copy your changes to the new CA Deliver skeleton version
and assemble it.
■ All modifications to these exits must be done as an SMP/E USERMOD
with the load module installed into CVDELOAD.
■ For your convenience, CVDEOPTN members are provided for all of
the user exits.
Save a copy of your user exits in case you need to revert to release r11.5,
r11.6, or r11.7. For more information about user exits, see the chapter
"User Exits" in the Reference Guide.
Step 16 No supplementary instructions
Step 17 Install Optional Features (Optional)
Review the chapter "Installing Features".
Verify that the LMP key has been supplied for each feature that you want
to install (see the Enter the LMP Code step in the "Installation" chapter),
then follow the installation instructions in the chapter "Installing
Features."
Be sure that all STEPLIB statements in your JCL reference the new
CAI.CVDELOAD.
There has been a minor change to cross-memory (one of the CA Deliver
optional features):The cross-memory task program name has been
changed to EC0DRV. Any JCL that contains the earlier release names,
must be changed to EC0DRV.
For more information about installing cross-memory services, see the
"Installing Online Interfaces" chapter.

114 Installation Guide

Chapter 9: Reverting to a Prior Installation
This section provides the instructions to use to revert to Release 11.7, Release 11.6, or
Release 11.5.

This section contains the following topics:

Revert to Release 11.7 (see page 115)
Reverting to Release 11.6 (see page 115)
Reverting to Release 11.5 (see page 116)

Revert to Release 11.7

Follow these steps:
1. Use the CA Deliver Version 12.0 RMODBASE utility to set the version of your CA
Deliver database back to a CA Deliver Release 11.7 database.
The format of the VERSION control statement is:
VERSION 11.7
2. Use the CA Deliver Release 11.7 RMODBASE utility to OLOAD the Release 11.7
online panel library into your database.
3. Use the CA Deliver Release 11.7 release RMODBASE utility to BLOAD the Release
11.7 banner page library to your database.
4. If you modified any of the CA Deliver user exits, revert to your Release 11.7 versions
of the exits.
5. Change your JCL, Procs, and started task JCL to point to the Release 11.7 libraries.
6. If the Version 12.0 load library was link listed, revert to the Release 11.7 link listed
library.

Reverting to Release 11.6

Follow these steps:
1. Use the CA Deliver Version 12.0 RMODBASE utility to set the version of your CA
Deliver database back to a CA Deliver Release 11.6 database.
The format of the VERSION control statement is:
VERSION 11.6

Chapter 9: Reverting to a Prior Installation 115

Reverting to Release 11.5

2. Use the CA Deliver Release 11.6 RMODBASE utility to OLOAD the Release 11.6
online panel library into your database.
3. Use the CA Deliver Release 11.6 RMODBASE utility to BLOAD the Release 11.6
banner page library to your database.
4. If you modified any of the CA Deliver user exits, revert to your Release 11.6 versions
of the exits.
5. Change your JCL, Procs, and started task JCL to point to the Release 11.6 libraries.
6. If the Version 12.0 load library was link listed, revert to the Release 11.6 link listed
library.

Reverting to Release 11.5

Follow these steps:
1. Use the CA Deliver Version 12.0 RMODBASE utility to set the version of your CA
Deliver database back to a CA Deliver Release 11.5 database.
The format of the VERSION control statement is:
VERSION 11.5
2. Use the CA Deliver Release 11.5 RMODBASE utility to OLOAD the release 11.5
online panel library into your database.
3. Use the CA Deliver Release 11.5 RMODBASE utility to BLOAD the release 11.5
banner page library to your database.
4. If you modified any of the CA Deliver user exits, revert to your release 11.5 versions
of the exits.
5. Change your JCL, Procs, and started task JCL to point to the release 11.5 libraries.
6. If the Version 12.0 load library was link listed, revert to the release 11.5 link listed
library.

116 Installation Guide

Chapter 10: Installing Online Interfaces
This section contains the following topics:
How to Complete Configuration of the XMS Online Interfaces With CA MSM (see page
117)
How to Configure the Online Interfaces Without CA MSM (see page 146)
Prepare to Start the Cross Memory Task (see page 208)
Start the Cross Memory Task (see page 208)

How to Complete Configuration of the XMS Online Interfaces

With CA MSM
These steps are configured automatically by the EBC Common Component
Configuration Option:
■ XMS Startup PROC
■ Initialization Parameter Statements
■ Modify, Assemble and Link of the EC0XMCTR Module
■ Definition of Transactions and Programs to CICS

The EBC Common Component Configuration Option also includes several other external
tasks that are required to complete the configuration.

Define Security Requirements

Follow these steps to define security requirements for CA Top Secret Security (eTrust
CA Top Secret) security:
1. Rename the existing facility in the facility matrix table if you do not have a facility
defined for RMOXMS:
user1=NAME=RMOXMS

2. Verify that the correct PGMname is defined for the new facility, where PGMname is
either the first three characters or all the eight characters of the program name that
is going to make security calls (EC0 or EC0DRV).
3. Create region ACID for the facility:
TSS CRE(rmoxms) pass(nopw,0) type(user) dept(dept)
mastfac(rmoxms) NODSNCHK NORESCHK NOVOLCHK NOLCFCHK NOSUBCHK

Chapter 10: Installing Online Interfaces 117

How to Complete Configuration of the XMS Online Interfaces With CA MSM

4. Define the RMOXMS STC to the TSS STC record:

TSS ADDTO(STC) PROCNAME(rmoxms) ACID(rmoxms)

5. Give access to the ACIDs required to sign on to this facility:

TSS ADD(ACID) FAC(rmoxms)

Install the ISPF/Cross-Memory Online Retrieval Option

The ISPF/Cross-Memory Online Retrieval Option runs under IBM's ISPF for z/OS Version
3.0 and higher.

Important! This interface requires Cross-memory services to be already installed. For

more information, see Install Cross-Memory Services in this chapter.

Note: In the JCL for the cross-memory services task, the parameter XMSSUB must be set
to YES.

Installation Steps

The following steps are required to install the ISPF/cross-memory online retrieval
option. Each step is explained in detail later in the sections that follow.
1. (Optional) Add STEPLIB DD statements to the TSO LOGON procedures if the load
modules were not copied to a linklist library.
2. Add the panel and command table libraries to the TSO LOGON procedures.
3. (Optional) Modify an ISPF Selection Menu to Select Online Retrieval feature.

Step 1: (Optional) Add STEPLIB DD Statements to the TSO LOGON Procedures

The action you take in this step depends on what you did during the base-product
installation—specifically, did you:
■ Authorize the program load library, or
■ Copy the modules to a system authorized library.

If the CA Deliver load modules were not copied to one of the libraries in the linklist,
proceed with this step; otherwise go to the next step.

For this interface, the libraries do not have to be APF authorized. Authorization is
provided in the cross-memory installation. Multiple versions of this online interface can
coexist in one TSO library concatenation.

118 Installation Guide

 How to Complete Configuration of the XMS Online Interfaces With CA MSM

Do one of the following:

■ Add a STEPLIB DD statement for the library that contains the load modules to the
LOGON procedures for those TSO users who are going to use the
ISPF/cross-memory online retrieval option.
■ Provide the load library using the ISPF LIBDEF facility.

Note: If multiple versions of CA Deliver are going to be running simultaneously, or you

want to also run a previous version of RMOSPF or RMOTSO, concatenate the load library
you want RMOSPF or RMOTSO to use first.

More information:

Step 6: Modify the Skeleton JCL (see page 96)

Step 2: Add Panel and Command Table Libraries to TSO LOGON

If you are going to run CA Deliver under ISPF, proceed with this step. For Version 3 or
higher, both the command table library and the panel library are used.

To add panel and command table libraries to the TSO LOGON procedure:
1. Concatenate the command table library CAI.CVDETBL0 to DD statement ISPTLIB.
2. Concatenate the panel library CAI.CVDEPNL0 to DD statement ISPPLIB.

Note: If you also plan to use RMOSPF (the ISPF interface), and multiple versions of CA
Deliver, concatenate CAI.CVDETBL0 first. Use the CAI.CVDETBL0 from the most current
release.

Step 3: (Optional) Modify an ISPF Selection Menu to Select Online Retrieval

If you want to add a selection code to one of the ISPF selection menus for the online
retrieval feature, proceed with this step; otherwise, your ISPF detailed instructions are
complete.

Chapter 10: Installing Online Interfaces 119

How to Complete Configuration of the XMS Online Interfaces With CA MSM

Note: If you add a selection code, you are able to select the online retrieval feature in
the same way you select other ISPF options.

Use the value next to the NAME parameter on your Initialization Parameter Worksheet
for PARM (high-level database name).

Use the values in this table for either SPF or ISPF.

Type Selection Code is Defined As

ISPF (all versions) 'PGM(EC0XMSPF) PARM(high-level-database-name)
NEWAPPL(RMO)'
SPF 'PGM(EC0XMSPF) PARM(high-level-database-name)'

Panel Libraries

The names of the panel libraries vary from site to site and for the different releases of
ISPF. These panel libraries are allocated to the ISPPLIB DD statement under TSO.

Be aware that some installations do not allow direct modifications of IBM panels and
libraries. In this case, you can place the modified panels in user or site-specific libraries
and concatenate them ahead of the IBM libraries.

Ask your system administrator for the specific ISPF panel library that applies to your site
and contains the panel ISR@PRIM.

Note: The selection menus shown in these examples are part of the program product
ISPF and are copyrighted by IBM.

120 Installation Guide

 How to Complete Configuration of the XMS Online Interfaces With CA MSM

Example 1

This example shows you how to add selection code R to the primary option menu
ISR@PRIM for ISPF. The bright, offset text identifies the inserted lines.

----------------------- ISPF/PDF PRIMARY OPTION MENU --------------------

%OPTION ===>_ZCMD +
% +USERID - &ZUSER
% 0 +ISPF PARMS - SPECIFY TERMINAL AND USER PARAMETERS +TIME - &ZTIME
% 1 +BROWSE - DISPLAY SOURCE DATA OR OUTPUT LISTINGS +TERMINAL - &ZTERM
% 2 +EDIT - CREATE OR CHANGE SOURCE DATA +PF KEYS - &ZKEYS
% 3 +UTILITIES - PERFORM UTILITY FUNCTIONS
% 4 +FOREGROUND - INVOKE LANGUAGE PROCESSORS IN FOREGROUND
% 5 +BATCH - SUBMIT JOB FOR LANGUAGE PROCESSING
% 6 +COMMAND - ENTER TSO COMMAND, CLIST, OR REXX EXEC
% 7 +DIALOG TEST - PERFORM DIALOG TESTING
% 8 +LM UTILITIES- PERFORM LIBRARY ADMINISTRATOR UTILITY FUNCTIONS
% C +CHANGES - DISPLAY SUMMARY OF CHANGES FOR THIS RELEASE
% R +RMOSPF - DELIVER ADMINISTRATION
% T +TUTORIAL - DISPLAY INFORMATION ABOUT ISPF/PDF
% X +EXIT - TERMINATE ISPF USING LOG AND LIST DEFAULTS
%
+ENTER%END+COMMAND TO TERMINATE ISPF.
)INIT
.HELP = ISR00003
&ZPRIM = YES /* ALWAYS A PRIMARY OPTION MENU */
&ZHTOP = ISR00003 /* TUTORIAL TABLE OF CONTENTS */
&ZHINDEX = ISR91000 /* TUTORIAL INDEX - 1ST PAGE */
)PROC
&ZSEL = TRANS( TRUNC (&ZCMD,'.')
0,'PANEL(ISPOPTA)'
1,'PGM(ISRBRO) PARM(ISRBRO01)'
2,'PGM(ISREDIT) PARM(P,ISREDM01)'
3,'PANEL(ISRUTIL)'
4,'PANEL(ISRFPA)'
5,'PGM(ISRJB1) PARM(ISRJPA) NOCHECK'
6,'PGM(ISRPTC)'
7,'PGM(ISPYXDR) PARM(ISR) NOCHECK'
8,'PANEL(ISRLPRIM)'
C,'PGM(ISPTUTOR) PARM(ISR00005)'
R,'PGM(EC0XMSPF) PARM(RMO.SYSTEM1) NEWAPPL(RMO)'
T,'PGM(ISPTUTOR) PARM(ISR00000)'
' ',' '
X,'EXIT'
*,'?' )
&ZTRAIL = .TRAIL
)END

Chapter 10: Installing Online Interfaces 121

How to Complete Configuration of the XMS Online Interfaces With CA MSM

Note:
■ NEWAPPL(RMO) is required and must be specified as shown previously in this
section.
This parameter is used with the command table library concatenation from Step 3
of the ISPF Installation Instructions.
■ NEWAPPL(RMO) allows CA Deliver to correctly interpret commands and program
function key invocation.
If this parameter is not specified, certain PF keys such as the scroll keys may not
function.

122 Installation Guide

 How to Complete Configuration of the XMS Online Interfaces With CA MSM

Example 2

This example shows you how to add selection code R to the primary option menu
ISP@PRIM for SPF. Shading identifies the inserted lines.
%----------------------- SPF–MVS PRIMARY OPTION MENU ---------------
%OPTION ===>_OPT
% +USERID -
% 0 +ISPF PARMS - SPECIFY TERMINAL AND USER PARAMETERS +TIME -
% 1 +BROWSE - DISPLAY SOURCE DATA OR OUTPUT LISTINGS +TERMINAL –
% 2 +EDIT - CREATE OR CHANGE SOURCE DATA +PF KEYS -
% 3 +UTILITIES - PERFORM SPF UTILITY FUNCTIONS
% 4 +FOREGROUND - COMPILE, ASSEMBLE, OR DEBUG
% 5 +BACKGROUND - COMPILE, ASSEMBLE, OR LINK EDIT
% 6 +COMMAND - ENTER TSO COMMAND OR CLIST
% 7 +SUPPORT - TEST DIALOG OR CONVERT MENU/MESSAGE FORMATS
% 8 +LM UTILITIES- PERFORM LIBRARY ADMINISTRATOR UTILITY FUNCTIONS
% R +RMOSPF - DELIVER ADMINISTRATION
% T +TUTORIAL - DISPLAY INFORMATION ABOUT SPF
% X +EXIT - TERMINATE SPF USING LIST/LOG DEFAULTS
%
+PRESS%END KEY TO TERMINATE SPF+
%
)INIT
.HELP = TTUTOR
&ZHTOP = TTUTOR /* TUTORIAL TABLE OF CONTENTS */
&ZHINDEX = TINDEX /* TUTORIAL INDEX - 1ST PAGE */
)PROC
&ZSEL = TRANS( TRUNC (&OPT,'.')
0,'PANEL(ISPOPT)'
1,'PGM(ISRBRO)'
2,'PGM(ISPEDIT)'
3,'PANEL(ISPUTIL)'
4,'PANEL(ISPFORA)'
5,'PANEL(ISRJOB)'
6,'PGM(ISPTSO)'
7,'PANEL(ISPOTAC)'
R,'PGM(EC0XMSPF) PARM(RMO.SYSTEM1)'
T,'PGM(ISPTUTOR) PARM(T)'
' ',' '
X,'EXIT'
*,'?' )
)END

Example 3

This example shows you how to add selection code 3.R as a sub-option to the utilities
menu ISPUTIL for ISPF.

Chapter 10: Installing Online Interfaces 123

How to Complete Configuration of the XMS Online Interfaces With CA MSM

The bright, offset text identifies the inserted lines.

%----------------------- UTILITY SELECTION MENU -----------------

%OPTION ===>_OPT +
% +
% 1 +LIBRARY LIBRARY UTILITY:
+ PRINT INDEX LISTING OR ENTIRE DATASET
+ PRINT, RENAME, DELETE, OR BROWSE MEMBERS
+ COMPRESS DATASET
% 2 +DATASET DATASET UTILITY:
+ DISPLAY DATASET INFORMATION
+ ALLOCATE, RENAME, OR DELETE ENTIRE DATASET
+ CATALOG OR UNCATALOG DATASET
% 3 +MOVE/COPY MOVE OR COPY MEMBERS OR DATASETS
% 4 +CATALOG CATALOG MANAGEMENT:
+ DISPLAY OR PRINT CATALOG ENTRIES
+ INITIALIZE OR DELETE USER CATALOG ALIAS
% 5 +RESET RESET STATISTICS FOR MEMBERS OF ISPF LIBRARY
% 6 +HARDCOPY INITIATE HARDCOPY OUTPUT
% 7 +VTOC DISPLAY OR PRINT VTOC ENTRIES FOR A DASD VOLUME
% 8 +OUTLIST DISPLAY, DELETE, OR PRINT HELD JOB OUTPUT
% 9 +SCRIPT/VS FORMAT, DISPLAY, AND OPTIONALLY PRINT SCRIPT TEXT
% R +RMOSPF DELIVER ADMINISTRATION
)INIT
.HELP = TU
)PROC
&SEL = TRANS( TRUNC (&OPT,'.')
1,'PGM(ISPUDA) PARM(UDA1)'
2,'PGM(ISPUDA) PARM(UDA1)'
3,'PGM(ISPUMC)'
4,'PGM(ISPUCA)'
5,'PGM(ISPURS)'
6,'PGM(ISPUHC)'
7,'PGM(ISPUVT)'
8,'PGM(ISPUOL) PARM(UOL01)'
9,'PGM(ISPUSC) PARM(SCRPTA)'
R,'PGM(EC0XMSPF) PARM(RMO.SYSTEM1) NEWAPPL(RMO)'
' ',' '
*,'?' )
)END

124 Installation Guide

 How to Complete Configuration of the XMS Online Interfaces With CA MSM

ISPF Cross-Memory Notes

Be aware of the following:

■ The primary RMOXMS region must be started with the XMSSUB=YES parameter.
■ The XMSSUB=YES parameter must only be used in an XMS address space with a
default subsystem ID (SUBSYS=XMC0 or not specified).
■ If multiple RMOXMS regions are started, they must be started with XMSSUB=NO
parameter.
Only the primary XMS region can have XMSSUB=YES specified.
■ The XMS regions must have the XMS=YES parameter to make it accessible.
■ The EBCXMCTR table must be assembled during installation to define the
relationship between CA Deliver and CA View database high-level qualifiers. The
table contains an EBCXMOPT macro to define initialization options and the
EBCXMTRN macro for each CICS user transaction.

The EBCXMTRN macro also contains options for the specific database as follows:
■ SUBSYS= parameter of the cross-memory task must match the SUBSYS= parameter
specified in the EBCXMCTR table entry.
■ RECON=YES can be used to allow reconnection (after an ISPF terminal error) at the
point of exit.
■ TIMEOUT= specifies how long ISPF will wait for the XMS session to respond after
the user enters input, in seconds.
We recommend as high a value as possible but not less than 240 (4 minutes).

To abort the XMS session and return the user to ISPF or the TSO command prompt,
press the ATTN key.

Note: The SUBMAX= parameter controls the number of user connections, not the
USERMAX= parameter. USERMAX= only applies when you are using the subtask with the
CICS interface.

Install the TSO/Cross-Memory Online Retrieval Option

Important! This interface requires cross-memory services to be installed. For more
information, see the topic Installing Cross-Memory Services in this chapter.

Note: The parameter XMSSUB must be set to YES in the JCL for the cross-memory
services task.

Chapter 10: Installing Online Interfaces 125

How to Complete Configuration of the XMS Online Interfaces With CA MSM

Installation Steps

The following steps are required to install the TSO/Cross-Memory Online Retrieval
Option. Each step is explained in detail in the sections that follow.
1. (Optional) Add STEPLIB DD Statements to the TSO LOGON procedures if the load
modules were not copied to a linklist library.
2. (Optional) Create user CLISTs to execute the CA Deliver TSO/XMS driver program.

Step 1: (Optional) Add STEPLIB DD Statements

The action you take in this step depends on what you did during the base-product
installation—specifically, did you:
■ Authorize the program load library or
■ Copy the modules to a system authorized library

If the CA Deliver load modules were not copied to one of the libraries in the linklist,
proceed with this step; otherwise go to the next step.

To add STEPLIB DD statements (for the library containing the CA Deliver load modules)
to the TSO LOGON procedures, do the following:
■ Add a STEPLIB DD statement for the library that contains the CA Deliver load
modules to the LOGON procedures for those TSO users who are to use the
ISPF/Cross-Memory Online Retrieval Option.

Note: For this interface, the libraries do not have to be APF authorized—authorization is
provided in the cross-memory installation. Multiple releases of this online interface can
coexist in one TSO library concatenation.

Step 2: (Optional) Set up the TSOXMS Driver Program

To create user CLISTs to execute the CA Deliver TSOXMS driver program, issue:

EC0XMTSO highlevel.databasename

126 Installation Guide

 How to Complete Configuration of the XMS Online Interfaces With CA MSM

TSO Cross-Memory Notes

Be aware of the following:

■ The primary RMOXMS region should be started with the XMSSUB=YES parameter.
■ The XMSSUB=YES parameter must only be used in an XMS address space with a
default subsystem ID (SUBSYS=XMC0 or not specified).
■ If multiple RMOXMS regions are started, they must be started with XMSSUB=NO
parameter.
Only the primary XMS region can have XMSSUB=YES specified.
■ The XMS regions must have the XMS=YES parameter to make it accessible.
■ The EBCXMCTR table must be assembled during installation to define the
relationship between CA View and CA Deliver database high-level qualifiers. The
table contains an EBCXMOPT macro to define initialization options and the
EBCXMTRN macro for each CICS user transaction.

The EBCXMTRN macro also contains options for the specific database as follows:
■ SUBSYS= parameter of the cross-memory task.
This parameter must match the SUBSYS= parameter specified in the EBCXMCTR
table entry.
■ RECON=YES can be used to allow reconnection (after a TSO terminal error) at the
point of exit.
■ TIMEOUT= specifies how long TSO will wait for the XMS session to respond after the
user enters input, in seconds.
We recommend as high a value as possible but not less than 240 (4 minutes).

To abort the XMS session and return the user to ISPF or the TSO command prompt,
press the ATTN key.

Note: The SUBMAX= parameter controls the number of user connections, not the
USERMAX= parameter. USERMAX=only applies when you are using the subtask with the
CICS interface.

Install the VTAM Online Retrieval Option

Important! This facility uses the cross-memory feature distributed with CA Deliver and
must be installed with that feature. For more information about cross-memory feature,
see the Install Cross-Memory Services section in this chapter.

Chapter 10: Installing Online Interfaces 127

How to Complete Configuration of the XMS Online Interfaces With CA MSM

Installation Steps

The following steps are required to install the VTAM online retrieval option. Each step is
explained in detail in the sections that follow.
1. Define the APPL definition statement to VTAM.
2. (Optional) Create a USS Table Definition.

Step 1: Define the Application Program to VTAM

Add this application program definition to SYS1.VTAMLST:

* SYS1.VTAMLST(rmomajor)
rmomajor VBUILD TYPE=APPL
rmovtam APPL ACBNAME=rmovtam,AUTH=(PASS,ACQ),EAS=nn

where:
rmomajor
Specifies the application program major node name.
Use the SYS1.VTAMLST member name. The member name must be unique and
must not be the same as the names on the APPL statement.
AUTH=(PASS,ACQ)
Is required when the cross-memory parameter VTAMPASS=YES is used to support
multiple cross-memory regions.
If VTAMPASS=NO, you can specify AUTH=(ACQ). For more information about the
VTAMPASS parameter, see the Add the Start Procedure for the Cross-Memory
Online Task step in this chapter.
EAS=nn
Specifies the approximate number of concurrent sessions.
rmovtam
Specifies the minor node name of the application program.
■ This name must be unique within the network domain; it is the APPLID
referenced in the USS definition table or LOGON command.
■ This name is also specified on the cross-memory RMOAPPL parameter.
■ If not specified, the network-unique name (the name of the APPL definition
statement) is used.

Step 2: (Optional) Create a USS Table Definition

To simplify the manner in which a user logs on to VTAM online retrieval, you can create
a USS definition table for CA Deliver.

128 Installation Guide

 How to Complete Configuration of the XMS Online Interfaces With CA MSM

Example

Assume that two CA Deliver systems have been created. The databases for the two
systems have high-level names of RMO.SYSTEM1 and RMO.SYSTEM2, and you want a
user to simply enter one of the commands to log on to VTAM online retrieval for the
respective systems:

RMO1
RMO2

Create a USS definition table as follows:

USSTAB
*
* ENTRY FOR RMO1
*
USSCMD CMD=RMO1,REP=LOGON,FORMAT=PL1
USSPARM PARM=APPLID,DEFAULT=RMOVTAM
USSPARM PARM=LOGMODE
USSPARM PARM=DATA,DEFAULT=RMO.SYSTEM1
*
* ENTRY FOR RMO2
*
USSCMD CMD=RMO2,REP=LOGON,FORMAT=PL1
USSPARM PARM=APPLID,DEFAULT=RMOVTAM
USSPARM PARM=LOGMODE
USSPARM PARM=DATA,DEFAULT=RMO.SYSTEM2
USSEND

Chapter 10: Installing Online Interfaces 129

How to Complete Configuration of the XMS Online Interfaces With CA MSM

VTAM Cross-Memory Notes

Be aware of the following:

■ For VTAM only regions, you can start the primary RMOXMS task with the
XMSSUB=NO parameter. However if this is not a VTAM only region, we recommend
that you start the primary RMOXMS region with the XMSSUB=YES parameter.
■ If multiple RMOXMS regions are started, they must be started with XMSSUB=NO
parameter.
Only the primary XMS region can have XMSSUB=YES specified.
■ VTAM only XMS regions can have the XMS=NO parameter to make it accessible.
■ All XMS interfaces require the EC0XMCTR table. You must assemble the table during
installation to:
– Define the relationship between CA Deliver and CA View database high-level
qualifiers and the session options to be used
– Provide information used to build the XMS database table. Only the database
high-level qualifier is used for VTAM XMS users.
■ Specify the RMOAPPL=applid parameter. This parameter provides VTAM user
signon capability.
Note: When you are using multiple VTAM XMS regions, each region must have a
unique applid.
■ To pass VTAM signon requests to other XMS regions, specify the VTAMPASS=YES
parameter.
■ When you are using multiple VTAM XMS regions, the values for LGNFMT=,
RMOVDTB=, VTMQUERY=, and VTMSAA= must be the same in each region.
Otherwise, the XMS interface may react in unpredictable ways.
■ To activate the VTAM generic resource support for your cross memory regions,
specify the VGRAPPL= parameter.
Note: For more information about VTAM generic resources, see the following topic.

VTAM Generic Resource Name

If the VGRAPPL parameter is specified in an EMAS complex, this parameter specifies a

common VTAM generic resource name for the entire EMAS complex.

Specifying the common VTAM generic resource name in the session request can initiate
VTAM cross memory sessions to any of the EMAS members.

When you are using the VTAM generic resource name, by default VTAM tries to request
a session with an EMAS member in the same MVS image.

If it is not possible to get the session that was requested, VTAM uses normal load
balancing when passing the session request to one of the active EMAS members.

130 Installation Guide

 How to Complete Configuration of the XMS Online Interfaces With CA MSM

Install the CA Roscoe/Cross-Memory Online Retrieval Option

The CA Roscoe/cross-memory online retrieval option runs as a command processor
under ETSO/Roscoe.

Important! This interface requires cross-memory services to be installed. For more

information about cross-memory services, see the Install Cross-Memory Services section
in this chapter. Be sure to set the parameter XMSSUB to YES in the JCL for the
cross-memory services task.

Installation Steps

The following steps are required to install the CA Roscoe/Cross-Memory Online

Retrieval Option. Each step is explained in detail in the sections that follow.
1. (Optional) Concatenate the Load Module Library to the ETSOLIB DD statement, if
the load modules were not copied to a linklist library.
2. Add the control statement for the RMOROS command processor to the Eligible
Program List (EPL).
3. Invoke CA Roscoe/Cross-Memory Online Retrieval.

Step 1: (Optional) Concatenate the Load Module Library

If the load modules were not copied to a linklist library, concatenate the library that
contains the load modules to the ETSOLIB DD statement in the CA Roscoe startup JCL, .

Note: If you have CA View, the CA View load modules must also be either in the linklist
or in a ETSOLIB statement with this step.

Step 2: Add RMOROS Command Processor Statements

Important! This step is for CA Roscoe 6.0 and Higher.

Add these EPL control statements to member ETSOPGMS for the CA Roscoe user with
the RO prefix:

Column Contents
1–8 EC0XMROS
9 Blank
10–12 Number of users allowed to access CA Deliver at one time
13 Blank
14–17 CPU time slice (use 9999 to prevent premature termination)
18 Blank

Chapter 10: Installing Online Interfaces 131

How to Complete Configuration of the XMS Online Interfaces With CA MSM

Column Contents
19–24 Maximum memory (in KB) below the 16 MB line
This memory is only for the cross-memory driver program (50 KB is
ample)
25 Blank
26–31 Maximum memory (in KB) below the line that CA Deliver can acquire at
one time
Use 999999 so that GETMAINs are not limited
32 Blank
33–38 Maximum memory (in KB) above the 16 MB line
This memory is only for the cross-memory driver program (50 KB is
ample)
39 Blank
40–45 Maximum memory (in KB) above the line that CA Deliver can acquire at
one time
Use 999999 so that GETMAINs are not limited
46 Blank
47–48 CP to call EC0XMROS as a TSO command processor
49 Y – Application authorized to issue MODESET SVC
50 Blank
51-52 CP to call EC0XMROS as a TSO command processor
53-255 Ignored

132 Installation Guide

 How to Complete Configuration of the XMS Online Interfaces With CA MSM

CA Roscoe Cross-Memory Notes

Be aware of the following:

■ Start the primary RMOXMS region with the XMSSUB=YES parameter.
The XMSSUB=YES parameter must only be used in an XMS address space with a
default subsystem ID (SUBSYS=XMC0 or not specified).
■ If multiple RMOXMS regions are started, they must be started with XMSSUB=NO
parameter.
Only the primary XMS region can have XMSSUB=YES specified.
■ The XMS regions must have the XMS=YES parameter to make it accessible.
■ The EBCXMCTR table must be assembled during installation to define the
relationship between CA View and CA Deliver database high-level qualifiers.
The table contains an EBCXMOPT macro to define initialization options and the
EBCXMTRN macro for each CICS user transaction.

The EBCXMTRN macro also contains options for the specific database as follows:
■ SUBSYS= parameter of the cross-memory task.
This parameter must match the SUBSYS= parameter specified in the EBCXMCTR
table entry.
■ RECON=YES can be used to allow reconnection (after a TSO terminal error) at the
point of exit.
■ TIMEOUT= specifies how long TSO is to wait for the XMS session to respond after
the user enters input, in seconds.
We recommend as high a value as possible but not less than 240 (4 minutes).

Note: The SUBMAX= parameter controls the number of user connections, not the
USERMAX= parameter. USERMAX=only applies when using the subtask with the CICS
interface.

Install the CICS Pseudo-Conversational Option

Important! This option uses the cross-memory feature distributed with CA Deliver and
must be installed with that feature. For more information about cross-memory, see
Install Cross-Memory Services.

Chapter 10: Installing Online Interfaces 133

How to Complete Configuration of the XMS Online Interfaces With CA MSM

Installation Steps

The following steps are required to install the CICS Pseudo-Conversational Option. Each
step is explained in detail in the sections that follow.
1. Place the CA Deliver load libraries into DFHRPL and STEPLIB.
2. Code the PCT and PPT Table Entries to CICS.
3. (Optional) Prepare the interface to a user-written CICS menu system.

Step 1: Add Modules to DFHRPL and STEPLIB

The CA Deliver load library is required in the CICS DFHRPL and in the STEPLIB in the CICS
region.

Note: If the CAI.CVDELOAD load library is in the linklist, it does not have to be included
as a STEPLIB in the CICS region

Be sure that these modules are available in the DFHRPL concatenation of libraries.
1. EC0CICUX
2. EC0CIEND
3. EC0CINIT
4. EC0CISRV
5. EC0XMCIC
6. EC0Cversion-number
Where:
release-number represents the CICS release number.
– CTS 3.1 release number: 0640
– CTS 3.2 release number: 0650
– CTS 4.1 release number: 0660
– CTS 4.2 release number: 0670
– CTS 5.1 release number: 0680

You can copy the six modules to the DD statement DFHRPL in your CICS task. However,
we strongly recommend that you concatenate CAI.CVDELOAD to the DD statement
DFHRPL.

Note: Several CA Deliver modules are loaded (MVS load) from the CICS STEPLIB or
LINKLIST. Verify that the entire CA Deliver load library is defined in the CICS STEPLIB or is
included in the linklist.

134 Installation Guide

 How to Complete Configuration of the XMS Online Interfaces With CA MSM

Step 2: Code the PCT and PPT Table Entries to CICS

The CICS transactions and programs were previously defined in the MSM configuration
step. Review the following points to determine if they are applicable to your installation.

CICS Resource Definition Online Storage Protection

If you have CICS storage protection activated, resource definition online settings are
required, as follows:
■ For all transactions:
TASKDATALOC=ANY
TASKDATAKEY=CICS

■ For all programs:

DATALOCATION=ANY
EXECKEY=CICS

PLT Start-up List

Add these table entries to the last phase of the PLT startup list to initialize the subtask
that is used for cross-memory access:

DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM
DFHPLT TYPE=ENTRY,PROGRAM=EC0CINIT

PLT Shutdown List

Add these table entries to the first phase of the PLT shutdown list to ensure that the
subtask that executes as part of the CA Deliver online facility correctly shuts down when
CICS shuts down:

DFHPLT TYPE=ENTRY,PROGRAM=EC0CIEND
DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM

Optional DCT Entries

Specify a value for the DESTID parameter in the EBCXMOPT macro in the EC0XMCTR
module and corresponding DCT entries. This value defines a transient data destination
for messages issued by the subtask.

Note: Specify a blank for DESTID to suppress the generation of informational messages
from the subtask.

Chapter 10: Installing Online Interfaces 135

How to Complete Configuration of the XMS Online Interfaces With CA MSM

The DCT entries for a DESTID of XMC0 are:

RMOLOG DFHDCT TYPE=SDSCI, FOR CICS MESSAGES AND SHUTDOWN

BLKSIZE=250, STATISTICS
BUFNO=1,
DSCNAME=RMOLOG,
RECFORM=VARUNBM,
RECSIZE=242,
TYPEFLE=OUTPUT
XMC0G DFHDCT TYPE=EXTRA,
DESTID=XMC0,
DSCNAME=RMOLOG

Step 3: (Optional) Invoke the System from a CICS Menu System

If you want to invoke CA Deliver from a user-written CICS menu system, then return to
that menu system when you exit from CA Deliver, do the following:

Invoke CA Deliver from the menu system by using this CICS command:

EXEC CICS START TRANSID(DELIVER transaction-id)

TERMID(EIBTRMID)
FROM(data-area)
LENGTH(4)

where:
TRANSID(DELIVER transaction-id)
Specifies the CA Deliver transaction ID.
TERMID(EIBTRMID)
Specifies the terminal that a CA Deliver transaction will communicate with.
FROM (data-area)
Specifies the optional variable length character string.
The format of the data-area parameter is:
tran,
where:
tran
Specifies the return menu CICS transaction to be started when CA Deliver
finishes.
Note: None of the data-area parameters is required.
LENGTH (4)
Specifies the number of bytes in the data field being passed.

136 Installation Guide

 How to Complete Configuration of the XMS Online Interfaces With CA MSM

Note:

When CA Deliver receives control, it retrieves the four-byte return transaction ID and
saves it from iteration to iteration.

If the retrieve fails, CA Deliver retains the information that it was started directly from a
terminal, not a menu system.

When CA Deliver finishes processing, it determines whether it should return to a menu

system by starting the return transaction.

If there is a saved transaction ID, CA Deliver starts the return transaction before it exits
to CICS by issuing:
EXEC CICS START TRANSID(RETURN transaction-id)
TERMID(EIBTRMID)
NOCHECK

CICS Notes

The cross memory CICS access involves two different address spaces: the CICS address
spaces and the XMS address spaces.

CICS Address Spaces

The user's CICS transactions and the cross memory support subtask reside in the
address spaces.
■ If multiple CICS regions are used to access CA Deliver, each CICS region will have an
XMS support subtask.
■ If you are using CICS/MRO, CA Deliver normally runs in an AOR (application region).

XMS Address Spaces

Be aware of the following:

■ The primary RMOXMS region can be started with the XMSSUB=YES or XMSSUB=NO
parameter.
■ CICS has a router subtask in its region and does not require the XMSSUB=YES
function. However, we recommend that you start the primary XMS region with
XMSSUB=YES.
■ If multiple RMOXMS regions are started, they must be started with XMSSUB=NO
parameter.
Only the primary XMS region can have XMSSUB=YES specified.
■ The XMS regions must have the XMS=YES parameter to be accessible.
■ The SUBSYS= parameter must match the EC0XMCTR table entry for the CICS
transaction.

Chapter 10: Installing Online Interfaces 137

How to Complete Configuration of the XMS Online Interfaces With CA MSM

■ The EBCXMCTR table must be assembled during installation to define the

relationship between CA View and CA Deliver database high-level qualifiers.
The table contains an EBCXMOPT macro to define initialization options and the
EBCXMTRN macro for each CICS user transaction.

The EBCXMTRN macro also contains options for the specific database as follows:
■ SUBSYS= parameter can be used to route the CA Deliver transaction to an alternate
XMS subsystem ID. The SUBSYS= of the cross memory task must match the SUBSYS=
parameter specified in the EBCXMCTR table entry.
■ TRANID=parameter specifies the CA Deliver transaction identifier for CICS.
■ RECON=YES can be used to allow reconnection (after a CICS terminal error) at the
point of exit.
Note: Do not specify RECON=YES if you use a multi-session manager that assigns LU
names from a pool of names. Coding RECON=YES under these conditions could
allow a user to be connected to another user's session. For more information, see
Multi-Session Managers later in this chapter.
■ TIMEOUT= specifies how long CICS is to wait for the XMS session to respond after
the user enters input, in seconds.
We recommend as high a value as possible but not less than 240 (4 minutes).

CICS XMS Subtask Startup

Use one of these methods to start the XMS subtask automatically:

1. When the CICS region is started, use the DFHPLTPI definition to automatically start
the XMS subtask.
2. Define a transaction for the EC0CINIT program to allow for manual startup.
3. Write a CICS program to transfer control (XCTL) to EC0CINIT when you want to start
the XMS subtask.

Until the XMS subtask is started, expect the transactions referencing EC0XMCIC to
terminate with an error message that indicates that the XMS subtask is not active.

Note:
■ When the CICS region is terminated, the DFHPLTSD definition is to be used to
terminate the XMS subtask.
You can manually terminate the XMS subtask through a user application program
that LINKs the EC0CIEND or you can use the optional transaction defined for
EC0CIEND for manual termination.

138 Installation Guide

 How to Complete Configuration of the XMS Online Interfaces With CA MSM

■ If you want to terminate the XMS subtask manually, we recommend that you use
the DFHPLTSD entry to terminate the XMS subtask. This definition is needed to
clean up linkages to the XMS address spaces.
■ To prevent users from shutting down the XMS subtask, secure the optional
transaction for program EC0CIEND.

Multi-Session Managers Using Virtual LU Names

Multi session manager products, for example CA TPX Session Management (CA TPX), can
be configured to assign an LU name to a user's terminal at the time the user selects the
CICS application.

Important! This assignment means that a user can enter CICS each time with a different
terminal ID which can cause problems for CA Deliver application.

For example: If a user uses a multi-session manager to end a session, or shuts the PC
down, CA Deliver does not know that the user has left. Another user might select CICS,
be assigned to the same LU name as the previous user, and enter CA Deliver with the
same terminal ID as the previous user. CA Deliver believes that there are two active
users on the same terminal.

To prevent this situation, you can add a small amount of code to the CICS Autoinstall
Control Program.

Note: The default name of this program is DFHZATDX and its source is located in
SDFHSAMP.

Chapter 10: Installing Online Interfaces 139

How to Complete Configuration of the XMS Online Interfaces With CA MSM

If you are not a CICS systems programmer, discuss this situation with the person in your
company who is responsible for CICS support and maintenance.

The sample code that follows shows how to clear an active user from the CA Deliver
application at terminal deletion time. Insert this code in your Autoinstall Control
Program.

The source that is shipped with CICS contains this line:

* ==> PUT DELETE CODE HERE

Insert the code after that line.

LOAD EP=EC0XSLOC,ERRET=RETURN
LR R6,R0 GET EBCXSLOC ADDRESS
ICM R8,B'1111',0(R6) ADDR OF MAIN CONTROL BLOCK
BZ RETURN GET OUT IF NONE
LA R7,4(,R8) LOOK LIKE FIRST USER BLOCK
XSU_LOOP DS 0H
ICM R7,B'1111',8(R7) USER BLOCK ADDR
BZ RETURN GET OUT IF DONE
CLC DELETE_TERM_ID,104(R7) FOR THIS TERMINAL?
BNE XSU_LOOP NO
TM 120(R7),X'01' ACTIVE ENTRY?
BZ XSU_LOOP NO
OI 120(R7),X'02' SHOW SESSION DONE
B RETURN EXIT PROGRAM

This code does the following:

1. Attempts to load program EC0XSLOC
■ If the load fails, this is not the region containing CA Deliver and it exits.
■ If CA Deliver is active in this region, the first word of EC0XSLOC contains the
address of the main control block.
If this word is zero, CA Deliver is not active and the program exits.
2. Scans the chain of CA Deliver user control blocks to find the terminal to be deleted
■ If the program finds the terminal ID, it makes sure that the user block is in use
and is active, then it clears the appropriate fields.
■ If the block does not represent an active user, the program continues to search
the chain to the end.
■ If the program gets to the end of the chain without finding the terminal ID, the
program exits.
■ If you implement this change to the terminal deletion section of the Autoinstall
Control Program, you can prevent the problems caused by the methods that
were used to leave the CA Deliver application.

140 Installation Guide

 How to Complete Configuration of the XMS Online Interfaces With CA MSM

Install the IMS Online Retrieval Option

Use these steps to install the IMS online retrieval option.

Important! This facility uses the cross-memory feature distributed with CA Deliver and
must be installed with that feature. For more information about cross-memory, see
Installing Cross-Memory Services.

Installation Steps

This list summarizes the steps required to install the IMS Online Retrieval Option.
Detailed instructions are in the sections that follow.
1. Code the IMS TRANSACT, PSB and APPLCTN macros.
2. Run the PSB, ACB, and SYSGEN Procedures.
3. Load EC0IMSUX Modules.
4. Move load modules to IMSVS.PGMLIB.

Important! All JCL and macros provided in this section are provided as general examples
only and must be modified for your site's systems and standards.

Step 1: Code the Macros

Use the examples in this section as a guide as you code these macros, and implement
them in your IMS system.
■ (IMS) TRANSACT macro
■ PSB macros
■ APPLCTN macro

TRANSACT Macro

One or more transactions must be defined for the IMS online retrieval program
RMOXMIMS. Normally, only one transaction identifier is defined, although you can
define multiple transactions.

This TRANSACT macro identifies the RMOXMIMS transaction to IMS:

TRANSACT NAME=EC0XMIMS,SPA=(18)

PSB Macros

This PSB must be generated for the EC0XMIMS transaction:

PCB TYPE=TP,ALTRESP=YES,MODIFY=YES
PSBGEN PSBNAME=EC0XMIMS,LANG=ASSEM,COMPAT=YES

Chapter 10: Installing Online Interfaces 141

How to Complete Configuration of the XMS Online Interfaces With CA MSM

APPLCTN Macro

This APPLCTN must be generated for the RMOXMIMS transaction:

APPLCTN PSB=EC0XMIMS

Step 2: Run the PSB, ACB, and SYSGEN Procedures

Use the macros created in Step 1. Code the Macros as input for these procedures:

PSBGEN
ACBGEN
IMS SYSGEN

Step 3: Load EC0IMSUX Modules

Move load modules EC0IMSUX to IMSVS.PGMLIB.

Note: EC0IMSUX is in CAI.CVDELOAD and must be copied to IMSVS.PGMLIB.

IMS Notes (New Version)

Be aware of the following:

■ The new IMS/DC Transaction Program (EC0XMIMS) is a replacement for the older
RMOXMIMS program.
■ The EC0XMIMS does not need to be linkedited to the ASMTDLI interface program.
The transaction is now conversational with a SPASIZE=18 (this can be adjusted).
■ If you use extended color, the SEGSIZE= may need to be increased, because
extended color data streams can be a 50% increase over the monochrome data
stream size.
To determine the SEGSIZE= value, take the terminal that will use the interface with
the largest screen size, in bytes, and apply this formula:

ROWS * COLS * 1.5 = SEGSIZE

For example, a 3278-5 with a 27 x 132 screen size would be (27 * 132 * 1.5) = 5346.
If the SEGSIZE= is too small, the terminal user will get an RC= "A6" message
indicating that a message insert failed.

142 Installation Guide

 How to Complete Configuration of the XMS Online Interfaces With CA MSM

IMS/DC Parameter Relationships

The cross-memory IMS/DC access involves up to three different address spaces as

follows:
■ IMS/DC message processing region address spaces
The user's IMS/DC transaction resides here. If multiple IMS/DC users are processing
concurrently (input being processed by the XMS system), a separate IMS/DC
message region is used for each user.
IMS/DC can control the maximum number of IMS/DC transactions executing at one
time.
■ The XMS support subtask
– The subtask is started when the XMSSUB=YES input parameter is used when an
XMS address space is started.
– The subtask can be in a separate XMS address space or share the address space
with XMS or VTAM sessions.
– The XMSSUB=YES must only be used in an XMS address space with a default
subsystem ID (SUBSYS=XMC0 or not specified).
– If multiple XMS address spaces are started, only one can have the XMSSUB=YES
specified.
Note: All IMS/DC, TSO/XMS, ISPF/XMS and CA Roscoe/XMS sessions share the same
XMS subtask.
■ XMS address spaces
See the topic that follows.

Chapter 10: Installing Online Interfaces 143

How to Complete Configuration of the XMS Online Interfaces With CA MSM

IMS/DC Cross-Memory Notes

Be aware of the following:

■ The primary RMOXMS region is to be started with the XMSSUB=YES parameter.
This region can be in a separate XMS address space or share the address space with
XMS or VTAM sessions.
■ The XMSSUB=YES parameter must only be used in an XMS address space with a
default subsystem ID (SUBSYS=XMC0 or not specified).
■ If multiple RMOXMS regions are started, they must be started with XMSSUB=NO
parameter.
Only the primary XMS region can have XMSSUB=YES specified.
■ The XMS regions must have the XMS=YES parameter to make it accessible.
■ The EBCXMCTR table must be assembled during installation to define the
relationship between CA View and CA Deliver database high-level qualifiers. The
table contains an EBCXMOPT macro to define initialization options and the
EBCXMTRN macro for each CICS user transaction.

The EBCXMTRN macro also contains options for the specific database:
■ SUBSYS= parameter of the cross-memory task.
The parameter must match the SUBSYS= parameter specified in the EBCXMCTR
table entry.
■ RECON=YES can be used to allow reconnection (after an ISPF terminal error) at the
point of exit.
■ TIMEOUT= specifies how long ISPF is to wait for the XMS session to respond after
the user enters input, in seconds.
We recommend a value as high as possible but not less than 240 (4 minutes).

To abort the XMS session and return the user to ISPF or the TSO command prompt,
press the ATTN key.

Note: The SUBMAX= parameter controls the number of user connections, not the
USERMAX= parameter. USERMAX=only applies when you are using the subtask with the
CICS interface.

To control screen size manually, use these operands. The SNA query command can also
be used to determine the device characteristics.

Enter For Terminal Type

M2 3278-2 24 x 80 default screen size
M2H 3278-2 24 x 80 highlighting

144 Installation Guide

 How to Complete Configuration of the XMS Online Interfaces With CA MSM

Enter For Terminal Type

M2X 3279-2 24 x 80 color highlighting
M2C 3279-2 24 x 80 color
M3 3278-3 32 x 80
M3H 3278-3 32 x 80 highlighting
M3X 3279-3 32 x 80 color highlighting
M3C 3279-3 32 x 80 color
M4 3278-4 43 x 80 highlighting
M4H 3278-4 43 x 80 highlighting
M4X 3279-4 43 x 80 color highlighting
M4C 3279-4 43 x 80 color
M5 3278-5 27 x 132
M5H 3278-5 27 x 132 highlighting
M5X 3279-5 27 x 132 color highlighting
M5C 3279-5 27 x 132 color
M6 3290 62 x 80
M6H 3290 62 x 80 highlighting
M7 3290 31 x 160
M7H 3290 31 x 160 highlighting
M8 3290 62 x 160
M8 3290 62 x 160 highlighting

For other modifications to your system, see your VTAM programmer.

Chapter 10: Installing Online Interfaces 145

How to Configure the Online Interfaces Without CA MSM

Optional Initialization Parameter Statements

The optional initialization parameter statements are delivered as comments in the
initialization member RMOPARMS in the CVDEOPTN library.

Review these initialization parameters in the RMOPARMS member after configuration is

completed.

Note: For more information about the descriptions of these parameters, see the chapter
Initialization Parameters in the Reference Guide.

If any of the parameters are deemed necessary, remove the comment and supply the
necessary parameter before you start CA Deliver.

How to Configure the Online Interfaces Without CA MSM

The topics in this section describe the manual tasks you must perform if you are not
using CA MSM to configure your product.

This section also describes the online interface options, the cross-memory drivers, and
how to install the online interfaces, including these topics:
■ Online and cross-memory interfaces
■ Cross-memory drivers for ISPF, TSO, and CA Roscoe interfaces
■ Installation of these options:
– ISPF online retrieval option
– TSO online retrieval option
– CA Roscoe online retrieval option
– Cross-memory services
– ISPF/cross-memory online retrieval option
– TSO/cross-memory online retrieval option
– VTAM online retrieval option
– CA Roscoe/cross-memory online retrieval option
– CICS pseudo-conversational option
– IMS online retrieval option

146 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Online Interfaces
The following table lists the online interfaces, whether cross-memory services (XMS)
must be installed and any special advantages of using the interface.

Online Interface XMS Advantages

ISPF NO Provides full online access without the need for a
cross-memory region
ISPF/XMS YES Does not require the STEPLIB to be APF authorized
To simplify migration, you can run multiple versions of
CA Deliver concurrently.
TSO NO Provides full online access without the need for a
cross-memory region
TSO/XMS YES Does not require the STEPLIB to be APF authorized
To simplify migration, you can run multiple versions of
CA Deliver concurrently.
VTAM YES Supports extended data stream to queriable terminals
CICS YES To simplify migration, you can run multiple versions of
CA Deliver concurrently
IMS/DC YES
CA Roscoe NO Provides full online access without the need for a
cross-memory region
CA Roscoe/XMS YES Does not require the STEPLIB to be APF authorized
To simplify migration, you can run multiple versions of
CA Deliver concurrently.

Cross-Memory Services Interface (XMS)

The cross-memory services interface manages several interfaces; this allows you to
control online access with a single operator interface. Advantages of the interfaces are
discussed later in this chapter.

Chapter 10: Installing Online Interfaces 147

How to Configure the Online Interfaces Without CA MSM

The parameters in the startup procedure for the cross-memory task allow you to
control:
■ The maximum number of users allowed on the system
■ Whether to cancel users when they are inactive for a specified time (CANCEL and
LONGWAIT)

Note: For information about startup parameters, see Installing Cross-Memory Services
later in this chapter.

The operator commands available to modify the cross-memory task allow you to:
■ Cancel users
■ Suspend additional logons
■ List online usage statistics
■ Modify selected cross-memory startup JCL parameters

Note: For more information about operator commands, see the chapter "Operator
Commands" in the Reference Guide.

Cross-Memory Drivers for Interfaces

You can use cross-memory services drivers to run the TSO, ISPF, and CA Roscoe online
interfaces.

The advantages of using these drivers are:

■ Users are authorized by cross-memory drivers.
When you use the cross-memory services drivers for the ISPF, TSO, or CA Roscoe
interfaces, users are authorized by cross-memory and do not also need
authorization from the online interface (for example, TSO).
■ Multiple versions of CA Deliver can run simultaneously.
When you use the cross-memory services drivers for the ISPF, TSO, or CA Roscoe
interfaces, you can run multiple versions of CA Deliver concurrently. This ability
supports migration; it makes it easier to migrate when you are converting to a new
version level of CA Deliver.
You can also run multiple versions of the online interfaces simultaneously.

Restrictions

These restrictions apply when you execute the program using the cross-memory drivers
for TSO, ISPF, and CA Roscoe:
■ TSO SUBMIT is not used. The SUBMIT occurs from the connected cross-memory
region.

148 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

■ Direct reprints from the user have the JES banner pages of the cross-memory
region. The internal system banner page can be used to check the user requesting
the reprint.

User Exits

User exits run in the cross-memory region and do not have access to TSO or CA Roscoe
allocations.

Install the ISPF Online Retrieval Option

The ISPF online retrieval option runs under the IBM Interactive System Productivity
Facility (ISPF) for z/OS Version 3.0 and higher.

Installation Steps

The following steps are required to install the ISPF/cross-memory online retrieval
option. Each step is explained in detail later in the sections that follow.
1. (Optional) Add STEPLIB DD statements to the TSO LOGON procedures if the load
modules were not copied to a linklist library.
2. Add the panel and command table libraries to the TSO LOGON procedures.
3. (Optional) Modify an ISPF Selection Menu to Select Online Retrieval feature.

(Optional) Step 1: Add STEPLIB Statements

The action you take in this step depends on what you did during the base product
installation—specifically, did you:
■ Authorize the program load library or
■ Copy the modules to a system-authorized library

If the CA Deliver load modules were not copied to one of the libraries in the linklist,
proceed with this step; otherwise go directly to the next step.

Follow these steps:

1. Add STEPLIB DD statements to the TSO LOGON procedures if the load modules are
not in a linklist library.
2. Add a STEPLIB DD statement for the library containing the product's load modules
to the LOGON procedures for those TSO users who are going to be using the ISPF
online retrieval option.

Note: If you have CA View, the CA View load modules must also be either in the linklist
or in a STEPLIB statement with this step.

Chapter 10: Installing Online Interfaces 149

How to Configure the Online Interfaces Without CA MSM

Step 2: Add the Panel and Command Libraries (ISPF only)

Note: If you are running under SPF, go to Step 3.

If you run CA Deliver under ISPF, proceed with this step.

To add the panel and command libraries to the TSO LOGON procedure:
1. Concatenate the command table library CAI.CVDETBL0 to DD statement ISPTLIB.
2. Concatenate the panel library CAI.CVDEPNL0 to DD statement ISPPLIB.

Note: If you also plan to use RMOSPF (the ISPF interface), and multiple versions of CA
Deliver, concatenate CAI.CVDETBL0 first. Use the CAI.CVDETBL0 from the most current
release.

Step 3: (Optional) Modify an ISPF Selection Menu to Select Online Retrieval

If you want to add a selection code for the online retrieval feature to one of the ISPF
selection menus, proceed with this step; otherwise, your detailed instructions for ISPF
are complete.

To define your selection code, use the following command:

PGM(RMOSPF) PARM(high-level-database-name) NEWAPPL(RMO)

Use the value next to the NAME parameter on your Initialization Parameter Worksheet
for PARM (high-level-database-name).

Note: Adding a selection code allows you to select the online retrieval feature in the
same way you would select other ISPF options.

Panel Libraries

The names of the panel libraries vary from site to site and for the different releases of
ISPF. These panel libraries are allocated to the ISPPLIB DD statement under TSO.

Be aware that some installations do not allow direct modifications of IBM panels and
libraries. In this case, you can place the modified panels in user or site-specific libraries
and concatenate them ahead of the IBM libraries.

Ask your system administrator for the specific ISPF panel library that applies to your site
and contains the panel ISR@PRIM.

Note: The selection menus shown in the following examples are part of the program
product ISPF and are copyrighted by IBM.

150 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Example 1

This example shows you how to add selection code R to the primary option menu
ISR@PRIM for ISPF.

The offset lines are the inserted lines.

%----------------------- ISPF/PDF PRIMARY OPTION MENU ------------------------

%OPTION ===>_ZCMD +
% +USERID - &ZUSER
% 0 +ISPF PARMS - SPECIFY TERMINAL AND USER PARAMETERS +TIME -
% 1 +BROWSE - DISPLAY SOURCE DATA OR OUTPUT LISTINGS +TERMINAL -
% 2 +EDIT - CREATE OR CHANGE SOURCE DATA +PF KEYS - &ZKEYS
% 3 +UTILITIES - PERFORM UTILITY FUNCTIONS
% 4 +FOREGROUND - INVOKE LANGUAGE PROCESSORS IN FOREGROUND
% 5 +BATCH - SUBMIT JOB FOR LANGUAGE PROCESSING
% 6 +COMMAND - ENTER TSO COMMAND, CLIST, OR REXX EXEC
% 7 +DIALOG TEST - PERFORM DIALOG TESTING
% 8 +LM UTILITIES - PERFORM LIBRARY ADMINISTRATOR UTILITY FUNCTIONS
% C +CHANGES - DISPLAY SUMMARY OF CHANGES FOR THIS RELEASE
% R +RMOSPF - DELIVER ADMINISTRATION
% T +TUTORIAL - DISPLAY INFORMATION ABOUT ISPF/PDF
% X +EXIT - TERMINATE ISPF USING LOG AND LIST DEFAULTS

%
+ENTER%END+COMMAND TO TERMINATE ISPF.
)INIT
.HELP = ISR00003
&ZPRIM = YES /* ALWAYS A PRIMARY OPTION MENU */
&ZHTOP = ISR00003 /* TUTORIAL TABLE OF CONTENTS */
&ZHINDEX = ISR91000 /* TUTORIAL INDEX - 1ST PAGE */
)PROC
&ZSEL = TRANS( TRUNC (&ZCMD,'.')
0,'PANEL(ISPOPTA)'
1,'PGM(ISRBRO) PARM(ISRBRO01)'
2,'PGM(ISREDIT) PARM(P,ISREDM01)'
3,'PANEL(ISRUTIL)'
4,'PANEL(ISRFPA)'
5,'PGM(ISRJB1) PARM(ISRJPA) NOCHECK'
6,'PGM(ISRPTC)'
7,'PGM(ISPYXDR) PARM(ISR) NOCHECK'
8,'PANEL(ISRLPRIM)'
C,'PGM(ISPTUTOR) PARM(ISR00005)'
R,'PGM(RMOSPF) PARM(RMO.SYSTEM1) NEWAPPL(RMO)'
T,'PGM(ISPTUTOR) PARM(ISR00000)'
' ',' '
X,'EXIT'
*,'?' )
&ZTRAIL = .TRAIL
)END

Chapter 10: Installing Online Interfaces 151

How to Configure the Online Interfaces Without CA MSM

Note:
■ NEWAPPL(RMO) is required and must be specified as shown previously in this
section.
This parameter is used with the command table library concatenation from Step 3
of the ISPF Installation Instructions.
■ NEWAPPL(RMO) allows CA Deliver to correctly interpret commands and program
function key invocation.
If this parameter is not specified, certain PF keys such as the scroll keys may not
function.

152 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Example 2

This example shows you how to add selection code R to the primary option menu
ISP@PRIM for SPF. Shading identifies the inserted lines.
%----------------------- SPF–MVS PRIMARY OPTION MENU ---------------
%OPTION ===>_OPT
% +USERID -
% 0 +ISPF PARMS - SPECIFY TERMINAL AND USER PARAMETERS +TIME -
% 1 +BROWSE - DISPLAY SOURCE DATA OR OUTPUT LISTINGS +TERMINAL –
% 2 +EDIT - CREATE OR CHANGE SOURCE DATA +PF KEYS -
% 3 +UTILITIES - PERFORM SPF UTILITY FUNCTIONS
% 4 +FOREGROUND - COMPILE, ASSEMBLE, OR DEBUG
% 5 +BACKGROUND - COMPILE, ASSEMBLE, OR LINK EDIT
% 6 +COMMAND - ENTER TSO COMMAND OR CLIST
% 7 +SUPPORT - TEST DIALOG OR CONVERT MENU/MESSAGE FORMATS
% 8 +LM UTILITIES- PERFORM LIBRARY ADMINISTRATOR UTILITY FUNCTIONS
% R +RMOSPF - DELIVER ADMINISTRATION
% T +TUTORIAL - DISPLAY INFORMATION ABOUT SPF
% X +EXIT - TERMINATE SPF USING LIST/LOG DEFAULTS
%
+PRESS%END KEY TO TERMINATE SPF+
%
)INIT
.HELP = TTUTOR
&ZHTOP = TTUTOR /* TUTORIAL TABLE OF CONTENTS */
&ZHINDEX = TINDEX /* TUTORIAL INDEX - 1ST PAGE */
)PROC
&ZSEL = TRANS( TRUNC (&OPT,'.')
0,'PANEL(ISPOPT)'
1,'PGM(ISRBRO)'
2,'PGM(ISPEDIT)'
3,'PANEL(ISPUTIL)'
4,'PANEL(ISPFORA)'
5,'PANEL(ISRJOB)'
6,'PGM(ISPTSO)'
7,'PANEL(ISPOTAC)'
R,'PGM(EC0XMSPF) PARM(RMO.SYSTEM1)'
T,'PGM(ISPTUTOR) PARM(T)'
' ',' '
X,'EXIT'
*,'?' )
)END

Chapter 10: Installing Online Interfaces 153

How to Configure the Online Interfaces Without CA MSM

Example 3

This example shows you how to add selection code 3.R as a sub-option to the utilities
menu ISPUTIL for ISPF.

The offset lines are the inserted lines.

%----------------------- UTILITY SELECTION MENU --------- -----------
%OPTION ===>_OPT +
% +
% 1 +LIBRARY - LIBRARY UTILITY:
+ PRINT INDEX LISTING OR ENTIRE DATASET
+ PRINT, RENAME, DELETE, OR BROWSE MEMBERS
+ COMPRESS DATASET
% 2 +DATASET - DATASET UTILITY:
+ DISPLAY DATASET INFORMATION
+ ALLOCATE, RENAME, OR DELETE ENTIRE DATASET
+ CATALOG OR UNCATALOG DATASET
% 3 +MOVE/COPY - MOVE OR COPY MEMBERS OR DATASETS
% 4 +CATALOG - CATALOG MANAGEMENT:
+ DISPLAY OR PRINT CATALOG ENTRIES
+ INITIALIZE OR DELETE USER CATALOG ALIAS
% 5 +RESET - RESET STATISTICS FOR MEMBERS OF ISPF LIBRARY
% 6 +HARDCOPY - INITIATE HARDCOPY OUTPUT
% 7 +VTOC - DISPLAY OR PRINT VTOC ENTRIES FOR A DASD VOLUME
% 8 +OUTLIST - DISPLAY, DELETE, OR PRINT HELD JOB OUTPUT
% 9 +SCRIPT/VS - FORMAT,DISPLAY, AND OPTIONALLY PRINT SCRIPT TEXT
% R +RMOSPF - DELIVER ADMINISTRATION

)INIT
.HELP = TU
)PROC
&SEL = TRANS( TRUNC (&OPT,'.')
1,'PGM(ISPUDA) PARM(UDA1)'
2,'PGM(ISPUDA) PARM(UDA1)'
3,'PGM(ISPUMC)'
4,'PGM(ISPUCA)'
5,'PGM(ISPURS)'
6,'PGM(ISPUHC)'
7,'PGM(ISPUVT)'
8,'PGM(ISPUOL) PARM(UOL01)'
9,'PGM(ISPUSC) PARM(SCRPTA)'
R,'PGM(RMOSPF) PARM(RMO.SYSTEM1) NEWAPPL(RMO)'
' ',' '
*,'?' )
)END

154 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Install the TSO Online Retrieval Option

The following step is required to install the TSO online retrieval option and is explained
in detail in the next topic.

(Optional) Add STEPLIB DD statements to the TSO LOGON procedures if the load
modules are not in a linklist library.

Step 1: (Optional) Add STEPLIB DD Statements

The action you take in this step depends on what you did during the base-product
installation—specifically, did you:
■ Authorize the program load library or
■ Copy the modules to a system authorized library

If the load modules were not copied to one of the libraries in the linklist:
■ Add a STEPLIB DD statement (for the library containing the load modules) to the
TSO LOGON procedures for those TSO users who are to use the native TSO online
retrieval option.

If the load modules were copied to one of the libraries in the linklist, no STEPLIB DD
statements are required.

Note: If you have CA View, the CA View load modules either must also be in the linklist,
or placed in a STEPLIB statement with this step.

Install the CA Roscoe Online Retrieval Option

The CA Roscoe online retrieval option runs as a command processor under
ETSO/Roscoe.

The following steps are required to install the CA Roscoe/Cross-Memory Online

Retrieval Option. Each step is explained in detail in the sections that follow.
1. (Optional) Concatenate the Load Module Library to the ETSOLIB DD statement, if
the load modules were not copied to a linklist library.
2. Add the control statement for the RMOROS command processor to the Eligible
Program List (EPL).
3. Invoke the RMOROS command processor.

Chapter 10: Installing Online Interfaces 155

How to Configure the Online Interfaces Without CA MSM

Step 1: (Optional) Concatenate the Load Module Library

If the load modules were not copied to a linklist library, concatenate the library that
contains the load modules to the ETSOLIB DD statement in the CA Roscoe startup JCL.

Note: If you have CA View, the CA View load modules must also be either in the linklist
or in an ETSOLIB statement with this step.

Step 2: Add RMOROS Command Process

Add this Eligible Program List control statement to member ETSOPGMS for the CA
Roscoe user with the RO prefix:

Column Contents
1–8 RMOROS
9 Blank
10–12 Number of users allowed to access CA Deliver at one time
13 Blank
14–17 CPU time slice; use 9999 to prevent premature termination
18 Blank
19–24 Maximum memory (in KB) below the 16 MB line
This value can vary depending on size of database and other factors
(0001000 should be adequate).
25 Blank
26–31 Maximum memory (in KB) below the line that CA Deliver can acquire
at one time
Use 999999 so that GETMAINs are not limited.
32 Blank
33–38 Maximum memory (in KB) above the 16 MB line
This value can vary depending on the features used (000512 should
be adequate).
39 Blank
40–45 Maximum memory (in KB) above the line that CA Deliver can acquire
at one time
Use 999999 so that GETMAINs are not limited.
46 Blank
47–48 CP to call RMOROS as a TSO command processor

156 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Column Contents
49 Y – Application authorized to issue MODESET SVC
50 Blank
51-52 CP to call EC0XMROS as a TSO command processor
53-255 Ignored

Install Cross-Memory Services

The cross-memory services interface is required for these online interfaces:
■ CICS pseudo-conversational
■ IMS
■ VTAM
■ ISPF/cross-memory
■ TSO/cross-memory
■ CA Roscoe/cross-memory

This list summarizes the steps to install the cross-memory services. Detailed instructions
are in the sections that follow.
1. (Optional) Add the Start Procedure to the PROCLIB for the Cross-Memory Online
Task.
2. (Optional) Modify, Assemble, and Link the EC0XMCTR Module.
3. Define Security Requirements.

Cross-Memory Services Regions

The VTAM and XMS (cross-memory services) interfaces operate in one or more
cross-memory online regions.

A cross-memory region can be configured as:

■ An XMS only region
■ A VTAM only region
■ A combination of XMS and VTAM users

Chapter 10: Installing Online Interfaces 157

How to Configure the Online Interfaces Without CA MSM

Be aware of the following:

■ Each cross-memory region is configured with the start-up parameters provided on
the PARM= of the execute statement, and with an optional SYSIN DD statement.
The REGION= specification determines the maximum number of users supported.
■ Allow 20 MB (megabytes) for the XMS region plus 1 MB of storage for every two
users.

For example, if you specified a REGION of 120 MB, you could specify:

USERMAX=200

If more users are needed, multiple regions can be started under the same SUBSYS=
value and will be chained together.

Note: The REGION ID specified in the parameters must be different for each region, and
if VTAM interface is used, a different RMOAPPL= name will be needed for each region.

Interface Parameter Requirements

This table lists the optional and required parameters for each interface.

Note: The numbers next to the interface values refer to note references.

Parameter VTAM TSO TSO/ISPF CA Roscoe CICS IMS/DC

CANCEL Opt. (1) Opt. (1) Opt. (1) Opt. (1) Opt. (1) Opt. (1)

LGNFMT Opt. (2)

LGNSEC Opt. (3) Opt. (3) Opt. (3) Opt. (3) Opt. (3) Opt. (3)

LGNPROP Opt. (3) Opt. (3) Opt. (3) Opt. (3) Opt. (3) Opt. (3)
LONGWAIT Opt. (1) Opt. (1) Opt. (1) Opt. (1) Opt. (1) Opt. (1)
MSGLVL Opt. Opt. Opt. Opt. Opt. Opt.
RMOAPPL Req.
RMOVTDB Opt. (4)
SMFSESS Opt. (5) Opt. (5) Opt. (5) Opt. (5) Opt. (5) Opt. (5)
SUBSYS Opt. (6) Opt. (6) Opt. (6) Opt. (6) Opt. (6) Opt. (6)
USERMAX Req. Req. Req. Req. Req. Req.
VTAMPASS Opt. (7)
VTAMSAA Opt. (8)
VTMQUERY Opt. (9)

158 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Parameter VTAM TSO TSO/ISPF CA Roscoe CICS IMS/DC

XMS Opt. Opt. Opt. (10) Opt. (10) Opt. Opt. (10)
(10) (10) (10)
XMSSUB Req. Req. (11) Req. (11) Req. (11)
(11)

Notes for the Interface Parameter Requirements Table

1. The CANCEL= and LONGWAIT= values work together.
We recommend that you set CANCEL=YES and set LONGWAIT to a value
appropriate for your site.
2. LGNFMT= should either not be specified, or it is to be specified as the default
(LGNFMT=1), unless your session manager cannot provide logon data in the normal
format.
If RMOVTDB= is specified, LGNFMT=1 must be specified; any VTAM logon data will
be ignored.
3. The LGNSEC= and LGNPROP= work together, and require the default RMOUSxUX
exit.
If LGNSEC=YES or LGNSEC=YESP is used (to indicate external security signon), the
LGNPROP=YES/NO will be used to control whether security violations, database
opens and jobs submitted will use the user ID (LGNPROP=YES which is the default)
or will use the XMS region's user ID.
It works as follows:
– In the online region, the CA Deliver database is opened before logon, and uses
the XMS region's user ID.
4. The RMOVTDB= only affects VTAM access, and is only to be used when the session
manager cannot produce valid LOGON DATA.
For the valid formats supported by CA Deliver, see the LGNFMT= parameter.
5. The SMFSESS= is to be specified when the user needs to collect user session
statistics (CPU, logon/LOGOFF times, storage used, and so on).
6. The SUBSYS= is only to be specified when you are using a non-default subsystem ID
under MVS.
The default is release specific; it does not require JCL/PARM changes when you are
converting to a new software release.
7. VTAMPASS= is only to be specified if you are going to be running a multi-region
VTAM interface.
The other VTAM regions must specify the same parameters (LGNFMT= RMOVDTB=,
VTMQUERY=, VTAMSAA=), or the interface might react in unpredictable ways.

Chapter 10: Installing Online Interfaces 159

How to Configure the Online Interfaces Without CA MSM

8. VTMQUERY= is to be specified either as NORM (normal) or allowed to default to

that value.
VTMQUERY=NONE works, but CA Deliver cannot detect color/high-light terminal
attributes so color/high-light support will be shut off.
VTAMSAA=NO is to be used if terminals cannot support the SNA QUERY LIST
command, such as the older 3270/3290 devices and some older PC/3270
emulators.
9. XMS=NO is to be used when you are going to be using only the VTAM interface.
10. XMS=YES (the default) must be used to provide support for these interfaces.
11. XMSSUB=YES must be specified to provide support for these interfaces.
The XMSSUB=YES must reside in an XMS region with a default SUBSYS= value. If
multiple XMS regions are started, only one region can have XMSSUB=YES. The other
regions will still be available for user sessions, but their traffic will be routed
through the region specifying XMSSUB=YES.
If you terminate the region with XMSSUB=YES, all sessions using the subtask are
goint to fail (that is, all TSO/XMS, ISPF/XMS, CA Roscoe/XMS, IMS/DC regions). CICS
has router SUBTASK in its region, and does not use the XMSSUB=YES function.
12. The OVERRIDE parameter is valid for all interfaces and is optional. It might be
specified only in the execute statement PARM field and it cannot be coded in the
SYSIN data set.
If the parameter is not coded, the default duplicate parameter substitution
hierarchy is SYSIN then the EXEC PARM.
– The OVERRIDE parameter determines whether parameters in the execute
statement PARM field have precedence over parameters in the SYSIN data set.
– If OVERRIDE is coded in the execute statement PARM field, parameters
specified in the execute statement PARM field will override duplicate
specifications in the SYSIN data set.
– If OVERRIDE is not coded, parameters specified in the SYSIN data set are used
and corresponding parameter specifications in the execute statement PARM
field are ignored.
– The OVERRIDE parameter does not have any sub-parameters and it is coded as
is in the execute statement PARM field.
– If this parameter is coded in the SYSIN data set, error message "EBCDRV99
OVERRIDE KEYWORD NOT ALLOWED IN SYSIN STATEMENTS - RUN ENDED
U0016" is going to be displayed in the XMS job log and XMS will terminate with
a return code of 16.

160 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Step 1: Add the Start Procedure for the Cross-Memory Online Task

Add this start-procedure JCL for the cross-memory online retrieval task as member
CBROSDRV to SYS1.PROCLIB. Sample JCL for this PROC is provided in member
CBROSDRV of CAI.CVDEPROC.

//CBROSDRV EXEC PGM=EC0DRV,REGION=1024K,TIME=1440,

// PARM=('XMSSYS01,RMOAPPL=RMOVTAM,USERMAX=30,VTAMPASS=YES')
//*
//STEPLIB DD DSN=&CAI.CVDELOAD,DISP=SHR
//*
//SYSPRINT DD SYSOUT=A <--MESSAGE LOG (NEW, OUTPUT REQUIRED WHEN SUBMITTING
//* DUMP TO CA TECH SUPPORT)
//*
//RMOLOG DD SYSOUT=A <--MESSAGE LOG (NEW, OUTPUT REQUIRED WHEN
//* SUBMITTING DUMP TO CA TECH
//* SUPPORT) ONLY USED WHEN XMSSUB=YES)
//*
//EBCUDUMP DD SYSOUT=A <--INTERNAL DUMP OUTPUT (NEW, OUTPUT REQUIRED WHEN
//* SUBMITTING DUMP TO CA TECH SUPPORT)
//*
//*
//SYSUDUMP DD SYSOUT=A <--MVS DUMP OUTPUT (OPTIONAL, MVS DUMP CAN BE ROUTED
//* WITH SYSMDUMP OR SYSABEND ALSO)
//* WARNING!!!! ABENDAID DUMPS ARE OF NO USE CORRECTING
//* PROBLEMS WITH RMOXMS. YOU MUST ALWAYS SUPPRESS
//* ABENDAID IF YOU HAVE IT INSTALLED FOR THIS REGION.
//*
//SYSIN DD DSN=CAI.CVDEOPTN (PARMXMS),DISP=SHR

SYSIN Statements for Parameters

The REGIONID parameter is positional and must be specified in the PARM= statement of
the cross-memory task JCL.

You can use SYSIN DD statements to specify the other cross-memory parameters.

If you are going to run multiple regions, specify these parameters in the PARM=
statement:

SUBSYS=
RMOAPPL=
XMS=

You can specify the rest of the parameters with SYSIN DD statements. If you place the
SYSIN statements in a PDS member, you can alter the parameters without shutting
down the cross-memory region. Be aware that the parameters do not take effect until
the next time the region is shut down and restarted.

Chapter 10: Installing Online Interfaces 161

How to Configure the Online Interfaces Without CA MSM

Note:
■ SYSIN parameters for cross-memory services must start in column #1. Any
parameter that does not begin in column #1 is treated as a comment and is ignored.
■ The OVERRIDE parameter cannot be coded in the SYSIN data set.
– If the OVERRIDE parameter is coded in the execute statement PARM field, a
duplicate parameter in the PARM field and the SYSIN data set will be set to the
value specified in the PARM field parameter.
– If the OVERRIDE parameter is not coded in the execute statement PARM field, a
duplicate parameter in the PARM field and the SYSIN dataset will be set to the
value specified in the SYSIN dataset parameter.

Start Procedure Parameters

XMSSYS01 (in the PARM statement) specifies the one- to eight-character REGIONID. The
REGIONID is positional—it must be the first value of the PARM= statement.

This value is used to define separate cross-memory regions attached to one MVS
subsystem (specified by the SUBSYS parameter).

Note: Each separate RMOXMS region has its own REGIONID. We suggest using the PROC
name of the cross-memory-started task.

162 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

CANCEL=YES|NO
Indicates one of the following:
■ CANCEL=YES specifies that a user who is inactive (no commands entered) for
the time specified by the LONGWAIT parameter will be canceled, and the
session will be terminated. With CANCEL=YES, all users will be automatically
canceled if the region is shut down by an operator command.
■ CANCEL=NO specifies that the connection is not canceled, and the user status
changes to LONGWAIT.
Default: NO
LGNFMT=n
Specifies the format of the data parameter when logging on to a VTAM region
where n is a digit (1 through 3), as follows:
1 database//userid/password/newpass
2 userID/password/newpass/database/mode
3 database/mode
Default: 1
LGNPROP=YES|NO
Indicates whether the CA Deliver user ID should be passed to MVS for propagation
during submit processing.
This parameter is only valid if LGNSEC=YES is specified.
Default: YES
LGNSEC=YES|NO|PASSWORD|YESP
Indicates whether there is to be RACROUTE security checking.
LGNSEC must be YES or YESP if you are accessing a database that has the CA Deliver
initialization parameter SECURITY=EXTERNAL specified.
Modifications to default logon exit (RMOUSXUX) is not required to implement
external security. This exit is only provided so that you can customize the exit to
provide any necessary functionality.
For example, to access external security packages directly, without SAF, you must
modify and install the RMOUSXUX user exit.
These values for LGNSEC are effective when the default exits are implemented:
Value
Result
YES
External security checking is performed using SAF calls.

Chapter 10: Installing Online Interfaces 163

How to Configure the Online Interfaces Without CA MSM

External security verifies userid only for all cross-memory interfaces (with no
interruption to the user).
A panel is presented to the user to verify userid and password.
Note: This panel is only presented when the user interface does not
automatically send the userid to the XMS region.
Because the password is not forwarded, RACF or CA ACF2R Security (eTrust
CA-ACF2) requires additional specifications. For RACF or CA ACF2, see
Bypassing Password Verification in the chapter "Security" in the Reference
Guide for implementation instructions.
NO
No SAF call to external security is performed.
The user ID is checked internally against CA Deliver definitions.
If no match is found, CA Deliver might or might not dynamically create a user ID
depending on the value of your DEFMODE initialization parameter.
Review your DEFMODE values to be sure that they are appropriate.
PASSWORD
No call to external security is performed.
Internally, user ID and password are verified.
YESP
External security checking is performed using SAF calls.
External security verifies userid and password for all cross-memory interfaces
(with no interruption to the user).
A panel is presented to the user to verify the userid and password. This panel is
only presented when the user interface does not automatically send the userid
and password to the XMS region.
Default: NO
LONGWAIT=nn
Specifies the number of minutes of inactivity (no commands entered) before a
user's session is terminated.
The CANCEL parameter must be YES to terminate the session.
Default: 15
MSGLVL=CRIT|ACTN|NORM|INFO|TRCE
Indicates the level of message to be written to the started task job log.
Unless they are suppressed, the CRITICAL and ACTION messages are written to the
console. These settings cause these types of messages to be displayed:

164 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

CRIT
Displays critical messages.
ACTN
Displays critical and action messages.
NORM
Displays critical, action, and normal messages.
Default: NORM
INFO
Displays all but trace messages.
TRCE
Displays all messages.
Note: This parameter does not suppress messages from the SYSPRINT log.
RMOAPPL=applname
Specifies the RMOVTAM APPLID which provides VTAM user signon capability.
Default: RMOVTAM.
RMOVTDB=high-level.databasename
Specifies that this database high-level qualifier must be used by all RMOVTAM
interface users.
Typically, you would not specify this value and allow the user to specify which
database to access when the user logs on. When this parameter is specified, any
database specified at logon time with the VTAM logon command is ignored.
SMFSESS=nnn
Specifies whether SMF records are to be collected for the cross-memory sessions.
The EBCSMFU1 macro documents the records available.
Default: zero—no record collection.
SUBSYS=name
Specifies the four-character MVS subsystem.
This must match the value in the EC0XMCTR table.
Default: XMC0
Note: The SUBSYS parameter does not apply to VTAM or IMS interface users.
USERMAX=nn
The maximum number of sessions to be allowed.
Default: 10

Chapter 10: Installing Online Interfaces 165

How to Configure the Online Interfaces Without CA MSM

VTAMPASS=YES|NO
Indicates whether signon requests can be passed to other regions in this subsystem
when this region cannot accept the request
Possible reasons for not being able to accept a signon request are that the
USERMAX parameter has been exceeded, or a SUSPEND operator command has
been issued.
If VTAMPASS=YES is specified, include PASS in the AUTH value on the APPL
statement in the VTAM definition. If you want to run multiple regions, VTAMPASS
must be YES.
Default: NO
VTMQUERY=ALL|NORM|NONE
Indicates whether the VTAM interface will QUERY terminals with dynamic log
modes to determine the alternate screen size.
Use this parameter only to query VTAM terminals that support SNA QUERY
commands and do not have an alternate screen size defined in their logmode.
ALL
Queries all terminals.
NORM
Queries the terminal if the bind image indicates it is a VTAM QUERY terminal,
and there is no alternate screen size defined.
NONE
Does not query any terminals (and color is not supported).
Default: NORM
VTAMSAA=YES|NO
Indicates whether all terminals are SAA compliant.
If you have the following:
– Older terminals that cannot support SAA (3290 terminals, for example
– These older terminals are going to be connecting with log modes that indicate
that CA View should query their alternate screen size
You must specify VTAMSAA=NO or these terminals are not able to log onto the
SARVTAM interface.
VTAMSAA=NO causes more overhead in logging on terminals than can be queried,
and is only to be used when required.
XMS=YES|NO
Indicates whether cross-memory users are to be allowed to sign on to the region.
Set XMS=NO if this is a VTAM only region, and cross-memory is not to be
supported.

166 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Note: If XMS=NO, there should be a VTAM ACB name coded in the SARAPPL=
parameter.
Default: YES
XMSSUB=YES|NO
XMSSUB=YES is required for ISPF cross-memory, TSO cross-memory, and CA Roscoe
cross-memory sessions.
All other interface users should set XMSSUB=NO.
Default: NO

RMOLOG DD Statement (Optional)

The optional RMOLOG DD statement is used to specify where to write the log of user
subtask messages.

This output is critical to resolving user subtask ABENDs, and is to be submitted to CA

Technical Support along with the region or task dump created with an ABEND.

SYSPRINT DD Statement (Optional)

The optional SYSPRINT DD statement is used to specify where to write the log of
cross-memory (RMOXMS) messages.

This output is critical to resolving RMOXMS ABENDs, and is to be submitted to CA

Technical Support along with the region or task dump created with an ABEND.

EBCUDUMP DD Statement

The EBCUDUMP DD statement is required, and is used to specify where to write a

special dump of CA Deliver control blocks that do not appear in normal MVS dump
output.

This output is critical to resolving RMOXMS ABENDs, and is to be submitted to CA

Technical Support along with the region or task dump created with an ABEND.

Chapter 10: Installing Online Interfaces 167

How to Configure the Online Interfaces Without CA MSM

Notes:
■ On ABEND Output, only regular MVS dump output should be collected. Output from
dump compression and analysis programs is not helpful to technical support—you
might be required to recreate the dump.
■ Acceptable types include SYSUDUMP, SYSMDUMP, or SYSABEND output, in
print-record format. IPCS/SVC dumps and CICS transaction or region dumps are also
acceptable, but must be formatted for printing before they are placed on the tape.
■ The RMOXMS region uses the operator facility to abort a user's task for various
problems. These problems might be a LONGWAIT time out, a VTAM I/O error, or a
detected internal error, which appear in the log followed by a U0522 ABEND of the
user subtask. No dump is generated.

STEPLIB for This Job

The action you take in this step depends on what you did during the base-product
installation. Specifically, did you:
■ Authorize the program load library or
■ Copy the modules to a system authorized library.

Be aware of the following before you run this job:

■ If the CA Deliver load modules were copied to an authorized library other than one
of the linklist libraries, you must change the data set name on the STEPLIB DD
statement.
■ If the load modules were copied to a linklist library, you must remove the STEPLIB
DD statement.
■ If you have CA View installed, you must consider these possibilities before you run
the job listed previouslyabove:If the CA Deliver load modules were copied to an
authorized library other than one of the linklist libraries, concatenate the CA Deliver
load library as a second STEPLIB after the CA View load library in the STEPLIB DD
statement.
■ If the load modules were copied to a linklist library, do nothing.

Step 2: Modify, Assemble, and Link the EC0XMCTR Module

The EC0XMCTR module defines the relationship between a transaction identifier and
the database, and session attributes. Also, the execution options for the cross-memory
subtask system are also defined in this module. All interfaces except VTAM require the
EC0XMCTR table.

168 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Be aware of the following:

■ You must assemble the EC0XMCTR table during installation to define the
relationship between CA View and CA Deliver database qualifiers, and the session
options to be used, and to provide information used to build the XMS database
table.
■ The table contains an EBCXMOPT macro to define initialization options and one
EBCXMTRN, RMOXMTRN, or INBXMTRN macro for each TSO user session. For all
users except VTAM, the transaction being used for each session must be defined in
an EBCXMTRN statement. Only the database high-level qualifier is used for VTAM
XMS users.
■ The transaction definition macros are searched by database name, and the first
match is used. If no entry is found in the EC0XMCTR table, the session is rejected.

A sample EBCXMCTR source program is in the CAI.CVDESRC library, which is unloaded as

part of CA Deliver's installation. The source is comprised of one or more assembler
macros.

Format of the Macros

The first statement defines the system options and has this format:

EBCXMOPT DESTID=dest,SRVTRAN=transaction,MSGLVL=level, X
DESTID=CICS-dest,LOGWAIT=timout-val, X
USERMAX=user-number,WAITCNT=maxcount

The next group of statements is for each transaction, database, or both to be accessed;
they have this format:

EBCXMTRN TRANID=tranid,INDEX=high-level-name,TIMEOUT=sec, X
SUBSYS=subsysid,RECON=yes|no, X
MSGSUPP=yes|no

The last statement generates the transaction table:

EBCXMTRN TYPE=GEN

Finally, an assembler END statement is needed to end the table:

END

Chapter 10: Installing Online Interfaces 169

How to Configure the Online Interfaces Without CA MSM

EBCXMOPT Statement Parameters

The following parameters are specified in the EBCXMOPT statement:

DESTID=dest
Specifies the transient data destination to which messages from the CICS subtask
are sent.
– Supply a DESTID to indicate that a queue (typically an extra partitioned queue
that points to a SYSOUT data definition name) is defined.
– Leave DESTID blank to specify that messages from the CICS subtask are not to
be captured.
XMC11=transaction
Specifies a four character transaction that is to be added to the EBCXMC11 timeout
message.
This transaction allows for site-specific tailoring of the timeout message.
Default: None
SRVTRAN=transaction
Specifies the transaction defined for EC0CISRV that is initiated as a service
transaction when CA Deliver CICS is initialized.
Default: XMC0
MSGLVL=CRIT|ACTN|NORM|INFO|TRCE
Indicates the level of messages to display on the console.
These settings cause the following types of messages to be written:
CRIT
Displays only critical messages.
ACTN
Displays only critical and action messages.
NORM
Displays only critical, action, and normal messages.
INFO
Displays all but trace messages.
TRCE
Displays all messages.
Default: NORM

170 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

LOGWAIT=nnn
Indicates the amount of time a user is to wait to log on before the user's session
times out.
Default: 200 seconds (2 minutes, 00 seconds)
SGNCNT=nn
Controls the number of logon control blocks allocated. These blocks are only used
during the logon process. They are then reused and made available to other users
attempting to log on.
When you increase the SGNCNT value, be aware that 256 bytes of ECSA are needed
each time SGNCNT is increased by 1. Typically, 5 logon blocks are enough, but the
value cannot exceed 50.
Default: 5
SUBMAX=nn
Indicates the total number of user control blocks that are allocated when a
cross-memory subtask (other than CICS) is initialized.
Default: 500
USERMAX=nn
Indicates the number of user control blocks that are allocated when CICS is
initialized.
Default: 500
WAITCNT=nnn
The number of sessions for which the subtask can wait.
Default: 256
IMSMENU
The IMS/DC conversational menu to transfer to when CA Deliver terminates.
If this value is not specified, the transaction in the SPA is set to blanks.
IMSSPA
The size of the IMS/DC SPA.
The SPA size must be at least 18, but cannot exceed 100.
Default: 18

Chapter 10: Installing Online Interfaces 171

How to Configure the Online Interfaces Without CA MSM

EBCXMTRN Statement Parameters

The following parameters are specified in the EBCXMTRN statements:

TYPE=EXPRESS|GEN
Specifies whether this is a transaction/database entry or the table is to be
generated.
GEN
Generates the table.
EXPRESS
Contains a transaction code and index entry for CA Deliver. SAR and INB are
valid for CA Viewr and CA Balancing Report Control (CA Balancing) if this is a
combined table.
TRANID=tranid
Defines the transaction identifier for CICS.
For TSO, ISPF, and CA Roscoe (the cross-memory drivers), TRANID is ignored, and
the first instance of the database high-level qualifier is used.
INDEX=high-level-name
Defines the high-level name of the database.
TIMEOUT=nnn
Defines the time out value, in seconds, to be used by this transaction.
– This value is used as the maximum wait time for a response from the RMOXMS
started task.
– This value must be greater than zero and less than 9999 seconds (which is two
hours, 40 minutes).
– If you do not want any timeout to occur, specify TIMEOUT=NO.
Default: 240 seconds (four minutes)
SUBSYS=subsys-id
Defines a four-character MVS subsystem name which must match the value
specified for SUBSYS in the cross-memory started task JCL.
Each subsystem can support multiple databases and/or CICS/IMS regions.
Default: XMC0
Note:
■ There is no need to change the default unless you wish to bring up multiple
cross-memory regions and separate transactions for testing or performance
reasons.
■ This subsystem name is not defined in SYS1.PARMLIB.

172 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

RECON=YES|NO
Indicates whether a user can reconnect to a lost session.
Default: NO.
MSGSUPP=YES|NO
Indicates whether a termination message is displayed when a session is terminated
by a user.
Default: NO. This does not suppress messages generated from abnormal
termination.

Note: The statements follow standard assembler coding conventions.

Macro Coding Example

Assume that two CA Deliver systems have been created.

The databases for the two systems have high-level names of RMO.SYSTEM1 and
RMO.SYSTEM2. A user must enter transaction identifier RM1 for the first system and
RM2 for the second.

The source for program EC0XMCTR contains these control statements:

EBCXMOPT MSGLVL=CRIT,USERMAX=50
EBCXMTRN TRANID=RM1,INDEX=RMO.SYSTEM1
EBCXMTRN TRANID=RM2,INDEX=RMO.SYSTEM2
EBCXMTRN TYPE=GEN
END

EBCXMTRN TYPE=GEN must be the last statement before the END. This statement
causes the EBCXMCTR CSECT to be generated.

Sample JCL

Sample JCL for this job is provided in member BROSXCTR of CAI.CVDEJCL.

This job provides an SMP/E USERMOD which assembles and links an

installation-dependent version of EC0XMCTR.

Chapter 10: Installing Online Interfaces 173

How to Configure the Online Interfaces Without CA MSM

Parameters for Online Interfaces

The EC0XMCTR table defines the way linkages between the online drivers and the XMS
region are established. Some of the parameters are used only in specific environments
and others are used in all environments.

This table indicates which parameter affects each online interface.

All XMS interfaces require the EC0XMCTR table.

You must:
■ Assemble the table during installation to define the relationship between CA View
and CA Deliver database high-level qualifiers and the session options that are to be
used
■ Provide the information that is used to build the XMS database table.
Note: Be aware if both CA View and CA Deliver are installed and the CA View
interface is doing any access to an associated DLVR database, the associated DLVR
database needs to be added as an entry in the EC0XMCTR table

Only the database high-level qualifier is used for VTAM XMS users.

The numbers in parentheses are explained in the notes section that follows the table.

Parameter TSO TSO/ISPF CA Roscoe CICS IMS/DC

DESTID Opt. (1)
XMC11 Opt. (8)
SRVTRAN Opt. (2)
MSGLVL Opt. Opt. Opt. Opt. Opt.
LOGWAIT Opt. Opt. Opt. Opt. Opt.
SUBMAX Opt. (3) Opt. (3) Opt. (3) Opt. (3)
USERMAX Opt. (4)
WAITCNT Opt. (5) Opt. (5) Opt. (5) Opt. (5) Opt. (5)
IMSMENU Opt. (6)
IMSSPA Opt. (7)

Note: The numbers next to the table values refer to note references.

174 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Notes for the Online Interface Parameters

Follow these steps:

1. DESTID= specifies an optional CICS destination to which message output is to be
written.
2. SRVTRAN= specifies the service transaction ID.
This transaction is required for CICS, but you can use the default service transaction
name XMC0.
3. SUBMAX= controls the maximum connections that can be managed by the subtask
program.
The default is 500, which should be changed for most users. Each ISPF/XMS,
TSO/XMS, CA Roscoe/XMS, or IMS/DC user connects through the XMS subtask and
the value defines the total number of users that can be connected from these
interfaces at one time.
4. USERMAX= controls the maximum connections that can be managed by the subtask
program.
The default is 500. Each CICS region can manage this number of sessions. To
increase the value, you must restart the CICS or XMS region that owns the subtask.
5. WAITCNT= specifies a value that should remain at the default value at this time.
Major performance problems occur if you set this to a lower value. Note that this
value cannot be set above 255.
6. IMSMENU= specifies the IMS/DC conversational menu to transfer to when CA
Deliver ends. If this value is not specified, the SPA TRAN is set to blank upon
termination.
7. IMSSPA= specifies the length of the IMS/DC spa to be used (IMS/DC only).
This parameter allows the spa size to be adjusted so that CA Deliver can transfer to
user transactions.
IMS/DC requires the spa size to remain the same. The spa size must be at least 18
bytes, and although you can specify a spa size of up to 100 bytes, only the first 18
bytes are used.
8. XMC11= specifies an optional 4-character CICS transaction ID that is displayed as
part of message EBCXMC11 when a CICS user times out.

Step 3: Define Security Requirements

Follow these steps to define security requirements for CA Top Secret Security (eTrust
CA Top Secret):
1. Rename the existing facility in the facility matrix table if you do not have a facility
defined for RMOXMS:
user1=NAME=RMOXMS

Chapter 10: Installing Online Interfaces 175

How to Configure the Online Interfaces Without CA MSM

Be sure that the correct PGMname is defined for the new facility, where PGMname
is either the first three characters or all the eight characters of the program name
that is to make security calls (EC0 or EC0DRV).
2. Create region ACID for the facility:
TSS CRE(rmoxms) pass(nopw,0) type(user) dept(dept)
mastfac(rmoxms) NODSNCHK NORESCHK NOVOLCHK NOLCFCHK NOSUBCHK

3. Define the RMOXMS STC to the TSS STC record:

TSS ADDTO(STC) PROCNAME(rmoxms) ACID(rmoxms)

4. Give access to the ACIDs required to sign on to this facility:

TSS ADD(ACID) FAC(rmoxms)

Install the ISPF/Cross-Memory Online Retrieval Option

The ISPF/Cross-Memory Online Retrieval Option runs under IBM's ISPF for z/OS Version
3.0 and higher.

Important! This interface requires Cross-memory services to be already installed. For

more information, see Install Cross-Memory Services in this chapter.

Note: In the JCL for the cross-memory services task, the parameter XMSSUB must be set
to YES.

Installation Steps

The following steps are required to install the ISPF/cross-memory online retrieval
option. Each step is explained in detail later in the sections that follow.
1. (Optional) Add STEPLIB DD Statements to the TSO LOGON procedures if the load
modules were not copied to a linklist library.
2. Add the panel and command table libraries to the TSO logon procedures. (For ISPF
only, not for SPF.)
3. (Optional) Modify an ISPF selection menu to select the online retrieval feature.

Step 1: (Optional) Add STEPLIB DD Statements to the TSO LOGON Procedures

The action you take in this step depends on what you did during the base-product
installation—specifically, did you:
■ Authorize the program load library, or
■ Copy the modules to a system authorized library.

176 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

If the CA Deliver load modules were not copied to one of the libraries in the linklist,
proceed with this step; otherwise go to the next step.

For this interface, the libraries do not have to be APF authorized. Authorization is
provided in the cross-memory installation. Multiple versions of this online interface can
coexist in one TSO library concatenation.

Do one of the following:

■ Add a STEPLIB DD statement for the library that contains the load modules to the
LOGON procedures for those TSO users who are going to use the
ISPF/cross-memory online retrieval option.
■ Provide the load library using the ISPF LIBDEF facility.

Note: If multiple versions of CA Deliver are going to be running simultaneously, or you

want to also run a previous version of RMOSPF or RMOTSO, concatenate the load library
you want RMOSPF or RMOTSO to use first.

More information:

Step 6: Modify the Skeleton JCL (see page 96)

Step 2: Add Panel and Command Table Libraries to TSO LOGON

If you are going to run CA Deliver under ISPF, proceed with this step. For Version 3 or
higher, both the command table library and the panel library are used.

To add panel and command table libraries to the TSO LOGON procedure:
1. Concatenate the command table library CAI.CVDETBL0 to DD statement ISPTLIB.
2. Concatenate the panel library CAI.CVDEPNL0 to DD statement ISPPLIB.

Note: If you also plan to use RMOSPF (the ISPF interface), and multiple versions of CA
Deliver, concatenate CAI.CVDETBL0 first. Use the CAI.CVDETBL0 from the most current
release.

Step 3: (Optional) Modify an ISPF Selection Menu to Select Online Retrieval

If you want to add a selection code to one of the ISPF selection menus for the online
retrieval feature, proceed with this step; otherwise, your ISPF detailed instructions are
complete.

Chapter 10: Installing Online Interfaces 177

How to Configure the Online Interfaces Without CA MSM

Note: If you add a selection code, you are able to select the online retrieval feature in
the same way you select other ISPF options.

Use the value next to the NAME parameter on your Initialization Parameter Worksheet
for PARM (high-level database name).

Use the values in this table for either SPF or ISPF.

Type Selection Code is Defined As

ISPF (all versions) 'PGM(EC0XMSPF) PARM(high-level-database-name)
NEWAPPL(RMO)'
SPF 'PGM(EC0XMSPF) PARM(high-level-database-name)'

Panel Libraries

The names of the panel libraries vary from site to site and for the different releases of
ISPF. These panel libraries are allocated to the ISPPLIB DD statement under TSO.

Be aware that some installations do not allow direct modifications of IBM panels and
libraries. In this case, you can place the modified panels in user or site-specific libraries
and concatenate them ahead of the IBM libraries.

Ask your system administrator for the specific ISPF panel library that applies to your site
and contains the panel ISR@PRIM.

Note: The selection menus shown in these examples are part of the program product
ISPF and are copyrighted by IBM.

178 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Example 1

This example shows you how to add selection code R to the primary option menu
ISR@PRIM for ISPF. The bright, offset text identifies the inserted lines.

----------------------- ISPF/PDF PRIMARY OPTION MENU --------------------

%OPTION ===>_ZCMD +
% +USERID - &ZUSER
% 0 +ISPF PARMS - SPECIFY TERMINAL AND USER PARAMETERS +TIME - &ZTIME
% 1 +BROWSE - DISPLAY SOURCE DATA OR OUTPUT LISTINGS +TERMINAL - &ZTERM
% 2 +EDIT - CREATE OR CHANGE SOURCE DATA +PF KEYS - &ZKEYS
% 3 +UTILITIES - PERFORM UTILITY FUNCTIONS
% 4 +FOREGROUND - INVOKE LANGUAGE PROCESSORS IN FOREGROUND
% 5 +BATCH - SUBMIT JOB FOR LANGUAGE PROCESSING
% 6 +COMMAND - ENTER TSO COMMAND, CLIST, OR REXX EXEC
% 7 +DIALOG TEST - PERFORM DIALOG TESTING
% 8 +LM UTILITIES- PERFORM LIBRARY ADMINISTRATOR UTILITY FUNCTIONS
% C +CHANGES - DISPLAY SUMMARY OF CHANGES FOR THIS RELEASE
% R +RMOSPF - DELIVER ADMINISTRATION
% T +TUTORIAL - DISPLAY INFORMATION ABOUT ISPF/PDF
% X +EXIT - TERMINATE ISPF USING LOG AND LIST DEFAULTS
%
+ENTER%END+COMMAND TO TERMINATE ISPF.
)INIT
.HELP = ISR00003
&ZPRIM = YES /* ALWAYS A PRIMARY OPTION MENU */
&ZHTOP = ISR00003 /* TUTORIAL TABLE OF CONTENTS */
&ZHINDEX = ISR91000 /* TUTORIAL INDEX - 1ST PAGE */
)PROC
&ZSEL = TRANS( TRUNC (&ZCMD,'.')
0,'PANEL(ISPOPTA)'
1,'PGM(ISRBRO) PARM(ISRBRO01)'
2,'PGM(ISREDIT) PARM(P,ISREDM01)'
3,'PANEL(ISRUTIL)'
4,'PANEL(ISRFPA)'
5,'PGM(ISRJB1) PARM(ISRJPA) NOCHECK'
6,'PGM(ISRPTC)'
7,'PGM(ISPYXDR) PARM(ISR) NOCHECK'
8,'PANEL(ISRLPRIM)'
C,'PGM(ISPTUTOR) PARM(ISR00005)'
R,'PGM(EC0XMSPF) PARM(RMO.SYSTEM1) NEWAPPL(RMO)'
T,'PGM(ISPTUTOR) PARM(ISR00000)'
' ',' '
X,'EXIT'
*,'?' )
&ZTRAIL = .TRAIL
)END

Chapter 10: Installing Online Interfaces 179

How to Configure the Online Interfaces Without CA MSM

Note:
■ NEWAPPL(RMO) is required and must be specified as shown previously in this
section.
This parameter is used with the command table library concatenation from Step 3
of the ISPF Installation Instructions.
■ NEWAPPL(RMO) allows CA Deliver to correctly interpret commands and program
function key invocation.
If this parameter is not specified, certain PF keys such as the scroll keys may not
function.

180 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Example 2

This example shows you how to add selection code R to the primary option menu
ISP@PRIM for SPF. Shading identifies the inserted lines.
%----------------------- SPF–MVS PRIMARY OPTION MENU ---------------
%OPTION ===>_OPT
% +USERID -
% 0 +ISPF PARMS - SPECIFY TERMINAL AND USER PARAMETERS +TIME -
% 1 +BROWSE - DISPLAY SOURCE DATA OR OUTPUT LISTINGS +TERMINAL –
% 2 +EDIT - CREATE OR CHANGE SOURCE DATA +PF KEYS -
% 3 +UTILITIES - PERFORM SPF UTILITY FUNCTIONS
% 4 +FOREGROUND - COMPILE, ASSEMBLE, OR DEBUG
% 5 +BACKGROUND - COMPILE, ASSEMBLE, OR LINK EDIT
% 6 +COMMAND - ENTER TSO COMMAND OR CLIST
% 7 +SUPPORT - TEST DIALOG OR CONVERT MENU/MESSAGE FORMATS
% 8 +LM UTILITIES- PERFORM LIBRARY ADMINISTRATOR UTILITY FUNCTIONS
% R +RMOSPF - DELIVER ADMINISTRATION
% T +TUTORIAL - DISPLAY INFORMATION ABOUT SPF
% X +EXIT - TERMINATE SPF USING LIST/LOG DEFAULTS
%
+PRESS%END KEY TO TERMINATE SPF+
%
)INIT
.HELP = TTUTOR
&ZHTOP = TTUTOR /* TUTORIAL TABLE OF CONTENTS */
&ZHINDEX = TINDEX /* TUTORIAL INDEX - 1ST PAGE */
)PROC
&ZSEL = TRANS( TRUNC (&OPT,'.')
0,'PANEL(ISPOPT)'
1,'PGM(ISRBRO)'
2,'PGM(ISPEDIT)'
3,'PANEL(ISPUTIL)'
4,'PANEL(ISPFORA)'
5,'PANEL(ISRJOB)'
6,'PGM(ISPTSO)'
7,'PANEL(ISPOTAC)'
R,'PGM(EC0XMSPF) PARM(RMO.SYSTEM1)'
T,'PGM(ISPTUTOR) PARM(T)'
' ',' '
X,'EXIT'
*,'?' )
)END

Example 3

This example shows you how to add selection code 3.R as a sub-option to the utilities
menu ISPUTIL for ISPF.

Chapter 10: Installing Online Interfaces 181

How to Configure the Online Interfaces Without CA MSM

The bright, offset text identifies the inserted lines.

%----------------------- UTILITY SELECTION MENU -----------------

%OPTION ===>_OPT +
% +
% 1 +LIBRARY LIBRARY UTILITY:
+ PRINT INDEX LISTING OR ENTIRE DATASET
+ PRINT, RENAME, DELETE, OR BROWSE MEMBERS
+ COMPRESS DATASET
% 2 +DATASET DATASET UTILITY:
+ DISPLAY DATASET INFORMATION
+ ALLOCATE, RENAME, OR DELETE ENTIRE DATASET
+ CATALOG OR UNCATALOG DATASET
% 3 +MOVE/COPY MOVE OR COPY MEMBERS OR DATASETS
% 4 +CATALOG CATALOG MANAGEMENT:
+ DISPLAY OR PRINT CATALOG ENTRIES
+ INITIALIZE OR DELETE USER CATALOG ALIAS
% 5 +RESET RESET STATISTICS FOR MEMBERS OF ISPF LIBRARY
% 6 +HARDCOPY INITIATE HARDCOPY OUTPUT
% 7 +VTOC DISPLAY OR PRINT VTOC ENTRIES FOR A DASD VOLUME
% 8 +OUTLIST DISPLAY, DELETE, OR PRINT HELD JOB OUTPUT
% 9 +SCRIPT/VS FORMAT, DISPLAY, AND OPTIONALLY PRINT SCRIPT TEXT
% R +RMOSPF DELIVER ADMINISTRATION
)INIT
.HELP = TU
)PROC
&SEL = TRANS( TRUNC (&OPT,'.')
1,'PGM(ISPUDA) PARM(UDA1)'
2,'PGM(ISPUDA) PARM(UDA1)'
3,'PGM(ISPUMC)'
4,'PGM(ISPUCA)'
5,'PGM(ISPURS)'
6,'PGM(ISPUHC)'
7,'PGM(ISPUVT)'
8,'PGM(ISPUOL) PARM(UOL01)'
9,'PGM(ISPUSC) PARM(SCRPTA)'
R,'PGM(EC0XMSPF) PARM(RMO.SYSTEM1) NEWAPPL(RMO)'
' ',' '
*,'?' )
)END

182 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

ISPF Cross-Memory Notes

Be aware of the following:

■ The primary RMOXMS region must be started with the XMSSUB=YES parameter.
■ The XMSSUB=YES parameter must only be used in an XMS address space with a
default subsystem ID (SUBSYS=XMC0 or not specified).
■ If multiple RMOXMS regions are started, they must be started with XMSSUB=NO
parameter.
Only the primary XMS region can have XMSSUB=YES specified.
■ The XMS regions must have the XMS=YES parameter to make it accessible.
■ The EBCXMCTR table must be assembled during installation to define the
relationship between CA Deliver and CA View database high-level qualifiers. The
table contains an EBCXMOPT macro to define initialization options and the
EBCXMTRN macro for each CICS user transaction.

The EBCXMTRN macro also contains options for the specific database as follows:
■ SUBSYS= parameter of the cross-memory task must match the SUBSYS= parameter
specified in the EBCXMCTR table entry.
■ RECON=YES can be used to allow reconnection (after an ISPF terminal error) at the
point of exit.
■ TIMEOUT= specifies how long ISPF will wait for the XMS session to respond after
the user enters input, in seconds.
We recommend as high a value as possible but not less than 240 (4 minutes).

To abort the XMS session and return the user to ISPF or the TSO command prompt,
press the ATTN key.

Note: The SUBMAX= parameter controls the number of user connections, not the
USERMAX= parameter. USERMAX= only applies when you are using the subtask with the
CICS interface.

Install the TSO/Cross-Memory Online Retrieval Option

Important! This interface requires cross-memory services to be installed. For more
information, see the topic Installing Cross-Memory Services in this chapter.

Note: The parameter XMSSUB must be set to YES in the JCL for the cross-memory
services task.

Chapter 10: Installing Online Interfaces 183

How to Configure the Online Interfaces Without CA MSM

Installation Steps

The following steps are required to install the TSO/Cross-Memory Online Retrieval
Option. Each step is explained in detail in the sections that follow.
1. (Optional) Add STEPLIB DD Statements to the TSO LOGON procedures if the load
modules were not copied to a linklist library.
2. (Optional) Set Up the TSOXMS Driver Program.

Step 1: (Optional) Add STEPLIB DD Statements

The action you take in this step depends on what you did during the base-product
installation—specifically, did you:
■ Authorize the program load library or
■ Copy the modules to a system authorized library

If the CA Deliver load modules were not copied to one of the libraries in the linklist,
proceed with this step; otherwise go to the next step.

To add STEPLIB DD statements (for the library containing the CA Deliver load modules)
to the TSO LOGON procedures, do the following:
■ Add a STEPLIB DD statement for the library that contains the CA Deliver load
modules to the LOGON procedures for those TSO users who are to use the
ISPF/Cross-Memory Online Retrieval Option.

Note: For this interface, the libraries do not have to be APF authorized—authorization is
provided in the cross-memory installation. Multiple releases of this online interface can
coexist in one TSO library concatenation.

Step 2: (Optional) Set up the TSOXMS Driver Program

To create user CLISTs to execute the CA Deliver TSOXMS driver program, issue:

EC0XMTSO highlevel.databasename

184 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

TSO Cross-Memory Notes

Be aware of the following:

■ The primary RMOXMS region should be started with the XMSSUB=YES parameter.
■ The XMSSUB=YES parameter must only be used in an XMS address space with a
default subsystem ID (SUBSYS=XMC0 or not specified).
■ If multiple RMOXMS regions are started, they must be started with XMSSUB=NO
parameter.
Only the primary XMS region can have XMSSUB=YES specified.
■ The XMS regions must have the XMS=YES parameter to make it accessible.
■ The EBCXMCTR table must be assembled during installation to define the
relationship between CA View and CA Deliver database high-level qualifiers. The
table contains an EBCXMOPT macro to define initialization options and the
EBCXMTRN macro for each CICS user transaction.

The EBCXMTRN macro also contains options for the specific database as follows:
■ SUBSYS= parameter of the cross-memory task.
This parameter must match the SUBSYS= parameter specified in the EBCXMCTR
table entry.
■ RECON=YES can be used to allow reconnection (after a TSO terminal error) at the
point of exit.
■ TIMEOUT= specifies how long TSO will wait for the XMS session to respond after the
user enters input, in seconds.
We recommend as high a value as possible but not less than 240 (4 minutes).

To abort the XMS session and return the user to ISPF or the TSO command prompt,
press the ATTN key.

Note: The SUBMAX= parameter controls the number of user connections, not the
USERMAX= parameter. USERMAX=only applies when you are using the subtask with the
CICS interface.

Install the VTAM Online Retrieval Option

Important! This facility uses the cross-memory feature distributed with CA Deliver and
must be installed with that feature. For more information about cross-memory feature,
see the Install Cross-Memory Services section in this chapter.

Chapter 10: Installing Online Interfaces 185

How to Configure the Online Interfaces Without CA MSM

Installation Steps

The following steps are required to install the VTAM online retrieval option. Each step is
explained in detail in the sections that follow.
1. Define the Application Program to VTAM.
2. (Optional) Create a USS Table Definition.

Step 1: Define the Application Program to VTAM

Add this application program definition to SYS1.VTAMLST:

* SYS1.VTAMLST(rmomajor)
rmomajor VBUILD TYPE=APPL
rmovtam APPL ACBNAME=rmovtam,AUTH=(PASS,ACQ),EAS=nn

where:
rmomajor
Specifies the application program major node name.
Use the SYS1.VTAMLST member name. The member name must be unique and
must not be the same as the names on the APPL statement.
AUTH=(PASS,ACQ)
Is required when the cross-memory parameter VTAMPASS=YES is used to support
multiple cross-memory regions.
If VTAMPASS=NO, you can specify AUTH=(ACQ). For more information about the
VTAMPASS parameter, see the Add the Start Procedure for the Cross-Memory
Online Task step in this chapter.
EAS=nn
Specifies the approximate number of concurrent sessions.
rmovtam
Specifies the minor node name of the application program.
■ This name must be unique within the network domain; it is the APPLID
referenced in the USS definition table or LOGON command.
■ This name is also specified on the cross-memory RMOAPPL parameter.
■ If not specified, the network-unique name (the name of the APPL definition
statement) is used.

Step 2: (Optional) Create a USS Table Definition

To simplify the manner in which a user logs on to VTAM online retrieval, you can create
a USS definition table for CA Deliver.

186 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Example

Assume that two CA Deliver systems have been created. The databases for the two
systems have high-level names of RMO.SYSTEM1 and RMO.SYSTEM2, and you want a
user to simply enter one of the commands to log on to VTAM online retrieval for the
respective systems:

RMO1
RMO2

Create a USS definition table as follows:

USSTAB
*
* ENTRY FOR RMO1
*
USSCMD CMD=RMO1,REP=LOGON,FORMAT=PL1
USSPARM PARM=APPLID,DEFAULT=RMOVTAM
USSPARM PARM=LOGMODE
USSPARM PARM=DATA,DEFAULT=RMO.SYSTEM1
*
* ENTRY FOR RMO2
*
USSCMD CMD=RMO2,REP=LOGON,FORMAT=PL1
USSPARM PARM=APPLID,DEFAULT=RMOVTAM
USSPARM PARM=LOGMODE
USSPARM PARM=DATA,DEFAULT=RMO.SYSTEM2
USSEND

Chapter 10: Installing Online Interfaces 187

How to Configure the Online Interfaces Without CA MSM

VTAM Cross-Memory Notes

Be aware of the following:

■ For VTAM only regions, you can start the primary RMOXMS task with the
XMSSUB=NO parameter. However if this is not a VTAM only region, we recommend
that you start the primary RMOXMS region with the XMSSUB=YES parameter.
■ If multiple RMOXMS regions are started, they must be started with XMSSUB=NO
parameter.
Only the primary XMS region can have XMSSUB=YES specified.
■ VTAM only XMS regions can have the XMS=NO parameter to make it accessible.
■ All XMS interfaces require the EC0XMCTR table. You must assemble the table during
installation to:
– Define the relationship between CA Deliver and CA View database high-level
qualifiers and the session options to be used
– Provide information used to build the XMS database table. Only the database
high-level qualifier is used for VTAM XMS users.
■ Specify the RMOAPPL=applid parameter. This parameter provides VTAM user
signon capability.
Note: When you are using multiple VTAM XMS regions, each region must have a
unique applid.
■ To pass VTAM signon requests to other XMS regions, specify the VTAMPASS=YES
parameter.
■ When you are using multiple VTAM XMS regions, the values for LGNFMT=,
RMOVDTB=, VTMQUERY=, and VTMSAA= must be the same in each region.
Otherwise, the XMS interface may react in unpredictable ways.
■ To activate the VTAM generic resource support for your cross memory regions,
specify the VGRAPPL= parameter.
Note: For more information about VTAM generic resources, see the following topic.

VTAM Generic Resource Name

If the VGRAPPL parameter is specified in an EMAS complex, this parameter specifies a

common VTAM generic resource name for the entire EMAS complex.

Specifying the common VTAM generic resource name in the session request can initiate
VTAM cross memory sessions to any of the EMAS members.

When you are using the VTAM generic resource name, by default VTAM tries to request
a session with an EMAS member in the same MVS image.

If it is not possible to get the session that was requested, VTAM uses normal load
balancing when passing the session request to one of the active EMAS members.

188 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Install the CA Roscoe/Cross-Memory Online Retrieval Option

The CA Roscoe/cross-memory online retrieval option runs as a command processor
under ETSO/Roscoe.

Important! This interface requires cross-memory services to be installed. For more

information about cross-memory services, see the Install Cross-Memory Services section
in this chapter. Be sure to set the parameter XMSSUB to YES in the JCL for the
cross-memory services task.

Installation Steps

The following steps are required to install the CA Roscoe/Cross-Memory Online

Retrieval Option. Each step is explained in detail in the sections that follow.
1. (Optional) Concatenate the Load Module Library to the ETSOLIB DD statement, if
the load modules were not copied to a linklist library.
2. Add the control statement for the RMOROS command processor to the Eligible
Program List (EPL).
3. Invoke CA Roscoe/Cross-Memory Online Retrieval.

Step 1: (Optional) Concatenate the Load Module Library

If the load modules were not copied to a linklist library, concatenate the library that
contains the load modules to the ETSOLIB DD statement in the CA Roscoe startup JCL, .

Note: If you have CA View, the CA View load modules must also be either in the linklist
or in a ETSOLIB statement with this step.

Step 2: Add RMOROS Command Processor Statements

Important! This step is for CA Roscoe 6.0 and Higher.

Add these EPL control statements to member ETSOPGMS for the CA Roscoe user with
the RO prefix:

Column Contents
1–8 EC0XMROS
9 Blank
10–12 Number of users allowed to access CA Deliver at one time
13 Blank
14–17 CPU time slice (use 9999 to prevent premature termination)
18 Blank

Chapter 10: Installing Online Interfaces 189

How to Configure the Online Interfaces Without CA MSM

Column Contents
19–24 Maximum memory (in KB) below the 16 MB line
This memory is only for the cross-memory driver program (50 KB is
ample)
25 Blank
26–31 Maximum memory (in KB) below the line that CA Deliver can acquire at
one time
Use 999999 so that GETMAINs are not limited
32 Blank
33–38 Maximum memory (in KB) above the 16 MB line
This memory is only for the cross-memory driver program (50 KB is
ample)
39 Blank
40–45 Maximum memory (in KB) above the line that CA Deliver can acquire at
one time
Use 999999 so that GETMAINs are not limited
46 Blank
47–48 CP to call EC0XMROS as a TSO command processor
49 Y – Application authorized to issue MODESET SVC
50 Blank
51-52 CP to call EC0XMROS as a TSO command processor
53-255 Ignored

190 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

CA Roscoe Cross-Memory Notes

Be aware of the following:

■ Start the primary RMOXMS region with the XMSSUB=YES parameter.
The XMSSUB=YES parameter must only be used in an XMS address space with a
default subsystem ID (SUBSYS=XMC0 or not specified).
■ If multiple RMOXMS regions are started, they must be started with XMSSUB=NO
parameter.
Only the primary XMS region can have XMSSUB=YES specified.
■ The XMS regions must have the XMS=YES parameter to make it accessible.
■ The EBCXMCTR table must be assembled during installation to define the
relationship between CA View and CA Deliver database high-level qualifiers.
The table contains an EBCXMOPT macro to define initialization options and the
EBCXMTRN macro for each CICS user transaction.

The EBCXMTRN macro also contains options for the specific database as follows:
■ SUBSYS= parameter of the cross-memory task.
This parameter must match the SUBSYS= parameter specified in the EBCXMCTR
table entry.
■ RECON=YES can be used to allow reconnection (after a TSO terminal error) at the
point of exit.
■ TIMEOUT= specifies how long TSO is to wait for the XMS session to respond after
the user enters input, in seconds.
We recommend as high a value as possible but not less than 240 (4 minutes).

Note: The SUBMAX= parameter controls the number of user connections, not the
USERMAX= parameter. USERMAX=only applies when using the subtask with the CICS
interface.

Install the CICS Pseudo-Conversational Option

Important! This option uses the cross-memory feature distributed with CA Deliver and
must be installed with that feature. For more information about cross-memory, see
Install Cross-Memory Services.

Chapter 10: Installing Online Interfaces 191

How to Configure the Online Interfaces Without CA MSM

Installation Steps

The following steps are required to install the CICS Pseudo-Conversational Option. Each
step is explained in detail in the sections that follow.
1. Place the CA Deliver load libraries into DFHRPL and STEPLIB.
2. Code the PCT and PPT Table Entries to CICS.
3. (Optional) Prepare the interface to a user-written CICS menu system.

Step 1: Add Modules to DFHRPL and STEPLIB

The CA Deliver load library is required in the CICS DFHRPL and in the STEPLIB in the CICS
region.

Note: If the CAI.CVDELOAD load library is in the linklist, it does not have to be included
as a STEPLIB in the CICS region

Be sure that these modules are available in the DFHRPL concatenation of libraries.
1. EC0CICUX
2. EC0CIEND
3. EC0CINIT
4. EC0CISRV
5. EC0XMCIC
6. EC0Cversion-number
Where:
release-number represents the CICS release number.
– CTS 3.1 release number: 0640
– CTS 3.2 release number: 0650
– CTS 4.1 release number: 0660
– CTS 4.2 release number: 0670
– CTS 5.1 release number: 0680

You can copy the six modules to the DD statement DFHRPL in your CICS task. However,
we strongly recommend that you concatenate CAI.CVDELOAD to the DD statement
DFHRPL.

Note: Several CA Deliver modules are loaded (MVS load) from the CICS STEPLIB or
LINKLIST. Verify that the entire CA Deliver load library is defined in the CICS STEPLIB or is
included in the linklist.

192 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Step 2: Define Transaction and Programs to CICS

To access CA Deliver using CICS, define the required transactions and programs for the
CICS interface.

Use the sample jobs described to define:

■ Sample CA Deliver transaction: RMO1
■ CA Deliver service transaction: XMC0
■ Optional CA Deliver startup transaction: RMI
■ Optional CA Deliver shutdown transaction: RMX
■ CA Deliver CICS retrieval programs:
– EC0CICUX
– EC0XMCIC
– EC0CINIT
– EC0CIEND
– EC0CISRV
– EC0C0620
– EC0C0621
– EC0C0622
– EC0C0630
– EC0C0640
– EC0C0650
– EC0C0660
– EC0C0670
– EC0C0680
■ Optionally, define one or more site-specific transaction identifiers for the
pseudo-conversational program EC0XMCIC.

Note:
■ You must define a separate, unique transaction identifier for each CA Deliver
database you want to access under CICS.
■ The sample job is located in CVDEJCL member CICSDLVR.

Chapter 10: Installing Online Interfaces 193

How to Configure the Online Interfaces Without CA MSM

Sample Job to Define CA Deliver Transactions and Programs to CICS:

//EXAMPLE JOB .....
//*********************************************************************
//* SAMPLE CICS JCL TO DEFINE PROGRAMS AND SAMPLE TRANSACTIONS *
//* FOR CA DELIVER XMS INTERFACE *
//* *
//* NOTE: *
//* UPDATE PROCEDURE SUBSTITUTIONAL PARAMETERS FOR *
//* 'CICSLOAD' AND 'CICSCSD' ACCORDING TO SITE STANDARDS. *
//* *
//* MANUAL CHANGES ARE REQUIRED IN THIS JOB STREAM *
//* TO UPDATE SYSIN PORTIONS BEYOND THE CONTROL *
//* OF THE PROCEDURE'S SUBSTITUTIONAL PARAMETERS. *
//* *
//* EDIT GROUP(GGGGGG) WHERE GGGGGG IS THE CICS DEFINED GROUP *
//* FOR YOUR CA DELIVER CICS DEFINITIONS. *
//* *
//*********************************************************************

194 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

//*
//CICSXMS PROC CICSLOAD='CICS.SDFHLOAD',
// CICSCSD='CICS.DFHCSD'
//*********************************************************************
//* DEFINE SAMPLE Deliver TRANSACTION: RMO1 *
//* DEFINE SERVICE TRANSACTION: XMC0 *
//* DEFINE OPTIONAL STARTUP TRANSATION: RMI *
//* DEFINE OPTIONAL TERMINATE TRANSATION: RMX *
//* DEFINE CA DELIVER CICS RETRIEVAL PROGRAMS: *
//* EC0CICUX *
//* EC0XMCIC *
//* EC0CINIT *
//* EC0CISRV *
//* EC0CIEND *
//* EC0C0620 *
//* EC0C0621 *
//* EC0C0622 *
//* EC0C0630 *
//* EC0C0640 *
//* EC0C0650 *
//* EC0C0660 *
//* EC0C0680 *
//* *
//* ** OPTIONAL ** *
//* DEFINE YOUR SITE SPECIFIC Deliver TRANSACTION. USE THE DEFINE *
//* STATEMENTS FOR THE SAMPLE VW1 TRANSACTION AS YOUR MODEL. *
//* *
//* THE FOLLOWING PARAMETERS DEFINE VIEW TRANSACTION ID: RMOT *
//* *
//* DEFINE TRANS(RMOT) GROUP(GGGGGG) PROG(EC0XMCIC) *
//* TASKDATAL(ANY) TASKDATAK(CICS) *
//* *
//* WHERE GGGGGG IS THE CICS DEFINED GROUP FOR YOUR *
//* CA DELIVERCICS DEFINITIONS. *
//*********************************************************************
//STEP1 EXEC PGM=DFHCSDUP,REGION=1024K
//STEPLIB DD DSN=&CICSLOAD,DISP=SHR
//DFHCSD DD DSN=&CICSCSD,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//*
// PEND
//CICSXMS EXEC CICSXMS
//STEP1.SYSIN DD *

Chapter 10: Installing Online Interfaces 195

How to Configure the Online Interfaces Without CA MSM

DEFINE TRANS(RMO1) GROUP(GGGGGG) PROG(EC0XMCIC)

TASKDATAL(ANY) TASKDATAK(CICS)
DEFINE TRANS(XMC0) GROUP(GGGGGG) PROG(EC0CISRV)
TASKDATAL(ANY) TASKDATAK(CICS)
DEFINE TRANS(RMI) GROUP(GGGGGG) PROG(EC0CINIT)
TASKDATAL(ANY) TASKDATAK(CICS)
DEFINE TRANS(RMX) GROUP(GGGGGG) PROG(EC0CIEND)
TASKDATAL(ANY) TASKDATAK(CICS)
DEFINE PROG(EC0CICUX) GROUP(GGGGGG) LANGUAGE(ASSEMBLER)
DATALOCATION(ANY) EXECKEY(CICS)
DEFINE PROG(EC0XMCIC) GROUP(GGGGGG) LANGUAGE(ASSEMBLER)
DATALOCATION(ANY) EXECKEY(CICS)
DEFINE PROG(EC0CISRV) GROUP(GGGGGG) LANGUAGE(ASSEMBLER)
DATALOCATION(ANY) EXECKEY(CICS)
DEFINE PROG(EC0CINIT) GROUP(GGGGGG) LANGUAGE(ASSEMBLER)
DATALOCATION(ANY) EXECKEY(CICS)
DEFINE PROG(EC0CIEND) GROUP(GGGGGG) LANGUAGE(ASSEMBLER)
DATALOCATION(ANY) EXECKEY(CICS)
DEFINE PROG(EC0C0620) GROUP(GGGGGG) LANGUAGE(ASSEMBLER)
DATALOCATION(ANY) EXECKEY(CICS)
DEFINE PROG(EC0C0621) GROUP(GGGGGG) LANGUAGE(ASSEMBLER)
DATALOCATION(ANY) EXECKEY(CICS)
DEFINE PROG(EC0C0622) GROUP(GGGGGG) LANGUAGE(ASSEMBLER)
DATALOCATION(ANY) EXECKEY(CICS)
DEFINE PROG(EC0C0630) GROUP(GGGGGG) LANGUAGE(ASSEMBLER)
DATALOCATION(ANY) EXECKEY(CICS)
DEFINE PROG(EC0C0640) GROUP(GGGGGG) LANGUAGE(ASSEMBLER)
DATALOCATION(ANY) EXECKEY(CICS)
DEFINE PROG(EC0C0650) GROUP(GGGGGG) LANGUAGE(ASSEMBLER)
DATALOCATION(ANY) EXECKEY(CICS)
DEFINE PROG(EC0C0660) GROUP(GGGGGG) LANGUAGE(ASSEMBLER)
DATALOCATION(ANY) EXECKEY(CICS)
DEFINE PROG(EC0C0670) GROUP(GGGGGG) LANGUAGE(ASSEMBLER)
DATALOCATION(ANY) EXECKEY(CICS)
DEFINE PROG(EC0C0680) GROUP(GGGGGG) LANGUAGE(ASSEMBLER)
DATALOCATION(ANY) EXECKEY(CICS)
/*

CICS Resource Definition Online Storage Protection

If you have CICS storage protection activated, resource definition online settings are
required, as follows:
■ For all transactions:
TASKDATALOC=ANY
TASKDATAKEY=CICS

196 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

■ For all programs:

DATALOCATION=ANY
EXECKEY=CICS

PLT Start-up List

Add these table entries to the last phase of the PLT startup list to initialize the subtask
that is used for cross-memory access:

DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM
DFHPLT TYPE=ENTRY,PROGRAM=EC0CINIT

PLT Shutdown List

Add these table entries to the first phase of the PLT shutdown list to ensure that the
subtask that executes as part of the CA Deliver online facility correctly shuts down when
CICS shuts down:

DFHPLT TYPE=ENTRY,PROGRAM=EC0CIEND
DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM

Optional DCT Entries

Specify a value for the DESTID parameter in the EBCXMOPT macro in the EC0XMCTR
module and corresponding DCT entries. This value defines a transient data destination
for messages issued by the subtask.

Note: Specify a blank for DESTID to suppress the generation of informational messages
from the subtask.

The DCT entries for a DESTID of XMC0 are:

RMOLOG DFHDCT TYPE=SDSCI, FOR CICS MESSAGES AND SHUTDOWN

BLKSIZE=250, STATISTICS
BUFNO=1,
DSCNAME=RMOLOG,
RECFORM=VARUNBM,
RECSIZE=242,
TYPEFLE=OUTPUT
XMC0G DFHDCT TYPE=EXTRA,
DESTID=XMC0,
DSCNAME=RMOLOG

Step 3: (Optional) Invoke the System from a CICS Menu System

If you want to invoke CA Deliver from a user-written CICS menu system, then return to
that menu system when you exit from CA Deliver, do the following:

Chapter 10: Installing Online Interfaces 197

How to Configure the Online Interfaces Without CA MSM

Invoke CA Deliver from the menu system by using this CICS command:

EXEC CICS START TRANSID(DELIVER transaction-id)

TERMID(EIBTRMID)
FROM(data-area)
LENGTH(4)

where:
TRANSID(DELIVER transaction-id)
Specifies the CA Deliver transaction ID.
TERMID(EIBTRMID)
Specifies the terminal that a CA Deliver transaction will communicate with.
FROM (data-area)
Specifies the optional variable length character string.
The format of the data-area parameter is:
tran,
where:
tran
Specifies the return menu CICS transaction to be started when CA Deliver
finishes.
Note: None of the data-area parameters is required.
LENGTH (4)
Specifies the number of bytes in the data field being passed.

Note:

When CA Deliver receives control, it retrieves the four-byte return transaction ID and
saves it from iteration to iteration.

If the retrieve fails, CA Deliver retains the information that it was started directly from a
terminal, not a menu system.

When CA Deliver finishes processing, it determines whether it should return to a menu

system by starting the return transaction.

If there is a saved transaction ID, CA Deliver starts the return transaction before it exits
to CICS by issuing:
EXEC CICS START TRANSID(RETURN transaction-id)
TERMID(EIBTRMID)
NOCHECK

198 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

CICS Notes

The cross memory CICS access involves two different address spaces: the CICS address
spaces and the XMS address spaces.

CICS Address Spaces

The user's CICS transactions and the cross memory support subtask reside in the
address spaces.
■ If multiple CICS regions are used to access CA Deliver, each CICS region will have an
XMS support subtask.
■ If you are using CICS/MRO, CA Deliver normally runs in an AOR (application region).

XMS Address Spaces

Be aware of the following:

■ The primary RMOXMS region can be started with the XMSSUB=YES or XMSSUB=NO
parameter.
■ CICS has a router subtask in its region and does not require the XMSSUB=YES
function. However, we recommend that you start the primary XMS region with
XMSSUB=YES.
■ If multiple RMOXMS regions are started, they must be started with XMSSUB=NO
parameter.
Only the primary XMS region can have XMSSUB=YES specified.
■ The XMS regions must have the XMS=YES parameter to be accessible.
■ The SUBSYS= parameter must match the EC0XMCTR table entry for the CICS
transaction.
■ The EBCXMCTR table must be assembled during installation to define the
relationship between CA View and CA Deliver database high-level qualifiers.
The table contains an EBCXMOPT macro to define initialization options and the
EBCXMTRN macro for each CICS user transaction.

The EBCXMTRN macro also contains options for the specific database as follows:
■ SUBSYS= parameter can be used to route the CA Deliver transaction to an alternate
XMS subsystem ID. The SUBSYS= of the cross memory task must match the SUBSYS=
parameter specified in the EBCXMCTR table entry.
■ TRANID=parameter specifies the CA Deliver transaction identifier for CICS.

Chapter 10: Installing Online Interfaces 199

How to Configure the Online Interfaces Without CA MSM

■ RECON=YES can be used to allow reconnection (after a CICS terminal error) at the
point of exit.
Note: Do not specify RECON=YES if you use a multi-session manager that assigns LU
names from a pool of names. Coding RECON=YES under these conditions could
allow a user to be connected to another user's session. For more information, see
Multi-Session Managers later in this chapter.
■ TIMEOUT= specifies how long CICS is to wait for the XMS session to respond after
the user enters input, in seconds.
We recommend as high a value as possible but not less than 240 (4 minutes).

CICS XMS Subtask Startup

Use one of these methods to start the XMS subtask automatically:

1. When the CICS region is started, use the DFHPLTPI definition to automatically start
the XMS subtask.
2. Define a transaction for the EC0CINIT program to allow for manual startup.
3. Write a CICS program to transfer control (XCTL) to EC0CINIT when you want to start
the XMS subtask.

Until the XMS subtask is started, expect the transactions referencing EC0XMCIC to
terminate with an error message that indicates that the XMS subtask is not active.

Note:
■ When the CICS region is terminated, the DFHPLTSD definition is to be used to
terminate the XMS subtask.
You can manually terminate the XMS subtask through a user application program
that LINKs the EC0CIEND or you can use the optional transaction defined for
EC0CIEND for manual termination.
■ If you want to terminate the XMS subtask manually, we recommend that you use
the DFHPLTSD entry to terminate the XMS subtask. This definition is needed to
clean up linkages to the XMS address spaces.
■ To prevent users from shutting down the XMS subtask, secure the optional
transaction for program EC0CIEND.

200 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Multi-Session Managers Using Virtual LU Names

Multi session manager products, for example CA TPX Session Management (CA TPX), can
be configured to assign an LU name to a user's terminal at the time the user selects the
CICS application.

Important! This assignment means that a user can enter CICS each time with a different
terminal ID which can cause problems for CA Deliver application.

For example: If a user uses a multi-session manager to end a session, or shuts the PC
down, CA Deliver does not know that the user has left. Another user might select CICS,
be assigned to the same LU name as the previous user, and enter CA Deliver with the
same terminal ID as the previous user. CA Deliver believes that there are two active
users on the same terminal.

To prevent this situation, you can add a small amount of code to the CICS Autoinstall
Control Program.

Note: The default name of this program is DFHZATDX and its source is located in
SDFHSAMP.

If you are not a CICS systems programmer, discuss this situation with the person in your
company who is responsible for CICS support and maintenance.

The sample code that follows shows how to clear an active user from the CA Deliver
application at terminal deletion time. Insert this code in your Autoinstall Control
Program.

The source that is shipped with CICS contains this line:

* ==> PUT DELETE CODE HERE

Insert the code after that line.

LOAD EP=EC0XSLOC,ERRET=RETURN
LR R6,R0 GET EBCXSLOC ADDRESS
ICM R8,B'1111',0(R6) ADDR OF MAIN CONTROL BLOCK
BZ RETURN GET OUT IF NONE
LA R7,4(,R8) LOOK LIKE FIRST USER BLOCK
XSU_LOOP DS 0H
ICM R7,B'1111',8(R7) USER BLOCK ADDR
BZ RETURN GET OUT IF DONE
CLC DELETE_TERM_ID,104(R7) FOR THIS TERMINAL?
BNE XSU_LOOP NO
TM 120(R7),X'01' ACTIVE ENTRY?
BZ XSU_LOOP NO
OI 120(R7),X'02' SHOW SESSION DONE
B RETURN EXIT PROGRAM

Chapter 10: Installing Online Interfaces 201

How to Configure the Online Interfaces Without CA MSM

This code does the following:

1. Attempts to load program EC0XSLOC
■ If the load fails, this is not the region containing CA Deliver and it exits.
■ If CA Deliver is active in this region, the first word of EC0XSLOC contains the
address of the main control block.
If this word is zero, CA Deliver is not active and the program exits.
2. Scans the chain of CA Deliver user control blocks to find the terminal to be deleted
■ If the program finds the terminal ID, it makes sure that the user block is in use
and is active, then it clears the appropriate fields.
■ If the block does not represent an active user, the program continues to search
the chain to the end.
■ If the program gets to the end of the chain without finding the terminal ID, the
program exits.
■ If you implement this change to the terminal deletion section of the Autoinstall
Control Program, you can prevent the problems caused by the methods that
were used to leave the CA Deliver application.

Install the IMS Online Retrieval Option

Use these steps to install the IMS online retrieval option.

Important! This facility uses the cross-memory feature distributed with CA Deliver and
must be installed with that feature. For more information about cross-memory, see
Installing Cross-Memory Services.

Installation Steps

This list summarizes the steps required to install the IMS Online Retrieval Option.
Detailed instructions are in the sections that follow.
1. Code the IMS TRANSACT, PSB and APPLCTN macros.
2. Run the PSB, ACB, and SYSGEN Procedures.
3. Load EC0IMSUX Modules.
4. Move load modules to IMSVS.PGMLIB.

Important! All JCL and macros provided in this section are provided as general examples
only and must be modified for your site's systems and standards.

202 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

Step 1: Code the Macros

Use the examples in this section as a guide as you code these macros, and implement
them in your IMS system.
■ (IMS) TRANSACT macro
■ PSB macros
■ APPLCTN macro

TRANSACT Macro

One or more transactions must be defined for the IMS online retrieval program
RMOXMIMS. Normally, only one transaction identifier is defined, although you can
define multiple transactions.

This TRANSACT macro identifies the RMOXMIMS transaction to IMS:

TRANSACT NAME=EC0XMIMS,SPA=(18)

PSB Macros

This PSB must be generated for the EC0XMIMS transaction:

PCB TYPE=TP,ALTRESP=YES,MODIFY=YES
PSBGEN PSBNAME=EC0XMIMS,LANG=ASSEM,COMPAT=YES

APPLCTN Macro

This APPLCTN must be generated for the RMOXMIMS transaction:

APPLCTN PSB=EC0XMIMS

Step 2: Run the PSB, ACB, and SYSGEN Procedures

Use the macros created in Step 1. Code the Macros as input for these procedures:

PSBGEN
ACBGEN
IMS SYSGEN

Step 3: Load EC0IMSUX Modules

Move load modules EC0IMSUX to IMSVS.PGMLIB.

Note: EC0IMSUX is in CAI.CVDELOAD and must be copied to IMSVS.PGMLIB.

Chapter 10: Installing Online Interfaces 203

How to Configure the Online Interfaces Without CA MSM

IMS Notes (New Version)

Be aware of the following:

■ The new IMS/DC Transaction Program (EC0XMIMS) is a replacement for the older
RMOXMIMS program.
■ The EC0XMIMS does not need to be linkedited to the ASMTDLI interface program.
The transaction is now conversational with a SPASIZE=18 (this can be adjusted).
■ If you use extended color, the SEGSIZE= may need to be increased, because
extended color data streams can be a 50% increase over the monochrome data
stream size.
To determine the SEGSIZE= value, take the terminal that will use the interface with
the largest screen size, in bytes, and apply this formula:

ROWS * COLS * 1.5 = SEGSIZE

For example, a 3278-5 with a 27 x 132 screen size would be (27 * 132 * 1.5) = 5346.
If the SEGSIZE= is too small, the terminal user will get an RC= "A6" message
indicating that a message insert failed.

IMS/DC Parameter Relationships

The cross-memory IMS/DC access involves up to three different address spaces as

follows:
■ IMS/DC message processing region address spaces
The user's IMS/DC transaction resides here. If multiple IMS/DC users are processing
concurrently (input being processed by the XMS system), a separate IMS/DC
message region is used for each user.
IMS/DC can control the maximum number of IMS/DC transactions executing at one
time.
■ The XMS support subtask
– The subtask is started when the XMSSUB=YES input parameter is used when an
XMS address space is started.
– The subtask can be in a separate XMS address space or share the address space
with XMS or VTAM sessions.
– The XMSSUB=YES must only be used in an XMS address space with a default
subsystem ID (SUBSYS=XMC0 or not specified).
– If multiple XMS address spaces are started, only one can have the XMSSUB=YES
specified.
Note: All IMS/DC, TSO/XMS, ISPF/XMS and CA Roscoe/XMS sessions share the same
XMS subtask.
■ XMS address spaces
See the topic that follows.

204 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

IMS/DC Cross-Memory Notes

Be aware of the following:

■ The primary RMOXMS region is to be started with the XMSSUB=YES parameter.
This region can be in a separate XMS address space or share the address space with
XMS or VTAM sessions.
■ The XMSSUB=YES parameter must only be used in an XMS address space with a
default subsystem ID (SUBSYS=XMC0 or not specified).
■ If multiple RMOXMS regions are started, they must be started with XMSSUB=NO
parameter.
Only the primary XMS region can have XMSSUB=YES specified.
■ The XMS regions must have the XMS=YES parameter to make it accessible.
■ The EBCXMCTR table must be assembled during installation to define the
relationship between CA View and CA Deliver database high-level qualifiers. The
table contains an EBCXMOPT macro to define initialization options and the
EBCXMTRN macro for each CICS user transaction.

The EBCXMTRN macro also contains options for the specific database:
■ SUBSYS= parameter of the cross-memory task.
The parameter must match the SUBSYS= parameter specified in the EBCXMCTR
table entry.
■ RECON=YES can be used to allow reconnection (after an ISPF terminal error) at the
point of exit.
■ TIMEOUT= specifies how long ISPF is to wait for the XMS session to respond after
the user enters input, in seconds.
We recommend a value as high as possible but not less than 240 (4 minutes).

To abort the XMS session and return the user to ISPF or the TSO command prompt,
press the ATTN key.

Note: The SUBMAX= parameter controls the number of user connections, not the
USERMAX= parameter. USERMAX=only applies when you are using the subtask with the
CICS interface.

To control screen size manually, use these operands. The SNA query command can also
be used to determine the device characteristics.

Enter For Terminal Type

M2 3278-2 24 x 80 default screen size
M2H 3278-2 24 x 80 highlighting

Chapter 10: Installing Online Interfaces 205

How to Configure the Online Interfaces Without CA MSM

Enter For Terminal Type

M2X 3279-2 24 x 80 color highlighting
M2C 3279-2 24 x 80 color
M3 3278-3 32 x 80
M3H 3278-3 32 x 80 highlighting
M3X 3279-3 32 x 80 color highlighting
M3C 3279-3 32 x 80 color
M4 3278-4 43 x 80 highlighting
M4H 3278-4 43 x 80 highlighting
M4X 3279-4 43 x 80 color highlighting
M4C 3279-4 43 x 80 color
M5 3278-5 27 x 132
M5H 3278-5 27 x 132 highlighting
M5X 3279-5 27 x 132 color highlighting
M5C 3279-5 27 x 132 color
M6 3290 62 x 80
M6H 3290 62 x 80 highlighting
M7 3290 31 x 160
M7H 3290 31 x 160 highlighting
M8 3290 62 x 160
M8 3290 62 x 160 highlighting

For other modifications to your system, see your VTAM programmer.

TSO, ISPF, CA Roscoe and Cross-Memory Address Spaces

TSO, ISPF, or CA Roscoe cross-memory access involves address spaces and subtasks as
follows:
■ TSO or CA Roscoe address spaces
The TSO command, ISPF, or CA Roscoe application program resides here. If
ISPF/XMS is being used with ISPF split-screen active, up to two sessions can be
executing at the same time, to the same database or different databases.

206 Installation Guide

 How to Configure the Online Interfaces Without CA MSM

■ The XMS support subtask

This subtask is started when XMSSUB=YES input parameter is used when starting an
XMS address space. The subtask can be in a separate XMS address space, or it can
share the address space with XMS or VTAM sessions.
– The XMSSUB=YES must only be used in an XMS address space with a default
subsystem ID (SUBSYS=XMC0 or not specified).
– If multiple XMS address spaces are started, only one can have the XMSSUB=YES
specified.
Note: All IMS/DC,TSO/XMS, ISPF/XMS, and CA Roscoe/XMS sessions share the same
XMS subtask.
■ XMS address spaces
The XMS regions must have the XMS=YES parameter to make them accessible.
Note: The SUBSYS= parameter must match the EC0XMCTR table entry for the
database.
Multiple address spaces can be used if needed.

Multiple Cross-Memory Region Requirements

Be aware of the folloing:
■ All cross-memory regions started under the same SUBSYS ID are chained together.
■ The REGIONID positional parameter is the first value of the PARM= statement for
the cross-memory task.
You must specify a different REGIONID for each started cross-memory region.
■ The value of the XMSSUB parameter for the primary region depends on the type of
XMS region you are defining.

See this table for the XMSSUB values. Specify XMSSUB=NO for all other started regions.

Primary Region Type XMSSUB Recommendation

Non-VTAM Must use XMSSUB=YES
CICS Recommend using XMSSUB=YES
VTAM-only XMSSUB=NO use allowed

Chapter 10: Installing Online Interfaces 207

Prepare to Start the Cross Memory Task

Note:
■ You must specify XMS=YES for all other started regions except for VTAM only
regions where XMS=NO is permissible.
■ Each VTAM cross-memory region requires a different applid. The applid is specified
using the RMOAPPL= parameter.
■ Each VTAM cross-memory region requires VTAMPASS=YES.
■ The VTAM administrator must verify that each VTAM cross-memory applid has this
setting:
AUTH=(PASS,ACO).

Prepare to Start the Cross Memory Task

Follow these steps:
1. (Optional) Add the start procedure to PROCLIB for the cross-memory online task.
2. (Optional) Modify, assemble, and link edit the EC0XMCTR module.
3. Define security requirements for CA Top Secret Security (eTrust CA-Top Secret).

Start the Cross Memory Task

Start the XMS CBROSDRV procedure.

208 Installation Guide

Chapter 11: Installing the Features
This chapter describes the CA Deliver features and provides information about how to:
1. Change the date format on panels
2. Set up the CA 11 interface
3. Set up CA 11 to run with CA Deliver
4. Install the CA GSS (Global Subsystem) interface
5. Install the CA Deliver host command environment into CA GSS

This section contains the following topics:

Change the Date Format Shown on Panels (see page 209)
Set Up the CA 11 Interface (see page 211)
Set Up CA 11 to Run with CA Deliver (see page 212)
Install the Host Command Environment into CA GSS (see page 214)

Change the Date Format Shown on Panels

The date format, date separator character, and time separator characters are specified
in the RMODFMT load module.

The date format is specified in the first byte (hex location 00) of the load module as a
hexadecimal value of 00 through 07 as follows:

Date Format Hexadecimal Value

MM/DD/YYYY (default) 00
DD/MM/YYYY 01
YYYY/MM/DD 02
YYYY/DD/MM 03
MM/DD/YY 04
DD/MM/YY 05
YY/MM/DD 06
YY/DD/MM 07

Chapter 11: Installing the Features 209

Change the Date Format Shown on Panels

■ A date separator character can be assigned in the second byte (hex location 01) of
the load module. The default data separator is a slash (/).
■ A time separator character can be assigned in the third byte (hex location 03) of the
load module.
The default time separator is a colon (:).
Note: Use printable characters that are not likely to be confused with syntactical
data, such as a comma or a quotation mark for the date and time separator
characters.
■ Use USERMOD BRNSDFMT in CAI.CVDEJCL to set values in RMODFMT.
Change the values in the REP statements in the AMASPZAP input to the values that
you want.

For example, if you selected MM/DD/YY for your default format, a dash (-) for the date
separator, and no change for the time separator, change the AMASPZAP statements in
BRNSDFMT as follows:

From: ++ZAP(RMODFMT).
NAME RMODFMT RMODFMT
VER 0000 0061,7A00
REP 0000 0061,7A00
$$
To: ++ZAP(RMODFMT).
NAME RMODFMT RMODFMT
VER 0000 0061,7A00
REP 0000 0460,7A00
$$

■ The first field in the VER and REP statements contains the location in the module
that is being changed. In this case, it is 0000. Do not change this value.
■ The second field contains four hexadecimal values separated into groups of two by
a comma.
■ The VER statement verifies that the values in this statement are the same as the
values found at location 0000 in RMODFMT.
■ The REP statement gives the values that will replace the data at location 0000 in
RMODFMT.

In the preceding example:

■ The first position in field 2 in the REP statement was changed from 00 to 04 to
specify the MM/DD/YY date format as defined in the preceding table.

210 Installation Guide

 Set Up the CA 11 Interface

■ The second position was changed from 61 (/) to 60 (-).

■ The third position is unchanged since we are not changing the time separator in this
example.
■ The fourth position is never changed.

Note: If you want to make a change to RMODFMT, you must reapply this USERMOD.

Set Up the CA 11 Interface

To set up an interface between CA 11 and CA Deliver, verify that one or more of the
following conditions exist:
■ You use two or more CA Deliver databases.
■ CA Deliver and CA 11 run on different operating systems and use the CA Deliver
network input feature.
■ Another vendor program is installed which does not allow you to specify the CA
Deliver database name through parameters on the EXEC statement.
■ You use both CA Deliver and CA Balancing Report Control (CA Balancing).

To set up an interface between CA 11 and CA Deliver:

1. Create a sequential data set to specify parameters for the CA Deliver and CA 11
interface program.
In this data set, specify the names of the CA Deliver databases and the destination
where CA 11 runs.
2. If CA 11 is executing on a different operating system, specify the name of this data
set in the RMOPARMS DD statement when you set up the CA 11 procedure catalog
for CA Deliver.
In this data set, specify the subsystem name of the CA L-Serv Database Manager
that is to manages the CA Balancing database (if CA Balancing is used with CA
Deliver).

Data Set Attributes

These attributes are needed to specify the data set referenced in the RMOPARMS DD
statement:
■ DSORG=PS
■ RECFM=FB
■ LRECL=80

Chapter 11: Installing the Features 211

Set Up CA 11 to Run with CA Deliver

Data Set Statements

In this data set, specify these two control statements:
■ One or more names of the CA Deliver databases that are used.
■ The name of the JES2 or JES3 destination on which CA 11 runs, if it is executing on a
different operating system.

Syntax of Control Statements in the Data Set

The syntax of the statement used to specify the name of a CA Deliver database is:

NAME high-level-name

where high-level-name represents the name of the CA Deliver database.

The syntax of the statement used to specify the name of the destination on which CA 11
runs is:

FROM-NODE NAME=JES2/JES3-dest-where-CA 11-runs

where JES2/JES3-dest-where-CA 11-runs represents the name of the originating

destination on which CA 11 runs.

These control statements are also described in the Reference Guide.

If there are identical job definitions in different CA Deliver databases, maintain the order
of the CA Deliver databases in the data set referenced in the RMOPARMS DD statement
for your entire execution.

Set Up CA 11 to Run with CA Deliver

To use CA 11 with CA Deliver and store reports in CA View, use CA View Release 11.5 or
higher and CA Deliver Release 11.5 or higher, and then follow these steps:
1. Change the program name in the first step of your JCL for the CA 11 job:
//STEP1 EXEC PGM=U11RMS,PARM='U11RMS-parms', or,
//STEP1 EXEC PGM=UCC11RMS,PARM='UCC11RMS-parms'

212 Installation Guide

 Set Up CA 11 to Run with CA Deliver

2. Change the utility name RMORMS:

//STEP1 EXEC PGM=RMORMS,PARM='U11RMS-parms', or,
//STEP1 EXEC PGM=RMORMS,PARM='UCC11RMS-parms'

If the program in the CA 11 JCL shown above is anything other than U11RMS, or if
you have any program that wraps around the CA 11 program, contact CA Technical
Support.
Note: For a description of RMORMS, see the Reference Guide.
3. Do one of the following:
■ If two or more CA Deliver databases are used or CA Balancing is used, add this
RMOPARMS DD data set name statement to the JCL for the CA 11 job:
//RMOPARMS DD DSN=sequential-data set-name,DISP=SHR

■ If only one is used, insert the name of the single CA Deliver database as a
parameter in front of the CA 11 program name parameters:
//STEP1 EXEC PGM=RMORMS,PARM='RMO-db;U11RMS-parms', or,
//STEP1 EXEC PGM=RMORMS,PARM='RMO-db;UCC11RMS-parms'

4. Determine if CA Deliver executes on a destination other than CA 11 and if the CA

Deliver network input feature is used, then do one of the following:
■ If the answer is yes to one of the above, go to Step 5.
■ If the answer is no to both of the above, go to Step 9.
5. Insert this statement on the last line of the RMOPARMS data set:
FROM-NODE JES2/JES3-dest-where-CA 11-runs

6. Insert the following DD statement in the first step (the RMORMS Step) of your JCL:
//RMONETn DD SYSOUT=(x,,form-name),DEST=dest-where-RMO-runs

Note: CA Deliver uses the output from this DD statement to determine whether the
job that is currently running is a rerun job.
7. Set the initialization parameter NETRERUN to YES.
8. Load the CA Deliver modules to the destination where CA 11 is going to execute:
■ EC0MSG
■ EC0SDIM
■ EC0SVC35
■ RMORCH
■ RMORMS
9. Set the initialization parameter MAXHIST to the maximum number of generations
that are expected to rerun jobs.

Chapter 11: Installing the Features 213

Install the Host Command Environment into CA GSS

To back out only reports produced within the last five generations, set MAXHIST=5.
Note: If the historical data report that you want to rerun has been purged, CA
Deliver cannot delete or flag these reports. You must manually delete these reports.
For more information about deleting reports manually, see the CA Deliver
Administrator Guide.
10. To rerun jobs that produce bundled reports and to specify when and how the
bundles are to be produced, use:
– TheLATE, INTERVAL, WAIT, and BUNDLE CONFIRM fields on the Bundle
Definition Attributes panel
– The Print Bundle Now tabular command P on the Active Bundle List panel
Note: For more information about the Bundle Definition Attributes Panel, the
Active Bundle List panel and the Print Bundle Now tabular command P, see the
Administration Guide.
CA Deliver cannot delete or flag bundle-holding copies if bundles have already been
queued for printing.
The RMORMS utility transmits the current rerun information from the originating
system on which CA Deliver is not installed to the receiving systems.
11. Review the RMSWARN initialization parameter in the Reference Guide. This
parameter affects how RMORMS reacts when the started task is not active.

Install the Host Command Environment into CA GSS

CA GSS (Global Subsystem) for MVS Release 2.6 is required for this installation.

To install the CA Deliver host command environment interface module into CA GSS, do
the following:
1. Be sure that MVS/TSO is running.
2. Ensure that CA GSS is installed on your system.
3. Look at the data set and member that are allocated to the PARMLIB DDNAME in CA
GSS.
4. Edit the data set/member and add the following line:
ADDRESS DELIVER RMOINTF
5. Add the CA Deliver load library to the concatenation of the CA GSS command
procedure.
6. Restart CA GSS.

214 Installation Guide

Appendix A: Installation Worksheets
This appendix contains worksheets to use to record your installation, initialization, and
started task parameters

This section contains the following topics:

Installation Worksheet (see page 215)
Initialization Parameter Worksheet (see page 216)
Started Task Worksheet (see page 219)

Installation Worksheet
This worksheet contains the SMP/E and system-related items required for the product
installation. Fill out this worksheet carefully and retain this information for future
reference.

Step 1: Global Install Parameters

■ Enter \ and your standard SYSOUT class for CA product installs
and SMP output.
Default: SYSOUT=____________ SYSOUT=_______________

■ Enter the installation product tape VOLSER.

Default: TAPVOL=____________ TAPVOL=_______________

■ Enter the name for the started task.

Default: STCNAM=CAHBB0ST STCNAM=______________

Step 2: Data Set Qualifiers and SMP Parameters

■ Enter the data set high-level qualifiers you plan to assign to
the common distribution, target, and SMP libraries.
Default: CAI='CAI.' CAI=___________________
Default: DSHLQ='CAI.' DSHLQ=________________

■ Enter your generic unit name for permanent work DASD

volumes.
Default: PERMDA=SYSDA PERMDA=_______________

Appendix A: Installation Worksheets 215

Initialization Parameter Worksheet

■ Enter your generic unit name for temporary work DASD

volumes.
Default: WORK=SYSDA WORK=_________________

■ Enter your generic unit name for the tape drives.

Default: TAPE=TAPE TAPE=__________________

■ Enter the DASD pack you plan to use as your SMP

temporary library volume.
Default: TLIB=DUMSER TLIB=__________________

Initialization Parameter Worksheet

Parameter Value
ARCH
ARCH__
ARCH__
ARCH__
ARCH__
ARCH__
ARCH__
ARCH__
ARCH__
ARCH__
ARCH__
ARCH__
ARCH__
ARCH__
AUTHTID
AUTOACT
BANNER
BEGINDAY
BNDLBNR1

216 Installation Guide

 Initialization Parameter Worksheet

Parameter Value
BNDLBNR2
BNDLBNR3
BNDLCLS
BNDLCONF
BNDLDEST
BNDLHDTL
BNDLINT
BNDLMOUT
BNDLSCAN
BNDLWAIT
BOT
CCX
DAYS
DEFDEL
DEFOUT
DEFREPRT
DEFRVIEW
EFORMAT
EMAILQ
EXTSEC
FEATURE
FREEALL
GSS
HDETAIL
HISTCNT
INBSSN
JOBCLSL
JOBREF
LOGO
MAXHIST

Appendix A: Installation Worksheets 217

Initialization Parameter Worksheet

Parameter Value
MAXJESQ
NAME
NETCLSL
NETDEST
NETFORM
NETONLY
NETREQUE
NETRERUN
NETUNDEF
OFFPW
OUTPUT
PRBTASK
PREVRUN
REDISP
RMSWARN
RPTENQ
RPTNPROD
SAR
SARBUFCT
SECMSG
SETCMD
SETPAGE
SETPW
SMF
SMF30
START
STKCHNn
STKMODE
STKNOTXT

218 Installation Guide

 Started Task Worksheet

Parameter Value
STNAMEn
(1, 2, 3, 4, 5)
STOPPW
SYSCLSL
SYSID
TEXT
TIME
WARNING
WEBSVR1
WEBSVR2
WEBSVR3
WEBSVR4
WRITER

Started Task Worksheet

Use this worksheet to list the data set names that are to be used in various steps of the
installation process.

Initialization Parameter
DDname: RMOPARMS

Data set name: _______________________________

Job Name Translation Control

DDname: RMOJTAB

Data set name: _______________________________

Appendix A: Installation Worksheets 219

Appendix B: Integration with CA OPS/MVS
EMA
This section contains the following topics:
Overview (see page 221)
Ensure that CA OPS/MVS Is Enabled for Capturing These Events (see page 222)
CA Deliver Active State Events (see page 222)
CA Deliver Heartbeat Events (see page 224)

Overview
CA Deliver provides seamless integration with CA OPS/MVS by automatically
communicating both active status events and heart beat events to CA OPS/MVS. The
enabling technology for this is through a generic event API call that CA OPS/MVS
provides the other mainframe products so that they can communicate events to CA
OPS/MVS.

You do not need to do anything for CA Deliver to enable this event communication
interface to CA OPS/MVS. If CA Deliver and CA OPS/MVS are active in the same z/OS
image, CA Deliver automatically communicates these automation events to CA
OPS/MVS.

By generating active status events CA Deliver and other CA products are able to
communicate to CA OPS/MVS’s System State Manager (SSM) component when they are
starting, up, stopping or down.

SSM is a built-in feature that uses an internal relational data framework to proactively
monitor and manage started tasks, online applications, subsystems, JES initiators, and
other z/OS resources including your CA mainframe products. SSM compares the current
state of online systems, hardware devices, and the other resources with their desired
state, and then automatically makes the necessary corrections when a resource is not in
its desired state. This provides proactive and reactive state management of critical
resources.

Appendix B: Integration with CA OPS/MVS EMA 221

Ensure that CA OPS/MVS Is Enabled for Capturing These Events

Before the CA OPS/MVS interface existed, CA OPS/MVS could automate active status
events for your CA products; however this typically required monitoring unique
messages for each CA product. With this interface, CA OPS/MVS can capture these
events for any of your CA products with a single automation event rule.

With the heart beat event, CA Deliver can communicate a normal, warning, or problem
overall health status and reasoning to CA OPS/MVS on a regular interval. Once CA
Deliver begins generating heart beat events for CA OPS/MVS, CA OPS/MVS can also
react to the lack of a heart beat event from CA Deliver, treating this as an indication that
there is either a potential problem with CA Deliver, or there is a larger system-level
problem that is taking place.

Ensure that CA OPS/MVS Is Enabled for Capturing These Events

To ensure that this CA OPS/MVS interface is active, make sure the CA OPS/MVS
parameter APIACTIVE is set to its default of ON. This allows CA OPS/MVS to
acknowledge and process the events generated by CA Deliver and other CA products
through this interface.

CA Deliver Active State Events

CA Deliver provides a direct interface to the CA OPS/MVS System State Manager (SSM)
application to notify CA OPS/MVS of the current operating state of the given CA Deliver
address space. The CA OPS/MVS SSM application can use this information to
automatically control the operation of the CA Deliver address space, as well as any other
address space that is dependent upon the CA Deliver address space being active. For
more information on using CA OPS/MVS SSM see the CA OPS/MVS User Guide.

The CA Deliver product active state is presented to CA OPS/MVS and can be processed
by the following rule:

)API CASTATE

222 Installation Guide

 CA Deliver Active State Events

The available OPS/REXX variables for CA Deliver product state management are:

OPS/REXX Variable Value

API.APPLICATION CA Deliver
API.VERSION Current release
API.LEVEL 00000
API.EVENTID CASTATE
API.MSGID CASTATE
API.TEXT State of CA Deliver

The API.TEXT variable has the following format:

State of appl_id is current_state'

appl_id
Specifies the same value as the API.APPLICATION variable
current_state
STARTING
Indicates that CA Deliver is initializing
UP
Indicates that CA Deliver is active
STOPPING
Indicates that CA Deliver is terminating
DOWN
Indicates that CA Deliver is exiting the system

For more information on how to use the CASTATE API, see the member SSMCAAPI of
opsmvsHLQ.STATEMAN.RULES.

Appendix B: Integration with CA OPS/MVS EMA 223

CA Deliver Heartbeat Events

CA Deliver Heartbeat Events

CA Deliver provides a continuous heartbeat event directly to CA OPS/MVS. CA OPS/MVS
can use this information in several ways to determine the operational health of the CA
Deliver product.

CA Deliver issues a heartbeat update every nnnn seconds that notifies CA OPS/MVS of
the current operational health of the CA Deliver product.

If CA Deliver detects a health state change, it immediately generates a heartbeat update

without waiting for the nnnn second heartbeat interval to expire. In this way, CA Deliver
provides CA OPS/MVS with a constant operational health state view of the CA Deliver
product.

CA OPS/MVS can also react to the lack of a heartbeat update from CA Deliver and an
indication that there is either a potential problem with CA Deliver, or there is a larger
system level problem that is taking place.

The CA Deliver product heartbeat event is presented to CA OPS/MVS and can be

processed by the following rule:

)API CAHEARTBT

The available OPS/REXX variables for CA Deliver state management are:

OPS/REXX Variable Value

API.APPLICATION CA Deliver
API.VERSION Current release
API.LEVEL 00000
API.EVENTID CAHEARTBT
API.MSGID CAHEARTBT
API.TEXT State of CA Deliver

224 Installation Guide

 CA Deliver Heartbeat Events

The API.TEXT variable has the following format:

appl_id Status: heartbeat_state Reason: reason_text

appl_id
Specifies the value of the API.APPLICATION variable.
heartbeat_state
Heart_beat_state can be one of the following:
NORMAL
Indicates that CA Deliver is operating normally, without any detected problems.
WARNING
PROBLEM
reason_text
reason_text explains the problem as reported by the event API call.

For information on how you use the CAHEARTBT API, see members APIHRTB1,
APIHRTB2, and APIHRTB3 of opsmvsHLQ.SAMPLE.RULES.

Appendix B: Integration with CA OPS/MVS EMA 225

Index
A CPU id • 81
cross-memory • 147, 148, 158
abend output • 167 drivers • 148
access interface parameter requirements • 158
login • 30 interfaces, installing • 147
adding variables • 98 services (XMS) • 147, 158
allocate and mount • 37 advantages • 147
attributes • 98, 211 parameter • 158
data set • 211 customer support, contacting • 3
highlight • 98
D
B
data set • 211, 212
BROWSE panel, customizing the • 98 attributes • 211
statements • 212
C data sets, SVC dump • 20
CA 11 • 211, 212 database name • 212
interface setup • 211 date • 81
originating destination name of • 212 LMP key certificate expiration • 81
CA Common Services • 18 deleting variables • 98
definition of • 18 distribution • 15
CA GSS (Global Subsystem) • 214 libraries • 15
command procedure • 214 download
CA MSM usage scenarios • 25 files using ESD • 33
CA Roscoe • 90, 131, 148 options • 40
Cross-Memory Online Retrieval Option • 131 overview • 31
interface driver • 148 to mainframe through a PC • 44
Online Retrieval Option • 90 using batch JCL • 41
CAI Resource Initialization Manager (CAIRIM) • 18, drivers, cross-memory • 148
81 dump • 20, 21, 167
CAI.SAMPJCL analysis and elimination • 20
library • 58 output • 167
sample jobs • 58 parameters, system • 21
CAIRIM (CAI Resource Initialization Manager) • 18,
81 E
CANCEL parameter • 158 EBC (Extended Base Component), library • 15
CICS • 136 EBCUDUMP DD statement • 167
menu system • 136 ETSO • 90
color, defining for panels • 98 ETSOLIB DD statement • 90
command libraries, adding • 84 EXEC statement • 211
concatenation, PROCLIB • 21 execution • 81, 148
constants, modifying • 98 keys • 81
contacting technical support • 3 restrictions • 148
control statements • 212 expiration date, LMP key certificate • 81
syntax of • 212 Extended Base Component (EBC), library • 15
copy files to USS directory • 40, 41, 44 external HOLDDATA • 53

Index 227
F J
free space • 36 Java version support • 46
JCL • 21
G procedures • 21
GIMUNZIP utility • 46 job name translation control • 219
global install parameters • 215
K
H key certificate • 81
hardware requirements • 15
hash setting • 46
L
HELP panel, customizing the • 98 length of variables • 98
hexadecimal characters, reserved • 98 LGNFMT parameter • 158
high-level qualifier • 46 LGNPROP parameter • 158
highlight attributes • 98 LGNSEC parameter • 158
HOLDDATA • 53 libraries • 15, 84
host command environment • 214 distribution • 15
panel and command • 84
I library • 15
IEBCOPY • 58 EBC (Extended Base Component) • 15
initialization • 18 License Management Program (LMP) • 81, 82, 83
routines • 18 encrypted code • 81
Initialization Parameter Worksheet • 215, 216 execution key • 81
installation • 215 execution software parameter • 82
worksheets • 215 key certificate • 81
installing • 18, 89, 117, 118, 131, 147, 149 licensing agreement for • 82
CA Roscoe Cross-Memory Online Retrieval multiple codes • 83
Option • 131 LMP (License Management Program) • 81, 82, 83
cross-memory • 147 encrypted code • 81
interfaces • 147 execution key • 81
from Pax-Enhanced ESD • 31 execution software parameter • 82
from tape • 57 key certificate • 81
ISPF • 118, 149 licensing agreement for • 82
Cross-Memory Online Retrieval Option • 118 multiple codes • 83
online retrieval option • 149 LONGWAIT parameter • 158
MVS interfaces • 18
online interfaces • 117
M
software • 18 macros • 169
TSO online retrieval option • 89 format of • 169
Integrated Cryptographic Services Facility (ICSF) • 46 maintenance • 62
internal HOLDDATA • 53 menus • 88
ISPF • 118, 148, 149 ISPUTIL utilities • 88
Cross-Memory Online Retrieval Option • 118 MIS director, specifying the • 81
interface driver • 148 modifying constants • 98
online retrieval option, installing • 149 MSGLVL parameter • 158
ISPTLIB DD statement • 84 multiple LMP codes • 83
ISPUTIL utilities menu • 88 MVS interfaces, installing • 18

228 Installation Guide

N code • 81
product download window • 33
network input feature • 211 product-level directory • 45
NEWAPPL(RMO) • 85 products, automatic startup of • 18
O Q
OLIB • 98 Qname • 104
online • 117
interfaces • 117 R
installing • 117
read me • 31, 46
OPTLIB • 82
REGIONID parameter • 161
originating destination name of CA 11 • 212
reprints • 148
P requirements for installing • 15
hardware • 15
panel libraries, adding • 84 RESERVE • 104
parameters • 21, 118, 158, 161, 215 restrictions, execution • 148
CANCEL • 158 RMOAPPL parameter • 158
install • 215 RMOLOG DD • 167
LGNFMT • 158 RMOVTDB parameter • 158
LGNPROP • 158 RMOXMS region • 167
LGNSEC • 158
LONGWAIT • 158 S
MSGLVL • 158
sample JCL • 58
REGIONID • 161
sample jobs • 41, 45
RMOAPPL • 158
CAtoMainframe.txt • 41
RMOVTDB • 158
Unpackage.txt • 45
SMFSESS • 158
SARINIT initialization utility • 105
SUBSYS • 158
SDUMP (SVC dumps) • 20
system dump • 21
segments, overlapping • 90, 118, 125, 127, 131, 133,
USERMAX • 158
149
VTAMPASS • 158
site contact, technical • 81
VTAMSAA • 158
SMF exits • 18
VTMQUERY • 158
SMFSESS parameter • 158
XMS (cross-memory services) • 158
SMP/E
XMSSUB • 118, 158
GIMUNZIP utility • 46
pax ESD procedure
receive the package • 47
copy product files • 40
software • 18
create product directory • 45
installation • 18
download files • 33
stacked reports containing overlapping segments •
receive the SMP/E package • 47
90, 118, 125, 127, 131, 133, 149
set up USS directory • 36
Started Task Worksheet • 215, 219
pax file
statements • 84, 90, 212
copy files to USS directory • 40, 41, 44
data set • 212
position of variables • 98
ETSOLIB DD • 90
procedures, JCL • 21
OSPTLIB DD • 84
process overview • 31
STEPLIB • 84
PROCLIB • 21
STEPLIB DD • 84
product • 81
STEPLIB • 84

Index 229
STEPLIB DD • 84, 168 Started Task • 215, 219
storage requirements, estimating • 15
SUBMIT • 148 X
support, contacting • 3 XMS (cross-memory services) • 147, 158
SVC • 18, 20 parameter • 158
dumps (SDUMP) • 20 XMSSUB parameter • 118, 158
eliminating user • 18
syntax of control statements • 212
SYSPRINT DD statement • 167
system • 21, 104
dump parameters • 21
integrity product • 104

T
tape, installing from • 57
technical • 81
site contact • 81
technical support, contacting • 3
TSO • 89, 148
interface driver • 148
online retrieval option, installing • 89
SUBMIT • 148

U
UNIX System Services (USS)
access requirements • 31, 36
directory cleanup • 51
directory structure • 36
UNZIPJCL • 46
user • 149
exits • 149
USERMAX parameter • 158

V
variables • 98
adding • 98
deleting • 98
length of • 98
position of • 98
verifying software installation • 18
VTAMPASS parameter • 158
VTAMSAA parameter • 158
VTMQUERY parameter • 158

W
worksheets • 215, 219
Initialization Parameter • 215
installation • 215

230 Installation Guide