implementer user guide

IMPLEMENTER

w w w . m k s . c o m

User Guide

MKS ImplementerUser Guide

The information in this manual is subject to change without notice.

Copyright 1988-2002 MKS Inc. and Mortice Kern Systems International SRL. All rights reserved.

MKS Inc. ato this matparticular damages r

All rights ror translat

All MKS pregistered

CORPORAT410 AlbertWaterloo, Canada

tel: 519 884fax: 519 88sales: 800 2

www.mks

SIU5.3-0203nd Mortice Kern Systems International SRL (collectively MKS) make no warranty of any kind with regard erial, including, but not limited to the implied warranties of merchant ability, performance, or fitness for a purpose. MKS shall not be liable for errors contained herein, or for any direct, incidental, or consequential esulting from the use of this material.

eserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, ed into any language in any form by any means, without written permission from MKS.

roducts are trademarks or registered trademarks of MKS Inc. All rights reserved. All other trademarks or trademarks are the property of their respective holders.

E HEADQUARTERS WORLDWIDE OFFICES: StreetON N2L 3V3

22514 886165 2797

.com

2500 S. Highland AvenueSuite 200Lombard, IL USA60148tel: 630 495 2108fax: 630 495 3591sales: 800 633 1235

15 Third AvenueBurlington, MA USA01803tel: 781 359 3300fax: 781 359 3399

12450 Fair Lakes CircleSuite 400Fairfax, VA USA22033tel: 703 803 3343fax: 703 803 3344sales: 800 265 2797

Martinstrae 42-4473728 EsslingenGermanytel: +49 711 351775 0fax: +49 711 351775 11

Third Floor, Dukes CourtDuke Street, WokingSurreyGU21 5BHUnited Kingdomtel: +44 (0)1483 733900fax: +44 (0)1483 733901sales: +44 (0)1483 733919

31

Table of Contents

Chapti

ers 1 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Who Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2What to Know Before Using This Product . . . . . . . . . . . . . . . . . . . . . . 2Whats Inside This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8MKS Issue Tracking Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Using DesignTracker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Using Integrity Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Using Integrity Manager and DesignTracker . . . . . . . . . . . . . . . 10Issue Database Considerations and Assumptions . . . . . . . . . . . 11

Starting Implementer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Menu Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Overview of Implementer Features . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Integration With Integrity Manager . . . . . . . . . . . . . . . . . . . . . . . 15The Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Technology-based Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Change Control Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Developer Productivity Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Distribution Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Test Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Inquiries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Release Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Third-Party Vendor Integration . . . . . . . . . . . . . . . . . . . . . . . . . . 28Additional Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Whats New in This Release? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Documentation Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Integrity Manager Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Technology-based Enhancements . . . . . . . . . . . . . . . . . . . . . . . . 32User Interface Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Vendor Integration Enhancements . . . . . . . . . . . . . . . . . . . . . . . 36

User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38System Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

ii

Table of Contents

Project Leader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Tester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Understanding Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Environment Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40u s e r g u i d e

Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Source Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Object Owners and Authorities . . . . . . . . . . . . . . . . . . . . . . . . . . 42Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Library List Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Defaults for Promotion Requests . . . . . . . . . . . . . . . . . . . . . . . . . 44Remote Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Environment Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Object Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Environment Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Environment Integrity Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Application Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3 Using the Workbench for Development Activities . . . . . 49Understanding the Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Using the Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Identifying Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Reviewing Work Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Checking Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Changing Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Compiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Promoting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Time Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Managing Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Workbench Ease of Use Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Optional Check Out and Promotion Methods . . . . . . . . . . . . . . 55Member/Object Status and History . . . . . . . . . . . . . . . . . . . . . . . 55Alternate Views and Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Multiple Selection Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Automatic Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Concurrent Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56User-Defined Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Work With Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Command Prompting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Using the Clipboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Basic Clipboard Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Using Command Options to Add Clipboard Items . . . . . . . . . . 60Using the ICRTRQS Command to Promote Clipboard Items . 63

Table of Contents

Using the IPRCCBD Command to Process the Clipboard . . . . 63Checking Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Check Out Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Checking Out From Work With Objects . . . . . . . . . . . . . . . . . . . 67Checking Out Using the Clipboard . . . . . . . . . . . . . . . . . . . . . . . 69iii

Performing Emergency Check Out . . . . . . . . . . . . . . . . . . . . . . . 69Checking Out for Concurrent Development . . . . . . . . . . . . . . . 69Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Editing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Using PDM User-Defined Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Setting Up User-Defined Options . . . . . . . . . . . . . . . . . . . . . . . . 72Changing User Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Displaying PDM User-Defined Options . . . . . . . . . . . . . . . . . . . 77Processing PDM User-Defined Options . . . . . . . . . . . . . . . . . . . 77

Workbench Compiles of Locked Objects . . . . . . . . . . . . . . . . . . . . . . 79Identifying the Compile Object . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Workbench Testing of Locked Objects . . . . . . . . . . . . . . . . . . . . . . . . 83Setting a Library List From an Environment Library List . . . . 83Available PDM Default Options . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Displaying Related Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Promotion Request Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Promotion Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Creating Promotion Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Task Variations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Compiling and Moving Promotion Requests . . . . . . . . . . . . . . . . . . . 89Member/Object Status and History . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Online Inquiry of Development Activity . . . . . . . . . . . . . . . . . . . . . . 95Working With Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Changing a Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Deleting a Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Associating Multiple Design Requests With a Lock . . . . . . . . . 99

Changing a Design Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Repeating Workbench Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

4 Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Creating Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Creating Projects From Implementer . . . . . . . . . . . . . . . . . . . . . 104Creating Projects From ProjectMaster . . . . . . . . . . . . . . . . . . . . 106Setting Up a Default Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Project Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Project Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Project Management Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Time Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Advanced Scheduling Features . . . . . . . . . . . . . . . . . . . . . . . . . 109Reporting Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

iv

Table of Contents

5 Performing Check Out . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Check Out Fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Check Out Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Using the One Step Checkout Method . . . . . . . . . . . . . . . . . . . 113Using the Traditional Checkout Method . . . . . . . . . . . . . . . . . . 115u s e r g u i d e

Task Variations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Checking Out Single Source With Multiple Objects . . . . . . . . 123Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Using Object Version Stamping in Check Out . . . . . . . . . . . . . . . . . 125Processing Versions in Check Out . . . . . . . . . . . . . . . . . . . . . . . 125

Checking Out IFS Files and Directories . . . . . . . . . . . . . . . . . . . . . . . 127IFS Object Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . 127Checking Out Using the IFS Object Name . . . . . . . . . . . . . . . . 128Checking Out the Contents of an Environment . . . . . . . . . . . . 129Check Out IFS (ICHKOUTIFS) Command . . . . . . . . . . . . . . . . 130Automatically Creating Object Codes in Check Out . . . . . . . . 134Support for Multi-Platform Check Out . . . . . . . . . . . . . . . . . . . 135

