CA Deliver

Best Practices Guide

r11.6

This documentation and any related computer software help programs (hereinafter referred to as the "Documentation") are for your informational purposes only and are 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 used or disclosed by you except as may be permitted in 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 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 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 THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, 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 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 2010 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

CA Product References
This document references the following CA products: CA 11 Restart and Tracking (CA 11) CA Deliver (CA Deliver) CA Mainframe Software Manager (CA MSM) CA Output Management Web Viewer (CA OM Web Viewer) CA Spool (CA Spool) CA View (CA View)

Contact CA
Contact Technical Support For your convenience, CA provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA products. At http://ca.com/support, you can access the following: 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

Provide Feedback If you have comments or questions about CA product documentation, you can send a message to [email protected]. If you would like to provide feedback about CA product documentation, complete our short customer survey, which is also available on the CA Support website, found at http://ca.com/docs. Best Practices Guide Process These best practices represent years of product experience, much of which is based on customer experience reported through interviews with development, technical support, and technical services. Therefore, many of these best practices are truly a collaborative effort stemming from customer feedback.

To continue and build on this process, we encourage users to share common themes of product use that might benefit other users. Please consider sharing your best practices with us. To share your best practices, contact us at [email protected] and preface your email subject line with "Best Practices for product name" so that we can easily identify and categorize them.

Contents
Chapter 1: Introduction 7
Purpose of this Guide .......................................................................... 7 Audience ...................................................................................... 7 Mainframe 2.0 Overview ....................................................................... 7 Mainframe 2.0 Features ........................................................................ 8

Chapter 2: Installation and Configuration

11

Installation ................................................................................... 11 CA Common Services ..................................................................... 12 Installation in a Test Environment.......................................................... 12 Use a Common CA High Level Qualifier Symbolic ............................................ 13 Downward Compatibility................................................................... 14 Implementation .............................................................................. 14 Library Authorization ...................................................................... 14 Multiple System Images with Shared Database and Checkpoint File .......................... 15 Configuration ................................................................................. 15 Initialization Parameters .................................................................. 15 Cross-Memory Services Parameters ........................................................ 17 Bundle Initialization and Timing Parameters ................................................ 18 Scheduled Distribution .................................................................... 19 Data Set Collector ........................................................................ 19 Direct Archival to CA View ................................................................. 20 Archive Reports Parameter ................................................................ 20 Integration and Interface Points ............................................................... 21 Integrate CA View with CA Deliver ......................................................... 21 Integrate Email Notification by way CA Spool, CA OM Web Viewer ............................ 21 Automate Job Reruns ..................................................................... 22

Index

23

Contents 5

Chapter 1: Introduction
This section contains the following topics: Purpose of this Guide (see page 7) Audience (see page 7) Mainframe 2.0 Overview (see page 7) Mainframe 2.0 Features (see page 8)

Purpose of this Guide

The guide provides a brief introduction to CA's Mainframe 2.0 strategy and features, and describes the best practices for installing and configuring CA Deliver.

Audience
The intended audience of this guide is systems programmers and administrators who install, configure, deploy, and maintain the product.

Mainframe 2.0 Overview

Mainframe 2.0 is our strategy for providing leadership in the mainframe operating environment. We intend to lead the mainframe marketplace for customer experience, Out-Tasking solutions, and solution innovation. After listening to customer needs and requirements to keep the mainframe operating environment viable and cost-effective, we are providing new tools to simplify usage and to energize this operating environment for years to come. CA Mainframe Software Manager (CA MSM) is an important step in realizing the Mainframe 2.0 strategy. CA MSM simplifies and standardizes the delivery, installation, and maintenance of mainframe products on z/OS systems. CA MSM has a browser-based user interface (UI) with a modern look and feel for managing those solutions. As products adopt Mainframe 2.0 features and CA MSM services, you can acquire, install, and manage your software in a common way. CA MSM provides software acquisition and installation that make it easier for you to obtain and install CA mainframe products, and apply the recommended maintenance. The services within CA MSM enable you to manage your software easily based on industry accepted best practices. The common browser-based UI makes the look and feel of the environment friendly and familiar.

