Aldon/CMS User’s Guide User’s Guide UG
Aldon/CMS™ Change Management System for the IBM iSeries
User’s Guide Version 7.2, Revised October 21, 2003
Aldon Computer Group, Inc. 6001 Shellmound Ave. #600, Emeryville, CA 94608 +1.510.839.3535 Fax +1.510.839.2894
Copyright © 1994-2003 by Aldon Computer Group, Inc. All rights reserved. The information contained in this manual is subject to change without notice and does not represent a commitment on the part of Aldon Computer Group, Inc. Aldon Computer Group, Inc. makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Aldon Computer Group, Inc. shall not be liable for errors contained in this manual or for incidental or consequential damages in connection with the furnishing, performance or use of this material. Trademarks and Registered Trademarks Aldon®, Aldon/CMS, Aldon/CMS Requester Module, Aldon Workbench, Analyzer, Harmonizer Plus, and S/Compare-Harmonizer are trademarks of Aldon Computer Group, Inc. Adobe, and Acrobat are trademarks of Adobe Systems Incorporated. Pentium and Intel are registered trademarks of Intel Corporation. 400, DB2, IBM, ILE, Integrated Language Environment, iSeries, OS/400, SQL/400, and VisualAge are trademarks of International Business Machines Corporation. Microsoft, Windows, Visual C++, and Windows NT are registered trademarks of Microsoft Corporation. Java is a trademark of Sun Microsystems, Inc. All other brand or product names are trademarks or registered trademarks of their respective companies or organizations. Aldon Computer Group, Inc. 6001 Shellmound Avenue #600 Emeryville, CA 94608-1924 Phone: +1.510.839.3535 Fax: +1.510.839.2894 Email:
[email protected] World Wide Web: www.aldon.com
Aldon/CMS User’s Guide User’s Guide UG
Aldon/CMS User’s Guide Contents Chapter 1 Introduction
UG 1-1
What is Aldon/CMS? .........................................................................................UG 1-2 About this Document ..........................................................................................UG 1-2 Basic Terms and Concepts .................................................................................UG 1-3 Group .....................................................................................................UG 1-3 Application ............................................................................................UG 1-3 Release ..................................................................................................UG 1-3 Environment ..........................................................................................UG 1-3 Object ....................................................................................................UG 1-4 Types of Objects Handled .....................................................................UG 1-5 Comprehensive View of Objects ...........................................................UG 1-5 Object Movement ..................................................................................UG 1-6 Library Groups ......................................................................................UG 1-7
Chapter 2 Basics
UG 2-1
Starting Aldon/CMS ...........................................................................................UG 2-2 Setting User Preferences ....................................................................................UG 2-3 Setting Your Preferences .......................................................................UG 2-4 Checking Out Objects ........................................................................................UG 2-5 Checking Out Different Types of Objects .............................................UG 2-5 Selecting the Correct Copy of the Object ..............................................UG 2-6 Development Tips .................................................................................UG 2-6 Checking Out From Production ............................................................UG 2-8 Checking Out From a Test Environment ..............................................UG 2-9 Editing Source ..................................................................................................UG 2-10 Compiling .........................................................................................................UG 2-11 Creating Objects ..................................................................................UG 2-14 Working with Create Parameters ........................................................UG 2-15 Promoting Objects ............................................................................................UG 2-17 Installing Live ...................................................................................................UG 2-22 Overview .............................................................................................UG 2-24 Install Live Concepts ...........................................................................UG 2-26 Installing Live on Promote ..................................................................UG 2-27
Aldon/CMS User’s Guide
Contents • UG iii
Installing Live Outside of the Promote Function ................................ UG 2-29 Working with Dependent Objects .................................................................... UG 2-32 Acquiring Object Dependency Data ................................................... UG 2-34 Scanning for Object Dependencies ..................................................... UG 2-35 Specifying Object Dependencies ........................................................ UG 2-36 Acting Upon Dependent Objects ........................................................ UG 2-37 Emergency Checkout and Promotion .............................................................. UG 2-41 Resolving Conflicts .......................................................................................... UG 2-42 Conflicts and Conflict Condition Records .......................................... UG 2-42 Harmonizer and ACMS ...................................................................... UG 2-43 Working with Conflict Records .......................................................... UG 2-43 Resolving and Clearing Checkout Conflicts ....................................... UG 2-45 Restricting Promotes ........................................................................................ UG 2-47 Establishing and Meeting Testing Standards with ANALYZER .................... UG 2-49 Overview of the Aldon/CMS-ANALYZER Interface ........................ UG 2-49 How ANALYZER and Aldon/CMS Work Together ......................... UG 2-50 Additional Analyzer Concepts ............................................................ UG 2-51 Details of Instrumenting and Setting Testing Requirements .............. UG 2-51 Procedures for Using ANALYZER with ACMS ............................... UG 2-53
Chapter 3 Additional Features
UG 3-1
Development Log ............................................................................................... UG 3-2 Archiving ........................................................................................................... UG 3-3 Using Emergency Checkout on an Archived Object ............................ UG 3-5 Object Distribution ............................................................................................. UG 3-6 Task Tracking System ........................................................................................ UG 3-7 Adding a Task ....................................................................................... UG 3-8 Using the Aldon Response Manager Interface ................................... UG 3-12 Managing Tasks .................................................................................. UG 3-13 Checking out and Promoting Objects in Tasks ................................... UG 3-13 Working with Task Hours ................................................................... UG 3-15 User Requests ................................................................................................... UG 3-16 Interface Options for Submitting User Requests ................................ UG 3-17 What Happens to Submitted User Requests? ..................................... UG 3-17 User Requests from Within Aldon/CMS ............................................ UG 3-17 User Requests from the iSeries outside of Aldon/CMS ..................... UG 3-18 Verifying Objects ............................................................................................. UG 3-19
Chapter 4 User Interface
UG 4-1
Available Interfaces ........................................................................................... UG 4-2 Summary of Panel Interface Features ................................................................ UG 4-2 Common User Access Standards .......................................................... UG 4-2
UG iv • Contents
Aldon/CMS User’s Guide
Context-Sensitive Help Text .................................................................UG 4-2 Input Fields: Prompting and Selecting ..................................................UG 4-3 Scrolling ................................................................................................UG 4-3 Fully Functional Command Line ..........................................................UG 4-4 WRKSBMJOB and WRKSPLF Access ...............................................UG 4-4 Setting Advanced User Preferences ...................................................................UG 4-4 Subsetting ...........................................................................................................UG 4-9
Chapter 5 Additional Actions
UG 5-1
Adding an Object ................................................................................................UG 5-2 When to Add an Object to Aldon/CMS ................................................UG 5-2 Object Addition Concepts .....................................................................UG 5-2 Working with Pseudo-Source .............................................................................UG 5-6 Example of Pseudo-Source for a Message File ...................................UG 5-10 Deleting a Copy of an Object ...........................................................................UG 5-10 Deleting the Production Copy of an Object ........................................UG 5-11 Using Data Libraries for Testing ......................................................................UG 5-11 Update DVP Data Sets After Modifying Checked Out Files ..............UG 5-12 Additional Task Actions ...................................................................................UG 5-12 Responding to User Requests ..............................................................UG 5-12 Adding Objects to a Task ....................................................................UG 5-15 Removing Objects from Tasks ............................................................UG 5-16 Changing a Task ..................................................................................UG 5-17 Updating the Task Status Field ...........................................................UG 5-17
Chapter 6 Multiple-Release Applications
UG 6-1
Aldon/CMS Works with Multiple Releases .......................................................UG 6-2 Expanding the Definition of “Release” .................................................UG 6-2 Two Release Types: Base and Delta .....................................................UG 6-3 Relationships Between Releases ...........................................................UG 6-4 Aldon/CMS Features with Multiple Releases ....................................................UG 6-5
Glossary
UG Gloss-1
About this Glossary .................................................................................... UG Gloss-1 Glossary Terms ........................................................................................... UG Gloss-1
Aldon/CMS User’s Guide Index
Aldon/CMS User’s Guide
UG Index-1
Contents • UG v
UG vi • Contents
Aldon/CMS User’s Guide
Aldon/CMS User’s Guide User’s Guide UG
Chapter 1 Introduction
This chapter introduces Aldon’s Change Management System, explains the purpose of this guide, and provides an explanation of basic terms and concepts you will need to understand to use the application effectively. The following topics are included: • “What is Aldon/CMS?” on page UG 1-2 • “About this Document” on page UG 1-2 • “Basic Terms and Concepts” on page UG 1-3 Online Help Text
Aldon/CMS User’s Guide
For detailed descriptions of the fields, options, and function keys displayed or available at any of the panels shown in this document, please see the online help text.
Introduction • UG 1-1
What is Aldon/CMS? Aldon’s Change Management System (ACMS) helps you develop quality programs quickly and economically, by providing tools for planning, executing, monitoring, and controlling the software development process. ACMS helps you implement the standards, rules, and structures you specify to balance your needs for security, flexibility, and ease of use. In addition, ACMS keeps track of all changes to create a complete audit trail. A wide variety of interface options allows programmers to work in different environments. You use ACMS to: • Improve quality • Increase productivity • Make development work easier • Standardize your development methods • Reduce the learning curve for new staff and at project startup • Improve communications • Secure software assets • Provide an audit trail
About this Document The goal of this document is to provide programmers and quality assurance personnel with the information they need to perform all common daily activities using ACMS. This document: • Describes the most convenient way to perform each action while also mentioning some alternative methods • Introduces functions used for task management and object distribution • Directs readers to the relevant sections of the “Aldon/CMS Daily Operations Reference” and “Aldon/CMS Setup and Administration Reference” for complete information
UG 1-2 • Introduction
Aldon/CMS User’s Guide
Scope of this Document
The examples shown in this document assume a single release application. This means that all objects for the application reside in a single set of libraries. Some additional fields and field values appear on panels when working in a multiple-release application. Use the online help text for assistance with these fields. “Chapter 6, Multiple-Release Applications” provides a discussion of some issues unique to a multiple-release application.
Basic Terms and Concepts Group A group or application group is a named category that lets you group applications together to simplify management. For example, you could group applications by vendor, or by function. You could also put all applications in one group.
Application With ACMS, related objects are defined as an application. For example, one application may contain objects required for managing a manufacturing operation. Another may contain objects used to manage personnel and human resources.
Release If an application is developed using a single release, the term release refers to the set of libraries that contain the objects that make up the application.
Environment As objects move through the stages of development, they move through corresponding ACMS environments. An environment consists of one or more libraries, organized to operate as a function-specific unit. Environments have relationships, predefined by ACMS, to the libraries of other environments. The predefined relationships orchestrate movement of objects into and out of environment libraries. You define environments during the release setup. See “Defining a Release” starting on page SA 13-1 in the "Aldon/CMS Setup and Administration Reference" for more information on release setup.
Aldon/CMS User’s Guide
Introduction • UG 1-3
ACMS supports up to four environments for each release: • Development • Integration (optional) • Quality Assurance (optional) • Production Unlimited Number of Environments Supported
If you need to structure your development effort into more than four environments, you can define child or delta releases subordinate to your main (base) release. Each child release can also have up to four environments. See “Chapter 6, Multiple-Release Applications” for more information. Development, Integration and Quality Assurance are sometimes referred to as the active environments. Objects in these environments are being modified or tested.
Check Out
Development
Integration
Quality Assurance
Production
Promote
Figure 1 - ACMS Environments and Object Movement
Environment Model Benefits
You can simplify development work and reduce the learning curve for new employees or contractors by organizing releases into environments with consistent naming conventions.
Object ACMS recognizes an object as a unique combination of application name, object name, and object type. Within an application, all objects with the same name and type are considered to be versions of the same object. ACMS assumes that objects with the same name and type across different applications, do not have a relationship to each other.
UG 1-4 • Introduction
Aldon/CMS User’s Guide
Types of Objects Handled ACMS works with: • Objects created from source code such as COBOL or RPG programs (including ILE programs) • Objects created by CL commands such as data areas, job descriptions, or SQL packages • Object created by SQL statements including aliases, indexes, tables, views, triggers, user defined types, and user defined functions and procedures • Objects created by third party vendor packages such as PowerHouse from Cognos. When you define a release, ACMS creates database entries that associate source-based objects with their source code, and records other objects as non-source objects. Developers can modify both source-based and non-source objects. When developers modify a source-based object, they receive the source code associated with the object for editing. When developers modify a non-source object, they receive the actual object which can serve as a model for the new replacement object. ACMS also provides a pseudo-source facility for storing and executing CL commands to create CL-based objects or SQL statements to create SQL based objects.
Comprehensive View of Objects Most panels within ACMS do not display source file and library information, only the environment, object name, type, and attribute. Using the panels, you can use options to perform actions on objects, without having to know which libraries or source files the objects and their source need to come from or go to. ACMS tracks and controls the location of each object and its source.
Aldon/CMS User’s Guide
Introduction • UG 1-5
Using the object database, ACMS provides a comprehensive view of all objects in an application with the Work with Objects by Release panel shown below: CWRKOBJREL Position to
Work with Objects by Release . . . . . . .
__________
*TOP, *BOT, starting characters
Type options, press Enter. (*=Combined job) 2=Edit 3=Check out* 4=Delete 5=Browse source 7=Promote* 13=Request checkout* 14=Create* 17=Request promote* 30=Display log... More: + Opt Object Type Attribute Release Envs Rl Cnds E Chkout Dvp. ACTGLL *FILE LF AC/BAS D QP ACTGLP *FILE PF AC/BAS IQP COMMENTRY *PGM CBL AC/BAS P COMMIO *PGM CBL AC/BAS I P COMMPRT *PGM CBL AC/BAS P RCVENTRY *PGM RPG AC/BAS P RCVIO *PGM RPG AC/BAS P RCVPRT *PGM RPG AC/BAS P TEST *PGM RPG AC/BAS D ADA
Subset Rel:ALDON/ACMSDEMO/BASE Command ===> _________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F6=Add object F10=View 3 F11=View 2 F13=Repeat F19=Work with tasks F23=More options F24=More keys
Figure 2 - Work with Objects by Release panel
The Envs column on the panel shows all environments that contain a copy of the object using single letter environment abbreviations (“D” for Development, “I” for Integration, “Q” for Quality Assurance, and “P” for Production). For example, the Envs column in Figure 2 shows that the logical file ACTGLL is present in Development, Quality Assurance, and Production.
Object Movement Figure 1 on page UG 1-4 shows the flow of source and objects during development. A movement from Production, Quality Assurance, or Integration to Development is a checkout. Any movement toward Production is a promotion. A developer checks out an object to work on it. Once the developer finishes modifications, he/she then promotes the object through Integration and Quality Assurance, back into Production. When an object reaches Integration, Quality Assurance or Production, it can be distributed to additional libraries on the same system or on remote systems using an “install live” option or standard ACMS object distribution.
UG 1-6 • Introduction
Aldon/CMS User’s Guide
Library Groups A library group is a collection of objects that you want ACMS to treat the same when updating data libraries or distributing objects. You use an object’s assigned library group and your mapping of library groups to data set and distribution target libraries to tell ACMS where to place the object when updating data libraries or distributing objects. The use of library groups lets you use fewer Production libraries while providing a high degree of control over the updating of data sets and the distribution of objects into target libraries on remote systems. At release setup, you divide each Production library into one or more library groups. In the simplest case, each Production library has just one library group containing all the objects in that library. You assign each object in a release to exactly one library group. If an object has source, you also assign the source to a library group. You make library group assignments when mapping, loading, or adding objects to an application or when you check an object out from a parent release to a child release for the first time. You can change an object’s library group assignment later if necessary. When you define a data set, you specify which library groups update each data library in the data set. Each library group can update at most one library in a given data set. When you define an object distribution target, you specify which library groups distribute objects to each library in the target. Each library group can distribute objects to at most one library in a given target. The figure below illustrates how you might use library groups for a release:
Aldon/CMS User’s Guide
Introduction • UG 1-7
UG 1-8 • Introduction
Aldon/CMS User’s Guide
Aldon/CMS User’s Guide User’s Guide UG
Chapter 2 Basics
This chapter explains how to start ACMS and set basic user preferences. You will also find step-by-step instructions for checking out, editing, compiling, and promoting objects. The following topics are included: • “Starting Aldon/CMS” on page UG 2-2 • “Setting User Preferences” on page UG 2-3 • “Checking Out Objects” on page UG 2-5 • “Editing Source” on page UG 2-10 • “Compiling” on page UG 2-11 • “Promoting Objects” on page UG 2-17 • “Installing Live” on page UG 2-22 • “Working with Dependent Objects” on page UG 2-32 • “Emergency Checkout and Promotion” on page UG 2-41 • “Resolving Conflicts” on page UG 2-42 • “Restricting Promotes” on page UG 2-47 • “Establishing and Meeting Testing Standards with ANALYZER” on page UG 2-49 Online Help Text
Aldon/CMS User’s Guide
For detailed descriptions of the fields, options, and function keys displayed or available at any of the panels shown in this document, please see the online help text.
Basics • UG 2-1
Starting Aldon/CMS To sign on for demonstration access • Sign on with user ID ACMSDEMO. The initial password for this user ID is ACMSDEMO. You must change the password the first time you sign on. If the password has been changed, ask your product administrator for the current password.
To start Aldon/CMS 1. On an iSeries command line, type the following command:
ACMSLIB/STRACMS where ACMSLIB is the name of the ACMS product library. The default value is ACMSLIB. If the library is not found, check with the person responsible for ACMS installation. 2. Press ENTER.
The Aldon Change Management System main menu displays: CACMS
Ver 7.2
Aldon Change Management System
(C) Copyright Aldon Computer Group, Inc. 1989-2003.
All Rights Reserved.
Type choice, press Enter. 1. 2. 3. 4. 5. 6. 7. 11. 12. 13. 14.
Work with objects by release Work with objects by developer Work with archive objects Work with conditions Work with tasks Distributions menu Display log Setup menu Work with applications Work with releases Work with data sets
User defaults: Rel:ALDON/ACMSDEMO/BASE Dvp:ADA Tsk:*NONE Command ===> __________________________________________________________________ _______________________________________________________________________________ F3=Exit F4=Prompt F9=Retrieve F14=WRKSBMJOB F18=WRKSPLF F22=More functions
Figure 3 - Aldon/CMS Main Menu
The main menu provides access to all ACMS functions. Most developers use the Work with Objects by Developer panel (accessed with main menu option 2) for their daily activities.
UG 2-2 • Basics
Aldon/CMS User’s Guide
Setting User Preferences ACMS lets you specify personal default values (user defaults) which automatically focus panels throughout ACMS on the objects of interest to you, and preset action oriented panels with default values. You can specify a release and task and your developer name as defaults to display only the information that is relevant to the work you are performing. You can also set preferences to display information that will let you coordinate the work of multiple developers and multiple tasks (all applications and all developers). ACMS stores user defaults between sessions so you only need to work with them when you want to change them. The ACMS command interface also uses these values as defaults. You can also change your default source code editor and define a PDM-style user options file. See “Setting Advanced User Preferences” on page UG 4-4 for details on these options.
To work with user preferences You access the More Functions panel, shown below, with F22 (More functions) from most ACMS panels. CMORFNC
Rel 07.1
More Functions
Type choices, press Enter. User defaults: Release . . . Application Group . . Developer . . . Task . . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
BASE + *NONE, name ACMSDEMO + *NONE, name ALDON + *NONE, name ADA + *NONE, name *NONE + *NONE, name
Type choice, press Enter. __
1. 2. 3. 4. 5. 6.
Edit development tools Set user-defined option file Set operation defaults Enter/work with user requests Record task hours Act upon dependent objects
11. *. *. 14. *. 16.
Work with tasks ASC's Abstract/Probe+ Hawkeye's Pathfinder Generate DDL from SQL object ASPECT's LANSA Analyze object dependencies
Command ===> __________________________________________________________________ _______________________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F6=DSPMSG F9=Retrieve F12=Cancel F14=WRKSBMJOB F18=WRKSPLF
Figure 4 - More Functions panel
The first time you display the More Functions panel, all values are set to *NONE. With these settings in effect, ACMS shows you all objects associated with all developers for all applications.
Aldon/CMS User’s Guide
Basics • UG 2-3
A plus (+) sign after a field on a panel indicates that you can position the cursor in the field and press F4 (Prompt) to retrieve a list of values available for selection.
Promptable Fields
Setting Your Preferences Before you start to work as an ACMS developer, use the More Functions panel to focus ACMS on the objects that you want to work with and designate yourself as the default developer. This helps you focus on your own work by eliminating objects from other applications and objects in other developer libraries from displayed lists.
To specify a default application and release 1. At the ACMS main menu, press F22 (More functions). Note
You can also press F22 from most other panels within ACMS. The More Functions panel, shown in Figure 4 on page UG 2-3, displays. 2. Position the cursor in the Application field and press F4 (Prompt).
The Select Application panel, which shows all available applications with their group and description, displays. 3. To select an application, type a slash (/) over the period by the
application and press ENTER. The More Functions panel displays, with the Application and Group fields filled in. Note
If you cannot determine the proper application, consult your application manager. 4. Position the cursor in the Release field and press F4 (Prompt).
The Select Release panel, which shows the releases defined for the application you selected, displays. 5. To select a release, type a slash (/) over the period by the release and
press ENTER. The More Functions panel displays, with the Release, Application, and Group fields filled in with the values to focus ACMS panels on the objects you want to work with. Note
If you cannot determine the proper release, consult your application manager. 6. Press ENTER to return to the previous panel.
Your new user defaults are now in effect.
UG 2-4 • Basics
Aldon/CMS User’s Guide
To specify yourself as the default developer To limit the objects displayed on the Work with Objects by Developer panel to those copies of objects that were last checked out to you, specify yourself as the default developer. Specifying yourself as the default developer also saves you from specifying yourself as the developer every time you perform a checkout. 1. At the ACMS main menu, press F22 (More functions). Note
You can also press F22 from most other panels within ACMS. The More Functions panel, shown in Figure 4 on page UG 2-3, displays. 2. In the Developer field, do one of the following:
–
Type your CMS developer name.
-ora.
Position the cursor in the Developer field and press F4 (Prompt). The Select Developer panel displays.
b.
To select the developer name assigned to you, type a slash (/) over the corresponding period and press enter. The More Functions panel displays.
Note
If you are not sure which developer definition to use or if a developer definition has not been created for you consult with the person responsible for ACMS setup. 3. Press ENTER without selecting an option to confirm your changes and
exit the panel.
Checking Out Objects ACMS provides controlled access to source code through a checkout function. The checkout function ensures that only authorized users check out source code, and tracks object movement to ensure that changes made by one developer are not overwritten by changes made by another developer.
Checking Out Different Types of Objects When modifying a source-based object, the developer checks out the source code associated with the object for editing. When modifying a non-source object, the developer receives the actual object which can serve as a model for the new replacement object.
Aldon/CMS User’s Guide
Basics • UG 2-5
Selecting the Correct Copy of the Object Copies of an object may exist simultaneously in Development, Integration, Quality Assurance, and Production. You can only modify source in the Development environment. When invoked, the checkout function locates the most recently modified copy of an object, in the environment closest to Development, and copies its source to the Development library associated with a designated developer. To fix an urgent Production problem, use the emergency checkout function to obtain the Production copy of the object regardless of other copies that may be active. ACMS automatically keeps track of all copies of an object in its database and uses this information to correctly complete regular and emergency checkouts.
Development Tips Use the Work with Objects by Developer Panel as Your Home Base ACMS is designed to provide access to the most commonly used functions from the Work with Objects by Developer panel shown below. The panel lists all objects in the application which have been checked out to the current developer and have not yet been promoted back into the Production environment. The objects in this list can be either in an individual or in a common development library. CWRKOBJDVP Position to
Work with Objects by Developer . . . . . . .
__________
*TOP, *BOT, starting characters
Type options, press Enter. 2=Edit 3=Check out* 4=Remove(cancel chk) 7=Promote* 13=Request checkout* 14=Create*
Opt Object RCVENTRY RCVENTRY RCVIO RCVIO TEST
Type *PGM *PGM *PGM *PGM *PGM
Attribute RPG RPG RPG RPG RPG
Release AC/BAS AC/BAS AC/BAS AC/BAS AC/BAS
(*=Combined job) 5=Browse source 17=Request promote ...
Developer ADA ADA ADA ADA ADA
Env E DVP QUA DVP QUA DVP
Checkout Requests
Oth Cnd
Subset: Rel:ALDON/ACMSDEMO/BASE Command ===> _________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F10=View 3 F11=View 2 F12=Cancel F19=Work with objects F23=More options F24=More keys
Figure 5 - Work with Objects by Developer panel
You can check out objects already in active environments other than Development with option 3 (Check out) on the Work with Objects by Developer panel. The Work with Objects by Developer panel will not list any objects the first time you display it.
UG 2-6 • Basics
Aldon/CMS User’s Guide
To start work on existing objects, perform checkouts from Production using the Work with Objects by Release panel shown in Figure 6 on page UG 2-7. Jump to the Work with Objects by Release Panel to Check Out from Production At the Work with Objects by Developer panel, press F19 (Work with objects) to jump to the Work with Objects by Release panel shown below. (Note that on the Work with Objects by Release panel, F19 displays the Work with Tasks panel.) You can also access the Work with Objects by Release panel by returning to the main menu and selecting option 1 (Work with objects by release). CWRKOBJREL Position to
Work with Objects by Release . . . . . . .
__________
*TOP, *BOT, starting characters
Type options, press Enter. (*=Combined job) 2=Edit 3=Check out* 4=Delete 5=Browse source 7=Promote* 13=Request checkout* 14=Create* 17=Request promote* 30=Display log... More: + Opt Object Type Attribute Release Envs Rl Cnds E Chkout dvp. ACTGLL *FILE LF AC/BAS P ACTGLP *FILE PF AC/BAS P COMMENTRY *PGM CBL AC/BAS P COMMIO *PGM CBL AC/BAS P COMMPRT *PGM CBL AC/BAS P R RCVENTRY *PGM RPG AC/BAS D QP ADA RCVIO *PGM RPG AC/BAS D QP ADA RCVPRT *PGM RPG AC/BAS D P ADA TEST *PGM RPG AC/BAS D ADA Subset Rel:ALDON/ACMSDEMO/BASE Command ===> _________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F6=Add object F10=View 3 F11=View 2 F13=Repeat F19=Work with tasks F23=More options F24=More keys
Figure 6 - Work with Objects by Release panel
The Work with Objects by Release panel displays objects in all environments of a release, not just the ones you are working on. Controlling the Object List The Work with Objects by Release panel provides a list of objects determined by your current user defaults and subsetting values. Use F22 (More functions) and F17 (Subset) to set the criteria governing the list. Criteria set with F22 (More functions) apply to all ACMS panels and remain in effect until changed. Criteria set with F17 (Subset) apply only to the current panel and are reset to default values each time you enter the panel. With commonly used default values, the Work with Objects by Release panel displays all objects in the release you are working in.
Aldon/CMS User’s Guide
Basics • UG 2-7
The Envs Field Provides a Snapshot of Each Object The Work with Objects by Release panel shows each object in the release, with one record per object. Letters in the Envs column correspond to copies of the object in the various ACMS environments. For example, in the figure above, the program RCVPRT has copies in Development (D) and Production (P) but not in Integration (I) or Quality Assurance (Q). This presentation lets you see the development status of each object at a glance.
Checking Out From Production To start work on an object, you must check it out from Production.
To start work on an object 1. At the ACMS main menu, type option 2 (Work with Objects by
developer) and press ENTER. The Work with Objects by Developer panel, shown in Figure 5 on page UG 2-6, displays. The panel shows records only for those objects currently undergoing development or testing. 2. Press F19 (Work with objects). The Work with Objects by Release
panel, shown in Figure 6 on page UG 2-7, displays. This panel shows records for all objects. 3. In the Opt field by the objects you want to check out, type 3
(Check out) and press ENTER. The Check Out Objects panel displays: CCKOOBJ
Check Out Objects
Type the additional checkout information below, press Enter. To developer . For task . . Print checkout Run option . . Comment for log
. . . . . . . . report . . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
ADA N 1
+ Name + Name, Y=Yes, N=No 1=Run interactively, 2=Run in batch
. . . .
.
Objects selected for checkout: Object ACTGLL
Type *FILE
Attribute LF
2 objects selected for checkout. F3=Exit F4=Prompt F7=Add task F16=Select dependent objects
Release AC/BAS
------- From ------Rel Env Library * PDN A54DMOPDN
F8=Change task F20=Enlarge list
F11=View 2 F12=Cancel F22=More functions
Figure 7 - Check Out Objects panel 4. In the To developer field, specify the developer to receive the object.
UG 2-8 • Basics
Aldon/CMS User’s Guide
5. Optionally, in the For task field, specify a task. 6. Optionally, in the Comment for log field, type a comment for the
development log. Note
The use of tasks and checkout comments may be required or optional as determined by release setup values. 7. Press ENTER to perform the checkout.
ACMS checks the object out to your developer library. When the Work with Objects by Release panel redisplays, notice the new letter “D” in the Envs column reflecting the object placed in development by the checkout, and the developer name in the Chkout dvp column. 8. To start working with objects checked out from Production, press F12
(Cancel) from the Work with Objects by Release panel to return to the Work with Objects by Developer panel. Note
The developer name defaults to the value set on the More Functions panel.
Checking Out From a Test Environment To continue work on an active object 1. At the ACMS main menu, type option 2 (Work with Objects by
developer) and press ENTER. The Work with Objects by Developer panel, shown in Figure 5 on page UG 2-6, displays. The panel shows records only for those objects currently undergoing development or testing. 2. In the Opt field by the object or objects you want to check out, type 3
(Check out) and press ENTER. The Check Out Objects panel, shown in Figure 7 on page UG 2-8, displays. Note
You can perform the checkout on any record for the object. ACMS automatically uses the correct copy of the object to complete the checkout so that you can edit the most recently modified copy. If an object exists only in Production, it does not appear on the Work with Objects by Developer panel. To check out both active objects (those in a test environment) and objects only present in Production, use the Work with Objects by Release panel. 3. In the To developer field, specify the developer to receive the object. 4. Optionally, in the For task and Comment for log fields, specify a
task and a comment for the development log. 5. Press ENTER to perform the checkout.
When the Work with Objects by Developer panel redisplays, notice the new record reflecting the object placed in Development by the checkout.
Aldon/CMS User’s Guide
Basics • UG 2-9
Editing Source You can only edit source for checked out objects.
To edit from the Work with Objects by Developer panel 1. At the ACMS main menu, type option 2 (Work with Objects by
developer) and press ENTER. The Work with Objects by Developer panel, shown in Figure 5 on page UG 2-6, displays. The panel shows records only for those objects currently undergoing development or testing. 2. In the Opt field by the object, do one of the following:
Note
–
Type 2 (Edit) to activate SEU for a source-based object.
–
Type 19 (Alt Edit) to activate SDA for a display file.
You can remap either option to activate another source editor defined to ACMS using option 1 (Edit development tools) on the More Functions panel. For instructions on how to define additional development tools to ACMS, see “Development Tool Setup” starting on page SA 7-1 in the “Aldon/CMS Setup and Administration Reference”.
To edit from the Work with Objects by Release panel 1. At the ACMS main menu, type option 1 (Work with Objects by
release) and press ENTER. The Work with Objects by Release panel displays. 2. In the Opt field by the object, do one of the following:
Note
–
Type 2 (Edit) to activate SEU for a source-based object.
–
Type 19 (Alt Edit) to activate SDA for a display file.
The Work with Objects by Release panel does not provide some development related options available on the Work with Objects by Developer panel.
To edit using PDM Use any command line to start PDM, locate the object in your developer library, and start editing.
UG 2-10 • Basics
Aldon/CMS User’s Guide
Compiling ACMS automates object creation. No prior set up is required to create objects with ACMS. ACMS determines compile parameters by object type and attribute. The defaults defined with the shipped product meet the needs of many sites without modification. Object Creation Commands ACMS contains create command definitions for all existing IBM create commands. You can define additional vendor or custom create commands to ACMS as described in “Custom Object Creation Setup” starting on page SA 23-1 in the “Aldon/CMS Setup and Administration Reference”. Using Pseudo-Source If a non-source object is CL or SQL-based (can be created by executing one or more CL commands or SQL statements), the developer can create pseudo-source for the object. Pseudo-source is a source member that contains the CL commands or SQL statements to create the object. Pseudo-source for a CL-based object is not a CL program that can be compiled. Pseudo-Source Example You can use pseudo-source to create a message file. Without pseudo-source, the description of what goes in the message file must exist outside of ACMS. With pseudo-source, you can enter all the commands necessary to create and populate the message file in a CL member. You then associate this pseudo-source member with the message file object using option 16 (Change checked out object) on the Work with Objects by Developer panel. From this point on, ACMS recreates the object by executing each statement in the pseudo-source. To modify the message file, you only need to change the pseudo-source member. Use of pseudo-source is optional. ACMS handles execution of the pseudo-source you provide to create non-source objects. You do not need to use special create commands. Using pseudo-source has the following benefits: • Provides a starting point for future modifications • Provides a place to save comments regarding the object • Provides an archive history of object changes • Lets you use Aldon's Harmonizer source comparison utility to compare versions of an object • Allows editing with a PC-based editing tool
Aldon/CMS User’s Guide
Basics • UG 2-11
See “Working with Pseudo-Source” on page UG 5-6, for additional information on creating pseudo-source and an example of pseudo-source for a message file. Automatic Creation of Non-Resident Objects The object creation function supports creation of non-resident objects to obtain copies required for testing. The create non-resident function compiles an object directly into an environment where it is required to prevent level checks, or otherwise help build the test environment. Non-resident object creation does not move objects through Development, therefore the audit trail clearly reflects that although the object moved into an active environment, it was not changed. ACMS object referencing can identify all non-resident objects required to test a changed object. Aldon/CMS Manages the Object Creation Library List ACMS builds the object creation library list automatically based on the environment in which you are creating the object. See “Library Lists” starting on page CG 1-1 in the “Aldon/CMS General Topics Reference” for further details. Action Options Marked with an Asterisk (*) An asterisk (*) after an option indicates that if you select multiple objects with that option, ACMS groups the selected objects into a single job for processing. When ACMS processes objects as a group it performs operations in the correct order to achieve the requested result. Actions performed as group jobs include checkout, create, and promote. See “Option Processing for Sub-Files (Lists)” starting on page DO F-13 in the “Aldon/CMS Daily Operations Reference” for more information on option processing. Automatic Sequencing in Multi-Object Create Jobs If you select several related objects for creation at the same time, ACMS creates them in the correct order so that the creation of all objects will work. For logical files with fields defined by reference to other logical files, and a few other special circumstances, ACMS cannot determine the correct create order automatically. In these cases you can tell ACMS the correct create order by specifying object dependencies manually. See “To prepare to create a logical file with fields defined by reference” on page DO 4-8 in the “Aldon/CMS Daily Operations Reference”for more information.
UG 2-12 • Basics
Aldon/CMS User’s Guide
Automatic Collection of Object Dependency Data Each time you create an object, ACMS captures information detailing what other objects the created object depends on. ACMS makes this object dependency data available as an aid in recreating dependent objects to avoid level checks, to populate test environments, and to help you understand the impact of object changes. Automatic Collection and Reuse of Object Creation Parameters Each time you create an object, ACMS uses the object creation parameters used for the previous creation, unless you specifically override those parameters. Single-copy create specifications, used to override existing object creation parameters are discussed in “Working with Create Parameters” on page UG 2-15. Advanced Object Creation Control ACMS allows you to customize create command definitions and defaults for further object creation control. When used, these methods take precedence over automatic collection and reuse of object creation parameters. Consult with your ACMS administrator and see “Single-Copy Create Specifications” starting on page DO 4-16 in the “Aldon/CMS Daily Operations Reference” and “Custom Object Creation Setup” starting on page SA 23-1 in the “Aldon/CMS Setup and Administration Reference” for further information.
Aldon/CMS User’s Guide
Basics • UG 2-13
Creating Objects To create an object in an active environment 1. At the ACMS main menu, type option 2 (Work with Objects by
developer) and press ENTER. The Work with Objects by Developer panel, shown in Figure 5 on page UG 2-6, displays. The panel shows records only for those objects currently undergoing development or testing. 2. In the Opt field by the object, type 14 (Create) and press ENTER.
The Create Objects panel, similar to the one shown below, displays: CCRTOBJ
Create Objects
Type the additional create information below, press Enter. For task . . . . . . . . . Stop upon failure . . . . . Print compile listing . . . Do you wish to specify data conversion methods Change Analyzer options . . Comment for log . . . .
. . . . . . . . .
Y N
+ Name Y=Yes, N=No Y=Yes, N=No
. . . . . .
Y N
Y=Yes, N=No Y=Yes, N=No
Objects selected for create: Object Type Attribute ACTGL *FILE PF
1 objects selected for create. F3=Exit F4=Prompt F19=Submit without prompt
Release AC/BAS
Environment DVP ADA
F11=View 2 F20=Enlarge list
Library
F12=Cancel F22=More functions
Figure 8 - Create Objects panel 3. Complete values on the panel as desired. Note
ACMS does not log creates in the Development environment. 4. Press ENTER to submit the create job.
Note
UG 2-14 • Basics
You can also create objects in the Development, Integration, and Quality Assurance environments from the Work with Objects by Release panel. If copies of the selected object exist in more than one environment, a selection panel displays where you can select the copy or copies to create.
Aldon/CMS User’s Guide
To create an object in Production You must use the Work with Objects by Release panel to create objects in Production, because the Work with Objects by Developer panel does not display Production copies of objects. 1. At the ACMS main menu, type option 1 (Work with Objects by
release) and press ENTER. -orAt the Work with Objects by Developer panel, press F19. The Work with Objects by Release panel displays. 2. In the Opt field by the object, type 14 (Create) and press ENTER.
A Create Objects panel, similar to the one shown in Figure 8 on page UG 2-14, displays. 3. Complete values on the Create Objects panel as desired. 4. Press ENTER to submit the create job.
Working with Create Parameters The procedure in this section creates a single-copy create specification or override associated with the copy of the selected object. This override remains associated with that copy as it moves through environments. This allows ACMS to create the object in a new environment using the new parameters instead of the parameters previously used for a copy of the object already in that environment. If the copy is used to fulfill a checkout, the single-copy create specification accompanies the copy to Development. If a copy of the object remains behind in Integration or Quality Assurance, the single-copy create specification remains with that copy as well. If custom create command defaults are in use at your site, you must incorporate parameters specified in the single-copy create specification into the create command default when the object reaches Production to make the changes permanent. See “Single-Copy Create Specifications” starting on page DO 4-16 in the “Aldon/CMS Daily Operations Reference” and “Custom Object Creation Setup” starting on page SA 23-1 in the “Aldon/CMS Setup and Administration Reference” for further information.
Aldon/CMS User’s Guide
Basics • UG 2-15
To change create parameters for an object 1. At the Work with Objects by Developer or the Work with Objects by
Release panel, in the Opt field, type 15 (Change create options). The Change Object Creation Options panel displays. 2. In the Create command and Library fields, make your changes. 3. Optionally, in the Create Options field, do one of the following:
–
Type command keywords and parameters to change execution parameters for the create command
–
Place the cursor on the first line of the field and press F4 to prompt the create command currently in effect for the object. Complete the command parameters as needed and press ENTER to return the parameters to the Create Options field
–
Type *DFT to reset options to defaults
4. Press ENTER.
ACMS uses the options specified instead of options used on the existing copy of the object, not in addition to them.
To view the create command associated with an object 1. At the ACMS main menu, type option 1 (Work with Objects by
release) and press ENTER. -orAt the Work with Objects by Developer panel, press F19. The Work with Objects by Release panel displays. 2. In the Opt field by the object, type 8 (Display attributes) and press ENTER.
A spool file (PRTFPRTOBJ), which lists the create command used for the object, displays.
UG 2-16 • Basics
Aldon/CMS User’s Guide
Promoting Objects When you complete your changes for an object, you use the promote function to move the object to the appropriate environment based on options selected during release setup. Continue promoting the object forward through environments as you complete each phase of testing until the object reaches the Production environment. The ACMS promote function automates many steps which typically require considerable effort on the part of the developer. For example, when promoting a physical file into Production, ACMS performs the following main steps to ensure the desired result: 1. Allocate source and object in the to and from environments. 2. Rename related logicals in the to environment. 3. Rename any existing copy of the object in the to environment. 4. Copy source to the to environment. 5. Create the physical file in the to environment. 6. Copy data from the renamed physical file to the new physical file. 7. Rebuild all logicals over the new physical file. 8. Delete the renamed to source and object. 9. Delete the from source and object. 10. Deallocate source and objects.
Other steps include creation of an archive copy of the source and object and updating data libraries defined for the Production environment. Promotes of Multiple Objects Executed as Combined Jobs As indicated by the asterisk after option 7 (Promote*) promote jobs execute as combined jobs which means ACMS compiles related objects in the correct order. ACMS recognizes the difference between reference files and physical files. For a discussion of combined jobs, see “Action Options Marked with an Asterisk (*)” on page UG 2-12. Recreating Dependent Objects When you initiate promotion, ACMS offers you the opportunity to recreate objects dependent on those you are promoting. This helps you quickly integrate the changed objects into the new environment by avoiding level checks. For a discussion of working with dependent objects see “Working with Dependent Objects” on page UG Chapter 2-32.
Aldon/CMS User’s Guide
Basics • UG 2-17
Promote Automatically Compiles Object’s Correct Parameters Because ACMS reads object create parameters required for each object from the prior copy of the object, the promote function creates objects as necessary without assistance. Promoting New Objects ACMS must know how to create an object in order to promote it. For some types of objects you must create an object newly added to a release successfully in your developer library the first time before ACMS can promote it. During the first promotion of a new object, ACMS scans the existing compiled object and uses those create parameters to create the new copy on promotion. Advanced Object Creation Control and the Promote Function If single-copy create specifications, custom create command definitions, or create command defaults are in use at your site, ACMS uses additional information to create objects. See the sections “Single-Copy Create Specifications” starting on page DO 4-16 in the “Aldon/CMS Daily Operations Reference” and “Custom Object Creation Setup” starting on page SA 23-1 in the “Aldon/CMS Setup and Administration Reference” for further information.
To promote an object 1. At the ACMS main menu, type option 2 (Work with objects by
developer) and press ENTER. The Work with Objects by Developer panel, shown in Figure 5 on page UG 2-6, displays. 2. In the Opt field by the object or objects to promote, type 7 (Promote)
and press ENTER. The Promote Objects panel displays: CPRMOBJ
Promote Objects
Type choice, press Enter. Do you wish to select dependent objects for create . .
Y
Y=Yes, N=No
Objects selected for promote: Object ACTGLL RCVIO
Type *FILE *PGM
Attribute LF RPG
Release AC/BAS AC/BAS
2 objects selected for promote. F3=Exit F10=View 3 F11=View 2
--- Environment E FROM DVP ADA DVP ADA
F12=Cancel
---TO QUA QUA
F22=More functions
Figure 9 - Promote Objects panel
UG 2-18 • Basics
Aldon/CMS User’s Guide
Tip
You can control the default value displayed in the Do you wish to select dependent objects for create field on this panel using option 3 (Set operation defaults) on the More Functions panel. 3. In the Do you wish to select dependent objects for create field type
Y. 4. Press ENTER.
The Select Dependent Objects to Create panel displays: CSELDEPOBJ
Select Dependent Objects to Create
Any dependent objects to be created with this promote must be selected separately for each represented promote-to release and environment. Type options, press Enter. Press Enter with no options to continue. 1=Select all objects 2=Display list for individual selections 5=Display selections
Opt
------ Promote-to (Reference) ------- Objects Env Release Selected QUA ALDON/ACMSDEMO/BASE
Release Option None .
Last Action
. . . . . . . . . . . . . . . . . . . . . .
F3=Exit
F12=Cancel
F16=Review promote objects
F22=More functions
Figure 10 - Select Dependent Objects to Create panel 5. Press ENTER to select dependent objects using the default criteria
specified for the release. Note
Aldon/CMS User’s Guide
See online help text for details on selecting dependent objects for creation during promotion.
Basics • UG 2-19
If you selected at least one data object for promotion, the Specify Data Conversion panel displays. Use the Specify Data Conversion panel to define CPYF options and specify a custom data conversion program. CDTACNVSPC
Specify Data Conversion
Release . . . . . . Promote to release . Release defaults: CPYF FMTOPT . . . Retain saved data Position to . . . .
: :
ALDON/ACMSDEMO/BASE *SAME
: : .
*MAP N
Conversion program . : *NONE Library . . . . . : *TOP, *BOT, starting characters
Type choices, press Enter. CPYF opt (1=*DFT, 2=*MAP/*DROP, 3=*MAP, 4=*DROP, 5=*NOCHK, 6=*NONE, 9=*NOCPY) Conversion: Program (*DFT, *NONE, name) Library (*LIBL, name) Retain (saved) data (Y=Yes, N=No)
Object DATAFILE
To Rpl CPYF Env Cpy Opt QUA Yes 1
F3=Exit
F5=Refresh
---- Conversion ----Program Library *NONE
F12=Cancel
Retn --- Prior Specification --Data CPYF Program Library * *NO PRIOR SPECIFICATIONS
F16=Review objects
F22=More functions
Figure 11 - Specify Data Conversion panel 6. At the Specify Data Conversion panel, specify data conversion
options for each data object by doing the following: a.
If the object is a physical file, in the CPYF Opt field, change the record format field mapping by typing one of the following: 2 (for *MAP/*DROP), 3 (for *MAP), 4 (for *DROP), or 5 (for *NOCHCK), – or – Do either of the following: – To use CPYF options specified for the release, type 1 (for *DFT) CPYF options specified for the release display on line 6 of this panel.
Tip
– To perform the conversion without calling CPYF before a conversion program, type 9 (for *NOCOPY) See the online Help for details regarding these CPYF options. b.
Under - - Conversion - -, in the Program field, do one of the following: – To perform conversion without use of a conversion program, type *NONE – To use the conversion program specified for the release, type *DFT
UG 2-20 • Basics
Aldon/CMS User’s Guide
The conversion program specified for the release displays on line 7 of this panel.
Tip
– To specify a conversion program other than that specified for the release, type the program name c.
Under - - Conversion - -, in the Library field, do one of the following: — If, in the Program field you specify *NONE or *DFT leave this field blank — If, in the Program field you specified a conversion program, type the name of the library containing the program
d.
In the Retn Data field, do one of the following: — Type Y to retain a renamed copy of the replaced object including its data
Note
The promote report provides the name and location of the renamed copy of the object. — Type N to convert data in the object without saving a renamed copy —Accept the default value, *, to apply the default option indicated in the Retain saved data field at the top of the panel. 7. Repeat Step 6 for each data object in the list. 8. Press ENTER to confirm your data conversion choices and proceed to
the next step in the promote process. See “Specifying Data Conversion Options,” starting on page CG 3-31 in the “Aldon/CMS General Topics Reference” for more information. If you completing any selection of dependent objects and data conversion specifications, the Specify Promote Options panel displays: CPRMOPT
Specify Promote Options
Type choices, press Enter. Stop upon failure . . . . . Print compile listing . . . Check development timestamps Leave resident . . . . . . .
. . . .
. . . .
. . . .
Install live from ITG Install live from QUA Install live from PDN Distribute from ITG . Distribute from QUA . Distribute from PDN .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
For task (dependent objects) . . . Comment for log . . . .
F3=Exit F4=Prompt F19=Submit without prompt
Y N N 2
Y=Yes, Y=Yes, Y=Yes, 1=All,
N=No N=No N=No 2=None, 3=Dependent
Y=Yes, Y=Yes, Y=Yes, Y=Yes, Y=Yes, Y=Yes,
N=No N=No N=No N=No N=No N=No
+ Name
F5=Refresh F12=Cancel F22=More functions
F16=Review objects
Figure 12 - Specify Promote Options panel
Aldon/CMS User’s Guide
Basics • UG 2-21
9. At the Specify Promote Options panel, in the Stop upon failure field,
if you are promoting several related objects and do not wish to continue the job if promotion of an object fails, type Y. 10. In the Leave resident field, accept the default value. 11. If you are promoting any COBOL or RPG programs and have
ANALYZER installed, More: + displays. Press PAGE DOWN or ROLL to display Analyzer options fields to request preparation of these programs for collection of testing statistics by ANALYZER and set testing requirements which must be met before ACMS will permit subsequent promotion of the programs. UP
For more information see “Establishing and Meeting Testing Standards with ANALYZER,” starting on page UG 2-49. 12. Press ENTER to display the Submit Job panel form where you submit
the promote job.
To confirm successful promotion You can track the movement of an object from one environment to another through promotion using: • The environment abbreviation displayed in the Env column on the Work with Objects by Developer panel • The single-character environment codes displayed in the Envs column on the Work with Objects by Release panel To update the object’s status information on the panel, press F5 (Refresh) after the promote completes successfully. You can also press F18 (WRKSPLF) to check the promote report for successful completion, or select the object with option 30 (Display log) to display development log entries for the object.
Installing Live Install live is a method of quickly and easily copying objects from ACMS test or Production libraries to additional libraries for testing or production use. Once configured for a release environment, development and testing staff can use install live without any knowledge of the inner workings of the ACMS object distribution system. Install live provides users with the ability to group objects so that they are installed as a unit. Any failure causes the entire group of changes to be backed out.
UG 2-22 • Basics
Aldon/CMS User’s Guide
While primarily intended for use as part of a promote job, users can also invoke install live independent of the promote function using options available on the Work with Objects by Release, Work with Tasks, and Work with Conditions panels. This section includes the following topics: • “Overview,” starting on page UG 2-24 • “Install Live Concepts,” starting on page UG 2-26 • “Installing Live on Promote,” starting on page UG 2-27 • “Installing Live Outside of the Promote Function,” starting on page UG 2-29 For information on additional end user actions, see “Installing Live” starting on page DO 3-23 in the “Aldon/CMS Daily Operations Reference”. For information on configuring install live and recovering from error conditions, see “Installing Live” starting on page DS 7-1 in the “Aldon/CMS Object Distribution Reference”.
Aldon/CMS User’s Guide
Basics • UG 2-23
Overview You can request install live for one or more objects for a specific environment of a specific release. (In this chapter, references to an environment always mean an environment of a specific release, not to, for example, Integration environments of all releases as a category.) ACMS copies the objects to a predefined “target” which is a group of one or more additional libraries. The target may be located on the same “host” system where ACMS is installed, or on a different “remote” system networked with the host system. Typically, the target constitutes a “live environment” used either as the actual production environment for the application, or as a “clean” testing environment. The figure below shows a release with two install live targets:
Check Out
Development
Promote
Integration
Quality Assurance
Production
Install Live QA Install Live Target
Production Install Live Target
Install live is a one-way copying of objects. There is no normal flow of objects from install live targets back into ACMS controlled environments. Install live can be configured for the Integration, Quality Assurance, and Production environments of a release. Install live on promote
Most frequently, install live is used in conjunction with the promote function. For example, when you promote objects forward from Integration to QA, you can simultaneously initiate install live of the same objects into the QA install live target.
Objects located using environment object creation library list
The object you select for install live need not be present in the environment associated with the target as long as it is available in the object creation library list for the environment. For example, if you are promoting a modified file to QA, and a program that uses that file is not included in that promote job and is not already present in the QA environment, you can use the “create dependent objects” feature of the
UG 2-24 • Basics
Aldon/CMS User’s Guide
promote function to locate the first available copy of the program in the QA object creation library list, and create that program “non-resident” into the QA environment. At the same time, if you are installing live, the recompiled program is selected for install live to the QA install live target. In this way install live helps you build a complete copy of the application for testing or production use in parallel to the corresponding ACMS environment. For a discussion of object creation library lists, see “Object Creation Library Lists” starting on page CG 1-6 in the “Aldon/CMS General Topics Reference”. Installing live independent of promote
You can also invoke install live independent of the promote function. When invoked independently, you can select almost any object defined to the release to install live for any environment configured for install live. A copy of the object must be locatable using the object creation library list for the environment. One common situation in which an object would be unavailable for install live for a given environment would be a newly added object that has never been promoted to or through that environment and is therefore not “visible” to the environment through its object creation library list.
Designed to be simple and easy for users
Install live is designed to insulate end-users from the intricacies of ACMS object distribution setup and management. All information required for install live of objects to targets is predefined. The user need only select the desired objects. Defaults for scheduling of distribution and installation steps, software to automate installation, and conversion of data into new file formats can be modified by users if permitted by configuration options. Most commonly, users simply press Enter to accept the defaults.
Many additional features available
The features described above meet the needs of most locations. Additional features and flexibility are available for sites with more complex needs. For information on additional install live features and capabilities, see “Additional Install Live Features” starting on page DO 3-23 in the “Aldon/CMS Daily Operations Reference”. For instructions on using install live, start with “Install Live Concepts,” starting on page UG 2-26. For instructions on configuring install live, go to “Configuring Install Live” starting on page DS 7-2 in the “Aldon/CMS Object Distribution Reference”.
Aldon/CMS User’s Guide
Basics • UG 2-25
Install Live Concepts Install Live “From” Release Environment The install live environment is the environment from which you install live an object. This is the environment with which the install live target libraries are associated (see figure on page UG 2-24). If you are installing live on promote, the “from” environment is always the environment into which you are promoting the objects. If you are installing live outside of promote, the “from” environment can be any environment of a release for which you have configured install live. You specify the release by selecting the record for the object in that release on the Work with objects by Release panel. You specify the “from” environment during the install live job definition process by selecting an environment record on the Select Environments for Install Live panel (page UG 2-30) or the Select Environments for Request Install Live panel (page DO 3-31). Eligible Objects An object is eligible for install live for a given environment if the object, its source, or both, are assigned to a library group selected in the install live distribution profile for the environment. As an end-user of install live you are insulated from direct knowledge of the existence of distribution profiles. You can select any object for install live regardless of eligibility for install live. Watch for feedback from ACMS in fields on the panels and in messages displayed on the panels so you know which objects were and were not distributed to the install live targets. If you have trouble installing live certain objects, contact the person responsible for install live configuration.
UG 2-26 • Basics
Aldon/CMS User’s Guide
Installing Live on Promote If you choose to create dependent objects, they will also be included in the objects selected for install live.
To install live on promote Configure install live for the release environments with which you want work. See “Configuring Install Live” starting on page DS 7-2 in the “Aldon/CMS Object Distribution Reference” for details.
Prerequisites
1. Begin promoting in the standard manner as described in “To promote
an object,” starting on page UG 2-18. 2. At the Specify Promote Options, in the Install live from field for
each appropriate environment, type a Y. 3. Complete other fields on the panel appropriately and press ENTER.
The Install Live on Promote panel displays: CLIVPRM
Install Live on Promote
Objects selected for promote to or create in the following environments have been designated for install live. Type options, press Enter. Press Enter with no options to continue. 2=Review objects; review/change specifications
Opt
Env ITG
Elig. Objs. 1
Release DOUGS/DMS01/BASE
F3=Exit F12=Cancel F22=More functions
F16=Review objects
Changeable Specifications Sched. Install Data Cnv. Yes Yes Yes
F19=Submit without prompt
One record displays in the list for each release environment for which you are promoting objects. An install live job can be generated for each of these release environments. 4. Proceed with install live by doing one of the following:
–
To accept all defaults for the install live jobs shown, press ENTER Go to “To complete the install live on promote process,” starting on page UG 2-29.
–
Aldon/CMS User’s Guide
To modify default values, in the Opt field by each release environment for which you want to modify default values, type a 2 (Review objects; review/change specifications) and press ENTER
Basics • UG 2-27
The Install Live upon Promote panel displays: CINSLIVPRM
Install Live upon Promote
Release . . . . . . . . : Environment . . . . . . :
DOUGS/DMS01/BASE ITG
Type choice, press Enter. 1. 2. 3. 4.
Change Change Change Change
comment for log schedule installation method data conversion specifications
Objects selected for install live: Object PF
F3=Exit
Type *FILE
Attribute PF
F12=Cancel
Elig. Known Yes
Install Copy Env Release DVP *SAME
F22=More functions
5. At the Install Live upon Promote panel, type the number
corresponding to the first install live job definition aspect you want to change and press ENTER. Do one of the following: –
If you selected 1 (Change comment for log), go to “To change the install live comment” starting on page DO 3-25 in the “Aldon/CMS Daily Operations Reference”
–
If you selected 2 (Change schedule), go to “To change the install live schedule” starting on page DO 3-25 in the “Aldon/CMS Daily Operations Reference”
–
If you selected 3 (Change installation method), go to “To change the install live installation method” starting on page DO 3-27 in the “Aldon/CMS Daily Operations Reference”
–
If you selected 4 (Change data conversion specifications), go to “To change install live data conversion specifications” starting on page DO 3-29 in the “Aldon/CMS Daily Operations Reference”
6. After completing changes to an install live job definition aspect, the
Install Live upon Promote panel redisplays. 7. Do one of the following:
UG 2-28 • Basics
–
To change another install live job definition aspect, go to Step 5 above
–
To end changes to this install live job, press ENTER without typing a choice
Aldon/CMS User’s Guide
8. If you selected another release environment for install live job
modification, the Install Live upon Promote panel displays for the next release environment. –
Go to Step 5 above
–
If no more release environments are selected for install live job modification, the Install Live on Promote panel redisplays.
9. At the Install Live on Promote panel, do one of the following:
–
To continue changing install live jobs, in the Opt field by each release environment for which you want to modify default values, type a 2 (Review objects; review/change specifications) and press ENTER
Return to Step 3 on page UG 2-27. –
To end changes to the install live jobs and continue with the promote job, press ENTER. Go to “To complete the install live on promote process” below.
To complete the install live on promote process If you are also creating standard distribution sets with the promote job, panels for the distribution function appear before the Submit Job panel displays. Otherwise, the Submit Job panel displays. • At the Submit Job panel, press ENTER to submit the promote jobs, install live jobs, and any standard distribution jobs for processing.
Installing Live Outside of the Promote Function In addition to installing live as part of a promote job, you can also install live from several “Work with...” panels.
To install live outside of the promote function Prerequisites
• Configure install live for the release environments with which you want to work. See “Configuring Install Live” starting on page DS 7-2 in the “Aldon/CMS Object Distribution Reference” for details. • You must have at least one object “visible to” an environment for which install live is configured. “Visible to” means the object can be located in the object creation library list for the environment. Note that this means the object need not be resident in the environment. 1. At the ACMS main menu, type option 1 (Work with objects by
release) and press ENTER to display the Work with Objects by Release panel. 2. At the Work with Objects by Release panel, in the Opt field by each
object you want to install live, type option 47 (Install live) and press ENTER.
Aldon/CMS User’s Guide
Basics • UG 2-29
3. If you selected objects of more than one release for install live, the
Select Releases for Install Live panel displays: CSELILVREL
Select Releases for Install Live
Objects have been selected for install live in the following releases. Type default for the additional install live information. Comment for log
. . . .
Type options, press Enter 1=Select for install live Opt 1 1
Release DOUGS/DMS01/BASE DOUGS/DMS01/DELTA
Command ===> F3=Exit
F4=Prompt
Text
F9=Retrieve
F12=Cancel
F13=Repeat
If this panel does not display, it means all selected objects are of the same release. The panel displays one record for each release containing objects you selected for install live. On initial display, all releases are selected. Press ENTER to continue. 4. If objects in a release you are working with can be installed live into
more than one environment, the Select Environments for Install Live panel displays: CSELILVENV Release
Select Environments for Install Live
. . . . . . . . :
DOUGS/DMS01/BASE
The following environments are eligible for install live. Type default for the additional install live information. Comment for log
. . . .
Type options, press Enter 1=Select for install live Opt
Environment ITG Integration PDN Production
Only install live-defined environments presented for selection. Command ===> F3=Exit F4=Prompt F9=Retrieve F12=Cancel
UG 2-30 • Basics
F13=Repeat
Aldon/CMS User’s Guide
The panel displays one record for each release environment configured for install live. –
In the Opt field by each environment for which you want to install the objects live, type 1 (Select for install live) and press ENTER.
This panel does not display if only one environment of the release is configured for install live. 5. The Install Live panel displays: CINSLIV
Install Live
Release . . . . . . . . : Environment . . . . . . :
DOUGS/DMS01/BASE ITG
Type the additional install live information below, press Enter. Comment for log . . . . Do you wish to change: Schedule . . . . . . . . . . . . . . Installation method . . . . . . . .
N N
Y=Yes, N=No Y=Yes, N=No
Objects selected for install live: Object MARKSOBJ
Type *PNLGRP
Attribute
Elig. Known Yes
1 objects selected for install live. F3=Exit F5=Refresh F12=Cancel F22=More functions
Install Copy Env Release ITG *SAME
F19=Submit without prompt
The release and environment for which you are installing the objects live display at the top of the panel. Objects you selected for install live to that release environment are listed one per record in the lower portion of the panel. Type a Y (Yes) in the field for each install live job attribute you want to change:
Note
Aldon/CMS User’s Guide
–
To change default values controlling when objects are sent, received, or installed, in the Schedule field, type Y (Yes)
–
To change default values controlling software used to install the objects into the target libraries, in the Installation method field, type Y (Yes)
–
If you have selected data objects for install live and want to change default data conversion parameters, in the Data conversion specifications field, type Y (Yes) The Data conversion specifications field is visible only when data objects are selected for install live.
Basics • UG 2-31
6. After selecting any job attributes for modification, press ENTER.
Do one of the following: –
If you chose to modify scheduling defaults, the Install Live Schedule panel displays. Go to “To change the install live schedule” starting on page DO 3-25 in the “Aldon/CMS Daily Operations Reference”.
–
If the first job attribute you chose to modify was installation method defaults, the Specify Install Live Method panel displays. Go to “To change the install live installation method” starting on page DO 3-27 in the “Aldon/CMS Daily Operations Reference”.
–
If the first job attribute you chose to modify was data conversion specifications, the Specify Data Conversion panel displays. Go to “To change install live data conversion specifications” starting on page DO 3-29 in the “Aldon/CMS Daily Operations Reference”.
–
If you did not select any job attributes for modification, the Submit Job panel displays. Continue with “To complete the install live outside of promote” below.
To complete the install live outside of promote • At the end of the job definition process, the Submit Job panel displays. Press ENTER to submit the job for processing.
Working with Dependent Objects ACMS can gather information on object dependencies to allow easy locating of all objects dependent on a given object. For example, for a given physical file, ACMS can list all logical files and programs that reference that physical file directly, all programs that use the physical file indirectly through a logical file, and all programs that use the physical file indirectly through inclusion of a copy file member that references the physical file. Development
UG 2-32 • Basics
When working in development, a change made to one object often affects other objects. A good example of this is modification of a physical file referenced by several programs as well as by several logical files. ACMS provides the opportunity to identify all “dependent” objects at checkout and promotion. Identification of dependent objects at checkout enables checkout and modification of the related objects. Identification of dependent objects at promotion enables compilation of related objects over the modified versions.
Aldon/CMS User’s Guide
Testing and Production
Knowing where an object is used aids in assessing the impact of changing a given copy member, copy book, file, program or any object on which another object may depend. After changing an object or completing one phase of testing, use object dependencies when promoting the object to automatically locate and create objects needed to work with the changed object in the new environment.
Create Dependencies
ACMS tracks which requisite objects are required at create time by a dependent object using the Create Dependent field. A Y in this field indicates the requisite object is required to create the dependent object. A program has a create dependent relationship with logical and physical files it references directly, and copy members it references. A logical file has a create dependent relationship with the physical file or files on which it is based. A logical file may also have a create dependent relationship on another logical file if fields in the logical file are defined by referencing formats in the second logical file.
Search Paths
ACMS tracks which requisite objects should also be examined for additional indirect dependencies using two Search Paths fields. A Y in either field tells ACMS to include any requisites of the requisite object as requisites of the dependent objects. The distinction between the two fields is somewhat arbitrary: • Search Paths Database ACMS automatically places a Y in this field for all logical files to include the physical files they depend on. You might also want to specify a Y in this field manually for an input/output program used by other programs to access a file. • Search Paths Other You can place a Y in this field to indicate that the requisite object is an include member or copy member used by the dependent object. A program or other object can have a “search paths other” relationship with any other object it uses which need not be available to recreate the program or other object. Examples include a help text panel group used by a program. The ACMS object dependency scanning function can establish Create Dependent and some Search Path Database dependencies. You must specify most other Search Path dependencies manually, based on an understanding of the relationships between the objects.
Aldon/CMS User’s Guide
Basics • UG 2-33
Acquiring Object Dependency Data The ACMS object dependency functions rely on complete and accurate information accumulated in the ACMS database. When you first begin using ACMS, the information in the database may not be complete. Over time, as automatic and manual processes extend the coverage of the database, the effectiveness of the object dependency functions increases. ACMS can acquire object dependency data through scanning or specification. Scanning
Scanning is the collection of object dependency data by ACMS from object descriptions and from the compiler during object creation. ACMS can scan for object dependency data: • During release setup • Manually when requested by the user • Automatically every time an object is added, or created (including creates performed during promotion) Automatic scanning is enabled by a release option. See your ACMS administrator for information on whether or not scanning for object dependency data is enabled for a given release at your site. Scanning creates object dependency records indicating all apparent requisite objects for the object created. Requisite objects need not be defined to ACMS to be recorded in dependency records. Some dependency relationships cannot be determined by scanning and must be specified manually. For more information on scanning: • During release setup, see “Scan loaded objects for requisite objects?” on page SA 18-4 in the “Aldon/CMS Setup and Administration Reference” • Manually, all or part of a release, see “To scan an object for dependencies from the Work with Objects by Developer panel” on page UG 2-35. • Automatically on promote and create for a release, see “Maintain object dependency data” on page SA 13-10 in the “Aldon/CMS Setup and Administration Reference”
Specification
UG 2-34 • Basics
Specification is directly identifying to ACMS what objects are dependent on which other objects. Some types of object dependencies cannot be detected by the scanning program. In these cases you can specify object dependency data through specification.
Aldon/CMS User’s Guide
There are two ways to specify object dependency information: • The panel interface (see “To manually specify object dependencies” on page UG 2-36) — or — • The command interface (see “Overview: Object Dependency Commands” on page CG 7-27 in the “Aldon/CMS General Topics Reference”) The command interface can be used to load object dependency information from third party software into the ACMS database. More Information
For more information on: • How to scan for object dependencies, see “Scanning for Object Dependencies” below • How ACMS collects, stores, and helps you use object dependency data, see “Working with Object Dependencies” starting on page DO 4-18
Scanning for Object Dependencies You can initiate a scan for dependent objects from the Work with Objects by Developer panel or from the Work with Objects by Release panel.
To scan an object for dependencies from the Work with Objects by Developer panel 1. At the Work with Objects by Developer panel, in the Opt field by the
object, type 20 (Scan for requisite objects) and press ENTER. The Submit Job panel displays to confirm submission of the scan job for the selected object. 2. Press ENTER to submit the scan job.
To scan an object for dependencies from the Work with Objects by Release panel 1. At the Work with Objects by Release panel, in the Opt field by the
object, type 20 (Scan for requisite objects) and press ENTER. The Scan for Requisite Objects panel displays to clarify which copies of the object you wish to scan. 2. Complete the fields on the panel using help text for assistance where
necessary. 3. Press ENTER.
The Submit Job panel displays.
Aldon/CMS User’s Guide
Basics • UG 2-35
4. Press ENTER again to initiate the scan job.
The scan job updates object dependency data in the ACMS database.
Specifying Object Dependencies This section describes how to manually specify object dependencies using the panel interface. See “Overview: Object Dependency Commands” on page CG 7-27 in the “Aldon/CMS General Topics Reference” for more information on the command interface.
To manually specify object dependencies 1. At the Work with Objects by Developer or the Work with Objects by
Release panel, in the Opt field by the object, type 40 (Define requisite objects) and press ENTER. The User-Defined Requisite Objects panel displays: CDFNRQTOBJ Object . . . Object type Release . . Environment
. .
User-Defined Requisite Objects . . . .
. . . .
. . . .
. . . .
. . . .
. . . .
: : : :
TEST *PGM ALDON/ACMSDEMO/BASE DVP ADA
Type options, changes and additions, press Enter. 4=Remove Requisite Object + Opt Name Type RCVPRT *PGM
Create Dependent
Search Paths Database Other
Command ===> F3=Exit F4=Prompt/Select from list F5=Refresh F8=Next environment F10=Page to new entries
. . . . . . . . . More: + . . . . . . . . . . . F7=Previous environment . F24=More keys
Figure 13 - User Defined Requisite Objects panel 2. Do the following for each requisite object you want to define:
Note
UG 2-36 • Basics
a.
In the Requisite Object Name and Type fields, identify the object.
b.
Use the Create Dependent, Search Paths Database, and Search Paths Other fields to specify the types of dependency relationships by typing a Y in each applicable field.
You can specify requisite objects that are not defined to ACMS.
Aldon/CMS User’s Guide
3. If you accessed this panel from the Work with Objects by Release
panel, use F8 (Next environment) and F7 (Previous environment) to move between copies of the object in different ACMS environments. Complete a requisite objects list for each copy of the object. 4. Press ENTER to load the defined relationships into the ACMS object
database.
Acting Upon Dependent Objects You can act upon dependent objects through the panel interface, or by using the ACMSACTDOB command. The actions you can take on dependent objects during checkout and promote are limited to checking out dependent objects and creating dependent objects respectively. You can work with dependent objects using a wide variety of options on the Act upon Dependent Objects panel. For information on the ACMSACTDOB command, see “The Display Dependent Objects Command” starting on page CG 7-28 in the “Aldon/CMS General Topics Reference”. The following topics describe procedures for acting upon dependent objects through the panel interface: • “To include dependent objects in a checkout or emergency checkout” below • “To create dependent objects during promotion” below • “To display object requisites,” starting on page UG 2-38 • “To access the Act upon Dependent Objects panel,” starting on page UG 2-38 • “To display dependents of objects not defined to ACMS,” starting on page UG 2-39
To include dependent objects in a checkout or emergency checkout • At the Check Out Objects panel, shown in Figure 7 on page UG 2-8, or at the Check Out Objects (Emergency) panel, press F16 (Select dependent objects)
To create dependent objects during promotion 1. At the Promote Objects panel, shown in Figure 9 on page UG 2-18, in
the Do you wish to select dependent objects for create field, type Y. 2. Press ENTER.
The Select Dependent Objects to Create panel displays.
Aldon/CMS User’s Guide
Basics • UG 2-37
3. Select an environment with option 2 and press ENTER.
To display object requisites 1. At the Work with Objects by Developer panel or the Work with
Objects by Release panel, select an object with option 39 (Display requisite objects) and press ENTER. The Display Requisite Objects panel, which shows object dependency data, displays: CDSPRQTOBJ Object . . . . Object type . Release . . . Environment . Last Aldon/CMS
. . . . . . . . . . . . scan
----- Requisite ---Object Type ACTGLL *FILE
Command ===> F3=Exit F9=Retrieve
. .
Display Requisite Objects . . . . .
. . . . .
: : : : :
RCVPRT *PGM ALDON/ACMSDEMO/BASE QUA 03/11/97 14:26:59 *CURRENT
Defined by ACMS
F4=Prompt F12=Cancel
Create Dependent Y
. . . . . . . . .
Search Paths Database Other
F7=Previous environment
F8=Next environment
. . . . . . . . . .
Figure 14 - Display Requisite Objects panel 2. If you accessed this panel from the Work with Objects by Release
panel, use F8 (Next environment) and F7 (Previous environment) to move between copies of the object in different ACMS environments.
To access the Act upon Dependent Objects panel To work with dependent objects using a broad variety of options, use the Act upon Dependent Objects panel. You can access the Act Upon Dependent Objects panel from “Work with...” panels using the following paths: • At the Work with Objects by Developer panel or the Work with Objects by Release panel, select an object with option 41 (Act upon dependent objects). • At the Work with Tasks panel, select a task with option 41 (Act upon dependent objects) to work with objects dependent on objects associated with the task.
UG 2-38 • Basics
Aldon/CMS User’s Guide
• At the Work with Objects by Developer or the Work with Objects by Release panel, select several objects with option 42 (Act upon dependent objects*) to work with objects dependent on those selected in a single pool rather than working with objects dependent on each selected object separately as with option 41 (Act upon dependent objects). • At the More Functions panel, select option 6 (Act upon dependent objects), then specify a reference object and press ENTER. This method also lets you specify reference objects not defined to an ACMS release. See “To display dependents of objects not defined to ACMS” below for more information. Options available on the Act upon Dependent Objects panel when accessed in this way include most options available on the “Work with...” panel from which it was accessed.
To display dependents of objects not defined to ACMS You must have created object dependency records for the dependent objects you want to work with associating them with the objects you name as reference objects. See “Acquiring Object Dependency Data” on page UG 2-34 for more information.
Prerequisite
1. At any ACMS panel where F22 is available, press F22 (More
functions) to display the More Functions panel. 2. At the More Functions panel, select option 6 (Act upon dependent
objects) and press ENTER to display the Act upon Dependent Objects Selection panel: CDEPOBJSEL
Act upon Dependent Objects - Selection
Type choices, press Enter. Reference: Release . . . Application Group . . Reference environment . . If DVP, developer . . .
. . . . .
. . . . .
. . . . .
BASE + Name ACMSDEMO + Name ALDON + Name PDN DVP, ITG, QUA, PDN + Name
Reference objects: Name
Command ===> F3=Exit
Type +
F4=Prompt
Name
Type +
F9=Retrieve
Name
More: Type +
+
F12=Cancel
Figure 15 - Act upon Dependent Objects - Selection panel
Aldon/CMS User’s Guide
Basics • UG 2-39
3. At the Act upon Dependent Objects - Selection panel, in the Release,
Application, and Group fields, identify the release within which you want to work with dependent objects. 4. In the Reference environment field, type the three character
abbreviation corresponding to the release environment for which you want to work with dependent objects. 5. If, in the Reference environment field, you specified DVP, type the
name of the developer environment for which you want to work with dependent objects. 6. In the Reference objects section, in the Name and Type fields,
identify the requisite objects for which you want to work with dependent objects. Note
The requisite objects need not be defined to ACMS as part of an ACMS release. Reference objects should be objects that appear in the create or execution library list for objects in the reference release environment. 7. Press ENTER.
The Act upon Dependent objects panel displays listing all dependent objects for the requisite objects.
To display and act upon dependent objects recursively You can use ACMS to display and act upon objects that are dependent on dependent objects, and objects that are in turn dependent on those dependent objects. 1. Display dependent objects for an object defined to ACMS on the Act
Upon Dependent Objects panel as described in “To access the Act upon Dependent Objects panel,” starting on page UG 2-38. 2. At the Act upon Dependent Objects panel, by the dependent object for
which you want to display dependent objects, type 41 or 42 (Act upon dependent objects) and press ENTER. Note
UG 2-40 • Basics
Repeat step 2 above to display dependent objects at deeper levels of recursion.
Aldon/CMS User’s Guide
Emergency Checkout and Promotion Use the emergency checkout function of ACMS to bypass the normal development cycle when a production failure occurs. The emergency checkout function checks source directly out of the Production environment, even if a copy of the object exists in Integration, or Quality Assurance as shown in the figure below. Subsequent promotion of the copy checked out with emergency checkout moves the object directly back to the Production environment as shown in Figure 17.
Emergency checkout always takes Production copy
Standard checkout takes copy closest to Development
Development
Quality Assurance
Integration
Production
Figure 16 - Object Movement on Emergency Checkout
Standard promotions Development
Integration
Quality Assurance
Production
Promotion after emergency checkout
Figure 17 - Promotion After Emergency Checkout
Protection of Work in Progress with Conflict Records If copies of the object exist in Development, Integration, or Quality Assurance, ACMS creates conflict condition records on these active copies when you perform the emergency checkout. Conflict records prevent promotion of those copies of the object until the emergency changes have been integrated with the work in progress. You need not resolve the conflicts immediately. Promote the urgent changes you need to Production as soon as they are ready. Resolve conflicts on active copies of the object as time allows once Production is up and running again.
Aldon/CMS User’s Guide
Basics • UG 2-41
ACMS can also invoke Harmonizer, a source comparison utility available from Aldon, to help you merge the emergency changes with those made to the other active copies of the object if necessary.
To perform an emergency checkout • At the Work with Objects by Release panel, in the Opt field by the object, type 23 (Check out (emergency) and press ENTER. Panels used to complete the checkout closely resemble those used for a normal checkout. Note
Option 23 is not included in the default set of option prompts visible on the panel. Press F23 (More options) to display additional options. Identifying Objects Checked Out with the Emergency Checkout Function The Work with Objects by Developer and Work with Objects by Release panels both have a column labeled E. ACMS displays a Y in this column to indicate objects checked out with the emergency checkout function.
To promote objects checked out with the emergency checkout function • At the Work with Objects by Developer or the Work with Objects by Release panel, select the objects with option 7 and proceed as you would for a standard promotion. No special steps are required to promote objects checked out with the emergency checkout function. What Happens When Emergency Checkouts are Promoted The ACMS database maintains a record of the object's special status and promotes directly to Production without moving the object through any intervening environments that may exist.
Resolving Conflicts Conflicts and Conflict Condition Records In ACMS, conflict condition records or conflict records prevent hazardous object movements from taking place without proper authority and needed integration of parallel changes. The ACMS object database tracks all copies of an object within an application. ACMS uses information in the object database to identify checkouts that could result in overwriting of one set of changes by another on promotion and create conflict condition records on the copies of the object involved.
UG 2-42 • Basics
Aldon/CMS User’s Guide
Because ACMS tracks each copy of the object at risk and prevents dangerous promotions, a conflict need not be resolved immediately. A conflict must be removed by a user with the proper authority before promotion of the affected copies. Resolve conflicts by merging changes, then promote the copy of the object created by the merge.
Harmonizer and ACMS Harmonizer Helps Resolve Conflicts Harmonizer is a source comparison and merge utility available from Aldon. Harmonizer helps you resolve conflicts by • comparing the two conflicting copies, • producing a clear report indicating all lines added, changed, deleted, or moved in each version, and by • creating a composite output file containing the merged set of all changes in both copies. This merged source member serves as a starting point for integration of the two sets of changes. In some cases the merged source produced by S/Compare Harmonizer may be ready to test and use without any manual integration work. How Harmonizer and ACMS Work Together If Harmonizer is installed on your system, ACMS helps you use Harmonizer to resolve conflicting program changes. • ACMS automatically creates a reference copy of the program at risk when a checkout occurs that could result in overwriting one set of changes with another on promotion. Harmonizer compares each changed version with this reference copy to identify the changed lines. • Options within ACMS provide direct, seamless access to Harmonizer from the panel used to work with conflict conditions. ACMS passes Harmonizer all required parameters and later deletes the reference copy when you clear the conflict condition.
Working with Conflict Records To work with conflict records for a single object • At the Work with Objects by Developer or the Work with Objects by Release panel, select the object with option 12 and press ENTER. The Work with Requests and Conditions panel, shown in Figure 18, displays.
Aldon/CMS User’s Guide
Basics • UG 2-43
To work with conflict records for all objects • At the ACMS main menu, type option 4 (Work with conditions) and press ENTER. -orAt the Work with Objects by Release panel, press F20 (Work with conditions) The Work with Requests and Conditions panel displays: CWRKCND Position to
Work with Requests and Conditions . . . . . . .
__________
Type options, press Enter. 3=Check out* 4=Remove condition 27=Promote to parent*
Opt Object RCVPRT
Type *PGM
Release AC/BAS
*TOP, *BOT, starting characters
7=Promote* 30=Display log
Cnd C E
Condition Environment QUA
(*=Combined job) 19=Merge modified source 47=Install live* ---- Conflict ---Rel Environment * DVP ADA
Subset: Obj:RCVPRT Objtyp:*PGM Rel:ALDON/ACMSDEMO/BASE Command ===> _________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F10=View 4 F11=View F12=Cancel F14=WRKSBMJOB F17=Subset F18=WRKSPLF 24=More keys
Figure 18 - Work with Requests and Conditions panel
Cnd Column This column identifies checkout conflicts. The following values are possible: • Multiple Checkout Conflict (C M) This copy of the object and the one pointed to by the reference entry were in the Development environment at the same time. The Development copy that is associated with this conflict cannot be promoted before the conflict is removed. Prior to removing the conflict, check the copy that is pointed to by the reference entry to insure that you will not write over another developer's changes. • Emergency Checkout Conflict (C E) The copy of the object that is associated with this conflict was active (i.e. in Development, Integration, or Quality Assurance) when the source was copied from Production by an emergency checkout operation. This conflict must be removed before the active copy can be promoted. Prior to removing the conflict, insure that you will not write over the emergency fix when you promote the object to production.
UG 2-44 • Basics
Aldon/CMS User’s Guide
Condition Environment Column This column indicates the location of the conflict copy, the object copy that cannot safely promote forward toward Production. The conflict condition associated with the conflict copy prevents this promotion. After resolving the conflict, an authorized user removes the conflict condition. Promotion of this conflict copy without resolving the differences between the two copies would overlay the “at-risk copy” of the object containing a different set of changes made in parallel to the changes made in the conflict copy. Conflict Environment Column This column indicates the location of the at-risk copy of the object which could be overwritten with loss of changes it contains. Promotion of the conflict copy into the Conflict Environment would destroy the changes contained in the at-risk copy.
Resolving and Clearing Checkout Conflicts Before clearing a multiple checkout or emergency checkout conflict condition, merge changes from the conflict copy and the at-risk copy of the object to prevent overwriting of changes on promotion. Use Harmonizer from Aldon to resolve checkout conflicts if it is installed on your system.
To resolve a conflict without using Harmonizer 1. Check the object out to Development if it is not already present in
Development. 2. Examine the changes made in each copy and combine them as desired
into the new merged source member in your Developer library. Be sure to identify all changes in both copies relative to the common version from which both were created. Use an archived copy of the original common version if necessary. 3. Clear the “C M” or “C E” conflict condition as described in “To clear
a conflict condition” on page UG 2-46. 4. Promote the copy containing the integrated changes from
Development.
To resolve a conflict using Harmonizer You must have a licensed copy of Aldon's Harmonizer source comparison utility installed to use this method. Setup options control execution parameters of the comparison. Most users do not change the default options. See “Setting S/Compare-Harmonizer Defaults” in the “Aldon/CMS Setup and Administration Reference” for details.
Aldon/CMS User’s Guide
Basics • UG 2-45
1. At the Work with Objects by Developer or the Work with Objects by
Release panel, in the Opt field by the object flagged with the conflict condition, type 12 (Work with conditions) and press ENTER. The Work with Requests and Conditions panel, shown in Figure 18 on page UG 2-44, displays. 2. In the Opt field by the “C M” or “C E” conflict record, type 19
(Merge modified source) and press ENTER. The Specify Merge Source Options panel displays. Note
If Harmonizer is not installed, option 19 is not available. 3. At the Specify Merge Source Options panel identify the file and
library to receive the merged source produced by Harmonizer. You can use your ACMS developer library. Accepting the default file name, “MERGESRC” prevents overlay of source members by the same name that might be present in your developer library. 4. Press ENTER.
Harmonizer produces a report clearly indicating the changes made in each of the two conflicting copies and a “composite output file” containing the merged changes from both conflicting copies. See the Harmonizer user documentation for more information. 5. Edit the merged source to integrate the two sets of changes as desired. 6. Check the object out to Development if it is not already there. 7. Replace the checked out copy with the member produced by
Harmonizer containing the integrated changes. 8. Clear the “C M” or “C E” conflict condition as described in “To clear
a conflict condition” below. 9. Promote the copy containing the integrated changes from
Development.
To clear a conflict condition Merge changes from conflicting copies before clearing the conflict condition to avoid overlaying one set of changes with another. 1. At the Work with Objects by Developer or the Work with Objects by
Release panel, in the Opt field by the object flagged with the conflict condition, type 12 and press ENTER. The Work with Requests and Conditions panel, shown in Figure 18 on page UG 2-44, displays. 2. In the Opt field by the conflict condition record, type 4 and press ENTER.
You can now promote the object using option 7 “Promote” from any panel where it is available.
UG 2-46 • Basics
Aldon/CMS User’s Guide
Restricting Promotes Purpose of Promotion Requests
You can assign ACMS users specific authorities to limit their ability to promote to Production or any other ACMS environment. Typically, you might wish to require that most users request promotions to Production and grant authority to fulfill those requests to one or more managers. You can also restrict a user’s ability to promote into Integration and Quality Assurance to help maintain controlled test environments.
Making Promotion Requests Mandatory
To require promotion requests, set up user authorities as described in “Requiring request to promote to” starting on page SA 2-14 in the “Aldon/CMS Setup and Administration Reference”
To request a promotion 1. Select the object with option 17 (Request promote) on the Work with
Objects by Developer panel. The Request Promote panel displays: CRQSPRM
Request Promote
Type the additional promote information below, press Enter. Comment for log
. . . .
__________________________________________________
Objects selected for request promote: Object RCVIO RCVPRT
Type *PGM *PGM
Attribute RPG RPG
F3=Exit F10=View 3 F22=More functions
Release AC/BAS AC/BAS
F11=View 2
----- To ----Env Library PDN A54DMOPDN PDN A54DMOPDN
F12=Cancel
F20=Enlarge list
Figure 19 - Request Promote panel
The Request Promote panel lists all objects selected together for requesting promotion. 2. In the Comment for log field, type a comment for the development
log if desired and press ENTER. ACMS creates a promotion request record on the selected copy of the object. No object movement occurs at this time.
Aldon/CMS User’s Guide
Basics • UG 2-47
Identifying Objects with Pending Promote Requests ACMS indicates objects with promote requests pending with “R P” in the Cnd column on the Work with Requests and Conditions panel shown below: CWRKCND Position to
Work with Requests and Conditions . . . . . . .
__________
Type options, press Enter. 3=Check out* 4=Remove condition 27=Promote to parent*
Opt Object __ RCVIO
Type *PGM
Release AC/BAS
*TOP, *BOT, starting characters
7=Promote* 30=Display log
Cnd R P
Condition Environment QUA
(*=Combined job) 19=Merge modified source 47=Install live* ---- Conflict ---Rel Environment
Subset: Obj:RCVIO Objtyp:*PGM Env:Q Rel:ALDON/ACMSDEMO/BASE Command ===> _________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F10=View 4 F11=View 2 F12=Cancel F14=WRKSBMJOB F17=Subset F18=WRKSPLF 24=More keys
Figure 20 - Work with Requests and Conditions panel, Promotion Request
On the Work with Objects by Developer panel, an object with a pending promote request has an “R” in the Oth Cnd column with a blank in the Checkout Requests column. On the Work with Objects by Release panel, objects with pending promote requests and checkout requests display an “R” on the Cnds column. Distinguish promote requests from checkout requests by selecting an object with option 12 (Work with conditions) to display its pending requests on the Work with Requests and Conditions panel, or by pressing F20 to work with pending requests and conditions for all objects on the same panel.
To fulfill a promotion request Any user with the necessary authority can promote objects with pending promotion requests. Setting up user authorities is described in “Request or perform checkout or promotion” starting on page SA 3-9 in the “Aldon/CMS Setup and Administration Reference”. • Select the object with the pending promotion request with option 7 (Promote) on any panel where it is available. Option 7 (Promote) is available on the Work with Requests and Conditions, the Work with Objects by Developer, and the Work with Objects by Release panels, among others.
UG 2-48 • Basics
Aldon/CMS User’s Guide
Establishing and Meeting Testing Standards with ANALYZER This section includes the following topics: • Overview of the Aldon/CMS-ANALYZER Interface starting below • How ANALYZER and Aldon/CMS Work Together on page UG 2-50 • Additional Analyzer Concepts on page UG 2-51 • Details of Instrumenting and Setting Testing Requirements on page UG 2-51 • Procedures for Using ANALYZER with ACMS on page UG 2-53
Overview of the Aldon/CMS-ANALYZER Interface ANALYZER is a COBOL and RPG test coverage monitor available from Aldon. ANALYZER identifies how well you have tested a program before you move it into Production, telling you: • The percentage of code your tests have executed • The percentage of changed code your tests have executed • Which lines of code your tests have executed • Which lines of code were missed The interface between ACMS and ANALYZER The ACMS-ANALYZER interface: • Allows you to define and enforce testing requirements • Manages the process of preparing your code for testing with ANALYZER • Tracks execution statistics for all programs defined to ACMS regardless of the method used to initiate the test Requirements You must have a copy of the separately licensed ANALYZER tool installed on the same system as ACMS. Both ANALYZER and ACMS must be installed using the same Aldon common installation library. ANALYZER works on COBOL, COBOL ILE, RPG, RPG ILE, and RPG IV program source.
Aldon/CMS User’s Guide
Basics • UG 2-49
Interface Setup See “Setting ANALYZER Defaults” starting on page SA 6-1 in the “Aldon/CMS Setup and Administration Reference” for information on setting ANALYZER defaults.
How ANALYZER and Aldon/CMS Work Together 1. You check out programs in the normal fashion as described in “To
start work on an object,” starting on page UG 2-8. 2. You modify programs as desired in Development. Instrumenting the program and setting test standards
3. You then promote the programs. When you promote the programs
into the environment in which you want to measure testing with ANALYZER, you invoke ANALYZER as part of the promote job to prepare or instrument the programs for collection of testing statistics and set testing standards. For more information, see Step 11 in “To promote an object,” starting on page UG 2-18 and “To instrument a program and set testing standards,” starting on page UG 2-53. ANALYZER inserts code in the program source to track test execution and compiles this instrumented version of the program into the promote-to environment. To support the option of promoting without compiling, ACMS also saves a renamed copy of the compiled object created from uninstrumented source in the environment object library.
Location of source files
Testing standards enforced by ACMS
Testing the program
ACMS saves all instrumented and uninstrumented source in the source library designated for the environment. Source files used are as follows:
Type of Source
Source File Name
Instrumented source for all COBOL programs and non-ILE RPG
ANLZSRC
Instrumented source for all RPG ILE programs
ANLZSRCLE
Uninstrumented source
normal source file designated for each object
ACMS records the testing requirements established during the promote for the program in that environment in its database, and places a C A (conflict ANALYZER) conflict condition on the program in the promote-to environment. The conflict condition prevents promotion of the program to the next environment. 4. You then test the program by executing the instrumented program in
the test environment with your test data. Each test run generates statistics.
UG 2-50 • Basics
Aldon/CMS User’s Guide
Reporting test results to ACMS
5. You run the ANALYZER display report (command ANLZDSP) to
view the results of your tests. See ANALYZER documentation for more information. ANALYZER reports execution statistics to ACMS. 6. Repeat Step 4 and Step 5 as needed until you reach the desired level
of testing. Passing the test standards
The first time you run an ANALYZER display report after you reach both test requirements established for the program during the previous promotion, ACMS automatically changes the C A conflict condition to an A A (ANALYZER cleared) acknowledgement condition. 7. You can now promote the program to the next environment.
Promoting to the next environment
On promotion, ACMS: –
Deletes the instrumented copy of the program
–
Deletes the instrumented source
–
Promotes the uninstrumented version of the program
Additional Analyzer Concepts ANALYZER statistics measure testing coverage in terms of intervals. “Interval” Defined
In ANALYZER, an interval is a series of program statements that meet the following condition: if the first statement in the sequence is executed, then all of the remaining statements in the sequence must also be executed. ACMS lets you set two test standards: one relative to all intervals in the program, the other relative to all changed code intervals in the program.
“Changed Code” Defined
ANALYZER identifies changed code intervals by comparing line level change dates in the current copy of the program source with the date the program was checked out from Production.
Details of Instrumenting and Setting Testing Requirements This section describes the three fields used to request ANALYZER code insertion and set testing requirements.
Aldon/CMS User’s Guide
Basics • UG 2-51
The following figure shows these fields as they appear for a specific promote: CPRMOPT
Specify Promote Options More: -
Type choices, press Enter. Analyzer options: Instrument when promoting to . . Percentage of code to execute before promoting out of: Percentage of total code . . . Percentage of changed code . .
F3=Exit F5=Refresh F19=Submit without prompt
Y
Y=Yes, N=No 0 0
0-100 0-100
F12=Cancel F16=Review objects F22=More functions
Figure 21 - Fields for ANALYZER Instrumentation and Testing Requirements
Instrument when promoting to Specifies whether or not ACMS invokes ANALYZER to insert test monitoring code in your COBOL or RPG program source. You can specify this option at the release level for the Integration environment and/or QA environments. The release-level setting serves as a default for all promotes into a given environment. You can also override the release-level defaults for a specific promote into a given environment. Percentage of total code Specifies the percentage of total code intervals which must be executed by testing before ACMS allows promotion of programs out of the promote to environment. Percentage of changed code Specifies the percentage of changed code intervals which must be executed by testing before ACMS allows promotion of programs out of the promote to environment.
UG 2-52 • Basics
Aldon/CMS User’s Guide
Procedures for Using ANALYZER with ACMS To instrument a program and set testing standards 1. Check out programs in the normal fashion as described in “To start
work on an object,” starting on page UG 2-8. 2. Modify programs as desired in Development. 3. Begin to promote the object as described in “To promote an object,”
starting on page UG 2-18. 4. When you reach the Specify Promote Options panel, do the
following: –
Be sure that Instrument when promoting to is set to Y.
–
Change the settings of Percentage of total code and Percentage of changed code to reflect the testing levels desired for programs in this promote.
5. Press ENTER to submit the promote using the Submit Job panel.
For additional information on how ANALYZER works with ACMS see “How ANALYZER and Aldon/CMS Work Together,” starting on page UG 2-50.
To check the current level of testing Run the ANALYZER display report as described in the ANALYZER “User’s Guide.”
Aldon/CMS User’s Guide
Basics • UG 2-53
UG 2-54 • Basics
Aldon/CMS User’s Guide
Aldon/CMS User’s Guide User’s Guide UG
Chapter 3 Additional Features
This chapter provides information about using the development log and archiving features, and provides a high-level overview of object distribution. You will also find procedures to get you started with using the ACMS task tracking functions, work with user requests, and verify objects. The following topics are included: • “Development Log” on page UG 3-2 • “Archiving” on page UG 3-3 • “Object Distribution” on page UG 3-6 • “Task Tracking System” on page UG 3-7 • “User Requests” on page UG 3-16 • “Verifying Objects” on page UG 3-19 Online Help Text
Aldon/CMS User’s Guide
For detailed descriptions of the fields, options, and function keys displayed or available at any of the panels shown in this document, please see the online help text.
Additional Features • UG 3-1
Development Log ACMS maintains a log of all operations it performs if requested to do so during application setup (See Figure 37 on page SA 9-3 of the “Aldon/CMS Setup and Administration Reference”). The log includes an entry for each operation performed on each ACMS object. If you request an operation affecting multiple objects, a separate entry is generated for each object. For example, if you check out three objects simultaneously, ACMS creates a checkout log entry for each object. Creates of objects in the Development environment are the one exception to the above. ACMS does not log any information, including comments, regarding creates in Development.
Exception
To view an object's history • At the Work with Objects by Developer or the Work with Objects by Release panel, select an object with option 30 and press ENTER. The Display Development Log panel displays: CDSPDEVLOG
Display Development Log
Position to . . . . . . .
________
*TOP, *BOT, date
Type options, press Enter. 5=Display detail More: Opt Object RCVIO RCVIO RCVIO RCVIO RCVIO
Type *PGM *PGM *PGM *PGM *PGM
Release AC/BAS AC/BAS AC/BAS AC/BAS AC/BAS
Date 2/28/97 3/11/97 3/11/97 3/11/97 3/11/97
Time 18:44:14 13:44:38 14:06:08 14:16:23 14:20:50
Act Cde LOD CHK PRM CRT CHK
User ACMSDEMO ACMSDEMO ACMSDEMO ACMSDEMO ACMSDEMO
Er Version Cd 00000000 00000000 00100001 00100002 00100002
*BOT displayed: New display shows latest items (bottom of list). Command ===> _________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F9=Retrieve F10=View 4 F11=View 2 F12=Cancel F13=Delete F17=Subset F21=Print F22=More functions
Figure 22 - Display Development Log panel
This panel displays log entries sorted by date and time with the most recent events at the bottom of the list. Each log record identifies the object, the action performed, the user performing the action, comments, the object version number, and error codes generated during some operations.
UG 3-2 • Additional Features
Aldon/CMS User’s Guide
Use F10 and F11 (View n) to view additional information. Press F21 (Print) to print log entries. Activity Codes The Act Cde column indicates the activity performed. Object Version Numbers Each copy of each object in ACMS bears a unique eight-position object version number with no decimal. The eight digits are divided into two functional parts: the first three digits are the “development number” and the last five digits are the “creation number.” ACMS increments the development number each time you promote the object from Development into the first ACMS controlled environment. ACMS increments the creation number each time you create the object in a controlled environment. Object version numbers also appear in development log entries which provide an audit trail of all development activity. Object version numbers also provide the ability to verify the versions of objects installed on a remote system through ACMS object distribution and help organize archived copies of objects. For more information about object version numbers, see “Object Version Numbers” starting on page DO 4-35 in the “Aldon/CMS Daily Operations Reference”.
Archiving If an application uses the archive feature of ACMS, promotion of an object into the Production environment moves source for the prior copy of the object to the application archive before replacing it with source for the new copy of the object. If for any reason, the object must be retrieved, it can be checked out into the Development environment from the Archive library. Archiving Options Application-level setup options control whether or not archiving is performed, the number of copies saved, whether source only, or source and object is archived, and whether or not to compress source. See “Archive source only,” starting on page SA 2-8 and “Specify Archive Library” starting on page SA 9-5 in the “Aldon/CMS Setup and Administration Reference” for details on setting up the archive.
Aldon/CMS User’s Guide
Additional Features • UG 3-3
To work with archived objects 1. At the ACMS main menu, type option 3 (Work with archive options)
-orAt the Work with Objects by Release panel, in the Opt field by an object, type 24 (Work with archive). 2. Press ENTER.
Copies of the object saved in the archive display on the Work with Archive Objects panel: CWRKARCOBJ Position to
Work with Archive Objects . . . . . . .
__________
*TOP, *BOT, starting characters
Type options, press Enter. (*=Combined job) 3=Check out* 4=Delete 5=Browse source 23=Check out (emergency)* -- Archive --Opt Object Type Release Date Time Version Attribute Src Obj RCVENTRY *PGM AC/BAS 2/28/97 9:16 00900000 RPG Y N RCVENTRY *PGM AC/BAS 2/24/97 12:07 00800000 RPG Y N RCVENTRY *PGM AC/BAS 2/21/97 12:13 00700000 RPG Y N
Subset: Obj:RCVENTRY Objtyp:*PGM Rel:ALDON/ACMSDEMO/BASE Command ===> _________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F9=Retrieve F11=View 2 F13=Repeat F17=Subset F21=Print F22=More functions
Figure 23 - Work with Archive Objects panel
This panel includes a record for each archived copy of the object selected. Each record includes the object version number and flags indicating whether the archive includes source and/or the compiled object.
To restore an object from the archive to the normal development process 1. At the Work with Objects by Release panel, in the Opt field by the
object, type 24 (Work with archive). 2. Press ENTER.
Copies of the object saved in the archive display on the Work with Archive Objects panel shown in Figure 23. 3. In the Opt field by the copy of the object, type 3 (Check out) and
press ENTER. The Restore Archive Objects panel displays. This panel is very similar to the Check Out Objects panel shown in Figure 7 on page UG 2-8.
UG 3-4 • Additional Features
Aldon/CMS User’s Guide
4. In the To developer field, specify the developer to receive the object
and specify a task if desired. You can also enter a comment for the development log. 5. Press ENTER to restore the object from the archive.
Using Emergency Checkout on an Archived Object Use the emergency checkout function on an archived object to by-pass your normal testing requirements and quickly return an archived object to the Production environment. Restoring an archived copy of an object directly to Production could often result in level checks and a Production failure. To prevent this possibility, ACMS always restores archived objects to Development. Creation of the object in Development eliminates the possibility of level checks in Production. Subsequent promotion of the restored object from Development moves the object directly to Production to quickly restore your production environment to its desired state.
To return an archived object to Production 1. At the Work with Objects by Release panel, in the Opt field by the
object, type 24 (Work with archive). 2. Press ENTER.
Copies of the object saved in the archive display on the Work with Archive Objects panel shown in Figure 23 on page UG 3-4. 3. In the Opt field by the copy of the object, type 23 Check out
(emergency) and press ENTER. The Restore Archive Objects panel displays. This panel is very similar to the Check Out Objects panel shown in Figure 7 on page UG 2-8. 4. In the To developer field, specify the developer to receive the object
and specify a task if desired. You can also enter a comment for the development log. 5. Press ENTER to restore the object from the archive. 6. Return to the Work with Objects by Release panel and promote the
object to Production with option 7 (Promote).
Aldon/CMS User’s Guide
Additional Features • UG 3-5
Object Distribution After developing and testing objects, you can distribute them using ACMS object distribution. You can distribute objects to remote locations using: • IBM's Systems Network Architecture Distribution System (SNADS) • TCP/IP communications provided by CONNECT:Direct (available from Sterling Commerce,) or RSF • Magnetic media You can also distribute locally to libraries outside of ACMS on the same system. Distribute objects automatically on promotion into Integration, Quality Assurance or Production, or initiate distribution separately. Object distribution supports multiple locations and multiple libraries. After creating a distribution set which packages a group of objects for transmission, you can completely automate the remaining four steps: extract, transfer/transmit to the remote processor, restore on the remote processor, and install on the remote processor. The remote processor can notify the host upon completion of each step. ACMS supports various levels of roll-back during the distribution process to ensure successful installation. You can distribute objects during promotion to Integration, Quality Assurance, or Production to place objects on a remote processor for integration or quality assurance testing or for production use. Type Y in the Distribute from ITG, Distribute from QUA, or Distribute from PDN field on the Specify Promote Options panel shown in Figure 12 on page UG 2-21 when submitting the promote job. You can also distribute objects outside of the promote process. The ability to distribute during promotion is subject to restriction by release- and application-level options. See the "Aldon/CMS Object Distribution Reference" for details on distributing outside of the promote function. See the discussion of the Distribute when promoting to fields starting on page SA 13-12 in the "Aldon/CMS Setup and Administration Reference" for details on restricting distribution during promotion. ACMS distributes instrumented source from Integration or Quality Assurance
UG 3-6 • Additional Features
If you use ANALYZER to instrument source on promotion to Integration or Quality Assurance, and distribute source from Integration or Quality Assurance for testing on another system, ACMS distributes the instrumented copy of the source. This is true whether you distribute on promote or outside of the promote function.
Aldon/CMS User’s Guide
Task Tracking System Why Use the Task Tracking System Most information technology organizations have a three to five year backlog of software development with which to contend. The ACMS central object database enables the Task Tracking System to group objects needed to accomplish a goal and to associate the objects with notes describing the task. Basic Features and Functions The Task Tracking System is a communication method allowing end users, developers, and project managers to describe work to be done, new ideas, enhancements and/or problems. Task tracking provides a management tool to group objects as a single entity to simplify the work of ensuring all objects for a task move through the development cycle as one. You can create a time budget for a task, record hours worked, and generate statistics. Topics in this Section The following topics are included in this section: • “Adding a Task,” starting on page UG 3-8 • “Using the Aldon Response Manager Interface,” starting on page UG 3-12 • “Managing Tasks,” starting on page UG 3-13 • “Working with Task Hours,” starting on page UG 3-15 User Requests End users and developers can also request tasks and ask questions using a simple “requester” interface. For information on user requests, see the section“User Requests,” starting on page UG 3-16.
Aldon/CMS User’s Guide
Additional Features • UG 3-7
Adding a Task To add a new task 1. At the Work with Objects by Developer or the Work with Objects by
Release panel, press F7 (Add task). The Define Task panel displays: CDFNTSK
Define Task
Type choices. Task . . . . . . . . . Initial: Release . . . . Application Group . . . Type options, press Enter. 1=Select Opt 1 1 1
TESTTSK BASE + ACMSDEMO + ALDON +
Name *NONE, Name Name Name
Press F21 to select all.
Task definition option Specify definition Specify task notes Specify task objects Specify task releases/objects Specify task budget
Command ===> F3=Exit F4=Prompt F22=More functions
F9=Retrieve
F12=Cancel
F21=Select all
Figure 24 - Define Task panel 2. In the Task name field, type the name of the task. The name can be up
to ten (10) characters. Naming Tasks
Selecting Task Definition Options
Many different naming conventions are possible. Some organizations use an application abbreviation and a number, others use the user's initials and a number. Task names must follow rules for iSeries names and must be unique within a given ACMS installation. 3. In the Opt fields, type a 1 by Specify definition, Specify task notes,
and Specify task objects. After you familiarize yourself with the options you may wish to skip those not of interest. 4. Press ENTER.
The Specify Task Definition panel displays. 5. Continue with the instructions in “To specify the task definition” on
page UG 3-9.
UG 3-8 • Additional Features
Aldon/CMS User’s Guide
To specify the task definition 1. Complete the steps in “To add a new task” on page UG 3-8.
The Specify Task Definition panel displays: CTSKDFN
.
Specify Task Definition
Task . . . . . . . . . . :
TESTTSK
Type choices, press Enter. Task type Task text
. . . . . . . . . . . . . .
More: ENH + *BLANK, type code Add prompting on expenditure category field
Requested by . . . . . . Requesting department . Request date . . . . . .
Ada *BLANK 03/11/97
Priority . . . . . . . . Status . . . . . . . . .
3 + EVL +
Priority code Status code
Identifying keywords: Keyword 1 . . . . . . Keyword 2 . . . . . . Keyword 3 . . . . . .
*BLANK *BLANK *BLANK
*BLANK, keyword *BLANK, keyword *BLANK, keyword
+ *BLANK, department code Date
. . . . + . . . . . . . . . . . . . . .
. Command ===> F3=Exit
F4=Prompt
F5=Refresh
F9=Retrieve
F12=Cancel
. .
Figure 25 - Specify Task Definition panel 2. Position the cursor in the Task type field and press F4 (Prompt) to
display a list of types defined at your site. Note
Task types are user-defined at setup. The Select Task Type panel displays. 3. To select a code, type a slash (/) over the period by the item and press ENTER
to return to the Specify Task Definition panel.
4. In the Task text field, type text describing the task. 5. In the Requested by field, type the name of the person requesting the
task. 6. Use F4 (Prompt) for the Requesting department, Priority, and
Status fields to select predefined values. Status field
The Status field is perhaps the most important value in the task definition. A project manager changes this field to reflect progress of the task toward completion. Developers consult this field, usually by subsetting the list of tasks, to identify new work assigned to them. ACMS user authorities control who may update this field. You may want to assign tasks an initial status of “REQ” when initially requested by the end user. A manager can then assign new status as an escalation method. 7. Optionally, in the fields under Identifying keywords, type keywords
that will help you retrieve the task without knowing the task name.
Aldon/CMS User’s Guide
Additional Features • UG 3-9
8. If custom fields are available, press PAGE DOWN (ROLL UP) to
complete the custom fields. 9. Press ENTER.
The Edit Task Notes panel displays. 10. Continue with the instructions in “To edit task notes” below.
To edit task notes ACMS provides a facility for entering additional notes or other information regarding a task. The Edit Task Notes panel displays the note categories defined for use on your system. Categories use either of two note formats: a single screen, or, for users familiar with IBM's Source Editing Utility (SEU), an SEU member. The ACMS manager can create note templates for each note category to help standardize and structure information entered by users. 1. Complete the steps in “To add a new task” on page UG 3-8. 2. Complete the steps in “To specify the task definition” on page
UG 3-9. The Edit Task Notes panel displays: CEDTNTE Task
Edit Task Notes . . . :
TESTTSK
Type options, press Enter. 1=Change 5=Display Opt
Editor SEU *SCREEN *ARM
Exists No No
Notes category Description of proposed changes User Requests Aldon Response Manager associated notes
Command ===> F3=Exit F4=Prompt
F9=Retrieve
F12=Cancel
Figure 26 - Edit Task Notes panel 3. In the Opt field by the categories you want to work with, type 1 and
press ENTER. A note entry panel displays. See “Working with Task Notes” starting on page TT 8-3 in the “Aldon/CMS Task Tracking Reference” for more information on working with task notes.
UG 3-10 • Additional Features
Aldon/CMS User’s Guide
4. At the Edit Task Notes panel, press ENTER with no categories selected
to start adding task objects. The Add Task Objects panel displays. 5. Continue with the instructions in “To add task objects” below.
To add task objects • The most commonly used method of adding objects to an existing task is to name a task in the For task field during checkout or object creation • You can also assign objects in Development to a task using option 21 (Assign tasks) on the Work with Objects by Developer panel • See “Adding Objects to a Task” on page UG 5-15 for additional methods of adding objects to tasks Follow the instructions below to complete addition of the task and to define task objects during task addition if desired. 1. Complete the steps in “To add a new task” on page UG 3-8. 2. Complete the steps in “To specify the task definition” on page
UG 3-9. 3. Complete the steps in “To edit task notes” on page UG 3-10.
The Add Task Objects panel displays: CTSKOBJ Release
Add Task Objects . . . . . . . . :
ALDON/ACMSDEMO/BASE
Type choice. Default developer (for new entries) . . .
*NONE
+ *NONE, name
Type options, changes and additions, press Enter. 4=Remove ----- Object + ----Opt Name Type
More: Developer + *DFT *DFT *DFT *DFT *DFT *DFT *DFT
Command ===> F3=Exit F4=Prompt/Select from list F10=Page to new entries F12=Cancel
+
Text
F5=Refresh
F9=Retrieve
Figure 27 - Add Task Objects panel 4. In Name and Type fields, identify any objects you want to associate
with the task at this time. Press F4 (Prompt) to select from a list. 5. Press ENTER to return to the Define Task panel.
Aldon/CMS User’s Guide
Additional Features • UG 3-11
To include objects from more than one release To include objects from more than one release in a task, use the Specify Task Releases/Objects option instead of the Specify Task Objects option. See “Multiple-Release Tasks” starting on page TT 6-2 in the “Aldon/CMS Task Tracking Reference” for more information on working with multiple-release tasks. See “Working with Task Hours,” starting on page UG 3-15 for information on recording and reviewing hours worked on a task.
To specify a task budget If you need to track the amount of time spent on a task, use the Specify Task Budget panel to begin the time tracking process. Specify a task budget, enter any hours already accrued to the task, estimate the percentage of work already completed on the task, specify a scheduled completion date, and assign an ACMS user to manage the task if desired. See “Creating a Task Time Budget” starting on page TT 4-5 in the “Aldon/CMS Task Tracking Reference” for more information on working with task time budgets.
To complete the task definition • At the Define Task panel, press ENTER with no items selected to complete the creation of the task and return to the previous panel.
Using the Aldon Response Manager Interface If you have the Aldon Response Manager help desk system installed on the ACMS host system, or on a system connected to the ACMS host system via SNADS, you can link problems reported by customers in Aldon Response Manager to ACMS tasks implemented to solve those problems. See “Working with Problems” starting on page TT B-1 in the “Aldon/CMS Task Tracking Reference” for more information.
UG 3-12 • Additional Features
Aldon/CMS User’s Guide
Managing Tasks You can view lists of tasks, perform actions on all objects grouped into a task as a unit, and perform task management functions from the Work with Tasks panel shown in Figure 28.
To manage tasks • At the ACMS main menu, type option 5 (Work with tasks) and press ENTER. The Work with Tasks panel displays: CWRKTSK Position to
. . . . . . .
Task TESTTSK
Type ENH
. . . . . . . . . .
*TOP, *BOT, starting characters
Type options, press Enter. 2=Change 3=Check out 4=Delete 7=Promote 9=Close 10=Finish 11=Print attributes Opt
.
Work with Tasks
8=Display attributes 12=Work with objects ...
Text Add prompting on expenditure category field
. Subset: State:*ACT Rel:ALDON/ACMSDEMO/BASE Command ===> F3=Exit F4=Prompt F5=Refresh F6=Add task F12=Cancel F19=Work with objects F23=More options
. . F10=View 5 F11=View 2 F24=More keys
Figure 28 - Work with Tasks panel
See “System Setup” starting on page TT 2-1 in the “Aldon/CMS Task Tracking Reference” for more information on managing tasks.s
Checking out and Promoting Objects in Tasks To check out all objects in a task 1. Display the “Work with Tasks” panel as described in “To manage
tasks” on page UG 3-13. 2. In the Opt field by the task, type 3 (Check out) and press ENTER.
The Check Out Objects panel displays with a list of all objects associated with the task selected for checkout. 3. In the To developer field, specify the developer to receive the object.
You can also type a comment for the development log. 4. Press ENTER to check out all objects associated with the task.
Aldon/CMS User’s Guide
Additional Features • UG 3-13
To promote all objects in a task 1. Display the “Work with Tasks” panel as described in “To manage
tasks” on page UG 3-13. 2. In the Opt field by the task, type 7 (Promote) and press ENTER.
The Promote Objects panel displays with a list of all objects associated with the task selected for promotion. 3. To create dependent objects as part of the promote job, do the
following: a.
In the Create dependent objects field, type 1 and press ENTER. The Select Dependent Objects to Create panel, shown in Figure 10 on page UG 2-19, displays.
b.
Press ENTER after selecting dependent objects for creation to proceed to the Specify Promote Options panel shown in Figure 12 on page UG 2-21.
4. To promote without creating dependent objects, do the following: a.
In the Create dependent objects field, type 2.
b.
Press ENTER. The Specify Promote Options panel, shown in Figure 12 on page UG 2-21, displays.
5. Complete values on the Specify Promote Options panel and press ENTER
UG 3-14 • Additional Features
to submit the promote job using the Submit Job panel.
Aldon/CMS User’s Guide
Working with Task Hours To record hours for a task 1. Press F22 (More functions).
The More Functions panel, shown in Figure 4 on page UG 2-3, displays. 2. Type option 5 (Record task hours) and press ENTER to display the
Record Task Hours panel: CRCDTSKHRS
Record Task Hours
User . . . . . . . . . . :
ADA
Type new entries, press Enter. Date (*CURRENT, date)
Task + TESTTSK
Date *CURRENT
Command ===> F3=Exit F4=Prompt
Hours (-999.99 - 999.99) Act Hours Cde 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
F5=Refresh
Pct Cmpl(*CALC, 0 - 100)
Pct Cmpl Comment *CALC *CALC *CALC *CALC *CALC *CALC *CALC *CALC *CALC *CALC *CALC
F9=Retrieve
More:
F12=Cancel
+
F16=Review hours
Figure 29 - Record Task Hours panel 3. Complete the Task, Date, Hours, Act Cd (activity code), Pct Cmpl
(percent complete), and Comment fields. 4. Press ENTER to confirm you entries and return to the More Functions
panel. 5. Press ENTER again to exit the More Functions panel.
To review recorded hours 1. Display the Record Task Hours panel using instructions provided in
“To record hours for a task” on page UG 3-15. 2. Press PAGE UP (ROLL DOWN) to display previously entered task hours.
Records appear in the order in which the hours were recorded.
To review recorded hours summed by date 1. Display the Record Task Hours panel using instructions provided in
“To record hours for a task” on page UG 3-15.
Aldon/CMS User’s Guide
Additional Features • UG 3-15
2. Press F16 (Review Hours) to display the Review User Hours panel: CRVWUSRHRS
Review User Hours
User . . . . . . . . . . :
ADA
Subset: For task . . . . . Position to . . . . . . .
*ALL
Date 09/21/97 09/22/97 09/23/97
Hours 10.00 08.00 11.00
Subset: *NONE F4=Prompt
Date
+ *ALL, name *TOP, *BOT, date Hours
Date
Hours
F12=Cancel
Figure 30 - Review User Hours panel
This panel displays the total hours reported on each date. 3. In the Subset: For task field, type a task name to display only hours
reported for that task.
User Requests User requests allow a user to quickly request creation of a task, report trouble, or ask a question. The user may be an end-user not defined to ACMS or they may be an ACMS user. You may want to limit task addition authority to certain ACMS users. If you limit task addition authority, user requests allow ACMS users who are not authorized to create tasks to initiate tasks by communicating with those with the authority to do so. For Information on Responding to and Managing User Requests See sections in the chapter “Additional Actions” starting with “Responding to User Requests” on page UG 5-12.
UG 3-16 • Additional Features
Aldon/CMS User’s Guide
Interface Options for Submitting User Requests A user submits a user request using either a ACMS panel or a stand-alone program that runs on the host iSeries independent of ACMS. The advantage of the stand-alone program is that users need not be registered as ACMS users to make requests.
What Happens to Submitted User Requests? A project manager using ACMS responds to a user request by creating a task and associating it with the request or by typing a response text. The requester can inquire as to the status of their previously entered requests to receive information on the task, if one is associated with the request, and to read response text entered by the project manager.
User Requests from Within Aldon/CMS This section provides step-by-step instructions for submitting and checking on user requests on the iSeries, from within ACMS.
To submit a user request 1. On the iSeries, in ACMS, press F22 (More functions) from any panel
where it is available to display the More Functions panel. 2. In the Option field, type 4 and press ENTER.
The Enter User Request panel displays: CENTUSRRQS
. .
Enter User Request
User . . . . . . . . . . :
ADA
Ada User Definition
.
Type choices, press Enter. Description . . . . . . Type . . . . . . . . . . Urgency . . . . . . . .
1=Bug, 2=Enhancement, 3=Question 1=High, 2=Medium, 3=Low Text
Command ===> F3=Exit F4=Prompt
F9=Retrieve
F12=Cancel
More:
. . . . . . . + . . . . . . . . . . . . .
F16=Work with user requests
Figure 31 - Enter User Request panel
Aldon/CMS User’s Guide
Additional Features • UG 3-17
3. In the Description field, type a request description of up to 50
characters, and in the Type and Urgency fields, type numeric values to indicate the type and urgency of the issue. 4. In the Text field, type a message of any length describing the issue in
detail. 5. Press ENTER to submit the request.
To check on a user request 1. On the iSeries in ACMS press F22 (More functions) from any panel
where it is available to display the More Functions panel. 2. In the Option field, type 4 and press ENTER.
The Enter User Request panel, shown in Figure 31 on page UG 3-17, displays. 3. Press F16 to display the Work with User Requests panel subset to
display only requests you created. 4. In the Opt field by the request you want to check, type 5 (Display)
and press ENTER. The Display User Request panel displays, showing the current information regarding the request.
User Requests from the iSeries outside of Aldon/CMS This section provides step-by-step instructions for submitting and checking on user requests on the iSeries, outside of ACMS.
To submit a user request on the iSeries 1. On the iSeries, at any command line, type the following command:
ACMSUSRRQS 2. Press ENTER.
The Enter User Request panel, shown in Figure 31 on page UG 3-17, displays. 3. In the Description field, type a request description of up to 50
characters, and in the Type and Urgency fields, type numeric values to indicate the type and urgency of the issue. 4. In the Text field, type a message of any length describing the issue in
detail. 5. Press ENTER to submit the request.
UG 3-18 • Additional Features
Aldon/CMS User’s Guide
To check on a user request 1. On the iSeries, at any command line, type the following command:
ACMSUSRRQS 2. Press ENTER.
The Enter User Request panel, shown in Figure 31 on page UG 3-17, displays. 3. Press F16 to display the Work with User Requests panel subset to
display only requests you created. 4. In the Opt field by the request you want to check, type 5 (Display)
and press ENTER. The Display User Request panel displays, showing the current information regarding the request.
Verifying Objects ACMS maintains a database describing the location and nature of all application objects. This allows you to use the ACMS verify functions at any time to check the integrity of application libraries, data sets, and remote libraries that receive distributed objects. Verification checks for addition or deletion of objects from outside of ACMS, checks object ownerships and authorities, and identifies possible problems with logical/physical file relationships.
To verify an application release or distributed objects 1. On the ACMS main menu, type option 13 and press ENTER to request
verification of a release on the host system or of objects placed on a remote processor using ACMS object distribution. The Work with Releases panel displays. 2. In the Opt field by the release you want to verify, type 9 and press ENTER.
The Populate Menu displays. 3. Do one of the following:
–
Type 1 to verify a release on the host system.
-or–
Type 9 to verify distributed objects on a remote system.
4. Press ENTER.
Aldon/CMS User’s Guide
Additional Features • UG 3-19
To verify a data set 1. On the ACMS main menu, type option 14 and press ENTER.
The Work with Data Sets panel displays. 2. In the Opt field by the data set you want to verify, type 9 and press ENTER.
The Verify Data Set panel displays. 3. Complete the fields at the Verify Data Set panel and press ENTER.
To verify a single data library 1. At the ACMS main menu, type option 14 (Work with data sets) and
press ENTER to display the Work with Data Sets panel. 2. At the Work with Data Sets panel, in the Opt field by the data set with
which the data library you want to verify is associated, type 12 (Work with libraries) and press ENTER to display the Work with Data Libraries panel. 3. At the Work with Data Libraries panel, in the Opt field by the data
library you want to verify, type 9 (Verify) and press ENTER to display the Verify Data Library panel. 4. Select objects to verify and press ENTER to display the Submit Job
panel. 5. Press ENTER to submit the verify job.
UG 3-20 • Additional Features
Aldon/CMS User’s Guide
Aldon/CMS User’s Guide User’s Guide
UG
Chapter 4 User Interface
This chapter explains the interfaces available to access ACMS functions, how to set advanced user preferences, and how to use subsetting panels in the product. The following topics are included: • “Available Interfaces” on page UG 4-2 • “Summary of Panel Interface Features” on page UG 4-2 • “Setting Advanced User Preferences” on page UG 4-4 • “Subsetting” on page UG 4-9 Online Help Text
Aldon/CMS User’s Guide
For detailed descriptions of the fields, options, and function keys displayed or available at any of the panels shown in this document, please see the online help text.
User Interface • UG 4-1
Available Interfaces The main access to ACMS is through the panel interface. Many functions may also be performed using commands or PDM user defined options provided by Aldon. These Aldon provided PDM options may also be used within Hawkeye's Pathfinder and ASC's Abstract Probe+ cross referencing and documentation tools. PDM-style options may also be created to perform custom actions from object lists within the ACMS panel interface. User exits are also available to invoke custom user provided programs during most functions that move or create objects.
Summary of Panel Interface Features Common User Access Standards ACMS panels follow the Common User Access Standards defined for the iSeries by IBM. The goal of these standards and of implementation of Aldon products in accordance with them, is to provide a single user interface across applications that is consistent, efficient, and easy to use. A user's time and energy can then be spent in productive work rather than in untangling and deciphering the idiosyncrasies of each application they use. Although the panel interface is designed to be clear and simple, users may have questions about some features, or may want to insure they are taking full advantage of all the interface has to offer. “Option Processing for Sub-Files (Lists)” starting on page DO F-13 in the "Aldon/CMS Daily Operations Reference" describes features important for Aldon users. Features most important for new ACMS users are summarized below:
Context-Sensitive Help Text Context sensitive help text is available at all times throughout Aldon's iSeries applications by pressing the Help or F1 key. Context is determined by the panel displayed and by the position of the cursor when Help is requested. Place the cursor on or near an input field to retrieve a description of the field's function and valid entry options.
UG 4-2 • User Interface
Aldon/CMS User’s Guide
Field Level / Panel Level Help text is available for input fields, fields that display information, messages, function keys, and some other screen features. Panel level help text, which gives an overview of the purpose of the panel and its relationship to preceding and following panels, is also provided. To retrieve panel level help text, position the cursor on the title line or on any empty area of the panel, or press F2 after retrieving field level help. Global Help Topics To reach global help text relating to the product as a whole, retrieve field or panel level help text, then press F11 (Search index). A list of global help topics displays on the IBM Search Index panel. Select the desired global help topic with option 5 and press Enter. Global help topics include a glossary of important ACMS terms, a descriptive list of user authorities, and overviews of the checkout, promote, and object creation functions. Hypertext Links and Search Index Hypertext links in some help topics provide access to additional help information. Hypertext links appear as underscored orange text. Activate a link by placing the cursor at or on the link text and pressing the Enter key. Press F11 on any Aldon help display to access additional information by topic through a search index.
Input Fields: Prompting and Selecting Input fields appear as underscores. If the list of values allowed for a field is fixed and short, it appears to the right of the field. A “+” symbol after a field indicates you can prompt for a list of allowed values with F4. Values display on a “single selection panel” with each allowed value preceded by a period. Type a slash (/) over the period preceding the desired value and press Enter to make a selection.
Scrolling When there is more information to view than will fit on one panel, “More: +” is displayed on the right side. Press Page Down (or Roll Up) to view additional items. When “More: -+” or “More: -” is displayed, press Page Up (Roll Down) to return to previously viewed items.
Aldon/CMS User’s Guide
User Interface • UG 4-3
Fully Functional Command Line On most panels a fully functional command line appears immediately above the function key prompts. Any iSeries command may be executed from this line. Retrieve commands executed during the current ACMS session by pressing F9. To maintain iSeries security, the command line does not display for users with “Limit Capabilities” set to *YES in their user profile.
WRKSBMJOB and WRKSPLF Access Access to the IBM WRKSBMJOB command via F14 and WRKSPLF via F18 is also provided on many panels.
Setting Advanced User Preferences Perform all the following functions from the More Functions panel accessed by pressing F22 (More functions) from most panels within ACMS.
To specify a default task Specify a default task chiefly for use in checking out objects. You can also reference the default task using the special value *USERDFT on some subsetting panels and when performing some ACMS functions through the command interface. 1. Press F22 (More functions) from most panels within ACMS to
display the More Functions panel. 2. Position the cursor in the Task field. 3. Enter the name of the desired task or press F4 (Prompt) to select a
task from a list of all tasks selected by the current release, application, and group values. 4. Press ENTER to confirm your changes.
UG 4-4 • User Interface
Aldon/CMS User’s Guide
To change development tool defaults Development tool defaults specify the development tool ACMS invokes when a user working in an application selects an object for editing with option 2 (Edit) or option 19 (Alt Edit), or for browsing with option 5 (Browse). Work with development tool defaults to tell ACMS when to invoke a development tool. 1. Press F22 (More functions) from most panels within ACMS to
display the More Functions panel. 2. At the More Functions panel, type option 1 (Edit development tools)
and press ENTER to work with user-level development tool defaults. The Edit User Development Tools panel displays: CEDTDVMTOL
Edit User Development Tools
User . . . . . . . . . . :
ADA
Type changes, additions and deletions, press Enter. To add or change an entry, type new data. To delete an entry, space over the Tools entries. Object type (*ANY, type) Object attribute (*ANY, name, generic*, *BLANK) Application (*ANY, group/application) More: + Object Edit tools Browse Type + Attribute + Application + Primary + Secondary + tool + *ANY *ANY *ANY . *ANY *ANY *ANY . *ANY *ANY *ANY . *ANY *ANY *ANY . *ANY *ANY *ANY . *ANY *ANY *ANY . *ANY *ANY *ANY . . Command ===> . F3=Exit F4=Prompt F5=Refresh F9=Retrieve F12=Cancel F16=Review defaults
Figure 32 - Edit User Development Tools panel
See “To set development tool defaults for a single user” starting on page SA Chapter 7-10 in the "Aldon/CMS Setup and Administration Reference" or help text for this panel for details. 3. Specify the type, attribute, and application for which you would like
to change the default development tool selections in the left three columns. 4. Prompt to select from the list of available development tools for
option 2 (Edit) and option 19 (Alt edit) invocation. Option 2 invokes the primary editing tool, option 19 invokes the secondary editing tool. 5. Press ENTER to confirm your changes.
Aldon/CMS User’s Guide
User Interface • UG 4-5
To define a user options file 1. Press F22 (More functions) from most panels within ACMS to
display the More Functions panel. 2. Type option 2 (Set user-defined option file) and press ENTER to
specify a user-defined option file. The Set User-Defined Option File panel displays: CUSROPT
Set User-Defined Option File
Type choices, press Enter. File . . . . . . . . . Library . . . . . . Member . . . . . . . .
QAUOOPT ADA *FIRST
*NONE, name *NONE, name *FIRST, *NONE, name
Command ===>
F3=Exit
. .
F4=Prompt
F5=Refresh
F9=Retrieve
F12=Cancel
Figure 33 - Set User-Defined Option File panel 3. In the File, Library, and Member fields, identify the member
containing user-defined options. 4. Press ENTER to confirm your changes.
User-defined PDM-style options can be used to perform actions on several ACMS panels. See “PDM-Style User Options” starting on page DO D-1 in the "Aldon/CMS Daily Operations Reference" for details on defining and using PDM-style user options with the ACMS panel interface.
To set operation defaults 1. Press F22 (More functions) from most panels within ACMS to
display the More Functions panel. 2. At the More Functions panel, in the Opt field, type 3 (Set operation
defaults) and press ENTER.
UG 4-6 • User Interface
Aldon/CMS User’s Guide
The first page of the Set User Operation Defaults panel displays: CUSROPRDFT
. .
Set User Operation Defaults
Type choices, press Enter. More:
+
1. Select dependent objects on promote The promote objects function includes the following option on the first panel. Your response determines whether a subsequent panel appears for selection of dependent objects. Please specify below your default entry for this option. . . Do you wish to select dependent objects for create . . . N Y=Yes, N=No . . 2. Screen Design Aid development tool If you select option 19=AltEdit for an object of type *FILE, attribute DSPF, and the source member for the file does not yet exist, Aldon/CMS cannot determine the intended Screen Design Aid function. Please specify below the action Aldon/CMS should take in this situation. Aldon/CMS response . . .
F3=Exit
3
F5=Refresh
1=Design display, 2=Design menu, 3=Prompt for desired function
F12=Cancel
Figure 34 - Set User Operation Defaults panel, page 1 of 2 3. Use the fields on this panel to set default values controlling:
–
Creation of dependent objects during promote jobs
–
The effect of selecting new, empty DSPF *FILE objects with option 19 “Alt Edit.”
4. Press PAGE DOWN (ROLL UP) to view additional fields.
Page two of the Set User Operation Defaults panel displays: CUSROPRDFT
Set User Operation Defaults
Type choices, press Enter. More: 3. Cursor position in More Functions You may specify the initial positioning of the cursor on the More Functions panel. Please specify below the input line on which the cursor should be positioned when More Functions is requested. Initial cursor position
Function key not allowed. F3=Exit F5=Refresh
1
1=First available input line, 2=Option line, 3=Command line
F12=Cancel
Figure 35 - Set User Operation Defaults panel, page 2 of 2
Aldon/CMS User’s Guide
User Interface • UG 4-7
5. Use the fields on this panel to set default values controlling:
–
Initial cursor positioning on the “More Functions” panel
6. Press ENTER to confirm you choices.
UG 4-8 • User Interface
Aldon/CMS User’s Guide
Subsetting All “Work with...” panels in ACMS allow you to tailor the items displayed in the list through a “Subset...” panel accessed with F17 (Subset). CSBSOBJDVP
. . . .
Subset Objects by Developer List
Type choices, press Enter. Developer
. . . . . . .
*USERDFT
+ *USERDFT, *ALL, *NAMED, *CRTNONRES, name Environment . . . . . . *ACT *ACT, D/I/Q . . Object . . . . . . . . . *ALL *ALL, generic*, name . Object type . . . . . . *ALL + *ALL, type . Object attribute . . . . *ALL + *ALL, generic*, name, *BLANK . . Has condition category . *NA *NA, *ANY, *NOT, A/C/R . . Included in task . . . . *NA + *USERDFT, *NA, *ANY, *NOT, . generic*, name . . Release . . . . . . . . *USERDFT + *USERDFT, *ALL, generic*, name . Application . . . . . *USERDFT + *USERDFT, *ALL, generic*, name . Group . . . . . . . *USERDFT + *USERDFT, *ALL, generic*, name . . . User defaults: Rel:ALDON/ACMSDEMO/BASE Dvp:*NONE Tsk:TESTTSK . F3=Exit F4=Prompt F5=Refresh F12=Cancel F22=More functions
Figure 36 - Subset Objects by Developer List panel
Subset panels work with user default values set on the More Functions panel. The special value *USERDFT represents a value specified on the More Functions panel. In the sample subset panel shown above, the value for Developer is *USERDFT. If the More Functions panel specifies a developer name, accepting the value *USERDFT on the Subset panel is the same as entering that developer name on the Subset panel. Note
All Subset panels default the Release, Application, and Group fields to *USERDFT. When you press ENTER, only items that meet all subsetting criteria display on the associated “Work with...” panel. ACMS saves values specified on a Subset panel only until you exit the associated “Work with...” panel. Values entered on the More Functions panel are saved until you change them. Examples • To display objects checked out by all developers, type *ALL in the Developer field. • To display only objects in Integration, type I in the Environment field.
Aldon/CMS User’s Guide
User Interface • UG 4-9
UG 4-10 • User Interface
Aldon/CMS User’s Guide
Aldon/CMS User’s Guide User’s Guide UG
Chapter 5 Additional Actions
This chapter provides information on when and how to add objects to and delete objects from ACMS, how to work with pseudo-source and data libraries, and how to perform additional task-related work. The following topics are included: • “Adding an Object” on page UG 5-2 • “Working with Pseudo-Source” on page UG 5-6 • “Deleting a Copy of an Object” on page UG 5-10 • “Using Data Libraries for Testing” on page UG 5-11 • “Additional Task Actions” on page UG 5-12 Online Help Text
Aldon/CMS User’s Guide
For detailed descriptions of the fields, options, and function keys displayed or available at any of the panels shown in this document, please see the online help text.
Additional Actions • UG 5-1
Adding an Object When to Add an Object to Aldon/CMS Adding an object to ACMS defines it to the ACMS object database. Add an object to ACMS when you want it to appear on ACMS displays and be available for manipulation using ACMS functions. You must add an object to ACMS before promoting it or creating it through the ACMS interface. An object need not exist at the time you add it to the ACMS database. ACMS just issues a warning message asking you to confirm addition of any object not found in your developer library. *RCDS Objects You may also wish to add an object to allow manipulation of a defined range of records together as a unit. ACMS provides a facility to define such a range of records as an *RCDS “records object.” Records objects may be checked out, modified in Development, and promoted through testing environments just like any other object. See “Record Objects” on page DO C-1 in the “Aldon/CMS Daily Operations Reference” for detailed information on defining and working with *RCDS objects. See“Interface to J.D. Edwards Tools” on page TI 3-1 of the “Third Party Interfaces Reference” for information on using *RCDS objects to work with J.D. Edwards objects.
Object Addition Concepts Extended Attribute For program objects, ACMS uses an additional field, the extended attribute, to indicate handling procedures appropriate for each type of object. Each program object, SQL function, or SQL procedure uses one of the following five extended attributes:
UG 5-2 • Additional Actions
OPM (Original Program Model)
Create a program object using a traditional CRTxxxPGM command which does not make use of any IBM Integrated Language Environment (ILE) features.
BND
Create a program object with a CRTBNDxxx command which makes use of some ILE features.
ILE
Create an ILE program object by linking one or more *MODULE objects with the CRTPGM command.
SQL
Create an SQL-defined SQL function or stored procedure.
Aldon/CMS User’s Guide
EXT
Create an externally defined SQL function or procedure.
SRC
Create a sourced SQL function.
Data object ACMS lets you define which objects are data objects and which are not. For objects you designate as data objects, ACMS allows you to specify copy file format options and custom conversion programs. By default, ACMS assigns a data status to a new object as follows:
Object type
Default Data Status
Physical file
Data
Logical file
Non-data
Other object
Non-data
You can override the default status by typing the appropriate option number when you define a new object.
Source Option and Pseudo-Source ACMS handles source based objects and non-source based objects. In addition, the ACMS pseudo-source facility allows you to store, retrieve, and use the information needed to create CL based objects such as data areas, JOBDs and message files and SQL based objects such as tables, views, and aliases. By using pseudo-source in ACMS, you can automatically create these objects when necessary, and modify them without having to remember commands and option settings previously used to create the object. For SQL aliases, you can create pseudo-source yourself or ACMS will generate it for you automatically. Pseudo-source is a member containing CL commands which, when executed, create an application object. ACMS interprets the CL commands and creates the object when requested to do so on promotion into a new environment, or in place within an environment. Use pseudo-source for any application object that can be created from CL commands.
To add an object Note
Aldon/CMS User’s Guide
For more information on adding SQL objects, see “Adding SQL Objects,” starting on page DO G-2.
Additional Actions • UG 5-3
1. At the Work with Objects by Developer panel, press F6.
The Add Release Object panel displays: CADDOBJ
.
Add Release Object
. .
Type choices, press Enter.
. Release . . . . . . . . Application . . . . . Group . . . . . . . Object . . . . . . . . .
Object type . . . Object attribute . Extended attribute Data object . . Developer . . . Source option . . Source file . . Source member . Task . . . . . . . Comment for log .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command ===> F3=Exit F4=Prompt
BASE + Name ACMSDEMO + Name ALDON + Name DEMORPG4
. . . .
Name *PGM + Type RPG + Attribute OPM ILE, BND, OPM (*PGM) SQL (*FILE) * *=Default, Y=Yes, N=No ADA + Name 1 1=Source, 2=Pseudo source, 9=None QRPGSRC Name . *OBJNAME Name, *OBJNAME . + Name .
F7=Add task
. . . F22=More functions
F12=Cancel
Figure 37 - Add Release Object panel 2. Complete fields on the panel using help text for assistance where
necessary. Use F4 (Prompt) with the cursor in any field followed by a plus (+) sign to select a value for the field from a list. 3. Press ENTER after completing necessary values.
If the release to which you are adding the object uses more than one library group, the Select Library Group for Object panel displays: CSELOBJLGP
Select Library Group for Object
Object . . . . . . . : Object type . . . . :
TESTOBJ *PGM
Release
EVENS/MARK/BASE
. . . . . . :
Object attribute . . : Extended attribute . : Data object . . . . :
CBL OPM No
A library group must be selected for the object in this release. Type option, press Enter. 1=Select (one only) Opt
F3=Exit
UG 5-4 • Additional Actions
Production Library MDEBASPDN1 MDEBASPDN2 MDEBASPDN3 MDEBASPDN4
Library Group 01 Programs 02 Files 03 Source 04 Other
F4=Prompt
F9=Retrieve
F12=Cancel
F22=More Functions
Aldon/CMS User’s Guide
Note
Library groups displayed on these panels are for demonstration purposes only. You can define as many or as few library groups as necessary to meet your needs. See “Stage 5: Specifying Library Groups” starting on page SA 13-16 in the “Aldon/CMS Setup and Administration Reference” and “Changing Release Options” starting on page SA 22-4 in the “Aldon/CMS Setup and Administration Reference” for more information. 4. At the Select Library Group for Object panel, in the Opt field by the
library group you want to receive the object you are adding, type 1 (Select) and press ENTER. If you are adding a source based object, the Select Library Group for Source panel displays: CSELSRCLGP
Select Library Group for Source
Object . . . . . . . : Object type . . . . :
TESTOBJ *PGM
Release
EVENS/MARK/BASE
. . . . . . :
Object library group :
Object attribute . . : Extended attribute . : Data object . . . . :
CBL OPM No
01 Programs
A library group must be selected for the source in this release. Type option, press Enter. 1=Select (one only) Opt
Production Library MDEBASPDN1 MDEBASPDN2 MDEBASPDN3 MDEBASPDN4
Library group 01 Programs 02 Files 03 Source 04 Other
F3=Exit
F4=Prompt
F9=Retrieve
F12=Cancel
F22=More Functions
5. At the Select Library Group for Source panel, in the Opt field by the
library group you want to receive source for the object you are adding, type 1 (Select) and press ENTER. ACMS defines the object to the object database and displays the Add Release Object panel again. You can continue to add objects by changing values on the Add Release Object panel as appropriate and then pressing ENTER to confirm your entries. To exit the add object function and return to the previous panel, press ENTER a second time without modifying any fields.
Aldon/CMS User’s Guide
Additional Actions • UG 5-5
Working with Pseudo-Source The object need not already exist when you create pseudo-source for it. Aldon recommends use of a separate dedicated source file such as PSEUDOSRC to contain pseudo-source members. Library Replacement Variable for Pseudo-Source Replace the name of the library with &LIB in the pseudo-source. When ACMS interprets the CL commands or SQL statements to create the object, it replaces &LIB with the correct library name, depending on the environment for which the object is created. Note
When creating pseudo-source for an SQL table with a constraint based on a reference to a field in that same table, be sure to specify &LIB in the “references” statement of the constraint. Member Type Create pseudo-source members for CL based objects with a member type of CLP. You may also use member type CL, however, you must then turn off syntax checking to permit entry of the &LIB ACMS variable. Create pseudo-source members for SQL based objects with a member type of SQLC or another member type of your choosing. The member type SQLC has the advantage of identifying the object as SQL-based on iSeries displays outside of ACMS and of avoiding syntax checking problems from use of the &LIB ACMS variable. What to Include in a Pseudo-Source Member In the source member, include the command to create the object and any commands necessary to modify the object into the desired form. It is not necessary to include a command in the pseudo-source to delete the object before re-creating it. ACMS handles this automatically. Comments To include comments in the pseudo-source member, place “/*” and “*/” around the comment text. White Space Use blank lines and indenting to improve the readability of your pseudo-source as desired.
To create pseudo-source for a new CL based object 1. Open a source member with a member type of CLP. 2. In the member, enter the CL commands needed to create the object.
UG 5-6 • Additional Actions
Aldon/CMS User’s Guide
3. In the create command entered for the object in the member, replace
the name of the library to contain the object with “&LIB”. 4. Save the member in a file of your choosing in your Developer library. 5. Add the object to ACMS using the standard procedure described in
the section “To add an object” on page UG 5-3. In the Source option field on the Add Release Object panel specify 2 for pseudo-source.
To create pseudo-source for a new SQL based object 1. Open a source member with a member type of SQLC. 2. In the member, enter the SQL statements needed to create the object. 3. In the create statement entered for the object in the member, replace
the name of the library to contain the object with “&LIB”. 4. Save the member in a file of your choosing in your Developer library. 5. Add the object to ACMS using the standard procedure described in
the section “To add an object” on page UG 5-3. In the Source option field on the Add Release Object panel specify 2 for pseudo-source.
To create pseudo-source for an existing SQL-based object ACMS provides access to an IBM application program interface (API) which generates SQL statements for an existing SQL-based object, or CL based physical or logical file. The SQL statements, which are placed in a source member, reproduce the original object. You can then edit these SQL statements into pseudo-source form. This function is particularly useful if you have SQL-based objects for which you do not have source. Note Prerequisites
Some bugs in the IBM API have been reported. For the following procedure, the object must be defined to ACMS and present in the Development environment. 1. At the Work with Objects by Developer panel, in the Opt field by the
object, type 43 (Generate DDL from SQL object) and press ENTER.
Aldon/CMS User’s Guide
Additional Actions • UG 5-7
The Generate SQL Data Definition Language panel displays: CGENSQLDDL
Generate SQL Data Definition Language
Type choices, press Enter. More: Database object
. . . . . . :
Library . . . . . . . . . : Database object type . . . . :
DOUGS2 TABLE
Source file to receive output Library . . . . . . . . . . Output member options: Member to receive output . . Replace or add records . . .
PSEUDOSRC DOUGS
Name Name, *LIBL, *CURLIB
TABLENSRC *REPLACE
Name, *FIRST *REPLACE, *ADD
Command ===> F3=Exit F4=Prompt
+
TABLENSRC
F9=Retrieve
F12=Cancel
F22=More functions
Figure 38 - Generate SQL Data Definition Language panel 2. In the Source file to receive output field identify the source file to
receive the generated source. For example you might want to use PSEUDOSRC. 3. In the Library field for the source file type the name of your
developer source library. 4. Complete the remainder of the panel. 5. Press PAGE DOWN (ROLL UP) to work with additional parameters. 6. Press ENTER to create the source member.
The resulting source member contains SQL statements for the object. 7. Associate the created member with the object as pseudo-source by
following the instructions in “To associate pseudo-source with an object defined to Aldon/CMS,” starting on page UG 5-9. Begin with Step 3. 8. At the Work with Objects by Developer panel, in the Opt field by the
object, type 2 (Edit) and press ENTER to edit the member. Convert the generated SQL statements in the member into pseudo-source form by removing unnecessary statements and replacing the create-in library name with the &LIB ACMS substitution variable. Note
The generate DDL function can also be used on an object not defined to ACMS by selecting option 14 (Generate DDL from SQL object) on the More Functions panel. Pseudo-Source for SQL
UG 5-8 • Additional Actions
Aldon/CMS User’s Guide
To associate pseudo-source with an object defined to Aldon/CMS 1. Check the object out to Development if it is not already there. 2. Create pseudo-source for the object by doing following the
instructions in one of the following sections: –
“To create pseudo-source for a new CL based object,” starting on page UG 5-6
–
“To create pseudo-source for a new SQL based object,” starting on page UG 5-7
–
“To create pseudo-source for an existing SQL-based object,” starting on page UG 5-7
3. At the Work with Objects by Developer panel, in the Opt field, type
16 and press ENTER. The Change Checked Out Object panel displays: CCHGOBJ
. .
Change Checked Out Object
Object . . . Object type Release . . Developer .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
: : : :
OLDMSGS *MSGF ALDON/ACMSDEMO/BASE CHARLES
. . . . . . .
Type choices, press Enter. Object attribute . . . : Extended attribute . . : Data object . . . . . . Source option
. . . . .
Source file . . . . . Source member . . . . Source library group :
N 2 PSEUDOSRC OLDMSGS 3
Y=Yes, N=No 1=Source, 2=Pseudo-source, 9=No source Name Name .
. . . .
Command ===> F3=Exit
. . F4=Prompt
F9=Retrieve
F12=Cancel
F22=More functions
Figure 39 - Change Checked Out Object panel 4. In the Data object field, do one of the following:
–
If you want ACMS to treat the object as a data object, type a Y
–
If you do not want ACMS to treat the object as a data object, type an N
5. In the Source option field, type 2 (Pseudo source). 6. In the Source file and Source member fields, identify the source file
and member containing the pseudo-source. 7. Press ENTER to confirm the changes and return to the previous panel.
Aldon/CMS User’s Guide
Additional Actions • UG 5-9
Example of Pseudo-Source for a Message File The figure below shows an example of pseudo-source for a message file. Columns . . . : 1 71 Edit CHARLES/PSEUDOSRC SEU==> SAMPLEMSGS *************** Beginning of data ************************************* 0001.00./* Enclose comments such as this one as shown. */ 0002.00 0003.00 CRTMSGF MSGF(&LIB/SAMPLEMSGS) TEXT('Object text for sample + 0004.00 message file.') 0005.00 0006.00 ADDMSGD MSGID(SAM0001) MSGF(&LIB/SAMPLEMSGS) MSG('This is the + 0007.00 level 1 text.') + 0008.00 SECLVL('This is the second level text for the first + 0009.00 message.') + 0010.00 SEV(30) 0011.00 ADDMSGD MSGID(SAM0002) MSGF(&LIB/SAMPLEMSGS) MSG('This is first 0012.00 level text 2nd.') + 0013.00 SECLVL('This is second level text for sample message + 0014.00 number SAM0002. It says almost the same + 0015.00 thing as the first level message.') ****************** End of data ****************************************
. . .
. . . . . . . . . . . . . . . . . ..
(C) COPYRIGHT IBM CORP. 1981, 1996.
Figure 40 - Pseudo-Source Example Displayed in SEU
Deleting a Copy of an Object When to Delete from a Test Environment Delete a copy of an object from a test environment (Integration or Quality Assurance) after checking the copy back out to Development for further work if you do not want the copy in the test environment used for further testing. If the copy in the test environment contains serious flaws that are likely to confuse or impede testing of other objects, you should probably delete it (AFTER checking it out to Development). If you check the object out from the testing environment to make minor additional changes, and the copy in the test environment is not likely to confuse or impede testing of other objects, you can leave it behind for further testing. When you have completed your additional changes on the copy checked out to Development, promoting this new copy from Development replaces the copy left behind in the test environment. When to Delete from Development Delete a copy of an object from the Development environment when: • You decide you checked the object out in error • You want to delete the changes you made to the Development copy
UG 5-10 • Additional Actions
Aldon/CMS User’s Guide
• You are resolving a conflict and have merged the changes in the Development copy into another copy of the object • You are defining a new object to ACMS and made a mistake that cannot be fixed using option 16 (Change checked out object) on the Work with Objects by Developer panel. (Object name, source library, file, and member, and Production library assignments cannot be changed once established.)
To delete a copy of an active object 1. Locate the record for the copy of the object you wish to delete on the
Work with Objects by Developer panel. 2. In the Opt field by the copy, type 4 (Delete) and press ENTER.
The Confirm Remove (Cancel Checkout) of Objects panel displays. 3. Press ENTER to proceed with the deletion.
ACMS deletes the object and corresponding source from the selected environment. If the copy is in Development and is the last remaining copy of the object, ACMS does not delete the source.
Deleting the Production Copy of an Object The deletion of Production copies of objects is not necessary in the normal course of development work and is therefore beyond the scope of this document. Deleting production copies requires special authority. A Production copy is almost never deleted unless the object becomes obsolete and is no longer used.
Using Data Libraries for Testing A data library is a user defined library identified to ACMS which contains populated files. With ACMS, you associate one or more data libraries together as a data set. You associate a data set with a specific environment of a specific release and specify rules for how ACMS should update the data set. ACMS updates the data set with new file descriptions and descriptions of other data objects you promote into that environment. For the Development environment, ACMS updates the data set automatically whenever you create a file or other data object.
Aldon/CMS User’s Guide
Additional Actions • UG 5-11
Data sets and data libraries are most commonly used for testing changes and for managing multiple sets of production data. This section discusses issues bearing on the use of data sets and data libraries for testing. For a complete discussion of data sets and data libraries see “Data, Data Libraries, and Data Sets” on page CG 3-1 of the “Aldon/CMS General Topics Reference.”
Update DVP Data Sets After Modifying Checked Out Files Update data libraries in data sets associated with the Development environment to test modifications made to checked out files. Use commands outside of ACMS to update files in data libraries with your new changes.
Additional Task Actions Responding to User Requests To work with user requests, a user must be a registered ACMS user, and must have appropriate authority for the action they wish to perform.
To view the list of requests 1. At the Work with Objects by Developer panel, press F19 (Work with
objects). The Work with Objects by Release panel displays. 2. At the Work with Objects by Release panel, press F19 (Work with
tasks). The Work with Tasks panel displays. 3. At the Work with Tasks panel, press F16 (Work with user requests).
UG 5-12 • Additional Actions
Aldon/CMS User’s Guide
The Work with User Requests panel displays: CWRKUSRRQS Position to
Work with User Requests. . . . . . . .
Type options, press Enter. . 2=Respond to 4=Delete 5=Display Opt User Request BOBB 9 JEANNEF 1 JEANNEF 2 JEANNEF 3 JEANNEF 4
. . .
*TOP, *BOT, date
6=Add task for
Date Ste Task 01/15/97 OPN TSK001 01/16/97 OPN TSK008 01/16/97 OPN 01/16/97 OPN TSK010 01/16/97 OPN
9=Close
10=Finish.
. Description More: . Sort not handling special chars . Slow retrieval of detail records. Can we add direct access to del?. The F8 key is not working . I'm not authorized to use new fns.
Subset: Ste:*ACT (*BOT displayed: New display shows latest items (bott ... . Command ===> . F3=Exit F4=Prompt F5=Refresh F10=View 3 F11=View 2 . F12=Cancel F13=Repeat F17=Subset F21=Print F24=More keys
Figure 41 - Work with User Requests
This panel displays all unfinished user requests sorted by creation date. On initial display the panel shows most recently created requests which appear at the bottom of the list. From left to right on the initial view the Work with User Requests panel displays the following information: –
iSeries profile name of the user creating the request,
–
request number,
–
date the request was made,
–
status code for the request,
–
name of a task associated with the request, and
–
short description of the request entered by the requester.
To read a user request 1. Display the Work with User Requests panel as described in “To view
the list of requests” on page UG 5-12. 2. In the Opt field by the user request you want to read, type 2 (Respond
to) and press ENTER.
Aldon/CMS User’s Guide
Additional Actions • UG 5-13
The Respond to User Request panel displays: CRSPUSRRQS Request . : Description: User text : Task . . . : Type . . . :
Respond to User Request. JEANNEF 2 Time . . . : Friday's Request from Mark Can we add direct access to del?.. *NONE ENH Urgency . : MD State . . :
01/16/97
. 13:40. .
OPN
Text It would be very helpful if we could add direct access to the delete function from the review panel. We often find errors that could easily be fixed if there were a direct path.
. . . . . . . . . . .
Type choices, press Enter. . . Assign to task . . . . . New state . . . . . . . Command ===> F3=Exit F4=Prompt F20=Response text entry
*SAME *SAME
+ *SAME, *NONE, name *SAME, OPN, CLO, FIN
F9=Retrieve F7=Add task F22=More functions
F12=Cancel
. . . . .
Figure 42 - Respond to User Request panel
The upper portion of this panel displays the description of the request, along with codes indicating the type and urgency of the request. The Text field in the middle portion of the panel displays the text entered by the requester describing their concern. Use the fields at the bottom of the panel to assign the request to a task and change the state of the request. 3. Read the description of the request and any text entered by the
requester. Perform any required research. You may exit and return to this panel at a later time if necessary.
To enter a text response to a user request 1. Display the Respond to User Request panel as described in “To read a
user request” above. 2. Press F20 (Response text entry).
A Response Text field displays at the bottom of the panel. 3. In the Response Text field, type response text. 4. Press ENTER when finished to return to the previous panel.
To associate a user request with an existing task 1. Display the Respond to User Request panel as described in “To read a
user request” on page UG 5-13. 2. In the Assign to task field, type the name of the task or press F4
(Prompt) to select a task from a list. 3. Press ENTER to confirm your changes and return to the previous panel.
UG 5-14 • Additional Actions
Aldon/CMS User’s Guide
To associate a request with a new task 1. Display the Respond to User Request panel as described in “To read a
user request” on page UG 5-13. 2. Press F7 (Add task) to define the new task. 3. Define the task as described in the section“To add a new task” on
page UG 3-8. 4. Press ENTER upon completion of the task definition to redisplay the
Respond to User Request panel. The Task field in the upper portion of the panel displays the name of the new task to indicate that the user request is assigned to that task.
Adding Objects to a Task Add objects to a task during any of the following processes: Object Checkout Associate objects with a task on checkout using the For task field on the Check Out Objects or Check Out Objects (Emergency) panels. See “Checking Out Objects” starting on page DO 3-2 in the “Aldon/CMS Daily Operations Reference”, or the TASK keyword of the ACMSCHKOUT or ACMSCHKFRN commands discussed in “The Check Out Objects Command,” starting on page CG 7-6 and “The Check Out Foreign Object Command” starting on page CG 7-8 in the “Aldon/CMS General Topics Reference”. Object Creation Associate objects with a task on creation using the For task field on the Create Objects panel discussed in “Create With or Without Task Association” starting on page DO 4-5 in the “Aldon/CMS Daily Operations Reference” or the TASK keyword when creating objects using the ACMSCREATE command. Object Addition Associate a new object with a task during addition of the object to the release using the Task field on the Add Release Object panel or the TASK keyword when adding objects using the ACMSADDOBJ command. Object Development Associate an object in Development with a task by selecting the object with 21 (Assign tasks) on the Work with Objects by Developer panel. See “Working with Objects by Developer” starting on page DO 4-2 in the “Aldon/CMS Daily Operations Reference” for more information.
Aldon/CMS User’s Guide
Additional Actions • UG 5-15
Task Definition List objects in the task definition using the Add Task Objects panel or the OBJ keyword of the ACMSADDTSK command.
To display the Add Task Objects panel 1. Display the Define Task panel as described in “To add a new task” on
page UG 3-8. 2. Type 1 by Specify task objects and press ENTER.
To display the Add Task Objects panel, select the option Specify task objects on the Define Task panel discussed in the section “To add a new task” on page UG 3-8.
To display the Change Task Objects panel 1. At the Work with Objects by Developer panel, press F19 (Work with
objects). The Work with Objects by Release panel displays 2. Press F19 (Work with tasks).
The Work with Tasks panel displays. 3. In the Opt field by the task, type 2 (Change) and press ENTER.
The Change Task panel displays. 4. Type option 3 (Change task objects) and press ENTER.
The Change Task Objects panel displays.
Removing Objects from Tasks Remove objects from a task in any of the following ways: Using the Change Task Panel Remove objects from the task definition using the Change Task Objects panel accessed as described in“To change an existing task” on page UG 5-17. Canceling a Checkout If you associate an object with a task at checkout using the For Task field on the Work with Objects by Release panel, then later cancel the checkout using option 4 (Remove, cancel chk) on the Work with Objects by Developer panel, this also cancels the association between the object and the task.
UG 5-16 • Additional Actions
Aldon/CMS User’s Guide
Changing a Task To change an existing task 1. At the Work with Objects by Developer panel, press F19 (Work with
objects). The Work with Objects by Release panel displays 2. Press F19 (Work with tasks).
The Work with Tasks panel displays. 3. In the Opt field by the task, type 2 (Change) and press ENTER.
The Change Task panel displays. 4. Select the task definition option you wish to work with and press ENTER.
Updating the Task Status Field Use the task status field to summarize a task’s progress toward completion. ACMS ships with the following predefined task status codes: EVL — Under evaluation REJ — Rejected ACP — Accepted WIP — Work in Progress CMP — Completed Use these codes or define codes of your own. See “Customizing Task Tracking” starting on page TT 7-1 in the “Aldon/CMS Task Tracking Reference” for more information. Using the default codes you might assign all new tasks a task status of EVL. Application managers would check for tasks in their application having this status and evaluate whether or not they should be performed. For rejected tasks they would change the task status to REJ, for accepted tasks that they did not yet wish to begin work on they would assign a status of ACP.
Aldon/CMS User’s Guide
Additional Actions • UG 5-17
To update the task status field 1. At the Work with Objects by Developer panel, press F19 (Work with
objects). The Work with Objects by Release panel displays 2. Press F19 (Work with tasks).
The Work with Tasks panel displays. 3. In the Opt field by the task, type 2 (Change) and press ENTER.
The Change Task panel displays. 4. Type 1 by the Change definition option and press ENTER.
The Specify Task Definition panel displays. 5. In the Status field, type the task status, or press F4 (Prompt) to select
a code from a list. 6. Press ENTER to confirm the change and return to the previous panel.
UG 5-18 • Additional Actions
Aldon/CMS User’s Guide
Aldon/CMS User’s Guide User’s Guide UG
Chapter 6 Multiple-Release Applications
This chapter explains how ACMS works with multiple releases and explains the two release types: base and delta. The following topics are included: • “Aldon/CMS Works with Multiple Releases” on page UG 6-2 • “Aldon/CMS Features with Multiple Releases” on page UG 6-5 Online Help Text
Aldon/CMS User’s Guide
For detailed descriptions of the fields, options, and function keys displayed or available at any of the panels shown in this document, please see the online help text.
Multiple-Release Applications • UG 6-1
Aldon/CMS Works with Multiple Releases For sites with relatively simple development needs, a single release of an application may be sufficient. For sites developing or maintaining several versions of an application simultaneously or customizing third party software, ACMS supports multiple releases. ACMS fully integrates multiple-release capability throughout all product features in ways that are largely transparent to the user. The same panels perform development functions when working with a single release application or an application with many releases. This section illustrated the capabilities of ACMS. For the purpose of development work, as long as you know which version of the application you should be working in and set your user defaults for that release, the details of how ACMS works with multiple releases should not affect you.
Expanding the Definition of “Release” Old meaning of the Term Release When developing using only a single release, the term release refers unambiguously to the set of libraries created with the ACMS define release function to perform changes on those objects. This includes a single set of Integration, Quality Assurance, and Production libraries. Development libraries may also be considered part of the release but are often shared among several releases. (Integration and Quality Assurance libraries are optional at release setup.) Added Meaning of Release when Developing Multiple Releases Under multiple-release development, the term release sometimes refers to a set of objects in an application assembled according to a library list. The libraries in this list may come from one or more “releases” using the first sense of the term. A release in this sense is also referred to as a functional version of the application. Relationships between releases defined by the application manager allow ACMS to build these library lists for applications developed using multiple releases. Explanation of how releases combine to form functional versions in ACMS requires introduction of three additional concepts: Base release, Delta release, and parent release.
UG 6-2 • Multiple-Release Applications
Aldon/CMS User’s Guide
Two Release Types: Base and Delta There are two types of releases in ACMS: Base releases and Delta releases, illustrated below. A Base release contains a complete set of application objects. A Delta release contains objects changed since the prior release and any newly added objects.
Base and Delta Releases Base Release: BASE 1 Object A Object B Object C Object D Object E Object F Object G
Delta Release: DELTA 1A Modified Object, A' Modified Object, D' New Object, H Figure 43 - Base and Delta Releases
Aldon/CMS User’s Guide
Multiple-Release Applications • UG 6-3
Relationships Between Releases Parent Release Each Delta release has exactly one parent release. A Base release has no parent release. Release Trees Related releases may be visualized as a tree of Delta releases descending from a Base release. The samples illustrate the range of valid release relationships under ACMS.
Sample Valid Release Trees Base 1
Delta 1A
Base 2
Delta 2A
Base 3
Delta 3A
Delta 3B
Delta 2B
Each rectangle represents a release. Arrows extend from each delta release to its parent. An application may have several base releases. Figure 44 - Sample Valid Release Trees
Forming a Functional Version of the Application The set of releases traversed by starting at any Delta release and tracing back to the Base form a functional version of the application. Modified objects closer to the starting Delta replace older copies of the objects closer to the Base. Placement of libraries in the library list in accordance with their order in the tree structure provides the correct copy of each application object for compilation, and for running the application. Each release has its own environment libraries. Development of multiple related releases can take place at the same time.
UG 6-4 • Multiple-Release Applications
Aldon/CMS User’s Guide
Aldon/CMS Features with Multiple Releases Multi-Release Tasks Tasks may be associated with objects from more than one release. The releases need not be releases of the same application. For details “Multiple-Release Tasks” starting on page TT 6-1 in the "Aldon/CMS Task Tracking Reference". What Happens During Checkout and Emergency Checkout The application manager defines the relationships between releases of an application during release setup. ACMS uses these relationships when performing checkouts to locate the correct copy of the desired object in the correct related release if it is not already present in the release in which you wish to perform the modifications. The application manager specifies the release in which to perform a given set of modifications. After development of a release is complete, the manager can use release-level options to lock a release for further checkouts. What Happens During Compiling ACMS builds correct object creation library lists based on the release structure defined by the application manager. What Happens During Standard Promote Standard promotion moves objects forward toward and into the Production environment of the release for which the object was checked out. Standard promote never moves objects between releases. Promote to Parent A “promote to parent” function is available for promoting objects from the Production environment of a child release to the Production environment of the child’s parent release. You can also create a distribution set as part of a promote to parent job. For more information see “Promoting to a Parent Release,” starting on page DO 3-16. Object Dependencies ACMS tracks object dependencies across multiple related releases.
Aldon/CMS User’s Guide
Multiple-Release Applications • UG 6-5
Conflicts and Multiple-Release Development Aldon/CMS tracks conflicts between objects based on defined relationships between releases. ACMS provides notification of conflicts and prevents potentially destructive object movements. Promotion of objects with release conflicts as far as some designated environment may be permitted depending on the “Allow promotions with conflicts to” release option for the release. For more information see “Allow promotes with conflicts to” starting on page SA 2-12 in the "Aldon/CMS Setup and Administration Reference"and consult your ACMS administrator.
UG 6-6 • Multiple-Release Applications
Aldon/CMS User’s Guide
Aldon/CMS User’s Guide User’s Guide UG
Glossary
About this Glossary This glossary defines terms in the “User’s Guide” unique to ACMS. For a complete glossary of all ACMS terms, see the “Master Glossary” starting on page AO 3-1 in the “Aldon/CMS Documentation Guide”.
Glossary Terms acknowledgement condition condition created when an object checked out using the emergency checkout function is promoted back to Production. acknowledgement conditions notify managers that normal development procedures have not been followed for a particular object. A user must have ACMS “Clear acknowledgement condition” authority to remove an acknowledgement condition.
active environments environments in which objects are changed or tested. Development, Integration, and Quality Assurance are the active environments. Production is not an active environment. See also “environments.”
Aldon/CMS User’s Guide
• UG Gloss-1
ANALYZER a COBOL and RPG test coverage monitor available from Aldon. Analyzer identifies how well you have tested a program before you move it into Production by telling you the percentage of code your tests have executed; the percentage of changed code your tests have executed; which lines of code your tests have executed; and which lines of code were missed.
application a collection of objects designed to achieve a specific goal and the source code used to create those objects. An application may exist as one or more releases, with each release containing a complete or partial set of the objects required to achieve the application's goal.
application group set of related applications. Each application group may have one application designated as a shared application. The shared application can contain common programs, files, and other objects used by applications in the application group.
archive library optional ACMS environment that receives copies of old objects as new copies are moved into the Production environment. A single archive library receives objects from all releases of one application.
authorities approximately two dozen individual flags set for each user to control their access to the various functions of ACMS. Specify authorities for each user at the global level. Specify additional sets of authorities at the application and/or release level to give a user different authorities within a given application or release.
checkout a user initiated copying of source for an object from Integration, Quality Assurance, or Production to Development for the purpose of modification. The object itself is copied if the object is not source based.
UG Gloss-2 •
Aldon/CMS User’s Guide
condition a flag in the ACMS object database on a particular copy of an object. Conditions provide information, and in some cases also restrict actions on the object until the condition is removed. Conditions are of three types: request conditions, conflict conditions, and acknowledgement conditions.
conflict condition condition created when an object already in Development is checked out again as allowed by the multiple checkout option, when an active object is checked out as part of an emergency checkout operation, or when a copy of an object resides in a delta release and the object is checked out in an ancestor release or another “notifying release”. A conflict condition prevents promotion of the object with which it is associated until it is removed.
data conversion program a program supplied by the user and executed during a promote, create, or object distribution installation process to move existing data into a new version of a physical file.
data library a User defined library which contains populated data objects such as files. A data library is a member of one data set. The data set definition controls updating of the data library with new data object descriptions promoted into the environment with which the data set is associated.
data set a set of one or more data libraries associated with a specific release and environment of an application. You assign attributes governing object ownership and authorities, error monitoring, and automatic addition of new data objects to the data set as a whole rather than to individual data libraries. You also request update of the date set as a whole rather than as individual data libraries.
dependent object if an object, “A,” is required at create time or execution time by another object, “B,” then “B” is a dependent object of “A”.
Aldon/CMS User’s Guide
• UG Gloss-3
developer an ACMS construct which associates a name with descriptive text, a default owner of objects, and libraries to contain source and objects checked out for modification. A user checks objects out to a developer to move object source to the associated library for modification. ACMS keeps track of the developer to which each object is checked out and retrieves the modified source from the corresponding library to complete promotion of the object. Developer names can correspond to individuals or work groups. Developer names may correspond to an iSeries user profile but this is not required.
developer library A developer library is a library specified in an ACMS developer definition to receive checkouts for that developer, or into which objects checked out to that developer are compiled. A local developer definition may specify separate libraries for source and objects. A remote developer definition may specify separate libraries for source and objects on the remote system as well as a local object library for testing compiled objects with objects in other environments of the release.
Development The environment comprised of the group of libraries named in developer definitions to contain objects checked out for modification.
distribution the act of sending objects from applications controlled by ACMS to other locations for installation and use. Distribution may also be used “locally” to copy objects to libraries outside of ACMS on the same system.
distribution set a complete description of an object distribution project. A distribution set associates a list of tasks or individual objects to distribute with an application profile and one or more receiving location profiles. ACMS uses the information specified in the distribution set to locate the objects selected for distribution and perform the steps necessary to deliver the objects to the desired locations in the form specified.
UG Gloss-4 •
Aldon/CMS User’s Guide
environment a function specific library or set of libraries which form the basic structure of ACMS. Libraries of an environment have relationships pre-defined by ACMS to the libraries of other environments. The predefined relationships orchestrate movement of objects into and out of the environment libraries. The four environments definable under ACMS are Development, Integration, Quality Assurance, and Production. Except for Development, the libraries which constitute a given environment for a release are not shared with other releases.
group see “application group.”
installing live an expedited process through which ACMS distributes a copy of each object in a promote job to libraries outside ACMS controlled environments for testing or production use. The libraries outside of ACMS contain a separate “live” version of the application under development.
Integration optional ACMS environment used for testing. Integration can be used by developers for testing their changes together before promotion to Quality Assurance.
library group a named portion of a Production library. At release setup, you divide each Production library into one or more library groups. Library groups let you store different kinds of objects in the same library, and then update them into different libraries of a data set or distribute them into different libraries of a distribution target.
Aldon/CMS User’s Guide
• UG Gloss-5
non-resident object an object which does not exist in a given environment but which may be accessed via the object creation library list for that environment. As long as the object is non-resident, objects dependent on it must use the next copy of the object located using the library list. Testing of an object in an environment may require creating resident copies of non-resident objects using the create non-resident function. For example, testing a changed file requires recompiling the programs that use that file to avoid level checks. To maintain version control, ACMS requires creation of these programs into the environment containing the changed file. This changes the status of such programs in the testing environment from non-resident to resident.
Production group of one or more libraries for a given release defined to ACMS that receives objects after they have been modified and tested.
promote user initiated movement of an object toward the Production Environment from Development, Integration, or Quality Assurance.
pseudo-source a member created by the user containing CL commands or SQL statements which, when executed, create an application object. ACMS moves the member with the object through the various environments as if it were standard source and uses it to recreate the object as needed or when requested. Pseudo-source is available for checkout which greatly simplifies modification of the object.
Quality Assurance an optional ACMS environment used for final testing by Quality Assurance personnel or for user acceptance testing.
release Release refers to either a set of objects, or the set of libraries created to perform changes on those objects. In the first sense, a release is the subset of application objects assembled according to a library list. ACMS forms the library list by starting at the named release and tracing back through the ancestry tree until a base release is reached.
UG Gloss-6 •
Aldon/CMS User’s Guide
release libraries the set of libraries which contain all copies of all objects for a release. Use existing libraries as Production libraries for a release or have ACMS create new libraries for Production. ACMS always creates the libraries used for Integration and Quality Assurance environments. Integration, Quality Assurance, and Production libraries comprise the release libraries for a release. Development libraries are not created by ACMS and are usually not closely associated with individual releases.
request condition condition created when a user requests checkout or promotion of an object.
resident object an object placed in an ACMS environment by a direct user action such as checkout, promotion, or non-resident creation is resident in that environment. Examples: An object checked out into Development is resident in Development. An object promoted into QA or Integration is resident in QA or Integration. A non-resident object created into QA or Integration is then resident in QA or Integration.
subsetting selection of items for display using multiple criteria. Subsetting in ACMS is usually performed on a panel accessed by function key F17. On return to the original display, only items meeting all subsetting criteria appear.
task a group of objects identified for modification to achieve a defined goal with associated descriptive and tracking information. Use tasks as an aid in manipulating and managing objects. Fields are available for notes on the task, keywords, and a task budget.
test environment Integration or Quality Assurance environments used for testing changed software.
Aldon/CMS User’s Guide
• UG Gloss-7
user (ACMS user) an iSeries user profile associated with descriptive text and a set of authority values. The authority values govern access to ACMS functions by persons signing on under that user profile. A user must be defined to ACMS to enter the panel interface or to use ACMS commands or PDM options.
Verify an ACMS function which checks objects in release libraries against information about those object in the ACMS database and against ownerships and authorities specified by ACMS or the user. Discrepancies are recorded in a report.
UG Gloss-8 •
Aldon/CMS User’s Guide
Aldon/CMS User’s Guide Index Page Identifiers in Aldon iSeries Documents Page identifiers consist of a two character document abbreviation followed by a chapter number or appendix letter, and a page number within that chapter or appendix. Example: UG 1-5 indicates the fifth page of chapter 1 in the “Aldon/CMS User’s Guide.” Using This Single-Document Index 1. Locate the desired topic in the index. 2.
Click on a page reference to jump to the indicated page.
3.
From a referenced page, you can right-click, then select Go Back from the pop-up menu one or more times to return to this index.
For assistance in using Acrobat, see the chapter “Using CD-ROM Documents Online” in the Installation Guide.
Symbols * (asterisk) following panel option text, designates ’combined job’ options UG 2-12 *RCDS objects UG 5-2 + (plus sign) indicating promptable field UG 2-4
A Acknowledgement conditions A A (ANALYZER cleared) UG 2-51 defined UG Gloss-1 ACMSLIB product library contains STRACMS command UG 2-2 ACMSUSRRQS command (submit user request) UG 3-18 Act upon Dependent Objects - Selection panel UG 2-39
Aldon/CMS User’s Guide
Active environments creating objects in UG 2-14 defined UG Gloss-1 introduced UG 1-4 Add Release Object panel UG 5-4 Add Task Objects panel UG 3-11 Adding see also Creating, Defining, and Identifying objects UG 5-2 objects to a task UG 5-15 tasks UG 3-8 Aldon Response Manager (ARM) interface to Aldon/CMS (ACMS) UG 3-12 Aldon/CMS (ACMS) documentation. see Documentation goals of UG 1-2 main menu, displaying UG 2-2 object database introduced UG 1-5 product description UG 1-2 starting UG 2-2 terms and concepts, basic UG 1-3 Aldon/CMS Main Menu UG 2-2 ANALYZER defined UG Gloss-2 ANALYZER-Aldon/CMS interface automatic clean-up after completion of testing UG 2-51 changed code defined UG 2-51 checking the current level of testing UG 2-53 conflict and acknowledgement conditions used by UG 2-50, UG 2-51 distributing instrumented source from QA UG 3-6 how it works UG 2-50 to UG 2-51 instrumenting using UG 2-50 overview UG 2-49 passing the testing standards UG 2-51 procedures for using UG 2-53 programing languages supported by UG 2-49 requirements UG 2-49 setting testing standards with UG 2-50 testing standards, how enforced UG 2-50 ANLZSRC file to contain OPM source instrumented with ANALYZER UG 2-50
• UG Index-1
ANLZSRCLE file to contain ILE source instrumented with ANALYZER UG 2-50 Application groups defined UG 1-3, UG Gloss-2 Applications defined UG 1-3, UG Gloss-2 multiple-release introduction to structure of UG 6-2 Archiving UG 3-3, UG 3-4 defined (library/environment/process) UG Gloss-2 emergency checkout and UG 3-5 restoring objects UG 3-4 Audit trail clarified by non-resident object creation UG 2-12 produced automatically by ACMS UG 1-2 Authorities, Aldon/CMS defined UG Gloss-2
B Base releases defined and illustrated UG 6-3, UG 6-4 in definition of release UG Gloss-6 introduced UG 6-2 mentioned UG 1-4 required in forming functional version of an application UG 6-4
C C A (conflict ANALYZER condition) UG 2-50, UG 2-51 CDTACNVSPC UG 2-20 CEDTNTE UG 3-10 Change Checked Out Object panel UG 5-9 Changed code (ANALYZER-Aldon/CMS interface term) defined UG 2-51 Changing see also Editing tasks UG 3-13, UG 5-17 Check out from Production UG 2-8 Check Out Objects panel UG 2-8 Checking out from Integration UG 2-9 from Quality Assurance UG 2-9 Checkout defined UG 1-6, UG Gloss-2 discussed UG 2-5 introduced UG 1-6 selects the correct copy of the object UG 2-6 Child releases promoting from to parent release UG 6-5 CL based objects, creation of supported by ACMS UG 1-5
UG Index-2 •
COBOL programs creation of supported by ACMS UG 1-5 testing of supported by ANALYZER-Aldon/CMS interface UG 2-49 Combined job processing introduced UG 2-12 Command line, access provided to UG 4-4 Commands use of ’user defaults’ (personal defaults) by UG 2-3 ACMSUSRRQS (submit user request) UG 3-18 Conditions conflict, defined UG Gloss-3 defined UG Gloss-3 request, defined UG Gloss-7 Conflict condition records C A (conflict ANALYZER) UG 2-50, UG 2-51 clearing UG 2-46 defined UG 2-42, UG Gloss-3 discussed UG 2-42 emergency checkout conflicts (C E) UG 2-41, UG 2-44 introduced UG 2-41 multiple checkout conflicts (C M) UG 2-44, UG 6-6 resolving conflicts indicated by UG 2-45 working with for all objects UG 2-44 working with for single object UG 2-43 Conflicts checkout, identified by conflict condition records UG 2-45 CONNECT:Direct TCP/IP distribution interface mentioned UG 3-6 Constraints SQL table, self-referential UG 5-6 Controlling access to source authorities UG Gloss-2 checkout and UG 2-5 Copying objects and source for modification. see Checkout objects to libraries outside of ACMS. see Distributing CPYF options data conversion, specifying for during promote UG 2-20 Create Objects panel UG 2-14 Creating objects. see Creating objects Creating objects automatic collection and reuse of parameters for UG 2-13 command definitions for defining for custom or vendor commands, ACMS capability UG 2-11 for IBM commands, predefined to ACMS UG 2-11
Aldon/CMS User’s Guide
Creating objects (continued) commands for viewing command selected for an object by ACMS UG 2-16 library list built automatically for UG 2-12 overriding previous parameters for UG 2-16 overview UG 2-11
D Data conversion retaining copy of previous version during UG 2-21 specifying during promote UG 2-20 specifying program for when promoting UG 2-21 Data conversion programs defined UG Gloss-3 Data libraries defined UG 5-11, UG Gloss-3 updated automatically UG 5-11 verifying UG 3-20 verifying the contents of UG 3-20 Data objects identifying when adding objects UG 5-3 Data sets defined UG Gloss-3 updating for Development UG 5-12 verifying contents of UG 3-20 DDL, generating from SQL object (ACMS function) UG 5-7 Defaults operation defaults, setting UG 4-6 setting to control initial cursor positioning on More Functions panel UG 4-6 setting to control option 19=Alt edit response when *FILE DSPF purpose is ambiguous UG 4-6 setting to control selection of dependent objects for create on promote UG 4-6 setting to control selection of requisite objects for create in Development UG 4-6 Define Task panel UG 3-8 Deleting objects from Development UG 5-10 objects from Production UG 5-11 objects from test environments UG 5-10 Delta releases defined and illustrated UG 6-3, UG 6-4 introduced UG 6-2 Demonstration access to ACMS sign on for UG 2-2
Aldon/CMS User’s Guide
Dependent objects See also Requisite objects acquiring data regarding UG 2-34 during object creation UG 2-13 acting on creating during promotion UG 2-19, UG 2-37 creating during promotion, setting default governing UG 4-7 for reference objects not defined to ACMS UG 2-39 including in a checkout UG 2-37 leaving resident on promote UG 2-22 outside of checkout and promote functions UG 2-38 recursively UG 2-40 defined UG Gloss-3 discussed UG 2-32 for requisites not defined to ACMS UG 2-39 introduced UG 2-13 Developer libraries defined UG Gloss-4 Developers defined UG Gloss-4 Development (Aldon/CMS environments) defined UG Gloss-4 Development log confirming promotion with UG 2-22 defined UG 3-2 discussed UG 3-2 optional comment entry for UG 2-9, UG 2-14, UG 2-22, UG 2-47, UG 3-5 viewing an object's history in UG 3-2 Development tools activating from within Aldon/CMS UG 2-10 changing default selections UG 4-5 setting display vs. menu default for Screen Design Aid UG 4-6 Display Development Log panel UG 3-2 Display Requisite Objects panel UG 2-38 Distributing see also Distribution and Installing live locally UG 3-6 on promote to Integration, Quality Assurance, or Production UG 3-6 to remote locations UG 3-6 using CONNECT:Direct. see CONNECT:Direct TCP/IP communications Distribution see also Distributing and Installing live defined UG 3-6, UG Gloss-4 introduced UG 1-6, UG 3-6 object version numbers used in UG 3-3 tape as medium for UG 3-6
• UG Index-3
Distribution (continued) verification of targets used in UG 3-3 Distribution sets defined UG Gloss-4 introduced UG 3-6 Documentation goal of User’s Guide UG 1-2 using context sensitive help text UG 4-2
E Edit Task Notes panel UG 3-10 Edit User Development Tools panel UG 4-5 Editing see also Changing Editing objects UG 2-10 Editor selecting with user defaults UG 2-3, UG 4-5 Emergency checkouts conflict records and UG 2-41 defined UG 2-41 discussed UG 2-41 how indicated UG 2-42 introduced UG 2-6 object movement during, figure UG 2-41 performing UG 2-42 promotion after UG 2-42 promotion subsequent to, figure UG 2-41 Enter User Request panel UG 3-17 Environments defined UG 1-3, UG Gloss-5 design benefits of model UG 1-4 introduced UG 1-4 relationship between various, figure UG 1-4 up to four supported by ACMS UG 1-4 Envs field on Work with Objects by Release panel UG 2-8 Examples pseudo-source UG 5-10 EXT (extended attribute for SQL externally defined functions and procedures) UG 5-3 External reference objects acting on objects dependent on UG 2-39
F Flow charts install live object movement UG 2-24
G Generate DDL from SQL object (ACMS function) UG 5-7 Generate SQL Data Definition Language panel UG 5-8 Glossary partial, for User's Guide UG Gloss-1
UG Index-4 •
H Harmonizer defined UG 2-43 introduced UG 2-11 mentioned UG 2-42 merging source changes with UG 2-43 resolving conflicts using UG 2-45 Help text discussed UG 4-2 field level UG 4-3 hypertext links, using UG 4-3 panel (global) level UG 4-3 retrieving UG 4-2 search index, using UG 4-3 History of a non-source object provided by archived pseudo-source UG 2-11 of an object, viewing UG 3-2 How to act upon dependent objects using a variety of options UG 2-38 add an object UG 5-3 an object to a task UG 3-11, UG 5-15 a task UG 3-8 associate a user request with an existing task UG 5-14 a user request with a new task UG 5-15 change development tool defaults UG 4-5 a task UG 5-17 check on a user request from within Aldon/CMS UG 3-18, UG 3-19 checkout dependent objects UG 2-37 objects by task UG 3-13 from Production for emergency fix UG 2-42 clear a conflict condition record UG 2-46 create dependent objects during promotion UG 2-37 objects in an active environment UG 2-14 objects in Production UG 2-15 define a user options file UG 4-6 delete an active copy of an object UG 5-11 display object requisites UG 2-38 distribute objects on promote to QA UG 3-6 edit from Work with Objects by Release panel UG 2-10 using PDM UG 2-10 fulfill a promote request UG 2-48
Aldon/CMS User’s Guide
How to (continued) identify objects checked out with emergency function UG 2-42 objects with pending promote requests UG 2-48 instrument a program for testing with ANALYZER-Aldon/CMS interface UG 2-53 override previous create parameters for an object UG 2-16 promote objects UG 2-18 after emergency checkout UG 2-42 by task UG 3-14 read a task request UG 5-13 record task hours alternate method UG 3-15 quick, multi-task method UG 3-15 remove an object from a task UG 5-16 request a promotion UG 2-47 request a task from within ACMS UG 3-17 resolve a conflict using Harmonizer UG 2-45 without Harmonizer UG 2-45 respond to a user request UG 5-12 with a text message UG 5-14 restore objects from archive to normal development UG 3-4 using emergency checkout UG 3-5 review task hours summed by date UG 3-15 scan for object dependency data by manual request UG 2-35 set operation defaults UG 4-6 specify a default application and release UG 2-4 a default task UG 4-4 object dependencies manually UG 2-36 yourself as default developer UG 2-5 subset lists to display desired items UG 2-7, UG 4-9 verify a data library UG 3-20 a release or distributed objects UG 3-19 view the create command selected for an object by ACMS UG 2-16 an object’s history UG 3-2 submitted user requests UG 5-12 work with archived objects UG 3-4 conflict records for a single object UG 2-43 conflict records for all objects UG 2-44 tasks UG 3-13 user preferences UG 2-3, UG 4-4 user requests UG 5-12
Aldon/CMS User’s Guide
I IBM create commands predefined to ACMS UG 2-11 ILE programs extended attribute to identify UG 5-2 handled by ACMS UG 1-5 testing of (COBOL and RPG) supported by ANALYZER-Aldon/CMS interface UG 2-49 Install Live on Promote panel UG 2-27 Install Live panel UG 2-31 Install Live upon Promote panel UG 2-28 Install live. see Installing live Installing live “from” release environment UG 2-26 see also Distributing and Distribution concepts UG 2-26 defined UG Gloss-5 design goal of UG 2-25 diagram of object flow UG 2-24 eligible objects UG 2-26 introduced UG 2-22 object creation library list and UG 2-24 on promote UG 2-27 to UG 2-29 outside of promote (from “Work with...” panels) UG 2-29 to UG 2-32 overview UG 2-24 to UG 2-25 Instrument when promoting to, ANALYZER-ACMS interface field UG 2-52 Instrumenting for testing with ANALYZER-Aldon/CMS interface UG 2-50 Integration (ACMS environments) checking out from UG 2-9 defined UG Gloss-5
L Leave behind. See Leave resident Leave resident option on Specify Promote Options panel UG 2-22 Level checks, automatic prevention of by ACMS UG 2-12 Library groups defined UG Gloss-5 introduced UG 1-7 Library lists managed by ACMS for object creation UG 2-12 Log, development see Development log
M Merging source changes with Harmonizer UG 2-43 More Functions panel UG 2-3 Multiple-release applications introduction to structure of UG 6-2
• UG Index-5
Multiple-release tasks introduced UG 6-5
N Non-resident objects defined UG Gloss-6 introduced UG 2-12 Non-source objects introduced UG 1-5
O Object dependency data specifying manually UG 2-36 Object distribution. see Distributing; Distribution Object movement by checkout UG 1-6 by emergency checkout UG 2-41 by non-resident object creation UG 2-12 by promotion UG 1-6 by restoring from archive UG 3-4 environments and, basic, figure UG 1-4 Objects ACMS definition of UG 1-4 adding UG 5-2 deleting UG 5-10 editing UG 2-10 matched with source during release creation UG 1-5 types handled by ACMS UG 1-5 version numbers for UG 3-3 Operation defaults setting UG 4-6
P Panels Act upon Dependent Objects - Selection UG 2-39 Add Release Object UG 5-4 Add Task Objects UG 3-11 Aldon/CMS Main Menu UG 2-2 Change Checked Out Object UG 5-9 Checkout Objects UG 2-8 Create Objects UG 2-14 Define Task UG 3-8 Display Development Log UG 3-2 Display Requisite Objects UG 2-38 Edit Task Notes UG 3-10 Edit User Development Tools UG 4-5 Enter User Request UG 3-17 Generate SQL Data Definition Language UG 5-8 Install Live UG 2-31 Install Live on Promote UG 2-27 Install Live upon Promote UG 2-28 More Functions UG 2-3 Promote Objects UG 2-18
UG Index-6 •
Panels (continued) Request Promote UG 2-47 Respond to User Request UG 5-14 Select Environments for Install Live UG 2-30 Select Releases for Install Live UG 2-30 Set User Operation Defaults UG 4-7 Set User-Defined Option File UG 4-6 Specify Data Conversion UG 2-20 Specify Promote Options UG 2-21 Specify Task Definition UG 3-9, UG 3-10 Subset Objects by Developer List UG 4-9 User-Defined Requisite Objects UG 2-36 Work with Archive Objects UG 3-4 Work with Objects by Developer UG 2-6 Work with Objects by Release UG 1-6, UG 2-7 Work with Requests and Conditions UG 2-44, UG 2-48 Work with Tasks UG 3-13 Work with User Requests UG 5-13 Parent releases defined and illustrated UG 6-4 introduced UG 6-2 promoting to, introduced UG 6-5 PDM, editing objects with from ACMS UG 2-10 PDM-style user options setting up file for UG 4-6 Percentage of changed code, ANALYZER-Aldon/CMS interface field UG 2-52 Percentage of total code, ANALYZER-Aldon/CMS interface field UG 2-52 Product libraries ACMSLIB UG 2-2 Production (ACMS environments) creating objects in UG 2-15 defined UG Gloss-6 distributing on promote to UG 3-6 Project See Task Project tracking system See Task tracking system Promote Objects panel UG 2-18 Promote requests creating UG 2-47 discussed UG 2-47 fulfilling UG 2-48 identifying pending UG 2-48 introduced UG 2-47 Promoting confirming successful completion of UG 2-22 creating dependent objects during setting default governing UG 4-7 data conversion, specifying when UG 2-20 defined UG 1-6, UG Gloss-6 discussed UG 2-17 distributing as part of. see Distributing, on promote how to UG 2-18
Aldon/CMS User’s Guide
Promoting (continued) installing live during UG 2-27 to UG 2-29 introduced UG 1-6 leaving objects resident UG 2-22 making mandatory UG 2-47 new object sometimes requires one manual creation before UG 2-18 to parent introduced UG 6-5 Prompting input fields marked with “+” sign UG 2-4, UG 4-3 Pseudo-source benefits of UG 2-11 defined UG Gloss-6 discussed UG 5-3 example UG 5-10 example, figure UG 5-10 introduced UG 1-5 working with UG 5-6
Q Quality Assurance (ACMS environments) checking out from UG 2-9 defined UG Gloss-6 distributing instrumented source from UG 3-6 distribution on promote to. see Quality Assurance, distributing from
Releases, multiple base and delta releases defined UG 6-3 base and delta releases defined, figure UG 6-3 checkout and UG 6-5 conflicts between monitored to coordinate development UG 6-6 development functions and UG 6-5 parent release defined UG 6-4 promote and UG 6-5 valid release relationships, examples, figure UG 6-4 working with UG 6-2 Removing objects from a task UG 5-16 Request conditions defined UG Gloss-7 Request Promote panel UG 2-47 Requisite objects displaying UG 2-38 Resident objects defined UG Gloss-7 Respond to User Request panel UG 5-14 Retn Data field UG 2-21 RPG programs creation of supported by ACMS UG 1-5 testing of supported by ANALYZER-Aldon/CMS interface UG 2-49
S R Record task hours alternate method UG 3-15 quick, multi-task method UG 3-15 Release libraries defined UG Gloss-7 Release types base introduced UG 6-2 mentioned UG 1-4 base and delta defined and illustrated UG 6-3 delta introduced UG 6-2 parent introduced UG 6-2 relationships between defined UG 6-4 Releases defined UG 1-3, UG Gloss-6 definition expanded for multiple-release development UG 6-2 objects matched with source during creation of UG 1-5 verifying objects in UG 3-19
Aldon/CMS User’s Guide
Scanning for object dependency data UG 2-34 Screen Design Aid development tool setting display vs. menu default for UG 4-6 Search paths other field UG 2-33 Select Environments for Install Live panel UG 2-30 Select Releases for Install Live panel UG 2-30 Set User Operation Defaults panel UG 4-7 Set User-Defined Option File panel UG 4-6 Signing on for demonstration access UG 2-2 Single-copy create specifications creating UG 2-16 SNADS (System Network Architecture Distribution System) object distribution and UG 3-6 Source code controlling access to UG 2-5 editing UG 2-10 matched with objects during release creation UG 1-5 Specify Data Conversion panel UG 2-20 Specify Promote Options panel UG 2-21 Specify Task Definition panel UG 3-9
• UG Index-7
SQL associating pseudo-source with UG 5-7 creating pseudo-source for UG 5-7 EXT (extended attribute for externally defined functions and stored procedures) UG 5-3 objects handled by ACMS UG 1-5 pseudo-source associating with UG 5-7 creating for UG 5-7 for table with self-referential constraint UG 5-6 generating statements from object as precursor to UG 5-7 with multiple library references UG 5-6 SRC (extended attribute for sourced functions) UG 5-3 SQL (extended attribute for SQL objects) UG 5-2 SQLC (member type for SQL pseudo-source) UG 5-6 SRC (extended attribute for sourced SQL functions) UG 5-3 Starting ACMS UG 2-2 ACMS directly UG 2-2 STRACMS command using to start Aldon/CMS UG 2-2 Structure of multiple-release applications introduced UG 6-2 Subset Objects by Developer List panel UG 4-9 Subsetting UG 4-9 defined UG Gloss-7
T Task tracking system see also Tasks; User requests introduced UG 3-7 Tasks see also Task tracking system; User requests adding UG 3-8 adding objects to UG 5-15 at checkout UG 5-15 changing existing UG 5-17 checking out objects by UG 3-13 default task, setting UG 4-4 defined UG Gloss-7 hours for, recording alternate method of UG 3-15 quick, multi-task method of UG 3-15 hours for, reviewing, summed by date UG 3-15 multiple-release introduced UG 6-5 notes for entering into UG 3-10 promoting objects by UG 3-14 removing objects from UG 5-16 status of, updating UG 5-17
UG Index-8 •
TCP/IP distribution via CONNECT:Direct mentioned UG 3-6 Test environments defined UG Gloss-7 Testing COBOL and RPG enhanced by ANALYZER-Aldon/CMS interface UG 2-49 standards, setting with ANALYZER-Aldon/CMS interface UG 2-50 Third party vendor packages handled by ACMS UG 1-5 Tips controlling default for dependent object creation on promote UG 2-19 hot key access from Work with Objects by Developer to Work with Objects by Release panel UG 2-7 using Work with Objects by Developer panel as home base UG 2-6
U User defaults (personal defaults) advanced, setting UG 4-4 defined UG 2-3 editor(s), setting default UG 2-3 focusing displays on objects of interest with UG 2-3 introduced UG 2-3 release, application, and group, setting defaults for UG 2-3 setting default editor(s) UG 4-5 specifying a PDM-style user options file UG 2-3, UG 4-6 task, setting default UG 4-4 User interface command line UG 4-4 help text UG 4-2 input fields UG 4-3 options available UG 4-2 prompting UG 4-3 scrolling UG 4-3 selecting items UG 4-3 WRKSBMJOB access to UG 4-4 WRKSPLF access to UG 4-4 User requests see also Task tracking system; Tasks associating with a task UG 5-14 checking on from ACMS UG 3-18, UG 3-19 creating from ACMS UG 3-17 creating from iSeries outside of ACMS UG 3-18 defined UG 3-16 discussed UG 3-16 reading UG 5-13 responding to UG 5-12 viewing list of UG 5-12
Aldon/CMS User’s Guide
User-Defined Requisite Objects panel UG 2-36 Users (Aldon/CMS) defined UG Gloss-8
V Verifying data set libraries individually UG 3-20 data sets UG 3-20 defined UG Gloss-8 discussed UG 3-19 distributed objects UG 3-19 releases UG 3-19 Version numbers for objects basic information UG 3-3
W Work with Archive Objects panel UG 3-4 Work with Objects by Developer panel UG 2-6 editing source from UG 2-10 introduced UG 2-6 using as home base for development UG 2-6 Work with Objects by Release panel UG 1-6, UG 2-7 direct access to from Work with Objects by Developer UG 2-7 editing source from UG 2-10 Envs field on provides snapshot of each object UG 2-8 introduced UG 1-6 Work with Requests and Conditions panel UG 2-44, UG 2-48 CND column codes for checkout conflicts UG 2-44 Work with Tasks panel UG 3-13 Work with User Requests panel UG 5-13
Aldon/CMS User’s Guide
• UG Index-9
UG Index-10 •
Aldon/CMS User’s Guide