Checking Out for Concurrent Development . . . . . . . . . . . . . . . . . . 136Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Checking Out Related Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Task Variation for Multiple Recurring Members/Objects . . . 140Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Checking Out With a Design Request . . . . . . . . . . . . . . . . . . . . . . . . 141Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Using ILE Object Codes in Check Out . . . . . . . . . . . . . . . . . . . . . . . . 148Binding Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Bound Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149ILE SQL Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Service Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Update Service Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149ILE Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Update ILE Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Checking Out Physical File Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Using Different Source and Object Names in Check Out . . . . . . . . 151User Authorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Typical User Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152LANSA Export/Import Authorities . . . . . . . . . . . . . . . . . . . . . 152

Checking Out for Reject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Removing Source and Objects From QA . . . . . . . . . . . . . . . . . . 153Task Variation for Rejecting From the Menu . . . . . . . . . . . . . . 154Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Object Name Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Performing Name Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Check Out (ICHKOUT) Command . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Table of Contents

Check Out Command Variations . . . . . . . . . . . . . . . . . . . . . . . . 162Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Converting RPG/400 or RPGIII Source Code to ILE RPG/400 . . . 163Converting CRTBNDxxx ILE Programs to CRTPGM Programs . . 165Checking Out Using PathFinder Information . . . . . . . . . . . . . . . . . 167v

Environment and Library Setup . . . . . . . . . . . . . . . . . . . . . . . . . 167Performing the Check Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

6 Performing Promotions . . . . . . . . . . . . . . . . . . . . . . . . . . 171Promotion Request Fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Promotion Request Numbering . . . . . . . . . . . . . . . . . . . . . . . . . 173Creating Promotion Requests in Batch . . . . . . . . . . . . . . . . . . . 173Default Compile Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Promotion Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Create Request Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Creating Requests With the One Step Promotion Method . . . . . . . 175Resolving Promotion Request Problems . . . . . . . . . . . . . . . . . . 177

Creating Requests With the Traditional Promotion Method . . . . . 177Optimizing Physical File Promotions . . . . . . . . . . . . . . . . . . . . 183Overriding Job Submission Defaults . . . . . . . . . . . . . . . . . . . . . 186Changing Job Queues During the Compile Step . . . . . . . . . . . 187Changing Compile Commands . . . . . . . . . . . . . . . . . . . . . . . . . 187Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Creating Requests by Selecting From Locks . . . . . . . . . . . . . . . . . . . 189Benefits of Selecting From Locks . . . . . . . . . . . . . . . . . . . . . . . . 190Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Creating Requests From the Object List . . . . . . . . . . . . . . . . . . . . . . 192Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Creating Requests From the Member List . . . . . . . . . . . . . . . . . . . . . 193Task Variations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Creating a Request by Copying a Request . . . . . . . . . . . . . . . . . . . . 195Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Creating Requests With the ICRTRQS Command . . . . . . . . . . . . . . 196Creating Requests With the ICRTRQS Command PDM Option . . 198

Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Selecting Additional Target Environments . . . . . . . . . . . . . . . . . . . . 199

Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Promoting Related Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Related Request Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Overriding Create Request Defaults . . . . . . . . . . . . . . . . . . . . . . . . . 205

Removing Objects and Source in Promotion . . . . . . . . . . . . . . 205Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Changing Request Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

vi

Table of Contents

Maintaining Promotion Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Promoting IFS Files and Directories . . . . . . . . . . . . . . . . . . . . . . . . . 212

Support for Browser-based Promotions . . . . . . . . . . . . . . . . . . 213Options for Promoting IFS Objects . . . . . . . . . . . . . . . . . . . . . . 213Considerations When Using *.* for Promotion . . . . . . . . . . . . 214u s e r g u i d e

Automatically Creating Object Codes in Create Request . . . . 215Upgrading a Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Java Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Promoting Physical File Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Using Different Source and Object Names in Promotion . . . . . . . . 219Compiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Staged Compiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Compile Library List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Third-Party Compile Procedures . . . . . . . . . . . . . . . . . . . . . . . . 223Job Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Compile Request (ICMPRQS) Command Option . . . . . . . . . . . . . . 224Moving Promotion Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Allocating Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Authorities and Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Source Member Considerations . . . . . . . . . . . . . . . . . . . . . . . . . 225Issuing Move Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228Move Request (IMOVRQS) Command Option . . . . . . . . . . . . 228

Special Command Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Special Command Substitution Variables . . . . . . . . . . . . . . . . . 233Special Commands in Promotion: IEXCRQSDTL Command 236Special Commands to Manage DDM . . . . . . . . . . . . . . . . . . . . . 240Special Commands to Change Promotion Status . . . . . . . . . . 245Special Commands in Check Out . . . . . . . . . . . . . . . . . . . . . . . . 245Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Managing Concurrent Development . . . . . . . . . . . . . . . . . . . . . . . . . 248Resolving a Conflict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Advanced Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Object Version Stamping in Promotion . . . . . . . . . . . . . . . . . . . 251Emergency Promotions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Problem Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Completing Failed Promotions . . . . . . . . . . . . . . . . . . . . . . . . . . 254Other Creation Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255Using ILE Object Codes in Promotion . . . . . . . . . . . . . . . . . . . . 256Batch Promotion Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256Distributing Promotion Requests . . . . . . . . . . . . . . . . . . . . . . . . 256

Scheduling Promotion Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Table of Contents

Promotion Request Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258Promotion Step Internal Processing . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Create Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Export Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Compile Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262vii

Distribution Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263Move Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263Work Libraries Used During Promotion . . . . . . . . . . . . . . . . . . 265Host Work Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Remote Work Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

7 Performing Distributions . . . . . . . . . . . . . . . . . . . . . . . . . 271Moving and Distributing Promotion Requests by System . . . . . . . 272

Moving/Distributing All Promotion Requests By System . . . 272Submitting Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274Moving/Distributing to a Specific System . . . . . . . . . . . . . . . . 275Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277Move/Distribute by System Submission Options . . . . . . . . . . 277

Displaying Move Requests by System/Environment . . . . . . . . . . . 278Filtering Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Controlling Remote Job Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . 280Using the Default Job Schedule . . . . . . . . . . . . . . . . . . . . . . . . . 280Overriding the Default Job Schedule . . . . . . . . . . . . . . . . . . . . . 281Remote Job Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Changing Remote Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Moving Remote Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Using the Implementer Receiver Menu . . . . . . . . . . . . . . . . . . . . . . . 287Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Working With Requests on the Remote System . . . . . . . . . . . . 288Restoring Remote Requests (IRSTRMTRQS) . . . . . . . . . . . . . . 289Moving Remote Requests (IMOVRMTRQS) . . . . . . . . . . . . . . 290

Working With Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

