Changeman Administrator Guide

July 2002

VERSION 5.3

Administrator Guide

COPYRIGHT

This manual, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by such license, no part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of SERENA Software, Inc. The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by SERENA Software, Inc. SERENA Software, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this book.

Copyright © 2001, 2002 SERENA Software Inc. All rights reserved.

TRADEMARKS

ChangeMan, Comparex, StarTool, StarWarp, UltiMIS, ULTIMIZER, Eye-Spy, Eye-Spy/390, Detect+Resolve, SERNET, eChange Man and Change Transfer are registered trademarks of SERENA Software, Inc. Serena, Merge+Reconcile, FULL.CYCLE, eHealing, eFull.Cycle, eRequestMan, ChangeXpress, ChangeContent, StarProbe, StarSpy, StarTest, StarSuite, and SER10TY are trademarks of SERENA Software, Inc.

IBM, IMS, DB2, DFSMShsm, RACF, MVS/ESA, and MVS are trademarks and registered trademarks of the International Business Machines Corporation in the United States, other countries, or both. All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.

Publication Date: July 19, 2002

3

CONTENTS

About This Book 9

Before You Begin 9Name Change 9Objective 9Audience 9Components / Scope 9Manual Organization. 11Related Publications. 11Support 12Using Online Help 13

Online Tutorial 13Online Help Screens 13Online Error Messages 13

Chapter 1: IntroductionWhat is the ChangeMan ZMF Administrator Guide 15ChangeMan ZMF Administrator 15

Global Administrator 15Application Administrator 16Security Administrator 16ChangeMan ZMF Monitor 16General Administrator 16

Chapter 2: What is ChangeMan ZMF?Change Packages 19Impact Analysis 19Checkout 20Staging 20Audit 21Recompile and Relink 21Freeze 22Promotion 22Approval 22Production Installation 23

4

Contents

Baseline Libraries and Delta Decks 23Backout Management Facilities 23Emergency Changes 24

Chapter 3: Pre-Implementation DecisionsCustomizing ChangeMan ZMF for Your Site 25

Modify Skeletons 25Implement Exits 25Establish Initial History Records 25

Managing Library Space 26Allocating Staging Libraries 26Allocating Baseline Libraries 26Allocating Promotion Libraries 27Allocation Production Libraries 27

Using Baseline Libraries for Production Libraries 27Setting Up Remote Sites for Production Libraries 28Setting Up Security 28

Security Entities 29Securing Libraries 30Granting User Access 33

Setting Up User Restrictions 34Allow Temporary Change Packages 35Work Request and Department Number Required 35Planned Installation Calendar 35Disable Installation Calendar 36Normal Business Hours 36Overlay Prior Staged Component 36Checkout Enforcement 36Allow Concurrent Checkout 37Validate Version During Staging 37Staging Restriction Level 37Audit Level 37Designated Procedures 38Secured Components 38Approval Lists 38

Other Considerations 39Global Parameters for Staging Library Allocation 39Application Parameters for Staging Library Allocation 39Edit Staging Recovery Mode 39Query Of Available Users Options 40Keep Baseline By Site 40

5

Serena™ ChangeMan® ZMF 5.3 Administrator Guide

Remote Sites 40Package Approvals 40Promotion And Demotion 41

How Does Promotion Work 41Promotion Library Cleanup 42Promotion Security 43Promotion Rule 43Promotion Rule By Promotion Level 45Promotion Rule 0 45First Promote 46Other Restrictions And Options 46Promotion Paths 47Approvals and Promotion 47Promotion Libraries In SYSLIB Concatenations 48

Enterprise Change Packages 48Staging Versions 49

Staging Versions Installed 49Staging Versions Enabled 49Serena™ ChangeMan® M+R Licensed 50Considerations For Staging Versions 50

Implementation Checklist 50ChangeMan ZMF Administrator Duties 52

Chapter 4: Setting Up Global AdministrationAccessing the Global Administration Options 55Setting up Global Parameters 56Defining Library Types And Staging Library Attributes 72Defining the Languages 79Defining the Compiling Procedures 80Defining Reason Codes 81Defining Sites 82Locking or Unlocking Application Definitions 86Setting the Planned Installation Calendar 88Creating or Updating the Global Notification File 90

Enabling the Global Notification Facility 90Creating Global Notification Messages 91Updating the Global Notification Message 92

Accessing the Global Selectable Options 94Using Package User Records 95

6

Contents

Chapter 5: Setting Up Application AdministrationHow Global Settings affect Application Settings 97Accessing Application Administration 97

Creating a New Application 98Updating Existing Applications 99Locks on Application Administration 100

Setting Application Parameters 100Defining Library Types And Staging Library Attributes 111

Library Type Order 111Defining Library Types for a New Application 112Updating Application Library Types 119

Defining the Languages 122Defining the Compiling Procedures 123Setting Up Planned Approvals 124Setting Up Unplanned Approvals 127Defining Application Sites 129

Defining Sites For A New Application 129Updating Application Site Information 131

Configuring Promotion Sites, Levels, and Libraries 132Promotion Definition Order 133Configuring Promotion For A New Application 133Update Promotion For An Application 140

Configuring Baseline Libraries 144Allocating Baseline Libraries 144

Defining Optional Component Descriptions, Procedure, and Security 147Defining Component General Information 147

Deleting Components 149Updating the components in either component list. 149

Designate Optional Component Compiling Procedures 150Setting Component Security 152

Specify the component to be updated. 152Access a Package Driven Security List. 153Complete the Component Level Security Panel. 153Delete a component’s security entries. 153Delete, enter or update component secured ID’s. 154

Deleting an Application 154Accessing the Application Selectable Options Panel 155Updating the Global Notification File 155Configuring Production Libraries 158Configuring Temporary Packages for ALL Sites 159

7


Chapter 6: Custom ModificationsInitial Skeleton Modifications 161Customizing ChangeMan ZMF 161

User Exits In ChangeMan ZMF 161ISPF Skeletons In ChangeMan ZMF 162ChangeMan ZMF Utilities 162

Chapter 7: Monitoring Site and Application PackagesAccessing the Monitor Option Panel 164

Querying Package Information 164Packages in Limbo 165

Acting on Packages 165Closing a Super or Complex Package 166Manually Submitting a Package in Limbo for Installation 166

Installation Jobs 167Monitoring the ChangeMan ZMF Internal Scheduler 170

Reviewing the Internally Scheduled Packages List 171Acting on the Packages 171

Chapter 8: Configuring Remote SitesOverview of Remote Sites 173How does it Work? 173Setting Up Remote Sites Globally 174Maintaining Remote Sites 175Setting up Remote Sites for Applications 176Establishing a Remote Site - Global Administrator 176Selecting a Remote Site - Application Administrator 179Updating an Existing Site - Application Administrator 179Enabling the Network Data Mover 180

Chapter 9: Defining and Running ChangeMan ZMF ReportsChangeMan ZMF Reports 183SAS or Assembler Report Programs 185

Generating Reports With SAS 185Generating Reports Without SAS 186

Defining and Running Reports: Global Administrator 187Accessing Global Reports 187Run Reports: Global Administrator 190Baseline Analyzer Report: Global Administrator 192Link Date Report: Global Administrator 192

8

Contents

DB2 Object Dependency Report: Global Administrator 193Defining and Generating Reports: Application Administrator 193

Accessing Application Reports 193Define Reports: Application Administrator 194Run Reports: Application Administrator 196Baseline Analyzer Report: Application Administrator 198Link Date Report: Application Administrator 198DB2 Object Dependency Report 199

Baseline Analyzer Report 199Baseline Analyzer Report 199Sample Baseline Analyzer Report 202

Link Date Report 204Link Date Report Example 204Link Date Report Data 205

Chapter 10: Housekeeping TasksCleaning Up Backup Libraries 207

Bypass Cleanup of Backup Libraries 207Perform Package Processing for Backup Library Cleanup 208Perform Commit Processing for Backup Library Cleanup 214Considerations for Cleaning up Backup Libraries 219

Running Reports 221Log Activities (CMNBAT30) 222

Index 223

9

ABOUT THIS BOOK

BEFORE YOU BEGIN

See the README for the latest updates and corrections for this manual.

A printed copy of the README is included in the Serena™ ChangeMan® ZMF distribution box. The latest version of the README is available on the Serena eSupport self-service Web site at Support.Serena.com. After you logon, click FTP Downloads from the main portal, navigate to the Documentation folder, and then to the ChangeMan ZMF folder.

NAME CHANGE

This document describes Serena™ ChangeMan® ZMF, Software Change Manager for z/OS & OS/390. This product of SERENA Software, Inc., was previously called Change Man. The new name more clearly reflects the role of the product in the Serena™ ChangeMan® family of products. Note that the product was also called Serena ChangeMan for z/OS & OS/390.

OBJECTIVE

The ChangeMan ZMF 5.3 Administrator Guide provides information about how Serena™ ChangeMan® ZMF may be configured, and it provides instructions for administering that configuration.

AUDIENCE

This document is intended for ChangeMan ZMF administrators. This document assumes no prior knowledge of ChangeMan ZMF.

COMPONENTS / SCOPE

The members delivered in ChangeMan ZMF libraries include these components:

• SERNET (known previously as Serena/Network), which manages communication for ChangeMan ZMF and other Serena mainframe products.

• Serena ChangeMan ZMF, which provides comprehensive, automated configuration management.

• SER10TY License Manager, which manages SERtificates used to enable licensed Serena mainframe software on authorized CPUs.

10

About This Book

• Components for all selectable options of Serena ChangeMan ZMF. If you license one or more of these options, the components are enabled through the SER10TY License Manager.

11


MANUAL ORGANIZATION.

RELATED PUBLICATIONS.

This chapter… Contains this information…

About This Book

Information about this publication. Contact information for Serena Software.

1 Description of the Administrator Guide; nomenclature, instructions for obtaining help.

2 Description of new features and functions of ChangeMan ZMF 5.3, notes on changes to user procedures.

3 Description of key concepts, package lifecycle, and library management.

4 Detailed discussion of functions and settings, and descriptions that must be made before implementation.

5 Detailed description of Global Administration panels and entries

6 Detailed description of Application Administration panels and entries

7 Instructions for managing failed installs and managing the internal scheduler.

8 Description of sites, instructions for setting up global sites.

9 Details about ChangeMan ZMF utility programs, their parameters and execution.

10 Description of ChangeMan ZMF exit programs and how they change system behavior.

11 Description of ChangeMan ZMF reporting functions, details about selected reports.

12 Detailed discussion of housekeeping (maintenance) tasks.

Title Description

ChangeMan ZMF 5.3 Installation Guide

Step by step instructions for initial installation of ChangeMan ZMF. Assumes no prior version or that the existing version will be overlaid by the installation.

12

About This Book

These manuals are included on the Serena EPIC CD-ROM in Adobe Acrobat format. The files are password protected (case sensitive). The CD-ROM also contains the Adobe Acrobat Reader for viewing, searching, and printing the manual.

SUPPORT

Serena Software provides technical support on the Internet through the Serena eSupport self-service Web site. To access the eSupport site, go to http://support.serena.com and login with your ID and password to see the eSupport Customer Portal. From there, you can:

• Report new issues.

• Search our problem-tracking system for information about existing problems.

• View a knowledge base of frequently asked questions and helpful product hints.

• Query the call tracking database to obtain the current status of an open issue.

• Access our FTP server to download product fixes and documentation in PDF format.

• Subscribe to one of our mailing list servers (LISTSERVE) to receive the latest product information by e-mail.

If you need a password or ID, please e-mail or call the appropriate support department for your country

ChangeMan ZMF 5.3 System Messages

Description of messages issued from ChangeMan ZMF, SERENET, and ChangeMan ZMF options.

ChangeMan ZMF 5.3 Customization Guide

Technical information about ChangeMan ZMF that is useful for modifying the delivered product to fit your needs.

United States, Canada United Kingdom, Germany, Austria, France, Switzerland, BENELUX

Support Hours

Monday through Friday5:00 A.M. to 5:00 P.M. (Pacific Time)

Monday through Friday 7:30 A.M. to 6:30 P.M. (United Kingdom Time)

E-mail [email protected] [email protected]

URL http://support.serena.com http://support.serena.com

Phone 877.696.1850 44 1494 765888

Facsimile 650.522.6698 44 1494 766888

For support in all other countries, please contact your local distributor.

Title Description

mailto:[email protected]




13


For product questions or requests, you may need to first contact a designated representative in your company before calling Serena Customer Support.

USING ONLINE HELP

Online help is the primary source of information about ChangeMan ZMF. Online help is available as a tutorial, through Help screens, and in ISPF error messages.

Online Tutorial

ChangeMan ZMF includes an online Tutorial that provides information about its features and operations, from high-level conceptual descriptions to detailed descriptions of screen fields.

To view the Tutorial Table of Contents, select option T from the Primary Option Menu or jump to it by typing =T and pressing ENTER.

Press PF1 from anywhere in the Tutorial for a complete list of Tutorial navigation commands and PF keys.

Online Help Screens

If you have questions about how a particular ChangeMan ZMF screen works, you can view a help panel by pressing PF1 from anywhere on the screen.

Online Error Messages

If you make an invalid entry, or if you make an invalid request for a function, ChangeMan ZMF displays a short error message in the upper right corner of the screen. Press PF1 to display a long error message that provides details about the error condition.

Remember that the long message does not display automatically. You must request the long message by pressing PF1.

14

About This Book

15

INTRODUCTION 1WHAT IS THE CHANGEMAN ZMF ADMINISTRATOR GUIDE

This guide is intended for ChangeMan ZMF global and application administrators as well as for security administrators. It assumes that the administrator has a thorough knowledge of ChangeMan ZMF functions, and is familiar with MVS™ and the security system in use.

CHANGEMAN ZMF ADMINISTRATOR

As an administrator, your responsibilities depend on your administrative domain. You may be any or all of the following:

Global Administrator

If you are the global administrator, it is your responsibility to set the high-level rules (called parameters) of your site's implementation process. They can be as restrictive or liberal as you choose. For example, you have the option to completely prohibit or allow your site's developers to check out components to their personal libraries.

Note Rules are set for ChangeMan ZMF users on two levels. The global administrator sets them first, and these choices can be further restricted on an application by application basis by the application administrator.

It is also your responsibility to specify to ChangeMan ZMF the systems with which it interacts and the details regarding the staging library allocation. For example, as the global administrator you may choose CA-Panvalet® as your baseline library storage means. You specify many other details, including procedures used for compiling (depending on languages for source), maximum allowance for schedule package installation on a daily basis, notification vehicles for people who need information on packages awaiting approval, and so forth.

16

Chapter 1: Introduction

Application Administrator

If you are the application administrator, it is your responsibility to set rules of your application's implementation process. They can only be as liberal as the values which are set by the global administrator (although you can further restrict your users). For example, if the global administrator lets users at the site check components out to their personal libraries, you can restrict your users from checking out components to their personal libraries. But if the global administrator has already restricted their access, you cannot override the global administrator's decision and give them permission.

Like the global administrator, you also set staging library information as well as determine compiling procedures for the languages used in your application's development. In addition, you configure the promotion libraries (if any) and baseline libraries used by your application. You create approval lists that are used by ChangeMan ZMF to notify strategic people in your development process that a change package is ready to be moved on to the next level of integration, testing, or into production.

In fact, no matter whether you are a global or an application administrator, you are capable of running reports for the site or the applications; you may also be responsible for setting up remote site information (if you have remote sites).

Security Administrator

As the security administrator, you assist and consult with the global and application administrators on site, user, library and component level security using the security package in use at your site. You are expected to be an expert in that system's functions and capabilities and you set up the overall security of your development process.

ChangeMan ZMF Monitor

As a ChangeMan ZMF monitor, you oversee packages and work closely with users during the implementation process, and you may be involved in resubmitting installation jobs if there are problems at package installation time. Also, you have the ability to hold packages back from installation as well as change the status of packages in limbo.

General Administrator

As the general administrator, you may be an expert in the periodic housekeeping tasks for ChangeMan ZMF such as starting up and shutting down each ChangeMan ZMF instance, updating the query information, backing up or recovering the package master, or clearing the activity log.

You may customize ChangeMan ZMF by implementing user exits, using and updating the services, creating custom reports, setting up the SYSOUT facility, or updating skeletons. Finally, you may also be a specialist in setting up the administration for the many selectable options which can be purchased individually for the unique needs of your site.

17


All of the responsibilities described above, except for customizing ChangeMan ZMF skeletons and administration for selectable options, are described further in this document. Information about skeletons is contained in the ChangeMan ZMF Customization Guide, and the selectable option information is contained in the individual selectable option manuals.

The global, application, and monitor administrative domains described above require that you have been defined to the individual security entities as such. See “Setting Up Security” on page 28 for further details.

18

Chapter 1: Introduction

19

WHAT IS CHANGEMAN ZMF? 2ChangeMan ZMF is a software change management product that integrates, automates, and controls the essential components of the software management lifecycle. With ChangeMan ZMF, the implementation of effective software management control is simplified.

CHANGE PACKAGES

A Change Package is a grouping of all the components (Source, Copybook, Load, JCL, control cards, compiling procedures, documentation, and other components) required to implement a software change into production.

You can build Change Packages for any type of change, including permanent, emergency, temporary, simple, and complex changes. A variety of information can be associated with a Change Package. For example, reasons for the change, contingency plans, special implementation instructions, work request numbers, and contact lists can all be captured when the Change Package is created.

All Change Packages are referenced in the Package Master, a control file that contains the significant information regarding current and previous Change Packages. At creation time, a unique Change Package number is assigned to facilitate cross referencing. When a programmer adds components to a Change Package, that information is added to the Package Master.

IMPACT ANALYSIS

To analyze the impact of changes, many organizations rely on data from a variety of sources, such as batch library scans and cross reference files. This method makes it difficult to maintain all sources of data and verify that they are current. ChangeMan ZMF provides a comprehensive facility to capture, query, and enforce relationships between components.

These relationships include not only the traditional ones, such as a source and executable relationship, but also other relationships based on common references to copybooks, SQL Include components, CA-Panvalet® ++INCLUDE components, CA-Librarian® - INC components, Called Subroutines, and JCL fields such as program name, filename, or data set name.

20

Chapter 2: What is ChangeMan ZMF?

CHECKOUT

Checkout enables you to reintroduce components residing in baseline or promotion libraries to the change cycle. Generally, production level components are checked out for modification. However, you can check out any previous version of a baseline component.

Depending on how ChangeMan ZMF is configured, one can check out components:

• To personal libraries

• To staging libraries

• Only if they are associated with change packages

• In batch

• Online

• Concurrently with other components

If your site has applications that require parallel development, you can configure ChangeMan ZMF to allow concurrent checkout of components. ChangeMan ZMF has an automated process for managing this concurrent development. As part of this process, ChangeMan ZMF ensures that each owner of a version is aware of the actions of the other owners.

After you check out components and make necessary modifications, ChangeMan ZMF records the components and the associated change package for further impact analysis. This ensures that your developers are always working with the proper version of a component.

STAGING

Staging is the process of introducing newly developed (or previously developed) components into the change cycle for modification or enhancement, and packaging with related change package components. When you stage a component, ChangeMan ZMF recognizes the type of component that you are staging and copies it into a staging library of corresponding type (source, load, JCL, documentation, copybook, etc.). Staged components are also associated with a pre-defined change package, which is the vehicle used to move components through the change cycle and track the history of change management activities for each staged component.

In change management systems other than ChangeMan ZMF, staging libraries are merely pre-production holding areas shared by one or more application groups. After components are tested in development libraries, they are copied into staging libraries prior to production implementation.

ChangeMan ZMF staging libraries are more than pre-production holding libraries. Components can be modified and tested in protected ChangeMan ZMF staging libraries. Moreover, when you stage source components, they are compiled and the resulting load modules are identified, helping you to maintain the integrity of source-to-load relationships.

21


In addition, ChangeMan ZMF maintains up-to-date records of all staging activities for packages and components. For example, when you stage a source component, the time that the component was staged is recorded, along with the name of any associated load modules, or copybooks, and the compiling procedures and linkage parameters used during the compile. This information is kept in ChangeMan ZMF's master file, the package master. You can view this component and package information any time by using the query function.

ChangeMan ZMF further extends the concept of staging by providing a means of isolating components from other changes in progress. This prevents uncontrolled and unknown copybooks and subroutines from being inadvertently referenced, allowing parallel or concurrent development without the risk of accidental overlays. The stable coexistence of multiple versions of a single component simplifies the blending of changes.

AUDIT

The ChangeMan ZMF audit process enables you to ensure correct synchronization of components and procedures. Because of the range of features offered by the Package Master and the Impact Analysis database, ChangeMan ZMF maintains control of current and past modifications and component versions. Therefore, potential production problems can be identified before they impact production.

The audit function inspects the staging library contents of an evolving change package with respect to baseline library contents. The inspection looks for situations such as a package that shows no change from the baseline library, or a package that contains an LOD component that does not match its SRC component. Recognizing such out-of-sync situations helps you detect code that is inconsistent with your development procedure and other code problems. Examples of out-of-sync situations that the ChangeMan ZMF audit addresses include:

• Copybooks that have been changed after a source program has been compiled.

• Source programs that must be recompiled due to a copybook change.

• Called subroutines that have been changed after a referencing source program has been compiled and linked.

With ChangeMan ZMF you can enforce by application whether you want an audit, and if so, whether you want to correct or leave potential uncovered problems.

RECOMPILE AND RELINK

The Recompile and Relink functions are intended to introduce components into packages in special circumstances. Neither Recompile nor Relink copies the source into the package, but instead keeps the output of the process. This may be helpful if:

• A copybook has changed, but not the referencing source (Recompile).

• The source code is not available for a driver, but a change is made to a subroutine (Relink).

22


• It is necessary to perform a composite link where the resulting load component name does not have accompanying source (Relink).

Both Recompile and Relink use the component’s history from the package master. For example, Relink picks up the link options that were used when the program was last compiled.

Both Recompile and Relink can be used to resolve certain types of out-of-sync situations found during the audit of a package.

FREEZE

Another unique ChangeMan ZMF feature is the ability to freeze Change Packages. When the Change Package is ready for the next phase of the change implementation lifecycle, a freeze is performed to prevent further modifications. The freeze also positions the Change Package for promotion or approval. Traditional methods accomplish this function by moving components from the development libraries to a separate set of libraries or, in some cases, separate environments. ChangeMan ZMF controls your updates in conjunction with your security system, so component movement is no longer necessary.

If further modifications are required, you can unfreeze a Change Package, and the approval process is reset.

PROMOTION

ChangeMan ZMF has the ability to promote Change Packages through multiple shared, pseudo-production promotion environments. These promotion environments are secured as if they are production, and ChangeMan ZMF controls all updates.

ChangeMan ZMF considers shared promotion environments a place where full integrated system testing may be performed. When the time comes for a full system or an integrated system test, authorized approvers promote the acceptable components into the promotion environments.

When testing is complete and the Change Package is approved, ChangeMan ZMF removes the components from the promotion environments. All production installation occurs from the Change Package staging environment. With ChangeMan ZMF, you define your testing methodology and the number of testing levels that are required.

APPROVAL Approvals for change package installation are performed online, eliminating the requirement for manual approval processes. During the ChangeMan ZMF approval process, authorized approvers can indicate that the change package is acceptable for production implementation, or they have the option to reject or review the change and generate a checklist of questionable or unclear items for the programmer to resolve.

23


ChangeMan ZMF relies on your security system; it does not use internal personnel tables. Approval lists of specific USERIDs or approving entities are defined to your security system so that electronic approvals can be collected.

For each application, a variety of approvers can be included on the approver list. Separate approval lists can be created for scheduled, planned changes and for unplanned, emergency changes, or you can choose to use an approval hierarchy. With ChangeMan ZMF, you have the flexibility to make these choices.

PRODUCTION INSTALLATION

ChangeMan ZMF is actively involved in the management and control of actual production component installation. Component installation can be automated through the ChangeMan ZMF internal scheduling system, or through the ChangeMan ZMF direct interface with a job scheduling system. In addition to component movement, ChangeMan ZMF performs other production installation activities such as DB2 Plan binding.

ChangeMan ZMF also has a unique change quantity threshold facility that allows you to control the number of changes that occur in a given time period. For example, you may want to limit the number of change packages that are installed during month-end processing.

BASELINE LIBRARIES AND DELTA DECKS

ChangeMan ZMF recognizes that your software components are a vitally important business asset. It gives you the ability to store your production source components in a structure that works for your organization. Components can be stored in PDS’s, CA-Librarian files or CA-Panvalet files. Components can be segregated by application or by categories, such as batch versus online. Equally, applications can share libraries.

ChangeMan ZMF automatically stores prior versions of components. These versions can be stored as full copies (inherent for load components), or as delta decks. It uses a unique reverse base/delta technique known as stacked reverse deltas. With this technique, the current version of the component is the base, and delta decks are created to backtrack to previous versions.

BACKOUT MANAGEMENT FACILITIES

Comprehensive backout management requires more than simply backing up the components of a change. In addition to backing up the source, it is important to recreate the executable component from the source and ensure that the recreation takes place properly.

ChangeMan ZMF has comprehensive backout management facilities. In addition to source components, the prior functioning executable components can be automatically backed up. If a backout becomes necessary, ChangeMan ZMF automatically restores these executable components to production. It also performs all necessary DB2 Plan rebinding automatically.

24


Because ChangeMan ZMF is package driven, it backs out all the components of a change automatically.

EMERGENCY CHANGES

Critical abends occur at inopportune times and require immediate attention. Because ChangeMan ZMF contains the ability to create Unplanned Change Packages, and the ability to maintain a separate list of approvers for unplanned changes, emergency changes are safe, fast and easy to perform. Additionally, because of the facility (optional) to concurrently check out components, ChangeMan ZMF provides notification to any developer affected by the change so that the emergency fix can be incorporated globally into all change packages.

ChangeMan ZMF does not impede the emergency change process by requiring that the component be released, reassigned, or renamed by the original owner.

25

PRE-IMPLEMENTATION DECISIONS 3

This chapter provides you with important considerations that you may take up after ChangeMan ZMF has been installed, but before you set it up for your sites, applications, and users.

CUSTOMIZING CHANGEMAN ZMF FOR YOUR SITE

Modify Skeletons

For most batch processing jobs, ChangeMan ZMF uses a library of customized ISPF skeletons. Skeletons consist of programming logic and variables, and you communicate with them through the values entered on ChangeMan ZMF panels. In the appropriate skeleton, these values are substituted for variables, creating the JCL and other parameters necessary for submitting batch jobs. (See the “Serena™ ChangeMan® ZMF Skeleton Reference” manual about tailoring skeletons.)

Implement Exits

ChangeMan ZMF contains exits, which are routines that you can modify and implement to customize different user tasks in different functions. (See the Serena™ ChangeMan® ZMF Customization Guide).

Establish Initial History Records

ChangeMan ZMF keeps information about components (also called history) in the Component Master file. This information includes compile and link options for the component. These options are used during the compile, recompile and relink processes.

It may be beneficial to pre-load this information before components are accessed through ChangeMan ZMF. CMNBAHST allows you to establish an initial history record for components. (Utility CMNBAHST is described in the Serena™ ChangeMan® ZMF Customization Guide.)

26

Chapter 3: Pre-Implementation Decisions

MANAGING LIBRARY SPACE

To build, distribute, install and back out change packages, ChangeMan ZMF allocates and accesses a number of data sets. There are administrative functions at the global and application level that provide you with the capability to enter and update information about how these data sets are named and allocated. ChangeMan ZMF provides modules that you can implement to help you manage library space more effectively. See the descriptions of SEREX001, CMNEX015, and CMNEXINS.

The staging libraries are always allocated using PDS; the other libraries may be allocated using whatever storage method your site prefers. Since there is only one backup of production (called the hot backup), it is stored using PDS (independent of how you specify the storage means for the actual library.)

Allocating Staging Libraries

The staging library allocation is always managed through the administration panels during set-up. (See “Setting Up Global Administration” on page 55)

Allocating Baseline Libraries

ChangeMan ZMF baseline libraries may be pre-allocated outside of ChangeMan ZMF, or the application administrator may allocate PDS baselines through ChangeMan ZMF during application set-up. The following table describes the ways you can store the production and prior versions of components in baseline libraries.

Storage Means

Number of Levels Stored

Comments

Full PDS 2-10 The production version of a component is stored in full PDS format. There is an additional PDS library for each prior version level.

Stacked Reverse Delta

2-999 The production version of a component is stored in full PDS format. Prior versions are stored in proprietary reverse delta deck format. All reverse delta decks are stacked in a single PDS library.

Librarian 2-10 The production version of a component is stored in a CA-Librarian file. There is an additional CA-Librarian file for each prior version level.

Librarian Archie

2-255 The production version of a component and all prior versions are stored in a single CA-Librarian file.

27


Allocating Promotion Libraries

Promotion libraries must be allocated outside of ChangeMan ZMF administration. After the libraries are allocated, they are defined to ChangeMan ZMF while setting up Promotion (“Configuring Promotion Sites, Levels, and Libraries” on page 132)

Allocation Production Libraries

See “Using Baseline Libraries for Production Libraries” on page 27 below for a discussion of baseline versus production libraries. If you decide to use production libraries, they are allocated outside of ChangeMan ZMF. The section “Configuring Production Libraries” on page 158 explains how to define the libraries.

USING BASELINE LIBRARIES FOR PRODUCTION LIBRARIES

ChangeMan ZMF has the ability to synchronize baseline libraries and production libraries. This can be useful when development and production processing occur in different locations. If your production applications run at the same site as your baseline libraries, you may not need to set up separate ChangeMan ZMF production libraries. Remember, ChangeMan ZMF baseline libraries can be standard PDS’s and can be accessed by external tasks. Eliminating ChangeMan ZMF production libraries where possible could result in significant DASD savings.

Panvalet 2-10 The production version of a component and all prior versions are stored in a single CA-Panvalet library.

Reverse Delta Deck PDS

2-10 The production version of a component is stored in full PDS format. Prior versions are stored in proprietary reverse delta deck format. There is an additional PDS library of reverse delta decks for each prior version level.

Note: This storage means is obsolete for new baseline libraries, but existing baselines with this storage means are supported.

Storage Means

Number of Levels Stored

Comments

28


SETTING UP REMOTE SITES FOR PRODUCTION LIBRARIES

An alternative to using baseline libraries for your production libraries is to set up additional ChangeMan ZMF subsystems. This allows you to segregate packages still in development from production level packages. You define one subsystem as your development site and the additional subsystems as remote sites where production level packages can be distributed and installed. Baseline libraries reside at the development site and production libraries are kept on the remote site CPU.

You set up remote sites during global administration by configuring your ChangeMan ZMF subsystems as either D (Development site) or DP (Development and Production site) for the subsystem you designate as your development site, and P (Production site) for the subsystem you designate as your production site.

If you initially invest in a single subsystem, but are planning to incorporate remote site subsystems in the future, configure your single subsystem as DP, not ALL. Setting up as an ALL site enables you to have both development and production libraries on a single CPU, but prohibits you from attaching remote sites.

SETTING UP SECURITY

ChangeMan ZMF allows you to choose the security system which is used in your environment as a control layer between users and sensitive ChangeMan ZMF functionality, projects, and data. ChangeMan ZMF supports CA-ACF2®, RACF®, and CA-Top Secret® as security systems.

We have attempted to provide enough detail in this section to help you set up the security that ChangeMan ZMF requires. However, this section is not intended to replace your security package documentation. Read the manuals provided with your security product if there are questions about specific procedures related to that product.

It is recommended that the global administrator defines the entity names for the resources. The global administrator must have direct authority or the immediate assistance of other people who are responsible for security changes.

When using ChangeMan ZMF, users must first pass the security system check to log on to TSO. The user then attaches to the ChangeMan ZMF subsystem. ChangeMan ZMF is now in control and can perform security checks on the user's TSO ID to determine their authorization level.

ChangeMan ZMF ties into the security system to ensure that only authorized users have access to certain functions. For instance, only those TSO ID's assigned to a particular application may create change packages, and only specific ID's may approve those packages for installation into production.

29


Security Entities

The way ChangeMan ZMF allows only specific people access to certain functions is by the use of entity names. Some of these names are fixed by internal convention, while others are decided entirely by your administrators. A single TSO-ID, multiple TSO-IDs, or a group name can be associated with the entity name to allow access to the restricted functions. When a user attempts to perform a potentially sensitive function, ChangeMan ZMF performs an “entity check.” This check is posed to your security system - CA-ACF2, RACF, or CA-Top Secret. If the user's TSO ID is associated with the entity name, he is allowed to proceed. Otherwise, a message is displayed on screen stating the user's lack of authorization. Of course, anyone may sign on to ChangeMan ZMF to use non-restricted functions such as querying packages, reviewing the log, and using the Tutorial.

Setting up the necessary security is a two phase operation for some functions. First, ChangeMan ZMF must be defined to your security system; then, the security information must be defined to ChangeMan ZMF.

The following table lists the expected entity names, the function they apply to, and whether they require definition in ChangeMan ZMF. The first five entity names, prefixed CMN, are fixed names and are always checked at the beginning of a session. The Serena™ ChangeMan® ZMF Installation Guide directs your efforts in producing these entities.

Entity Function Define to ChangeMan ZMF

CMNGBADM Global Administration authority

Associated TSO-ID’s or groups

CMNLCADM Application Administration authority

Associated TSO-ID’s or groups

CMNREVRT Revert authority Associated TSO-ID’s or groups

CMNBKOUT Backout authority Associated TSO-ID’s or groups

CMNMON Monitor authority Associated TSO-ID’s or groups

(varies) Staging restriction level Define when setting application parameters

(varies) Checkout restriction level Define when setting application parameters

(varies) Application approvers Define when setting application approval

(varies) Application promoters Define when setting application promotion

3 to 4 character application mnemonic

Application users Associated TSO-ID’s or groups

30


The last five entities are optional and installation dependent. They are determined by the administrators. (See “Setting Up Global Administration” on page 55 for setting global parameters and see “Setting Up Application Administration” on page 97 for setting application parameters.)

Administrators, approvers, and promoters must also be application users to gain access to specific applications.

Securing Libraries

One of the fundamental design criteria of ChangeMan ZMF is that it guarantees the source/load relationship. This can only happen if ChangeMan ZMF alone has access to the source code staged and the load component created.

Through your security system, you can ensure that ChangeMan ZMF has exclusive access to application baseline libraries, production (temporary, backup) libraries, and staging libraries. For each application, you can authorize specific users read only access or no access to their application libraries.

ChangeMan ZMF must be defined to your security system as a Resource Class, as a started task, and given proper authority to update, create, and delete data sets. Naturally, ChangeMan ZMF would never delete your baseline libraries, but it must be the only one to update them with the most current versions in production, as well as maintaining prior versions. Likewise with the production, temporary, and backup libraries in your production environment, users must be denied access (and ChangeMan ZMF allowed access) to ensure the source/load relationship.To accomplish this, refer to your security system's manuals.

The individual package staging libraries are created and updated by users, but only through ChangeMan ZMF. So, again, only ChangeMan ZMF is allowed create and update access.

31


The following table shows the libraries, the recommended format for generic names, and the access level required by ChangeMan ZMF. Only RACF and CA-Top Secret systems require the protection steps listed; CA-ACF2 sites must define the ChangeMan ZMF instance with access to all data sets and by default so that users do not have access to the libraries. (RACF and CA-Top Secret's use of ALTER is equivalent to CA-ACF2's use of ALLOC.)

Library Recommended Format

RACF CA-Top Secret

CA-ACF2

Baseline prj.BASE.* Update Update Update

Development (optional)

prj.DEV.* Read/Update Read/Update Read/Update

Staging prj.CMNSTAGE.* Altera Altera Altera

Promotion Updateb Updateb Updateb

Production (your target library names)

Updateb Updateb Updateb

DATA SETSECURITY

ChangeMan Multiple Access Levels

0

- 1

- 2

SRC

LOD

CPY

TEMP

PROD

BKUP

USER

USER Read Only Access

Production

Baseline

Staging

ACF2, RACF &

TOP SECRET

32


Baseline Recommendations

If you use the stacked reverse delta format (SRD), baseline 0 should probably have UPDATE access, while baseline -1, etc. should probably be given ALTER access. The reason has to do with the format of the baseline -1 file. Normally, this file starts relatively small and grows over time at a steady rate, thus the file must be constantly reallocated. By comparison, the baseline 0 file remains approximately static in size after compression. If the SRD format is not used, then UPDATE should be sufficient for both baseline 0 and baseline -1 and following.

Production and Temporary Recommendations

The production and temporary libraries have a different consideration than baseline libraries. Often they start small and continue to grow. If the growth is substantial then ALTER access may be needed, otherwise, UPDATE access should be sufficient.

Development (or Personal) Recommendations

If you want to stage components from an external development library, ChangeMan ZMF must have read access to that library or that request fails. If you want to check out components to an external development library, ChangeMan ZMF must have write access to that library or that request also fails.

It is recommended that ChangeMan ZMF be granted read/update access to all external data sets that users may stage from or check out to. Thus, access to many hundreds of data sets may be required. Such extensive access does not allow users to read/update development data sets if they do not also have personal access.

ChangeMan ZMF determines a user's personal access to a development data set before acting upon the request. For example, assume that ChangeMan ZMF has read/write access to the development data set CMN.DEV.SOURCE. A ChangeMan ZMF user must have at least read access to this data set before staging from it. Personal write access is required before ChangeMan ZMF permits the checkout of components to this data set.

Temporary prj.TEMP.* Updateb Updateb Updateb

Backup prj.BKUP.* Updateb Updateb Updateb

a. Alter is required when using CMNUPDAT or CMNCOPY with the REALLOC parameter as ChangeMan ZMF must be able to delete and reallocate a data set. CMNUPDAT is run mainly in the installation jobs against Baseline and Production libraries. The ChangeMan ZMF Administrator must determine whether or not to allow ChangeMan ZMF to reallocate these libraries via the REALLOC parameter of CMNUPDAT.

b. Update if the user will be editing in place from stage of a non-ChangeMan ZMF controlled development library. Read if just a simple stage from a non-ChangeMan ZMF controlled library.

Library Recommended Format

RACF CA-Top Secret

CA-ACF2

33


Granting User Access

ChangeMan ZMF operates under the userid of the SERNET started task. A ChangeMan ZMF user request is processed using the authority of the SERNET userid, not the authority of the user's logon ID. Access to system resources are granted to the SERNET userid through your security system.

For example, if a user initiates a COBOL compile during a ChangeMan ZMF session, it appears as though the user has submitted a batch job. Actually, the JCL was submitted by the ChangeMan ZMF instance through SERNET in response to an authorized user request. If the user attempts to run a similar process outside of ChangeMan ZMF, the update of protected libraries must be disallowed.

The following areas must be considered when setting up security, specifically granting user access to:

• Session utility data sets.

• Batch job submission.

• Viewing and purging batch job output.

Refer to the Serena™ ChangeMan® ZMF Installation Guide or the individual security system documentation for details on RACF, CA-ACF2, or CA-Top Secret.

Session Utility Data Sets

ChangeMan ZMF may allocate a number of utility/work data sets during each user session. These data sets are cataloged, manipulated, and (normally) deleted by ChangeMan ZMF automatically. Processes that use these data sets fail if installation security prohibits their creation. Affected functions include:

• ISPF file tailoring of all batch jobs

• Editing of staging data sets

• On-line file comparisons

• Baseline browse

The default naming convention for these utility data sets allocates data set names that start with the concatenated value of ISPF variables &ZPREFIX and &ZUSER. However, by use of exit CMNEXINS it is possible to tailor the data set names to reflect your installation’s naming conventions. In many installations, this means that the data sets begin with the value of the user's logon ID. ChangeMan ZMF must have allocate access to data set names that begin with the logon ID of all potential ChangeMan ZMF users.

If such access is contrary to security policies, an exit is available to vary the utility data set names so they conform to installation requirements.

Submitting Batch Jobs

• User Initiated Requests - Compiles, Batch Checkout, Or Audit

34


The user is presented with a job card that may be changed before submission. Most often, users want to run jobs that begin with their logon ID. In the same manner that ISPF handles the printing of its own log and list data sets, ChangeMan ZMF appends an alphabetic character and/or automatically increments it between job submissions. For example, after job USER01A is submitted, the next suggested job name is USER01B. (The user may type over this value.)

• Implementation Jobs - Production Install And Baseline Ripple

Except for the job name, job cards are built with information supplied via the global and/or application administration parameters. The default implementation job names begin with the 3 to 4 character application mnemonic, followed by the last two digits of the ChangeMan ZMF skeleton, followed by the last 2 to 3 digits of the change package number. For example, the baseline ripple JCL is built using skeleton CMN30. The baseline ripple job name for package “ABCD000123” would be ABCD3023. The baseline ripple job name for package “XYZ000456” would be XYZ30456.

Both categories of jobs are submitted by ChangeMan ZMF and run with the access associated to the SERNET started task. The SERNET instance requires authority to submit jobs with variable job names, account codes, and other job card parameters. If such access is contrary to security policies, an exit is available to restrict and/or vary the job card information that is allowed.

Viewing and Purging Batch Job Output

Users normally access SDSF, IOF or some other output manager to see the output of the jobs they have run. ChangeMan ZMF users may want to view (and possibly purge) the output of the jobs they have initiated via the ChangeMan ZMF instance.

Installations may limit the jobs that a user may access on the output queue, particularly if they were initiated by an alternate logon ID; i.e., ChangeMan ZMF. Such restrictions should be removed and/or access should be granted to a range of job names, and potential ChangeMan ZMF users should be advised of what job names they can or cannot access.

SETTING UP USER RESTRICTIONS

A primary function of ChangeMan ZMF is to protect and regulate your valuable code. To do this, there are specific choices to be made about ChangeMan ZMF functions. For example, do you want to allow two users to work on the same component at the same time?

Many of these choices are set by parameters in ChangeMan ZMF itself. Part of this implementation of ChangeMan ZMF is setting these parameters in the global and application administration functions. By setting these parameters, you further define the functions the end users have and access. In the above example, the parameter would be “Allow Concurrent Checkout”. If this parameter is set to “no”, only one person can work on the component at any given time.

“Setting Up Global Administration” on page 55 and “Setting Up Application Administration” on page 97 detail the set up requirements and identifies some of the policies you may want to set.

35


Allow Temporary Change Packages

A temporary change package is not permanent and may never be rippled into baseline. It is automatically deleted from production after a specified number of days (the user provides this information). The staging library contents associated with temporary change packages are placed into temporary libraries which are concatenated ahead of production libraries. They are never rippled into baseline and are deleted from the temporary libraries after a specified number of days by ChangeMan ZMF.

If the you restrict this option, the user is not allowed to select this change package option during package creation. If you allow temporary packages, users are required to enter the number of days the package is to remain in production after installation (duration number of days).

Work Request and Department Number Required

The work request number as well as the department number can be used to track change packages in certain ChangeMan ZMF batch reports. They can also be used to select viewing of package information within the Query function.

If you require all applications (and their users) to enter a work request number or a department number during change package creation, then users are not allowed to finish creating a change package without entering this information. (ChangeMan ZMF performs no validation checks on the number, but only that one is entered.)

Planned Installation Calendar

If you are the global administrator, you can set up a Planned Installation Calendar which limits the maximum number of planned changes that can be installed for any given date in the forthcoming 52 weeks. See “Setting up the Installation Calendar” in “Chapter 4. Setting up Global Administration”. Setting the maximum number to zero stops any planned package from being planned for installation on that date (unplanned change packages are not restricted by the calendar). This a zero implies a non business day. A planned package cannot be scheduled for installation on a date that has already reached its maximum limit.

For the user, this information is accessible from the Dates option in the Build Change Package Menu. The user does not update the actual calendar. During package creation, they enter the desired installation date for each remote site selected to receive the package. ChangeMan ZMF verifies that the date is available and increments the calendar accordingly. If the date entered is not available (either the maximum allowable packages have been met or the date is blocked), the user is not be able to create the change package until a valid date is entered.

Unplanned change packages are not affected by this calendar.

36


Disable Installation Calendar

This option allows you to completely disable the Planned Installation Calendar. When a user creates a change package, ChangeMan ZMF only checks the install date to verify if it is a valid date, and disregards the maximum packages criteria.

Normal Business Hours

The application Planned Approval list is incorporated into any change package that is created within normal business hours. An unplanned package uses the Unplanned Approval list if it is created outside of normal business hours. Normal business hours are defined in Global Administration Parameters.

Overlay Prior Staged Component

This situation only occurs if more than one user is attempting to re-stage components within a change package. (Of course, all users may stage and re-stage components as many times as they need to, but this option refers to two or more users working in the same change package and attempting to re-stage [overlay] each other's components.)

If overlaying a previously staged component is allowed, ChangeMan ZMF issues a warning to the user requesting the staging of an already-staged component (already staged by another user within the same package), and inform the first user that the component has been overlaid.

Checkout Enforcement

You can set the checkout enforcement rule such that if a component exists in baseline, it must be checked out before it can be staged. There are levels to this rule:

Level Rule

1 Any component may be staged regardless of whether it exists in baseline or has been checked out to a package. ChangeMan ZMF does not check for the component's existence in the baseline libraries.

2 Users attempting to stage a component that exists in the baseline but has not been checked out must pass a security system ENTITY CHECK before the stage can proceed. The entity name is specified in the application parameter generation. Staging is not allowed if the user does not pass the entity check.

3 Disallow anyone from staging a component which exists in the baseline library but has not been checked out to the package requesting the stage.

37


Allow Concurrent Checkout

This rule is used to dictate whether a user can check out components that are already checked out to another package. It only applies to planned packages, not emergency packages.

Validate Version During Staging

This option validates the component versions during staging. If the same component is in motion in two different packages, the first package to baseline ripple can force the user of the other package to halt development and recheckout the latest version of the component.

Staging Restriction Level

This option restricts who is allowed to stage NEW components. New components are not yet associated or checked out to a package.

Audit Level

You cannot freeze the change package without passing audit. The Audit Level in application administration sets the maximum return code that audit may produce and still allow your change package to pass the audit:

Level Rule

1 All users can work on new components. This means they can stage components that are not yet associated with a packages (called development driven staging) as well as stage component that are associated with a package (called package driven staging).

2 Allows only users who have been defined to a special entity by their TSO ID to stage new components. Otherwise, they can only check out and stage components that are associated with a change package.

3 Does not allow you to stage new components, only ones currently associated with a package. This effectively disables development driven staging.

Audit Code Explanation

0 Audit is never required. It may be performed, but this is optional.

1 Audit is required but any return code (except ABEND) is acceptable.

2 Audit is required but the return code must not exceed (12). This means that there are out-of-sync situations within this set of staging libraries

38


Designated Procedures

If the administrator has chosen to designate a compiling procedure for one of the application's components with force level 1, then any user wishing to freeze a change package with the selected component MUST perform the last stage request with the designated procedure. ChangeMan ZMF allows staging with alternate procedures during package development, but the final stage (before attempting to freeze) must be performed with the designated compile procedure for each component. If force level 2 is chosen, then any user wishing to stage the component must use the designated compile procedure. When designating a procedure for the component, the application administrator may have entered extra compile and/or link options (you can use CMNEX025 for component level parsing).

Secured Components

If the administrator has chosen to secure one of the application's components to specific TSO-ID's, generic TSO-ID's, or to an Entity, then ONLY the TSO IDs associated with the component are allowed to check out or stage the component during change package development.

Approval Lists

The administrator has set up a list of approvers for this application's change packages, entity names associated with each approver description, and whether the approver will be called upon to approve packages (generated for another application) which impact this application. More than one TSO ID can be associated with each entity name so that packages can be approved when your regular approver is absent. When unplanned packages are created outside normal business hours, only the abbreviated list of approvers needs to be met. However, the installed package remains on the list of packages to be approved until the complete approval list is met. (This is called “Post Approval” and it is intended to facilitate emergency change packages.)

3 Audit is required but the return code must not exceed (8). This means that there are no out-of-sync situations within the staging libraries but there are out-of-sync situations within the baseline.

4 Audit is required but the return code must not exceed (4). This means that there are no out-of-sync situations in both staging and baseline sets of libraries, but there is at least one component of a staging library that is identical to the corresponding component in baseline (duplicate).

5 Audit is required but the return code must not exceed (0). This means that there are no out-of-sync situations and no duplicates.

Audit Code Explanation

39


OTHER CONSIDERATIONS

Global Parameters for Staging Library Allocation

If you are the global administrator, you set up a model for the staging data set names, size allocation specifications, and types of libraries to be allocated, so that each time a user creates a change package, the package's staging libraries are allocated based on certain standards.

The data set names follow this model:

• Four consecutive question marks “????” must appear where the application mnemonic (three or four alphanumeric characters) is to be substituted.

• Seven consecutive pound signs “#######” must appear where the package number (.#000123) is to be substituted.

• Example:????.CMNSTAGE.#######

• Result: DEMO.CMNSTAGE.#000001.SRC

Application Parameters for Staging Library Allocation

If you are the application administrator, you determine which library types are required to be generated as staging libraries for each application. If you choose to defer staging library allocation, ChangeMan ZMF does not allocate the library type at package creation time. (The user has the option during package creation to request allocation of any of the deferred library types.) If the user makes a stage/checkout request for any component of the deferred type, then the staging library is automatically allocated based on the size parameters chosen for the application.

Edit Staging Recovery Mode

This application level parameter causes ChangeMan ZMF to store all of the user's edits to change packages so that they can recover them in the event that their TSO session fails. After the failure, upon reentering ChangeMan ZMF, they have a choice of recovering or canceling the recovery. If you set the recovery mode to off then the user's profile also has recovery mode set to off. If you turn it on (after it has been off for a period of time) the user needs to reset their profile. Otherwise, the recovery process does not work. Have the user complete the following steps to reset their user profile after you update this parameter.

1. Access any Package Driven List (you can do this through staging, recompiling or relinking).

2. Edit a component by typing E next to the package you want to edit.

3. Type profile at the command line. The user profile information is displayed.

4. Type recover on (or recover off) at the command line.

40


Query Of Available Users Options

Beginning with Version 4.1.0, you can query source component staging information after the package has been frozen. If you implement customized user option panel names, or add customized panels and want to enable users to query information about them, edit panels CMNQRY22, CMNSTG04, CMNSTG05, CMNRCMP1. Link each of these four panels to any user option names or panels you have customized.

Keep Baseline By Site

If the baseline is kept by site, each remote site's set of baseline libraries are maintained by applications at the development site, and users are required to select from a remote site list when making requests from baseline, such as checkout or utility rename/scratch.

Remote Sites

The global administrator has determined whether or not there are any remote production sites, how to transmit to them, and by what name they shall be known. The application administrator has chosen from the global list only those remote sites that are appropriate to application; thus the application's users may send change packages only to the remote sites designated for the application. (The user may select any or all of the remote sites from the application's list.)

PACKAGE APPROVALS

The application administrator must set up two approval lists for each application.

• Planned Approvals

This list of approvals is automatically incorporated into all planned packages. It is also included in unplanned packages that are created during normal business hours. Normal business hours are defined in application administration.

• Unplanned Approvals

This list of approvals is automatically incorporated into unplanned packages that are created outside of normal business hours, which are defined in application administration.

Unplanned Approvals are intended to provide an alterative list of approvers for emergency changes that are urgent and may be needed at a time when approvers in Planned Approvals are not available.

Important considerations when defining Planned and Planned Approvals in application administration include:

• The type of approval list incorporated into an unplanned package depends on system time that the package was created and on the definition of normal business hours in application administration. The package install time is not considered.

41


• If an unplanned package is created with Unplanned Approvals, the Planned Approvals are added to the package after the package is installed. The package is displayed on the CMN120 Unplanned Packages Pending Post Approval report until all approvals are granted. An approval that is defined in both Unplanned and Planned Approvals does not need to be approved a second time.

• Approvals that are defined as Linked Package Approver in the Planned and Unplanned Approval lists are included in a package only when a package is linked to other packages using Serena™ ChangeMan® Enterprise Change Portal.

• Approvals may be dynamically added to packages at Freeze by exit program CMNEX009 based on package conditions such as the presence of a library type or a the existence of a value in a Package User Variable.

• Restrictions can be placed on who can approve a package by setting Approval Restrictions in Application Parameters.

• The order of approval notification is influenced by the Hierarchical Approval Process indicator in Global Parameters.

PROMOTION AND DEMOTION

Promotion is a ChangeMan ZMF facility that applies the changes in a package to libraries used for testing and other purposes.

Promotion can populate libraries used for:

• Batch testing where test libraries are coded in STEPLIB or JOBLIB statements in common application testing JCL.

• Online testing where application testing libraries are coded in region JCL.

• Unit testing where libraries are loosely controlled and populated by any developer who wants to run a test.

• Quality Assurance test libraries that must be tightly controlled and can only be populated by the QA testing coordinator.

• Training environments where software changes must be available for training classes before they are installed into production.

• Any purpose that requires package components to be copied into a fixed set of libraries.

How Does Promotion Work

Promotion copies components from package staging libraries into libraries that an enterprise uses for application testing or other purposes. Promotion may also be configured to execute additional processes to prepare promoted components for execution. Such processes might include CICS PHASEIN, DB2 bind, and IMS™ gens.

Demotion deletes components from libraries that were populated by promotion. Demotion may also execute processes such as CICS PHASEIN, DB2 bind, and IMS gens to adapt an environment to the changes made by demotion.

42


Each set of libraries that promotion can target is represented by a promotion level. The ChangeMan ZMF Administrator defines promotion levels for each application with the library types that can be promoted and the names of the libraries that are targeted for each type. Library types for promotion usually include the executable components in your package and may also include nonexecutable types like source code. However, a promotion level does not have to include all library types in an application.

Each promotion level is defined under a site. Promotion can populate libraries and prepare executables on local sites, which means environments that are on the same MVS image as the ChangeMan ZMF server. Promotion can also populate libraries and prepare executables on remote sites, which means environments that are on MVS images separate from the image where the ChangeMan ZMF server runs.

Full promote and demote operate at the package level. All components in a package that are eligible for promotion are promoted or demoted together. The current promotion level is recorded at the package and the component level.

Selective promote and demote operate on individual components in a change package. The package promotion level remains the same, but the component promotion level changes.

Since application test libraries are often shared with other developers and projects, promotion looks for potential overlays by comparing the names of package components eligible for promotion against the directories of the target libraries. The person promoting the package is given a choice whether to proceed and overlay matching components in the promotion libraries or cancel the promotion request.

Promotion must not be confused with the physical movement of components through a series of test libraries and into production libraries. Promotion always copies components from package staging libraries into target promotion libraries. Likewise, at baseline ripple and install, package components are copied from package staging libraries into baseline and production libraries.

Promotion Library Cleanup

ChangeMan ZMF is delivered with the promotion facility configured to provide the maximum level control over the contents of promotion libraries. Promotion can be configured to satisfy other priority requirements.

In the maximum control configuration, when a package is promoted from one level to another, promotion libraries at the prior level are cleaned up. ChangeMan ZMF deletes the components from the libraries in the prior promotion level, unless a component originally promoted from the package was overlaid by promotion from another package.

Promotion libraries are also cleaned up when a promoted package is baselined or installed.

This configuration assumes that promotion libraries used for testing are concatenated over baseline libraries or production libraries or copies of these libraries. The objective is to guarantee that if no packages are promoted to a set of test libraries, those libraries are empty, and the test environment behaves exactly like production because it is running only production components.

43


In some testing environments, such as those that use databases and/or data dictionaries, it is not possible to concatenate promotion libraries over production libraries. Components must accumulate in the promotion environment as packages are cycled through development, testing, and install. To satisfy this requirement, ChangeMan ZMF skeletons must be modified to disable promotion library cleanup at promotion, demotion, and install.

If promotion cleanup is disabled, the package lifecycle must be carefully analyzed to discover when orphans might be inadvertently left in promotion libraries, and when package components might not be copied to a particular accumulation library at all.

Promotion Security

Each promotion level in an application is associated with a security entity, which is defined in the mainframe security system (RACF, CA-ACF2, or CA-Top Secret). By working with the security administrator to grant or deny userid access to the promotion security entities in the security system, the ChangeMan ZMF administrator can limit who can promote and demote packages in a particular promotion level.

For example, all developers might be permitted to promote packages to a unit test promotion level. Only Quality Assurance test coordinators might be permitted to promote packages to a QA test promotion level.

Promotion Rule

The behavior of the promotion function is governed by the Promotion Rule. The administrator selects a Promotion Rule for each application that provides the level of management for change packages, components, and promotion libraries that is required by the application.

44


The following table describes how the Promotion Rule determines the requirements for promoting and demoting packages and components.

Rule Restrictions

0 Full and selective promote and demote are allowed without freezing the package first.

Requires the following sequence to change a promoted component:

• Selective unfreeze (only if the package is frozen)

• Edit

• Stage (“Restage”)

• Selective freeze of the component (only if the package is frozen)

• Selective promotion to any level up to the package promotion level.

1 Requires that the package be frozen for promote and demote.


• Selective demote of the component

• Selective unfreeze

• Edit

• Stage

• Audit package

• Selective freeze of the component

• Selective promotion back to the package promotion level.



• Selective demote of the component

• Selective unfreeze

• Edit

• Stage

• Audit package


• Selective promotion through all intermediate levels to the package promotion level.

45


Note The Promotion Rule does not change the requirements for audit. If audit is required before freeze, then audit is required before selective freeze.

Promotion Rule By Promotion Level

Normally, all promotion levels in all sites in an application are governed by the Promotion Rule coded in application administration parameters.

However, the level of control over promotion usually differs between lower promotion levels used for developer unit testing and higher promotion levels used for systems testing, quality assurance testing, and user acceptance testing.

exit program CMNEX027 can be used to assign different promotion rules to different promotion levels. This exit can also be used to assign other promotion restrictions to individual promotion levels.

Promotion Rule 0

If the Promotion Rule is set to 0 for an application (or for a promotion level with exit program CMNEX027), many promotion controls are relaxed. These relaxed rules may be appropriate for certain uses like populating libraries used in early component testing.



• Full demote of the package

• Selective unfreeze of the component

• Edit

• Stage

• Audit package


• Full promotion through all promotion levels up to the original promotion level.



• Full demote of the package

• Revert the package to development status

• Edit

• Stage

• Audit package

• Freeze package

• Full promotion through all intermediate levels to the package promotion level.

Rule Restrictions

46


In addition to the requirements listed in the Promotion Rule table above, the relaxed controls for Promotion Rule 0 include:

• Components that are not ACTIVE that are in library types eligible for promotion are bypassed and a message is displayed.

• Re-staging a component sets the component promotion level to 0. The package promotion level is not changed.

• Package may be promoted to levels that are not the next contiguous level.

Promotion Rule 0 must be used with caution because it allows different visions of a component to exist in promotion libraries and staging libraries.

First Promote

When a package is at promotion level 0 (not promoted), special procedures apply to the first promotion action. These procedures, specially in combination with Promotion Rule 0, can be useful for promoting individual package components for testing before the entire package is ready for testing.

• A package component may be selectively promoted when the change package is at Level 0 (not promoted). A selective promote in these circumstances is labeled a first promote.

• When all components are promoted to the same level as the first promote, the package promotion level is changed to that level. The package may be fully promoted or demoted from this new level.

• After a first promote, a package cannot be promoted until all components are selectively promoted to that level.

Other Restrictions And Options

These are general rules for promoting and demoting packages and components:

• Except for first promote, a component cannot be selectively promoted to a promotion level higher than the package promotion level.

• Except for first promote, the package promotion level is set only by a full promotion. The package promotion level is reset after a full demotion, not after all components have been selectively demoted.

• A package may not be promoted or demoted if components are at different promotion levels above the 0 level. Components may need to be selectively promoted or demoted to align components at the package level.

• A package may not be promoted to the current package promotion level. A component may not be selectively promoted to its current component promotion level.

• Promotion or demotion for local sites is accomplished in one batch job. Promotion or demotion for remote sites requires three batch jobs, one of which runs at the remote location.

47


• All promotion jobs that are initiated on the user’s MVS image obtain JOB card information from the Promote Options Panel. Promotion jobs that run at remote sites obtain JOB card information from the Site Definition in application administration. Job names for jobs that run at remote sites may be modified with exit program CMNEX008.

Promotion Paths

When promotion is defined for an application, the administrator creates each promotion level under a site defined in Application Administration.

The administrator can set the Force Demotion field for sites in the promotion definition to allow packages to be promoted to levels in more than one site at the same time. Sites may also be defined so that packages must be demoted in other sites before they can be promoted to levels in that site.

Levels, sites, and the Force Demotion field may be configured to provide multiple promotion paths within the same application. Here are some alternative promotion path definitions.

• Define each level under a unique site so that the Force Demotion field can be used to allow promotion or any or all promotion levels at the same time.

• Define all levels under one site to provide a single promotion path for all packages. If there is only one promotion site defined in an application, the promotion function skips over the site selection panel when a package is promoted or demoted.

• Group promotion levels under several sites to create multiple promotion paths. There might be a path for packages with online system changes and a different path for packages with batch system changes.

• Use sites for special promotion purposes. A promotion level with training environment libraries as targets might be defined under a unique site. A package containing new software would be promoted to this level on a certain calendar date to support training classes no matter where the package was promoted in other sites.

Approvals and Promotion

Approvals and promotion are separate facilities.

• Users authorized to promote packages to a level may promote frozen packages to that level no matter what approvals have been granted.

• Users authorized for approval can approve frozen packages no matter where a package may be promoted.

• The last approver initiates distribution and/or scheduling regardless of the last promotion level reached.

The package lifecycle always requires approvals. The package lifecycle does not require that packages be promoted before they are baselined and installed.

However, security entities for promotion and approvals may be used to provide a procedure that mixes promotion privileges with approval responsibility, as in the following example:

48


• The QA coordinator is permitted update authority to a promotion security entity to allow her to promote packages to the QA test environment.

• The QA coordinator is permitted update authority to an approval security entity to allow her to enter an approval labeled “QA Testing”.

The QA coordinator should only approve a package for “QA Testing” after she has promoted the package, the package has been tested, and she has examined QA test results.

Note Planned and Unplanned Approval definitions include an “Order No.” field. When this field is incorrectly called an “approval level”, users often confuse its purpose with the function of a “promotion level”.

Promotion Libraries In SYSLIB Concatenations

Library concatenations for SYSLIB DD statements in compile and link edit JCL are automatically build by ChangeMan ZMF skeletons. These skeletons put staging libraries at the top of the concatenation and baseline libraries at the bottom. Promotion libraries are placed between staging and baseline libraries.

You may exclude individual promotion libraries from these SYSLIB concatenations by coding the SYSLIB Exclude field in the promotion library definition in application administration. The SYSLIB Exclude field only has meaning for like-copy and like-load library types.

ENTERPRISE CHANGE PACKAGES

Change packages on multiple ChangeMan ZMF instances and change packages on multiple Serena™ ChangeMan® DS servers can be linked to provide a cross-platform software change lifecycle. These enterprise change packages are managed by Serena™ ChangeMan® Enterprise Change Portal (ECP).

When ChangeMan ECP links a ChangeMan ZMF change package to other packages, ChangeMan ECP takes control over parts of the package lifecycle. After a package is linked, these functions can be performed only through ChangeMan ECP:

• Freeze

• Revert

• Final approval

The link package function in ChangeMan ZMF is enabled by the global and application administrators, who set the Allow Linked Packages parameter in Global and Application Administration Parameters.

The application administrator also sets up planned and unplanned approvals that can be approved only through ChangeMan ECP. The LNK PKG field on these approvals must be set to YES, and the security entity for these approvals must be restricted to enterprise change package coordinators who use ChangeMan ECP.

49


STAGING VERSIONS

The staging versions facility can save an unlimited number of versions of a package component that a developer might create in a staging library between the time the component is first added to the package and the time the package is baselined.

Staging versions may be created only for components that can be edited from the Stage: Package Components panel.

Staging versions are stored as full copies in a compressed format in a VSAM file. Each version may be labeled with an optional 35-character description.

Some features of staging versions are available if the staging versions facility has been installed. More features of the staging versions facility are available for package components in a library type if the facility has been enabled for the library type by the application administrator. The merge facility of staging versions is only available if your company has licensed Serena™ ChangeMan® M+R.

Staging Versions Installed

The staging versions facility is installed if the HPSPLIB and HPSIN DD statements are included in the SERNET started procedure for the ChangeMan ZMF instance.

These features are available if the staging version facility has been installed:

• The “VC” Staging Selection Code can be used to display the Version Control panel for any component that is on the Stage: Package Components panel.

• The Version Control panel always shows a STG version and usually a BAS version. These versions are pointers to the component in the staging library and baseline library respectively.

• From the Version Control panel, the STG and BAS versions can be browsed, viewed, and compared.

Staging Versions Enabled

The staging versions facility may be enabled for a library type by setting the Save Staging Versions parameters in Global and Application Library Types.

These features are available in library types for which the staging version facility has been enabled.

• Users can add a component change description each time they create a new version of a package component on the Stage: Package Components panel.

• Users can save a staging version whenever they change a component on the Stage: Package Component panel.

50


• The administrator can make ChangeMan ZMF create a staging version every time a staging library member in the enabled library type is changed, or ChangeMan ZMF can ask if the user wants to overlay the component in the staging library without first creating a staging version.

• From the Version Control panel, the user can browse and view staging versions.

• Users can compare any two staging versions listed on the Version Control panel.

• Administrators can delete staging versions listed on the Version Control panel.

Serena™ ChangeMan® M+R Licensed

If your company has licensed ChangeMan M+R, and your administrator has installed the software, you can merge three to eight versions listed on the Version Control panel to create a new version of the component. ChangeMan M+R is automatically invoked, and the Base and derivative versions are automatically assigned.

Considerations For Staging Versions

You must consider the following issues before you decide to install or enable save staging versions:

• If the staging versions facility is installed, ChangeMan ZMF reads one of the staging version VSAM files whenever a user performs a function that replaces a member in a staging library. This VSAM read might have an adverse affect on ChangeMan ZMF response time.

• If the staging versions facility is installed and enabled for a library type, ChangeMan ZMF writes to the save staging version VSAM files whenever a user saves a staging version. This VSAM write might have an adverse affect on response time.

You can disable staging versions for a library type by changing the Save Staging Versions parameter to NO in the library type definition in Application Parameters.

You can de-install the staging package facility by removing the HPSPLIB and HPSIN DD statements from the SERNET started task JCL. You can then delete the three staging version VSAM files.

IMPLEMENTATION CHECKLIST

The following checklist is a high-level overview of the steps to implement ChangeMan ZMF. Some of the items have been covered in more detail earlier in this chapter. Since every site is different, and every implementation needs to be tailored for your specific needs, this checklist is only a suggestion of the steps you may wish to take.

Most implementations are done one application at a time. The first application may be a real application in your shop, or a test application set up to become familiar with ChangeMan ZMF.

51


1. Form an Implementation Team. This team usually consists of security personnel, application leads, application programmers, systems programmers, operations analysts, managers, et cetera. These are the people that can make and carry out the decisions necessary to implement ChangeMan ZMF.

2. Form an Application Test Team. This team should consist of someone who could perform program tests where required and someone that is extremely familiar with your existing change control process and/or compile and link edit procedures. Additionally, someone that is familiar with ISPF skeletons would be a large plus but this process could be learned if required. Your security administrator must be on alert as changes are needed periodically during the initial phases of implementation.

3. Conduct an implementation planning session with appropriate staff to determine how ChangeMan ZMF will help control the current environment and what the flow of the entire process should be.

4. Identify ALL libraries that will be managed by ChangeMan ZMF for the application.

5. Locate ALL compile/link edit procedures that will be required for integration into ChangeMan ZMF for the application. If current procedures are in skeleton format, all skeletons must be expanded and all symbolic variables must be resolved. This means that you have to review all the options for the compile/link edit procedures.

6. Identify ALL language types that will be required for integration into ChangeMan ZMF for the application (i.e., ASM, COBOL, DB2, CICS). If multiple versions of a language are required, that must also be noted. Each of these languages must have compile/link edit procedures that have been identified above.

7. Ensure the installation security package has been altered properly as outlined in the security portion of the ChangeMan ZMF documentation. This must include the set up of required ChangeMan ZMF entity names, association of the appropriate userids to those entity names, and set up of the proper data set access rules for the ID associated with the subsystem.

8. Have two TSO ID’s available for use in ChangeMan ZMF.

• The first ID must have the following privileges:

— All five ChangeMan ZMF entity privileges

— External authority for update of custom skeleton library

• The second ID is a standard TSO ID with no additional authority to ChangeMan ZMF. This ID only has access to a specific application, and it must not have any administrative capabilities. It is used for testing/debugging the system. Remember to grant this ID access to data sets and batch jobs as outlined earlier in this chapter.

9. The subsystem should be brought up, security resource rules established and set up for a test application, and the global and application administrative parameters should be defined with liberal rules. These initial administrative decisions may be made more restrictive later as you become more familiar with the product. Finish setting up the test application by defining libraries, languages, procedures, et cetera. (These processes are detailed in Chapter 4 and Chapter 5 of this Administrator Guide.)

52


10. If you are using the DB2 option, the installation procedures for DB2 should be followed, ensuring that the ID associated with the subsystem has SYSADM OR BIND/ADD authority for all DB2 programs. For more information on the DB2 option see the Serena™ ChangeMan® ZMF DB2 Option manual.

11. Identify all ChangeMan ZMF exits that will assist in the enforcement of shop standards for customization, if required. (See the Serena™ ChangeMan® ZMF Customization Guide)

12. Have test programs for each of the above language types so that the STAGE process may be completely tested. The resultant size (length) of the linked component is a good indicator of the ChangeMan ZMF process producing an equivalent load component to the one currently in production. In other words, the load components should be the same size if the skeletons invoked the same compile/link edit procedures. Running a parallel test of those components is a final test.

When the above tasks have been completed, you are ready to move through a phased implementation of ChangeMan ZMF. Many of the above tasks must be performed for each new application that is moved under ChangeMan ZMF control, for example, identifying the libraries necessary. Other tasks, such as setting up the subsystem security rules, are one time only items and do not need to be performed again.

CHANGEMAN ZMF ADMINISTRATOR DUTIES

The person who will become the ChangeMan ZMF administrator should be very involved in the implementation process. Not only will this help familiarize the administrator with the product, but he/she can be involved in the decisions about functions that he/she may later have to teach to users.

In addition, the administrator traditionally has many other duties in the supervision of ChangeMan ZMF. They can include:

• Consider the implementation needs of your sites, including space allocation for libraries as well as security needs. (See “Setting Up Global Administration” on page 55.)

• Set global parameters for your ChangeMan ZMF installation. (See “Setting Up Global Administration” on page 55.)

• Consult on and/or set application parameters. (See “Setting Up Application Administration” on page 97.)

• Set the global and/or application parameters for remote sites. (See “Configuring Remote Sites” on page 173.)

• Produce and browse reports for your sites or specific applications. (See “Defining and Running ChangeMan ZMF Reports” on page 183.)

• Customize ChangeMan ZMF for your site. Customization includes the implementation of exits and tailoring skeletons. (See the Serena™ ChangeMan® ZMF Customization Guide.)

• Continually monitor ChangeMan ZMF for packages in limbo as well as packages whose installation you wish to expedite or prohibit “Monitoring Site and Application Packages” on page 163.

53


• Periodically execute housekeeping functions such as starting up and shutting down the ChangeMan ZMF instance, backing up the Package Master, clearing the logs, updating the query component relationship information. (See “Housekeeping Tasks” on page 207.)

• Act as primary contact for questions, problems and suggestions forwarded to Serena Customer Support.

54


55

SETTING UP GLOBAL ADMINISTRATION 4

This chapter explains how to set up and change global administration for your ChangeMan ZMF instance. Some entries in global administration define general use parameters and functions. Other global administration entries limit the range of choices available when defining parameters and functions for applications.

ACCESSING THE GLOBAL ADMINISTRATION OPTIONS

Perform these steps to access the Global Administration Options panel.

1. On the ChangeMan ZMF Primary Option Menu, select option A and press ENTER. The Administration Options panel is displayed:

2. On the Administration Options panel, type G and press ENTER. The Global Administration Options panel is displayed:

CMNADMOM ------------------- ADMINISTRATION OPTIONS --------------------------- OPTION ===> A Application - Perform application administration functions G Global - Perform global administration functions Press ENTER to process; Enter END command to exit.

CMNGAMEN --------------- GLOBAL ADMINISTRATION OPTIONS --------------------- OPTION ===> 1 Parms - Generate global parameters 2 Library - Generate library types 3 Language - Generate language names 4 Procedures - Generate compiling procedures 5 Reason Codes - Generate reason codes for unplanned packages 6 Sites - Generate site information 7 Lock/Unlock - Lock or unlock application parameters D Dates - Update the installation calendar I Impact - Perform impact analysis maintenance N Notify - Update the global notification file O Options - Configure selectable options R Reports - Generate Change Man batch reports S Skeleton - Create, update, and test skeleton procedures Press ENTER to process; Enter END command to exit.

56

Chapter 4: Setting Up Global Administration

SETTING UP GLOBAL PARAMETERS

As a global administrator you can set parameters to govern the action of users. If you set these global parameters liberally, you allow the application administrator more choice in configuring ChangeMan ZMF at the application level. The application parameters can be more restrictive than the global parameters, but they cannot be more liberal. This allows more control over sensitive applications while allowing other applications more latitude.

Note The rules you set up for ChangeMan ZMF during global administration are not application specific—they affect all applications.

To setup the global parameters, complete the following steps, which consists of accessing five Global Parameters panels.

1. From the Global Administration Options menu (CMNGAMEN), select option 1. The Global Parameters Part 1 of 6 panel (CMNGGP01) is displayed:

The following table describes the fields of the Global Parameters Part 1 of 6 panel (CMNGGP01) and the valid information that you can enter in the fields.

Field Description

SUBSYSTEM Displays the subsystem ID that you are currently logged onto

RLS option Type Yes or No to indicate whether you wish to activate record level sharing (RLS). An activated RLS allows several ChangeMan ZMF instances to run different applications and share the same package master.

CMNGGP01 -------------- GLOBAL PARAMETERS - PART 1 OF 6 --------------------- COMMAND ===> SUBSYSTEM: M RLS option: YES CHANGE MAN ENVIRONMENT ===> A (A/D/DP/P) JOB ENTRY SYSTEM ===> JES2 (JES2 or JES3) SITE NODE NAME ===> U510ALL LOGICAL UNIT OR SYSTEM NAME ===> P393 DEFAULT UNIT NAME ===> 3390 (Generic disk unit) DEFAULT VOLUME SERIAL ===> SECURITY SYSTEM ===> SAF (SAF, RACF, ACF2, or TSS) CHANGE MAN SECURITY RESOURCE ===> $CHGMAN INSTALLATION JOB SCHEDULER ===> CMN (CMN, Manual or Other) SCHEDULER INTERVAL IF CMN ===> 005 (Minutes) TRANSMISSION VEHICLE ===> IEBCOPY (IEBCOPY or Other) NORMAL BUSINESS HOURS: FROM ===> 0001 TO ===> 0002 (HHMM format) AGING - INSTALLED PACKAGES ===> 32 (0 to 999 days) - STAGING DATASETS ===> 8 (0 to 999 days) Press ENTER to process; Enter END command to exit.

57


CHANGEMAN ENVIRONMENT

Type one of the following:

A (All environment has both development and production on one machine. It does not manage libraries in ChangeMan ZMF P (production) environments.

D (Development environment allows change packages to be built, approved, promoted, distributed to remote sites, rippled into Baseline libraries, but not installed into Production libraries. This choice is appropriate for a data center where changes are developed, but where production processing does not occur.

DP (Development and production environment allows change packages to be built, approved, promoted, distributed to remote sites, rippled into Baseline libraries, and installed into Production libraries. This choice is appropriate for a data center where changes are developed, installed into production, and distributed to remote sites for production installation.

P (Production environment is a production center, also referred to as a remote site. No development is performed on this machine)

Note: Once you choose an environment type, do not change it.

JOB ENTRY SYSTEM

Type the name of the job entry system (JES2 or JES3) used at your site.

SITE NODE NAME Type a common name or nickname for this ChangeMan ZMF instance.

LOGICAL UNIT OR SYSTEM NAME

Type the logical unit or system name (SMF ID) where this ChangeMan ZMF instance runs.

DEFAULT UNIT NAME

Type the generic unit name for DASD to be used for dynamic allocations for this ChangeMan ZMF instance. This field may be left blank if DEFAULT VOLUME SERIAL is used.

DEFAULT VOLUME SERIAL

Type the DASD volume serial number to be used for dynamic allocations for this ChangeMan ZMF instance. This field may be left blank if DEFAULT UNIT NAME is used.

SECURITY SYSTEM

Enter the name of the security system used at your site. This field must match the setting in the SERLCSEC module. See the Serena™ ChangeMan® ZMF Installation Guide.

SAF is an acronym for System Authorization Facility, an interface defined by MVS that enables programs to use system authorization services to protect access to resources such as data sets and MVS commands. SAF provides a common interface for IBM RACF, CA-ACF2, and CA-Top Secret where your security rules are defined.

If you use TCP/IP to communicate with ChangeMan ZMF, it must use SAF to interface to your security system.

Field Description

58


INSTALLATION JOB SCHEDULER

Enter the default scheduling system that displays to users when they are building a change package (in the Installation Instructions panels). The scheduling system controls the submission of the package installation batch jobs.

CMN

The ChangeMan ZMF internal scheduling system.

Allows a user to change this field to either CMN or MANUAL when specifying change package information. When packages use the CMN scheduler, ChangeMan ZMF monitors can delay installation or install the packages early. See “Chapter 8. Monitoring Site/Application Packages” for details.

MANUAL

Allows a user to manually control the submission of installation and de-installation jobs. Causes the installation process to begin as soon as the package is approved. Package installation can be inhibited by holding the last approval or the package can be installed immediately by approving the package before the scheduled installation date and time.

Prohibits the user from changing this field when specifying change package information.

OTHER

An external scheduler such as CA7, ADC2, CA-Scheduler, and so forth. OTHER causes ChangeMan ZMF to submit a batch job to add the package install job information to the scheduler's database.

You must modify skeleton CMN17 to include the batch interface for your site's scheduling system.

Allows the user to change this field to either CMN, MANUAL, or OTHER when specifying change package information.

SCHEDULER INTERVAL IF CMN

Specify how often ChangeMan ZMF checks for packages ready to be installed if CMN is the job scheduler type. Enter the information in the MMM format (minutes). The available range is from 1 to 255.

TRANSMISSION VEHICLE

Enter the data transmission vehicle that ChangeMan ZMF uses to transmit messages, change packages, and other data between the development system and the production systems at the remote sites. This variable is used in file tailoring the install jobs.

IEBCOPY

You can use IEBCOPY if there are no remote sites and DASD is shared between the development and production environments.

If your site is an ALL or a DP environment, this field must be IEBCOPY. (Since no real data transfer takes place within both of these environments, only a copy utility is needed.)

OTHER

Enter OTHER to use a different transmission vehicle.

NORMAL BUSINESS HOURS

Enter the time range describing the normal business day in military notation (HHMM).

Field Description

59


2. When you have completed entering information on the Global Parameters Part 1 of 6 panel (CMNGGP01) and press ENTER. The Global Parameters Part 2 of 6 panel (CMNGGP02) is displayed:

AGING: INSTALLED PACKAGES

Enter the number of days a package record is to remain within the Package Master itself. The package must be in BAS, INS, or TCC status for this value to take effect. Once the aging criteria set here have been met, the package can be deleted through a housekeeping job. We recommend that this value be set at 500.

Note: The choices you make here and in the AGING:STAGING DATASETS field described below affect DASD to the extent that the package records continue to take up space until they are deleted.

AGING: STAGING DATASETS

Enter the number of days that staging data sets from a package remain in the systems catalog. The corresponding change package must be in BAS, INS, or TCC status for this value to take effect.

To delete the Staging data sets after the package is installed, run the appropriate housekeeping jobs to either delete or archive the package records (see “Chapter 9. Housekeeping Tasks”). The housekeeping job for deletion of the Staging data sets removes them after the aging criteria have been met. After the housekeeping job deletes the Staging data sets for a package, a user can no longer back out the package.

The installed package record must exist in the Package Master at the time that its associated staging libraries are deleted. Thus, the installed packages value must be greater than or equal to the staging data sets value.

Field Description

CMNGGP02 -------------- GLOBAL PARAMETERS - PART 2 OF 6 ----------------------- COMMAND ===> BASELINE: STACKED REVERSE DELTA ===> YES (Y/N) PANVALET ===> YES (Y/N) USER DEFINED ===> NO (Y/N) LIBRARIAN ===> YES (Y/N or LAM) KEEP BASELINE BY SITE ===> NO (Y/N) REQUIRE WORK REQUEST NUMBER ===> NO (Y/N; affects INFO) REQUIRE DEPARTMENT NUMBER ===> NO (Y/N) DISABLE INSTALLATION CALENDAR ===> YES (Y/N) ALLOW TEMPORARY PACKAGES ===> YES (Y/N) PROCESS PARTICIPATING PACKAGES BY INSTALLATION DATE ===> NO (Y/N) HIERARCHICAL APPROVAL PROCESS ===> YES (Y/N) APPROVER NOTIFICATION VEHICLE: SERNET ===> YES (Y/N) BATCH ===> YES (Y/N) ALLOW DESIGNATED PROC OVERRIDE ===> NO (Y/N) USE GLOBAL NOTIFICATION FILE ===> YES (Y/N) ALLOW APPLICATION UPDATE TO FILE ===> YES (Y/N) GLOBAL NOTIFICATION FILE ===> PROD99.PROFSERV.CMN510N.NOTEFILE Press ENTER to continue; Enter B to go back 1 screen, or CANCEL to exit.

60


The first five fields of the panel specify the storage means for back levels of Baseline libraries. Except for CA-Panvalet and CA-Librarian, the current level of any baseline library is configured as a PDS. The storage means for the back levels of each particular Baseline library are selected by the Application Administrator (under the Baseline option) based on the means allowed here.

A YES in one of these fields lets the Application Administrator choose to use one of these formats for libraries, and enables a particular library format during Application Administration. A NO prevents the Application Administrator from using this storage means, and disables this format during Application Administration.

61


The following describes the fields of the Global Parameter Part 2 of 6 panel (CMNGGP02) and the valid information that you can enter in the fields.

Field Description

STACKED REVERSE DELTA

Enter YES to allow use of the Stacked Reverse Delta format. This storage means uses one PDS for the (0) level, and a second PDS for the -001 through -999 levels. Backup levels are stored in compressed form. This option optimizes disk space utilization.

Enter NO to disallow the use of this option.

PANVALET Enter YES to let users keep backup levels of baseline in CA-Panvalet libraries.

This option lets ChangeMan ZMF stage from a CA-Panvalet file and check out from and to a CA-Panvalet file. The systems installer must generate and compile the component SERIFACE, with the CA-Panvalet interface turned on before you choose this option.

Enter NO to disallow use of this option.

LIBRARIAN Enter YES or LAM if you have CA-Librarian Masters.

This choice lets ChangeMan ZMF stage from a CA-Librarian file and check out from and to a CA-Librarian file.

Enter LAM if you use Library Access Method. (CA-Librarian 3.6 or higher is required.) Use LAM if you plan, during testing, to concatenate PDS COPY libraries with baseline. For example:

//SYSLIB DD DISP=SHR,DSN=CGMZ.CMNSTAGE.#000123.CPY,// SUBSYS=LAM// DD DISP=SHR,DSN=CMNBASE.LAM.CPY,// SUBSYS=LAM

This option implies that you have generated SERIFACE for CA-Librarian.

Enter NO to disallow use of this option.

USER DEFINED Enter YES to allow another type of library organization be used. This choice requires file tailoring of install skeletons. It implies that you have generated CMNIFACE for Other.

Enter NO to disallow use of these other types of library organizations.

62


KEEP BASELINE BY SITE

Enter YES to allow the Development (D) or Development (DP) Production site to keep a set of Baseline libraries for each additional site that has been generated within their ChangeMan ZMF system. Use if an application has multiple sites, and you want to maintain Baseline libraries at each site. With YES, you receive subsequent prompts at baseline library definition, and package build, to indicate which site is being selected.

Enter NO if remote site Baseline libraries are not to be maintained. When you enter NO, the Baseline libraries are only kept at the DP or D site.

NO is the recommended option because it:

Prevents duplications of DASD

Makes the maintenance of skeletons easier

Keeps multiple sites synchronized

Note: You can only select one site at package creation time and all checkouts are from the baselines associated with that site. You cannot install to two sites in the same package when you keep baselines by site.

Audit only runs against the baselines/site selected at package create time and only the baseline/site libraries selected at that time are concatenated in batch jobs for that package.

Use package query (option Q.P) to see which sites were included in the package.

REQUIRE WORK REQUEST NUMBER

Enter YES to require users to enter a work request number during package creation.

Enter NO to let the entry of a work request number be optional.

REQUIRE DEPARTMENT NUMBER

Enter YES to require users to enter a department number during package creation.

Enter NO to let the entry of a department number be optional.

DISABLE INSTALLATION CALENDAR

This option lets the Global Administrator disable the Planned Installation Calendar. When you create a change package, ChangeMan ZMF only checks the install date to verify if it is a valid date, and disregards the maximum packages criteria.

Enter YES to let users specify any date for the schedule installation date of packages.

Enter NO to dictate the scheduling of package installation by the Planned Installation Calendar.

ALLOW TEMPORARY PACKAGES

Temporary change packages are placed into production and concatenated ahead of Production libraries. They are never rippled into Baseline and are deleted from the production environment after the number of days specified at package creation.

Enter YES to let temporary change packages be created.

Enter NO to disallow users to create temporary change packages

Field Description

63


PROCESS PARTICIPATING PARCKAGES BY INSTALLATION DATE

* This option is for audit.

Audit can process participating package groups within a Complex or Super package base on the installation date of participating packages.

Participating packages defined to a Complex or Super package that have not been baselined and have installation dates that are equal to or earlier than the participating package containing the component to be compiled or link-edited are included as part of the SYSLIB concatenation.

Enter YES to process and audit participating packages within a Complex or Super package by the installation date.

Enter NO to process and audit all participating packages defined to a Complex or Super package.

HIERARCHICAL APPROVAL PROCESS

Enforce the numeric approval sequence specified in the Order Number field of the Planned Approvals and Unplanned Approvals in application administration. When the approval sequence is enforced, notification is sent to userids and e-mail addresses in coded in User(s) to Notify only when approvals at lower is executed as each approval becomes “pending” approval.

At freeze, all Users to Notify at the lowest Order Number for the lowest numeric in the sequence specified in the approval Order Number. Notification of “Users to notify” at the next sequential Order Number occurs when all approvals at the previous Order Number have been entered.

Type NO to notify all approval “Users to notify” at all Order Numbers when the package is frozen.

APPROVER NOTIFICATION VEHICLE

Enables notification vehicles for this ChangeMan ZMF instance. Notification vehicles are used to notify an approver about packages pending approval. You can enable more than one.

SERNET - Send notification data through SERNET to ChangeMan ECP, which will format an e-mail message and send through SMTP.

BATCH - File tailor skeleton CMN$$NTF and submit the generated JCL with Job Card Information defined in Application Administration Parameters.

Note: Notification through MVS SEND is always available.

ALLOW DESIGNATE PROC OVERRIDE

Use this option to allow or prohibit the update of a component’s LOD TYPE value specified within the Application’s DESIGNATED COMPILE PROCEDURE option. A YES entered here allows update to a component’s LOD TYPE value. This value overrides the TARGET TYPE value specified at the Application’s LIBRARY TYPE option. A NO entered here prohibits the update to a component’s LOD TYPE value; in this case the LOD TYPE field displays in browse only mode.

USE GLOBAL NOTIFICATION FILE

Activates or deactivates the Global Notification Facility. This is a facility that enables administrators to send online messages to end users. See “Creating or Updating the Global Notification File” on page 90. for details.

NO deactivates the GNF. The GNF option does not display on the Primary Option Menu (CMN@PRIM), and the ALLOW APPLICATION UPDATE PARAMETER field is automatically set to NO.

YES activates the GNF. The GNF option displays on the Primary Option Menu (CMN@PRIM). If you enter YES, you must also fill in the ALLOW APPLICATION UPDATE TO FILE field and the GLOBAL NOTIFICATION FILE NAME field.

Field Description

64


Note The Delta Deck storage means is obsolete for new baseline libraries. However, existing baselines with this storage means are supported.

3. When you complete entering information on the Global Parameters Part 2 of 6 panel (CMNGGP02)panel, press ENTER. The Global Parameters Part 3 of 6 panel (CMNGGP03) is displayed:

ALLOW APPLICATION UPDATE TO FILE

This field controls the display of the GNF option on the Application Administration Options panel (CMNLAMEN), as well as update access to the GNF.

Enter NO to not display the GNF option during application administration. Updates to the notification file are disallowed.

Enter YES to display the GNF option during application administration. Application Administrators are allowed update access to the notification file

GLOBAL NOTIFICATION FILE NAME

Defines the data set name where authorized GNF users can specify and edit a notification message. If you specify NO in the USE GLOBAL NOTIFICATION FILE field, this field is not required and is always stored as blank. If you specify YES in the USE GLOBAL NOTIFICATION FILE field, you must enter a PDS or SEQUENTIAL data set that follows standard naming conventions.

Field Description

CMNGGP03 -------------- GLOBAL PARAMETERS - PART 3 OF 6 --------------------- COMMAND ===> AUDIT LEVEL ===> 0 (0,1,2,3,4,5) CHECKOUT ENFORCEMENT RULE ===> 1 (1,2,3) ALLOW CONCURRENT CHECKOUT ===> YES (Y/N) ALLOW CHECKOUT TO PERSONAL LIB. ===> YES (Y/N) STAGING RESTRICTION LEVEL ===> 1 (1,2,3) SAVE TO PERSONAL & STAGING LIBS ===> NO (Y/N) OVERLAY PRIOR STAGED MODULE ===> YES (Y/N) VALIDATE VERSION DURING STAGING ===> NO (Y/N) PROMOTION/DEMOTION RULE ===> 0 (0,1,2,3,4) VALIDATE ISPF LIBRARIES ISPLLIB ===> YES (Y/N) ISPMLIB ===> YES (Y/N) ISPPLIB ===> YES (Y/N) ISPSLIB ===> YES (Y/N) Press ENTER to continue; Enter B to go back 1 screen, or CANCEL to exit.

65


The following table describes the fields on the Global Parameters Part 3 of 6 panel (CMNGGP03) and the valid information that you can enter on the panel.

Field Description

AUDIT LEVEL Enter the numeric value that dictates the Audit level that must be passed before a change package can be frozen.

0—Audit is recommended, but is optional.

1—Audit is required, but any return code (except ABEND) is acceptable. This is the default option.

2—Audit is required, and the return code must not exceed 12. This implies that there are out-of-sync situations within the Staging libraries.

3—Audit is required, and the return code must not exceed 8. This implies that there are no out-of-sync situations within the Staging libraries, but there are out-of-sync situations with respect to the Baseline libraries.

4—Audit is required, and the return code must not exceed 4. This implies that there are no out-of-sync situations within the Staging libraries or the Baseline libraries, but at least one component of the Staging library is a duplicate of its Baseline counterpart.

5—Audit is required, and the return code must not exceed 0. This implies that there are no out-of-sync situations within either the Staging libraries or the Baseline libraries and no duplicates exist.

CHECKOUT ENFORCEMENT RULE

Enter the numeric value that dictates the rule that must be passed before a component (not new components, but components that exist in the Baseline) can be staged. The administrator can restrict who stages components that are not first checked out from baseline.

1—Checkout is optional.

Any component can be staged, regardless of whether it exists in Baseline or has been checked out to a package. ChangeMan ZMF does not check for the component's existence in the Baseline libraries.

2—Checkout is required unless the user passes an entity check.

Users attempting to stage a component that exists in the Baseline but has not been checked out must pass a security system ENTITY CHECK before the stage can proceed. The entity name is specified in the application parameter generation. Staging is not allowed if the user does not pass the entity check.

3—Checkout is mandatory.

Disallow anyone from staging a component that exists in the baseline library but has not been checked out to the package requesting the stage.

ALLOW CONCURRENT CHECKOUT

Enter YES to let a component be checked out to personal or Staging libraries. (Allow concurrent checkout of components that are already included in a change package. During installation, the second checked out component overlays the first.)

Enter NO to prevent a component be checked out if it resides in another package. (This prevents users from checking out components that are already checked out to a package.)

This rule applies to the same package as well as other packages that share the same Baseline library. It does not apply to unplanned (emergency) packages.

ALLOW CHECKOUT TO PERSONAL LIB

Enter YES to let users check out to a personal library.

Enter NO to require all checkouts to go to Staging libraries.

This rule does not apply to unplanned (emergency) packages.

66


STAGING RESTRICTION LEVEL

Enter the appropriate numerical value to determine which users are allowed to stage new components. From the user's view, it regulates the Stage Development Driven user option in the Stage Options panel (CMNSTG00).

1—Lets all users access both Development Driven (stage components into a package without checking them out) and Package Driven stage options.

2—Requires user to pass an entity check before they are allowed to stage any components via the Stage Development Driven option. Only TSO ID’s associated with the ENTITY name are allowed to use both stage options. The entity name, which must be defined to your security system, is specified in Staging Restriction Level in the application parameters.

3—All users are required to check out all components to a package before staging, effectively disabling the Stage Development Driven Option

SAVE TO PERSONAL & STAGING LIBS

This rule applies to edit in Staging when a personal or Development library is involved.

Enter YES to allow updates to Staging and personal libraries.

Enter NO to allow updates to the Staging library only when a component is staged from a Development library and then edited through ChangeMan ZMF.

OVERLAY PRIOR STAGED MODULE

If one user in an application has staged a source component, and another user tries to stage another version of the same component in the same change package, this field dictates whether overlaying of the first component is allowed.

Enter YES to let any previously staged component be overlaid. ChangeMan ZMF issues a confirmation request before overlaying the component.

Enter NO to allow only a single owner of a component. This option is not enforced against members that are checked out to the package in batch.

More than one user can access the same component within the same change package. Entering a NO in this field prevents overlaying of the same component by another user. (This is based on the ISPF statistics in the user’s personal library. If those statistics do not match what is defined as the user ID in the staging package, ChangeMan ZMF does not allow an overlay.) The determining factor for the overlay is the TSO ID in the package.

VALIDATE VERSION DURING STAGING

This function ensures the integrity of a Baseline library component between Checkout and Staging. Users must check out components (not stage from development libraries) for this function to be in effect. This option is also affected by the STAGING RESTRICTION LEVEL field. If the Baseline version of a component has been altered after a user has checked it out (for example, another package has been installed that contains this component), staging of that component is prevented.

Enter YES to enforce this validation (requires a regression test).

Enter NO to ignore the validation.

Field Description

67


PROMOTION/ DEMOTION RULE

Enter the appropriate numeric value of the rule to regulate the movement of components from Promotion libraries to Staging libraries (for editing) and back again. For an overview of Promotion in the ChangeMan ZMF cycle, see “What is ChangeMan ZMF?” on page 19.

0—Allows Promotion and Demotion of components, even when the change package has not been frozen. This is liberal Promotion and Demotion.

This option allows re-editing of components in Staging, without requiring a demotion. Thus, different versions of a component can exist simultaneously in Staging and Promotion libraries. For example, if a component at promotion level 2 is edited in Staging, its promotion level is shown as “0” on the promotion panel. However, the component still exists in the level 2 library. It is the user’s responsibility to monitor these versions and demote previously promoted components, if desired.

Rules 1 through 4 restrict promotion to frozen (FRZ) packages only:

1—Requires selective Demotion of a component followed by selective Refreeze, Edit, and Promotion directly back to the package's promotion level.

2—Requires selective Demotion of a component followed by selective Refreeze, Edit, and Promotion through all intermediate promotion levels.

3—Requires full Demotion of the entire package followed by a selective Refreeze, Edit, and Promotion through all intermediate promotion levels.

4—Requires full Demotion of the entire package followed by a Revert of the entire package to DEV status.

VALIDATE ISPF LIBRARIES

Validates the ISPF library concatenation used in a ChangeMan ZMF client against the library concatenation coded in the SERNET started procedure.

When an ISPF client session is started, the ISPF library concatenation used to connect to ChangeMan ZMF is superseded by the concatenation coded in the SERNET started procedure. The VALIDATE ISPF LIBRARIES function ensures that no unauthorized libraries are subsequently concatenated for ChangeMan ZMF execution by a LIBDEF in the user’s TSO session.

The VALIDATE ISPF LIBRARIES function also verifies the ISPF library concatenation used in ChangeMan ZMF cataloged procedure CMNxJOBS. This prevents users from substituting a procedure with unauthorized libraries by using a JCLLIB statement in the JOB STATEMENT INFORMATION on ChangeMan ZMF panels that invoke the batch API.

ISPLLIB Type YES to validate ISPF load library concatenation (data set names and order).

Type NO to bypass validation of the ISPF load library concatenation.

ISPLIB Type YES to validate ISPF message library concatenation (data set names and order).

Type NO to bypass validation of the ISPF message library concatenation.

ISPLPLIB Type YES to validate ISPF panel library concatenation (data set names and order).

Type NO to bypass validation of the ISPF panel library concatenation.

ISPLSIB Type YES to validate ISPF skeleton library concatenation (data set names and order).

Type NO to bypass validation of the ISPF skeleton library concatenation.

Field Description

68


4. After you have completed entering information in the fields of the panel, press ENTER. The Global Parameters Part 4 of 6 panel (CMNGGP04) is displayed:

The following table describes the fields on the Global Parameters Part 4 of 6 panel (CMNGGP04) and the valid information that you can enter on the panel:

Field Description

YES

NO

Do not increment the job name suffix for batch jobs submitted for background processing; force background processing for a userid to single-thread. This rule applies to all applications.

Allow YES or NO entry for this option in Application Administration Parameters.

USE ZPREFIX IN BATCH JOBS

Determines if ChangeMan ZMF uses the userid to construct a TSO profile to identify the variable pools when a TSO session is opened for batch API processing.

YES

NO

Use &ZPREFIX instead of &ZUSER in the PROFILE PREFIX command in batch TSO sessions for batch API functions. This rule applies to all applications.


CREATE COMPONENT WORK RECORDS

Determines if component work records are created when a package component is changed. Component work records show who has updated a package component. Component work records can be accessed from the package component list.

YES

NO

Create a component work record when a package component is updated. This rule applies to all applications.


CMNGGP04 -------------- GLOBAL PARAMETERS - PART 4 OF 6 ----------------------- COMMAND ===> JOB NAME INCREMENT OVERRIDE ===> NO (Y/N) USE ZPREFIX IN BATCH JOBS ===> NO (Y/N) CREATE COMPONENT WORK RECORDS ===> NO (Y/N) FORCE AUDIT OF UNPLANNED PACKAGES ===> NO (Y/N) BYPASS STAGING LIBRARY ENQUEUES ===> NO (Y/N) ALLOW LINK PACKAGES ===> YES (Y/N) MEMO DELETE EMPTY PACKAGES ONLY ===> NO (Y/N) APPROVAL RESTRICTIONS: PACKAGE CREATOR CANNOT APPROVE ===> NO (Y/N) PACKAGE WORKER CANNOT APPROVE ===> NO (Y/N) ONLY 1 APPROVAL PER USER ID ===> NO (Y/N) DISPLAY PACKAGE USER OPTION PANEL(S) ===> YES (Y/N) Press ENTER to continue; Enter B to go back 1 screen, or CANCEL to exit.

69


FORCE AUDIT OF UNPLANNED PACKAGES

Determines if audit is required for unplanned packages.

This option is only in effect if the Audit Level is higher than 0.

YES

NO

Require audit before freeze for unplanned packages. A bad return code from audit will not prevent freeze for unplanned packages. This rule applies to all applications.


BYPASS STAGING LIBRARY ENQUEUES

Determines if all staging libraries in a package are enqueued while a delete request from the Stage Package Component panel is processed.

YES

NO

Disable the staging library enqueue for component delete processing. This rule applies to all applications.


ALLOW LINK PACKAGES

Determines if applications can be defined to allow packages to be linked to other change packages through ChangeMan ECP. Refer to the ChangeMan ECP Linked Package facility. Linked packages are subject to delete, freeze, approval, and revert restrictions.

YES

NO

Permit applications to be defined that allow packages to be linked to other packages through ChangeMan ECP.

Prohibit package linking in this ChangeMan ZMF instance.

MEMO DELETE EMPTY PACKAGES ONLY

Prohibit package Memo Delete if a change package contains any components. This restriction also applies to packages that contain only scratch or rename utility requests.

YES

NO

Require all applications to specify YES for this parameter in Application Administration to restrict Memo Delete.


APPROVAL RESTRICTIONS

The next three fields on this panel limit a user’s approval authority for a planned package, even though they may otherwise be permitted to approval to that package. Approval restrictions controlled by these parameters do not apply to unplanned packages.

PACKAGE CREATOR CANNOT APPROVE

Prohibits the user who created a package from entering an approval for that package, even if they are authorized by the security system to enter approvals.

This option applies only to planned packages. Approvals for unplanned packages are not effected by this option.

YES

NO

Prohibit users from entering an approval for a package that they created. This restriction applies to all applications.


Field Description

70


5. After you have completed entering information in the fields of the panel, press ENTER. The Global Parameters Part 5 of 6 panel (CMNGGP05) is displayed:

PACKAGE WORKER CANNOT APPROVE

Prohibits a user who has worked on a component in a package from entering an approval for that package, even if they are authorized by the security system to enter approvals.


YES

NO

Prohibit a user who worked on a package component from entering an approval for the package. This restriction applies to all applications.

Allow YES or NO entry for this option in Application Administration Parameters. level.

ONLY 1 APPROVAL PER USER ID

Prohibits one user from entering more than one approval for a package, even if they are authorized by the security system to enter those approvals.


YES

NO

Restrict each userid to only one approval per package. This restriction applies to all applications.


DISPLAY PACKAGE USER OPTION PANEL(S)

Determines if the panels that contain the Package User Record fields are displayed when users access these functions: Package Create, Package Update, Package Query.

YES

NO

Display the panels containing Package User Record fields.

Hide the panels containing Package User Record fields.

Field Description

CMNGGP05 -------------- GLOBAL PARAMETERS - PART 5 OF 6 --------------------- COMMAND ===> STAGING LIBRARY MODEL DATASET NAME: DEV MODEL DSNAME ===> PROD99.CMN.Q510ALL.????.####### PRD MODEL DSNAME ===> PROD99.CMN.Q510ALL.????.####### - “????” is placeholder for application name. - “#######” is placeholder for package number (.#000123). - (press <HELP> for more information) PACKAGE MASTER ===> PROD99.CMNSYS.Q510ALL.CMNPMAST COMPONENT MASTER ===> PROD99.CMNSYS.Q510ALL.CMNCMPNT DELAY FILE ===> PROD99.CMNSYS.Q510ALL.CMNDELAY EMAIL SERVER ADDRESS: TCP/IP ADDRESS ===> 111.111.111.111 PORT NUMBER ===> 22222 Press ENTER to continue; Enter B to go back 1 screen, or CANCEL to exit.

71


The following table describes the fields on the Global Parameters Part 5 of 6 panel (CMNGGP05) panel and the valid information that you can enter in the fields.

Note For environments where packages are installed at remote sites (DP environment), you must use different patterns to differentiate between Development and Production libraries.

If this is a DP environment using IEBCOPY as the transmission vehicle, use identical names for both fields.

It is recommended that at least one node be fixed and contain the letters CMN (the standard abbreviation for ChangeMan ZMF). The four letters following CMN can be any letters that are easily recognizable in the user's environment.

Field Description

DEV MODEL DSNAME

Enter the model data set name for Staging libraries in the development environment. Four questions marks (????) in the data set name are replaced with the appropriate application mnemonic. Seven pound signs (#######) are replaced with the change package number.

ChangeMan ZMF uses the model data set name when it allocates each Staging library. Development and production Staging libraries are created for each change package (but note exception below). A separate Staging library is created for each library type in the package. The data set names are generated using the patterns entered here. If you are generating parameters for an ALL environment, use the same pattern in the PRD MODEL DSNAME as well

PRD MODEL DSNAME

Enter the model data set name for staging libraries in the production environment. Replacements are made as described above. If the environment is D or DP, you must also enter this information in the Site definition (Global Administrator option 6). This identifies the installation libraries for each remote site to the development site

PACKAGE MASTER

COMPONENT MASTER

DELAY FILE

The name of the package master, component master, and delay files used by the ChangeMan ZMF session.

ECP WEB SERVER ADDRESS

The TCP/IP address and port number of the Web server where ChangeMan ECP runs. ChangeMan ECP will send notifications through your SMTP E-mail server. This information is required if the SERNET approval notification vehicle is activated. See “APPROVER NOTIFICATION VEHICLE” on page 63.

TCP/IP ADDRESS The TCP/IP address of the Web server where ChangeMan ECP runs.

PORT NUMBER The port number of the Web server where ChangeMan ECP runs.

72


6. After entering information in the Global Parameters Part 5 of 6 panel (CMNGGP05), press END. The Global Parameters Part 6 of 6 panel (CMNGGP06) is displayed:

This job card information is used when the package installation jobs are built at Freeze time. Specifically, ChangeMan ZMF uses it when submitting batch jobs for distributing change packages, acknowledging distribution, installing change packages, acknowledging installation, backing out change packages, and rippling an application's baseline files.

The job name is set to reflect package and installation transaction numbers This is the only job card information that the Global and Application Administrators provide. Users are required to set up similar job cards for batch API jobs such as Staging and Freezing.

Information provided here is used as the default for the Application Administrator, who can modify it at the application level. The Global Administrator for DB2 can also override it.

The global parameters are generated after you press ENTER.

DEFINING LIBRARY TYPES AND STAGING LIBRARY ATTRIBUTES

A library type definition sets processing rules for the components stored under that library type. The definition also sets the data set attributes for the package staging library that is allocated for the library type. The Global Administrator defines the library types that are available to applications.

Global administration will contain library types for all unique component types and processing requirements that might be required in any application. Library types can be changed at the application level, but they should be standardized on global definitions to simplify administration maintenance.

To define a global library type, follow these steps.

CMNGGP06 -------------- GLOBAL PARAMETERS - PART 6 OF 6 --------------------- COMMAND ===> JOB STATEMENT INFORMATION: ===> //CMNSTART JOB (X170,374),GLOBAL,_______________________________________ ===> // CLASS=U,MSGCLASS=9_______________________________________ ===> //* JOBCARD FROM GLOBAL PARAMETERS PART 5 OF 5 PANEL CMNGGP05___________ ===> //*_____________________________________________________________________ This job card will be used when the package installation jobs are built at freeze time. The job name will change to reflect package and install transaction numbers. The job card can be overridden at the Application Administration "PARMS" option and the Global Administration DB2 option. Press ENTER to generate global parameters. Enter B to go back 1 screen or CANCEL to exit.

73


1. On the Global Administration Options panel, type 2 on the Option line and press ENTER. The Global Library Types Part 1 of 2 panel is displayed. The first time you access this panel to define global library types, the panel is empty.

After you have entered library type definitions, the Global Library Types Part 1 of 2 panel might look like this.

CMNCGLT0 -------------- GLOBAL LIBRARY TYPES PART 1 OF 2 -- Row 1 to 17 of 150 COMMAND ===> SCROLL ===> PAGE Enter END command to save changes or CANCEL to exit. Enter * in line command field for global staging libraries selection list. LIB LIKE DEFER TARGET SEL. TYPE DESCRIPTION (S/C/L/P)(Y/N) TYPE OPT. '''' ___ ____________________________________________ _ _ ___ __ '''' ___ ____________________________________________ _ _ ___ __ '''' ___ ____________________________________________ _ _ ___ __ '''' ___ ____________________________________________ _ _ ___ __ '''' ___ ____________________________________________ _ _ ___ __ '''' ___ ____________________________________________ _ _ ___ __ '''' ___ ____________________________________________ _ _ ___ __ '''' ___ ____________________________________________ _ _ ___ __ '''' ___ ____________________________________________ _ _ ___ __ '''' ___ ____________________________________________ _ _ ___ __ '''' ___ ____________________________________________ _ _ ___ __ '''' ___ ____________________________________________ _ _ ___ __ ******************************* Bottom of data ********************************

CMNCGLT0 -------------- GLOBAL LIBRARY TYPES PART 1 OF 2 -- Row 1 to 17 of 150 COMMAND ===> SCROLL ===> PAGE Enter END command to save changes or CANCEL to exit. LIB LIKE DEFER TARGET SEL. TYPE DESCRIPTION (S/C/L/P)(Y/N) TYPE OPT. '''' CPY Copybooks___________________________________ C Y ___ __ '''' CTC Control Statements (PARMLIB)________________ P Y ___ __ '''' DBB DB2 Bind Control____________________________ P Y ___ __ '''' DBR DB2 DBRM____________________________________ P Y ___ __ '''' JCL Job Execution JCL___________________________ P Y ___ __ '''' LCT Link Edit Control Statements________________ P Y ___ __ '''' LST Compressed Stage Listings___________________ P Y ___ __ '''' LOD Load Modules________________________________ L Y ___ __ '''' MAP BMS MAP Load Modules________________________ L Y ___ __ '''' MPC BMS MAP Copybook (DSECT)____________________ C Y ___ __ '''' MPS BMS MAP Source______________________________ S Y MAP __ '''' OBJ Object Code_________________________________ P Y ___ __ '''' PRC JCL Cataloged Procedures____________________ P Y ___ __ '''' PKG DB2 Package Bind Control____________________ P Y ___ __ '''' SKL ISPF Skeletons______________________________ P Y ___ __ '''' SRC Source Code_________________________________ S Y LOD __

74


The following table describes the fields on the Global Library Types Part 1 of 2 panel.

Field Description

Line Command Type a line command to the left of a panel row.

S

I

R

D

Select to see the next panel for this library type.

Insert a blank library type row.

Repeat an existing library type row.

Delete an existing library type row.

LIB TYPE Type a three character library type.

Some library types are reserved. These types have built-in attributes, and they are used in particular internal processes.:

ASC

CPY

CTC

DBB

DBR

DOC

JCL

LCT

LOD

LST

PRC

SRC

APS painted screens (ChangeMan ZMF APS Option) - DCB must be RECFM=F/FB, LRECL=240

Copybooks - Defaults to Like-Copy (see the definitions for the LIKE types below.) DCB must be RECFM=F/FB, LRECL=80

Control Statements - Defaults to Like-PDS. DCB must be RECFM=F/FB, LRECL=80

DB2 Bind Control Statements (ChangeMan ZMF DB2 Option) - Defaults to Like-PDS. Used by the ChangeMan ZMF DB2 Selectable Option. DCB must be RECFM=F/FB, LRECL=80

DB2 DBRM (ChangeMan ZMF DB2 Option) - Defaults to Like-PDS. Used by the ChangeMan ZMF DB2 Selectable Option. DCB must be RECFM=F/FB, LRECL=80

Documentation. Defaults to Like-PDS. DCB must be RECFM=F/FB/V/VB

JCL - Defaults to Like-PDS, although libraries with this type are included in Impact Analysis JCL relationships. DCB must be RECFM=F/FB, LRECL=80

Link Edit Control Statements - Defaults to Like-PDS. DCB must be RECFM=F/FB, LRECL=80

Load Modules - Defaults to Like-Load. DCB must be RECFM=U.

Compressed Stage Listings - Defaults to Like-PDS. Cannot be explicitly staged. DCB must be RECFM=F/FB, LRECL=80.

Cataloged JCL Procedures - Default to Like-PDS, although libraries with this type are included in Impact Analysis JCL relationships. DCB must be RECFM=F/FB, LRECL=80

Source Code - Defaults to Like-Source. DCB must be RECFM=F/FB, LRECL=80

DESCRIPTION Enter freeform text describing the library type.

75


If you have a large number of library types (more than 40), you can alphabetize library types on the Global Library Types Part 1 of 1 panel to make it easy to locate a global library type when you define application library types.

LIKE (S/C/L/P) Type a one-character LIKE code to define behaviors and characteristics of a library type.

S

C

L

P

Blank

Like-Source - Components in Like-Source library types are staged through a batch job defined by a Language and Procedure assigned to the component to create a component in a Like-Load library type. Every Like-Source library type must have a TARGET TYPE in its Library Type Definition. There is a source-load relationship between every Like-Source component and a Like-Load component. Members in Like-Source libraries are analyzed for Impact Analysis CPY relationships.

Like-Copy - Components in Like-Copy library types are not processed through a procedure by stage. Like-Copy libraries are included in SYSLIB concatenations for copybook libraries. Members in Like-Copy libraries are analyzed for Impact Analysis CPY relationships.

Like-Load - Components in Like-Load libraries are assumed to be the product of a stage procedure performed on a Like-Source component. Like-Load libraries are included in SYSLIB concatenations for load libraries. Members in Like-Load libraries are analyzed for Impact Analysis LOD relationships.

Like-PDS -Components in Like-PDS library types are not processed through a procedure by stage. Like-PDS libraries are not included in SYSLIB concatenations for copybook or load libraries. Members in Like-PDS libraries are not analyzed for Impact Analysis relationships.

Like-Other - If you leave the LIKE field blank in a Library Type Definition, the type is referred to as “Like-Other”. Components in Like-Other library types are staged through a batch job created from an ISPF skeleton named CMN$$xxx where xxx is the Like-Other library type. You must code Like-Other skeletons from a model named CMN$$OTH delivered from SERENA. Like-other libraries are not analyzed for Impact Analysis relationships.

Like-Other components are not analyzed by Audit.

DEFER Y

N

Defer allocation of the staging library for this types until the fist component of the type is staged or checked out.

Allocate the stage library for this type when the change package is created, even though there may never be any members of this library type in the package.

TARGET TYPE Type a Like-Load target library type for each Like-Source library type.

SELECTABLE OPTION

Use this field to associate a library type with a ChangeMan ZMF selectable option that you have licensed. The behavior of the library type may require further definition in administration panels or ISPF skeletons.

A

D

I

APS Option

DB2 Option

IMS Option

Field Description

76


a) To add a library type, type I (Insert) in the line command above where you want to insert the library type and press ENTER. An empty library type entry is inserted on the panel.

b) To delete a library type, type D (Delete) in the line command for the library type and press ENTER.

2. For each library type on the Global Library Types Part 1 of 2 panel, you must complete a second panel of information. Type S in the line command for a library type and press ENTER. The Global Library Types Part 2 of 2 panel is displayed. The first time you access this panel for a library type, the panel is empty:

CMNCGLT1 -------------- GLOBAL LIBRARY TYPES PART 2 OF 2 -------------------- COMMAND ===> LIBRARY TYPE: CPY - Copybooks LIKE VALUE: C DEFER VALUE: Y STAGING DATASET ATTRIBUTES: GENERIC UNIT NAME ===> (Generic group name or unit) VOLUME SERIAL ===> (Required if GENERIC UNIT unspecified) SPACE UNITS ===> (TRK, CYL or BLK) PRIMARY QUANTITY ===> (In above units) SECONDARY QUANTITY ===> (In above units) DIRECTORY BLOCKS ===> RECORD FORMAT ===> RECORD LENGTH ===> BLOCK SIZE ===> DATA SET TYPE ===> (LIBRARY for PDSE, PDS for pds, or blank) OTHER OPTIONS: CHECKOUT COMPONENT DESCRIPTION ===> NO (Y/N) CHECKOUT COMPONENT ACTIVITY FILE ===> NO (Y/N) COMPONENT ACTIVITY FILE TYPE ===> SAVE STAGING VERSIONS ===> (YES/NO/OPT) Press ENTER to process; Enter END command to exit.

77


After you have entered information on the Global Library Types Part 2 of 2 panel, it might look like this.

The following table describes the fields on the Global Library Types Part 2 of 2 panel.

Field Description

GENERIC UNIT NAME

Type the DASD generic group or unit device name to be used for allocating staging libraries for this library type. This field may be left blank if the VOLUME SERIAL field is used.

VOLUME SERIAL Type the DASD volume serial number where stage libraries are to be allocated for this library type. This field may be left blank if the GENERIC UNIT NAME field is used.

SPACE UNITS Type the units to be used for the primary and secondary space allocations for staging libraries for this library type.

TRK

CYL

BLK

Allocate space in tracks.

Allocate space in cylinders.

Allocate space in blocks.

PRIMARY QUANTITY

SECONDARY QUANTITY

DIRECTORY BLOCKS

Type the primary space, secondary space, and directory block allocation to be used for the staging libraries for this library type.

Use the MINIMUM space allocations, especially the PRIMARY QUANTITY. ChangeMan ZMF dynamically reallocates stage libraries if extents or directory blocks are exhausted as the change package grows.

Unused space in PDS stage libraries is freed when the change package is frozen. ChangeMan ZMF does not automatically compress stage libraries, but you can compress stage libraries for a package with the ZP Package List command.

CMNCGLT1 -------------- GLOBAL LIBRARY TYPES PART 2 OF 2 ---------------------- COMMAND ===> LIBRARY TYPE: CPY - Copybooks LIKE VALUE: C DEFER VALUE: Y STAGING DATASET ATTRIBUTES: GENERIC UNIT NAME ===> 3390 (Generic group name or unit) VOLUME SERIAL ===> (Required if GENERIC UNIT unspecified) SPACE UNITS ===> TRK (TRK, CYL or BLK) PRIMARY QUANTITY ===> 1 (In above units) SECONDARY QUANTITY ===> 1 (In above units) DIRECTORY BLOCKS ===> 5 RECORD FORMAT ===> FB RECORD LENGTH ===> 80 BLOCK SIZE ===> 0 DATA SET TYPE ===> PDS (LIBRARY for PDSE, PDS for pds, or blank) OTHER OPTIONS: CHECKOUT COMPONENT DESCRIPTION ===> NO (Y/N) CHECKOUT COMPONENT ACTIVITY FILE ===> NO (Y/N) COMPONENT ACTIVITY FILE TYPE ===> SAVE STAGING VERSIONS ===> NO (YES/NO/OPT) Press ENTER to process; Enter END command to exit.

78


RECORD FORMAT Type the staging library record format for this library type. Valid values include:

F, FA, FB, FBA, FBM, FM, FS, V, VA, VB, VBA, VBM, VM, U

Legend:

F - Fixed length recordsV - Variable length recordsU - Undefined format recordsB - Blocked recordsS - Standard blocksA - ASA printer control charactersM - Machine code printer control characters

RECORD LENGTH Type the logical record length for components in this library type.

BLOCK SIZE Type the staging library block size for this library type.

You may enter 0 to let SMS calculate the best block size for the storage device.

DATA SET TYPE Type LIBRARY for PDSE stage libraries. Leave the field blank or type PDS for PDS stage libraries.

CHECKOUT COMPONENT DESCRIPTION

YES

NO

Copy the Component General Description from the Package Master to the change package when a component is checked out. Allow developers to create or update the Component General Description through a change package.

Do not copy the Component General Description from the Package Master to the change package when a component is checked out. Prevent developers from creating or updating the Component General Description in a change package.

The Component General Description can always be created or updated through Application Administration.

CHECKOUT COMPONENT ACTIVITY FILE

YES

NO

Automatically checkout a second component with the same name in a second library type when you checkout a component in this library type.

The second library type specified below in the COMPONENT ACTIVITY FILE TYPE field. The second library type is called a “Component Activity File” here, but it can be any like-PDS library type defined to this application.

If you check out a component to a personal library, the Activity File is checked out to the staging library. If there is no Activity File member with the same name in baseline, you must create one (stage from development) in your package. If there is no matching Activity File member, Audit flags a SYNCH6!

Checkout components in this type without checking out a second component with the same name in another library type.

COMPONENT ACTIVITY FILE TYPE

Type the library type of the Component Activity File. This field is only required if YES is specified in the CHECKOUT COMPONENT ACTIVITY FILE field.

Field Description

79


3. When you are finished updating fields on the Global Library Type Part 2 of 2 panel, press ENTER to return to the Global Library Types 1 of 2 panel.

4. When you are finished updating library type definitions on the Global Library Type Part 1 of 2 panel, press PF-3 or type END and press ENTER to store the application library type definitions in the ChangeMan ZMF Package Master File.

DEFINING THE LANGUAGES

You provide ChangeMan ZMF with all of the language names available in this environment. ChangeMan ZMF can still process component types if source and like source language types are not defined here, but when you define them, users are able to reference these component types by language. The Application Administrators select from this list when individual applications are set up. This information can also be used as a selection list from within the global options whenever necessary.

To define the languages, take the following steps:

1. Select option 3 on the Global Administration Options panel. The Global Language Names panel (CMNGGLNG) is displayed:

SAVE STAGING VERSIONS

Restricts how the application library type can be defined to save a previous version in a staging library before it is overlaid by a new version from edit-in-stage, checkout, or stage from development. See “Staging Versions” on page 49

YES

NO

OPT

The application library type must always be defined to save staging versions.

The application library type can never be defined to save staging versions.

The application administrator can define the library type to always save staging versions, never save staging versions, or prompt the developer to make a choice.

Field Description

CMNGGLNG ------------------- GLOBAL LANGUAGE NAMES ----------------------------COMMAND ===> SCROLL ===> CSR

Enter END command to save changes or CANCEL to exit.

LANGUAGE'''' COBOL2__'''' COBOL __'''' ASM __'''' PLI __

80


2. Define a standard language or update an existing standard language on the panel. The standard language names you define is associated with the language assumption feature of ChangeMan ZMF. This feature assists users who neglect to explicitly define the language type of a source or like-source component type that they stage. The language assumption feature searches the code of the staged component, matches its language name to the standard language names you define, and names it.

3. Type END to save your entry.

DEFINING THE COMPILING PROCEDURES This option is used to enter all the different procedures that are needed to compile and link source components. This information is displayed for selection during any application level change package staging. Thus, it must include all of the procedures for change installation of all applications.

Even if your application does not contain any source components, you must enter a compile procedure.

To define the compiling procedures, take the following steps.

1. Select option 4 from the Global Administration Options panel. The Compile Procedure List panel (CMNPRCNM) is displayed:

This panel lists all of the pre-defined compiling procedures. Skeletons for these procedures must exist in the custom skeletons library (see Serena™ ChangeMan® ZMF Skeleton Reference for details).

2. Create or update the rows of the list, and type END to save your changes. The following table describes the fields of the panel.

Column Description

LANGUAGE Enter the language name for the compile procedure. If you want to select from a list of available language names, enter *. The Language Name Selection List is displayed.

CMNPRCNM ------------------- COMPILE PROCEDURE LIST ---------------------------COMMAND ===> SCROLL ===> CSR


Enter * in LANGUAGE or PROCEDURE fields for selection list.

LANGUAGE PROCEDURE DESCRIPTION'''' COBOL2__ ________ _____________________________________________

81


DEFINING REASON CODES

This option is used to enter all available reason codes and descriptions for unplanned permanent or temporary change packages. When creating this change package, the user must choose a code from the Reason Code List.

To define reason codes, take the following steps

1. Select option 5 on the Global Administration Options panel. The Reason Code List panel (CMNRSNCD) is displayed:

2. Create or update the rows of the list, and type the END command to save your changes. The following tables describes the field on the Reason Code List panel.

PROCEDURE Enter the procedure name. If you want to select from a list of procedure names, enter *.

You cannot use a numeric or special character in the fourth position of the procedure name.

DESCRIPTION Enter the procedure description, which can be up to 44 alphanumeric characters.

Column Description

CODE Enter the reason code in alphanumeric format, for example, E01 or 01E.

REASON DESCRIPTION

Enter the reason description with a maximum of 44 alphanumeric characters.

Column Description

CMNRSNCD ---------------------- REASON CODE LIST ------------------------------COMMAND ===> SCROLL ===> CSR


CODE DESCRIPTION'''' 004 User error__________________________________

82


DEFINING SITES

A site specifies target information for a promotion process or an install process. A site may be local or remote.

You must define a site for each production ChangeMan ZMF environment that is a target for installs. Every promotion level definition must be associated with a site.

Perform the following steps to define a site:

1. On the Global Administration Options panel, select option 6. The Global Site List Part 1 of 2 panel is displayed. The first time you access this panel to define global sites, the panel is empty:

Local Site A target that is on the same LPAR as the development ChangeMan ZMF instance.

A target on a different LPAR from the ChangeMan ZMF instance can be defined as a local site if it shares DASD and catalogs with the ChangeMan ZMF development LPAR, and no DB2 binds are required.

Remote Site A target that is on a different LPAR than the development ChangeMan ZMF. instance that does not share DASD and catalogs, or that requires DB2 binds.

CMNGRST1 ---------------- GLOBAL SITE LIST PART 1 OF 2 ----- Row 1 to 12 of 12 COMMAND ===> SCROLL ===> HALF Enter END command to save changes or CANCEL to exit. SITE NAME '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ ******************************* Bottom of data ********************************

83


After you have entered site names on the Global Site List Part 1 of 2 panel, it might look like this.

The following table describes the fields on the Global Site List panel.

The order of site names on the Global Site List Part 1 of 2 panel is not significant.

a) To insert a new site, type I (Insert) in the command line above the point where you want the new site to appear and press ENTER. An empty site definition line is inserted.

b) To delete an existing site, type D (Delete) in the line command for the site you want to delete and press ENTER.

2. For each site on the Global Site List Part 1 of 2 panel, you must complete a second panel of information. Type S in the line command for the site and press ENTER.

Field Description

SITE NAME Type a nickname for a promotion or install target. The site name must begin with an alphabetic character.

Site names should convey the purpose of the site in the context of promotion and/or install. Developers pick install site names from a list when they create a package, and they pick a promotion site name from a list when they promote their package.

CMNGRST1 ---------------- GLOBAL SITE LIST PART 1 OF 2 ------- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> HALF Enter END command to save changes or CANCEL to exit. SITE NAME '''' Q510DP__ '''' N510DP__ '''' LOCAL01_ ******************************* Bottom of data ********************************

84


a) If the ChangeMan ZMF instance you are using to make this update is an A (All) environment, the Site Definition Part 2 of 2 panel is displayed:

b) If the ChangeMan ZMF instance you are using to make this update is DP (Development/Production) environment, the Site Information Part 2 of 2 panel is displayed:

CMNGPRST --------- N510DP SITE DEFINITION - PART 2 OF 2 ----------------------- COMMAND ===> LOGICAL UNIT/SYSTEM NAME ===> DEFAULT UNIT NAME ===> (Generic disk unit) DEFAULT VOLUME SERIAL ===> PRD STAGING MODEL DSNAME ===> ????.CMNSTAGE.####### TRANSMISSION VEHICLE ===> (IEBCOPY or Other) SITE JOB STATEMENT INFORMATION: SITE JOB STATEMENT INFORMATION: ===> //CMNSTART JOB ,ACCOUNT INFORMATION,____________________________________ ===> // CLASS=?,MSGCLASS=?_______________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.

CMNGRST2 --------- Q510DP SITE INFORMATION - PART 2 OF 2 ---------------------- COMMAND ===> CHANGE MAN SUBSYSTEM ID ===> LOGICAL UNIT/SYSTEM NAME ===> DEFAULT UNIT NAME ===> (Generic disk unit) DEFAULT VOLUME SERIAL ===> CHANGE MAN DELAY FILE ===> PRD STAGING MODEL DSNAME ===> ????.CMNSTAGE.####### TRANSMISSION VEHICLE ===> (IEBCOPY or Other) TIME DIFFERENCE ===> (+/-HHMM) SITE JOB STATEMENT INFORMATION: ===> //CMNSTART JOB ,ACCOUNT INFORMATION,____________________________________ ===> // CLASS=?,MSGCLASS=?_______________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.

85


The first time you access either of these panels, the fields are mostly blank. After you have entered site information on the Site Information Part 2 of 2 panel, it might look like this.:

The following table describes the fields on these panels.

Field Description

CHANGEMAN SUBSYSTEM ID

Type the subsystem ID of the target ChangeMan ZMF instance for this site.

Not required in an A environment, and not displayed on the panel.

LOGICAL UNIT/SYSTEM NAME

If you are defining a local site, type the LOGICAL UNIT OR SYSTEM NAME used in Global Administration Parameters.

If you are defining a remote site, type the logical unit or system name (SMF ID) that is used by your transmission software to locate the target site.

DEFAULT UNIT NAME

Type the generic unit name for DASD to be used for dynamic allocations at the target site. This field may be left blank if DEFAULT VOLUME SERIAL is used.


Type the DASD volume serial number to be used for dynamic allocations at the target site. This field may be left blank if DEFAULT UNIT NAME is used.

CHANGEMAN DELAY FILE

Type the fully qualified data set name (no quotes) for the VSAM Delay file at the target site. (Not required for A environments.)

PRD STAGING MODEL DSNAME

If you are defining a local site, type the DEV MODEL DSNAME from Global Administration Parameters.

If you are defining a remote site, type the model data set name for staging libraries at the target site.

Four question marks (????) in the data set name are replaced by the appropriate application mnemonic. Seven pound signs (#######) are replaced by the change package number.

Not required in an A environment, and not displayed on the panel.

CMNGRST2 ---------- Q510DP SITE INFORMATION - PART 2 OF 2 --------------------- COMMAND ===> CHANGE MAN SUBSYSTEM ID ===> A LOGICAL UNIT/SYSTEM NAME ===> QREMOTE DEFAULT UNIT NAME ===> SYSDA (Generic disk unit) DEFAULT VOLUME SERIAL ===> CHANGE MAN DELAY FILE ===> PROD142.PROFSERV.CMN510N.CMNDELAY PRD STAGING MODEL DSNAME ===> PROD99.CMN.QREMOTE.????.####### TRANSMISSION VEHICLE ===> IEBCOPY (IEBCOPY or Other) TIME DIFFERENCE ===> -0100 (+/-HHMM) SITE JOB STATEMENT INFORMATION: ===> //CMNSTAR JOB (X170,374),'GLOBAL Q510DP SITE',_________________________ ===> // CLASS=A,MSGCLASS=9______________________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.

86


3. When you are finished updating fields on the Site Definition Part 1 of 2 panel, press ENTER to return to the Global Site List Part 1 of 2 panel.

4. When you are finished updating site definitions on the Global Site List Part 1 of 2 panel, press PF-3 or type END and press ENTER to store the site definitions in the ChangeMan ZMF Package Master file.

LOCKING OR UNLOCKING APPLICATION DEFINITIONS

As the Global Administrator, you can lock or unlock application definitions with the Lock/Unlock Applications panel. When an application is locked, the Application Administration Options cannot be used to update the application definition, and application administration panels are displayed in browse mode.

The only functions an application administrator can execute when an application is locked are:

• Update the Global Notification File if that function is allowed by the global administration parameters.

• Submit reports from the Report Selection List panel.

• Submit the Baseline Analyzer Report and the Link Date Report.

Application Administration Options also display in browse mode when another administrator is updating an application. If that administrator’s session is interrupted, the application status may display IN USE, even through no one is currently updating the application. The Global Administrator must unlock the application to make the application definition available for update.

To lock, unlock, or reset an application definition:

1. On the Primary Option Menu, select option A and press Enter. The Administration Options panel is displayed.


If you are defining a local site, type IEBCOPY.

If you are defining a remote site, type OTHER to include transmission steps in promote JCL or install JCL.

TIME DIFFERENCE

Type the difference in system clock time between this site and the development site where change packages are created.

Enter a positive time difference in hours and minutes (+hhmm) if this site is to the east of the development site. Enter a negative time difference (-hhmm) if this site is to the west of the development site. The default time difference is +0000.

The time difference parameter is used to verify that the package install date and time that you enter when you create a package is a time that has not already passed at a remote site.

SITE JOB CARD INFORMATION

Enter the default job card to be used at the target site.

Field Description

87


2. On the Administration Options panel, select option G and press Enter. The Global Administration Options menu is displayed.

3. On the Global Administration Options panel, select option 7 and press Enter. The Lock/Unlock Applications panel is displayed:

The following table describes the fields on the Lock/Unlock Applications panel.

Field Description

Line Command Type a line command to change the application status.

L

U

R

Lock the application to prohibit changes to application administration.

Unlock the application to allow changes to application administration.

Reset the “in use” indicator.

APPL Displays application mnemonics defined to ChangeMan ZMF.

DESCRIPTION Displays the application descriptions.

STATUS Indicates if the application is available for update.

LOCKED

UNLOCKED

IN USE

RESET

Blank

The Global Administrator has locked the application. Application administration cannot be changed until the Global Administrator unlocks the application. Application administration panels are displayed in browse mode.

The Global Administrator has just unlocked the application. Application administration is available for update.

Another administrator is currently updating application administration. Application administration panels are displayed in browse mode.

The Global Administrator has just reset the “in use” indicator. Application administration is available for update.

Application administration is available for update.

CMNGBULP ------------------ LOCK/UNLOCK/RESET IN USE --------- Row 1 to 6 of 6 COMMAND ===> SCROLL ===> PAGE Enter L (lock), U (Unlock) or R (Reset in use flag). APPL DESCRIPTION STATUS _ APS QA DP Test Application _ BET QA DP Test Application LOCKED _ CCW Ulrica’s Test QA system _ DAM1 Don’s test application IN USE _ DEMO DEMO APPL MAY BE DELETED AND REDEFINED _ T510 Test v510 application for use by all LOCKED ******************************* Bottom of data ********************************

88


4. On the Lock/Unlock Applications panel, type L (lock), U (unlock), or R (Reset) in the line command for an application and press Enter. The STATUS field is updated to LOCKED, UNLOCKED, or RESET. Application availability is changed immediately.

5. Press PF-3, or type END on the Command line and press Enter to exit the Lock/Unlock Applications panel. You cannot “CANCEL” changes you made.

SETTING THE PLANNED INSTALLATION CALENDAR

The Planned Installation Calendar limits the number of planned packages that may be scheduled for install on the same calendar day. This restriction does not apply to unplanned packages.

To update the Planned Installation Calendar, perform the following steps:

1. On the Global Administration Options panel, type D and press ENTER.

2. If the ChangeMan ZMF instance you are using to make this update is an A (All) environment, the Planned Installation Calendar panel is displayed immediately. This panel is described in step 3c below.

3. If the ChangeMan ZMF instance you are using to make this update is not an A (All) environment, the Calendar Options panel is displayed:

a) On the Calendar Options panel, type 2 and press ENTER, and the Planned Installation Calendar panel shows in display mode. This panels displays the total number of installs that may be scheduled across all sites and the total number of installs that have already been scheduled. The # and MAX numbers displayed for each day on this panel represent the sum of the # and MAX numbers for all sites.

b) On the Calendar Options panel, type 1 and press ENTER, and the Site Selection List panel is displayed:

CMNCLDOM ---------------------- CALENDAR OPTIONS ------------------------------ OPTION ===> 1 Site - Display or update installation calendar by site 2 Composite - Display a composite installation calendar Press ENTER to process; Enter END command to exit.

CMNRMTSL --------------- DEMO - SITE SELECTION LIST ---------- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> HALF SITE NAME _ Q510DP _ N510DP _ LOCAL01

89


c) On the Site Selection List panel, type S on the line command for a site name and press ENTER. The Planned Installation Calendar panel is displayed:

The following table describes the fields on the Planned Installation Calendar panel.

Field Description

STARTING DATE This is the calendar date for the first day in the row. Each row displays seven days. The Starting Date will be the day before the current system date to include packages scheduled for install on the prior calendar date due to a negative Time Difference specified in the Site definition in Global Administration.

# Displays the total number of packages scheduled for installed on that day at this site.

MAX A data entry field for the maximum number of planned packages that may be scheduled for install on that day for this site.

The maximums are initially set to zero for all dates.

To reset MAX for all dates. type SETALL nnn on the command line. To set MAX for a all occurrences of a day of the week, enter SETddd nnn (example: SETMON 123). To reset the MAX for one date, over typing the MAX number for that day.

To block scheduling installs for any planned packages on a given date, leave MAX at zero for that day.

To set MAX to an unlimited number of unplanned packages for all days or for a specific day, type SETALL 255 or SETddd 255 on the command line. The value of the maximum number of planned packages is displayed as UNL.

Note: If a site was created only for promotion to a local site, leave MAX set to zero for all dates.

TOTALS # Displays the total number of packages scheduled for instal in that week at this site.

TOTALS MAX Displays the maximum number of planned packages that may be scheduled for install in that week at this site.

The # and TOTALS # fields are automatically incremented when change packages are created. These fields are automatically decremented when change packages are rescheduled or installed.

CMNCLNDR ----------- PLANNED INSTALLATION CALENDAR -------- CALENDAR UPDATED Press ENTER to update calendar or END command to exit. STARTING MON TUE WED THU FRI SAT SUN TOTALS DATE # MAX # MAX # MAX # MAX # MAX # MAX # MAX # MAX 2000/04/10 000 022 000 022 000 022 000 022 000 022 000 022 000 022 0000 0154 2000/04/17 000 022 000 022 000 022 000 022 000 022 000 022 000 022 0000 0154 2000/04/24 000 022 000 022 000 022 002 022 001 022 000 022 001 022 0004 0154 2000/05/01 000 022 000 022 000 022 000 022 000 022 000 022 000 022 0000 0154 2000/05/08 000 022 000 022 000 022 000 022 000 022 000 022 000 022 0000 0154 2000/05/15 000 022 000 022 000 022 000 022 000 022 000 022 000 022 0000 0154

90


CREATING OR UPDATING THE GLOBAL NOTIFICATION FILE

Administrators use the Global Notification facility to pass information to ChangeMan ZMF users. You can use this facility to inform users about:

• Scheduled down time.

• Scheduled maintenance changes to ChangeMan ZMF.

• Work-arounds for recently discovered problems.

• Upcoming ChangeMan ZMF education or discussion sessions.

When a user connects to ChangeMan ZMF after an administrator updates the Global Notification File, this ISPF short message is displayed in the upper right corner of the Primary Option Menu: “NOTIFICATION UPDATED”. If the user presses PF1, this long message is displayed:

CMN1116I - Option-N file last updated 07/15/2002 13:57 last read 07/14/2002

The short message persists on the Primary Option Menu until the user selects option N (Notify) to display the Global Notification File.

The global administrator allocates the Global Notification File and enables the Global Notification Facility. Global administrators update the file with information for users, and they can grant application administrators the same privilege.

Enabling the Global Notification Facility

Follow these steps to allocate a Global Notification File and enable the Global Notification Facility.

BROWSE WSER239.WSER239.D197B7EF.T36A5D91.OUTLIST Line 00000000 Col 001 080 Command ===> Scroll ===> HALF ********************************* Top of Data ********************************** Notification Date: 07/15/2002 ChangeMan ZMF will be unavailable between 0600 and 0700 on Sunday July 20 when Maintenance Package 58 will be applied. See the ChangeMan page on the Intranet for a description of the changes that will be made. ------------------------------------------------------------------------ Notification Date: 06/10/2002 ChangeMan ZMF will be unavailable between 0600 and 0700 on Sunday June 16 when Main ten ace Package 57 will be applied. See the ChangeMan page on the Intranet for a description of the changes that will be made. ******************************** Bottom of Data ********************************

91


1. Outside of ChangeMan ZMF, allocate a permanent Global Notification File as a partitioned or sequential data set. Use any of these file characteristics:

Serena recommends that you allocate a small sequential file with a fixed record length of 80 bytes. A single track of 3390 equivalent disk has room for over 600 lines of notification messages.

If you allocate a PDS, ChangeMan ZMF will reallocate the library if it ever runs out of extents or directory space. However, the trade-off is that a PDS accumulates unusable space and should be compressed periodically.

Note If you allocate the Global Notification File as a PDS, create a member in the library with at least one (blank) record. When you specify the data set name in global administration parameters below, use the fully qualified PDS member name.

2. In your security system, grant the SERNET instance userid UPDATE access to the file you allocated. (Grant ALTER access if you allocated a PDS so ChangeMan ZMF can reallocate this library.) Administrators and users do not need access granted in your security system because they access the file through ChangeMan ZMF.

3. From the Global Administration Options panel (CMNGAMEN), select option 1. The Global Parameters Part 1 of 6 panel (CMNGGP01) is displayed.

4. Press Enter. The Global Parameters Part 2 of 6 panel (CMNGGP02) is displayed.

5. On the Global Parameters Part 2 of 6 panel (CMNGGP02), enter information to define the Global Notification Facility.

a) In the Use Global Notification File field, type Yes.

b) In the Allow Application Update To File field, type Yes if you want application administrators to update the Global Notification File that is displayed to all ChangeMan ZMF users.

c) In the Global Notification File field, type the data set name of the file you allocated.

6. Press Enter continuously until you are returned to the Global Administration Options panel (CMNGAMEN)

Creating Global Notification Messages

Follow these steps to create your first Global Notification message for ChangeMan ZMF users.

Data Set Organization DSORG=PS or PO

Record Format RECFM=FB, FBM, FBA, VB, VBM, or VBA

Logical Record Length LRECL maximum 256

92


1. From the Global Administration Options panel (CMNGAMEN), select option N. An ISPF edit session is opened for an empty ChangeMan ZMF temporary file.

2. Using ISPF functions, edit the temporary file to create the message that you want ChangeMan ZMF users to see.

3. Press PF3 to exit the edit session. ChangeMan ZMF copies the temporary file back to the Global Notification File. Type Cancel to exit the edit session without saving your entries.

Updating the Global Notification Message

Follow these steps to update the Global Notification File with new messages for ChangeMan ZMF users.

ISREDDE2 WSER239.WSER239.D197B7EF.T3A87376.OUTLIST Columns 00001 00072 Command ===> Scroll ===> HALF ****** ***************************** Top of Data ****************************** ==MSG> -Warning- The UNDO command is not available until you change ==MSG> your edit profile using the command RECOVERY ON. '''''' '''''' '''''' '''''' '''''' '''''' '''''' '''''' '''''' '''''' '''''' '''''' '''''' ****** **************************** Bottom of Data ****************************

ISREDDE2 WSER239.WSER239.D197B7EF.T3ADCD39.OUTLIST Columns 00001 00072 Command ===> Scroll ===> HALF ****** ***************************** Top of Data ****************************** ==MSG> -Warning- The UNDO command is not available until you change ==MSG> your edit profile using the command RECOVERY ON. 000001 000002 Notification Date: 06/10/2002 000003 000004 ChangeMan ZMF will be unavailable between 0600 and 0700 on Sunday June 000005 16 when Maintenance Package 57 will be applied. See the ChangeMan page on 000006 the Intranet for a description of the changes that will be made. 000007 ****** **************************** Bottom of Data ****************************

93


1. From the Global Administration Options panel (CMNGAMEN), select option N. An ISPF edit session is opened for a ChangeMan ZMF temporary file that contains the current contents of the Global Notification File.

Note If the global administrator specified Yes In the Allow Application Update To File field, you can access this function from the Application Administration Functions panel (CMNLAMEN).

2. Using ISPF functions, insert lines to type new a new message that you want displayed to all ChangeMan ZMF users. Add new messages at the top of the file.


ISREDDE2 WSER239.WSER239.D197B7EF.T3BEC7B8.OUTLIST Columns 00001 00072 Command ===> Scroll ===> HALF ****** ***************************** Top of Data ****************************** ==MSG> -Warning- The UNDO command is not available until you change ==MSG> your edit profile using the command RECOVERY ON. 000001 000002 Notification Date: 06/10/2002 000003 000004 ChangeMan ZMF will be unavailable between 0600 and 0700 on Sunday June 000005 16 when Maintenance Package 57 will be applied. See the ChangeMan page on 000006 the Intranet for a description of the changes that will be made. 000007 ****** **************************** Bottom of Data ****************************

ISREDDE2 WSER239.WSER239.D197B7EF.T3C3AE58.OUTLIST Data set copied Command ===> Scroll ===> HALF ****** ***************************** Top of Data ****************************** ==MSG> -Warning- The UNDO command is not available until you change ==MSG> your edit profile using the command RECOVERY ON. 000001 000002 Notification Date: 07/15/2002 000003 000004 ChangeMan ZMF will be unavailable between 0600 and 0700 on Sunday July 000005 20 when Maintenance Package 58 will be applied. See the ChangeMan page on 000006 the Intranet for a description of the changes that will be made. 000007 000008 ------------------------------------------------------------------------ 000009 000010 Notification Date: 06/10/2002 000011 000012 ChangeMan ZMF will be unavailable between 0600 and 0700 on Sunday June 000013 16 when Maintenance Package 57 will be applied. See the ChangeMan page on 000014 the Intranet for a description of the changes that will be made. 000015 ****** **************************** Bottom of Data ****************************

94


ACCESSING THE GLOBAL SELECTABLE OPTIONS The Global Administrator can access the various selectable options that have been acquired for this data center.

Access the Global Selectable Options.

1. Select option O on the Global Administration Options panel. The Global Selectable Options panel is displayed.

• The highlighting of this panel differs depending on which options your site has installed.

• If no selectable options have been purchased by your data center, no options are listed.

2. Select the number for the option that you want to view and press ENTER. A Global Selectable Options panel (CMNGBSOP) similar to the following is displayed:

The following table lists each possible options and a brief description of it. For complete details about using the option, see the individual ChangeMan ZMF option manuals.

Option Description

APS Lets you checkout and stage APS and non-APS entities as ChangeMan ZMF components.

DB2 Maintain DB2 programs, DB2 Data Request Components (DBRMs), and DB2 plans.

INFO Administration panels related to ServiceDesk/390, the IBM Information Management (INFO/MAN) interface.

OFM This option enables you to create and utilize customized forms as panels within ChangeMan ZMF. Full support of the mechanisms for completing, submitting, and approving forms within a change package is provided together with a notification facility to inform approvers when a form is submitted for their approval.

IMS This option allows you to define IMS control regions and library sub-type information for ChangeMan ZMF implementation.

CMNGBSOP ----------------- GLOBAL SELECTABLE OPTIONS --------------------------OPTION ===> 1 APS - Change Man APS administrative functions 2 DB2 - Maintain DB2 information 3 INFO - Specify Info/Management change rule 4 OFM - Configure Online Forms Manager 5 IMS - IMS Control Region IDs, and Library Sub-Type information Press ENTER to process; Enter END command to exit.

95


USING PACKAGE USER RECORDS

ChangeMan ZMF allows sites to store user data in a Package Master record associated with a given package. In Version 4.1.6, this was done with the CMNEX100 user exit. Now, under ChangeMan ZMF 5.3, this is done with a Global Option. It is enabled by turning on “Display Package User Option panel(s)” in Global Administration. When this option is turned on, Package User panels are available at create, update, and query time. These two modifiable panels (CMNDPUP1 and CMNDPUP2) are in the main panel library. As administrator, you can customize these panels to allow the user to store data in the Package User Record. There are currently the following variables available to you:

USR0101 - USR0115 1 byteUSR0201 - USR0211 2 bytesUSR0301 - USR0310 3 bytesUSR0401 - USR0410 4 bytesUSR0801 - USR0810 8 bytesUSR1601 - USR1605 16 bytesUSR4401 - USR4405 44 bytesUSR7201 - USR7205 72 bytes

Please note that USR0199 is reserved for internal use as an indicator for the second panel display. This must be included on the first panel. You can only use the variables listed above. Any others you put on the panel are not stored in the Package Master file.

Package User records can be edited via the update function of the Build menu (option ‘E’), or from the package list using the ‘UE’ line command. Only character data can be stored in these fields. This data is available to the same user exits that the old CMNEX100 data was, specifically: CMNEX002, CMNEX003, CMNEX009, CMNEX023, and CMNEX024. In the assembler code for the exits, the naming convention IXP$* is used, with ‘*’ indicating the numeric portion of the above variable names.

Note: You must run conversion utility CMNRFMT to make data stored under Version 4 exit program CMNEX100 available as Package User Data under Version 5. See the Serena™ ChangeMan® ZMF Migration Guide.

96


97

SETTING UP APPLICATION ADMINISTRATION 5

This chapter explains how to set up and change administration for ChangeMan ZMF applications. Entries in application administration define the rules for managing the change lifecycle in each application.

HOW GLOBAL SETTINGS AFFECT APPLICATION SETTINGS

Application fields can only be configured within the scope of the corresponding global fields. For example, if the Global Administrator restricted a particular field to NO at the global level, you cannot change the field definition to YES at the application level. The same applies to other types of fields (besides YES or NO). For example, if the staging restriction level in the global parameters is set to 3 (the most restrictive level), the staging restriction level at the application level cannot be 1 or 2; it must be a 3. However, if the staging restriction level at the global level is set to 1, then the staging parameter at the application level can be set to 1, 2, or 3.

The following recommendations may help you set the application variables.

• Choose a three or four-character mnemonic that identifies the application. CMNEX004 controls the mnemonics you can use.

• Gather the actual library names for Baseline, Production, Temporary, Backup, and Development.

• Decide which library types will be used by all applications, maintained in Baseline, and installed into Production.

• Determine the average space allocation needed for an update to the application (We recommend space in terms of tracks and at least 20 directory blocks.).

ACCESSING APPLICATION ADMINISTRATION

Follow these steps to access application administration options.

98

Chapter 5: Setting Up Application Administration

1. On the Primary Option Menu, type A and press ENTER. The Administration Options panel is displayed:

2. On the Administration Options panel, type A and press ENTER. The Application Administration Options panel is displayed:

Creating a New Application

Perform these steps to create a new application.

1. On the Application Administrative Options panel, type the mnemonic for the new application in the APPLICATION field. The application mnemonic must be three or four characters long, and the first character of the mnemonic must be alphabetic or national (@ $ #).

2. Type 1 on the Option line and press ENTER. The Application Parameters Part 1 of 3 panel is displayed. You must start on this panel to define a new application.

Note Your security administrator must add the application mnemonic to the resource class and grant you UPDATE access before you can create the application in ChangeMan ZMF. See “Pre-Implementation Decisions” on page 25.


CMNLAMEN ------------- APPLICATION ADMINISTRATION OPTIONS --------------------- OPTION ===> APPLICATION ===> DEMO (Blank for list) 1 Parms - Generate application parameters 2 Library - Generate library types 3 Language - Generate language names 4 Procedures - Generate compiling procedures 5 Pln Approvals - Create planned approval list 6 Upl Approvals - Create unplanned approval list 7 Promotion - Configure promotion libraries 8 Sites - Configure site information B Baseline - Configure baseline libraries C Component - Update component information, procedures, security D Delete - Delete an application N Notify - Update the Global Notification File O Options - Configure selectable options P Production - Configure production libraries R Reports - Generate application batch reports Press ENTER to process; Enter END command to exit.

99


Updating Existing Applications

There are two ways to access an existing application for update:

Single Application

1. On the Application Administration Options panel, type the application mnemonic in the APPLICATION field.

2. Type one of the administration options on the Option line, and press ENTER. The first panel for that option is displayed.

Application List

1. On the Application Administration Options panel, leave the APPLICATION field blank, leave the Option line blank, and press ENTER. The Application List panel is displayed:

The following table describes the fields on the Application List panel.

Field Description

Line Command Type a one-character application administration option listed at the top of the panel.

APPL Displays application mnemonics defined to ChangeMan ZMF.

DESCRIPTION Displays the application descriptions.

HIGHEST # Displays the number of change packages that have been created in an application since the application was first defined.

CMNPLST2 ---------------------- APPLICATION LIST ------------- Row 1 to 5 of 5 COMMAND ===> SCROLL ===> PAGE LINE COMMANDS: 1-Gen Parms 2-Libraries 3-Language 4-Procedures 5-Pln. Apprv 6-Unp. Apprv 7-Promotion 8-Sites B-Baseline C-Component D-Delete N-Notify O-Options P-Production R-Reports APPL DESCRIPTION HIGHEST # STATUS _ $MIK Test application for CMN510 000001 _ IMS1 IMS Application 000009 _ NAVI SCRIPTION ADDED VIA RPC 000155 _ DEMO DEMO APPL MAY BE DELETED AND REDEFINED 000002 LOCKED _ T510 Test v510 application for use by all 000012 IN USE ******************************* Bottom of data ********************************

100


2. On the Application List panel, type an application administration option number in the line command for the application you want to update and press ENTER. The first panel for that option is displayed.

Locks on Application Administration

You cannot update application administration if the application is locked or in use.

• Access to application administration may be locked by the Global Administrator. In this case, the following message is displayed when you select an Application Administration Option:

CMN5175I - Application parameters globally locked for update.

The Global Administrator must unlock the application before you can update the application definition. See “Locking or Unlocking Application Definitions” on page 86

• Another administrator is currently updating the application definition. In this case, the following message is displayed when you select an Application Administration Option:

CMN5176I - Application parameters currently being updated by USER238.

When the other administrator finishes their update, the application definition becomes available for update.

If message CMN5176I displays when no other administrator is updating the application, the Global Administrator must reset the “in use” indicator. “Locking or Unlocking Application Definitions” on page 86

SETTING APPLICATION PARAMETERS

You set and generate your ChangeMan ZMF application parameters from the Application Parameters panels. Many of the application level parameters are a subset of global parameters, but they are tailored for the individual needs of each application's developers. The information you enter during this process is used as a default for change package creation; and in some cases, as boundaries for the change package process. By individually defining each application, you manage the implementation process through ChangeMan ZMF.

STATUS Indicates whether the application is available for update.

LOCKED

IN USE

Blank

The Global Administrator has locked the application. Application administration cannot be changed until the Global Administrator unlocks the application. Application administration panels are displayed in browse mode.

Another administrator is currently updating application administration. Application administration panels are displayed in browse mode.

Application administration is available for update.

Field Description

101


You can think of the parameter generation as a set of rules by which the users are governed. Many of the parameters set in these panels are originally set at the global level. Typically, these global parameters are very liberal, allowing the full spectrum of choice. The individual application level parameters can be more restrictive, tightening down on any sensitive application areas while allowing other applications more latitude.

If the parameter is governed by the Global Administrator's choices for the same parameters a reference back to the global tables has been included.

Note If the Global Administrator restricted any settings at the global level you cannot change the field definition to a less restricted setting at the application level.

1. Select option 1 on the Application Administration Options menu (CMNLAMEN). The Application Parameters Part 1 of 3 panel (CMNGLP01) is displayed:

The following table describes the fields on the panel and the valid information that you can enter on the panel.

Field Description

APPLICATION DESCRIPTION

Enter a 40-character description of this application.

OPTIONAL MODEL TO COPY

Enter the application mnemonic that you want to use as a model for this application's parameters. This is optional if another application has been generated that has many of the same parameters. Use this option to “copy forward” and then modify where needed.

OPTIONAL SKELETON RELEASE ID

Enter the release identifier to be used at this site. If you want to select from a list of available release ID’s, type *. The Release ID (Selection) List is displayed.

CMNGLP01 --------APPLICATION PARAMETERS - PART 1 OF 3 ----------------------- COMMAND ===>

APPLICATION DESCRIPTION ===> OPTIONAL MODEL TO COPY ===> (Clone an application) OPTIONAL SKELETON RELEASE ID ===> (* for list) NORMAL BUSINESS HOURS FROM ===> TO ===> (HHMM) KEEP BASELINE BY SITE ===> (Y/N) ALLOW TEMPORARY PACKAGES ===> (Y/N) AUDIT LEVEL ===> (0,1,2,3,4,5) CHECKOUT ENFORCEMENT RULE ===> (1,2,3) ENTITY CHECK IF RULE 2 ===> ALLOW CONCURRENT CHECKOUT ===> (Y/N) ALLOW CHECKOUT TO PERSONAL LIB. ===> (Y/N) STAGING RESTRICTION LEVEL ===> (1,2,3) ENTITY CHECK IF LEVEL 2 ===> OVERLAY PRIOR STAGED MODULE ===> (Y/N) VALIDATE VERSION DURING STAGING ===> (Y/N) PROMOTION/DEMOTION RULE ===> (0,1,2,3,4)

Press ENTER to continue; Enter END command to exit.

102


NORMAL BUSINESS HOURS

Enter the time range describing the normal business day in military notation (HHMM).

If a user creates an unplanned change package outside of these hours, the package only requires the abbreviated approval list to be promoted or installed.

To always attach an abbreviated approval list for unplanned change packages, enter one minute for the range of your normal business day. For example, enter 0300 to 0301. ChangeMan ZMF always attaches an abbreviated approval list to unplanned change packages except between 3:00 a.m. and 3:01 a.m.

KEEP BASELINE BY SITE

Baseline libraries are maintained for each application.

Enter YES to allow the Development or Development Production site to keep a set of Baseline libraries at that site for each additional site that has been generated within their ChangeMan ZMF system. Use if an application has multiple sites and you want to maintain Baseline libraries at each site.

Enter NO if remote site Baseline libraries are not to be maintained. Only keep a single set of Baseline libraries for the site.

This is the recommended option to choose because it:

• Prevents duplications of DASD

• Makes the maintenance of skeletons easier

• Keeps multiple sites synchronized

ALLOW TEMPORARY PACKAGES

Temporary change packages are placed into production and concatenated ahead of Production libraries. They are never rippled into Baseline and are deleted from the production environment after a number of days specified at package creation.

Enter YES to let temporary change packages be created.

Enter NO to disallow users to create temporary changes.

AUDIT LEVEL Enter the numeric value that dictates the Audit level that must be passed before a change package can be Frozen.

0—Audit is recommended but entirely optional.

1—Audit is required but any return code (except ABEND) is acceptable. This is the default option.

2—Audit is required and the return code must not exceed 12. This implies that there are “out-of-sync” situations within the Staging libraries.

3—Audit is required and the return code must not exceed 8. This implies that there are no “out-of-sync” situations within the Staging libraries, but there are “out-of-sync” situations with respect to the Baseline libraries.

4—Audit is required and the return code must not exceed 4. This implies that there are no “out-of-sync” situations within the Staging libraries or the Baseline libraries, but at least one component of Staging library is a “duplicate” of its baseline counterpart.

5—Audit is required and the return code must not exceed 0. This implies that there are no “out-of-sync” situations with either the Staging libraries or the Baseline libraries and no “duplicates” exist.

Field Description

103


CHECKOUT ENFORCEMENT RULE

Enter the numeric value that dictates the rule that must be passed before a component (not new components, but components that exist in the Baseline) can be staged. The administrator can restrict who stages components that are not first checked out from Baseline.

1—Checkout is optional.

Any component can be staged, regardless of whether it exists in Baseline or has been checked out to a package. ChangeMan ZMF does not check for the component's existence in the Baseline libraries.

2—Checkout is required unless the user passes an entity check.

Users attempting to stage a component that exists in Baseline, but has not been checked out, must pass a security system ENTITY CHECK before the stage can proceed. The entity name is specified in the application parameter generation. Staging is not allowed if the user does not pass the entity check.

3—Checkout is mandatory.

Disallow anyone from staging a component that exists in the Baseline library but has not been checked out to the package requesting the stage.

ENTITY CHECK IF LEVEL 2

If rule 2 of the above checkout enforcement rules was selected, enter the Entity Name. This is the name used for the entity check when users sign on to ChangeMan ZMF and select the Stage function. Those users whose TSO ID has been associated to the entity name are allowed to stage components that have not been checked out to their package but exist in the application's Baseline library.

ALLOW CONCURRENT CHECKOUT

Enter YES if components can be checked out to personal or Staging libraries. (This allows concurrent checkout of components that are already included in a change package. During installation the second, checked-out component overlays the first.)

Enter NO if components cannot be checked out if they reside in another package. (This prevents users from checking out components that are already checked out to a package.)

This rule applies to the same package as well as to other packages. It is disregarded for unplanned (emergency) packages.

ALLOW CHECKOUT TO PERSONAL LIB

Enter YES to let users check out to a personal library.

Enter NO to require all checkouts to go to Staging libraries.

This rule is disregarded for unplanned (emergency) packages.

STAGING RESTRICTION LEVEL

This option restricts who is allowed to stage new components and who does maintenance. From the user's view, it regulates the Stage Development Driven user option in the Stage Options panel (CMNSTG00).

1—Allow all users access to both Development Driven (stage components into a package without checking them out) and Package Driven stage options.

2—Users are required to pass an entity check before being allowed to stage any components via the Stage Development Driven option. Only TSO IDs associated with the ENTITY name are allowed to use both stage options. The entity name, which must be defined to your security system, is specific in the Staging Restriction Level in the application parameters.

3—All users are required to CHECKOUT all components to a package before staging, effectively disabling the Stage - Development Driven Option.

Field Description

104


ENTITY CHECK IF 2 ABOVE

If Staging Restriction 2 (above) was selected. This is the name used for the entity check when users sign on to ChangeMan ZMF and select the Stage Function. Those users whose TSO ID has been associated to the entity name are allowed to stage from a development driven list.

OVERLAY PRIOR STAGED COMPONENT

If one user in an application has staged source components and another user tries to stage another version of the same component in the same change package, this field dictates whether overlaying of the first component is allowed.

Enter YES to let any prior staged component be overlaid. A confirmation warning request is issued by ChangeMan ZMF before this is done.

Enter NO to enforce a single owner of a component. This option is not enforced against members that are checked out to the package in batch.

Note: More than one user can access the same component within the same change package. Entering a NO in this field prevents the overlaying of the same component by another user. This is based on what the ISPF statistics are in the user’s personal library. If those statistics do not match what is defined as the user ID in the staging package, then ChangeMan ZMF does not allow an overlay. The TSO ID in the package is a determining factor for the overlay. For example, if the TSO ID on panel CMNSTG01 (described in the Serena™ ChangeMan® ZMF User Guide) is SER20, then only SER20 is able to bring in a different copy of the component.

Field Description

105


VALIDATE VERSION DURING STAGING

This function ensures the integrity of a Baseline library component between checkout and staging. Users must check out components (not stage from Development libraries) for this function to be in effect. This option is also affected by the STAGING RESTRICTION LEVEL field. If the baseline version of a component has been altered after a user has checked it out (for example, another package has been installed that contains this component), staging of that component is prevented.

Enter YES to enforce this validation (require a regression test).

Enter NO to ignore the validation.

PROMOTION/ DEMOTION RULE

Enter the numeric value that regulates the movement of components from Promotion libraries to Staging (for editing) and back again. For an overview of Promotion in the ChangeMan ZMF cycle, see “What is ChangeMan ZMF?” on page 19.

0—Allows the Promotion and Demotion of components even if the change package has not yet been frozen. This is liberal Promotion and Demotion.

It allows re-editing of components in the staging library, without forcing a Demotion. Thus, different versions of a component can exist simultaneously in Staging and Promotion libraries.

For example, if a component at promotion level 2 is edited in staging, its promotion level is shown as 0 at the promotion panel. However, the component still exists in the level 2 library.

It is the responsibility of the users to monitor these versions and demote previously promoted components, if desired.

Rules 1 through 4 restrict Promotion to frozen (FRZ status) packages only:

1—Requires selective Demotion of a component followed by selective Refreeze, Edit, and Promotion directly back to the package's promotion level.

2—Requires selective Demotion of a component followed by selective Refreeze, Edit, and Promotion through all intermediate promotion levels.

3—Requires full Demotion of the entire package followed by a selective Refreeze, Edit, and Promotion through all intermediate promotion levels.

4—Requires full Demotion of the entire package followed by a Revert of the entire package to DEV status.

Field Description

106


2. After you have completed entering information in the fields of the panel, press ENTER. The Application Parameters Part 2 of 3 panel (CMNGLP02) is displayed:

The following table describes the fields on the Application Parameters Part 2 of 3 panel (CMNGLP02) and the valid information that you can enter on the panel:

Field Description

JOB NAME INCREMENT OVERRIDE

Determines if the job name suffix is incriminated in batch jobs submitted for background processing (batch API jobs). This option applies if:

• The job name in the JOB STATEMENT INFORMATION field consists of a userid and a one-character suffix.

• You select Batch (background) as the processing mode for stage or checkout, or you run Audit Auto Resolve.

YES

NO

Do not increment the job name suffix for batch jobs submitted for background processing; force background processing for a userid to single-thread.

Increment the job name each time a job is submitted for background processing.

USE ZPREFIX IN BATCH JOBS

Determines if ChangeMan ZMF uses the userid to construct a TSO profile to identify the variable pools when a TSO session is opened for batch API processing.

YES

NO

Use &ZPREFIX instead of &ZUSER in the PROFILE PREFIX command in batch TSO sessions for batch API functions.

Use &ZUSER in the PROFILE PREFIX command in batch TSO sessions for batch API functions.

CMNGLP02 -------------- APPLICATION PARAMETERS - PART 2 OF 3 ---------------- COMMAND ===> JOB NAME INCREMENT OVERRIDE ===> NO (Y/N) USE ZPREFIX IN BATCH JOBS ===> NO (Y/N) CREATE COMPONENT WORK RECORDS ===> NO (Y/N) FORCE AUDIT OF UNPLANNED PACKAGES ===> NO (Y/N) BYPASS STAGING LIBRARY ENQUEUES ===> NO (Y/N) ALLOW LINK PACKAGES ===> NO (Y/N) MEMO DELETE EMPTY PACKAGES ONLY ===> NO (Y/N) APPROVAL RESTRICTIONS: PACKAGE CREATOR CANNOT APPROVE ===> NO (Y/N) PACKAGE WORKER CANNOT APPROVE ===> NO (Y/N) ONLY 1 APPROVAL PER USER ID ===> NO (Y/N) ALLOW DESIGNATED PROC OVERRIDE ===> NO (Y/N) Press ENTER to continue; Enter B to go back 1 screen, or CANCEL to exit.

107


CREATE COMPONENT WORK RECORDS

Determines if component work records are created when a package component is changed. Component work records show who has updated a package component. Component work records can be accessed from the package component list.

YES

NO

Create a component work record when a package component is updated.

Do not create component work records.

FORCE AUDIT OF UNPLANNED PACKAGES

Determines if audit is required for unplanned packages.

This option is only in effect if the Audit Level is higher than 0.

YES

NO

Require audit before freeze for unplanned packages. A bad return code from audit will not prevent freeze for unplanned packages.

Allow freeze without audit for unplanned package.

BYPASS STAGING LIBRARY ENQUEUES

Determines if all staging libraries in a package are enqueued while a delete request from the Stage Package Component panel is processed.

YES

NO

Disable the staging library enqueue for component delete processing.

Enqueue all staging libraries for a package while processing a delete request.

ALLOW LINK PACKAGES

Allows packages in this application be linked to other change packages through ChangeMan ECP. Refer to the ChangeMan ECP Linked Package facility. Linked packages are subject to delete, freeze, approval, and revert restrictions.

YES

NO

Allow packages in this application to be linked to other packages through ChangeMan ECP.

Prohibit package linking in this application.

MEMO DELETE EMPTY PACKAGES ONLY

YES

NO

Prohibit package Memo Delete if a change package contains any components or utility requests (scratch or rename).

Permit Memo Delete when a package contains components or utility requests.

APPROVAL RESTRICTIONS

The next three fields on this panel limit a user’s approval authority for a planned package, even though they may otherwise be permitted to approval to that package. Approval restrictions controlled by these parameters do not apply to unplanned packages.

PACKAGE CREATOR CANNOT APPROVE

Prohibits the user who created a package from entering an approval for that package, even if they are authorized by the security system to enter approvals.


YES

NO

Prohibit users from entering an approval for a package that they created.

Allow users to approve a package that they created, if they are authorized.

Field Description

108


PACKAGE WORKER CANNOT APPROVE

Prohibits a user who has worked on a component in a package from entering an approval for that package, even if they are authorized by the security system to enter approvals.

This option is in effect only if the CREATE COMPONENT WORK RECORDS option is YES.


YES

NO

Prohibit a user who worked on a package component from entering an approval for the package.

Allow a user who has worked on a package component to approve the package, if they are authorized.

ONLY 1 APPROVAL PER USER ID

Prohibits one user from entering more than one approval for a package, even if they are authorized by the security system to enter those approvals.


YES

NO

Restrict each userid to only one approval per package.

Allow a userid to enter more than one approval for a package, if they are authorized.

ALLOW DESIGNATE PROC OVERRIDE

Allows specification of a different target load type in a Designated Compile Procedure than the Target Type defined for the like-source type in Application Library Types.

YES

NO

Allow a different like-load type to be entered in the LOD Type field on the Component List panel (the second panel for Designated Compile Procedure definitions).

Restrict the Old Type field to the same value as the Target Load in Application Library Types.

Field Description

109


3. After you have completed entering information in the fields of the panel, press ENTER. The Application Parameters Part 3 of 3 panel (CMNGLP03) is displayed:

The following table describes the fields of the Application Parameters Part 3 of 3 panel (CMNGLP03) and the information that you can enter on the panel.

Field Description

AGING INSTALLED PACKAGES

Enter the number of days that you wish the package record to remain in the Package Master.

Since the installed package record must exist in the Package Master at the time its associated Staging libraries are deleted, the value in this field must be greater than or equal to the value in the Aging Staging Datasets field. Also, the status of the package must be BAS, INS, or TCC.

AGING STAGING DATASETS

Enter the number of days that you wish the staging data sets from the package to remain in the systems catalog.

The value in this field must be less than or equal to the value in the Aging Installed Packages field. Also, the status of the corresponding change package must be BAS, INS, or TCC.

To delete or archive the package records, run the appropriate housekeeping job.

NOTE: The housekeeping job deletes the staging data sets after the package installation date. Once the staging data sets are deleted, you cannot backout the package.

CMNGLP03 ------------- NAVI PARAMETERS - PART 3 OF 3 -------------------------- COMMAND ===> AGING - INSTALLED PACKAGES ===> 30 (0 to 999 days) - STAGING DATASETS ===> 14 (0 to 999 days) DEFAULT UNIT NAME ===> 3390 (Generic disk unit) DEFAULT VOLUME SERIAL ===> REQUIRE WORK REQUEST NUMBER ===> NO (Y/N; affects INFO) REQUIRE DEPARTMENT NUMBER ===> NO (Y/N) HIERARCHICAL APPROVAL PROCESS ===> NO (Y/N) SAVE TO PERSONAL & STAGING LIBS ===> NO (Y/N) EDIT STAGING RECOVERY MODE ON ===> NO (Y/N) JOB CARD INFORMATION: ===> //NAVIAPPL JOB (X170,374),'APPL NAVI',__________________________________ ===> // CLASS=U,MSGCLASS=9_______________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to generate application parameters. Enter B to go back 1 screen or CANCEL to exit.

110


DEFAULT UNIT NAME

Enter the generic unit name for disk packs that all dynamic allocations use unless otherwise specified (for example, SYSDA).

It is the type of disk device to use for allocation of (non-temporary) data sets by ChangeMan ZMF. This is the disk device in which ChangeMan ZMF allocates the X.REMOTESITE and the.PACKAGE set of the staging data sets.

This field can be left blank if you specify the Default Volume Serial in the DEFAULT VOLUME SERIAL field. (If this field and the default volume serial are left blank, it could lead to the use of temporary disk device usage, for example, 3390. The allocated data sets are then subject to being scratched without notification.)


Enter the volume serial number that all dynamic allocations use unless specified elsewhere in ChangeMan ZMF.

The serial number of the volume to use for allocation of (non-temporary) data sets by ChangeMan ZMF. This field is not required if the DEFAULT UNIT NAME field has been set. This is the serial number of the volume in which ChangeMan ZMF allocates the X.REMOTESITE and the.PACKAGE set of the staging data sets.

REQUIRE WORK REQUEST NUMBER

Enter YES to require users to enter a work request number during package creation.

Enter NO to make the entry of a work request number optional.

REQUIRE DEPARTMENT NUMBER

Enter YES to require users to enter a department number during package creation.

Enter NO to make the entry of a department number optional.

HIERARCHICAL APPROVAL PROCESS

Type YES to notify package approval “User to notify” in the sequence specified in the approval Order Number. Notification of “Users to notify” at the next sequential Order Number occurs when all approvals at the previous Order Number have been entered.

Type NO to notify all approval “Users to notify” at all Order Numbers when the package is frozen.

SAVE TO PERSONAL & STAGING LIBS

Enter YES to update Staging and Personal libraries.

Enter NO to allow updates to the Staging library only when a component is staged from a Development library and then edited through ChangeMan ZMF.

Field Description

111


4. Press ENTER to save and generate the application parameters.

DEFINING LIBRARY TYPES AND STAGING LIBRARY ATTRIBUTES

A library type definition sets processing rules for the components stored under that library type. The definition also sets the data set attributes for the package stage library that is allocated for the library type. The Application Administrator defines the library types in each application.

Application library types are copied from global library type definitions. Only library types defined in global administration can be defined in an application. However, an application does not have to contain all of the library types defined in global administration.

Library Type Order

The order that library types are listed on the Application Library Types Part 1 of 2 panel determines the order that library types are processed in some ChangeMan ZMF functions. (This panel is shown on page 113.)

EDIT STAGING RECOVERY MODE ON

Indicate whether the edit staging recovery mode is on.

Enter YES to allow users to keep track of all changes made to a component. These changes are stored in a development data set. If an ABEND occurs, users can recover the changes when reentering ChangeMan ZMF.

Note: To activate the Recovery Process during a ChangeMan ZMF Edit-In-Staging session, this field must be ON.

Enter NO to not allow users to recover the changes when reentering ChangeMan ZMF after an ABEND occurs.

JOB CARD INFORMATION

This job card information is used when the package installation jobs are built at Freeze time. Specifically, ChangeMan ZMF uses it when submitting batch jobs for distributing change packages, acknowledging distribution, installing change packages, acknowledging installation, backing out change packages, and rippling an application's baseline files.

The job name is set to reflect package and installation transaction numbers This is the only job card information that the Global and Application Administrators provide. Users are required to set up similar job cards for batch API jobs such as Staging and Freezing.

Field Description

112


Library Concatenations

ChangeMan ZMF uses the library type definition order when it includes stage libraries in library concatenations for batch job JCL. The following table lists some library concatenations that depend on the library type definition order.

The staging library sequence in concatenations matches the order of application library types definitions. The order of promotion and baseline libraries is not affected by library type definitions on the Application Library Type Part 1 of 2 panel.

Audit Auto-Resolve

The Auto-Resolve feature of audit submits recompile and relink jobs to automatically resolve out-of-synch conditions in a change package. Recompile jobs are submitted before relink jobs. The sequence of recompile and relink jobs is determined by the order of library type definitions on the Application Library Type Part 1 of 2 panel.

If you code Like-Source library types for subroutines before Like-Source library types for calling programs, Audit Auto-Resolve submits recompile jobs for subroutines before submitting recompile jobs for calling programs.

If you code Like-Load library types for subroutines before Like-Load library types for calling programs, Audit Auto-Resolve submits relink jobs for subroutines before submitting relink jobs for calling programs.

Processing subroutines before calling programs is the most efficient way to resolve all out-of-synch conditions in the fewest number of steps.

Defining Library Types for a New Application

Perform these steps to define the library types for a new application.

JCL ddname Library Type Used in batch jobs...

SYSLIB LIKE-C types Copybook expansion steps running ChangeMan ZMF program CMNWRITE

Copybook libraries in compile and assemble jobs

Copybook libraries in BMS MAP gens

Copybook libraries in IMS PSB/DBD gens

SYSLIB LIKE-L types Load libraries in link edit

Load libraries in IMS PSB/DBD gens

INCLIB Target Type Load libraries in link edit.

OBJLIB Object library types defined in skeleton CMN$$VAR

Object libraries in link edit

113


1. On the Application Administration Options panel, type 2 on the Option line and press ENTER. The Application Library Types Part 1 of 2 panel is displayed:

The following table describes the fields on the Application Library Types Part 1 of 2 panel.

Field Description


S

I

R

D

*

Select to see the next panel for this library type.


Repeat an existing library type row.

Delete an existing library type row.

Display a selection list of available library types.

CMNCLLT0 ------------ DEMO - LIBRARY TYPES PART 1 OF 2 ----- Row 1 to 15 of 17 COMMAND ===> SCROLL ===> PAGE Enter END command to save changes or CANCEL to exit. LIB LIKE DEFER TARGET SEL. TYPE DESCRIPTION (S/C/L/P)(Y/N) TYPE OPT. '''' CPY Copybooks___________________________________ C Y ___ __ '''' CTC Control Statements (PARMLIB)________________ P Y ___ __ '''' DBB DB2 Bind Control____________________________ P Y ___ __ '''' DBR DB2 DBRM____________________________________ P Y ___ __ '''' JCL Job Execution JCL___________________________ P Y ___ __ '''' LCT Link Edit Control Statements________________ P Y ___ __ '''' LST Compressed Stage Listings___________________ P Y ___ __ '''' LOD Load Modules________________________________ L Y ___ __ '''' MAP BMS MAP Load Modules________________________ L Y ___ __ '''' MPC BMS MAP Copybook (DSECT)____________________ C Y ___ __ '''' MPS BMS MAP Source______________________________ S Y MAP __ '''' OBJ Object Code_________________________________ P Y ___ __ '''' PRC JCL Cataloged Procedures____________________ P Y ___ __ '''' PKG DB2 Package Bind Control____________________ P Y ___ __ '''' SKL ISPF Skeletons______________________________ P Y ___ __ '''' SRC Source Code_________________________________ S Y LOD __

114


LIB TYPE Type a three character library type.

Some library types are reserved. These types have built-in attributes, and they are used in particular internal processes.:

ASC

CPY

CTC

DBB

DBR

DOC

JCL

LCT

LOD

LST

PRC

SRC

APS painted screens (ChangeMan ZMF APS Option) - DCB must be RECFM=F/FB, LRECL=240

Copybooks - Defaults to Like-Copy (see the definitions for the LIKE types below.) DCB must be RECFM=F/FB, LRECL=80

Control Statements - Defaults to Like-PDS. DCB must be RECFM=F/FB, LRECL=80

DB2 Bind Control Statements (ChangeMan ZMF DB2 Option) - Defaults to Like-PDS. Used by the DB2 Selectable Option. DCB must be RECFM=F/FB, LRECL=80

DB2 DBRM (ChangeMan ZMF DB2 Option) - Defaults to Like-PDS. Used by the DB2 Selectable Option. DCB must be RECFM=F/FB, LRECL=80

Documentation. Defaults to Like-PDS. DCB must be RECFM=F/FB/V/VB

JCL - Defaults to Like-PDS, although libraries with this type are included in Impact Analysis JCL relationships. DCB must be RECFM=F/FB, LRECL=80

Link Edit Control Statements - Defaults to Like-PDS. DCB must be RECFM=F/FB, LRECL=80

Load Modules - Defaults to Like-Load. DCB must be RECFM=U.

Compressed Stage Listings - Defaults to Like-PDS. Cannot be explicitly staged. DCB must be RECFM=F/FB, LRECL=80.

Cataloged JCL Procedures - Default to Like-PDS, although libraries with this type are included in Impact Analysis JCL relationships. DCB must be RECFM=F/FB, LRECL=80

Source Code - Defaults to Like-Source. DCB must be RECFM=F/FB, LRECL=80

DESCRIPTION Enter freeform text describing the library type.

Field Description

115


LIKE (S/C/L/P) Type a one-character LIKE code to define behaviors and characteristics of a library type.

S

C

L

P

Blank

Like-Source - Components in Like-Source library types are staged through a batch job defined by a Language and Procedure assigned to the component to create a component in a Like-Load library type. Every Like-Source library type must have a TARGET TYPE in its Library Type Definition. There is a source-load relationship between every Like-Source component and a Like-Load component. Members in Like-Source libraries are analyzed for Impact Analysis CPY relationships.

Like-Copy - Components in Like-Copy library types are not processed through a procedure by stage. Like-Copy libraries are included in SYSLIB concatenations for copybook libraries. Members in Like-Copy libraries are analyzed for Impact Analysis CPY relationships.

Like-Load - Components in Like-Load libraries are assumed to be the product of a stage procedure performed on a Like-Source component. Like-Load libraries are included in SYSLIB concatenations for load libraries. Members in Like-Load libraries are analyzed for Impact Analysis LOD relationships.

Like-PDS -Components in Like-PDS library types are not processed through a procedure by stage. Like-PDS libraries are not included in SYSLIB concatenations for copybook or load libraries. Members in Like-PDS libraries are not analyzed for Impact Analysis relationships.

Like-Other - If you leave the LIKE field blank in a Library Type Definition, the type is referred to as “Like-Other”. Components in Like-Other library types are staged through a batch job created from an ISPF skeleton named CMN$$xxx where xxx is the Like-Other library type. You must code Like-Other skeletons from a model named CMN$$OTH delivered from SERENA. Like-other libraries are not analyzed for Impact Analysis relationships.

Note: Like-Other components are not analyzed by Audit.

DEFER Y

N

Defer allocation of the staging library for this types until the fist component of the type is staged or checked out.

Allocate the stage library for this type when the change package is created, even though there may never be any members of this library type in the package.

TARGET TYPE Type a Like-Load target library type for each Like-Source library type.

SELECTABLE OPTION

Use this field to associate a library type with a ChangeMan ZMF selectable option that you have licensed. The behavior of the library type may require further definition in administration panels or ISPF skeletons.

A

D

I

APS Option

DB2 Option

IMS Option

Field Description

116


When the Application Library Types Part 1 of 2 panel is first displayed for a new application, all of the library types defined on the Global Library Types Part 1 of 2 panel are displayed The definitions displayed on this panel are the same as those in global administration.

Note Library type definitions should be standardized across all applications. You should not change the fields displayed for a library type on the Application Library Types Part 1 of 2 panel. If you need a unique definition for a library type, you should define a new global library type.

2. If a library type is not needed for this application, or if you wish to change the order of the definitions by deleting and redefining a library type, type D (Delete) in the line command for the library type on the Application Library Types Part 1 of 2 panel and press ENTER. The library type is deleted.

3. To add a library type to the Application Library Types Part 1 of 2 panel that you previously deleted:

a) Type I (Insert) in the line command above where you want to insert the library type and press ENTER. An empty library type entry is inserted on the panel.

b) Type * in the line command for the empty library type definition and press ENTER. The Global Library Type Selection List panel is displayed:

c) On the Global Library Type Selection List panel, type S in the line command for any global library type that you want to add at the insert point on the Application Library Type Part 1 of 2 panel. You may select multiple library types, but you can not scroll down to select global library types from multiple pages of the Global Library Type Selection List at one time.

d) Press ENTER to return to the Application Library Type Part 1 of 2 panel, where the new library types have been added at the insertion point.

CMNGLTPL ------------- GLOBAL LIBRARY TYPE SELECTION LIST - Row 1 to 20 of 151 COMMAND ===> SCROLL ===> PAGE LIB DESCRIPTION _ CPY Copybooks _ CTC Control Statements (PARMLIB) _ DBB DB2 Bind Control _ DBR DB2 DBRM _ JCL Job Execution JCL _ LCT Link Edit Control Statements _ LST Compressed Stage Listings _ LOD Load Modules _ MAP BMS MAP Load Modules _ MPC BMS MAP Copybook (DSECT) _ MPS BMS MAP Source _ OBJ Object Code _ PRC JCL Cataloged Procedures _ PKG DB2 Package Bind Control _ SKL ISPF Skeletons _ SRC Source Code _ TST Test Library Type

117


4. There is a second panel for each library type that defines additional processing rules and the staging library attributes for a library type. Type S in the line command for a library type and press ENTER. The Application Library Types Part 2 of 2 panel is displayed:

The following table describes the fields on the Application Library Type Part 2 of 2 panel.

Field Description

GENERIC UNIT NAME

Type the DASD generic group or unit device name to be used for allocating staging libraries for this library type. This field may be left blank if the VOLUME SERIAL field is used.

VOLUME SERIAL Type the DASD volume serial number where stage libraries are to be allocated for this library type. This field may be left blank if the GENERIC UNIT NAME field is used.

SPACE UNITS Type the units to be used for the primary and secondary space allocations for staging libraries for this library type.

TRK

CYL

BLK

Allocate space in tracks.

Allocate space in cylinders.

Allocate space in blocks.

PRIMARY QUANTITY

SECONDARY QUANTITY

DIRECTORY BLOCKS

Type the primary space, secondary space, and directory block allocation to be used for the staging libraries for this library type.

Use MINIMUM space allocations, especially the PRIMARY QUANTITY. ChangeMan ZMF dynamically reallocates stage libraries if extents or directory blocks are exhausted as the change package grows.

Unused space in PDS stage libraries is freed when the change package is frozen. ChangeMan ZMF does not automatically compress stage libraries, but you can compress stage libraries for a package with the ZP Package List command.

CMNCLLT1 ------------ DEMO - LIBRARY TYPES PART 2 OF 2 ------------------------ COMMAND ===> LIBRARY TYPE: CPY - Copybooks LIKE VALUE: C DEFER VALUE: Y STAGING DATASET ATTRIBUTES: GENERIC UNIT NAME ===> 3390 (Generic group name or unit) VOLUME SERIAL ===> (Required if GENERIC UNIT unspecified) SPACE UNITS ===> TRK (TRK, CYL or BLK) PRIMARY QUANTITY ===> 1 (In above units) SECONDARY QUANTITY ===> 1 (In above units) DIRECTORY BLOCKS ===> 5 RECORD FORMAT ===> FB RECORD LENGTH ===> 80 BLOCK SIZE ===> 0 DATA SET TYPE ===> PDS (LIBRARY for PDSE, PDS for pds, or blank) OTHER OPTIONS: CHECKOUT COMPONENT DESCRIPTION ===> NO (Y/N) CHECKOUT COMPONENT ACTIVITY FILE ===> NO (Y/N) COMPONENT ACTIVITY FILE TYPE ===> SAVE STAGING VERSIONS ===> NONE ALWAYS/NONE/PROMPT Press ENTER to process; Enter END command to exit.

118


RECORD FORMAT Type the staging library record format for this library type. Valid values include:

F, FA, FB, FBA, FBM, FM, FS, V, VA, VB, VBA, VBM, VM, U

Legend:

F - Fixed length recordsV - Variable length recordsU - Undefined format recordsB - Blocked recordsS - Standard blocksA - ASA printer control charactersM - Machine code printer control characters

RECORD LENGTH Type the logical record length for components in this library type.

BLOCK SIZE Type the staging library block size for this library type.

You may enter 0 to let SMS calculate the best block size for the storage device.

DATASET TYPE Type LIBRARY for PDSE stage libraries. Leave the field blank or type PDS for PDS stage libraries.

CHECKOUT COMPONENT DESCRIPTION

YES

NO

Copy the Component General Description from the Package Master to the change package when a component is checked out. Allow developers to create or update the Component General Description through a change package.

Do not copy the Component General Description from the Package Master to the change package when a component is checked out. Prevent developers from creating or updating the Component General Description in a change package.

The Component General Description can always be created or updated through Application Administration.

CHECKOUT COMPONENT ACTIVITY FILE

YES

NO

Automatically checkout a second component with the same name in a second library type when you checkout a component in this library type.

The second library type specified below in the COMPONENT ACTIVITY FILE TYPE field. The second library type is called a “Component Activity File” here, but it can be any like-PDS library type defined to this application.

If you check out a component to a personal library, the Activity File is checked out to the staging library. If there is no Activity File member with the same name in baseline, you must create one (stage from development) in your package. If there is no matching Activity File member, Audit flags a SYNCH6!

Checkout components in this type without checking out a second component with the same name in another library type.

COMPONENT ACTIVITY FILE TYPE

Type the library type of the Component Activity File. This field is only required if YES is specified in the CHECKOUT COMPONENT ACTIVITY FILE field.

Field Description

119


When this panel is first displayed for a library type in a new application, the fields on the panel are the same as the fields on the Global Library Types Part 2 of 2 panel for the library type.

Note You may adjust the values displayed on the Application Library Types Part 2 of 2 to fit the needs of the application you are defining. Library type standardization does not need to include the attributes and rules displayed on this panel.

5. When you are finished updating fields on the Application Library Type Part 2 of 2 panel, press ENTER to return to the Application Library Types 1 of 2 panel.

6. When you are finished creating library type definitions on the Application Library Types Part 1 of 2 panel, press PF-3 or type END and press ENTER to store the application library type definitions in the Package Master file.

Updating Application Library Types

Perform these steps to update application library type definitions.

SAVE STAGING VERSIONS

This field dictates whether a component in a staging library is saved before it is overlaid by a new version from edit-in-stage, checkout, or stage from development.

ALWAYS

NONE

PROMPT

The previous version is always saved in a staging version before overlay.

The previous version is never saved before overlay.

The developer may choose not to save a staging version if the following are true:

The developer is replacing or overlaying the component in the staging library, not deleting it.

The ID on the component in the staging library is the same as the developer’s TSO userid.

Field Description

120


1. On the Application Administration Options panel, type 2 on the Option line and press ENTER. The Application Library Types Part 1 of 2 panel is displayed:

See the table that starts on page page 113 that describes fields on this panel.

Note Library type definitions should be standardized across all applications. You should not change the fields displayed on the Application Library Types Part 1 of 2. If you need a unique definition for a library type, you should define a new global library type.

2. To delete a library type from the Application Library Types Part 1 of 2 panel, type D (Delete) in the line command for the library type and press ENTER.

3. To add a library type to the Application Library Types Part 1 of 2 panel:

a) Type I (Insert) in the line command above where you want to insert the library type and press ENTER. An empty library type entry is inserted on the panel.

CMNCLLT0 ------------ DEMO - LIBRARY TYPES PART 1 OF 2 ---- Row 1 to 16 of 150 COMMAND ===> SCROLL ===> PAGE Enter END command to save changes or CANCEL to exit. Enter * in line command field for global staging libraries selection list. LIB LIKE DEFER TARGET SEL. TYPE DESCRIPTION (S/C/L/P)(Y/N) TYPE OPT. '''' CPY Copybooks___________________________________ C Y ___ __ '''' CTC Control Statements (PARMLIB)________________ P Y ___ __ '''' DBB DB2 Bind Control____________________________ P Y ___ __ '''' DBR DB2 DBRM____________________________________ P Y ___ __ '''' JCL Job Execution JCL___________________________ P Y ___ __ '''' LCT Link Edit Control Statements________________ P Y ___ __ '''' LST Compressed Stage Listings___________________ P Y ___ __ '''' LOD Load Modules________________________________ L Y ___ __ '''' MAP BMS MAP Load Modules________________________ L Y ___ __ '''' MPC BMS MAP Copybook (DSECT)____________________ C Y ___ __ '''' MPS BMS MAP Source______________________________ S Y MAP __ '''' OBJ Object Code_________________________________ P Y ___ __ '''' PRC JCL Cataloged Procedures____________________ P Y ___ __ '''' PKG DB2 Package Bind Control____________________ P Y ___ __ '''' SKL ISPF Skeletons______________________________ P Y ___ __ '''' SRC Source Code_________________________________ S Y LOD __ '''' TST Test Library Type___________________________ P Y ___ __

121


b) Type * in the line command for the empty library type definition and press ENTER. The Global Library Type Selection List panel is displayed:

c) On the Global Library Type Selection List panel, type S in the line command for any global library type that you want to add at the insert point on the Application Library Type Part 1 of 2 panel. You may select multiple library types, but you can not scroll down to select global library types from multiple pages of the Global Library Type Selection List at one time.

d) Press ENTER to return to the Application Library Type Part 1 of 2 panel, where the new library types have been added at the insertion point.

CMNGLTPL ------------- GLOBAL LIBRARY TYPE SELECTION LIST - Row 1 to 20 of 151 COMMAND ===> SCROLL ===> PAGE LIB DESCRIPTION _ CPY Copybooks _ CTC Control Statements (PARMLIB) _ DBB DB2 Bind Control _ DBR DB2 DBRM _ JCL Job Execution JCL _ LCT Link Edit Control Statements _ LST Compressed Stage Listings _ LOD Load Modules _ MAP BMS MAP Load Modules _ MPC BMS MAP Copybook (DSECT) _ MPS BMS MAP Source _ OBJ Object Code _ PRC JCL Cataloged Procedures _ PKG DB2 Package Bind Control _ SKL ISPF Skeletons _ SRC Source Code _ TST Test Library Type

122


4. To update additional processing rules or the staging library attributes for a library type, type S in the line command for the library type on the Application Library Types Part 1 of 2 panel. The the Application Library Types Part 2 of 2 panel is displayed:

See the table that starts on page page 117 that describes fields on this panel.

Note You may adjust the values displayed on the Application Library Types Part 2 of 2 to fit the needs of the application you are defining. Library type standardization does not need to include the attributes displayed on this panel.

5. When you are finished updating library type definition fields on the Application Library Type Part 2 of 2 panel, press ENTER to return to the Application Library Types 1 of 2 panel.

6. On the Application Library Type Part 1 of 2 panel, press PF-3 or type END and press ENTER to store the application library type definitions in the ChangeMan ZMF Package Master File.

DEFINING THE LANGUAGES

You provide ChangeMan ZMF with all of the language names available in this environment. ChangeMan ZMF can still process component types if source and like source language types are not defined here, but when you define them, users are able to reference these component types by language. The Application Administrators select from this list when individual applications are set up. This information can also be used as a selection list from within the global options whenever necessary.

To define the languages, take the following steps:

CMNCLLT1 ------------ DEMO - LIBRARY TYPES PART 2 OF 2 ------------------------ COMMAND ===> LIBRARY TYPE: CPY - Copybooks LIKE VALUE: C DEFER VALUE: Y STAGING DATASET ATTRIBUTES: GENERIC UNIT NAME ===> 3390 (Generic group name or unit) VOLUME SERIAL ===> (Required if GENERIC UNIT unspecified) SPACE UNITS ===> TRK (TRK, CYL or BLK) PRIMARY QUANTITY ===> 1 (In above units) SECONDARY QUANTITY ===> 1 (In above units) DIRECTORY BLOCKS ===> 5 RECORD FORMAT ===> FB RECORD LENGTH ===> 80 BLOCK SIZE ===> 0 DATA SET TYPE ===> PDS (LIBRARY for PDSE, PDS for pds, or blank) OTHER OPTIONS: CHECKOUT COMPONENT DESCRIPTION ===> NO (Y/N) CHECKOUT COMPONENT ACTIVITY FILE ===> NO (Y/N) COMPONENT ACTIVITY FILE TYPE ===> SAVE STAGING VERSIONS ===> NONE ALWAYS/NONE/PROMPT Press ENTER to process; Enter END command to exit.

123


1. Select option 3 on the Application Administration Options panel. The Application Language Names panel (CMNCLLNG) is displayed:

2. Define a standard language or update an existing standard language on the panel. The standard language names you define is associated with the language assumption feature of ChangeMan ZMF. This feature assists users who neglect to explicitly define the language type of a source or like-source component type that they stage. The language assumption feature searches the code of the staged component, matches its language name to the standard language names you define, and names it.

3. Type END to save your entry.

DEFINING THE COMPILING PROCEDURES This option is used to enter all the different procedures that are needed to compile and link source components. This information is displayed for selection during any application level change package staging. Thus, it must include all of the procedures for change installation of all applications.

Even if your application does not contain any source components, you must enter a compile procedure.

To define the compiling procedures, take the following steps.

1. Select option 4 from the Application Administration Options panel. The Application Compile Procedures panel (CMNCLPRC) is displayed:

This panel lists all of the pre-defined compiling procedures. Skeletons for these procedures must exist in the custom skeletons library (see the Serena™ ChangeMan® ZMF Skeleton Reference manual for details).

CMNCLLNG ------------------- APPLICATION LANGUAGE NAMES ----------------------------COMMAND ===> SCROLL ===> CSR


LANGUAGE'''' COBOL2__'''' COBOL __'''' ASM __'''' PLI __

CMNCLPRC ------------------ APPLICATION COMPILE PROCEDURE ------------------------COMMAND ===> SCROLL ===> CSR


Enter * in LANGUAGE or PROCEDURE fields for selection list.

LANGUAGE PROCEDURE DESCRIPTION'''' COBOL2__ ________ _____________________________________________

124


2. Create or update the rows of the list. The following table describes the fields of the panel.

SETTING UP PLANNED APPROVALS

The Planned Approvals definition determines who must approve packages, the order of approvals, and how approvers are notified that their approval is required.

See “Package Approvals” on page 40 for a discussion of the difference between Planned and Unplanned Approval lists.

To create or update a Planned Approvals list, follow these steps.

1. On the Application Administration Options panel, type 5 on the Option line and press ENTER. The Planned Approvals Part 1 of 2 panel is displayed:

Column Description

LANGUAGE Enter the language name for the compile procedure. If you want to select from a list of available language names, enter *. The Language Name Selection List is displayed.

PROCEDURE Enter the procedure name. If you want to select from a list of procedure names, enter *. The Procedure Selection List is displayed.

You cannot use a numeric or special character in the fourth position of the procedure name.

DESCRIPTION Enter the procedure description, which can be up to 44 alphanumeric characters.

CMNCAPLD ---------- DEMO - PLANNED APPROVALS PART 1 OF 2 ----- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> PAGE Define an approval list for all planned packages; Use line command S to supply recipient notification. Enter END command to save changes or CANCEL to exit. SECURITY ORDER INT. LNK APPROVER DESCRIPTION ENTITY NO. APR. PKG '''' Enterprise Change Coordinator_______________ CMNECP__ 00 ___ YES '''' Development Manager_________________________ CMNDVMGR 10 YES ___ '''' Quality Assurance Manager___________________ CMNQAMGR 20 ___ ___ '''' Change Control______________________________ CMNQAMGR 30 ___ ___ ******************************* Bottom of data ********************************

125


The following table describes the fields on the Application Planned Approvals Part 1 of 2 panel.

Field Description

Line Command Type a value line command.

S

I

R

D

Select to see the next panel for this approval

Insert a blank approval row.

Repeat an existing approval

Delete an existing approval

APPROVER DESCRIPTION

Type a description of the approval. To avoid excessive maintenance, do not use an approver’s name.

SECURITY ENTITY

Type the security entity name that is used to grant authority to TSO userids to enter this approval.

You must define this security entity in our security system. Grant the appropriate authority TSO userids in your security system to grant approver authority to individuals. See “Pre-Implementation Decisions” on page 25 for details.

ORDER NO. Type an order number if an approval hierarchy is required.

Order number 00 may be approved at any time.

A group of approvals with the same non-zero order number may be approved in any order.

Start with order numbers 10 and increment by 10 so that other approvers can be added later.

Link Package approvals automatically reset their order numbers to 00.

INT. APR. Indicates whether this approval is added to participating packages in other applications that are defined on the Affected Applications panel of participating packages in this application. This approval is added only if it is different from approvals in the affected application.

YES

Blank or NO

Add this approval to participating package in applications listed on the Affected Applications panel of participating packages in this application.

Do not add this approval to participating packages in affected applications.

LNK PKG Indicates whether this approval is added to packages that are linked to other change packages through ChangeMan ECP.

YES

Blank or NO

Add this approval to linked packages.

Do not add this approval to linked packages.

126


2. On the Plannced Approvals Part 1 of 2 panel, type S on the line command for an approval and press Enter. The Planned Approvals Part 2 of 2 panel is displayed:

The following table describes the fields on the Planned Approvals Part 2 of 2 panel.

The information on the Planned Approvals Part 2 of 2 panel is used to:

• Notify an approver that there is a package awaiting for their approval.

• Allow queries for packages awaiting approval based on TSO userids entered in User(s) to Notify.

These rules apply when you are setting up approval notifications:

• Approver notification is not required for an approval.

• You can create multiple notifications for an approval.

Field Description

Vehicle Type the vehicle used to notify approvers about packages pending approval. You may use any vehicle activated in Global Administration Parameters. You can also use MVSSEND.

BATCH

SERNET

MVSSEND


Send notification data through SERNET to ChangeMan ECP, which formats an e-mail message and send through SMTP.

Issue an MVS SEND message to TSO user IDs.

User(s) to Notify Type the appropriate user identifications for the notification vehicle. Separate multiple user identifications with commas.:

E-mail Address or Mailing List

TSO Userid

Use with the SERNET vehicle. Also use with the BATCH vehicle if REXX program CMNSMTP has been activated in skeleton CMN$$NTF.

Use for vehicle MVSSEND,

CMNCAPL1 ---------- DEMO - PLANNED APPROVALS PART 2 OF 2 ----- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> CSR Press END command to exit. APPROVER: Development Manager ENTITY: CMNDVMGR ORDER NO: 10 Vehicle User(s) to Notify '''' MVSSEND_ USER120,USER84______________________________ '''' SERNET__ [email protected]__________________________ '''' SERNET__ [email protected]__________ ******************************* Bottom of data ********************************

127


• You can create multiple notifications using the same vehicle.

SETTING UP UNPLANNED APPROVALS

The Unplanned Approvals definition determines who must approve packages, the order of approvals, and how approvers are notified that their approval is required.

See “Package Approvals” on page 40 for a discussion of the difference between Unplanned and Planned Approval lists.

To create or update an Unplanned Approvals list, follow these steps.

1. On the Application Administration Options panel, type 6 on the Option line and press ENTER. The Unplanned Approvals Part 1 of 2 panel is displayed:

The following table describes the fields on the Application Planned Approvals Part 1 of 2 panel.

Field Description

Line Command Type a value line command.

S

I

R

D

Select to see the next panel for this approval.

Insert a blank approval row.

Repeat an existing approval.

Delete an existing approval.

APPROVER DESCRIPTION

Type a description of the approval. To avoid excessive maintenance, do not use an approver’s name.

SECURITY ENTITY

Type the security entity name that is used to grant authority to TSO userids to enter this approval.

You must define this security entity in our security system. Grant the appropriate authority TSO userids in your security system to grant approver authority to individuals. See “Pre-Implementation Decisions” on page 25 for details.

CMNAAPLD --------- DEMO - UNPLANNED APPROVALS PART 1 OF 2 ---- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> PAGE This approval list applies to all UNPLANNED packages created during non-business hours. Use line command S to supply recipient notification. Enter END command to save changes or CANCEL to exit. SECURITY ORDER LNK APPROVER DESCRIPTION ENTITY NO. PKG '''' Enterprise Change Coordinator_______________ CMNECP__ 00 YES '''' Operations Supervisor_______________________ CMNOPNS_ 10 ___ ******************************* Bottom of data ********************************

128


2. On the Unplanned Approvals Part 1 of 2 panel, type S on the line command for an approval and press Enter. The Unplanned Approvals Part 2 of 2 panel is displayed:

The following table describes the fields on the Planned Approvals Part 2 of 2 panel.

ORDER NO. Type an order number if an approval hierarchy is required.

Order number 00 may be approved at any time.

A group of approvals with the same non-zero order number may be approved in any order.

Start with order numbers 10 and increment by 10 so that other approvers can be added later.

Link Package approvals automatically reset their order numbers to 00.

LNK PKG Indicates whether this approval is added to packages that are linked to other change packages through ChangeMan ECP.

YES

Blank or NO

Add this approval to linked packages.

Do not add this approval to linked packages.

Field Description

Vehicle Type the vehicle used to notify approvers about packages pending approval. You may use any vehicle activated in Global Administration Parameters. You can also use MVSSEND.

BATCH

SERNET

MVSSEND


Send notification data through SERNET to ChangeMan ECP, which formats an e-mail message and send through SMTP.

Issue an MVS SEND message to TSO user IDs.

Field Description

CMNAAPL1 --------- DEMO - UNPLANNED APPROVALS PART 2 OF 2 ---- Row 1 to 1 of 1 COMMAND ===> SCROLL ===> PAGE Press END to save changes or CANCEL to exit. APPROVER: Operations Supervisor ENTITY: CMNOPNS ORDER NO: 10 Vehicle User(s) to Notify '''' MVSSEND_ USER567____________________________________ ******************************* Bottom of data ********************************

129


The information on the Unplanned Approvals Part 2 of 2 panel is used to:

• Notify an approver that there is a package awaiting for their approval.

• Allow queries for packages awaiting approval based on TSO userids entered in User(s) to Notify.

These rules apply when you are setting up approval notifications:

• Approver notification is not required for an approval.

• You can create multiple notifications for an approval.

• You can create multiple notifications using the same vehicle.

DEFINING APPLICATION SITES

A site specifies target information for a promotion process or an install process. A site may be local or remote.

Sites are defined in global administration. Application Administrates select sites for an application from those global definitions. ChangeMan ZMF permits you to alter a site definition at the application level, but

Sites are selected from those global administration definitions for use in an application.

You must define an application site for each production ChangeMan ZMF environment that is a target for installs. Every promotion level definition must include a site.

Defining Sites For A New Application

Perform these steps to defines sites for a new application.

User(s) to Notify Type the appropriate user identifications for the notification vehicle. Separate multiple user identifications with commas.:

E-mail Address or Mailing List

TSO Userid

Use with the SERNET vehicle. Also use with the BATCH vehicle of REXX program CMNSMTP has been activated in skeleton CMN$$NTF.

Use for vehicle MVSSEND,

Local Site A target that is on the same LPAR as the development ChangeMan ZMF instance.

A target on a different LPAR can be defined as a local site if it shares DASD and catalogs with the ChangeMan ZMF development LPAR and no DB2 binds are required.

Remote Site A target that is on a different LPAR than the development ChangeMan ZMF instance, or that requires DB2 binds.

Field Description

130


1. On the Application Administration Options panel, type 8 on the Option line and press ENTER. The Application Site List Part 1 of 2 panel is displayed. The first time you access this panel to define sites for a new application, the panel is empty:

2. Type * in the line command for the first blank Site Name and press ENTER. The Global Site Selection List panel is displayed:

3. On the Global Site Selection List panel, type S in the line command for one or more global sites that you want to define in the new application. Press ENTER, and all selected sites are added to the Application Site Part 1 of 2 panel at the insertion point.

4. Continue selecting sites from the Global Site Selection List panel until all sites needed for the application are listed on the Application Site Part 1 of 2 panel.

CMNCLRST -------------- DEMO - SITE LIST PART 1 OF 2 ------- Row 1 to 12 of 12 COMMAND ===> SCROLL ===> PAGE Enter END command to save changes or CANCEL to exit. Enter * in line command field for global list. SITE NAME '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ '''' ________ ******************************* Bottom of data ********************************

CMNGRSTL ----------------- GLOBAL SITE SELECTION LIST -------- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> PAGE SITE NAME _ Q510DP _ N510DP _ LOCAL01 ******************************* Bottom of data ********************************

131


5. There is a second panel of information for each site on the Application Site Part 1 of 2 panel. Type S in the line command for a site and press ENTER. The Application Site Information List Part 2 of 2 panel is displayed:

6. The jobcard information displayed on the Application Site Information Part 2 of 2 panel is used to build JCL for jobs that run at the selected site. Update this information as required.

7. When you are finished updating the jobcard information Application Site Information Part 2 of 2 panel, press ENTER to return to the Application Site List Part 1 of 2 panel.

8. When you are finished updating site definitions on the Application Site List Part 1 of 2 panel, press PF-3 or type END and press ENTER to store the site definitions in the ChangeMan ZMF Package Master file.

Updating Application Site Information

Perform these steps to update application site definitions.

1. On the Application Administration Options panel, type 8 on the Option line and press ENTER. The Application Site List Part 1 of 2 panel is displayed:

2. To delete an application site on the Application Site List Part 1 of 2 panel, type D (Delete) in the line command for the site and press ENTER.

3. To add a library type on the Application Site List Part 1 of 2 panel:

a) Type I (Insert) in the line command above where you want to insert the site and press ENTER. An empty site entry is inserted on the panel.

CMNRSTJB ---------- LOCAL01 SITE INFORMATION - PART 2 OF 2 -------------------- COMMAND ===> SITE JOB STATEMENT INFORMATION: ===> //CMNSTART JOB (X170,374),APPL-DEMO,____________________________________ ===> // CLASS=U,MSGCLASS=9_______________________________________ ===> //* JOBCARD FROM DEMO APPL PARMS 3 OF 3 PANEL CMNGLP03__________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.

CMNCLRST -------------- DEMO - SITE LIST PART 1 OF 2 --------- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> PAGE Enter END command to save changes or CANCEL to exit. Enter * in line command field for global list. SITE NAME '''' Q510DP__ '''' N510DP__ '''' LOCAL01_ ******************************* Bottom of data ********************************

132


b) Type * in the line command for the site definition and press ENTER. The Global Remote Site Selection List panel is displayed:

c) On the Global Site Selection List panel, type S in the line command for one or more global sites that you want to add to the application. Press ENTER, and all selected sites are added to the Application Site Part 1 of 2 panel at the insertion point.

4. To update jobcard information for a site, type S in the line command for a site on the Application Site Part 1 of 2 panel and press ENTER. The Application Site Information List Part 2 of 2 panel is displayed:

The jobcard information displayed on the this panel is used to build JCL for jobs that run at the selected site.

5. When you are finished updating the jobcard information Site Information Part 2 of 2 panel, press ENTER to return to the Application Site List Part 1 of 2 panel.

6. When you are finished updating site definitions on the Application Site List Part 1 of 2 panel, press PF-3 or type END and press ENTER to store the site definitions in the ChangeMan ZMF Package Master file.

CONFIGURING PROMOTION SITES, LEVELS, AND LIBRARIES

The Application Administrator configures promotion for an application by defining a hierarchy of sites, promotion levels, library types, and test library names. When developers, project managers, and test coordinators promote or demote a package in the application, they choose a site and a promotion level as the target for their action.

For a discussion of the Promotion function, see “Promotion And Demotion” on page 41.

CMNGRSTL ----------------- GLOBAL SITE SELECTION LIST -------- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> PAGE SITE NAME _ Q510DP _ N510DP _ LOCAL01 ******************************* Bottom of data ********************************

CMNRSTJB ---------- LOCAL01 SITE INFORMATION - PART 2 OF 2 -------------------- COMMAND ===> SITE JOB STATEMENT INFORMATION: ===> //CMNSTAR JOB (X170,374),'GLOBAL LOCAL01 SITE',TIME=1,_________________ ===> // CLASS=A,MSGCLASS=9______________________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.

133


Promotion Definition Order

The order that promotion sites, levels, and library types appear on application administration panels determines the order that promotion libraries are concatenated in batch job JCL.

The following table lists some library concatenations that depend on the promotion definition order.

Configuring Promotion For A New Application

Perform these steps to set up promotion for a new application.

JCL ddname Library Type Used in batch jobs...

SYSLIB LIKE-C types Copybook expansion steps running CMNWRITE

Copybook libraries in compile and assemble jobs

Copybook libraries in BMS MAP gens

Copybook libraries in IMS PSB/DBD gens

SYSLIB LIKE-L types Load libraries in link edit

Load libraries in IMS PSB/DBD gens

INCLIB Target Type Load libraries in link edit.

OBJLIB Object library types defined in skeleton CMN$$VAR

Object libraries in link edit

134


1. On the Application Administration Option panel, type 7 on the Option line and press ENTER. The Application Promotion Site List panel is displayed. When this panel is first accessed for a new application, it is empty:

2. To populate the Application Promotion Site List panel, type * in the line command for the first empty Site Name entry and press ENTER. The Application Site Selection List panel is displayed:

3. On the Application Site Selection List panel, type S in the line command for each site that you want to define as a promotion target for the new application. Press ENTER, and you return to the Application Promotion Site List panel, where the selected sites are displayed.

CMNLRPMS --------------- DEMO - PROMOTION SITE LIST ---------- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> HALF Enter END command to save changes or CANCEL to exit. Enter * in line command field for local list. FORCE INTERNAL READER CLASS SITE NAME DEMOTION (Y/N) SITE LOCAL '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ ******************************* Bottom of data ********************************

CMNRMTSL --------------- DEMO - SITE SELECTION LIST ---------- Row 1 to 2 of 2 COMMAND ===> SCROLL ===> PAGE SITE NAME _ Q510DP _ N510DP _ LOCAL01 ******************************* Bottom of data ********************************

135


4. Complete the other fields on the Application Promotion Site List panel. The following table describes the fields on that panel.

Field Description


S

I

R

D

*

Select to see the next panel for this site.

Insert a blank site row.

Repeat an existing site.

Delete an existing site.

Display a selection list of available sites.

SITE NAME Displays the promotion site nickname copied from an application site definition.

FORCE DEMOTION (Y/N)

Defines the rules for promoting a package to more than one site at the same time

N

Y

Allow a package to be promoted to this site at the same time it is promoted to another site.

Require a package to be demoted in all other sites before it can be promoted to this site. Require a package promoted to this site to be demoted before it may be promoted in another site.

INTERNAL READER CLASS

Defines the output class for submitting job JCL to the internal reader. Promote/demote to a remote site runs jobs at the target site and on the MVS image where ChangeMan ZMF runs.

SITE: Output class for jobs submitted to the internal reader at a remote site. This entry is not used for local sites, but it must always be entered.

LOCAL: Output class for jobs submitted to the internal reader on the MVS image where ChangeMan ZMF runs.

136


5. When you have finished entering site information on the Application Promotion Site List panel, it might look like this.

6. You must define promotion levels for each promotion site. On the Application Promotion Site List panel, type S in the line command for a Site Name, and press ENTER. The Application/Site Promotion Levels panel is displayed. When this panel is first displayed for a site, it is empty:

CMNLRPMS --------------- DEMO - PROMOTION SITE LIST ---------- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> HALF Enter END command to save changes or CANCEL to exit. Enter * in line command field for local list. FORCE INTERNAL READER CLASS SITE NAME DEMOTION (Y/N) SITE LOCAL '''' Q510DP__ N A A '''' N510DP__ N A A '''' LOCAL01_ Y A A '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ '''' ________ _ _ _ ******************************* Bottom of data ********************************

CMNLRPM2 ------------ DEMO/Q510DP - PROMOTION LEVELS ------- Row 1 to 12 of 12 COMMAND ===> SCROLL ===> PAGE Enter END command to save changes or CANCEL to exit. NICKNAME ENTITY LEVEL PROCEDURE (* for a list) '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ ******************************* Bottom of data ********************************

137


7. Complete a promotion level entry for each promotion environment you want for this application in this site. The table that follows describes fields on the Application/Site Promotion Levels panel.

8. When you have completed defining promotion levels on the Application/Site Promotion Levels panel, might look like this.

Field Description


S

I

R

D

Select to see the next panel for this promotion level.

Insert a blank promotion level row.

Repeat an existing level.

Delete an existing level.

NICKNAME Type a nickname for the promotion level. Use a nickname that expresses the function of the promotion site, such as UNIT10 for Unit Test at Promotion Level 10.

ENTITY Type a promotion security entity name. This security entity is used with your security system to authorize a TSO userid to promote/demote to this level.

LEVEL Type a numeric promotion level. Number promotion levels in increments of 5 or 10 so that more levels can be added in between later.

PROCEDURE Type the name of the skeleton procedure to be used in ISPF file tailoring to build JCL for promotion jobs.

CMN$$PRM

CMN$$RPM

For promotion levels with libraries on a local site. If no entry is made, ChangeMan ZMF automatically inserts this skeleton name.

For promotion levels with libraries on a remote site.

--------------------- DEMO/Q510DP - PROMOTION LEVELS ------- Row 1 to 12 of 12 COMMAND ===> SCROLL ===> PAGE Enter END command to save changes or CANCEL to exit. NICKNAME ENTITY LEVEL PROCEDURE (* for a list) '''' UNIT10__ ALLDEV__ 10 CMN$$PRM '''' UNIT20__ ALLDEV__ 20 CMN$$PRM '''' SYSTST30 PROJMGR_ 30 CMN$$PRM '''' QATEST40 QAMGR___ 40 CMN$$PRM '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ '''' ________ ________ __ ________ ******************************* Bottom of data ********************************

138


9. For each promotion level on the Application/Site Promotion Levels panel you must define target library types and data set names. Type S on the line command of a promotion level, and the Application/Site Promotion Libraries panel is displayed. The first time this panel is displayed for a promotion level it is blank:

10. To add library types on the Application/Site Promotion Libraries panel, type * in the line command for the first blank entry on the panel and press ENTER. The Library Type Selection List panel is displayed:.

------------------- DEMO/N510DP - PROMOTION LIBRARIES ------ Row 1 to 3 of 12 COMMAND ===> SCROLL ===> PAGE Enter END command to save changes or CANCEL to exit. PROMOTION NAME: UNIT10 LEVEL: 10 Enter * in line command field for library type selection list. SYSLIB LIB EXCLUDE TARGET LIBRARIES '''' ___ _ ____________________________________________ Shadow ____________________________________________ Library 1 ____________________________________________ Library 2 ____________________________________________ Library 3 '''' ___ _ ____________________________________________ Shadow ____________________________________________ Library 1 ____________________________________________ Library 2 ____________________________________________ Library 3 '''' ___ _ ____________________________________________ Shadow ____________________________________________ Library 1 ____________________________________________ Library 2 ____________________________________________ Library 3

CMNLTPSL ---------------- LIBRARY TYPE SELECTION LIST ----- Row 1 to 19 of 151 COMMAND ===> SCROLL ===> PAGE LIB DESCRIPTION _ CPY Copybooks _ CTC Control Statements (PARMLIB) _ DBB DB2 Bind Control _ DBR DB2 DBRM _ JCL Job Execution JCL _ LCT Link Edit Control Statements _ LST Compressed Stage Listings _ LOD Load Modules _ MAP BMS MAP Load Modules _ MPC BMS MAP Copybook (DSECT) _ MPS BMS MAP Source _ OBJ Object Code _ PRC JCL Cataloged Procedures _ PKG DB2 Package Bind Control _ SKL ISPF Skeletons _ SRC Source Code _ TST Test Library Type

139


d) On the Library Type Selection List panel, type S in the line command for any application library type that you want to add at the insert point on the Application/Site Promotion Libraries panel. You may select multiple library types, but you can not scroll down to select library types from multiple pages of the Library Type Selection List at one time.

Promotion library types usually include executable library types that are tested. However, you may also wish to promote other types to allow for checkout from promotion.

e) Press ENTER to return to the Application/Site Promotion Libraries panel, where the new library types have been added at the insertion point.

11. On the Application/Site Promotion Libraries panel, type information in the remaining fields for each library type. The following table describes the fields on the Application/Site Promotion Libraries panel.

Field Description

PROMOTION NAME

Promotion nickname selected on the previous panel.

LEVEL Promotion level defined on the previous panel.


I

R

D

*


Repeat an existing library type.

Delete an existing library type.

Display a selection list of available library types.

LIB Application library type for this promotion level.

SYSLIB EXCLUDE Determines if promotion libraries associated with this library type are excluded from file tailoring during stage, recompile, and relink. Use this parameter to omit Like-Copy and Like-Load from SYSLIB concatenations. These libraries are also excluded from Audit.

If you change this flag during a package lifecycle, Audit may find SYNCH15!

Y

N

Exclude promotion libraries from file tailoring at stage, recompile, and relink. Exclude the libraries from Audit processing.

Include library in normal processing.

TARGET LIBRARIES

Shadow

Library 1Library 2Library 3

Type the fully qualified data set names of target promotion libraries.

A shadow library is a library on the local site that is synchronized with promotion libraries at the remote site. If you leave the shadow library blank, the DSN coded for Library 1 is copied into the shadow library name.

A shadow library is required if remote promotion skeleton CMN$$RPM is specified for a promotion level. A shadow library will not be updated if skeleton CMN$$PRM is specified for a promotion level.

Up to three promotion libraries may be targeted for each library type.

140


Promotion library types usually include executable library types. However, you may wish to promote other types to allow for checkout from promotion.

12. To save the new application promotion definition:

a) On the Application/Site Promotion Libraries panel, press PF-3 or type END on the Command Line and press Enter.

b) On the Application/Site Promotion Levels panel, press PF-3 or type END on the Command Line and press Enter.

c) On the Application Promotion Site List panel, press PF-3 or type END on the Command Line and press Enter.

Update Promotion For An Application

Perform these steps to update the promotion definitions for an application.

1. On the Application Administration Option panel, type 7 on the Option line and press ENTER. The Application Promotion Site List panel is displayed:

See the table that starts on page page 135 that describes the fields on Application Promotion Site List panel.

2. To delete a site from the Application Promotion Site List panel, type D (Delete) in the line command for the site and press ENTER.

3. To add a site to the Application Promotion Site List panel:

a) Type I (Insert) in the line command above where you want to insert the site and press ENTER. An empty site row is inserted on the panel.

CMNLRPMS --------------- DEMO - PROMOTION SITE LIST ---------- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> HALF Enter END command to save changes or CANCEL to exit. Enter * in line command field for local list. FORCE INTERNAL READER CLASS SITE NAME DEMOTION (Y/N) SITE LOCAL '''' Q510DP__ N A A '''' N510DP__ N A A '''' LOCAL01_ Y A A ******************************* Bottom of data ********************************

141


b) Type * in the line command for the empty site definition and press ENTER. The Application Site Selection List panel is displayed:

4. On the Application Site Selection List panel, type S in the line command for each site that you want to add. Press Enter, and you return to the Application Promotion Site List panel, where the selected sites are displayed.

5. Complete the other fields on the Application Promotion Site List panel.

6. To update promotion levels for a promotion site., on the Application Promotion Site List panel, type S in the line command for a Site Name, and press ENTER. The Application/Site Promotion Levels panel is displayed:

See the table that starts on page page 137 for a description of the fields on this panel.

7. Complete the other fields on the Application/Site Promotion Levels panel.

CMNRMTSL --------------- DEMO - SITE SELECTION LIST ---------- Row 1 to 2 of 2 COMMAND ===> SCROLL ===> PAGE SITE NAME _ Q510DP _ N510DP _ LOCAL01 ******************************* Bottom of data ********************************

--------------------- DEMO/Q510DP - PROMOTION LEVELS ------- Row 1 to 12 of 12 COMMAND ===> SCROLL ===> PAGE Enter END command to save changes or CANCEL to exit. NICKNAME ENTITY LEVEL PROCEDURE (* for a list) '''' UNIT10__ ALLDEV__ 10 CMN$$PRM '''' UNIT20__ ALLDEV__ 20 CMN$$PRM '''' SYSTST30 PROJMGR_ 30 CMN$$PRM '''' QATEST40 QAMGR___ 40 CMN$$PRM ******************************* Bottom of data ********************************

142


8. To update the library types and promotion libraries for a promotion level, on the Application/Site Promotion Levels panel, type S on the line command for a promotion level, and the Application/Site Promotion Libraries panel is displayed:

See the table that starts on page page 139 for a description of the fields on this panel.

9. To delete a library type with its promotion libraries from the Application/Site Promotion Libraries panel, type D (Delete) in the line command for the library type and press ENTER.

10. To add a library type with promotion libraries to the Application/Site Promotion Libraries panel:

a) Type I (Insert) in the line command above where you want to insert the library type and press ENTER. An empty library type row is inserted on the panel.

CMNLRPM3 ----------- DEMO/N510DP - PROMOTION LIBRARIES ------- Row 1 to 3 of 4 COMMAND ===> SCROLL ===> PAGE Enter END command to save changes or CANCEL to exit. PROMOTION NAME: UNIT10 LEVEL: 10 Enter * in line command field for library type selection list. SYSLIB LIB EXCLUDE TARGET LIBRARIES '''' JCL N PROD239.SERN510D.NLOCLV10.JCL_______________ Shadow PROD239.SERN510D.NLOCLV10.JCL_______________ Library 1 ____________________________________________ Library 2 ____________________________________________ Library 3 '''' LOD Y PROD239.SERN510D.NLOCLV10.LOD_______________ Shadow PROD239.SERN510D.NLOCLV10.LOD_______________ Library 1 ____________________________________________ Library 2 ____________________________________________ Library 3 '''' MAP Y PROD239.SERN510D.NLOCLV10.map_______________ Shadow PROD239.SERN510D.NLOCLV10.map_______________ Library 1 ____________________________________________ Library 2 ____________________________________________ Library 3

143


b) Type * in the line command for the empty library type row and press ENTER. The Application Site Selection List panel is displayed:

c) On the Library Type Selection List panel, type S in the line command for any application library type that you want to add at the insert point on the Application/Site Promotion Libraries panel. You may select multiple library types, but you can not scroll down to select library types from multiple pages of the Library Type Selection List at one time.

Promotion library types usually include executable library types that are tested. However, you may also wish to promote other types to allow for checkout from promotion.

d) Press ENTER to return to the Application/Site Promotion Libraries panel, where the new library types have been added at the insertion point.

11. Complete the rest of the fields on the Application/Site Promotion Libraries panel.

12. To save your updates to the application promotion definition:

a) On the Application/Site Promotion Libraries panel, press PF-3 or type END on the Command Line and press Enter.

b) On the Application/Site Promotion Levels panel, press PF-3 or type END on the Command Line and press Enter.

c) On the Application Promotion Site List panel, press PF-3 or type END on the Command Line and press Enter.

CMNLTPSL ---------------- LIBRARY TYPE SELECTION LIST ----- Row 1 to 19 of 151 COMMAND ===> SCROLL ===> PAGE LIB DESCRIPTION _ CPY Copybooks _ CTC Control Statements (PARMLIB) _ DBB DB2 Bind Control _ DBR DB2 DBRM _ JCL Job Execution JCL _ LCT Link Edit Control Statements _ LST Compressed Stage Listings _ LOD Load Modules _ MAP BMS MAP Load Modules _ MPC BMS MAP Copybook (DSECT) _ MPS BMS MAP Source _ OBJ Object Code _ PRC JCL Cataloged Procedures _ PKG DB2 Package Bind Control _ SKL ISPF Skeletons _ SRC Source Code _ TST Test Library Type

144


CONFIGURING BASELINE LIBRARIES

With Option B on the Application Administration Options panel, you can specify the names of an application's Baseline libraries. ChangeMan ZMF uses these names when it creates batch jobs to “ripple” an application's Baseline libraries after a change package has been installed. ChangeMan ZMF assumes these libraries exist and that it can update them.

If you have set Application Parameters to “Keep Baseline by Site =Y” on Part 1 of the Application Parameters panel, then Baseline libraries must be configured for each site. See “Configuring Remote Sites” on page 173 for details.

Allocating Baseline Libraries

1. Select option B on the Application Administration Options panel. The Baseline Configuration Part 1 of 2 panel (CMNCBAS1) is displayed:

The following table describes the field of the Application Baseline Configuration Part 1 of 2 panel (CMNCBAS1) and the information that you can enter when creating a new libraries.

Field Description

TYPE Enter the library type. If you want to select from a list of available library types, enter *. The Library Type Selection List is displayed.

LEVELS Enter the number of previous levels that you want ChangeMan ZMF to maintain Baseline for each library type.

Note: If you specify the storage means as LA (CA-Librarian Archie), the level has a maximum of 255. You enter only one data set name, however, when you select this entry for specifying the actual Baseline data set name on the Application Baseline Configuration Part 2 of 2 panel described below.

CMNCBAS1 --- DEMO - BASELINE CONFIGURATION PART 1 OF 2 ----- ROW 1 TO 5 OF 5 COMMAND ===> SCROLL ===> PAGE Enter END command to save changes or CANCEL to exit. Enter * in line command field for library type selection list. BASELINE STORAGE MEANS INSTALL P-Standard PDS PV-Panvalet IN PROD L-Librarian LA-Librarian Archie TYPE LEVELS (Y/N/C) SD-Stacked Reverse Delta ‘’’’ CPY 3__ Y SD ‘’’’ JCL 3__ Y SD ‘’’’ LOD 3__ Y P_ ‘’’’ PRC 3__ Y SD ‘’’’ SRC 3__ Y SD ******************************* Bottom of data ********************************

145


2. To update an existing library, type S to select a row to specify the actual data set names for the item. The Application Baseline Configuration Part 2 of 2 panel (CMNCBAS2) is displayed:

The Application Baseline Configuration Part 2 of 2 panel (CMNCBAS2) specifies the names of an application's Baseline libraries. The rows are already generated when you access the panel. From this panel you can verify or allocate the Baseline library data sets. ChangeMan ZMF uses these names when it creates batch jobs to “ripple” an application's Baseline libraries after a change package has been installed. ChangeMan ZMF assumes these libraries exist and that it can update them.

If you have set “Keep Baseline by Site = Y” on the Application Parameter Part 1 of 2 panel (CMNGLP01) then Baseline libraries must be configured for each site. “Configuring Remote Sites” on page 173.

INSTALL IN PRD This option is for installation in production.

Enter Y (Yes) if the library type is to be included in Production libraries as change packages are installed.

Enter Y to install temporary packages for ALL sites.

Enter N (No) if the library type is only maintained in a development environment.

If you want to make Baseline and Production the same physical site, mark all of the rows of this column N, and leave the Production Libraries panels blank.

Enter C (Conditional) if the library type exists in a remote site. The library type noted is installed in that remote site.

STORAGE MEANS Enter one of the following storage means:

P - PDS

L - CA-Librarian

LA - CA-Librarian Archie

PV - CA-Panvalet

SD - Stacked Reverse Delta

Note: Delta libraries must be RECFM=FB.

Field Description

CMNCBAS2 --- DEMO - BASELINE CONFIGURATION PART 2 OF 2 ----- ROW 1 TO 2 OF 2COMMAND ===> SCROLL ===> CSR


LIBRARY TYPE: SRC - 255 LEVELS MAINTAINEDSTORAGE MEANS: SDLINE COMMANDS: A - Allocate, V - Verify

LEVEL DATASET NAME STATUS_ 0 PROD99.CMN416.ASSEMBLE_______________________ -254 PROD99.CMN416.DELTA.ASSEMBLE________________******************************* BOTTOM OF DATA ********************************

146


3. In a desired row of the Application Parameter Part 1 of 2 panel (CMNGLP01), type A or V to allocate or verify a baseline library.

Note This option is not available for CA-Librarian or CA-Panvalet.

• If you typed V in the desired row, the Dataset Information panel (CMNDSINF) is displayed:

• If you typed A, in the desired row, the Allocate Dataset panel (CMNALCDS) is displayed)

If a Baseline library data set does not exist, the message “Data set not catalogued” displays in the upper right-hand corner, and *ERROR is displayed in the STATUS column next to the data set name.

CMNDSINF-------------------- DATASET INFORMATION -----------------------------COMMAND ===>

LIBRARY TYPE: SRCDATASET NAME: PROD99.CMN416.ASSEMBLE

GENERAL DATA: CURRENT ALLOCATION: VOLUME SERIAL: STR84F ALLOCATED CYLINDERS: 99 DEVICE TYPE: 3380 ALLOCATED EXTENTS: 6 ORGANIZATION: PDS MAX. DIR. BLOCKS: 60 RECORD FORMAT: FB RECORD LENGTH: 80 BLOCK SIZE: 6000 CURRENT UTILIZATION: 1ST EXTENT CYLINDERS: 39 USED CYLINDERS: 88 SECONDARY CYLINDERS: 12 USED EXTENTS: 6 USED DIR BLOCKS: 32DATASET DATE INFORMATION: NUMBER OF MEMBERS: 191 CREATION: 1998/01/06 EXPIRATION: LAST REFERENCED: 1999/06/14

CMNALCDS ---------------------- ALLOCATE DATASET ------------------------------COMMAND ===>

LIBRARY TYPE: SRCDATASET NAME: PROD99.CMN416.ASSEMBLE

GENERIC UNIT NAME ===> 3390 (Generic group name or unit) VOLUME SERIAL ===> (Required if GENERIC UNIT unspecified) SPACE UNITS ===> TRK (TRK, CYL or BLK) PRIMARY QUANTITY ===> 10 (In above units) SECONDARY QUANTITY ===> 10 (In above units) DIRECTORY BLOCKS ===> 50 (Must be greater than zero) RECORD FORMAT ===> FB RECORD LENGTH ===> 80 BLOCK SIZE ===> 6000 DATA SET TYPE ===> (Library for PDSE, PDS for PDS, or Blank) Press ENTER to allocate; Enter END command to cancel.

147


DEFINING OPTIONAL COMPONENT DESCRIPTIONS, PROCEDURE, AND SECURITY

With Option C, you can define optional components for your applications so that you can do the following:

• Provide general information about the optional component that allows the user to enter or update descriptions for the application's components from either a Baseline driven list or the Package Master driven list of components.

• Specify component designated compiling procedures that allows the user to specify the required compile procedure to be used before a package can be frozen.

• Set security information for the component that allows the user to limit access to the application's components by entering those TSO ID’s or entities that are authorized to stage each component.

These records are keyed (made unique) by component name and library type. They are NOT keyed by application. Therefore, Application Administrators can overlay each other's records.

Any entries made here apply across all applications.

Select whether to define General, Procedures, or Security information on the Component Information Options panel.

1. On the Application Administration Options panel, select option C. The Application Component Information Options menu (CMNCMP00) is displayed:

DEFINING COMPONENT GENERAL INFORMATION

You can define and update component descriptions. To select the components that you want to define or update, follow these steps:

CMNCMP00 ---------- DEMO - COMPONENT INFORMATION OPTIONS ----------------------OPTION ===>

G General - Update component general information P Procedures - Specify component designated compile procedures S Security - Maintain component level security information

Press ENTER to process; Enter END command to exit.

NOTE: Component Information Options affect ALL applications.

148


1. Select option G on the Application Component General Information panel (CMNCMP00). The Application Component General Information panel (CMNCMPG1) is displayed:

2. At the command line, type 1 (to access the Baseline Driven Component List) or 2 (to access the Package Master Component List), and in a library type in the LIBRARY TYPE field, type a library type.

If you leave the LIBRARY TYPE field blank, the Library Type Selection List panel (CMNLTPSL) displays, and you must select a library type before the Baseline or package driven lists display.

3. Press ENTER.

• If you chose option 1, the Baseline Driven Component List panel is displayed:

• If you chose option 2, the Package Master Driven Component List panel (CMNCMP01) is displayed:

CMNCMPG1 ---------- DEMO - COMPONENT GENERAL INFORMATION ----------------------OPTION ===>

LIBRARY TYPE ===> (Blank for list)

1 Baseline - Select from baseline libraries 2 Package - Process existing component information records


CMNCMPG2 ST - SER.CMNQ.BASE0.PDS -------------------------- ROW 1 TO 20 OF 38 COMMAND ===> SCROLL ===> CSR NAME STATUS VV.MM CREATED LAST MODIFIED SIZE INIT MOD ID _ AAAAAAA7 02.01 92/02/22 93/05/27 15:15 1 10 10 SER05 _ AAAAAA6 02.01 92/02/22 93/05/27 15:16 2 10 8 SER05 _ AAAAA5 02.01 92/02/22 93/05/27 15:16 3 10 7 SER05 _ AAAA4 02.01 92/02/22 93/05/27 15:16 4 10 6 SER05 _ AAA3 02.01 92/02/22 93/05/27 15:17 5 10 6 SER05 _ AA2 02.01 92/02/22 93/05/27 15:17 6 10 5 SER05

CMNCMP01 ----------------------- COMPONENT LIST ----------- ROW 1 TO 17 OF 17COMMAND ===> SCROLL ===> CSR

NAME TYPE_ CMNADMSO SRC_ CMNAPI2 SRC_ CMNATACH SRC_ CMNAUD10 SRC_ CMNBATCH SRC_ CMNBSAM SRC_ ******************************* BOTTOM OF DATA ********************************

149


Deleting Components

1. From either the Baseline or Package Master Driven Component Lists, place the cursor in the first column of the library row that you want to change.

2. Type a D in the first column of the desired row in the list to delete a component description. The component row is deleted.

3. Press [END].

If you are working on the Baseline Driven Component List and you have set “Keep Baseline by Site = N” on Part 1 of the Application Parameters panel, ChangeMan ZMF returns you to the Component General Information panel.

If you are working on the Baseline Driven Component List and you have set “Keep Baseline by Site = Y” on Part 1 of the Application Parameters panel, the Remote Site Selection List displays so that you can choose another site for component updates. Repeat this procedure for each site you wish to update.

If you are working on the Package Master Driven Component List, ChangeMan ZMF returns you to the Component General Information panel.

Updating the components in either component list.

1. From either the Baseline or Package Master Driven Component Lists, place the cursor in the first column of the library row that you want to change and type S.

2. Press [ENTER]. The Component General Description panel (CMNCMPG3) is displayed:

3. Type in a general description of the component.

4. Press END. This saves your changes and returns you to the Baseline or Package Master Driven Component Lists. The STATUS column next to the selected component name in the list now displays CHANGED.

Repeat these steps for each approval row that you want to change.

CMNCMPG3 ------ C410 - CMNAUD10.SRC GENERAL DESCRIPTION --- ROW 1 TO 13 OF 13COMMAND ===> SCROLL ===> CSR

Enter END command to save; CANCEL to exit.

(maximum 48 lines)'''' This program gathers all the data for the Audit Process_________________'''' ________________________________________________________________________'''' ________________________________________________________________________'''' ________________________________________________________________________******************************* BOTTOM OF DATA ********************************

150


DESIGNATE OPTIONAL COMPONENT COMPILING PROCEDURES

1. Select option P on the Component Information Option panel. The Designate Compiling Procedures panel is displayed.

If you choose to designate compiling procedures for the application's components, then any user that wants to freeze a change package with the selected component must stage with the procedures entered on the panel (force level 2). If you designate a compiling procedure with force level 1, ChangeMan ZMF allows staging with alternate procedures during package development. However, the final stage (before attempting to freeze) should be performed with the designated compile procedure for each component.

The following table describes the field of the Designated Compile Procedures panel (CMNCMPP1).

Field Description

COMPONENT NAME

Enter the full component name or pattern masked name. The pattern can be a combination of letters and an “*” to indicate wildcard information. The first character, however, must be a letter. For example, A* is acceptable, but * is not.

LIBRARY TYPE Enter the library type. If you want to select from a list of library types, enter a blank in this field. The Library Type Selection List is displayed.

This must be either SRC (source) or any of the application's library types that have been set up to be handled “like source.”

COMPILE PROCEDURE

Enter the compiling procedure name. If you want to select from a list of compiling procedures, enter a blank in this field. The Compiling Procedure Selection List is displayed.

You can set up as many or as few compiling procedures as you need.

LANGUAGE NAME Enter the language name. If you want to select from a list of language names, enter a blank in this field. The Language Name Selection List is displayed.

CMNCMPP1 ---------- DEMO - DESIGNATED COMPILE PROCEDURES ---------------------- OPTION ===> C - Change or Add component procedures D - Delete component procedures blank - List defined procedures COMPONENT NAME ===> (Full name or pattern; blank for list) LIBRARY TYPE ===> (Blank for list) COMPILE PROCEDURE ===> (Blank for list) LANGUAGE NAME ===> (Blank for list) COMPILE PARMS ===> LINK EDIT PARMS ===> DB2 PRE-COMPILE ===> (Y/N) OTHER OPTIONS ===> (Y/N for additional user options) FORCE LEVEL ===> (1-Before Freeze only, 2-Always required) Press ENTER to process; Enter END command to exit.

151


2. From this panel, if you know the name of the component for which you are designating procedures, you can update the information from this panel, type C at the command line to change a component's procedure and provide the component name in the COMPONENT NAME field as well as type in entries in each of the required fields of the panel.

If you don’t know the name of the component, type a pattern or a blank in the COMPONENT NAME field on the Designated Compiling Procedure panel.

COMPILE PARMS Enter the compiling parameters.

LINK EDIT PARMS Enter the link edit parameters.

DB2 PRE-COMPILE

Enter YES if a DB2 pre-compile is required.

Enter NO if a DB2 pre-compile is not required.

OTHER OPTIONS The User Options facility allows you to modify the logic within a single ChangeMan ZMF skeleton and tailor that skeleton to fit the processing requirements of many kinds of compile and link procedures.

FORCE LEVEL Specify the force option:

Enter 1 to let users compile the component with alternate procedures (before the last compile prior to freeze).

Users can use any procedure, any compile and link parameters and any user options during staging. However, audit and freeze validate each component and ensure that this designated procedure was used for the final stage. Otherwise, the package fails audit and is not available for freeze.

Enter 2 to require users to always use the designated procedure.

Field Description

152


3. Press [ENTER]. The Component List panel (CMNCMPP2) is displayed:

Complete the fields on the Component Driven List panel. The fields and behavior for this list are the same as the list on the Designated Compiling Procedure panel (even though the abbreviations for the columns differ slightly from the fields of the Designated Compiling Procedure panel).

You complete the fields using the same commands and requirements as the Designated Compiling Procedure panel, except you repeatedly specify component compiling procedures for component rows using the Select (to change and update) and Delete commands in the first column of the desired row on the list.

4. Press END. This saves your changes and returns you to the Designated Compiling Procedure panel.

SETTING COMPONENT SECURITY

ChangeMan ZMF lets you set component level security for a particular component or group of components. Before you specify this Component User List, you must first indicate which component you want to update.

Specify the component to be updated.

1. Select option S on the Component General Information panel. The Component Level Security panel is displayed.

2. Update and/or delete user component security access from the Component User List with one of the following methods (the results are the same for either method):

CMNCMPP2 ----------------- C410 - COMPONENT LIST ----------- ROW 1 TO 4 OF 27COMMAND ===> SCROLL ===> CSR

Enter END command to save changes or CANCEL to exit. Enter S line command to select additional options. Enter * in PROC or LANGUAGE field, for list.

NAME TYPE LANGUAGE LOD FORCE DB2 COMPILE PARMS PROC TYPE OPT PC LINK EDIT PARMS ------------------------------------------------------------------------_ C* SRC ASM LOD 1 NO __________________________________ CMNASM __________________________________ ------------------------------------------------------------------------_ CMN$XMEM SRC ASM LOD 2 NO __________________________________ CMNASM AC=1______________________________ ------------------------------------------------------------------------_ CMN* SRC ASM LOD 1 NO __________________________________ CMNASM __________________________________ ------------------------------------------------------------------------_ CMNATACH SRC ASM LOD 2 NO __________________________________ CMNASM AC=1______________________________

153


If you know the names of the components for which you are setting security, you can directly access the user list. To do so, follow these steps:

• Type the full component name in the COMPONENT NAME field.

• Type the component library type in the COMPONENT TYPE field.

3. Press ENTER. The Component User List panel is displayed. Go to task 3 to complete this panel.

Repeat this task for every component that you want to update.

If you do not know the names of the components or if you want to set security for a set of components of the same type with a common naming convention, you first access a Package Driven Security List.

Access a Package Driven Security List.

1. Type a pattern in the COMPONENT NAME field. The pattern can be a combination of letters and an “*” to indicate wild card information. An example is: S*.

If you leave this field blank, ChangeMan ZMF returns you to the Component Information Options panel.

2. Type the component library type in the COMPONENT TYPE field.

3. Press ENTER. The Component Level Security List panel (CMNCMPS1) is displayed:

Complete the Component Level Security Panel.

1. This panel is used to select package master components that are needed for security level information updates.

2. Type C and press ENTER at the command line to change a component's procedure. The Component User List panel is displayed.

3. Repeat this step for every component that you want to change.

Delete a component’s security entries.

1. Type D and press [ENTER] to delete a component's security entries. All of the component's security entries are deleted (if you access the Component User List for this component it is blank).

CMNCMPS1 ------------ DEMO - COMPONENT LEVEL SECURITY -------------------------COMMAND ===>

COMPONENT NAME ===> ABC10000 (Pattern or blank for list)COMPONENT TYPE ===> SRC (Pattern or blank for list)


154


2. Repeat this step for each component's security that you want to delete.

Delete, enter or update component secured ID’s.

Delete, enter, or update component secured user ID’s for either a Baseline library or the Package Master on the Component User List panel (CMNCMPS2).

Note When you protect the application's components only the user IDs entered in this panel are allowed to stage and checkout the selected component during change package development.

DELETING AN APPLICATION

Use Option D to confirm a user's request to delete an application. All packages must be physically deleted from an application before the application can be deleted. Packages in MEMO DELETE are considered to be logically deleted. You must run housekeeping to physically delete the logically deleted (MEMO DELETED) packages from the application library.

Run Report 100, ‘Application Configuration Report,’ to get a list of all baseline and promotion libraries. Manually delete the libraries listed in Report 100, unless they are currently being used by another application.

Packages that are in motion can be deleted. Packages that have been installed and aged are deleted when the appropriate housekeeping task is executed.

Delete an application

1. Select option D on the Application Administration Options panel. The Confirm Delete panel (CMNDPROJ) is displayed.

CMNCMPS2 ----------- C410 - CMNATACH.SRC USER LIST ---------- ROW 1 TO 6 OF 6COMMAND ===> SCROLL ===> CSR


USERID ENTITY (Y/N; blank=N)'''' USER00__ N'''' USER02__ N'''' USER08__ N'''' USER06__ N'''' USER32__ N'''' USER05__ N******************************* BOTTOM OF DATA ********************************

155


2. Press [ENTER] to continue with the deletion or enter the END command to cancel the deletion.

The following table describes the fields of the Confirm Delete panel (CMNDPROJ).

ACCESSING THE APPLICATION SELECTABLE OPTIONS PANEL

Selecting Option O from CMNLAMEN is the same as selecting this option in CMNGAMEN. The only difference is that during application administration, you can access the Application Selectable Options panel (CMNGBSOP) instead of the Global Options panel. For more details, refer to the discussion in “Accessing the Global Selectable Options” on page 94 as well as the individual manuals that apply to those options.

UPDATING THE GLOBAL NOTIFICATION FILE

Administrators use the Global Notification facility to pass information to ChangeMan ZMF users. You can use this facility to inform users about:

• Scheduled down time.

• Scheduled maintenance changes to ChangeMan ZMF.

• Work-arounds for recently discovered problems.

• Upcoming ChangeMan ZMF education or discussion sessions.

Field Description

APPLICATION Displays the application mnemonic.

HIGHEST PACKAGE

Displays the application's highest package number.

RELEASE ID Displays the release ID.

CMNDPROJ ----------------------- CONFIRM DELETE -------------------------------COMMAND ===>

APPLICATION: DEMODESCRIPTION:HIGHEST PACKAGE:RELEASE ID:

Press ENTER key to confirm delete request;Enter END command to cancel delete request.

156


When a user connects to ChangeMan ZMF after an administrator updates the Global Notification File, this ISPF short message is displayed in the upper right corner of the Primary Option Menu: “NOTIFICATION UPDATED”. If the user presses PF1, this long message is displayed:

CMN1116I - Option-N file last updated 07/15/2002 13:57 last read 07/14/2002

The short message persists on the Primary Option Menu until the user selects option N (Notify) to display the Global Notification File.

The global administrator allocates the Global Notification File and enables the Global Notification Facility. Global administrators update the file with information for users, and they can grant application administrators the same privilege.

If the global administrator enabled the Global Notification facility and set the Allow Application Update To File field to Yes in global administration parameters, follow these steps to update the messages in the Global Notification File that is displayed to all ChangeMan ZMF users.

BROWSE WSER239.WSER239.D197B7EF.T36A5D91.OUTLIST Line 00000000 Col 001 080 Command ===> Scroll ===> HALF ********************************* Top of Data ********************************** Notification Date: 07/15/2002 ChangeMan ZMF will be unavailable between 0600 and 0700 on Sunday July 20 when Maintenance Package 58 will be applied. See the ChangeMan page on the Intranet for a description of the changes that will be made. ------------------------------------------------------------------------ Notification Date: 06/10/2002 ChangeMan ZMF will be unavailable between 0600 and 0700 on Sunday June 16 when Main ten ace Package 57 will be applied. See the ChangeMan page on the Intranet for a description of the changes that will be made. ******************************** Bottom of Data ********************************

157


1. From the Application Administration Options panel (CMNLAMEN), select option N. An ISPF edit session is opened for a ChangeMan ZMF temporary file that contains the current contents of the Global Notification File.

Note Although you can update the Global Notification File through the Application Administration Options panel, which may also display an application mnemonic, the updates you enter are displayed to all users of ChangeMan ZMF, not just to users with access to your application...

2. Using ISPF functions, insert lines to type new a new message that you want displayed to all ChangeMan ZMF users. Add new messages at the top of the file.


ISREDDE2 WSER239.WSER239.D197B7EF.T3BEC7B8.OUTLIST Columns 00001 00072 Command ===> Scroll ===> HALF ****** ***************************** Top of Data ****************************** ==MSG> -Warning- The UNDO command is not available until you change ==MSG> your edit profile using the command RECOVERY ON. 000001 000002 Notification Date: 06/10/2002 000003 000004 ChangeMan ZMF will be unavailable between 0600 and 0700 on Sunday June 000005 16 when Maintenance Package 57 will be applied. See the ChangeMan page on 000006 the Intranet for a description of the changes that will be made. 000007 ****** **************************** Bottom of Data ****************************

ISREDDE2 WSER239.WSER239.D197B7EF.T3C3AE58.OUTLIST Data set copied Command ===> Scroll ===> HALF ****** ***************************** Top of Data ****************************** ==MSG> -Warning- The UNDO command is not available until you change ==MSG> your edit profile using the command RECOVERY ON. 000001 000002 Notification Date: 07/15/2002 000003 000004 ChangeMan ZMF will be unavailable between 0600 and 0700 on Sunday July 000005 20 when Maintenance Package 58 will be applied. See the ChangeMan page on 000006 the Intranet for a description of the changes that will be made. 000007 000008 ------------------------------------------------------------------------ 000009 000010 Notification Date: 06/10/2002 000011 000012 ChangeMan ZMF will be unavailable between 0600 and 0700 on Sunday June 000013 16 when Maintenance Package 57 will be applied. See the ChangeMan page on 000014 the Intranet for a description of the changes that will be made. 000015 ****** **************************** Bottom of Data ****************************

158


CONFIGURING PRODUCTION LIBRARIES

With Option P from the Application Administration Options panel, ChangeMan ZMF lets you configure Production libraries by specifying the names of an application's Production libraries by the application’s type and site. When change packages are installed or backed out, ChangeMan ZMF uses these names to create batch jobs that update Production libraries. ChangeMan ZMF assumes these libraries already exist and that it can update them.

If you want to make baseline and production the same physical site, leave these lists blank and mark the entries under INSTALL IN PROD as N.

1. Select option P on the Application Administration Options panel. The Production Libraries panel (CMNCPRDL) is displayed:

2. Specify the names of the applications’ Production libraries. The following table describes the Production Libraries panel (CMNCPRDL).

3. Enter the END command.

Field Description

TYPE Enter the library type. If you want to select from a list of available library types or if you want to select more than one library type, enter *. The Library Type Selection List is displayed.

DATA SET NAME In each row enter the data set names (Production, Temporary, and Backup libraries, in that order) that ChangeMan ZMF is to associate with the library type (CPY, JCL, PRC, and so forth) for the application's Production libraries at the remote site.

If you selected Y in the Install in Prod field on the Baseline Configuration Part 1 of 2 (CMNCBAS1) panel to install temporary packages for ALL sites, enter NULLFILE in both the Production Dataset Name and Backup Dataset Name fields.

You can enter data set names that do not currently exist. However, during the building of actual application level change packages, the data sets must have been allocated on accessible packs or the build function aborts.

CMNCPRDL ---------- DEMO - PRODUCTION LIBRARIES ------------------------------COMMAND ===> SCROLL ===> CSR

Enter END command to save changes or CANCEL to exit.Enter * in line command field for library type selection list.

TYPE PRODUCTION DATASET NAME TEMPORARY DATASET NAME BACKUP DATASET NAME'''' ___ ____________________________________________ ____________________________________________ ____________________________________________

159


CONFIGURING TEMPORARY PACKAGES FOR ALL SITES

Define temporary packages for ALL site configurations.

1. On the Primary Option menu (CMN@PRIM), select option A. The Administrative Options panel (CMNADMOM) is displayed.

2. On the Administrative Options panel, select option A. The Application Administration Options panel (CMNLAMEN) is displayed.

3. On the Application Administration Options panel, enter the name of the application that you want to update in the Application field, and select option B, and press ENTER. The Configure Baseline Libraries (CMNCBAS1) panel is displayed.

4. On the Configure Baseline Libraries panel, enter Y or C in the Install in Prod field for each library type that you want in this application.

5. Press PF3 (END) to save your changes and return to the Application Administration Options panel.

6. On the Application Administration Options panel, select P to define your Production libraries for this application. The Production Libraries panel (CMNCPRDL) is displayed.

7. On the Production Libraries panel, enter NULLFILE in both the Production Dataset Name and Backup Dataset Name fields.

8. Enter the Temporary Dataset Name for each temporary Production library that you want to use.

9. Press ENTER.

160


161

CUSTOM MODIFICATIONS 6INITIAL SKELETON MODIFICATIONS

Serena recommends against including ChangeMan ZMF load libraries in the LINKLIST. Therefore, some ISPF skeletons must be modified to add a JOBCARD statement to batch jobs submitted by ChangeMan ZMF. Other skeletons must be modified to provide dataset names for system libraries that comply with local data center standards.

Initial skeleton customization is detailed in the Serena™ ChangeMan® ZMF Customization Guide.

CUSTOMIZING CHANGEMAN ZMFChangeMan ZMF provides a rules-based environment for software configuration management. Its architecture and design provide processes based on best practices for managing application components through the development lifecycle to guarantee the integrity of production systems and data. The basic definitions of ChangeMan ZMF processing rules established by settings in Global and Application Administration.

Serena recognize that SCM best practices can be expressed differently in different companies. ChangeMan ZMF architecture is intended to provide customers with the opportunity to modify details of the development lifecycle process. User exits provide you with access to core processes to expand the options. While user interfaces have expanded beyond the mainframe, many key functions are based on batch processing that can be modified to fit your requirements.

User Exits In ChangeMan ZMF

ChangeMan ZMF exits are programs that are called by base product programs. Exits permit you to alter the processing of base product programs depending on the information passed to the exit. Using exits, you can:

• Change defaults and settings for interaction with the operating system.

• Alter what ChangeMan ZMF will do under specific component, package, or life cycle conditions.

• Change who has authority to initiate specific ChangeMan ZMF tasks.

• Change when authorized users can initiate certain tasks.

162

Chapter 6: Custom Modifications

Common reasons for using exits include:

• Adapt ChangeMan ZMF to your data center standards and environment.

• Enforce your company’s standards, processes, and procedures for software change management.

• Implement custom processes to manage unique component build processes.

• Add rule-based flexibility to standard ChangeMan ZMF processing.

The use of exits to provide custom ChangeMan ZMF functions is described in the Serena™ ChangeMan® ZMF Customization Guide.

ISPF Skeletons In ChangeMan ZMF

ChangeMan ZMF uses standard ISPF services to build batch job JCL from ISPF skeletons. This approach provides extraordinary flexibility through the use of standard IBM facilities. You can build your own batch processes inside ChangeMan ZMF for component “builds” and other processes. ChangeMan ZMF maintains the integrity of your software change management environment by securing development and production libraries and allowing only authorized access to its functions.

Modification of ISPF skeletons to provide custom ChangeMan ZMF functions is described in the Serena™ ChangeMan® ZMF Customization Guide.

ChangeMan ZMF Utilities

Utility programs included in ChangeMan ZMF batch processes run under the control of program parameters and SYSIN keyword parameters. You can change utility parameters in delivered ChangeMan ZMF skeletons to adjust component processing to fit your standards and requirements. These utilities can also be included in custom skeletons to provide unique functions you design.

ChangeMan ZMF utilities are described in the Serena™ ChangeMan® ZMF Customization Guide.

163

MONITORING SITE AND APPLICATION PACKAGES 7

ChangeMan ZMF lets you monitor your site and applications for change package discrepancies as well as monitor and override user provided installation information. To access any of this functionality the security administrator must have given you access to the monitor functional area.

ChangeMan ZMF allows you to monitor your applications for change packages, which show discrepancies or abnormalities including the following:

• Distribution without distribution acknowledgment

• Installation date has passed

• Package in APR status in ALL environment

• Package in INS status in ALL environment

• Package status not being changed in TCC after duration

• All Complex/Super packages with OPN status

By querying the applications (or the site) for this information and marking them as being in limbo, you provide filtering criteria for the packages that you want to query.

Although the monitor function is similar to the query function, the functionality has been extended to let authorized users:

• Change install dates

• Change a package's status

• Edit and submit jobs to production

Change packages which have these discrepancies are considered to be in limbo. You can query the applications for these packages, and act upon the package (such as delete it or postpone its installation).

If your site uses ChangeMan ZMF for scheduling, you can monitor a list of packages scheduled for installation, and selectively change, hold, or release installation of the package.

The Monitor Option panel (CMNMONIT) allows you to perform the above tasks.

164

Chapter 7: Monitoring Site and Application Packages

ACCESSING THE MONITOR OPTION PANEL

The Monitor Option panel (CMNMONIT) lets you select and monitor packages in limbo or the internal scheduler. To access this panel, select option M on the Primary Option Menu.

Querying Package Information

The Monitor Packages in Limbo panel (CMNQRYL1) lets you provide Change Package information to query.

1. From the Monitor Option panel, type 1. The Monitor Packages in Limbo panel (CMNQRYL1) is displayed:.

2. In the PACKAGE ID field, type the name of the package you are going to monitor, or select a package based on the following filter criteria:

To select from a list of: Do this:

Applications Leave the PACKAGE ID field blank

Select an application (enter S)

Select one or several packages (enter S)

All packages at your site Enter an * in the PACKAGE ID field

All packages of a certain pattern Use * pattern masking in the PACKAGE ID field

CMNMONIT ---------------------- MONITOR OPTIONS -------------------------------OPTION ===>

1 Limbo - Monitor packages in limbo 2 Scheduler - Monitor the CMN internal scheduler


CMNQRYL1 ----------------- MONITOR PACKAGES IN LIMBO --------------------------COMMAND ===>

SPECIFY SELECTION CRITERIA:PACKAGE ID ===> (Full name or pattern; blank for list)FROM INSTALL DATE ===> (YYYYMMDD) TO INSTALL DATE ===> (YYYYMMDD)FROM CREATION DATE ===> (YYYYMMDD) TO CREATION DATE ===> (YYYYMMDD)


165


3. Press ENTER. ChangeMan ZMF queries the packages you designated for discrepancies and the Limbo Package List panel (CMNRYL2) is displayed:.

PACKAGES IN LIMBO

The Limbo Package List panel (CMNRYL2) allows you to do any of the following functions:

• Delete, mark for a memo delete, change the installation date, edit and submit the job, or change the status of the package

• Manually submit a package for installation

Acting on Packages

The TYPE column of the Limbo Package List panel (CMNRYL2) displays the reason for flagging a package as limbo.

1. To act on a package in limbo, place the cursor in a desired row and do any of the following:

• Type DE and press ENTER to physically delete the package. The package is marked for deletion, which occurs as soon as you leave this panel.

• Type MD and press ENTER to memo delete the package. ChangeMan ZMF marks the package for a memo delete.

All packages to be installed in a given date range

In year, month, day format (YYYYMMDD), specify the FROM INSTALL DATE and the TO INSTALL DATE, to list all packages that are scheduled to be installed in that date range

Leave the field blank to access all dates

Select one or several packages (enter s)

All packages created in a given date range

In year, month, day format (YYYYMMDD), specify the FROM CREATION DATE and the TO INSTALL DATE, to list all packages that were created during that date range



To select from a list of: Do this:

CMNQRYL2 --------------------- LIMBO PACKAGE LIST -----------------------------COMMAND ===> SCROLL ===> CSR

Enter END command to process or CANCEL to exit.

PACKAGE ID STATUS INSTALL CREATION LEVEL TYPE REQUEST LIMBO DESCRIPTION__ DEV ______

166


Validate that participating packages are not associated with any super or complex package, and that super or complex packages have no participating packages associated.

• Type CD and press [ENTER] to change the installation date of the package. Type the new change package installation date in the INSTALL field.

• Type CS and press ENTER to change the package status. Type the new status in the STATUS field.

• Type S and press ENTER to manually submit a job to install the package. The Submit Job From panel is displayed. It is described in the following section.

2. Press END. This processes the commands. You can type CANCEL at the command line to exit without processing.

When changing the status to DEL, validate that participating packages are not associated with any super or complex package, and that super or complex packages have no participating packages associated.

Closing a Super or Complex Package

Once created, super and/or complex packages are automatically marked for limbo, you can close a super or complex package by updating its package status from OPN to CLO. For example

1. Specify the line command CS on the desired package row.

2. Enter the desired status (CLO in this example).

3. Press ENTER.

Manually Submitting a Package in Limbo for Installation

1. From the Limbo Package List panel mark a desired package for installation by typing an S in the first column of the row.

2. Press ENTER. A panel similar to the following CMNQRYL4 panel is displayed:

3. Type S to select the job to submit or type D to deselect the job to submit, and press ENTER.

• *SELECT, displays in the STATUS column if you typed S

• *DESELECT, displays in the STATUS column if you typed D.

4. Press END. ChangeMan ZMF processes the jobs you selected.

CMNQRYL4 B FROM PROD99.CMN416.PANELS ----------------------------------------COMMAND ===> SCROLL ===> CSR NAME STATUS VV.MM CREATED CHANGED SIZE INIT MOD ID_ CMNQRYL4

167


INSTALLATION JOBS

The ChangeMan ZMF install process is accomplished by a sequence of batch jobs.

The first job in the sequence is initiated by the Scheduler defined in the package Installation Instructions. The rest of the jobs in the sequence are automatically submitted to the internal reader by the preceding job or by ChangeMan ZMF when successful completion of a preceding job is recorded in the Package Master.

When you attempt to restart an install process for a package in Limbo, you must choose which job to restart and you must know whether to submit that job in the development environment or on a ChangeMan ZMF production environment that runs at a remote site.

The following table describes ChangeMan ZMF installation jobs, and it indicates where each job runs. If do not have remote production environments, your packages use a subset of these jobs to install your packages.

DEVELOPMENT CENTER REMOTE SITE

Job Action Job Action

10 Package is audited and/or frozen.

Jobs are created in “...X.&node”.

Package is approved.

Job 10 is submitted to initiate the distribution.

CMNBATCH transaction '10' says distribution initiated and status is changed to DIS.

Vehicle is asked to submit job 11 at remote site.

11 Staging libraries are sent to remote site. 10 Staging libraries are received including QSAM package master.

Job 11 is submitted.

11 CMNBATCH transaction '11' overlays package records (on PM) with QSAM package master; proper node record is time stamped; status is DIS.

Job 14 is submitted. (Only if IEBCOPY is not used.)

14 Job 14 requests vehicle to submit 15 at DEV site.

17 Job 17 is submitted if external (not internal) scheduler is used.


168


15 Job 15 is submitted. (Only if IEBCOPY is used.)

15 CMNBATCH transaction '15' stamps acknowledgment of distribution.

19 Notification to package creator that distribution failed.

21 Perform DB2 bind for production installation. (INSTALL IN PROD = YES).

20 Job 20 is submitted to check if package was previously installed, if not, then it begins installation.

20 CMNBATCH transaction '20' changes package status to 'INS'.

20 Job 24 is submitted. (Only if IEBCOPY is not used.)

20t If Temporary, Job 20t runs to install members into Temporary libraries.

24 Requests vehicle to submit 25 at DEV site.

28 Requests vehicle to submit 29 at DEV site.

25 CMNBATCH transaction '25' changes package status to 'INS.'

29 Notification to package creator that installation failed.

25 If Permanent, Job 30 is submitted.

30 Job 30 is submitted if system environment is 'ALL'.

30 CMNBATCH transaction '30' changes package status to 'BAS' and ripples the baseline.

30 Delete members from promotion libraries based on promotion level and library type.

31 If Temporary, Job 31 runs to delete members from temporary libraries.

31t CMNBATCH transaction '31' changes package status to 'TCC' (Temporary Change Cycled) and date/time stamp. Submit job 35.



169


32 Performs DB2 bind for production installation (INSTALL IN PROD = NO).

34t Requests vehicle to submit 35t at DEV site.

35t Package status updated to TCC and date/time stamped when all remote sites have been cycled.

38t Requests vehicle to submit 39t at DEV site.

39t Notification to package creator that the package cycle failed.

CASE: A permanent change must be backed out.

Operator makes human decision to back out (full) particular package. Enters backout reasons on panel and ChangeMan ZMF instance copies package to same flat file that was sent from development center. Job 50 is submitted.

49 Job 21 runs the DB2 bind for production backout (INSTALL IN PROD = YES).

50 Backs out the change by copying back from BKUP Libraries.

Changes package status to 'BAK'.

Job 54 is submitted if IEBCOPY is used, else job 51.

50 If system environment is 'ALL', job 55 is submitted.

51 Job 51 transmits a QSAM package master to the development center and requests a vehicle to submit job 54.

54 Reads flat package and transmits reasons.

Updates backout reasons into correct package.

55 Job 55 is submitted to reverse ripple the baseline if all remote sites are backed out.

55 Status is changed to 'BAK', * node record is date and time stamped.

56 Job 32 runs the DB2 bind for production backout (INSTALL IN PROD = NO).




170


MONITORING THE CHANGEMAN ZMF INTERNAL SCHEDULER

Once a package has been marked for internal scheduling and distributed, it is under the control of the Internal Scheduler. This tool lets the administrator display a list of scheduled jobs (by entering selection criteria, or blanks for the entire list), and to selectively change, hold, or release jobs. Use this panel to enter criteria for displaying the jobs currently under the control of the Internal Scheduler.

1. From the Monitor Option panel, select option 2. The Monitor Internal Scheduler Part 1 of 2 (CMNMISCH) is displayed:

59 Notification to package creator that package backout failed.


Package is audited and/or frozen.

Jobs are created in “...X.&node”.

Package is approved.

Job 10 is submitted to initiate the distribution.



CMNMISCH ---------- MONITOR INTERNAL SCHEDULER - PART 1 OF 2 ------------------COMMAND ===>

SPECIFY SELECTION CRITERIA:PACKAGE ID ===> C416 (Full name or pattern; blank for list)FROM INSTALL DATE ===> 940524 (YYYYMMDD) TO INSTALL DATE ===> (YYYYMMDD)


171


2. To monitor the Internal Scheduler for a package, in the PACKAGE ID field, type in the name of the package you want to monitor, or select a package based on the following filter criteria:

3. Press ENTER. ChangeMan ZMF processes your specifications and displays all the internally scheduled jobs which fit the criteria. The Monitor Internal Scheduler Part 2 of 2 (CMNMISC2) panel is displayed:

Reviewing the Internally Scheduled Packages List

When the Monitor Internal Scheduler Part 2 of 2 (CMNISC2) panel is displayed, you see the jobs that have been internally scheduled.

You can also use the following commands:

• Type L (package ID) and press ENTER. The list is positioned to that package's job. You can use this command just like the standard ISPF Locate command.

• Type L CGM and press ENTER. ChangeMan ZMF positions the job list to the first occurrence of any CGM change package jobs.

Acting on the Packages

1. To act on one of the packages, place the cursor in the appropriate row and perform one of the following actions:

To select from a list of... Do the following...

Applications Leave the PACKAGE ID field blank

Select an application (enter s)


All packages at your site Enter an * in the PACKAGE ID field

All packages of a certain character string Use * pattern masking in the PACKAGE ID field

All packages to be installed in a given date range

In year, month, day format (YYYYMMDD), specify the FROM INSTALL DATE and the TO INSTALL DATE, to list all packages that are scheduled to be installed in that date range



CMNMISC2 ----------- MONITOR INTERNAL SCHEDULER PART 2 OF 2 -------------------COMMAND ===> SCROLL ===> CSR

Enter END command to process or CANCEL to exit.

PACKAGE ID DATE TIME PACKAGE TYPE REQUEST STATUS_ ______ ____

172


• Type C and press ENTER to change the job's installation date or time. Type in the new date or time in the appropriate column. The STATUS field is flagged with the *CHANGE message.

• Type D and press ENTER to delete an individual package from the scheduler. The STATUS field is flagged with the *DELETE message.

• Type H and press ENTER to place a hold on the job. The installation for the package cannot be executed until the hold is removed (using the R command below). The STATUS field is flagged with the *HOLD message.

• Type R and press ENTER to release a job that has been held. The job is performed at the regularly scheduled date and time, or immediately if these have expired. The STATUS field is flagged with the *RELEASE message.

• Type S and press ENTER to submit the deinstall job for temporary packages before the temporary duration has expired. The STATUS field is flagged with the *SUBMIT message.

2. Press END. If you have entered line commands to change, delete, hold, release, or submit jobs, this action saves the changes and returns you to part 1 of the Monitor Internal Scheduler Part 1 of 2 panel (CMNMISCH).

173

CONFIGURING REMOTE SITES 8This chapter contains information about configuring remote sites for ChangeMan ZMF, on a global as well as an application level, and outlines how to enable the Network Data Mover.

OVERVIEW OF REMOTE SITES

Remote sites are additional STCs where ChangeMan ZMF installs components. The additional STC can be on:

• A separate computer in another building

• A separate computer in the same building

• A logical CPU on the same machine as part of an LPAR (logical partition) without shared DASD

Any of these remote site configurations enables you to develop components on one CPU and distribute and install production level components onto a different CPU.

All ChangeMan ZMF functions are performed from the defined development site. The remote site acts only as a receiver of production components. In fact, the only time developers interact with remote sites is when they select which remote site to distribute and install production components to.

HOW DOES IT WORK? When you request remote promotion, ChangeMan ZMF constructs execution JCL based on the administration fields that you specified. (Note that you can have execution JCL libraries similar to the installation JCL libraries.) Next, it invokes your transmission vehicle (IEBCOPY or NDM) to transmit the execution JCL library and copies of any needed Staging data sets to the remote system (site). Then, it uses the remote site’s internal reader to invoke jobs (in the execution JCL library) to copy members from the Staging to the remote promotion libraries. After these jobs complete, ChangeMan ZMF ‘cleans up’ the execution JCL and Staging libraries at the remote site. When it returns successfully, ChangeMan ZMF copies the Staging library members to the shadow library on the originating site (a shadow library as a duplicate or copy of what exists on the remote site). Next, it ‘cleans up’ the execution JCL that resides on that site. Finally, it notifies the user of the success or failure of the promotion request and updates the package master.

174

Chapter 8: Configuring Remote Sites

At installation time, ChangeMan ZMF only needs to transmit execution JCL to the remote site. This is because the execution JCLs sole function is to delete members. (This is similar to demotion). So, ChangeMan ZMF cleans up your promotion libraries at the remote site, as well as the shadow libraries that reside on the originating site. This means that if your remote site is only a test site, but you want it to simulate your production site, you must install ChangeMan ZMF on the test site. By doing this, you ‘synch up’ your production libraries. If you don’t want to install ChangeMan ZMF on the test site and you don’t want to ‘clean up’ the test promotion libraries, you must edit the installation skeletons to remove this functionality.

As delivered the only program that is required at the remote site is CMNDELRN. This program must reside in an APF authorized library. The skeletons can be changed to use CMNxxxx or SERxxxx programs also, but that would also require those programs to be in an APF authorized library.

SETTING UP REMOTE SITES GLOBALLY

The Global Administrator is responsible for creating, deleting, and updating remote site information for ChangeMan ZMF. This functionality is accessed from the Global Administration Options panel.

1. Set up multiple ChangeMan ZMF subsystems by designating one subsystem for your development site, and one for each remote site.

2. Bring up the Remote Site ChangeMan ZMF instance.

3. Set global parameters.

CMNGGP01 -------------- GLOBAL PARAMETERS - PART 1 OF 5 -----------------------COMMAND ===>

CHANGE MAN ENVIRONMENT ===> P ( A - All, D - Dev, SUBSYSTEM: DP - DevProd, P - Prod)SINGLE CPU (VSAM NOT SHARED) ===> NO (Y/N)JOB ENTRY SYSTEM ===> JES2 (JES2 or JES3)SITE NODE NAME ===>LOGICAL UNIT OR SYSTEM NAME ===>DEFAULT UNIT NAME ===> (Generic disk pack)DEFAULT VOLUME SERIAL ===>SECURITY SYSTEM ===> SAF (SAF, RACF, ACF2, or TSS)CHANGE MAN SECURITY RESOURCE ===> $CHGMANINSTALLATION JOB SCHEDULER ===> CMN (CMN, Manual or Other) SCHEDULER INTERVAL IF CMN ===> 010 (Minutes)TRANSMISSION VEHICLE ===> IEBCOPY (IEBCOPY or Other)NORMAL BUSINESS HOURS: FROM ===> 0800 TO ===> 1600 (HHMM format)AGING - INSTALLED PACKAGES ===> 180 (0 to 999 days) - STAGING DATASETS ===> 7 (0 to 999 days)


175


The following table describes the fields on the Global Parameters Part 1 of 5 panel (CMNGGP01).

4. Customize distribution and installation skeletons.

Several skeletons are involved in the distribution and installation of packages to defined remote sites. Customize these skeletons in accordance with the data set names and transmission vehicles you are using at your site.

MAINTAINING REMOTE SITES

All Remote Sites require the running of normal maintenance utilities.

For information on how to run housekeeping tasks, see “Chapter 9. Housekeeping Tasks.”

Field Description

CHANGEMAN ENVIRONMENT

Define as a Remote Site.

P—Always the configuration at a remote site CPU. The production site receives the installed production level package components from a D or DP site.

SITE NODE NAME Define a unique Site Note Name for this Remote Site.

LOGICAL UNIT OR SUBSYSTEM NAME

This is how systems are defined internally. If your data transmission vehicle is NDM or BDT, enter the logical unit name (the name that NDM or BDT uses to identify this system).

If your data transmission vehicle is IEBCOPY, enter the subsystem name (for example: SYSA).

INSTALLATION JOB SCHEDULER

Define at development site.

If you are using an internal scheduler, define the same one at your development site that you define for your remote site.

The only difference between scheduling remote site implementation for a remote site and a single site is that you schedule change package implementation for all of your remote sites.

Review the tasks in the section “Setting Up the Installation Calendar” in “Chapter 4. Setting Up Global Administration.” In task 3, when you access the calendar, you have an extra step. The Remote Site Selection List displays, and you select a remote site from the list before updating the calendar. Once you have finished updating the calendar, you return to the Remote Site Selection list so you can select another one for updating.

If you do not specify a scheduler, the CMN (default) scheduler is invoked at start up time. When you build a package at the DP site and then install the package, the ChangeMan ZMF scheduler distributes the package to the remote site and sends scheduler information. Therefore, the remote site needs to have the same scheduler either attached or defined.


Define at development site.

176


Note To prevent unwarranted modification of remote site Production libraries, ChangeMan ZMF omits the display of the Build, Promote, Approve, Freeze, and Delete options from the Primary Menu.

SETTING UP REMOTE SITES FOR APPLICATIONS

This section describes an option accessible from the Global Administration Option panel and the Application Administration Option panel that displays a list of remote sites. This list, which is displayed during application level creation of a change package, allows you to create, delete, and update all the remote sites where ChangeMan ZMF is installed. Hence, it includes all the valid sites for change implementation.

Note If this is an ALL site, the remote site capability is limited to remote promotion

ESTABLISHING A REMOTE SITE - GLOBAL ADMINISTRATOR

To establish a remote site, do the following:

1. From the Primary Option Menu, select option A on the Primary Option Menu. The Administration Options panel is displayed.

2. From the Administration Options panel, select option G. The Global Administration Options panel is displayed.

3. From Global Administration Options panel, select option 6. The Global Remote Site List panel (CMNGRST1) is displayed:

From the The Global Remote Site List panel (CMNGRST1), you can create a new site.

1. With the cursor in the LCMD column of the library row, insert a new line (type I and press ENTER)

2. In the SITE NAME column, using the following rules, type the name of the site:

• Specify up to 8 alphanumeric characters

• Make the first character of the remote site name alphabetic

3. Press ENTER to save your new site entry.

CMNGRST1 ---------------- GLOBAL SITE LIST PART 1 OF 2 ------- Row 1 to 6 of 6 COMMAND ===> SCROLL ===> CSR Enter END command to save changes or CANCEL to exit. SITE NAME '''' CMNM____ '''' TEST____ '''' TEST2___ '''' TEST3___ '''' TEST4___ '''' TEST5___

177


4. place the cursor in the LCMD column of the remote site you just added, and type S and press ENTER

• If this is a DP site, the Remote Site Information panel (CMNGRST2) is displayed:

• If this is an ALL site, the Test Remote Site Promotion panel (CMNGPRST) is displayed:

Provide information for each of the required fields.

CMNGRST2 ----- ----- TEST5 SITE INFORMATION - PART 2 OF 2 --------------------- COMMAND ===> CHANGE MAN SUBSYSTEM ID ===> LOGICAL UNIT/SYSTEM NAME ===> DEFAULT UNIT NAME ===> (Generic disk pack) DEFAULT VOLUME SERIAL ===> CHANGE MAN DELAY FILE ===> PRD STAGING MODEL DSNAME ===> ????.CMNSTAGE.####### TRANSMISSION VEHICLE ===> IEBCOPY (IEBCOPY or Other) TIME DIFFERENCE ===> +0000 (+/-HHMM) REMOTE SITE JOB STATEMENT INFORMATION: ===> //SERVER JOB (ACCOUNT),SITE JOB CARD MODEL________________________________ ===> //CLASS=?,MSGCLASS=?,NOTIFY=______________________________________________ ===> //*_______________________________________________________________________ ===> //*_______________________________________________________________________ Press ENTER to process; Enter END command to exit.

CMNGPRST --------- TEST5 SITE DEFINITION - PART 2 OF 2 ------------------------ COMMAND ===> LOGICAL UNIT/SYSTEM NAME ===> DEFAULT UNIT NAME ===> (Generic disk pack) DEFAULT VOLUME SERIAL ===> TRANSMISSION VEHICLE ===> (IEBCOPY or Other) REMOTE SITE JOB STATEMENT INFORMATION: ===> //SERVER JOB (ACCOUNT),SITE JOB CARD MODEL________________________________ ===> //CLASS=?,MSGCLASS=?,NOTIFY=______________________________________________ ===> //*_______________________________________________________________________ ===> //*_______________________________________________________________________ Press ENTER to process; Enter END command to exit.

178


The following table describes the field on the Remote Site Information panel (CMNGRST2).

5. After entering information on the panel, press ENTER.

Field Description

CHANGEMAN SUBSYSTEM ID

Enter the ChangeMan ZMF subsystem ID or leave this field blank to use the default subsystem ID. (DP only)

LOGICAL UNIT/SYSTEM NAME

Enter the logical unit or system name.

This is the name defined for the CPU or LPAR for which the remote site is located, and it is associated with the transmission vehicle selected on the CMNGP01 (Global Parameter) panel.

DEFAULT UNIT NAME

Enter the default unit name to have the X.REMOTESITE production library allocated on. Leave blank if default volume serial is entered.


Enter the X.REMOTESITE Staging library for this site to have it allocated on the default VOLSER specified here. Enter the default VOLSER to have the X.REMOTESITEPROD library allocated on. Leave blank if default unit name is entered.

CHANGEMAN DELAY FILE

If this information is being configured for the same site specified on Part 1 of the Global Parameters panel, then specify the same delay file specified there in this field. If not, specify the delay file of the REMOTESITE that is being configured in this field.

PRD STAGING MODEL DSNAME

If this information is being configured for the same site specified on Part 1 of the Global Parameters panel, then specify the DEV staging model dsname specified there in this field. If not, specify the PRD staging model dsname for the REMOTESITE being configured in this field. (DP only)


If this information is being configured for the same site specified on Part 1 of the Global Parameters panel, then specify the transmission vehicle specified there in this field. If not, specify the transmission vehicle for the REMOTESITE being configured in this field.

If you specify OTHER and you plan to use the Network Data Mover (NDM), see “Enabling the Network Data Mover” on page 180.

TIME DIFFERENCE

Type the difference in system clock time between this site and the development site where change packages are created.

Enter a positive time difference in hours and minutes (+hhmm) if this site is to the east of the development site. Enter a negative time difference (-hhmm) if this site is to the west of the development site. The default time difference is +0000.

The time difference parameter is used to verify that the package install date and time that you enter when you create a package is a time that has not already passed at a remote site.

REMOTE SITE JOB CARD INFORMATION

Enter the default job card to be used at the site.

179


SELECTING A REMOTE SITE - APPLICATION ADMINISTRATOR


1. From the Primary Option Menu, select option A on the Primary Option Menu. The Administration Options panel (CMNADMOM) is displayed.

2. From the Administration Options panel (CMNADMOM), select option A. The Application Administration Options panel (CMNLAMEN) is displayed.

3. From Application Administration Options panel (CMNLAMEN), select option 8. The Application Remote Site List panel (CMNCLRST) is displayed:

From The Application Remote Site List panel (CMNCLRST), you can create a new site or update an existing site.

1. With the cursor in the LCMD column of the library row, insert a new line (type I and press ENTER)

2. In the SITE NAME column, type the name of the globally defined remote site or type an asterisk in the column to select from the global remote site list.

3. Press ENTER to establish and save your new site.

UPDATING AN EXISTING SITE - APPLICATION ADMINISTRATOR


1. From the Primary Option Menu, select option A on the Primary Option Menu. The Administration Options panel (CMNADMOM) is displayed.

2. From the Administration Options panel (CMNADMOM), select option A. The Application Administration Options panel (CMNLAMEN) is displayed.

CMNCLRST -------------- NAVI - SITE LIST PART 1 OF 2 --------- Row 1 to 5 of 5 COMMAND ===> SCROLL ===> Enter END command to save changes or CANCEL to exit. Enter * in line command field for global list. SITE NAME '''' CMNM____ '''' TEST____ '''' TEST2___ '''' TEST3___ '''' TEST4___ ******************************* Bottom of data ********************************

180


3. From Application Administration Options panel (CMNLAMEN), select option 8. The Application Remote Site List panel (CMNCLRST) is displayed:

4. From the Remote Site List Part 1 of 2 panel, place the cursor in the LCMD column of the library row that you want to update, and type S (Select) and press ENTER. The Test Remote Site Information Part 2 of 2 panel (CMNRSTJB) is displayed:

5. On the Test Remote Site Information panel (CMNRSTJB), enter the job card information required for any internal jobs that you might submit at the specified remote site.

6. Press ENTER to save your changes, or enter the END command to exit.

Repeat the above steps for each remote site that you want to update.

ENABLING THE NETWORK DATA MOVER

If your shop possesses at least one remote site and you want to use Network Data Mover (NDM) as the transmission vehicle, refer to member #NDM in the CMNZMF CNTL file, and do the following:

1. Copy member #NDM from the vendor CMNZMF CNTL library into your custom CNTL library.

2. Modify the data set name to conform to your standards for the procedure library.

CMNCLRST -------------- NAVI - SITE LIST PART 1 OF 2 --------- Row 1 to 5 of 5 COMMAND ===> SCROLL ===> Enter END command to save changes or CANCEL to exit. Enter * in line command field for global list. SITE NAME '''' CMNM____ '''' TEST____ '''' TEST2___ '''' TEST3___ '''' TEST4___ ******************************* Bottom of data ********************************

CMNRSTJB ---------- TEST5 SITE INFORMATION - PART 2 OF 2 ---------------------- COMMAND ===> SITE JOB STATEMENT INFORMATION: ===> //CMNSTART JOB ,ACCOUNT INFORMATION,____________________________________ ===> // CLASS=?,MSGCLASS=?_______________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.

181


3. Create the procedure library by changing all occurrences of $/ to ./ for IEBUPDTE and submit the job. Next, modify CMN$$NDM.

4. Copy skeleton CMN$$NDM from the delivered skeleton library and put it into your custom skeleton library. If the batch module DMBATCH cannot be found in a linklisted library, a Steplib is necessary.

5. Further down in the skeleton is a sign on for SYSIN that reads:

SIGNONUSERID=(&RSOWNER)NETMAP=&NDMMAP,ESF=YES

By design, &RSOWNER will not resolve. To prevent ordinary users from seeing the USERID while they browse the skeleton, you must hard code an authorized resource owner USERID outside the skeleton, as follows:

//SYSINDDDISP=SHR,DSN=node.NDM.SIGNON <=== Secured // DD * NETMAP=&NDMMAP,ESF=YES

6. You must secure the data set node.NDM.SIGNON from read and update, by all except NDM, ChangeMan ZMF, and your Global Administrator. The file contents’ (possibly a secured PDS member) should read:

SIGNON USERID=(superid) -

7. Where superid represents a real userid. The authority level of this userid must be sufficient to do the following:

• Transmit data sets created by ChangeMan ZMF to remote sites.

• Allocate and update ChangeMan ZMF target staging data sets at the remote site.

• Return acknowledgment messages.

Note Do not forget to use the continuation dash to get to the next line of the skeleton that describes NETMAP and so on.

As delivered, the parameter to DMBATCH reads PARM=(NNNNNNN). Essentially, this parameter implies NO to each of seven NDM internal questions.

Changing this parameter value impacts diagnostic messages, activity logging, and the chosen DDNAMES.

182


183

DEFINING AND RUNNING CHANGEMAN ZMF REPORTS 9CHANGEMAN ZMF REPORTS

ChangeMan ZMF includes a facility to generate reports to assist your enterprise in managing software configuration changes. ChangeMan ZMF reports display information about components and change packages. The audience for these reports includes:

• Change management team

• IT business partners

• IT Project Managers

• ChangeMan ZMF Global Administrators

• ChangeMan ZMF Application Administrators

• Developers who use ChangeMan ZMF

The following table lists reports delivered with ChangeMan ZMF.

Report Description

CMN010 Summary of Planned and Unplanned Packages

CMN050 Installed Package History Report

CMN060 Installed Simple Change Package History Report

CMN090 Super/Complex Packages Report

CMN100 Application Configuration Report

CMN110 Work Request Number Report

CMN120 Package That Need Post Approval

CMN130 Unplanned Packages Pending Post Approval

CMN140 Report of Rejected Packages

CMN150 Unplanned Packages by Reason Code

CMN160 Trend Analysis of Planned Changes

184

Chapter 9: Defining and Running ChangeMan ZMF Reports

Samples of these reports can be viewed in the REPORTS member of the CMNZMF SAMPLES library.

Information for ChangeMan ZMF reports comes from the VSAM Package Master, the VSAM Component History file, or from sequential backups of these files.

CMN170 Trend Analysis of Unplanned Reason Codes

CMN180 Component History Report

CMN190 Trend Analysis of Unplanned Packages

CMN200 Copies, Source and Load Component Report

CMN210 Utility (Scratch/Rename) Report

CMN240 Activity Summary by Application

CMN250 Activity Summary by Department Number

CMN260 Implementation Schedule

CMN500 Package Information Report

CMN890 Skeleton Release ID Report

CMN900 Designated Procedures Report

CMN910 Package using the CMN Scheduler

CMN920 Packages/Staging Datasets to be Deleted

Note: This report only marks packages and staging data sets for cleanup. To delete them, you must run the housekeeping function for reports.

CMN930 Implementation Calendar Discrepancy Report

Note: This report only marks the calendar for resynch. To run the resynch, you must run the housekeeping function for reports.

CMN940 Components without Component Level Security

CMN950 Delinquent Package Report

CMN960 Component Level Security Information

CMN970 Packages Pending Approval

CMN980 Implementation Calendar Report

CMN990 Global Administration Configuration Report

Report Description

185


ChangeMan ZMF reports can be run online or from batch JCL. Reports can be run by global administrators, application administrators, and users who have read access to an application. The privilege to run each report can be restricted as follows:

• Global administrators only

• Application administrators and global administrators only

• Users, application administrators, and global administrators.

SAS OR ASSEMBLER REPORT PROGRAMS

There are two report generators delivered with ChangeMan ZMF:

• SAS program CMNSAS10.

• Assembler program CMNBAT10.

Serena recommends that you use the SAS program to run ChangeMan ZMF reports. You must have the SAS System installed on your mainframe.

If SAS is not installed on your mainframe, you can use the assembler report generator. See “Generating Reports Without SAS” on page 186.

Generating Reports With SAS

If you initiate reports online, skeleton CMN$$RPT is file tailored to create batch JCL. This skeleton is delivered in member CMN$$RPT in the CMNZMF SKELS file on the ChangeMan ZMF distribution CD or tape.

Sample JCL for a stand alone batch reporting job is in the REPORTS member of the CMNZMF CNTL file.

You must modify both of these members before you can use them to run ChangeMan ZMF reports:

1. Copy the skeleton and JCL members from the vendor libraries to your custom libraries.

2. Update the SAS library names to match the names you use for ChangeMan ZMF libraries:

somnode.CHGMAN.SAS(CMNSAS10)somnode.CHGMAN.SAS

3. Update the name of the SAS procedure, if necessary. SAS is the name of the procedure in the delivered skeleton and JCL. The SAS procedure may have been installed in your PROCLIB under a different name (such as SAS800).

4. In the stand alone JCL, update the data set names for the Package Master File and the Component Master File. See comments in the stand alone JCL for using sequential backups and the BKUP keyword parameter.

186


Generating Reports Without SAS

If SAS is not installed on your mainframe, you must use assembler program CMNBAT10 to produce ChangeMan ZMF reports.

The assembler version of ChangeMan ZMF reporting differs from the SAS version in the following ways:

• The assembler versions have been functionally stabilized. The reports are Y2K compliant, but they have not been enhanced to select or display data recently added to ChangeMan ZMF.

• You cannot customize the assembler program that produces reports.

• Date range selection is not supported in the assembler version of reports.

• These reports are not supported in the assembler version.

Stand alone batch JCL for program CMNBAT10 is delivered in member REPORTS2 in the CMNZMF CNTL file on the distribution CD or tape.

Skeleton CMN$$RPT is used to file tailor reporting job JCL when reports are initiated online. CMN$$RPT is delivered in the CMNZMF CNTL library on the distribution CD or tape.

Follow these steps to implement the assembler version of ChangeMan ZMF reports:

1. Use the REPORTS2 sample JCL as a model to modify skeleton CMN$$RPT to use program CMNBAT10 instead of the SAS procedure.

2. Delete the reports not available in the assembler version of reports from report selection list panels. See “Define Reports: Global Administrator” on page 188 and “Define Reports: Application Administrator” on page 194.

Report Description

CMN500 Package Information Report

CMN890 Skeleton Release ID Report

CMN900 Designated Procedures Report

CMN910 Package using the CMN Scheduler

CMN940 Components without Component Level Security

CMN960 Component Level Security Information

CMN970 Packages Pending Approval

CMN980 Implementation Calendar Report

CMN990 Global Administration Configuration Report

187


DEFINING AND RUNNING REPORTS: GLOBAL ADMINISTRATOR

Accessing Global Reports

Follow these steps to access the reports facility in global administration.

1. On the Primary Option Menu, select option A and press ENTER. The Administration Options panel is displayed:

2. On the Administration Options panel, type G and press ENTER. The Global Administration Options panel is displayed:


CMNGAMEN --------------- GLOBAL ADMINISTRATION OPTIONS ------------------------ OPTION ===> 1 Parms - Generate global parameters 2 Library - Generate library types 3 Language - Generate language names 4 Procedures - Generate compiling procedures 5 Reason Codes - Generate reason codes for unplanned packages 6 Sites - Generate site information 7 Lock - Lock or reset application parameter locks D Dates - Update the installation calendar I Impact - Perform impact analysis maintenance N Notify - Update the global notification file O Options - Configure selectable options R Reports - Generate Change Man batch reports S Skeleton - Create, update, and test skeleton procedures Press ENTER to process; Enter END command to exit.

188


3. On the Global Administration Options panel, type R and press ENTER. The Define Or Generate ChangeMan Batch Reports panel is displayed:

4. Define Reports: Global Administrator

As a global administrator you can:

• Remove standard reports from the ChangeMan ZMF report facility.

• Add reports that you coded as modifications to SAS program CMNSAS10.

• Restrict who can run reports.

Follow these steps to define reports in global administration.

1. On the Define Or Generate ChangeMan Batch Reports panel, type 1 and press Enter. The Define Global ChangeMan Reports panel is displayed:

CMNREPT0 -------- DEFINE OR GENERATE CHANGE MAN BATCH REPORTS ----------------- OPTION ===> 1 Define - Define Change Man Batch Reports 2 Reports - Generate Change Man Batch Reports 3 Analyzer - Submit Baseline Analyzer Report 4 Link Date - Submit Link Date Report 5 DB2 - Submit DB2 object dependency Report Press ENTER to process; Enter END command to exit.

CMNREPT1 -------------- DEFINE GLOBAL CHANGE MAN REPORTS --- Row 1 to 16 of 31 COMMAND ===> SCROLL ===> PAGE Enter END command to process or CANCEL to exit. Enter * in line command for default report selection list. ID Type Report Description '''' 010 U Summary of Planned and Unplanned Packages__ '''' 050 A Installed Package History Report___________ '''' 060 A Installed Simple Package History Report____ '''' 090 A Super/Complex Packages Report______________ '''' 100 A Application Configuration Report___________ '''' 110 A Work Request Number Report_________________ '''' 120 A Unplanned Packages Pending Post Approval___ '''' 130 A Report of Backed Out Packages______________ '''' 140 A Report of Rejected Packages________________ '''' 150 A Unplanned Packages by Reason Code__________ '''' 160 A Trend Analysis of Planned Packages_________ '''' 170 A Trend Analysis of Unplanned Reason Codes___ '''' 180 A Component History Report___________________ '''' 190 A Trend Analysis of Unplanned Packages_______ '''' 200 A Copies, Source and Load Component Report___ '''' 210 A Utility (Scratch/Rename) Report____________

189


The following table describes the fields on the Define Global ChangeMan Report panel.

2. If you typed * in the line command, the Default Defined Report Selection List panel is displayed:

Field Description

Line Command Type a line command to insert, repeat, or delete a report row.

I

R

D

*

Insert a new report row below the selection.

Repeat an existing report row.

Delete an existing report.

Display the Default Defined Reports Selection List to add a standard report.

ID Displays the three-character report ID. Report IDs must be unique.

Type Type a report type to determine who can run the report online.

G

A

U

Only global administrators can run this report.

Application Administrators can run this report, and they may make the report available for users to run. See “Defining and Generating Reports: Application Administrator” on page 193

Users in any application can run this report.

Report Description

Description of the report.

CMNREPT8 ----------- DEFAULT DEFINED REPORTS SELECTION LIST- Row 1 to 17 of 31 COMMAND ===> SCROLL ===> PAGE Enter END command to process or CANCEL to exit. ID Type Report Description _ 010 A Summary of Planned and Unplanned Packages__ _ 050 A Installed Package History Report___________ _ 060 A Installed Simple Package History Report____ _ 090 A Super/Complex Packages Report______________ _ 100 A Application Configuration Report___________ _ 110 A Work Request Number Report_________________ _ 120 A Unplanned Packages Pending Post Approval___ _ 130 A Report of Backed Out Packages______________ _ 140 A Report of Rejected Packages________________ _ 150 A Unplanned Packages by Reason Code__________ _ 160 A Trend Analysis of Planned Packages_________ _ 170 A Trend Analysis of Unplanned Reason Codes___ _ 180 A Component History Report___________________ _ 190 A Trend Analysis of Unplanned Packages_______ _ 200 A Copies, Source and Load Component Report___ _ 210 A Utility (Scratch/Rename) Report____________ _ 240 A Activity Summary by Application____________

190


3. On the Default Report Selection List panel, type S in the line command of the reports that you wish to select, and press Enter. You return to the Define Global ChangeMan Reports panel, where the selected reports have been inserted.

4. To save your updates, press PF-3 or type End on the Command line and press Enter.

Run Reports: Global Administrator

Follow these steps to run reports from global administration.

1. On the Define or Generate ChangeMan Batch Reports panel, type 2 and press Enter. The Generate ChangeMan Batch Report panel is displayed:

The following table describes the fields on the Generate ChangeMan Batch Report panel.

Field Description

APPLICATION Type the application mnemonic (three or four characters).

Type a pattern for an application range, maximum of four characters, using * for a mask or pattern.

Type **** to run reports for all applications.

Leave this field blank to display the Application Selection List panel from which you may select one application.

JOB STATEMENT INFORMATION

Job card information for your reporting job.

CMNREPT3 ------------- GENERATE CHANGE MAN BATCH REPORTS ---------------------- COMMAND ===> APPLICATION ===> (Full name, pattern or blank for list) JOB STATEMENT INFORMATION: ===> //USER83V JOB (X170,374),’CHANGE MAN’, <=== CHANGE ACCORDINGLY______ ===> // MSGCLASS=9,NOTIFY=USER83 <=== CHANGE ACCORDINGLY______ ===> /*JOBPARM S=ESA5 <=== CHANGE ACCORDINGLY______ ===> //*________________________________________<=== CHANGE ACCORDINGLY______ Press ENTER to process; Enter END command to exit.

191


2. After typing information on the Generate ChangeMan Batch Reports panel, press Enter. The Report Selection List panel is displayed

The following table describes the fields on the Report Selection List panel.

You may select multiple reports on the Report Selection List panel. Press PF-8 to page down on the Report Selection List panel, and press PF-7 to page up.

Field Description

Package Number Type a package number for Report 500:

Type a package number to report one package. No masking is allowed.

Leave blank to report all packages for the selected applications.

Release ID Type a Release ID for Report 890:

Type a particular Release ID.

Type a pattern for a Release ID range, maximum of four characters, using * for a mask or pattern.

Leave blank to report all Release IDs.

Report Range Type a range of inclusive dates for the selected reports. Leave these fields blank to report all dates.

Line Command S

D

Select the report.

Deselect the report.

ID Displays the three-character report ID.

Report Description Displays a description of the report.

CMNREPT6 ------------------- REPORT SELECTION LIST --------- Row 1 to 12 of 31 COMMAND ===> SCROLL ===> PAGE Enter END command to process or CANCEL to exit. Package Number ===> (optional, report 500) Release ID ===> (optional, report 890, blank or mask) Report Date Range From ===> (YYYYMMDD, optional) To ===> (YYYYMMDD, optional) ID Report Description _ 010 Summary of Planned and Unplanned Packages _ 050 Installed Package History Report _ 060 Installed Simple Package History Report _ 090 Super/Complex Packages Report _ 100 Application Configuration Report _ 110 Work Request Number Report _ 120 Unplanned Packages Pending Post Approval _ 130 Report of Backed Out Packages _ 140 Report of Rejected Packages _ 150 Unplanned Packages by Reason Code _ 160 Trend Analysis of Planned Packages _ 170 Trend Analysis of Unplanned Reason Codes

192


3. To run the selected reports, press PF-3 or type End on the Command line and press Enter.

Baseline Analyzer Report: Global Administrator

Follow these steps to run the Baseline Analyzer Report from global administration.

1. On the Define Or Generate ChangeMan Batch Reports panel, type 3 in Option and press Enter. The Generate ChangeMan Baseline Analyzer Report panel is displayed:

The following table describes the fields on the Generate ChangeMan Baseline Analyses Report panel.

2. After typing information on the Generate ChangeMan Baseline Analyzer Report panel, press Enter. A message is displayed indicating that the job has been submitted.

See “Baseline Analyzer Report” on page 199 for a description of the Link Date report.

Link Date Report: Global Administrator

Follow these steps to run the Link Date report from global administration.

Field Description

APPLICATION Type the application mnemonic (three or four characters).

Type a pattern for an application range, maximum of four characters, using * for a mask or pattern.

Type **** to run reports for all applications.

Leave this field blank to display the Application Selection List panel from which you may select one application.

JOB STATEMENT INFORMATION

Job card information for your reporting job.

CMNBLA03 -------- GENERATE CHANGE MAN BASELINE ANALYZER REPORT ---------------- COMMAND ===> APPLICATION ===> (Full name or pattern) JOB STATEMENT INFORMATION: ===> //USER239Z JOB (X170,374),CAMPBELL,CLASS=A,MSGCLASS=H,TIME=1,___________ ===> // NOTIFY=USER239___________________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.

193


1. On the Define Or Generate ChangeMan Batch Reports panel, type 4 in Option and press Enter. The Generate ChangeMan Link Date Report panel is displayed:

2. Review the job card statement information, make any necessary changes. Once you have verified the information, press Enter. A message is displayed indicating that the job has been submitted.

See “Link Date Report” on page 204 for a description of the Link Date report.

DB2 Object Dependency Report: Global Administrator

The DB2 Object Dependency report is a batch report that analyzes components managed by the DB2 Option of ChangeMan ZMF. See the ChangeMan ZMF DB2 Option Getting Started Guide for information on this report.

DEFINING AND GENERATING REPORTS: APPLICATION ADMINISTRATOR

Accessing Application Reports

Follow these steps to access the reports in application administration options.

1. On the ChangeMan Primary Option Menu, select option A and press ENTER. The Administration Options panel is displayed:

CMNLNKD1 ------------ GENERATE CHANGE MAN LINK DATE REPORT -------------------- COMMAND ===> JOB STATEMENT INFORMATION: ===> //USER239Y JOB (X170,374),CAMPBELL,CLASS=A,MSGCLASS=H,TIME=1,___________ ===> // NOTIFY=USER239___________________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.


194


2. On the Administration Options panel, type A and press ENTER. The Application Administration Options panel is displayed:

3. On the Application Administration Options panel, type an mnemonic, type R on the Option line, and press ENTER. The Define Or Generate ChangeMan Batch Reports panel is displayed:

Define Reports: Application Administrator

As an application administrator you can:

• Remove reports from the reports selection.

• Add reports to the reports selection list.

• Restrict who can run reports.

Follow these steps to define reports in application administration.

CMNLAMEN ------------- APPLICATION ADMINISTRATION OPTIONS --------------------- OPTION ===> APPLICATION ===> (Blank for list) 1 Parms - Generate application parameters 2 Library - Generate library types 3 Language - Generate language names 4 Procedures - Generate compiling procedures 5 Pln Approvals - Create planned approval list 6 Upl Approvals - Create unplanned approval list 7 Promotion - Configure promotion libraries 8 Sites - Configure site information B Baseline - Configure baseline libraries C Component - Update component information, procedures, security D Delete - Delete an application N Notify - Update the Global Notification File O Options - Configure selectable options P Production - Configure production libraries R Reports - Generate application batch reports Press ENTER to process; Enter END command to exit.

CMNREPT0 -------- DEFINE OR GENERATE CHANGE MAN BATCH REPORTS ----------------- OPTION ===> 1 Define - Define Change Man Batch Reports 2 Reports - Generate Change Man Batch Reports 3 Analyzer - Submit Baseline Analyzer Report 4 Link Date - Submit Link Date Report 5 DB2 - Submit DB2 object dependency Report Press ENTER to process; Enter END command to exit.

195


1. On the Define Or Generate ChangeMan Batch Reports panel, type 1 and press Enter. The Define Application ChangeMan Reports panel is displayed:

The following table describes the fields on the Define Application ChangeMan Report panel.

Field Description

Line Command Type a line command to insert, repeat, or delete a report row.

I

R

D

*

Insert a new report row below the selection.

Repeat an existing report row.

Delete an existing report.

Display the Global Defined Reports Selection List to add a report.

ID Displays the three-character report ID. Report IDs must be unique.

Type Type a report type to determine who can run the report online.

A

U

Application administrators can run this report.

Users authorized for this application can run this report.

Report Description Description of the report.

CMNREPT2 ------- DEFINE APPLICATION DEMO CHANGE MAN REPORTS Row 1 to 16 of 22 COMMAND ===> SCROLL ===> PAGE Enter END command to process or CANCEL to exit. Enter * in line command for default report selection list. ID Type Report Description '''' 050 A Installed Package History Report___________ '''' 060 A Installed Simple Package History Report____ '''' 090 U Super/Complex Packages Report______________ '''' 100 A Application Configuration Report___________ '''' 110 A Work Request Number Report_________________ '''' 120 U Unplanned Packages Pending Post Approval___ '''' 130 A Report of Backed Out Packages______________ '''' 140 A Report of Rejected Packages________________ '''' 150 A Unplanned Packages by Reason Code__________ '''' 160 A Trend Analysis of Planned Packages_________ '''' 170 A Trend Analysis of Unplanned Reason Codes___ '''' 180 A Component History Report___________________ '''' 190 A Trend Analysis of Unplanned Packages_______ '''' 200 A Copies, Source and Load Component Report___ '''' 210 A Utility (Scratch/Rename) Report____________ '''' 240 A Activity Summary by Application____________

196


2. If you typed * in the line command, the Global Defined Report Selection List panel is displayed:

3. On the Global Report Selection List panel, type S in the line command of the reports that you wish to select, and press Enter. You return to the Define Application ChangeMan Reports panel, where the selected reports have been inserted.

4. To save your updates, press PF-3 or type End on the Command line and press Enter.

Run Reports: Application Administrator

Follow these steps to run reports from application administration.

1. On the Define or Generate ChangeMan Batch Reports panel, type 2 and press Enter. The Generate Application Batch Report panel is displayed:

CMNREPT7 ------------ GLOBAL DEFINED REPORTS SELECTION LIST- Row 1 to 17 of 22 COMMAND ===> SCROLL ===> PAGE Enter END command to process or CANCEL to exit. ID Type Report Description _ 050 A Installed Package History Report___________ _ 060 U Installed Simple Package History Report____ _ 090 A Super/Complex Packages Report______________ _ 100 A Application Configuration Report___________ _ 110 A Work Request Number Report_________________ _ 120 A Unplanned Packages Pending Post Approval___ _ 130 A Report of Backed Out Packages______________ _ 140 A Report of Rejected Packages________________ _ 150 A Unplanned Packages by Reason Code__________ _ 160 A Trend Analysis of Planned Packages_________ _ 170 A Trend Analysis of Unplanned Reason Codes___ _ 180 A Component History Report___________________ _ 190 A Trend Analysis of Unplanned Packages_______ _ 200 A Copies, Source and Load Component Report___ _ 210 A Utility (Scratch/Rename) Report____________ _ 240 A Activity Summary by Application____________ _ 250 A Activity Summary by Department Number______

CMNREPT4 --------- GENERATE APPLICATION DEMO BATCH REPORT --------------------- COMMAND ===> Job Statement Information: ===> //USER239X JOB (X170,374),CAMPBELL,CLASS=A,MSGCLASS=H,TIME=1,___________ ===> // NOTIFY=USER239___________________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.

197


2. Type Job Statement Information on the Generate Application Batch Report panel and press Enter. The Report Selection List panel is displayed:

The following table describes the fields on the Report Selection List panel.

You may select multiple reports on the Report Selection List panel. Press PF-8 to page down on the Report Selection List panel, and press PF-7 to page up.

Field Description

Package Number Type a package number for Report 500:

Type a package number to report one package. No masking is allowed.

Leave blank to report all packages for the selected application.

Release ID Type a Release ID for Report 890:

Type a particular Release ID.

Type a pattern for a Release ID range, maximum of four characters, using * for a mask or pattern.

Leave blank to report all Release IDs.

Report Range Type a range of inclusive dates for the selected reports. Leave these fields blank to report all dates.

Line Command S

D

Select the report.

Deselect the report.

ID Displays the three-character report ID.

Report Description Displays a description of the report.

CMNREPT6 ------------------- REPORT SELECTION LIST --------- Row 1 to 12 of 31 COMMAND ===> SCROLL ===> PAGE Enter END command to process or CANCEL to exit. Package Number ===> (optional, report 500) Release ID ===> (optional, report 890, blank or mask) Report Date Range From ===> (YYYYMMDD, optional) To ===> (YYYYMMDD, optional) ID Report Description _ 010 Summary of Planned and Unplanned Packages _ 050 Installed Package History Report _ 060 Installed Simple Package History Report _ 090 Super/Complex Packages Report _ 100 Application Configuration Report _ 110 Work Request Number Report _ 120 Unplanned Packages Pending Post Approval _ 130 Report of Backed Out Packages _ 140 Report of Rejected Packages _ 150 Unplanned Packages by Reason Code _ 160 Trend Analysis of Planned Packages _ 170 Trend Analysis of Unplanned Reason Codes

198


3. To run the selected reports, press PF-3 or type End on the Command line and press Enter.

Baseline Analyzer Report: Application Administrator

Follow these steps to run the Baseline Analyzer Report from application administration.

1. On the Define Or Generate ChangeMan Batch Reports panel, type 3 in Option and press Enter. The Generate ChangeMan Baseline Analyzer Report panel is displayed:

2. Review the job card statement information, make any necessary changes. Once you have verified the information, press Enter. A message is displayed that indicates the job has been submitted.

See “Baseline Analyzer Report” on page 199 for a description of the information on the Baseline Analyzer report.

Link Date Report: Application Administrator

Follow these steps to run the Link Date report from application administration.

1. On the Define Or Generate ChangeMan Batch Reports panel, type 4 in Option and press Enter. The Generate ChangeMan Link Date Report panel is displayed:

2. Review the job card statement information, make any necessary changes. Once you have verified the information, press Enter. A message is displayed indicating that the job has been submitted.

See “Link Date Report” on page 204 for a description of the information on the Link Date report.

CMNBLA04 - GENERATE BASELINE ANALYZER REPORT FOR APPLICATION DEMO ------------- COMMAND ===> Job Statement Information: ===> //USER239A JOB (X170,374),CAMPBELL,CLASS=A,MSGCLASS=H,TIME=1,___________ ===> // NOTIFY=USER239___________________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.

CMNLNKD1 ------------ GENERATE CHANGE MAN LINK DATE REPORT -------------------- COMMAND ===> JOB STATEMENT INFORMATION: ===> //USER239Y JOB (X170,374),CAMPBELL,CLASS=A,MSGCLASS=H,TIME=1,___________ ===> // NOTIFY=USER239___________________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.

199


DB2 Object Dependency Report

The DB2 Object Dependency report is an batch report that analyzes components managed by the DB2 Option of ChangeMan ZMF. See the ChangeMan ZMF DB2 Option Getting Started Guide for information on this report.

BASELINE ANALYZER REPORT

Baseline Analyzer is a utility that allows you to analyze the integrity of your source and load relationships. It identifies those components that have not yet been properly migrated by ChangeMan ZMF as well as discrepancies between source components and executable components.

//jobname JOB (account),'CHGMAN/BASLN', <=== Change Accordingly // CLASS=?,NOTIFY=?, <=== Change Accordingly // MSGCLASS=? <=== Change Accordingly //* //* Sample jcl to run Baselin Analyzer. //* //BASLN EXEC PGM=CMNBASLN, // PARM='SUBSYS=x, <=== Update subsystem ID// USER=x' <== Specify valid TSO ID //SYSPRINT DD SYSOUT=* //RPCTRACE DD SYSOUT=* //BASLNRPT DD SYSOUT=* //SUMRYRPT DD SYSOUT=* //SYSIN DD *

/*

As a global or application administrator, you can run the Baseline Analyzer based on the following:

• After installing a package into production and you want to analyze your baseline libraries

• On the applications (projects) you want to inspect

• Monthly, on the entire ChangeMan ZMF subsystem

Baseline Analyzer Report

The baseline data set report contains the following information:

Header line

prints on every page. It contains the Baseline Analyzer name, the ChangeMan ZMF version, and the full date and time of the report request. The following is a sample of the header line

200


Baseline Analyzer (MVS - 5.3) Monday July 20, 1998 @ 12:05:05 Page 1

Baseline library information line

prints for each library processed. It contains the application in which the library is defined, the library type it is defined as, and the baseline library being processed. The following is a sample of the baseline library information line:

Application = FLOO Library Type = LOD Baseline Library name= PROD.BASE0.LOD

Component detail line

prints for every component processed. It contains the load component name, source component name, source library type, package name, directory SETSSI, baseline hash token, and package hash token. The following is a sample of the component detail line:

Load Source Library Package Directory Package Baseline PackageComponent Component Type Name SETSSI SETSSI Hash Hash

CMN$ACPM CMN$ACPM SRC FLOO001014 481F4167 481F4167 BAD43BF500000754 AD43BF500000754

CMN$STUB CMN$STUB SRC FLOO001014 481F4191 481F4191 67ED922300004030 7ED922300004030

CMN$UTIL CMN$UTIL SRC FLOO001014 481F4C58 481F4C58 ABF07A350003B4B1 BF07A350003B4B1

CMN$XMEM CMN$XMEM SRC FLOO001014 481F4CD8 481F4CD8 C04F3EEF000031FD 04F3EEF000031FD

201


Status line

prints for every component, below the affected component detail line (indented). The list Status Condition Messages (following the code below) describes component status values. The following is a sample of the status lines:

CMNAPI n/a n/a n/a 47826C12 ? ? ? Last baseline rippled package information not in the component history recordCMNAPIXM n/a n/a n/a 46EEA9E9 ? ? ? Orphan/new component - this component has not been baseline rippled by Change ManCMNAPI2 ? n/a ? 47287788 ? ? ? Last baseline rippled package information not in the component history recordCMNAPI3 ? ? ? 4703EABA ? ? ? Orphan/new component - this component has not been baseline rippled by Change Man

Status Condition Messages

The following table provides a description of the status condition message and its description.

Condition Message Description

BLANK status line The load component is in-synch with the source component.

Baseline/Package SETSSI not matching The SETSSI number within the baseline directory does not match the SETSSI in the package master load record. A third-party vendor product could have changed the baseline component SETSSI entry or the load module in baseline has been copied over.

Baseline/Package HASH not matching The hash token for the baseline component does not match the hash token in the package master source and load records. The source component could have been changed outside of ChangeMan ZMF, using ISPF edit, or the package master’s source and load records could have been corrupted.

Last baseline rippled Package not found Last baseline rippled package information not in the component history record. This load component is currently part of an active ChangeMan ZMF package. The package has not been through the life cycle, or baseline rippled.

Source baselines not defined The library type of this source component no longer exists with the application

Source Records not in Package Master The originating source and load component records are not in the package master or that package record within the package master could be corrupted.

Components not found in Source Baseline The originating source component for this load module is not in the SOURCE baseline library. The component was deleted or renamed in the baseline library.

202


Summary section

This section of the Baseline Analyzer report is a summary of the number of components processed and a count of each type of status condition message in the baseline data set report section. The summary section also gives the condition code on exit. The following is a sample of the summary section, which helps to identify and correct problems in your code.

Summary of Baseline Analyzer Activity:

Number of Components Processed = 762Number of Baseline/Package SETSSI does not match = 7Number of Baseline/Package HASH does not match = 0Number of last baseline rippled Package not found = 77Number of Source Baseline not defined = 0Number of Source Record not in Package Master = 0Number of Component not found in Source Baseline = 1Number of Stand alone load module = 0Number of Orphan/New Components = 596Number of Components in Synch = 81

CMN5400I - Time of day at end of job: 12:05:05 - Condition Code on exit: 04

Sample Baseline Analyzer Report

The sample Baseline Analyzer report for the excerpts and descriptions (above) of sections within the report follows.

SYSIN: APPL=FLOO SYSIN: TYPE=* SYSIN: APPL=JOHN SYSIN: TYPE=* CMN5400I - Time of day at end of job: 12:05:05 - Condition Code on exit: 04 CMNBASLN has a compile date/time of 05/12/1998 16.20 Baseline Analyzer (MVS - 5.3) MONDAY JULY 20, 1998 @ 12:05:05 Page 1Application = FLOO Library type = LOD Baseline Library name = PROD03.BASE0.LOD

Load Source Library Package Directory Package Baseline Package

Stand alone load modules The load component was not created by compiling a source component within a ChangeMan ZMF package. It is probably a vendor load module

Orphan/New Components This component has not been baseline rippled by ChangeMan ZMF. This load component has never been part of a ChangeMan ZMF package. There is no history record or information for this component.

Condition Message Description

203


Component Component Type Name SETSSI SETSSI Hash Hash

CMN$ACPM CMN$ACPM SRC FLOO001014 481F4167 481F4167 BAD43BF500000754 BAD43BF500000754

CMN$XMEM CMN$XMEM SRC FLOO001014 481F4CD8 481F4CD8 C04F3EEF000031FD C04F3EEF000031FD

CMNAPI n/a ? ? 47826C12 ? ? ? Last baseline rippled package information not in the component history recordCMNAPIXM ? ? ? 46EEA9E9 ? ? ? Orphan/new component - this component has not been baseline rippled by Change ManCMNAPPRV CMNAPPRV SRC FLOO001016 48203BB9 48203BB9 6BE2A9DE00048CA0 6BE2A9DE00048CA0

CMNATACH CMNATACH SRC FLOO001017 478E401C 48204470 E7521977000101D0 E7521977000101D0 Load baseline SETSSI does not match the package master SETSSICMNAUDRC n/a ? ? 46EEAE49 ? ? ? Last baseline rippled package information not in the component history recordCMNBAT10 CMNBAT10 SR2 FLOO001016 48203CE7 48203CE7 B3E2A18D0005934B B3E2A18D0005934B

Baseline Analyzer (MVS - 5.3) MONDAY JULY 20, 1998 @ 12:05:05 Page 2

Load Source Library Package Directory Package Baseline PackageComponent Component Type Name SETSSI SETSSI Hash Hash

CMNBAT50 CMNBAT50 SR2 FLOO001017 481EEEC5 48204525 E97E088200006C1D E97E088200006C1D Load baseline SETSSI does not match the package master SETSSICMNBAT90 CMNBAT90 SR2 FLOO001017 481EED19 48204550 A744966A0000655C A744966A0000655C Load baseline SETSSI does not match the package master SETSSICMNBIND CMNBIND LOD FLOO001014 481EED26 481EED26 ? 0000000000000000...

Summary of Baseline Analyzer Activity:Number of Components Processed = 762

Number of Baseline/Package SETSSI does not match = 7

Number of Baseline/Package HASH does not match = 0

Number of last baseline rippled Package not found = 77

Number of Source Baseline not defined = 0

Number of Source Record not in Package Master = 0

Number of Component not found in Source Baseline = 1

Number of Stand alone load module = 0

Number of Orphan/New Components = 596

Number of Components in Synch = 81

204


CMN5400I - Time of day at end of job: 12:05:05 - Condition Code on exit: 04

LINK DATE REPORT

The Link Date report lists the contents of every library concatenated in the STEPLIB DD statement of the SERNET started task that runs a ChangeMan ZMF instance. The purpose of the report is to help Serena diagnose problems you may report to Customer Support.

The report is the same whether it is run from global or application administration.

Link Date Report Example

This is an example of the Link Date Report.

********************************* TOP OF DATA ************************ Change Man Component Link Date Report (MVS - 5.3.0) SUNDAY JULY 1, 2001 @ 17:09 Data set being processed ===> PROD142.PROFSERV.APF.LOAD Member Link Name Date Time SETSSI CMNDB2SQ 20010525 120000 4DDE40C0 CMNVSRVC 20010221 120000 4D63A540 SERBSAM 20010327 160545 4D90B1D9 SERVERAO 20010601 120000 4DE77B40 Data set being processed ===> PROD99.CMN520Q.LOAD Member Link CMN$CSEC 20010627 173440 4E0A10B0 CMN$DSS 20010627 222853 4E0A55A5 CMN$PAPR 20010625 131718 4E07315E CMN$PCMD 20010628 150650 4E0B3F8A CMN$PCRT 20010625 131718 4E07315E CMN$PIDV 20010625 131718 4E07315E CMN$PILC 20010625 131718 4E07315E CMN$PISC 20010625 112252 4E07168C

SERENQ 20010103 120000 4D230BC0 SERPRINT 20010329 153233 4D934D11 SERREAL 20010103 120000 4D230BC0 Data set being processed ===> BH3DB2.DSN510.SDSNLOAD Member Link Name Date Time SETSSI

205


CMN6310I - No Change Man components to list within BH3DB2.DSN510.SDSNLOAD. Data set being processed ===> PROD99.APS300.LOAD Member Link Name Date Time SETSSI CMN6310I - No Change Man components to list within PROD99.APS300.LOAD . CMN5400I - Time of day at end of job: 17:09:09 - Condition Code on exit: 00******************************** BOTTOM OF DATA ***********************

Link Date Report Data

The ChangeMan ZMF version is printed in the first line of the report. The rest of the information displayed on the report is self explanatory.

206


207

HOUSEKEEPING TASKS 10ChangeMan ZMF Housekeeping Tasks are tasks that are normally performed outside of the ChangeMan ZMF ISPF interface; they allow you to protect and store your data as well as keep ChangeMan ZMF running at optimal performance levels.

The ChangeMan ZMF instance needs to be down if you are restoring, reorganizing or clearing the log file. You can backup when the ChangeMan ZMF instance is up, but remember that it may miss some updates that occur during that time period. For tasks requiring the ChangeMan ZMF instance to be down it is recommended that they be submitted periodically and at night (when the least number of users are affected). Sample JCL for housekeeping jobs is in the CMNZMF CNTL library delivered on the distribution CD or cartridge.

Note Housekeeping jobs are described in the Serena™ ChangeMan® ZMF Installation Guide. This chapter contains additional details about some of those jobs.

CLEANING UP BACKUP LIBRARIES

Backup Libraries are associated with ChangeMan ZMF Production Libraries. When a package is installed, the current version of a component is copied from the Production Library to the Backup Library so it can be restored if package is backed out.

You have three ways to handle the cleanup of Backup Libraries, and thereby manage the growth of components that accumulate in these data sets. By specifying the appropriate option as a PARM parameter on the JCL EXEC statement when running program CMNBATCH, you can do one of the following:

• Bypass cleanup of Backup Libraries (the default).

• Perform "Package" processing.

• Perform "Commit" processing.

Bypass Cleanup of Backup Libraries

To bypass cleanup of Backup Libraries, you can specify the parameter 'BACKUPLIB=N' for program CMNBATCH. This is the default, so specifying the BACKUPLIB parameter is optional. When CMNBATCH runs, the CMN920 transactions delete the Staging Libraries but no attempt is made to delete components from the Backup Libraries:

//CMNBATCH EXEC PGM=CMNBATCH,

208

Chapter 10: Housekeeping Tasks

// PARM='SUBSYS=?,BACKUPLIB=N'

Perform Package Processing for Backup Library Cleanup

If cleanup processing is required for your site and you plan to process Backup Libraries by package association, use package processing for cleanup of Backup Libraries. You can do this by specifying 'BACKUPLIB=P' in program CMNBATCH when executing this program for housekeeping purposes, as in the following JCL:

//CMNBATCH EXEC PGM=CMNBATCH,// PARM='SUBSYS=?,BACKUPLIB=P'

During “Package” processing, CMNBATCH calls the program CMNCLNUP. The component being deleted in the Backup Library is first compared to its corresponding component in the Staging Library. If the directory entries for both components match, CMNCLNUP deletes the component from the Backup Library. Because this only happens to packages that have been ‘memo deleted’ or has ‘aged’, you have ensured that a component deleted from the Backup Library came only from a specific Staging Library in a specific package.

The following discussion describes this type of clean up operation:

1. Assume that you created a package named PKG$000010 that contains the unique-named component 'XYZ0000'. When package PKG$000010 is installed, ChangeMan ZMF attempts to copy component “XYZ0000” from the production library associated with this package to the Backup Library in the CMN20 job. Because this component is unique and never resided in the production library, the IEBCOPY step that copies the component from the production library to the Backup Library ends with an RC=0004. At this time, the Backup Library has no component named “XYZ0000”. When CMN20 runs, the component “XYZ0000” is copied from the Staging Library to the production library. When CMN20 completes successfully and CMN30 executes, the baseline ripple happens.

209


Before In-stall

After Install

Staging Production Backup

Staging library for PKG$0010

contains component XYZ0000.



Production library for

application name PKG$ contains no component XYZ0000.

Backup library for application name PKG$ contains no component XYZ0000.

Backup library for application

name PKG$ has no components

named XYZ0000.

Production library for

application name PKG$

contains component

XYZ0000 from package

PKG$0010.

1 2XYZ0000

XYZ0000

XYZ0000

210


2. Assume that you created a package named PKG$000020 that contains component “XYZ0000” in the Staging Library. You make changes to the component, and schedule the package for installation. When the package is installed, the CMN20 job attempts to copy the component “XYZ0000” from the production library associated with this package to its corresponding Backup Library. Because a same-named component was previously-placed in the same production library by package PKG$000010, the IEBCOPY step backs up the component by performing a copy from the production library to the Backup Library. When IEBCOPY ends with an RC=0000, the Backup Library contains a component named “XYZ0000” from package PKG$000010. In the install step of CMN20, the next component “XYZ0000” from package PKG$000020 is copied from its Staging Library to the production library. As a result, the component “XYZ0000” from package PKG$000020 overlays the same-named component that was there previously from package PKG$000010. When CMN20 completes successfully and CMN30 executes, baseline ripple happens.

211





Staging library for PKG$0020 contains component XYZ0000.

Production library for application name PKG$

contains component name

XYZ0000 from PKG$0020.

Backup library for application name PKG$ contains

component name XYZ0000 from

PKG$0010.

XYZ0000

1

2

XYZ0000 XYZ0000

212


3. Assume that package PKG$000010 in BAS status has “aged”, so that the package is included in the CMN920 report, thereby creating the delete Staging Libraries transaction record for this package. This record becomes part of the SYSIN input for program CMNBATCH. PKG$000020 remains because it was installed at a later time and has not yet “aged”.

During housekeeping, the CMN920 report generates a delete Staging Library transaction record for PKG$000010. When CMNBATCH reads the delete Staging Libraries transaction record, it builds a table from the package master listing all the components in package PKG$000010 that reside in a single Staging Library. Thereafter, the data set names for the Staging Library, the production library, and the Backup Library (associated with package PKG$000010 for one library type) are placed in another table. Then, CMNBATCH calls program CMNCLNUP to pass the component list and library list tables. Program CMNCLNUP then opens (1) the staging data set for package PKG$000010 under the DDname of SYSUT1, and (2) the Backup Library for package PKG$000010 under the DDname of SYSUT2.

Next, program CMNCLNUP obtains the component name 'XYZ0000' from the component list and compare the directory entry for component 'XYZ0000' (from the Staging Library of package PKG$000010) to the directory entry of component 'XYZ0000' (in the Backup Library). If they match, you have ensured that component 'XYZ0000' in the Backup Library could only have arisen from package PKG$000010. Component 'XYZ0000' is deleted from the Backup Library. Alternatively, if the entries do not match, no deletion occurs. This ensures that any component being deleted from the Backup Library is directly associated only with the specific package.

213



PKG$0010

Package PKG$0020

Component XYZ0000 is

from package PKG$0020.

Component XYZ0000 is

from package PKG$0010.

XYZ0000

Package Mas-ter

CMNCLNUP

CMNBATCHCMNDELAY

Create CMN920Report

PackagePKG$0010

Ages

XYZ0000XYZ0000XYZ0000

SYSU

T2SYSUT1

214


Once all components are processed, CMNCLNUP returns to the CMNBATCH program, which builds a component list for the next library type of package PKG$000010, and calls CMNCLNUP again until all library types have been processed. Thereafter, the Staging Libraries are deleted for the package, and the next transaction record is read, and housekeeping resumes.

Because a component is tied directly to the package that is scheduled for deletion, this method of cleaning up the Backup Libraries is termed ‘package processing’.

When a site has been running ChangeMan ZMF for an extended period of time and cleanup of Backup Libraries has not been performed, the Backup Libraries might have grown substantially and they are populated with many components from many packages. By running prior housekeeping jobs without ‘clean up,’ many packages and their corresponding Staging Libraries have probably been deleted, leaving many of their associated components in their respective Backup Libraries. This might result in retaining many orphan components (in the Backup Library) that are not deleted when you run a cleanup. This is because before cleanup processing became available as a new feature, prior housekeeping jobs may have deleted the package records and Staging Library for an old component in the Backup Library.

As future packages are installed with the same named components as those in the Backup Library, the CMN20 job overlays old components in the Backup Library with the components being copied from the Production Library. Over time, the cleanup process matches components in the Backup Libraries from recently aged packages. This could take a long time, and if a component in a Backup Library never gets replaced it will always remain there.

Perform Commit Processing for Backup Library Cleanup

If your site requires that the cleanup of Backup Libraries to be handled by ‘commit’ processing, specify the keyword 'BACKUPLIB=C' for program CMNBATCH when executing this program for housekeeping, as follows:

//CMNBATCH EXEC PGM=CMNBATCH,// PARM='SUBSYS=?,BACKUPLIB=C'

'Commit' processing differs from 'Package' processing in that the latter is a two-library “compare and delete” operation whereas former is a three-library operation. 'Commit' processing means that once a component has been installed in the production library and the package for that component has reached its aging criteria, you intend to commit that component to production and to remove any same-named components in the Backup Library regardless of the originating package. You are essentially committing the component in the production library. Provided the components for all aged packages in production are functionally stable, committing the components enables you to manage growth in the Backup Libraries for your ChangeMan ZMF system.

During 'Commit' processing, a component in the Staging Library is compared to the same-named component in the production library. If the directory entries for these components match, then the component is arbitrarily deleted from the Backup Library. During 'Package' cleanup, in contrast, the Staging Library and the Backup Library are compared to determine if the component is in the Backup Library.

215


The following steps describes the ‘Commit’ processing.

1. Assume that you create a package called PKG@000100 that contains component 'ABC00001' in the Staging Library. Next, you change the component and schedule the package for installation. When the package is installed, the CMN20 job attempts to copy a component named 'ABC00001' from the production library associated with this package to its corresponding Backup Library.

If a same-named component was previously-placed in the same production library by a previously installed package, the IEBCOPY step backs up the component by copying it from the production library to the Backup Library. The Backup Library then has a component named 'ABC00001' from a previous package. When CMN20 runs, the same-named component 'ABC00001' from package PKG@000100 is copied from its Staging Library to the production library. As a result, the component 'ABC00001' from package PKG@000100 overlays the same-named component that was there previously. When CMN20 completes successfully, the CMN30 job executes a baseline ripple for package PKG@000100, with the following result:

216



Staging library contains

component named

ABC00001 from any previously

installed change package

Staging Library for PKG$0010

contains component ABC00001.

Production library for application name PKG$

contains component name ABC00001 from PKG$000100.

Backup library for application name PKG$ contains

component name ABC00001 from any previously

installed change package.

1

2

ABC00001

ABC00001ABC00001ABC00001

217


2. Assume that package PKG@000100 in BAS status has reached its aging criteria so that it is included in the CMN920 report that creates the delete Staging Libraries transaction record for this package. Next, program CMNBATCH is executed with the parm keyword of 'BACKUPLIB=C' in the EXEC statement. Then, the package that will be cleaned up is identified from the delete Staging Libraries transaction record. Next, program CMNBATCH extracts information from the package master to build a table listing all the components for package PKG@000100 that reside in a single Staging Library. The component name list only contains components that are known to ChangeMan ZMF for that package.

In this example, the component list would only contain 'ABC00001' because it was the only component in package PKG@000100. Next, the data set names for the Staging Library, the production library, and the Backup Library associated with package PKG@000100 (for one library type) are placed in another table. Finally, CMNBATCH calls program CMNCLNUP and passes the component list and library names list.

Once CMNCLNUP accesses the data set names table, it opens the following:

— Staging data set for package PKG@000100 under the ddname of SYSUT1.

— Production library for package PKG@000100 under the ddname of SYSC$DSN.

— Backup library data set for package PKG@000100 under the ddname SYSUT2.

Next, CMNCLNUP accesses the component names list table to obtain the component 'ABC00001’. Program CMNCLNUP compares the directory entry for component ‘ABC00001’ from the SYSUT1 Staging Library of package PKG@000100 to the directory entry of the same-named component in the SYSC$DSN production library. If the entries match, you have verified that the component 'ABC00001' in the production library must have come from package PKG@000100, and component ‘ABC00001' is deleted from the Backup Library represented by ddname SYSUT2 regardless of the source package.

218


If the directory entries do not match, then deletion does not occur. This means that any component residing in the Backup Library with the same name as the component being compared in the Staging and Production Libraries is deleted if the components match.


Staging Library contains

component ABC00001from PKG$000100.

Staging Library contains component named

ABC00001. This Staging Library is from any previously

installed package, and this library may already be

deleted from a prior execution of housekeeping.

Production Library contains same component

ABC00001 from package PKG$000100.

Backup Library contains a component

ABC00001 from any previously

installed package.

ABC00001

Package Mas-terCMNCLNUP

CMNBATCHCMNDELAY

Create CMN920Report.

PackagePKG$0010

Ages.

ABC00001ABC00001ABC00001

SY

SUT1 SY

SUT2

SY

S$D

SN

219


Considerations for Cleaning up Backup Libraries

Cleanup to the Backup Libraries whether by package processing or commit processing results in you being unable to perform a Backout. In deciding whether to use package processing or commit processing, consider the time packages are aged and the length of time that packages remain in development before they are eventually installed in production. Commit processing of the Backup Libraries is the most conservative implementation of a cleanup process because deletion occurs based on aging of the package currently in production. In setting the aging of the Staging Library by number of days, the installation can judge when the component in the Production Library has reached a point of functional stability such that the component in the Backup Library is no longer required and can be safely removed. This means stability in a component is based on its execution in production over a period of time with no problems after which you can release space occupied by the Staging Libraries and delete the backup component from the Backup Library. In commit processing whatever number of days you specify to age the Staging Libraries is the number of days that a backup component can be expected to remain in the Backup Library.

With package processing deletion occurs based only on aging of the package. Package processing would be used less often than commit processing. Low activity packages with long aging criteria and short install intervals with infrequent housekeeping runs could use package processing to manage the Backup Libraries. With package processing there is the possibility that a package could start its 90 day aging on June 1 when it is installed. A second package containing the same component name could be created on June 1 and install on August 30 resulting in the old component from the first package being copied from the production library to the Backup Library. Housekeeping could run that night where the first package installed June 1 has now aged resulting in the backup component being deleted within a day of the second package being installed. This would impact your ability to backout from the second package. For high activity applications containing many packages in motion with varying install intervals and short aging criteria where you run housekeeping frequently, use commit processing to ensure that the backup for a component in production remains in the Backup Library for at least the number of days specified in Application Administration for the aging of the Staging Libraries.

Cleanup performs all comparisons between the directory entry for each member in their respective library. Every field in the directory entry for a member is compared to its corresponding field in the directory entry for the same named member in the other library. Cleanup does not read the entire PDS directory for the Staging Library and compare for all members found. Cleanup gets its member list from the package master for the package that has aged and searches the Staging Library for the member name. If you allow the Staging Library to be used as a repository for members outside of ChangeMan ZMF, the cleanup process does not include them. Since only components known to ChangeMan ZMF are included, the comparison process between members based on only the directory entry is accurate.

220


Consider when a site has been running ChangeMan ZMF for an extended period of time and the cleanup of the Backup Libraries has not been implemented. The Backup Libraries may have experienced substantial growth over this time period, and the Backup Libraries are populated with many components from many packages. With the running of prior housekeeping jobs without cleanup of the Backup Libraries many packages and their corresponding Staging Libraries have probably been deleted leaving many of their associated components residing in their respective Backup Libraries. This results in the possibility of leaving many orphan components in the Backup Library which are not deleted when you start running a new cleanup process with your housekeeping task.

This is because there is no package record or Staging Library available to perform a compare against what resides in the Backup Library for a package that prior housekeeping has deleted. As packages are installed in the future with the same named components as those that exist in the Backup Library, the result is old components are overlaid in the Backup Library with the components being copied from the production library as part of the CMN20 job. Over time the cleanup process catches up with delete processing as it encounters more hits in the Backup Libraries from recently aged packages. This catch up process could take an extended period of time, and if a component in a Backup Library never gets replaced it will always remain.

The cleanup process follows the parameters specified at Application Administration, Option B, Baseline Configuration, Panel CMNBAS1 where the customer site sets the ‘Install in Prod’ indicators to ‘N’, ‘Y’, or ‘C’. During the cleanup process a read is performed to the package master for General Record 4 (library types) to identify all of the library types defined just to the package that has aged or is in memo delete status. Then a read is performed to Local Record 4 (baseline libraries) where the baseline install indicator is checked. If the library type is defined to the package but the ‘Install in Prod’ indicator is set to ‘N’, then cleanup excludes the library. The cleanup process picks up only the library types defined in General Record 4 that have a corresponding library type in Local Record 4 with the install indicator set to ‘Y’ or ‘C’. Next Local Record 5 (Production Libraries) is read to obtain the data set names of the production libraries.

When cleaning up the Backup Libraries (for packages) with either 'package' or 'commit' processing, consider the following:

• From the Baseline Configuration Panel (CMNCBAS1) during Application Administration, check the “Install in Prod” indicator setting. If the baseline library type is defined to the package but the indicator is set to N, then cleanup excludes the Backup Library for that same library type.

• From the Production Libraries Panel (CMNCPRDL) during Application Administration, check whether the production libraries are defined. The cleanup process checks for the baseline install indicator and for the presence of production libraries defined in the package master to decide which Backup Libraries are subject to cleanup processing.

• From the Application Parameters Panel (CMNGLP02), during Application Administration, check the aging criteria established for Installed Packages and Staging Data Sets.

221


• Changing this number might generate two separate transactions on different dates, one to remove package records from the package master and one to delete the Staging Libraries. Cleanup processing reads the package records and requires the Staging Libraries for the comparison.

• Therefore, the package records and the Staging Libraries must both exist during cleanup processing. So, for proper housekeeping, the Installed Packages value must be greater than or equal to the Staging Data Sets value.

• Because the cleanup process deletes components from the Backup Library, you have no backout capability. Furthermore, you must maintain unique component names if you choose to perform “commit” processing and share the same Backup Library among different applications.

RUNNING REPORTS

Reports can be run individually from inside ChangeMan ZMF using the R option on the Administration Global and Application menus, using Option 6 on the Primary Option menu, or you can submit them as a batch processing job. The JCL provided with ChangeMan ZMF runs all reports for all applications at your site. They can be run from the package master (VSAM file) or a backup (flat file).

There are two JCL members provided in the CMNZMF CNTL library:

• REPORTS

Uses the customizable SAS program which allows you to create your own reports.

• REPORTS2

Uses a program which assumes you do not want to create your own reports.

Refer to the actual JCL member for details on the steps of both batch jobs, and be aware of the following:

• SAS control cards must be prepared. For an explanation, see “Defining and Running ChangeMan ZMF Reports” on page 183.

• Report 920 identifies aged packages and Staging Libraries. Transactions are written to the tranfile DDNAME (if not dummied out) and actioned in program CMNBATCH (instead of the “batch” step).

• Report 930 re-synchs the implementation calendars. Transactions are written to the tranfile DDNAME (if not dummied out) and actioned in program CMNBATCH (instead of the “batch” step).

• If the report task is to be executed under a ChangeMan ZMF subsystem, be sure that the SUBSYS parameter, along with the actual SUBSYSTEMS ID, is coded within the EXEC card of the CMNBATCH step.

• If the ChangeMan ZMF instance is DOWN when housekeeping is executed, the BATCH step receives an RC=6. This just acknowledges that the ChangeMan ZMF instance is down and that all transactions are written to the DELAY file. Execution begins when the task is brought up again.

222


LOG ACTIVITIES (CMNBAT30)CMNBAT30 is a report writer that processes and prints selected log inquiries. This batch program generates the Log Activity Report (CMN020) in batch mode.

223

INDEX

Symbols#, field description 89

Aaccess

development libraries 32grant user 33personal libraries 32purge batch job output 34session utility data sets 33submitting batch jobs 33view batch job output 34

administrationapplication

setting up 97general checklist 52global 192

compiling procedures 80, 123installation calendar 88parameters 56reason codes 81

languages, determining 79, 122administrator

application 16general 16global 15security 16

aging installed packagesfield description 59, 109

aging staging datasetsfield description 59, 109

allocatebaseline libraries 26production libraries 27promotion libraries 27staging libraries 26

Allocate Dataset panel (CMNALCDS) 146

allow application update to filefield description 64

allow checkout to personal lib 103allow concurrent checkout

field description 65, 103allow temporary packages

field description 62, 102appl

field description 87, 99application

administrator 16application administration

affect of global settings 97setting up 97

Application Baseline Configuration Part 2 of 2 panel (CMNCBAS2) 145

Application Compile Procedures panel (CMNCLPRC) 123

Application Component General Information panel (CMNCMPG1) 148

Application Component Information Options menu (CMNCMP00) 147

application descriptionfield description 101

Application Language Names panel (CMNCLLNG) 123

application packages, monitoring 163application parameters

setting 100staging library allocation 39

Application Parameters Part 1 of 2 panel (CMNGLP01) 101

Application Selectable Options panel 155

applicationsdeleting 154field description 155setting up remote sites for 176

approvaldescribed 22

approval lists 38planned 40

setting up 124, 127unplanned 40

approver descriptionfield description 125, 127

approver notification vehiclefield description 63

audit

description 21recompile 21relink 21

audit levelfield description 65, 102

Bbackout

management facilities 23

backup libraries, cleaning up 207

Backup Library Cleanup 214baseline

allocate libraries 26keep by site 40libraries 23

recommendations 32using for production libraries

27baseline analyzer

accessingglobal administration 192

reportsdata set report 199

status condition messages 201using 199

Baseline Configuration Part 1 of 2 panel (CMNCBAS1) 144

Baseline Driven Component List panel 148

baseline librariesconfiguring 144

batch joboutput

purging 34viewing 34

submitting access 33block size

field description 78, 118

business hours, normal 36

Ccalendar

224

Index

installationdisable 36setting up 88

planned installation 35Change Man delay file

field description 85, 178Change Man environment

field description 175change package

allow temporary 35defined 19

change requesttrack 35

check 29

checklist, implementation 50checkout

concurrent 37description 20enforcement 36

checkout component activity filefield description 78, 118

checkout component descriptionfield description 78, 118

checkout enforcement rulefield description 65, 103

Cleaning up Backup Libraries 219

CMNBAT10 186

CMNBATCH 208, 214

CMNCLNUP 208

CMNCMPP2 152

CMNDPUP1 95

CMNDPUP2 95

CMNGBSOP 155

CMNGGP04 70

CMNQRYL1 164

CMNQRYL2 165

CMNSAS10 185code

column description 81codes

transaction 167column descriptions

code 81description 81, 124language 80, 124procedure 81, 124reason description 81

compile parmsfield description 151

compile procedurefield description 150

Compile Procedure List panel (CMNPRCNM) 80

compiling proceduresglobal administration 80, 123

componentgeneral information, defining 147production installation, 23security 152storing 23

component activity file typefield description 78, 118

Component Driven List panel 152Component General Description

panel (CMNCMPG3) 149Component Level Security List panel

(CMNCMPS1) 153

Component List panel (CMNCMPP2) 152

component namefield description 150

Component User List panel (CMNCMPS2) 154

componentssecured 38

concurrent checkout 37configuring

baseline libraries 144production libraries 158promotion environments 132promotion libraries 132remote sites 173

configuring remote promotion 43

Confirm Delete panel (CMNDPROJ) 154

customizedescriptions 25skeleton 25

customizingskeletons 175

Ddata set

accessing session utility 33data set name

field descriptions 158Dataset Information panel

(CMNDSINF) 146dataset type

field description 78, 118DB2

option description 94DB2 pre-compile

field description 151

debugging, link date report 204default unit name

field description 57, 85, 110, 178default volume serial

field description 57, 85, 178defer

field description 75, 115defining

component general information 147

deleting, application 154

delta deck 23department number

track change request by 35description

field description 74, 87, 99, 114descriptions

column description 81, 124dev model dsname

field description 71development

librariesaccess 32

directory blocksfield description 77, 117

Eedit staging recovery mode on

field description 111emergency changes

described 24enforcement

checkout 36

entity 29defining names 28name

limiting access 29securing libraries 30

entity check if 2 abovefield description 104

entity check if level 2field description 103

exitimplementing 25

extra user optionsfield description 151

Ffield description

field descriptionsallow checkout to personal lib

225


103promotion/demotion rule 105

field descriptions# 89aging installed packages 59, 109aging staging datasets 59, 109allow application update to file 64allow concurrent checkout 65, 103allow temporary packages 62, 102appl 87, 99application 155application description 101approver description 125, 127approver notification vehicle 63audit level 65, 102block size 78, 118Change Man delay file 85, 178Change Man environment 175checkout component activity file

78, 118checkout component description

78, 118checkout enforcement rule 65, 103compile parms 151compile procedure 150component activity file type 78,

118component name 150data set name 158dataset type 78, 118DB2 pre-compile 151default unit name 57, 85, 110, 178default volume serial 57, 85, 178defer 75, 115description 74, 87, 99, 114dev model dsname 71directory blocks 77, 117edit staging recovery mode on 111entity check if 2 above 104entity check if level 2 103extra user options 151force option 151forced demotion (Y/N) 135generic unit name 77, 117global notification file name 64heirarchical approval process 110highest # 99highest package 155install in PRD 145installation job scheduler 58, 175interfacing approver (Y/N) 125internal reader class 135

job entry system 57keep baseline by site 62, 102language name 150levels 144lib type 74, 114LIBRARIAN 61library type 150link edit parms 151logical unit or subsystem name 175logical unit or system name 57logical unit/system name 85, 178normal business hours 58, 102optional model to copy 101optional skeleton release ID 101order no. 125, 128overlay prior staged component

104overlay prior staged module 66PRD staging model dsname 85,

178primary quantity 77, 117promotion/demotion rule 67record format 78, 118record length 78, 118release ID 155remote site job card information

86, 178require department number 62,

110require work request number 62,

110save to personal & staging libs 110secondary quantity 77, 117security entity 125, 127security system 57site node name 175space units 77, 117staging restriction level 103starting date1 89subsystem 56target LOD type 75, 115totals # 89totals max 89transmission vehicle 58, 86, 175,

178type 144, 158validate version during staging 105volume serial 77, 117

force optionfield description 151

forced demotion (Y/N)field description 135

freezedescribed 22

Ggeneral

administrator 16generic unit name

field description 77, 117global

administrator 15

global administration 192compiling procedures 80, 123installation calendar 88languages, determining 79, 122parameters 56reason codes 81remote sites, setting up 174

Global Administration Options menu (CMNGAMEN) 55, 187, 194

Global Language Names panel (CMNGGLNG) 79

Global Library Types Part 1 of 1 Table 74

Global Library Types Part 1 of 2 panel (CMNCGLT0) 73

Global Library Types Part 2 of 2 panel (CMNCGLT1 76

global notification file namefield description 64

global parameterssetting up 56staging library allocation 39

Global Parameters panel, part 4 of 5 70

Global Parameters Part 1 of 5 panel (CMNGGP01) 56


Global Parameters Part 3 of 5 panel (CMNGGP03) 64–65, 68, 106

Global Parameters Part 4 of 5 panel (CMNGGP04) 68, 70, 106, 109


Global Selectable Options panel (CMNGBSOP) 94

grantuser access 33

Hheirarchical approval process

field description 110highest #

field description 99highest package

226

Index

field description 155housekeeping tasks

about 207

Iimpact analysis

description 19

implementation checklist 50INFO

option description 94install in PRD

field description 145installation

guide 11installation calendar

disable 36planned 35setting up 88

installation job schedulerfield description 58, 175

installation proceduresnetwork data mover 180

interfacing approver (Y/N)field description 125

internal reader classfield description 135

internal schedulermonitoring 170

internally scheduled packagesacting on 171reviewing 171

internet supportdescribed 12

Jjob entry system


Kkeep baseline by site 40


LLAM

see library access methodlanguage

column description 80, 124language name


languages, determining 79, 122levels

field description 144lib type

field description 74, 114field description see also type

LIBRARIANfield description 61

librariesallocate baseline 26cleaning up 207

libraryaccessing development 32accessing personal 32allocate production 27allocate promotion 27baseline recommendations 32entity names 29managing space 26recommended formats 31securing 30

library access method (LAM) 61library type

field description 150library types

reserved 74, 114lifecycle

single-site configuration 19

like load 75, 115

Limbo Package List panel 165link date

report 204link edit parms

field description 151Lock/Unlock Applications panel

(CMNGBULP) 87

Log Activity Report (CMN020) 222logical unit or subsystem name

field description 175logical unit or system name

field description 57logical unit/system name


Mmessages, baseline analyzer status

condition 201

Monitor Option panel (CMNMONIT) 164

Monitor Packages in Limbo panel 164Monitor Packages in Limbo panel

(CMNQRYL1) 164

monitoringapplication packages 163internal scheduler 170site packages 163

NNetwork Data Mover (NDM) 180normal business hours

described 36field description 58, 102

Ooption descriptions

DB2 94INFO 94

optional component descriptions, defining 147

optional model to copyfield description 101

optional skeleton release IDfield description 101

order no.field description 125, 128

overlayprior staged component 36

overlay prior staged componentfield description 104

overlay prior staged modulefield description 66

Ppackage master 153Package Master Driven Component

List panel (CMNCMP01) 148

Package User Records 95packages

internally scheduledacting on 171reviewing 171

monitoringapplication 163site 163

panelsCMNCMPP2 152CMNGAMEN (Global

Administration Options menu) 55, 187, 194

CMNGGP01 (Global Parameters Part 1 of 5 panel 56

CMNGGP01 (Global Parameters Part 1 of 5 panel) 56

227




CMNGGP04 70CMNGGP04 (Global Parameters

Part 4 of 5 panel) 68, 70, 106, 109

CMNQRYL1 164CMNQRYL2 165Component Driven List 152Global Parameters, part 4 of 5 70Limbo Package List 165Monitor Packages in Limbo 164

parametersapplication, setting 100

personallibrary

access 32

plannedinstallation calendar 35

planned approval list 40setting up 124, 127

Planned Approvals Part 1 of 2 panel (CMNCAPLD) 124, 127

Planned Approvals Part 2 of 2 panel (CMNCAPL1) 126, 128

Planned Installation Calendar panel (CMNCLNDR) 88

PRD staging model dsnamefield description 85, 178

pre-implementationconsiderations 25

primary quantityfield description 77, 117

procedure 147column description 81, 124

proceduresdesignated 38

producing reportsabout 183

productlatest information 12

productionallocate libraries 27component installation 23libraries

setting up remote sites for 28using baseline libraries for 27

libraryrecommendations 32

production librariesconfiguring 158

Production Libraries panel (CMNCPRDL) 158

promotionallocate libraries 27approvals during 47described 22remote

overview 173promotion environments

configuring 132promotion libraries

configuring 132promotion/demotion rule


RReason Code List panel

(CMNRSNCD) 81reason codes

global administration 81reason description

column description 81recompile

described 21record format

field description 78, 118record length

field description 78, 118recovery mode

staging 39release ID

field description 155relink

described 21remote

promotionhow administrators can config-

ure 43remote promotion

about 173how does it work 173overview 173

remote sitesetting up for production libraries

28remote site job card information

field description 86, 178remote sites

configuring 173maintaining 175setting up for applications 176setting up globally 174sites

remote 40

reportsbaseline analyzer report 199

link date 204producing 183running 221

require department numberfield description 62, 110

require work request numberfield description 62, 110

restriction levelstaging 37

reversedelta deck 23

SSAS

reports 185save to personal & staging libs

field description 110scheduler see internal schedulersecondary quantity

field description 77, 117secure

libraries 30

security 147administrator 16component 152setting up 28

security entityfield description 125, 127

security systemfield description 57

SERENAmailing list

subscribing 12session utility data set

accessing 33single-site configuration

lifecycle 19site node name

field description 175site packages

monitoring 163skeleton

customize 25skeletons

customizing 175space

managing library 26space units

field description 77, 117stage

overlay prior staged component 36staging

description 20

228

Index

recovery mode 39restriction level 37validate version during staging 37

staging librariesallocating 26

staging libraryallocation

global parameters 39

staging library allocationapplication parameters 39

staging restriction levelfield description 103

starting date1field description 89

submitbatch jobs 33

subsystemfield description 56

supportinternet 12

Ttarget LOD type

field description 75, 115temporary

allow change package 35library

recommendations 32

totals #field description 89

totals maxfield description 89

trackchange request 35

transaction codes 167transmission vehicle

field description 58, 86, 175, 178type


Uunplanned approval list 40user access

granting 33user options

query 40

Vvalidate version during staging

field description 105volume serial


Wwork request

track change request by 35

Changeman Administrator Guide

Documents

Transcript of Changeman Administrator Guide