Chapter 1: Introduction 7

Mainframe 2.0 Features

We follow the IBM z/OS packaging standards using SMP/E, with some additional CA qualities of service added, to make installation simple and consistent. Additionally, through the synchronization of product releases and the use of common test environments, we will declare a yearly mainframe software stack that includes many new releases with enhanced functionality. This stack is certified for interoperability across the CA mainframe product portfolio and the base IBM z/OS product stack.

Mainframe 2.0 Features

Mainframe 2.0 has the following main features: CA Mainframe Software Manager (CA MSM) Delivers simplified acquisition, installation, and deployment capabilities using a common z/OS-based web application delivered through a browser-based UI. CA MSM includes the following services: Product Acquisition Service (PAS) Facilitates the acquisition of our mainframe products and services, including product base installation packages and program temporary fixes (PTFs). This service integrates the inventory of products available on your system with CA Support, providing a seamless environment for managing and downloading software and fixes onto your system. Software Installation Service (SIS) Facilitates the installation and maintenance of our mainframe products in the software inventory of the driving system. This service enables you to browse and manage the software inventory using a web interface, and automates tasks for products that use SMP/E to manage installation. You can browse downloaded software packages, and browse and manage one or more consolidated software inventories (CSIs) on the driving system. Software Deployment Service (SDS) Facilitates the deployment of our mainframe products from the software inventory of the driving system. This service enables you to deploy installed products that are policy driven with a set of appropriate transport mechanisms across a known topology. The enterprise system topology can include shared DASD environments, networked environments, and z/OS systems. Policies represent a combination of CA metadata input that identifies the component parts of a product and user-supplied input that identifies the deployment criteria, such as where it will go and what will it be called. Electronic Software Delivery (ESD) Enables you to get our products from an FTP server. We have improved this process so that you no longer need to build a tape to install the product.

8 Best Practices Guide

Mainframe 2.0 Features

Best Practices Management Integrates with IBM Health Checker for z/OS to verify that deployed software follows our best practices. The health checks continually monitor the system and software to provide feedback on whether the software continues to be configured optimally. Best Practices Guide Provides best practices for product installation and configuration. Note: For additional information about the CA Mainframe 2.0 initiative, see http://ca.com/mainframe2.

Chapter 1: Introduction 9

Chapter 2: Installation and Configuration

This section contains the following topics: Installation (see page 11) Implementation (see page 14) Configuration (see page 15) Integration and Interface Points (see page 21)

Installation
Use CA MSM to acquire, install, and maintain your product. Business Value: CA MSM provides a common way to manage mainframe products. CA MSM provides a web interface, which works with Electronic Software Delivery (ESD) and standardized installation and management of mainframe products. You can use it to download and install CA Deliver. CA MSM lets you download product and maintenance releases over the Internet directly to your system from the CA Support website. After you use CA MSM to download your product or maintenance, you use the same interface to install the downloaded software packages using SMP/E. Additional Considerations: After you install the product, use the CA Deliver Installation Guide to set it up. CA MSM can continue to help you maintain your product. More Information: For more information about CA MSM, see the CA Mainframe Software Manager Guide. For more information about product setup, see the CA Deliver Installation Guide.

Chapter 2: Installation and Configuration 11

Installation

CA Common Services
Make sure you have installed the most current release of CA Common Services. Business Value: The latest release of CA Common Services contains the most current infrastructure updates, allowing you to successfully use the latest features, and preventing potential errors that can occur from using out-of-date services. Note: CA Common Services r11 SP8 is required to take advantage of the Health Checker feature. More Information: For more information on CA Common Services, see the Installation Guide.

Installation in a Test Environment

