K007791E - Getting Started

Unicenter CA-Bundl for z/OS & OS/390

Getting Started 5.0

K00779-1E

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

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

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

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

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

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

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

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

2002 Computer Associates International, Inc.

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

Contents iii

getstart.doc, printed on 10/29/2002, at 2:38 PM

Contents

Chapter 1: Introduction Unicenter CA-Bundl 5.0 Documentation..........................................1–1

Downloading the Documentation ............................................1–2 Viewing PDF Documentation ................................................1–3 Related Documentation .....................................................1–3

Contacting Technical Support ...................................................1–3 Summary of Product Changes ...................................................1–4 Conventions Used in this Guide ............................................... 1–10

Chapter 2: Introducing Unicenter CA-Bundl Overview of the Unicenter CA-Bundl Installation Process ..........................2–1 Installing Under SMP/E ........................................................2–2

Major SMP/E Operations ...................................................2–3

Chapter 3: System Requirements CA Common Services ..........................................................3–1

CAI Resource Initialization Manager (CAIRIM) ...............................3–1 CA-LMP...................................................................3–2 CA-LServ ..................................................................3–2

iv Getting Started


Unicenter CA-Bundl and CA-DRAS ............................................. 3–3 Installation Requirements................................................... 3–3

Mainframe............................................................. 3–3 PC Environment ....................................................... 3–4

Unicenter CA-Bundl Installation Materials ....................................... 3–4 Hardware Requirements ....................................................... 3–5

Target Libraries ............................................................ 3–5 Distribution Libraries....................................................... 3–5

Software Requirements......................................................... 3–6 Unicenter CA-Bundl 5.0 Component SYSMODs............................... 3–6 CA Common Services Component........................................... 3–6 Optional CA-DRAS Component ............................................. 3–6

Library Authorization .......................................................... 3–7

Chapter 4: Installing Unicenter CA-Bundl Preparing for Installation ....................................................... 4–1

CA-DRAS Agent Support ................................................... 4–1 CA Common Services Considerations........................................ 4–1 Unicenter CA-Bundl Upgrade Considerations ................................ 4–2 Installation Steps........................................................... 4–2

Step 1: Complete the Customization Worksheet................................... 4–3 Unicenter CA-Bundl Customization Worksheet ............................... 4–4

Step 2: Load the Installation Sample JCL (SAMPJCL) Library (Required) ............ 4–7 Step 3: Allocate Libraries (Required) ............................................. 4–8

Step 3a: Allocate Target and Distribution Libraries ............................ 4–8 If You Have More Than One Computer Associates Product ................ 4–8

Step 3b: Allocate Private SMP/E Libraries .................................... 4–9 Step 4: Customize the SMP Procedure (Required) ................................ 4–10 Step 5: RECEIVE the Services (Required) ........................................ 4–10

FMIDs ................................................................... 4–10 Step 6: APPLY the Services (Required) .......................................... 4–10 Step 7: Authorize Program Load Libraries (Required) ............................ 4–11

Contents v


Step 8: Enter the LMP Code (Required) ......................................... 4–11 LMP Key Certificate ...................................................... 4–11 Defining the CA-LMP Execution Key ....................................... 4–13 Multiple LMP Codes...................................................... 4–14

Step 9: Tailor the Execution JCL................................................ 4–14 Step 10: Tailor the Procedures ................................................. 4–18 Step 11: Initialize Test VSAM Files (Required)................................... 4–19

Initializing New VSAM Files .............................................. 4–21 Step 12: Install the CICS Option (Optional)...................................... 4–21

Installing the CICS Option................................................. 4–22 Step 13: Install the Advantage CA-Roscoe Option (Optional) ..................... 4–23

Installing the Advantage CA-Roscoe Option for Use with Unicenter CA-Bundl . 4–23 Starting the Unicenter CA-Bundl Online System and End-User Facilities ....... 4–24

Step 14: Install Unicenter CA-Bundl VTAM View (Optional) ..................... 4–24 Installing VTAM View .................................................... 4–24

Step 15: Install the TSO Interface (Optional)..................................... 4–26 Installing TSO ............................................................ 4–26

Step 16: Set Up CA-LServ to Execute Unicenter CA-Bundl........................ 4–27 Step 17: Test Your Unicenter CA-Bundl Installation.............................. 4–28 Step 18: Create Production VSAM Files ......................................... 4–29

Upgrading CA-Bundl 4.9 to Unicenter CA-Bundl 5.0 ......................... 4–30 Step 19: ACCEPT the Services (Optional) ....................................... 4–32

ACCEPT Considerations with Pre-Installed Services ......................... 4–33 Step 20: Using a Single File Server with Multiple Unicenter CA-Bundl Systems..... 4–34

Chapter 5: Providing Security in Unicenter CA-Bundl How Security Works in Unicenter CA-Bundl......................................5–1 Types of Security You Can Provide in Unicenter CA-Bundl.........................5–2 Security Options Screen.........................................................5–4

Fields and Descriptions .....................................................5–4 Modifying a Security Options Record ............................................5–6 Deciding What Access Users Need ...............................................5–7

vi Getting Started


Granting Authority to Screens and Applications ................................. 5–10 Creating TSF Records...................................................... 5–11 TSF Detail: Function Security Screen ........................................ 5–12

Fields and Descriptions ................................................ 5–12 TSF Detail: Application Security Screen ..................................... 5–13

Fields and Descriptions ................................................ 5–14 Granting or Changing Authority Through Exit Routines (Optional)................ 5–14

Guidelines ............................................................... 5–15 Providing Logon-Level Security ............................................ 5–15

Types of Checking You Can Perform .................................... 5–16 How Passwords are Handled When SECURITY=BUNDL is Specified .......... 5–17 LOGONXT Exit Routine ................................................... 5–18 Modifying User Identifiers and Mail Code Lists at Logon Time ................ 5–18

Providing Mail Code-Level Security ............................................ 5–19 Factors That Determine Reports a User Can View ............................ 5–19 Defining Mail Code-Level Security ......................................... 5–20

VSF Detail Screen ............................................................. 5–21 Fields and Descriptions .................................................... 5–21

Establishing Defaults for Mail Code-Level Security............................... 5–23 Methods of Establishing Defaults ........................................... 5–24 Establishing Defaults Through a VSF Record ................................ 5–24 Establishing Defaults Through the Security Options Screen ................... 5–25

Authorizing Users for Specific Mail Codes ...................................... 5–26 Methods of Authorizing Users ............................................. 5–26

Activating Mail Code-Level Security............................................ 5–27

Chapter 6: Setting Unicenter CA-Bundl Options and Session Defaults Processing Options Screen ..................................................... 6–1

Fields and Descriptions ..................................................... 6–2 Default User Option Screen .................................................... 6–6

Fields and Descriptions ..................................................... 6–7 Options Page 2 Screen......................................................... 6–10

Fields and Descriptions .................................................... 6–11

Contents vii


Setting Unicenter CA-Bundl Processing Options ................................ 6–18 Setting Default User Options for Unicenter CA-Bundl Sessions ................... 6–19 PF Definitions Screen ......................................................... 6–20

Fields and Descriptions ................................................... 6–21 Assigning Unicenter CA-Bundl Commands to PF Keys .......................... 6–21

Chapter 7: Exit Routines Unicenter CA-Bundl Exit Routines ...............................................7–1 Input Page Exit Routine.........................................................7–1

Rules for Writing an Input Page Exit Routine..................................7–2 Additional Information About the Input Page Exit Routine .....................7–4 Additional Information about SAMPEX2M Exit, Line Limit Controls ............7–9

Output Exit Routines ......................................................... 7–10 Device Control Exit Routine ............................................... 7–10 Banner Page Exit Routine.................................................. 7–11 Output Page Exit Routine ................................................. 7–11 Identifying Your Exit Routines for Unicenter CA-Bundl ...................... 7–12 Overriding Exit Routines for Particular Devices ............................. 7–12 Rules for Writing an Output Exit Routine ................................... 7–13 How Unicenter CA-Bundl Calls Output Routines............................ 7–14 Purpose of First and Second-Level Indicators................................ 7–14 Indicator Values for the Device Control Exit Routine ......................... 7–14

First-Level Indicator .................................................. 7–15 Second-Level Indicator ................................................ 7–15

Indicator Values for the Banner Page Exit Routine ........................... 7–16 First-Level Indicator .................................................. 7–16 Second-Level Indicator ................................................ 7–16

Points about the Sequence of Output Distribution ........................... 7–18 Description of the Flow Diagram........................................... 7–18 Additional Information about the Device Control Exit Routine................ 7–19 Additional Information about the Banner Page Exit Routine .................. 7–21 Additional Information about the Output Page Exit Routine .................. 7–22

viii Getting Started


Online Security Exit Routines .................................................. 7–23 Types of Online Security Exit Routines ...................................... 7–24 Logon Security Exit Routine................................................ 7–24 Logoff Security Exit Routine ............................................... 7–24 Mail Code Security Exit Routine ............................................ 7–25 View Print Security Exit Routine............................................ 7–25 Application Security Exit Routine........................................... 7–25 Administrative Record Access Security Exit Routine.......................... 7–25 Rules for Writing an Online Security Exit Routine ............................ 7–26 Comment: Sel, Type, and Action Allowed ................................... 7–27

Coding a Logon Security Exit Routine .......................................... 7–27 Coding a Logoff Security Exit Routine .......................................... 7–30 Coding a Mail Code Security Exit Routine....................................... 7–31 Coding a View Print Security Exit Routine ...................................... 7–33 Coding an Application Security Exit Routine .................................... 7–35 Coding an Administrative Record Access Security Exit Routine ................... 7–37 Coding a TSO Report Access Logging Exit Routine............................... 7–39 Coding the Cooperative Processing Logon Security Exit Routine .................. 7–41

Appendix A: Disk Space Allocation Disk Space Allocated to Page Data and View Page Files .......................... A–1 Factors in Projecting DASD Requirements for Page Data Files ..................... A–2

Extended Addressability for the Unicenter CA-Bundl VSAM Files ............. A–3 Managing Space Effectively.................................................... A–3 Unicenter CA-Bundl Files ..................................................... A–4

Distribution Index Files.................................................... A–4 Control Table Files ........................................................ A–5 Storage Table Files ........................................................ A–7

Index

Introduction 1–1


Chapter

1 Introduction

This chapter provides a summary of the key changes included in the Unicenter CA-Bundl 5.0 release as well as introductory information about this guide and an overview of the Unicenter CA-Bundl installation process.

Unicenter CA-Bundl 5.0 Documentation The following documentation is provided with Unicenter CA-Bundl 5.0:

Documentation Format

Unicenter CA-Bundl Getting Started PDF and printed

Unicenter CA-Bundl Administrator Guide PDF

Unicenter CA-Bundl Product Overview PDF

Unicenter CA-Bundl Release Summary PDF

Unicenter CA-Bundl User Guide PDF

Unicenter CA-Bundl VTAM View System Guide PDF

Unicenter CA-Bundl 5.0 Documentation

1–2 Getting Started


Downloading the Documentation

Unicenter CA-Bundl is distributed on two cartridges, a product cartridge, and a documentation cartridge. The product cartridge allows you to install Unicenter CA-Bundl or apply cumulative maintenance.

The documentation cartridge contains Unicenter CA-Bundl 5.0 documentation in PDF format. The documentation cartridge will be replaced as documentation updates are incorporated into the existing documentation set.

To download CAI.SAMPJCL from the documentation cartridge, do the following:

1. Edit and execute the following JCL:

//UNLOAD JOB (account),’name’,MSGCLASS=a,CLASS=a //COPY EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=* //SYSUT1 DD DSN=CAI.SAMPJCL, // DISP=(OLD,KEEP,KEEP), // UNIT=xxxx, <== CART UNIT // DCB=DEN=4,LABEL=(9,SL), // VOL=SER=CCxxxD, <== CART VOLSER //SYSUT2 DD DSN=cai.ccxxxx.pds, <== USER PDS // DISP=(NEW,CATLG,DELETE), // UNIT=SYSDA,SPACE=(3120,(401,40,20),RLSE) //SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(1,1)) //SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(1,1)) //SYSIN DD * COPY INDD=SYSUT1,OUTDD=SYSUT2 /* //

2. To download the PDF files, execute SAMPJCL member CC50PDF.

Note: Use binary file transfer when transferring the PDF files to the Desktop/PC environment.

Contacting Technical Support

Introduction 1–3


Viewing PDF Documentation

Unicenter CA-Bundl PDF (Portable Document Format) documentation has been optimized for use with the Adobe Acrobat Reader. You can download Adobe Acrobat Reader at http://www.adobe.com/products/acrobat which will allow you to view and print PDF files.

Related Documentation

See any of the following documents for more information about Unicenter CA-Bundl:

Unicenter CA-Balancing System Guide

Unicenter Output Management Document Viewer User Guide

Unicenter Output Management Web Viewer Getting Started (intranet or internet access)

CA Common Services Getting Started (formerly Unicenter TNG Framework for OS/390)

IBM AFP Workbench for Windows: Technical Reference (Online)

Adobe Systems Inc. Type Manager User Guide (Microsoft Windows version)

Contacting Technical Support For technical information about Unicenter CA-Bundl, visit the Computer Associates Technical Support web site at http://esupport.ca.com.

Technical Support is available 24 hours a day, 7 days a week. For assistance, contact your local Computer Associates Technical Support Center.

http://www.adobe.com/products/acrobat

http://esupport.ca.com/

Summary of Product Changes



Summary of Product Changes The following is a list of the key changes included in Unicenter CA-Bundl 5.0:

1. Added Facility to Reduce Archive Index File Size

Unicenter CA-Bundl 5.0 supports eleven (11) archival index files (AIF and AIF0-9). DPMB074, a split utility program, is provided to split the current archive index file (AIF) into a maximum of eleven files. This provides greater processing flexibility for the Unicenter CA-Bundl system.

A split control report only option has been provided in the DPMB074 program to assist you in planning your space requirements for the new split files. See the chapter “Using and Scheduling Unicenter CA-Bundl Jobs and Programs” in the Unicenter CA-Bundl Administrator Guide for more information about the Unicenter CA-Bundl program, DPMB074.

2. New Online Archive Status Screen

A new Archive File Status screen has been added as option #7 to the Unicenter CA-Bundl 5.0 “Operations Menu.” The AIF and AIF0-9 record counts and date ranges are maintained in the Unicenter CA-Bundl System File (BSF) and displayed on this new screen. The screen is updated whenever online users or batch utilities either add or delete records from the Archive Index Files.

3. Improved Archival Retrieval Performance

Online retrieval of archive indexes is much faster once the split of the archive index files is complete. The split archive index file (AIF and AIF0-9) will contain a specified date range of records. By using the date range information, Unicenter CA-Bundl can position the file directly to the desired year range eliminating lengthy searches.

Date checks have been added to the online archival program to reduce the amount of time needed to fill up your screen when displaying the archive indexes available to your user ID.


Introduction 1–5


