Aldon.pdf

Aldon LM(i) Daily Operations Reference Daily Operations Reference DOAldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference Version 7.5 Copyright © 1994-2007 by Aldon. 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. Aldon 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 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 Lifecycle Manager, Aldon Deployment Manager, Aldon Community Manager, Aldon LM, Aldon LM(e), Aldon LM(i), Aldon DM, Aldon CM, Aldon LM(i) Requester Module, Aldon Workbench, Analyzer, Harmonizer Plus, and S/Compare-Harmonizer are trademarks of Aldon. 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, System i, 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 6001 Shellmound Avenue #600 Emeryville, CA 94608-1901 Phone: +1-510-839-3535 (US), 44-1932-355711 (UK) Fax: +1-413-751-4273 Email: [email protected] World Wide Web: www.aldon.com Updated: August 8, 2007 Product version: 7.5 Aldon LM(i) Daily Operations Reference Daily Operations DO Daily Operations Reference Contents Preface Chapter 1 Overview of Aldon Lifecycle Manager (System i Edition) DO vii DO 1-1 Introduction ........................................................................................................DO 1-1 Applications and Releases ..................................................................................DO 1-2 Aldon LM(i) Release Environments ..................................................................DO 1-3 Development Environment ...................................................................DO 1-3 Integration Environment .......................................................................DO 1-4 Quality Assurance .................................................................................DO 1-4 Production .............................................................................................DO 1-4 Archive ..................................................................................................DO 1-4 Objects ................................................................................................................DO 1-5 Types of Objects ....................................................................................DO 1-5 Identifying Objects ................................................................................DO 1-5 Object Movement ...............................................................................................DO 1-6 Access to Object Movement .................................................................DO 1-6 Checkout ................................................................................................DO 1-7 Promoting ..............................................................................................DO 1-7 Conflict Records ....................................................................................DO 1-7 Object Deployment ...............................................................................DO 1-8 Emergency Checkout and Promotion ....................................................DO 1-8 Archiving ............................................................................................................DO 1-8 Task Tracking System ........................................................................................DO 1-9 Accessing Aldon Community Manager .............................................................DO 1-9 Aldon LM(i) Works with Multiple Releases ......................................................DO 1-9 Object Version Numbers ..................................................................................DO 1-11 Object Referencing ...........................................................................................DO 1-12 Object Creation .................................................................................................DO 1-12 Object Ownership and Authorities ...................................................................DO 1-13 Verify ................................................................................................................DO 1-14 Aldon LM(i) Users ...........................................................................................DO 1-14 User Interfaces ..................................................................................................DO 1-16 Aldon LM(i) Daily Operations Reference Contents • DO i Chapter 2 Using Aldon Lifecycle Manager (System i Edition) DO 2-1 Introduction to Using Aldon LM(i) ................................................................... DO 2-1 Starting Aldon LM(i) ......................................................................................... DO 2-1 Aldon LM(i) Main Menu ................................................................................... DO 2-2 Global View ....................................................................................................... DO 2-3 Global User Defaults ............................................................................ DO 2-3 Panel Specific Subsetting ...................................................................... DO 2-5 “Hot Keys” ............................................................................................ DO 2-5 “Work with...” Panels ........................................................................................ DO 2-5 Working with Release Objects ........................................................................... DO 2-6 Options Available on the Work with Objects by Release Panel ........... DO 2-9 Subsetting a “Work with” Panel ......................................................... DO 2-15 Chapter 3 Moving Objects DO 3-1 Checking Out Objects ........................................................................................ DO 3-2 Overview ............................................................................................... DO 3-2 Eligible Objects ..................................................................................... DO 3-3 Eligible Recipients ................................................................................ DO 3-3 Eligible Agents: Authority to Request or Perform Checkouts ............. DO 3-3 Object Flow ........................................................................................... DO 3-4 Ownership and Authority ...................................................................... DO 3-5 Check Out With or Without Requests .................................................. DO 3-5 Check Out With or Without Task Association ..................................... DO 3-6 Selecting Additional Dependent Objects .............................................. DO 3-6 Available Interfaces .............................................................................. DO 3-6 Checking out Objects ............................................................................ DO 3-8 Transferring Objects Between Developers ........................................... DO 3-9 Emergency Checkouts .......................................................................... DO 3-9 Checking Out Files for a Child Release .............................................. DO 3-10 Promoting Objects ........................................................................................... DO 3-10 Eligible objects ................................................................................... DO 3-10 Eligible Agents: Authority to Request or Perform Promotes ............. DO 3-11 Object Flow ......................................................................................... DO 3-12 Session Protection ............................................................................... DO 3-12 Creating vs. Moving ........................................................................... DO 3-12 Creating on Promotion ........................................................................ DO 3-13 Moving on Promotion ......................................................................... DO 3-14 Level Checks ....................................................................................... DO 3-14 Dependent Objects .............................................................................. DO 3-14 Ownership and Authorities ................................................................. DO 3-15 Physical Files and Tables .................................................................... DO 3-15 Logical Files ....................................................................................... DO 3-16 Handling Data on Promotion .............................................................. DO 3-16 Deploying on Promote ........................................................................ DO 3-16 DO ii • Contents Aldon LM(i) Daily Operations Reference ......................DO 3-29 Changing Install Live Default Values .........DO 3-25 Selecting Objects to Merge ........DO 3-38 Move/Define Object Function ................................DO 4-11 Moving to ILE .....................................................DO 3-26 Merge Objects into Parent vs.................................DO 3-44 Cancelling Checkouts and Deleting Objects .....................................................................................................................................DO 4-11 Adding an Object ..........................DO 4-10 Changing Object Attributes .............DO 3-18 Promoting Objects .............DO 3-38 Modifying and Testing ILE Objects .......................................................................................................................................DO 3-17 Creating Promotion Requests ................................................DO 4-9 Associating Source with an Object ..................................................................DO 3-46 Chapter 4 Working with Objects DO 4-1 Working with Objects by Developer ........................................................................................................DO 3-18 Emergency Checkout and Promotion ..................................................................................................................DO 3-45 Deleting Archived Objects ......................DO 3-44 Retiring Objects ................DO 3-34 Fulfilling Install Live Requests ............................................................. Promote to Parent ........................DO 3-17 Promotion With or Without Requests .........................DO 3-36 Clearing Invalid Install Live Request Conditions ..............................DO 3-17 Available Interfaces .DO 4-13 Single-Copy Create Specifications ................................................................................................................................................................................................................................................................................................................................................................................................................DO 4-2 Creating Objects .......................DO 3-34 Objects Not Yet Eligible ...............................................................DO 3-26 Merging Does Not Change Object Version Numbers .......................................DO 3-18 Moving Objects to a Parent Release ..................................DO 3-19 Effects of Promote to Parent ...................Third Party Cross Referencing Files Update on Promotion to Production ..................................................................................................................................DO 4-4 Object Creation and ILE ........DO 3-26 Merging Produces Multiple Log Entries ...............................DO 3-26 Task/Release Connections Made Automatically ........................................................................................................DO 4-8 Changing an Object Description ............DO 3-19 Merging Objects into a Parent Release ..........................................DO 3-30 Requesting Install Live ..........DO 3-29 Additional Install Live Features .......................................................................DO 3-34 Objects Ineligible Due to Library Groups ....................DO 3-37 Changing an Object’s Production Location ..............................................................................................DO 4-16 Aldon LM(i) Daily Operations Reference Contents • DO iii .........................................................................................................DO 3-44 Modifying and Testing ILE Modules ........................................................................DO 3-44 Modifying and Testing ILE Programs ........................................................DO 3-26 Installing Live ..............................DO 3-19 Capabilities and Features of the Promote to Parent Function ....................... ........................... DO 4-36 Deleting Development Log Entries ............................................................... DO 5-17 Selecting Objects to Compare ................................................................................................................................... DO 5-13 Resolving Conflicts Using Merge ................................................................................................. DO 4-24 Create Command Defaults and Binding Directories .......................................................... DO 5-10 Resolving and Clearing Conflicts ...................................................................................................................... DO 4-24 Other Setup Recommendations for ILE Objects .................................................................. DO 5-16 Comparing With Harmonizer ......................................................................................... DO 5-2 Conditions Defined ....... DO 4-38 Chapter 5 Working with Conditions and Conflicts DO 5-1 What are Conflicts and Non-Conflict Conditions? ....... DO 4-33 Development Log Action Codes .................................. DO 4-32 Use Subsetting to Limit Entries Displayed ............................................ DO 5-18 Batch Compare Report ........................................................................................................................... DO 5-12 Merging With Harmonizer ....Working with Object Dependencies ..................................................... DO 4-35 Development Log Error Codes . DO 5-3 Types of Requests and Non-Conflict Conditions ................... DO 4-24 Using Object Dependency Data ................................DO 4--36 Object Version Numbers ................................................................................. DO 5-19 Working with the System i PCO Session ...................................................................... DO 5-5 Working with Conflicts ................................................................... DO 5-19 Chapter 6 DO iv • Contents Aldon LM(i) Daily Operations Reference .................... DO 5-11 Promoting Cleared Conflicts ............. DO 5-8 Common Types of Conflicts ........................................................................................................ DO 4-25 Acting upon Dependent Objects .................................................................................. DO 4-25 Overview ..................................................................... DO 5-7 Conflict Status ............................................ DO 4-20 Working with Binding Directories ....................... DO 5-15 Batch Merge Report ........ DO 4-26 Act upon Dependent Objects Panel ................. DO 5-11 Setting Your Default Compare and Merge Method ...... DO 5-2 Working with Requests and Non-Conflict Conditions .................................. DO 5-13 Navigating The PC Merge Window ......................................................... DO 4-21 Technical Details .......................................................... DO 4-18 Completing Object Dependency Data for ILE Objects ...................... DO 5-2 Conflicts Defined ..................................... DO 5-11 Rules for Promoting Conflict Objects ..... DO 5-9 Less Common Conflict Types ........................................................................................................................................................................................................................... DO 5-17 Navigating The PC Compare Window .......................................... DO 5-7 To display the Work with Conflicts panel ......................................................................................................................................................................................................... DO 4-26 Using the Development Log .......................................................... ......................................DO 6-7 Object Data Report ........DO C-13 How Aldon LM(i) Manages the Physical and Logical Files .....DO D-2 Aldon Option Setup for Abstract/Probe+ and Pathfinder ...............................................................DO 6-9 Appendix A Pseudo-Source DO A-1 About Pseudo-Source ......................................................................................................................................................................................................................................................PRTFCHKOUT ..........................................PRTFDSPLOG ...................DO C-3 Requirements and Limitations for *RCDS Objects .....................PRTFPROMOT ...................................DO A-2 Appendix B Menus as Aldon LM(i) Objects DO B-1 Developing System i Menus with Aldon LM(i) .......................................................................................................................................................................................................................................................................................DO C-9 Working with *RCDS Objects .........DO 6-8 Development Log Report ..................................DO 6-2 Custom Report Example .....................................................................PRTFPRTOBJ ..............DO D-2 Aldon Option Setup for PDM .................................................................................DO C-11 *RCDS Objects in Multiple-Release Applications ...................................................................DO C-12 Working with Underlying Files ..................DO B-12 Appendix C Record Objects DO C-1 Overview ............DO B-1 Handling Menu Objects Using Non-Default Values .............DO D-3 Using Aldon Options ...............................................DO B-3 Handling Menu Objects Using Pseudo-Source ..............................................................................................DO C-5 Controlling *CONTAIN File Creation Options ..............................................................................................................................DO D-5 Aldon LM(i) Daily Operations Reference Contents • DO v ....................................................................................................................DO C-4 Defining Record Objects ..............................DO A-2 Technical Details ............DO 6-1 Page Headings .......................................................................Reports DO 6-1 Overview of Reports .........................................DO B-8 Working With Pseudo-Source Based System i Menus ....................................................................DO 6-6 Promote/Create Object Report .DO C-2 *RCDS Object Limitations and Requirements .........DO C-3 Requirements and Limitations for the Underlying Files ............................................DO D-1 Aldon Option Setup ................DO 6-2 Checkout Report ..........................DO 6-1 Custom Reports .............DO C-13 Appendix D PDM-Style User Options DO D-1 About PDM-Style User Options ..................................... ...........................................DO F-10 Multiple Selection Panels ................................................................................................................................................................................................DO F-2 Panel Name and Title ...DO F-3 Function Keys ..................................Overview and General Instructions ......................DO F-9 Selection Panels ..........................DO F-9 Program Message Line ................... DO G-2 SQL Packages ................................... DO G-3 Object Text for SQL Objects ................................................................DO F-10 Option Processing for Sub-Files (Lists) .................................................................................................. DO D-11 Creating User Options .........................................................................................................DO F-3 Panel Body .................................... DO D-7 Processing Queued Orders ....................... DO D-5 The Aldon Options ............................................................................................ DO D-15 Appendix E Interface to Abstract/Probe+™ and Pathfinder™ Appendix F The Panel Interface DO E-1 DO F-1 Introduction .................................................................................................................................................. DO D-8 Using Single-Object Options ............................................................ DO G-5 Daily Operations Reference Index DO Index-1 DO vi • Contents Aldon LM(i) Daily Operations Reference ............................................ DO D-10 User Supplied Options ....................................................................................DO F-7 Enter Key ..................................DO F-1 The System i Panels .......DO D--6 Object Selection ...................................................................................... DO G-4 SQL Performance Improvement Suggestions ................................................................................................................ DO D-11 Defining the Options File to Aldon LM(i) ......DO D--15 Using User Options in Aldon LM(i) .........DO F-13 Appendix G SQL Objects DO G-1 Adding SQL Objects ........................................................................................................................................................................................................................................................................................................................................................................................................................................DO F-9 Terminal Message Line ................................................................DO F-9 Single Selection Panels .............................DO F-11 PC Terminal Emulation ........................................................................ By managing the entire process of moving objects from the production environment into development. • Programmers leave unexpectedly and no one knows what modifications they have been working on. • “Small” changes that did not appear to need much testing end up causing major production bugs. it is difficult to discover if it was caused by new software changes and. Aldon LM(i) allows you to feel confident that your Aldon LM(i) Daily Operations Reference Preface • DO vii . which are intended to protect the production environment.Aldon LM(i) Daily Operations Reference Daily Operations DO Preface DO In the rush to meet implementation deadlines and to reduce growing data processing backlogs. Aldon Lifecycle Manager (System i Edition) (Aldon LM(i)) helps to eliminate these problems by providing an automated method for enforcing standards and for maintaining control over the development process. if so. inevitably leads to unexpected and costly production failures. The inability to track modifications and to manage the development and testing effort can lead to other serious problems. management control over the development process often diminishes and testing and quality assurance standards are neglected. • Source and object code get “out of sync” so that it is difficult to know exactly what source code is running in production. worse yet. what those changes were. the source for a production object is lost. When a problem occurs in production. • Two programmers modify the same program simultaneously and one unwittingly overwrites the other's changes. Or. and back into production again. Neglecting these standards. through testing and Quality Assurance. the programmer requests or performs a promotion into a testing environment. Development of reliable software requires testing of changes with multiple sets of test data. Entry of a comment for each checkout or promotion can be optional or required.procedures are being followed and to know exactly what the status of any object is at any time. or as a separate step. After testing. the object is deleted from the Development environment to ensure that no duplicate copies exist. For each application. In addition. This enables you to require more rigorous testing for critical applications. Aldon LM(i) logs the checkout and ensures that no one else can inadvertently check out the same program. specify to Aldon LM(i) how many environments an object must pass through before it is moved back into the production environment. promote the object into the next testing stage or into production. For example. Since every operation is logged. Aldon LM(i) keeps multiple data libraries in sync by automatically updating data libraries with your latest file changes as they are developed and promoted. Once objects have been placed in the quality assurance or production environment on your development system. you can authorize users to specific functions by application. specify whether you want objects to pass through separate testing and Quality Assurance phases. New tasks may be defined by authorized users at any time from within common functions. It enforces them. and aid in selecting and manipulating the objects involved. they can be deployed via SNADS or magnetic media to remote systems where they can undergo further development or can be placed in production. Deploy automatically on promotion into quality assurance or production. For each application you define to Aldon LM(i). you can allow programmers to check out objects. In addition. With Aldon LM(i). it is easy to find out who has worked with application objects and what operations they have performed. a programmer must “check out” a copy of an object to make changes to it. Users may DO viii • Preface Aldon LM(i) Daily Operations Reference . but may want librarians or managers to promote them into testing or Quality Assurance. The production environment may also require multiple sets of parallel yet independent data. Tasks help users organize changes in progress. Allow some users to request checkouts or promotions and others to fulfill their requests. When an object is promoted from Development. When the changes are complete. Aldon LM(i) allows you to set your standards. Objects in an application being changed for a common goal can be temporarily grouped together as a task using the Task Tracking System. Evaluate all or part of an application to check for problems at any time using the verify function. the associated source is always moved with it and it can be recompiled in the new environment to ensure that the source and object match. as when an application processes data for several divisions of a company on a single system. It is an integrated system to provide you with management control of the entire software development process. It allows you to manage change. or to replace production objects within the original release as soon as new ones are fully tested. With this method. or view task information from a panel dedicated to working with tasks. it is easy to return to the former production release. You can name the default job queues. then indicate to Aldon LM(i) which ones to work with and what you want done. and output queues for Aldon LM(i) for each application or release. All panels are SAA compliant and supported by context sensitive help text. Aldon LM(i) is not just a simple implementation tool or a turnover-to-production utility. If you elect to create new releases. Display a list of objects that meet your criteria. For extra safety. Aldon LM(i) provides similar flexibility by allowing you to check out and promote objects into a new release. It maintains the structure and the standards and allows you to know exactly what activity is occurring. Tell Aldon LM(i) how to structure your development environment and what your standards are. You can then retrieve the archived copies if a failure occurs. Any number of tasks can be under development simultaneously. if a problem arises in the new release. the results of several tasks will typically be included in each release. Aldon LM(i) is designed to be comprehensive and easy to use.inquire about an individual task's status by focusing any of the Aldon LM(i) object displays on that task. Aldon LM(i) Daily Operations Reference Preface • DO ix . It helps you to get more changes and tasks into production more quickly without sacrificing quality and reliability. If you group objects being changed into tasks with the Task Tracking System. For objects in production. job descriptions. Aldon LM(i) stores all of the objects for a particular release in separate libraries which can be placed ahead of the previous release libraries in production library lists. The panels offer a “point and shoot” orientation. you can archive existing copies of production source members and objects before they are replaced. Use of the Task Tracking System can be optional or required. You can also set rules for naming the libraries that contain objects at each stage of the development cycle or can allow specific names to be given. DO x • Preface Aldon LM(i) Daily Operations Reference . through Integration and Quality Assurance. and deployment libraries Aldon LM(i) Daily Operations Reference Overview of Aldon Lifecycle Manager (System i Edition) • DO 1-1 . and operations you might want different classes of users to perform • Testing procedures for objects in various stages of development • Use of reference libraries in assigning ownership and authorities to objects • Use of the Aldon LM(i) verify function to check the integrity of release libraries. releases. It describes: • Grouping of programs into applications and releases • Grouping of libraries into environments for each release • Movement of objects through release environments during the development process • Integration of multiple-release capabilities into Aldon LM(i) • Options for structuring applications. It defines Aldon LM(i) concepts. and environments • Movement of source and objects from Production into Development. data libraries. and processes.Aldon LM(i) Daily Operations Reference Daily Operations DO Chapter 1 Overview of Aldon Lifecycle Manager (System i Edition) Introduction This chapter provides an overview of how Aldon Lifecycle Manager (System i Edition) (Aldon LM(i)) manages the software development and implementation process. and provides examples of how to use Aldon LM(i) to perform development work. and back into Production again within a release • Adding and populating releases to create new versions of an application • Suggested Aldon LM(i) user classes. For example. For each release you can specify: • The number of testing environments used • Library naming rules • Assignment of authorities to objects in various stages of development and testing. production objects are replaced as soon as new copies are fully tested. Another may contain objects used to manage personnel and human resources. and output queues DO 1-2 • Overview of Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . job descriptions.Applications and Releases With Aldon LM(i). This includes job queues. Use application-level settings to instruct Aldon LM(i) whether to: • Log each action taken on application objects • Log deployment of objects to other systems • Manage production data • Archive old copies of objects If there is a single release for an application. and in production • Who has access to the Aldon LM(i) operations that work with objects • Object creation commands • Options governing object creation library lists • The processing environment for Aldon LM(i) operations performed on objects in the release. If there are multiple releases for an application. related objects are defined as an application. changed objects accumulate in a new set of libraries as work on them is completed. When development of a release is complete. one application may contain objects required for managing a manufacturing operation. you can lock the release to prevent further modification of Production objects. As you move objects through each phase of the development. Development Environment Developers use the Development environment for the creation of new objects and for the maintenance of existing ones. PC based development is also supported.Aldon LM(i) Environments The following sections briefly describe each Aldon LM(i) environment. The different environments each use different libraries. Development Integration * Quality Assurance * Production *optional environments **defined at application level Archive ** Figure 1 . testing. A developer's libraries may be located on a remote system connected to the host system on which Aldon LM(i) resides. and implementation process.Aldon LM(i) Release Environments Each Aldon LM(i) release consists of several environments. and which environments are optional or shared among releases. Aldon LM(i) Daily Operations Reference Overview of Aldon Lifecycle Manager (System i Edition) • DO 1-3 . Descriptions indicate the purpose of each environment. The Development environment is the only environment in which source can be changed. Developers can also test their changes using this environment. Each environment contains objects and corresponding source at a specific stage of the development cycle. Developers can share development libraries if necessary. A developer may use the same libraries for all releases of all applications or may have different libraries identified for some applications or releases. Each developer can have separate libraries for source and objects or they can have one library containing both source and objects. objects pass through corresponding Aldon LM(i) environments. This structure allows developers and testing personnel to access the appropriate copies of objects with simple library list modifications. Development libraries contain objects developers are currently working with. The Integration environment for a release consists of either one source library and one object library or one library containing both source and objects. so they must be checked out into the Development environment to be fixed if failures occur during Quality Assurance testing. The Production environment can contain a full set of source and objects. Quality Assurance Use the optional Quality Assurance environment for final testing by Quality Assurance personnel or for user acceptance testing. Source members cannot be changed in Quality Assurance. Add or remove the Quality Assurance environment of a release as needed. They must be checked out into the Development environment for further modification if failures occur during Integration testing. Its contents are typically controlled by a Quality Assurance librarian. DO 1-4 • Overview of Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . Archive The optional Archive environment receives copies of old objects as new copies are moved into the Production environment. Objects end up in the Production environment after passing through the testing environments. A user with “Restore from archive” and “Perform checkout” or “Perform emergency checkout” authority can restore copies of old objects from the archive to Development.Integration Environment Use the optional Integration environment when multiple developers want to test their changes together. Production The Production environment within a release can consist of up to 23 libraries. Add or remove the Integration environment of a release as needed. it is combined with the Production environments of prior releases to form a working version of the application. Source members cannot be changed in Integration. or it can consist of only objects and source that have been changed for a release. It also consists of either one source library and one object library or one library containing both source members and objects. If the Production environment of a release consists of only changed objects. each of which can contain source and objects. “Source” includes both standard compilable source code and pseudo-source except where pseudo-source is specifically mentioned. The same object-name/type combination may be used in more than one application. and records other objects as “non-source objects. and the execution of pseudo-source to recreate CL based objects. Aldon LM(i) creates database entries associating source-based objects with their source code. the developer receives the source code associated with the object for editing. If a non-source object is CL based (can be created by executing one or more CL commands). The developer associates the pseudo-source with the object using an Aldon LM(i) function to transform the non-source object into a source-based object. Pseudo-source is a CL source member containing commands that create the object.Objects Types of Objects Aldon LM(i) works with objects created from source code such as COBOL or RPG programs (including ILE programs). binding program modules into ILE programs. When modifying a non-source object. and source-based objects for which no source is available. the developer may create “pseudo-source” for it. Aldon LM(i) re-creates the object by executing the pseudo-source when necessary. and objects created by some third party vendor packages such as PowerHouse from Cognos. objects that must be created by applications. When modifying a source-based object. Several versions of each unique object which may exist. each in a different release environment. “Source-based” refers to both compilable language based and CL based objects. “creating an object” refers to compiling programs and program modules. objects created by CL commands such as data areas or JOBDs. When you define a release. In this user documentation. Identifying Objects Within an application. a given object-name/type combination identifies a unique object. “Non-source object” refers to CL based objects not associated with pseudo-source. The pseudo-source is available as the starting point for future modifications. but Aldon LM(i) does not recognize or enforce any relationship between objects in different applications. the developer receives the actual object which can serve as a model for the new replacement object.” Both source-based and non-source objects are available to developers for modification. Aldon LM(i) Daily Operations Reference Overview of Aldon Lifecycle Manager (System i Edition) • DO 1-5 . Figure 2 . the movement process is separated into two steps. you might want to allow developers to request that objects be promoted into the Integration environment. Once an object reaches Quality Assurance or Production. Figure 2 depicts the flow of source and objects during development. In addition. The object is then promoted through testing. The second is the fulfillment of that request. Any movement from Production. and back into Production. it can be deployed to remote systems. If you select this option. or Integration to Development is called a checkout.Object Movement Within a Release Access to Object Movement Before any movement operation is performed. Aldon LM(i) checks to ensure that the requesting user is authorized to perform that operation.Object Movement As objects move through the stages of development. Quality Assurance. You can allow some users to request a promotion or checkout operation and others to actually perform it. A developer checks out an object to work on it. Quality Assurance. Any movement toward Production is called a promotion. you DO 1-6 • Overview of Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . For example. The first step is the creation of a request. they move through corresponding Aldon LM(i) environments. but might want a development manager to actually review the requests and perform the promotions. Aldon/CMS Environments and Object Movement Checkout Production Production Development Integration* Quality Assurance* Production Promotion * These environments optional at release setup. The checkout function ensures that only authorized users check out source code and tracks object movement to insure that changes are performed cumulatively rather than in parallel. but not into Quality Assurance. You can require some users to create requests to check out or promote objects and can allow others to check out and promote without requests. Promoting After completing modifications. you may want to allow developers to promote objects into the Integration environment. Conflict Records Conflict records prevent hazardous object movements from taking place without proper authority and needed integration of parallel changes. Checkouts that could result in an overwrite of one set of changes by another on promotion.can restrict users from performing specific types of promotions. promote an object from Development into the next environment in use for the release (Figure 2). For example. Aldon LM(i) Daily Operations Reference Overview of Aldon Lifecycle Manager (System i Edition) • DO 1-7 . then promote the copy of the object created by the merge. In addition. If you are working with multiple releases of an application. changes in one release that may be important for other releases can generate conflict conditions in those releases. Aldon LM(i) object referencing identifies and presents related objects which may also require checkout and modification to work with objects initially selected for checkout. Resolve conflicts by merging changes with Harmonizer or Harmonizer (Windows Edition). create “conflict condition” records on the copies of object involved. Continue promoting the object forward from environment to environment as you complete each phase of testing until the object reaches the Production environment. Conflict records must be removed by a user with the proper authority before promotion of the copies. Authority to request or perform promotions or checkout operations can be granted for the entire system or for each application. Checkout Aldon LM(i) provides controlled access to source code through use of a checkout function. you can require requests for promotions into some environments and allow promotions into other environments without requests. The Aldon LM(i) object database tracks all copies of an object within an application. Archiving If an application uses the archive feature of Aldon LM(i). Integration. This prevents the inadvertent overwriting of the emergency change when the object that was checked out with the normal checkout function is promoted into the Production environment. Aldon LM(i) can also invoke Harmonizer or Harmonizer (Windows Edition) to merge the emergency changes with those made to the other active copy of the object if necessary. or Quality Assurance. If a copy of the object exists in Development. Aldon LM(i) creates a conflict condition record to prevent promotion of the object until the emergency changes have been integrated with the work in progress. the object must be retrieved. If for any reason. Deploy objects automatically on promotion into Quality Assurance or Production. you can deploy them using Aldon LM(i) object deployment. it can be checked out into the Development environment from the Archive library. Check source directly out of the Production environment. Emergency Checkout and Promotion Use the emergency checkout function of Aldon LM(i) to bypass the normal development cycle when a production failure occurs. Promotion moves the object directly back to the Production environment. even if a copy of the object exists in Development. DO 1-8 • Overview of Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . or initiate deployment separately. Deploy them to remote locations using IBM's Systems Network Architecture Deployment System (SNADS) or magnetic media. or locally to libraries outside of Aldon LM(i) on the same system. Integration. or source and object is archived using application-level options. 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. Control the number of copies saved and whether source only.Object Deployment After developing and testing objects. or Quality Assurance. For more information about CM. A URL to CM. You can move groups of objects together by specifying the task. a single release of an application may be sufficient. Accessing Aldon Community Manager You can access Aldon Community Manager (CM) issues from associated Aldon LM(i) tasks. see “Linking to Aldon CM Issues” starting on page TT B-1 in the “Aldon LM(i) Task Tracking System Reference”.Task Tracking System Use the Aldon LM(i) Task Tracking System to group objects needed to accomplish a goal and to associate the objects with notes describing the task. in a particular environment. Aldon LM(i) Daily Operations Reference Overview of Aldon Lifecycle Manager (System i Edition) • DO 1-9 . or with an outstanding check out or promotion request and to select the ones you want to move from the lists. Every checkout or promotion is logged by Aldon LM(i) so that you can track the history of every object and can determine the status of any object or task at any time. For sites developing or maintaining several versions of an application simultaneously. displays the issue(s) attached to a specific Aldon LM(i) task. Aldon LM(i) Works with Multiple Releases For sites with relatively simple development needs. available on the Work with Tasks panel. Community Manager allows you to link one or more CM issues to any task in Aldon LM(i). or you can move one object at a time. Aldon LM(i) allows you to review lists of the objects by task. Use the same panels to perform development functions when working with an application with a single release as when working with an application having many releases. Aldon LM(i) supports multiple releases. Multiple-release capability is fully integrated throughout Aldon LM(i) and is largely transparent to the user. A' Modified Object. D' New Object.There are two types of releases in Aldon LM(i): Base releases and Delta releases (Figure 3). For many applications. Aldon LM(i) supports an unlimited number of Base and Delta releases for each application. a simple release structure consisting of a single Base release. 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 Base release contains a complete set of application objects. Modified objects closer to the starting Delta replace older copies of the objects closer to the Base. The set of releases traversed by starting at any Delta release and tracing back to the Base form a functional version of the application.Aldon LM(i) Release Types Related releases may be visualized as a tree of Delta releases descending from a Base release. DO 1-10 • Overview of Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . or a Base release with one associated Delta release is sufficient. and running the application. 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 checkout. compilation. A Delta release contains objects added and changed since the prior release. The samples in Figure 4 on page DO 1-11 illustrate the range of valid release relationships under Aldon LM(i). H Figure 3 . Aldon LM(i) Daily Operations Reference Overview of Aldon Lifecycle Manager (System i Edition) • DO 1-11 . Aldon LM(i) provides tools for tracking and resolving these conflicts.Conflicts may arise when changes are made to related releases. Object version numbers also appear in development log entries which provide an audit trail of all development activity. Sample Valid Release Trees Base 1 Base 2 Base 3 Delta 1A Delta 2A Delta 3A Delta 3B Base 4 Delta 2B Delta 4A Base 5 Delta 4B Delta 4C Delta 5A Delta 5B Delta 5C Delta 5D Delta 4D Delta 4E Delta 4F Figure 4 .Sample Valid Release Trees Object Version Numbers Each copy of each object in Aldon LM(i) bears an object version number identifying the Production copy it originated from and the number of times it has been checked out. You can define additional vendor or user supplied create commands to Aldon LM(i) at the global or application level. At the release and application levels you can set defaults by object name. DO 1-12 • Overview of Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . file. Use create command defaults to direct Aldon LM(i) to use a vendor or user supplied create command instead of defaulting to the standard IBM command. or global level. Options for both custom and standard IBM commands may also be specified in create command defaults. No special commands are needed. The command and command options to be used for a given object type and attribute can be specified in a “create command default. The create command and options used for a given copy of an object can be: • Specified directly by editing the create options for existing copies of the object • Allowed to default to values set for that object type and attribute by a create command default at the release. No prior set up is required to create objects with Aldon LM(i).Object Referencing Aldon LM(i) can gather information on object dependencies to allow easy locating of all objects depending on a given object. specify create command defaults for individual objects as well as by type and attribute. use object dependencies when promoting the object to automatically locate and create objects needed to work with the changed object in the new environment. Aldon LM(i) ships with global-level create command definitions for all existing IBM create commands. Object Creation Aldon LM(i) automates and simplifies object creation. Aldon LM(i) handles execution of the pseudo-source you provide to create non-source objects. See “Custom Object Creation Setup” starting on page SA 23-1 in the “Aldon LM(i) Setup and Administration Reference” for more information. or program. application. Knowing where an object is used aids in assessing the impact of changing a given copy member.” At the application level. include member. After changing an object or completing one phase of testing. Defaults set when the product is shipped meet the needs of many sites without modification. or application. release. to assign ownership and authorities by object name. The default ownership and authorities assigned by Aldon LM(i) have been carefully chosen and will meet the needs of many locations. When you promote objects or load them into Aldon LM(i) libraries from libraries that are not defined to Aldon LM(i). or use existing libraries with “live” objects or older copies of the objects that already have the correct settings. and the use of reference libraries and objects are described in “Ownership. This circumvents checkout to Development and subsequent promotion back to the desired environment. Create a special reference library for any environment of any release. Aldon LM(i) maintains limits on access to the Integration. Production. or by any combination of these parameters. The create non-resident function compiles an object directly into an environment where it is required to prevent level checks. but does not revoke any existing authorities. Aldon LM(i) Daily Operations Reference Overview of Aldon Lifecycle Manager (System i Edition) • DO 1-13 . Identify reference libraries by name. object type. Aldon LM(i) assigns an owner to them and grants specific authorities. yet flexible. Authorities. Source never enters Development so change control is maintained. Quality Assurance. Create special reference libraries containing only as many dummy reference objects as needed. or share reference libraries across any number of environments in any number of releases and applications. Reference libraries and reference objects provide an additional method of assigning ownership and authority that is powerful. Aldon LM(i) uses one of two methods to assign ownership and authority to an object: Aldon LM(i) defaults or reference objects. When you define a new release to Aldon LM(i) by mapping existing libraries. Use reference objects. Aldon LM(i) first checks for an applicable reference object. and allows a broad range of control with minimum set up. and Archive libraries and to the objects in them. Aldon LM(i) object referencing can identify all non-resident objects required to test a changed object.The object creation function also supports creation of “non-resident” objects to obtain copies required for testing. Default ownerships and authorities. Aldon LM(i) environment. or locate them using the library list in effect when the operation is performed. When assigning ownership and authorities to an object. If Aldon LM(i) does not find a reference object it uses default values. Object Ownership and Authorities In order to prevent unauthorized changes to source and objects. and Reference Libraries” on page CG 2-1. Aldon LM(i) grants itself all authority to the libraries and objects. Quality Assurance. developers usually have complete authority to the objects in their own libraries and the ability to use the objects in the Integration. you can allow them to request checkouts and provide another user with the ability to fulfill their requests. For this reason. and Production environments. Quality Assurance. In Aldon LM(i) you can define user “classes” for different types of users. you can allow developers to check out source members and objects when they need to work with them.Verify Aldon LM(i) maintains a database describing the location and nature of all application objects. Verification checks for addition or deletion of objects from outside of Aldon LM(i). Use the Aldon LM(i) verify functions at any time to check the integrity of application libraries. This section describes predefined user classes included with Aldon LM(i) and the operations they might perform. With Aldon LM(i). &DEVELOPER Developers are directly responsible for maintaining existing source members and objects. see “Verify Functions” starting on page SA 25-1 in the “Aldon LM(i) Setup and Administration Reference”. data libraries. You can have a similar arrangement with promotes. checks object ownerships and authorities. you may have only a few classes of users authorized to perform a wide variety of Aldon LM(i) activities. If you do not want developers to be able to check out source members and objects without approval. and Production DO 1-14 • Overview of Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . and identifies possible problems with logical/physical file relationships. and remote libraries that receive deployed objects. and for creating new ones. They also must be able to test the changes they have made before promoting objects from their development libraries. If your development staff is very large. You can allow developers to promote objects into the Integration. Aldon LM(i) Users There are a number of different types of Aldon LM(i) users. Define an individual user as a member of a class or by specifying unique authorities. you may have many different classes of users with authority to only a limited number of functions. For more information about Aldon LM(i) verify functions. If your staff is small. In addition. To control the contents of the Quality Assurance libraries. &LIBRARIAN In a large development operation. you can grant them the authority to the checkout or promotion functions. managers can be given authority to define the tasks. you might want to assign a person the responsibility of controlling the objects in a particular environment. You might also want to give managers the ability to resolve and clear any conflicts that might occur and to create or change options. &QUALITY (Quality Assurance Personnel) Quality Assurance personnel typically perform testing activities and control the contents of the Quality Assurance libraries. another who fulfilled promotion requests into Quality Assurance. Aldon LM(i) Daily Operations Reference Overview of Aldon Lifecycle Manager (System i Edition) • DO 1-15 . and the definitions of applications and releases. This person would have the ability to fulfill promotion or checkout requests.environments. and another who fulfilled requests for promotion into the Production environment. To do testing. you could have one person who fulfilled requests for promotion into Integration. you might grant them the authority to request promotions into the Production environment or to actually promote objects into the Production environment once they have been thoroughly tested. If you choose to group application changes into tasks. You could also assign a specific person the responsibility of fulfilling checkout requests. Since you can grant authority to specific promotion operations. defaults. You can also give developers emergency checkout authority so they can quickly perform an urgent fix without weakening the audit trail or the structure defined for normal program development. &MANAGER If you would like managers to review checkout or promotion requests and to actually fulfill them. Librarians or operators might also have the ability to resolve and clear conflict conditions or deploy objects to remote systems. authorities. and Production environments. or you can require that they submit promotion requests that are actually fulfilled by a manager or librarian. they also need to have the ability to promote objects from Integration or Development into Quality Assurance. they require access to the objects in the Quality Assurance. efficient. Help text is available for input fields.User Interfaces The main access to Aldon LM(i) is through the panel interface. DO 1-16 • Overview of Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . User exits are also available to invoke custom user provided programs during most functions that move or create objects. 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. function keys. To retrieve panel level help text. These Aldon provided PDM options may also be used within Hawkeye’s Pathfinder and Abstract Probe+ cross referencing and documentation tools. is to provide a single user interface across applications that is consistent. which gives an overview of the purpose of the panel and its relationship to preceding and following panels. and some other screen features. or press F2 after retrieving field level help. Panel level help text. Aldon LM(i) panels follow the Common User Access Standards defined for the System i by IBM. Although the panel interface is designed to be clear and simple. The goal of these standards and of implementation of Aldon products in accordance with them. Hypertext links appear as underscored orange text. Context is determined by the panel displayed and by the position of the cursor when Help is requested. messages. Hypertext links on some help displays provide access to additional help information. and easy to use. or may want to insure they are taking full advantage of all the interface has to offer. PDM-style options may also be created to perform custom actions from object lists within the Aldon LM(i) panel interface. is also provided. Many functions may also be performed using commands or PDM user defined options provided by Aldon. position the cursor on the title line or on any empty area of the panel. users may have questions about some features. “Appendix B: The Panel Interface” describes features important for Aldon users. fields that display information. Place the cursor on or near an input field to retrieve a description of the field's function and valid entry options. 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. Features most important for new Aldon LM(i) users are summarized below: Context sensitive help text is available at all times throughout Aldon's System i applications by pressing the Help or F1 key. Press Page Down (or Roll Up) to view additional items. Retrieve commands executed during the current Aldon LM(i) session by pressing F9. it appears to the right of the field. If the list of values allowed for a field is fixed and short.Input fields appear as underscores. On most panels a fully functional command line appears immediately above the function key prompts. the “Daily Operations Reference”. This concludes the overview of Aldon LM(i). Values display on a “single selection panel” with each allowed value preceded by a period. Access to the IBM WRKSBMJOB command via F14 and WRKSPLF via F18 is also provided on many panels. refer to the “Setup and Administration Reference”. press Page Up (Roll Down) to return to previously viewed items. When there is more information to view than will fit on one panel. When “More: -+” or “More: -” is displayed. Any System i command may be executed from this line. For detailed information on set up and operations. A “+” symbol after a field indicates you can prompt for a list of allowed values with F4. “More: +” is displayed on the right side. and to the help text provided within Aldon LM(i). Aldon LM(i) Daily Operations Reference Overview of Aldon Lifecycle Manager (System i Edition) • DO 1-17 . Type a slash (/) over the period preceding the desired value and press Enter to make a selection. DO 1-18 • Overview of Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . On an System i command line. Prerequisite Aldon LM(i) must be registered in the “common installation library. Aldon LM(i) Daily Operations Reference Using Aldon Lifecycle Manager (System i Edition) • DO 2-1 .. execute the following command: STRALDPRD The Start ALDON Products panel displays.” panels for object movement and manipulation. The Work with Objects by Release panel is discussed in detail.” See “The Common Installation Library. At the Start ALDON Products panel. type 1 (Select) and press ENTER to display the Aldon LM(i) main menu. Starting Aldon LM(i) To start Aldon LM(i) from the Aldon Products Menu Use the following steps to start Aldon LM(i) from a menu of all Aldon products identified to the common installation library.. 2.Aldon LM(i) Daily Operations Reference Daily Operations DO Chapter 2 Using Aldon Lifecycle Manager (System i Edition) Introduction to Using Aldon LM(i) This chapter introduces the main menu and the “global view” design used by panels throughout Aldon Lifecycle Manager (System i Edition) (Aldon LM(i)) and discusses “Work with. 1.” starting on page CG 8-1 for details. in the Opt field by the command STRLMI (or STRACMS). the Work with Objects by Release panel. 3. Work with objects by release Work with objects by developer Work with archive objects Conditions menu Work with tasks Deployment menu Display log Work with verify requests Setup menu Work with applications Work with releases Work with data sets User defaults: Rel:ALDON/ACMSDEMO/BASE Dvp:*NONE Tsk:*NONE Command ===> __________________________________________________________________ F3=Exit F4=Prompt F9=Retrieve F14=WRKSBMJOB F18=WRKSPLF F22=More functions Figure 5 . (C) Copyright Aldon. For example. 6. 13. and portions of 6 and 8. 4.5 Aldon Lifecycle Manager for System i All Rights Reserved. Options and portions of options not discussed in this document are discussed in the “Setup and Administration Reference.To skip the Main Menu when starting Aldon LM(i) Type the number of a main menu option after the STRLMI (or STRACMS) command to by-pass the main menu and display the selected panel. 3. 11. 7. 8. The main menu provides access to all functions in Aldon LM(i). 2. For example. to proceed directly to the Work with Objects by Developer panel. 1. press Enter. 5.Aldon LM(i) Main Menu Access the functions described in this chapter from the main menu shown in Figure 5.” DO 2-2 • Using Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . by entering the command STRLMI 1. or by entering the corresponding main menu option number after STRLMI (or STRACMS) on the command line. 7. This “Daily Operations Reference” discusses the following main menu options: 1. 14. execute the following command: ACMSLIB/STRLMI 2 Aldon LM(i) Main Menu CACMS Rel 07. go directly to the first menu option. Inc. 2. Type choice. 1989-2006. 5. 4. 12. For example. Separate values are maintained for each user. then press Enter to return to the previous panel. at a given time. developer and task. is equivalent to entering these values on subset panels such as the Subset Objects by Release List panel shown in Figure 9 on page DO 2-15.Global View Aldon LM(i) provides a global view of an organization's complete software development effort while at the same time allowing the user to focus. on only the items of interest. group. Aldon LM(i) also uses values entered here as defaults for completing some operational panels. or from most other panels within Aldon LM(i). Global User Defaults Press F22 on the main Aldon LM(i) menu. In addition to their use on subsetting panels. These defaults are referenced for subsetting a “Work with” panel with *USERDFT on the associated subset panel. Enter selection criteria on subsetting panels to limit items displayed on other panels to the desired range. the default of *USERDFT values shown in Figure 6. This capability is implemented through the use of global and panel specific subsetting panels. Enter default values for any or all parameters. Use the top portion of the More Functions panel to set default values for release. application. Commands and user defined PDM options also use the default values. For example. Aldon LM(i) automatically enters the developer specified on the More Functions panel as the developer to receive objects being checked out on the Check Out Objects panel. Aldon LM(i) Daily Operations Reference Using Aldon Lifecycle Manager (System i Edition) • DO 2-3 . These user defaults are maintained by Aldon LM(i) both during and between Aldon LM(i) sessions until changed by the user. to display the More Functions panel shown in Figure 6. 2. You must install the corresponding third party software and define it to Aldon LM(i) using option 11 on the Global Setup menu as discussed in “ABSTRACT/PROBE+. . Work with tasks ASC's Abstract/Probe+ Hawkeye's Pathfinder Generate SQL DDL LANSA Analyze object dependencies Command ===> __________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F6=DSPMSG F9=Retrieve F12=Cancel F14=WRKSBMJOB F18=WRKSPLF Figure 6 . name name name name name name Type choice. . See the section “Requesting Tasks” under “Additional Features in the Aldon LM(i) “User's Guide” for details on entering user requests. Key option 13 to retrieve the HAWKBAR menu bar. 13. . and documentation tools for an individuals use and to set user options customizing features of the Aldon LM(i) panel interface. . . . . . press Enter. . . . . 14. BASE ACMSDEMO ALDON PGMRA *NONE *NONE + + + + + *NONE. 4. . . . .CMORFNC Rel 07.More Functions Panel More Functions Use the lower portion of the More Functions panel to access editing. . . . . 3. . . . *NONE. . press Enter. Application Group . . . Edit development tools Set user-defined option file Set operation defaults Enter/work with user requests Record task hours Act upon dependent objects 11. . 16. . . Third Party Products Key option 12 to access the main Abstract/Probe+ menu. . .5 More Functions ALDONT01 Type choices. . . . . . 5. . . Key option 15 to work with LANSA. *NONE. User defaults: Release . . *NONE. . . . 6. Developer . 12. . . __ 1. *NONE. . . . . . . . . . . . setting a user-defined options file. Other Options See the section “Setting Advanced User Preferences” in the Aldon LM(i) “User's Guide” for details on changing development tool defaults. . SQL statement generation. . .” starting on page TI 1-1 before activating it from this menu. . 15. . . Job ASP group . + *NONE. . DO 2-4 • Using Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . Task . . cross referencing. . and setting operation defaults. . . . these panels display information for all releases in all applications. Focus a “Work with” panel on as narrow or broad a group of items as desired by using the default settings on the “More Functions” panel and the subsetting panel specific to that “Work with. With default settings. The original panel re-displays in the exact state you left it before hot keying. Select an item with the appropriate option to display information about that item on a different “Work with.” panel.. or by returning to the main menu and selecting a different panel.Panel Specific Subsetting Global defaults specified on the More Functions panel work in conjunction with subsetting panels specific to each “Work with. Move easily between “Work with. Other options are unique to a single panel.” panels.” panel are maintained until the user exits from the panel back to the main Aldon LM(i) menu..” Panels “Work with” panels provide different views of application objects... and provide options for performing daily operations. For further discussion and an example of subsetting see “Subsetting a “Work with” Panel” on page DO 2-15..” panel..” panel such as the Subset Objects by Release List panel shown on page Figure 9 on page DO 2-15. Many options can be performed from several “Work with..” panels allow direct access to other “Work with.... The various panels provide different information about objects organized for different purposes....” panels are accessed via “hot keys”.” panel..... Subsetting criteria entered for a specific “Work with.. conditions and tasks..” panels using function keys and options. Criteria remain in effect while Aldon LM(i) performs requested functions on listed items. “Hot Keys” Function keys and options on many “Work with. Together... Criteria are also preserved if other “Work with. Aldon LM(i) Daily Operations Reference Using Aldon Lifecycle Manager (System i Edition) • DO 2-5 . Return to the previous “Work with..” panels.. “Work with. Press the appropriate function key to display more than a single object on a different “Work with..” panel by pressing F12=Cancel. global defaults and subsetting allow users to display and work with as broad or narrow a group of items as they desire. DO 2-6 • Using Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . The Work with Requests and Non-Conflict Conditions panel is also introduced. (*=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 D Release Envs Rl T Cnds E Chkout Dvp. The next sections describe panels in order of first use by a new Aldon LM(i) user starting with the Work with Objects by Release panel.” on page SA 25-12. ACTGLL *FILE LF K AC/BAS D QP O ACTGLP *FILE PF K AC/BAS IQP COMMENTRY *PGM CBL AC/BAS P COMMIO *PGM CBL AC/BAS I P COMMPRT *PGM CBL AC/BAS P RCVPRT *PGM RPG AC/BAS P TEST *PGM RPG AC/BAS * 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 7 . Use option 3 to Work with Archive Objects panel. press Enter.. Subsetting for the Work with Objects by Release panel is described in some detail. Use option 4 to work with objects with pending checkout requests. or acknowledgement conditions using the Work with Requests and Non-Conflict Conditions panel shown in Figure 33.Use option 1 on the main menu. . conflict conditions. Each object is listed once for each release containing it. to Work with Objects by Release panel shown in Figure 7 on page DO 2-6.Work with Objects by Release. __________ *TOP. this panel lists all objects associated with the user defaults setting from the More Functions panel. “Work with Requests and Non-Conflict Conditions panel. . Working with Release Objects CWRKOBJREL Position to Work with Objects by Release . View 1 of 3 Select option 1 from the main menu to display the Work with Objects by Release panel shown in Figure 7 and Figure 8. promotion requests. . .” on page DO 5-4. . “Work with Verify Requests panel. Use option 5 to work with objects that have been grouped to organize activity towards a defined goal using the Work with Tasks panel shown in Figure on page TT 3-4. Subsetting for other “Work with” panels is similar and is fully documented in the on-line help text. With default subsetting. *BOT.. Use option 7 to Work with Verify Requests panel shown in Figure 130. starting characters Type options. . Use option 2 to Work with Objects by Developer panel shown in Figure 19 on page DO 4-2. the record displays “D P” to show that copies of the object exist in both Development and Production. letters representing copies not selected appear in lower case. A letter “P” in the Rl column indicates that the release specified in the object record (the “local release”) does not contain a Production copy of the object so the Production copy of an ancestor release will be used for Production purposes. The Rl column is used in applications with multiple releases. and is checked out by a developer.Development I . View 1. A plus sign (+) indicates a descendant release Production environment also contains a copy. pending conditions (Cnds). A minus appears if the local release does contain a Production copy. and flags indicating the data option (D). Columns also list the deployment status of the object (T). a blank indicates Promote data. Aldon LM(i) Daily Operations Reference Using Aldon Lifecycle Manager (System i Edition) • DO 2-7 . If a record includes some copies selected by the current subset criteria. if the object in the example above is checked out for a task.In both views of the panel. For example. entries include the object name. also includes object attribute. if an object is in the Production environment. and release.Quality Assurance P .) The data option column (D) displays a single letter abbreviation for objects that have the Change object data option set to Y (Yes). For example. D . A minus sign (-) indicates the Production environment of an ancestor release also contains a copy of the object. K indicates Keep destination data. In this case the local copy is used in place of the ancestral copy of the object. and membership in that task is specified as a subset criterion.Integration Q . emergency checkout status (E). environments (Envs) and related releases (Rl) containing copies. The environments column (Envs) displays a single letter abbreviation for each environment containing a copy of the object.Production * . shown in Figure 7. and a checkout developer name (Chkout dvp. Lower case display informs the user that while a Production copy exists.Retired object It is possible for copies of an object to exist simultaneously in multiple environments. and a * indicates there are multiple data options between environments. it will not be affected by any options selected. type. “D p” is displayed because the Production copy is not associated with the task. and other copies not selected. and “R” indicates a pending request for checkout or promotion of the object.If the installation job fails.The T (Targets) column displays the deployment status for each object. For more information about the Show Deployment status field. as an ancestor. the “level” of the release (Lvl). In the emergency checkout column (E).When an object is selected for installation at a eligible target. The checkout developer column (Chkout dvp. shown in Figure 8. “Y” indicates the object is currently checked out using the emergency checkout function. “C” indicates a conflict condition. View 2. A Delta release with the Base release as parent is a level 1 release because it has one release.) displays the name of a developer to whom the object is currently checked out. An eligible target is a target with Show deployment status on object displays option selected as Y (Yes). An outstanding deployment exists from the time an installation job is submitted through to successful installation. The T column shows the following values: Outstanding deployment status . and an “other developer” name. A Delta release with a level 1 Delta as parent is a DO 2-8 • Using Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . the object is given an 'F' status. (blank) . The level of a release is a number indicating how many ancestors a release has. provides the full release name. In the conditions column (Cnds). it is given an 'O' status.Not participating or not in any install status. “A” indicates an acknowledgement condition. This specification is effective for all targets (locations) defined to the target definition. if the Show Deployment status field has been selected on the Specify Target Definition panel. the Base. A Base release has no ancestors and may be thought of as level 0. Deployment failure status . see “Maintaining Target Definitions” starting on page DS 5-6 in the “Aldon LM(i) Object Deployment Reference”. The other developer column (Other dvp) is described in the following paragraph. . . Control the editor used through development tool definitions and development tool usage defaults. 6=Print source 8=Display attributes 15=Change create options 19=AltEdit Opt __ __ __ __ __ Object CLNADR CLNADRL DEMOCBL1 DEMOCBL2 DEMOCBL3 Type *FILE *FILE *PGM *PGM *PGM (*=Combined job) 12=Work with conflicts 28=Work with conditions .level 2 release. each checked out to a different developer. .. .. View 2 of 3 View 3. Move through the list by using the Page Up (Roll Down) and Page Down (Roll Up) keys. *BOT. More: + Release Lvl Other dvp. Initiate any of several operations from this panel. CWRKOBJREL Position to . or type an entry in the “Position to” field to move to a particular entry without paging through the list.” indicates the developer to which a copy now in Integration or Quality Assurance was checked out to. Use option 1 on the More Functions panel to set user-level editing and browsing defaults. starting characters Type options. Work with Objects by Release __________ *TOP. Options Available on the Work with Objects by Release Panel * (after an option description) See “Option Processing for Sub-Files (Lists)” on page DO F-11 for information on *=Combined job options and the processing of multiple non-combined job options as a group. Type an entry in the option field for a particular object to perform the indicated action on that object. . “Other dvp. If there are copies in each of these environments. 2=Edit Edit source for the object using the primary editor specified for the selected object. *MULT-n appears where n is a number indicating the number of developers to whom the object is checked out.Work with Objects by Release. . ALDON/ACMSDEMO/BASE BASE ALDON/ACMSDEMO/BASE BASE MARKE ALDON/ACMSDEMO/BASE BASE MARKE ALDON/ACMSDEMO/BASE BASE ALDON/ACMSDEMO/BASE BASE Subset: Rel:ALDON/ACMSDEMO/BASE Command ===> _________________________________________________________________ F7=Add task F9=Retrieve F12=Cancel F14=WRKSBMJOB F17=Subset F18=WRKSPLF F20=Work with conditions F21=Print F24=More keys Figure 8 . not shown. press Enter. Aldon LM(i) Daily Operations Reference Using Aldon Lifecycle Manager (System i Edition) • DO 2-9 . The object list on the Work with Objects by Release panel is sorted by object name. displays descriptive text associated with each object. Warning This option can be used to delete all copies of the object (including archived copies). DO 2-10 • Using Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . Use option 1 on the More Functions panel to set user-level editing and browsing defaults. tasks with which it is associated.. Control the browse tool used through development tool definitions and development tool usage defaults. source file. 10=Specify data conversion Specify data conversion options for moving data in a data library or Production library into a changed physical file. or source member.” starting on page CG 3-35 for more information. or an object's source to a different library group. A confirmation panel displays. 4=Delete Delete one or more copies of the object from the release using the confirmation panels discussed in “Cancelling Checkouts and Deleting Objects. 9=Move/Define Move an object to a different library group.” authority to the environment containing the copy to be deleted. 6=Print source Print source for the object 7=Promote* Promote the object forward to the next environment using the Promote Objects panel. For moving groups of objects.” starting on page DO 3-45..3=Check out Copy the object to a developer for modification using the Check Out Objects panel. and deployment sets with which it is associated. 5=Browse source Browse objects using the browse tool specified for the selected object. 8=Display attributes Display the description of the object as registered in the Aldon LM(i) database. 11=Print attributes Print a description of the object’s status in the release including environments and libraries containing copies. see “29=Move/Define (library groups)*” below. You must have “Perform promotion to. See “To specify data conversion options in advance. Options 41 and 42 read this information from the Aldon LM(i) database to locate all objects dependent on a selected object. 15=Change create options Change the Aldon LM(i) database records controlling how the object is created using the Change Object Creation Options panel. 13=Request checkout* Create a request for checkout for the object using the Request Checkout panel. 19=Alternate edit Edit source for the object using the secondary editor specified for the selected object. 20=Scan for requisite objects* Scan an object to identify the other objects it requires for its creation and functioning. SQLCBL. Control the editor used through development tool definitions and development tool usage defaults.12=Work with conflicts View all conflicts pending for that object on the Work with Conflicts panel. 18=Work with tasks Displays tasks associated with the selected object on the Work with Tasks panel. • Specify the existence of and location of pseudo-source for a non-source object • Change the data option of an object 17=Request promote* Create a request for promotion for the object using the Request Promote panel. Aldon LM(i) Daily Operations Reference Using Aldon Lifecycle Manager (System i Edition) • DO 2-11 . 14=Create* Create the object in place using the Create Objects panel. You can: • Assign an attribute such as RPT. 16=Change Use the Change Checked Out Object panel to change the description of an object in Development in the Aldon LM(i) object database. or PLI38 to an object • Change the extended attribute of an object to indicate whether or not it uses the ILE program model. 30=Display log Display development log entries for the object using the Display Development Log panel. 27=Promote to parent* Promote an object from a child or Delta release to its parent or ancestor release. 37=Request promote to parent* Request promote an object from a child or Delta release to its parent or ancestor release. what overrides are to be applied prior to executing the create command for the object. 29=Move/Define (library groups)* Change the object and source library group assignments for a group of objects. 35=Compare Compare two different copies of an object using Aldon’s Harmonizer or Harmonizer (Windows Edition) comparison utility. You must have an installed copy of Harmonizer or Harmonizer (Windows Edition) defined to Aldon LM(i) to use this option. as it is promoted or deployed. 25=Retire Retire object flags an object as deleted so that.23=Check out (emergency)* Copy the object from Production to a developer for emergency modification.” starting on page DO 3-21 for more information. DO 2-12 • Using Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . When an object is retired. See also “9=Move/Define” above. any other version of the object existing in a later environment or an ancestor release becomes invisible during execution. 32=Change create overrides Object create overrides specify for individual objects. 28=Work with conditions Display requests and conditions pending for the selected object on the Work with Requests and Non-Conflict Conditions panel. See “To promote individual objects to parent. the target object is made inaccessible. 24=Work with archive Display information about archived copies of the object on the Work with Archive Objects panel. 44=Work with deployment sets Displays the Work with Deployment sets panel. The Select Environments for Deploy Objects panel displays if deployment profiles are defined for more than one environment for each selected release. the dependent objects for each appear on separate panels. Any failure causes the entire group of changes to be backed out. 41=Act upon dependent objects Locate objects which depend on the selected object for creation or functioning. If several objects are selected together with this option. Once identified. 47=Install live* Copy the object from Aldon LM(i) test or Production libraries to additional libraries for testing or Production use. Aldon LM(i) Daily Operations Reference Using Aldon Lifecycle Manager (System i Edition) • DO 2-13 . dependent objects may be acted on using all available options. 45=Assign binding directories Work with binding directory/program associations for a binding directory or ILE program using the Work with Binding Directories panel.39=Display requisite objects Display a list of objects required by the selected object for creation or functioning on the Display Requisite Objects panel. The displayed objects are requisites of the selected object. Once identified. 42=Act upon dependent objects* Locate objects which depend on the selected object for creation or functioning. For more information. 40=Define requisite objects Manually specify additional objects as requisites of the selected object using the User-Defined Requisite Objects panel. 50=Merge into parent* Merge an object from the production environment of a child release to the production environment of the parent release. 48=Deploy* The Work with Deployment sets panel displays if objects of more than one release are selected. Install live can copy the object to additional libraries locally on the host system or to libraries on one or more remote systems. dependent objects may be acted on using all available options. Install live provides a way to group objects so that they are installed as a unit. see “Merging Objects into a Parent Release” on page DO 3-25. Use option 12 to access the Work with Requests and Non-Conflict Conditions panel for a specific object. for promotions. the work with Developer Objects panel. F17=Subset Subset the Work with Objects by Release panel using the Subset Objects by Release panels shown in Figure 9 on page DO 2-15 and Figure 10 on page DO 2-17. use option 3 or 7 from this panel to check out or promote objects. See the “Defining Users. create the requests from this panel with options 13 and 17.” starting on page SA 3-1 for more information on request requirements.57=Request install live* Create a request for install live of an object. DO 2-14 • Using Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . You can require some users to create requests to check out or promote an object and allow others to check out and promote without requests. or. 99=Display LM(i) blocking where used. F6=Add Object Add an object not previously defined to the application to this release using the Add Release Object panel shown in Figure 41 on page UG 5-4. Access this function by pressing F6 on the Work with Tasks panel.” Descriptions of function keys available on the Work with Objects by Release panel that are unique to this panel or to Aldon LM(i) are described below. Request requirements never apply to emergency checkouts which are controlled with a separate authorization. the Work with Requests and Non-Conflict Conditions panel. XX (User defined PDM-Style options) This panel supports use of PDM-Style options created by the user and defined to Aldon LM(i). If you opted not to use requests for checkouts or promotions. To fulfill those requests.. General purpose function keys are described in “Appendix B: The Panel Interface. You can require requests for promotions into some environments and allow promotions into other environments without requests. Use of this option on an object of the release results in a list of all objects defined to LM(i) that use the selected object as a blocking object or source. If you opted to require checkout or promotion requests.. use the Work with Tasks panel. For more information. see “Overview of Blocking Objects and Source” starting on page UG 5-17 in the “Aldon LM(i) User’s Guide”. F7=Add Task Define a new task for organizing development work using the Define Task panel shown in Figure 32 on page UG 3-8. *ALL. . Press PAGE DOWN to display the second page of the Subset Objects by Release List panel. . . . In environment . *BLANK + *USERDFT. . . . *PARLENV. name 1=All. name + *USERDFT. *NA Release . *CRTNONRES. . Developer designation. *USERDFT Application . name. F21=Print Print the currently selected list of object records as a report using a confirmation panel similar to the panel shown in Figure 43. F20=Conditions menu “Hot key” to the Work with Requests and Non-Conflict Conditions panel shown in Figure 27 on page UG 2-52. . . . . *USERDFT. Select as true for . View 1 of 2 The Select as true for field modifies the meaning of the “In environment” parameter specified on the line above. . *EXPAND. CSBSOBJREL Subset Objects by Release List Type choices. QUA Dvp:*NONE Tsk:*NONE F12=Cancel F22=More functions Figure 9 . 2=Res only. .” on page DO 6-3. name + *NA. . generic*. . *USERDFT. . Specify 1 to include a record in the display if any copies of the object in a release are present in the selected environment(s). type + *NA. *NAMED. . . . . generic*. . press F17 to work with the Subset Objects by Release List panels shown in Figure 9 on page DO 2-15 and Figure 10 on page DO 2-17. . . *NA 1 *NA *NA 1 *ALL *NA. . *ANY. . . . Set selection criteria as desired and press Enter. name *STD.Subset Objects by Release List. . .F19=Work with tasks “Hot key” to the Work with Tasks panel shown in Figure 36 on page UG 3-13. Use these panels to select object records for display on the previous panel. D/I/Q/P 1=Any copy. . ITG. The previous panel displays with only those records meeting all selection criteria. generic*. . . generic*. . name *ALL. *ALL + Object attribute . press Enter. . . *ALL. Aldon LM(i) Daily Operations Reference Using Aldon Lifecycle Manager (System i Edition) • DO 2-15 . *SHARED DVP. . . . . name + *USERDFT. generic*. . *ACT. 3=Non-res only Object type . generic*. . Residence status . Subsetting a “Work with” Panel To limit the object entries displayed on the Work with Objects by Release panel. *USERDFT Group . *ALL. Included in task . Object . . . . . . *NOT. *STD *PARLENV environment User defaults: Rel:ALDON/DEMOAPP/BASE1 F3=Exit F4=Prompt F5=Refresh *ALL. Specify 2 to require that all copies of the object in a release be present in the selected environment(s). . “Confirm Print of List Panel. . 2=Every copy + *NA. *USERDFT Release view . . or QUA that is to be used to decide the environment of the parent copy. 47 (Install live). DO 2-16 • Using Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . Enter a 2 for “Select as” to exclude the record because a copy exists outside of Production (the object also exists in Quality Assurance). application. ITG. only options 8 (Display attributes). When release view is set to *PARLENV. 30 (Display log). release. Enter a 1 for “Select as” to include the record because a copy is present in Production. You cannot change your user default release when this subset view is active. You must specify a *PARLENV environment of either DEV. and deployment. The purpose of the view is informational and allows selection for install live. When the subset is in effect. In the Residence status field. and group by pressing F22=More functions. select one of the following: • 1 = All— Creates both non-resident and resident objects • 2 = Res only— Creates only resident objects • 3 = Non res only— Creates only non-resident objects The Release view field controls whether or not records display for ancestors of a release that contain earlier versions of the same objects or contribute production copies of objects not contained in production libraries of a local release. Set “In environment” to “P”. and 57 R(equest Install Live) are available. This view can only be selected when subset to a single release and only shows test environment letters if the selected release (or one of its ancestors) has the option Include parallel environments of parent release for creates set to Y (Yes). Q. Set *USERDFT values for task. install live. *PARLENV (parallel environments) setting causes the RL (Related Releases) column to show the environment letter (I. developer.Example: Object DEMOCBL1 is present in a release in the Quality Assurance and Production environments. if there is not a copy of the object in the production environment of the selected release. or P) of the ancestor copy to be used for creates. the *PARLENV environment field must also be filled in. library group *NA. At the second page of the Subset Objects by Release List panel. More: Has condition category Include retired objects Retired as seen from environment . *UNDEFINED. .Subset Objects by Release List. and *PARLENV environment set to ITG. For more information about parallel environments of parent release. DVP.Objects that are not normally visible may appear in the list. *ONLY *ANY. see “Parallel Environments of Parent Releases” starting on page CG 1-6 in the “Aldon LM(i) General Topics Reference”. From the standpoint of DELTA2. If the *PARLENV environment is set to DVP then X appears. ITG. object X does not exist. QUA. *ANY. *NO. View 2 of 2 The Include retired objects field specifies whether retired objects are to be included in the resulting list. library group F3=Exit F4=Prompt F5=Refresh F12=Cancel F22=More functions Figure 10 . release view set to *PARLENV. Library group: Object Source *NA *NA *ANY *NA *NA + *NA. Aldon LM(i) Daily Operations Reference Using Aldon Lifecycle Manager (System i Edition) • DO 2-17 . . The Display Attributes function (option 8) shows the same parent production copy as shown on the list when requested from the *PARLENV view. If this is not PDN. A/C/F/H/R *NA. CSBSOBJREL Subset Objects by Release List Type choices. enter the desired criteria. *ANY. but if *PARLENV environment is set to QUA. PDN + *NA. then X would not appear because the ITG environment is not included when compiling or deploying from the QUA environment. *NOT. as in the following example: D I Q X P BASE release DELTA1 release (include parallel environments of parent) DELTA2 release (not include parallel environments of parent) If the list is subset to DELTA2 release. press Enter. then object X. a special note is made. that exists only in ITG of BASE appears in the list. or both. press F4 (Prompt) to select a library group from a list.• *NA— Include all retired objects in the subset it they meet the other selection criteria • *NO— Exclude all retired objects from the list • *ONLY— Only show retired objects in the subset list The Retired as seen from environment field qualifies the Include retired object selection by defining what environment you want the retired objects to apply to: • *ANY • DVP • ITG • QUA • PDN For example. DVP. ITG. you can subset by object. In the Library group field. if the object has been checked out and retired. it does not show as retired. If you are already requesting a subset to a single release. but if you are viewing from PDN. Enter the library group number 01 to 99. source. but the retire has only been promoted as far as QUA then the object would be seen as retired if you are viewing from the *ANY. or QUA. DO 2-18 • Using Aldon Lifecycle Manager (System i Edition) Aldon LM(i) Daily Operations Reference . ” starting on page DO 3-19 • “Merging Objects into a Parent Release. and requirements for object movement in Aldon Lifecycle Manager for System i (Aldon LM(i)). This chapter also describes how to work with less commonly used functions. This chapter includes the following topics: • “Checking Out Objects.” starting on page DO 3-45 • “Deleting Archived Objects. options.” starting on page DO 3-38 • “Modifying and Testing ILE Objects. and function keys displayed or available at any of the panels shown in this document.” starting on page DO 3-2 • “Promoting Objects.” starting on page DO 3-10 • “Emergency Checkout and Promotion. options. Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-1 .” starting on page DO 3-44 • “Cancelling Checkouts and Deleting Objects.” starting on page DO 3-18 • “Moving Objects to a Parent Release.” starting on page DO 3-25 • “Installing Live. See the “User's Guide” for a basic conceptual overview and step-by-step instructions for more commonly used object movement functions. please see the online help text. rules.” starting on page DO 3-46 Online Help Text For detailed descriptions of the fields.” starting on page DO 3-29 • “Changing an Object’s Production Location.Aldon LM(i) Daily Operations Reference Daily Operations DO Chapter 3 Moving Objects This chapter provides detailed conceptual overviews and discusses functions. Also. When invoked. the checkout function locates the most recently modified copy of an object and copies it to the Development library associated with a designated developer. You can only modify source in the Development environment. and Production. The checkout function insures that only authorized users check out source code and tracks object movement to insure that changes within a release are performed cumulatively rather than in parallel. Copies of an object may exist simultaneously in Development. Quality Assurance. the ACMSCHKOUT command. 8. Quality Assurance. Many functions described in this chapter may also be performed with commands or “user-defined” PDM options provided by Aldon. Addition of these libraries to the system portion of the library list by the user is contrary to the design of Aldon LM(i) and may cause serious problems. use the emergency checkout to obtain the Production copy of the object regardless of other copies that may be active. 10. Integration. If you have not yet read the “User’s Guide” and “Overview of Aldon Lifecycle Manager (System i Edition). 11. Alternate Interfaces Checking Out Objects Overview Aldon LM(i) provides controlled access to source code through use of a checkout function. Aldon LM(i) automatically manages the library list for checkouts by adding and then removing libraries for Integration. To fix an urgent Production problem. please do so.Assumed Background Understanding This chapter assumes a basic understanding of Aldon LM(i).” Access the checkout function using the panel interface. See “Chapter 1: Library Lists” in the “General Topics Reference” for more information. and 12 in the “Setup and Administration Reference” describe the procedures for application and release definition.” starting on page DO 1-1. or user-defined PDM options. you must define the application and release you are working with before performing any of the functions described in this chapter. Chapters 7. See “Appendix F: PDM-Style User Options” and “Command Interface. and Production as necessary. DO 3-2 • Moving Objects Aldon LM(i) Daily Operations Reference . the ACMSCHKFRN command.” starting on page CG 7-1 of the “General Topics Reference” for details. Objects requested for checkout that are not yet present in the release are obtained from the Production environment of the closest ancestor release. see “Defining Users. The ACMSCHKFRN command adds special checkout access to objects in libraries outside of Aldon LM(i). Unless multiple checkout is allowed for the release. If a developer is likely to work on copies of the same object from different releases at the same time.or release-level developer definitions as described in “Chapter 9: Application Authorities and Developers” and “Chapter 18: Working with Releases” in the “Setup and Administration Reference. Quality Assurance. The user performing the checkout must have *ALL authority to the developer's source library. an object that is already in Development for a given release cannot be checked out again for that release until the Development copy is promoted back into the first Aldon LM(i) testing environment.” Eligible Agents: Authority to Request or Perform Checkouts Grant authority to request or perform checkout operations for the entire system or for each application. See the section “Defaults for New Releases” in “Chapter 2: Standard Global Setup Functions” of the “Setup and Administration Reference” for more information on request requirements.Eligible Objects Objects in Integration. and Production are eligible for selection by the checkout function. Objects are always eligible for emergency checkout by users with the appropriate authority. ancestor release Production environments are included in the library list for checkouts. Both source-based and non-source objects are eligible for checkout.” starting on page SA 3-1. Eligible Recipients All developers defined to Aldon LM(i) are eligible to receive objects through checkout from any Aldon LM(i) release. Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-3 . If the release has ancestors. specify libraries different from those specified by a developer's global developer definition for a given application or release using application. For information on defining developers. Aldon LM(i) copies source from the Production environment. Object Movement on Checkout Emergency checkout always takes Production copy Standard checkout takes copy closest to Development Development Integration * Quality Assurance * Production * These environments optional at release setup. the checkout function copies the actual object to the object library for the selected developer to serve as model for the new copy of the object. • When you check an object out with the emergency checkout function. There are two types of checkouts: standard and emergency. The object corresponding to the source is not copied since it is assumed that the source is being checked out for modification and will be compiled to create a new copy of the object. • A standard checkout obtains source from the environment closest to Development. Figure 11 . Aldon LM(i) searches the release's environments in sequence from Integration through Quality Assurance. For non-source objects.Object Flow Checkout copies an object's source from testing or Production to Development.Object Movement on Checkout DO 3-4 • Moving Objects Aldon LM(i) Daily Operations Reference . This search sequence insures that the first copy encountered contains all modifications that have been made to the object. Figure 11 on page DO 3-4 illustrates object flow for standard and emergency checkouts. The two types differ in the environment from which objects are checked out and in the way objects checked out are later promoted. The exception being objects specified with data option 2 (promote data) when both the source and the object (including all data) are copied to the appropriate development libraries. even if there is a more recent active copy of the object. and Production. For source-based objects. the checkout function copies source for the selected object to the source library for the selected developer. the object is copied to the library without data. Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-5 . Aldon LM(i) creates one. If you do not use checkout requests. If a source file of the correct type does not exist. Hint For non-source SQL objects. just the source is copied to the development environment library. you can allow some users to request checkout operations and others to actually perform them. you may want to require requests. You can perform emergency checkouts without requests even if you require requests for standard checkouts. Check Out With or Without Requests The procedures for checking out objects vary depending on whether you use checkout requests. The second is the fulfillment of that request. If the data object is set to Promote Data. just the source member is copied to the Development library. • Check out of Data Objects— If the data object is set to Keep Destination Data. and sets *USE as the *PUBLIC authority. • Checkout of SQL Objects— If the SQL object is defined with pseudo source. In the case of a non-source based object. If there is no source defined to Aldon LM(i). the movement process is separated into two steps.Ownership and Authority For most checkouts. For more information about the movement of data. Data Libraries. you can still use option 5 to browse the source that Aldon LM(i) generates for you or use option 43 (Generate SQL pseudo source) to generate the source and change the object to use pseudo-source. If you use checkout requests. You can require some users to create requests to check out objects and can allow others to perform checkout operations without requests. assigns ownership to the user specified as Owner of objects in the description of the receiving developer. For more information see “To create pseudo-source for an existing SQL-based object” starting on page UG 5-7 in the “Aldon LM(i) User’s Guide”. Aldon LM(i) creates a member in an existing source file in the developer's library. The first step is the creation of a request. the object is copied to the library with all its data as well as the source. If you want to allow developers to request that objects be checked out to them. a single operation checks out objects. If you use requests. but want a development manager or librarian to actually review the requests and perform the checkout operations. see “Data. and Data Sets” starting on page CG 3-1 in the “Aldon LM(i) General Topics Reference”. This occurs because there are many SQL objects that cannot be copied to a different environment with the CRTDUPOBJ command. the checkout process simply marks the object as checked out but does not copy/create the object in the development environment library. Users with “Change task definition” authority can add objects to an existing task or define a new task when requesting or performing a checkout. See “PDM-Style User Options.Check Out With or Without Task Association You can require a task identifier to complete a checkout. Available Interfaces Request checkouts through the Aldon LM(i) panel interface or with Aldon-supplied PDM user options. See Figure 7. For example. View 1 of 3. Aldon's user defined options also work with Hawkeye's Pathfinder cross-referencing and documentation tool.” starting on page DO D-1 for a discussion of the PDM interface. See Figure 19. Aldon LM(i) sets the value of the task for checkout according to the task that is selected on Work with tasks or to the subset criteria for Work with objects by release or developer.” on page DO 2-6 • Work with Objects by Developer using option 13. if you enter Work with tasks. If a task identifier is required. “Work with Objects by Release. ACMSCHKFRN. Complete checkouts through the Aldon LM(i) panel interface with the Checkout command. Selecting Additional Dependent Objects Aldon LM(i) object referencing features may be used to identify all objects dependent on those objects initially selected for checkout. or with Aldon-supplied PDM user options. ACMSCHKOUT. the object must either already be part of a defined task at checkout. Checkout Foreign command. The following sections describe the panel interface and System i commands. To create checkout requests You can create checkout requests from: • Work with Objects by Release using option 13 (Request checkout*). and facilitates implementing changes by speeding the checkout process. select option 12 (Work with objects) to work with the objects for the task. This allows assessment of the impact a change will have on other portions of the application before the change is undertaken. the object must already be included in the task they enter on the checkout panel.” on page DO 4-2 DO 3-6 • Moving Objects Aldon LM(i) Daily Operations Reference . “Work with Objects by Developer Panel. or it must be added to a new or existing task at checkout. then request a checkout. View 1 of 4. For users without this authority. the task for the checkout operation defaults to the one you originally selected. “Work with Tasks panel. . This panel lists the objects selected and provides fields for entering the developer to receive the objects. . . . . View 1 of 5. Change printer file Objects selected for request checkout: Object Type Release DEMOCBL2 *PGM ALDON/ACMSDEMO/BASE + Name + Name 1 objects selected for request checkout. . Roll Down or F20 to view additional objects in the list. F3=Exit F4=Prompt F7=Add task F16=Act upon dependent objects F20=Enlarge list F12=Cancel F22=More functions Figure 12 . . To developer . . . To deploy objects in a single task among several developers. . . PHILV For task . press Enter. Type 13 by one or more individual objects or tasks. Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-7 . . See Figure 2.” on page DO 3-7. “Request Checkout panel. Press F4 with the cursor in the To Developer field for a list of existing values. .” on page TT 3-4 1. On the Work with Objects by Release panel. select the task with option 12=Work with objects instead of option 13 to display objects in the selected task on the Work with Objects by Release panel. Press Page Up. CRQSCHK Request Checkout Type the additional checkout information below. 2. Complete these fields and press ENTER to create checkout requests for the objects listed. Comment for log . . All objects listed on the Request Checkout panel will be requested for checkout to this developer. and a comment. all the objects in a task must be assigned to the same developer. .Request Checkout panel To developer Type the developer name for the developer to whom you want the objects checked out. . . . If you select several tasks for checkout requests on the Work with Tasks panel. . 3. . 4.• Work with Tasks panel using option 13. . Press ENTER to display the Request Checkout panel shown in Figure 12. When selected by task. . . . . . . . select individual objects in the task for checkout requests with option 13. . each task appears on a separate Request Checkout panel. a task with which the objects are associated. Aldon LM(i) sets the value of the task for checkout according to the task that is selected on Work with tasks or to the subset criteria for Work with objects by release or developer. Selecting a task selects all objects associated with the task. “Work with Requests and Non-Conflict Conditions panel. the name of the task with which you are working is displayed and cannot be changed. After making your checkout selections. View 1 of 4. Comment for log Type a comment that describes the reason for the checkout operation.” on page DO 2-6 • Work with Objects by Developer panel shown in Figure 19. View 1 of 5.” on page DO 4-2 Select one or more objects with checkout requests pending on the Work with Requests and Non-Conflict Conditions panel. press ENTER to display the Checkout Objects panel. “Work with Objects by Developer Panel.” on page DO 5-4. Checking out Objects Fulfill checkout requests and checkout objects directly without checkout requests with option 3 (Checkout) from one of several panels. if present. “Work with Objects by Release. Select one or more individual objects on the: • Work with Objects by Release panel shown in Figure 7. View 1 of 3. “Work with Tasks panel. shown in Figure 33. For each task you can specify a separate developer and checkout parameters. Create a new task by pressing F7.” on page TT 3-4. This comment is written to the development log. If you selected a task for checkout requests on the Work with Tasks panel. DO 3-8 • Moving Objects Aldon LM(i) Daily Operations Reference .or application-level options settings may require association of objects with a task for completion of a checkout. identify the task to which the object belongs or to which it is to be added. Press Enter to request checkout of the selected objects. is enforced when checkouts are completed.For task If you selected individual objects on the Work with Objects by Release or Work with Objects by Developer panels. The Task field is optional for checkout requests. but the requirement. Global. Select one or more tasks on the Work with Tasks panel shown in Figure 2. . . Objects checked out with the emergency checkout function return directly to Production when promoted from Development bypassing all testing environments. 3. “Work with Objects by Release. .” on page DO 2-6 • Work with Tasks panels. Aldon LM(i) moves source. . At the Transfer Objects panel. press Enter. “Work with Tasks panel. . . . and object. Press ENTER to complete the transfer. At the Work with Objects by Developer panel. . type the name of the developer to receive the transferred objects. . . if available. . . See Figure 7. . View 2 of 5. . 2=Run in batch N 1 Checkouts selected for transfer: Object HIWORLDCL Type *PGM Attribute CLP Release MARKE/MDE720/DELTA1 From Developer MARKE 1 objects selected for transfer. . . Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-9 . press ENTER to display the Emergency Checkout panel. . . Emergency Checkouts To request emergency checkout of the selected objects. . . . Print transfer report .Transferring Objects Between Developers To transfer an object from one developer to another. To transfer checked out objects between developers 1. if available from the current developer's source and object libraries to the new developer's source and object libraries. To developer . use option 23 (Check out (emergency)*) on the: • Work with Objects by Release panel. . . View 1 of 3.” on page TT 3-5. . . + Name Y=Yes. in the To developer field. The emergency checkout function always obtains source from the Production copy of the object regardless of any active copies that may exist. . . . . . The Transfer Objects panel displays: CTFROBJ Transfer Objects Type the additional transfer information below. F3=Exit F4=Prompt F12=Cancel F15=Full name F20=Enlarge list F22=More functions 2. . After selecting objects. N=No 1=Run interactively. See Figure 3. select the objects you want to transfer with option 26 (Transfer*) and press ENTER. . . . Run option . Comment for log . . Recommendation If you check out a physical file to a child release. Eligible objects Conflict free objects in active environments are eligible for promotion. and that physical file has logical files over it. Checkout of an object when a copy already exists in the development environment (this can only happen if multiple checkouts are allowed).” Access the promote function using the panel interface. In every standard promote. These events cause Aldon LM(i) to create a conflict condition: 1. Aldon strongly recommends that you also checkout any logical files built over that physical file. the command interface. the promoted source and objects move forward to the next environment. An object checked out with the emergency checkout function moves from Development directly into the Production environment on promotion. and Production as necessary. See “Chapter 1: Library Lists” in the “General Topics Reference” for more information. any movement forward from development or testing toward Production is a promotion. some care must be taken to ensure that relationships of logical files to physical files are maintained. Quality Assurance. Aldon LM(i) automatically manages the library list for promotes by adding and then removing libraries for Integration. Addition of these libraries to the system portion of the library list by the user is contrary to the design of Aldon LM(i) and may cause serious problems. Aldon LM(i) may also fail to recreate the modified physical file in data sets associated with the child release. 2.Checking Out Files for a Child Release If you are developing using multiple releases and are checking out files. you may receive level checks or other undesirable results later. Promoting Objects In Aldon LM(i). or the user-defined PDM options provided by Aldon. bypassing any intervening test environments. If you do not check out the logical files. Emergency checkout of an object already active or in development (promotion or the pre-existing active copy is blocked). DO 3-10 • Moving Objects Aldon LM(i) Daily Operations Reference . An object with a conflict condition pending cannot be promoted until the condition is cleared. Conflict Conditions panel (Figure 33. If you are working with multiple releases of an application. Since the update failure may have affected testing of the file. Data Libraries. request an update of the data libraries.” starting on page SA 11-1 • “Overview of Release Functions” starting on page SA 13-1 in the “Aldon LM(i) Setup and Administration Reference” Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-11 . see “Data. check to insure that the file has been tested correctly. Remove the condition using the Work with Requests and Non. To clear a data update failure. “Work with Requests and Non-Conflict Conditions panel.” To clear a multiple checkout or emergency checkout conflict condition. Objects checked out with the emergency checkout function can be promoted without requests even if you require requests for standard promotions.” on page DO 5-4).” on page DO 5-8) and merge the changes. Unsuccessful attempt by Aldon LM(i) to update a data set for which Monitor for update errors is set to Y (Yes) during promotion of a file. and Data Sets” starting on page CG 3-1 in the “Aldon LM(i) General Topics Reference”. Clear the conflict and promote the object containing the merged changes. examine the versions of the object in conflict as indicated by the Work with Conflicts panel (Figure 34.3. “Work with Conflicts Panel. 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. 4. changing the production copy of an object or checking an object out for modification in one release creates a conflict condition on each copy of the object in each “notified release. For more information. For more information see: • “Working with Users and User Classes” starting on page SA 3-2 in the “Aldon LM(i) Setup and Administration Reference” • “Specifying Application Authorities. For more information see “Allow promotes with conflicts to” starting on page SA 2-11 in the “Aldon LM(i) Setup and Administration Reference”and consult your Aldon LM(i) administrator. for the entire system or for specific applications or releases. Eligible Agents: Authority to Request or Perform Promotes Grant users authority to request or perform promotes by environment. Object Flow A standard promotion moves an object from its current environment towards Production one environment at a time. Session Protection To protect active jobs that might be using programs deleted or replaced by promotion.Object Movement on Promotion During a promote. If there is a copy of the object and source in the “to” environment that would have been replaced by a successful promotion. If a promotion is unsuccessful. deleting an active copy on checkout. source and object remain in the “from” environment. DO 3-12 • Moving Objects Aldon LM(i) Daily Operations Reference . Aldon LM(i) moves source and object from the “from” environment to the “to” environment.) For details on use of QRPLOBJ by Aldon LM(i) see “Aldon Lifecycle Manager for System i Technical Details. installing a deployment on a remote system. replacing objects with the Load function. Aldon LM(i) copies old versions of programs to the IBM managed library QRPLOBJ before deleting them after a successful promotion. Moving Use release-level options to specify whether to recompile source on promotion into each active Aldon LM(i) environment or move the existing objects and associated source without recreating objects. (Aldon LM(i) also copies old versions of programs to QRPLOBJ when creating in place. Standard Promotions Development Integration* Quality Assurance* Production * optional environments Emergency Promotion Figure 13 . it remains intact. Figure 13 illustrates object flow for standard and emergency promotions.” starting on page CG 6-1. Creating vs. Promotion of an object checked out with the emergency checkout function moves the object directly from Development into the Production environment. If the promote is successful. Aldon LM(i) removes the promoted source and object from the “from” environment when the promotion completes successfully. and when deleting objects from a release. Set defaults for the release-level options at the global and application level.” Source members that are not associated with a specific object (for example. the library list for creating objects promoted to Quality Assurance includes Quality Assurance and Production libraries. Unique user or software vendor supplied create commands can be defined to Aldon LM(i) at the global or application level. Quality Assurance. You can add libraries that are not a part of your release to the end of the compilation library lists by changing the job description used by the promotion jobs. (If you are not using some of the optional environments. copy members) and non-source objects are promoted without compilation regardless of your option settings. Aldon LM(i) uses either the IBM supplied create command for the object type and attribute or a user defined create command. See the section “Production Environment Options” in “Chapter 2: Standard Global Setup Functions” and the section “Specify Default Options for New Releases” in “Chapter 8: Defining a New Application. Creating on Promotion When you create objects on promotion. The library list for creating objects on promotion to Integration includes Integration. and Production libraries. The constructed list uses and prioritizes libraries from the different Aldon LM(i) environments to reference appropriate copies of each source member and object during compilation. Aldon LM(i) constructs a library list to use for the creation job. To re-create objects on promotion.) Under the same conditions. The library list used to create objects on promotion to Production includes only Production libraries. the corresponding libraries do not exist and are not included in the list.” Note Use of qualified names to find copies of referenced objects in specific libraries instead of relying on the library list is contrary to the design of Aldon LM(i) and is not recommended. See “Chapter 19: Custom Object Creation Setup” and the section “Defining Custom Create Commands” in “Chapter 10: Working with Applications” for more information on defining create commands. See “Creating Objects with Shared Applications” starting on page CG 1-11 in the “Aldon LM(i) General Topics Reference” for information on sharing programs and files among multiple applications automatically through definition of a “shared application. Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-13 . select. in sharing releases of other applications. This is due to the fact that the referenced objects in the testing library list may be different from the ones used for compilation. Dependent Objects Aldon LM(i) object referencing features may be used to avoid level checks. you may experience level checks and unpredictable results when testing in the “to” environment. you can locate. if the promoted object is in a shared application. you may still experience level checks. Level Checks If you create objects as you promote them forward. This uses less system resources than for compilations. For example. or release-level. and you promote one object. Re-creating objects on promotion ensures that matching source and objects are kept together. For IBM supplied create commands. and increases the probability that copies used for testing are also used for re-creation. existing objects move forward with the source. Eliminate level checks in this type of situation by compiling the program in place with option 14 (Create*) on the Work with Objects by Release panel. if an object that depends on changed objects in the “from” environment is moved forward without those referenced objects and is not recreated in the “to” environment. and. you promote a program and then a display file that is used by that program. The program was compiled with the older copy of the display file. then you promote an object that it references or depends on. If object dependency data is kept current. Set command parameter values for a specific copy of an object as described in “Single-Copy Create Specifications” on page DO 4-16. DO 3-14 • Moving Objects Aldon LM(i) Daily Operations Reference .With either type of command you can use creation parameter defaults set at the global. or you can set the command parameter values for that specific copy of the object prior to the promotion. application. and recreate dependent objects automatically or manually during promotion or select a promoted object with option 41 or 42 to locate and recreate dependent objects after promote completes. For custom create commands Aldon LM(i) must use your defaults. Moving on Promotion If you direct Aldon LM(i) not to create new copies of objects on promotion. in other descendent releases. Aldon LM(i) can locate and recreate dependent objects in the same release. However. you can direct Aldon LM(i) to use the command parameter values that were used to create the copy of the object you are promoting. If a link between a physical file inside Aldon LM(i) and a logical file outside of Aldon LM(i) is found. Data Option Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-15 . For more information see the online help for the Leave resident field on the Promote Objects panel (“To promote an object” starting on page UG 2-25 in the “Aldon LM(i) User’s Guide”). Recreate the logical outside of Aldon LM(i) after promotion has completed. Aldon LM(i) can use the defaults that work well for many sites to set ownership and authorities or Aldon LM(i) can set them based on specially created or existing copies of the objects you have specified as reference objects.” Physical Files and Tables Associated Files As you promote a physical file or table.” starting on page CG 2-1. see “Promote with Data” on page IN 3-16 in the “Aldon LM(i) Installation and Upgrade Guide” and “Data Option” on page DO 4-14 in the “Aldon LM(i) Daily Operations Reference”. Ownership and Authorities When you promote an object. and reference libraries to set ownership and authorities. 8. For more information about data options. To complete the promotion. see “Ownership. it checks for links to logical files outside of Aldon LM(i).Leave resident option You can also elect to leave a copy of objects resident in the Promote from environment when you promote them. Aldon LM(i) performs additional steps to ensure that any associated logical files that reference it can be used for testing with the new physical file. exit Aldon LM(i) and eliminate the link by deleting the logical. When Aldon LM(i) promotes a physical file. Authorities. Aldon LM(i) blocks the promotion and issues an error message. if you wish. Aldon LM(i) assigns an owner to the copy of that object in the “to” environment and sets authorities to control access to it. You may want to leave copies resident on promote if you need a full set of objects to perform testing in a development or testing environment. and Reference Libraries. and Production environments. Return to Aldon LM(i) and complete the promotion. For details on the use of Aldon LM(i) defaults. Data is copied on promotion depending on the data option set for the file. reference objects. and also Chapters 2. and 12 in the “Setup and Administration Reference. You can selectively leave objects resident if objects dependent on them are remaining in the environment. Note The leave resident function is not supported for the Development environment. This prevents unauthorized changes to source members and objects in the Integration. Quality Assurance. For more information about installing live. Install live is used in conjunction with the promote function. but the data in any attached data set is preserved. see “Installing Live. DO 3-16 • Moving Objects Aldon LM(i) Daily Operations Reference . For example. If the data object is set to Promote Data. Handling Data on Promotion When promoting a data object with the default setting of Keep Destination Data. Aldon LM(i) performs additional steps to ensure that it does not point to a physical file in another environment. The exception being on promotion to ITG or QUA where no data is preserved in the environment libraries. Optionally. when you promote objects forward from Integration to QA. Data Libraries. Deploying on Promote Once objects have been changed. or Production to place objects on a remote processor for integration or quality assurance testing or for production use.” starting on page DO 3-29. and Data Sets. logical files are recompiled upon promotion rather than moved regardless of the value entered for the move/compile option.” starting on page CG 6-1 for important information about physical and logical file handling in Aldon LM(i). a user supplied conversion program can be executed to update the existing data to the new format. you can simultaneously initiate install live of the same objects into the QA install live target.” starting on page CG 3-1 for more information. they can be promoted using either the deploy on promote or install live on promote function. Quality Assurance. See “Data. When necessary. For more information about object deployment. Aldon LM(i) either updates the existing data with the new format or if the file does not exist. see “Object Deployment” starting on page UG 3-6 in the “Aldon LM(i) User’s Guide”. See “Aldon Lifecycle Manager for System i Technical Details.Logical Files When you promote a logical file. both the environment library and any specified data set libraries are updated with the new data object format and all existing data is replaced with the data from the from environment library. You can deploy objects during promotion to Integration. creates an empty copy of the file. Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-17 . you could allow promotion into Integration without a prior request. For example. Perform promotes through the Aldon LM(i) panel interface with the Promote command. Available Interfaces Request promotes through the Aldon LM(i) panel interface with the Request Promote Objects command. or with Aldon-supplied PDM user options. Aldon LM(i) can automatically update cross-referencing files each time a job promotes objects into Production. a single step promotes objects. but could require a request for promotion into the Quality Assurance environment. If you require promotion requests. the promotion process is separated into two steps. The second is the fulfillment of that request. Promotion With or Without Requests You can set release options to require promotion requests prior to actual promotion into some or all of the environments for a release. If you use requests. ACMSPROMOT.” starting on page CG 7-1 for a discussion of the Command interface. ACMSRQSPRM. If you do not require promotion requests. Refer to the section “Production Environment Options” in “Chapter 2: Standard Global Setup Functions. see “ABSTRACT/PROBE+” starting on page TI 1-1 in the “Aldon LM(i) Additional Interfaces Reference”. The following sections describe the panel interface.” and the section “Specify Release Options” in “Chapter 12: Defining a Release” in the “Setup and Administration Reference” to set options for promoting with or without requests. See “Command Interface. or with Aldon-supplied PDM user options. The first is the creation of a promotion request.Third Party Cross Referencing Files Update on Promotion to Production If your site has Abstract/Probe+ from ASC or Hawkeye's Pathfinder installed.” the section “Specify Default Options for New Releases” in “Chapter 8: Defining a New Application. For more information. See “Appendix F: PDM-Style User Options” for a discussion of the PDM interface. you can allow some users to request promotes and others to actually perform them. You can require some users to create requests to checkout or promote an object and can allow others to perform promotes without requests. Emergency Checkout and Promotion Perform emergency checkouts by selecting the desired objects with option 23 (Emergency checkout) and completing the Emergency Checkout panel. • Objects on the Work with Objects by Developer panel shown in Figure 19 on page DO 4-2. • Tasks with associated objects on the Work with Tasks panel shown in Figure 3 on page TT 3-5. this enables easy tracking of all moves to production that did not go through the normal testing path.” on page DO 5-4. DO 3-18 • Moving Objects Aldon LM(i) Daily Operations Reference . • Objects with promote requests pending on the Work with Requests and Non-Conflict Conditions panel shown in Figure 33. “Work with Requests and Non-Conflict Conditions panel. the Work with Tasks panel (Figure 3 on page TT 3-5). Type option 17 by one or more individual objects or tasks and press ENTER to display the Request Promote panel. Create promotion requests with option 17 (Request promote) from the Work with Objects by Release panel (Figure 7 on page DO 2-6).Creating Promotion Requests Promotion requests may be optional or required depending on the release options and a user's authorities. which is very similar to the standard checkout panel (Figure 12 on page UG 2-13). Promotion requests are never required when promoting objects checked out with the emergency checkout function regardless of the requirement for standard objects. Promoting Objects Access to Object Promotion Promote objects by using option 7 to select: • Objects on the Work with Objects by Release panel shown in Figure 7 on page DO 2-6. Aldon LM(i) maintains a record of objects checked out with the emergency checkout function and moves these objects directly back into the Production environment on promotion. or the Work with Objects by Developer panel (Figure 19 on page DO 4-2). Data set update and deployment occur during the promote the same way as a normal promote to production. An acknowledgement condition is always set on when an emergency checkout is promoted. ” starting on page DO 3-21 and “To promote to parent by task. However. Version numbers are updated. Data sets are updated but no deployment is done following either a promote or merge to parent.” starting on page DO 3-25. See “Step 5” in “To promote individual objects to parent” on page DO 3-21.Moving Objects to a Parent Release Aldon LM(i) now supports two methods to move objects to the parent release: • Promote to parent— Follows the standard promote options recompiling the object if required. See “To promote individual objects to parent. • Deploy on promotion to parent. the version number does not change. Capabilities and Features of the Promote to Parent Function The promote to parent function has the following capabilities: • Select objects individually or by task. some Delta releases may also be parents. and the data option can be overridden. Terminology: Child vs. this discussion uses “child” or “child Delta” rather than Delta to refer to the release you are promoting from when you promote into the parent release. • Merge to parent— Provides the ability to move the objects to the parent release without any changes. • A request promote to parent function is available. See “Specifying Data Conversion Options. Delta Every Delta release is a “child” release of some parent. You can automatically create a deployment set while promoting to a parent release.” starting on page CG 3-32. See “To request promote to parent. For example. Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-19 . • Data conversion on promote to parent Data conversion options supported for normal promotes are also supported for promote to parent.” starting on page DO 3-24. Data sets are updated and deployment sets automatically created. Data options for the individual objects are observed. Effects of Promote to Parent Promoting objects to a parent release has the following effects: • The effect on the data in the parent release depends on the data option set for the object. To avoid confusion. the object is always copied. Aldon LM(i) puts the source in the file and member defined for the object in the parent release. • The library group and physical library of the promoted object and source are set to match the library groups of the object and source it is replacing in the parent. Aldon LM(i) deletes the Production copy of the physical file in the “from” release including any data it contains. A message to this effect appears on the promote report. Aldon LM(i) puts the source in the location specified in the child release and creates the file if necessary. Aldon LM(i) truncates the source records as necessary. the promoted object is no longer in the promote from environment • If a copy of the promoted object is active (in Development. or Quality Assurance) in the parent release. Aldon LM(i) sets the “allow object activity” flag to “N=No” for the parent release in the task definition Prerequisites The following prerequisites are common to promoting both individual objects and tasks to a parent release: • The release option “Allow promote to parent” must be set to Y in the child Delta release DO 3-20 • Moving Objects Aldon LM(i) Daily Operations Reference .• Warning: When you promote a physical file to the parent release. LM(i) assigns the library groups using the same method as if the object was being added as new. • As with a standard promote. Aldon LM(i) creates a “C P” release conflict on the active copy • Aldon LM(i) creates a “C R” release conflict on each copy of the promoted object in notified releases of the parent release (other than the promote from release) • If the promoted object is associated with a task in the child release: – – – The association is preserved Aldon LM(i) associates the parent release with the task if the association was not already defined Upon automatic creation of an association of the parent release with the task. Integration. The library group of the object in the parent can be changed either before or after the promote by using option 9 (Move/define). If the object is not defined in the parent release. • When you promote a source based object to a parent release. Warning: If the record length in the parent source file is shorter than that of the child release source file. • Aldon LM(i) deletes and recreates logical files as needed. Note You can change the location of an objects' source in a release using 9 (Move/Define) on the Work with Objects by Release or Work with Objects by Developer panels. If the object is new to the parent. . in the Opt field by the ENTER CPRMOBJPRN objects you want to promote. 3=Dependent To Library To be set Dependent objects selected: Leave resident . 2=Display list for individual selections. Optionally.” starting on page CG 3-32 for more information. F22=More functions Figure 14 . . . Create dependent objects . in the Create dependent objects field. the Specify Data Conversion panel displays next. . .Promote Objects to Parent panel 3. Objects selected for promote to parent: From Object Type Attribute Library NEWAREA *DTAARA PF ACMDL1PDN2 F3=Exit F12=Cancel 1 objects selected for promote. 2. Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-21 . . Leave the Create dependent objects field blank and press ENTER to proceed with the promotion. Press Enter with no selection to continue. . . . type 1 (Work with objects by release) and press ENTER to display the Work with Objects by Release panel. . . . 5=Display selections 2 1=All.• You must have “Perform promotion from child” authority in the parent release • Objects must be in the Production environment of the child Delta release • Objects cannot be a member of any unextracted deployment sets created on promotion into the child release Production environment • Objects need not exist in the parent release To promote individual objects to parent 1. . 1=Select all objects. 2=None. : Type selection. type 27 (Promote to parent) and press to display the Promote Objects to Parent panel: Promote Objects to Parent ALDON/ACMSDEMO/DELTA1 ALDON/ACMSDEMO/BASE Release . . See “To specify data conversion on promote. 4. press Enter. . If you are promoting a data object. At the Work with Objects by Release panel. . : To parent release . . 5. . . type an option number and press ENTER to work with creation of dependent objects. At the Aldon LM(i) main menu. . . . : Object type . . : From release . Do the following: a. . : CSELOBJLGP Object . : Application . . . . . : To release . 2=Specify libraries Create in Release ACM/BAS From Release ACM/DL1 Opt 2 Object NEWAREA Type *DTAARA Attribute F3=Exit F10=View 3 F16=Review objects F11=View 2 F12=Cancel F22=More functions This panel lists one record for each object for which you must assign library groups. Press ENTER to display the Select Library Group for Object panel for the first object in the list: Select Library Group for Object NEWAREA *DTAARA ALDON/ACMSDEMO BASE Object attribute . Type option. : No DELTA1 Library group for the object cannot be mapped between releases. . . the Specify Libraries for Promotes and Creates panel displays: CCRTMAP Specify Libraries for Promotes and Creates Libraries cannot be mapped to the parent or non-resident release in which the following objects are to be created. . 1=Select (one only) Opt Library Group 01 Programs 02 Files 03 Source 04 Other Production Library ACMBASPDN1 ACMBASPDN2 ACMBASPDN3 ACMBASPDN4 1 F3=Exit F4=Prompt F9=Retrieve F12=Cancel F22=More Functions b. . . press Enter.6. : Extended attribute . . . DO 3-22 • Moving Objects Aldon LM(i) Daily Operations Reference . . . . . . press Enter. After completing any required data conversion specifications. . . . Type options. . : Data object . if Aldon LM(i) cannot determine the correct library group for an object in the parent release. Press ENTER to continue. Type 1 (Select) in the Opt field to assign the object library group. Press Enter with no options to continue. . : To release . . . . . : Object library group : Select Library Group for Source NEWAREA *DTAARA ALDON/ACMSDEMO BASE 04 Other Object attribute . until all library group assignments have been made. . Press ENTER to continue. : Data object . . in the Opt field by the object. When you finish assignments for the last object. press Enter. . . type 2 (Specify libraries) and press ENTER To continue with the promote job. . Type option. Do one of the following: – – To change library group assignments for an object. . . 1=Select (one only) Opt Library group 01 Programs 02 Files 03 Source 04 Other F4=Prompt F9=Retrieve F12=Cancel Production Library MDEBASPDN1 MDEBASPDN2 MDEBASPDN3 MDEBASPDN4 F22=More Functions 1 F3=Exit c. . . Type 1 (Select) in the Opt field to assign the source library group. the Specify Libraries for Promotes and Creates panel displays again. . d. : Extended attribute . : Application . the Select Library Group for Source panel displays: CSELSRCLGP Object . . : Object type . .If the object is source based. . : From release . . . and c. . : No DELTA1 Library group for the source cannot be mapped between releases. . . . Continue to perform Steps b. press ENTER with no options selected Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-23 . N=No Y=Yes. press Enter. only eligible objects (those in Production) are promoted. Leave resident . . . . .Specify Promote Options panel Note You can use the Install live from PDN field or the Deploy from PDN field to create a deployment set for the objects you are promoting. . Other objects associated with the task are not promoted. N=No Y=Yes. . . type 5 (Work with tasks) and press ENTER to display the Work with Tasks panel. . At the Submit Job panel. N N Y=Yes. . . At the Aldon LM(i) main menu. . . . the Specify Promote Options panel displays: CPRMOPT Type choices. . . . 2. On the Specify Promote Options panel. F3=Exit F5=Refresh F19=Submit without prompt F12=Cancel F16=Review objects F22=More functions Figure 15 . N N 3 Y=Yes. . . . complete options as desired and press ENTER to display the Submit Job panel. . . . . . type 27 (Promote to parent) and press ENTER to display the Promote Objects to Parent panel. . in the Opt field by the task you want to promote. . 8. To promote to parent by task When using “Promote to parent” on a task. . 2=None. At the Work with tasks panel. . 7. N=No 1=All. . .After you complete library group assignments and press ENTER. . 3=Dependent Specify Promote Options Install live from PDN Deploy from PDN Comment for log . DO 3-24 • Moving Objects Aldon LM(i) Daily Operations Reference . . complete options as desired and press ENTER to submit the promote job. Print compile listing . 1. . . N=No . . . . . Stop upon failure . At the Aldon LM(i) main menu. no merging of source members or data is performed during the process. type 37 (Request promote to parent) and press ENTER to display the Request Promote to Parent panel. 2. Note Although we use the term MERGE. The Merge Objects into Parent Release option is only available for objects in the production environment of a delta release. Merge Objects into Parent (option 50) allows you to move the current production version of an object from a child (delta) release to its parent release without doing all of the processing associated with a promote to parent.To request promote to parent Use of promote to parent requests is optional. Sites use requests if they want to more finely divide and control responsibilities and authorities for this function. Merging Objects into a Parent Release Merge Objects into Parent Release was introduced to replace some of the functionality lost when the option to merge releases was removed. and QUA in either release. The child source and object replaces the existing parent source and object. type 1 and press ENTER to display the Work with Objects by Release panel. Contact your Aldon LM(i) administrator for more information. ITG. Note You can also request promote to parent of a task from the Work with Tasks panel or use the command ACMSRQSPMP. At the Work with Objects by Release panel. for compatibility with the old action. when there are no active copies of the object in either the child or parent release. Complete the fields on the Request Promote to Parent panel and press ENTER to submit the request. Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-25 . 3. Prerequisite • The release option “Allow promote to parent” must be set to Y in the child Delta release 1. Accessed from the Work with Objects by Release Panel. There are some options with regards to data that are explained further on in this section. in the Opt field by the objects you want to promote. That is you can only execute the merge if there are no copies in DVP. Merging Selected Objects by Batch Job A single batch job is submitted to merge all of the selected objects. Promote to Parent • Regardless of settings. or you can use the Subset Objects by Release List panel (F17) to select a subset of the objects to merge. SQL indexes and views. The two log records ensure visibility to users tied to either release. Task/Release Connections Made Automatically If the child release object has task associations. they are also moved forward to the parent release. the object is re-created in the parent release libraries. those associations are carried forward to the parent release. replacing existing parent source and objects. Examples of object types where CRTDUPOBJ is not used include logical files. The CRTDUPOBJ command is used to process most objects to ensure that an exact copy of the child release object is placed in the parent release. In cases where CRTDUPOBJ is not possible. merged objects are not compiled into the release • Version numbers do not change. Merging Produces Multiple Log Entries The merge objects into parent function generates log records for both the “From” child release and the “To” parent release. The existing version number is retained in the new object DO 3-26 • Moving Objects Aldon LM(i) Daily Operations Reference . Merge Objects into Parent vs. During the batch portion of the merge.Selecting Objects to Merge You can merge objects individually or in groups. objects and source are copied into the parent release production libraries. merge all of the objects in the production environment of a delta release simultaneously. Replaced source and objects are archived prior to being replaced. Merging Does Not Change Object Version Numbers Version numbers are not altered as part of the merge process. if archiving is active for the application. If the child release object has special creation options defined. and stored procedures. The existing merge-from (child) object version number is retained in the new object. At the Aldon LM(i) main menu. . . type 1 (Work with objects by release) and press ENTER to display the Work with Objects by Release panel. . press Enter. At the Work with Objects by Release panel. : Into parent release . . Type N (default) if you require the data in the parent copy of the object to be preserved. in the Opt field by the objects you want to promote. N Y Y=Yes. N=No Y=Yes. Stop upon failure . . The Merge Objects into Parent panel displays. ." F22=More functions + Figure 16 . . : Type choices. Type Y (Yes) if you want the data from the child copy of the data object to replace the data in the parent copy of the object. .Merge Objects into Parent panel 3. CMRGOBJPRN Release . If left to N the next screen will allow the entry of Data Conversion options. . Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-27 . . .• You can override the data option settings for Keep destination data and Promote with data • Log entries are indicated with MGC (Object merged to parent (child record)) and MGP (Object merged to parent (parent record)) versus promote entries of PRC and PRP • Data sets are updated • Deployment sets are not created including install live • No exit programs are executed • Object cannot be active in either release • No conditions To merge individual objects into parent 1. The Use child data field displays only if at least one of the objects selected is defined with Data option set to Keep destination data. N=No Merge Objects into Parent BONNIEM/TEST731/DELTA BONNIEM/TEST731/BASE Objects selected for merge into parent: From Object Type Attribute Library ACTGLP *FILE PF B74DELPDNF To Library B74BASPDNF WARNING: Data in merged objects may be lost. . . F3=Exit F12=Cancel F15=Full name See "Use child data. Comment for log . . . . Use child data . . type 50 (Merge into parent) and press ENTER. 2. 4. Applies to non-source based LFs and *CONTAINs. For more information. pressing enter displays the Specify Data Conversion panel. At the Submit Job with Varying Library Lists panel. see “Defining Data Conversion Options” starting on page DS 8-25 in the “Aldon LM(i) Object Deployment Reference” and “To specify data conversion on promote” starting on page CG 3-32 in the “Aldon LM(i) General Topics Reference”. *CONFLICT displays. If you enter Y. Note If there are data objects to be promoted to the parent with differing Use child data needs (some Y. In the Stop upon failure field. if you are merging several objects and do not wish for the job to continue if the merge of a single object fails. The replaced parent copy is archived according to the archive rules for the application. or QUA. *CONFLICT There is a conflict on the Child Release copy of the object that must be cleared before the merge can take place. Use this panel to define CPYF options and/or specify a custom data conversion program. 6. Active means there is a copy in either DVP. The format but not the data in any data set or deployment target is updated. Once each object has been successfully merged. if necessary. This option is available to provide compatibility with the old merge release function. If an object is not valid for Merge to Parent. ITG. the data object in the child should be changed to data option Promote Data before the merge. the same way as a promote to parent works. The following reason codes can display: *ACTIVE— the object is still active in either the parent or the child release. DO 3-28 • Moving Objects Aldon LM(i) Daily Operations Reference . press ENTER to display the Submit Job with Varying Library Lists panel. then they must be merged in separate jobs. 7. 5.If the Use Child Data field is left as N. Note If both *CONFLICT and *CONDITION. the reason code displays under the To Library column. Once you have completed specifying your options. type Y. only the copy of the object in the parent environment library is updated with the new data. the child copy is deleted. If an error occurs during the merge process. some N). change default values for the merge job. *CONDITION— There is a condition on the child release copy of the object that must be cleared before the merge can take place. If that data in all libraries is to be replaced. the child release copy is left intact and the job stops or continues according to the option selected. The objects selected for merge are listed. Press ENTER to submit the merge job. *NOT ABLE— the object is not eligible for merge to parent. in target definitions you define a library to receive content for each library group in the release. In such cases Aldon LM(i) helps you create several install live jobs in the same submit process. The user cannot pick and choose targets when defining the install live job. For information on configuring install live and recovering from error conditions. For example. and let the deployment profile limit what content is sent. In some circumstances it may be useful to exclude some content from automatic installation at a target. This works even on tasks with objects in multiple releases. but not select library groups containing source code. see “Installing Live” starting on page DS 7-1 in the “Aldon LM(i) Object Deployment Reference”. You can grant authority to request install live and authority to initiate install live jobs to different users just as you can for the checkout and promote functions.Installing Live For an introduction to install live see “Install Live Concepts” on page UG 2-31 in the “Aldon LM(i) User’s Guide” For an introduction to install live and additional end user topics see “Installing Live” starting on page UG 2-29 in the “Aldon LM(i) User’s Guide”. In such cases all defined targets receive all install live deployments for that environment. you could create a target definition that prevents installation of the library group containing object source. For most purposes. Install live requests Multiple targets per environment Library group selection in deployment profile controls content sent to targets Possible to block installation of a library group for an individual target definition Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-29 . You can define multiple targets to receive install live deployments for a given environment. Additional Install Live Features Install live by task You can use the install live function from the Work with Tasks panel to select all objects in a task for install live. one for each environment containing task objects you want to install live. you could select library groups containing programs and data objects. For example. For greater flexibility you can use the standard deployment function. You can do this by not mapping the library group to an installation library in the target definition. You control the content deployed to targets during install live configuration by selecting library groups in the deployment profile for the release environment. . in the Comment for log field. . Go to Step 6 on page UG 2-34. . When you press ENTER. Install Live Definition DOUGS/DMS01/DELTA PDN Command ===> F3=Exit F5=Refresh F12=Cancel F22=More functions • At the Install Live Definition panel. modify the comment as desired and press ENTER. . . To change the install live schedule Prerequisite Do either of the following: • Perform the steps in “To install live on promote” starting on page UG 2-32 in the “Aldon LM(i) User’s Guide”. . . be sure to type Y (Yes). be sure to type 2 (Change schedule). When you reach step Step 5 on page UG 2-33. . . . . press Enter. : Type choice. At step Step 5 on page UG 2-33. At Step 5 on page UG 2-36. . DO 3-30 • Moving Objects Aldon LM(i) Daily Operations Reference . Comment for log . : Environment . the Install Live Definition panel displays: CINSLIVDFN Release . • Perform the steps in “To install live outside of the promote function” starting on page UG 2-35 in the “Aldon LM(i) User’s Guide”. . . in the Schedule field.Changing Install Live Default Values To change the install live comment Prerequisite Perform the steps in “To install live on promote” starting on page UG 2-32 in the “Aldon LM(i) User’s Guide”. . be sure to type 1 (Change comment for log). . . – – For more information on the send. . If you did not select any additional job attributes for modification.” starting on page DO 3-33. press Enter. . the Submit Job panel displays. . At Step 5 on page UG 2-36. . . do one of the following: – If the next job attribute you chose to modify was installation method defaults. *MONTHSTR. be sure to type Y (Yes). *NODELAY. At Step 5 on page UG 2-33. *SUN.” starting on page DO 3-31. Go to “To change install live data conversion specifications. . . and install steps. To change the install live installation method Prerequisite Do either of the following: • Perform the steps in “To install live on promote” starting on page UG 2-32 in the “Aldon LM(i) User’s Guide”. *WED. ----. *SAT. . . . in the Installation method field. *MON. Go to “To change the install live installation method. . and install steps as desired and press ENTER. If you are installing live outside of promote. . Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-31 . the Specify Install Live Method panel displays. date) Schedule time (*CURRENT. see “Deploying the Set” starting on page DS 1-8 in the “Aldon LM(i) Object Deployment Reference”. . . . Command ===> F3=Exit F5=Refresh F12=Cancel F22=More functions • At the Install Live Schedule panel. Start receive . receive. . . : Environment . *TUE. receive. *MONTHEND. be sure to type 3 (Change installation method). . .Schedule ---Date Time *CURRENT *CURRENT *CURRENT *NODELAY *CURRENT *NODELAY Schedule date (*CURRENT. time) Install Live Schedule DOUGS/DMS01/DELTA PDN Start send . . • Perform the steps in “To install live outside of the promote function” starting on page UG 2-35 in the “Aldon LM(i) User’s Guide”. Go to “To complete the install live outside of promote” starting on page UG 2-37 in the “Aldon LM(i) User’s Guide”. the Install Live Schedule panel displays: CINSLIVSCD Release . modify the Date and Time values for the send. the Specify Data Conversion panel displays. .When you press ENTER. *FRI. : Type choices. . go to Step 6 on page UG 2-34. If the next job attribute you chose to modify was data conversion specifications. If you are installing live on promote. . . *THU. Start install . . 9=None Name *RCVLIB. 9=None Name *RCVLIB. Parameters . Go to “To complete the install live outside of promote” starting on page UG 2-37 in the “Aldon LM(i) User’s Guide”. If you are installing live on promote. do one of the following: – If the next job attribute you chose to modify was data conversion specifications. . Library . . . the Install Live Method panel displays: CINSLIVMTH Specify Install Live Method DOUGS/DMS01/DELTA PDN Release . press Enter. . . *LIBL. . : Type choices. . . 2=Program. Go to “To change install live data conversion specifications. *LIBL. – DO 3-32 • Moving Objects Aldon LM(i) Daily Operations Reference . . .When you press ENTER. Command or program Library . . . . . go to Step 6 on page UG 2-34. . 4=Program Name Name Name. . Function at end . . *FIRST + If method 3 or 4: DB file or program . . 2=Program. 1 1=Auto install. : Environment . : Type choices. name 9 1=Command. . . . . . : Environment . . Parameters .” starting on page DO 3-33. press Enter. . . . the Submit Job panel displays. . More: If method 2: Function at begin . If you did not select any additional job attributes for modification.3=DB job. . More: Installation method . . name Command ===> F3=Exit F5=Refresh F12=Cancel F22=More functions • At the first and second pages of the Install Live Method panel. . . . . . Member (of DB file) Command ===> F3=Exit F5=Refresh F12=Cancel F22=More functions CINSLIVMTH Specify Install Live Method DOUGS/DMS01/DELTA PDN Release . . . . . . 9 1=Command. . . . . . If you are installing live outside of promote. the Specify Data Conversion panel displays. . modify values controlling installation of the objects at the targets as desired and press ENTER. . Command or program Library . . . in the Data conversion specifications field. 4=*DROP. go to Step 6 on page UG 2-34.” starting on page DS 6-8. be sure to type Y (Yes). name) Retain (saved) data (Y=Yes. 9=*NOCPY) Conversion: Program (*DFT. Specify Data Conversion DOUGS/DMS01/DELTA PDN *MAP N Conversion program . the Submit Job panel displays. . . Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-33 . 6=*NONE. starting characters Type choices.Conversion ----Program Library *DFT Retn Data * Object PF Type *FILE F3=Exit F5=Refresh F12=Cancel F22=More functions • At the Specify Data Conversion panel. For more information on specifying installation methods the. Defaults: CPYF FMTOPT Retain saved Position to .See the online help text for information regarding the installation method values available. be sure to type 4 (Change data conversion specifications). : . press Enter. . see “Defaults for Installation. 5=*NOCHK. : *TOP. Environment . At step Step 5 on page UG 2-33. . . modify values controlling conversion of existing data at the targets into new file formats as desired and press ENTER. To change install live data conversion specifications Prerequisite Do either of the following: • Perform the steps in “To install live on promote” starting on page UG 2-32 in the “Aldon LM(i) User’s Guide”. . When you press ENTER. . . name) Library (*RCVLIB. N=No. . . *=*DFT) CPYF Opt 1 ---. Do one of the following: – – If you are installing live on promote. *NONE. . : data : . : . *LIBL. 3=*MAP. *BOT. If you are installing live outside of promote. the Specify Data Conversion panel displays: CSPCLIVCNV Release . . Go to “To complete the install live outside of promote” starting on page UG 2-37 in the “Aldon LM(i) User’s Guide”. At Step 5 on page UG 2-36. : *NONE Library . CPYF opt (1=*DFT. 2=*MAP/*DROP. . . . • Perform the steps in “To install live outside of the promote function” starting on page UG 2-35 in the “Aldon LM(i) User’s Guide”. . 1. Objects Not Yet Eligible It is possible to request install live of an object for an environment in which the object is not yet available for install live. At the Work with Objects by Release panel.” starting on page CG 3-31.” starting on page DS 6-7. See “Configuring Install Live” starting on page DS 7-2 in the “Aldon LM(i) Object Deployment Reference” for details. This most easily happens when a new object is added to a release. The user requesting install live must have “Request install live from. and “Defaults for Data Conversion. At the Aldon LM(i) main menu. The object becomes available when it is promoted to or beyond the environment for which the install live is requested. type option 1 (Work with objects by release) and press ENTER to display the Work with Objects by Release panel. • Establish user authorities. A request cannot be completed until the object is available. type option 57 (Request install live) and press ENTER. “fulfilling” the install live request as if valid deletes the request condition. In such cases. To request install live Prerequisites • Configure install live for the release environments with which you want work. The request condition specifies an object and environment for which the object is to be installed live. in the Opt field by each object you want to install live. 2. DO 3-34 • Moving Objects Aldon LM(i) Daily Operations Reference . Requesting Install Live Requesting install live places an install live request condition on an object. see “Data Conversion.. Objects Ineligible Due to Library Groups It is also possible to request install live for an object that is not eligible for install live because the library group or groups to which it is assigned are not defined for deployment for the selected environment.. Messages indicating that the object will not be installed live display during the job definition process. A user with the necessary authority can then complete the request by installing the object live for the requested environment.See the online help text for information regarding the data conversion options available. For more information on data conversion.” authority for the environment for which they will request install live. . If the Select Environments for Request Install Live panel does not display. the Select Environments for Request Install Live panel displays: CSELILVENV Release Select Environments for Request Install Live DOUGS/DMS01/BASE . Comment for log . . Press ENTER to continue. Command ===> F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Repeat The panel displays one record for each release environment configured for install live. Type options. Type options. : The following environments are eligible for install live. press Enter 1=Select for request install live Opt 1 1 Release DOUGS/DMS01/BASE DOUGS/DMS01/DELTA Text Command ===> F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Repeat The panel displays one record for each release containing objects you selected for install live. press Enter 1=Select for request install live Opt Environment ITG Integration PDN Production Only install live-defined environments presented for selection. it means all objects are selected for install live for the same environment. . . Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-35 . 4. . .3. On initial display. . – In the Opt field by each environment for which you want to request install live. type 1 (Select for request install live) and press ENTER. Comment for log . all releases are selected. . If objects in the release you are working with can be installed live into more than one environment. . . Type default for the additional install live information. . If objects of more than one release are selected for install live. the Select Releases for Request Install Live panel displays: CSELILVREL Select Releases for Request Install Live Objects have been selected for install live in the following releases. . Type default for the additional install live information. . ” authority for the environment for which they will fulfill install live requests. . .. : Request Install Live ALDON/ACMSDEMO/BASE QUA Type the additional install live information below. – Fulfilling Install Live Requests To fulfill install live requests Establish user authorities. . The user fulfilling an install live request must have “Perform install live from. . . . At the Aldon LM(i) main menu. . . type a comment for the development and deployment logs. Comment for log .. . . 5. .This panel does not display if only one environment of the release is configured for install live. The Request Install Live panel displays: CRQSINSLIV Release . In the Comment for log field. . Objects selected for request install live: Object Type Attribute PGM11 *PGM RPG 1 objects selected for request install live. Aldon LM(i) creates an install live request condition for each object you selected. type option 4 (Conditions menu) and press ENTER to display the Work with Requests and Non-Conflict Conditions panel. Command ===> F3=Exit F4=Prompt F9=Retrieve F12=Cancel F22=More functions The release and environment for which you are installing live display at the top of the panel. DO 3-36 • Moving Objects Aldon LM(i) Daily Operations Reference . Do one of the following: – If there are additional releases for which you selected objects. you are done requesting install live for the selected objects. If the Work with Objects by Release panel displays. press Enter. Go to Step 4 on page DO 3-35. Objects you selected for install live from that release environment are listed one per record in the lower portion of the panel. . 6. : Environment . the Select Environments for Request Install Live panel displays for the next release. Press ENTER. . . 1. See“To install live on promote” on page UG 2-32 in the “Aldon LM(i) User’s Guide” and “To install live outside of the promote function” on page UG 2-35 for more information. Continue with Step 3 on page UG 2-35 to complete submission of the install live job. At the Work with Requests and Non-Conflict Conditions panel. The Condition Environment column indicates the environment for which install live was requested. its source. 2. Aldon LM(i) displays messages and warnings during the install live job definition process so you will know that certain requests are being cleared but not satisfied.. in the Opt field by each install live request you want to complete. Note You can also fulfill install live requests from the Work with Objects by Release and Work with Tasks panels. from these panels you must use option 28 (Work with conditions. However. 3. You attempt to satisfy install live requests by defining an install live job. Aldon LM(i) automatically removes invalid requests when you attempt to satisfy them. If you find that you are working with invalid requests while processing requests. You will not be able to satisfy the request by installing the object live until the conditions are met. or both must be associated with a library group that is mapped to an install live library by the target definition Aldon LM(i) does not check these conditions when users request install live for an object. An object is eligible for install live for a given release environment if the following conditions are met: • There must be a deployment profile of type “live” for the release environment • There must be at least one target defined by a target definition of type “live” associated with that deployment profile • The object. Clearing Invalid Install Live Request Conditions Users may sometimes create an install live request for an object for a particular release environment that is not valid. Either of the two methods of defining install live jobs may be used to satisfy install live requests. you can follow either of two courses of action: • You can proceed with the install live job definition process that results in satisfying valid requests and clearing invalid requests Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-37 .Objects with pending install live requests are identified by the code combination R L in the Cnd column.) to determine the release environment for which the request is pending on an object. type option 47 (Install live) and press ENTER. To prevent requests which cannot be satisfied from accumulating.. Changing an Object’s Production Location When adding or loading an object to the Aldon LM(i) database. and Hold. then Proceed to satisfy the requests – Changing conditions to satisfy requirements may involve one or more of the following: • Modifying target definitions or object library group assignments so that library groups containing the object and/or its source are mapped to target libraries • Creating a “Live” deployment profile associated with “Live” target definitions for the release environment for which the install live was requested if one did not previously exist You can also delete invalid install live requests using the Work with Requests and Non-Conflict Conditions panel as described in “Cnd Column Codes: Requests.• You can: – – Back out of the job definition process by pressing F12 and/or F3 Configure install live definitions or change object library group assignments to satisfy the requirements to make the requests valid.” starting on page DO 5-5. Acknowledgements. The library groups are initially assigned when you: • Map or load a release • Add a new object to a release under development • Check out or create a non-resident object into a delta release from an ancestor release. Move/Define Object Function You can use the Aldon LM(i) move/define function to reassign the existing library groups (and therefore production locations) for an object and its source or to define the library groups for the object and source in descendant releases where the object is not currently resident. The library groups define which library the source and object resides in when promoted to the production environment. you also have to define the names of the source file and the member within that source. it is designated a library group for the object and/or a library group for the source when applicable. This DO 3-38 • Moving Objects Aldon LM(i) Daily Operations Reference . Failure. If the object has source. If required. If you need to deploy an object from a release where it is not resident and the library group allocation is not *MAP or via a library group exit program. you must have Perform checkout authority • For an object that exists in one or more controlled environments you must have authority to Promote to. you must have Promote to.. the existing copies of the object should be manually moved to the new library.. the highest environment in which the object resides in that release.function can also be used to change the names of the source file and source member. authority for that environment From the Work with Objects by Release panel you must have the following authority: • For an object that exists only in the Development environment. How Aldon LM(i) changes Production Locations If an object is currently resident in production when its library group is changed the following actions occur: • If the new library group is associated with a different production environment library. you can use this option to define the library group for the non-resident release. or completely stop updating data sets and deployments with the data object. even though the move may result in future updates of the object going to different data libraries. • When moving source Aldon LM(i) first copies the source member to the new file. Authority requirements to use the Move/Define function Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-39 . If the member is to remain in the same file in the same library then a simple rename is used. Effects of changing an object’s Production location Moving the object to a new library group may cause Aldon LM(i) to update the object into different data libraries in data sets or deployments. From the Work with Objects by Developer panel you must have the following authority: • For an object in Development.. you must have Perform checkout authority • For an object in any other active environment. The highest environment is the environment closest to the Production environment and inclusive of the Production environment. You must review the data set and deployment definitions to ensure the object/source will in the future go to the correct library. Aldon LM(i) does not take any action on copies of the object in data libraries or deployment targets. Aldon LM(i) moves the current production copy of the object (and/or source) to the new production environment library.. then removes it from its previous location. . . . *SAME. . . . . press Enter. . . . library group number library group number name name Command ===> F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Move/define in descendent releases F15=Full name F22=More functions 3. : : : : Move/Define Object A *PGM DMS/DMS/DMS 1 first lg DMSDMSPDN1 1 first lg DMSDMSPDN1 Data option . . . . : CLP OPM To To To To object source source source library group library group file . . type 9 (Move/Define) and press ENTER to display the Move/Define Object panel: CMOVOBJ Object . . in the To object library group field. . . . member . *SAME. . . . : Resident in release . . group .” starting on page DO 3-39. The new locations you designate must be available as follows: • Library groups must be defined in the release • The source file need not exist. but need not be resident or present in the Production environment of an ancestor release. . . . . *SAME + *SAME + *SAME *SAME *SAME. . In the Opt field by the object you want to move. At the Move/Define Object panel. . . : Object type . Aldon LM(i) creates it if necessary • The source member must not already be in use for another object in the release in the selected source file • The source member must not be checked out to more than one developer if you are changing its source file or source member name. Promote Yes Object attribute . At the Aldon LM(i) main menu. To move/define a single object See “Authority requirements to use the Move/Define function. . . . *SAME. . 1. : Type choices. : Release . . . . . : Object Object Source Source library library library library group .The object you want to move must be defined to the release you are working with. do one of the following: – – Type option 1 (Work with objects by release) and press ENTER to display the Work with Objects by Release panel Type option 2 (Work with objects by developer) and press ENTER to display the Work with Objects by Developer panel 2. do one of the following: DO 3-40 • Moving Objects Aldon LM(i) Daily Operations Reference . . . . : Extended attribute . type a new library group number. To leave the object in its current library group. accept the default value. Aldon LM(i) changes the object’s Production location as specified. accept the default value. To move/define an object if descendent releases are available If descendent releases are available. *SAME.– – To move the object to a new library group. *SAME 4. In the To source file field. *SAME To move the object’s source to a different source member. do either of the following: – – 7. do one of the following: – – 6. accept the default value. To move the object’s source to a new library group. type a new library group number To leave the object’s source in its current library group. type a new source file name To leave the object’s source in the current source file. Press ENTER. In the To source member field. type a new source member name To leave the object’s source in the current source member. F13 (Move/define in descendent releases) displays on the Move/Define Object panel. In the To source library group field. Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-41 . do one of the following: – – 5. *SAME To move the object’s source to a different source file. accept the default value. . AS Object attribute . . . . . CSELRELLGP Object . : *VIEW Extended attribute . . . . . Move/Define Object in Descendent Release AS Object attribute . . . . Release level Find release . . . . . . . . . : Object Object Source Source library library library library group . . : DOUGS/DMS/DMS BASE + Name SQL Type options. . . . . . : DOUGS/DMS/DMS2 (not defined) (not defined) Data option . . The Move/Define Object in Descendent Release panel displays. press Enter. : : : : Type choices. From the Move/Define Object panel. . Specify Library Groups for Descendent Releases . . Attempt map first . . group . . : : : : . . This panel lists descendent releases. .” starting on page DO 3-39. 1. . . : Release . . At the Aldon LM(i) main menu. : *VIEW Extended attribute . library group number F9=Retrieve F12=Cancel F15=Full name To move a group of objects This procedure can also be used to define library groups for a group of non-resident objects in a child release. 2=Specify library groups Opt Descendent Release DMS2 DMS3 Lvl 1 2 Res No No Object LG Library (not defined) (not defined) Source LG Library (not defined) (not defined) F3=Exit F11=View 2 F12=Cancel F15=Full name F22=More functions 2. N=No *SAME. . . press F13 to display the Specify Library Groups for Descendent Releases panel. . See “Authority requirements to use the Move/Define function. . type option 1 (Work with objects by release) and press ENTER to display the Work with Objects by Release panel. Command ===> F3=Exit F4=Prompt F22=More functions Y *SAME + *SAME + Y=Yes. . To source library group . Object type . . . . : Promote No SQL Object . . press Enter. . . . library group number *SAME. CMOVOBJDSC Specify library groups for the object and press ENTER. . . DO 3-42 • Moving Objects Aldon LM(i) Daily Operations Reference . Release . allowing you to specify Library Group assignments for descendent releases. . To object library group . . : Object type . . : Resident in release .1. Y Y=Yes. . . . . . In the Print move report field. library group number *SAME + *SAME. At the Move/Define Objects panel. : Type the additional move information below. . *SAME Type Y (Yes) to print a report describing the move action Type N (No) to suppress report printing To run the job interactively. 3. accept the default value. type a new library group number To leave the object in its current library group. For non-resident objects. . N=No 1 1=Run interactively. *SAME To move the object’s source to a new library group. . Run option . . . N=No *SAME + *SAME. In the Run option field. The LG fields display current library group assignments for each object and its source. library group number N Y=Yes. . attempt map first . . do one of the following: – – To move the object to a new library group. . Aldon LM(i) changes object Production locations as specified. CMOVOBJLGP Release object you want to move. .2. . . To source library group . . accept the default value. Print report . . In the To source library group field. do one of the following: – – 5. in the To object library group field. type 1 (Run interactively) To run the job in batch mode. . . in the Opt field by each ENTER. type a new library group number To leave the object’s source in its current library group. . To object library group . 2=Run in batch Objects selected for move (library groups): Extn Dta Object Type Attribute Attr Opt LF *FILE LF No MODULE2 *MODULE RPGLE No PF *FILE PF Yes Res No Yes Yes Object Source LG Library LG Library 01 DS1DSDPDN1 01 DS1DSDPDN1 01 DS1DSDPDN1 01 DS1DSDPDN1 01 DS1DSDPDN1 01 DS1DSDPDN1 F3=Exit F4=Prompt F12=Cancel F22=More functions The lower portion of the panel lists all objects selected for the move. Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-43 . . . At the Work with Objects by Release panel. do one of the following: – – – – 6. press Enter. . . . type 2 (Run in batch) 4. type 29 (Move (library groups)) and press The Move/Define Objects (Library Groups) panel displays: Move/Define Objects (Library Groups) DOUGS/DMS01/DELTA . . do either of the following: 7. . Press ENTER. To avoid incrementing version numbers for the unchanged ILE program. Retiring Objects Most types of objects can now be retired. If splitting a module referenced in a binding directory into two modules. Modifying and Testing ILE Programs To change the list of modules on which an ILE program is based. Change creation defaults recorded in the Aldon LM(i) database for the object using option 15. You can retire an object by checking it out to the development environment. Creation via option 14 creates the object using creation parameters modified with option 15 in the previous step. delete the copy in Development after testing there is complete and recreate the ILE program as a non-resident object in next testing environment instead of promoting it from Development. Aldon LM(i) creates the ILE program over obsolete copies of the modules accessed through the object creation library list for the receiving environment. any other version of the object existing in a later environment or an ancestor release becomes invisible during execution.” on the Work with Objects by Release or Work with Objects by Developer panels. If you check out an ILE program with its modules. “Change create options. check out the ILE program along with the desired modules and change the modules in Development. the target object is made inaccessible. Retire object flags the object so that. Create the program with Aldon LM(i) option 14. be sure to promote both the ILE program and the changed modules it uses together. see “Retiring Objects” on page UG 5-12 in the “Aldon LM(i) User’s Guide”. If you do not promote the changed modules. using option 25 (Retire) from the Work with objects by Release or Work with Objects by Developer panels. For more information. as it is promoted or deployed. When an object is retired. check out the ILE program and any binding directories to be modified. DO 3-44 • Moving Objects Aldon LM(i) Daily Operations Reference . checkout the binding directory referencing the module for modification as well.Modifying and Testing ILE Objects Modifying and Testing ILE Modules To make modifications within the modules on which an ILE program is based. To delete an object from Development you must have OS/400 authority to the developer library and object. *SBS 1 *SBS. Deletion of the last copy of an object in a release also deletes all copies of the object archived for that release from the application's Archive library. Type choices and press Enter to confirm your selections for 4=Delete. an additional panel will display allowing selection of the specific environments from which to delete copies of the object. D/I/Q/P 1=Run interactively. . Copies of the object in other releases of the application are not effected. If the object was associated with a task at checkout using the “For Task” field on the Work with Objects by Release panel. . Work with Objects by Developer. Aldon LM(i) Daily Operations Reference Moving Objects • DO 3-45 . .Cancelling Checkouts and Deleting Objects You can delete an object that is no longer required in a given environment with option 4 (Delete) on the Work with objects by Release. CDLTOBJREL Confirm Delete of Objects Warning! Before pressing Enter to confirm your choices for 4=Delete. After deletion of the last copy of an object in a release. or Act upon Dependent Objects panels. . there will be no copies of the object or associated source for the object anywhere within Aldon LM(i) for that release. To delete an object from Integration you must have “Perform promotion to Integration” authority. deleting it cancels the association with the task. .Confirm Delete of Objects Panel Initial selection of an object for deletion displays the Confirm Delete of Objects panel shown in Figure 17. The exact panel displayed depends on the panel from which the function is called. Press F12=Cancel to return to change your selections. To delete an object from QA you must have “Perform promotion to QA” authority. . Delete an object from a release by deleting all copies of the object in all environments. . MARKE Opt Object 4 CLNADR Type *FILE Attribute PF D Release ACM/BAS F10=View 3 F11=View 2 F12=Cancel F15=Full name Figure 17 . To delete objects from Production you must have “Delete production objects” authority. . 2=Run in batch Envs D QP Rl T Cnds E Chkout Dvp. Select for delete from environments Run option . If more than one copy of the object is eligible for deletion. . *ALL. consider that deleting the last copy of an object within a release also deletes the Archive copies for that release. Log entries for the object are preserved. . . . . pressing Enter from the Confirm panel displays a second panel allowing selection of the copy or copies you wish to delete. . . . . Select zero or more copies. . place a 4 by the corresponding entry on the Work with Archive Object panel (accessed via option 3 “Work with archive objects” on the main Aldon LM(i) menu). . F12=Cancel F22=More functions Figure 18 . .Select Copy of Object to Delete Panel Deleting Archived Objects To delete a copy of an object from the archive. . press Enter. : Release . .If the record selected for deletion represents copies of the object in several environments. . 1=Select Opt Attribute PF PF Environment DVP MARKE QUA Library MARKE ACQUAL 3 objects selected for delete. . . CSELDLTOBJ Select Copy of Object to Delete CLNADR *FILE ALDON/ACMSDEMO/BASE Object . “Work with release definition” authority is required to delete an archive copy of an object. . Press F12=Cancel to return and not delete objects. DO 3-46 • Moving Objects Aldon LM(i) Daily Operations Reference . . : Copy of object to be deleted not known for the above object. . . . . : Object type . please see the online help text. Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-1 . and function keys displayed or available at any of the panels shown in this document.Aldon LM(i) Daily Operations Reference Daily Operations DO Chapter 4 Working with Objects This chapter discusses the following topics: • “Working with Objects by Developer” on page DO 4-2 • “Creating Objects” on page DO 4-4 • “Changing an Object Description” on page DO 4-9 • “Adding an Object” on page DO 4-13 • “Single-Copy Create Specifications” on page DO 4-16 • “Working with Object Dependencies” on page DO 4-18 • “Completing Object Dependency Data for ILE Objects” on page DO 4-20 • “Using Object Dependency Data” on page DO 4-25 • “Using the Development Log” on page DO 4-32 Online Help Text For detailed descriptions of the fields. options. . *BOT. .. . CWRKOBJDVP Position to . . 2=Edit source 3=Check out* 4=Remove(cancel chk) 7=Promote* 13=Request checkout* 14=Create* Opt Object Type Attribute @_070213 *DTAARA @_610_DTA *DTAARA @_610_DTA *DTAARA @A *PGM RPG @NEWFILE *FILE PF ABCSQLRPG *PGM SQLRPGLE ABCSQLRPG *SQLPKG PACKAGE ABCSQLRPG *SQLPKG PACKAGE ACTGLL *FILE LF ACTGLP1 *FILE PF 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 (*=Combined job) 5=Browse source 17=Request promote . starting characters Type options. The Work with Objects by Developer panel. View 2 of 4 DO 4-2 • Working with Objects Aldon LM(i) Daily Operations Reference . More: + Checkout Oth D Release E Developer Env T Requests Cn G75/BS1 DALEA DVP D75/BAS DALEA DVP G75/BS1 DALEA D** G75/BS1 JUDYS DVP K G75/BS1 JUDYS QUA B75/BAS TONYS2 QUA G75/TD1 TONYS DVP B75/BAS TONYS2 QUA D75/DL1 CATHYC DVP K G75/BS1 JUDYS QUA Figure 19 . press Enter. View 1 of 4 CWRKOBJDVP Position to Work with Objects by Developer . as well as Aldon LM(i) specific functions. Release ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE Lvl BASE BASE BASE BASE BASE BASE BASE Type options.Work with Objects by Developer Panel.Working with Objects by Developer Libraries and objects in Development environments are outside of the Aldon Lifecycle Manager for System i (Aldon LM(i)) control system. . .. which is not shown. Beyond this. displays descriptive text for each object. shown in Figure 19 through Figure 22.. developers are free to work with objects using the tools and techniques to which they are accustomed. . and will accept it back into Aldon LM(i) only from the library in which it was placed. also provides access to common development functions. . . press Enter. *BOT. . Work with Objects by Developer __________ *TOP. 6=Print source 8=Display attributes 15=Change create options 19=AltEdit Opt __ __ __ __ __ __ __ Object CLNADRL CLNADRL CLNADRL DEMOCBL1 DEMOCBL1 DEMOCBL2 DEMOCBL3 Type *FILE *FILE *FILE *PGM *PGM *PGM *PGM Env DVP DVP QUA DVP QUA DVP QUA Version 00100002 00100003 00100001 00100002 00100001 00100001 00200001 Subset: Rel:ALDON/ACMSDEMO/BASE Command ===> _________________________________________________________________ F6=Add object F7=Add task F14=WRKSBMJOB F15=Full name/fold F17=Subset F18=WRKSPLF F22=More functions F24=More keys Figure 20 . __________ *TOP. Aldon LM(i) records movement of an object to a specific development library.. . View 4. . starting characters (*=Combined job) 12=Work with conflicts 28=Work with conditions .Work with Objects by Developer Panel. . View 4 of 4 With default subsetting.CWRKOBJDVP Position to Work with Objects by Developer . . Object Library MARKE PHILV ACQUAL MARKE ACQUAL MARKE ACQUAL ------------.. __________ *TOP. . . . starting characters (*=Combined job) 25=Retire 26=Transfer* 30=Display log 39=Display requisite objects . . and so on. An object is active if it is in the Development. . such as 7 (Promote). *BOT. starting characters Type options. object type. (*=Combined job) 9=Move/define 10=Specify data conversion 16=Change 18=Work with tasks 21=Assign tasks* 22=Remove task assignments . or Quality Assurance environments. More: Opt __ __ __ __ __ __ __ Object CLNADRL CLNADRL CLNADRL DEMOCBL1 DEMOCBL1 DEMOCBL2 DEMOCBL3 Type *FILE *FILE *FILE *PGM *PGM *PGM *PGM Text CLNADRL Logical File CLNADRL Logical File CLNADRL Logical File COBOL DEMO Program COBOL DEMO Program COBOL DEMO Program COBOL DEMO Program for Aldon/CMS Demo for Aldon/CMS Demo for Aldon/CMS Demo Main Module Main Module 1st Subordinate Module 2nd Subordinate Module + Type options. Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-3 .Work with Objects by Release Panel.) See the online help text for this panel for descriptions of all available options and function keys..Source ------------Library File Member MARKE QDDSSRC CLNADRL PHILV QDDSSRC CLNADRL ACQUAL QDDSSRC CLNADRL MARKE QCBLSRC DEMOCBL1 ACQUAL QCBLSRC DEMOCBL1 MARKE QCBLSRC DEMOCBL2 ACQUAL QCBLSRC DEMOCBL3 Opt __ __ __ __ __ __ __ Object CLNADRL CLNADRL CLNADRL DEMOCBL1 DEMOCBL1 DEMOCBL2 DEMOCBL3 Type *FILE *FILE *FILE *PGM *PGM *PGM *PGM Env DVP DVP QUA DVP QUA DVP QUA Subset: Rel:ALDON/ACMSDEMO/BASE Command ===> _________________________________________________________________ F9=Retrieve F13=Repeat F21=Print F24=More keys Figure 21 . Subset the panel with F17 and F22 to focus the display on a single application. task. . The sample panels are subset for the Base release of the ACMSDEMO application. (See “Option Processing for Sub-Files (Lists)” on page DO F-11 for information on “*=Combined job” options. . 20=Scan for requisite objects* 32=Change create overrides Subset: Rel:ALDON/ACMSDEMO/BASE Command ===> _________________________________________________________________ F9=Retrieve F13=Repeat F21=Print F23=More options F24=More keys Figure 22 . . Some options on this panel are also available from the more general Work with Objects by Release panel. press Enter. developer. *BOT. . *TOP. the Work with Objects by Developer panel displays one record for each active copy of all objects in Aldon LM(i). . Integration. .Work with Objects by Developer Panel.. View 3 of 4 CWRKOBJDVP Position to Work with Objects by Developer . and the processing of multiple non-combined job options as a group. press Enter. release. Instead. – Recreate unchanged dependent objects when the objects they reference change. For example. Obtain resident copies of objects needed in an environment for other testing reasons – – Resident Object A resident object is an object that currently exists in the specified environment. Maintain test and Production environments as file layouts change. when you promote a changed file layout to QA. Flow for Object Creation Creating a resident object in place does not result in object movement. you do not want to recreate the dependent programs in Production. or the Production environment of a delta release (Creation of a resident non-source object is not allowed because the create has no effect. Phantom objects are also considered non-resident even though they have been created in the environment by Aldon LM(i).) Non-Resident Object Eligible Objects Testing and Non-Resident Object Creation Testing of an object in an environment may require creating resident copies of non-resident objects using the create non-resident option. if a Production file changes. You can create: • Any resident source-based object in any Aldon LM(i) environment • Any non-resident objects into Integration. testing a changed file requires recompiling the programs that use that file to avoid level checks. which changes the status of these programs in the testing environment from non-resident to resident. you may want to recreate the programs that use it. but that is not currently present in the specified release environment. you can use the create function to create new copies in the QA environment over the new file layouts. DO 4-4 • Working with Objects Aldon LM(i) Daily Operations Reference . A non-resident object is an object that is defined to the release or one of the release’s ancestors.Creating Objects Uses of Create Function • In Development. For example. create objects to recompile changed source • Outside of Development. For example. Quality Assurance. Aldon LM(i) also uses object dependency data to create objects in the correct order when a create job includes multiple objects. Aldon LM(i) captures object dependency data when creating objects to ensure the accuracy of object dependency data. replaces it in the data set with the new file description. Selects the next available copy of an object as a model using the object creation library list 2..” authority to an environment to create objects in that environment. the object must already be included in the task they enter on the create panel. If a previous copy of the file exists in a data set. For users without this authority. Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-5 . and Data Sets” starting on page CG 3-1 in the “Aldon LM(i) General Topics Reference” for more information. Version Numbers of Objects Made Resident Because the created copy did not pass through Development and was not changed. You can then promote or delete the object from the environment like any other object. then copies any data in the old version of the file into the new description.. When you create a logical file or physical file. Users with “Change task definition” authority can add objects to an existing task or define a new task when performing a create.How Aldon LM(i) creates a non-resident object into a given environment 1. See “Data. Recompiles the object in the target environment from that source For a discussion of Aldon LM(i) object creation library lists see “Library Lists” starting on page CG 1-1 in the “Aldon LM(i) General Topics Reference”. the created copy has the same Aldon LM(i) object version number as the model upon which it is based. A user must have “Perform promotion to. Aldon LM(i) copies the file format into: • Each data set associated with the receiving environment • Each data set associated with environments further from Production that does not contain a more recently modified copy of the file. Copies source for that copy to the target environment 3. Aldon LM(i) saves the old copy. A task identifier is always optional for a create. Create With or Without Task Association Object Dependency Data Data in Data Sets Effect of Pending Conditions on Creation Eligible Agents: Authority to Create Objects Pending conditions on an object do not inhibit object creation. Creation of a non-resident object makes that object resident in the selected environment. Data Libraries. ” starting on page DO 4-16. “Single-Copy Create Specifications. and “Custom Object Creation Setup” starting on page SA 23-1 in the “Aldon LM(i) Setup and Administration Reference” for more information on create commands and create command selection. With selection of the appropriate release setup option. is available on the Work with Objects by Release. and Work with Tasks panels. To create non-resident objects 1. See “Object Creation. by one or more objects. Work with Developer Objects. Create. Aldon LM(i) automatically creates objects on promotion into a new environment. type 14 (Create) and press ENTER. DO 4-6 • Working with Objects Aldon LM(i) Daily Operations Reference . Tip You can also select objects for non-resident creation by selecting a task with option 14 on the Work with Tasks panel. Act upon Dependent Objects. The Work with Objects by Release panel displays.Automatic Create Command Selection Aldon LM(i) selects the correct IBM or user-defined create command and options for each object based on the object's type. and Aldon LM(i) database entry. attribute. You can create objects outside of the promote function using: • The Create Objects panel discussed below and in “Creating Objects” starting on page UG 2-15 in the “Aldon LM(i) User’s Guide” Option 14. At the Aldon LM(i) main menu. • The ACMSCREATE command discussed in “ACMSCREATE Command Syntax” starting on page CG 7-10 in the “Aldon LM(i) General Topics Reference” • Aldon-supplied PDM user options discussed in “PDM-Style User Options” on page DO D-1 in the “Daily Operations Reference For System i Servers” Automatic Create on Promote Available Interfaces To create resident objects See “To create an object in an active environment” starting on page UG 2-19 in the “Aldon LM(i) User’s Guide”. type option 1 and press ENTER.” starting on page DO 1-12. 2. In the Opt field. . . . . For task . Do you wish to specify data conversion methods . D/I/Q/P 1=Both. . . . . . 2=Res. . Change Analyzer options . *SBS. Objects with residence status Based on residence status . N=No . . . .) • After identifying the command processing program. *SBS 3 1 Y N N N *SEL. . R=*REL Y=Yes. .” starting on page DO 4-16 for more information. . . . . do one of the following: – – Type 3 to create only non-resident objects. 3=Non res 1=Now. Note If the residence status of objects in target environments is likely to change between the time you complete this panel and the time the create job runs. 4. . . This allows you to more effectively control modification of environments with multiple step procedures involving multiple jobs. 2 objects selected for create. 5. . F3=Exit F4=Prompt F7=Add task F12=Cancel F20=Enlarge list F10=View 3 F11=View 2 F22=More functions 3. . . Type 1 to create both non-resident and resident objects. you may wish to type 2 in the Based on residence status field to defer checking of residence status until the job actually runs. . N=No Y=Yes. . Create in environments . create the *CMD object by selecting it with option 14 as described in “Creating Objects” on page UG 2-15 in the “Aldon LM(i) User’s Guide”. R=*REL Y=Yes. press Enter. In the Objects with residence status field. To create *CMD objects in Development Prerequisite Aldon LM(i) creates *CMD objects in Development. . N=No. Comment for log . . . N=No. . . . Stop upon failure . . . . Objects selected for create: Object DEMOCBL1 DEMOCBL3 Type *PGM *PGM Attribute CBL CBL Release ACM/BAS ACM/BAS Environments DVP ITG QUA PDN DVP MARKE ITG QUA PDN (ITG)(QUA) PDN . . . Complete other values on the panel as desired. *ALL. but you must first identify the command processing program using option 15 (Change create options) (See “Single-Copy Create Specifications. .The Create Objects panel displays: CCRTOBJ Create Objects Type the additional create information below. Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-7 . Press ENTER to submit the create job. . . . Print compile listing? . 2=At run time + Name Y=Yes. In the Requisite Object Name and Type fields. See “Overview: Object Dependency Commands” starting on page CG 7-25 in the “Aldon LM(i) General Topics Reference” for more information.To prepare to create a logical file with fields defined by reference By default. type Y. Aldon LM(i) creates logical files in alphabetical order. use F8 (Next environment) and F7 (Previous environment) to move between copies of the object in different Aldon LM(i) environments. Note You can also create manual object dependency records using the command interface. See “Library Lists” starting on page CG 1-1 in the “Aldon LM(i) General Topics Reference” for a discussion of object creation library lists. Aldon LM(i) constructs the library list based on the environment in which the ILE program is created. See “Custom Object Creation Setup” starting on page SA 23-1 in the “Aldon LM(i) Setup and Administration Reference” for details on object creation commands. Use the Create Dependent field. type the name of the referenced logical file and *FILE. If you accessed this panel from the Work with Objects by Release panel. (See “To manually specify object dependencies” on page UG 2-41 in the “Aldon LM(i) User’s Guide”. At the Work with Objects by Developer or the Work with Objects by Release panel. Complete a requisite objects list for each copy of the logical file. b. type 40 (Define requisite objects) and press ENTER. This results in incorrect creation of a logical file with fields defined by reference to another logical file if the referenced file comes later alphabetically than the referencing file. Aldon LM(i) uses the same object creation library lists for ILE objects as for other object types. DO 4-8 • Working with Objects Aldon LM(i) Daily Operations Reference . Object Creation and ILE Aldon LM(i) includes create command definitions for all ILE object creation commands at installation. in the Opt field by the referencing logical file. create manual object dependency records for the referencing logical file with the following procedure: 1. To allow Aldon LM(i) to correctly create the referencing logical file. The User-Defined Requisite Objects panel displays. Aldon LM(i) selects modules and binding directories used by an ILE program from the first environment containing them within the library list. Press ENTER to load the defined relationships into the Aldon LM(i) object database. 4.) 2. 3. Do the following for each referenced logical file: a. the source file change remains in effect for any copies of the object in other environments of the release. type option 2 (Work with objects by developer) and press ENTER to display the Work with Objects by Developer panel. when executed. including information on creating pseudo-source for an object. create the desired object. these fields are blank.Changing an Object Description Extended attribute field Aldon LM(i) uses a special Aldon LM(i) extended attribute to select handling procedures appropriate for each type of program object. If the object is associated with source or pseudo-source. Source option field The Source option field indicates whether the object is associated with source. Create *MODULE objects from source as a separate step with option 14 (Create). Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-9 . At the Aldon LM(i) main menu. the file and member containing the source or pseudo-source display. Note Pseudo source If you change the source file for a checked out object. source refers to both standard compilable source code and pseudo-source. Pseudo source refers to members containing CL commands which. In this documentation. but then cancel the checkout using option 4 (Remove (cancel chk)). ILE program objects are non-source objects. pseudo source. see “Pseudo-Source” on page DO A-1. BND — Bound — This value instructs Aldon LM(i) to create a partial ILE program object with a CRTBNDxxx command which makes use of some ILE features. For further discussion of pseudo-source. If no source is associated with the object. To change an object description 1. ILE — Integrated Language Environment — This value instructs Aldon LM(i) to create a full ILE program object by linking one or more *MODULE objects with the CRTPGM command. If you want to reverse the source file change. Possible extended attribute values are: OPM — Original Program Model — This value instructs Aldon LM(i) to create a program object using a traditional CRTxxxPGM command which does not make use of any IBM Integrated Language Environment (ILE) features. you must change the source file back to the original before you cancel the checkout. or no source. . . Source member Source library For task . . . Comment for log . . in the Source option field. developer to whom the object is checked out. specify the library group number for the library group to contain the object’s source. . Extended attribute Data option . . group . : Developer . do one of the following: – – To associate standard source with the object. object type. In the Source library group field. 2=Pseudo source. *=Default 1=Source. + Name _________________________________________________ Command ===> __________________________________________________________________ F3=Exit F4=Prompt F9=Retrieve F12=Cancel F22=More functions Figure 23 .2. In the Source file. Object type . Source file . . 1 QCBLSRC DEMOCBL2 3 + Attribute Extension 1=Keep destination data. 5. . . Complete the steps in “To change an object description. type the names of the file. release. . Press ENTER to associate the source with the object. . . . . . Note You can place the cursor in this field and press F4 (Prompt) to select a library group from a list. press Enter. . . CBL . .Change Checked Out Object Panel Note This panel displays the object name. 2=Promote data. . . . 2. in the Opt field by the object you want to change the description of. . . Associating Source with an Object To associate source or pseudo-source with an object 1. OPM + . type 2 (Pseudo-source) 3. type 1 (Source) To associate pseudo-source with the object. 9=None Change Checked Out Object DEMOCBL2 ALDON/ACMSDEMO/BASE MARKE . : *PGM . . . and Source member fields. . . . 4. . . . type 16 (Change object) and press ENTER to display the Change Checked out Object panel: CCHGOBJ Object . . . Source option . . . . : Type choices. Object attribute . . : Release . . the extended attribute (for programs). . . At the Change Checked Out Object panel. .” starting on page DO 4-9. . . . * : : : : . . . and data option. DO 4-10 • Working with Objects Aldon LM(i) Daily Operations Reference . attribute. and member containing the source or pseudo-source for the object. . . . At the Work with Objects by Developer panel. in the Opt field by the program you want to convert. libraries do not display on the bottom of this panel. Note You can place the cursor in the Object attribute field and press F4 (Prompt) to select the appropriate attribute from a list. At the Aldon LM(i) main menu. Aldon LM(i) changes the extended attribute of the program. At the Change Checked Out Object panel. Moving to ILE Aldon LM(i) supports conversion of programs from the “original program model” to partial ILE and to full ILE. Changing Object Attributes The Change Object Description panel can also be used to change the attribute of an object so that the appropriate create command is used. type 16 (Change checked out object) and press ENTER to display the Change Checked Out Object panel shown in Figure 23 on page DO 4-10. Make whatever changes are necessary in the program source code. 2. do one of the following: – – To change a BND program to ILE. Check the object out to Development. 4. but changing the attribute has the added benefit of making the nature of the object clear on display panels. type the new object attribute. Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-11 . For example. To change an OPM program to BND. At the Work with Objects by Developer panel. Press ENTER. type BND 5. In the Extended attribute field.If there is more than one library in your Production environment. in the Object attribute field. to create RPT programs. type ILE Go to “To complete conversion to ILE” on page DO 4-12. The same effect can be achieved by defining object creation defaults for objects. type option 2 (Work with objects by developer) and press ENTER to display the Work with Objects by Developer panel. 3. change program object attributes from RPG to RPT. but an additional panel appears on which you can specify the destination library for the source. To convert a program to ILE Prerequisites Define the program to Aldon LM(i). 1. 1 1=Copy source to existing *MODULE. . in the Select action field. . Aldon LM(i) does not change or delete the actual source previously associated with the OPM or BND program. . . . the source remains in its original location in your developer library. . press Enter. . type 2 (Add new *MODULE (copy source)) To convert to ILE without associating the program source with a *MODULE. . . . Select action . Press ENTER to display the Define Module Object panel: CDFNMDLOBJ Release . . . In Step 4. . in the Source option field. Command ===> . . . . . in the Select action field. . . do one of the following: – – – To copy the source to an existing *MODULE. . . . . . Prerequisites Complete the steps in “To convert a program to ILE” on page DO 4-11. 2. If. .To complete conversion to ILE This procedure describes how to use the Define Module Object panel to associate existing source for a *PGM converted to ILE with a *MODULE object. : : : : Define Module Object ALDON/ACMSDEMO/BASE DEMORPG3 QRPGSRC DEMORPG3 MARKE The existing source for the above program may be use for a *MODULE object. *SYSOBJNAM Name Module . 3. Task . At the Change Checked Out Object panel. RPG *SYSOBJNAM + + + Figure 24 . Source file . DO 4-12 • Working with Objects Aldon LM(i) Daily Operations Reference . . you typed 1 (Copy) or 2 (Add). At the Define Module Object panel. . From source for program From source file . Developer . If 2=Add new *MODULE: Module attribute . . type 1 (Copy source to existing *MODULE) To add a new *MODULE and copy the source into it. . . type 9 (No source). . Comment for log . . . . . . . . type the name of the module to receive the source for the program. . type 9 (None) 4. 1.Define Module Object Panel Note Information regarding the program source for the program converted to ILE displays at the top of the panel. . . 2=Add new *MODULE (copy source ) 9=None Name Attribute Name Name. . . . in the Extended attribute field. be sure to type ILE. . in the Module field. Type choices. : From source member . . . Source member . See “Adding an Object” starting on page UG 5-2 in the “Aldon LM(i) User’s Guide” for details on adding an object with the panel interface. Interfaces Available Add a new object using the Add Release Object panel or the ACMSADDOBJ command discussed in “The Add Object Command” on page CG 7-12. Adding an Object When to Add an Object If a developer creates a new object. Adding Objects with the Panel Interface Press F6 to add a new object from the Work with Objects by Release panel shown in Figure 7 on page DO 2-6. If. in the Select action field. and Source member fields. To Change an Object From BND Back to OPM To change an object back to extended attribute OPM from extended attribute BND. If you are modifying objects from a third party software vendor and have chosen not to define the vendor's base release to Aldon LM(i). or from the Work with Objects by Developer panel shown in Figure 19 on page DO 4-2. 6. load or map the object again as described in “Mapping a Release.” starting on page SA 17-1. Source file. then in the Module attribute.5. type the attribute source file. and source member names for the new module. Press ENTER to confirm your entries. See the section “The Check Out Foreign Object Command” starting on page CG 7-8 in the “Aldon LM(i) General Topics Reference” for details.” starting on page SA 16-1 and “Loading a Release. Authority Required You must have “Perform checkout” authority to add a new application object. you may wish to use the ACMSCHKFRN command to simultaneously add and check out objects from the vendor base release. define it to Aldon LM(i) before promoting it from the Development environment. An object need not exist at the time it is “added”. you typed 2 (Add). Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-13 . Object Source Identification Specify the location of the associated source. or the object is a records object (Aldon defined type *RCDS) type 1. If pseudo-source is provided. If no source is associated with the object type 9 for Source option. The data option is set for each object and determines whether the data in the from environment replaces data in the target library when the object is promoted or deployed. Aldon LM(i) uses the extended attribute to select handling procedures appropriate for each type of program object. Data Option The object data option allows objects to be promoted with or without their data. • ILE— This value instructs Aldon LM(i) to create an ILE program object by linking one or more *MODULE objects with the CRTPGM command. Possible extended attribute values are: • OPM— Stands for “Original Program Model. specify the extended attribute. See “Record Objects” starting on page DO C-1 for more information on defining *RCDS objects. The object name and type together must be unique within a given application. the object will be moved from the developer's object library to the new environment. • BND— This value instructs Aldon LM(i) to create a program object with a CRTBNDxxx command which makes use of some ILE features.Specifying a Developer Specify the name of the developer definition for the developer adding the new object. Aldon LM(i) moves source from the source library named in this developer definition.” This value instructs Aldon LM(i) to create a program object using a traditional CRTxxxPGM command which does not make use of any IBM Integrated Language Environment (ILE) features. or deployed. and attribute of the object. CPYF or a user defined DO 4-14 • Working with Objects Aldon LM(i) Daily Operations Reference . If you directed Aldon LM(i) to re-create objects on promotion from Development. Identifying the Program “Model” For program objects. • Keep destination data— For objects with this setting. Create *MODULE objects from source as a separate step via option 14=Create. data in the target library is preserved when a new copy of the object is promoted. type. type 2. Unique Object Name/Type Required Specify the name. updated in a data set library. Aldon LM(i) deletes the object from the developer's object library on promotion. If you direct Aldon LM(i) to move the existing object forward with the source. When you promote the object from Development. ILE program objects are non-source objects. If standard source is provided. The logical files. Press F4 to prompt for a list of values allowed for any field followed by a + sign. indexes. data set and target libraries. At checkout time the file definition and the data are copied to the developer's library. Note *RCDS objects cannot be over a physical file with Data option value of 2 (Promote data). Objects with any other type/attribute combination default to 2 (Promote data). Type a comment describing the add operation for the development log. Examples of files that are changed in this way include tax tables. Physical files and tables default to 1 (Keep destination data). views or indexes are automatically re-created whenever the designated physical file or table changes. Task Association To include the object in an existing task. changes can be made to both its layout and to its data. • *— indicates that the default value for the object type/attribute is to be used. when you press ENTER from the Add Release Object panel. On the second panel. and control files. views or indexes built over them. data in the from environment is copied forward to the target library with the newly formatted object. aliases. Note The Keep destination data value is not allowed for logical files. select one of your library groups to receive the object from the final promotion. Multiple Library Groups If you are using multiple library groups. specify the library group to receive the object's source member. To associate the object with a new task. On the first panel. This is the default setting for physical files and SQL table objects. triggers. Data is copied to controlled environment. views. and constraints. At the time of promote. This data is updated by developers when functional changes are required and not by users on a daily basis. Files that are checked out and promoted with data can be defined with or without source and can have logical files. actuarial tables for insurance applications. two additional panels display. These changes can be promoted and deployed together. While the table or file is in development. type the task name. • Promote data— For objects with this setting. press F7. Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-15 . This option is used for physical files or tables that are used to control how the application functions. data is copied forward into the next environment as well as into the associated data sets and targets.conversion program is used to copy data from the old copy of the object to the newly created one. If a copy of the object remains behind in Integration or Quality Assurance. application-. See “Adding SQL Objects. a single-copy create specification is sufficient and simpler. or global-level create command default. If the copy is used to fulfill a checkout. DO 4-16 • Working with Objects Aldon LM(i) Daily Operations Reference .” starting on page DO G-2 for more information on adding SQL objects.” starting on page DO B-1 for information on defining menus to Aldon LM(i). See “Menus as Aldon LM(i) Objects. see “Object Creation” on page DO 1-12. While it exists. see “Application-Level Create Command Defaults” starting on page 12-10 in the “” • For information on working with create command defaults at the release-level. For many purposes. The single-copy create specification travels with the copy of the object as it moves through the release environments. see “Release-Level Defaults for Object Creation” starting on page SA 22-7 in the “Aldon LM(i) Setup and Administration Reference” • For a general discussion of Aldon LM(i) object creation. a single-copy create specification supersedes all command defaults that would otherwise apply to that copy. see “Custom Object Creation Setup” starting on page SA 23-1 in the “Aldon LM(i) Setup and Administration Reference” • For information on working with command defaults at the application level.Special Object Types See “Record Objects” starting on page DO C-1 for more information on defining *RCDS objects. a copy of the single-copy create specification remains associated with that copy of the object as well. and information on working with create command defaults at the global level. the single-copy create specification accompanies the copy to Development. See index entries under “ILE” for additional information on working with ILE objects. or a release-. Single-Copy Create Specifications Aldon LM(i) creates objects like the existing copy in the same environment or like the first copy found using the object creation library list unless instructed to do otherwise by a single-copy create specification. See also the following topics: • For general information on create commands and create command defaults. do either of the following: 6. In the Create keywords field. . Create command . . Press ENTER. CRTCBLPGM *LIBL *SYS. . . Library . type *DFT to reset to defaults): GENOPT(*NOOPTIMIZE) USRPRF(*USER) TEXT('DEMORPG4 test program’) Command ===> _________________________________________________________________ F3=Exit F4=Prompt F9=Retrieve F12=Cancel F15=Full name Figure 25 . . Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-17 . : : : : Change Object Creation Options ALDON/ACMSDEO/BASE DEMORPG4 Environment . Type the keywords and parameter values Press F4 (Prompt) to display a prompt screen showing the parameters for the specified command 5.To define a single-copy create specification 1. At the Aldon LM(i) main menu. .Change Object Creation Options Panel 3. . press Enter. Object name . : *PGM Object library . . Object type . . . : RPG Extended attribute . . The Change Object Creation Options panel displays: CCHGCRT Release . command *LIBL. . : DVP MDEBSPDN1 OPM Type choices. In the Create command field type the name of the custom create command to be used or *SYS to use the standard IBM create command. . . specify the library containing the create command by doing one of the following: – – – – Type *LIBL to search the library list Type a specific library name. . In the Opt field by the object for which you want to define create specifications. . . . . Object attribute . library Create options (Press F4 to prompt. . In the Library field. . if you specified a value other then *SYS in the Create command field. . . 4. . . type option 15 (Change create options) and press ENTER. do one of the following: – – Type option 1 (Work with objects by release) and press ENTER to display the Work with Objects by Release panel Type option 2 (Work with objects by developer) and press ENTER to display the Work with Objects by Developer panel 2. . CSELCHGCRT Select Copy of Object for Change of Creation Options ACTGLL *FILE GARYM/GARYMAPP/BASE Object . 2. Press F12=Cancel to return and not change creation options. . . type *DFT in upper case and press ENTER. . . . If the Select Copy of Object for Change of Creation Options panel displays. : Object type . press Enter. . begin by following the procedure described above in “To define a single-copy create specification” starting on page DO 4-17 in the “Aldon LM(i) Daily Operations Reference”. : Release . or copy procedures • At release activation • When adding objects • When creating objects DO 4-18 • Working with Objects Aldon LM(i) Daily Operations Reference .Select Copy of Object for Change of Creation Options panel To delete a single-copy create specification 1. To delete a single-copy create specification. Press ENTER. see “Working with Dependent Objects. map. . . When Aldon LM(i) Obtains Dependent Object Data Aldon LM(i) obtains requisite/dependent object data: • When directed to scan objects during load. . : Copy of object for change of creation options not known for the above object. type a 1 (Select) by the copy or copies for which you want to define create specifications. . 1=Select Opt Attribute LF LF Environment QUA PDN Library GM7BASQUAL GM7BASPDN1 Type F3=Exit F12=Cancel F15=Full name F22=More functions Figure 26 . . .” starting on page UG 2-38. Working with Object Dependencies Use requisite/dependent object data to help determine the scope of tasks and to facilitate recreating dependent objects to avoid level checks. in the Create options field. . . Select zero or more copies. . Perform steps 1 through Step 4. When you get to Step 5.7. . For an introduction to how Aldon LM(i) works with object dependencies. . . . particularly those not scanned by Aldon LM(i). Aldon LM(i) combines and presents the information from all three sources. When you request a list of objects dependent on or requisite to a given object.” starting on page DO 4-20. The three sources are: • Aldon LM(i) scans • Object dependencies identified manually by the user through the Aldon LM(i) panel interface • Object dependencies identified by third party software and specified to Aldon LM(i) through the command interface You can specify dependency information for a given object using any or all of these sources. How Object Dependency Data is Stored A requisite/dependent object record moves with the copy of the object for which it was created and also applies to new copies of the object created by checkout. Manual Completion of Object Dependency Date for ILE Objects Aldon LM(i) scans cannot determine all dependency information for some ILE objects. The Aldon LM(i) database maintains information identifying the source of each object dependency record. Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-19 .) • When requested to do so for a release or for individual objects • From commands executed with data from third party software Manually Specifying Object Dependencies Use the panel interface or the ACMSUSRSCN command to directly identify requisite/dependent object relationships. • For information on manual completion of ILE dependency data see “Completing Object Dependency Data for ILE Objects. • For more information on specifying with the panel interface see“Specifying Object Dependencies” starting on page UG 2-41 in the “Aldon LM(i) User’s Guide” • See “Overview: Object Dependency Commands” on page CG 7-25 in the “Aldon LM(i) General Topics Reference” for more information on the command interface.• When promoting objects from local developers or between Aldon LM(i) controlled environments (Note: Aldon LM(i) does not scan for requisite/dependent object data when promoting from a remote developer environment. To prevent the loss of dependency information. Aldon LM(i) replaces a given type of object dependency record only with records generated in the same manner. perform the following steps: • *MODULE — Manual dependency specification is usually not necessary DO 4-20 • Working with Objects Aldon LM(i) Daily Operations Reference . or copy procedures see “Population Functions Overview” starting on page SA 15-1 in the “Aldon LM(i) Setup and Administration Reference” • Scanning individual objects within a release and directly identifying requisite/dependent object relationships. but cannot determine if modules for a given ILE program were specified directly in a create command list or indirectly using a binding directory. The Aldon LM(i) database preserves specified object dependency records and propagates them as new copies of the object are created via checkout. Dependence on a binding directory must therefore be specified manually. map. type. From the scan. To provide complete ILE object dependency data. environment.” starting on page UG 2-39 of the Aldon LM(i) “User's Guide” • Directly identifying requisite/dependent object relationships through the command interface see “Overview: Object Dependency Commands” starting on page CG 7-25 in the “Aldon LM(i) General Topics Reference” Completing Object Dependency Data for ILE Objects Aldon LM(i) can scan ILE objects for dependency data during mapping or loading.Aldon LM(i) refreshes object dependency records produced by scanning each time the object is recreated. and later by request. Aldon LM(i) can determine the modules used to create an ILE program. and release • Date and time of last scan by Aldon LM(i) • Aldon LM(i) scan current flag • Requisite object name (first 10 bytes) and type • Requisite defined by flag • Create dependent flag • Recursive flag Additional Information Regarding Acquiring Object Dependency Data For additional information on: • Scanning objects during load. see “Acquiring Object Dependency Data. Each record includes the following information for an object: • Dependent object name. in the Opt field by the ILE *PGM or *SRVPGM object.• *BNDDIR — Manually identify *MODULE objects specified by a binding directory as requisite objects for that binding directory using the procedure described in “To manually specify object dependencies” starting on page UG 2-41 in the “Aldon LM(i) User’s Guide”.” starting on page DO 4-21. select the binding directories with option 45 (Assign binding directories) as described in “To work with binding directory entries. Binding directories used by an ILE program cannot be determined by scanning. This information is necessary to complete object dependency data for ILE programs that use binding directories. Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-21 .” starting on page DO 4-21 – • *PGM and *SRVPGM — Programs may also be selected with option 45 (Assign binding directories) to identify binding directories used by a given program as described in “To work with binding directory entries. – Manually identify programs using a given binding as described in “To work with binding directory entries. or binding directory (*BNDDIR). type option 45 (Assign binding directories) and press ENTER. To work with binding directory entries • At the Work with Objects by Release or Work with Objects by Developer panel. To identify programs using a given binding directory. Working with Binding Directories Use the Work with Binding Directories panel to associate binding directories with ILE programs that use them.” starting on page DO 4-21 With requisite objects recorded and binding directory/program relationships identified via option 45. Each record describes a previously defined association between a binding directory and an ILE program. Aldon LM(i) identifies the ILE program as dependent on the modules it uses. At the Work with Binding Directory Entries panel. If entered by selecting a binding directory. press F6 (Add). Display the Work with Binding Directory Entries panel as described in “To work with binding directory entries. the panel lists all binding directories associated with the selected ILE program. DO 4-22 • Working with Objects Aldon LM(i) Daily Operations Reference . press Enter. To add a binding directory entry 1. 4=Delete Opt Bind Dir BNDDIR BNDDIR Pgm Name ALDSCMAIN ALDSRVPGM Pgm Type *PGM *SRVPGM Application GARYM GARYAPP GARYM GARYAPP Release BASE BASE Subset: Rel:GARYM/GARYAPP/BASE Bnddir:BNDDIR Command ===> F3=Exit F4=Prompt F5=Refresh F6=Add F14=WRKSBMJOB F17=Subset F18=WRKSPLF F21=Print F9=Retrieve F12=Cancel F22=More functions Figure 27 . 2.The Work with Binding Directories panel displays: CWRKBNDDIR Work with Binding Directories Type options.” starting on page DO 4-21. the panel lists all ILE programs and service programs associated with the selected binding directory.Work with Binding Directories Panel Note If entered by selecting an ILE program or service program. . If the binding directory is identified in the Binding directory field. . : Group . Press ENTER to create the new binding directory entry. . .” starting on page DO 4-21. . *SRVPGM Program name . The Add Binding Directory Entry panel redisplays with a message confirming addition of the binding directory entry. . . 5. . 6. in the Binding directory field. . type the type of the ILE program with which to associate the binding directory b. Release . . If the program name and type are identified in the Program name and Program type fields. . go to step Step 3 To stop adding binding directory entries. In the Program name field. .Add Binding Directory Entry Panel 3. if it is not already completed. . . . . : BASE GARYAPP GARYM BNDDIR + Name *PGM. . press Enter. : Application . 4. . . press F3 (Exit) To delete a binding directory entry 1. type the name of the binding directory or press F4 (Prompt) to select from a list. do the following: a. : Binding directory . . Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-23 . Input fields are blank and ready for addition of another binding directory entry. . .The Add Binding Directory Entry panel displays: CADDBNDDIR Add Binding Directory Entry Type choices. Do one of the following: – – To add another binding directory entry. Command ===> F3=Exit F4=Prompt F5=Refresh F9=Retrieve F12=Cancel Figure 28 . . type the name of the ILE program with which to associate the binding directory or press F4 (Prompt) to select the program name and type from a list In the Program type field. Display the Work with Binding Directory Entries panel as described in “To work with binding directory entries. . . Program type . The Confirm Delete of Binding Directory Entries panel displays with a list of entries selected for deletion. This allows easy modification and creation of binding directories within Aldon LM(i). If you specify a binding directory in the create command default. type 4 (Delete) and press ENTER. Technical Details The next time you create the program after identifying an option 45 binding directory reference. (The exceptions to this are the “entry procedure module” required in each program and any service programs used by the program. These two types of items cannot be specified from a binding directory and are never deleted from the object creation information. 3. or you can hard code the binding directory in the create command default. Other Setup Recommendations for ILE Objects Conversion of binding directories to pseudo-source based objects after loading or mapping is recommended. Aldon LM(i) performs the following actions: • Adds the binding directory to the object creation information for the program kept in the Aldon LM(i) object database • Removes modules named in the directory or directories which are also in the module list from the last time the object was created from the module list. in the Opt field by each entry you want to delete. Press ENTER to confirm deletion. You can leave the binding directory parameter of the command blank to assign the binding directory with option 45 (Assign binding directories) on the Work with Objects by Release panel or Work with Objects by Developer panel.) Create Command Defaults and Binding Directories If you use a create command default for an ILE program.2. This avoids duplication. DO 4-24 • Working with Objects Aldon LM(i) Daily Operations Reference . Aldon LM(i) ignores any binding directory you may have associated with the program using option 45. Aldon LM(i) uses options specified in the default to create the program. At the Work with Binding Directory Entries panel. A non-resident object does not actually exist in the indicated environment. The reference release and environment together identify the location of the reference objects for the purpose of assessing whether or not other objects are dependent on them. A real copy of each non-resident object exists in an environment subsequent to the reference environment and can be used as a source to create the non-resident object into the reference environment. Example: You display objects dependent on a file (the reference object) which you have changed and promoted into QA (the reference environment). QUA indicates the information is about the object relative to the Quality Assurance reference environment. If copies of these objects dependent objects are not present in the reference environment they are said to be non-resident with respect to that reference environment. no copy of the object actually exists in that environment.Using Object Dependency Data Overview Reference Object The term “reference object” in this discussion refers to the object on which the objects to be acted on depend. the term “reference object” refers to an object used as a model for assigning ownership and authorities to other objects. You display objects dependent on this changed file. The Environment for some of the programs that use the changed file is displayed as (QUA). Phantom files are also considered non-resident even though they have been created in the environment by Aldon LM(i). Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-25 . Objects that have not been changed but which are needed for testing a changed object are dependent on the changed object. That is. but its presence there is implied or required by one of the reference objects. Elsewhere in Aldon LM(i) documentation. The parentheses indicates that the object is non-resident in that environment. Reference Release and Environment Object dependencies are determined relative to one or more reference objects and relative to the presence of those objects in a specific environment of a specific release. Non-Resident Object One important use of the object dependency information is as an aid in populating an environment with copies of all the objects needed to test a changed reference object promoted into that environment. These two uses of the phrase are completely unrelated. but a copy is found using the object creation library list for the Quality Assurance environment. ” starting on page DO 4-28. For instructions on using this panel see “To act on objects dependent on a given “reference object”..” panels for a wide variety of purposes • During a promote job initiated with option 7 (Promote) from any of several “Work with.Acting upon Dependent Objects Access and use object dependency data from any of the following general starting points: • Starting with options 39 (Display requisite objects).” panels by typing Y in the Do you wish to select dependent objects for create field • During a checkout or emergency checkout by pressing F16 (Act upon dependent objects) • From the More Functions panel with option 6 (Act upon dependent objects) See “To display dependents of objects not defined to Aldon LM(i)” on page UG 2-45 in the “Aldon LM(i) User’s Guide” for more information.. This field is sometimes input protected if you display dependent objects while performing some actions. Panels used to act upon dependent objects from all of these starting points are similar and are discussed below.. Act upon Dependent Objects Panel Use the Act upon Dependent Objects panel shown in Figure 29 on page DO 4-28 to display a list of objects dependent on reference objects. Fields on this panel are discussed below: Upper Portion of the Panel Reference release Displays the name of the reference release containing the reference object or objects in the format group/application/release. 41 (Act upon dependent objects). DO 4-26 • Working with Objects Aldon LM(i) Daily Operations Reference . This panel displays: • Object dependencies established by the Aldon LM(i) automatic scan function accessed through the panel interface • Dependencies established manually by the user with object dependency commands. or 42 (Act upon dependent objects*) on several “Work with.. and act upon objects in the list. Reference environment Establishes the reference environment for the reference objects. Env column indicates the environment within the release containing the model object. The -. -. Lower Portion of the Panel The lower portion of the panel displays the list with one record for each dependent object. Reference object(s) For a list based on a single reference object. Environment (Views 1 and 4) Indicates the environment of each object listed. Y — When the reference environment is DVP. specifies the name of the developer whose libraries constitute the reference environment. lists the reference object using the format “object-name type attribute. developer If DVP is specified as the Reference environment. *MULT-n — The object is checked out to more than one developer.Resident -Release Env (View 4) For non-resident dependent objects. The number indicates the number of copies of the object currently in development. Dep (View 1) The “create dependent” field displays the following values: Y — the object depends on a reference object at create time (blank) — the object depends on a reference object at execution time Checkout Developer (View 1) This field displays the following values: name — The developer name the object is currently checked out to is displayed.If DVP. The -.” For a list based on several reference objects. Non-resident object environment appears in parentheses Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-27 . Crt. a Y in this field indicates the dependent object is currently checked out to a developer environment other than the current reference environment. This can only happen in the event of an emergency checkout or an additional standard checkout if multiple checkouts are permitted. Parentheses surrounding the environment designation of an object indicate the object is non-resident in that environment.Resident -Release column indicates the release containing the model object. press F19 (Review reference objects) to review the list of reference objects. displays the release and environment containing the next available copy of the object. *SAME indicates the model is located in the same release as the non-resident dependent object.Resident -. developer field. developer . If. Reference object . .Act upon Dependent Objects Note The same panel with some different options displays when selecting dependent objects for creation during a promote job. ALDON/ACMSDEMO/BASE PDN DVP. ITG. DO 4-28 • Working with Objects Aldon LM(i) Daily Operations Reference . 3. . in the Opt field by a task.) At the More Functions panel. PDN + Name ACTGLL *FILE PF *TOP. Position to . for Reference environment. Reference environment If DVP. press Enter. . : . developer field. . . . type option 41 or 42 and press ENTER On the Work with Tasks panel. press ENTER to redisplay the dependent object information relative to the new reference environment. type option 41 (all object in the task serve as reference objects) At the Check Out Objects or Check Out Objects (Emergency) panels. in the Opt field by the reference object. Crt Checkout Environment Dep Developer PDN Y PDN Y Type options. . starting characters 5=Browse source 17=Request promote* D Release AC/BAS AC/BAS (*=Combined job) 7=Promote* 30=Displsy log . type option 6 and press ENTER – – – The Act upon Dependent Objects panel displays: CACTDEPOBJ Reference release . in the If DVP. QUA. 2. . *BOT. In the Reference environment field.. 2=Edit 3=Check out* 4=Delete 13=Request checkout* 14=Create* Opt Object COMMPRT RCVPRT Type *PGM *PGM Attribute CBL RPG Subset: PriEnvObj:*CTL RefObj:Y Command ===> F3=Exit F4=Prompt F5=Refresh F12=Cancel F19=Review reference objects F10=View 4 F23=More options F11=View 2 F24=More keys Figure 29 . . type the name of the developer whose libraries constitute the reference environment. Act upon Dependent Objects : . 4. If you changed the Reference environment or If DVP. The Select Dependent Objects panel displays which is essentially the same as the Act Upon Dependent Objects panel but limited to selected additional objects for checkout. you typed DVP. type a three character environment abbreviation for the desired environment.To act on objects dependent on a given “reference object” 1. . Do one of the following: – At the Work with Objects by Release or Work with Objects by Developer panels. . press F16 (Select dependent objects) (Objects selected for checkout constitute the reference objects.. . . type the option number of the action you want to perform and press ENTER. . . 2=Res. Select one of the following: 1 — include both resident and non-resident objects 2 — include only resident objects 3 — include only non-resident objects Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-29 . . . . . . You must instead perform a checkout to place them there. . . . . 2=No. *NONE 1=Yes. . *ALL Recursive dependencies . . . . generic*. . . . . 3=Only + *ALL. . . . . . . . . 3=Non res *ALL. Y Create-dependent only . . . . . . if dependent 1 Dependent object type . . . . N=No Y=Yes. . To subset the Act upon Dependent Objects panel Prerequisite Display the Act upon Dependent Objects panel as described in “To act on objects dependent on a given “reference object”” on page DO 4-28 1. Complete the panel by working with the fields discussed below. *CTL Reference objects. . : Group . . 3=Only *ALL. then press ENTER to display dependent objects meeting all subset criteria. . . Reference release: Status in reference environment 1 Prior environments . . : Type choices. 3=Non res *ALL. : Status in reference environment 1 Prior environments . *ALL Sharing: Release . CSBSDEPOBJ Subset Dependent Objects List ALDON/ACMSDEMO/BASE PDN More: + Reference release . *CTL Reference objects. . if dependent 1 Other releases: Descendent release . . Notes You cannot create non-resident objects into the Development environment. D/I/Q. . . press Enter. *NONE + 1=Both. . . Press F5 (Refresh) after performing actions that move objects to update information displayed on the panel. In the Opt field by the dependent object you want to act on. . *CTL. . *CTL. : Reference environment . *NONE 1=Yes. . . .5. 2=No. . Press F17(Subset) to change dependent object list subsetting using the Subset Dependent Objects List panel shown in Figure 30 on page DO 4-29. . name. . 2=Res. : *NONE Application . D/I/Q. N F3=Exit F4=Prompt F5=Refresh 1=Both. . Status in reference environment Specify the kinds of dependent objects to include. type Y=Yes. .Subset Dependent Objects List Panel page 1 of 2 2. . N=No F22=More functions F12=Cancel Figure 30 . . specify the descendent releases from which you wish to list dependent objects. *ALL. (Development is not a controlled environment. Application. DO 4-30 • Working with Objects Aldon LM(i) Daily Operations Reference . Aldon LM(i) ignores this field. and Group fields to select releases of sharing applications from which to include dependent objects. The following values are available: 1 — (Yes) include reference objects in the list if also dependent 2 — (No) exclude reference objects from the list of dependent objects 3 — (Only) display only reference objects which are also dependent Descendent release If the reference release has descendents. The following values are available: *CTL — include the controlled environments Integration and Quality Assurance if they are prior to the reference environment. and Group If the reference release is of a shared application. Application. D/I/Q — type one or more single character environment abbreviations to include selected prior environments. Prior environments are those environments closer to Development relative to the reference environment specified above. *ALL — include dependent objects from all prior environments. Sharing: Release. if dependent Specify whether or not to exclude the reference objects on which the list is based from the list. to include dependent objects regardless of type. Objects selected with option 41 or 42 on the previous panel may be dependent on one another. If the reference release has no descendents. Type an object type to include only dependent objects of that type in the list. Production is a controlled environment. but would also require including Production environments of ancestor releases which is not supported in the current release). Dependent object type Accept the default value. Press F4 (Prompt) to select from a list of types. use the Release. *NONE — include dependent objects only from the reference environment.Prior environments Specify the prior environments from which to include dependent objects. Reference objects. . Type N to include objects dependent on the reference objects at create or execution time. . . . The Subset Dependent Objects List panel displays. . . 4. Press PAGE DOWN (ROLL UP) to display the second page of the Subset Dependent Objects List panel: CSBSDEPOBJ Subset Dependent Objects List ANNETTEW/SAVIO/BASE PDN Reference release . in the Opt field by the object that would be replaced by the promotion to parent you want to simulate. . . . Create-dependent only Select dependent objects by dependency type. name F3=Exit F4=Prompt F5=Refresh F12=Cancel F22=More functions Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-31 . : Reference environment . *NONE + *NONE. To see the impact of promotion to parent on dependents 1. . : Type choices. type 41 (Act upon dependent objects) and press ENTER to display the Act upon Dependent Objects panel. 3. At the Act upon Dependent Objects panel. . More: As if reference objects were promoted from release . 2. For example. *CHILD. press F17 (Subset). . Type N (No) to include only objects that are directly dependent on the selected objects. At the Aldon LM(i) main menu. type option 1 (Work with objects by release) and press ENTER to display the Work with Objects by Release panel. press Enter.Recursive dependencies Type Y (Yes) to include objects that are dependent on selected objects and those that are dependent on the dependents of selected objects. if you want to simulate promote to parent of an object from a delta release to its parent. At the Work with Objects by Release panel. Type Y to included only objects dependent on the reference objects at create time. type 41 by the record for the parent copy of the object. . . . *SAME. To View Object Histories To view the activity for multiple objects within an Aldon LM(i) release or application select option 7 (Display Log) from the Aldon LM(i) main menu. Each log entry can be associated with multiple tasks. At the second page of the Subset Dependent Objects List panel. select option 5 (Work with tasks) from the Aldon LM(i) main menu. type the name of the child release from which the object would be promoted to parent or press F4 (Prompt) to select from a list. To view the activity for multiple objects associated with an Aldon LM(i) task. type option 30 (Display log) next to the required object on one of the following panels: Work with objects by release Work with objects by developer Act upon dependent objects Work with requests and non-conflict conditions The selected entries are sorted by date and time. in the As if reference objects were promoted from release field. To view the activity for a single object. To display detail regarding the tasks associated with the object. Type option 30 (Display log) next to the task you are interested in and press ENTER. see “To view additional information for a log record” on page DO 4-34. 6. This happens when an object is active for multiple tasks simultaneously. Using the Development Log To Activate or Deactivate Development Log Use for an Application See “To Activate or Deactivate Development Log Use for an Application” on page 12-4. DO 4-32 • Working with Objects Aldon LM(i) Daily Operations Reference .5. Press ENTER to display objects which would be dependent on the reference object if it were promoted to the parent release on the Act upon Dependent Objects panel. release.To subset to limit entries displayed. the “Related Release” defaults to *PRMFRMCHD. Application. . . *BOT. Display Development Log ________ *TOP. . and Group are set to the values of that object. press F17 (Subset) to display the Subset Development Log panel. . Aldon LM(i) logs all development activities with the following single exception: Aldon LM(i) does not log any information. • Release.Display Development Log Panel.. press Enter. . see “Use Subsetting to Limit Entries Displayed” on page DO 4-33. application. date Type options. Creates in all other Aldon LM(i) environments are logged. the user who performed the operation that generated the log entry. Use this panel to limit the displayed entries by object name or type. View 1 of 5 Some Actions Produce Multiple Log Entries Creates in Development Do Not Produce Log Entries The promote to parent function generates log records for both the “From” child release and the “To” parent release. task. regarding creates in the Development environment. and if the child release allows promote to parent. Command ===> F3=Exit F4=Prompt F5=Refresh F9=Retrieve F10=View 5 F11=View 2 F12=Cancel F13=Delete F17=Subset F21=Print F22=More functions Figure 31 . . The defaults for the Subset Development Log panel are determined by the path used to access the panel. • If there is a child release associated with the object’s release. Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-33 . CDSPDEVLOG Position to . including comments. using option 30 (Display log) on one of the “Work with” panels. In all other cases. the defaults are as follows. related releases. 5=Display detail More: Act Er Opt Object Type Release Date Time Cde User Version Cd DEMOCBL3 *PGM ACM/BAS 8/11/93 21:24:13 PRM MARKE 00200001 47 CLNADRL *FILE ACM/BAS 8/11/93 21:41:45 RMC MARKE 00100002 CLNADRL *FILE ACM/BAS 8/11/93 21:41:48 RMC MARKE 00100001 CLNADRL *FILE ACM/BAS 8/11/93 21:43:01 CAN MARKE 00100003 CLNADRL *FILE ACM/BAS 8/11/93 21:43:48 PRM MARKE 00200000 CLNADRL *FILE ACM/BAS 8/11/93 21:44:07 PRM MARKE 00100002 DEMOCBL2 *PGM ACM/BAS 8/11/93 21:44:07 PRM MARKE 00100001 DEMOCBL3 *PGM ACM/BAS 8/11/93 21:45:51 RMR MARKE CLNADRL *FILE ACM/BAS 8/11/93 21:46:42 PRM MARKE 00300000 DEMOCBL1 *PGM ACM/BAS 8/11/93 21:47:03 PRM MARKE 00200000 DEMOCBL1 *PGM ACM/BAS 8/11/93 21:47:19 PRM MARKE 00100002 Subset: Rel:ALDON/ACMSDEMO/BASE (*BOT displayed: New display shows late . or date. Use Subsetting to Limit Entries Displayed From the Display Development Log panel. If the Subset Development Log panel is accessed through a specific object. the default is *ANCESTOR. . The *ANCESTOR subset includes activity in ancestor releases. . . . . . .Note The *PRMFRMCHD subset includes activity in the child release. . . . . . do one of the following: – Press the F10 or F11 key to cycle through the four available views on the Display Development Log panel — or— – In the Opt field by a record. . . . No activity from ancestor or child releases is shown with this subset. . use the Related releases field to limit the records displayed to those in a selected release. Printing Development Log Reports Print the log entries currently selected at any time by pressing F21. . . : : : : : : : : ILEPGM PDN DOUGS/DMS52/DMS52 CRT Object created 03/19/99 09:06:02 PDN Text ASLKJF DDDD Object type . . . : Version . . . . type option 7 (Display log) and press ENTER to display the Display Development Log panel. . . From environment Task NBR01 NBR02 NBR03 NBR04 NBR05 NBR06 Command ===> F3=Exit Type BUG ENH DOUGS *SAME More: + F4=Prompt F9=Retrieve F12=Cancel DO 4-34 • Working with Objects Aldon LM(i) Daily Operations Reference . . . . See the on-line help text and “Custom Reports. . . option 7 (Display log): • Release. Environment . Release . : Error code . . To view additional information for a log record Prerequisite At the Aldon LM(i) main menu. . . • At the Display Development Log panel. . . . . . If the Subset Development Log panel is accessed from the main menu. . . . .” starting on page DO 6-2 for details on customizing the report to meet your needs. . . . . . . . . Date . : User . Comment . . . Time . . . Application. . and ancestors or children of that release. . : From release . Activity . . type 5 (Display details) and press ENTER to display the Development Log Entry Detail panel: Development Log Entry Detail . and Group default to *USRDFT • “Related Release” defaults to *NONE. Selecting Log Entries for Display by Related Releases On the Subset Development Log panel (F17=Subset). . . : *PGM 00200000 CDSPLOGDTL Object . . . Development Log Action Codes Table 1 . or member Source code merged from multiple object versions Object merged from selected release to target release(s) Object promoted to parent (child record) Object promoted with leave resident option Object promoted Object promoted to parent (parent record) Checked out object transferred to different developer Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-35 . file.Development Log Action Codes Code ACT ADD BKL BKO CAN CHG CHK CLC CRN CRT CRR DEF DLA DLE DLT ECK EXL EXT INL INS LOD MGC MGP MOV MRG MRL PRC PLV PRM PRP RAS Text Object activated via activate release function Object added to release Object installed live has been backed out Object deployed has been backed out Check out or add of object cancelled Object description changed Object checked out Object cleared of conflicts Object created as a “non-resident” object Object created (note: creates in Development are not logged) Object created for retired object Library groups defined for the object for a release in which it is non-resident Object deleted from the archive library Object deleted from environment Object deleted from the release Object checked out with emergency checkout Object extracted for install live Object extracted for deployment Object installed for install live Object installed for deployment Object loaded to release Object merged to parent (child record) Object merged to parent (parent record) Object moved to new library group. Table 2 . The first digit of each error code describes the severity of the error and the second digit describes the cause of the error.Table 1 .Development Log Error Codes First Digit 1 2 3 4 Warning Completed with errors Failed action Action not attempted Second Digit 0 1 2 3 4 5 6 7 8 Function failed . see “Object Version Numbers” starting on page UG 3-3 in the “Aldon LM(i) User’s Guide”. Table 2 lists the possible values. DO 4-36 • Working with Objects Aldon LM(i) Daily Operations Reference .Development Log Action Codes (Continued) Code RET RMA RMC RMF RMH RMR RPP RQC RQI RQP RST Text Object retired Acknowledgement condition for object removed Cleared conflict condition for object removed Failed condition has been removed Hold condition has been removed Request condition for object removed Request to promote to parent Request to checkout Request to install live Request to promote Object restored from archive to development Development Log Error Codes Error codes are two digits long.No detail available Object not found Source not found Library or developer not found Access problem Delete of old object failed Archive of old object failed Failed due to cancellation of job Object time stamp earlier than source Object Version Numbers For basic information on object version numbers. excluding all vowels and the letter Y. when a position reaches Z. Aldon LM(i) Daily Operations Reference Working with Objects • DO 4-37 . Object version numbers use a 30-base number system.The eight digits of an object version number are divided into two functional parts: the first three digits are the “development number” and the last five digits are the “creation number.” Some rules regarding the incrementing of both parts of object version number: Function Add Object Map or Load release. the next number to the left of it will be incremented. The farthest right value of the DVP# side or CREATE# side will be incremented through all numbers and letters before the next position is incremented. Therefore. first time existence for the object Map or Load release. X X X X X X X X X X X X The Aldon LM(i) copy release function maintains the version number of the object it was copied from. Increment Create No. The Aldon LM(i) merge to parent option retains the version number of the merge-from (child) object in the new object. The numbers 0-9 are used first. then the letters B-Z. copies of object exist in the application Activate a release Compile in Development Promote out of Development (with compile or CRTDUPOBJ) Promote from ITG or QUA with compile Promote from ITG or QUA without compile CRTNONRES with compile CRTNONRES without compile Compile in place in a controlled environment No Change X X Increment DVP No. Promote to parent is treated as promotes within controlled environments. press Enter. . Deleting log entries saves disk space and speeds searches. . From earliest entry through date . DO 4-38 • Working with Objects Aldon LM(i) Daily Operations Reference . Press Help or F1 to consult the on-line help text for assistance.Delete Development Log Entries panel 4. To delete development log entries Prerequisite You must have “Work with release definition” authority to a release in order to delete development log entries for that release. Sign on to Aldon LM(i) as a user with Work with release definition authority for the release or releases for which you wish to delete development log entries. BASE + *ALL. . . Release . . . . . At the Display Development Log panel. . . . . . . 2. . 2=Run in batch Command ===> F3=Exit F4=Prompt F5=Refresh F12=Cancel F22=More functions Figure 32 .Deleting Development Log Entries Delete development log entries from time to time if you wish. . Application . Delete log entries online or as a batch job. . name ALDONDEMO + Name ALDON + Name *CURRENT 1 *CURRENT. date 1=Run interactively. At the Aldon LM(i) main menu. Group . . At the Delete Development Log Entries panel. . . 1. type option 7 (Display log) and press ENTER to display the Display Development Log panel. . . . complete the panel and press ENTER to delete development log entries. . Run option . press F13 (Delete) to display the Delete Development Log Entries panel: CDLTDEVLOG Delete Development Log Entries Type choices. 3. . generic*. . condition codes.” starting on page DO 5-17 • “Working with the System i PCO Session.Aldon LM(i) Daily Operations Reference Daily Operations DO Chapter 5 Working with Conditions and Conflicts This chapter introduces Aldon Lifecycle Manager (System i Edition) (Aldon LM(i)) conflicts.” starting on page DO 5-7 • “Setting Your Default Compare and Merge Method.” starting on page DO 5-2 • “Working with Requests and Non-Conflict Conditions.” starting on page DO 5-19 Aldon LM(i) Daily Operations Reference Working with Conditions and Conflicts • DO 5-1 . The following topics are included: • “What are Conflicts and Non-Conflict Conditions?. It explains conflict types. and describes the process for working with these conditions.” starting on page DO 5-13 • “Comparing With Harmonizer. and non-conflict conditions. requests.” starting on page DO 5-3 • “Working with Conflicts.” starting on page DO 5-12 • “Merging With Harmonizer. and hold. acknowledgement. the PF in the production environment of the child release will not be populated with data. Conflicts Defined A conflict is used to notify that a change to one instance of an object may need to be applied to one or more other instances of the object that could be based on the version being changed. Sibling releases can be manually defined as notifiers. ANALYZER acknowledgement reports achievement of the specified degrees of test coverage. • The ANALYZER hold condition is created during the promotion to an ITG or QUA environment where minimum testing requirements have been set. DO 5-2 • Working with Conditions and Conflicts Aldon LM(i) Daily Operations Reference . Promotion is restricted until the condition has been removed. promotion. • A request condition is created when a user requests checkout. Conditions provide information. • A failure condition is created when a data set update has failed.What are Conflicts and Non-Conflict Conditions? Conditions Defined A condition is a flag in the Aldon LM(i) object database on a particular instance of an object. Aldon LM(i) creates an acknowledgement condition when you promote an object back to production after it was checked out using the emergency checkout function. ancestor releases always notify descendent releases. or install live of an object. see “Types of Requests and Non-Conflict Conditions” on page DO 5-5. Conflicts are created when the notifying instance of an object is changed. • A hold condition is created when the physical file in the parent is checked out to the child release. and in some cases restrict actions on the object until the condition is removed. Promotion to the production environment of the child release is restricted until the condition has been removed. Notifying instances are defined by the relationship of releases within an application. For more information. Promotion is restricted until the condition has been removed. For example. There are four condition types: request. This condition is designed to make the user aware that unless they take some action. failure. The condition is automatically deleted when the specified percentage of code has been exercised. The acknowledgement condition does not restrict object movement. • An acknowledgement condition is created to notify development managers that normal procedures have been bypassed for a particular object. Promotion of conflict objects may be restricted until the conflict has been cleared. Aldon LM(i) can be set up so that specific users cannot perform these operations themselves. ITG or QUA environment in the release • An object that is active (in development. For information about conflict types. When there is a change in the production copy of an object in the notifying release that is also present in any environment of the notified release. or quality assurance) in an ancestor release is checked out in a descendant release • An object present in a notified release is checked out. Aldon LM(i) creates a release conflict on all copies of the object in the notified release. loaded. • Conflict object – this is the object instance in the notified release that was based on the changed object before the change was made. or copied into a “notifying release. but must request these operations.There are always two object instances involved in any conflict: • Changed object – this is the object instance in the notifying release whose change has caused the conflict. see “Common Types of Conflicts” on page DO 5-9. or promote an object. • An object is promoted to a parent release from a child release while the object is active in the parent release Working with Requests and Non-Conflict Conditions Request conditions indicate that a user wants to check out an object. Aldon LM(i) Daily Operations Reference Working with Conditions and Conflicts • DO 5-3 .” A notifying release is a release that notifies another release of the same application of changes in objects common to both releases. Common Causes of Conflicts • An object already in development is checked out again to another development environment • An emergency checkout is performed and an instance of the object resides in a development. Request conditions are displayed on the Work with Requests and Non-Conflict Conditions panel. perform an install live of an object. integration. and then wait until someone with authority fulfills the request. Requests can be completed by applying the appropriate option to condition records on the Work with Requests and Non-Conflict Conditions panel or to object records displayed on the Work with Objects by Release or Work with Objects by Developer panel. . . type option 4 (Conditions menu) and press ENTER to display the Conditions menu. The record also includes the name of the user whose action created the condition.. At the Conditions menu. 3=Check out* 4=Remove 7=Promote* 30=Display log 47=Install live* Opt Object AAAAAAA ACTGLL ACTGLP ACTGLP2 AFFMAS AFFMAS AFFTRN AFFTRN ALTERTBL Type *FILE *FILE *FILE *FILE *FILE *FILE *FILE *TABLE D Release GM5/BAS D50/D50 K D50/BD3 K D50/D50 K GM5/BAS K GM5/DEL K GM5/BAS K GM5/DEL K D50/D50 Environment DVP ADA PDN DVP DOUGS ITG DVP DOUGS DVP DOUGS DVP DOUGS DVP DOUGS DVP DOUGS Cnd R C A E R C R P R C R C R C R C R C Date 02/07/07 02/14/07 01/18/07 01/18/07 01/18/07 01/18/07 01/18/07 01/18/07 01/18/07 Subset: Rel:ALDON/ACMSDEMO/BASE Command ===> _________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F10=View 4 F11=View 2 F12=Cancel F17=Subset F19=Work with objects F24=More keys Figure 33 .Work with Requests and Non-Conflict Conditions panel Each condition record lists the name. This method displays all conditions that meet your current subsetting specifications. type. *BOT.. 2. a two character condition abbreviation. Press F11 to view the comment associated with each request or condition. press Enter. release. type option 2 (Work with requests and non-conflict conditions) and press ENTER. At the Work with Objects by Release or Work with Objects by Developer panel. . -or3. . . This panel displays a list of the active conditions and allows you to select specific conditions to work with. . by an object with a condition. __________ *TOP. At the Aldon LM(i) main menu. CWRKCND Position to Work with Requests and Non-Conflict Conditions .) and press ENTER.To display the Work with Requests and Non-Conflict Conditions panel 1. This method displays requests and non-conflict conditions only for the selected object. starting characters (*=Combined job) 27=Promote to parent* More: + Initiating User ALISONM DOUGS DOUGS DOUGS DOUGS DOUGS DOUGS DOUGS DOUGS Type options. and environment of the associated object. DO 5-4 • Working with Conditions and Conflicts Aldon LM(i) Daily Operations Reference . Press F17 (Subset) to display the Subset Requests and Non-Conflict Conditions List panel. Checkout requests list the name of the developer designated to receive the object in the environment column. Use the subset panel to limit the entries displayed. type 28 (Work with conditions. and the date that the condition was created. use option 4 (Remove). but the actual deployment has not yet occurred. Use option 7 to fulfill promotion requests. Use option 47 to fulfill install live requests. Failure..” Sections below discuss working with conditions within each category. failure conditions is “F”.Cnd Column Codes: Requests. and 4 provide additional information about when conditions were created.) by a non resident delta object. See “Installing Live” on page DO 3-29 for discussions of completing install lives. Acknowledgements. Aldon LM(i) Daily Operations Reference Working with Conditions and Conflicts • DO 5-5 . Request for Install Live (R L) A request for install live of the object has been made. Request for Promotion (R P) A promotion request for the object has been made. See “Checking Out Objects” on page DO 3-2 for discussions of completing checkouts. and Hold The first character of the Condition code in the Cnd column categorizes the condition by condition type. If you type 28 (Work with conditions. acknowledgement is “A”. See “Promoting Objects” on page DO 3-10 for discussions of completing promotes. For example. conditions for the parent copy of the object are displayed. Note for Delta Releases If you are working with a delta release. Views 2. but the actual checkout has not yet occurred. To cancel requests or clear conditions To cancel requests or clear acknowledgement conditions. and hold is “H. the users involved. Use option 3 to fulfill checkout requests. but the actual promotion has not yet occurred. and the reference release and environment involved. conditions on the parent copy are not displayed. 3.. Types of Requests and Non-Conflict Conditions Request for Checkout (R C) A checkout request for the object has been made. for request conditions the first character is “R”. and the delta release does not contain a copy of an object. on the Work with Objects by Release panel. Request for Promotion to Parent Release (R R) A request has been made to promote the object to the parent release of the release in which it currently resides. 2. DO 5-6 • Working with Conditions and Conflicts Aldon LM(i) Daily Operations Reference . on the Work with Objects by Developer or Work with Release Objects panel. The acknowledgement condition does not restrict object movement. Use option 27 to fulfill promote to parent requests. Promotion is restricted until the condition has been removed. This automatically updates the data set with the new format of the file. remove the condition with option 4 on the Work with Requests and Non-Conflict Conditions panel. ANALYZER Cleared (A A) The copy of the program object associated with this conflict met testing requirements that were specified in Aldon LM(i). Data Set Update Failure (F T) A data set associated with the environment the file was promoted into or created in was not updated successfully. Correct the problem that prevented the data library update. Use the following steps to clear this condition: To remove a data set update failure condition 1. 3. This condition warns that programs may fail with file level checks. Failure to update one or more data sets with Monitor for update errors set to Y (Yes) with a promoted file creates a fail test data update condition (F T) to warn that testing of the file may not be complete. but the actual promotion has not yet occurred. Emergency Acknowledgement (A E) An emergency checkout/promotion acknowledgment warns supervisory personnel that the normal development and testing cycle has been bypassed by promotion directly to production of an object checked out with the emergency checkout function. See “Moving Objects to a Parent Release” on page DO 3-19 for discussions of completing promotes to a parent release. The test coverage is measured by ANALYZER when you run the ANALYZER Display Report. Re-create the file in-place in the desired environment using option 14 (Create). Provided the update ran successfully. At the Work with Objects by Release or Work with Objects by Developer panel. This condition prevents promotion of the file into the production environment of the delta but not into Integration or Quality Assurance. Promotion is restricted until the condition has been removed. During promotion. then promote the object. You can select the specific conflict(s) to work with. and the changed object. type option 4 (Conditions menu) and press ENTER to display the Conditions menu.ANALYZER Hold (H A) You set testing requirements for this copy of the program object on promotion into the current environment. Delta Release Data Hold (H D) The physical file associated with this condition was checked out to a Delta release from another release. Aldon LM(i) changes this condition to an “A A” ANALYZER acknowledgement condition when ANALYZER reports achievement of the specified degrees of test coverage. type 12 (Work with conflicts. Working with Conflicts A conflict may limit the promotion of an object. conflict type.) and press ENTER. ANALYZER temporarily instrumented the program for collection of testing statistics. see “Establishing and Meeting Testing Standards with ANALYZER” starting on page UG 2-54 in the “Aldon LM(i) User’s Guide”. ANALYZER evaluates test coverage when you run the ANALYZER Display Report. To display the Work with Conflicts panel 1.. The Work with Conflicts panel displays a list of conflicts with the status. type option 1 (Work with conflicts) and press ENTER. This method displays all conflicts that meet your current subsetting specifications. -or3. clear the conflict. At the Conditions menu. 2. by an object with a condition. This method displays conflicts only for the selected object. For more information about ANALYZER. Resolve the differences between the conflicting objects. Aldon LM(i) Daily Operations Reference Working with Conditions and Conflicts • DO 5-7 . The condition reminds users that manual loading of data into the file from other releases may be required.. At the Aldon LM(i) main menu. Changed Object Rel Environment * QUA D50 ITG D50 PDN D50 ITG D50 PDN DS2 PDN D50 ITG D50 PDN D50 DVP DOUGS D50 DVP DOUGS D50 ITG Type options. . release. . The record also includes the conflict status. starting characters (*=Combined job) 35=Compare More: + . Active (ACT) Restrictions on promoting the conflict object are defined at the release level.Work with Conflicts Panel Each conflict record lists the name.This panel displays a list of the conflicts and allows you to select specific conflicts to work with. . and the release and environment of the changed object. 2=Clear* 5=Display detail Opt Object ACMSLIB ACTGLL ACTGLL ACTGLL ACTGLL ACTGLL ACTGLL ACTGLL ACTGLP ACTGLP ACTGLP2 Type *SRCMBR *FILE *FILE *FILE *FILE *FILE *FILE *FILE *FILE *FILE *FILE 19=Merge 30=Display log Sts ACT AP ACT AP ACT ACT AP ACT INA INA AP Typ MCK RCK RCK RCK RCK RCK RCK RCK RCK RCK RCK D Release DHS/DB1 D50/DS2 D50/DS2 D50/DS3 D50/DS3 D50/DS3 D50/BD3 D50/BD3 K D50/DS2 K D50/BD3 K D50/DS2 Environment DVP DMITRIS PDN PDN PDN PDN PDN PDN PDN PDN PDN PDN Subset: Rel:ALDON/ACMSDEMO/BASE Command ===> _________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F10=View 4 F11=View 2 F12=Cancel F17=Subset F19=Work with objects F24=More keys Figure 34 . Work with Conflicts *TOP. press Enter. Use the Subset panel to limit the entries displayed. Restrictions on promote are the same as for an active conflict. and environment of the associated object. Press F11 to view the comment associated with each conflict. . a three character conflict type abbreviation. . DO 5-8 • Working with Conditions and Conflicts Aldon LM(i) Daily Operations Reference . *BOT. Active pending (AP) Applies to release conflicts where the changed object is in either ITG or QUA of the notifying release. Press F17 (Subset) to display the Subset Conflicts List panel. View 2 indicates if there is a reference source available for merge. . CWRKCNF Position to . It indicates that the changes may not yet be finalized so it may be too early to resolve the conflict object. type. Conflict Status A conflict can have one of the following statuses. Restrictions on promote are the same as for an active conflict. Promote from Child Conflict (PFC) . Add Conflict (ADD) Adding a new version of the object to a notifying release sets a conflict on any instance resident in a notified release. This is the object instance in the notifying release whose change has caused the conflict.the changed instance of the object was checked out in the notifying release. Merge Conflict (MRG) . each copy is both a changed and a conflict object in relation to each other. For instance.an emergency checkout caused the changed object to go into the production environment ahead of the conflict object.Clear pending (CP) Any active conflict that will be cleared by the promotion of a cleared conflict.is created when a merge to parent is done and there is an active instance of the object in the parent release. Multiple Checkout Conflict (MCK) . Emergency Checkout Conflict (ECK) . Release Checkout Conflict (RCK) . the conflicting object now contains the changes made to the changed object. Aldon LM(i) Daily Operations Reference Working with Conditions and Conflicts • DO 5-9 .More than one instance of the object is checked out to development in the same release. There are no restrictions on promoting the object. The conflict object can normally be promoted. Common Types of Conflicts These conflicts are based on the changed object. Release Conflict (REL) . The exception being an emergency check out when the conflict object would go into the production environment that is the target of the emergency checkout.the promotion of an object from a child release to the production environment of the parent release creates a conflict on any instance active in the parent release. Inactive (INA) Any conflict for which the changed object is in a development environment.A conflict type of REL displays when the changed object and conflict object reside in different releases. Cleared (CLR) A conflict that has been marked as cleared. Delete Changed Object of Cleared Conflict (DCC) When a conflict is cleared. This is the object instance in the notifying release whose change has caused the conflict. Therefore. if the changed object is subsequently deleted. Foreign Checkout Conflict (FRN) Can occur if an object is added or checked out to a notifying release as a result of the ACMSCHKFRN command. therefore it is assumed changes were made to the conflict object to match the changed object. DO 5-10 • Working with Conditions and Conflicts Aldon LM(i) Daily Operations Reference . Delete From Environment Conflict (DLE) Deleting the object in a notifying release creates a conflict in a child release only if there is an instance in a parent release of the deleted object. or QUA) when it was deleted and that there is another instance of the object in a higher environment within the same release.Delete Conflict (DLT) Deleting the version in a notifying release sets a conflict on any instance resident in a notified release. Activate Conflict (ATV) Indicates that the conflict was created during the activation of a new release that was set as the notifier of another existing release. Retiring the “middle” release instance rather than deleting it always causes a RCK conflict. Load Conflict (LOD) Loading a new version of an object to the production environment creates a conflict on any active instance in the same release or resident in notified releases. Aldon LM(i) creates a new conflict if the following conditions are met: • The conflict was cleared in the development environment. ITG. • The changed object was resident in an active environment (DVP. Aldon LM(i) assumes that changes were made to the conflict object to match the changes made to the changed object. Less Common Conflict Types These conflicts are based on the changed object. Cleared conflicts are marked. No further action is needed. type a 19 to merge modified versions of source into a single source file. check the conflict object out. Clear the conflict on the development copy only. For more information about using Harmonizer. Promoting Multiple Checkouts Aldon LM(i) simplifies promotion following multiple checkouts by enabling you to promote inactive (changed object is in development) conflicts and specifying the environment up to which active conflicts can be promoted. Aldon LM(i) Daily Operations Reference Working with Conditions and Conflicts • DO 5-11 . the conflict can be cleared from Work with Conflicts panel by typing 2 (Clear*) by the conflict record. If you have Harmonizer installed. 3. You can merge the changes manually or use Aldon Harmonizer or Aldon Harmonizer (Windows Edition).” starting on page DO 5-13. 4. merge changes from the conflict copy and the changed copy of the object to prevent overwriting of changes on promotion. not deleted. compile and test.Resolving and Clearing Conflicts Before clearing a conflict. Use Harmonizer or manually apply the required changes. 5. Each conflict has its own internal tracking number. 2. Determine if any changes are required to the conflict object. Clearing of a conflict on one instance of an object automatically clears related conflicts on other versions of the object when the cleared version is promoted to the environments of the other versions. You can now promote the development copy of the object using option 7 (Promote*). If Harmonizer is not installed. If changes are required. For more information about using Harmonizer. this option does not appear. Promoting Cleared Conflicts Aldon LM(i) tracks related conflicts and auto clears conflicts where possible. see“Merging With Harmonizer. If not.” starting on page DO 5-13. until all objects affected by the conflict are cleared. To clear a conflict 1. see“Merging With Harmonizer. Rules for Promoting Conflict Objects • There are no restrictions on promoting a cleared conflict object. Set User Operation Defaults panel. in the Opt field. and clear pending object may be promoted are governed by the release definition. except to a production environment that is the target of an emergency checked out object. Please specify your default entry for this option. That is. Press F22 (More functions) from most panels within Aldon LM(i) to display the More Functions panel. Compare and merge methods The compare and merge functions include the following option if both Harmonizer and Harmonizer for Windows are installed on your system. • The environments to which an active. active pending. users can set their individual default for the Compare and Merge method to be used. At the More Functions panel. see “Defining a Release” starting on page SA 14-1 in the “Aldon LM(i) Setup and Administration Reference” Setting Your Default Compare and Merge Method When both Harmonizer (Batch) and Harmonizer (Windows) are available.• An inactive conflict object can be promoted. • A non-cleared conflict object can never be promoted to the environment of the changed object. 2=Batch F3=Exit F5=Refresh F12=Cancel Figure 35 . To set default options for compare and merge method 1. type 3 (Set operation defaults) and press ENTER. Compare/merge method . The Set User Operation Defaults panel displays. More: 5. the conflict object can never overwrite the changed object unless the conflict has been cleared. For more information. .: CUSROPRDFT Set User Operation Defaults Type choices. press Enter. if it is available. page 3 of 3 DO 5-12 • Working with Conditions and Conflicts Aldon LM(i) Daily Operations Reference . 1 1=PC. Compare and merge methods field. Note Merge (option 19) is not available if: – – Harmonizer or Harmonizer (Windows Edition) is not installed The object is not source based Aldon LM(i) Daily Operations Reference Working with Conditions and Conflicts • DO 5-13 . In the Opt field by the conflict record. To resolve a conflict using Merge We recommend that the conflict object be checked out prior to executing the merge and the merge should be done against the conflict on the checked out copy. Page Down to the third panel to 5. Use the Page Up or Page Down key to move between the three panels. displays. 1. The Merge Source panel displays. To use Harmonizer (Windows Edition) you must also have the PC part of the product installed on your PC and be using IBM Client Access to view the Aldon LM(i) screens. Merging With Harmonizer Resolving Conflicts Using Merge You must have a licensed copy of Aldon's Harmonizer or Harmonizer (Windows Edition) installed and set up to use this function. shown in Figure 25 on page UG 2-49.2. For more information. 2. type 19 (Merge) and press ENTER. see “Setting up Harmonizer and Harmonizer (Windows Edition)” starting on page SA 5-1 in the “Aldon LM(i) Setup and Administration Reference”. type 12 (Work with conflicts) and press ENTER. At the Work with Objects by Developer or the Work with Objects by Release panel. The Work with Conflicts panel. Type 1=PC to run interactively or 2=Batch for batch execution for the compare and merge methods. in the Opt field by the object flagged with the conflict condition. . . . . . . . The *DVPSRC option replaces the existing checked out source with the output from the merge. The left pane displays the source for the conflict object and the right pane displays the source of the changed object. Merge source into: File . . . . . . . . . “MERGESRC” prevents overlay of source members by the same name that might be present in your developer library. . . . . Comment for log . . Release .– CMRGSRC The reference source is not available Merge Source : : : : : ACMSLIB *SRCMBR DMITRIS/DIMAAPP/BASE1 DVP DMITRIS BASE1 Environment . . . You may set your default of PC or batch from F22 More options. Library . see “Navigating The PC Merge Window” starting on page DO 5-15 in the “Aldon LM(i) Daily Operations Reference”. . . *DVPSRC Name 1=PC. . . . . 5. . . Press ENTER. The merged source is output to the requested file. MERGESRC DMITRIS2 Name. .Merge Source panel 3. DO 5-14 • Working with Conditions and Conflicts Aldon LM(i) Daily Operations Reference . Object type . At the Merge Source panel identify the file and library to receive the merged source produced by Harmonizer. You can use any Aldon LM(i) library you choose. . press Enter. Merge method . For PC— The compare screen is displayed as a separate window on your PC. and changed lines being applied to the reference source and from which of the two sources in conflict the change originated. For batch jobs— A batch job is submitted that produces a printed report indicating additions. The merge result may be edited before saving. 2=Batch Command ===> _________________________________________________________________ F3=Exit F4=Prompt F9=Retrieve F12=Cancel F15=Full name Figure 36 . deletions. The bottom pane displays the results of the merged members. . . . type 1 (PC) to run the merge job interactively. . . Environment . . . If merge method displays as 1 or 2 and is not changeable. This option is only available if the object is already checked out and the merge method selected is PC. Accepting the default file name. . . then the product to support the other function has not been installed or set up. . 4. . . . Changed object: Release QUA Type choices. For more information. . . . : Object . Type 2 (Batch) for batch execution. In the Merge method field. 8. Deleted lines are shown with a strike through. You can use F5 and F6 to jump between conflicts and use Ctrl A to accept conflicts or edit the merged source before saving. The letters beside the sequence number and change date in the top panes represent: R— Matches reference source I— Inserted D— Deleted The letters beside the sequence number and change date in the bottom pane represent: R— Matches reference source in both sources A— Changed in source shown in top left pane B— Changed in source shown in top right pane The merge result is editable so conflicting records can be instantly resolved. 7. When you have completed the merge activities. Aldon LM(i) Daily Operations Reference Working with Conditions and Conflicts • DO 5-15 . If this dialog is closed without saving the merged member. Navigating The PC Merge Window The top panes show the differences between the two objects in conflict and the reference object. If not already checked out. Promote the copy containing the integrated changes from Development. Clear the conflict condition as described in “To clear a conflict” below. Compile and test the new merged source. a message box displays informing you that the merge result will not be saved and do you want to continue. 9.6. clicking Save displays the save confirmation window indicating where the merged source is to be saved. The bottom pane shows merged source. check out the object and replace the checked out source with the merged source. Select N (No) to return to the merge window. Select Y (Yes) for the merge window to close with no save. Conflicting records are highlighted in yellow and occur where the same record was changed in both the sources being merged. Once the save is complete, the PC program runs the System i clean up command and then closes. Figure 37 - PC Merge Window Batch Merge Report The printed batch report identifies additions, deletions, and changed lines being applied to the reference object and from which of the two objects in conflict the change originated. For more information, see Harmonizer Users Guide. Figure 38 - Batch Merge Report DO 5-16 • Working with Conditions and Conflicts Aldon LM(i) Daily Operations Reference Comparing With Harmonizer Selecting Objects to Compare Use Compare (option 35) to select the two instances of a source based object to compare. The member selected on the Compare panel becomes the “comparefile copy.” The newer version of a program is usually selected as the comparefile copy. To select copies of the object to compare 1. At the Work with Objects by Developer, Work with Objects by Release, or the Work with Conflicts panel, in the Opt field by the object, type 35 (Compare). 2. Press ENTER. The Select Copies of Object for Compare Source panel displays. Note If Harmonizer or Harmonizer (Windows Edition) is not installed, option 35 is not available. Select Copies of Object for Compare Source ARS277 CATHY/CATHY Object type . . . : Selected release . : *PGM CATHYC CSELSCP Object name . . : Application . . : Type choice. Compare method . . . . . Type options, press Enter. 1=Select as compare file Opt 2 1 Environment QUA PDN DVP CATHYC DVP CATHY3 PDN PDN 1=PC, 2=Batch 2=Select as reference file Lvl BASE BASE 1 1 1 BASE Release CATHYC CATHYC DELTA1 DELTA1 DELTA1 CATHYB Command ===> _________________________________________________________________ F3=Exit F4=Prompt F9=Retrieve F12=Cancel F15=Full name Figure 39 - Select Copies of Object for Compare Source Panel 3. In the Compare method field, type 1 (PC) to run the compare job interactively. Type 2 (Batch) for batch execution. You may set your default of PC or batch from F22 More options. 4. If the compare option was taken from the Work with Conflicts display, the changed object defaults to be the compare source (1=Select as compare file) and the conflict object defaults to be the reference source (2=Select as reference file). When coming from the Aldon LM(i) Daily Operations Reference Working with Conditions and Conflicts • DO 5-17 Work with Objects by Release or Developer panel, the selected instance defaults to the compare file (1) and the reference file (2) must be selected. 5. Press ENTER. Note For batch jobs— A batch job is submitted that produces a printed report indicating additions, deletions, and changed lines made to the compare version. For PC— The compare screen is displayed as a separate window on your PC. The left pane displays the compare file and the right pane displays the reference file. Differences are highlighted by lines connecting the two panes. For more information, see “Navigating The PC Merge Window” starting on page DO 5-15 in the “Aldon LM(i) Daily Operations Reference”. Navigating The PC Compare Window Harmonizer (Windows Edition) indicates the additions, deletions, and changed lines in the compare window. The differences are colorfully identified with highlighted blocks pointing to the differences. You can select “Sync Panes” from the View drop-down list box, to enable your window panes to scroll in sync. Use F7 and F8 to skip to the next difference. When you have completed the compare, close the window. All ways of closing the window work the same. The PC program runs a command on the System i to clean up the work files. Figure 40 - PC Compare Window DO 5-18 • Working with Conditions and Conflicts Aldon LM(i) Daily Operations Reference Batch Compare Report The printed report identifies additions, deletions, and changed lines. Figure 41 - Batch Compare Report Working with the System i PCO Session Harmonizer (Windows Edition) is only available from within Aldon LM(i). After you have selected the compare or merge options, press ENTER. The System i PCO Session N command Prompt window displays and remains blank. Figure 42 - PCO session A command prompt Aldon LM(i) Daily Operations Reference Working with Conditions and Conflicts • DO 5-19 The compare or merge panel then displays as a separate window. Returning focus to the Aldon LM(i) session allows you to continue working on that panel without affecting the compare or merge displayed. Note Be aware that if you select multiple simultaneous merges to the same target source as you close each merge the source will be overwritten with the output from that merge. The PCO session N command prompt window must remain open during the compare or merge session. with a new window being opened for each one. Further compares and merges may be selected. DO 5-20 • Working with Conditions and Conflicts Aldon LM(i) Daily Operations Reference . Closing it causes the compare or merge panel to terminate without saving the merge output or cleaning up the work files in System i. Aldon LM(i) Daily Operations Reference Daily Operations DO Chapter 6 Reports Overview of Reports Many Aldon Lifecycle Manager for System i (Aldon LM(i)) panels include a print function which, when used with subsetting criteria, provides a wide variety of custom reports. Aldon LM(i) also provides fixed format reports to display the results of operations, Aldon LM(i) setup values, and information about applications, releases, objects, and tasks. This chapter describes and provides an example of the custom report printing capability and provides samples and descriptions of the most important fixed format reports. Page Headings Headings print at the top of all report pages. On the first header line, the product and version appear at the left, the name of the report is centered, and the page number appears at the right. On the second line, the name of the printer file appears at the left, copyright information is in the center, and the date and time the report was generated appear at the right. The first page of all reports also lists the Job number, profile, and device or program from which the report was requested at the left on line three, and the CPU serial number (or “Demo at”) and company name in the center of line four. The company name is specified during the installation procedure and may be changed by re-running the Install program. Aldon LM(i) Daily Operations Reference Reports • DO 6-1 Custom Reports Create custom reports from many Aldon LM(i) panels using F21=Print. Control custom reports by controlling the list of items, the range of items printed, and the fields printed for each item. Control the list Control the list of items available for inclusion in the report by subsetting the “Work with” panel with F17=Subset and/or F22=More functions before requesting the report. Subsetting “Work with” panels is discussed in “Subsetting a “Work with” Panel” on page DO 2-15. Control the range Control the range printed from the available list by specifying the “First entry” and “Last entry” to print on the confirmation panel. Accept defaults *TOP and *BOT for “First entry to print” and “Last entry to print” to print the entire list, or restrict the range by entering all or part of an item name as a starting or ending point. For example if the report lists information about objects, enter all or part of an object name to specify a First or Last entry to print. Enter *TOPSCREEN to specify the first item visible at the top of the list when you pressed F21. Enter *BOTSCREEN to specify the last item visible when you pressed F21. Control the fields Control the fields of information printed for each item by selecting a “View” with F11 on the confirmation panel. The view selected determines which fields appear on the report. Report views are similar to but independent from views selected on “Work with” panels. View selection is not currently available for all reports. Custom Report Example This example demonstrates printing the custom report for the Work with Objects by Developer panel. Control the List The Work with Objects by Developer panel displays active objects, and may be subset by developer, environment, object, type, attribute, condition, task, release, application, and application group. In this example, the panel is subset for Developer = ACMSDEMO, Release=BASE, Application=ACMSDEMO, and Group=ALDON. DO 6-2 • Reports Aldon LM(i) Daily Operations Reference After setting the subset criteria, press F21 from the Work with Objects by Developer panel to display a Confirm Print of List panel such as the one shown in Figure 43. CFMPRTDVO Confirm Print of List Type choices, press Enter to confirm your request to print the list. Press F12=Cancel to cancel your print request. First entry to print . . . Last entry to print . . . *TOP *BOT *TOP, *TOPSCREEN, starting characters *BOT, *BOTSCREEN, *MATCH, starting characters This print view prints the following fields: object, type, attribute, release, developer, Env, Lvl, version, conditions F11=Print view 2 F12=Cancel Figure 43 - Confirm Print of List Panel Control the Range This example uses the default values *TOP and *BOT. *TOP begins the print range with the first record selected by current subsetting criteria. *BOT ends the print range with the last record selected by current subsetting criteria. *TOPSCREEN and *BOTSCREEN begin and end the print range with the records displayed at the top and bottom of the previous panel on entry into the print function. Enter a character string for First or Last entry to print to begin or end the print range with the first or last record matching the specified string. Aldon LM(i) evaluates the string entered against the primary key field used to sort records on the previous panel. In this example, object name is the primary key field. Enter *MATCH for Last entry to print to print only records matching the record specified in the First record to print field. Aldon LM(i) Daily Operations Reference Reports • DO 6-3 Control the View Three “Views” are available for printing the Work with Objects by Developer panel: View 1 2 3 4 Fields Included Object, Type, Attribute, D, Release, Developer, Env, E, Checkout requests, conditions Object, Type, Env, Version, Release, Lvl Object, Type, Env, Object library, Source; Library, File, Member Object, Type, Text Select the desired view with F11, then press Enter to produce the report. Figure 45 on page DO 6-5 shows a sample View 1 report. Figure 44 on page DO 6-4 shows a sample View 2 report. Figure 45 on page DO 6-5 shows a sample View 3 report. .. Aldon LM(i) version V084_07.5 Printer file PRT FDVPOBJ Job 066734/ALISONM/QPADEV000J Subsets in effect: Developer . . . . . . Environment . . . . . Object . . . . . . . . Object type . . . . . Object attribute . . . Has condition category Included in task . . . Release . . . . . . . Application . . . . Group . . . . . . Range in effect: First entry printed . Last entry printed . . Object ========== CLNADR CLNADR CLNADRL DEMOCBL1 DEMOCBL2 Type ======== *FILE *FILE *FILE *PGM *PGM . . . . . . . . . . : : : : : : : : : : *ALL *ACT *ALL *ALL *ALL *NA *NA BASE ACMSDEMO ALDON *TOP *BOT Developer ========== ALISONM ALISONM ALISONM ALISONM ALISONM Env === DVP QUA QUA QUA DVP Lvl ==== BASE BASE BASE BASE BASE Version ======== 00100002 00100001 00100001 00100001 00100001 -- Conditions Chkout rqs Oth Emg ========== === === Work with Objects by Developer Copyright (c) Aldon, Inc. 1989-2004 Licensed at Aldon Computer Group Inc. Page 1 11:04 AM Job JULY 6, 2007 . : . : Attribute D Release ========== ================================ PF ALDON/ACMS4.0/CMS7.31 PF ALDON/ACMS4.0/CMS7.31 LF ALDON/ACMS4.0/CMS7.31 CBL K ALDON/ACMS4.0/CMS7.31 CBL K ALDON/ACMS4.0/CMS7.31 * * * * * E N D O F L I S T I N G * * * * * Figure 44 - Work with Objects by Developer Report view 1 DO 6-4 • Reports Aldon LM(i) Daily Operations Reference .0/CMS7. . . . . Has condition category Included in task .31 CBL ALDON/ACMS4. . . . Object ========== CLNADR CLNADR CLNADRL DEMOCBL1 DEMOCBL2 Type ======== *FILE *FILE *FILE *PGM *PGM . : . . Last entry printed . .31 ALISONM * * * * * E N D O F Env === DVP QUA QUA QUA DVP Object Library ========== MARKE ACMBASQUAL ACMBASQUAL ACMBASQUAL MARKE -----------. : . .31 ALISONM CBL ALDON/ACMS4. Range in effect: First entry printed . .Main Module COBOL DEMO Program . Environment . 2007 .0/CMS7. 1989-2004 Licensed at Aldon Computer Group Inc. . Group . . . . Range in effect:First entry printed . .31 CBL K ALDON/ACMS4. .1st Subordinate Module * * * * * Work with Objects by Developer Copyright (c) Aldon.5 Printer file PRTFDVPOBJ Job 066734/ALISONM/QPADEV000J Subsets in effect: Developer .31 LF K ALDON/ACMS4. Object ========== CLNADR CLNADR CLNADRL DEMOCBL1 DEMOCBL2 Type ======= *FILE *FILE *FILE *PGM *PGM . : Attribute D Release Developer ========== ====================== ========= PF ALDON/ACMS4. . Has condition category Included in task . . . . . Object type . . : : : : : : : : : : *ALL *ACT *ALL *ALL *ALL *NA *NA BASE ACMSDEMO ALDON *TOP *BOT Developer ========== ALISONM ALISONM ALISONM ALISONM ALISONM O F Env ==== DVP QUA QUA QUA DVP Text ==================================== CLNADR Physical File for Aldon/CMS Demo CLNADR Physical File for Aldon/CMS Demo CLNADRL Logical File for Aldon/CMS Demo COBOL DEMO Program . .Work with Objects by Developer Report view 3 Aldon LM(i) Daily Operations Reference Reports • DO 6-5 . : : : : : : : : : : *ALL *ACT *ALL *ALL *ALL *NA *NA BASE ACMSDEMO ALDON *TOP *BOT Work with Objects by Developer Copyright (c) Aldon. Release . . . . . . . Object attribute . . . . . 2007 Page 1 11:04 AM Job . .0/CMS7. .Aldon LM(i) version V084_07.0/CMS7. . Last entry printed . . .31 * * * * * E N D L I S T I N G Figure 46 . . . . JULY 6.0/CMS7. . . . . . . Object attribute .31 ALISONM LF K ALDON/ACMS4.31 ALISONM PF ALDON/ACMS4.0/CMS7. .31 ALISONM CBL K ALDON/ACMS4. . . . . . .Source ----------Library File Member ========== ======== ========== MARKE QDDSSRC CLNADR ACMBASQUAL QDDSSRC CLNADR ACMBASQUAL QDDSSRC CLNADRL ACMBASQUAL QCBLSRC DEMOCBL1 MARKE QCBLSRC DEMOCBL2 * * * * * * L I S T I N G Figure 45 .31 PF ALDON/ACMS4. . Page 1 11:04 AM Job JULY 6. . . Application . 1989-2004 Licensed at Aldon Computer Group Inc. Inc. . . . . . . .Work with Objects by Developer Report view 2 Aldon LM(i) version V084_07.0/CMS7. . . Object . . . . . . Object type . . .0/CMS7. . . . Environment . . Inc. Release . . . . . . . : Attribute D Release ========== ===================== PF ALDON/ACMS4. . . . .0/CMS7. . .0/CMS7. . . Group . . . Object . Application .5 Printer file PRTFDVPOBJ Job 066734/ALISONM/QPADEV000J Subsets in effect: Developer . . If any errors occurred during the checkout operation. It also names the release for which the checkout is performed. lists all of the objects checked out. which is shown in Figure 47 on page DO 6-6. type Y (Yes). Aldon LM(i) version V084_07.Checkout Report . 1989-2007 Page 1 11:04 AM Job JULY 6. Figure 47 . ---. type and attribute. Begin to check out objects in the normal way. Correct the errors and repeat the checkout operation. 2007 Licensed at Aldon Computer Group Inc.From ----Release Object Type Attribute Release Env Developer Comment ================================ ========== ======== ========== ========== === ========== =========================== ALDON/ACMSDEMO/BASE CLNADR *FILE PF *SAME PDN ALISONM ALDON/ACMSDEMO/BASE DEMOCBL1 *PGM CBL *SAME PDN ALISONM ALDON/ACMSDEMO/BASE DEMOCBL2 *PGM CBL *SAME PDN ALISONM 3 objects were checked out. Inc. the receiving developer. the object name. 2.5 Printer file PRTFDVPOBJ Job 066734/ALISONM/QPADEV000J Checkout Copyright (c) Aldon. Aldon LM(i) can produce a report which summarizes the results of the checkout operation. they are listed on this report. This report. To print a checkout report 1. Program ACMSCHKOUT completed successfully.Checkout Report DO 6-6 • Reports Aldon LM(i) Daily Operations Reference . the release and environment containing the checkout copy. in the Print checkout report field. The highest CMSnnnn message severity received was 0. 3. and the checkout comment.PRTFCHKOUT When objects are checked out to a Developer. On the Check Out Objects panel. Complete the checkout in the normal way. attribute.5 Printer file PRTFDVPOBJ Job 066734/ALISONM/QPADEV000J Promote/Create Objects Copyright (c) Aldon. CMS2347 0Data library DS1DS1PDTA was successfully updated for file DMSLF01. 1989-2007 Licensed at Aldon Computer Group Inc.Promote Objects Report Aldon LM(i) Daily Operations Reference Reports • DO 6-7 . the promote or create comment. the name. and the “From” and “To” environments for each object. If a job combines promote and create operations. the title reads “Promote/Create Object Report.PRTFPROMOT Aldon LM(i) can create source-based objects automatically when they are promoted. 1 objects were created. Page 1 6. displays the release name. When objects are recompiled as a part of the promotion operation. Data library DS1DS1PDTA was successfully updated for file DMSPF01. the far right columns display the release and environment containing the model object the new copy is created from. allowing the user to correct the errors and repeat the promotion operation. shown in Figure 48 on page DO 6-7. The report also displays the extended attribute of any program objects listed. or you can request creation in place in a developer library or in an Aldon LM(i) controlled library. Program ACMSCREATE completed successfully. The report title changes depending on the operation(s) performed. the report displays the create command used. Inc. Aldon LM(i) produces a report for each create or promote job. P Release C Object Type ======================= = ========== ========== DOUGS/DMS01/DMS01 P MSPF01 *FILE CRTPF Non-Res Create Ext From To From Attribute Attr Environment Env Release Env Comment ========== ==== ============ === ========== === ========================= PF QUA PDN FILE(DS1DS1PDN1/DMSPF01) SRCFILE(DS1DS1PDN1/QDDSSRC) SRCMBR(DMSPF0 FILETYPE(*DATA) MBR(DMSPF01) EXPDATE(*NONE) MAXMBRS(00001) MAINT(*I D) RECOVER(*NO) FRCACCPTH(*NO) SIZE(0000010000 01000 00003) ALLOCAT NO) CONTIG(*NO) UNIT(*ANY) FRCRATIO(*NONE) WAITFILE(*IMMED) WAITRCD 060) SHARE(*NO) DLTPCT(*NONE) ALWUPD(*YES) ALWDLT(*YES) LVLCHK(*YES TEXT(' ') Object DMSPF01 type *FILE successfully scanned in environment PDN. Any errors that occurred during the promotion are listed. as when creating dependent objects during a promote job. 1 objects were promoted. Aldon LM(i) version V084_07. Figure 48 .” This report. The second column displays “P” for a promote or “C” for a create operation. An Aldon LM(i) information message appears for each object scanned for object dependency data. 2007 11:04 AM Job JULY CMS1343 CMS2347 0 0 CMS2350 0 Data library DS1DS1QDTA not updated for file DMSPF01 because the file was at the same level as in env QUA. When a non-resident object is created.Promote/Create Object Report . type. DOUGS/DMS01/DMS01 C DMSLF01 *FILE LE PDN CMS1343 0Object DMSLF01 type *FILE successfully scanned in environment PDN. The highest CMSnnnn message severity received was 0. 5 Printer file PRTFDVPOBJ Job 066734/ALISONM/QPADEV000J Object . . developer. and tasks and deployment sets the object is a member of. : COBOL DEMO Program . A table lists the version number. . . . Aldon LM(i) version V084_07. Inc. . . .PRTFPRTOBJ Select an object with option 11 on the Work with Objects by Release panel to print a complete description of the object from the Aldon LM(i) object tracking database.Object Data Report DO 6-8 • Reports Aldon LM(i) Daily Operations Reference . .Main Module Create command .Object Data Report . . location. and any conditions pending for each copy of the object. . . : Type . . . . . . . . . . . : COBOL DEMO Program . . . . . 1989-2007 JULY 6. . The report lists the Aldon LM(i) controlled libraries the object passes through during the development cycle. . . : CRTCBLPGM PGM(ACMBASINTG/DEMOCBL1) SRCFILE(ACMBASINTS/QCBLSRC) SRCMBR(DEMOCBL1) Checkout requests ================= Task ========== ACMS004669 Dply. . . : OBJECT DATA Copyright (c) Aldon. : Release . .Source ---------------Environment Release Attribute Attr Opt Version Status Library Library File Member Type ============== ========== ========== === === ======== ======== ========== ========== ========== ========== ====== PDN *SAME PF KEP 00100000 *CURRENT ACMBASPDN1 ACMBASPDN1 QCBLSRC DEMOCBL1 Normal Object library group: 1 Object Source library group: 2 Source Tasks . . . . . . . : CRTCBLPGM PGM(ACMBASPDN1/DEMOCBL1) SRCFILE(ACMBASPDN1/QCBLSRC) SRCMBR(DEMOCBL1) QUA *NOT RES *SAME ACMBASQUAL ACMBASQUAS QCBLSRC DEMOCBL1 Normal ITG *SAME CBL OPM 00100100 *CURRENT ACMBASINTG ACMBASINTS QCBLSRC DEMOCBL1 Object text . . . : ACMS004669 Object text . . 2007 Page 1 11:04 AM Job Licensed at Aldon Computer Group Inc ACMSADDREL *PGM GARYM/GARYMAPP/BASE Ext Dta Scan Object ---------------. . . . . A release abbreviation followed by *NOT RES indicates the object is not currently resident in the indicated environment.Main Module Create command . Set ========= 0000015 0000065 Text ================================================== Add development log rcds for install/back out Status ====== Deployment started New * * * * End of Listing * * * * Figure 49 . . . .Display Development Log Report view 1 Aldon LM(i) Daily Operations Reference Reports • DO 6-9 .From ---------Release Environment ========== ============== To Environment ============== PDN PDN PDN PDN PDN PDN PDN DVP MARKE DVP MARKE DVP MARKE ITG ITG ITG ITG Display Development Log Copyright (c) Aldon. . To date . . press F21 to print development log reports. and by selecting the range of records and set of fields to print on the Confirm Print of List panel. . . Activity code . . . . Customize the development log report by subsetting the Display Development Log panel with F17. For example. : . : : : : : : : : : : : *ALL *ALL *ALL *ALL *NA BASE ACMSDEMO ALDON *NONE *FIRST *LAST *TOPSCREEN *BOTSCREEN Act Date Time Cde ======= ======== === 1/16/95 18:10:40 LOD 1/16/95 18:10:50 LOD 1/16/95 18:10:58 LOD 1/16/95 18:11:06 LOD 1/16/95 18:11:18 LOD 1/16/95 18:11:28 LOD 1/16/95 18:11:51 LOD 1/17/95 9:38:15 CHK 1/17/95 9:38:22 CHK 1/17/95 9:38:24 CHK 1/17/95 10:15:26 PRM 1/17/95 10:15:53 PRM 1/17/95 10:16:02 PRM 1/17/95 11:04:10 CRT * * * * * E N D Er Cd == Version ======= 00100000 00100000 00100000 00100000 00100000 00100000 00100000 00100001 00100001 00100001 00100001 00100001 00100001 37 00100001 O F L I S --------. . simultaneous checkout of three objects produces three log entries. 2007 . . . . . . . . Aldon LM(i) version V084_07. . . . . . Application . . . User . 1989-2007 Licensed at Aldon Computer Group Inc. . Page 1 11:04 AM Job JULY 6. deletions of objects. Affects task . . Inc. Release .. . Object ======== DEMOCBL1 DEMOCBL2 DEMOCBL3 DEMORPG1 DEMORPG2 DEMORPG3 CLNADRL CLNADR DEMOCBL1 DEMOCBL2 CLNADR DEMOCBL1 DEMOCBL2 DEMOCBL2 Type ====== *PGM *PGM *PGM *PGM *PGM *PGM *FILE *FILE *PGM *PGM *FILE *PGM *PGM *PGM . . Load. . . . On the Display Development Log panel. . . : Release ==================== ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE ALDON/ACMSDEMO/BASE *SAME *SAME *SAME *SAME *SAME *SAME *SAME T I N G PDN PDN PDN DVP DVP DVP ITG * * MARKE MARKE MARKE * * * Figure 50 .PRTFDSPLOG Aldon LM(i) maintains a log of all development operations it performs. . Object type . If you request an operation that affects multiple objects. . .Development Log Report . . and creation of object in place.5 Printer file PRTFDVPOBJ Job 066734/ALISONM/QPADEV000J Subsets in effect: Object . From date . . . . . . . . add object functions. . . . . . . . . . Aldon LM(i) generates a separate log entry for each object. and Copy Release. . Group . . . cancellations of checkouts. . Range in effect: First entry printed Last entry printed . promotions. . Related releases . . additions of new objects to a release using the Map. . . . . . Development operations include checkouts. 5 Printer file PRTFDVPOBJ Job 066734/ALISONM/QPADEV000J Subsets in effect: Object . . Inc. . . . . . Object ========== DEMOCBL1 DEMOCBL2 DEMOCBL3 DEMORPG1 DEMORPG2 DEMORPG3 CLNADRL CLNADR DEMOCBL1 DEMOCBL2 CLNADR DEMOCBL1 DEMOCBL2 DEMOCBL2 Type ===== *PGM *PGM *PGM *PGM *PGM *PGM *FILE *FILE *PGM *PGM *FILE *PGM *PGM *PGM . . . Activity code . . Affects task . . . . 2007 Page 1 11:04 AM Job . : : : : : : : : : : : *ALL *ALL *ALL *ALL *NA BASE ACMSDEMO ALDON *NONE *FIRST *LAST *TOPSCREEN *BOTSCREEN Display Development Log Copyright (c) Aldon. Object type . . . . . . : . . . Range in effect: First entry printed Last entry printed . . . . . . . . User . . . . . . . : Act Release Date Time Cde User Task Comment ======= ======== ======== === ========== ========== ============================================== ACM/BAS 1/16/95 18:10:40 LOD MARKE ACM/BAS 1/16/95 18:10:50 LOD MARKE ACM/BAS 1/16/95 18:10:58 LOD MARKE ACM/BAS 1/16/95 18:11:06 LOD MARKE ACM/BAS 1/16/95 18:11:18 LOD MARKE ACM/BAS 1/16/95 18:11:28 LOD MARKE ACM/BAS 1/16/95 18:11:51 LOD MARKE ACM/BAS 1/17/95 9:38:15 CHK MARKE ACM/BAS 1/17/95 9:38:22 CHK MARKE ACM/BAS 1/17/95 9:38:24 CHK MARKE ACM/BAS 1/17/95 10:15:26 PRM MARKE ACM/BAS 1/17/95 10:15:53 PRM MARKE ACM/BAS 1/17/95 10:16:02 PRM MARKE ACM/BAS 1/17/95 11:04:10 CRT MARKE * * * * * E N D O F L I S T I N G * * * * * Figure 51 . . . . Release . To date . . . . .Aldon LM(i) version V084_07. . . . . . 1989-2007 Licensed at Aldon Computer Group Inc. Related releases . . Group . . . .Display Development Log Report view 2 DO 6-10 • Reports Aldon LM(i) Daily Operations Reference . Application . . JULY 6. . . . . . . . . . . . . . . . . From date . ” starting on page UG 5-3 • “Working with Pseudo-Source.” starting on page UG 2-16 • “Pseudo-Source Example.Aldon LM(i) Daily Operations Reference Daily Operations DO Appendix A Pseudo-Source This appendix contains the following sections: • “About Pseudo-Source” on page DO A-2 • “Technical Details” on page DO A-2 • “To determine whether an object is pseudo-source based” on page DO A-3 For additional information on setting up and using pseudo-source see: • “Types of Objects Handled” starting on page UG 1-5 in the “Aldon LM(i) User’s Guide” • “Using Pseudo-Source.” starting on page UG 5-6 • “To map pseudo-source objects in a library group” starting on page SA 16-6 in the “Aldon LM(i) Setup and Administration Reference” Aldon LM(i) Daily Operations Reference Pseudo-Source • DO A-1 .” starting on page UG 2-16 • “Source Option and Pseudo-Source. and views. This appendix provides additional information and technical details. The Aldon Lifecycle Manager for System i (Aldon LM(i)) pseudo-source facility provides a way to store.SEU panel for pseudo-source entry Technical Details When Aldon LM(i) creates an object from pseudo-source. the object is moved using CRTDUPOBJ into the designated library replacing any previously existing copy. : 1 71 Edit MARKE/QCLSRC SEU==> ____________________________________________________________ TESTDTAARA *************** Beginning of data ************************************* 0001. see “Working with Pseudo-Source” starting on page UG 5-6 in the “Aldon LM(i) User’s Guide”. Figure 52 . retrieve. .00 VALUE('ABC') TEXT('TEST PSEUDO-SOURCE') AUT(*ALL) ****************** End of data **************************************** (C) COPYRIGHT IBM CORP. The final copy is then created in the destination library. and use the information needed to create CL based objects such as data areas. DO A-2 • Pseudo-Source Aldon LM(i) Daily Operations Reference .About Pseudo-Source For basic information on creating and using pseudo-source. SQL objects are handled differently because they cannot be moved after creation. 1991. this temporary copy is deleted. it first creates the object in a temporary library. An example of pseudo-source for a data area appears below: Columns . indexes. if the create executes without errors. .00 CRTDTAARA DTAARA(&LIB/TESTDTAARA) TYPE(*CHAR) LEN(3) + 0002. JOBDs. and SQL based objects such as tables. 1981. An SQL object is first created from pseudo-source in a temporary library. then. If this create is successful. Aldon LM(i) Daily Operations Reference Pseudo-Source • DO A-3 . 3. Data sets are usually updated immediately after successful promotion of the SQL object into the associated Aldon LM(i) environment library.When populating an SQL object into a data library there is no preceding “test create..Source . in the Opt field by the ENTER object you want to investigate. 2. type 8 (Display attributes) and press to view details about the object.section under the Type column heading.. type option 2 (Work with objects by developer) and press ENTER to display the Work with Objects by Developer panel. To determine whether an object is pseudo-source based 1. At the Aldon LM(i) main menu. Then Aldon LM(i) creates the new copy into the data set library. At the Work with Objects by Developer panel. or no source) at the far right in the . pseudo-source.” Any previous copy of the SQL object in the data set is deleted. You will find the objects source type (normal. DO A-4 • Pseudo-Source Aldon LM(i) Daily Operations Reference . ” starting on page DO B-8 Developing System i Menus with Aldon LM(i) Menu Objects Outside of Aldon LM(i) Outside of Aldon LM(i). a System i menu exists as three objects based on two source members: Component display file (*DSPF) Corresponding Source Members member type MNUDDS in QDDSSRC.” starting on page DO B-1 • “Handling Menu Objects Using Non-Default Values. The following topics are included: • “Developing System i Menus with Aldon LM(i).” starting on page DO B-3 • “Handling Menu Objects Using Pseudo-Source. command list. member type MNUCMD (also in QDDSSRC with suffix QQ) Aldon LM(i) Daily Operations Reference Menus as Aldon LM(i) Objects • DO B-1 .Aldon LM(i) Daily Operations Reference Daily Operations DO Appendix B Menus as Aldon LM(i) Objects This appendix describes how to work with System i menu objects in Aldon Lifecycle Manager for System i (Aldon LM(i)). Once inside Aldon LM(i). you cannot directly determine which menus use which methods and therefore. try converting a few menus to the pseudo-source method to see if the time savings is worth the conversion effort. For information on the pseudo-source method. but requires no further special user action. which menus require the extra value entry step and which do not. For information on the non-default value method.” starting on page DO B-8. see “Handling Menu Objects Using Non-Default Values” below. menu object. display file command member.” panels. Since the method in use for a particular menu is not visible on the “Work with. When creating a new release from objects outside of Aldon LM(i). The non-default value method requires users to type two non-default SDA values each time they modify a menu in Development.” starting on page DO A-3 for help in determining the editing method currently in use for a *MENU object. See “To determine whether an object is pseudo-source based.Component menu object (*MENU) message file (*MSGF) Corresponding Source Members (no source) (no source) Menu Objects Inside of Aldon LM(i) The current version of Aldon LM(i) handles System i menu objects by separately tracking the display file. We recommend that for long term use you rely on one method or the other. You may want to try both methods. If you find you are making frequent menu modifications. and associated message file. and the extra steps required by the non-default value method starts to impact efficiency. DO B-2 • Menus as Aldon LM(i) Objects Aldon LM(i) Daily Operations Reference . see “Handling Menu Objects Using Pseudo-Source. The pseudo-source method requires creation of a special pseudo-source source member for a menu the first time a user modifies it in Aldon LM(i). you map or load each of these components without taking any special steps... there are two methods of supporting the editing and promotion of menu objects: the non-default value method and the pseudo-source method. the menu object and the message file are non-source objects inside of Aldon LM(i): Component display file (*DSPF) command list (*SRCMBR) menu object (*MENU) message file (*MSGF) Source Obtained From member type MNUDDS in QDDSSRC command list.) To add a System i menu Add a System i menu to an application in Aldon LM(i) by performing these steps: 1. type option 2 (Work with objects by developer) and press ENTER to display the Work with Objects by Developer panel.Handling Menu Objects Using Non-Default Values Under the non-default value method. At the Aldon LM(i) main menu. member type MNUCMD (also in QDDSSRC with suffix QQ) (no source) (no source) (*SRCMBR is an Aldon LM(i) defined data type containing source code that is not directly compilable into an object. the display file and command list have normal source code. Aldon LM(i) Daily Operations Reference Menus as Aldon LM(i) Objects • DO B-3 . . . . 2=Promote data. . . . . DO B-4 • Menus as Aldon LM(i) Objects Aldon LM(i) Daily Operations Reference . . . . . the member is contained in the file QDDSSRC. OPM (*PGM) SQL (*FILE) * 1=Keep destination data. . . 9=None QDDSSRC Name *SYSOBJNAM Name. . complete values as shown above to add the display file with its existing display file source member (MNUDDS). . Source option . press Enter. .2. . Command ===> __________________________________________________________________ _______________________________________________________________________________ F3=Exit F4=Prompt F7=Add task F12=Cancel F24=More keys Add the Display File 3. Note When you press ENTER. press F6 (Add object) to display the Add Release Object panel: CADDOBJ Type choices. . Source file . . . . . At the Work with Objects by Developer panel. . 2=Pseudo source. . Object attribute . You can perform these object additions in any order. . . BASE + Name ACMSDEMO + Name ALDON + Name MENU400 Name Type + Attribute ILE. . . . . . . BND. Application Group . . . Release . . . . . . . . Fill in the correct file name for your file. . . Source member Task . . . . . . Developer . . Extended attribute Data option . . . In this example. . The instructions below assume you are adding all component objects at the same time before returning to the Work with Objects by Developer panel. . the Add Release Objects panel redisplays. *SYSOBJNAM + Name Add display file for sample System i menu MENU400 *FILE DSPF + Add Release Object Object type . . . Object name. *=Default LINDAC + Name 1 1=Source. all at one time or at different times. . . . . . . Comment for log . . . . . panels for selecting the object and source library groups display. . See “Adding an Object” starting on page UG 5-2 in the “Aldon LM(i) User’s Guide” for more detailed instructions on adding objects. . At the Add Release Objects panel. . After you complete these panels. . . . . . . . . . BND. . . . . . At the Add Release Objects panel. . . . . The source file is usually the same as that containing the display file added in the figure above. . . BND. Extended attribute Data option . . . Application Group . *=Default LINDAC + Name 9 1=Source. . Release . . . . . Developer . . . . . . Source option . . . . . . Source member Task . . Comment for log . . . . . . . . . 2=Pseudo source. . . . . . Application Group . . Comment for log . . . . Source member Task . . . . . . . . . . . . . . . . Source file . *SYSOBJNAM + Name Add display file for sample System i menu MENU400 *MENU DSPF + Object type . OPM (*PGM) SQL (*FILE) * 1=Keep destination data. . press Enter. . add the *MENU menu object as a non-source object as shown below: Add Release Object Type choices. . .Add the Command List for the Display File 4. 2=Promote data. . . . . . At the Add Release Objects panel. . *SYSOBJNAM + Name Add display file for sample System i menu MENU400 *SRCMBR MNUCMD + Object type . . BASE + Name ACMSDEMO + Name ALDON + Name MENU400 Name Type + Attribute ILE. . . . . . 9=None QDDSSRC Name *SYSOBJNAM Name. . . Add Release Object CADDOBJ Type choices. . . 9=None Name *SYSOBJNAM Name. . . . . . . . . . Source option . . BASE + Name ACMSDEMO + Name ALDON + Name MENU400QQ Name Type + Attribute ILE. Object attribute . . Object . Extended attribute Data option . . . *=Default LINDAC + Name 1 1=Source. Source file . . . Command ===> __________________________________________________________________ _______________________________________________________________________________ F3=Exit F4=Prompt F7=Add task F12=Cancel F24=More keys Add the *MENU Object without Source CADDOBJ 5. 2=Pseudo source. . . . . . . . . . Object . . Command ===> __________________________________________________________________ _______________________________________________________________________________ F3=Exit F4=Prompt F7=Add task F12=Cancel F24=More keys Aldon LM(i) Daily Operations Reference Menus as Aldon LM(i) Objects • DO B-5 . . . . . . Object attribute . Release . Developer . . . . . . . . . . 2=Promote data. . . . . . OPM (*PGM) SQL (*FILE) * 1=Keep destination data. . press Enter. add the command list for the display file using Aldon LM(i) data type *SRCMBR as shown below. . . . . . . . . . . . Add the Menu Message File 6. At the Add Release Objects panel, add the menu message file as a non-source object as shown below: CADDOBJ Type choices, press Enter. Release . . . Application Group . . Object . . . . . . . . . . . . . . . . . . . . . . . . BASE + Name ACMSDEMO + Name ALDON + Name MENU400 Name Type + Attribute ILE, BND, OPM (*PGM) SQL (*FILE) * 1=Keep destination data, 2=Promote data, *=Default LINDAC + Name 9 1=Source, 2=Pseudo source, 9=None Name *SYSOBJNAM Name, *SYSOBJNAM + Name Add display file for sample System i menu MENU400 *MSGF + Add Release Object Object type . . . Object attribute . Extended attribute Data option . . . Developer . . . Source option . Source file . Source member Task . . . . . . Comment for log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command ===> __________________________________________________________________ _______________________________________________________________________________ F3=Exit F4=Prompt F7=Add task F12=Cancel F24=More keys To edit a menu To work with a System i menu, check out and promote the display file, command list, menu, and menu message file together at the same time. You must use this procedure each time you modify a *MENU object created without pseudo-source. If you do not use this procedure, the menu will fail to work when promoted out of Development. 1. At the Aldon LM(i) main menu, type option 1 and press ENTER to display the Work with Objects by Release panel. 2. At the Work with Objects by Release panel, in the Opt fields by the display file, command list, menu, and message file, type option 3 (Check out) and press ENTER to check the menu component objects out to development. 3. Complete the checkout in the standard manner. See the “Checking Out Objects,” starting on page UG 2-10 for assistance if necessary. 4. At the Work with Objects by Release panel or Work with Objects by Developer panel, in the Opt field by the *FILE object, type option 19 (AltEdit) and press ENTER to edit the menu with SDA. 5. Edit the menu in SDA in the usual manner. DO B-6 • Menus as Aldon LM(i) Objects Aldon LM(i) Daily Operations Reference 6. In SDA, after you are finished editing the menu, exit to display the Exit SDA Menus panel: Exit SDA Menus File . . . . . . : Library . . . . : QDDSSRC DEBM DDS member . . . . . : Commands member . . . : TESTLIBL TESTLIBLQQ Type choices, press Enter. Save new or updated menu source . . . . For choice Y=Yes: Source file . . . . . . . . . . . . Library . . . . . . . . . . . . . Text . . . . . . . . . . . . . . . . Replace menu members . . . . . . . . Create menu objects . . . For choice Y=Yes: Prompt for parameters Object library . . . . Replace menu objects . F3=Exit F4=Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . Y QDDSSRC DEBM Y Y Y DEBM Y Y=Yes, N=No Name, F4 for list Name, *LIBL, *CURLIB Y=Yes, N=No Y=Yes, N=No Y=Yes, N=No Name, *CURLIB Y=Yes, N=No F12=Cancel 7. In the Prompt for parameters field, type Y (Yes) and press ENTER to display the Create Menu panel: Create Menu (CRTMNU) Type choices, press Enter. Menu . . . . . . . . . Library . . . . . . Menu type . . . . . . Display file . . . . . Library . . . . . . Message file . . . . . Library . . . . . . Command line . . . . . Display function keys Current library . . . Product library . . . Replace menu . . . . . Text ‘description’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MENU400 DEBM *DSPF MENU400 *LIBL MENU400 *LIBL *LONG *YES *NOCHG *NOCHG *YES *BLANK Name Name, *CURLIB *DSPF, *PGM, *UIM Name,*MENU Name, *LIBL, *CURLIB Name, *MENU Name, *LIBL, *CURLIB *LONG, *SHORT, *NONE *YES, *NO Name, *NOCHG, *MNULIB... Name, *NOCHG, *NONE *YES, *NO F3=Exit F4=Prompt F5=Refresh F13=How to use this display F10=Additional parameters F24=More keys Bottom F12=Cancel 8. At the Create Menu panel, in the Display file and Message file Library fields, type *LIBL and press ENTER. Note This procedure creates the *MENU object with the library value *LIBL coded in the object description for the location of the display file and message file. When you promote the menu components to a new environment, Aldon LM(i) uses the CRTDUPOBJ command to accomplish the promotion. Because the *MENU object description that is moved specifies *LIBL, the components in the new Aldon LM(i) Daily Operations Reference Menus as Aldon LM(i) Objects • DO B-7 environment library will be referenced by the *MENU object rather than those in the developer library where the *MENU object was created. 9. At the Work with Objects by Release panel or Work with Objects by Developer panel, in the Opt field by each of the four menu object components, type 7 (Promote) and press ENTER to promote the objects from Development to the next environment. 10. Repeat Step 9 as necessary until the components reach Production. Handling Menu Objects Using Pseudo-Source When handling menu objects using pseudo-source, the display file and command list have normal source code, the menu object is based on pseudo-source, and the message file is a non-source object: Component display file (*DSPF) command list (*SRCMBR) menu object (*MENU) message file (*MSGF) Source Obtained From member type MNUDDS in QDDSSRC command list, member type MNUCMD (also in QDDSSRC with suffix QQ) pseudo-source created by user (no source) (*SRCMBR is an Aldon LM(i) defined data type containing source code that is not directly compilable into an object.) To add a System i menu using pseudo-source 1. At the Aldon LM(i) main menu, type option 2 and press ENTER to display the Work with Objects by Developer panel. DO B-8 • Menus as Aldon LM(i) Objects Aldon LM(i) Daily Operations Reference 2. At the Work with Objects by Developer panel, press F6 (Add object) to display the Add Release Object panel: CADDOBJ Type choices, press Enter. Release . . . Application Group . . Object name. . . . . . . . . . . . . . . . . . . . . . BASE + Name ACMSDEMO + Name ALDON + Name MENU400 Name Type + Attribute ILE, BND, OPM (type *PGM only) * 1=Keep destination data, 2=Promote data, *=Default LINDAC + Name 1 1=Source, 2=Pseudo source, 9=None QDDSSRC Name *SYSOBJNAM Name, *SYSOBJNAM + Name Add display file for sample System i menu MENU400 *FILE DSPF + Add Release Object Object type . . . Object attribute . Extended attribute Data option . . . . . . . . . . . . . . . Developer . . . . . . . Source option . . . . . Source file . . . . Source member . . . Task . . . . . . . . . . Comment for log . . . . Command ===> __________________________________________________________________ _______________________________________________________________________________ F3=Exit F4=Prompt F7=Add task F12=Cancel F24=More keys Figure 53 - Add Menu Display File Using Add Release Objects Panel Add the Display File 3. At the Add Release Objects panel, complete values as shown in Figure 53 to add the display file with its existing display file source member (MNUDDS). In this example, the member is contained in the file QDDSSRC. Fill in the correct file name for your file. Note When you press ENTER, panels for selecting the object and source library groups display. After you complete these panels, the Add Release Objects panel redisplays. The instructions below assume you are adding all component objects at the same time before returning to the Work with Objects by Developer panel. You can perform these object additions in any order, all at one time, or at different times. See “Adding an Object” starting on page UG 5-2 in the “Aldon LM(i) User’s Guide” for more detailed instructions on adding objects. Aldon LM(i) Daily Operations Reference Menus as Aldon LM(i) Objects • DO B-9 Add the Command List for the Display File CADDOBJ Type choices, press Enter. Release . . . . . Application . . Group . . . . Object name . . . . Object type . . . Object attribute . Extended attribute Data option . . . . . . . . . . . . . . . . . . . . . . . . . . . BASE + Name ACMSDEMO + Name ALDON + Name MENU400QQ Name Type + Attribute ILE, BND, OPM (type *PGM only) * 1=Keep destination data, 2=Promote data, *=Default LINDAC + Name 1 1=Source, 2=Pseudo source, 9=None QDDSSRC Name *SYSOBJNAM Name, *SYSOBJNAM + Name Add display file for sample System i menu MENU400 *SRCMBR MNUCMD + Add Release Object Developer . . . . . . . Source option . . . . . Source file . . . . Source member . . . Task . . . . . . . . . . Comment for log . . . . Command ===> __________________________________________________________________ _______________________________________________________________________________ F3=Exit F4=Prompt F7=Add task F12=Cancel F24=More keys Figure 54 - Add Menu Commands List Using Add Release Object Panel 4. At the Add Release Objects panel, add the command list for the display file using Aldon LM(i) data type *SRCMBR as shown in Figure 54. The source file is usually the same as that containing the display file added in Figure 53. Add the *MENU Menu Object. CADDOBJ Type choices, press Enter. Release . . . Application Group . . Object name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BASE + Name ACMSDEMO + Name ALDON + Name MENU400 Name Type + Attribute ILE, BND, OPM (type *PGM only) * 1=Keep destination data, 2=Promote data, *=Default LINDAC + Name 2 1=Source, 2=Pseudo source, 9=None PSEUDOSRC Name *SYSOBJNAM Name, *SYSOBJNAM + Name Add display file for sample System i menu MENU400 *MENU DSPF + Add Release Object Object type . . . Object attribute . Extended attribute Data option . . . Developer . . . . . . . Source option . . . . . Source file . . . . Source member . . . Task . . . . . . . . . . Comment for log . . . . Command ===> __________________________________________________________________ _______________________________________________________________________________ F3=Exit F4=Prompt F7=Add task F12=Cancel F24=More keys Figure 55 - Add *MENU Object Using Add Release Object Panel DO B-10 • Menus as Aldon LM(i) Objects Aldon LM(i) Daily Operations Reference 5. At the Add Release Objects panel, add the *MENU menu object with its pseudo source as shown in Figure 55. For the source file, enter the file to contain the pseudo source member which you will create in Step 6 below. The source file and member need not exist when you add the *MENU menu object. Note We recommend using a source file other than QDDSSRC to contain the pseudo-source. You might want to use the name PSEUDOSRC 6. Using SEU or another source editor, create pseudo-source for the Create Pseudo-Source for the *MENU Object *MENU menu object as shown in Figure 56. Save the member in a file with a name such as PSEUDOSRC. Aldon LM(i) uses the &LIB pseudo-source parameter to specify the correct library to contain the menu based on the environment the object is created in instead of basing creation on the System i description of the object which lists the library the object was last created in. See “Working with Pseudo-Source” starting on page UG 5-6 in the “Aldon LM(i) User’s Guide” and “Pseudo-Source,” starting on page DO A-1 for more information on using pseudo-source. Note Columns . . . : 1 71 Edit LINDAC/PSEUDOSRC SEU==> ____________________________________________________________ MENU400 *************** Beginning of data ************************************* 0001.00 CRTMNU MENU(&LIB/MENU400) TYPE(*DSPF) ****************** End of data **************************************** (C) COPYRIGHT IBM CORP. 1981, 1991 Figure 56 - Create Pseudo-Source Member for *MENU Object Using SEU Aldon LM(i) Daily Operations Reference Menus as Aldon LM(i) Objects • DO B-11 Add the Menu Message File 7. At the Add Release Object panel, add the menu message file as a non-source object as shown in Figure 57. CADDOBJ Type choices, press Enter. Release . . . Application Group . . Object name. . . . . . . . . . . . . . . . . . . . . . BASE + Name ACMSDEMO + Name ALDON + Name MENU400 Name Type + Attribute ILE, BND, OPM (type *PGM only) * 1=Keep destination data, 2=Promote data, *=Default LINDAC + Name 9 1=Source, 2=Pseudo source, 9=None Name *SYSOBJNAM Name, *SYSOBJNAM + Name Add display file for sample System i menu MENU400 *MSGF + Add Release Object Object type . . . Object attribute . Extended attribute Data option . . . . . . . . . . . . . . . Developer . . . . . . . Source option . . . . . Source file . . . . Source member . . . Task . . . . . . . . . . Comment for log . . . . Command ===> __________________________________________________________________ _______________________________________________________________________________ F3=Exit F4=Prompt F7=Add task F12=Cancel F24=More keys Figure 57 - Add Menu Message File Using Add Release Object Panel 8. At the Work with Objects by Release panel or Work with Objects by Developer panel, in the Opt field by the *FILE object, type option 19 (AltEdit) and press ENTER to edit the menu with SDA. 9. Edit the menu in SDA in the usual manner. Working With Pseudo-Source Based System i Menus To work with a pseudo-source based System i menu, check out and promote the display file, command list, menu, and menu message file together at the same time. When you want to modify a menu object for the first time, you create pseudo-source for the *MENU object component and use the Change Object Description panel to associate this pseudo-source with the object in the Aldon LM(i) database. To modify a pseudo-source based System i menu object for the first time With the pseudo-source method, the first time you modify a System i menu object after mapping or loading it you must create the pseudo-source. After that you just need to check out and promote the four components together. DO B-12 • Menus as Aldon LM(i) Objects Aldon LM(i) Daily Operations Reference See the “Checking Out Objects. 2. 1991 Figure 58 . in the Opt column. Create Pseudo-Source for the *MENU Object 4. command list.” starting on page UG 2-10 for assistance if necessary. 1981. menu. select the display file. At the Work with Objects by Release panel. At the Aldon LM(i) main menu. Using SEU or another source editor. create pseudo source for the *MENU menu object as shown in Figure 58.Create Pseudo-Source Member for *MENU Object Using SEU Aldon LM(i) Daily Operations Reference Menus as Aldon LM(i) Objects • DO B-13 .1. Complete the checkout in the standard manner.00 CRTMNU MENU(&LIB/MENU400) TYPE(*DSPF) ****************** End of data **************************************** (C) COPYRIGHT IBM CORP. 3. Columns . : 1 71 Edit LINDAC/PSEUDOSRC SEU==> ____________________________________________________________ MENU400 *************** Beginning of data ************************************* 0001. See “Working with Pseudo-Source” starting on page UG 5-6 in the “Aldon LM(i) User’s Guide” and “Pseudo-Source. . and menu message file with option 3 (Check out) and press ENTER to check the menu component objects out to development.” starting on page DO A-1 for more information on using pseudo-source. type option 1 (Work with objects by release) and press ENTER to display the Work with Objects by Release panel. . Aldon LM(i) uses the &LIB pseudo-source parameter to specify the correct library to contain the menu based on the environment the object is created in instead of basing creation on the System i description of the object which lists the library the object was last created in. . . . 9. Extended attribute Data option . In the Source file. and Source member fields. . in the Opt field by the *MENU object. . . *=Default 1=Source. 10. : Type choices. : Release . . .5. at the Work with Objects by Developer panel. . and menu message file objects. . 9=None Name Name Library group number Change Checked Out Object MENU400 ALDON/ACMSDEMO/BASE LINDAC . . . . . At the Change Checked Object panel. Source file . type the number of the library group to hold source for the object and press ENTER. . Object type . . . . . Object attribute . In Aldon LM(i). . : : : . . . . . type option 2 (Pseudo-source) 7. Command ===> F3=Exit F4=Prompt F9=Retrieve F12=Cancel F22=More functions 6. . . DO B-14 • Menus as Aldon LM(i) Objects Aldon LM(i) Daily Operations Reference . . At the Work with Objects by Developer panel. type 16 (Change object) and press ENTER to display the Change Checked Out Object panel: CCHGOBJ Object . command list. 2=Pseudo source. . . . press Enter. in the Source option field. . group Comment for log . : Developer . . . . 8. . select the *MENU object with option 19 (AltEdit) to modify the menu using SDA. type the name of the file and member containing the pseudo-source created in Step 4. . menu. . . Tip You can press F4 to select the library group from a list. 2=Promote data. . Source option . . . . Source member Source library . Promote the display file. *MENU DSPF * 2 PSEUDOSRC MENU400 2 + 1=Keep destination data. . . . . In the Source library group field. . ” starting on page DO -12 Aldon LM(i) Daily Operations Reference Record Objects • DO C-1 .Aldon LM(i) Daily Operations Reference Daily Operations DO Appendix C Record Objects *RCDS objects are introduced in the section titled “*RCDS Objects” starting on page UG 5-2 in the “Aldon LM(i) User’s Guide”.” starting on page DO -9 • “Working with *RCDS Objects.” starting on page DO -3 • “Defining Record Objects.” starting on page DO -2 • “*RCDS Object Limitations and Requirements. This chapter includes the following topics: • “Overview.” starting on page DO -13 • “*RCDS Objects in Multiple-Release Applications.” starting on page DO -11 • “Working with Underlying Files.” starting on page DO -5 • “Controlling *CONTAIN File Creation Options.” starting on page DO -13 • “How Aldon LM(i) Manages the Physical and Logical Files. This protects any records which may have been created or modified by the developer. Promote the *RCDS object using standard Aldon LM(i) promote options. In the developer library. For subsequent modifications. Aldon LM(i) creates the file in the developer library if necessary and copies records from the appropriate Aldon LM(i) controlled environment for modification. You define a new *RCDS object over base files defined to the release and present only in Production. For each *RCDS object. You use the Aldon LM(i) Add Object function to add the *RCDS object and specify a developer in the process. you check the *RCDS object out using standard Aldon LM(i) checkout options. may be checked out. identify the range of records in each base file which together comprise the object. If Aldon LM(i) creates new files it also copies the specified range of records to the files from the Production files on which the *RCDS object is based. Aldon LM(i) ignores changes to records outside the ranges specified for the checked out *RCDS object at promote time. The *RCDS object definition in the Aldon LM(i) object database identifies the range or ranges of records that constitute the object. Aldon LM(i) does not copy records. You can copy records to the developer library files from Production using your standard file handling tools and techniques outside of Aldon LM(i) if necessary. Once defined. or delete records within the identified ranges as necessary. When you define a new *RCDS object. DO C-2 • Record Objects Aldon LM(i) Daily Operations Reference . If the required files are already present in the developer object library. you modify. Aldon LM(i) creates any required logical or physical files in the developer object library if they are not already present. How Record Objects Work Define a *RCDS object over one or more keyed files which serve as “base” files. indicated by the Aldon defined type *RCDS. a records object. modified. and promoted like any other object in Aldon LM(i).Overview The Purpose of Record Objects Aldon Lifecycle Manager for System i (Aldon LM(i)) provides a facility for defining a range of records as an object. add. (If you define a *RCDS object using the ACMSADDOBJ command.What Aldon LM(i) Does When You Define a *RCDS Object If you define a *RCDS object using the Aldon LM(i) panel interface. This protects changes or additions made by the developer. Aldon LM(i) converts both the logical and the physical file it is over to type *CONTAIN • When you define the first *RCDS object over a file. Because of limitations in how the CPYF command handles record sorting. Aldon LM(i) supports definition of *RCDS objects in either the Development environment or the Production environment. Aldon LM(i) uses the CPYF command to manipulate *RCDS objects. no source library group is defined. If files are already present records are not copied. • Numeric keys used in files on which *RCDS objects are based must be defined as UNSIGNED. *RCDS Object Limitations and Requirements Requirements and Limitations for the Underlying Files • The file directly referenced in the *RCDS object definition must be keyed.) • If you define a new *RCDS object in the Development environment – – Aldon LM(i) creates a database entry for the *RCDS object placing the object in the Development environment Aldon LM(i) creates any required files not already present in Development and copies the defined range of records to those files. any numeric key fields in physical or logical files used to define *RCDS objects must be defined as Aldon LM(i) Daily Operations Reference Record Objects • DO C-3 . Because *RCDS objects are not source based. Aldon LM(i) always defines the new *RCDS object as present in the Development environment. Changes the Aldon LM(i) object type of the base file or files from *FILE to the special Aldon LM(i) object type *CONTAIN throughout the application If a base file is a logical file. The library group is used to select the *RCDS for deployment and to determine where *CONTAIN files are placed in deployment targets and in the production environment. Aldon LM(i) – – Library Groups and *RCDS Objects When you define a *RCDS object you assign it to an object library group. Other sequencing keywords should not be used. The logical file must not be over any other physical files. – – – The logical file must be the only logical over the physical file. DO C-4 • Record Objects Aldon LM(i) Daily Operations Reference . or *FILE objects eligible for conversion to type *CONTAIN as defined above in “Requirements and Limitations for the Underlying Files” • Ranges of records specified for *RCDS objects cannot overlap • In the current release of Aldon LM(i). • If a keyed logical file is used to accesses a physical file. and The physical file must not have already been converted to type *CONTAIN (already in use by a *RCDS object) • The *FILE or files used as the base for a *RCDS object must be defined to Aldon LM(i) • The *FILE must be in an activated release • All copies of the *FILE object in the application must be in the Production environment (the *FILE object cannot have any “active” copies (copies in Development. This overrides the default field type of SIGNED which causes sorting problems when moving records between files. in any release of the application) • The *FILE object also cannot be included in any non-finished deployment sets Requirements and Limitations for *RCDS Objects • Files over which *RCDS objects are defined must be type *CONTAIN.UNSIGNED in the file description DDS. Integration or Quality Assurance). all records for a record object in a given file must be contained in a single key range • A given physical file may be used as the basis for *RCDS objects directly or through at most one logical file • A logical file used as a base for *RCDS objects may be over no more then one physical file • *RCDS objects cannot be built over physical files that have Data Option set to option 2 (Promote data). Physical files must have Data Option set to option 1 (Keep destination data). Physical files must have Data Option set to option 1 (Keep destination data). For additional information on mapping and loading files at release definition see “Population Functions Overview” starting on page SA 15-1 in the “Aldon LM(i) Setup and Administration Reference”. At the Work with Objects by Release panel. 1. At the Aldon LM(i) main menu. New files added to a release using the add object function can also be used as the basis for *RCDS objects. Aldon LM(i) Daily Operations Reference Record Objects • DO C-5 . Note *RCDS objects cannot be built over physical files that have Data Option set to option 2 (Promote data).Defining Record Objects To define files to Aldon LM(i) for use by *RCDS objects Map or Load files on which *RCDS objects will be based as you would any other object when populating a new release. type 1 to display the Work with Objects by Release panel. 2. press F6 (Add object) to display the Add Release Object panel. For additional information on adding new files to a release see “Adding an Object” starting on page UG 5-2 in the “Aldon LM(i) User’s Guide” To define a *RCDS object Prerequisite The release must be activated. *RCDS + + * MARKE 9 *SYSOBJNAM + + Name Type Attribute ILE. . . . . . . . . *RCDS objects must be no source. Release . . . . d. . . . . Object name . b. At the Add Release Object panel a. . . type 9 (None). type a name for the *RCDS object In the Object type field. Object attribute . . In the Object name field. . . . type the name of the developer definition for the developer who will first work with the object.Note *RCDS objects may also be defined using F6 from the Work with Objects by Developer panel or the ACMSADDOBJ command discussed in “Command Interface. . 2=Pseudo source. . press Enter. Source file . . . . . DO C-6 • Record Objects Aldon LM(i) Daily Operations Reference . . . . Source member Task . e. *SYSOBJNAM Name Command ===> __________________________________________________________________ F3=Exit F4=Prompt F7=Add task F12=Cancel F24=More keys Figure 59 . . . . . .Add Release Object Panel (for *RCDS object) 3. type *RCDS In the Developer field. . . . . Source option . . *=Default Name 1=Source. . 2=Promote data. . . . OPM (type *PGM only) 1=Keep destination data. . . . Extended attribute Data option . . In the Source option field. Work with the Task and Comment for log fields as desired. . . . . . 9=None Name Name. . . Comment for log . . . BASE MARK1 MARKE TESTOBJ + + Name Name + Name Object type . . . Application Group . . . . . Developer . c.” Add Release Object CADDOBJ Type choices.” starting on page CG 7-1. . . BND. . . type the name of the file member. In the File name field. In the Number of key fields field. . . Under Copy from record key. . . In the Member name field.Define *RCDS Object Panel 5. b. More: File name . In the Key value field. . type the character string specifying the actual key values for the first record of the range. . . Note CCSID (coded character set identifier) conversions are not performed on character fields when a single string is specified. Specify the key string in quotation marks if it contains blanks. 1 00002 Number Character value Command ===> __________________________________________________________________ _______________________________________________________________________________ F3=Exit F4=Prompt F9=Retrieve F12=Cancel F22=More functions Figure 60 . KEYEDPF *FIRST 1 00001 Name Name. lower-case letters. Member name . specify the number of key fields to use in selecting the starting record. Enter 1 to use only the first key of the file. b. . Hexidecimal key values You can specify the key value in hexadecimal format if you desire. Specifying key values in hexadecimal is useful for ensuring selection of all records in a file (x'00' thru x'FF'). . . Press ENTER to check the values entered. *FIRST Number + Define *RCDS Object Character value Copy to record key: Number of key fields . . At the Define *RCDS Object panel. . .4. . . . If all values are correct. Key value . . Aldon LM(i) Daily Operations Reference Record Objects • DO C-7 . type descriptive text for the *RCDS object as desired. . or special characters. or if the key contains packed decimal or binary numeric fields or is a variable-length character field. press Enter. . . . . type the name of the keyed physical or logical file. the Define *RCDS Object panel displays: CADDOBJRCD Type choices. . 6. in the Object text field. . Enter 2 to use the first and second key fields etc. Identify the location of the first desired record range by doing the following: a. Copy from record key: Number of key fields Key value . Object text . . 7. . . identify the first record of the record range by doing the following: a. . . . . Define a keyed logical file over the unkeyed physical file.” starting on page DO C-9. 10. Note Later. 2. 12. 1. type 1 (Select). Edit the record range of the *RCDS object in Development as desired. Aldon LM(i) copies the specified record range to Development. The Select Library Group for Object panel displays. Press ENTER to add the *RCDS object. Aldon LM(i) changes the type of the production files to *CONTAIN and sets the default values to control file replication. If you wish to include record ranges from additional files. Aldon LM(i) does not copy the record range from Production. 9. Under Copy to record key: identify the last record of the record range in the same fashion as for the from record described above in Step 7. If the files are not present. Press ENTER. Note The object library group for a *RCDS object is used for the purpose of selecting the object for update into a data set or for determining eligibility for deployment. 14. Specify each additional range using Step 6 through Step 8 above. in the Opt field by the desired library group. DO C-8 • Record Objects Aldon LM(i) Daily Operations Reference . If the files are present. For information on controlling file replication see “Controlling *CONTAIN File Creation Options. If the files were already present in Development. Define the *RCDS object over the keyed logical file. At the Select Library Group for Object panel.8. when you check out an existing *RCDS object for further modification. Aldon LM(i) creates the required files and copies the designated records to the files from the Production copies of the files. press PAGE DOWN (ROLL UP) to display additional fields for identifying files. To define a *RCDS object over an unkeyed physical file Use the following procedure to include records from an unkeyed physical file in a *RCDS object. Aldon LM(i) checks to see if the required file or files are present in the object library of the identified developer. the object data library also determines the installation location of the *CONTAIN file or files for the deployed record range. members and key ranges. 13. 11. outside of Aldon LM(i) copy the necessary record range to the file or files in the developer library for the developer specified in Step 3c above. If deployed. If the file is not in Development. Select N to delete the *CONTAIN file from a controlled active environment as soon as the last *RCDS object over the base file leaves that environment. These values control the extent and persistence of the base files in controlled active environments (Development. Promote the changed *RCDS object to the test environment with full replication selected if this is the case. Select N to include all records in the *CONTAIN file in each environment into which you promote the *RCDS objects. Select Y to leave the *CONTAIN file behind in controlled active environments when the last *RCDS object over it leaves the environment. Discussion Testing may require the presence of a complete copy of the file on which a *RCDS object is based in the test environment. The values you select in one release need not match for copies of the same *CONTAIN file in different releases of an application. With this setting. and Quality Assurance).Controlling *CONTAIN File Creation Options Aldon LM(i) provides two parameters to control the replication and persistence of a *CONTAIN file upon which *RCDS objects are based: • Populate only requested records • Keep container file in all environments You can set these parameters individually for each *CONTAIN file in a release. Populate only requested records This setting controls whether Aldon LM(i) copies all or just a portion of the base file when placing the base file in controlled active environments to support promotion of *RCDS objects defined over it. Keep container file in all environments This setting tells Aldon LM(i) when to delete copies of the *CONTAIN file from controlled active environments. Select Y to move only the range of records specified in *RCDS objects selected for promote. Aldon LM(i) leaves the *CONTAIN file in controlled active environments as long as a *RCDS object is defined over the base file in any release of the application. Integration. an empty copy of the *CONTAIN is created and the range of records defined by the *RCDS object is copied to Development. A full copy of the contain file is created in Development. Aldon LM(i) Daily Operations Reference Record Objects • DO C-9 . If testing requires a complete copy of the base file. DO C-10 • Record Objects Aldon LM(i) Daily Operations Reference . . type Y To populate the complete file. . Object type . Keep container file in all environments . . 2. type 15 by the physical file *CONTAIN object you want to work with to display the Change *CONTAIN Creation Options panel. in the Populate only requested records field. type Y To delete the container file when the last *RCDS object over it leaves the environment. . . . Change *CONTAIN Creation Options : : : : ALDON/ACMSDEMO/BASE CLNADRL Environment . . type 1 to display the Work with Objects by Release panel. Object attribute . Command ===> F3=Exit F4=Prompt F9=Retrieve F12=Cancel Figure 61 . . do the following: – – To populate only requested records. At the Work with Objects by Release panel. . . . . type N If the *RCDS object is defined over more than one physical file. CCHGCRTCON Release . . : LF Y N Y=Yes. . . At the Change *CONTAIN Creation Options panel. Object name . To control *CONTAIN file replication and persistence 1. : *CONTAIN Object library . . you may wish to avoid time consuming file copying by leaving the file in the various environments even when it is not required by the presence of *RCDS objects. . . and the file is quite large.Change *CONTAIN Create Options Panel 3. type N 4. . . In the Keep container file in all environments field. . do the following: – – Note To leave a copy of the container file behind after the last *RCDS object over it leaves the environment. . . N=No Y=Yes. . . N=No PDN ACMBASPDN1 Populate only requested records . you can change the creation options independently for each *CONTAIN object corresponding to a physical file. . At the Aldon LM(i) main menu. . If the files are already present. can be deployed using a given deployment profile. Aldon LM(i) copies the complete *CONTAIN file to Development. Perform all subsequent promotions of the *RCDS object in the same fashion as objects of other types. and commands as standard objects. • For *RCDS objects. archiving. You must delete the object and add a new one. If they are not already present in the Development environment. • Checkout. Aldon LM(i) uses the object library group only to decide whether or not the *RCDS object is eligible for update into a deployment target.Working with *RCDS Objects Work with *RCDS objects using the same options. • First time promotion of a newly defined *RCDS object requires the presence of the underlying file or files in your developer object library. • Aldon LM(i) treats *RCDS objects as program objects as opposed to data file objects. You can map the library group containing a *RCDS object to a data set library. Aldon LM(i) updates the new *RCDS object (its specified range of records) in the data set. you must manually (outside of Aldon LM(i)) copy the defined record range from Production if necessary. When you deploy a *RCDS object. you define an object library group but no source library group. Since it is not a data object. emergency checkout. You will not be able to promote the *RCDS object until these files and the defined record range are in place. functions. The underlying files may be in any library defined to Aldon LM(i) for the Production environment. inclusion in tasks. Aldon LM(i) Daily Operations Reference Record Objects • DO C-11 . • The ACMSCHKFRN command does not handle *RCDS objects. object version numbering. and object deployment all apply to *RCDS objects in the same fashion as objects of other types. When you check out a *RCDS object. Aldon LM(i) does not preserve the data in any replaced copy in the data set library. Aldon LM(i) places these files in your developer library automatically and copies the defined record range into them from Production when you define the *RCDS object. • *CONTAIN objects cannot be checked out with any function or command. • The range of records defined in *RCDS objects cannot be changed. This is true regardless what options you choose to control *CONTAIN file replication. and what library to install it in for a given deployment target. the library group of the *RCDS object determines the target library to receive the underlying file or files. type 1 to display the Work with Objects by Release panel. the types of the files on which they are based change from *CONTAIN to *FILE. When the last *RCDS object definition is deleted. At the Work with Objects by Release panel do one of the following: – – To display the record range. To view or print a *RCDS record range description 1. type option 4 (Delete) Press ENTER. Note When Aldon LM(i) creates *CONTAIN files in a descendent release to support a *RCDS object checked out to that release from an ancestor release it carries forward any *CONTAIN file creation options which may have been set for the parent release copies of these files. Records within the *RCDS objects are not affected by deletion of the *RCDS object definition. do the following: 1.Warning Modification of files on which *RCDS objects are based within Integration. After converting all relevant *CONTAIN objects back to *FILE objects. 2. the records may be modified in Production by a user program without conflict. type 8 (Display attributes) by a *RCDS object To print a description of the record range. Quality Assurance or Production by a user program is contrary to the design of Aldon LM(i) and may cause unexpected results. DO C-12 • Record Objects Aldon LM(i) Daily Operations Reference . Delete all *RCDS object definitions over the *CONTAIN files by doing the following: a. type 6 (Print source) by a *RCDS object *RCDS Objects in Multiple-Release Applications On addition of a new *RCDS object or checkout of an existing *RCDS object to a release that does not contain the underlying *CONTAIN files. To Delete *RCDS Objects 2. b. Set these options on the files in the descendent release using the procedure described in “To control *CONTAIN file replication and persistence” on page DO C-10. 3. At the Work with Objects by Release panel. At the Aldon LM(i) main menu. To stop handling records with *RCDS objects To stop handling the records contained in *RCDS objects with Aldon LM(i). Promote all *RCDS objects defined over a given file to Production. in the Opt field by the *RCDS objects you want to delete. Aldon LM(i) copies the *CONTAIN files and any logicals over them to the Production environment of that release. it is accompanied by a phantom copy of its corresponding physical file. *CONTAIN. Aldon LM(i) Daily Operations Reference Record Objects • DO C-13 . Aldon LM(i) creates and manages “phantom” copies of a file in each Development or test environment containing a *RCDS object based on it. Promote all *RCDS objects over the *CONTAIN object to Production. Delete the definitions of all *RCDS objects over the *CONTAIN object. If the file is a logical file. To meet this requirement while allowing multiple test environments. System i constraints require that if an executing application uses several *RCDS objects based on a given file. Phantom files do not appear on displays. The only actions allowed for a *CONTAIN file are: • Modification of the replication and persistence settings as described in “Controlling *CONTAIN File Creation Options” • Conversion back into a normal *FILE object by deleting all overlying *RCDS definitions To convert a *CONTAIN file back to type *FILE 1. and are not available for checkout or deployment. How Aldon LM(i) Manages the Physical and Logical Files Aldon LM(i) treats files on which *RCDS objects are based in a way somewhat similar to the way it handles files containing source for standard objects. Note Deletion of *RCDS objects leaves the records identified in the *RCDS object definition intact and unchanged in the base files. but are identified with a special Aldon defined type. all *RCDS objects must be obtained from the same file in the same library. The Production copies of the base files remain visible on displays of release objects.Working with Underlying Files Files converted to type *CONTAIN cannot be checked out for modification. 2. The *CONTAIN object converts the object back to type *FILE in all releases of the application. For the first promotion into a second test environment. For promotion into Production. Promotion of the last *RCDS object out of a Development or test environment may or may not cause Aldon LM(i) to delete the underlying members and files depending on the setting of Keep container file in all environments in the *CONTAIN file creation options for each *CONTAIN object. Aldon LM(i) creates new copies of the physical file members in the receiving environment using data from the Production copies of the files.) DO C-14 • Record Objects Aldon LM(i) Daily Operations Reference .” starting on page DO C-9. If necessary. copies of the records for the promoted object remain behind for testing with the other *RCDS objects. When a *RCDS object is promoted out of an environment which still contains *RCDS objects from the same files. The identified ranges of records from the Development files are then overlaid into these files. the files and members already exist and only the records for the *RCDS object are moved. (For details. New copies of the records are created in the environment into which the object is promoted. physical and logical files are again copied from the Production environment and then overlaid with the specified ranges of records. Promotion of a subsequent *RCDS object into an environment that already contains *RCDS objects defined over the same file members overlays records for the new object into the existing file members which contains records for the previously promoted record objects.For the first promotion. see “Controlling *CONTAIN File Creation Options. files to contain the members are also created along with any logical files used. For example. creating. and also from source member and object lists within Abstract/Probe+™ from Advanced Systems Concepts (ASC) or Hawkeye's Pathfinder™. if a release requires inclusion of objects in tasks. Values not available through substitution may be completed manually by prompting with F4. and promoting objects from PDM (IBM's Program Development Manager). These options work from both source member and object lists in PDM. and promote operations with user-defined options if they are authorized to perform these functions within Aldon LM(i). The option processing program substitutes information regarding the selected item into the command for the option and then executes the completed command.Daily Operations Reference For System i Servers Daily Operations DO Appendix D PDM-Style User Options About PDM-Style User Options PDM-style user options provide a convenient way to perform actions on items selected from a list. Aldon LM(i) also supports the use of PDM-style options created by the user or other vendors on several panels within the Aldon LM(i) panel interface. An option definition identifies the command to perform the action. Aldon provides user-defined options for checking out. To use an option. Aldon LM(i) enforces the same user authorities and release defined requirements when processing actions ordered with user-defined options as it does for actions initiated with the standard Aldon LM(i) panel interface. Aldon LM(i) enforces these rules for option generated checkouts just as it does for checkouts generated within Aldon LM(i). or entry of a comment at checkout. Daily Operations Reference For System i Servers PDM-Style User Options • DO D-1 . and maps data from the item list to the command parameters using substitution variables. build. A user can only perform checkout. type characters identifying the option on the option line by the desired item and press Enter. ASC and Hawkeye now includes several Aldon options in their option file. DO D-2 • PDM-Style User Options Daily Operations Reference For System i Servers . PDM supports non-alphabetized option files but third party vendors may require that the file be alphabetized by option code. Aldon Option Setup for Abstract/Probe+ and Pathfinder This section applies only to Aldon LM(i) users who also use ASC's Abstract/Probe+ or Hawkeye's Pathfinder for cross referencing and documentation. Contact ASC or Hawkeye for a new copy of this file. setup is complete. Some of these options are also included by ASC and Hawkeye in the user options file deployed with their products. Subsequent sections describe installation of the options for use with PDM from the file supplied by Aldon with Aldon LM(i). Activate the option file as described by the vendor's documentation. and Hawkeye's Pathfinder. Aldon options merged into an existing option file may not be accessible to the third party vendor's program. Do not merge Aldon options into the existing third party file with CPYF as described below. Earlier copies of the option file received from your vendor do not include Aldon LM(i) options. or hand key the Aldon options using the Add function within PDM's option 9 “Work with user defined options” function. This appendix assumes basic familiarity with PDM and Aldon LM(i). Merging Aldon's option file with an existing options file results in a non-alphabetized file. and how to set up user or third party provided options for use with the Aldon LM(i) panel interface. If the file includes the Aldon options. Aldon Option Setup PDM options for Aldon LM(i) are deployed in a file named QAUOOPT in the library ACMSLIB. ASC's Abstract/Probe+. The next section discusses Aldon option setup for ASC's Abstract/Probe+ and Hawkeye's Pathfinder.This appendix describes how to set up Aldon provided user-defined options for use with PDM. . . . . . . *CURLIB. At the PDM main menu.IBM PDM Change Defaults Panel Daily Operations Reference For System i Servers PDM-Style User Options • DO D-3 . . . Full screen mode . . . Compile in batch Run in batch . *SRCLIB Y=Yes. *CURLIB. . F3=Exit F4=Prompt F5=Refresh F12=Cancel Figure 62 . Library . 1. . . . . . Object library . . . . . . *LIBL Name Y=Yes. Start PDM by executing the following command: STRPDM The PDM main menu displays. . . . . . . . . F4 for list Name. . press F18 (Change Defaults) to display the Change Defaults panel: Change Defaults Type choices. . N=No Name Name. N=No Y=Yes. N=No Change type and text . Replace object . . . . . . . . . . . N=No Y=Yes. 3. To activate Aldon options Prerequisites Create the options file or merge the Aldon options into an existing options file as described in “To copy Aldon options” above. . . *LIBL Y=Yes. . . Option file . . . Member . . Sign on with your user profile. . . . . 2. *USRPRF. . . Example: CPYF FROMFILE(ACMSLIB/QAUOOPT) TOFILE(YOURLIB/YOURFILE) MBROPT(*ADD) CRTFILE(*YES) Note The command creates the file if it does not already exist. *CURLIB. . . . . . N=No Name. . . . . . . .Aldon Option Setup for PDM To copy Aldon options • Use the System i copy file command to copy the Aldon option file to a new file or append it to an existing user-defined option file. . *SRCLIB N Y N QBATCH *LIBL Y QAUOOPT QGPL QAUOOPT N Name. . Job description Library . . . . . press Enter. The following example command appends the Aldon options to the file YOURFILE in library YOURLIB if such a file exists. The Specify Option File to Work With panel (not shown) displays with the default options file filled in. Note If you added the Aldon supplied options to an existing options file with CPYF. Press ENTER to proceed to the Work with User-Defined Options panel: Work with User-Defined Options File . . : QAUOOPT Type options. If two options use the same letter code. the Aldon options appear at the end of the list. At the PDM main menu. press Enter. . . . 5. . : Library . Go More. In the and Member field.. eliminate the conflict by assigning a new code to either of the conflicting options with the following steps: DO D-4 • PDM-Style User Options Daily Operations Reference For System i Servers . 6. 2=Change 3=Copy Opt _ _ _ _ _ _ _ _ _ Option B C G P Q R BG CG PG Command /* ACMS /* ACMS /* ACMS /* ACMS /* ACMS /* ACMS /* ACMS /* ACMS /* ACMS 4=Delete */ */ */ */ */ */ */ */ */ 5=Display ACMSLIB/ACMSPDMCRT ACMSLIB/ACMSPDMCKO ACMSLIB/ACMSPDMGO ACMSLIB/ACMSPDMPRM ACMSLIB/ACMSPDMPRM ACMSLIB/ACMSPDMCKO ACMSLIB/ACMSPDMCRT ACMSLIB/ACMSPDMCKO ACMSLIB/ACMSPDMPRM IDLIB(&L) NAME( IDLIB(&L) NAME( IDLIB(&L) IDLIB(&L) IDLIB(&L) IDLIB(&L) IDLIB(&L) IDLIB(&L) NAME( NAME( NAME( NAME( NAME( NAME( Order BUILD Order CKO Go (proc. Press ENTER to return to the main PDM menu. : QAUOOPT QGPL Member . In the Library field. b. . . . type option 9 (Work with user-defined options) and press ENTER. Eliminate any conflicts between your options and those added from the Aldon file. . Command ===> F3=Exit F9=Retrieve F4=Prompt F10=Command entry F5=Refresh F6=Create F24=More keys Figure 63 .4. . 8. The complete option list appears in Table 3 on page DO -6. c. type the name of the library containing your options file. If two options use the same letter code. .. 7. orders) Order PRM Order PRM RQS Order CKO RQS Order BUILD. whichever option appears later in the list will not be accessible. .IBM Work with User-Defined Options Panel Note The figure shows some of the PDM options provided by Aldon. Example: Figure 62 identifies the options file QAUOOPT in library QGPL. Go Order CKO. . type the name of your options file. In the Option file field. Go Order PRM. type the name of the member containing your options. . At the Change Defaults panel identify the options file containing the options by doing the following a. At the Change User-Defined Option panel. press ENTER with no options selected to save your changes and return to the PDM main menu.a. Press ENTER to confirm the change and return to the Work with User-Defined Options panel. Single-object options streamline the process by omitting these panels and performing actions either with default values or with values entered using the F4 option prompt interface. type the new letter code. Using Aldon Options Overview and General Instructions Some Aldon supplied options create action orders in a queue. At the PDM main menu. others create action orders and execute all queued orders. Options that process orders from the queue invoke two panels for selecting orders from the queue for processing. 12. Processing of selected orders continues using the same panels used in the standard Aldon LM(i) panel interface. Follow the instructions in “To define a user options file” starting on page UG 2-7 in the “Aldon LM(i) User’s Guide” to define the user options file to Aldon LM(i). After resolving all conflicts. 11. press F3 (Exit) to exit PDM. b. in the Option field. Daily Operations Reference For System i Servers PDM-Style User Options • DO D-5 . still others act immediately on a single object. 9. 10. c. bypassing the order queue. type 2 (Change) and press ENTER to display the Change User-Defined Option panel. Sign on to Aldon LM(i). In the Opt field by the option you want to associate with a new letter code. and then initiate processing of all queued orders: CG. Five similar options first place an action order in the queue. B. and QG. Option G initiates queue processing without creating an order.User Defined PDM Options for Aldon LM(i) Processes Order Queue Performs action on single object without using orders. BG. and P1. and Q. Three options act immediately on a single object bypassing the order queue and parameter panel interface: C1. PG.The Aldon Options Five options place action orders in a queue without initiating processing: C. Table 3 provides a complete list of Aldon LM(i) PDM options. B1. queue. RG. R. P. or Aldon LM(i) panels Action Category Request Checkout Option Code R RG Creates an Order X X Included in third party vendor file as option: HR X Perform Checkout C CG C1 X X X X X X X X X X X X X X X X HC Build (Create) B BG B1 HB Request Promote Q QG Perform Promote P PG P1 Process Order Queue G HG DO D-6 • PDM-Style User Options Daily Operations Reference For System i Servers . Table 3 . allows you to select the desired copy from the list of available copies. The option processing program locates the correct copy of the object to satisfy your request or. Aldon LM(i) searches all releases in alphabetical order. then searches the last release the user worked with using the standard panel interface. To determine the release for a selected object. There are several strategies for selecting objects to act on. the option processor determines the release for an object from the library that contains the option selected copy. the option processor first searches for a release containing the current library. List objects or source members for objects you wish to work with by selecting any library or source file defined to Aldon LM(i) that contains them. when appropriate. Display all logical files built on a particular physical file or all physical files used by a particular logical file. When possible. are present in this environment. Display all programs that use a particular file or all files used by a particular program. Selecting a library in the environment you wish to act on limits the display to eligible objects. Daily Operations Reference For System i Servers PDM-Style User Options • DO D-7 . Selecting the appropriate Production environment library works well for many purposes because all objects. Initiate action on an object by selecting any copy of the object or the object's source. Finally. the release is initially ambiguous as a developer library may contain objects from several releases. if the object still is not found. When selecting objects from a developer library. Use ASC's Abstract/Probe+ or Hawkeye's Pathfinder to display logically related groups of objects. then searches for the object in the last release the user worked with using the option interface.Object Selection The Aldon LM(i) object database tracks all copies of each release object. except those newly added. 2=Change 3=Copy 8=Display description Opt C C CG Object DEMOCBL1 DEMOCBL2 DEMOCBL3 DEMORPG1 DEMORPG2 DEMORPG3 Type *PGM *PGM *PGM *PGM *PGM *PGM 7=Rename 11=Move .IBM Work with Objects Using PDM Panel PSELORDREL Type options.Main Module COBOL DEMO Program . Work with Objects Using PDM Library . Select objects with the C and CG options as shown in Figure 64. . . Select any number of objects before processing. Text COBOL DEMO Program . .Processing Queued Orders Select objects with Aldon LM(i) options to create action orders. ACMSDMOPDN Position to . . .Select Orders by Release Panel DO D-8 • PDM-Style User Options Daily Operations Reference For System i Servers .1st Subordinate COBOL DEMO Program . Position to type . . . . Press Enter to proceed to the Select Orders by Release panel shown in Figure 65. . The order processor breaks up large groups of orders into batches as necessary.2nd Subordinate RPG Program 1 for Aldon/CMS Demo RPG Program 2 for Aldon/CMS Demo RPG Program 3 for Aldon/CMS Demo Bottom Parameters or command ===> _________________________________________________________________________ F11=Display names and types F12=Cancel F13=Repeat F14=Display Size F23=More options F24=More keys Figure 64 . 4=Delete 9=Save Attribute CBL CBL CBL RPG RPG RPG 5=Display 10=Restore __________ __________ Type options. press Enter.. . . .. 1=Select Opt Release _ ALDON/ACMSDEMO/BASE <----. . This section illustrates processing of queued orders using an example in which three objects are checked out from a PDM object listing of a release's Production library. . .Order counts by type --------> RqsCKO CKO EmgCKO RqsPRM PRM Build 3 Select Orders by Release Command ===> _________________________________________________________________ F3=Exit F4=Prompt F9=Retrieve F12=Cancel F14=WRKSBMJOB F18=WRKSPLF Figure 65 . press Enter. One line appears on this panel for each release with orders pending. press Enter.emergency Request Promote Promote Build (Create) Errors Command ===> __________________________________________________________________ _______________________________________________________________________________ F3=Exit F4=Prompt F9=Retrieve F12=Cancel F14=WRKSBMJOB F18=WRKSPLF Figure 66 . In this example. the Check Out Objects panel shown in Figure 67 on page DO D-10 appears. Select the release with option 1 and press Enter to proceed to the Select Orders panel. PSELORD Release: Select Orders ALDON/SITE/CORPORATE Type options. Daily Operations Reference For System i Servers PDM-Style User Options • DO D-9 . If the queue contains orders for only one release the Select Orders panel is the first panel displayed. The Select Orders panel appears once for each release selected on the Select Orders by Release panel.” starting on page DO 3-2. The number of orders counts by type appear in columns on the right. select Check out with option 1 to process all checkout orders for this release using the panels discussed in the section “Checking Out Objects.Select Orders Panel Select the categories of orders you wish to process with option 1 and press Enter to proceed to the standard confirmation panels for each type of order. 1=Process 4=Delete Opt 1 Description Orders Request Checkout Check out 3 Check out . All orders pending for a given release display on the Select Orders panel as shown in Figure 66. Processing a category on the Select Orders panel with option 1 processes the valid orders and deletes those with errors for that category. Use option 4 to delete all orders pending for the release in a particular category. For this example. If the release specification is invalid. N=No Y=Yes. correct the problem. . Comment for log . . . Single-object options execute immediately when you press Enter using default values for all parameters. To developer . . . 2=Run in batch F3=Cancel F4=Prompt F7=Add task F12=Cancel F20=Enlarge list Figure 67 . B1. . DO D-10 • PDM-Style User Options Daily Operations Reference For System i Servers . Aldon LM(i) performs a standard checkout with the current user as developer under the assigned task if the object is in a task. N=No 1=Run interactively. . . . . or prompt these commands or the single-object options with F4.+ . . . Delete all pending orders for the invalid release. Emergency checkout? . . accomplish the remainder of ordered actions using panels in the standard Aldon LM(i) interface. Objects selected for checkout Object DEMOCBL1 DEMOCBL2 DEMOCBL3 Type *PGM *PGM *PGM Attribute CBL CBL CBL ---Env QUA ITG PRD From ----Library ACQUAL ACINTG ACMSDMOPDN More: . the Select Orders panel displays with only option 4=Delete active and a Status message describing the problem appears immediately below the release identification line. and submit the orders again. object? . . . For task . . . . CCKOOBJ Release: ALDON/ACMSDEMO/BASE Check Out Objects Type the additional checkout information below. Run option . build. . Remove active checked out Print checkout report? . . . N=No Y=Yes. . . . . MARKE N N N 1 + Name + Name Y=Yes. . . . or promote a single object quickly using default values with the single-object options C1. For example. .Check Out Objects Panel After selecting the release and category of orders for processing. . . . and ACMSPROMOT commands. . . . . The connection between the PDM or third party vendor program's object or member list and the standard Aldon LM(i) interface panels is seamless. Panels for managing the order queue and specifying parameters do not display. . and P1. . . . . . . press Enter. For information on default values see syntax diagrams for the ACMSCHKOUT. . ACMSCREATE. All Aldon panels are fully supported with cursor sensitive help text. Using Single-Object Options Check out. . and does not automatically replace an existing copy in the target developer library or produce a checkout report. . . . . select an object for checkout with C1 and press Enter. . . . . Daily Operations Reference For System i Servers PDM-Style User Options • DO D-11 .” panels accessed through the first five main menu options: Work with Objects by Developer. Command parameters not available from a given Aldon LM(i) panel via substitution may be entered during use of the option by prompting with F4. and Work with Tasks panels. Work with Object by Release. Select a two character option designator not already in use. The following example displays the System i description of an object from the Work with Objects by Developer panel: DO DSPOBJD OBJ(&L/&N) OBJTYPE(&T) An option using these substitution variables may also be used on other Aldon LM(i) panels if prompted for the name of the library containing the object. Work with Archive Objects. or by using a file editor... Work with Requests and Non-Conflict Conditions. Use substitution variables shown in Table 4.Use single-object options to quickly process a single object. Enter the command to perform the option action and any parameters you wish to fill with data from the Aldon LM(i) panel. Each single-object option runs as a separate job and without recognition of possible object interdependencies with other selected objects. The substitution variable &L is not available on other panels as object entries may represent copies of the object in multiple environment. Creating User Options Create user options using the PDM option editor by selecting option 9 on the initial PDM menu and then pressing F6. User Supplied Options Aldon LM(i) supports user supplied options on the “Work with. Subenvironment (developer) Object description (from Aldon LM(i) database) Logon user name User defined option.Substitution Variables Supported Var Meaning From the Work with Objects by Developer Panel: &N &T &A &L &SM &F &SL &GP &PD &RS &RF &EV &SE &X &US &C Object name Object type Object attribute Object library Object source member Object source file Object source library Group name Product name Release selected Release in which object exists Environment. DO D-12 • PDM-Style User Options Daily Operations Reference For System i Servers . From the Work with Object by Release Panel &N &T &A &SM &F &GP &PD &RS &RF &X &US &C Object name Object type Object attribute Object source member Object source file Group name Product name Release selected Release in which object exists Object description (from Aldon LM(i) database) Logon user name User defined option.Table 4 . From the Work with Archived Objects Panel &N &T &A &SM &F &GP &PD &RS &RF &X &US &C Object name Object type Object attribute Object source member Object source file Group name Product name Release selected Release in which object exists Object description (from Aldon LM(i) database) Logon user name User defined option.Substitution Variables Supported (Continued) Var Meaning From the Work with Tasks Panel &N &GP &PD &RS &RF &X &US &C Task name Group name Product name Release selected Release in which task exists Task text Logon user name User defined option.Table 4 . Daily Operations Reference For System i Servers PDM-Style User Options • DO D-13 . Substitution Variables Supported (Continued) Var Meaning From the Work with Conditions Panel &N &T &A &GP &PD &RS &RF &EV &SE &US &C Object name Object type Object attribute Group name Product name Release selected Release in which object exists Environment. DO D-14 • PDM-Style User Options Daily Operations Reference For System i Servers .Table 4 . Subenvironment (developer) Logon user name User defined option. . At the More Functions panel. . . Specify the file. . At the Aldon LM(i) main menu. library. . Daily Operations Reference For System i Servers PDM-Style User Options • DO D-15 . . press Enter. . . and member containing the user options in the fields provided and press ENTER. Library . . name Command ===> F3=Exit F4=Prompt F5=Refresh F9=Retrieve F12=Cancel Figure 68 .Set User-Defined Option File Panel 3. Member . . . press F22 (More functions) to display the More Functions panel. *NONE *NONE *NONE *NONE. Using User Options in Aldon LM(i) Enter the character code for the desired user option by the item upon which you wish to act and press either Enter to execute immediately or F4 to prompt the command for completion of additional parameters. . type 2 (Set user defined option file) and press ENTER to display the Set User Options panel: CUSROPT Set User-Defined Option File Type choices. in the option field. . . . name Name *FIRST. . . File . . . .Defining the Options File to Aldon LM(i) To define the user options file 1. 2. DO D-16 • PDM-Style User Options Daily Operations Reference For System i Servers . This enables inquiries without leaving Aldon LM(i). Configure Aldon LM(i) to access your vendor program using the Describe Third Party Vendor Products panel accessed with option 11 from the Global Setup menu. Aldon LM(i) Daily Operations Reference Interface to Abstract/Probe+™ and Pathfinder™ • DO E-1 . allowing initiation of Aldon LM(i) functions directly from Abstract/Probe+ or Pathfinder panels. Perform Aldon LM(i) functions directly from Abstract/Probe+ or Pathfinder via user-defined options. See “PDM-Style User Options.” starting on page DO D-1 for further information on the use of Aldon provided PDM options. Quick access to both packages is provided via “F22=More functions” which is available on many Aldon LM(i) panels.Aldon LM(i) Daily Operations Reference Daily Operations DO Appendix E Interface to Abstract/Probe+™ and Pathfinder™ Aldon Lifecycle Manager for System i (Aldon LM(i)) provides several interface features for shops using Abstract/Probe+ from Advanced Systems Concepts (ASC) or Hawkeye's Pathfinder for documentation and cross referencing. Both ASC and Hawkeye include a file containing Aldon LM(i) PDM-Style User Options with their products. Use the Define Documentation by Third Party Vendor Product panel accessed with option 9 from the Global Setup menu to configure automatic updating of your documentation tool's cross-reference database each time a program is promoted to an Aldon LM(i) Production library. DO E-2 • Interface to Abstract/Probe+™ and Pathfinder™ Aldon LM(i) Daily Operations Reference . ” starting on page UG 4-2 provides information on the following topics: • “Context-Sensitive Help Text” on page UG 4-2 • “Input Fields: Prompting and Selecting” on page UG 4-33 • “Scrolling” on page UG 4-3 • “Fully Functional Command Line” on page UG 4-4 This appendix describes additional user interface features not covered by the “User’s Guide” and provides additional details regarding some features.Aldon LM(i) Daily Operations Reference Daily Operations DO Appendix F The Panel Interface Introduction Aldon products follow the SAA/CUA (System Application Architecture/Common User Access) Standards defined for the System i by IBM. Aldon LM(i) Daily Operations Reference The Panel Interface • DO F-1 . Some features of the standards included in Aldon products are not yet included in IBM's most frequently used System i panels. These standards are gradually coming into widespread use. The “User’s Guide” section “Summary of Panel Interface Features. display fields. line 21-22 line 23-24 line 25 DO F-2 • The Panel Interface Aldon LM(i) Daily Operations Reference . : ALDONCOMM Type options. 1=Select 5=Display installation data Opt 9 Product ACMS ANALYZER INTEGRATE HARMONIZER S/COMPARE Text Aldon Aldon Aldon Aldon Aldon Change Management System Analyzer (Test Coverage Monitor) Automated Integration Tools S/Compare and Harmonizer S/Compare without Harmonizer Status Not found Not found Installed Installed Not found 19 20 21 22 23 24 25 Command ===> F3=Exit F4=Prompt F14=WRKSBMJOB 09-03 SA F9=Retrieve F10=Show library F11=Show version F18=WRKSPLF MW KS IM II S1 ALDONT01 KB Figure 69 .Parts of a Typical Aldon Panel Location line 1 lines 2-19 line 20 Description Panel Name and Title The panel body. . A command line is present on most panels immediately below the message line. Press F4 to view the detailed version of a message. . Press Page Down (Roll Up) to view the additional messages. This line remains blank when there is no message to display. Function key prompts are displayed at the bottom of the panel.Sample Aldon Product Panel The parts of a typical Aldon panel and their locations on the sample panel shown in Figure 69 are as follows: Table 5 . A program message line is located immediately below the working area of the panel. then Press enter. If there is more than one message. instructions. a + appears at the right end of the message line.The System i Panels Line Number STRALDPRD Start ALDON Products 1 2 Common installation library . Contains input capable fields. etc. Terminal information line. selection menus. Panel Body The area of a panel between the program message line and the title line receives input from and displays information to the user. Aldon LM(i) Daily Operations Reference The Panel Interface • DO F-3 . If a “+” symbol appears after the field. In some cases default values may be entered for you. Values preceded by a colon (:) are display only and cannot be changed. you may change the value.) Accepted values are often listed to the right of the field. (See the section PC Terminal Emulation for exceptions. The list of values is displayed on a “single selection panel” or “multi selection panel. If there is an underscore.” Selection panels are described below. The user documentation usually refers to panels using the full title. Input Fields Input fields appear as underscores.Panel Name and Title Every Aldon Lifecycle Manager for System i (Aldon LM(i)) panel has a name in upper left corner followed by a title. A description of the field and the range of accepted values is always available through help text. you may prompt for a list of accepted values by placing the cursor in the field and pressing F4. + Opt __ __ __ __ __ __ __ __ Object DEMOCL1 DEMOCL2 DEMOCL3 DEMOCL4 DEMOCL5 DEMOCL6 DEMORPG1 DEMORPG2 Type *PGM *PGM *PGM *PGM *PGM *PGM *PGM *PGM Attribute CLP CLP CLP CLP CLP CLP RPG RPG Cnd R Env IP IP P QP QP QP DP DP DVPs Emg N N N N N N N Y R C 2 1 Command ===> _________________________________________________________________ F3=Exit F5=Refresh F6=Add Object F8=Check out F10=Promote F12=Cancel F24=More keys Figure 70 . 5 Condition 6 7 ALDON/DEMOAPP Release . *ALL + *ALL + Environments . 3=Check out* 4=Delete 7=Promote* 8=Display attributes 13=Request checkout 17=Request promote . the item in the list immediately preceding the name's position is displayed. “More: +”. If no item matches exactly. Only items which satisfy all or the selection criteria display.1 of Demonstration Application *ALL Type . *ALL + Position to . . The selection fields default to values which display the largest number of items. Figure 70 on page DO F-4) to aid in finding desired items. . : 4 Object . Figure 74. Figure 70 on page DO F-4) for limiting the items displayed. . Change the selection fields and press Enter again to display different items. Enter an item name or search string and press Enter. The list of items is scrolled so that the first item matching appears on the top line. Change one or more selection field to tailor the group displayed to your requirements. . Press the Enter key to display the selected items.. the press Enter. DO F-4 • The Panel Interface Aldon LM(i) Daily Operations Reference . Panels entered from a panel with subsetting by selection fields in effect use the same selection criteria. or Page Up (Roll Down) when “-” displays to view additional items. . . and Figure 75). (*=Combined job) More: . .More: -+ When there is more information to view than will fit on one panel. “More: -+”. . . . Position to A panel which displays long lists of items may have a “Position to” field (line 7. . .Example Panel: Work with Release Objects Panel Selection fields Some panels which display lists of items provide selection fields (lines 5 and 6. Type options. Press Page Down (Roll Up) when “+” displays. : RELEASE11 Release 1.. . Line Number CWRKOBJ Example Panel: Work with Objects 3 Application: Text . or “More: -” displays on the right side of the panel (Figure 73. Has condition . A/C/R *NA. name *ALL. : RELEASE11 Type options. . the press Enter. . *ALL *ALL *NA *NA + *ALL.CSBSOBJ Example Panel: Subset Objects List Type choices. *NOT. press Enter. . WRKOBJ Application: Example Panel: Work with Objects ALDON/DEMOAPP Release . . . Aldon provides a function key to hide fields at the top of a panel to make more space available for list entries. This feature is usually activated with F20. . . Figure 72 shows the example Work with Object panel as it might look after use of an Enlarge list function key. Aldon LM(i) Daily Operations Reference The Panel Interface • DO F-5 . .Example Panel: Subset Objects List Subsetting Sometimes selection fields appear on a separate “Subset” panel.. D/I/Q/P Object type . In environment . . . . *ANY. obtained by pressing a function key (usually F17). F3=Exit F4=Prompt F5=Refresh F12=Cancel Figure 71 . .. . . When available. . generic*. . such as the one shown in Figure 71. *ACT. Object . . .+ Opt Object Type Attribute Cnd Env DVPs Emg __ DEMOCL1 *PGM CLP IP N __ DEMOCL2 *PGM CLP R IP N __ DEMOCL3 *PGM CLP P N __ DEMOCL4 *PGM CLP QP N __ DEMOCL5 *PGM CLP QP N __ DEMOCL6 *PGM CLP R QP N __ DEMORPG1 *PGM RPG C DP 2 N __ DEMORPG2 *PGM RPG DP 1 Y __ DEMORPG3 *PGM RPG C DP 2 N __ DEMORPG4 *PGM RPG DP 1 Y __ DEMORPG5 *PGM RPG DP 1 N __ DEMORPG6 *PGM RPG DP 1 Y Command ===> _________________________________________________________________ F3=Exit F5=Refresh F6=Add Object F9=Retrieve F12=Cancel F20=Reduce list F23=More options F24=More keys Figure 72 . 2=Edit source 4=Delete 5=Browse source 6=Print attributes 14=Create* 15=Change create options . (*=Combined job) More: . Press F20 again to reduce the list and restore the hidden fields. . . type *NA.Example Panel: Work with Objects Enlarge/Reduce List In other cases. . press F20 to hide fields at the top of the panel and enlarge the item list to fill the available space. . . N=No *NONE. N=No *NONE. . . N=No Y Y *NONE Y V5R2M0 . . press the Page Down key to display additional options (Figure 74. you may obtain additional columns of information by pressing Function keys identified with the prompts “View 2. . the Page Up and Page Down keys (Roll Down and Roll Up) are used to move between the related panels. press Enter. . . . . . . . . . . . . . . Archive source only . Defaults for new applications: Default owner of objects . *NONE Y 100 Y 3 Y N Command ===> _________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F9=Retrieve F12=Cancel Figure 73 . Alternate Views On some panels which display columns of information. “More: +” is displayed on the first panel (Figure 73) to indicate that more options must be viewed by pressing Page Down.Additional Option Prompts When more options are active for a panel than fit in the option prompt area. Additional Function Key Prompts When more function keys are active for a panel than fit on the function key prompt area at the bottom of the panel. . . Default TGTRLS for create commands . Function keys remain active regardless of whether or not they appear in the prompt area. . . . Y . Allow long object names . Options are active regardless of whether or not they are currently displayed in the prompt area. . CGLBDOPT1 Type choices. N=No Y Y=Yes. . Copy text to task notes category . . Compress source . . Press F23=More options to display additional options in the prompt area. name Y Y=Yes. . . the labels and actions of the function keys rotate so that the previous view may be recalled. N=No Y 1-998.) appears after the last prompt. . . Use deployment log . N=No Y 1-32754 Y Y=Yes. . . . . . . . . . Define Global Options More: . . *PRV. . . . . . . . . . Y *CURRENT. Use activity log . N=No Y Y=Yes. . . .Sample Multi-Page Panel. Default source file text length Use archiving . . Multi-Page Panels In cases where it is necessary to set a larger number of related options than will fit on a single display screen. .. Each time an alternate view is displayed by pressing a function key. . . *NOMAX Y Y=Yes. 1 of 3 DO F-6 • The Panel Interface Aldon LM(i) Daily Operations Reference .+ Allow Override (Y/N) Y=Yes. VxRxMx *NONE. Global options: Activate user request facility .” “View 3" etc. After completing the options on the first panel. . . . . . . Figure 75). Maximum copies to archive . . . . . . an ellipsis (.. . at the bottom of the panel. . . . . press F24=More functions to toggle the display to show additional function key choices. . notes category Y=Yes. . . . name Y=Yes. . press Enter. Define Global Options More: . . . Check the help text to be sure of a key's affect on a given panel. . . then press Enter to submit the panels. . N Y N N *NONE N Allow promotes to parent release . *NONE. Aldon LM(i) Daily Operations Reference The Panel Interface • DO F-7 . . . . Others work in one of several ways depending on the panel. . . . . A function key defined for a panel remains active even when its prompt is not displayed. . N=No Y=Yes. . . Press function key F24 to retrieve the remaining prompts. . N=No Y=Yes. Y=Yes. QUA. . Library group assignment . . . press Enter. . . . Create objects when promoting to . . . Allow multiple check outs. . . Function Keys At the bottom of each panel are one or more lines of function key prompts. . If exit program. . . . 2 of 3 CGLBDOPT3 Type choices. N=No Y=Yes. . Try available update for object replace Command ===> _________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F9=Retrieve F12=Cancel Figure 74 . Values are not accepted for processing until all available panels are viewed. . N=No *MAP. N Y N N N *MAP *NONE Y *SYS N Y=Yes. . . the most commonly used keys are displayed by default. . . . . . . . . . . Defaults for new releases (continued): Production environment options: Require request to promote to . Require comment to check out . N=No *SYS. . . . PDN Y=Yes. . . Require task to check out . Run S/Compare when promoting to . . If there is not enough room to display prompts for all of the active function keys. . Y=Yes. . . SQL naming option . exit program *NONE. Require request to install live from Reference library . Y=Yes. N=No Y Y Y Y Y Y Y Y Y Y Defaults for new releases: Require comment to promote . . . Below is a list of the most common function keys and descriptions of their modes of action. . .+ Allow Override (Y/N) . .Sample Multi-Page Panel. . . .CGLBDOPT2 Type choices. library . . . . Allow promotes with conflicts to Maintain object dependency data . Y=Yes. . Define Global Options More: Allow Override (Y/N) . ITG. 3 of 3 Use Page Up and Page Down to view and change options until the desired settings are achieved. . Some function keys perform consistent actions on all panels. . *PROMPT. . . . *SQL Y=Yes. N=No N=No N=No N=No *LIBL. . N=No Y Y Y Y Y Y Command ===> _________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F9=Retrieve F12=Cancel Figure 75 . . N=No Y=Yes.Sample Multi-Page Panel. . . Require request to check out . Exit the current function and return to the panel from which it was called.. F4=Prompt F5=Refresh F6. Toggle the option prompt lines to display additional options which are available.” panels with record including object names. After retrieving commands back to the beginning of the queue. F15=Unfold DO F-8 • The Panel Interface Aldon LM(i) Daily Operations Reference . Enter values in the fields to limit items selected for display on the previous panel. Toggle the function key prompt lines to display additional function keys which are available. If the cursor is positioned on an object name. Commands are retrieved in last-in first-out order. Options selected for preceding items in the list.. Used for adding a variety of user defined items to the system. Exits from the current panel to the previously displayed panel without performing the action in progress. Display additional information about each item listed. are left alone. above of the current cursor position. On “Work with. In these cases. Press F4 with the cursor on the command line. if the cursor is outside the record list area. Retrieves System i commands entered on the command line during the current Aldon session. Reduce the list and restore the hidden fields by pressing the key again. the values present in the system when the function key is pressed are displayed. F9=Retrieve F11=View 1.Table 6 . If the panel displays values which change as a job executes. a blank line is displayed. If a caret (>) appears to the right of the object name.. F7=Add. F3 and F12 which cancels the current panel will appear identical in function. F17=Subset F18=WRKSPLF F20=Enlarge/Reduce list F23=More options F24=More keys Display a panel with several selection fields.. Current values of input capable fields are not updated until the Enter key is pressed. Most functions in Aldon LM(i) are contained in a single panel. toggle between “folded” and “unfolded” record display mode which truncates or displays long object names using two-line records. Repeat any valid option from a particular item downwards to the end of the list in an option field.Common Function Keys Function Key Help Key or F1=Help Text F3=Exit Description Retrieves help text keyed to the position of the cursor. to prompt for System i commands.2. If the panel was initially displayed with default values. Hide fields at the top of a list panel to make room for more list entries. these default values are restored. then retrieval starts over again with the most recent command. less than the full name is being displayed on the panel. displays the full object name. Refresh fields with current values. Executes standard IBM “work with submitted jobs” command. or anywhere else.3 F12=Cancel F13=Repeat F14=WRKSBMJOB F15=Full name and F15=Full name/fold. Place the cursor in a field followed by a “+” symbol and press F4 to prompt for a list of input values. Executes standard IBM “work with spool files” command. When the command has executed the panel is redisplayed with the keyed values and a blank command line. and messages regarding batch job execution are displayed here. If all values keyed meet input requirements. There are two types of selection panels: single item and multiple item. Terminal Message Line Terminals perform some basic input validation before transmitting key strokes to the host system. If a command has been keyed on the command line. Values keyed elsewhere on the panel are saved but not processed while the command is executed. Informational messages about system status. Program Message Line The program message line remains blank most of the time. the data is processed. Input error messages generated by the terminal are displayed on the last line of the panel.Enter Key The Enter key submits the panel for processing. Selection Panels When F4 is pressed with the cursor on and input field followed by a “+” symbol. position the cursor on the message line and press the Help key. error messages. The same panel or next panel is displayed as requested. If no command has been entered. the values keyed in the panel body are edited by the terminal program for adherence to input requirements. A “+” symbol at the end of a message indicates that the message is longer than one line. or that there are additional messages to display. Position the cursor on the message line and press the Page Down key to view additional message lines. or enter another command on the command line. a selection panel listing available values for the field is displayed. Press Enter again to process the values keyed on the panel. only the command is processed. and serves as a boundary between the body of the panel and the command line and function key prompts below. reminders about input requirements. To view a more detailed version of a message. Aldon LM(i) Daily Operations Reference The Panel Interface • DO F-9 . 1=Select Opt Name CLNADR 1 CLNADRL 1 DEMOCBL1 DEMOCBL2 1 DEMOCBL3 KEYEDPF Type *FILE *FILE *PGM *PGM *PGM *FILE Select Objects MARKE/MARK1/BASE *ALL + *ALL. . . . press Enter.”) over the period preceding the item you wish to select and press Enter. Position to . CSELGRP Example Panel: Single Selection Select one group by typing a / over the period. values display on a multiple selection panel such as the panel shown in Figure 77 on page DO F-10. The selected items are entered in the input fields on the preceding panel. Type a “/” (any character except “. . The selected item is entered in the input field on the preceding panel. . Group . . type F12=Cancel Figure 77 . CSELRLO Release . .Example Panel: Multiple Selection DO F-10 • The Panel Interface Aldon LM(i) Daily Operations Reference . . BONNIEM F12=Cancel Figure 76 . ALDON . . . . . Type a 1 in the field preceding each item you wish to select and press Enter. . then press Enter. Select as many items as desired on a multiple selection panel. . Type option.Single Selection Panels Only one item may be chosen from a single selection panel. BILLR . .Example Panel: Single Selection Multiple Selection Panels When prompting to complete a series of identical input fields. . : Subset object type . As each item selected for the confirmed option is encountered. Aldon LM(i) processes items selected with standard options in order from the top of the list to the bottom. However. There are two types of options: standard options and “combined job” options. Select any number of items for action with a given combined job option but do not mix requests for a combined job option with any other options. Press Enter from this parameter entry or confirmation panel to process the first item selected and save parameters and the confirmed=Yes flag for the remaining items. This clears saved parameters and confirmed flags for un-executed selections and redisplays the main list showing those options that remain unprocessed. Processing of these options is handled as follows.Option Processing for Sub-Files (Lists) Some panels in Aldon products display a list or “sub-file” of items each of which may be manipulated by entering a menu selection on the option line immediately preceding it to the left and pressing Enter. This gives the appearance that all items selected for the option are processed together at that time. An asterisk (*) following the option prompt indicates a combined job option. some options pool all items selected for that action for parameter entry and confirmation on one panel. adherence to this processing order is obvious. Aldon LM(i) Daily Operations Reference The Panel Interface • DO F-11 . For some combinations of options. Processing continues with the next item in the main list. Select any number if items for action with any combination of standard options. it is processed without display of a panel or other visible cue using the previously entered parameters and confirmation flag. The program searches the remaining list for other items flagged for that option and displays all on this panel. Combined job options perform operations on items which may be interdependent in the order required by their relationships. Cancel processing of the list at any time with F12 or F3. The parameter entry or confirmation panel displays when the first item selected with the option is encountered in the list. but list order processing is preserved. All other options are standard options. Edit source. (*=Combined job) More: . Exit SEU when finished to continue option processing. Delete Confirmation Proceed with Delete? DEMOCL2 DEMOCL4 DO F-12 • The Panel Interface Aldon LM(i) Daily Operations Reference .. . 2=Edit source 3=Copy 4=Delete 5=Browse source 8=Display attributes 14=Create* 15=Change create options . Press Enter to confirm deletion of all objects selected and delete DEMOCL2. The SEU source member editing panel displays.Sub-File Option Processing Example Option and Object 2 DEMOCL1 Discussion Processing begins at the top of the list.Example Panel: Work with Objects The following table describes the step-by-step processing of the options selected in the example panel above.WRKOBJ Application: Example Panel: Work with Objects ALDON/DEMOAPP Release . the press Enter. A confirmation panel displays for all objects selected for deletion. . : RELEASE11 Type options.. Table 7 .+ Opt Object Type Attribute Cnd Env DVPs Emg 2 DEMOCL1 *PGM CLP IP 4 DEMOCL2 *PGM CLP IP 8 DEMOCL3 *PGM CLP P 4 DEMOCL4 *PGM CLP QP DEMOCL5 *PGM CLP QP 8 DEMOCL6 *PGM CLP QP DEMORPG1 *PGM RPG DP DEMORPG2 *PGM RPG DP DEMORPG3 *PGM RPG DP DEMORPG4 *PGM RPG DP DEMORPG5 *PGM RPG DP Command ===> _________________________________________________________________ F3=Exit F5=Refresh F6=Add Object F9=Retrieve F12=Cancel F20=Reduce list F23=More options F24=More keys Figure 78 . Display SEU Panel for editing DEMOCL1 4 DEMOCL2 Processing continues with the second selected object. Object Attributes Display for DEMOCL6 xxxxxxx xxxxx xxxxx xxxxx xx xxxxxx xxxxxx This table refers to the example depicted on the panel shown in Figure 78 on page DO F-12. and the field may be mistaken for a display field. input capable fields are sometimes not obvious to users working from PC's.Table 7 . When in doubt. In cases where the value completely fills the field. the empty positions display as underscores and the field is recognizable as input capable. the “Type” field on line 5 in Figure 70 on page DO F-4 would appear as *ALL___ on a PC instead of *ALL. When a value does not completely fill an input field. try entering a value or use Help text. Object Attributes Display for DEMOCL3 xxxxxxx xxxxx xxxxx xxxxx xx xxxxxx xxxxxx 4 DEMOCL4 The confirmation flag for deletion of this object was obtained when the first deletion was encountered. Aldon LM(i) Daily Operations Reference The Panel Interface • DO F-13 . There are no parameters to enter and there is no need for confirmation. no underscore characters are present.Sub-File Option Processing Example 8 DEMOCL3 The Display attributes option does not pool all selected objects for processing. For example. PC Terminal Emulation Some older IBM System i terminal emulation software for PCs does not support underscored alphanumeric characters. DEMOCL4 is now deleted without display of a panel. (DEMOCL4 deleted at this point with no display) 8 DEMOCL6 The final object is processed. Consequently. Each object selected is processed individually as it appears in the list. DO F-14 • The Panel Interface Aldon LM(i) Daily Operations Reference . and function keys displayed or available at any of the panels shown in this document.” starting on page DO G-2 • “SQL Packages.” starting on page DO G-4 Online Help Text For detailed descriptions of the fields. Aldon LM(i) Daily Operations Reference SQL Objects • DO G-1 . options.Aldon LM(i) Daily Operations Reference Daily Operations DO Appendix G SQL Objects This appendix includes the following topics: • “Adding SQL Objects.” starting on page DO G-3 • “Object Text for SQL Objects. please see the online help text. Adding SQL Objects Add SQL objects using the procedures described in “Adding an Object” starting on page UG 5-2 in the “Aldon LM(i) User’s Guide”. The following table provides information for adding SQL objects supported by Aldon LM(i): SQL Object Alias Index Table View Package Function Related System i System Type *FILE *FILE *FILE *FILE ILE: *PGM. *MODULE. or *SRVPGM *PGM or *SRVPGM Aldon LM(i) Type *ALIAS *INDEX *TABLE *VIEW *SQLPKG *FUNCTN Aldon LM(i) Extended Attribute EXT SQL SRC Procedure *PGM or *SRVPGM *PROC EXT SQL Trigger Type *PGM or *SRVPGM *SQLUDT *TRIGGER *TYPE All types can be defined as non-source or pseudo source base. Creating Pseudo-Source for SQL See “Working with Pseudo-Source” starting on page UG 5-6 in the “Aldon LM(i) User’s Guide” for more information. Details for Adding SQL Package Objects See “SQL Packages. a second panel appears for specification of the System i system name of the underlying file object on which the SQL object is based. Additional information specific to SQL objects is provided below. Details for Adding SQL File Based Objects When adding SQL file based objects. DO G-2 • SQL Objects Aldon LM(i) Daily Operations Reference .” starting on page DO G-3. Most Aldon LM(i) functions and features work with SQL packages. You can load and map SQL packages using standard loading and mapping procedures. the name you specify on the Add Object panel is the SPECIFIC parameter for the object creation statement. are defined to Aldon LM(i) as non-source objects. SQL packages are not archived. You can include SQL packages in tasks and deploy SQL packages. Specify the SQL procedure or function name for the function or procedure on a subsequent panel that displays automatically when needed. Aldon LM(i) handles SQL packages. Details for SQL Trigger and User Defined Type Objects When adding SQL trigger and type objects. promoted. you must designate “pseudo-source” as the source option. You must designate “pseudo-source” as the source option. and promote SQL packages using standard Aldon LM(i) options and procedures. You can checkout.Details for Adding Functions and Procedures When adding SQL functions and procedures in Aldon LM(i). SQL packages are non-source objects Outside of Aldon LM(i). Note In the present release you can define SQL user defined types present in Production libraries to Aldon LM(i) but they cannot be checked out. When you copy releases. This command examines the ILE program you designate and prepares and stores as many of the SQL statements it contains as possible. An SQL package allows faster execution of SQL statements in an ILE program. module. you create SQL packages using the OS/400 CL command CRTSQLPKG. or deployed. SQL Packages Aldon LM(i) handles SQL packages. but rather. create. Aldon LM(i) Daily Operations Reference SQL Objects • DO G-3 . or service program by storing SQL statements from the program prepared in advance of program execution. No additional panels display during the add process. (object type *SQLPKG). SQL packages are therefore not source based or pseudo-source based. Add an SQL package to Aldon LM(i) using the general instructions provided in “To add an object” on page UG 5-3 in the “Aldon LM(i) User’s Guide”. If the SQL package and the ILE program on which it is based are both resident in the same environment. Aldon LM(i) creates a “phantom” copy of the ILE program in the Developer environment for the SQL package to reference. Aldon LM(i) captures and displays the first 50 characters of the maximum allowed length of 2000 bytes. Aldon LM(i) also performs this service for SQL objects. Use the object type *SQLPKG and source option 9 (No source). Aldon LM(i) creates and deletes phantom copies of the ILE program as necessary to ensure that the copy of the ILE program the SQL package references is in the same environment. the ILE program with which the package is associated must be resident in the “promote to” environment or a higher environment (closer to Production). As you promote the SQL package. Notes You must create a new SQL package manually the first time in Development using the CRTSQLPKG command so that Aldon LM(i) can scan and capture parameters required to recreated it as needed later. DO G-4 • SQL Objects Aldon LM(i) Daily Operations Reference . Aldon LM(i) first tries to retrieve the LONG_COMMENT from a COMMENT ON statement for the object. text for the object is retrieved and made available for viewing on Aldon LM(i) panels. For SQL objects.Phantom programs created to support SQL packages Each SQL package is associated with one copy of an ILE program. To the extent possible. This allows Aldon LM(i) to make sure that a copy. Therefore. if you checkout an SQL package without also checking out the corresponding ILE program. The program object must have an extended attribute of ILE or BND. of the ILE program is present in the “promote to” environment so the SQL package can be recreated there. When you add and promote a new SQL package. Object Text for SQL Objects When you add or create a non-SQL object with Aldon LM(i). either resident or phantom. A promote requirement To add an SQL package You can create an SQL package for ILE program objects of type *PGM and *SRVPGM. The SQL program the SQL package supports must exist in the Development library when you add the SQL package. If a LONG_COMMENT is retrieved. you can promote them together to satisfy this requirement. DBXLFI.This LONG_COMMENT method does not currently work for *TYPE and *TRIGGER objects. DBXATR) CREATE INDEX USRSYS/DBXREL_DBXAFL_DBXALB_DBXATR ON QSYS/QADBXREF (DBXREL. The commands should be entered using the SQL interface (STRSQL or RUNSQLSTM using an SQL source member that contains the commands). CREATE INDEX USRSYS/DBXREL_DBXFIL_DBXLIB_DBXATR ON QSYS/QADBXREF (DBXREL. DBXFIL. If no LONG_COMMENT is retrieved. DBXAFL.) SQL Performance Improvement Suggestions Having large numbers of files on your system can affect performance in reading system files. Aldon LM(i) attempts to retrieve the TEXT value for the corresponding system object. (Note: this is not possible for *PROC and *FUNCTN objects. DBXATR) CREATE INDEX USRSYS/DBFFDP_DBFLIB ON QSYS/QADBFDEP (DBFFDP. DBFLIB) Aldon LM(i) Daily Operations Reference SQL Objects • DO G-5 . DBXLB2. DBXALB. DBXATR) CREATE INDEX USRSYS/DBXREL_DBXLFI_DBXLB2_DBXATR ON QSYS/QADBXREF (DBXREL. DBXLIB. Creating the following indexes can improve performance significantly. DBXATR) CREATE INDEX USRSYS/DBXFIL_DBXATR ON QSYS/QADBXREF (DBXFIL. DO G-6 • SQL Objects Aldon LM(i) Daily Operations Reference . Click on a page reference to jump to the indicated page. and a page number within that chapter or appendix. DO C-10 defined DO C-3 limitations and requirements DO C-3 mapping or loading files for DO C-5 overview DO C-2 replication of. see SQL. custom object type. custom object type. custom object type. types. Symbols *ALIAS. indexes *MENU objects adding DO B-3 Aldon LM(i) Daily Operations Reference • DO Index-1 . then select Go Back from the pop-up menu one or more times to return to this index. triggers *TYPE. see SQL. custom object type. Example: DO 1-5 indicates the fifth page of chapter 1 in the “Aldon LM(i) Daily Operations Reference Reference. see binding directory *CMD objects creating in Development DO 4-7 identifying command processing program DO 4-7 *CONTAIN files controlling replication of DO C-9. see SQL. custom object type. custom SQL object type.Aldon LM(i) Daily Operations Reference Daily Operations DO Daily Operations Reference Index Page Identifiers in Aldon System i Documents Page identifiers consist of a two character document abbreviation followed by a chapter number or appendix letter. types. see SQL. SQL. procedures *RCDS objects DO C-2 adding DO C-5 and multiple-release applications DO C-12 defining DO C-5 promoting. aliases For assistance in using Acrobat. From a referenced page. see service programs *TABLE. A Abstract/Probe+ access DO 2-4 acknowledgements analyzer cleared DO 5-6 acknowledgment conditions emergency checkout/promote DO 5-6 ACMSCHKFRN command adding objects to release from vendor release DO 4-13 ACMSCHKFRN command (check out foreign object) mentioned DO 4-13 Act upon Dependent Objects panel DO 4-28 activate conflict DO 5-10 Add Binding Directory Entry panel DO 4-23 add conflict DO 5-9 Add Release Object panel DO C-6 Aldon LM(i) design strategy DO viii users DO 1-14 Aldon LM(i) main menu DO 2-2 Aldon option setup for Abstract/Probe+ and Pathfinder DO D-2 PDM DO D-3 aliases. see SQL. controlling DO C-10 *FUNCTN. user defined *SRVPGM (System i object type). custom object type. first time DO C-11 *SQLPKG. see the chapter “Using CD-ROM Documents Online” in the Installation Guide. packages *SQLUDT (System i object type). custom object type. you can right-click. see SQL. Locate the desired topic in the index. see SQL. 2. tables *TRIGGER. see SQL. views 3. adding using pseudo-source DO B-8 working with DO B-6 working with pseudo-source based DO B-12 *PROC. custom object type. functions *INDEX.” Using This Single-Document Index 1. see SQL. see SQL. aliases *BNDDIR. see SQL. user defined *VIEW. see changing.Confirm Print of List Report DO 6-3 Change *CONTAIN Creation Options panel DO C-10 Change Checked Out Object panel DO 4-10 Change Object Creation Options panel DO 4-17 change object data option DO 2-7 changing checked out objects. delta DO 3-19 CMOVOBJDSC DO 3-42 CMRGOBJPRN DO 3-27 CMRGSRC DO 5-14 commands ACMSVFYAPP (verify release) ACMSVFYAPP command (verify release) DO 5-16. identified DO 5-11 resolving conflicts DO 5-11 container files.CCFMPRTDVO DO 6-3 conflict types DO 5-9 conflicts checkout DO 5-9 checkout. and Aldon LM(i) DO 1-13 B base releases defined and illustrated DO 1-10 illustrated DO 1-11 LM(i) supports unlimited number per application DO 1-10 object’s presence in indicated on Aldon LM(i) panel DO 2-8 required in forming application DO 1-10 based on residence status field DO 4-7 binding directories assigning DO 2-13 completing object dependency data DO 4-20 to DO 4-24 BND extended attribute value for ILE DO 4-11 converting back to OPM from DO 4-13 C cancel requests or clear conditions DO 5-5 CCFMPRTDVO .PRTFCHKOUT DO 6-6 checkouts transferring to different developer DO 3-9 child releases checking out logical files with physical files DO 3-10 illustrated DO 1-11 merging to parent release DO 2-13 child vs. DO 5-17 conditions creation of objects not inhibited by DO 4-5 working with DO 5-2 conditions defined DO 5-2 Confirm Delete of Objects panel DO 3-45 Confirm Print of List Report . see *CONTAIN files copying PDM-style option files DO D-3 create commands DO Index-2 • Aldon LM(i) Daily Operations Reference .allow promote to parent DO 3-20 ANALYZER cleared DO 5-6 ANALYZER hold DO 5-7 ancestor releases illustrated DO 1-11 applications identifying DO 1-2 archiving deleting an object copy from library DO 3-46 mentioned DO ix relationship of to release environments DO 1-4 associating source and object when adding to an application DO 4-10 source with an object DO 4-10 attributes object. recommendation DO 3-10 dependent objects DO 4-26. DO 4-28 by adding to a checkout list DO 3-6 groups of objects DO 1-9 with or without task association DO 3-6 checkout act on objects using DO 3-8 available interfaces DO 3-6 conflict DO 5-9 discussed DO 3-2 to DO 3-6 eligible agents DO 3-3 eligible objects DO 3-3 eligible recipients DO 3-3 introduced DO viii. DO 5-18. object descriptions library group assignments DO 3-42 object attributes DO 4-11 object descriptions DO 4-9 object library groups DO 3-38 object source files DO 3-38 object source members DO 3-38 user defined options DO D-3 checking out child release.PRTFCHKOUT DO 6-6 checkout report . System i object. DO 1-6 object flow during DO 3-4 overview DO 3-2 ownership and authority assignments during DO 3-5 checkout objects report . DO 5-19 common installation library STRALDPRD command DO 2-1 Community Manager access from Aldon LM(i) DO 1-9 compare DO 5-13. see object attributes authorities. see creating objects.PRTFDSPLOG DO 6-9 Development Log. handling DO 3-16 data option DO 2-7 Data sets file descriptions updated automatically on promotion DO 4-5 Defaults object ownership and authorities DO 1-13 Define *RCDS Object panel DO C-7 Define Module Object panel DO 4-12 Defining user options file to Aldon LM(i) DO D-15 delete changed object of cleared conflict DO 5-10 delete conflict DO 5-10 Delete Development Log Entries panel DO 4-38 delete from environment conflict DO 5-10 Deleting development log entries DO 4-38 deleting archived objects DO 3-46 objects DO 3-45 delta release data hold DO 5-7 delta releases defined and illustrated DO 1-10 illustrated DO 1-11 LM(i) supports unlimited number per application DO 1-10 object’s presence in indicated on Aldon LM(i) panel DO 2-8 Dependent objects acting on subsetting lists of DO 4-29 dependent objects acting on DO 4-28 checking out DO 4-28 creating DO 4-28 leaving resident on promote DO 3-15 lists of DO 4-28 promoting DO 4-28 deploying on promote to parent DO 3-24 Deployment overview DO 1-8 descendent releases illustrated DO 1-11 Developers DO 1-14 developers changing DO 3-9 transferring checked out objects DO 3-9 development environment introduced DO 1-3 Development log deleting records from DO 4-38 Development creates not included in DO 4-33 printing reports from DO 4-34 selecting records in for display by release relationship DO 4-34 viewing object histories for multiple objects in DO 4-32 development log DO 1-9 development log action codes DO 4-35 Development Log Entry Detail panel DO 4-34 Development Log Report . create commands DO 4-6 Create Object Report .PRTFCREATE DO 6-7 Create Objects panel DO 4-7 Create* DO 2-11 Creating user options DO D-11 creating checkout requests DO 3-6 promotion requests DO 3-18 Creating objects authority required DO 4-5 eligibility rules for DO 4-4 ILE programs DO 4-8 non-resident DO 4-6 overview DO 1-12 set up for logical files that reference logical files DO 4-8 creating objects *CMD objects in development DO 4-7 command defaults DO 1-12 command definitions DO 1-12 create command selected automatically DO 4-6 dependent DO 4-26 overview DO 1-12 cross-reference files. using the DO 4-32 development tools user defaults DO 2-4 Display Development Log panel DO 4-33 E Editing objects System i *MENU objects Aldon LM(i) Daily Operations Reference • DO Index-3 . third party automatic update during promotes DO 3-17 CRTDUPOBJ DO 3-26 CSBMJOBLBL DO 3-28 CSELCHGCRT DO 4-18 CSELRELLGP DO 3-42 Custom Reports DO 6-2 D data library update failure DO 5-6 data on promotion. development DO 1-9 Logical files referencing other logical files. see SQL. DO 3-8 promotion requests DO 3-18 functions.using the pseudo-source method DO B-12 editing objects System i *MENU objects DO B-6 emergency acknowledgement DO 5-6 emergency checkout conflict DO 5-9 emergency checkouts DO 3-18 promoting objects after DO 3-18 Environments Aldon LM(i) DO 1-3 Development DO 1-3 Integration DO 1-4 Production DO 1-4 environments quality assurance DO 1-4 extended attributes. DO 4-20 to DO 4-24 converting back to OPM from BND DO 4-13 converting programs to DO 4-11 creating DO 4-8 extended attribute values for DO 4-11 modifying and testing DO 3-44 modifying and testing modules for DO 3-44 indexes. see SQL. functions accelerating execution of SQL statements in. see object extended attributes F failure condition data library update DO 5-6 Flow charts Aldon LM(i) Environments DO 1-3 flow charts object movement DO 3-4. DO 5-17 objects into parent vs. SQL. DO 5-17 Help text function key access to DO F-8 mentioned DO ix hot keys DO 2-5 How to view object histories for multiple objects DO 4-32 how to merge objects into parent of a delta DO 3-27 promote objects to parent of a Delta DO 3-21 start Aldon LM(i) from the Aldon products menu DO 2-1 M Managers DO 1-15 merge DO 4-37. SQL. DO 3-12 foreign checkout conflict DO 5-10 fulfilling checkout requests DO 3-6. promote DO 3-26 selected objects by batch job DO 3-26 selecting objects DO 3-26 task/release connections DO 3-26 merge modified source DO 5-13 I ILE programs DO Index-4 • Aldon LM(i) Daily Operations Reference . DO 5-13. packages completing object dependency data DO 2-13. see SQL. indexes installing live additional features DO 3-29 by task DO 3-29 changing default data conversion specifications DO 3-33 changing default installation method DO 3-31 changing default schedule DO 3-30 changing the comment DO 3-30 clearing invalid requests DO 3-37 controlling content installed DO 3-29 fulfilling requests DO 3-36 requesting DO 3-34 to multiple targets per environment DO 3-29 Integration (Aldon LM(i) environments) discussed DO 1-4 L leave resident purpose of DO 3-15 Librarians DO 1-15 library groups changing for a group of objects DO 3-42 changing for an object DO 3-38 changing for an object’s source DO 3-38 load conflict DO 5-10 log. set up for creation of DO 4-8 logical files checking out with physicals for child release DO 3-10 promotion of DO 3-13 G global user defaults DO 2-3 global view DO 2-3 H Harmonizer comparing Harmonizer merging DO 5-13. and Hawkeye Pathfinder interface DO D-1 Other Setup Recommendations for ILE Objects DO 4-24 Overview Aldon LM(i) environments DO 1-3 releases DO 1-9 Ownership of objects DO 1-13 P packages. discussed DO 4-4 creating to make resident. promote.Merge Objects into Parent panel DO 3-27 Merge Source panel DO 5-13. or source members DO 3-38 multiple checkout conflict DO 5-9 N Non-resident objects creating to make resident. source files. DO 4-9. DO 1-6 object version number DO 3-26 objects adding DO 4-13 changing production locations DO 3-38 Objects with residence status field (Create Objects panel) DO 4-7 OPM extended attribute value for ILE DO 4-11 OPM extended attribute value for ILE programs converting back to from BND DO 4-13 Options PDM style. DO 3-42 Move/Define Objects (Library Groups) DO 3-43 request checkout DO 3-7 Select Copy of Object to Delete DO 3-46 O object attributes changing DO 2-11. DO 5-14 merge to parent version number DO 4-37 merging log entries DO 3-26 to parent how to DO 3-27 More Functions panel DO 2-4 Move/Define Object in Descendent Release DO 3-42 Move/Define Objects (Library Groups) panel DO 3-43 Move/Define Objects panel DO 3-40. library list for DO 4-4 creating. and related functions) DO 3-1 objects to new library groups. see SQL. SQL. programs and service programs DO 2-13 object deployment. DO 4-11 changing when converting to ILE DO 4-13 conversion of program to ILE DO 4-11 object creation commands DO 1-12 role in auto selection of create commands DO 4-6 Object dependency data specifying manually DO 4-19 using DO 4-26 when obtained DO 4-18 object dependency data completing for ILE DO 4-20 to DO 4-24 completing for ILE binding directories. procedure for DO 4-6 non-resident objects phantom objects defined DO 4-4 version numbers not incremented DO 4-5 notified releases conflict records created on promote to parent DO 3-20 changing to convert a program to ILE DO 4-11 changing when converting from BND back to OPM DO 4-13 changing when converting to ILE DO 4-11. packages Page headings (for Reports) DO 6-1 Panel interface DO F-1 panel specific subsetting DO 2-5 panels Act upon Dependent Objects DO 4-28 Add Release Object DO C-6 Aldon LM(i) main menu DO 2-2 Change *CONTAIN Creation Options DO C-10 Change Checked Out Object DO 4-10 Change Object Creation Options DO 4-17 Confirm Delete of Objects DO 3-45 Create Objects DO 4-7 Define *RCDS Object DO C-7 Define Module Object DO 4-12 Delete Development Log Entries DO 4-38 Development Log Entry Detail DO 4-34 Merge Objects into Parent DO 3-27 More Functions DO 2-4 Move/Define Object in Descendent Release DO 3-42 Move/Define Objects DO 3-40. see deploying and deployment object descriptions changing DO 4-9 object extended attributes changing DO 4-9 Aldon LM(i) Daily Operations Reference • DO Index-5 . DO 3-42 moving groups of objects DO 3-42 objects (checkout. DO 4-12 identifying the program model as ILE DO 4-14 role in identifying program model as ILE DO 4-9 Object movement DO vii. DO D-1.checkout report DO 6-6 PRTFDSPLOG . authorizing DO 1-15 R record objects DO C-2 reference libraries introduced DO 1-13 reference objects introduced DO 1-13 release checkout conflict DO 5-9 Release Conflict (REL) DO 5-9 release levels indicated on Aldon LM(i) CWRKOBJREL panel DO 2-8 release view DO 2-16 Releases overview DO 1-9 remote developers objects not scanned DO 4-19 remove a data set update failure DO 5-6 Reports DO 6-1 DO Index-6 • Aldon LM(i) Daily Operations Reference . DO 6-10 PRTFDVPOBJ . moving objects DO 3-12 to DO 3-14 dependent objects DO 4-26 eligible agents DO 3-11 eligible objects DO 3-10 from child DO 3-21 groups of objects DO 1-9 interfaces available DO 3-17 leaving objects resident DO 3-15 level checks caused by. automatic coordination DO 3-15 place of DO viii session protection during DO 3-12 to parent DO 4-31 capabilities and features DO 3-19 discussed DO 3-19 to DO 3-24 effects of DO 3-19 how to DO 3-21 prerequisite for requesting DO 3-25 prerequisites DO 3-20 promotion. procedures production environments preventing level checks DO 4-4 Production libraries number supported DO 1-4 promote to parent function DO 3-19 promote from child conflict DO 5-9 Promote Object Report DO 6-7 Promote/Create Object Report DO 6-7 promoting access to the function DO 3-18 automatic update of third party files DO 3-17 creating vs. handling data DO 3-16 PRTFCHKOUT . DO D-11 phantom objects considered non-resident DO 4-4 create function DO 4-4 physical files checking out with logicals for child release DO 3-10 point and shoot orientation DO ix PowerHouse access to from DO 2-4 preface DO vii Print source DO 2-10 procedures. resolving DO 3-14 logical files.Work with Objects by Developer report DO 6-4 PRTFPROMOT .Promote Object Report DO 6-7 PRTFPRTOBJ . automatic coordination DO 3-16 object flow during DO 3-12 object movement. see SQL.Object Data Report DO 6-8 Pseudo-source determining whether used for an object DO A-3 discussed DO A-2 working with. DO 3-17 ownerships and authorities managed by Aldon LM(i) DO 3-15 physical file prevented by link to logical outside of Aldon LM(i) DO 3-15 physical files. additional details DO A-2 Q quality assurance discussed DO 1-4 quality assurance personnel.Display Development Log Report DO 6-9. DO 2-17 Transfer Objects DO 3-9 Work with Binding Directories DO 4-22 Work with Objects by Developer DO 4-2 Work with Objects by Release DO 2-9 Work with Requests and Non-Conflict Conditions DO 5-4 parent releases illustrated DO 1-11 PARLENV DO 2-16 Pathfinder HAWKBAR menu access DO 2-4 user-option interface DO D-1 PDM-style user options DO D-1 to DO D-15 using from Aldon LM(i) panels DO 2-14. SQL.Set User Options DO D-15 Set User-Defined Option File DO D-15 Specify Library Groups for Descendent Releases DO 3-42 Submit Job with Varying Library Lists DO 3-28 Subset Dependent Objects List DO 4-29 subset objects by release list DO 2-15. diagram DO 1-6 overview DO 3-10. changing for an object DO 3-38 Specify Library Groups for Descendent Releases DO 3-42 SQL adding objects DO G-2. see SQL. adding DO G-2 tables DO G-2 triggers DO G-2 types. triggers Types of objects supported DO 1-5 types. panels DO 2-15 Substitution Variables Supported table DO D-12 System i *MENU objects based on pseudo-source editing DO B-12 System i menu objects adding to Aldon LM(i) DO B-3 adding using pseudo-source DO B-8 T tables. user defined DO G-2 limits of Aldon LM(i) current support DO G-3 views DO G-2 SSA compliance DO ix starting LM(i) from the Aldon products menu DO 2-1 STRALDPRD command start Aldon products DO 2-1 Submit Job with Varying Library Lists panel CSBMJOBLBL DO 3-28 Subset Conflicts List panel DO 5-8 Subset Dependent Objects List panel DO 4-29 subset objects by release list panel DO 2-15.Create Object Report DO 6-7 Display Development Log DO 6-9. types. DO 2-17 Subset Requests and Non-Conflict Conditions List panel DO 5-4 Subsetting dependent object lists DO 4-29 subsetting work with. see SQL. DO G-3 to DO G-4 procedures DO G-2 service programs. user defined U user classes predefined DO 1-14 user defaults Aldon LM(i) Daily Operations Reference • DO Index-7 .. SQL. see SQL. DO 6-10 Object Data Report DO 6-8 Promote Object Report DO 6-7 Promote/Create Report DO 6-7 Work with Objects by Developer DO 6-4 reports checkout report DO 6-6 request and non-conflict conditions DO 5-5 Request Checkout panel DO 3-7 request conditions checkout DO 5-5 request for checkout DO 5-5 request for install live DO 5-5 request for promotion DO 5-5 request for promotion to parent release DO 5-6 requests install live DO 5-5 promote to parent DO 5-5 promotion DO 5-5 residence status field (Subset Objects by release panel) DO 2-16 retired object DO 2-7 S scanning remote developer DO 4-19 Screen Design Aid tool setting display vs. SQL user defined. tables tasks adding when defining new objects DO 4-15 testing create non-resident function DO 4-4 ILE modules DO 3-44 ILE programs DO 3-44 preventing level checks DO 4-4 Tracking object status DO 1-9 Transfer Objects panel DO 3-9 triggers. changing for an object DO 3-38 members.. DO G-3 aliases DO G-2 functions DO G-2 indexes DO G-2 object text acquisition and display DO G-4 packages DO G-2. menu default DO 5-12 Select Copy of Object for Change of Creation Options panel DO 4-18 Select Copy of Object to Delete panel DO 3-46 Service programs adding SQL DO G-2 and SQL packages DO G-3 Set User Options panel DO D-15 Set User-Defined Option File panel DO D-15 sibling releases illustrated DO 1-11 Single-copy create specifications creating DO 4-16 deleting DO 4-18 source code files. SQL. . DO 2-14 XX=user defined PDM-style options DO 2-14 Work with Requests and Non-Conflict Conditions DO 5-4 Work with Requests and Non-Conflict Conditions panel WRKCND DO 5-4 Work with. SQL. DO 4-3 Work with Objects by Release panel DO 2-9 Work with Objects by Release panel options * (after an option description) DO 2-9 10=specify data conversion DO 2-10 11=print attributes DO 2-10 12=work with conditions DO 2-11. see SQL. panels DO 2-5 working with *RCDS objects DO C-11 dependent objects DO 4-18 object by release DO 2-6 objects DO 4-1 objects by developer DO 4-2 physical files for *RCDS objects DO C-5 System i menu objects DO B-6 System i menu objects based on pseudo-source DO B-12 DO Index-8 • Aldon LM(i) Daily Operations Reference . DO 3-5 authority options for promote function DO 3-17 users (Aldon LM(i)) discussed DO 1-14 V version numbers incrementing rules DO 4-37 views.... views W Work with Binding Directories panel DO 4-22 Work with Objects by Developer panel DO 4-2. DO 2-12 13=request checkout* DO 2-11 15=change create options DO 2-11 16=change DO 2-11 17=request promote* DO 2-11 18=work with tasks DO 2-11 19=alternate edit DO 2-11 2=edit DO 2-9 20=scan for requisite objects* DO 2-11 23=check out (emergency)* DO 2-12 24=work with archive DO 2-12 25=retire DO 2-12 27=promote to parent* DO 2-12 29=move/define (library groups)* DO 2-12 3=check out DO 2-10 30=display log DO 2-12 32=change create overrides DO 2-12 35=Compare DO 2-12 37=request promote to parent* DO 2-12 39=display requisite objects DO 2-13 4=delete DO 2-10 40=define requisite objects DO 2-13 41=act upon dependent objects DO 2-13 42=act upon dependent objects* DO 2-13 44=Deploy* DO 2-13 44=Work with deployment sets DO 2-13 45=assign binding directories DO 2-13 47=install live* DO 2-13 5=browse source DO 2-10 50=merge into parent* DO 2-13 57=request install live* DO 2-14 7=promote* DO 2-10 8=display attributes DO 2-10 9=move/define DO 2-10 99=display LM(i) blocking where used.*USERDFT subsetting using DO 2-15 option 19=Alt edit response when *FILE DSPF ambiguous DO 5-12 user defined create commands selected automatically DO 4-6 user defined options DO D-11 Aldon LM(i) panels DO D-1 changing DO D-3 PDM and Pathfinder DO D-1 users authority options DO 2-14.