Perform your installation and initial evaluations of the product and its components on a test system. Business Value: New releases of CA Deliver can be installed in different SMP/E zones or data sets to allow a new release to run on a test system while the old release continues to run on production systems. Evaluating the product in a test environment lets you detect any possible problems before you roll it out to a production system, which will help ensure a seamless transition to the new release. More Information: Always be sure to review any upgrade considerations in the Installation Guide prior to upgrading CA Deliver.

12 Best Practices Guide

Installation

Use a Common CA High Level Qualifier Symbolic

CWhen installing more than one of CAs Mainframe Enterprise Report Management (ERM) release r11.5 products, we recommend that you install using one common high-level qualifier for the **CAI** symbolic that is shared by all of the products. Business Value: By installing and maintaining a single version of a CA common high-level qualifier, you reduce your maintenance effort, save disk space, and eliminate the possibility of executing symbolic utilities that may not be up-to-date with the latest maintenance. Additional Considerations: In particular, it is a best practice to install CA Deliver r11.5 and CA View r11.5 into the same SMP/E CSI data set and SMP/E zones. CA View and CA Deliver both require the EBC Common Component. Having both products in the same SMP/E environment is the best way to enforce cross-product dependencies and to insure that both products are at current maintenance levels. Notes: While it is a best practice for CA Deliver r11.5 and CA View r11.5 to share a common SMP/E CSI, CA Deliver r11.5 can not be installed into an SMP/E target and distribution zone that contains CA View r11. EBC r11.5 can not replace EBC r11 in an SMP/E environment that contains CA View r11 and/or CA Deliver r11. If you want to upgrade to CA Deliver r11.5 in a shared SMP/CSI containing CA Deliver and CA View r11, you can do one of the following: RECEIVE CA Deliver r11.5 and CA View r11.5, then APPLY and ACCEPT CA Deliver r11.5 and CA View r11.5 simultaneously. Install CA Deliver r11.5 and CA View r11.5 into new SMP/E target and distribution zones. This will also require you to allocate new target data sets.

Chapter 2: Installation and Configuration 13

Implementation

Downward Compatibility
Use direct archival from CA Deliver r11.5 to either CA View r11 or CA View 11.5 databases. Business Value: Maintains compatibility between CA Deliver r11.5, CA View r11, and CA View 11.5 databases. If CA Deliver is used to archive reports to several CA View databases, it is not necessary to invest excessive time and resources to immediately upgrade all of the databases at the same time that Deliver is upgraded to r11.5. Alternatively, it would be less resource-intensive, and would reduce the risk of configuration errors, to gradually upgrade the CA View databases to the r11.5 level. Additional Considerations: CA View r11.5 is also downward compatible with CA Deliver r11. Therefore, if it is preferable to upgrade CA View first, both CA Deliver r11.5 and r11 reports and bundles can be archived and reprinted from a CA View r11.5 database. Note: A cross memory region is limited to accessing a single version of CA Deliver. A CA Deliver r11.5 cross memory region cannot access a CA Deliver r11 database. More Information: For additional details on the cross-product compatibility of CA View and CA Deliver, refer to the Upgrade Considerations section of Introduction chapter in the CA Deliver Installation Guide.

Implementation
Once installation is complete, CA Deliver can be implemented. This section discusses the best practices for implementing CA Deliver.

Library Authorization
APF-authorize the target library by adding an entry for CAI.CAILIB to member IEAAPFxx of SYS1.PARMLIB. Business Value: Running an APF-authorized library ensures that CA Deliver executes with the appropriate permissions and approvals.

14 Best Practices Guide

Configuration

Multiple System Images with Shared Database and Checkpoint File