8 Handling Emergency Situations . . . . . . . . . . . . . . . . . . . 295Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Archiving Source and Objects on a Promotion Request . . . . . 296Using the Archive to Tape Features . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Working With Tape Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Archive Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Archive Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300Recovering Archived Source/Object by Request . . . . . . . . . . 300Common questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302Automatic Check Out Archive Options . . . . . . . . . . . . . . . . . . 302

viii

Table of Contents

Emergency Check Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Emergency Promotion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

9 Member and Object Handling . . . . . . . . . . . . . . . . . . . . . 307u s e r g u i d e

Compile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308Database Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Managing Non-Source-based SQL . . . . . . . . . . . . . . . . . . . . . . . 309Managing Source-based SQL (DDL) . . . . . . . . . . . . . . . . . . . . . 311Managing Traditional DDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

Special Object Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318Data Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318Data Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319Commands and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Managing ILE Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319Support for Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320Support for Service Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . 321Loading ILE Objects Into the Repository . . . . . . . . . . . . . . . . . 322Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

S/36 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325S/38 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325Extended Object Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

10 Integrating With Other Vendor Products . . . . . . . . . . . . 327Application and CASE Software Products . . . . . . . . . . . . . . . . . . . . 328American Software Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Object Codes for Check Out and Promotion . . . . . . . . . . . . . . 329Compiling Cobol Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330Message File Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

AS/SET Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330Checking Out AS/SET Definitions . . . . . . . . . . . . . . . . . . . . . . 331AS/SET Dependency Checking . . . . . . . . . . . . . . . . . . . . . . . . . 332Promoting AS/SET Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 334Archiving AS/SET Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 335Remote Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

BPCS Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336CODE/400 Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Creating the User-Defined Options . . . . . . . . . . . . . . . . . . . . . . 337Launching CODE/400 from Implementer . . . . . . . . . . . . . . . . 338

COOL:Xtras Change Management Integration . . . . . . . . . . . . . . . . 338Basic Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339Development Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345Member/Object Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345SQL Support for COOL:2E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

Table of Contents

Check Out Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346Working With Model Object Lists . . . . . . . . . . . . . . . . . . . . . . . 347Checking Out Model Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 347Concurrent Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349Checking Out Versionable Model Objects . . . . . . . . . . . . . . . . 349ix

User Exit Program Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350Promoting Model Information . . . . . . . . . . . . . . . . . . . . . . . . . . 351Promotion Flow: COOL:2E to COOL:2E Environment . . . . . . 351Promotion Flow: COOL:2E to Traditional Environment . . . . 354Working in a Change-Controlled Model . . . . . . . . . . . . . . . . . . 356Model Object Audit Information . . . . . . . . . . . . . . . . . . . . . . . . 357Impact Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359Managing EXCUSRSRC and EXCUSRPGM . . . . . . . . . . . . . . . 359Merging Model Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362Remote Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

J.D. Edwards Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363Starting the Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364Support for J.D. Edwards Traditional Objects . . . . . . . . . . . . . 364Support for J.D. Edwards DREAM Writer Versions . . . . . . . . 364Checking Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Displaying J.D. Edwards Items . . . . . . . . . . . . . . . . . . . . . . . . . . 365Compiling From the Workbench . . . . . . . . . . . . . . . . . . . . . . . . 365Promoting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366Remote Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366Archiving J.D. Edwards Special Objects . . . . . . . . . . . . . . . . . . 366

LANSA Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367Checking Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367Promoting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369Displaying Process/Functions . . . . . . . . . . . . . . . . . . . . . . . . . . 370Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370Save File Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371Remote Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371LANSA Export/Import Authorities . . . . . . . . . . . . . . . . . . . . . 372LANSA RDML Function Compare . . . . . . . . . . . . . . . . . . . . . . 372Understanding the Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

Lotus Notes and Domino Integration . . . . . . . . . . . . . . . . . . . . . . . . 376Powerhouse Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376Utility Software Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377ABSTRACT Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Version Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378Abstract User-Defined Options . . . . . . . . . . . . . . . . . . . . . . . . . 378Accessing ABSTRACT From Implementer . . . . . . . . . . . . . . . . 380

AOS Message Manager Integration . . . . . . . . . . . . . . . . . . . . . . . . . 380AS/NET Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381MIMIX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

xTable of Contents

NetView/DM Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381Net/Wrk400 Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381PathFinder Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

PathFinder Database Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . 382PathFinder User-Defined Options . . . . . . . . . . . . . . . . . . . . . . . 382

Appenu s e r g u i d e

PathFinder PDM Options for USERPATH . . . . . . . . . . . . . . . . 383PathFinder PDM Options for USERPDM . . . . . . . . . . . . . . . . . 383

ROBOT Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384

dixes A Compare/Merge Member Commands . . . . . . . . . . . . . . 385Compare Member (ICMPMBR) Command . . . . . . . . . . . . . . . . . . . 386Compare Member Report Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392LANSA Compare RDML (ICMPRDML) Command . . . . . . . . . . . . 394

LANSA Compare Members Report . . . . . . . . . . . . . . . . . . . . . . 396Merge Member (IMRGMBR) Command . . . . . . . . . . . . . . . . . . . . . . 398Merge Member Merge Report Listing . . . . . . . . . . . . . . . . . . . . . . . . 408

B Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

1Before You Begin1

Implementer is the leading change management solution for the iSeries 400 available on the market today. It provides developers and IT managers with a feature-rich and easy to use environment that expedites development by managing and streamlining critical development processes.

This chapter covers:

who should read this guide

what to know before using this product

whats inside this guide

document conventions

getting help

Before You Begin

2

Who Should Read This GuideThis guide is intended for Implementer users who play the following roles in software development projects:

Whau s e r g u i d e

Project leaders responsible for creating projects, managing concurrent development, moving and deploying promotion requests, and updating the system administrator about required system-wide changes.

Developers responsible for checking out members/objects from production libraries into development environments, creating promotion requests targeted to test or production environments, and submitting promotion requests for compiling into staging libraries.

Testers responsible for accepting promotion requests into test environments, testing changes, creating promotion requests to production or additional test environments, and submitting promotion requests for compiling into staging libraries.

NOTE

This guide is useful as a source of conceptual, user-related information. The Implementer System Administrator Guide provides the information that system administrators use on a daily basis.

t to Know Before Using This ProductThe instructions for using his product assume that you are familiar with the following:

OS/400 operating system

OS/400 security

OS/400 communications

Command line

Software development policies and procedures for your organization

NOTE

Throughout this guide, any references to the IBM iSeries 400 apply also to the IBM AS/400.

Whats Inside This Guide

Whats Inside This GuideThis guide contains comprehensive information about using all features that pertain to the setup and maintenance of Implementer. The guide is organized as follows:3

Chapter Description

Chapter 1: Before You Begin

Introduces you to MKS Implementer. Describes who should read this guide and how to use it, and options for getting help.