The Date Filter Span on the User Options Panel (page #2) is not used for the Archive Report Selection screen in Unicenter CA-Bundl 5.0.

4. Improved Archive Recovery Options Added to DPMB037

DPMB037 is the Unicenter CA-Bundl AIF (Archive Index File) disaster recovery program. Unicenter CA-Bundl 5.0 has added more selection criteria by the date, application, and report ID to allow selective restoration of archive indexes from the archive tape.

For more information about the Unicenter CA-Bundl program, DPMB037, see the chapter “Using and Scheduling Unicenter CA-Bundl Jobs and Programs” in the Unicenter CA-Bundl Administrator Guide.

5. New Online User Reprint Status screens

All online requests for archive reprints are shown in a separate Reprint Status screen provided for each user. Each user can quickly review and change the original request using the Reprint Status screen. All archive reprint or reload requests that are pending completion or placed on hold by the Unicenter CA-Bundl Administrator will be shown. Completed requests are deleted from the screen.

6. Online Operations Reprint Status Screens

A new online Operations Reprint Status screen is provided for the Unicenter CA-Bundl administrator. The screen is accessed from the Unicenter CA-Bundl Operations Menu screen by selecting option #6, Reprint Requests.

All requests made since the last clean of the RIFO file are displayed on the screen. The status of the reprint requests for all users is shown on the screen.




7. Additional Reprint Processing Options

A new program, DPMB005A, has been added to provide more versatility with additional processing options for reprint requests. Our new reprint job is executed in CC50J005, the reprint job stream and CC50J029, the End-of-Day Processing job stream. See the chapter “Using and Scheduling Unicenter CA-Bundl Jobs and Programs” in the Unicenter CA-Bundl Administrator Guide for the new PARM options provided in the Unicenter CA-Bundl program, DPMB005A.

8. z/OS 1.2 expansion to handle job numbers greater than 99,999

Various CA-Bundl 5.0 system changes where made to support the expansion of the job number to eight positions.

Expansions where made to the CA-Bundl online screens to provide the eight positions of job number. However, special handling was necessary on the Archive Selection List and the Reprint Status screens to support the larger job number display.

A Job Number Flag field has been added to the Processing Options Screen to control the display of job number on the Archive Selection List and Reprint Status screens.

For more information about this new field, see the topic Processing Options Screen in the chapter “Setting Unicenter CA-Bundl Options and Session Defaults.”


Introduction 1–7


9. The Collector, STCBUNDL, limits the number of lines collected

Two new parameters have been added to the collector parameters, MAXLINES and MAXOPT.

The input sample page exit program is used to control the collector line limits. This input page exit can be modified, as required, to handle special situations or specific job exceptions. See the chapter “Using and Scheduling Unicenter CA-Bundl Jobs and Programs” in the Unicenter CA-Bundl Administrator Guide for more information about the Unicenter CA-Bundl program, STCBUNDL.

10. CA LMP Support

Unicenter CA-Bundl 5.0 requires the use of the CA License Management Program (CA-LMP) for authorization checking. CA-LMP is a standardized approach to the tracking of licensed software that uses common real-time enforcement software to validate the user’s configuration.

CA-LMP replaces the Authorization statement found in AUTH member in the Unicenter CA-Bundl CNTL library.

Unicenter CA-Bundl uses the CAI Resource Initialization Manager (CAIRIM) portion of Unicenter TNG Framework for OS/390. You must install CA Common Services before you can run Unicenter CA-Bundl. CAIRIM prepares the operating system for Computer Associates products and components, and then executes them.

11. DPMB075, the AIF Remerge program

Program DPMB075 is provided in Unicenter CA-Bundl 5.0 to re-merge your AIF and AIF0-9 files into a new AIF file. The BSF split information record is updated and reset to reflect the merge of the AIF files. See the chapter “Using and Scheduling Unicenter CA-Bundl Jobs and Programs” in the Unicenter CA-Bundl Administrator Guide for more information about the Unicenter CA-Bundl program, DPMB075.




12. Unicenter CA-Bundl 5.0 is now installed using SMP

SMP is a tool that provides a simplified, yet accountable approach to MVS product integrity. It controls the installation and all subsequent maintenance of MVS products, as well as providing a log of all system activity. The primary goal of SMP processing is the stability of the running libraries.

13. New Online Reprint Request File – RIFO

The new RIFO file in Unicenter CA-Bundl 5.0 contains the archive reload or reprint requests. The RIFO has a new key structure to support the online reprint status screens for Unicenter CA-Bundl 5.0

A conversion program, DPMB073, is provided in Unicenter CA-Bundl 5.0 to convert the RIF file from CA-Bundl 4.9 to the new RIFO format. The conversion is not needed if all CA-Bundl v4.9 reprint requests have been completed.

14. New Processing Parms Added To Archive Clean Job streams

New processing parms were added to allow greater processing flexibility after the split of the AIF file is run. See the chapter “Using and Scheduling Unicenter CA-Bundl Jobs and Programs” in the Unicenter CA-Bundl Administrator Guide for more information about the Unicenter CA-Bundl programs, DPMB007 and DPMB027.


Introduction 1–9


15. Greater Processing Flexibility for Archive Consolidation

A new processing PARM was added to the consolidation program, DPMB019. This PARM allows you to specify which AIF files are to be input to the consolidation.

If you have split the AIF into separate files using the DPMB074 program, you can process the AIF0-9 files on a separate cycle from the current AIF file. Therefore, the archive files can be consolidated by year range. The consolidation frequency of the previous years archive data (AIF0-9) can be determined separately from the current year archived data (AIF).

The processing performance of the consolidation will be improved greatly when the AIF only is processed for consolidation. The AIF0-9 files can be consolidated in a separate run or cycle.

16. Program DPMB008, View File Clean, Control Report Only Option

Program DPMB008 can be run to produce a VPF0-9 control report regarding the status of the view page files. No clean of the VIF or VPF0-9 files will be done when this report option is coded.

17. Unicenter CA-Bundl VTAM Administrations and View

The Unicenter CA-Bundl system tables can be accessed via VTAM by specifying DATA(BUNADMN) at logon. The message, “BND1805 BUNADMN MODE, DATA ENTER USERID AND PASSWORD” is displayed upon logon. Enter your user ID and password to complete the logon process.

The default mode is Unicenter CA-Bundl View-only access via VTAM. It is not necessary to specify session DATA(BUNVIEW) for view-only access.

However, session DATA(BUNVIEW) is supported at logon for view-only access. The message “BND1806 BUNVIEW MODE, ENTER USERID AND PASSWORD” is displayed upon log on. Enter your user id and password to complete the log on process.

Conventions Used in this Guide



Generally, only Unicenter CA-Bundl administrators will have access to the Unicenter CA-Bundl system tables. Therefore, only administrators will specify the session DATA(BUNADMN) at logon.

Conventions Used in this Guide The following conventions apply throughout this guide:

PF Keys Programmable function keys, referred to as PF keys, are represented by the uppercase letters PF followed by one or two digits:

PF1

PF12

Note: On most keyboards, PF keys are located either along the top or to the right side of the main keys on the keyboard. PF keys are usually marked PF or simply F followed by a digit (for example, PF1 or F1).

Enter Key The word Enter represents any of the following keys marked on your keyboard:

ENTER, Enter, or enter

RETURN, Return, or return

↵, ↵ Enter, or ↵ enter

Special Typeface: Examples

Text shown in the Palatino Bold typeface (for example, DEVICE ID => FICHE) indicates the actual text you type, enter, or see on a Unicenter CA-Bundl screen, data set, or in some other input medium.

Conventions Used in this Guide

Introduction 1–11


Commands Commands supported via the online facility are represented by uppercase letters, as shown in the examples below:

HELP

ADD

DOWN

Variables Italic text shown with a command indicates a user-defined variable where you provide an actual value or information in its place. For example, the variable n in the keyword BDn represents a Unicenter CA-Bundl date format that you specify when creating Unicenter CA-Bundl distribution rules using keywords. You enter a number between 1 and 5 for n in the BDn keyword. The number corresponds to the following formats (where m=month, d=day, y=year):

n Date Format

1 mm/dd/yy

2 dd/mm/yy

3 yy/mm/dd

4 yy.ddd (Julian)

5 yyyy.ddd (Julian)

Introducing Unicenter CA-Bundl 2–1


Chapter

2 Introducing Unicenter CA-Bundl

This chapter is an overview of the Unicenter CA-Bundl installation process. It also provides information for using the System Modification Program/Extended (SMP/E) to install Unicenter CA-Bundl.

Overview of the Unicenter CA-Bundl Installation Process

Unicenter CA-Bundl requires the CAI Resource Initialization Manager (CAIRIM), one of the CA Common Services, and installs under SMP/E. Before you install Unicenter CA-Bundl, you must prepare your system, assemble your materials, and then follow the installation steps in order. Use the following list as a guide for the installation process:

1. Make sure that the CA Common Services are installed on your system and that the required hardware, software, and libraries are prepared.

Unicenter CA-Bundl uses the CAIRIM portion of the CA Common Services. CAIRIM prepares the operating system for Computer Associates products and components, then executes them. See the chapter “System Requirements” for specific information.

2. Assemble the installation materials.

The machine-readable program materials required for installation are distributed as a multi-file installation tape in SMP format.

Installing Under SMP/E



For more information, see the topic Unicenter CA-Bundl Installation Materials in the chapter “System Requirements.”

3. Install Unicenter CA-Bundl using SMP/E.

See the chapter “Installing Unicenter CA-Bundl” for a detailed list of the steps users must perform.

4. Use options and initialization parameters to customize Unicenter CA-Bundl according to the needs of your site, as follows:

Install one of the following online interface options:

– TSO

– VTAM

– Advantage CA-Roscoe

– CICS

See the chapter “Installing Unicenter CA-Bundl” for more information.

Installing Under SMP/E You must use SMP/E to perform product installation, tailoring, and maintenance. The following section describes the primary SMP/E operations that you must perform to install Unicenter CA-Bundl.

Installing Under SMP/E

Introducing Unicenter CA-Bundl 2–3


Major SMP/E Operations

SMP/E performs three major operations (listed below) when a product is installed or maintained. These operations manage a structure wherein a given product is present in two places: distribution libraries and target system libraries.

The distribution libraries are only used for maintenance operations; the product executes from the target system libraries.

The operations performed are as follows:

RECEIVE processing

The installation tape is loaded by SMP into temporary data sets. If an error is detected or you want to stop the process at this point, a REJECT operation may be run, which reverses any actions performed during RECEIVE processing.

APPLY processing

During APPLY processing, SMP performs the operations dictated by the modification control statements (MCS), and updates the target system libraries. The user may then test the modification. If the installation is to be aborted at this point, a RESTORE operation can be run to restore the system libraries from the distribution libraries.

ACCEPT processing

When the ACCEPT operation is run, the modification is permanently placed in the distribution libraries.

Important! There is no direct way to undo the modification once you run ACCEPT.

System Requirements 3–1


Chapter

3 System Requirements

This chapter provides the requirements for installing and running Unicenter CA-Bundl in the following topics:

CA Common Services

Unicenter CA-Bundl and CA-DRAS (Demand Repository Access System)

Installation materials

Hardware and software requirements

Library authorization

CA Common Services CA Common Services must be installed or maintained at the genlevel indicated on the Unicenter CA-Bundl cover letter before you can use the CAIRIM, CA-LMP, and CA-LServ components. See the CA Common Services Getting Started for more information.

CAI Resource Initialization Manager (CAIRIM)

CAIRIM is the common driver for a collection of dynamic initialization routines that eliminate the need for user SVCs, SMF exits, subsystems, and other installation requirements commonly encountered when installing systems software. CAIRIM prepares the operating system for Computer Associates products and components, then executes them.

CA Common Services



CAIRIM performs the following tasks:

Obtains SMF data

Verifies proper software installation

Installs MVS interfaces

Automatically starts up Computer Associates products and other vendor products

Proper timing and order of initialization

Note: Unicenter CA-Bundl requires CAIRIM to run the required CA-LMP.

CA-LMP

CA-LMP (Computer Associates License Management Program) is a standardized automated approach to the tracking of licensed software that uses common real-time enforcement software to validate the user‘s configuration. CA-LMP reports on activities related to the license, usage, and financial activity of program solutions.

CA-LMP features include the following:

A common key data set that can be shared among many CPUs

The use of “check digits“ to detect errors in transcribing key information

Execution keys that can be entered without affecting any Computer Associates software solution already running

No special maintenance requirements

CA-LServ

If CA-LServ has not been installed on your system, you must do so before proceeding with this installation. See your cover letter and the CA Common Services Getting Started for detailed instructions.

Unicenter CA-Bundl and CA-DRAS



Unicenter CA-Bundl and CA-DRAS Beginning with Unicenter CA-Bundl 5.0, the Unicenter CA-Bundl cooperative processing agents are included on the system tape and SMP/E installation. Using Unicenter Output Management Document Viewer and Unicenter Output Management Web Viewer, the Unicenter CA-Bundl cooperative agents work with CA-DRAS to provide access to your Unicenter CA-Bundl mainframe reports from your PC. Unicenter CA-Bundl reports can be accessed without requiring download by using CA-DRAS, Unicenter CA-Bundl cooperative agents and CA Common Services CCI (Common Communication Interface).

CA-DRAS is designed as an MVS output management server that is application or product independent. SQL requests for report data are received via the CA Common Services CCI and the Unicenter CA-Bundl agents invoked to read the Unicenter CA-Bundl database.

Installation Requirements

A summary of the Unicenter CA-Bundl and CA-DRAS installation requirements is listed below:

Mainframe

Unicenter CA-Bundl cooperative agents

CA-LServ 3.5 TL98010 or above

CA-DRAS 1.0 9910 or above

CA Common Services CCI R1.1 9611 or above

TCP/IP, OS/390, IBM, Interlink

Unicenter CA-Bundl Installation Materials



PC Environment

See the Unicenter Output Management Document Viewer and Unicenter Output Management Web Viewer documentation for PC environment requirements.

CA-DRAS and installation are separate and must be specifically requested. For more information, see the CA-DRAS Installation and Operation Guide.

Unicenter CA-Bundl Installation Materials A standard label magnetic tape containing the Unicenter

CA-Bundl SMP/E files referred to as the product tape. The Volser number is CCyymm (Unicenter CA-Bundl, Genlevel year and month). The tape contains the following files:

− DSN=CAI.SAMPJCL (File number 9)

An unloaded PDS that contains the entire sample JCL referred to in this document; pertains to the installation and execution of Unicenter CA-Bundl. Load via IEBCOPY.

− DSN=SMPMCS (File number 32)

This file contains the SMP modification control statements (MCS) used by SMP/E to install Unicenter CA-Bundl.

− Files beyond 32 are the SMP/E RELFILES that SMP/E will download to disk during RECEIVE processing.

Complete documentation set for Unicenter CA-Bundl. See the chapter “Introduction” for the list of documents.

Hardware Requirements



Hardware Requirements The following tables list the amount of disk space needed to install the Unicenter CA-Bundl target and distribution libraries. Use the tables to estimate the storage required for both libraries.

Target Libraries

Library Name Blksize Blocks Dir Blks Description

CAI.CAILIB 6144 4200 100 Common load library

CAI.CAIPROC 3120 50 2 Common procedure library

CAI.PPOPTION 3120 1500 100 Common options library

CAI.CAISRC 3120 330 4 Common source library

CAI.CAIMAC 3120 940 100 Common macro library

CAI.CAIISPP 3120 30 5 Common ISPF panel library

CAI.CAIMAP 3120 1500 50 Common view panels (English)

CAI.CAIRPT 4788 120 2 Sample Reports

CAI.CAICLIB 3120 50 2 Common clist library

WARNING! Do not reblock the libraries listed above–storage problems could occur.

Distribution Libraries

Library Name Blksize Blocks Dir Blks Description

CAI.BNDL.CCC50MLD 3120 1330 150 Macro library

CAI.BNDL.CCC50LLD 6144 580 75 Load library

CAI.BNDL.CCC50ILD 3120 10 5 ISPF library

CAI.BNDL.CCC50RLD 4788 50 2 Report library

Software Requirements



Software Requirements

Unicenter CA-Bundl 5.0 Component SYSMODs

SYSMOD Description

C$V5000 Unicenter CA-Bundl base function for the product component

CA Common Services Component

Component Description

CS91000 CAIRIM—supports CA LMP

Optional CA-DRAS Component

Component Description

CHF1000 CA-DRAS 1.0 Data Repository Access

Required for use with CA-DRAS agents for Unicenter CA-Bundl 5.0, Unicenter Output Management Document Viewer, and Unicenter Output Management Web Viewer.

Library Authorization



Library Authorization Unicenter CA-Bundl contains authorized programs. To run successfully, these programs must be executed from an authorized library. We recommend that you authorize the CAI Common Load Library, CAILIB.

Note: If other Computer Associates products have been installed, this library may already be authorized.

To authorize CAILIB, modify the appropriate member IEAAPFxx in SYS1.PARMLIB to add an entry for CAILIB as follows:

CAI.CAILIB xxxxxx,

where:

CAI.CAILIB is the data set name for the CAI Common Load Library

xxxxxx is the volume serial number on which it resides. An IPL may be necessary to complete the authorization.

Installing Unicenter CA-Bundl 4–1


Chapter

4 Installing Unicenter CA-Bundl

This chapter provides information about how to install Unicenter CA-Bundl for the first time or upgrade from a prior release. It includes JCL and CA Common Services considerations.

Preparing for Installation To install or upgrade Unicenter CA-Bundl, load all necessary data sets and information onto your system from the distribution tape supplied by Computer Associates.

CA-DRAS Agent Support

“Cooperative processing” Unicenter CA-Bundl agents are available for Unicenter CA-Bundl Release 5.0. These agents work with CA-DRAS to provide report viewing without requiring download with Unicenter Output Management Document Viewer and Unicenter Output Management Web Viewer.

CA Common Services Considerations

If all the services in CA Common Services have been installed at your site, you can skip this section. Otherwise, be aware that CA Common Services is delivered separately and the documented prerequisite components must be installed before you continue with the installation or attempt to execute Unicenter CA-Bundl.

Preparing for Installation



Note: See the Unicenter CA-Bundl cover letter for the Genlevel.

CAIRIM and CA-LServ are the only components required for Unicenter CA-Bundl 5.0. See your CA Common Services documentation for more information. Do the following:

1. Check to make sure that your system meets all the requirements listed in the chapter “System Requirements.”

2. When you get to step 8, supply the LMP code.

Note: Installing CA Common Services is a standard SMP procedure.

Unicenter CA-Bundl Upgrade Considerations

All new JCL is required because of changed JCL and naming conventions.

Installation Steps

Note: Be aware that if you are upgrading from a prior release of this product, several of the steps listed below will have modifications. See the topic Upgrading CA-Bundl 4.9 to Unicenter CA-Bundl 5.0 later in this chapter for a list of the modifications.

Before you begin the installation, review the following list, then use it as a checklist during the installation.

Step 1. Complete the Unicenter CA-Bundl Customization Worksheet

Step 2. Load the Installation Sample JCL (SAMPJCL) Library

Step 3. Allocate Libraries

Step 4. Customize the SMP/E Procedure

Step 5. RECEIVE the Services

Step 6. APPLY the Services

Step 7. Authorize Program Load Libraries

Step 1: Complete the Customization Worksheet



Step 8. Enter the LMP Code

Step 9. Tailor the execution JCL (SAMPJCL Library)

Step 10. Tailor the procedures

Step 11. Initialize VSAM files

Step 12. Install the CICS Option (optional)

Step 13. Install the Advantage CA-Roscoe Option (optional)

Step 14. Install Unicenter CA-Bundl VTAM View (optional)

Step 15. Install the TSO interface (optional)

Step 16. Set Up CA-LServ to Execute Unicenter CA-Bundl

Step 17. Test Your Unicenter CA-Bundl Installation

Step 18. Create Production VSAM Files

Step 19. ACCEPT the Services (optional)

Step 20. Use a single file server with more than one Unicenter CA-Bundl system

Step 1: Complete the Customization Worksheet This worksheet is designed to provide the key information that you will need to customize the CAI.SAMPJCL, CAI.PPOPTION, and CAI.CAIPROC libraries.

The file naming conventions and VSAM file configurations vary from site to site. Symbolic values are provided in the Unicenter CA-Bundl 5.0 CAI.SAMPJCL libraries to make the customization easier. The CAI.SAMPJCL naming conventions have changed to new Computer Associates standards for Unicenter CA-Bundl 5.0. The first four characters of the CAI.SAMPJCL member name are now CC50 followed by the standard identifier that was present in CA-Bundl 4.9 (for example, CC50J004, archive).




The worksheet will assist you in preparing the information needed to customize your Unicenter CA-Bundl JCL. Whether you plan to use the customization clist (CC50CUST) or update the JCL manually, the worksheet will be helpful in listing the information required. See Step 9: Tailor the Execution JCL for more information about how to use the customization clist and manually tailor the JCL.

Note: Later in this chapter, you will have to choose to either run the customization clist or manually update the JCL and PPOPTION members. At that time, you will need to determine how large to make your VSAM files. See the appendix “Disk Space Allocation” for more information.

Unicenter CA-Bundl Customization Worksheet

You will need the following information to customize your Unicenter CA-Bundl installation:

Description Default Value to be Used

Enter prefix value for the Unicenter CA-Bundl SAMPJCL library.

CAI

Enter high-level qualifier for the Unicenter CA-Bundl SMP/E libraries (for example, CAI.PPOPTION, CAI.CAIRPT, CAI.CAILIB, and so on).

CAI

Enter high-level qualifier for Unicenter CA-Bundl VSAM file name (for example, CAICC50.DPMFBSF).

CAICC50

If your installation has a TSO command which will clear the display screen, enter the command (for customization clist execution only).

None




Enter job card information for JCL below:


1:5 character job name prefix CC50J

Accounting information none

Programmer name none

Job class for batch jobs A

MSGCLASS X

NOTIFY none

Enter JES class information below:


Input JES class 5

Output JES class X

Enter unit name information below:


Tape device CART

Temporary data sets SYSDA

Enter volser information below:


DASD volser for CIF file SYSDA

Tape volser for CC50JBAK VOLSER

Unit name for CC50JCHK VOLSER

DASD volser for CC50JMSG SYSDA




Enter Archive Tape File information below:


GDG DSNAME (OMIT GDG QUALIFIER) SMPPREF. ARCH

ARCHIVE MODEL NAME SMPPREF. MODEL

Enter “TEST” or “PROD” for CC50J099 PARM TEST

Enter CA-LSERV subsystem information below:


Subsystem name LSRV

Unicenter CA-BUNDL file prefix DPMF

CA-LSERV load library SMPPREF. CAILIB

Enter the following information:


Enter CA-BUNDL 4.9 VSAM file prefix CAI.BUNDL49

Enter Unicenter CA-BUNDL 5.0 VSAM file DASD volsers below: (16 maximum, separated by commas)

Step 2: Load the Installation Sample JCL (SAMPJCL) Library (Required)



Note: At least two DASD volumes are recommended for VSAM space allocation. The VSAM file definitions in the CAI.PPOPTION library have been preset for small testing volume. Review the VSAM file definitions in the CAI.PPOPTION library, after initial testing.

Step 2: Load the Installation Sample JCL (SAMPJCL) Library (Required)

Unicenter CA-Bundl is installed via SMP/E. The standard cartridge tapes included in this package contain all the data necessary to install Unicenter CA-Bundl. Do the following before you install Unicenter CA-Bundl:

WARNING! If you have a set of tailored SAMPJCL from another release of Unicenter CA-Bundl, do not put the later JCL release in the same data set.

1. Load the SAMPJCL (sample JCL) library from the tape.

The DSN=CAI.SAMPJCL file is in IEBCOPY unloaded format and is the ninth file on the product tape.

2. Use the following JCL as a model to load the sample JCL library to DASD.

//LOAD EXEC PGM=IEBCOPY,REGION=256K //SYSPRINT DD SYSOUT=A //SYSUT1 DD DISP=(OLD,KEEP), // DSN=CAI.SAMPJCL, // UNIT=TAPE, <== generic tape // VOL=SER=CCyymm, <== CCyymm (Bundl, gnlv yr, mn) // LABEL=(9,SL), (product tape) // DCB=DEN=4 //SYSUT2 DD DISP=(NEW,CATLG,DELETE), // DSN=CAI.CC50.SAMPJCL, <== your DSN // UNIT=SYSDA, <== your generic DASD // VOL=SER=XXXXXX, <== permanent DASD volser // SPACE=(3120,(100,20,2)), <== min space req’d // DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB) //SYSUT3 DD UNIT=SYSDA, // SPACE=(CYL,(5,5)) //SYSUT4 DD UNIT=SYSDA, // SPACE=(CYL,(5,5)) //SYSIN DD * //COPY INDD=SYSUT1, OUTDD=SYST2

Step 3: Allocate Libraries (Required)



3. Customize the JCL members to reflect valid job statements, data set names, and unit and volume serial numbers.

Step 3: Allocate Libraries (Required) The tasks are presented in two sub-steps as follows:

Step 3a allocates the target and distribution libraries.

Step 3b allocates the private SMP/E libraries.

Edit the appropriate member, where necessary.

Note: JES3 users will have to split SAMPJCL member CC50ALC.

Step 3a: Allocate Target and Distribution Libraries

SAMPJCL member CC50ALC allocates all the target and distribution libraries required by Unicenter CA-Bundl during installation and maintenance.

If You Have More Than One Computer Associates Product

Many Computer Associates products have common components and common libraries that may be already installed. Perform a careful analysis before you allocate libraries so that you do not repeat installation steps that have already been completed. Refer to CC50ALC if you have questions about the substitutions performed for the installation procedure.

WARNING! Never change any of the DDnames or the low-level qualifier of the data set names.

Step 3: Allocate Libraries (Required)



All space allocations are given in blocks to allow for compatibility between DASD types. The allocations listed show the minimum amounts required for installing Unicenter CA-Bundl; you can adjust these values for your installation device types. Be sure to allow enough free space for maintenance, the more free space you allocate, the less often it will be compressed during maintenance.

For common libraries already present, be sure there is sufficient space for Unicenter CA-Bundl.

Important! Any currently allocated CAI target libraries may require expansion to accommodate this product. See Hardware Requirements in the chapter “System Requirements” to make sure that the available space in your target libraries will permit a successful APPLY.

Step 3b: Allocate Private SMP/E Libraries

CAINITE5 (in the SAMPJCL library) allocates and initializes a set of private SMP data sets for all Computer Associates products in SMP/E Release 5 format.

CAINITE5 also sets up CAI global, target, and distribution zones for Computer Associates products. Review comments within the member for necessary tailoring. Note that CAINITE5 can be run any number of times to alter defaults.

If you want to test Unicenter CA-Bundl, do the following:

1. Use CAINITE5 to allocate a new set of SMP libraries to install Unicenter CA-Bundl.

2. Perform your tests. When you are satisfied with your testing, reinstall Unicenter CA-Bundl into your existing SMP libraries (this will delete any release of Unicenter CA-Bundl).

Condition Code 4 on the Allocate of CSI step or the Initialize Private Zones step is acceptable.

Note: We recommend private data sets in order to keep Computer Associates products as distinct entities from other SMP data sets.

Step 4: Customize the SMP Procedure (Required)



Step 4: Customize the SMP Procedure (Required) SAMPJCL member CC50SMPE is the model JCL procedure using SMP/E to install this product. Tailor this member and rename as CAICC50. Procedure CAICC50 will be used in subsequent steps. Do one of the following:

Place this procedure into a system or user procedure library.

Access it from SAMPJCL with JCLLIB statements.

Step 5: RECEIVE the Services (Required) Member CC50REC RECEIVEs all FMIDs (functional SYSMODs) of the Unicenter CA-Bundl services.

Edit the JCL to conform to your installation standards.

FMIDs

The FMID that should be received (and later APPLYd and ACCEPTed) is listed below as it pertains to each of the Unicenter CA-Bundl services.

FMIDs: C$V5000

Step 6: APPLY the Services (Required) Member CC50APP APPLYs all the services (functional SYSMODs) of Unicenter CA-Bundl Services to the target libraries.


Note: A return code of 0 from the linkage editor is normal when APPLYing a new function. You must review the APPLY output listing for any abnormalities.

Step 7: Authorize Program Load Libraries (Required)



Step 7: Authorize Program Load Libraries (Required) Add an entry for CAI.CAILIB to member IEAAPFxx of SYS1.PARMLIB to APF-authorize the target library. Note that the authorization will not take effect until the next IPL.

Note: The load modules must reside in an authorized library.

Step 8: Enter the LMP Code (Required) For Unicenter CA-Bundl to initialize correctly, CA-LMP (License Management Program), a CA Common Services’ service, is required. CA-LMP provides a standardized and automated approach to the tracking of licensed software. Check the CA-LMP Key Certificate you received with your Unicenter CA-Bundl installation or maintenance tape.

LMP Key Certificate

Field Contents

Product Name Trademarked or registered name of the copy of Unicenter CA-Bundl licensed for the designated site and CPUs

Supplement Reference number of your license for a particular Unicenter CA-Bundl, 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 Date (MONTH dd, yyyy as in OCTOBER 25, 2002) that your license for Unicenter CA-Bundl expires for the installation and maintenance of the designated Unicenter CA-Bundl

Step 8: Enter the LMP Code (Required)



Field Contents

Technical Contact

Name of technical contact at your site responsible for the installation and maintenance of Unicenter CA-Bundl

The person to whom Computer Associates addresses all CA-LMP correspondence.

Execution Key Encrypted code (known as LMP Code during installation) required by CA-LMP for Unicenter CA-Bundl initialization

Product Code Two-character code that represents Unicenter CA-Bundl

MIS Director Name of the Director of MIS, or the person who performs that function at the 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 ID Code that identifies the specific CPU for which installation of your Unicenter CA-Bundl is valid

CPU Location Building address where the CPU is installed

CA-LMP is provided as an integral part of CAIRIM (Resource Initialization Manager), another TNG Framework for OS/390 service.

The CA-LMP execution key, provided on the key certificate, must be added to the CAIRIM parameters to ensure proper initialization of the Computer Associates software solution.

Step 8: Enter the LMP Code (Required)



Defining the CA-LMP Execution Key

To define a CA-LMP execution key to the CAIRIM parameters, modify member KEYS in OPTLIB data set. The following is the parameter structure for member KEYS. All parameters are required.

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

where:

pp Specifies the two-character product code

For any given CA-LMP software solution, this code agrees with the product code already in use by the CAIRIM initialization parameters for earlier Gen levels of Unicenter CA-Bundl.

ddmmmyy Specifies the CA-LMP licensing agreement expiration date

tttt-mmmm Specifies the CPU type and model (for example, 3090-600) on which the CA-LMP software solution is to run

If the CPU type and/or model require less than four characters, blank spaces are inserted for the unused characters.

ssssss Specifies the serial number of the CPU on which the CA-LMP software solution is to run

kkkkkkkkkkkkk Specifies the execution key needed to run the CA-LMP software solution

This CA-LMP execution key is provided on the Key Certificate shipped with each CA-LMP software solution.

The following example shows a control card for the CA-LMP execution software parameter. Note that the CA-LMP execution key is invalid and provided as an example only.

PROD(VA) DATE(01JAN97) CPU(3090-600 /370623) LMPCODE(52H2K06130Z7RZD6)

Step 9: Tailor the Execution JCL



See the CA Common Services Getting Started for information about defining the CA-LMP execution key to the CAIRIM parameters.

Multiple LMP Codes

Unicenter CA-Bundl consists of the base product, and several components (options) that are purchased separately. Since each component has its own LMP code, you are required to supply an LMP code for each component you purchased.

The following table lists the component product codes:

pp Component Description

PO Unicenter CA-Bundl base product

PU CICS online interface

PV Advantage CA-Roscoe online interface

PY VTAM online interface

Step 9: Tailor the Execution JCL This is the first of several sections that will assist you in tailoring the Unicenter CA-Bundl system JCL, procedures and VSAM cluster definitions.

A customization clist (CC50CUST) is provided in the CAI.SAMPJCL library to assist you in customizing your JCL and VSAM file cluster definitions. See “Step 1: Complete the Customization Worksheet” earlier in this chapter for a complete description of the execution of the customization clist.




Use the answers provided on the worksheet to respond to the questions when running the customization clist. The clist will update and replace the Unicenter CA-Bundl JCL members in the CAI.SAMPJCL and CAI.PPOPTION libraries with the values provided to the clist. It is extremely important that you execute the JCL member CC50CUSC in the CAI.SAMPJCL library to copy the CAI.SAMPJCL and CAI.PPOPTION libraries prior to execution of the clist. The JCL member CC50CUSR in CAI.SAMPJCL is provided so that you can restore these libraries prior to a rerun of the clist.

With the Unicenter CA-Bundl 5.0 release, new naming standards have been adopted for all JCL, VSAM file cluster definitions, and procedures. Please review the member names in the CAI.PPOPTION, CAI.SAMPJCL, and CAI.CAIPROC libraries. The new naming standards include the “CCnn” prefix (for example, CC50). This standard replaces the old “DPM” prefix that was used prior to Unicenter CA-Bundl 5.0.

The following is a list of several key considerations for customizing your execution JCL for Unicenter CA-Bundl 5.0:

The SMP/E prefix is used for the high-level qualifier of the system libraries (for example, CAI.PPOPTION, CAI.CAILIB, and so on)

The high-level qualifier of the VSAM file names is CAICC50.DPMFXXX as delivered. If you want to change it, you can either edit the VSAM clusters and JCL (CC50Jxxx) members in the CAI.PPOPTION and CAI.SAMPJCL libraries or execute the customization clist (CC50CUST) in your CAI.SAMPJCL library. It is suggested that you do not use the same DSNAME as your current production files.

The VSAM file definitions in the PPOPTION library have been preset with initial testing volumes only. A review of the PPOPTION VSAM file definitions will be needed for processing additional volumes.




See the appendix “Disk Space Allocation” for more information about space allocations for your VSAM files and for a complete list of these files and the PPOPTION members that define them.

The Execution JCL is located in the CAI.PPOPTION and SAMPJCL libraries. Procedures are located in the CAIPROC library. Tailor the symbolics to customize your JCL.

The following is a list of the key JCL members in CAI.PPOPTION and CAI.SAMPJCL:

Member Description

CC50CUSC Backup of CAI.PPOPTION and CAI.SAMPJCL libraries

CC50CUSR Restore CAI.PPOPTION and CAI.SAMPJCL libraries

CC50J001 Report Collector

CC50J002 Report Distribution

CC50J02A Special Distribution

CC50J004 Archives Master Index and Page

CC50J005 Reprint job stream

CC50J05B Load archive data to be reprinted (printed on next distribution cycle)

CC50J007* Delete expired archive records

CC50J008 Delete expired view index and view page records

CC50J009 Update Statistical Summary File

CC50J010 Update Statistical Summary File from the PSF Index File

CC50J011 Create SMF records and produce Summary Report




Member Description

CC50J012 Distribution within Job Report

CC50J013 Report of recipients for a report

CC50J014 Mail Code Maintenance

CC50J016 Resequence Report Distribution File

CC50J017 Produce Gummed Labels by Home Code

CC50J019* Archive Consolidation of Tape Files

CC50J026 Shut down active collectors and archive

CC50J029* End-of-day job stream

CC50J030 Clear BSF of active task name

CC50J037 Archive Index Recovery

CC50J038 List Message Log

CC50J073 RIF File Conversion Utility for Unicenter CA-Bundl 5.0

CC50J074* Archive File Split

CC50J74C* Archive File Split, produce Control Report only

CC50J075* Remerge Archive Index File

CC50J080* Index Utility

CC50J085 Insert/Modify Price Record in SSF

CC50J090 Change system date without clearing files

CC50J091 Generate sample reports to JES Spool

CC50J095 Print Statistical Summary Report

CC50J096 Initialize Page and Index Files

CC50J097 Reset View System

CC50J098 List file entries in Control Files

Step 10: Tailor the Procedures



Member Description

CC50J099* Initialize VSAM Files

CC50J99S Initialize and restore AIF, BSF, and AIF0-9 for rerun of CC50J074, archive split

CC50J99T* Initialize Specific Files

*These jobs reference the AIF file and are modified for the AIF split.

Step 10: Tailor the Procedures Tailor the following procedures in CAI.CAIPROC to your site specifications. Either add CAI.CAIPROC to your system procedures, or copy the members to the PROCLIB of your choice.

Note: We do not recommend copying PROCs.

Name Description

CACC50B1 Collection Procedure

CACC50B2 Distribution Procedure

CACC50B3 VTAM View

CACC50B4 Archive File Split Procedure

Step 11: Initialize Test VSAM Files (Required)



Step 11: Initialize Test VSAM Files (Required) CAI.PPOPTION contains members that are used to allocate the VSAM files. You must tailor the following members for your site. See the appendix “Disk Space Allocation” for a complete description of these files and important space considerations when defining them. If you ran the customization clist, you may still want to tailor these members to adjust the space allocations.

Note: Do not change the low-level name for these VSAM files. However, the DDNAME that references the file may be changed if you have different sets of VSAM files. The DDNAME is in the format of a four-digit prefix followed by a three to four-digit suffix. The default prefix is DPMF and the JCL was distributed with this prefix. As an example, the DPMF value in the DPMFAIF DDNAME may be changed to ABCD, making the DDNAME, ABCDAIF. But, the low-level qualifier for the VSAM data set must be DPMFAIF.

Member Name Description

CC50AIF DPMFAIF – Archive Index File

CC50AIF0 to CC50AIF9 DPMFAIF0 – DPMFAIF9

CC50ATF* DPMFATF

CC50BAIF BACKAIF – AIF backup

CC50BSF* DPMFBSF

CC50DSF* DPMFDSF

CC50DTF* DPMFDTF

CC50LGF* DPMFLGF

CC50MAP* DPMFMAP – Screen maps

CC50MCF* DPMFMCF

CC50NAIF NEWAIF

Step 11: Initialize Test VSAM Files (Required)



Member Name Description

CC50PDF0 to CC50PDF9 DPMFAIF0 – DPMFPDF9

CC50PIF DPMPIF

CC50PIF2 DPMPIF2

CC50PSF* DPMFPSF

CC50RDF* DPMFRDF

CC50RIF DPMFRIF

CC50RIFO DPMFRIFO

CC50RPF DPMFRPF

CC50RTF* DPMFRTF

CC50SCH* DPMFSCH

CC50SHF* DPMFSHF

CC50SIF DPMFSIF

CC50SRF* DPMFSRF

CC50SSF DPMFSSF

CC50STF* DPMFSTF

CC50TSF* DPMFTSF

CC50VIF* DPMFVIF

CC50VPF0 to CC50VPF9 DPMFVPF0 – DPMFVPF9

CC50VSF* DPMFVSF

*IMBED keyword has been changed to NOIMBED

To create a new set of VSAM files, follow the steps below. Otherwise, proceed with step 12.

WARNING! The PPOPTION members that are used to define the VSAM files also contain DELETEs for these files. Do not use the same high-level qualifier as your current Unicenter CA-Bundl production files when you tailor these members.

Step 12: Install the CICS Option (Optional)



Initializing New VSAM Files 1. Edit PPOPTION member CC50J099 and tailor it to your

site’s standards. Set the symbolic PROD to TEST (PRMV=’TEST ‘) to load test report definitions. DO NOT use the same DSNAMEs as your current production files. See the warning on the previous page.

2. Edit SAMPJCL member CC50JMAP and tailor it to your site’s standards. Use the same naming conventions as stated in step one above.

3. If CA-LServ is executing, shut it down.

4. Submit CC50J099 and review the output.

5. Submit CC50JMAP and review the output.

6. In step 18, you will upgrade your production files to 5.0.

Step 12: Install the CICS Option (Optional) The CICS Option is an optional Unicenter CA-Bundl software option that you purchase separately that enables CICS users to perform view and administration tasks in Unicenter CA-Bundl.

Did you purchase the CICS option and do you intend to use it in your organization?

If no, skip this section and proceed to step 13.

If yes, continue with step 12 to install the CICS option.

Important! CICS view is not authorized until the first report is collected.

Step 12: Install the CICS Option (Optional)



Installing the CICS Option 1. Determine for CICS immediate prints, if you are going to

use:

a. CICS JES interface using programs, DPMOB50A (admin) and/or DPMOB50V (view)

Note: Determine if you are going to use the CICS Spool User Exit, DPMOSPOL. This exit issues CICS Spool commands using the OUTDESCR parm, providing the flexibility to direct the spooled output to designated areas in a more controlled manner. The source code for DPMDSPOL is included in the CAI.PPOPTION library.

b. Spool writes from MVS using programs, DPMOZ50A (admin) and/or DPMOZ50V (view).

2. Create a PCT (Program Control Table) entry for each transaction created. The basic function of the PCT is to tie together the transaction ID with the program.

A sample PCT entry is presented in CAI.PPOPTION (CC50DPCT).

3. Create a PPT (Processing Program Table) entry for each program to be used (including the Spool user exit, if used). A PPT entry is used to locate programs to be loaded into main storage.

When the CICS option is started up, the PPT is initialized with the address of the load module. A sample PPT entry is presented in CAI.PPOPTION (CC50DPPT).

4. Either concatenate CAI.CAILIB in your CICS startup JCL or copy your programs (selected in step 1 of this procedure) to your CICS load library from CAI.CAILIB.

Note: If you do not use CAI.CAILIB, you will have to repeat this copy after applying maintenance to Unicenter CA-Bundl.

5. Do you want to restrict CICS users from viewing reports distributed through Unicenter CA-Bundl?

Step 13: Install the Advantage CA-Roscoe Option (Optional)



If no, go to Step 13: Install the Advantage CA-Roscoe Option (Optional); you are done with the CICS installation.

If yes, see Providing Mail Code-Level Security in the chapter “Providing Security in Unicenter CA-Bundl” for information about setting up mail code-level security at your organization.

Step 13: Install the Advantage CA-Roscoe Option (Optional)

The Advantage CA-Roscoe option is an optional software option that you purchase separately that enables Advantage CA-Roscoe/ETSO users to perform view and administration tasks in Unicenter CA-Bundl.

Did you purchase the Advantage CA-Roscoe option and do you intend to use it at your organization?

If no, skip this section and proceed to Step 14: Install Unicenter CA-Bundl VTAM View.

If yes, continue with Step 13 to install the Advantage CA-Roscoe option.

Installing the Advantage CA-Roscoe Option for Use with Unicenter CA-Bundl

1. Tailor, move and rename the CC50DROS and CC50DRUS members in the CAI.CAICLIB data set to an Advantage CA-Roscoe option RPF library.

2. Add the DPMOATSO and DPMOTSO programs, and the CAI.CAILIB members to the Advantage CA-Roscoe option eligible program table.

Step 14: Install Unicenter CA-Bundl VTAM View (Optional)



Starting the Unicenter CA-Bundl Online System and End-User Facilities

Execute the CC50DROS RPF to start the Unicenter CA-Bundl online system, and execute the CC50DRUS RPF to start the online end-user facilities.

This procedure is equivalent to executing the Unicenter CA-Bundl clist under TSO.

Before you activate Unicenter CA-Bundl security, you must implement the Unicenter CA-Bundl logon exit routine, DPMS960. See the chapter “Unicenter CA-Bundl Exit Routines“ for more information. At a minimum, the routine must use Advantage CA-Roscoe’s API facility to obtain actual user identifiers and give those identifiers to Unicenter CA-Bundl. Otherwise, Unicenter CA-Bundl uses Advantage CA-Roscoe’s own user identifier.


VTAM View is an optional Unicenter CA-Bundl software option that you purchase separately that enables VTAM users to perform view and administration tasks in Unicenter CA-Bundl.

Did you purchase Unicenter CA-Bundl VTAM View and do you intend to use it at your organization?

If no, skip this section and immediately go to Step 15: Install the TSO Interface.

If yes, continue with Step 14 to install VTAM View.

Installing VTAM View 1. Tailor member CC50VDEF in CAI.PPOPTION.




2. Copy the VTAM application definition from member CC50VDEF in CAI.PPOPTION to the SYS1.VTAMLST data set.

3. Enter the following command:

V NET,ACT,ID=memname

Where memname is the name of the SYS1.VTAMLST member that contains the VTAM definition for Unicenter CA-Bundl VTAM View.

Unicenter CA-Bundl VTAM View is made into a Unicenter CA-Bundl VTAM View application.

4. Modify member CC50VPRM in CAI.PPOPTION, which contains default initialization values for VTAM View.

You can specify two types of values in member CC50VPRM:

SETPARMS initialization statements, which you can specify only in member CC50VPRM; you cannot change these values after you start the VTAM View task

Unicenter CA-Bundl commands, such as SETOPTION, which you can specify either in member CC50VPRM or from an operator’s console (to change command values while VTAM View is executing)

5. Tailor the startup procedure for the VTAM View started task, member CACC50B3 in CAI.CAIPROC.

6. Do you want to restrict VTAM View users from viewing reports distributed through Unicenter CA-Bundl?

If no, proceed to step 15.

If yes, see the topic Providing Mail Code-Level Security in the chapter “Providing Security in Unicenter CA-Bundl” for more information about setting up mail code-level security at your organization.

Note: See the Unicenter CA-Bundl VTAM View System Guide for more information about security and Unicenter CA-Bundl VTAM View.

Step 15: Install the TSO Interface (Optional)



Note: New with Unicenter CA-Bundl 5.0, the general default is DATA(BUNVIEW) to view reports only. To access the Unicenter CA-Bundl administrative files, enter DATA(BUNADMN) at logon. For example, APPLID(BUND50TS) DATA(BUNADMN)

Important! The value specified for ACBNAME in member CC50VPRM must match the value specified in member CC50VDEF.

Step 15: Install the TSO Interface (Optional) Continue with this step if you plan to use the TSO interface to perform view and administration tasks in Unicenter CA-Bundl. Otherwise, skip this step and proceed to step 16.

Installing TSO 1. Modify your TSO logon procedure as follows:

a. If CAI.CAILIB is not in the link list, add CAI.CAILIB to the STEPLIB DD concatenation in your TSO logon procedure.

b. Add CAI.CAICLIB to the SYSPROC DD concatenation in your TSO logon procedure.

Once the above changes are made, your TSO logon procedure should start as follows:

//TSOPROC PROC //TSO EXEC PGM=IKJEF01,DYNAMNBR=50,PERFORM=2 //STEPLIB DD DSN=CAI.CAILIB,DISP=SHR // DD DSN=Other.Load.Libraries,DISP=SHR //SYSPROC DD DSN=CAI.CAICLIB,DISP=SHR // DD DSN=Other.Clist.Libraries,DISP=SHR

2. Modify the following clists in CAI.CAICLIB. The required changes are documented at the beginning of the clist.

CC50CLDL

CC50CLVW

Step 16: Set Up CA-LServ to Execute Unicenter CA-Bundl



Step 16: Set Up CA-LServ to Execute Unicenter CA-Bundl

CA-LServ, a part of CA Common Services, is a master started task that serves as the central control point of, and provides an interface to, Unicenter CA-Bundl processing and scheduling facilities. Do the following to set up CA-LServ to execute Unicenter CA-Bundl:

1. Install CA-LServ on your system.

2. Tailor and submit job CC50JMSG in CAI.SAMPJCL. This job, which is located in SAMPJCL, allocates a message log data set as a function under CA-LServ.

Note: This job allocates only one message log data set. If you want CA-LServ to switch to another log when the first one is filled, edit the JCL for the job to allocate a second data set. See the CA Common Services documentation for more information about defining multiple data sets for a log.

3. Tailor and copy these members from CAI.PPOPTION to the LSERV CNTL data set:

CC50DLDA: Unicenter CA-Bundl file allocations

CC50DLDR: Unicenter CA-Bundl file deallocations

CC50DLDS: Scheduler activation statement

CC50BMSG: New Unicenter CA-Bundl message definitions

Note: Due to Unicenter CA-Bundl 5.0 VSAM file changes, PPOPTION members, CC50DLDA and CC50DLDR, contain several changes:

The new DPMFRIFO file was added

The DPMFRIF file was removed

The DPMFAIF0-9 files for the AIF split option are commented out. Uncomment these files, if you are selecting the AIF split option.

Step 17: Test Your Unicenter CA-Bundl Installation



4. In member LDMPARM of the LSERV CNTL data set, insert the statements INCLUDE CC50DLDA and INCLUDE CC50DLDS.

5. In member LDMMSGS of the LSERV CNTL data set, insert the statement INCLUDE CC50BMSG.

6. Copy, to the LSERV CNTL data set, any jobs that the scheduler will submit for execution.

Note: Ensure that CC50J02A is included in this set of jobs. It is the job for automatic distribution located in PPOPTION.

Step 17: Test Your Unicenter CA-Bundl Installation The Unicenter CA-Bundl job CC50JCHK in SAMPJCL is a test stream that generates test reports, collects and distributes test reports, updates statistical information about Unicenter CA-Bundl, and archives reports. You use this job to determine if you can perform the tasks you most often perform through Unicenter CA-Bundl. The CC50JCHK job tests these Unicenter CA-Bundl procedures and programs:

CACC50B1 (collection)

CACC50B2 (distribution)

DPMB010 (update Statistical Summary File)

DPMB004 (archive)

You can execute CC50JCHK as often as you want.

Follow these steps to test your Unicenter CA-Bundl installation:

1. Start CA-LServ by issuing this MVS START command:

S task parms

Where task represents the name of the CA-LServ started task, and parms represents one or more start-up parameters that you are overriding from the start-up procedure’s JCL.

2. Tailor SAMPJCL member CC50JCHK and submit it.

Step 18: Create Production VSAM Files



3. Access the Unicenter CA-Bundl administration and view screens from any environment in which you have installed them. To do this, execute the Unicenter CA-Bundl view and administration clists from the appropriate environment.

4. When you start the Unicenter CA-Bundl administration screens, review the screens available from the System Options menu.

Note: These screens provide Unicenter CA-Bundl with important settings that are necessary to complete the installation process. The remaining chapters of this guide contain information about screens that provide security and default settings. See the Unicenter CA-Bundl Administrator Guide for information about screens used in a JES.ANY distribution.

Step 18: Create Production VSAM Files If you are installing Unicenter CA-Bundl for the first time, do the following:

1. Bring down CA-LServ.

2. ONLY execute step 4 below to initialize your VSAM files.

3. When you are finished, proceed to Step 19: ACCEPT the Services.

If you are upgrading Unicenter CA-Bundl from a prior release, use the instructions that follow to convert your production VSAM files to Unicenter CA-Bundl 5.0.




Upgrading CA-Bundl 4.9 to Unicenter CA-Bundl 5.0

Review the summary of product changes included in this guide. See Summary of Product Changes in the chapter “Introduction.”

1. Run DPMJ029 (your CA-Bundl 4.9 end-of-day job) followed by DPMJBAK (CA-Bundl 4.9 job) to back up files to tape. At this point, no further CA-Bundl 4.9 processing should be done.

2. Shut down the CA-LServ task(s).

3. If you are NOT going to split your AIF file, proceed with the next step (#4). Otherwise, do the following:

Unicenter CA-Bundl allows you to split your current AIF file into new AIF and AIF0-9 files.

Do the following to determine space requirements for each file:

a. Tailor and run CC50J74C in PPOPTION to obtain a control report on the file split.

b. Review the archived split control report record counts and calculate the DASD space required for the new Unicenter CA-Bundl 5.0 AIF and AIF0-9 files.

c. Modify the PPOPTION members, CC50AIF and CC50AIF0-9, then include the estimated number of records. The CA-Bundl 4.9 AIF file should be used as input. The output AIF and AIF0-9 files are dummy files in the CC50J74C JCL, no split will be performed.

Note: The AIF0-9 files will not grow during the Unicenter CA-Bundl 5.0 processing cycle. As each clean cycle is run, the AIF0-9 files should decrease in the number of records. The AIF will always contain the current year data and grow as new archives (DPMB004) are run. Therefore, you should plan for expansion or room for growth in the CC50AIF VSAM cluster definition.




4. Initialize your VSAM files.

This step will create your Unicenter CA-Bundl 5.0 production VSAM files. Review the VSAM file cluster definitions in the PPOPTION library to define the production naming conventions and space requirements for production processing.

Note: The VSAM file high-level qualifier should be different from the high-level qualifier of your current CA-Bundl 4.9 VSAM file.

Tailor and submit job CC50J099 in SAMPJCL to your site’s standards. Make sure to change the DPMB099 parm from TEST to PROD (for example, PRMV=’PROD’).

Make sure the OUTCLASS is the correct JES default output class for your site. The PROD parm will clear and reset all Unicenter CA-Bundl 5.0 VSAM files with only an initialization record.

a. Tailor and submit job CC50JMAP in SAMPJCL. This will initialize and build the online map files.

b. For CA-LServ, make sure the CC50DLDA, CC50DLDR, CC50DLDS members in CAI.PPOPTION have been changed to point to your Unicenter CA-Bundl 5.0 production files. See Step 16: Set Up CA-LServ to Execute Unicenter CA-Bundl for more information.

5. Tailor and run CC50REPO in SAMPJCL to load the remaining VSAM files to 5.0 from the 4.9 backup tape created in step #1 above.

Note that the BSF file will not be copied from the 4.9 backup tape. You must use the BSF file initialized in step 4 in the CC50J099 job.

Tailor and run CC50REP2 in SAMPJCL to load your 5.0 view files (VIF and VPF0-9) from your 4.9 files.

Step 19: ACCEPT the Services (Optional)



6. If you are not splitting your AIF file, proceed with the next step (#7). Otherwise, do the following:

Tailor and run CC50J074 in PPOPTION to split the AIF file into new AIF and AIF0-9 files. The DPMB074 parm is set to “1” year as the default. The AIF0-9 files will contain one year of archived data and the AIF will contain the current year plus any carryover. AIF0 will contain the oldest year data and AIF1 will contain the next oldest year data, and so on.

Review the space requirements in the CC50BAIF and the CC50NAIF VSAM cluster definitions in the PPOPTION library. The CC50BAIF will be a full backup of the current AIF file. Therefore, the number of records must equal the AIF file into the split. The CC50NAIF is a new AIF file after the split and only the records for the current year will be added to this file by the DPMB074 program.

If you need to rerun the CC50J074 job stream, run the CC50J99S job stream. This job stream is set to restore the AIF from the backup file, CC50BAIF, and reinitialize the BSF and AIF0-9 files with the DPMB099 program.

7. Restart the CA-LServ task.

Step 19: ACCEPT the Services (Optional) WARNING! ACCEPTING the services is not reversible.

Member CC50ACC ACCEPTs all the services (functional SYSMODs) of Unicenter CA-Bundl services to the distribution libraries.


Important! The SET BDY control statement should not be present for SMP 4 users; it has no meaning in SMP 4.

Step 19: ACCEPT the Services (Optional)



Be sure to include any maintenance PTF SYSMODs previously RECEIVEd and received from the cumulative maintenance step. The PTF SYSMODs should be the last in the list of SYSMODs to be ACCEPTed.

ACCEPT Considerations with Pre-Installed Services

If other Computer Associates solutions have been installed, some of these functions may have already been ACCEPTed. If this happens, a non-zero return code occurs. Remove the failing SYSMODs, then resubmit the job.

SMP/E users have the option of specifying REDO on the ACCEPT command statement, and should expect a return code of 8, which in this case, is permissible.

Do the following:

1. Modify the ACCEPT SELECT list accordingly.

2. Submit the job, then verify that the ACCEPT processing ran successfully.

If the SMP ACCEPT completes with a return code greater than 4, then:

Review the output carefully before continuing.

Correct the problem.

Resubmit the job.

Be aware of the following:

The PTF symbolic should be modified in either the SMP procedure or the ACCEPT SAMPJCL member (CC50ACC) to prevent tape allocation, that is, PTF=’DUMMY’.

If you are running SMP 4, remove the SET BDY input card.

Step 20: Using a Single File Server with Multiple Unicenter CA-Bundl Systems




Unicenter CA-Bundl uses the CA-LServ file server component of CA Common Services to access Unicenter CA-Bundl files. When you execute several Unicenter CA-Bundl systems at once (for example, test and production collectors), copies of Unicenter CA-Bundl can access unique sets of files through the same file server.

By default, Unicenter CA-Bundl jobs and users can access files that begin with the prefix DPMF.

Change the clists for TSO, the RPFs for Advantage CA-Roscoe, and the Start task for VTAM:

ALLOC F(DDN$xxxx) DUMMY

Specify a 1-to 4-character DDNAME prefix in place of xxxx.

A USERMOD, member CC50CIC in CAI.SAMPJCL, should be tailored and used to change the DDNAME prefix for different CICS programs.

Example The following is an example of the values you specify to share a file server among tasks.

In this example, the Unicenter CA-Bundl test system and production system request access to different sets of files through the same file server.

The ADDFILE statement for each set of files needs to be listed in the CC50DLDA member in the LSERV CNTL data set.

The DDN$TEST DD DUMMY statement tells a test collector job to access files with DDNAMEs that begin with TEST. The DDN$DPMF DD DUMMY statement tells a production collector job to access files with DDNAMEs that begin with DPMF.




The same file server manages both sets of files, as shown below:

Values for Test Collector JCL: //DDN$TEST DD DUMMY

Values for Production Collector JCL: //DDN$DPMF DD DUMMY

Tasks on CPU

Production Collector

Test Collector

Fileserver

DDprefix= DPMF

DDprefix= TEST

Providing Security in Unicenter CA-Bundl 5–1


Chapter

5 Providing Security in Unicenter CA-Bundl

This chapter describes the different types of security that you can define for Unicenter CA-Bundl and provides step-by-step instructions on how to implement each type of security.

How Security Works in Unicenter CA-Bundl

+ = BU ND L V S F A, B, C

U se r Ide ntifie r V S F D, E, F

L ist o f a llow e d m ail code s A, B, C, D, E, F

A

B

C

D

E

K

L

V IF

A

B

C

E

K

U se r s Re port S e le ction L ist

DP M S 96 2 (optiona l) Allow K

Approva l s

Actua l V IF , M ail Code s

Fa ilure s

DP M S 96 0 (op tiona l) Add Y, Z a nd re m ove D

Re vi se d list o f a llow e d m a il code s A, B, C, E, F , Y, Z

Acce ss S e curity

F ilte r

Types of Security You Can Provide in Unicenter CA-Bundl



Unicenter CA-Bundl first combines mail codes specified in the Bundl view security record in the View Security File (VSF), which authorizes users to access public mail codes and mail lists for view output, with the user’s view security record in the VSF.

Unicenter CA-Bundl then passes the list of allowed mail codes either to the logon security exit routine (DPMS960) or directly to the VIF Access Security Filter. DPMS960 examines and modifies the applications, Unicenter CA-Bundl functions, and mail codes to which users, administrators, and operators have access. The VIF Access Security Filter displays the mail codes.

Optionally, your administrator can set up Unicenter CA-Bundl so that it passes failed mail codes to the mail code security exit routine DPMS962, which, if it is correctly linked, adds mail codes to, or removes mail codes from, the list of VSF mail codes to which Unicenter CA-Bundl users have access. Any failed mail codes that are subsequently approved by DPMS962 are passed to the users’ report selection list. See the chapter “Exit Routines” for a description of the security exit routines.


By default, Unicenter CA-Bundl is unsecured. Anyone can perform Unicenter CA-Bundl administration functions (such as viewing or updating files that control report collection and distribution), and anyone can view the reports Unicenter CA-Bundl distributes. For this reason, consider carefully what type of security you need to define in Unicenter CA-Bundl.




The levels of security in Unicenter CA-Bundl are:

Function-level security restricts access to Unicenter CA-Bundl screens that enable you to perform a related set of functions

You can, for example, restrict access to the Collector and Page Data Files screen, which you use to stop jobs that collect reports for distribution.

Application-Level Security restricts access to administration and operations records by application identifier

You can, for example, restrict Unicenter CA-Bundl users who can access payroll application records.

Note: This type of security restricts access only to records you can add, change, or delete through Unicenter CA-Bundl administration and operations screens. It does not restrict access to view report data.

Logon-level Security restricts access to Unicenter CA-Bundl (for VTAM View users only) and modifies mail codes a user can access.

Mail Code-level Security restricts access to data in reports

For example, you can restrict access to a confidential payroll report by allowing only payroll staff to access the mail codes to which a report is delivered.

Security Options Screen



Security Options Screen The Security Options Screen is used to modify security in Unicenter CA-Bundl. Critical fields for function- and application-level security are shown in bold print.

---------------- CA-BUNDL: Security Options Screen ------------------ Command ==> MASTER Master ADMIN: User ID => TSOUSR1 <- Access to all administration functions SECURITY Mailcode => N <- Access to authorized mail codes only LEVELS: Function => Y <- Access to authorized functions only Application => N <- Access to authorized applications only Restrict MCF Records => N <- Access for authorized applications only MAILCODE Start With => 1 <- First character of mail code MATCH: Length => 7 <- Total number of characters

Fields and Descriptions

Field Description

Master User ID

Specifies the user identifier of a user who is authorized to access and use all Unicenter CA-Bundl operations and screens

If you specify a user identifier other than your own here, do not activate security options until you provide TSF records. Otherwise, you will not be able to access TSF records.

Security Options Screen



Field Description

Function Specifies whether you want to restrict access to Unicenter CA-Bundl functions by restricting access to Unicenter CA-Bundl screens

Specify N for no and Y for yes. If you do not specify a value in this field, N for no, is used by default.

Application Specifies whether you want to restrict access to records for particular applications

Specify N(o) or Y(es). If you do not specify a value in this field, N for no, is used by default. When you specify Y for yes, Unicenter CA-Bundl restricts access to records by application identifier on these screens:

ATF screens

RTF screens

RDF screens

SRF screens

STF screens

Operations Menu screens

Modifying a Security Options Record



Field Description

Restrict MCF Records

Specifies whether you want to restrict access to particular MCF records, which define mail codes

If you specify Y(es) in this field, the applications named on a user’s TSF record are compared with the name of mail codes on MCF records. When these values match, the user can access the MCF record. Otherwise, the MCF record is not displayed on the user screen.

If you specify Y in this field, use standard naming conventions for the mail codes that receive output for the same application. Start, for example, all mail codes for your accounts payable users with the prefix AP. Anyone who is authorized to the application AP and who has access to MCF screens can subsequently change mail codes that start with AP.

If you specify N in this field, anyone with access to MCF screens can access any MCF record.

If you do not specify a value in this field, N is used by default.

Modifying a Security Options Record Your first step in providing function- and application-level security is to modify the Security Options Record about the types of security you will use. This record performs these tasks:

Identifies a master administrator who is allowed access to all Unicenter CA-Bundl functions

Activates the security options you want. You can activate function-level security, application-level security, or both types of security

Deciding What Access Users Need



To modify the Security Options Record:

1. Do one of the following:

Enter =4.3 on the command line of any Unicenter CA-Bundl screen.

Select Option 3 on the Systems Options Menu.

The Security Options Screen will display.

2. Enter the desired values in the respective fields you want and press Enter.

The Security Options Record is modified as specified.

Deciding What Access Users Need To decide what Unicenter CA-Bundl screens and what applications each user needs to access, consider what users can do from each screen or application.

If you restrict a user’s access to an application, the user cannot see records for that application on any Unicenter CA-Bundl screen except the Collected Reports screens and the Collection Statistics screen. On these screens, users can see records for restricted applications but they cannot add, change, delete, or see the actual report data in those records. Also identify Unicenter CA-Bundl screens that users need to access.




The following table describes these screens and their functions and identifies the users who generally need access to the screens.

Function or Screen System Admin

Operator User

Current Reports List

Displays current reports distributed by Unicenter CA-Bundl

√

Archived Reports List

Retrieves archived reports

√ √

Operations Menu

Changes the processing status of Unicenter CA-Bundl records that initiate data distribution; views, prints, deletes, holds, and releases reports; stops Unicenter CA-Bundl collectors; displays collection statistics

√

DSF – Input Data Set

Indicates which reports to collect for distribution

√

ATF – Application IDs

Derives application identifiers for reports

√

RTF – Report IDs

Derives report identifiers and defines control items on pages

√





Operator User

DTF – Device Output

Defines output requirements for paper and microfiche output

√

MCF – Mail Codes, Lists

Creates mail codes and lists for all online view, distribution paper, and microfiche output

√

RDF – Basic Distribution

Creates distribution rules

√

STF – Translation Rule


√

SRF – Standard Rule


√

TSF – Func, Appl Security

Authorizes users to access Unicenter CA-Bundl functions and files, and applications for which Unicenter CA-Bundl is distributing reports

√

VSF – View Security

Authorizes access to mail codes and mail lists for view output

√

SHF – Text Changes

Replaces text on pages distributed through Unicenter CA-Bundl

√

Granting Authority to Screens and Applications




Operator User

LGF – Banner Page Logo

Defines logos that appear on Unicenter CA-Bundl banner pages

√

SCH – Scheduling

Creates a schedule that Unicenter CA-Bundl uses to submit jobs

√

System Options Menu

Changes Unicenter CA-Bundl processing options, default settings for users (including PF key settings), security options, and options used in JES.ANY distributions

Anyone with access to these screens can change security settings, including the master user identifier.

√

Granting Authority to Screens and Applications After deciding what access to grant users, you must create one or more TSF records that grant users authority to access Unicenter CA-Bundl screens and to records for applications.




Do the following:

Create one record that sets defaults for all Unicenter CA-Bundl administrators and operators

Create additional records as needed for individual Unicenter CA-Bundl administrators and operators

If you create a TSF record for a particular user, the authority granted on that record replaces the authority you grant on your default TSF record.

Creating TSF Records 1. Do one of the following:

Select Option 9 on the Table Maintenance Menu.

Enter =5.9 on the command line of any Unicenter CA-Bundl screen, then press Enter.

The TSF List Screen will display:

------------------------ CA-BUNDL: TSF List Screen ------------------------- Command ==> Sel User ID User Name Appl ID 1 Appl ID 2 ---------------------------------------------------------------------------- => ---------------------------------------------------------------------------- BUNDL DEFAULT FUNCTION SECURITY GL TSOUSER1 JOHN DOE AP AR TSOUSER2 JANE DOE AP AR

2. Enter ADD on the command line, then press Enter.

The TSF Detail: Function Security Screen will display.

3. Enter DOWN on the command line, then press Enter.

The TSF Detail: Application Security Screen with values in the User ID and User Name fields will display.




TSF Detail: Function Security Screen Note: All fields on this screen are critical.

--------------- CA-BUNDL TSF Detail: Function Security Screen -------------- Command ==> DOWN FOR APPLICATIONS RECORD User ID => TSOUSER1 INFO: User Name => JOHN DOE END USER: N <= Current Reports List N <= Archive Reports List OPERATOR: N <= Operations Menu SYS ADMIN: E <= DSF – Input Data Set N <= TSF – Func, Appl Security E <= ATF – Application IDs N <= VSF – View Security E <= RTF – Report IDs E <= SHF – Text Changes E <= DTF – Device Output E <= LGF – Banner Page Logo E <= MCF – Mail Codes, Lists E <= SCH – Scheduling E <= RDF – Basic Distribution E <= STF – Translation Rule N <= System Options Menu E <= SRF – Standard Rule


Field Description

User ID Specifies the user for whom you are creating this TSF record

Specify “BUNDL” for the default TSF record; otherwise, specify a TSO user identifier.

User Name Specifies a 1- to 25-character name for the user to whom this TSF record applies

END USER OPERATOR and SYS ADMIN

Identifies a set of Unicenter CA-Bundl screens

Use these fields to select screens and type of authority you are granting to users. Valid codes are:

E (edit and browse records)

B (browse records only)

N (prevents access to the screen)




TSF Detail: Application Security Screen

---------- CA-BUNDL TSF Detail: Application Security Screen ---------- Command ==> UP FOR FUNCTIONS RECORD User ID: TSOUSER1 INFO: User Name: JOHN DOE APPLICATIONS => AP* => AR* => => FOR THIS => => => => USER: => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => =>

Granting or Changing Authority Through Exit Routines (Optional)




Field Description

APPLICATIONS FOR THIS USER

Specifies applications to which the current Unicenter CA-Bundl administrator or operator is authorized

Unicenter CA-Bundl compares this value to the value for the Appl ID field (on ATF, RTF, RDF, STF, and SRF records) or the Mail Code field (on MCF records). When these values match, this user is authorized to access records for that application..

You can use an asterisk (*) as a wildcard character to match a prefix that precedes the * character. For example, specify AP* to match any application identifier that starts with the characters AP. You must specify at least one character before the * character.

You can also use a question mark (?) wildcard to ignore a position in the application code. For example, AP?A* to match any application identifier with AP in the first two positions, and A in the third position.


You can also use security exit routines to grant or change values for function-level and application-level security. Because Unicenter CA-Bundl executes these exit routines after checking TSF records, you can modify any values you set for a user through TSF records.




Guidelines

Use the online security exit routines as follows:

To change the list of Unicenter CA-Bundl functions a user is authorized to access, you use the Unicenter CA-Bundl logon security exit routine.

You can use this exit routine to change the list of screen and applications users can access. Unicenter CA-Bundl executes this exit routine at logon time, after building lists of authorized screens and applications through TSF records.

To change the list of Unicenter CA-Bundl applications a user is authorized to access, you use the Unicenter CA-Bundl logon security exit routine and the Unicenter CA-Bundl application security exit routine.

You can use an application security exit routine to change the list of applications users can access. This exit routine, however, is not intended for use in defining function-level security. Unicenter CA-Bundl executes this exit routine only if a user tries to access records for an unauthorized application (that is, Unicenter CA-Bundl executes this exit routine after building its list of authorized applications from TSF records or a logon security exit routine).

Note: You can also create your own exit routines or use exit routines that call a security package (such as RACF, eTrust CA-ACF2, or eTrust CA-Top Secret). See the topic Online Security Exit Routines in the chapter “Exit Routines” for information about writing your own exit routines for online security.

Providing Logon-Level Security

Logon-level security enables you to control Unicenter CA-Bundl VTAM View users from logging on and enables you to modify the list of mail codes for a Unicenter CA-Bundl user.




Types of Checking You Can Perform

For logon-level security, you can:

Validate the password a user enters when logging on to Unicenter CA-Bundl (for VTAM View users only)

Accept or reject the logon attempt, based on criteria you define in an exit routine (for VTAM View users only)

Modify user identifiers or the list of mail codes a user can access, based on criteria you define in an exit routine (for any Unicenter CA-Bundl user)

If you want Unicenter CA-Bundl to validate the password a user enters when logging on to VTAM View, specify a value for the SECURITY parameter in the SETPARMS statement, in the CC50VPRM member of the CAI.PPOPTION data set.

Use this decision table to determine the value to which you need to set the SECURITY parameter to define how you want Unicenter CA-Bundl to validate the password a user enters when logging on to VTAM View.

Value Description

SECURITY=BUNDL Validates passwords itself

Unicenter CA-Bundl compares the password the user enters to the password stored in the user’s TSF record.




Value Description

SECURITY=RACF Allows a security package (such as RACF, eTrust CA-ACF2, or eTrust CA-Top Secret) to validate the passwords

SECURITY=USER Prompts users to enter user identifiers and passwords (but does not use TSF records to validate the passwords)

You can use the LOGONXT exit routine in CAI.PPOPTION to validate passwords or to reject logon attempts based on criteria you define.

SECURITY=NONE Allows users to log directly into Unicenter CA-Bundl without specifying their user identifier and password

Unicenter CA-Bundl security and log on screens are not displayed.

How Passwords are Handled When SECURITY=BUNDL is Specified

When you specify SECURITY=BUNDL for the SETPARMS statement, Unicenter CA-Bundl compares the password a user enters at the VTAM View logon screen with a password stored in the user’s TSF record. If these values match, Unicenter CA-Bundl allows the logon to continue.

After you create or modify a user’s TSF record, the user must enter the password, BUNDL, when logging on to VTAM View. That password is stored in the user’s TSF record when the record is created or modified. Then, at logon time, the user must change their password. At that time, an encrypted password is stored in the user’s TSF record in place of the password, BUNDL.




Important! Make sure to inform new VTAM View users to use the password, BUNDL, the first time they log on, and to change the password immediately. If a user forgets their password, you cannot look up that password in the user’s TSF record. Instead, revert the password to BUNDL by modifying the user’s TSF record. You must then delete the user’s TSF record and add it again to reset the password. The user must logon for the first time using the password, BUNDL. A prompt to change the password to a new password will display.

LOGONXT Exit Routine

You can use the LOGONXT exit routine to allow or prevent VTAM View users from logging on, based on criteria you define.

Prevent a user from logging on to VTAM View, or call a security package (such as eTrust CA-ACF2) to identify authorized VTAM View users

Collect accounting information about logon attempts (such as when a user logged on to VTAM View) and record this information in an SMF record

Note: If you provide a LOGONXT exit routine, Unicenter CA-Bundl executes that routine for VTAM View users, no matter what value you specify for the SECURITY parameter. See the Unicenter CA-Bundl VTAM View System Guide for more information about writing this exit routine.

Modifying User Identifiers and Mail Code Lists at Logon Time

When a Unicenter CA-Bundl user logs on, Unicenter CA-Bundl obtains the list of mail codes that the user can access. After the logon is completed, you can use the logon security exit routine for Unicenter CA-Bundl to modify this list of mail codes or the user’s identifier.

Providing Mail Code-Level Security



If your Unicenter CA-Bundl users have a common prefix in their user identifiers, you can use the exit routine to authorize users instead of listing mail codes on the user’s VSF record. The exit routine provides a shorter way for you to authorize users that have common prefixes in their identifiers to mail codes they all need.

Suppose, for example, that all payroll department users need to access mail codes 123 and 456. If their identifiers all start with PAY, you can use the exit routine to authorize all user identifiers that start with PAY to mail codes 123 and 456. Using the common prefix PAY is easier than specifying mail codes 123 and 456 on each of their VSF records, and it also makes it easy for you to maintain this list of common mail codes for those users.

If you provide a logon security exit routine, Unicenter CA-Bundl executes that routine for all Unicenter CA-Bundl users, no matter what value you specify for the SECURITY parameter. See Coding a Logon Security Exit Routine in the chapter “Exit Routines” for information about how to write this exit routine.

Providing Mail Code-Level Security By default, Unicenter CA-Bundl allows users to view any reports sent to them through Unicenter CA-Bundl. To prevent users from viewing reports for particular mail codes, you need to provide mail code-level security.

Factors That Determine Reports a User Can View

Unicenter CA-Bundl considers these factors when it has reports to distribute:

The distribution rules your Unicenter CA-Bundl system administrator created

These rules tell Unicenter CA-Bundl which reports a mail code should receive.

Providing Mail Code-Level Security



The mail codes a user is authorized to view

Mail code-level security enables you to restrict a user’s ability to view reports for certain mail codes.

Note: When you have provided mail code-level security and a user tries to display reports, Unicenter CA-Bundl compares the mail code for those reports with the mail codes the user can view. When these mail codes match, Unicenter CA-Bundl displays the report on that user’s terminal. Otherwise, Unicenter CA-Bundl removes information about that report from the user’s terminal. The user does not see information about reports he or she cannot access. Unicenter CA-Bundl also uses application security to restrict access to reports that operators access through the Collected Reports List Screen.

Defining Mail Code-Level Security

You follow the general steps presented below to define mail code-level security for Unicenter CA-Bundl. These steps are described in detail later in this section.

1. Establish defaults for mail code-level security.

2. Authorize users to access additional mail codes (as needed).

3. Activate mail code-level security.

Note: You can also use SHF records to restrict a user’s ability to view certain areas on the page of a report. Using SHF records for this purpose is described in more detail in the Unicenter CA-Bundl Administrator Guide.

VSF Detail Screen



VSF Detail Screen The CA-Bundl VSF Detail Screen is used to establish defaults for mail code-level security. All fields on this screen are critical.

-------------------- CA-BUNDL: VSF Detail Screen --------------------- Command ==> RECORD User ID => BUNDL Seq No => 001 INFO: User Name => DEFAULT MAIL CODES VIEW PRINT: Device ID => 9700LETR Mode => SIMP MAIL CODES FOR THIS USER: => B50VIEW => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => => =>


Field Description

User ID Specifies a 1- to 8-character TSO identifier for this user

Seq No Specifies a 3-digit value that uniquely identifies this VSF record

User Name Specifies a 1- to 25-character name for this user

VSF Detail Screen



Field Description

Device ID and Mode

Specifies a 1- to 10-character identifier for a device or a group of devices

When a report is initially selected to queue for printing or select an archived report you want to reprint, Unicenter CA-Bundl goes through this process to fill in values in the Device ID and Mode fields:

1. If the VIF record contains the values OPERATIONS and STD for the device identifier and mode, respectively, Unicenter CA-Bundl uses that VIF record.

2. The contents of the user’s VSF record are checked for any values.

3. If the device identifier and mode are not yet defined, the contents of the Unicenter CA-Bundl VSF record are checked for any values.

4. If Mode field is still not defined, STD is inserted for JES2 and PRT for JES3.

5. If Device ID field is not yet defined, the mail code record is checked for a device identifier.

6. If Device ID field is not yet defined, the home code record is checked for a device identifier (if mail code record specifies a home code).

7. If the Device ID field is still not defined, DEFAULT is inserted.

Establishing Defaults for Mail Code-Level Security



Field Description

MAIL CODES FOR THIS USER

Specifies the mail codes and mail lists that users can access

Unicenter CA-Bundl users can access any view output sent to these mail codes or mail lists. If you do not want to authorize this user to any mail codes, leave this field blank.

You can use the asterisk (*) wildcard character to match a prefix that precedes the asterisk (*) character. Specify, for example, AP* to match any application identifier that starts with the characters AP. You must specify at least one character before the asterisk (*) character.

You can also specify the asterisk (*) wildcard character alone to access all mail codes.

Establishing Defaults for Mail Code-Level Security When you establish defaults for mail code-level security, you identify mail codes that any user can access. Select these defaults carefully because users can view any report sent to the mail codes you choose for them. Your system administrator can supplement these defaults for users as needed.




Methods of Establishing Defaults

You can use one or both of these methods to establish defaults:

Identify mail codes that all Unicenter CA-Bundl users can access by providing a VSF record for the user identifier, BUNDL. Provide this record even when you are not adding mail codes to this identifier.

Use the Security Options Screen (4.3) to indicate which part of a user identifier Unicenter CA-Bundl is to use to identify mail codes the user can access.

Establishing Defaults Through a VSF Record

One way to establish defaults for mail code-level security is to identify mail codes accessible by all Unicenter CA-Bundl users. To do this, create a VSF record for the user identifier, BUNDL:


Select Option A on the Table Maintenance Menu.

Enter =5.A on the command line of any Unicenter CA-Bundl screen.

The VSF List Screen will display.

------------------------ CA-BUNDL: VSF List Screen ----------------------- Command ==> Sel User ID Seq User Name Mail Code 1 Mail Code 2 => BUNDL 001 DEFAULT MAIL CODES B45VIEW




2. Enter ADD on the command line, then press Enter. The CA-Bundl VSF Detail Screen will display.

3. Enter the desired values in the appropriate fields, then press Enter. The VSF record is defined for user identifier, BUNDL as specified.

Establishing Defaults Through the Security Options Screen

Another way to establish defaults for mail code-level security is to indicate what part of a user identifier Unicenter CA-Bundl should compare to the mail code on reports. When a mail code and the user identifier portion match, the user can view reports for the mail code. You can use this technique to allow users to view their own reports, but not other users’ reports.

Display the Security Options Screen and specify values for the following fields:

Start With

Length

Example Suppose the fourth and fifth characters are always unique and you want users to access mail codes assigned these characters. To do this, specify 4 in the Start With field and specify 2 in the Length field, as shown here:

START WITH => 4

LENGTH => 2

Note: If you do not want Unicenter CA-Bundl to match mail codes with parts of a user identifier, specify 0 in the Start With field.

Authorizing Users for Specific Mail Codes



Authorizing Users for Specific Mail Codes After you have established defaults, you authorize users for specific mail codes they need.

Note: Do this only for users who need access to mail codes they cannot access by default.

Methods of Authorizing Users

You can use one or both of the following methods to authorize users to access specific reports:

Create VSF records for each user who needs access to additional mail codes

Authorize users through a mail code security exit routine

You may create this exit routine for your organization or an exit routine that calls a security package (such as RACF, eTrust CA-ACF2, or eTrust CA-Top Secret). Unicenter CA-Bundl calls this exit routine, DPMS962, when the mail code on a report and the mail codes a user is authorized to view do not match.

See the chapter “Exit Routines” for information about writing this exit routine.

Note: You can use the Logon Security exit routine, which Unicenter CA-Bundl executes at logon time, to change the list of mail codes for a user. See the topic Coding a Logon Security Exit Routine in the chapter “Unicenter CA-Bundl Exit Routines” for information about this exit routine.

Activating Mail Code-Level Security



Activating Mail Code-Level Security After you have authorized Unicenter CA-Bundl users to access the mail codes they need, activate mail code-level security as follows:

1. Display the Security Options Screen (4.3).

2. Enter Y in the Mailcode field.

Mail-code level security is now activated.

Setting Unicenter CA-Bundl Options and Session Defaults 6–1


Chapter

6 Setting Unicenter CA-Bundl Options and Session Defaults

This chapter describes the options that affect how Unicenter CA-Bundl operates and the default settings that affect Unicenter CA-Bundl sessions.

Processing Options Screen The following is an example of the Processing Options Screen, which you use to view or change the processing options Unicenter CA-Bundl uses. All fields on this screen are critical.

------------------ CA-BUNDL: Processing Options Screen --------------- Command ==> SYSTEM Process Date => P Mail Cd Banners => 1 OPTIONS: Wait Minutes => 1 Home Cd Banners => 1 Default Min PDF => 0 Default Out Class => X Default Max PDF => 4 Job Number Flag => N END USER OPTIONS: Max Pages/Find => 1000 Max Reprint Retpd => 100 EXIT Default Banner => DPMS951 Default Device => DPMS952 ROUTINES: Default Out Page => #NONE

Processing Options Screen




Field Description

Process Date

Specifies where to obtain the processing date:

P Prompts the operator to provide the date, or obtains the date from an automation software program

S Uses the current operating system date

If you do not specify a value, S is used by default.

Important! We strongly recommend that you specify S. If an operator specifies the wrong processing date, you must go through a recovery procedure to correct the date, and you must delete all reports that were collected with the incorrect date.

Wait Minutes

Indicates how long Unicenter CA-Bundl is to suspend processing when it has no data to collect

Enter a value (in minutes) from 1–99. If you do not specify a value, 1 is the default. Increase this value if you:

Have more than 100 DSF records

Execute more than two collection jobs




Field Description

Default Min PDF

Identifies the lowest-numbered page data file that will temporarily store output

Values are from 0–9.

We recommend that you use the default value, 0. This field sets the default value for all DSF records. You can override this value on a DSF record by specifying a value in the Min PDF field.

Several collection jobs can share a page data file. Only one collection job is allowed to update the file at a time. Therefore, you can experience processing delays if many collection jobs share a file or if a collection job writes large amounts of data to a file while other jobs wait for that file.

Default Max PDF

Identifies the highest-numbered page data file that will temporarily store output from Unicenter CA-Bundl

To limit a collection job to a range of page data files, enter the number of the last file in this range.

We recommend that you use the default value, 9. This field sets the default value for all DSF records; you can override this value on a DSF record by specifying a value in the Max PDF field.

Mail Cd Banners

Specifies how many copies of each banner page Unicenter CA-Bundl is to print between mail codes in a bundle

Enter a value from 1 to 9; the default is 2.

Note: This field affects only reports sent directly to print and reports that a Unicenter CA-Bundl user sends to the Unicenter CA-Bundl print queue. It has no effect on output that a Unicenter CA-Bundl user sends for immediate printing.




Field Description

Home Cd Banners

Specifies how many copies of each banner page Unicenter CA-Bundl is to print between home codes in a bundle

Enter a value from 1 to 9.

If you do not specify a value, 2 is used by default.

Note: This field affects only reports sent directly to print and ones that a Unicenter CA-Bundl user sends to the Unicenter CA-Bundl print queue. It has no effect on output that a Unicenter CA-Bundl user sends for immediate printing.

Default Out Class

Indicates the output class Unicenter CA-Bundl is to use for print output if none of your DTF records applies to that output

If you do not specify a value, A is used by default.

Job Number Flag

Controls how the job number displays on the Archive Selection List and the Reprint Status screens

Maximum job numbers for z/OS 1.2 contain the letter J followed by 7 digits, for example, Jnnnnnnn.

When you enter Y, 7 digits of the job number are displayed. Also, the “/”s are removed from the date on the Detail List for date options 1, 2, and 3. However, the date filter requires “/”s for date options 1, 2, and 3.

When you enter N (default), 5 digits of the job number are displayed and the “/”s are added to the date on the Detail List for date options 1, 2, and 3.




Field Description

Max Pages/Find

Sets a maximum number of pages that Unicenter CA-Bundl retrieves when a user enters a FIND command to search for a text string and Unicenter CA-Bundl cannot find that string

Specify a value from 1–999999. If you do not specify a value, 1000 is used by default.

Note: Less than or equal to 5000 is recommended.

Max Reprint Retpd

Sets a maximum retention period for reprint pages distributed to Unicenter CA-Bundl view users

Specify a value in one of the following formats (where n represents an actual value you specify):

nnn or nnD for days (998 maximum)

nW for weeks (99 maximum)

nM for months (99 maximum)

nY for years (99 maximum)

nC for cycles (99 maximum)

999 (to retain permanently)

Note: Retention periods are described in detail in the Unicenter CA-Bundl System Administrator Guide.

Default Banner

Identifies your default banner page exit routine

If you do not specify a value, DPMS951 is used by default.

Note: To override this routine, use the Banner field on a DTF record.

Default Device

Identifies your default device control exit routine

Specify #NONE in this field to indicate that there is no device control exit routine. If you do not specify a value, DPMS952 is used by default. To override this routine, use the Device field on a DTF record.

Default User Option Screen



Field Description

Default Out Page

Identifies your default output page exit routine

Specify #NONE in this field to indicate that there is no default output page exit routine.

There is no default routine for output pages. To override this routine, use the Out Page field on a DTF record.

Default User Option Screen The following is an example of the Options Page 1 screen, which you use to view or change the first page of default options for users. All fields on this screen are critical.

------------------------- Options Page 1 ----------------------------- Command ==> Language Preference => ENGLISH DOWN for Page 2 Date Format => 1 (1-5) ( MM/DD/YY ) Selection List Qualifiers => D (Description, Name) Auto-save View Settings => N (Yes/No) Column Separator(s) => | (None, or character to use) Ruler Line(s) => S (Top, Section, or None) SYSOUT Class => A Banner Pages => Y (Yes/No) Reformat Option => B (Lines, Columns, Both or None) Line Numbers => N (Yes/No)





Field Description

Language Preference

Specifies the language for view screens

Specify ENGLISH.

If blank, ENGLISH is used by default.

Note: Other languages are currently not available. For more information, see the topic The Language Preference Option in the Unicenter CA-Bundl User Guide.

Date Format Defines how dates are to be displayed on Unicenter CA-Bundl screens

Specify a number from 1 to 5. Use the following table to determine the value to enter in this field:

1 mm/dd/yy (06/30/00)

2 dd/mm/yy (30/06/00)

3 yy/mm/dd forat (00/06/30)

4 Julian-year/day-of-year (00/151)

5 extend-Julian/day-of-year (2000/151)

If you do not specify a value, format 1 is used by default.

Selection List Qualifiers

Indicates the fields Unicenter CA-Bundl is to use to identify a report on the Unicenter CA-Bundl view screens

Specify one of the following values:

D Uses the value in the Descrip field on the RDF Detail screen for that distribution

N Uses the values in the Report, Jobname, and Jobnum fields

If you do not specify a value, D is used by default.




Field Description

Auto-save View Settings

Indicates when to save view settings.

Specify one of the following values:

N Saves these settings only when users enter a SAVE command

Y Saves these settings automatically

If you do not specify a value, N is used by default.

Column Separator(s)

Sets the default value in the Column Separator(s) field on the View Options for Report Screen

Ruler Line(s) field identifies the character to use to separate columns in report displays.

Specify a single character. If you do not specify a value, a split vertical bar (|), sometimes called a pipe, is used.

Ruler Line(s) Sets the default value in the Ruler Line(s) field on the View Options for Report Screen

Ruler Line(s) field tells Unicenter CA-Bundl where to place horizontal rulers in report displays.

Specify one of these values:

N Omits rulers

S Places rulers between sections (line ranges)

T Places rules only at the top of the screen

If you do not specify a value, S is the default.




Field Description

SYSOUT Class

Sets the default value in the SYSOUT Class field on the View Options for Report Screen

SYSOUT Class field identifies what SYSOUT class to use when printing reports requested from view screens.

Specify a SYSOUT class.

Banner Pages Sets the default value in the Banner Pages field on the View Options for Report Screen

The Banner Pages field tells Unicenter CA-Bundl whether to insert banner pages in output you print from view screens.

Specify N or Y. If you do not specify a value, Y is used by default.

Reformat Option

Sets the default value in the Reformat Option field on the View Options for Report Screen

The Reformat Option field tells Unicenter CA-Bundl whether to reformat columns and lines in output you print from view screens.

Specify one of these values:

B Reformats both columns and lines

C Reformats columns only

L Reformats lines only

N Prints the report in its original format

If you do not specify a value, N is used by default.

Options Page 2 Screen



Field Description

Line Numbers

Sets the default value in the Line Number(s) field on the View Options for Report Screen

The Line Number(s) field tells Unicenter CA-Bundl whether to display line numbers on the left side of reports.

Specify N or Y. If you do not specify a value, N is used by default.

Options Page 2 Screen All fields on this screen are critical.

------------------------- Options Page 2 ----------------------------- Command ==> Automatic startup filters UP for Page 1 Application ==> Report ==> Home Code ==> Mail Code ==> Use Wildcard Filters ==> Y (Yes/No) Retain Filters ==> Y (Yes/No) Report Order ==> O (Newest first / Oldest first) Date Filter Span ==> 0031 (in days, 0 = no limit) Immediate Print Defaults Dest/Node ==> Remote ID ==> Form ==> Startup command ==> <




Use the Options Page 2 screen to display and change settings for special start-up filters and immediate print default options, which enable you to permanently define parameter settings that are to be entered automatically whenever you start Unicenter CA-Bundl.

The parameters you specify on the Options Page 2 screen apply only to the Current Report Selection List and Archive Report Selection List screens.


Field Description

Application Specifies that only reports generated by the application identified by the 1-to 10-character application identifier you enter in this field are to be listed on current and archived report list screens

Report Specifies that only reports identified by the 1-to 10-character report identifier you enter in this field are to be listed on current and archived report list screens

Home Code Specifies that only reports identified by the 1-to 10-character home code you enter in this field are to be listed on current and archived report list screens

Mail Code Specifies that only reports identified by the 1-to 10-character mail code you enter in this field are to be listed on current and archived report list screens




Field Description

Use Wildcard Filters

Specifies that Unicenter CA-Bundl is to interpret or not interpret the characters asterisk (*) and question mark (?) as wildcard characters on current and archived report list screens

Note: Asterisk (*) matches any trailing set of characters; question mark (?) matches any single character, including the blank character.

Y(es) tells Unicenter CA-Bundl to interpret the asterisk (*) and question mark (?) characters as wildcards when you enter them to search for or restrict the listing of reports on current or archived report list screens.

N(o) tells Unicenter CA-Bundl not to interpret the asterisk (*) and question mark (?) as wildcards.

If you do not specify a value in this field, the default value specified by your Unicenter CA-Bundl administrator is used. If your Unicenter CA-Bundl administrator does not specify a default value for this field, N is used.

You can also enter WILDCARD OFF and WILDCARD ON on the command line of any Unicenter CA-Bundl screen to activate or de-activate this wildcard facility for the remainder of your current user session or until changed.

If Y is specified in this field, ABC* is interpreted as all text strings that begin with ABC.

If N is specified in this field, ABC* is interpreted as the text string ABC only.




Field Description

Retain Filters Specifies if filter settings defined on the Options Page 2 screen are to be automatically carried over when you display different report selection lists (for example, when you switch from the Archive Report Selection List screen to the Current Report Selection List)

Y(es) Indicates that the current filter settings are to be automatically carried over when you switch to a different report selection list.

N(o) Indicates that the currently-set filters are to be cleared when you switch amongst the Current, Archived, and Collected Report Selection List screens.

You can carry over values amongst the Current, Archived, and Collected Report Selection List screens only.

If a value is not specified in this field, the default value specified by your Unicenter CA-Bundl administrator for this field is used. If your Unicenter CA-Bundl administrator does not specify a default for this field, N is used.

You can also enter REUSE OFF and REUSE ON on the command line of any Unicenter CA-Bundl screen to activate or deactivate this facility for the remainder of your current user session or until changed.

Report Order Specifies the order in which reports are to be listed on current and archived report list screens

O Displays the oldest produced or archived reports first

N Displays the most-recently produced or archived reports first




Field Description

Date Filter Span

Specifies the maximum number of days after the date you specify (in the Date filter field on selection list screens) that are to be listed on the Current Reports Selection List screen

Enter a value between 0 and 9999 inclusive in this field.

Use this decision table to determine the value to enter in this field to effect the result you want:

If You Want to Then You Specify, in the Date Filter Span Field

Display all dates starting with the date of oldest Unicenter CA-Bundl report

Enter blank in the Date filter field

The value 0 (zero)

Display all previous dates from a number of days ago up to and including the present day

Enter blank in the Date filter field

Actual number of days ago (up to and including the present day) you want

Display all previous dates starting from a specified date up to and including the current day

Specify the date on which to start in the Date filter field

The value 0 (zero)




Field Description

Date Filter Span (Continued)

If You Want to Then You Specify in the Date Filter Span Field

Display all previous dates starting from a specified date up to and including the current day


The value 0 (zero)

Display a range of dates starting at a specified date and ending at a specified number of days


Actual number of days after the end date specified in the Date Filter field

If you enter Y(es) in the Retain Filters field, the previously-defined value in the Date Filter field is used by default when you initially display a Report Selection List.

Notes: If the Report Order field is set to O(ldest)

and you want to display a list of all reports for the period August 1, 2000 through August 20, 2000, you specify August, 1, 2000 in the Date Filter field and the value 20 in the Date Filter Span field.

For the Archived Reports Selection List screen the Date Filter Span field will have no effect when the Report Order field is set to N(ewest). When the Report Order field is set to O(ldest) and a date is entered in the Date Filter field, it indicates how many days forward to search and display reports from the date entered in the Date Filter field.




Field Description

Dest/Node Specifies a personal immediate print default value you want automatically inserted in the Destination/Node field on the Specify Printing Parameters screen whenever you request an immediate print

The value you specify in this field is subsequently displayed (until you change it) in the Destination/Node field whenever you display the Specify Printing Parameters screen.

Remote ID Specifies a personal immediate print default value you want automatically inserted in the Remote ID field on the Specify Printing Parameters screen whenever you request an immediate print

The value you specify in this field is subsequently displayed (until you change it) in the Remote ID field whenever you display the Specify Printing Parameters screen.

Form Specifies a personal immediate print default value you want automatically inserted in the Form field on the Specify Printing Parameters screen whenever you request an immediate print

The value you specify in this field is subsequently displayed (until you change it) in the Form field whenever you display the Specify Printing Parameters screen.




Field Description

Startup command ==>

Enter a command or set of commands to be executed automatically every time you start Unicenter CA-Bundl

You can enter a maximum of 50 characters in this field.

Notes: The fast path commands are:

=n (equal sign) Selects option n on the CA-Bundl Main Menu

. (period) In place of the Enter key, you can use a period

The first two characters of the startup command field must begin with an equal sign (=) followed by a valid menu option. For example, startup command ==> =2 (positions you to the archive reports screen and issues the Enter key automatically.)

These commands are intended primarily for use on the Options Page 2 screen. These commands enable you to automatically jump to the screen you use most often when you start Unicenter CA-Bundl and execute Unicenter CA-Bundl commands.

Setting Unicenter CA-Bundl Processing Options



Field Description

Startup command ==>(Continued)

To automatically turn on the display of the screen identifier and display the Archived Report Selection List screen (which includes a filtered list of reports that are listed according to the start-up options you specify) every time you access Unicenter CA-Bundl, enter the command =2.PANELID in the Startup command ==> field on the Options Page 2 screen.

Setting Unicenter CA-Bundl Processing Options Unicenter CA-Bundl processing options set values (and, in some cases, default values) that affect how Unicenter CA-Bundl operates. Before you make Unicenter CA-Bundl available to your users, you need to review the processing options Unicenter CA-Bundl uses and modify them as needed.

To view or change the processing options that Unicenter CA-Bundl uses:


On the command line of any Unicenter CA-Bundl screen, enter =4.4.

From the System Options Menu, choose Option 4.

The Processing Options Screen will display.

2. Enter values in the desired fields, then press Enter.

The processing options are changed to the specified values.

Setting Default User Options for Unicenter CA-Bundl Sessions



Setting Default User Options for Unicenter CA-Bundl Sessions

Select the Default User Options and Options Page 2 screens to set default values that affect all Unicenter CA-Bundl online view users. An individual user can override these values on both screens.

To change the default values that affect all Unicenter CA-Bundl online view users:


Enter =4.1 on the command line of any Unicenter CA-Bundl screen.

From the System Options Menu, select Option 1.

The Options Page 1 screen will display.

2. Enter values in the desired fields.

3. Do you want to change values on the Options Page 2 screen?

If no, skip this step and go to step 5.

If yes, enter DOWN on the command line.

The Options Page 2 screen will display.

4. Enter values in the fields you want, and then press Enter.

Unicenter CA-Bundl uses the default user option values you specified for all new Unicenter CA-Bundl users.

To make the changes affect all users, you must run CC50J080 to delete the profile for all users.

See the chapter “Using and Scheduling Unicenter CA-Bundl Jobs and Programs” in the Unicenter CA-Bundl Administrator Guide for more information about CC50J080.

PF Definitions Screen



PF Definitions Screen You can assign Unicenter CA-Bundl commands that online view users issue most often to programmable function (PF) keys. You use the administrator’s PF Definitions screen to assign Unicenter CA-Bundl commands to PF keys for all online view users.

If an individual Unicenter CA-Bundl user does not reassign them during his or her own Unicenter CA-Bundl session, the commands you assign to PF keys on this screen are used by default.

The PF Definitions screen for administrators and users is the same screen. An online view user uses the PF Definitions screen to reassign commands to PF keys for their own Unicenter CA-Bundl session.

The following is a diagram of a typical PF Definitions screen. All fields are critical.

--------------------- CA-BUNDL: PF Definitions --------------------- Command ==> PF1 / PF13 => HELP PF2 / PF14 => PRINT PF3 / PF15 => END PF4 / PF16 => MENU PF5 / PF17 => FIND PF6 / PF18 => COLUMNS PF7 / PF19 => UP PF8 / PF20 => DOWN PF9 / PF21 => BACK PF10 / PF22 => LEFT PF11 / PF23 => RIGHT PF12 / PF24 => FORWARD

Assigning Unicenter CA-Bundl Commands to PF Keys




Field Description

PFn

(n represents an actual PF Key number shown on this screen.)

Indicates the command to which you want to assign PF key n


Be aware of the following rules when assigning Unicenter CA-Bundl commands to programmable function (PF) keys:

Commands you assign to PF keys can be up to 20 characters long.

You can assign any command to a PF key that you can enter on the command line of any Unicenter CA-Bundl screen.

You can use valid abbreviations of commands when assigning them to PF keys.

You can include operands with the commands to which you assign PF keys.

For example, you can assign FIND TOTALS to PF key PF 5. When you press PF 5, the Unicenter CA-Bundl command FIND TOTALS is executed (that is, Unicenter CA-Bundl searches for the text string TOTALS).




Use the following procedure to assign Unicenter CA-Bundl commands to PF keys for all online view users:


Enter =4.2 on the command line of any Unicenter CA-Bundl administration screen.

Choose Option 2 from the System Options Menu.

The administrator’s PF Definitions screen will display.

2. Move the cursor to the desired field and enter the new command you want over the current command shown in the field.

3. Repeat the previous step to reassign other commands to PF keys until you reassign all the commands you want.

4. Press Enter.

Unicenter CA-Bundl assigns the command or commands you entered to the corresponding PF key or keys shown for all online view users.

Note: Unicenter CA-Bundl retains the settings of PF keys until you change them for all online view users, or until an individual online view user changes them during a Unicenter CA-Bundl session. In order to make the administrator’s changes take effect for all users, you must run CC50J080 to delete the profile for all users. See the chapter “Using and Scheduling Unicenter CA-Bundl Jobs and Programs” in the Unicenter CA-Bundl Administrator Guide for more information about CC50J080.

Exit Routines 7–1


Chapter

7 Exit Routines

This chapter describes the Unicenter CA-Bundl exit routines and provides instructions on how to write them.

Unicenter CA-Bundl Exit Routines Input Page

Output

Online Security

Logon Security

Logoff Security

Mail Code security

View Print Security

Application Security

Administrative Record Access Security

TSO Report Access Logging

Input Page Exit Routine Unicenter CA-Bundl provides an input page exit routine that you can use to access pages of a report before Unicenter CA-Bundl examines those pages.

Input Page Exit Routine



You can use this exit routine to do the following:

Add headers to a page

Place control data on a page

Add, delete, modify, or replace a page

Change the home code, mail code, or particular information about the input data set from which the page was collected.

Limit the number of lines or pages collected from a JES data set. A page is inserted in the front of the collected data set indicating that the report has been truncated and exceeded the number of lines. The exit, SAMPEX2M, is delivered as an example of controlling the number of lines collected.

Note: Unicenter CA-Bundl calls this exit routine immediately after it collects pages but before it examines those pages.

Important! The sample input page exits (SAMPEXxx) shipped with Unicenter CA-Bundl are shells (frameworks) meant to assist you in creating your own exits. They are not intended for use as shipped.

Rules for Writing an Input Page Exit Routine

Follow these rules when coding an input page exit routine:

Execute the exit routine by specifying its name in the INPAGEX parameter statement for the appropriate collection jobs.

Make the exit routine reusable. The exit routine does not have to be re-entrant.

Use USERMOD CC50EXA in SAMPJCL to install your exit into CAI.CAILIB.


Exit Routines 7–3


Unicenter CA-Bundl arranges a page so that is has the same layout as when it is printed.

When you modify, insert, or replace pages, use the same structure as the Unicenter CA-Bundl pages:

− Use a line length of 204 bytes.

− Provide no more than 150 lines per page.

− Make the first character of each line an ASA carriage control character. Or, if you do not want to use a line, make the first character of the line the value X‘FF’.

− Space lines to match the layout of the page as it appears when you print it.

If a User 602 Abend occurs, look for the following Unicenter CA-Bundl messages:

− BND7280I PAGE EXIT ROUTINE – INVALID RC

− BND7281I PAGE EXIT ROUTINE – INVALID LINE COUNT

− BND7282I PAGE EXIT ROUTINE – INVALID PAGE RECEIVED

In this dump:

− Register 3 points to the exit’s parameter list

− Register 4 points to the input page exit

− Register 5 contains the return code issued from the exit routine’s last call

If a User 600 Abend occurs, then a VSAM error occurred.

Use caution when testing the exit routine because the exit routine can pass Unicenter CA-Bundl data that can later cause problems.

An invalid carriage control or a wrong line count, for example, does not immediately cause a 600 abend, but it can later cause problems during processing.




Look in the SAMPEX2x members of CAI.PPOPTION for sample input page exit routines.

Unicenter CA-Bundl does not execute an input page exit routine by default.

Additional Information About the Input Page Exit Routine

The following table provides details about coding an input page exit routine:

Information Description

Entry Environment

Problem state, problem program key, addressing mode 24

Preserve this entry environment and restore it when you return.

Register Usage at Entry

R1 Points to the address of a parameter list where the input data set, page, and page origin are described

The layout of the list is described on the next page. For a DSECT that lays out the parameter block, see the DPMCEX2A member of CAI.CAIMAC.

R13 Contains the address of the standard save area

R14 Contains the return address for Unicenter CA-Bundl

R15 Contains the entry point address for this exit routine

All other registers are undefined.


Exit Routines 7–5



Offsets for the Parameter List

Note: If C appears at offset +14, you can only change the offsets with an asterisk (*) after them.

+00 Four-byte hexadecimal address for the page record

If you provide a replacement page or insert a page, specify the address of the page here.

+04 Four-byte hexadecimal address of the subsystem options block

+08 Four-byte reserved area

+C Two-byte hexadecimal value for the number of lines on the page (including lines with an X‘FF’ carriage control character)

If you change the number of lines on a page, use this offset to determine how many lines are now on the page.

+E Two-byte hexadecimal value for the number of lines actually used on the page

This value equals the number of lines on the page minus the number of lines with an X‘FF’ carriage control character. Unicenter CA-Bundl calculates this value upon return.

+10 Two-byte hexadecimal value for the line length

This value is always 204 bytes. Do not change this value.





Offsets for the Parameter List (Continued)

+12 Two-byte hexadecimal value for the Unicenter CA-Bundl status code

A code of 0 indicates that the exit routine located a page. A code of 4 indicates that no page was found (that is, an end-of-file condition occurred).

+14 One-character code representing the type of data set (C for catalogued, J for JES)

+15 Eight-character name of the job that created the data set

+1D Eight-character JES number of the job that created the data set

+25 Eight-character writer name

+2D Eight-character undefined value

+35 Four-character form for the data set

+39 Four-byte hexadecimal value for the time when this data set was created

+3D Four-byte hexadecimal value for the date when this data set was created

+41 One-character JES output class

+42* 44-character external file name (from the DSF record)

+6E 44-character DSNAME

+9A Two-byte hexadecimal value for the number of copies from JES

+9C* Two-byte hexadecimal value for the logical record length of the data set


Exit Routines 7–7



Offsets for the Parameter List (Continued)

+9E* Two-byte hexadecimal value for the block size of the data set

+A0 Ten-character application identifier

Use the exit routine to modify.

+AA Ten-character report identifier

The exit routine can modify this identifier.

+B4 Four-digit hexadecimal value for the number of lines in the JES data set

+B8 Eight-character name of the PROC step that created the data set

+C0 Eight-character name of the step that created the data set

+C8 Eight-character DDNAME of the data set+D0 Eight-character group identifier for the data set

+D8 Ten-character home code (for JES.ANY distribution only)

The exit routine can modify this home code.

+E2 Ten-character mail code (for JES.ANY distribution only)

The exit routine can modify this mail code.





Return Code, Register 15

The functions you can perform through a return code depend on what value you receive for the Unicenter CA-Bundl status code (stored at offset +12 in the parameter list).

A code of 0 indicates that the exit routine located a page; a code of 4 indicates that no page was found.

When the code is 4, you can insert a page or acknowledge the end-of-file condition (EOF). If you insert a record, Unicenter CA-Bundl calls the exit routine again (with the status code set to 4). You can continue inserting records (one per call) until you acknowledge the end-of-file (EOF) condition.

Specify one of the following return codes to direct the exit routine:

Return Code

Action When Status Code=0


0 Use the unmodified page

Acknowledge end-of-file (EOF) condition

4 Use the modified page

Invalid

8 Delete the page Invalid

12 Replace the page Invalid

16 Insert a page before this one

Insert a page before this one


Exit Routines 7–9



Return Code, Register 15 (Continued)

Return Code



20 Do not call exit routine again for this data set

Acknowledge EOF

24 Do not call the exit routine again for this collector

Acknowledge EOF; do not call the exit routine again for this collector

Additional Information about SAMPEX2M Exit, Line Limit Controls

Use MAXLINES=99999999 (eight digits or numeric characters) in the STCPARM for the Unicenter CA-Bundl collector to specify the maximum number of lines that can be collected from a JES data set. We recommend that you zero-fill the value to eight digits. If less than eight digits are entered, program DPMB001 will zero-fill the values to the left of the first digit. For example, MAXLINES=50000, will be edited to MAXLINES=00050000.

The MAXOPT=BYPASS parameter is optional and can be included in STCPARM to bypass the remaining lines in the JES data set. A notification page is inserted into the Page Data files when the lines are bypassed. The remaining lines are deleted from the JES Spool when MAXOPT=BYPASS is coded. Use caution with MAXOPT=BYPASS. If it is not coded, a warning message is generated when a collected JES data set exceeds the maximum number of lines.

SAMPEX2M is a sample input page exit that can be customized as needed to handle the MAXLINES and MAXOPT processing. The source code is included on your Unicenter CA-Bundl installation tape.

Output Exit Routines



Example of STCPARM DD:

MAXLINES=99999999

Maximum number of lines to collect from a JES data set. MAXLINES must be numeric, no commas

MAXOPT=BYPASS

MAXLINES Bypass Option

INPAGEX=SAMPEX2M

Input page exit for handling collector line limits

When the MAXOPT=BYPASS option is coded and the collector reaches MAXLINES, a notification page is inserted by exit SAMPEX2M into the Page Data File indicating that the data set has been truncated. The remaining lines are deleted from the JES data set. Care should be taken in using the MAXOPT=BYPASS option. When the MAXOPT=BYPASS is not coded the data set is collected in full and a warning message is generated by the SAMPEX2M exit. The SAMPEX2M exit can be customized as required to handle exceptions and customizing options.

Output Exit Routines Output exit routines are provided to handle specialized printing needs for your reports, such as custom forms design, microfiche machines, or banner pages that contain the company logo.

Device Control Exit Routine

This exit routine, DPMS952, is used to write device control commands before banner pages or the first page of a report.

You can also do the following:

Set laser forms for banner pages

Insert Dynamic Job Descriptor Entry (DJDE) or Advanced Function Printing (AFP) commands at distribution breaks


Exit Routines 7–11


Control the devices that cut paper from continuous form rolls

Insert microfiche commands for custom handling of microfiche

Banner Page Exit Routine

The exit routine, DPMS951, is used to build a banner page for any of the distribution breaks that occur. You can also:

Create a custom banner page for each distribution break

Insert DJDE or AFP commands after a banner page

Place bar codes on the banner pages for electronic identification and sorting

You can create new copies of the banner page exit routine to handle banners for specific applications. The new exit routines are referenced in the DTF record for the report, application, and so on.

Output Page Exit Routine

The exit routine, DPMS957, is used to modify any report page just before it is sent to the output device. You can also:

Blank out columns on report pages for security purposes

Place a time and date stamp on report pages

Count pages and lines to keep detailed SMF or other statistical records

Notify operations that a report is an emergency print




Identifying Your Exit Routines for Unicenter CA-Bundl

To indicate which exit routines you want to use, set values for the Default Device, Default Banner, and Default Out Page fields on the Processing Options Screen. See the chapter “Setting Unicenter CA-Bundl Options and Session Defaults” for more information.

By default, Unicenter CA-Bundl executes two sample exit routines, DPMS951 (produces standard Unicenter CA-Bundl banner pages) and DPMS952 (contains standard device control commands for IBM 3800 and XEROX 8700 or 9700 series laser printers).

Note: Default output page exit routines are not provided because report pages for each organization are unique.

Overriding Exit Routines for Particular Devices

By default, Unicenter CA-Bundl executes the exit routines named on the Processing Options Screen for every set of output requirements defined through a DTF record. You can, however, indicate to execute a different routine or not to execute an exit routine at all.

Do the following to override these defaults for devices that share an output requirement.

1. On the command line of any Unicenter CA-Bundl screen, enter =5.4 or select Option 4 on the Table Maintenance Menu. The DTF List Screen will display.

2. Select the desired DTF record. The DTF Detail Screen will display.

3. Change the values for the Device, Banner, and/or Outpage fields, according to these rules:

To use a different routine, specify the name of the exit routine in the corresponding field.

To use the name of the exit routine on the Processing Options Screen, leave these fields blank.



08bugc7.doc, printed on 10/29/2002, at 2:55 PM

If you do not want to use an exit routine, specify #NONE in the corresponding field.

See the Unicenter CA-Bundl Administrator Guide for more information about DTF records.

Rules for Writing an Output Exit Routine

Remember these rules when writing an output exit routine:

Assume standard linkage and register-saving conventions.

Preserve all registers except R0, R1, and R15.

Unicenter CA-Bundl arranges a page so that it has the same layout as when it is printed.

When you modify, insert, or replace pages, use the same structure as Unicenter CA-Bundl pages:

− Use a line length of 204 bytes.

− Provide no more than 150 lines per page.

− Space lines to match the layout of the page, as it appears when you print it.

− Make the first character of each line an ASA carriage control character. Or if you do not want to use a line, make the first character of the line the value X‘FF’.

Each new exit you create should be assembled and linked into CAI.CAILIB using the supplied USERMODs in SAMPJCL.

− For DPMS951, use USERMOD CC5095X

− For DPMS952, use USERMOD CC5095Y

− For DPMS957, use USERMOD CC50OPX




How Unicenter CA-Bundl Calls Output Routines

When coding an output routine, consider how many times the routines are called and the order in which they are called:

The device control exit routine is called at the start and end of each distribution break in the processing index file and a final time after all distribution break calls are made.

The exit routine is called immediately before it writes the first page of each report to the output device.

The banner page exit routine is called at the start and end of each distribution break in the processing index file and a final time after all distribution break calls are made.

The exit routine is called immediately after the device control exit routine.

Output page exit routine is called once for each page of data.

Purpose of First and Second-Level Indicators

Unicenter CA-Bundl passes the device control and banner page exit routines two values: first and second-level indicators.

The first-level indicator tells the exit routine which distribution break Unicenter CA-Bundl is checking (or it indicates that this is the final call for the exit routines).

The second-level indicator tells the exit routine whether or not Unicenter CA-Bundl is checking the beginning or end of the distribution break.

The Output Page Exit routine has no significant second-level indicators and it uses the same first-level indicators as the other exit routines.

Indicator Values for the Device Control Exit Routine

These are the indicator values for the device control exit routine and the order of the distribution breaks.




First-Level Indicator

Distribution Break Value

Output requirement D

Home code H

Mail code M

Application A

Report R

Copy C

Beginning of data page S

Final call X

Second-Level Indicator


Before begin banner page A (or 1)

Before report (inventory or user) B

Before end banner page C (or 9)

After begin banner page N

After report (inventory or user) O

After end banner page P

Note: Calls for A and C are performed only when banner pages are printed. The remaining calls are performed at all times. Final call (X) is the only first-level indicator that is not paired with a second-level indicator.




Indicator Values for the Banner Page Exit Routine

These are the indicator values for the banner page exit routine and the order of the distribution breaks.

First-Level Indicator


Output requirement D

Home code H

Mail code M

Application A

Report R

Copy C

Final call X

Second-Level Indicator


Begin banner page A (or 1)

End banner page C (or 9)

Note: The exit routine must be prepared for multiple calls. Final call (X) is the only first-level indicator that is not paired with a second-level indicator.




The following diagram shows a typical distribution break sequence:

Note: More than one value can occur within a level. More than one mail code can occur, for example, within a home code, and more than one copy can occur within a report.




Points about the Sequence of Output Distribution Distribution sequence begins at the highest level

(destination, which is really an output requirement) and works inward to the lowest level (copy).

Distribution breaks can occur more than one time in the same distribution sequence (such as the two application breaks shown in the preceding section). No level is skipped, however, and the previous lower levels end before the new levels begin.

Description of the Flow Diagram

The indicator values shown in the previous flow diagram are passed to the device control and banner page exit routines in this order: D1, H1, M1, A1, R1, C1, S, C9, R9, A9, A1, R1, C1, S, C9, C1, S, C9, C1, S C9, R9, A9, M9, H9, D9, X.

Unicenter CA-Bundl calls the banner page exit routine 23 times, the device control exit routine 27 times, and the output page exit routine once for each page on each copy of the report.

Make sure that any exit routine you write or modify affects only the part of the output you want to customize.




Additional Information about the Device Control Exit Routine The following table provides additional information about

coding a device control exit routine (DPMS952). USERMOD CC5095Y in SAMPJCL can be used to install this exit routine.


Entry Environment

Problem state, problem program key 8, addressing mode 24



R1 This register points to a full word that in turn points to a parameter block

This parameter block is shown in member DPMCOXPB in CAI.CAIMAC.

R13 This register points to the address of the standard save area

R14 This register points to the return address

R15 This register points to the entry point of the exit routine

All other registers are undefined




The Unicenter CA-Bundl device control exit routine uses the BUNOUT macro to write device control commands. Unicenter CA-Bundl includes this macro as member BUNOUT in CAI.CAIMAC. The format of the macro is:

BUNOUT OUTRTN=addr1,BUFFER=addr2,BUFFLEN=len

Variable Represents

addr1 Entry point address of the output routine that writes lines to the output data set

If you do not specify the OUTRTN parameter (optional), the value $OX@RTN is used by default.

Tip: We recommend that you specify only $OX@RTN for the OUTRTN parameter. Specify a value other than $OX@RTN only if the parameter block DSECT cannot be addressed.

addr2 Address of the output buffer

len Length of the valid portion of the output buffer

If you do not specify a value, the value 133 is used by default.

mailto:$OX@RTN

mailto:$OX@RTN

mailto:$OX@RTN




Additional Information about the Banner Page Exit Routine

This table provides details about coding a banner page exit routine (DPMS951). USERMOD CC5095X in SAMPJCL can be used to install this exit routine.


Entry Environment




R1 This register points to two full words:

+0 Points to the parameter block shown in member DPMCOXPB in CAI.CAIMAC. Supply these values in the parameter block:

At label $OXRCOPY, specify the number of banner copies to print

At label $OXRINV, specify a code to tell Unicenter CA-Bundl whether you want inventory sheets for each distribution break

Specify D to receive inventory sheets for any distribution break except report and copy; to suppress an inventory sheet, specify N.

At label $OXRLPP, specify the number of lines per page for inventory sheets





Register Usage at Entry (Continued)

+4 Points to a blank page area

Build a new banner page here

This exit routine uses the DPMS804 subroutine for block lettering required on the default banners.





Additional Information about the Output Page Exit Routine

The following table provides additional information about coding the output page exit routine, DPMS957. USERMOD CC50OPX in SAMPJCL can be used to install this exit routine.


Entry Environment



Online Security Exit Routines





R1 This register points to two full words:

+0 Points to the parameter block shown in member DPMCOXPB in CAI.CAIMAC

+4 Points to the data page

You can modify this page in any way before it is printed.






0 Print the page

4 Do not print the page

Online Security Exit Routines Unicenter CA-Bundl provides exit routines that you use to enhance online security for TSO, Advantage CA-Roscoe, CICS, and VTAM.

Important! The sample online security exits shipped with Unicenter CA-Bundl are shells (frameworks) meant to assist you in creating your own exits. They are not intended for use as shipped.




Types of Online Security Exit Routines Logon

Logoff

Mail code

View print

Application

Administrative Record Access

Logon Security Exit Routine

This exit routine is used to examine and modify which applications, Unicenter CA-Bundl functions, and mail codes to which users, administrators, and operators have access.

Note: Unicenter CA-Bundl executes this exit routine at logon time after it has created lists of authorized applications, functions, and mail codes. It creates these lists from your VSF, TSF, or Security Options records. You can use the logon security exit routine to change values set by these records.

This exit routine affects logon security in all environments. Information about validating passwords and identifiers for VTAM View users is presented in the description of the LOGONXT routine. See the Unicenter CA-Bundl VTAM View System Guide for more information about validating passwords.

Logoff Security Exit Routine

This exit routine is used to handle special needs when a Unicenter CA-Bundl session ends. You can also do the following:

Clear out any special view environment a user may have set

Get accounting information (such as CPU usage time)

Send user to a special controlling transaction (such as CICS)




Mail Code Security Exit Routine

This exit routine is used to change the list of mail codes to which a Unicenter CA-Bundl user has access.

Note: This exit routine is executed if a user attempts to access records for an unauthorized mail code. You can use this exit routine to change the list of authorized mail codes created at logon time through VSF records, your Security Options record, or a logon security exit routine.

View Print Security Exit Routine

This exit routine is used to control print requests from Unicenter CA-Bundl users. You can use this exit routine to:

Override large page values a user provides

Reject a user’s print request

Application Security Exit Routine

Used to change the list of applications to which a Unicenter CA-Bundl user has access.

Note: This exit routine is executed if a user attempts to access records for an unauthorized application. You can use this exit routine to change the list of authorized applications created at logon time through TSF records or a logon security exit routine.

Administrative Record Access Security Exit Routine

Used to control access to each of the actions specified in the SEL column of the Unicenter CA-Bundl administration selection lists.

Note: This exit routine is executed if a user specifies an action for a record on an administration selection list. Use it when you want to maintain precise control of access at the record level.




Rules for Writing an Online Security Exit Routine Assume standard linkage and register saving conventions.

Preserve all registers except R0, R1, and R15.

Because multiple users can log on to Unicenter CA-Bundl concurrently, all online security exit routines must be re-entrant.

Do not use the MVS OPEN, CLOSE, LOAD, LINK, BLDL, or TSO facilities, or any other MVS facility that implicitly or explicitly calls the WAIT supervisor.

Do not use the STIMER or TTIMER macros.

Assign the following required names to your online security exit routines.

Exit Routine Required Name

Logon Security DPMS960

Logoff Security DPMS961

Mail Code Security DPMS962

View Print Security DPMS963

Application Security DPMS965

Administrative Record Access Security

DPMS966

TSO Report Access Logging DPMS967

Coding a Logon Security Exit Routine



Comment: Sel, Type, and Action Allowed

The codes that represent the values in the Sel column on a screen correspond to the codes for the types of change requested.

Value in Sel Column

Code for Type of Change

Action Allowed

B B Browse the record

C A Add a new record when copying, adding, or inserting

D D Delete the record

E U Update the record

M A/D Add a record using the new key and delete the record with the old key; this action is performed only if a new record was added

Coding a Logon Security Exit Routine Use this information to code logon security exit routine, DPMS960, in CAI.CAISRC. CAI.PPOPTION contains two samples of this exit: SAMPT960 and SAMPV960.

Use USERMOD CC50960 in SAMPJCL to install the logon security exit routine.


Entry Environment

The entry environment is determined by the AMODE value for the load module.

Preserve this entry environment and restore it upon return. The routine must be re-entrant.






R1 This register contains the address of the parameter list, in this format:

+0 Contains the address of the environment data area. For CICS, this is the DFHEISTG address

+4 Contains the address of eight-byte user identifier

+8 Contains address of list of mail codes

Each mail code is 10 bytes long. A maximum of 65 mail codes can be included in the list. If you add to or delete from the list, you must change the total at offset +C.

+C Contains the address of a full word with the number of mail codes in the list at offset +8

Change this value if the exit routine adds or deletes mail codes.






+10 Contains an application list address

Each application identifier is 10 bytes long. A maximum of 65 application identifiers can be included in this list.

If you add identifiers to or delete identifiers from this list, you must change the total at offset +14.

+14 Contains the address of a full word that indicates the number of application identifiers in the application list at offset +10

If you add or delete identifiers, change this value.

+18 Contains the address of the first of two full words that control access to the administration functions

These full words determine whether a user has edit or browse access to Unicenter CA-Bundl screens.

+1C Contains the address of a 32-byte user area passed to all exit routines

R13 This register contains the address of the standard save area

R15 This register contains the entry point address of the exit routine


Coding a Logoff Security Exit Routine





0 Continue with initialization

4 The user identifier has been modified

The new list of mail codes for the modified user identifier is appended to the existing list of mail codes. After the list is updated, the exit routine is called again.

8 Terminate this session immediately

Note: You must restore all registers (except 0, 1, and 15) upon return.

Coding a Logoff Security Exit Routine Use this information to code logoff security exit routine, DPMS961, in CAI.CAISRC. USERMOD CC50961 in SAMPJCL can be used to install this exit routine.


Entry Environment

The entry environment is determined by the AMODE value for the load module

Preserve this entry environment and restore it upon return. This exit routine must be re-entrant.

Coding a Mail Code Security Exit Routine





R1 This register contains the address of the parameter list in the following format:

+0 Contains the address of the environment data area. For CICS this is the address of DFHEISTG

+4 Contains the address of the eight-byte user identifier

+8 Contains the address of a 32-byte user area passed to all exit routines




Coding a Mail Code Security Exit Routine Use this information to code mail code security exit routine, DPMS962, in CAI.CAISRC. USERMOD CC50962 in SAMPJCL can be used to install this exit routine.


Entry Environment


Preserve this entry environment and restore it upon return. This exit routine must be re-entrant.

Coding a Mail Code Security Exit Routine








+8 Contains the address of the list of mail codes

Each mail code is 10 bytes long, and a maximum of 65 mail codes can be included in the list. If you add mail codes or delete mail codes from this list, you must change the total at offset +C.

+C Contains the address of a full word with the number of mail codes in the list at offset +8

Change the value if exit routine adds or deletes mail codes from the list.

+10 Contains the address of the 10-byte mail code to be checked.

+14 Contains the address of a 32-byte user area passed to all Unicenter CA-Bundl exit routines




Coding a View Print Security Exit Routine





Any value greater than 0 indicates that the user is authorized to view the mail code


Coding a View Print Security Exit Routine Use this information to code view print security exit routine, DPMS963, in CAI.CAISRC. USERMOD CC50963 can be used to install this exit routine.


Entry Environment


Preserve this entry environment and restore it upon return, the exit routine must be re-entrant.

Coding a View Print Security Exit Routine






+0 Contains the address of the environment data area. For CICS, this is the address is DFHEISTG.


+8 Contains the address of the nine-byte beginning page number

+C Contains the address of the nine-byte ending page number

+10 Contains the address of the one-byte SYSOUT class

+14 Contains the address of the eight-byte device identifier

+18 Contains the address of the eight-byte remote identifier

+1C Contains the address of the four-byte mode

+20 Contains the address of the three-byte number of copies

+24 Contains the address of the DTF record for this request

+28 Contains the address of a 32-byte user area passed to all Unicenter CA-Bundl exit routines




Coding an Application Security Exit Routine





Any value greater than 0 indicates that the print request is to be canceled


Coding an Application Security Exit Routine Use this information to code application security exit routine, DPMS965, in CAI.CAISRC. CAI.PPOPTION contains a sample of this exit, SAMPC965. USERMOD CC50965 in SAMPJCL can be used to install this exit routine.


Entry Environment


Preserve this entry environment and restore it upon return. This routine must be re-entrant.

Coding an Application Security Exit Routine








+8 Contains the address of the list of application identifiers

Each identifier is 10 bytes long, and you can include a maximum of 65 application identifiers. If you add identifiers to or delete identifiers from this list, you must change the total at offset +C.

+C Contains the address of a full word with the number of application identifiers in the list at offset +8

Change this value if the exit routine adds or deletes identifiers from the list.

+10 Contains the address of the ten-byte application identifier to be checked

+14 Contains the address of a 32-byte user area passed to all exit routines




Coding an Administrative Record Access Security Exit Routine





Any value greater than 0 indicates that the user is authorized for that application identifier



Use this information to code administrative record access security exit routine, DPMS966, in CAI.CAISRC. USERMOD CC50966 in SAMPJCL can be used to install this exit routine.


Entry Environment


Preserve this environment and restore it upon return. This exit routine must be re-entrant.



+0 Contains the address of the environment data area

For CICS, this is the address of DFHEISTG.






+4 Contains the address of the 8-byte user identifier

+8 Contains the value entered in the Sel column next to the record. This value can be: B, C, D, E, or M.

+C Contains a code to represent the type of change to the record that is being requested

Codes and the type of change they represent are:

A Add D Delete B Browse U Update

See the table in "Comment: Sel, Type, and Action Allowed" for a description on how these values correspond to the values specified in the Sel column.

+10 Contains a three-byte, uppercase name of the file being accessed

+14 Contains the address of the copy of the key of the record being accessed

+18 Contains the application code from the record being accessed, if it appears once in the record, or low values

+1C Contains the mail code from the record being accessed, if it appears once in the record, or low values

+20 Contains the address of the 32-byte user area passed to all exit routines


R14 This register contains the return address

Coding a TSO Report Access Logging Exit Routine








Any value greater than 0 indicates that access is to be denied


Coding a TSO Report Access Logging Exit Routine Use this information to code TSO report access logging security exit routine, DPMS967, in CAI.CAISRC. CAI.PPOPTION contains a sample exit, SAMPC967. USERMOD CC50967 can be used to install this exit routine.


Entry Environment


Preserve this environment and restore it upon return. This routine must be re-entrant.


R1 This register contains the address of the parameter list, in the following format:

+0 Contains the address of the environment data area. For CICS, this is the address of DFHEISTG

+4 Contains the address of the 8-byte user identifier

+8 Contains the address of the 7-character context code

Coding a TSO Report Access Logging Exit Routine





+12 Contains the address of primary record buffer

+14 Contains the address of a full word that indicates the number of application identifiers in the application list at offset +10

If you add or delete identifiers, you must change this value.

+16 Contains the address of the secondary record buffer (or 0 if it is not needed)

+20 Contains the address of the 100-byte message buffer

If exit moves text into this area, it is written to the log as message identifier 7967. Upon entry, this buffer is always set to nulls. Upon return, the text is assumed to end at the first null (x'00) byte. If the first byte is NULL, a message is not logged.

+24 Contains the address of the 32-byte static area that is passed to all exits for inter-exit communication




Coding the Cooperative Processing Logon Security Exit Routine





Any value greater than 0 indicates that the action is not to be permitted (logging is not allowed unless a message is copied to the message buffer)



Sample security exit, DPMS969, is used with the Unicenter Output Management Document Viewer or Unicenter Output Management Web Viewer products to control user ID and password validation. The DPMS969 exit routine is called by the Unicenter CA-Bundl cooperative processing agents to control access.

Use this information to code the Cooperative Processing security exit routine, DPMS969 in CAI.CAISRC. USERMOD CC50969 in SAMPJCL can be used to install this exit routine.

The user exit parameter list, BUNDUPL, in the CAIMAC library is included in this program and is passed into DPMS969 in register 1.

This exit routine validates the user ID and password using the RACROUTE REQUEST=VERIFY function. When the password has expired, the user ID is prompted for a new password in the Unicenter Output Management Document Viewer and Unicenter Output Management Web Viewer products. The new password is validated in DPMS969.





Entry Environment



R1 This register contains the address of the parameter list (mapped by BUNDUPL), in the following format:

+0 Contains the address of the 8-byte user ID

+4 Contains the address of the 8-byte user password

+8 Contains the address of the 8-byte new password

+C Contains the address of the 24-byte area into which the short message may be returned

+10 Contains the address of the 78-byte area into which the long message may be returned

+14 Contains the address of the 8-byte cursor position

+18 Contains the address of the 8-byte cross memory connection ID

+1C Contains the address of the exit communication area

If the exit moves text into this area, the text is written to the Unicenter CA-Bundl log as message identifier 7967. Upon entry, this buffer is always set to nulls. Upon return, the text is assumed to end at the first null (x'00) byte. If the first byte is NULL, a message is not logged.






+20 Contains the address of the security area (I.E.ACEE)

+24 Contains the address of the UPL extension

+28 Contains the user exit work area of 60F

+268 Contains the user exit short message 24 characters

+50C Contains the user exit long message 78 characters


R14 This register contains the return addressR15

This register contains the entry point address of the exit routine



Any value greater than 0 indicates that access is denied. The following values are set into Register 15 prior to the return to the caller:

R15 value '4' - Invalid user ID/ access denied

R15 value '8' - Invalid password

R15 value '12' - Password expired

R15 value '16' - Invalid new password

R15 value '20' - Unidentified error


Disk Space Allocation A–1


Appendix

A Disk Space Allocation

This appendix provides information for determining the amount of disk space to allocate for running Unicenter CA-Bundl.

Disk Space Allocated to Page Data and View Page Files

Unicenter CA-Bundl supports a maximum of ten Page Data files (PDF0-9) and ten View Page Files (VPF0-9). All VSAM file cluster definitions are included on your installation tape in the CAI.PPOPTION library.

Each VSAM file cluster should be reviewed and updated with your standard file name, disk volumes, and number of records.

The CAI.PPOPTION members, as delivered, are set to an average record size for installation and testing. However, determining the actual number of records required for these files should be made from your existing CA-Bundl 4.9 file definitions or calculated from the following size chart:

Factors in Projecting DASD Requirements for Page Data Files

A–2 Getting Started


3380 (single density)

3390 (single density)

Approximate Daily Capacity

Number of Usable Page Files Vols. Cyls. Vols. Cyls.

< 25,000 lines 1 .02 15 .01 12

< 250,000 lines 3 .12 100 .07 81

< 2,500,000 lines 3 .60 500 .36 405

< 5,000,000 lines 4 .90 800 .58 648

< 10,000,000 lines 5 1.60 1400 1.01 1134

< 20,000,000 lines 7 2.95 2600 1.89 2106

< 40,000,000 lines 10 5.65 5000 3.64 4050

Factors in Projecting DASD Requirements for Page Data Files

To project how much DASD you need to provide for Unicenter CA-Bundl page data files, consider these factors:

A print line averages 40 bytes

A page averages 2K bytes

Note: Your actual requirements may vary. Review the Archive Status Report produced by the Unicenter CA-Bundl DPMB004 program to see your actual averages. If your DASD requirement exceeds 4 GB, see the topic Extended Addressability for the Unicenter CA-Bundl VSAM Files that follows in this chapter for more information.

Managing Space Effectively



Extended Addressability for the Unicenter CA-Bundl VSAM Files

Unicenter CA-Bundl uses KSDS VSAM file architecture supported by standard IBM VSAM service routines and utilities. Beginning with DFSMS/MVS Version 1 Release 3.0, you can create and use VSAM KSDS files larger than the original 4 GB limit imposed by earlier releases to a maximum size of 128 TB.

To define a KSDS VSAM file with extended addressability, the data set must be defined with a data class specifying the DSNTYPE=EXT as well as EXTENDED ADDRESSABILITY=Y.

To change KSDS files to extended addressability, use the IDCAMS ALTER command.

Managing Space Effectively When Unicenter CA-Bundl collects a report, the following messages are generated. Use the information in these messages to manage space effectively.

BND7058: lists number of pages written to the page data file

BND7059: lists number of bytes of input collected for the report

BND7060: lists number of bytes of compressed input

BND7061: lists percentage input is compressed

BND7062: lists average page size, after compression

Note: You need additional DASD for index files and control tables.

Unicenter CA-Bundl Files



Unicenter CA-Bundl Files The tables in this section describe the Unicenter CA-Bundl distribution index files, control tables, and storage files.

Distribution Index Files

File Description

DPMFAIF Archive Index File

The “archived reports index” that maps the contents of the archive data sets. Entries are created in this file for each archived copy of the report.

DPMFAIF0-9 Split Archive Index Files

Program DPMB074, AIF Split Utility, allows you to split your AIF file into a new AIF and AIF0-9 files. The split can be done by year range (1-9).

DPMFPIF Processing Index File

Stores the indexes of reports to be processed during a particular execution of the distribution job.

DPMFRIF Reprint Index Work File

This is a work file built by Program DPMB005A.

DPMFRIFO Online Reprint Index File

The “selected reprint index” that maps the contents of the reprint page data file. Entries are created in this file for each reprint request made.

DPMFSIF Sorted Index File

The “operations index” that maps the contents of the page data files. Entries are created in this file for each copy or distribution of the report.




File Description

DPMFVIF View Index File

The “current report index” that maps out the contents of the view data files. Entries are created in this file for each copy or distribution of the report.

Control Table Files

File Description

DPMFATF Application Table File

Stores the records that identify each application identifier used in Unicenter CA-Bundl distribution rules.

DPMFBSF Unicenter CA-Bundl System File

Stores system-processing information.

DPMFDSF Input Data Set File

Stores the records that define (for Unicenter CA-Bundl) the data sets Unicenter CA-Bundl is to collect.

DPMFDTF Device Output File

Stores the records that define (for Unicenter CA-Bundl) the output requirements for reports.

DPMFLGF Banner Page Logo File

Stores records that define (for Unicenter CA-Bundl) all the different logos that appear on the banner page.




File Description

DPMFMCF Mail Code File

Stores the records that define delivery information that is to appear on the banner for each mail or home code.

DPMFRTF Report Table File

Stores the records that define rules that identify each report and control break identifier used in Unicenter CA-Bundl distribution rules.

DPMFRDF Report Distribution Table File

Stores the records that describe the specific distribution rules for each particular part of a report or for the report as a whole.

DPMFSCH Schedule File

Stores the records that control job submission by Unicenter CA-Bundl.

DPMFSHF Standard Header File

Stores records that replace, alter, or add standard information to report pages.

DPMFSRF Standard Rule File

Stores records that direct parts of a report to several mail codes or mail lists or several parts of a report to go to one mail code or mail list.

DPMFSTF Source Translate File

Stores records that translate a value from a report to a specific mail code or to mail lists. Job names can also be translated into mail codes or mail lists.




File Description

DPMFTSF Terminal Security File

Stores records that define the functions a user may access when the Unicenter CA-Bundl function security is used.

DPMFVSF View Security File

Stores records that define the mail codes a user may access when Unicenter CA-Bundl mail code security is used.

Storage Table Files

Collector Page Storage File

Description

DPMFPDF0 thru DPMFPDF9

Page data files contain compressed report data after it is collected. Data is retained in the page files until the page data files are reset by end-of-day processing.

DPMFVPF0 thru DPMFVPF9

View Page files contain highly compressed report data to be retained for online view access.

Miscellaneous Page Storage Files

Description

DPMFRPF Reprint Page Data File

Stores the reports to be printed after the data has been retrieved from archive.




Miscellaneous Storage Files

Description

DPMFMAP Map File

A collection of maps used throughout Unicenter CA-Bundl for the online, help, and tutorial screens.

DPMFPSF Processing Statistics File

Stores information about pages collected and distributed to view, paper, and fiche. File is reset during the end-of-day processing.

DPMFSSF Statistical Summary File

Stores the statistical processing information collected each day in the DPMFPSF by month and year.

Index–9


Index

A

ACCEPT processing, overview of, 2–3 SMP, 4–32

ACCEPTing services, 4–32

access, user, 5–7

addressability, extended, A–3

administrative record access security exit routine, 7–25, 7–37

Adobe Acrobat Reader, downloading the, 1–3

Advantage CA-Roscoe, installing, 4–23

allocating disk space, A–1 distribution libraries, 4–8 private SMP/E libraries, 4–9 target libraries, 4–8

application security exit routine, 7–25, 7–35 table file, A–5, A–6

Application field, 5–5, 6–11

Applications For This User field, 5–14

applications, granting authority to, 5–10

APPLY processing, overview of, 2–3

archive file split procedure, 4–18

Archive Index File (AIF), A–4

Archived Report List screen, 5–8

ATF – Application IDs, 5–8

authority, granting, 5–10, 5–14

Auto-save View Settings field, 6–8

B

banner page exit routine, 7–11, 7–16, 7–21 logo file, A–5

Banner Pages field, 6–9

BUNOUT macro, 7–20

C

CA Common Services, 3–1 services component, 3–6

CA-Bundl: VSF Detail Screen, 5–21

CA-DRAS (Distributed Repository Access System), 3–6

CAI Resource Initialization Manager (CAIRIM), description of, 3–1

CAIDS60, 4–9

Index–2 Getting Started


CAILIB (CAI Common Load Library), 3–7

CAINITE5, 4–9

CAIRIM (CAI Resource Initialization Manager), 2–1

CA-LMP (License Management Program), description of, 3–2

CA-LServ installing, 3–2 setting up, 4–27

CC50APP, 4–10

CC50SMPE, 4–10

changes in Unicenter CA-Bundl 5.0, 1–4

CICS, installing, 4–21

collection procedure, 4–18

Column Separator(s) field, 6–8

commands assigning to PF keys, 6–21 conventions used to represent, 1–11 Equals (=), 6–17 Startup, 6–17

common clist library, 3–5

component product codes, 4–14

components CA Common Services, 3–6 CA-DRAS, 3–6 product, 3–6

control table files, A–5 DPMFATF, A–5, A–6 DPMFBSF, A–5 DPMFDSF, A–5 DPMFDTF, A–5 DPMFLGF, A–5 DPMFMCF, A–6 DPMFRDF, A–6 DPMFRTF, A–6 DPMFSHF, A–6 DPMFSRF, A–6 DPMFSTF, A–6

DPMFTSF, A–7 DPMFVSF, A–7

conventions commands, 1–11 Enter key, 1–10 programmable function (PF) keys, 1–10 special typeface, 1–10 variables, 1–11

cooperative processing, 4–1 logon security exit routine, 7–41

creating production VSAM files, 4–29

Current Reports List screen, 5–8

customization clist, 4–14

D

DASD, requirements for page data files, A–2

Date Filter Span field, 6–14

Date Format field, 6–7

date formats, 1–11

Default Banner field, 6–5

Default Device field, 6–5

Default Max PDF field, 6–3

Default Min PDF field, 6–3

Default Out Class field, 6–4

Default Out Page field, 6–6

Default User Option Screen, 6–6

defaults establishing, 5–24 setting option, 6–19

Dest/Node field, 6–16

device control exit routine, 7–10, 7–14, 7–19 output File, A–5

Index–3


Device ID field, 5–22

disk space, allocation of, A–1

distribution index files

DPMFAIF, A–4 DPMFAIF0-9, A–4 DPMFPIF, A–4 DPMFRIFO, A–4 DPMFSIF, A–4 DPMFVIF, A–5

libraries, 3–5 output, sequence of, 7–18 procedure, 4–18 tape, product, 3–4

documentation list of, 1–1 viewing and printing, 1–3

DPMS960 security exit, 7–27







DSF – Input Data Set, 5–8

DTF – Device Output, 5–9

E

End User field, 5–12

end-user facilities, starting the, 4–24

Equals (=) command, 6–17

Execution JCL, 4–14

exit routine, banner page, 7–16

exit routines administrative record access security, 7–25, 7–37 application security, 7–25, 7–35 banner page, 7–11, 7–21 cooperative processing logon security, 7–41 device control, 7–10, 7–14, 7–19 granting authority through, 5–14 how to override for devices, 7–12 identifying, 7–12 input page, 7–1, 7–2, 7–4 logoff security, 7–24, 7–30 logon security, 7–24, 7–27 mail code security, 7–25, 7–31 online security, 7–23 output

calling order of, 7–14 page, 7–11, 7–22 rules for writing, 7–13

rules for writing, 7–26 TSO report access logging security, 7–39 view print security, 7–25, 7–33

extended addressability, A–3

F

fields Application, 5–5, 6–11 Applications For This User, 5–14 Auto-save View Settings, 6–8 Banner Pages, 6–9 Column Separator(s), 6–8 Date Filter Span, 6–14 Date Format, 6–7 Default Banner, 6–5 Default Device, 6–5 Default Max PDF, 6–3 Default Min PDF, 6–3 Default Out Class, 6–4 Default Out Page, 6–6 Dest/Node, 6–16 Device ID, 5–22



End UserR, 5–12 Form, 6–16 Function, 5–5 Home Cd Banners, 6–4 Home Code, 6–11 Job Number Flag, 6–4 Language Preference, 6–7 Line Numbers, 6–10 Mail Cd Banners, 6–3 Mail Code, 6–11 Mail Codes for this User, 5–23 Master User ID, 5–4 Max Pages/Find, 6–5 Max Reprint Retpd, 6–5 Operator, 5–12 PF, 6–21 Process Date, 6–2 Reformat Option, 6–9 Remote ID, 6–16 Report, 6–11 Report Order, 6–13 Restrict MCF Records, 5–6 Retail Filters, 6–13 Ruler Line(s), 6–8 Selection List Qualifiers, 6–7 Seq No, 5–21 Sys Admin, 5–12 SYSOUT Class, 6–9 Use Wildcard Filters, 6–12 User ID, 5–12, 5–21 User Name, 5–12, 5–21 Wait Minutes, 6–2

files AIF (Archive Index File), A–4 application table, A–5, A–6 ATF – Application IDs, 5–8 banner page logo, A–5 control table, A–5

DPMFATF, A–5, A–6 DPMFBSF, A–5 DPMFDSF, A–5 DPMFDTF, A–5 DPMFLGF, A–5 DPMFMCF, A–6 DPMFRDF, A–6

DPMFRTF, A–6 DPMFSHF, A–6 DPMFSRF, A–6 DPMFSTF, A–6 DPMFTSF, A–7 DPMFVSF, A–7

device output, A–5 distribution index, A–4

DPMFAIF, A–4 DPMFAIF0-9, A–4 DPMFPIF, A–4 DPMFRIF, A–4 DPMFSIF, A–4 DPMFVIF, A–5

DSF – Input Data Set, 5–8 DTF – Device Output, 5–9 input data set, A–5 LGF – Banner Page Logo, 5–10 mail code, A–6 Map, A–8 MCF – Mail Codes, Lists, 5–9 PIF (Processing Index File), A–4 Processing Statistics, A–8 RDF – Basic Distribution, 5–9 report

distribution table, A–6 table, A–6

Reprint Page Data, A–7 RTF – Report IDs, 5–8 SCH – Scheduling, 5–10 SHF – Text Changes, 5–9 SIF (Sorted Index File), A–4 source translate, A–6 SRF – Standard Rule, 5–9 standard

header, A–6 rule, A–6

Statistical Summary, A–8 STF – Translation Rule, 5–9 storage table, A–7

DPMFMAP, A–8 DPMFPSF, A–8 DPMFRPF, A–7 DPMFSSF, A–8

terminal security, A–7 TSF – Func, Appl Security, 5–9

Index–5


Unicenter CA-Bundl system, A–5 view

page, A–7 security, A–7

VIF (View Index File), A–5 VSF – View Security, 5–9

fileserver, using Unicenter CA-Bundl with, 4–34

FMIDs, 4–10

fonts, use of special, 1–10

Form field, 6–16

formats, date, 1–11

Function field, 5–5

H

hardware requirements, 3–5

Home Cd Banners field, 6–4

Home Code field, 6–11

I

input data set file, A–5 page exit routine, 7–1, 7–2, 7–4

installation materials, 3–4 testing the, 4–28

installing Advantage CA-Roscoe, 4–23 CA-LServ, 3–2, 4–27 CA-View, overview of, 2–1 CICS, 4–21 TSO Interface, 4–26 Unicenter CA-Bundl

loading the SAMPJCL, 4–7

using SMP/E, overview of, 2–3 VTAM View, 4–24

ISPF library, 3–5

italics, use of, 1–11

J

JCL, location of sample, 3–4

Job Number Flag field, 6–4

K

keys Enter, 1–10 PF, 1–10 Return, 1–10

L

Language Preference field, 6–7

LGF – Banner Page Logo, 5–10

libraries allocating, 4–8

distribution, 4–8 private SMP/E, 4–9 target, 4–8

distribution, 3–5 target, 3–5

library authorization, 3–7

Line Numbers field, 6–10

LMP (License Management Program), 3–2 execution key, 4–13 key certificate, 4–11

load library, 3–5



logoff security exit routine, 7–24, 7–30

logon security exit routine, 7–24, 7–27 providing, 5–15

M

macro library, 3–5

macros, BUNOUT, 7–20

Mail Cd Banners field, 6–3

mail code file, A–6 security exit routines, 7–25, 7–31

Mail Code field, 6–11

mail code-level security activating, 5–27 establishing defaults, 5–23 providing, 5–19

Mail Codes for this User field, 5–23

mail codes, authorizing users for, 5–26

Main Menu, displaying from any screen, 6–17

major SMP/E operations, 2–3

managing space, A–3

map file, A–8

Master User ID field, 5–4

Max Pages/Find field, 6–5

Max Reprint Retpd field, 6–5

MCF – Mail Codes, Lists, 5–9

MCF records, 5–14

menus, System Options, 5–10

modification control statements (MCS), 2–3, 3–4

multiple LMP codes, 4–14

O

online facility option, 1–11 reprint index file, A–4 security

exit routine, rules for writing, 7–26 exit routines, 7–23

types of, 7–24 system, starting the, 4–24

Operations Menu screen, 5–8

Operator field, 5–12

options setting defaults for, 6–19 setting processing, 6–18

Options Page 2 screen, 6–10

output exit routines, 7–10

calling order of, 7–14 rules for writing, 7–13

page exit routine, 7–11, 7–22

P

PF field, 6–21

PF keys, rules for assigning commands to, 6–21

PIF (Processing Index File), A–4

Process Date field, 6–2

processing index file, A–4 options, setting, 6–18

Processing Options Screen, 6–1

Index–7


Processing Statistics File, A–8

product changes, summary of, 1–4 codes, component, 4–14 tape, 3–4

Product Temporary Fix (PTF), 4–34

programmable function keys, 1–10

R

RDF – Basic Distribution, 5–9

RECEIVE processing, overview of, 2–3 SMP, 4–10

records security options, modifying, 5–6 VSF, 5–24

Reformat Option field, 6–9

related documentation, list of Unicenter CA-Bundl, 1–3

Remote ID field, 6–16

report, 3–5 distribution table file, A–6 table file, A–6

Report field, 6–11

Report Order field, 6–13

reprint data file, A–7 index work file, A–4

requirements hardware, 3–5 system, 3–1

Restrict MCF Records field, 5–6

Retail Filters field, 6–13

routines, output exit, 7–10

RTF – Report IDs, 5–8

Ruler Line(s) field, 6–8

S

sample JCL, location of, 3–4

SCH – Scheduling, 5–10

screens Archived, 5–8 CA-Bundl: Security Options Screen, 5–4 CA-Bundl: VSF Detail Screen, 5–21 Current Reports List, 5–8 Default User Option, 6–6 granting authority to, 5–10 Operations Menu, 5–8 Options Page 2, 6–10 Processing Options Screen, 6–1 System Options Menu, 5–10 TSF Detail: Application Security Screen, 5–11

security activating mail code-level, 5–27 mail code-level, 5–19, 5–23 options record, modifying, 5–6 overview of, 5–2 providing logon-level, 5–15 restricting, 5–19, 5–23, 5–26, 5–27 types of, 5–2

security exits DPMS960, 7–27 DPMS961, 7–30 DPMS962, 7–31 DPMS963, 7–33 DPMS966, 7–37 DPMS967, 7–39 DPMS969, 7–41

Selection List Qualifiers field, 6–7

Seq No field, 5–21

sequence of output distribution, 7–18



sessions, TSO Interface, setting defaults for, 6–19

SHF – Text Changes, 5–9

SIF (Sorted Index File), A–4

SMP procedure, customizing, 4–10

sorted index file, A–4

source translate file, A–6

split archive index file, A–4

SRF – Standard Rule, 5–9

standard header file, A–6 rule file, A–6

starting the online system and end-user facilities, 4–24

Startup commands, 6–17

Statistical Summary File, A–8

STF – Translation Rule, 5–9

storage table files, A–7 DPMFMAP, A–8 DPMFPSF, A–8 DPMFRPF, A–7 DPMFSSF, A–8

Sys Admin field, 5–12

SYSOUT Class field, 6–9

System Options Menu, 5–10

system requirements, 3–1

T

target libraries, 3–5

terminal security file, A–7

testing the installation, 4–28

TSF – Func, Appl Security, 5–9

TSF Detail: Application Security Screen, 5–11

TSO Interface, installing, 4–26 report access logging security exit routine, 7–39

U

Unicenter CA-Bundl Customization Worksheet for, 4–3 documentation, 1–1 loading the SAMPJCL, 4–7 related documentation, 1–3 security, 5–2 setting

option defaults, 6–19 processing options, 6–18

system file, A–5 using with file server, 4–34

upgrading Unicenter CA-Bundl from 4.9 to 5.0, 4–30

Use Wildcard Filters field, 6–12

User ID field, 5–12, 5–21

User Name field, 5–12, 5–21

users authorizing, 5–26 authorizing mail codes for, 5–26

Using a single file server with multiple Unicenter CA-Bundl systems, 4–34

V

variables, conventions used to represent, 1–11

Index–9


view index file, A–5 page file, A–7 print security exit routine, 7–25, 7–33 security file, A–7

VIF (View Index File), A–5

VSAM files creating production, 4–29 initializing test, 4–19

VSF – View Security, 5–9

VSF records, 5–24

VTAM View, 4–18 installing, 4–24

W

Wait Minutes field, 6–2


K007791E - Getting Started

Documents