You can run CA Deliver started tasks on multiple system images and share the same CA Deliver database and checkpoint file. This allows CA Deliver to pre-spool process sysout datasets on each system image, rather than having to post-spool process work through a single CA Deliver started task. Business Value: Faster and more efficient processing speed is achieved by allowing CA Deliver to run on multiple CPUs. The checkpoint is designed to handle up to thirty-two system images, which allows for faster processing and system integrity. Additional Considerations: If you set the CA Deliver initialization parameter HDETAIL to YES, the amount of history detail data can significantly increase the size of your database, slow down report processing, and eventually cause your started task to abend. You can run an RMODBASE with the STATUS control statement to display usage statistics on the CA Deliver database. For more information about this parameter, see the CA Deliver Reference Guide. More Information: See the Set Up on Multiple CPUs step in the Installation chapter in the CA Deliver Installation Guide.

Configuration
Initialization Parameters
When starting a CA Deliver system of the first time, it is a good practice to focus on the basic initialization parameters that comprise the minimum requirements for successful startup. After that occurs, examine the other initialization parameters to add more detailed processing options for your environment Business Value: Focusing on a basic subset of the initialization parameters will simplify a first-time installation and result in a faster implementation of CA Deliver. Additional options and parameters can be specified later, based on the evaluation of business requirements at your site. Additional Considerations: The following initialization parameters are the minimal requirements to specify when starting a CA Deliver system for the first time.

Chapter 2: Installation and Configuration 15

Configuration

Database Names Set NAME to the high level qualifier of the CA Deliver database and SAR to the high level qualifier of the primary CA View database. System Identifier Set SYSID to specify the parameter that identifies the CA Deliver started task. If multiple started tasks are run on the same system image, their SYSID parameters must be different. Pre-spool processing Set JOBCLSL to the job classes and SYSCLSL to the SYSOUT classes where Deliver will intercept reports using pre-spool processing. Post-spool Processing Set NETCLSL, NETDEST, and NETFORM to the SYSOUT class, destination, and form where Deliver will pick up reports from JES using post-spool processing. Post-spool processing is referred to as the CA Deliver Network Input Interface. Use NETONLY to state whether or not CA Deliver will only do post-spool processing. Archival Parameters Use the ARCHnn parameters to specify criteria for the archival of reports into CA View. You can specify up to 99 ARCHnn parameters. Use ARCH to specify the default ARCH parameter to use if a report definition does not specify an ARCH parameter. History Tracking Parameters Use HDETAIL, BNDLHDTL, and MAXHIST to specify whether detail history is being kept and how many generations of historical data are to be kept. Bundling Parameters Use BNDLMOUT and OUTPUT together to allow bundled reports with unlike attributes to be printed together. To avoid performance degradation when multiple RMOSTCs access the same database, only one started task should have BOT=YES specified. The other started tasks should have BOT=NO specified.

16 Best Practices Guide

Configuration

Daily Cycle Parameters Use TIME, BEGINDAY, and DAYS to specify the time of day and the days of the week when the CA Deliver daily cycle and bundle cycles are to occur. If there will be multiple CA Deliver RMOSTCs accessing the same database, we suggest that BOT=YES, and TIME be set in one RMOSTC only, and BEGINDAY be set to the same value in each RMOSTC. The other tasks should have BOT=NO and TIME=0000. More Information: See the Initialization Parameters chapter of the CA Deliver Reference Guide.

Cross-Memory Services Parameters

For first-time configuration of a cross memory region, thoroughly review the cross memory parameters to determine the most appropriate settings for your environment. In particular, consider how security will be used in conjunction with the XMS region, what type of online interfaces will be available to the XMS region, and how inactive and cancelled users will be handled. Business Value: Cross memory services provide an efficient mechanism to manage online user access to CA Deliver through a number of interfaces. This enables the CA Deliver administrator to use a cross memory region as a central point of administration for hundreds of users. Additional Considerations: The following cross-memory parameters are the most critical parameters to consider when starting a CA Deliver cross-memory task for the first time. Control of Idle Users Use CANCEL and LONGWAIT together to specify how long to wait before cancelling a user that is inactive. Security Controls Use the LGNPROP and LGNSEC parameters together to determine the type of security and the USERID that will be used for security checking and job submission. Online Interface And Logon Control Use the XMS and XMSSUB parameters TO determine whether cross memory users can log onto the XMS region and whether there is support the ISPF, TSO, and CA Roscoe interfaces.