Chapter 2: Getting Started

Explains where to find product installation information. Overviews the important features of Implementer, including whats new in this release. Describes the various user roles.

Chapter 3: Using the Workbench for Development Activities

Explains the versatile features of the Workbench. Describes how to access important Implementer features while using the Workbench as a home base for your work. Identifies where to look in this guide to find detailed information about each activity.

Chapter 4: Projects Explains how to use the Implementer to interface with MKS ProjectMaster, and perform common project management related activities.

Chapter 5: Performing Check Out

Explains the two checkout methods, and how to check out members/objects. Describes the various check out related options.

Chapter 6: Performing Promotions

Explains the two promotion methods. Describes how to promote member/objects from development to QA, and from QA to production. Describes the various promotion-related options.

Chapter 7: Performing Distributions

Explains how to distribute members/objects to remote systems using the Implementer Receiver.

Chapter 8: Handling Emergency Situations

Explains how to archive and roll back to prior member/object versions. Describes how to perform emergency check out and emergency create request functions.

Before You Begin

4

Docu

Chapter 9: Member and Object Handling

Explains how Implementer supports the different OS/400 types of objects and source members.

Chapter 10: Integrating Discusses the Implementer support for other vendor

Chapter Descriptionu s e r g u i d e

ment ConventionsThroughout this guide, the following typographical conventions are used.

NOTE

Notes containing important information are bordered by lines on the top and bottom.

With Other Vendor Products

software products. Explains actions you must take to ensure maximum integration. This chapter is divided into two sections to reflect the type of software products supported, Application and CASE products, and Utility products.

Appendix A: Compare/Merge Member Commands

Explains how to use the Compare Member (ICMPMBR) and Merge Member (IMRGMBR) commands to simplify and automate the process of comparing and integrating programming modifications, during the development process.

Appendix B: Glossary Defines the terminology that relates to Implementer.

Items in documentation Appear as

References to other manuals, new terms, and variables

italics

Keys you press, programs, files, directory names, and drive letters

ENTER

Code-based information, such as system messages, field syntax, macros, and commands, and information you type on menus and panels

ADDLIBLE

PC menus, commands New > Problem

PC drop-down menus the Session command

PC Dialog boxes, features Edit Options, Cancel, OK

Path names c:\mks\demo

Getting Help

Getting HelpMKS Customer Support is ready to assist you with product solutions. For assistance, you can choose the online system or telephone a Customer Support Representative.5

For online support, browse to www.mks.com and follow the links to the Support area. There you will find Frequently Asked Questions (FAQs), information about current releases, solution downloads, and Knowledge Base articles that can help you to quickly find the answers you need.

The hours of operation for MKS Customer Support are as follows:

North America: 8:00 A.M. to 8:00 P.M., Monday to Friday, Eastern Standard Time (GMT-5)

United Kingdom: 9:00 A.M. to 5:30 P.M., Monday to Friday, British Standard Time (GMT)

Germany: 9:00 A.M. to 5:30 P.M., Monday to Friday, West Europe Standard Time (GMT+1)

Online Web www.mks.com

E-mail [email protected]

Telephone North America 800 633 6298630 652 9350519 884 2270

UK +44 (0) 1483 733910Germany +49 711 351 775 51

Fax North America 630 495 4855

UK +44 (0) 1483 733901Germany +49 711 351 775 11

Before You Begin

6 u s e r g u i d e

2Getting Started7

This guide is for MIS professionals who implement change management or perform change management tasks. This chapter provides an overview of Implementer.

This chapter covers:

system requirements

issue tracking solutions

starting Implementer

overview of Implementer features

whats new in this release

user roles

understanding environments

Getting Started

8

System RequirementsThe minimum system requirement for this Implementer release is a RISC-based processor running OS/400 V4R4 or greater.

MKS

UsingDesigu s e r g u i d e

Additional requirements may apply for complete functionality of the MKS Integrity Solution multi-platform integration. For more information, see the Implementer Multi-Platform Solutions Guide.

Issue Tracking Solutions MKS creates solutions that help you where it matters mostin the management of changes in all your critical files and in the promotion of workflow collaboration among people in your organization. Put simply, MKS has the right solution for your business. In fact, keeping up with the pace of technology does not have to be painfulon the contrary, MKS thinks that setting the pace is much more rewarding.

nTrackerDesignTracker, one of the MKS iSeries Solution products, is delivered with Implementer. DesignTracker resides on the iSeries 400 and provides native workstation-based problem management capabilities. It manages issues and workflow for data processing services (service requests) and software development projects (design requests) on the iSeries 400. When you install Implementer, DesignTracker is the default issue-tracking system.

Although a legacy issue-tracking system, DesignTracker serves to address the needs of less complex environments. However, even if you have a more complex environment it may also serve the needs of your organization, particularly if you have external green screen interfaces into DesignTracker, or if you use the release management features of Implementer. Likewise, if you have Implementer integrated with SupportCenter for help desk management, or ProjectMaster for project management (provides total integration of the MKS iSeries Solution).

Today, however, many organizations are realizing an increasing need to adapt to the rapidly changing realm of technology and to capitalize on solutions that address those evolving needs. For organizations with more sophisticated and complex environments, MKS provides two additional options for issue tracking and managing development workflow:

MKS Issue Tracking Solutions

The best of breed solution uses Integrity Manager (replacing DesignTracker) to provide Windows and browser-based issue management and integrates with Implementer for iSeries 400-change management.

The alternate solution integrates Integrity Manager with

UsingManag9

DesignTracker and uses DTBridge (shipped with Implementer) to map updates between Integrity Manager and DesignTracker.

Both of these solutions are described next.

NOTE

Integrity Manager is a separately licensed component of the MKS Integrity Solution.

Integrity er

Integrity Manager is the best of breed enterprise choice for highly customizable process and workflow management. Any simple defect-tracking tool can record the status of a change request, but it does not monitor all the components that need to be modified, or the variety of tasks that need to be performed to resolve the issue. Integrity Manager extends the concept of defect tracking to include support for managing components, tasks, and workflow. This is particularly important when your organization has implemented a Software Configuration Management (SCM) process for the proposal, review, and approval of all software changes.

With this solution, Integrity Manager is the enterprise-wide issue management system that completely replaces DesignTracker. Integrity Manager integrates with other developer productivity toolsincluding Implementer, to control and track development activity in Implementer, and Microsoft Project, to leverage software investments and enhance coverage of the application development lifecycle.

Integrity Managers platform transparent, advanced, multi-tier architecture is scalable across the enterprise to support distributed developers and other constituents in the change process. Integrity Manager:

helps your development team capture and track all data related to change in your software system

allows you to set up a workflow to manage the change process

allows you to create change packages to correlate issues with specific Implementer revisions

provides metrics for your data including queries, reports, and charts

Getting Started

10

Integrity Manager is an extremely flexible issue management system that allows any number of user-defined issues, each identified by its type, and each type having its own user-defined set of fields; DesignTracker is more rigid with fixed type service requests and design requests that have various attributes.

UsingManagDesigu s e r g u i d e

Integrity Manager controls the activities of check out and promotion by an issues state, (whereas DesignTracker manages these activities by the status of a design request). Integrity Manager allows each issue type to have its own workflow of allowed state transitions. State based capabilities are assigned to the issue states to control the use of issues in check out and create request, and to allow Implementer to manage the check out and promotion functions.

The core of this integration allows Implementer to directly access Integrity Manager issues and update the issue state based on the development progress in Implementer. The issue ID associated with changing an item is trackedalong with the actual development changein Implementer; the issue details and state are tracked in Integrity Manager.

Integrity er and

nTracker

For organizations that require DesignTrackerfor example, if you use Implementers release management feature or are using SupportCenter or ProjectMasterbut you also have a need for Windows-based issue tracking, this solution works well.

With this solution, DesignTracker is used to manage and track service requests and design requests on the iSeries 400.

Integrity Manager uses issues to track changes in the software development cycle. For example, your administrator can configure Integrity Manager in a way that a problem issue may be associated with a solution issue for easy tracking and monitoring of both issues. Each issue has an audit trail, which may be used to evaluate internal processes for the effectiveness of the problem resolution process. In effect, issues track all aspects of any engineering endeavor.

Issue types capture and track a specific change request, defect, problem, solution, or task. For example, one issue type could record bugs and deficiencies in design. Another issue type could be used to request design changes that fix problems, or propose enhancements or new functionality for your product.

DTBridge (provided in Implementer) allows you to operate the centralized issue tracking system integrated with iSeries 400 change management. When DTBridge is run, issues entered into Integrity Manager are moved to the iSeries 400when an issue meets the criteria established within the DTBridge setup, a new design request is created on the iSeries 400 and the

MKS Issue Tracking Solutions

Integrity Manager issue is updated with the new design request number. You can elect to post all issues or a subset of issues based on rules that you define.

Issue Database Consiand Assum

Throughout this manual, the terms issue and design request or 11

derations

ptions

DR are interchangeable to the extent that any references to issues assumes that Integrity Manager is installed and configured as your issue tracking system, and any references to design requests (or DRs) and Service Requests assumes that DesignTracker is installed and configured as your issue tracking system.

On the Implementer panels that allow the use of an issue or a design request (for example, the Workbench, Check Out panel, Create Request panel, and inquiries) the field name Issue Number displays when Integrity Manager is installed; the field name Design Request displays when DesignTracker is installed. Throughout this guide, the field name Issue Number displays.

On the Implementer reports that print an issue or design request (for example, Request Report, Activity Report, Lock Report) the field name Issue Number displays when Integrity Manager is installed; the field name Design Request displays when DesignTracker is installed. Throughout this guide, the field name Issue Number displays.

Integrity Manager and DesignTracker cannot be used concurrently. If you currently use DesignTracker and want to convert to Integrity Manager, contact Customer Support for further information. If you currently use DesignTracker and plan to continue using DesignTracker, no further action is required.

For detailed information about the Implementer and Integrity Manager integration, see the Implementer Multi-Platform Solutions Guide.

Getting Started

12

Starting Implementer To start Implementer, use the Start Implementer (STRIM) command.

If you received the Implementer product from Computer Associates and

Menuu s e r g u i d e

have Implementer enabled for COOL:2E change management:

References to or the use of the Start Implementer command STRIM can be replaced with the STRCM command.

References to or the use of the Start Implementer Receiver command STRIR can be replaced with the STRCR command.

The host system default library name is Y2SYCM (not MKSIM).

The remote system default library name is Y2SYCR (not MKSIR).

The next section provides a listing of the command parameters that can be used with the STRIM and STRCM commands.

Access While My Workbench provides access to the day-to-day tasks performed by the developer, the menus allow access to all capabilities of Implementer. In addition, each menu option can be accessed directly by the STRIM command.

Menu access options are described in this guide when they are used for specific tasks.

You display the Implementer menu by using the STRIM command. The menu contains the following sections spread across multiple panels:

implementation

other common tasks

emergency functions

reports

setup functions

utilities

commands

Starting Implementer

Menu Access Command Options

Menu Option STRIM Command Value

Activity Report *ACTRPT13

Archive History Report *ARCHRPT

Archive Recovery *ARCRCV

Check Out *CHKOUT

Compile Promotion Request *CMPRQS

Concurrent Development Report *CONDEVRPT

Create Promotion Request *CRTRQS

Move Promotion Request by System/Environment *MOVRQSSYS

Environments *WRKENV

Environment Groups *WRKENVGRP

Environment Report *ENVRPT

Function Keys *WRKFNCKEY

Integrity Manager Setup *INTMGRSET

Job Log Inquiry *JOBLOGINQ

Lock Report *LCKRPT

MenuPanel 1 *M1 or *MENU1




Manage All Concurrent Development *MNGCONDEV

Move Promotion Request *MOVRQS

My Workbench *WRKBCH

Network Configuration *NETCFG

Objects *WRKOBJObject Codes *WRKOBJCDEObject Code Report *OBJCDERPTWork with Projects *WRKPRJRequest Inquiry *RQSINQ

Request Maintenance *RQSMNT

Getting Started

14

Over

Request Report *RQSRPT

Menu Access Command Options

Menu Option STRIM Command Valueu s e r g u i d e

view of Implementer FeaturesImplementer is the leading change management solution for the iSeries 400 available on the market today. It provides developers and IT managers with a feature-rich and easy to use environment that expedites development by managing and streamlining critical development processes.

software change management

version control software

developer productivity tool

distribution of software

project tracking

release control

release deployment

At the heart of Implementer is the Developers Workbench. From it, you can perform all the essential development tasks such as check in, check out, editing, compiling, promotion, and deployment, as well as resolve conflicts associated with parallel development. The result is that you spend more time doing what you enjoydeveloping software.

Development users and managers of the Implementer product have an intuitive interface in the Workbench.

Managers are able to view all requests and projects they are responsible for from the same Workbench. Implementer integrates all project information into the change management process. At the same time, application paths (either project-based or environment-based) ensure that object movement between environments occurs as defined, without requiring the constant

System Control Maintenance *SYSCTLMNT

Users *WRKUSR

User Report *USRRPT

Overview of Implementer Features

attention of the developer. In addition, integration of Implementer to other vendor products provides an open and complete interface to CASE and other vendor tools.

While making developers lives simpler, Implementer also provides features that IT managers demand for enterprise change management.