Chapter 2: Installation and Configuration 17

Configuration

More Information: See Installing Online Interfaces chapter in the CA Deliver Installation Guide for complete information.

Bundle Initialization and Timing Parameters

Use all of the bundle timing parameters on the Bundle Definition Attributes Panel to control when bundles are produced. The LATE, INTERVAL, WAIT, and WAIT for LATE fields work together to control bundle production. Bundle Initialization and Timing parameters selection are the most critical parameters to consider when starting a CA Deliver system for the first time. Business Value: Time management and planning of bundled output production will maximize operational efficiency by load balancing system resources and printer usage. Additional Considerations: The following bundle initialization and timing parameter are most critical. BEGINDAY, TIME, and DAYS Specify the time of day and the days of the week when BEGINDAY and possibly a bundle BEGINDAY are run. If there are multiple CA Deliver RMOSTCs accessing the same database, we suggest that the value of TIME be set in one RMOSTC only, in conjunction with BOT=YES in the same RMOSTC only. The other tasks should have BOT=NO and TIME=0000. Additionally, the value of BEGINDAY should be set to the same value on every RMOSTC region. Time The TIME parameter controls when the new daily cycle will begin. BEGINDAY If BEGINDAY is not specified, then the start of the daily cycle and the bundle BEGINDAY are the same. If the processing of bundles requires that bundles have a BEGINDAY at a time different from the start of the daily cycle then the bundle BEGINDAY time is specified by the BEGINDAY= parameter. More Information: See the Initialization Parameters chapter of the CA Deliver Reference Guide. See the Determine When a Bundle Is Produced table in the Creating a Bundle of Reports chapter in the CA Deliver Administration Guide.

18 Best Practices Guide

Configuration

Scheduled Distribution
Use the Scheduled Distribution feature to control report production. This feature can control a document distribution based on the day of a week. Business Value: Customers requiring printed or emailed output based on a particular distribution ID can specify which days of the week reports are to be sent. This can reduce report distribution and printing costs by eliminating unnecessary or redundant production work. Additional Considerations: A DAYS field has been added to the distribution specifications to identify the days of week that the recipient is to receive output. The default is Y (yes); the recipient will receive a new report each day of the week. The field can be set to Y (yes) or N (no) for each day of the week from Monday to Sunday. The DAYS field can be specified on the Report Definition Attribute Distribution Specification panel and the Distribution List Distribution Specifications pane.

Data Set Collector

Use the Data Set Collector feature to allow CA Deliver to process reports directly from a mainframe dataset. The data set collector, RMODSC, provides added flexibility by allowing multiple files to be processed, allowing distribution based on a specific report definition, and allowing manipulation and/or sectioning of input data through a named user exit. Business Value: The Data Set Collector enables more flexibility for report collection and provides an easy transition for customers when they are converting from other report distribution systems, which collect reports from a dataset. More Information: For more information about CA Deliver data set collector, RMODSC, see the chapter Utilities in the CA Deliver Reference Guide.

Chapter 2: Installation and Configuration 19

Configuration

Direct Archival to CA View

We recommend using direct archival to send reports directly to a CA View database. Using direct archival can reduce the need for the CA View archival task to use system resources to collect output from the JES spool, can allow bundle holding copies to be stored in CA View instead of JES, and can eliminate distribution of printed output when it is not needed. Business Value: Direct archival will reduce the system I/O, CPU, and JES resources required for electronic distribution of reports and can reduce costs associated with printing and delivering output. It can also improve productivity by allowing users to view bundled reports online immediately, without having to wait for bundles to be collected from JES. Additional Considerations: The ARCH and ARCHnn initialization parameters are used in conjunction with the ARCH parameter in CA Deliver Report Attributes panel to determine how reports are to be archived to different CA View databases.