IntegrIntegrManag15

Implementers Secure Promotion Technology (SPT) ensures your promotion and deployment process cannot be compromised.

ation With ity er

Managers can assign, manage, and track issues using MKS Integrity Manager, MKSs workflow management and issue tracking solution for NT and UNIX. Using either the Windows GUI or Web interface, Integrity Managers powerful and customizable workflow capabilities extend control over software development processes, regardless of the platform. Plus you can have a single repository of all software changes made throughout the organization.

MKS is at the forefront of responding to new and evolving capabilities of the iSeries 400, including Integrated File System (IFS), Java, and WebSphere. Implementer provides complete change management for the IFS. For teams developing applications for the iSeries 400 using VisualAge for Java, WebSphere Studio, or other IDEs, the solution is MKS Source Integrity Enterprise Edition.

Source Integrity Enterprise Edition is MKSs client/server, configuration management solution for NT and UNIX, which integrates with VisualAge for Java and WebSphere Studio. When a project or change is complete, Source Integrity Enterprise Edition makes the files immediately available to Implementer for deployment.

Getting Started

16

Implementer brings all Java and WebSphere components, Windows and Web files, and native OS/400 objects into a single change package, ensuring synchronized promotion and deployment of all the components of your application.

The Wu s e r g u i d e

NOTE

Integrity Manager is a separately licensed component of the MKS Integrity Solution. All functionality referencing MKS Integrity Manager requires Integrity Manager be installed and configured as your issue tracking system within Implementer.

All functionality referencing DesignTracker and design requests requires DesignTracker be installed and configured as your issue tracking system within Implementer (DesignTracker is the default issue-tracking system), In addition, DesignTracker requires SupportCenter and ProjectMaster require be installed to complete the interface, unless noted otherwise. DesignTracker and ProjectMaster are automatically shipped with Implementer.

orkbench The Workbench and the Work with Objects function provide ease of use for anyone involved in the change management process. From the Workbench, you can initiate and manage any task relating to design requests or projects. Developers get information in the form most useful to them. Managers use the Workbench to view all the changes for design requests and/or projects that are their responsibility.

The features and benefits available from My Workbench allow you to:

Check out members/objects for a design request or project using any selection criteria.

Edit and perform development tasks using Source Edit Utility (SEU), Screen Design Aid (SDA), Report Layout Utility (RLU), Work with Member Programming Development Manager (WRKMBRPDM), and the command line.

Filter, change, and/or create design requests or projects to manage development.

Check out or promote objects from multiple environments simultaneously.

Filter development activity by user, design request, promotion request, project, and/or any other established criteria.

Directly access other related Implementer functions such as Work with Objects, Compile Requests, Move Requests, and Request Inquiry.


Compare and merge source code from multiple environments using integrated compare and merge.

Display member/object status and status history.

Enter time for projects and tasks or initiate updates. 17

The Clipboard provides an industry unique selection capability by allowing you to select work from multiple assignments (for example, requests, portions of related projects, and different developers).The Clipboard automatically sorts all selections, ensuring that related components are properly grouped together.

Implementer provides an open interface to add software items to the Clipboard and to process the items on the Clipboard using commands. These commands can provide significant benefit to those companies who need to control and automate the promotion of software items received from their software vendors (for example, Program Temporary Fixes (PTFs) and new releases). A list of the delivered software items is automatically built into the Clipboard using a command, then all of the items are added to a promotion request using another command.

The Workbench compile feature provides significant advantage to using the PDM compile. Developers can compile with the knowledge and assurance that all compilation requirements are automatically applied for each software item checked out to the Workbench. This includes library list, user ownership, authorities, and overrides.

Options defined in PDM can be run directly from the Workbench. The Workbench supports the use of both PDM and Implementer supplied substitution characters. This adds significant value to using the Workbench over PDM, for carrying out development and testing activities for software items in progress within the development cycle.

The controlled testing facility enables you to process an item that is on the Workbench list without having to change your library list.

The F13 Repeat option allows you to repeat an option through the Workbench list.

An additional filtering selection capability allows you to display only those items checked out either to a development or to a testing location. This has particular benefit to those developers and testers who work across multiple business applications.

Getting Started

18

Technology-based Features

Implementer provides support for Integrated Language Environment (ILE) software development. This feature includes all functions associated with the check out, creation, and promotion currently available for traditional OS/400 software development. The focus of MKS is to provide the developer with the necessary tools and u s e r g u i d e

management information needed to develop and modify ILE software easily in a development environment. On promotion to test and production environments, all of the technical requirements associated with ILE software are automatically managed.

Implementer provides support for Integrated File System (IFS) software development, on both the iSeries 400 and Windows NT Server. The change management of all objects in the IFS is fully supported. This feature includes all functions associated with check out, creation, and promotion currently available for traditional OS/400 software development (for example, RPG programs and display files). Within the IFS structure, Document Library Objects (DLOs) are supported. When checking out or promoting DLOs, all attributes and characteristics of DLOs are automatically retained.

Implementer provides support for your e-Business applications by offering Web-based check out and promotion deployment of IFS objects, using a browser interface. This integration is built on the existing proven framework of Implementer technology, which includes the latest support for IFS technology and the change management of client/server development. For more information, see the Implementer Multi-Platform Solutions Guide.

Implementer supports the retention of existing DB2/400 attributes attached to a file that is being replaced by a new version, in addition to promoting a new version of a file with additional DB2 attributes.

Implementer provides integrated front-end and back-office change management. In conjunction with the MKS Integrity Solution, this feature allows iSeries developers to manage GUI and Web development. The MKS Integrity Solution provides state-of-the-art content management and software management and collaboration in one built-for-eBusiness integrated package. MKS Source Integrity Enterprise Edition provides deployment capabilities for both the client and back-office parts of the applicationall with a single change request. This ensures that all the software components associated with a change request go into production at exactly the same time.

Source Integrity Enterprise Edition offers change management for Windows and UNIX platforms. You can log new issues and track progress within the development organization using MKS Integrity


Manager, a robust issue and change management tracking technology with Windows and Web-based interfaces. With this solution, a single issue ID can be used to manage a change across multiple platforms.

Change Control Featu

Implementer is feature rich with change control features, as described next.19

res Application PathsPredefining the application path through development environments simplifies the promotion process. You can define a default path, and specify whether certain users can override the path. This takes the guesswork out of check out and promotion, and provides controlled access to each environment.

You can define application paths:

by project, or by environment and user (which allows nearly unlimited flexibility)

for all environment relationships: development, QA, production, and remote systems

separately, for standard and emergency paths

Concurrent DevelopmentImplementer ensures by default that two people cannot accidentally check out the same source member. If you want to perform concurrent development, Implementer manages the development to ensure you track all changes in an orderly fashion. Concurrent development allows automatic merging of multiple versions of source members back into one source member. This replaces the need to wait for one user to complete work on a change before the next person begins to work on changes.

SecurityImplementer ensures selected users control changes to production, development, and test libraries. You can tailor Implementer to the level of control you want. You can designate, by user, the menu options that can be used, the environments (and functions within each environment) that can be used, and the defaults that can be overridden.

Controlled Object CharacteristicsImplementer ensures objects have the correct characteristics when you promote them into production or into controlled test libraries. The ownership, authority, and compile characteristics are controlled as well.

Getting Started

20

Object Version StampingImplementer provides for object version stamping of items under change management control. This feature is beneficial for easy auditing and the identification of deployed objects. Object version stamping can be implemented in association with or independent of another feature, Design u s e r g u i d e

Request stamping.

With object versioning, each object, lock record, and repository record is stamped with a version number at predetermined pre-defined stages within the development cycle. With DR stamping, each object is stamped with the design request number that the object was checked out for. When multiple locks exist with multiple DRs, the object is stamped with the primary DR associated with the initial lock. In addition, the actual description of the object is changed by updating the APAR ID attribute with the revision number, and the PTF Number attribute with the DR number. This can be viewed by using the Display Object Description (DSPOBJD) command.

Audit Trail and Status InformationA complete audit trail of every change made by your developers is maintained, and this audit trail can be maintained for as long as you need it. You can inquire or report on check out, promotion, and distribution activities. This allows complete management control over all of your development projects.

The various Work with functions and inquiries provide easy-to-use features that allow you to review factors such as: what projects are currently in process, who is working on that project, and what promotions occurred at any given time. In addition, several reports contain this information as well.

It is often difficult to identify what caused an error in the promotion cycle because OS/400 job logs typically contain too much detail rather than too little. Implementer minimizes the messages that are included in the job log so you can be certain that the first diagnostic or escape message listed in the job log is the actual cause of the error in the promotion cycle. This can speed up the identification of what really caused the problem.

Related ObjectsWhen you check out primary objects or promote changes, you can optionally include other objects affected by changes to these objects. For example, for any changed logical file you can include the related programs for check out or promotion.


Production Environment ProtectionWith Implementer, you do not compile directly into your production libraries. Implementer compiles source into a temporary work library, and moves the source and objects into the target (production) libraries only after all objects compile successfully. This methodology ensures that

DevelProduTools21

partial updating does not occur if a program in a series of programs on a promotion request fails to compile. Additionally, it prevents excessive downtime of your production libraries, because you do not have to wait for compiles to complete when updating production.

Implementer helps you to control unauthorized changes to production libraries, except for the developers or user profiles that have move capabilities. Users who have move capabilities for a set of libraries do not have the authority to affect the libraries they control outside Implementer. For example, a user that controls promotion (has promotion capabilities for that environment) to the production environment of Accounts Receivable has the authority to promote members/objects through Implementer menu options and commands. However, OS/400 security does not allow the same user to affect those objects or source members directly outside of Implementer (using for example, Copy Source File (CPYSRCF), Create Duplicate Object (CRTDUPOBJ), and Delete Program (DLTPGM)). Specific programs that adopt the authority to update the production libraries accomplish this during the move step.

oper ctivity

Numerous Implementer features increase your development productivity.

Personal EnvironmentsDevelopers can work in their own personal environments or development libraries, Implementer environments, or libraries they share with other developers.

Optional Check Out and Promotion MethodsImplementer offers two methods for processing check out and promotionthe one step method and a traditional method. Both methods provide access to the same features and produce the same results. However, the one step method allows you to perform check out and promotion using a fast path approach that saves time and effort, thereby minimizing the number of steps required in the functions. The traditional methods, which are more interactive, display more panels and require additional input for processing.

Getting Started

22

User-Defined OptionsIf you use PDM (Programming Development Manager), you can set up Implementer to use PDM user-defined options for check out and promotion. If you use PathFinder or ABSTRACT, you can check out members (and their related members/objects) through the PathFinder or u s e r g u i d e

ABSTRACT menus. You can continue development once you have checked out the member.

Lock IdentificationThe Implementer check out feature saves you time locating the user who last changed an object because each member/object has a lock attached by the user who performed the check out.

Automated Move ProcessThe developer saves time moving objects because it is no longer a manual process.

Customized Function KeysYou can customize the function keys of the Implementer menu panels and other important functions. Use the function keys to access your own systems (such as your own problem tracking system) directly from the Implementer Menu, or to add commonly used commands to a function key.

Implementer Across Multiple DivisionsSecurity in the product allows for secure and restricted use of a single copy of Implementer used concurrently by multiple divisions of an organization.

Special Commands by Environment Implementer has an extremely powerful and flexible special commands facility. Special commands provide the facility to issue external commands and programs at user-defined stages within the check out and promotion process, thus bringing significant flexibility and openness to the product. Special commands can be defined for environments, and can be automatically attached to all promotion requests targeting that environment.


Special Command Promotion Processor IEXCRQSDTL The most significant one command of the Implementer special commands runs a user-defined command against each software item in a promotion

DistribSoftw23

request that meets some user-defined selection criteria. The command analyzes the promotion request items, and for each item that meets the selection criteria (for example, object code, object name, promotion action) the user-defined command runs.

ution are

Implementer can automatically distribute changes from a development system to remote systems with no intervention required at your remote sites.

Promotion requests can be to any of the following:

single environment

modified list of environments

predefined group of environments

specific systems per individual requests

different systems on the same request

Implementer can accomplish the promotion in separate steps or automatically as a single step that can include compile, move, and distribute.

It is necessary to define the target environment (or environment group) before request creation. The environment group definition determines:

Source location.

Whether source or objects (or both) are only distributed to the remote (remote initiated move) or moved to a remote production library (host initiated move) or both.

Whether the environment requires compilation and on what system the compile takes place (local or remote).

The distribution information: distribution method (TCP/IP, SNADS, tape, NetView/DM, SDMCom, NetWrk/400, AnyNet/400, AS/NET), who initiates the moves, whether the host is updated, and whether to retain requests on the remote system.

You can define the environment definition during the initial set up of Implementer. As your requirements change, you can add new definitions or change existing definitions.

Getting Started

24

Test Tools Implementer supports your testing and quality assurance efforts.

Multiple Test EnvironmentsYou can define an unlimited number of environments as test environments.

Versiou s e r g u i d e

These environments can exist on either the local or the remote systems.

Tester-Controlled Test AreasFor organizations that have separate testing or quality assurance teams, Implementer allows you to control and manage your own testing areas. Testers can be the users who accept changes placed into their test environments. The testers can indicate what members/objects are ready for promotion either by selecting the project that is ready for promotion or by copying previous promotion requests. This eliminates the need for the tester to select or type in each member/object during the promotion process.