Archive Reports Parameter

Use CA Deliver to take advantage of the CA View Functional Subsystem (FSS) collectors to archive fully composed AFP reports into CA View databases. This can be accomplished by using the ARCH parameter in the CA Deliver Report Definition Panel to send the report into JES with characteristics that fit the selection criteria of the FSS printer. Business Value: Maintain the value of your fully composed AFP data without losing the tracking data and security of your reports that are provided by CA Deliver. More Information: See Installing the FSS Collector section in the CA View Installation Guide.

20 Best Practices Guide

Integration and Interface Points

Integration and Interface Points

Integrate CA View with CA Deliver
Use CA Deliver in conjunction with CA View as a complete Output Management solution for managing reports. As indicated by other best practices in this manual, CA Deliver reports can be archived directly to CA View databases, viewed online, and backed up on storage media. All CA Deliver report attributes and distribution data are retained in CA View database. Business Value: Creating a complete solution optimizes report management. By implementing an automated archival and retrieval system you can automate day-to-day report management, minimize time-consuming manual tasks, and lower document delivery costs. Viewing reports online and printing fewer reports saves cost and reduces time spent reformatting, tracking, handling and rerunning reports.

Integrate Email Notification by way CA Spool, CA OM Web Viewer

Use the CA Spool Email Print Driver to notify report recipients that documents are available for viewing in CA Output Management Web Viewer, or to send copies of reports directly to recipients. The notification emails can include a link to the report, and deliver the report as an attachment in text, HTML, or PDF format. Business Value: Automates notification of report availability and simplifies database search and retrieval. The CA Deliver Email Notification feature is an efficient and robust method to track and distribute reports processed by CA Deliver. It provides the ability to distribute and track an entire report or selected pages of a report to recipients for online viewing. This can save the recipients time when waiting for a report to arrive. Instead of repeatedly checking for report arrival in CA OM Web Viewer, the recipient will know the report is ready when an email arrives. More Information: See the Setting Up Email and Email Notification chapter in the CA Deliver Administration Guide.Also, view the CA Spool Print Management Customization Guide.

Chapter 2: Installation and Configuration 21

Integration and Interface Points

Automate Job Reruns

Manage CA Deliver report and job reruns by implementing the CA 11 Workload Automation Restart and Tracking interface. Business Value: Automatically managing report data requiring job reruns provides reliable tracking of reports and eliminates the potential of time consuming manual effort when operating errors occur in output production. Additional Considerations: Refer to the NETRERUN and RMSWARN initialization parameters, and the RMORMS and RMOPRE utilities in the CA Deliver Reference Guide, and the PREVRUN job parameter in the CA Deliver Administrator Guide.

22 Best Practices Guide

Index
A
Archive Reports Parameter 20 Audience 7 Automate Job Reruns 22

P
Purpose of this Guide 7

S
Scheduled Distribution 19

B
Bundle Initialization and Timing Parameters 18

U
Use a Common CA High Level Qualifier Symbolic 13

C
CA Common Services 12 CA Product References iii Configuration 15 Contact CA iii Cross-Memory Services Parameters 17

D
Data Set Collector 19 Direct Archival to CA View 20 Downward Compatibility 14

I
Implementation 14 Initialization Parameters 15 Installation 11 Installation and Configuration 11 Installation in a Test Environment 12 Integrate CA View with CA Deliver 21 Integrate Email Notification by way CA Spool, CA OM Web Viewer 21 Integration and Interface Points 21 Introduction 7

L
Library Authorization 14

M
Mainframe 2.0 features 8 Mainframe 2.0 Features 8 Mainframe 2.0 overview 7 Mainframe 2.0 Overview 7 Multiple System Images with Shared Database and Checkpoint File 15

Index 23