If necessary, the tester can easily reject the change from quality assurance and check the member/object back out to the specific developer and environment or library.

n Control Implementer provides several different version control features. Using version control, you can:

Perform multiple or concurrent check out of a member/object. Implementers concurrent development function sends a message to other users at the start of concurrent development. You can integrate changes back together using the merge capability.

Define multiple environments to support all versions of your software. You can implement complete (or partial) development paths (Development, Quality Assurance, User Acceptance, and Production) for each version of the software.

Roll back up to 99 versions of your software. Rollback is accomplished by archiving members/objects.

Compare all object versions in your environments. You can view all environments that currently contain a specific member/object to ensure they all contain the identical object.

Enter revision numbers for tracking the member/object version. Revision numbers display on many of the panels and on various reports.


Reporting Implementer provides both transaction reports and master file reports, which allow you to review your change management process.

Transaction ReportsThe following reports are useful to analyze change management activities:25

Activity Report

This report can be used to analyze the status of all projects and environments. You can enter more than a dozen options to control printed information. This report is available from the Implementer Menu using option 31.

Lock Report

This report lists source members and/or objects that are currently checked out. For object revisions and IFS management, the report includes revisions and IFS file name. You can print the report in six different orders with a variety of selection criteria. Lock history is available using the Activity Report function. This report is available from the Implementer Menu using option 32.

Concurrent Development Report

This report lists source members and objects with ongoing concurrent development. For IFS objects, the IFS file name prints for each IFS object that has an IFS name defined. You can print information on locks, resolution detail, and historical concurrent development. This report is available from the Implementer Menu using option 33.

Request Report

This report includes all information about the promotion request and automatically prints when a request is created. You can optionally print the report for all requests or a range of requests; and print requests for all users or a specific user. The report includes environment and member/object information, and includes revision numbers if versioning is enabled. The report also includes physical file optimization values, and related requests if a Implementer is enabled to maintain cross environment related objects. This report is available from the Implementer Menu using option 35.

On remote systems, the report is available from the Implementer Receiver Menu using option 1, Remote Requests. Select the request with option 6=Print.

Getting Started

26

Archive History Report

This report lists all objects and source members that are currently in the archive library. This report is available from the Implementer Menu using option 34.

Inquiru s e r g u i d e

Master File ReportsMaster file reports inform you of authorized users, libraries controlled by Implementer, the controls being implemented, and the predefined defaults for using Implementer. These reports include:

Environment Report

This report lists the summary-level or detailed information that you have defined within Implementer for an environment. Available information includes library defaults, host and remote library list information, environment groups, related environments, standard and emergency paths, defaults for create request, promotion, (model copy details for COOL:2E environments), and compile, distribution, and move steps. It includes setup defaults for COOL:2E, AS/SET, LANSA, and J.D. Edwards (if installed). Information about products and versions built from an environment, and product versions that define an environment as the default customer environment, are available. The detailed report can include object code information (both active and inactive object codes), object authorities, and object name rules (if defined). This report is available from the Implementer Menu using option 37.

User Profile Report

This report provides a summary of users, or a list of all information defined with Implementer for the user profiles selected. This report is available from the Implementer Menu using option 36.

Object Code Report

This report prints information about object codes. You can include all object codes or only active object codes. You can specify the sorting sequence of the report. For IFS objects, the IFS file extension prints for each object code that has a special characteristic of PCFILE when the object code and extension are not the same. This report is available from the Implementer Menu using option 38.

ies A number of inquires and Work with functions are provided to display information from the Implementer database. All inquiries are interactive programs.


Inquiries allow for flexible queries on promoted objects, promotion requests, currently checked out items, archives, and much more. In addition, all inquiries are full OS/400 panels. The inquiries include features such as filtering, positioning, and scrollable panels.

In addition to the inquiry functions listed next, there are many Work

ReleaPlann27

with functions that provide inquiry features.

My Workbench

My Workbench allows you to inquire about locked members/objects or work in process. You can inquire about every promotion or design request that a member/object is associated with. It allows you to view source, compare source, and view all current development and associated design requests (when more than one design request is associated with a lock). In addition, it allows direct access to SEU, WRKMBRPDM, SDA, and RLU.

Work with Objects

The Work with Objects function allows you to inquire on the migration path of objects. You can inquire about: all member/objects or IFS objects only (in alphabetical order), every promotion or design request that a member/object is associated with, archived sources and objects, and the lock history of a particular source member/object. You can optionally use Work with Objects to inquire about members/objects that were deleted through Implementer.

Request Inquiry

The Request Inquiry function displays all information about promotion requests. You can display any promotion request not purged from the Implementer database.

Job Log Inquiry

The Job Log Inquiry function displays job logs saved by promotion steps. Depending on the environment definition, you can retain job logs for all batch promotion steps, or just for failed steps.

Work with Projects

The Work with Projects function displays requests and lock history for a project.

se ing

Implementer supports the unique requirements of distributed information technology (IT) environments, including the independent software vendor (ISV) community. Software versioning and release facility features include:

Getting Started

28

Release Control

This feature provides additional management control and orientation by release name or number for managing production environments and reviewing release history. Users can continue working in a continuous development model or a fixed-version development

Third-VendoIntegru s e r g u i d e

model. Both models support PTFs for each version, which optimizes developer time and productivity.

Release Deployment

This optional feature allows you to manage, track, and deploy software changes by client, installed system, licensed product, version number, or PTF, as well as monitor current release status and shipments. Both internal and external clients have greater control and flexibility over installation of change packages, such as user-specified test libraries, scheduled installations, and control over object owners and authorities.

Party r ation

Implementer interfaces with third-party solutions to provide our customers the integration needed to address their business cases.

COOL:2E

COOL:2E is an application development tool for the iSeries 400 developed by Computer Associates. Implementer provides change control for COOL:2E developed applications and traditionally developed (3GL) applications, under as a separately licensed product. The primary difference between Implementer and COOL:2E licensed version is that with COOL:2E, programmers can check out from an option within Implementer.

AS/SET

Implementer manages AS/SET definitions and generated traditional objects. Support for AS/SET fields, files, audit trails, action subroutine definitions, program definitions, and data models are provided.

LANSA

Implementer manages LANSA objects such as files, fields, processes, and functions. With Implementer, you can check out and promote LANSA objects in a controlled fashion, distribute LANSA objects to remote locations, and archive LANSA objects during promotion and roll them back when necessary. Includes support for LANSAs web interface.


J.D. Edwards

Implementer supports J.D. Edwards special objects and traditional objects for any J.D. Edwards 8.X versions and earlier. With I

implementer user guide

Documents