App Builder Enterprise Migration

BluePhoenix AppBuilder 2.0.3.
Enterprise Migration Guide
BluePhoenix AppBuilder 2.0.3.1 Enterprise Migration Guide September, 2002 Corporate Headquarters BluePhoenix Solutions Vlierwerf 7B 4704 SB Roosendaal The Netherlands +31 (0) 165 399 401 +31 (0) 165 396 308 fax www.bluephoenixsolutions.nl USA Headquarters BluePhoenix Solutions USA, Inc. 8000 Regency Parkway Cary, NC 27511 United States +1 919.380.5100 +1 919.380.5111 fax www.bluephoenixsolutions.com
1992-2002 BluePhoenix Solutions All rights reserved. BluePhoenix is a trademark of BluePhoenix Solutions. All other product and company names mentioned herein are for identification purposes only and are the property of, and may be trademarks of, their respective owners. Portions of this product may be covered by U.S. Patent Numbers 5,495,222 and 5,495,610 and various other non-U.S. patents. The software supplied with this document is the property of BluePhoenix Solutions, and is furnished under a license agreement. Neither the software nor this document may be copied or transferred by any means, electronic or mechanical, except as provided in the licensing agreement. BluePhoenix Solutions has made every effort to ensure that the information contained in this document is accurate; however, there are no representations or warranties regarding this information, including warranties of merchantability or fitness for a particular purpose. BluePhoenix Solutions assumes no responsibility for errors or omissions that may occur in this document. The information in this document is subject to change without prior notice and does not represent a commitment by BluePhoenix Solutions or its representatives.
TABLE OF CONTENTS
Table of Contents
AppBuilder 2.0.3.1 Enterprise Migration Guide
Migrating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Source Environment Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Creating the Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Selecting Objects for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Exporting the Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Target Environment Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Creating the Target for the Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Analyzing the Impact of the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Importing the Migration Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Migrating Run-time Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Source Environment Processing
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Preparing for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Accessing the Enterprise Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Creating the Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Selecting Objects for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Creating Relations From the Migration Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Migrating a Security Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 Creating Relations from the Root Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 Exporting the Migration Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Target Environment Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Creating the Target for Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Analyzing the Impact of Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Importing the Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 After You Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Automated Migration Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Before You Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Automated Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Overnight Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Status Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Using the Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Preparing for Automatic Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Sample Automated Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 After You Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Migration Actions
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Migration Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Add Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Add Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7 Add Relation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10 Add Text to Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Add Text to Relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Analyzing the Migration Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 Approve Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16 Automate Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17 Migrating Without Migration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 Clean-up Migration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20 Copy Migration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20 Count Migration Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21 Delete Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21 Delete Relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Table of Contents
Detect Objects to be Rebuilt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22 Export Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23 Selective Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23 Generate a Delta Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30 Generate a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31 Import Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32 List Migration Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33 Using Filters to List Migration Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36 List Relations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39 Maintain Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39 Toggle Import Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40 Batch Toggle Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40 View Results of Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
Migrating and Importing Run-time Applications . . . . . . . . . . . . . . . . . . . 6-1

COPYAPP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 Migrating and Exporting Using COPYAPP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 Export Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Exporting the Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Package Export Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Installing the COPYAPP Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Installing Run-time Package Import Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 Importing the Run-time Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Table of Contents
Installing the Import Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8 Package Installation Status Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9 Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13 Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15 Link the Import Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17 Update Entity and View Definition (VIDTEXT) File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17 Update the Rule Relationship and Rule Source Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18 Bind and Grant the DB2 Plans and Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18 PSB and ACB Application Specification Block (IMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18 Installing the Target System on CICS and IMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19 Step 1. Generate the Rule/Transaction Relationship Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20 Step 2. Define the Target System for CICS and IMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21 Modifying the Data Set Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22 Rollback Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22 Backing Up the Existing Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22 Restoring the Backed-up Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23 Updating Preparation Timestamps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
Setting Up the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Variables in the @MIGENVn INI file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 Automate Migration (MIGRATE) Action Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Migration Status Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1

Migration Status Value Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1
Migration Tables and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Migration Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 ENT_LOGKEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 E_MIGRTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2 R_MIGXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 REL_LOGKEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 Migration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4 Header and Row Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4 File Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Migration Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1

Using Migration Facility Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1 System Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1 User Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-3 Sample Exit Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-5 CLIST Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-6
Table of Contents
Migration Processing Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Audit Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Repository Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D-1 D-1 D-2 D-2 D-2
Freeway Migrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3 Object Attribute Listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Index
....................................................................................... i
Table of Contents
CHAPTER
MIGRATING APPLICATIONS
AppBuilder 2.0.3.1 Enterprise Administration Guide
The Enterprise Migration Facility allows you to: Migrate repository objects Migrate run-time applications The Enterprise Migration Facility copies repository objects from a source storage area to a target storage area, as shown in Figure 1-1. In any copy operation, the source is the place from which data is copied, and the target is the place to which the data is copied.
Figure 1-1 Basic Migration Processing
Typically, the Migration Facility is used to copy or upgrade an application, for example, from a development repository to a testing repository. The Migration Facility supports software promotion by: Copying applications between repositories Copying applications between repository versions Backing up applications to DASD or magnetic tape
1-1
Source Environment Steps
The migration process is described in the steps listed in Table 1-1.

Table 1-1 Source Environment Steps Source Environment Steps 1Creating the Migration Package 2Selecting Objects for Migration 3Exporting the Migration Package
Table 1-2
Target Environment Steps
Target Environment Steps 1Creating the Target for the Migration Package 2Analyzing the Impact of the Migration 3Importing the Migration Package
The following sections lists the action you use, a brief description, the procedures that make up the step, and the end result or deliverable.

Once you are logged on to the source repository, you must perform three steps in the source environment. Figure 1-2 illustrates the steps required to create and export a migration package.
Figure 1-2 Source environment processing
1-2
Migrating Applications
Creating the Migration Package

Use the following entities to create the migration package using the actions listed in each entry.
Action
Add Entity (ADDE) on the AppBuilder Host Workbench.
Description
The Add Entity action is the create action common to all entity types. The created entity is called the migration entity, and all actions performed during migration center around it. The Add Entity action generates a blank Add an Entity panel that contains several attributes. You define some attribute values and the system generates others. Migration attributes include: Name (30-character limit) System-generated system ID (six-character limit) to identify the entity Optional description attribute (30-character limit) to communicate the purpose of a migration entity to other project users DSN that can be either user- or system-generated, based on site-specific requirements System-generated migration state to identify the current state of the migration entity Note
The repository administrator(s) should establish naming standards for migration entities that are consistent with the naming standards established for development project entities.
Audit attributes have system-generated values that show who created or modified the object, as well as the time and place (enterprise or workstation) it was created or last modified. To create a migration package: 1. 2. 3. 4. 5. Choose the repository, version, and project from which you are migrating. Type in ADDE (Add Entity) to open the Add an Entity panel. Specify values for all user-definable attributes. Add text and keywords to further define the migration package. Save the entity.
Deliverable The migration entity is added to the source enterprise repository.
Selecting Objects for Migration

Use the following action to select objects for the migration package.
1-3
Action
Add Relation (ADDR) on the AppBuilder Enterprise Workbench.
Description
The Add Relation action creates a relationship between a migration entity and each root entity that you want to migrate. A relationship is any association between two entities. A migration entity is not complete until you create a relationship between that migration entity and one or more root entities. The number and kind of entities or hierarchies determine the scope of your migration package. You may optionally package a single entity or a group of entities at the function, process, or rule level. When you create a relationship between a migration entity and a root entity, you select whether you want to package the: Entity only One level below the root The Prepare hierarchy The Entity hierarchy Drawing To create a relationship: 1. 2. 3. 4. List the entities or entity hierarchies that you want to export. Use the add relation action to add a relationship between the migration entity and each entity that you want to migrate. Specify values for the user-definable attributes. Save the relation.
Deliverable The relationships established between the migration entity and the root entities are added to the source enterprise repository.
Exporting the Migration Package

Use the following action to export the migration package.
Action
Export the migration package (EXPORT) on the AppBuilder Enterprise Workbench.
1-4
Description
Export copies the generated migration package from the repository to tables, files, and sequential Data sets on DASD. You can choose the object parts that you want to export by including or excluding text, source, or keywords on the Export Options panel. The process options are useful if you are copying for the purpose of updating objects in a target environment. To export the generated migration package: 1. 2. 3. 4. 5. Run the export action for the selected migration entity. Accept or change the default export options to reflect the purpose of the migration. Check the migration state on the migration Maintain an Entity panel. If the migration state is Export Failed, find out why the job failed, correct the problem, and run the job again. When the migration state is Export Successful, use the List Migration Contents (LISTMIG) action to list the exported objects.
Deliverable Data from the repository is exported to external tables and files, and the export job completes with an Export Successful migration state.

After you have successfully completed the export migration package action, detach from the source repository and attach to the target repository. Perform the following three required target environment steps. Creating the Target for the Migration Package Analyzing the Impact of the Migration Importing the Migration Package
Creating the Target for the Migration Package

Use the following entities to create the target for the migration package using the actions listed in each entry.
Action
Add Entity (ADDE) action on the AppBuilder Enterprise Workbench.
1-5
Description
The Add Entity action opens a blank Add an Entity panel identical to the one generated in the source environment. However, the migration entity you create in the target environment becomes the target for the migration process. The information imported is linked to this entity and all actions revolve around it. The Add an Entity panel has 20 attributes. You define some attribute values, while the system generates others. The migration attributes are the same as the ones for the migration entity you created in the source environment. However, the DSN must be the same as the data set name assigned to the source migration entity. Note
The repository administrator(s) should establish naming standards for migration entities that are consistent with the naming standards established for development project entities.
Audit attributes have system-generated values that show who created or modified the object, as well as the time and place (enterprise or workstation) when and where it was created or last modified. To create a generated entity duplicate: 1. 2. 3. 4. 5. 6. Choose the repository, version, and project to which you are migrating. Use the add entity action to generate the blank Add an Entity panel. Specify values for all user-definable attributes. Enter the DSN given to the source migration entity. Add text and keywords to further define the migration package. Save the entity.
Deliverable The migration entity is added to the target enterprise repository.
Analyzing the Impact of the Migration

Use the following entities to analyze the impact for the migration package.
Action
Analyze Migration Impact (ANALYZE) action on the AppBuilder Enterprise Workbench.
Description
The Analyze action compares objects in a migration package with those in a target environment by taking the unstructured sequential object data from the exported migration files, copying it to temporary files and tables, and comparing objects one at a time. It reads each loaded object in a migration package and searches the target environment to find an object with the same key value. Then it tags each object in a migration package with one of the following migration status values:
1-6
Unchanged Import will Create Import will Update Import will Delete Unresolvable Collision You use these status values to decide whether or not to import an object. In addition to the migration status values, items that need to be prepared again during rebuild processing are noted. The Import action copies this information to the target repository. To use the Analyze action: 1. 2. 3. 4. 5. Run the Analyze action for a selected migration entity. Accept or change the default analyze options to reflect the purpose of the migration. Check the migration state on the migration Maintain Entity panel or Browse Entity panel. If the state is Analyze Failed, find out why the job failed, correct the problem, and run the job again. When the state is Analyze Successful, check your results by using the list migration contents (LISTMIG) action.
Deliverable The migration files on DASD are copied to temporary tables and files.
Importing the Migration Package

Use the following action to import the migration package.
Action
Import the migration package (IMPORT) on the AppBuilder Enterprise Workbench
Description
The Import action copies the migration data from the updated internal control table to the target environment. The migration entity must have an Analyze Successful migration state value before you can run the Import action. The output of Analyze processing is the input for import processing. Analyze processing creates temporary tables and files and tags each object in the migration package with a migration status value. Import processing reads the migration status values to know which items to create, update, or delete. You can choose the object parts that you want to import by including or excluding text, source, keywords, creates, updates, and deletes on the Import Options panel.
1-7
Migrating Run-time Applications
To import a migration package: 1. 2. 3. 4. 5. Run the Import action. Accept or change the default import options to reflect the purpose of the migration. Check the migration state on the migration Maintain an Entity panel. If the state is Import Failed, find out why the job failed, correct the problem, and run the job again. Use the List Migration Contents (LISTMIG) action to see the return codes for each object. When the state is Import Successful, check your results by using the List Migration Contents (LISTMIG) action.
Deliverable Data from the temporary files and tables is imported into the repository and the import job completes with an Import Successful migration status.
Migrating Run-time Applications

Once an application has been built and put into production, you can use the Enterprise Migration Facility to copy the applications executable objects from one location to another. Migration of a runtime application involves two steps: 1. Use the COPYAPP action to extract and export all or parts of run-time applications. The COPYAPP action extracts only the executable data needed to run in the target location. You can export multiple AppBuilder application environments (BATCH, CICS and IMS) at the same time. 2. Import the run-time applications and install them in the target environment. When the package has been installed, the imported application will have: Linked and edited all rules, reports, sets, and user components Bound and granted the DB2 application packages and/or plans Updated the run-time AppBuilder processing files Generated PSBs and ACBs (IMS only) Re-built the rule/transaction relationship tables and notified the target system (CICS/IMS) of updates to the application program
1-8
CHAPTER
SOURCE ENVIRONMENT PROCESSING
Source environment processing consists of the actions shown in Figure 2-1, performed in sequence. The steps required are described in detail in the following sections: Preparing for Migration Creating the Migration Package Selecting Objects for Migration Exporting the Migration Package
Figure 2-1 Source Environment Processing
univers
2-1
Preparing for Migration

Before you begin the migration process, be sure of the following: You are authorized to perform migration actions in the source and target environments you have chosen. Check with your repository administrator if you are not sure whether you are authorized to migrate. Your application has been prepared and can execute in the source environment. You meet the exit and entrance criteria of the source and target environments, respectively. You have enough time to complete the migration. The target environment has enough space and has been properly prepared. The INI variables on both the source and target repositories are set to the values you need. Use the View AppBuilder INI Files (INIDISP) action to check the values of your migration control environment variables. Contact your administrator if you need the INI variables changed. The administrator has set up the repository-to-repository relationship. The E_REPOSIT and R_REPREP DB2 tables define these relationships. E_REPOSIT defines the target repository and R_REPREP sets up which source version is allowed to migrate to which target version. Note
Check with your repository administrator for other requirements before migrating.
Accessing the Enterprise Repository

When you are ready to migrate, access the enterprise repository by following these steps: 1. 2. Following your site procedure, log on to the Time Sharing Option (TSO) system. On the command line of the Interactive Structured Programming Facility/Program Development Facility (ISPF/PDF) Primary Option menu, type the letter used to access the enterprise repository and press Enter. The installation team specifies this value during your AppBuilder installation; it is H in Figure 2-2. The System Options menu is then displayed.
2-2
Figure 2-2
ISPF/PDF Primary Option menu
Note 3.
The ISPF/PDF Primary Option menu shown in Figure 2-2 is a sample and includes site-specific options (for example, FORTE and PANVALET). The equivalent panel at your site may look different.
To access the enterprise repository, select option 1, ER, from the System Options menu and press Enter. See Figure 2-3.
System Options menu
Figure 2-3
Note
The number of options available depends on which options are installed.
2-3
The system displays the AppBuilder Host Workbench panel (Figure 2-4), from which you begin migration processing.
Figure 2-4 AppBuilder Host Workbench Panel
You can use the display entities (ENTITY) action at any time to display this panel.

The migration entity and its roots comprise the migration package, and all actions performed during migration processing center around it. The add entity (ADDE) action creates an instance of a migration entity in the enterprise repository (Figure 2-5).
2-4
Figure 2-5
Creating the migration package
univers
This section describes how to add a migration entity. 1. 2. Navigate to the AppBuilder Host Workbench panel of the repository, version, and project from which you want to migrate. (To change projects, use the change projects (PROJECTS) action.) Type ADDE on the Migration action line (Figure 2-6) and press Enter.
Creating the migration entity
Figure 2-6
ADDE
3.
On the blank Add an Entity detail panel, type the name and the description (Figure 2-7).
2-5
Figure 2-7
Naming the migration entity

AppBuilder Host Workbench
Repository: SUNRISE Action ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ADDE____ ________ ________ ________ ________
V: 1
Project: DEV
Level: 1
Entity Field File Form FSDM Scheme FSDM Value Function Help Text Identifier Key Location Logical Process Machine Migration Organization Physical Event Process Rebuild Package
4.
The name is an alphanumeric string up to 30 single-byte or 14 double-byte characters. The description can be up to 30 characters of text that explains the purpose of the migration to other Migration Facility users. Although a description is optional, it is highly recommended because it makes the migration entity much more useful to other project members.
5.
You can do one of three things with the Data Set Prefix field: Leave the field blank. The system generates the value when you save the entity. Type the prefix of the data set to which you are exporting your migration information. The repository administrators should establish naming standards for data sets. Type over a displayed value to bypass creating a migration data set. Migrating without writing migration files is faster and is appropriate when you will not be migrating to another target. See Migrating Without Migration Files on page 5-17 for more information. The prefix can be an alphanumeric string up to 17 characters. The system generates the remainder of the 44-character data set name, adhering to mainframe naming conventions.
6.
When you have finished, tab to the command line and type SAVE. Press Enter. Notice that after you save, the title changes from Add an Entity to Maintain an Entity, the systemdefined attributes are filled in, and you see a message that says User modifications to object have been saved. See Figure 2-8. After an entity is saved, you can change the user-defined attributes by overtyping values and then typing SAVE on the command line again.
2-6
Figure 2-8
Maintaining the migration entity

Maintain an Entity More: + Level: 3
Repository: SUNRISE Migration Attributes: Name . . . . . . . System Id . . . . . Description . . . . Data Set Prefix . . Migration State . .
V: 1
Project: DEV
. . . . .
. . . . .
. . . . .
. . . . .
. : . . :
DMC_VER2______________________ AA4FNR MIGRATE DMC_APP_1 FROM V1 TO V2 SEEROUT.M00016NR_ 14 N/A
Audit Attributes: Date Created . . . . . . . : 95/05/12 Time Created . . . . . . . : 09:13 Created by . . . . . . . . : SS0222 Date Maintained . . . . . . : 95/10/02 Time Maintained . . . . . . : 09:13 Maintained by . . . . . . . : SS0222 Project . . . . . . . . . . : DEV Change # . . . . . . . . . : 0001 Owner Id . . . . . . . . . : SS0222 Local Maintenance Date . . : 95/10/02 User modifications to object have been Saved. Command ===> _______________________________________________________________
Note
If the Autosave option is turned on, the information you enter is saved as soon as you press F3 to return to the previous level. A User modifications to object have been saved message appears at the bottom of the panel. However, if you request an action that takes you to a subsequent level, you may lose your changes when exiting from that level. Manually save your changes in this case to prevent losing them.
7.
Type TXE on the command line to add text to the entity. The text describes the purpose and scope of the migration package to other Migration Facility users (Figure 2-8 shows sample text). You should do this step, although it is optional. Press F3 to return to the Maintain an Entity panel.
Adding text to the migration entity
Figure 2-9
--------- SS0222.SS0196.MOD.STK ------------------------------ COLUMNS 001 072 TEXT for Migration Name . . . . . . . : DMC_VER2 Version . . . . . : 1 ****** ***************************** TOP OF DATA ****************************** 000001 USED TO MIGRATE DMC_APP1 (PAYROLL) FROM VERSION 1 TO VERSION 2 IN SUNRISE. ****** **************************** BOTTOM OF DATA ****************************
8.
Type K on the command line to add keywords to the entity. Keywords describe the purpose and scope of the migration package to other Migration Facility users. Figure 2-10 shows sample keywords. We recommend that you do this step, although it is optional. Press F3 to return to the Maintain an Entity panel.
Separate each keyword with a space and do not exceed 240 characters for all the keywords for a single entity.
Note
2-7
Figure 2-10
Adding keywords to the entity
--------- SS0222.SS0196.MOD.STK ------------------------------ COLUMNS 001 072 KEYWORDS for Migration Name . . . . . . . : DMC_VER2 Version . . . . . : 1 ****** 000001 000002 000003 000004 000005 000006 ****** ***************************** TOP OF DATA ****************************** MIGRATION DMC VER2 SS0222 DMC_CUSTOMER_MAINTENANCE DMC_CUSTOMER_RESERVATION **************************** BOTTOM OF DATA ****************************
9.
Press F3 to exit the Maintain an Entity panel. You can use the maintain entity (ME) action to display this panel if you want to check or change the entity attribute values.
10. Record the name of this entity, because you will use it throughout source environment processing. The migration entity is not complete until you add one or more root entities to it. At this stage, you can only list existing entities by using the list entity (LE) action, maintain entities by using the maintain entity (ME) action, or delete entities using the delete entity (DE) action. To continue with the migration process, you must now define the scope of objects to be included in the migration package by adding relations, which is described in the following section.

You now have to select objects to be included in the migration package. The Add Relation (ADDR) action defines the objects and their scope to be included in the migration package by creating relations between the migration entity and the objects you want to migrate. See Figure 2-11. The following sections describe the process: Creating Relations From the Migration Entity Migrating a Security Model Creating Relations from the Root Entity
2-8
Figure 2-11
Selecting objects for migration
univers
You can migrate objects within the Development Information Model or the Administration Information Model. The Development Information Model is composed of entity and relation types used for business system development. The Administration Information Model is composed of entity and relation types used for enterprise repository security and configuration. This section describes how to add objects to the migration package. You usually select objects for migration processing by creating relations from the migration package entity, but you can also add relations from the root entity to the migration package. You can create a relation between a migration package entity and root entities (or from the root entity to other entities) only if the entities are stored in the same version. That is, a migration package or root entity in version 2 can have a relation only to entities that are also in version 2. The next section describes creating relations from the migration package entity. The procedure for adding relations from the root entity is almost the same. The second section describes the differences between the two procedures.
Creating Relations From the Migration Entity

1. Record the name of each root entity that you want to add to the migration package. (You can use the update user profile (UPROF) action to change your profile so you can specify entities by their system ID instead of their name.)
2-9
2. 3.
On the AppBuilder Host Workbench panel, type LE on the Migration action line and press Enter to navigate to the AppBuilder List Facility for Entity Migration panel. Type ADDR on the action line of your migration entity (Figure 2-12) and press Enter.
Creating the relation from the migration entity
List Facility for Entity Migration Repository: SUNRISE V: 1 Project: DEV Level: 2
Figure 2-12
Action ________ ADDR____ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________
Name DC_MIG01 DMC_VER2 GETCAPPS GETVIREQ GET524S JXL_ADM_OBJECT_ALL LAI_PFDEFAULT MIG_DNAGE MIG_DNA0000 MIG_FDFAULT MIG_FGBL01 MIG_FREPORT MIG_NRV1TO_NRV2 MIG_QCLBWIND MIG_TCFLVIEW
System Id AA37NR AA4FNR AAAYNR AAAWNR AAAXNR JXLADMO AAAMNR AA1WNR AA1NNR AAABNR AA1MNR AAANNR AA3ONR AA24NR AA1YNR
On the Action Information pop-up panel, select a relation type from the list of available relation types (Figure 2-20), and press Enter.
Figure 2-13 Choosing the relation type
Information ------------------------More: + Add a Relation 1 Name Migration DMC_VER2______________________ 32 1. 2. 3. 4. 5. 6. 7. 8. Has-Root Has-Root Has-Root Has-Root Has-Root Has-Root Has-Root Has-Root Application Config. Attribute Bitmap Business Object Cell Collection Column Component | | | | | | | | | | | | | | | -------------------------- Action | | Action . . . . . . . . . . . : | Use . . . . . . . . . . . . . . | Entity Type . . . . . . . . . : | Name/System Id . . . . . . . . | | Relation Type . . . . . . . . . | | | | | | | |
Figure 2-14 provides a list of all the relation types available:
2-10
Figure 2-14
Relation Types Has-Root Identifier Has-Root Key Has-Root Location Has-Root Logical Process Has-Root Machine Has-Root Organization Has-Root Physical Event Has-Root Process Has-Root Project Is-A-Root-Of Rebuild Package Has-Root Relationship Has-Root Report Has-Root Rule Has-Root Section Has-Root Server Has-Root Set Has-Root State Has-Root Table Has-Root Transition Has-Root User Has-Root Value Has-Root View Has-Root Window
Has-Root Application Config. Has-Root Attribute Has-Root Bitmap Has-Root Business Object Has-Root Cell Has-Root Collection Has-Root Column Has-Root Component Has-Root Config. Unit Has-Root Current System Has-Root Data Store Has-Root Data Type Has-Root Database Has-Root Drawing Has-Root Entity Has-Root Event Has-Root Field Has-Root File Has-Root Form Has-Root Function Has-Root FSDM Scheme Has-Root FSDM Value Has-Root Group Profiles Group
Note
The STATIC_LINK_DEFAULT configuration unit is provided as part of the default repository to maintain a relationship indicating that a rule should be statically linked automatically during the rebuild process.
Notice that you can migrate the STATIC_LINK_DEFAULT configuration unit if you add it to a migration package. If there is a relationship between a rule and this configuration unit, the Rebuild Facility will statically link it. Migrating the STATIC_LINK_DEFAULT configuration unit will bring over the relationships to set up the objects in the target repository for static linking.
Migrating a Security Model

Follow these steps to migrate a security model: 1. 2. In the ADM project, create a migration entity. Under Group, select the group you want to migrate. Group is the root of the migration instead of the project because group is the root of the security model (the relationship is Group-has-Project and Group-has-User). 3. 4. Run the ADDR action against the group to be migrated. One of the options under ADDR is: 3. Is-a-Root-of Migration Run Export to migrate the security model.
2-11
5. 6.
In the target environments ADM project, import the security model. The system generates a blank Add a Relation panel with the Migration Name field filled in. In the Has-Root <entity type> Name field, type the name of the root entity that you want to add to the migration package (Figure 2-15).
Adding a relation to the root entity
Add a Relation Repository: SUNRISE V: 1 Project: DEV More: Level: 3 +
Figure 2-15
Migration Name . . . . . . . . . . . . DMC_VER2______________________ Has-Root Process Name . . . . . . . . . . . . Relationship Attributes: Scope type . . . . . . . . .
Type the name of the root entity to be added Select a scope type
VER2_DMC_APP_1_________________ 2
1. 2. 3. 4. 5.
Entity Only Entity Hierarchy Prepare Hierarchy One Level Drawing
Audit Attributes: Date Created . . . . . . . : Time Created . . . . . . . : Created by . . . . . . . . : Date Maintained . . . . . . : Command ===> _______________________________________________________________
7.
In the Scope field, select from the list of available migration scopes. Migration scope determines exactly what you will migrate. That is, you define whether the migration package includes only the root entity, every object in the hierarchy subordinate to the root entity, objects needed to prepare the root entity on the host, those objects in the hierarchy one level below the root entity, or drawings. You can define a different migration scope for each entity you include in the migration package. The following scope types are available:
Figure 2-16 Action Entity Only
Scope Types Description Only the entity and its parts (text, keywords, and source)and none of its child objectsare part of the migration package. This scope is useful for moving an object when the scope of changes are self-contained. The entityas well as all of its child objectsare part of the migration package. This scope is useful for copying new branches of an application. The entityand the child objects needed to prepare itare part of the migration package. This scope is useful for copying fixes to an existing application. The entityas well as objects one level below itare part of the migration package. Exporting one level below the entity hierarchy is useful for attaching new branches of an application to an existing application without moving the entire original application. A drawing and objects contained in the drawing are included in the package. It is useful to export drawings (such as window flow diagrams) when you are migrating only parts of an application, and it is a powerful way to migrate selectively.
Entity Hierarchy Prepare Hierarchy
One Level
Drawing
See Add Relation on page 5-7 for more information on migration scopes. Throughout migration processing, you can exclude items from the migration package, using the export options (including selective export), import options, and the toggle (TOGGLE) action. These features give you a high degree of control over the content of your import. 8. Tab to the command line, type SAVE, and press Enter.
2-12
After you save the relation, the panel heading changes from Add a Relation to Maintain a Relation, and the system fills in the values for the audit attributes. A message that reads User modifications to object have been saved appears in the command area (Figure 2-17).
Figure 2-17 Saving the relation
Maintain a Relation Repository: SUNRISE V: 1 Project: DEV More: + Level: 3
Migration Name . . . . . . . . . . . . DMC_VER2______________________ Has-Root Process Name . . . . . . . . . . . . VER2_DMC_APP_1_________________ Relationship Attributes: Scope type . . . . . . . . . 2
Entity Hierarchy
Audit Attributes: Date Created . . . . . . . : 95/05/12 Time Created . . . . . . . : 09:26 Created by . . . . . . . . : SS0222 Date Maintained . . . . . . : 95/10/02 Time Maintained . . . . . . : 09:26 Maintained by . . . . . . . : SS0222 Change # . . . . . . . . . : 0001 Local Maintenance Date . . : 95/10/02 User modifications to object have been Saved. Command ===> _______________________________________________________________
After a relation is saved, you can change the user-defined attributes by overtyping values and then typing SAVE on the command line again. 9. To add text to the relation, type TXR on the action line and press Enter. Use the text to describe the purpose of the relation to other project users. You should do this step, although it is optional. See Figure 2-18.
Adding text to the relation
Figure 2-18
--------- SS0222.SS0196.MOD.STK ------------------------------ COLUMNS 001 072 TEXT for Relations Name . . . . . . . : VER2_DMC_AP_1 Version . . . . . : 1 ****** 000001 000002 000003 ****** ***************************** TOP OF DATA ****************************** DMC_VER2 HAS ROOT PROCESS VER2_DMC_APP_1. SCOPE IS ENTITY HIERARCHY BECAUSE THE APPLICATION IS BEING MIGRATED TO VERSION 2 FOR THE FIRST TIME. **************************** BOTTOM OF DATA ****************************
To add another root entity of the same type to the migration package from the active Maintain a Relation panel, tab to the Has-Root <entity type> Name field, and overtype the first entity name with the next entity name. Then select the migration scope, type SAVE, and press Enter. The system displays the message, User modifications to object have been saved. To add a root entity of another entity type, press F3 to exit the active panel. Then repeat steps 2 through 7, until you have included all the objects you want to migrate. Press F3 to exit the Maintain a Relation panel. You can use the maintain relation (MR) action to display this panel if you want to check or change the relation attribute values. Use the list relations (LR) action to make sure you have included all the root entities you want in the migration package. Use the delete relation (DR) action to delete any entities that should not be in the migration package.
2-13
Once you determine that the migration package is complete, you are ready to export it. A later section, Exporting the Migration Package on page 2-17, describes the export (EXPORT) action in detail.
Creating Relations from the Root Entity

Although the more common way to select objects for the migration object is by creating relations from the migration package entity, you can also do so by creating relations from the root entity. The procedure is almost the same as the one just described for creating relations from the migration package entity. The differences between the two procedures are described below. 1. 2. 3. Record the name of each root entity that you want to add to the migration package. Also record the name of your migration entity. On the AppBuilder Host Workbench panel, type LE on the action line of the entity type you want to add to navigate to the AppBuilder List Facility for Entity <entity type> panel. Type ADDR on the action line that corresponds to the object that you want to include in the migration package (Figure 2-19). Press Enter.
Creating the relation from the root entity
List Facility for Entity Function Repository: SUNRISE V: 1 Project: DEV Level: 2
Figure 2-19
Action ________ ________ ________ ________ ADDR____ ________ ________ ________ ________ ________ ________ ________ ________
Name DBA_TEST531A_WFD_FUNCTION1 DVT_FUNCTION_ALL_EXECENV DXT_FUNCTION_ALL_EXECENV DMC_FUNC1 DMC_FUNC2 DMC_FUNC3 F_RUNM_01 F_WCP_001 MIG_FUNC4 MREP_FUNCTION_01 MREP_FUNCTION_02 MREP_FUNCTION_03 OVT_FUNCTION_ALL_EXECENV
System Id ZAAJLTO DVTFAEXE DXTFAEXE ZAMYF9N ZANWA9N ZANWO9N ZAAC57Z ZAAAB8D ZAAEXSU AF5LSR AF5MSR AF5NSR OVTFAEXE
Command ===> _______________________________________________________________
4.
Select Is-A-Root-Of Migration from the list of available relation types on the Action Information pop-up panel (Figure 2-20). Press Enter.
Choosing the relation type from the root entity
Figure 2-20
-------------------------- Action Information ------------------------| More: + | | Action . . . . . . . . . . . : Add a Relation | | Use . . . . . . . . . . . . . . 1 Name | | Entity Type . . . . . . . . . : Function | | Name/System Id . . . . . . . . DMC_FUNC2_____________________ | | | | Relation Type . . . . . . . . . 7_ 1. Has Bitmap | | 2. Is-Encap'ed-By Config. Unit | | 3. Replaces Current System | | 4. Intersects-With Entity | | 5. Uses Language | | 6. Is-Carried-Out-At Location | | 7. Is-A-Root-Of Migration | | | | Command ===> _______________________________________________________ | | F13=Actions F14=Entity F15=Collapse F16=Expand F17=Projects | | F18=SaveAs F19=Refresh F20=All F21=Print F22=Clear | -----------------------------------------------------------------------
You can scroll down to see more relation types, as shown in Figure 2-21.
2-14
Figure 2-21
Additional relation types
-------------------------- Action Information ------------------------| More: | | Action . . . . . . . . . . . : Add a Relation | | 9. Refines-Into Process | | 10. Is-A-Root-Of Rebuild Package | | | | Version . . . . . . . . . . . : 1 | | Prompt for Input. . . . . . . . 1 Yes | | |
5.
The system generates a blank Add a Relation panel with the Has-Root <entity type> Name field filled in. Type the name of your migration entity in the Migration Name field (Figure 2-22).
Naming the migration entity
Add a Relation Repository: SUNRISE V: 1 Project: DEV More: Level: 3 +
Figure 2-22
Type the name of the existing migration entity
Migration Name . . . . . . . . . . . . DMC_VER2______________________ Has-Root Process Name . . . . . . . . . . . . DMC_FUNC2_____________________ Relationship Attributes: Scope type . . . . . . . . . 2 1. 2. 3. 4. 5. Entity Only Entity Hierarchy Prepare Hierarchy One Level Drawing
Select the scope type
The name you type in the Migration Name field must match the name of your existing migration entity. 6. Tab to the Scope field, and select the migration scope. See Add Relation on page 5-7 for more information on migration scopes. 7. Tab to the command line, type SAVE, and press Enter. After you save the relation, the panel heading changes from Add a Relation to Maintain a Relation, and the system fills in the values for the audit attributes. A message that reads User modifications to object have been saved appears in the command area (Saving the relation on page 2-16).
2-15
Figure 2-23
Saving the relation

Maintain a Relation More: + Level: 3
Repository: SUNRISE
V: 1
Project: DEV
Migration Name . . . . . . . . . . . . DMC_VER2______________________ Has-Root Process Name . . . . . . . . . . . . DMC_FUNC2_____________________ Relationship Attributes: Scope type . . . . . . . . . 2
Entity Hierarchy
Audit Attributes: Date Created . . . . . . . : 95/05/12 Time Created . . . . . . . : 09:50 Created by . . . . . . . . : SS0222 Date Maintained . . . . . . : 95/10/02 Time Maintained . . . . . . : 09:50 Maintained by . . . . . . . : SS0222 Change # . . . . . . . . . : 0001 Local Maintenance Date . . : 95/10/02 User modifications to object have been Saved.
After a relation is saved, you can change the user-defined attributes by overtyping values and then typing SAVE on the command line again. 8. Type TXR on the action line to add text to the relation. Use the text to describe the purpose of the relation to other project users. We recommend this step, although it is optional. See Figure 2-24.
Adding text to the relation
Figure 2-24
--------- SS0222.SS0196.MOD.STK ------------------------------ COLUMNS 001 072 TEXT for Relations Name . . . . . . . : DMC_FUNC2 Version . . . . . : 1 ****** 000001 000002 000003 ****** ***************************** TOP OF DATA ****************************** DMC_VER2 HAS ROOT FUNCTION DMC_FUNC2. SCOPE IS ENTITY HIERARCHY BECAUSE THE APPLICATION IS BEING MIGRATED TO VERSION 2 FOR THE FIRST TIME. **************************** BOTTOM OF DATA ****************************
9.
If you want to add additional relations of the same type, navigate to the Maintain a Relation panel. Type over the name field, change the scope type if necessary, and press Enter. The system generates another blank Add a Relation panel, this time with the Migration Name field populated with the value you specified in the previous Add a Relation panel.
10. Tab to the command line, type SAVE, and press Enter. Repeat this step for each entity of the same type that you want to add to the migration package as a root entity. 11. To add an instance of another entity type, return to the AppBuilder Host Workbench panel of the project and repeat steps 2 through 8. 12. Repeat this procedure until you have included each root entity that you want in the migration package. 13. Press F3 to exit the Maintain a Relation panel. You can use the maintain relation (MR) action to display this panel if you want to check or modify the relation attribute values. Use the list relations (LR) action next to the migration entity to make sure you have included all the root entities you want in the migration package. The system displays each relation type, the name of each seed entity, the scope of each entity, and the date when the relation was created. Use the delete relation (DR) action to delete any entities that should not be in the migration package.
2-16
Once you determine that the migration package is complete, you are ready to export it. The next section describes the export (EXPORT) action in detail.

The export (EXPORT) action copies the objects defined in the migration package from the repository to migration files on DASD. The objects are exported to files outside the repository environment so they can be backed up or imported into another environment. See Figure 2-25.
Figure 2-25 Exporting the migration package
univers
This section describes how to export the migration package. 1. 2. On the AppBuilder Host Workbench panel, type LE on the Migration action line to navigate to the AppBuilder List Facility for Entity Migration panel. Type EXPORT on the action line of your migration entity (Figure 2-26) and press Enter.
2-17
Figure 2-26
Selecting the migration entity to export

List Facility for Entity Migration
Repository: SUNRISE
V: 1
Project: DEV
Level: 2
Action ________ EXPORT__ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________
Command ===> _____________________________________________________________
3.
On the Export Options panel, the object parts you can include are displayed with the letter S in the selection field (see Figure 2-26). Press Enter to keep the selected options. Type a space over the S to deselect an option. Text, source, or keywords respectively are not included in the migration package unless an S is entered in the adjacent fields. If you want to specify criteria for filtering what gets exported, type 1 for Yes in the Selective Export field. See Selective Export on page 5-23 for more information.
Note
Some repository administrators do not permit users to override the default processing options. See your administrator if you have any questions. Selecting migration export options
Migration Export Options
Figure 2-27
Name . . . . . . . . : DMC_VER2 Version . . . . . . : 1 Type 's' to select an option or type a space to deselect. Then press ENTER. Processing Options Object Parts to Process
. . . . . . . S Text S Source S Keywords . SEEROUT.M00016NR_
Data Set Prefix for Migration Files
Selective Export . . . . . . . . . . . 2 1. Yes 2. No
Command
=======> ___________________________________________________________
.
On the Data Set Prefix text line is the name of the data set you are exporting your migration information to (which was assigned when you created your source migration entity). Type spaces over the data set name to migrate without migration files, which omits making these data sets. This is useful if you are just migrating to another version in the same repository because it
2-18
reduces the processing time. See Migrating Without Migration Files on page 5-17 for more information. See Selective Export on page 5-23 for information on exporting selectively. If you type a new name in this field, a panel pops up to confirm your change (Figure 2-28).
Figure 2-28 Changing the Data Set Prefix
___________________ Confirm Request ____________________ | | | Do you wish to use SEEROUT.DMCMIG01 as your | | migration Data Set Prefix? | | | | | | | | 1 1. Yes | | 2. No | | | | Command ===> ________________________________________ | |________________________________________________________|
Note 4.
If you want to export to tape, you must first export to DASD successfully. Then use the copy migration files (COPYMIG) action. See Copy Migration Files on page 5-20 for more information.
Press Enter to start the export job and return to the AppBuilder List Facility for Entity Migration panel. The system acknowledges the submission of the export job with the message Export Migration for <entity name> Processed.
5.
Monitor the progress of your job by checking the value of the migration state on the Maintain an Entity panel (see Figure 2-29).
To see the migration state change, refresh the screen: press F19, or type REFRESH on the command line and press Enter.
Note
Figure 2-29
Checking the migration state value

V: 1
Project: DEV
. . . . .
. . . . .
. . . . .
. . . . .
. : . . :
DMC_VER2______________________ AA4FNR MIGRATE DMC_APP1 FROM V1 TO V2 SEEROUT.M00016NR_ 9 Export Job Executing
Audit Attributes: Date Created . . . . . . . : 95/05/12 Time Created . . . . . . . : 09:13 Created by . . . . . . . . : SS0222 Date Maintained . . . . . . : 95/10/02 Time Maintained . . . . . . : 09:55 Maintained by . . . . . . . : SS0222 Project . . . . . . . . . . : DEV Change # . . . . . . . . . : 0004 Owner Id . . . . . . . . . : SS0222 Local Maintenance Date . . : 95/10/02 Local Maintenance Time . . : 09:55:05 Command ===> _______________________________________________________________
6.
You cannot continue with target repository processing until the migration state registers a value of Export Successful. See Table 5-3 on page 5-5 for a complete list of migration state values. If the export job fails, review the job results using the Spool Display and Search Facility (SDSF) in the Interactive Structured Programming Facility (ISPF). Correct the problem, and run the job again.
2-19
7.
Record the name of the data set prefix from the migration Maintain an Entity panel. This file contains the migration information, which you will need for target repository processing. In the example in Figure 2-29, the data set prefix is SEEROUT.M00016NR.
To see what entities are included in the migration package, use the list relation (LR) action. The system displays each relation type, the name of each seed entity, the scope of each entity, and the date when the relation was created. The export (EXPORT) action submits a batch job to fulfill your request. When the job has finished, you can review the results online in many ways: Refresh the Maintain an Entity panel (press F19) to see the current Migration State attribute. The state reflects the submission, execution, incompletion, success, or failure of the job. Record the job number that is displayed after you submit the export job, then use SDSF to get detailed job status information. Look at the messages associated with export processing. For instructions on accessing, interpreting, and printing export job messages, see Export Migration on page 5-22. Once the migration package state is either successful or failed, you can use the view results for migration (RES) action next to the migration entity to display the results of the export. After the export, use the list migration contents (LISTMIG) action to see what was exported. Use the report on migration (REP) action to generate printed or on-line reports. If you want to see the migration report, you must generate it before importing. Once you determine that the export has been successful, you have completed source repository processing. The actions performed in the target repository are described in Chapter 3, Target Environment Processing
2-20
CHAPTER
TARGET ENVIRONMENT PROCESSING
After you have successfully exported the migration package, detach from the source repository and attach to the target repository if you are migrating between repositories, or change versions if you are migrating between versions. The following sections describe these steps: Creating the Target for Migration Package Analyzing the Impact of Migration Importing the Migration Package After You Import
Creating the Target for Migration Package

The purpose of the migration processing performed on the target repository is to copy the information from the source migration files to internal migration-control tables, which are used to update the repository. The add entity (ADDE) action creates an instance of a migration entity which becomes the root of the imported migration package. Figure 3-1 illustrates an overview of how target repository processing takes place. This section describes how to add a migration entity to the target repository. Note
Before you begin, make sure you know the data set prefix that was assigned to the source migration entity during source-environment processing. You can find the prefix on the Maintain an Entity panel for the source migration entity.
3-1
Figure 3-1
Target Repository Processing
univers
1. 2.
Navigate to the AppBuilder Host Workbench panel of the repository, version, and project to which you are migrating. (To change projects, use the change projects (PROJECTS) action.) Type ADDE on the Migration action line (Figure 3-2) and press Enter.
Creating the target migration entity
AppBuilder Host Workbench Repository: SUNRISE Action ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ADDE____ ________ ________ ________ ________ V: 2 Project: DEV Level: 1
Figure 3-2
Entity Field File Form FSDM Scheme FSDM Value Function Help Text Identifier Key Location Logical Process Machine Migration Organization Physical Event Process Rebuild Package
Command ===>_______________________________________________________________
3.
On the blank Add an Entity detail panel, type the name, a description (optional), and the name of the data set you are exporting your migration information from in the Data Set Prefix field (Figure 3-3). The name is an alphanumeric string up to 30 single-byte or 14 double-byte characters.
3-2
Target Environment Processing
The description can be up to 30 characters of text that explains the purpose of the migration to other Migration Facility users. Although a description is optional, it is highly recommended because it makes the migration entity much more useful to other project members. Note
Figure 3-3 The Data Set Prefix entry must exactly match the name of the export data set prefix you are importing. Naming the target migration entity
Add an Entity Repository: SUNRISE Migration Attributes: Name . . . . . . . System Id . . . . . Description . . . . Data Set Prefix . . V: 2 Project: DEV More: Level: 2 +
. . . .
. . . .
. . . .
. . . .
. DMC_VER2______________________ : . TARGET OF DMC_AP1 FROM V1 TO V2 . SEEROUT.M00016NR_
1. Analyze Approved 2. Export Successful 3. Import Successful 4. Import Job Submitted 5. Export Job Submitted 6. Export Job Failed 7. Analyze Job Failed 8. Analyze Job Executing 9. Export Job Executing 10. Analyze Successful 11. Analyze Job Submitted 12. Import Job Failed 13. Import Job Executing Command ===>_______________________________________________________________
Migration State . . . . . . :
4.
When you have finished, tab to the command line and type SAVE. Press Enter. Notice that after you save, the title changes from Add an Entity to Maintain an Entity, the systemdefined attributes are filled in, and you see a message that says User modifications to object have been saved. See Figure 3-4. After an entity is saved, you can change the user-defined attributes by overtyping values and then typing SAVE on the command line again.
Figure 3-4
Maintaining the target

Maintain an Entity More: Level: 2 +
V: 2
Project: DEV
. . . . . DMC_VER2______________________ . . . . : AA4HNR . . . . . TARGET FOR DMC_AP1 FROM V1 TO V2 . . . . . SEEROUT.M00016NR_ . . . . : 14 N/A
Audit Attributes: Date Created . . . . . . . : 95/05/12 Time Created . . . . . . . : 11:10 Created by . . . . . . . . : SS0222 Date Maintained . . . . . . : 95/10/02 Time Maintained . . . . . . : 11:10 Maintained by . . . . . . . : SS0222 Project . . . . . . . . . . : DEV Change # . . . . . . . . . : 0001 Owner Id . . . . . . . . . : SS0222 Local Maintenance Date . . : 95/10/02 User modifications to object have been Saved. Command ===>_______________________________________________________________
5.
Type TXE on the command line to add text to the entity. The text describes the purpose and scope of the migration package to other Migration Facility users (Figure 3-5 shows sample text). This step is optional. Press F3 to return to the Maintain an Entity panel.
3-3
Figure 3-5
Adding text to the migration entity
--------- SS0222.SS0196.MOD.STK ------------------------------ COLUMNS 001 072 TEXT for Migration Name . . . . . . . : DMC_VER2 Version . . . . . : 2 ****** ***************************** TOP OF DATA ****************************** 000001 USED TO MIGRATE DMC_APP_1 (PAYROLL) FROM VERSION 1 TO VERSION 2 IN SUNRISE.MOVING FROM DEVELOPMENT TO SYSTEM TEST. ****** **************************** BOTTOM OF DATA ****************************
Command ===>
______________________________________________ Scroll ===> PAGE
6.
Type K on the command line to add keywords to the entity. Keywords describe the purpose and scope of the migration package to other Migration Facility users (Figure 3-6 shows sample keywords). This step is optional. Press F3 to return to the Maintain an Entity panel.
Separate each keyword with a space, and do not exceed 240 characters for all the keywords for a single entity. Adding keywords to the entity
Note
Figure 3-6
--------- SS0222.SS0196.MOD.STK ------------------------------ COLUMNS 001 072 KEYWORDS for Migration Name . . . . . . . : DMC_VER2 Version . . . . . : 2 ****** 000001 000002 000003 000004 000005 000006 ****** ***************************** TOP OF DATA ****************************** MIGRATION DMC VER2 SS0222 DMC_CUSTOMER_MAINTENANCE DMC_CUSTOMER_RESERVATION **************************** BOTTOM OF DATA ****************************
Command ===>
______________________________________________ Scroll ===> PAGE
7. 8. 9.
Return to the Maintain an Entity panel. Press F3 to exit the Maintain an Entity panel. You can use the maintain entity (ME) action to display this panel if you want to check or change the entity attribute values. Record the name of this entity, because you will use it throughout target environment processing.
Now you are ready to analyze the impact of the migration before deciding to import the migration package. Analyzing the impact of migration is described in detail in the following section.
3-4
Analyzing the Impact of Migration

Before importing into the target repository, you must perform an impact analysis. This impact analysis is a what if report that informs you of the effect of a potential import. The analysis gives detailed counts of creates, updates, and deletes of all objects and object parts in the migration package, as well as which objects need to be prepared as a result of the migration. All actions to be applied to the target repository should be actions that you are expecting. The analyze migration impact (ANALYZE) action takes the unstructured sequential object data from the exported migration files, copies it to temporary files in the target environment, and compares objects in the migration package with those in the target environment. The development team then reviews the results of the analysis and imports the objects in the migration package. As an option, the development team can choose to skip particular objects. This section describes how to analyze the impact of the migration package. 1. 2. On the AppBuilder Host Workbench panel, type LE on the Migration action line to navigate to the AppBuilder List Facility for Entity Migration panel. Type ANALYZE on the action line of your migration entity (Figure 3-7) and press Enter.
Selecting the migration entity to analyze
Figure 3-7
Action Name System Id ANALYZE_ DMC_VER2 AA4HNR ________ GET_NRV1V2 AA3YNR ________ MIG_FDFAULT AA12NR ________ MIG_FREPORT AA13NR ________ WMM_MIG_PHY_EVT AA2INR ***************************** BOTTOM OF DATA ********************************
3.
On the Data Set Prefix text line of the Migration Analyze Options panel (Figure 3-8), the system displays the name of the data set from which you are importing your migration information (which you specified when you created your target migration entity).
Selecting analyze options
Migration Analyze Options
Figure 3-8
Name . . . . . . . . : DMC_VER2 Version . . . . . . : 2
Enter
processing information and press ENTER.
Processing Option Data Set Prefix for Migration Files
. SEEROUT.M00016NR_
You can type a different name here to check a different set of files
If you type a new name in the Data Set Prefix field because you want to analyze a different set of migration files, a panel pops up to confirm your change (Figure 3-9).
3-5
Figure 3-9
Changing the Data Set Prefix
___________________ Confirm Request ____________________ | | | Do you wish to use SEEROUT.AXPMIG01 as your | | migration Data Set Prefix? | | | | | | | | 1 1. Yes | | 2. No | | | | Command ===> ________________________________________ | |________________________________________________________|
If your first attempt at analyzing the migration impact failed and you are now using the analyze migration impact (ANALYZE) action for a subsequent time, you must choose another processing option: the Execution option. Select the Reload Migration Files option to resubmit the analyze job from the beginning. Select the Restart option to start the job from the internal step that failed (Figure 3-10). See Analyzing the Migration Impact on page 5-11 for a discussion on rerunning and restarting the analyze job.
Figure 3-10 Selecting the Reload or Restart option
Migration Analyze Options Name . . . . . . . . : DMC_VER2 Version . . . . . . : 2
Enter
processing information and press ENTER.
Processing Option Data Set Prefix for Migration Files . SEEROUT.M00016NR_ Execution Option . . . . . . . . . . . _ 1. Reload Migration Files 2. Restart
4.
Press Enter to start the analyze job and return to the AppBuilder List Facility for Entity Migration panel. A system acknowledges the submission of the analyze job with the message Analyze Migration Impact for <entity name> Processed.
5.
Monitor the progress of your job by checking the value of the Migration State attribute on the Maintain an Entity panel (see Figure 3-11).
3-6
Figure 3-11

V: 2
Project: DEV
. . . . . DMC_VER2______________________ . . . . : AA4HNR . . . . . TARGET FOR DMC_AP1 FROM V1 TO V2 . . . . . SEEROUT.M00016NR_ . . . . : 10 Analyze Successful
Audit Attributes: Date Created . . . . . . . : 95/05/12 Time Created . . . . . . . : 11:10 Created by . . . . . . . . : SS0222 Date Maintained . . . . . . : 95/10/02 Time Maintained . . . . . . : 11:10 Maintained by . . . . . . . : SS0222 Project . . . . . . . . . . : DEV Change # . . . . . . . . . : 0003 Owner Id . . . . . . . . . : SS0222 Local Maintenance Date . . : 95/10/02 Local Maintenance Time . . : 11:10 Command ===> ______________________________________________________________
Note 6.
To see the migration state change, refresh the screen: press F19, or type REFRESH on the command line and press Enter.
You cannot continue until the migration state registers a value of Analyze Successful. See Table 53 on page 5-5 for a complete list of migration state values. If the analyze job fails, review the job results using SDSF, correct the problem, and run the job again.
Note
When you run the analyze job again, you can choose to rerun or restart the job. See Analyzing the Migration Impact on page 5-11 for a more detailed discussion on rerunning and restarting the analyze job.
The analyze migration impact (ANALYZE) submits a batch job to fulfill your request. Once the job has finished, you can review the results online in several ways: Refresh the Maintain an Entity panel to see the current Migration State attribute. The state reflects the submission, execution, incompletion, success, or failure of the job. If the RES_TO_FILE variable in the @MIGENVn INI file is set to Y then you can use the view results of migration (RES) action to see the messages that contain the results of the batch job, including date and domesticates for job start and job end, as well as the final job state value. Record the job number that is displayed after you submit the analyze job. Then use SDSF to get detailed job status information. Look at the messages associated with analyze processing. For instructions on accessing, interpreting, and printing analyze job messages, see Analyzing the Migration Impact on page 5-11. When you determine that the analyze is completed, you can use the following actions to examine the migration package. Use the list migration contents (LISTMIG) to view the expected migration impact. From the list migration contents action: Use the delta (DELTA) action to view specifically what object parts are changing and the details of each part. Use the toggle (TOGGLE) action to manually exclude objects from the migration. Use the list relation (LR) action to see which objects need to be prepared as a result of the migration.
3-7
The resulting list has a migration will prepare message by each object to be prepared. You must first set the RUN_RBDETECTOR variable to Y for Yes in the @MIGENVn INI file, or type the RD (detect objects to be rebuilt) action. Use the summary counts for migration (COUNT) action to display the number of objects in the migration package by migration status and migration type. See Appendix A, Migration Status Values for a complete list of status values. Use the report on migration (REP) action to generate hard copy reports. If you want to see the migration report, you must generate it before importing. See Chapter 5, Migration Actions for more information. If you are satisfied with the results of the analyze migration impact, and you decide that the migration package is ready, you can import. Note
Your administrator may require you to get approval before importing a migration package. See Approve Migration on page 5-16 for more information.

The import (IMPORT) action copies the migration objects from temporary files and tables to the target repository. Successful completion of the analyze migration impact action and a careful review of the analysis precede successful import migration processing. This section describes how to import the migration package. 1. On the AppBuilder Host Workbench panel, type LE on the Migration action line to navigate to the AppBuilder List Facility for Entity Migration panel.
Remember, if your administrator requires it, you must get approval before importing a migration package. See Approve Migration on page 5-16 for more information.
Note 2.
Type IMPORT on the action line of your migration entity (Figure 3-12) and press Enter.
Selecting the migration entity to export
Figure 3-12
Action Name IMPORT__ DMC_VER2 ________ GET_NRV1V2 ________ MIG_FDFAULT ________ MIG_FREPORT ________ WMM_MIG_PHY_EVT ******************************* BOTTOM OF
System Id AA4HNR AA3YNR AA12NR AA13NR AA2INR DATA ******************************
3.
On the Import Options panel, the object parts and change types you can include are defaulted with the letter S in the selection field. See Figure 3-13. Press Enter to keep the selected options. Type a space over the S to deselect an option. If one or more object parts are excluded, they are not processed with the migration package. Remember that you cannot import anything you did not export.
3-8
If one or more import options are excluded, objects tagged Import will Create, Import will Update, or Import will Delete are not processed with the migration package. Note
Some repository administrators do not permit users to override the default processing options. See your administrator if you have any questions. Selecting the migration import options
Migration Import Options Name . . . . . . . . : DMC_VER2 Version . . . . . . : 2 Type 's' to select an option or type a space to deselect. Then press ENTER. Processing Options Object Parts to Process
Figure 3-13
. . . . . . . S Text S Source S Keywords
Import Options . . . . . . . . . . . . S Create S Update S Delete
Command
=======>
__________________________________________________________
4.
Press Enter to start the import job and return to the AppBuilder List Facility for Entity Migration panel. The system acknowledges the submission of the import job with the message Import Migration for <entity name> Processed.
5.
Monitor the progress of your job by checking the value of the migration state on the Maintain an Entity panel (see Figure 3-14).
To see the migration state change, you must refresh the screen: press F19, or type REFRESH on the command line and press Enter.
Note
Figure 3-14

V: 2
Project: DEV
. . . . . DMC_VER2______________________ . . . . : AA4HNR . . . . . TARGET FOR DMC_AP1 FROM V1 TO V2 . . . . . SEEROUT.M00016NR_ . . . . : 4 Import Job Submitted
Audit Attributes: Date Created . . . . . . . : 95/05/12 Time Created . . . . . . . : 11:10 Created by . . . . . . . . : SS0222 Date Maintained . . . . . . : 95/10/02 Time Maintained . . . . . . : 11:10 Maintained by . . . . . . . : SS0222 Project . . . . . . . . . . : DEV Change # . . . . . . . . . : 0003 Owner Id . . . . . . . . . : SS02222 Local Maintenance Date . . : 95/10/02 Local Maintenance Time . . : 11:10 Command ===> ______________________________________________________________
3-9
After You Import
6.
When the migration state registers a value of Import Successful, you can begin rebuild processing. See Table 5-3 on page 5-5 for a complete list of migration state values. If the import job fails, review the job results using SDSF. Correct the problem, and run the job again.
The import action submits a batch job to fulfill your request. Once the job has finished, you can review the results online in three ways: Refresh the Maintain an Entity panel (press F19) to see the current Migration State attribute. The state reflects the submission, execution, incompletion, success, or failure of the job. Record the job number that is displayed after you submit the Import job. Then use SDSF to get detailed job status information. Look at the messages associated with import processing. For instructions on accessing, interpreting, and printing Import job messages, see Import Migration on page 5-31. Once import processing completes successfully, you have finished migration processing.
After You Import

After the import job has completed, you can use the following actions to examine the imported migration package. Use the list migration contents (LISTMIG) action to examine what changes have been made to the repository. Use the list relation (LR) action to see which objects are included in the migration package, along with the scope of each root, and the date the relation was created. Use the analyze rebuild impact (RD) action to determine which objects you need to rebuild. Use the summary counts for migration (COUNT) action to display the number of objects in the migration package by migration status and migration type. Use the view results of migration (RES) action to see the messages that contain the: Results of the batch job Date and time stamp for the start of the job Date and time stamp for the end of the job Final job status value Use the report on migration (REP) action to generate hard copy reports. See Migration Actions for more information. When you are satisfied that objects have been created, updated, or deleted appropriately, the Enterprise Rebuild Facility prepares, links, installs, and binds the host objects in that environment. Refer to the Enterprise Rebuild Guide for more information.
3-10
CHAPTER
AUTOMATED MIGRATION PROCESSING
You can choose automated migration processing when both the source and target repositories are on the same CPU. Automated migration processing gives you the flexibility of deciding which methods or combinations of methods you want to process without manual intervention. Automated migration processing simplifies the migration and rebuild processes to the actions shown in Figure 4-1, performed in sequence. (Refer to the Enterprise Rebuild Guide for more information on rebuild processing.) The following sections describe the steps for automating migration processing: Before You Migrate Using the Migration Package Preparing for Automatic Processing Sample Automated Migration After You Migrate
4-1
Before You Migrate
Figure 4-1
univers
Before You Migrate

Before you begin the migration process, make sure of the following: You are authorized to perform migration actions in the source and target environments you have chosen. Check with your repository administrator if you are not sure whether you are authorized to migrate. Your application has been prepared and can execute in the source environment. It is a waste of time and resources to migrate applications that cannot execute. You meet the exit and entrance criteria of the source and target environments, respectively. You have enough time to complete the migration. The target repository is defined in the INI setup, and the INI variables on both the source and target repositories are set to the values you need. In addition, make sure the target environment has enough space. Use the view AppBuilder INI Files (INIDISP) action to check the values of your migration environment-control variables. Contact your administrator if you need the INI variables changed. The repository-to-repository relationships are set up correctly in the ADM project.
4-2
Automated Migration Processing
Before You Migrate
The E_REPOSIT and R_REPREP DB2 tables define these relationships. E_REPOSIT defines both source and the target repository, and R_REPREP sets up which source version is allowed to migrate to which target version. See the Managing Enterprise Repositories for more information. Note
Your repository administrator may have other criteria you must meet before migrating.
Refer to Enterprise Administration Guide for information on authorization, configuring the migration path, and other considerations which affect migration.
Automated Processing Options

You can choose the options listed in Table 4-1 before automated migration processing begins.
Table 4-1 Option Methods to process Repository ID and version number Objects parts to process Selective export Import options Automated migration processing options Description Choose one or more methods: export, analyze, import, or rebuild. Type the repository ID and version number for the target repository. Choose one or more object parts: text, source, and keywords. You can choose this option for each method. Choose yes or no to export selected objects. See Figure 5-12 on page 5-24 for more information. These are the options for the import action. See Import Migration on page 5-31 for more information.
The RUNIMP, RUNRBDA, RUNRBDPR, RUNRBDIN, and RUNRBDEX variables in the @MIGENVn INI file specify the default values used for the migrate options. The OVIMP, OVRBDA, OVRBDPR, and OVRBDIN variables determine whether you can override the default values used for the migrate options. In a typical scenario, your administrator sets the defaults to let you run everything automatically except for import, and allows you to override all the settings except for import. By doing that, you are forced to check your analyze results before importing into the target repository. Table 4-2 lists variables in the @MIGENVn INI file that affect how automated migration processing proceeds. See Chapter 7, Setting Up the Environment for more information about these variables.
Table 4-2 Variable SIGNAMI SIGNIMP SIGNRBD RUNIMP RUNRBDA RUNRBDPR INI variables for automated migration processing Description Specifies whether you need an authorized user to approve the migration process before you continue to the import job. The default value is No. Specifies whether you need an authorized user to approve the import process before you continue to the rebuild analyze job. The default value is No. Specifies whether you need an authorized user to approve the rebuild analyze process before you continue to the rebuild prepare job. The default value is No. Specifies whether you can import during automated migration. The default value is No. Specifies whether the rebuild package is to be analyzed during automated migration. The default value is No. Specifies whether the rebuild package is prepared during automated migration. The default value is Yes.
4-3
Using the Migration Package
Table 4-2 Variable
INI variables for automated migration processing (Continued) Description Specifies whether the rebuild package is installed during automated migration. The default value is Yes. Specifies whether the rebuild package is exported during automated migration. The default value is Yes. Specifies whether you can override the default value for the Import Migration option. The default value is No. Specifies whether you can override the default value for the Analyze Rebuild Package option. The default value is Yes. Specifies whether you can override the default value for the Prepare Rebuild Package option. The default value is Yes. Specifies whether you can override the default value for the Install Rebuild Package option. The default value is Yes.
RUNRBDIN RUNRBDEX OVIMP OVRBDA OVRBDPR OVRBDIN
Overnight Processing
Use the Migration Migrate Options window to specify overnight processing by typing 1 at the Overnight execution prompt in the MIGRATE options window to defer the MIGRATE action for overnight processing, as shown in Figure 4-2.
Figure 4-2 Deferring MIGRATE for overnight processing
Migration Migrate Options Name . . . . . . . . : LMK_MIG_DREP Version . . . . . . : 1 Type 's' to select or leave blank to deselect an option. Then press ENTER. Processing Options Methods to Process . . . . . Status Completed Completed
_ _ _ _
Export Migration Analyze Migration Import Migration Rebuild Migration
Defer MIGRATE for overnight Execution
1 1. Yes 2. No
The variable JOB_NIGHTCLA in the JCL section of the @HPSENV file must be set to the job class you use to specify overnight execution.
Status Fields
Status fieldslocated in the MIGRATE options window allow you to skip already completed steps when restarting MIGRATE.
Using the Migration Package

The automate migration (MIGRATE) action copies the objects defined in the migration package from the repository to migration files on DASD. Next, the automate migration (MIGRATE) action takes the
4-4
Preparing for Automatic Processing
unstructured sequential object data from the exported migration files, copies it to temporary files in the target environment, and compares objects in the migration package with those in the target environment. If the results of the analysis show that the incoming data will not cause a collision with the existing data in the target repository, the migration objects are copied from temporary files to the target repository. This section describes how to automatically migrate a migration package that you have already seeded with the root entities you want. The example selects automatic processing for all methods:
Migration Methods Export Analyze Import Rebuild Methods Analyze Prepare Install
Note that starting automatic migration processing at the rebuild methods, including all these methods, is equivalent to the super prepare action. Also note that you can select options only from the entry point method. That is, if you select to automate migration at the analyze action, then you can select options only for analyze. The default options (as specified in the @MIGENVn INI and @RBDENVn INI files) will be in effect for the remaining actions. You can choose various combinations of methods, as long as all prior steps completed successfully. You can start at any point, with the following provisions: You must successfully export and analyze before you can import The import must be successful before starting any of the rebuild methods The prepare method must be successful before you can install When you choose automated migration processing, the Migration Facility creates a migration entity in the target repository, analyzes it, and imports it. The Migration Facility also creates a rebuild package entity on the target and attaches the migration entity as the root.
Preparing for Automatic Processing

Perform the following steps to set up the environment so you can migrate automatically: 1. Locate the $MIGRATE member in the base INI installation files. This member has two sections that you need to edit: Specify the BASE, MOD, and REP level data sets of the repository you plan to migrate into Specify whether the REP level INI is to be allocated See the Enterprise Administration Guide for details. 2. Copy the $MIGRATE member into each repository level INI PDS, giving it the implementation name of each source and target repository you want to migrate from and to. If you plan on migrating within the same repository, you need to create only one member. 3. Enter the ADM project for the source repository of your migration path and add repository objects withe the same implementation names as the repository INI files you created in step 2. Repeat the procedure for the target repository.
4-5
Sample Automated Migration
4.
Add a relationship between the source repository object and the target repository object, specifying the options required on the relationship. Remember to do this for both the source and target repositories.
5.
Edit the @MIGENVn INI files for both the source and target repositories to specify what you want the MIGRATE command to do, and whether you can override these options (EXPORT, ANALYZE, IMPORT, RANALYZE, RPREPARE, and RINSTALL). Create a migration object in the sou4rce repository and the root entities. Perform the MIGRATE action against this migration package and specify the information the panels request.
6. 7.

In this example, the source repository is version 1 and the target is version 2 in the same repository. Follow the steps described below to automate migration. 1. On the AppBuilder Host Workbench panel, type LE in the action line next to Migration to navigate to the AppBuilder List Facility for Entity Migration panel.
The AppBuilder Host Workbench Panel
Figure 4-3
2.
Type MIGRATE on the action line of the migration entity you want to process (Figure 4-4) and press Enter.
4-6
Figure 4-4
Selecting the migration entity to migrate

Repository: SUNRISE
V: 1
Project: DEV
Level: 2
Action ________ MIGRATE_ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________
Command ===> ______________________________________________________________
3.
On the Migrate Options panel, type the letter S in the selection field by the methods you want to process automatically (see Figure 4-5). Press Enter.
Whether you can process all of the methods at once depends on how your repository administrator sets the @MIGENVn INI variables (where n is the repository version). If you are not authorized for certain methods, those fields are protected. For example, most administrators let you export and analyze the migration package automatically, but they do not let you import without reviewing the results of the analysis. Selecting migrate options
Migration Migrate Options
Note
Figure 4-5
Name . . . . . . . . : DMC_VER2 Version . . . . . . : 1 Type 's' to select an option or type a space to deselect. Then press ENTER. Processing Options Methods to Process . . . . . . . . . . S S S S
Export Migration Analyze Migration Import Migration Rebuild Migration
Command
=======> ___________________________________________________________
The next several panels offer options for each method you have chosen to process automatically. 4. On the Migration Export Options panel, all object parts are included by default with the letter S in the selection field (see Figure 4-6). Press Enter to keep the selected options. Type a space over the S to deselect an option. Text, source, or keywords respectively are not included in the migration package unless an S is entered in the adjacent fields.
4-7
Figure 4-6
Selecting export options

Migration Export Options
Command
=======> ___________________________________________________________
5.
Next, type the ID and version number of the repository to which you are migrating (Figure 4-7).
Selecting the target repository
Figure 4-7
------------------------------------------------------------------------| | | Migrating across Repository and/or Version. | | Enter the required information then press ENTER. | | | | Target Repository Options | | Repository Id . . . . . . . . . . . . SUNRISE_____________ | | Version . . . . . . . . . . . . . . . 2 | | | | | | Command =======> ____________________________________________________ | -------------------------------------------------------------------------
After you enter the target repository and version, the system validates the information with the @MIGENVn INI files and the E_REPOSIT and R_REPREP tables. You will receive a message if the source repository cannot migrate to the target repository, and processing will stop. However, if you are not authorized to perform a method, the job will fail before that job starts. 6. After you press Enter, a pop-up panel prompts you to enter the data set prefix for the migration files (Figure 4-8). The data set prefix is required if you are migrating to another repository. Enter prefix for migration files or leave blank to migrate without migration files
Figure 4-8
----------------------------------------------------------------------------| Command === ____________________________________________________________ | | | | Type blank and press enter if you do not wish to create migration files | | | | Data Set Prefix for Migration Files . . . __________ | | | | | -----------------------------------------------------------------------------
If you are migrating to another version of the same repository, you can blank out the data set name to migrate without creating migration files. This is useful when you know you will not be migrating to another target, particularly if you are just migrating to another version in the same repository, because it reduces processing time. See Migrating Without Migration Files on page 5-17 for more information. 7. Select your import options on the Import Options panel. The object parts and change types you can include are displayed with the letter S in the selection field (Figure 4-9). Press Enter to keep the selected options, or type a space over the S to deselect an option. If one or more object parts are excluded, they are not processed with the migration package.
4-8
If one or more Import options are excluded, objects tagged Import will Create, Import will Update, or Import will Delete are not processed with the migration package. Note
Figure 4-9 Some repository administrators do not permit users to override the default processing options. See your administrator if you have any questions. Selecting the migration import options
Migration Import Options Name . . . . . . . . : DMC_VER2 Version . . . . . . : 2 Type 's' to select an option or type a space to deselect. Then press ENTER. Processing Options Object Parts to Process
Import Options . . . . . . . . . . . . S Create S Update S Delete
8.
Select the methods you want to process in the Migration Rebuild Options panel, as shown in Figure 4-10.
Migration Rebuild Options panel
Migration Rebuild Options =======> _____________________________________________________
Figure 4-10
Command
Name . . . . . . . . : DMC_VER2 Version . . . . . . : 2 Type 's' to select an option or type a space to deselect. Then press ENTER. Processing Options Methods to Process . . . . . . . .
S Analyze Rebuild Package S Prepare Rebuild Package S Install Rebuild Package ______________________________
Application Configuration
. . . .
Export Rebuild Package . . . . . .. 2 1. Yes 2. No
9.
Press Enter to start the migrate job and return to the AppBuilder List Facility for Entity Migration panel. The system acknowledges the submission of the migrate job with the message Automatic Migration for <entity name> Processed.
10. Monitor the progress of your job by checking the value of the migration state on the Maintain an Entity panel (Figure 4-11 on page 4-10). Check the following: Migration entity on the source for the export method Migration entity on the target for the analyze migration impact and import methods Rebuild package entity on the target for the analyze rebuild impact, prepare, and install methods. Refer to Enterprise Rebuild Facility for more information about the methods on the target environment. Note
To see the migration state change, you must refresh the screen: press F19, or type REFRESH on the command line and press Enter.
4-9
After You Migrate
Figure 4-11

V: 1
Project: DEV
. . . . .
. . . . .
. . . . .
. . . . .
. : . . :
DMC_VER2______________________ AA4FNR MIGRATE DMC APP_1 FROM V1 TO V2 SEEROUT.M00016NR_ 9 Export Job Executing
Audit Attributes: Date Created . . . . . . . : 95/05/12 Time Created . . . . . . . : 09:13 Created by . . . . . . . . : SS0222 Date Maintained . . . . . . : 95/10/02 Time Maintained . . . . . . : 09:55 Maintained by . . . . . . . : SS0222 Project . . . . . . . . . . : DEV Change # . . . . . . . . . : 0004 Owner Id . . . . . . . . . : SS0222 Local Maintenance Date . . : 95/10/02 Local Maintenance Time . . : 09:55:05 Command ===> _______________________________________________________________
11. Automatic migration processing is not complete until the migration state registers a successful value for the last job you chose to complete. See Table 5-3 on page 5-5 for a complete list of migration state values. If migration processing fails, review the job results using the Spool Display and Search Facility (SDSF) in the Interactive Structured Programming Facility (ISPF). Correct the problem and continue processing by running each remaining job, beginning with the one that failed. The automate migration (MIGRATE) action submits each job to fulfill your request. Once the jobs are finished, you can review the results online in three ways: Refresh the Maintain an Entity panel (press F19) to see the current migration package state. The state reflects the submission, incompletion, execution, and success or failure of the job. Use SDSF in ISPF to get detailed job status information. Look at the messages associated with rebuild install processing.
After You Migrate

When you determine that the migration and rebuild processing has been successful, use the following actions to examine the migration package: List migration contents (LISTMIG) action on the migration entity List rebuild contents (LISTRBD) action on the rebuild package entity to examine what changes have been made to the repository View results of rebuild (RES) action to see the messages that contain the: Results of the batch job Date and time the job started Date and time the job ended
4-10
After You Migrate
Final job status value Use the Report (REP) action to generate hard copy or on-line reports. When you determine that the rebuild install has been successful, you are ready to test the application.
4-11
After You Migrate
4-12
CHAPTER
MIGRATION ACTIONS
The following list of actions describes the action names and functions that AppBuilder provides to manipulate the objects in your Enterprise repository.
Migration Actions
Table 5-1 summarizes migration actions in alphabetical order by command. Note
Table 5-1 Action ACTIONS List entity actions ADDE Add entity ADDR Add relation ANALYZE Analyze migration impact APPROVE Approve migration AUTOSAVE Update Autosave setting BE Browse entity BK Browse keywords BR Browse relation BTXE Browse entity text Contact your system administrator to modify INI variables. Actions Used During Migration Description Displays all actions available to you. The actions available depend on where you are in the migration process. This is a standard repository action. Adds a migration entity, around which all migration processing revolves. See Add Entity. Adds a relation between the migration entity and each root entity to be included in the migration package. See Add Relation. Checks for collisions and analyzes the impact the migration will have on the target repository. See Analyzing the Migration Impact. Allows an individual with a defined level of repository security to approve the results of the Analyze action, so that migration processing can continue. See Approve Migration. Turns the autosave feature on or off. This is a standard repository action. Lets you view entity attributes. This is a standard repository action. Lets you view an entitys keywords. This is a standard repository action. Lets you view relation attributes.This is a standard repository action. Lets you view an entitys text.This is a standard repository action.
5-1
Migration Actions
Table 5-1 Action
Actions Used During Migration (Continued) Description Deletes migration files, migration backup files, and migration processing information from internal control tables. See Clean-up Migration Information. Changes the ownership of an entity from your user ID or project to another user ID or project. This is a standard repository action. Copies migration files from DASD to DASD, from DASD to tape, or from tape to DASD. See Copy Migration Files on page 5-20. Counts the total number of entities in a migration package and counts the number of entities in a migration package by status. See Count Migration Contents on page 5-21. Deletes an entity from the enterprise repository. See Delete Entity on page 5-21. Customizes your debug profile so you can determine the level of detail given for foreground and batch processing trace information. This is a standard repository action. Compares two objectsone in the migration package and one in the target repositorythat have the same key value, to determine exactly how they differ. See Generate a Delta Report on page 5-29. Deletes a relation from the enterprise repository. This is a standard repository action. See Delete Relation on page 5-21 for more information. Displays a list of entity types. This is a standard repository action. Creates a list of all the entities that are directlyor indirectlyparents of a particular entity. This is a standard repository action. Exports the migration package to migration files in DASD. See Export Migration on page 5-22. Imports the migration package to the target version or repository. See Import Migration on page 5-31. Displays the environment control INI files. This is a standard repository action. Adds keywords to the migration entity so you can define the migration package. See Add Keywords on page 5-6. Displays an entity list of the particular type of entity you choose. This is a standard repository action. Lists object counts, objects included in the migration package, and their migration status. Also allows processing options on an object-by-object basis. See List Migration Contents on page 5-33. Locks an entity, which prevents others from making changes to the entity. This is a standard repository action. Lists instances of relationships between two entity types. After analysis, will also list items affected by the migration process. See List Relations on page 5-36. Displays the detail panel of any listed entity, and lets you modify the entity attributes. See Maintain Entity on page 5-39. Automates both source and target repository migration processing. See Automate Migration on page 5-17. Displays the detail panel of any listed relation, and lets you modify the relation attributes. This is a standard repository action.
CLEANUP Clean-up migration information CO Change ownership of entity COPYMIG Copy migration files COUNT Count migration contents DE Delete entity DEBUG Update debug profile DELTA Generate delta report DR Delete relation ENTITY Display entities EW Extended where-used report EXPORT Export migration IMPORT Import migration package INIDISP View AppBuilder INI files K Add keywords to entity LE List entity LISTMIG List migration contents LOCK Lock entity LR List relations ME Maintain entity MIGRATE Automate migration MR Maintain relation
5-2
Migration Actions
Add Entity
Table 5-1 Action
Actions Used During Migration (Continued) Description Lets you change from one project or version within a repository to another. This is a standard repository action. Detects objects that need to be rebuilt as a result of a migration. See Detect Objects to be Rebuilt on page 5-22. Updates the data and state values on any panel. This is a standard repository action. Generates a delta report, a count report, or a detail report on a migration entity. See Generate a Report on page 5-30. Lets you browse the results of the migration actions. See View Results of Migration on page 5-41. Helps you find and reuse existing entities by searching for entities of all types associated with specified keywords. This is a standard repository action. Lets you change the migration status of an object after the analyze migration impact process is complete. See Toggle Import Status on page 5-40. Adds text to the migration entity so you can define the migration package. See Add Text to Entity on page 5-10. Adds text to a relation so you can define the purpose of that relation. See Add Text to Relation on page 5-11. Provides access to user-written software to perform custom processing on any entity. This is a standard repository action. Unlocks an entity, which allows others to make changes to the entity. This is a standard repository action. Lets you update any of the attributes that define your user ID. This is a standard repository action. Provides access to user-written software to perform custom processing on any relation. This is a standard repository action.
PROJECTS Change projects RANALYZE Detect objects to be rebuilt REFRESH Refresh the screen REP Generate report RES View results of migration SRCH Search for keywords TOGGLE Toggle import status TXE Add text to entity TXR Add text to relation UEMTH Define user entity method UNLOCK Unlock entity UPROF Update user profile URMTH Define user relation method
The rest of this section describes each action, its attributes or options, and the end result or deliverable. The actions are in alphabetic order by the descriptive action name.
Add Entity
The Add Entity (ADDE) action is the create action common to all entity types. The created entity is called the migration entity, and all actions performed during migration source processing center around it. In the source environment, the ADDE action displays a blank Add an Entity panel where you can enter attribute values for a new migration entity. All source actions center around this entity. See Creating the Migration Package on page 2-4 for detailed instructions on adding the migration entity to the source repository. Once you complete source processing, you use the add entity action to create a migration entity in the target environment. The action displays a blank detail panel identical to the one generated in the source environment. However, the migration entity created in the target environment becomes the center for all migration target processing. See Creating the Target for Migration Package on page 3-1 for detailed instructions on adding the migration entity to the target repository.
5-3
Add Entity
Attributes
An attribute is a single characteristic of an entity or relationship. There are two types of attributes: User-defined Attributes System-generated Attributes
User-defined Attributes
Whenever you create a migration package in the repository, you must name the migration entity. You also have the option of adding a description or specifying the prefix of the data set where the migration information will be stored. Note
If you are adding a migration entity to the target repository, you must specify the prefix of the data set from which you are importing your information.
The first five attributes that appear on the Add an Entity panel are migration attributes (Figure 5-1) which identify the object and its status.
Figure 5-1 Migration attributes
Migration Attributes: Name . . . . . . . System Id . . . . . Description . . . . Dataset Prefix . . Migration State . .
. . . . .
. . . . .
. . . . .
. . . . .
. : . . :
DMV_VER2______________________ A12FF4 MIGRATE DMC FROM V1 TO V2_____ HPSOUT.M00001FF__ 14 N/A
The name and description attributes are user-definable. You can specify the data set prefix attribute or let the system generate the prefix. The system automatically generates the other attribute. Table 5-2 lists and describes the user-defined migration entity attributes.
Table 5-2 User-defined migration entity attributes Description Required. An alphanumeric string up to either 30 single-byte or 14 double-byte characters. No default. Optional. Up to 30 characters of text that explain the purpose of the migration to other Migration Facility users. No default value is generated. Although a description is optional, it is highly recommended because it makes the migration entity much more useful to other project members. Optional. An alphanumeric string up to 17 characters. The repository administrators should establish naming standards for data sets. If the data set name you type in is not valid, you will receive an error message once you try to export the migration package. The system generates the remainder of the 44-character data set name, adhering to mainframe naming conventions. If you leave the field blank, the system generates the entire data set name. User-defined attribute Name
Description
Data Set Prefix
5-4
Migration Actions
Add Entity
System-generated Attributes
As soon as you save the migration entity, the system generates the rest of the migration attributes and the audit attributes. Migration Attributes Migration attributes identify both the object and its status. The system does not generate values for description or name (the latter is required). The system ID and migration state are generated automatically. Table 5-3 lists and describes the system-generated migration attributes.
Table 5-3 System-generated migration entity attributes Description A default ID that consists of six single-byte characters. The first four characters are random alphanumeric characters. The starting string of characters is set at installation time, and the string is incremented with each new creation. The last two characters are the alphanumeric repository identifier that is also defined at installation. The state of the entity in the following migration jobs: export, analyze, import. Not Applicable means that the entity has not yet been seeded with one or more root entities. Submitted means that the job has been submitted and it is in the queue, but the job has not been processed. Executing means that the job has been submitted and it is being processed. Incomplete means that the job could not complete because of a JCL error. Successful means that the batch job ran successfully. Failed means that the job was submitted and the system processed it, but the job failed from a system or a job-related error. Exit the Migration Facility and browse the job results in the system utilities. Approved means that the results of the successful job have been approved, and you can now can go on to the next processing step. See Approve Migration on page 5-16 for more information. System-generated attribute
System ID
Migration State
Audit Attributes Audit attributes include fourteen fields that indicate who created or modified the object, as well as the time and date it was created or last modified (Figure 5-2).
Figure 5-2 Audit attributes
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Date . Time . Project User . . . . . . . . . . . . . . . . . . . : : : : : : : : : : : : : : 94/09/15 13:14 SS0222 94/09/15 13:14 SS0222 DEV 0001 SS0222 94/09/15 13:14 DEV SS0222 1 Audit Attributes: Date Created . . Time Created . . Created by . . . Date Maintained . Time Maintained . Maintained by . . Project . . . . . Change # . . . . Owner Id . . . . Local Maintenance Local Maintenance Local Maintenance Local Maintenance Version . . . . .
5-5
Add Keywords
The system automatically generates the values when you save the entity, and you cannot directly edit them. Table 5-4 describes the audit attributes.
Table 5-4 Audit attributes Description The date (year/month/day) the migration object was created. The time, based on a 24-hour clock, the migration object was created. The user ID of the individual who created the migration object. The date (year/month/day) the migration object was last modified. The time, based on a 24-hour clock, the migration object was last modified. The user ID of the individual who last modified the migration object. The name of the project in which the migration object was created. The number of times that the migration object has been updated. A value of 0001 indicates that the object has not been changed since it was created and 0002 indicates it has been changed and saved once since it was created. NOTE: The change number increases by one each time an object is saved, even if the object data do not change, or if only objects parts change. Owner ID Local Maintenance Local Date Local Time Local Project Local User Version The user ID of the individual who created the migration object. The user ID of the individual who created the migration object on the host. The date (year/month/day) the migration object was last modified on the host. The time, based on a 24-hour clock, the migration object was last modified on the host. The name of the project on the host in which the migration object was created. The user ID of the individual who last modified the migration object on the host. The repository version in which the migration object was created. Audit attribute Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project
Change #
Result
The migration entity is not complete until you add one or more root entities to it. At this stage, you can only list existing entities with the list entity (LE) action, maintain entities with the maintain entity (ME) action, or delete entities with the delete entity (DE) action.
Add Keywords
To reuse entities, developers must be able to find entities they can use in their applications. The keyword (K) action associates entity instances of different types with a particular subject. Defining consistent keywords lets you systematically search the repository for migration entities that you can reuse, as well as other reusable objects. See Creating the Migration Package on page 2-4 for instructions on adding keywords.
5-6
Migration Actions
Add Relation
Attributes
Keywords have no specific attributes. However, note that each word separated by a space is treated as an individual keyword, and that the total number of characters used for all of an entitys keywords cannot exceed 240.
Result
You can display or modify the keywords for a given entity by using the add keywords (K) action again. You can also search for keywords by using the search for keywords (SRCH) action.
Add Relation
The add relation (ADDR) action lets you include entities in the migration package by creating relations between the migration entity and the objects that you want to migrate. See Selecting Objects for Migration on page 2-8 for detailed instructions on adding a relation. You can add any one of the following relations to the migration entity at a time:
5-7
Add Relation
Figure 5-3
Relation Types Has-Root Identifier Has-Root Key Has-Root Location Has-Root Logical Process Has-Root Machine Has-Root Organization Has-Root Physical Event Has-Root Process Has-Root Project Is-A-Root-Of Rebuild Package Has-Root Relationship Has-Root Report Has-Root Rule Has-Root Section Has-Root Server Has-Root Set Has-Root State Has-Root Table Has-Root Transition Has-Root User Has-Root Value Has-Root View Has-Root Window
Has-Root Application Config. Has-Root Attribute Has-Root Bitmap Has-Root Business Object Has-Root Cell Has-Root Collection Has-Root Column Has-Root Component Has-Root Config. Unit Has-Root Current System Has-Root Data Store Has-Root Data Type Has-Root Database Has-Root Drawing Has-Root Entity Has-Root Event Has-Root Field Has-Root File Has-Root Form Has-Root Function Has-Root FSDM Scheme Has-Root FSDM Value Has-Root Group Profiles Group
Attributes
An attribute is a single characteristic of an entity or relationship. There are two types of attributes: User-defined Attributes System-generated Attributes
User-defined Attributes
Whenever you add relations to the migration entity, you must assign values for several attributes. On the Action Information pop-up panel, you only need to choose the relation type you want. The rest of the information on the panel is for your information, and you cannot change it. On the Add a Relation panel, you need to specify either the migration entity name or root entity name, depending on which entity you are adding the relation from. You also need to choose the migration
5-8
Migration Actions
Add Relation
scope. The system generates the audit information when you save the relation. Table 5-5 lists and describes each user-defined relation attribute.
Table 5-5 User-defined relation attributes Description Required. An alphanumeric string up to 30 single-byte or 14 double-byte characters. Must match the name of an existing migration entity. NOTE: The system populates this field if you are adding a relation from the migration entity. Required. An alphanumeric string up to 30 single-byte or 14 double-byte characters. Must match the name of an existing entity of the same type.a Required. The domain of available migration scopes. Entity Only means that only the entity and its parts, and none of its child objects, are part of the migration package. One Level means that the entity, as well as objects one level below it, are part of the migration package.b Prepare Hierarchy means that the entity, and the child objects needed to prepare the it, are part of the migration package. Entity Hierarchy means that the entity, as well as all of its child objects, are part of the migration package. Drawing means that the drawing object and all the objects in it are included in the package. User-defined attribute
Migration Name
Has-Root-Entity Name
Scope
a. The system populates this field if you are adding a relation from the root entity. b. When you export a rule that converses a window, using the One-Level scope, the windows view and field objects are also part of the export.
Migration Scope The migration scope can be a very useful tool for controlling what is migrated. The migration scope can be any of the following:
5-9
Add Relation
Figure 5-4 Entity Only One Level
Scope Types Entity Only scope is useful for moving an object when the scope of changes are selfcontained. Exporting one level below the entity hierarchy is useful for attaching new branches of an application to an existing application without moving the entire original application.a Prepare Hierarchy scope is useful for copying fixes to an existing application. Entity Hierarchy scope is useful for copying new branches of an application. Drawing scope is useful for exporting particular parts of an application. Exporting drawings, such as a window flow diagram, is useful for migrating only parts of an application and is a powerful way to migrate selectively. However, you must make sure to include all of the entities thatalthough not in the drawingare related to entities that are in the drawing. This is to ensure that all the entities that entities in the drawing inherit attributes from are included in the migration. Thus, it is important that your project management team establish naming standards so you will know how to query for the objects you need.
Prepare Hierarchy Entity Hierarchy
Drawing
a. A window cannot be exported as a seed to a migration entity using the one-level scope option. You can only use the entity hierarchy or prepare hierarchy scope options when using the window as the seed.
Scope is one of four methods used to control the contents of a migration. The other three methods are:
Selective export Toggle action Select objects to import by type or status Selects objects for the export action after impact analysis. See Selective Export for more information. Skips objects for the import action after impact analysis. See Toggle Import Status for more information. See Import Migration for more information.
System-generated Attributes
The system automatically populates the Migration Name or Has-Root-Entity Name fields, depending on which entity you are adding the relation from. As soon as you save the relation, the system also generates the audit attributes. Audit attributes include 12 fields that indicate who created or modified the object, as well as the time and date it was created or last modified. You cannot edit these field values directly. See Table 5-6 for a detailed description of the system-generated attributes.
Table 5-6 System-generated relation attributes Description The date (year/month/day) the relation was created. The time, based on a 24-hour clock, the relation was created. The user ID of the individual who created the relation. The date (year/month/day) the relation was last modified. The time, based on a 24-hour clock, the relation was last modified. The user ID of the individual who last modified the relation. The number of times that the relation has been updated. A value of 0001 indicates that the relation has not been changed since it was created and 0002 indicates it has been changed and saved once since it was created. NOTE: The change number increases by one each time an object is saved, even if the object data does not change, or if only its parts change. The date (year/month/day) the relation was last modified on the host. The time, based on a 24-hour clock, the relation was last modified on the host. The name of the project on the host in which the relation was created. The user ID of the individual who last modified the relation on the host. System-generated attribute Date Created Time Created Created by Date Maintained Time Maintained Maintained by
Change #
Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User
5-10
Migration Actions
Add Text to Entity
Table 5-6
System-generated relation attributes (Continued) Description The project version in which the relation was created.
System-generated attribute Version
Result
At this stage, you can list the root, or seed, entities that are included in the migration package with the list relation (LR) action, maintain the relation with the maintain relation (MR) action, or delete the relation with the delete relation (DR) action.
Add Text to Entity

Add text to your migration entity to describe the purpose of the migration package to other Migration Facility users. Include a brief description of the entitys purpose and the type of information it contains. For example, if you are migrating a fix into production, explain that in the text. See Creating the Migration Package on page 2-4 for instructions on adding text.
Attributes
Text has no specific attributes.
Result
You can display or modify the text for a given entity by using the add text to entity (TXE) action again.
Add Text to Relation

Add text to the relations between your migration entity and objects in the migration package. Use the text to describe the purpose and scope of the migration package to other Migration Facility users. Include a brief description of the relations purpose. For example, if you have attached the hierarchy of a new application that you are migrating for the first time, explain that in the text. See Creating the Migration Package on page 2-4 for instructions on adding text.
Attributes
Text has no specific attributes.
5-11
Analyzing the Migration Impact
Result
You can display or modify the text for a given entity by using the add text to relation (TXR) action again.

Before importing into the target repository, you must perform an impact analysis. This impact analysis is a what if report that informs you of the effect of a potential import. The analysis gives detailed counts of creates, updates, and deletes of all objects and object parts in the migration package, as well as which objects need to be prepared as a result of the migration. All actions to be applied to the target repository should be actions that you are expecting. The analyze migration impact (ANALYZE) action takes the unstructured sequential object data from the exported migration files, copies it to temporary files in the target environment, and compares objects in the migration package with those in the target environment. Table 5-7 summarizes some of the variables in the @MIGENVn INI file (where n is the repository version) that affect the analyze migration impact action. See Chapter 7, Setting Up the Environment for information about all of the @MIGENVn INI file variables.
Table 5-7 Variable RUN_DELTA RUN_DETAIL RUN_RBDETECTOR INI variables that affect the analyze action Description Determines whether the AppBuilder environment automatically runs a delta report with the analyze migration impact job. Determines whether the AppBuilder environment automatically runs a detail report with the analyze migration impact job. Determines whether the AppBuilder environment automatically analyzes rebuild impact with the analyze migration impact job. Specifies whether the system executes Seer-supplied exits during the analyze job. The Seer exit determines the pending record to be used for updating the target repository. Determines whether you need an authorized user to approve the migration process before you continue to the import job. Specifies whether the system executes user-supplied exits during the analyze job. The Seer exit determines the pending record to be used for updating the target repository.
SEEREXIT
SIGNAMI
USEREXIT
The RUN_DELTA variable in the @MIGENVn INI file determines whether or not the AppBuilder environment automatically runs a delta report with the analyze job. If you are migrating an application into a repository for the first time and you know there will be no changes, or deltasthen not running a delta report will improve the performance of your migration. Or you may choose to run a delta report at a later time. The FAST_PATH_RUN_DELTA variable in the @MIGENVn INI file controls whether AppBuilder automatically runs a delta report with the analyze job when using migrating without migration files. See Migrating Without Migration Files on page 5-17 for more information. Note
You can run a delta report manually, regardless of how you set these variables.
5-12
Migration Actions
The RUN_DETAIL variable in the @MIGENVn INI file determines whether the AppBuilder environment automatically runs a detail report with the analyze job. If you know you will run a detail report after the analyze job, then you can save time by running it automatically. However, not running a detail report improves the performance of your migration. The RUN_RBDETECTOR variable in the @MIGENVn INI file determines whether the AppBuilder environment automatically analyzes rebuild impact with the analyze migration impact job. You may not always want an analyze rebuild impact if you do not plan to rebuild (for example, if you intend to merely warehouse the results of a migration). Note
You can analyze rebuild impact manually, whether you run it automatically with the analyze job.
If the SEEREXIT and the USEREXIT are both enabled, the system processes the SEEREXIT first. See Appendix C, Migration Exits for more information. The SIGNAMI variable determines whether you need an authorized user to approve the migration process before you continue to the import job. If you are migrating automatically, the Automated Migration Facility fails at the import job if you are not authorized to import.
Options
Whenever you analyze the impact of a migration, the system by default uses the options selected during export processing and the migration-file data set name specified when you created the migration package. The migration-file data set name specifies the file the data is to be imported from. Table 5-8 lists and describes each analyze option.
Table 5-8 Analyze options Description Required only if this is not the first attempt. Reload means that the analyze action will resubmit the whole job. You must reload if you make any changes in the source repository. Restart means that the analyze action will start the job from the step that failed. Specify the migration data set prefix. Process option
Execution options
Migration Data Set Prefix
Migration Status Values

The analyze process tags each object part in a migration package with one of the migration status values listed in Table 5-9. In addition to the various status values, objects are marked to be reprepared during rebuild if the migration process has changed any significant attributes. Status value descriptions are detailed in: Rolled-up Status Values Reanalyzing Importing Part of the Migration Package Pausing for Impact Analysis Collisions
5-13
Table 5-9
Migration status values Description The object in the target repository is exactly the same as the object in the migration package. The import process will create the object in the target environment because no object matches the one in the migration package. An object in the migration package matches the name or system ID of an object in the target environment, but is otherwise different. The import process will update the object in the target environment. An object in the target repository matches an object in the migration package, but it has one or more relationships or object partstext, keywords, or source codethat the migration package lacks. The import process will delete any such extra relationships or parts so that the target object matches the migration package object. An object in a migration package has the same name as an object in the target environment, but a different system ID. In addition, a collision is marked if the value of the ANALYZEKEY is L (for long name), if objects have the same system ID but different names.
Status value Unchanged Import will Create
Import will Update
Import will Delete
Unresolvable Collision
Rolled-up Status Values The status value for the entity and its high-level relationship is called the rolled-up status value, as each of an objects extended attributes, or parts (text, keywords, and source), also has a status value. If all parts present for an object have a status of Import will Create, the objects status is rolled-up to Import will Create. If only some of the parts have a status of Import will Create, the entity itself will have a status of Import will Update. When the status is Import will Delete, only the relationship (not the parent or child entity) will be deleted. Reanalyzing You can restart or reload the analyze migration impact action. Restart continues migration processing from the last phase that completed successfully. Select the Restart option to start the job from the internal step that failed. Reload starts the migration over again from the beginning. Select the Reload Migration Files option to resubmit the analyze job from the beginning. Importing Part of the Migration Package Even if you cannot correct the condition, you may still be able to go on to import processing depending on what object part is causing the failure. You can run an application without the text and keyword object parts, but you cannot run an application without the entity, relation, and source code object parts. Therefore, if the text or keyword object parts are causing the failure, you can exclude the text and keyword processing options and return to process them later. See Import Migration and Toggle Import Status for more information. Pausing for Impact Analysis Set the variable SIGNAMI in the @MIGENVn file to Y to specify that an authorized user must approve the migration results before you continue to the import step. If you are not an authorized user, MIGRATE fails after impact analysis. Run the RES action to verify that MIGRATE failed for this reason.
5-14
Migration Actions
Once the repository administrator has reviewed the impact analysis and run the APPROVE action, you can resume automated migration by selecting Import Migration in the MIGRATE options window. Collisions When the value of the ANALYZEKEY value in the @MIGENVn INI file (where n is the repository version) is set to S (for system ID) and an object in a migration package has the same system ID as an object in the target environment but a different name, the AppBuilder environment updates the target object with the source name, unless a target object with a different system ID has the same source name. In this case, the AppBuilder environment marks a collision. If the source and target objects have the same name but different system IDs, the AppBuilder environment marks a collision. When the value of the ANALYZEKEY value in the @MIGENVn INI file is set to L (for long name), and an object in a migration package has the same system ID as an object in the target environment but a different name, the AppBuilder environment marks a collision. The AppBuilder environment also marks a collision for the reverse condition: the source and target objects have the same name but different system IDs. Table 5-10 summarizes how the value of the ANALYZEKEY variable affects when collisions are marked.
Table 5-10 Results based on ANALYZEKEY ANALYZEKEY S S L L Long name Different Same Different Same System ID Same Different Same Different Result Updates the target unless a different system ID has the same name (which is a collision) Updates the target unless a different name has the same system ID (which is a collision) Collision Collision
Normally, the analyze action detects collisions. If a collision is detected and you intend to rebuild, you must change the name of one of the objects. Remember that if you change the object in the target environment, you must reanalyze the migration package. If you change the object in the source environment, you must export the object again before you rerun the analyze job. If you are sure that there are no collisions, and you want to enhance performance, you can turn off collision detection. Risk of collisions is low when you use a fixed migration path, for example, Development to Quality Assurance to Production. Risk of collisions is high when you use a repository to store or collect pieces of applications. See Chapter 7, Setting Up the Environment for more information. Even if the analyze job finds collisions, you can still import the objects if the RUN_IMP_IF_COLLISION variable in the @MIGENVn INI file is set to Y. However, proceeding with the import may result in a disjointed hierarchy. Caution
Make sure you understand the ramifications of importing objects that will collide with objects in the target repository.
5-15
Approve Migration
Result
The analyze migration impact action submits a batch job to fulfill your request. Once the job has finished, you can review the results online in three ways: Refresh the Maintain an Entity panel (press F19) to see the current Migration State attribute. The state reflects the submission, execution, success, or failure of the job. Record the job number that is displayed after you submit the analyze job, then use SDSF to get detailed job status information. Look at the messages associated with analyze processing. If the RES_TO_FILE variable in the @MIGENVn INI file has a value of Y, use the view results of migration (RES) action to view migration system messages online in the AppBuilder environment. If the RES_TO_FILE variable has a value of N, exit the AppBuilder environment and browse the job results in the system utilities. See Chapter 7, Setting Up the Environment for more information. After the analyze job has completed, you can use the following actions to examine the migration package: Use the list migration contents (LISTMIG) action to view the migration impact results. From the List Migration Contents panel use one of the following: Delta (DELTA) action to view specifically which object parts are changing Toggle (TOGGLE) action to manually exclude objects from the migration Use the list relation (LR) action to see which objects need to be prepared as a result of the migration. The resulting list has a migration will prepare message by each object to be prepared. Use the summary counts for migration (COUNT) action to display the number of objects in the migration package by migration status and migration type. Use the report on migration (REP) action to generate paper or online reports.
Approve Migration
The purpose of the approve action is to require a second user to sign off on the results of the analyze process. A manager or supervisor can then maintain control over what is imported to a target environment. To implement the Approve action, configure the migration environment variables. The SIGNAMI variable in the @MIGENV.INI file determines whether or not you need an authorized user to approve the migration process before you continue to the Import job. The Automated Migration Facility pauses just before the submission of the Import job so you can get an authorized user to sign-off on the process before it continues. The SIGNIMP variable determines whether or not you need an authorized user to approve the migration process before you continue to the Rebuild Analyze job. The Automated Migration Facility pauses just before the submission of the Rebuild Analyze job so you can get an authorized user to signoff on the process before it continues. The SIGNRBD variable determines whether or not you need an authorized user to approve the migration process before you continue to the Rebuild Prepare job. If you are migrating automatically,
5-16
Migration Actions
Automate Migration
the Automated Migration Facility pauses just before the submission of the Rebuild Prepare job so you can get an authorized user to sign-off on the process before it continues.
Options
You are notified that you must get another user to sign off so you can continue. Check with your repository administrator or project manager to find out who can approve the job. A manager or supervisor reviews the completed job and toggles any pending import values, if necessary. The designated individual then types APPROVE on the migration entity action line on the List Facility panel. The system displays the message: Approve a migration process for <entity> Processed. You can now continue with migration processing.
Result
The migration state changes to Analyze Approved, which is required for import processing. If the RES_TO_FILE variable in the @MIGENVn INI file has a value of Y, use the view results of migration (RES) action to view migration system messages online in the AppBuilder environment. If the RES_TO_FILE variable has a value of N, exit the AppBuilder environment and browse the job results in the system utilities. See Chapter 7, Setting Up the Environment for more information.
Automate Migration
The automate migration action offers you various degrees of automation for both source and target repository processing. Because you can select multiple commands at one time, you can choose to automate either source or target repository processing, or both. See Chapter 4, Automated Migration Processing for more instructions. Some of the reasons you might want to use automated migration are: You want to reduce manual intervention in the process. You are migrating to another version in the same repository. You are copying to a new repository or repository version. In an environment where there are no other objects, the results of analyze-migration-impact processing are inconsequential. Before you begin, make sure that your administrator has set up the migration INI files for both the source and target repositories, and correctly configured the relationship between the two repositories.
5-17
Automate Migration
Migrating Without Migration Files

Migrating without migration files is a faster way of automating migration, because it does not create migration data sets. Migration data sets are useful when you are planning to migrate to more than one target because you can reuse the same data sets. But when you know you will not be migrating to another target, and particularly If you are migrating to only another version in the same repository, migrating without migration files reduces processing time. To skip creating a migration data set, follow these steps: 1. From a List Migration Entity panel type MIGRATE in the Action field of the entity you want to migrate, as shown in Figure 5-5.
Migrating a migration entity
List Facility for Entity Migration Command ===> ____________________________________________________________ Repository: SUNRISE V: 1 Project: dev Level: 2
Figure 5-5
Action Name System Id MIGRATE_ DMC_VER2 AFVCNR ________ GVK_NO_RLTN ADBWNR ________ GVK_Q26 AFKXNR ________ GVK_TIP_AND_GROUP ABZ2NR ________ TEST_MIGRATION ABDRNR ******************************* BOTTOM OF DATA ****************************
2.
Press Enter. A panel is displayed where you select migration options, as shown in Figure 5-6.
Migration Options panel
Migration Migrate Options =======> ___________________________________________________________
Figure 5-6
Command
Name . . . . . . . . : DMC_VER2 Version . . . . . . : 1 Type 's' to select an option or type a space to deselect. Then press ENTER. Processing Options Methods to Process . . . . . . . . . .
S Export Migration S Analyze Migration S Import Migration

_ Rebuild Migration
3.
Select the migration methods you want and then press Enter. A pop-up panel is displayed. Type the repository ID and version for the target repository as shown in Figure 5-7.
Target Repository Options panel
Figure 5-7
----------------------------------------------------------------------------| Command =======> _______________________________________________________ | | | | Migrating across Repository and/or Version. | | Enter the required information then press ENTER. | | | | Target Repository Options | | Repository Id . . . . . . . . . . . . SUNRISE________________ | | Version . . . . . . . . . . . . . . . 2 | | | | | -----------------------------------------------------------------------------
4.
Press Enter. A final pop-up panel is displayed, as shown in Figure 5-8.
5-18
Migration Actions
Clean-up Migration Information
Figure 5-8
Typing over the name for the migration data set
----------------------------------------------------------------------------| Command === ____________________________________________________________ | | | | Type blank and press enter if you do not wish to create migration files | | | | Data Set Prefix for Migration Files . . . __________ | | | | | -----------------------------------------------------------------------------
Type spaces over any data set prefix that is displayed to eliminate the creation of a migration data sets.
Result
The migrate action automatically applies the actions you selected against a specified migration entity. If the RES_TO_FILE variable in the @MIGENVn INI file has a value of Y, use the view results of migration (RES) action to view migration system messages online in the AppBuilder environment. If the RES_TO_FILE variable has a value of N, exit the AppBuilder environment and browse the job results in the system utilities. See Chapter 7, Setting Up the Environment for more information.
Clean-up Migration Information

The clean-up migration information (CLEANUP) action deletes migration files and migration processing information from internal control tables. 1. 2. Type CLEANUP either on the command line of the migration entity Maintain an Entity panel or in the Action line on the List Migration Entity panel. Press Enter. Select each of the Delete options by typing an S in the selection field (Figure 5-9).
Migration Clean-Up Options panel
Migration Clean-Up Options Name . . . . . . . . : ROBIN Version . . . . . . : 1 Type 's' to select an option or type a space to deselect. Then press ENTER. Processing Options Delete Options . . . . . . . . . . . .
Figure 5-9
S Migration Information S Migration Result Files

_ Migration Source Files
Command
=======>
___________________________________________________________
Migration result files are the files you can browse with the RES (view results of migration) action: results, count, and detail. Migration information is the data in the database. Migration source files are the migration data sets, that is the output from the migration. You can also choose to delete the migration data sets, but only if the migration state is export successful.
5-19
Copy Migration Files
3.
A pop-up panel asks for confirmation (Figure 5-10). Type a 1 for Yes.
Clean-up confirmation panel
Figure 5-10
---------------- Confirm Request ----------------------| | | Are you sure you want to clean up the Migration? | | | | | | | | | | 1 1. Yes | | 2. No | | | | Command ===> ________________________________________ | --------------------------------------------------------
4.
The system displays the message:
Clean-up Migration Information for <entity> Processed.
Options
Choosing to delete migration information deletes the files that you created when the migration package was exported, the migration internal-control table data, the internal-control table data about each object imported and rebuild. Note
Use delete migration information only if you are finished processing your migration. If you still plan to rebuild the migration package, do not run this action until you are finished with the rebuild process.
Result
Migration files, migration backup files, and migration processing information from internal control tables are deleted. If the RES_TO_FILE variable in the @MIGENVn INI file has a value of Y, use the view results of migration (RES) action to view migration system messages online in the AppBuilder environment. If the RES_TO_FILE variable has a value of N, exit the AppBuilder environment and browse the job results in the system utilities. See Chapter 7, Setting Up the Environment for more information.
Copy Migration Files

Use the copy migration file action to copy migration files from one storage device to another. You might want to copy to another storage device for these and other reasons: Copy migration files from DASD to DASD to make a backup copy of an application Copy migration files from DASD to tape to ship them to another location Copy migration files from tape to DASD to load a backed-up application To copy migration files: 1. After completing the export process, type COPYMIG on the action line of the migration entity from which, or to which, you want to copy. Press Enter.
5-20
Migration Actions
Count Migration Contents
2. 3.
On the Copy Migration Files panel, type the name of the data set to which you are copying the migration files. In the storage field, type D to store to DASD or T to store to tape. Press Enter. The system displays the message:
Copy Migration Files for <entity> Processed.
Options
You choose the data set prefix and media (DASD or tape) for both the source and the target. For tapes, specify the volume serial number and whether you want the migration target tape to be cataloged and the tape retention period.
Result
The migration files are copied to DASD or tape. If the RES_TO_FILE variable in the @MIGENVn INI file has a value of Y, use the view results of migration (RES) action to view migration system messages online in the AppBuilder environment. If the RES_TO_FILE variable has a value of N, exit the AppBuilder environment and browse the job results in the system utilities. See Chapter 7, Setting Up the Environment for more information.
Count Migration Contents

The COUNT action counts the total number of entities in a migration package and the number of entities in a migration package by status and migration type. Running a count provides a fast way to check the success of the methods. For example, the count at the end of the export job is 10,000 objects. If the count at the end of the import job is 9,500 objects, you know you lost 500 objects during the process and you can troubleshoot from that point.
Options
The RUN_COUNT variable in the @MIGENVn INI file specifies whether the AppBuilder environment runs a count of objects included in the migration package with every method. Not running counts improves performance. Note
You can still run the count migration contents (COUNT) action, regardless of how this variable is set.
Result
If the RES_TO_FILE variable in the @MIGENVn INI file has a value of Y, use the view results of migration (RES) action to view migration system messages online in the AppBuilder environment. If the RES_TO_FILE variable has a value of N, exit the AppBuilder environment and browse the job results in the system utilities. See Chapter 7, Setting Up the Environment for more information.
5-21
Delete Entity
Delete Entity
The delete entity (DE) action deletes a migration entity. The clean-up migration information (CLEANUP) action runs in the background. The DELMIG variable in the @MIGENVn INI file determines whether you can delete a migration entity. See Chapter 7, Setting Up the Environment for more information.
Delete Relation
The delete relation (DR) action deletes a relation between a migration entity and a root entity. Use the delete relation action to delete any entities you do not want in the migration package. First, use the list relation (LR) action next to the migration entity you want to delete a relation from. Then use the delete relation (DR) action next to the relation you want to delete. The result of the DR action is the same as the clean-up migration information (CLEANUP) action. Both actions delete migration files and migration processing information from internal control tables.
Detect Objects to be Rebuilt

You can view the list of objects to be rebuilt with the detect objects to be rebuilt relations (DR) action. The DR action analyzes rebuild impact and you view the results with a list relations (LR) action after the analyze has completed successfully.
Options
The RUN_RBDETECTOR variable in the @MIGENVn INI file determines whether the AppBuilder environment automatically analyzes rebuild impact with the analyze migration impact job. Note
You can analyze the rebuild impact manually, whether or not you run it automatically with the analyze job. Type RANALYZE next to the migration entity to analyze rebuild impact manually.
Result
If the RES_TO_FILE variable in the @MIGENVn INI file has a value of Y, use the view results of migration (RES) action to view migration system messages online in the AppBuilder environment. If the RES_TO_FILE variable has a value of N, exit the AppBuilder environment and browse the job results in the system utilities. See Chapter 7, Setting Up the Environment for more information.
5-22
Migration Actions
Export Migration
Export Migration
The export (EXPORT) action copies the objects defined in the migration from the repository to migration files on DASD. The objects are exported to files outside the repository environment so they can be backed up or imported into another environment.
Options
Migration entity text, source, and keywords are included in migration processing by default. Type a space in the selection field to exclude any of those parts. If you exclude any parts from the migration package, those parts will not be exported with the migration package. The migration-file data set name specifies the file where the information is to be stored. Table 5-11 lists the export options.
Table 5-11 Export options Process option Text Source Keywords Migration Data Set Prefix Selective Export Description Type a space in the selection field to exclude text from the migration package. Type a space in the selection field to exclude source from the migration package. Type a space in the selection field to exclude keywords from the migration package. The system fills in the migration data set prefix specified during the add-an-entity process. Choose Yes or No to import selected objects or not.
Some repository administrators do not permit users to override the default processing options. Contact your administrator if you have any questions. The export (EXPORT) action generates 13 standard migration files. The export method has a panel where the high level qualifier for the 13 standard data sets can be specified. The default high level qualifier is defined as the variable mig_file_id in the @MIGENVn INI file.
Result
The export (EXPORT) action submits a TSO program to fulfill your request. Once the job is finished, you can review the results online by doing one of the following: Refresh the Maintain an Entity panel (press F19) to see the current Migration State attribute. The state reflects the submission, execution, success or failure of the job. Record the job number that is displayed after you submit the export job, then use SDSF to get detailed job status information. If the RES_TO_FILE variable in the @MIGENVn INI file has a value of Y, use the view results of migration (RES) action to view migration system messages in the AppBuilder environment. If the RES_TO_FILE variable has a value of N, exit the AppBuilder environment and browse the job results in the system utilities. See Chapter 7, Setting Up the Environment for more information. After the export is finished, use the list migration contents (LISTMIG) action to display each entity, its parts, and whether import will create, update, or delete those parts or leave them unchanged. The EXP_COMMIT variable in the @MIGENVn INI file controls how import processing handles commits and rollbacks if an export job fails. If the variable has a value of 0, then commits and rollbacks
5-23
Export Migration
are performed at the migration level. Any error incurred during export processing will result in the rollback of the entire migration package. You may experience DB2 contention problems when EXP_COMMIT is set to 0 or a low value. On the other hand, setting the value of EXP_COMMIT variable to a high value results in poor performance because of DB2 overhead. Once you determine what caused the failure and have corrected that condition, you can reload export processing.
Selective Export
Selective export is a powerful way of controlling the contents of a migration. You should know the hierarchy and data in the migration, which must already exist in the target. (However, you cannot use selective export between a 5.2x and version 5.3x repository.) Follow these steps to use selective export: 1. 2. From a List Migration Entity panel type EXPORT and press Enter. The Migration Export Options panel is displayed, as shown in Figure 5-11. Type 1 in the Selective Export field and press Enter.
Migration Export Options panel
Migration Export Options ___________________________________________________________
Figure 5-11
Command
=======>
. . . . . . .
S Text S Source S Keywords
Data Set Prefix for Migration Files
. Seerout.export___
3.
The Selective Export panel is displayed, as shown in Figure 5-12. Type the entity type and any other properties you want to include or exclude.
5-24
Migration Actions
Export Migration
Figure 5-12
Selective Export panel
---------------------------- Selective Export ---------------------------| | | Enter the desired information or type ? on a field. Then press ENTER. | | | | Condition Value(s) | | Entity Type ?________ ___________________________________________________ | | ___________________________________________________ | | ___________________________________________________ | | | | (((( Property Cond Value(s) )))) Op | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | | | Command ==> ______________________________________________________________ | ----------------------------------------------------------------------------
4.
If you type a question mark (?), in the Condition field, a pop-up panel is displayed from which you can select the condition for the entity type, as shown in Figure 5-13.
Field-level help for Condition
---------------------------- Selective Export ---------------------------| ---------- Conditions ----------- | | Enter the desired information or type | | | | | | | | Condition Value(s) | ENTITY | | | Entity Type ?________ ______________ | | | | ______________ | _ IN | | | ______________ | _ NOT IN | | | | _ ALL | | | (((( Property Cond Valu | ************** BOTTOM OF DATA ** | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | | | | | Command ==> _________________________ | | | ----------------------------------------------------------------------------
Figure 5-13
If you type a question mark (?) in the Value(s) field, a pop-up panels display the entity types in your current repository (Figure 5-14).
5-25
Export Migration
Figure 5-14
| | | | | | | | | | | | | | | | | | | | |
Values Selection list panel
----- Value Selection List
-----| | ENTITY IN | | _ APPCFG | _ ATTRIB | _ BITMAP | _ BMPIMP | _ BUSOBJ | _ CELL | _ CFGUNIT | _ COLLECT | _ COLUMN | _ COMP | _ CURSYS | _ CUST | _ CUSTGRP | _ DATA | _ DATABAS | | | ----------------------------------
Scroll to see other values. The values that are available for entity type are shown in Table 5-12.
Table 5-12 Entity Types
APPCFG ATTRIB BITMAP BMPIMP BUSOBJ CELL CFGUNIT COLLECT COLUMN COMP CURSYS CUST CUSTGRP DATA DATABAS DRAWNG ENT
ENTITY EVENT EXEC FILE FLD FORM FSCHEME FUNC FVALUE GROUP HELP HLPTXT IDENT REPORT REPOSIT RLN RULE
SECTN SERVER SET SOURCE SOURCEB STATE STORE SYMBOL TABLE TEXT TRANS USER VALUES VIEW WINCON WINDOW WKNGRP WKSN
If you type a question mark (?) in the Property field, a pop-up panel is displayed with a list of properties you can select, as shown in Figure 5-15.
5-26
Migration Actions
Export Migration
Figure 5-15
Values for the Property field
---------------------------- Selective Export ---------------------------| ---------- Properties ----------- | | Enter the desired information or type | | | | | | | | Condition Value(s) | | | | Entity Type ALL______ ______________ | | | | ______________ | _ DATE MAINTAINED | | | ______________ | _ MAINTAINED BY | | | | _ OWNER ID | | | (((( Property Cond Valu | _ PROJECT | | | (___ ?_______________ ________ ____ | _ QA STATUS | | | ____ ________________ ________ ____ | ************** BOTTOM OF DATA ** | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | ____ ________________ ________ ____ | | | | | | | | Command ==> _________________________ | | | ----------------------------------------------------------------------------
If you type a question mark (?) in the set condition (Cond) field, a pop-up panel displays values that you can select (Figure 5-16).
Figure 5-16 Values for the set condition field
---------- Conditions ----------| | | | | DATE MAINTAINED | | | | _ BETWEEN | | _ IN | | _ NOT IN | | ************** BOTTOM OF DATA ** | | | | | | | | | | | | | | | | | | | | | | | | | | | ----------------------------------
If you type a question mark (?) in the conditional operation (Op) field, a pop-up panel displays the two values you can select (Figure 5-17 on page 5-27).
5-27
Export Migration
Figure 5-17
| | | | | | | | | | | | | | | | | | | | |
Values for the conditional operation field
----------- Cond Ops
-----------| | PROJECT | | _ AND | _ OR | ************** BOTTOM OF DATA ** | | | | | | | | | | | | | | | ----------------------------------
If you select all ANDs or all ORs for your selective export filter, the system automatically inserts the appropriate parentheses. However if you use a combination of AND and OR, you need to make sure you have the correct parentheses. Figure 5-18 shows a Selective Export panel filled in selecting all rules (and all the relationships in which the rules participate as parents) maintained between January 1, 1995 and November 15, 1995. Specify a range of values by separating the values with commas. Also, note that you need to type the leading zeros for single digit months or days. The format for the date must match the format of the Date Maintained (YY/MM/DD).
Figure 5-18 Completed Selective Export panel
---------------------------- Selective Export ---------------------------| | | Enter the desired information or type ? on a field. Then press ENTER. | | | | Condition Value(s) | | Entity Type IN_______ RULE_______________________________________________ | | ___________________________________________________ | | ___________________________________________________ | | | | (((( Property Cond Value(s) )))) Op | | (___ DATE_MAINTAINED_ BETWEEN_ 95/01/01,95/11/15_______________ )___ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | ____ ________________ ________ ________________________________ ____ ___ | | | | Command ==> ______________________________________________________________ |
When you have finished selecting what you want to export, a pop-up confirmation panel is displayed, as Figure 5-19 shows.
5-28
Migration Actions
Export Migration
Figure 5-19
Selective Export confirmation panel
------------------- Confirm Request -------------------| | | Selective export filter was defined. Do you wish | | to use it for this export? | | | | | | | | 1 1. Yes | | 2. No | | | | Command ===> ________________________________________ | --------------------------------------------------------
Note
The export job does not create a recoverable unit of work. Therefore, you can reload, but not restart, the export job.
Selective Export Result

The export job produces three results files that you can view with the RES action: Result, Count, and Detail. The Results file tells the date and time the job started and ended, and whether the job was successful or failed. Figure 5-20 shows the Count Report from the selective export results.
Figure 5-20 Count report for selective export results
Repository File Browser Name . . . . . . . : DMC_VER2 Version . . . . . : 1 ********************************* TOP OF DATA ********************************** Count Report for Migration DMC_VER2 Version 1 produced on 95/11/28 at 17:46:56. Migration Status Tot Count Ent Count Rel Count ------------------------------ ---------- ---------- ---------Exported 279 58 221 ------------------------------ ---------- ---------- ---------All 417 72 345 End of Report ******************************** BOTTOM OF DATA ********************************
Figure 5-21 shows the first panel of information from the Detail Report for the selective export results.
Figure 5-21 Detail report for selective export results
--------- SEEROUT.SR1.AGM6SR.EXPORT.DETAIL --------- LINE 00000000 COL 001 080 Repository File Browser Name . . . . . . . : DMC_VER2 Version . . . . . : 1 ********************************* TOP OF DATA ********************************** Detail Report for Migration DMC_VER2 Version 1 produced on 01/11/28 at 17:46:56. ******************************************************************************** Exported Entity Rule WXT_RULE_BATCH Exported Relation Rule WXT_RULE_BATCH Owns View WXT_VIEW_RULE_IO Exported Entity Rule WXT_RULE_BATCH_DB2 Exported Relation Rule WXT_RULE_BATCH_DB2 Owns View WXT_VIEW_RULE_IO Exported Entity Rule WXT_RULE_BATCH_DRIVER Command ===> ________________________________________________ Scroll ===> PAGE
5-29
Generate a Delta Report
Generate a Delta Report

Use the generate delta report (DELTA) action in conjunction with the list migration contents (LISTMIG) action to see the exact difference or change (delta) between two versions of an object or objects. Analyze processing assigns import status values to objects in a migration package. The Will be Updated value means that, although two objects share the same key valuethe same name or system IDthe two objects are different. If two objects are precisely the same, then the object in the migration package is tagged Unchanged. If the migrated version is imported, it overwrites the version in the target environment. The generate delta report action lets you compare the two objects, and decide whether you want to import the migrated version or toggle the import status to Skip Import. See Toggle Import Status. Follow these steps to generate a delta report: 1. 2. 3. 4. Use the list migration contents (LISTMIG) action to navigate to the List Contents panel. Select the Migration Status field of the objects you want to view. Type DELTA on the action line of the object you want to compare. Press Enter to view the delta report.
The RUN_DELTA variable in the @MIGENVn INI file determines whether or not the AppBuilder environment automatically runs a delta report with the analyze job. If you know you will run a delta report after the analyze job, you can save time by running it automatically. However, if you are migrating an application into a repository for the first time and you know there will be no changes, then not running a delta report will improve the performance of your migration. The FAST_PATH_RUN_DELTA variable in the @MIGENVn INI file controls whether the AppBuilder environment automatically runs a delta report with the analyze job when migrating without writing migration files. See Migrating Without Migration Files for more information. REFER TO FASTPATH DISCUSSION Note
You can run a delta report manually, regardless of how you set this variable.
See Chapter 7, Setting Up the Environment for more information.
Result
The system generates an online Migration Delta report.
Generate a Report
Use the generate report (REP) action to print information about a migration entity. You can generate a migration report, which can include a delta report, a count report, or a detail report. The delta report lets you see the exact differences or changes (deltas) that will be made to objects during a migration. The count report shows a count of the entities and relationships to be migrated.
5-30
Migration Actions
Import Migration
1. 2.
Navigate to the migration Maintain an Entity or List Entity panel. Type REP on the command line and press Enter, as shown in Figure 5-22.
Generating a report from the List Entity panel
List Facility for Entity Migration Command ===> _____________________________________________________________ Repository: SUNRISE V: 1 Project: DEV Level: 2
Figure 5-22
System Id AFTQNR ________ GVK_Q26 AFKXNR ________ GVK_Q26B AFMHNR ________ KMM_RPW_APPS ADMBNR ________ KMM_RUNM_AA_AB_WIN AD7WNR ________ TEST_MIGRATION2 ABDTNR ******************************* BOTTOM OF DATA *****************************
REP_____ DMC_VER2
Action
Name
3.
Press Enter. A panel is displayed where you can select the type of report you want, as shown in Figure 5-23. Select which reports you want to generate by typing S in the appropriate selection fields.
Migration Reporting Options panel
Migration Reporting Options ________________________________________________________
Figure 5-23
Command
=======>
Name . . . . . . : DMC_VER2 Version . . . . : 1 Type 's' to select an option or type a space to deselect. Then press ENTER. Processing Options Reports to Generate
. . . . . . . . . .
S Delta Report S Detail Report

_ Count Report
4.
Press Enter to print the report and return to the Maintain an Entity or List Entity panel. The system displays the message:
Migration Report for <entity> Processed.
Result
The system generates a paper report. If the RES_TO_FILE variable in the @MIGENVn INI file has a value of Y, use the view results of migration (RES) action to view migration system messages online in the AppBuilder environment. If the RES_TO_FILE variable has a value of N, exit the AppBuilder environment and browse the job results in the system utilities. See Chapter 7, Setting Up the Environment for more information.
Import Migration
The import (IMPORT) action copies the migration objects from temporary files and tables to the target repository. Successful completion of the analyze migration impact (ANALYZE) action and a careful review of the analysis precede successful import migration processing.
5-31
Import Migration
Options
You can choose to import all of the object parts analyzed, or a subset of those parts. You can further limit the scope of a migration package by selecting import options, which include or exclude objects depending on the status value they were assigned by the analyze process. Table 5-13 describes each import option.
Table 5-13 Import options Process option Text Source Keywords Create Update Delete Description Type a space in the selection field to exclude text from the migration package. Type a space in the selection field to exclude source from the migration package. Type a space in the selection field to exclude keywords from the migration package. Type a space in the selection field to exclude objects tagged Import will Create from the migration package. Type a space in the selection field to exclude objects tagged Import will Update from the migration package. Type a space in the selection field to exclude objects tagged Import will Delete from the migration package.
The PRTEXT, PRSOURCE, PRKEYS, PRCREATE, PRUPDATE, and PRDELETE variables in the @MIGENVn INI file specify which default values are used for the import processing options. The OVTEXT, OVSOURCE, OVKEYS, OVCREATE, OVUPDATE, and OVDELETE variables in the @MIGENVn INI file specify whether you can override the default values for the import processing options. For example, the defaults are set to process all object parts and statuses. Your administrator might let you override the text and keywords process options, but not the source process option, because you need source to run your application. Some of the migration entity audit attributes are tagged significant or insignificant. The significant valuesChange #, Local Maintenance, Local Date, Local Time, Local Project, and Local Userretain source values, regardless of the migration status value assigned by the analyze process. Retaining the source value of these attributes provides a more accurate trail of audit information. The RESPECT_IMP_LOCK variable determines whether or not locked objects are imported. The import fails if an object does not import because it is locked. If the analyze job finds collisions, you can still import the objects if the RUN_IMP_IF_COLLISION variable in the @MIGENVn INI file is set to Y. However, proceeding with the import may result in a disjointed hierarchy. Caution
Make sure you understand the ramifications of importing objects that will collide with objects in the target repository.
The SIGNIMP variable determines whether you need an authorized user to approve the migration process before you continue to the rebuild analyze job. If you are migrating automatically, the Automated Migration Facility fails at the rebuild analyze job if you are not authorized to analyze the rebuild.
5-32
Migration Actions
Import Migration
Result
The import (IMPORT) action submits a batch job to fulfill your request. Once the job has finished, you can review the results online in three ways: Refresh the Maintain an Entity panel (press F19) to see the current Migration State attribute. The state reflects the submission, execution, success, or failure of the job. Record the job number that is displayed after you submit the import job, then use SDSF to get detailed job status information. Look at the messages associated with import processing. If the RES_TO_FILE variable in the @MIGENVn INI file has a value of Y, use the view results of migration (RES) action to view migration system messages online in the AppBuilder environment. If the RES_TO_FILE variable has a value of N, exit the AppBuilder environment and browse the job results in the system utilities. See Chapter 7, Setting Up the Environment for more information. The IMP_COMMIT variable in the @MIGENVn INI file controls how import processing handles commits and rollbacks if an import job fails. If the variable has a value of 0, any error incurred during import processing will result in the rollback of the entire migration package. Once you determine what caused the failure and have corrected that condition, you can rerun both analyze and import processing. If the IMP_COMMIT variable has a numerical value greater than 0, then commits and rollbacks are performed at the object level. Any error incurred during import processing will result in the rollback of the last n number of imported objects, where n is the value of the IMP_COMMIT variable. The rollback includes the specified number of objects and all of their parts: keywords, relations, source code, and text. You may experience DB2 contention problems when IMP_COMMIT is set to 0 or a low value. On the other hand, setting the value of IMP_COMMIT variable to a high value results in poor performance because of DB2 overhead. Once you determine what caused the failure and have corrected that condition, you can rerun import processing, but not analyze processing. Caution
If you rerun analyze processing in this case, the information needed for rebuild processing is lost for rebuilding at the migration entity level. (If the IMP_COMMIT variable is 0, you can rebuild at the migration entity level.)
If you cannot correct the condition, you must still move forward with import processing. Exclude only the processing option of the object part that failed during processing. Import and rebuild the object parts that were successful. Rebuild from the function level instead of from the migration package entity. After you finish the import and the rebuild, return to the failed part, correct the condition, and process it again. For example, if importing source code fails, exclude source code from the migration package. Import and rebuild the rest of the object parts. Then return to correct the condition causing the failure, and rerun analyze and import. When you reanalyze the failed partsinstead of analyzing the entire migration packageyou must rebuild from the level where you started the analyze, export, and import. Refer to Enterprise Rebuild Guide for more information about rebuild.
5-33
List Migration Contents

Use the list migration contents (LISTMIG) action to see the exact contents of the migration package, as well as to select processing options on an object-by-object basis. The list migration contents action lists all objects in the migration package, so you can see exactly what was updated or created in the repository. You can filter the report to include or exclude entities and relations from the migration contents list that the system generates. A filter summary provides a count of total objects, filtered objects, filtered entities, and filtered relations. The entity and relation filters allow you to select what types of entities and relations to include in your migration contents list. Using the filters to get a report that lists only the objects of interest speeds processing considerably.
Using Filters to List Migration Contents

Follow the steps below to apply filters to your list of migration contents: 1. 2. Type LISTMIG on the migration entity action line. On the command line, type FILTER MODIFY to change the filter options (Figure 5-24).
Modifying filter settings
Figure 5-24
List Contents of Migration DMC_VER2 Version 1 Command =======> FILTER MODIFY_______________________________________________ Type 's' to select an option or type a space to deselect. Then press ENTER. Type FILTER ON/OFF/MODIFY on command line for filter processing. Display Parts Y Migration Status _ All _ Exported Total Count 2097 2097 Entity Count 915 915 Relation Count 1182 1182
******************************* BOTTOM OF DATA ******************************
3.
A pop-up panel displays a list of entities in the migration package to select for filtering (on the left side of the panel) and a summary of the current filter settings (on the right side of the panel), as shown in Figure 5-25.
5-34
Migration Actions
Figure 5-25
Selecting entities for filtering
-----------------------------------------------------------------------------| List Contents of Migration DMC_VER2 Version 1 | |------------------------------------------------------------------------------| |---------- Entity Filter ---------------------- Filter Summary -------------| | | | | | | | | | | | | | Press ENTER to apply selection. | | Counts: | | RIGHT/LEFT will toggle to the next filter. | | Total......... 2097 | | | | Filtered...... 81 | | _ All | | | | S Component | | Filters: | | _ Field | | Entity ....... Filtered | | _ File | | Project ...... All | | _ Function | | Relation ..... None | | _ Process | | | | _ Report | | | | S Rule | | | | _ Section | | | | _ Set | | | | _ Value | | | | _ View | | | | | | | ------------------------------------------------------------------------------
4.
Press F11 to display a pop-up panel on which you can select the relations in the migration package for filtering, as shown in Figure 5-26.
Selecting relations for filtering
Figure 5-26
---------------------------------------------------------------------------| List Contents of Migration DMC_VER2 Version 1 | |----------------------------------------------------------------------------| |-------------- Relation Filter ---------------------- Filter Summary -----| | | | | | | | | | Press ENTER to apply selection. | | Counts: | | RIGHT/LEFT will toggle to the next filter. | | Total......... 2097 | | | | Filtered...... 81 | | _ All | | | | _ Component Refers-To Set | | Filters: | | _ File Owns View | | Entity ....... Filtered | | _ Function Refines-Into Process | | Project ...... All | | _ Process Is-Defined-By Rule | | Relation ..... Filtered | | _ Report Contains Section | | | | S Rule Accesses File | | | | _ Rule Converses Report | | | | _ Rule Owns View | | | | _ Rule Refers-To Set | | | | S Rule Uses Component | | | | | | | | | | | | ************** BOTTOM OF DATA ************** | | | ----------------------------------------------------------------------------
5.
Press F11 again to display a pop-up panel on which you can apply filtering to projects in the migration package, as shown in Figure 5-27.
5-35
Figure 5-27
Selecting projects for filtering
---------------------------------------------------------------------------| List Contents of Migration DMC_VER2 Version 1 | |----------------------------------------------------------------------------| |--------------- Project Filter ----------------------- Filter Summary -----| | | | | | | | | | Press ENTER to apply selection. | | Counts: | | RIGHT/LEFT will toggle to the next filter. | | Total.......2097 | | | | Filtered......82 | | _ All | | | | S DEV | | Filters: | | _ ISP | | Entity ....... Filtered | | _ MI | | Project ...... Filtered | | _ PM | | Relation ..... Filtered | | _ QA | | | | _ SEER1 | | | | _ SEER2 | | | | _ TR | | | | _ TRNG | | | | | | | | | | | | | | | | ************** BOTTOM OF DATA ************** | | | ----------------------------------------------------------------------------
6.
On the resulting List Contents of Migration panel, type Y for Yes or N for No in the Display Parts single-character field (Figure 5-28). Then type FILTER ON or FILTER OFF on the command line to use or not use the filter in generating the list. Press Enter.
Turning on the filter selections
Figure 5-28
List Contents of Migration DMC_VER2 Version 1 Command =======> FILTER ON___________________________________________________ Type 's' to select an option or type a space to deselect. Then press ENTER. Type FILTER ON/OFF/MODIFY on command line for filter processing. Display Parts Migration Status _ All _ Exported
Y
Total Count 2097 2097 Entity Count 915 915 Relation Count 1182 1182
******************************* BOTTOM OF DATA ******************************
7.
Press F3 to display a panel that shows whether the filter is on and lists the number of filtered entities and relations found. See Figure 5-29. Type an S next to the migration status you want to display and press Enter.
Filtered entity and relation counts
List Contents of Migration DMC_VER2 Version 1 =======> ______________________________________________________
Figure 5-29
Command
Type 's' to select an option or type a space to deselect. Then press ENTER. Type FILTER ON/OFF/MODIFY on command line for filter processing. Display Parts Y Filter On Migration Total Entity Relation Status Count Count Count S All 82 81 1 _ Exported 82 81 1 . . . . . . . . . . . . . . . . . . . . . . . . . ******************************* BOTTOM OF DATA ******************************
8.
You can now view the results, as shown in Figure 5-30. Type DELTA to see the Delta report on an entity, or TOGGLE to change an entitys import status.
5-36
Migration Actions
List Relations
Figure 5-30
Command
Filtered List of Migration Contents
List Contents of Migration DMC_VER2 Version 1 =======> _________________________________________________________
Type DELTA or TOGGLE next to the desired object. Then press ENTER. Filter On DELTA___ Exported Entity Component CONVERTI Project: ISP Object..: Exported Text..: None Keywords: None Source: Exported ________ Exported Relation Component CONVERTI Owns View CONVERTI_I Object..: Exported Text..: None Keywords: None Source: None ________ Exported Relation Component CONVERTI Owns View CONVERTI_O Object..: Exported Text..: None Keywords: None Source: None
Project: ISP
Project: ISP
For more information about generating delta reports see Generate a Delta Report. For more information about overriding migration status values see Toggle Import Status.
Result
The system generates an online list of the migration contents based on your processing options. If the RES_TO_FILE variable in the @MIGENVn INI file has a value of Y, use the view results of migration (RES) action to view migration system messages online in the AppBuilder environment. If the RES_TO_FILE variable has a value of N, exit the AppBuilder environment and browse the job results in the system utilities. See Chapter 7, Setting Up the Environment for more information.
List Relations
The list relations action lists the root entities in the migration package. You can view one, several, or all types. After the analyze action, the LR action also lists the objects that need to be prepared as a result of migration if the RBDECTOR variable in the @MIGENVn INI file is set to Y. This prepare status is imported along with the rest of the object information and used during rebuild to determine the extent of the rebuild. 1. On the List Facility panel (Figure 5-31), type LR on the action line next to the entity whose relationships you want to view. Press Enter.
5-37
List Relations
Figure 5-31
List Facility for Migration Entities

Repository: SUNRISE
V: 1
Project: DEV
Level: 2
LR______ DMC_VER2
________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ GVK GVK_BK_CRAIG GVK_BK_PAULA GVK_CRAIG_GE GVK_DRAW GVK_GRE GVK_MIG_DRAWINGS GVK_POUGH GVK_P2 GVK_Q26 GVK_Q26B TEST_MIGRATION2
Action
Name
System Id AFT4NR AFJBNR AAAHNR AAAINR AFTXNR AFTUNR AESDNR ADZANR AFTPNR AFTQNR AFKXNR AFMHNR ABDTNR
Command ===> _____________________________________________________________
2.
On the Relation Options pop-up panel (Figure 5-32), type S in the selection field next to the relationship types you want to view. If you want to view all the relation types, type ALL on the command line. Press Enter. In this example, the DMC_VER2 migration entity has been analyzed and the RBDECTOR variable is set to Y, so the Relations Options panel displays the preparation status.
Displaying the preparation status
Figure 5-32
------------------ Relation Options ------------------| | | Select one or more. Then press enter. | | | | Entity . . . . : Migration | | Name . . . . . : DMC_VER2 | | | | Select Relation Type | | _ Will-Prepare Component | | _ Will-Prepare File | | _ Has-Root Function | | S Will-Prepare Process | | _ Will-Prepare Report | | _ Will-Prepare Rule | | _ Will-Prepare Set | | _ Will-Prepare Window | | ****************** BOTTOM OF DATA ******************* | | | | | | Cmd ===> ___________________________________________ | -------------------------------------------------------
3.
Selecting the Will-Prepare Process relationship displays a Relation List panel (Figure 5-33) for the migration entity.
5-38
Migration Actions
List Relations
Figure 5-33
Relation List panel for the Will-Prepare Process relation

Relation List for Entity Migration
Repository: SUNRISE V: 1 Entity Name: DMC_VER2 Relation Type: Will-Prepare Process Action ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________
Project: DEV
Level: 3
Name WXT_PROCESS_ALL_EXECENV WXT_PROCESS_EXECENV_BATCH WXT_PROCESS_EXECENV_CICS WXT_PROCESS_EXECENV_CICS_COOP WXT_PROCESS_EXECENV_CICS3270 WXT_PROCESS_EXECENV_MVS WXT_PROCESS_EXECENV_MVS_COOP WXT_PROCESS_EXECENV_PCCICS WXT_PROCESS_EXECENV_PCCICS_COP WXT_PROCESS_EXECENV_PCCICS3270 WXT_PROCESS_EXECENV_WKS WXT_PROCESS_MENU_L1 WXT_PROCESS_MENU_L2 XXT_PROCESS_ALL_EXECENV
Child Name WXT_PROCESS_ALL_EXECEN WXT_PROCESS_EXECENV_BATCH WXT_PROCESS_EXECENV_CICS WXT_PROCESS_EXECENV_CICS_COOP WXT_PROCESS_EXECENV_CICS3270 WXT_PROCESS_EXECENV_MVS WXT_PROCESS_EXECENV_MVS_COOP WXT_PROCESS_EXECENV_PCCICS WXT_PROCESS_EXECENV_PCCICS_COP WXT_PROCESS_EXECENV_PCCICS3270 WXT_PROCESS_EXECENV_WKS WXT_PROCESS_MENU_L1 WXT_PROCESS_MENU_L2 XXT_PROCESS_ALL_EXECENV
Command ===> _______________________________________________________
Scroll right to view the following additional column headings: Located In Date Created Time Created Created By (user ID Date Maintained Time Maintained Maintained By (user ID) Change Number Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User (user ID) If you select more than one relation from the list, the panel looks like Figure 5-34.
Figure 5-34 Selecting more than one relation
Relation List for Entity Migration Repository: SUNRISE Entity Name: DMC_VER2 V: 1 Project: DEV Level: 3
Action ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________
Relation Type Will-Prepare Component Will-Prepare Component Will-Prepare Component Will-Prepare Component Will-Prepare Component Will-Prepare Component Will-Prepare Component Will-Prepare Component Will-Prepare Component Will-Prepare Component Will-Prepare Component Will-Prepare File Will-Prepare File Will-Prepare File
Name WXT_COMPONENT_BATCH_ASM WXT_COMPONENT_BATCH_ASM_DB2 WXT_COMPONENT_BATCH_ASM_L1 WXT_COMPONENT_BATCH_ASM_L2 WXT_COMPONENT_BATCH_ASM_01 WXT_COMPONENT_BATCH_ASM_01A WXT_COMPONENT_BATCH_ASM_02 WXT_COMPONENT_BATCH_C WXT_COMPONENT_BATCH_C_DB2 WXT_COMPONENT_BATCH_C_L1 WXT_COMPONENT_BATCH_C_L2 WXT_FILE_COMP_DB2 XXT_FILE_COMP_DB2 WXT_FILE_COMP_DB2
Command ===> _______________________________________________________________
5-39
Maintain Entity
Scroll right to see the following additional column headings: System ID Sequence 4. If you select the Has-Root Function relation instead on the Relation Options panel in Figure 5-31, the panel in Figure 5-35 is displayed.
Has-Root Function relation
Relation List for Entity Migration Repository: SUNRISE V: 1 Entity Name: DMC_VER2 Relation Type: Has-Root Function Project: DEV Level: 3
Figure 5-35
LR______ WXT_FUNCTION_ALL_EXECENV
Scope type Date Created Entity Hierarchy 95/10/10 ________ XXT_FUNCTION_ALL_EXECENV Entity Hierarchy 95/10/10 ________ YXT_FUNCTION_ALL_EXECENV Entity Hierarchy 95/10/10 ******************************* BOTTOM OF DATA ****************************
Action
Name
5.
You can type LR next to one of the relations to list its relations (Figure 5-35). Press Enter. The panel in Figure 5-36 is displayed.
Listing relations of the Has-Root Function relation
Figure 5-36
------------------ Relation Options ------------------| | | Select one or more. Then press enter. | | | | Entity . . . . : Function | | Name . . . . . : WXT_FUNCTION_ALL_EXECENV | | | | Select Relation Type | | _ Is-A-Root-Of Migration | | _ Refines-Into Process | | _ Is-A-Root-Of Rebuild Package | | ****************** BOTTOM OF DATA ******************* | | | | | | | | | | | | | | | | Cmd ===> ___________________________________________ | -------------------------------------------------------
6.
Press F3 to exit the Relation List panel.
Result
The system generates an online list of the relations in the migration package.
Maintain Entity
Use this action to display an entitys Maintain an Entity panel where you edit the entitys attributes or determine its migration status value. Type ME on the action line next to the migration entity you want to update.
5-40
Migration Actions
Toggle Import Status
Toggle Import Status

Analyze processing assigns import status values to objects in a migration package (see Chapter 3, Target Environment Processing). The purpose of the toggle import status (TOGGLE) action is to change the migration status of an object after you complete the analyze process. For example, if an objects status is Will be Updated and the object is imported, the import process overwrites the object in the target environment. This action lets you toggle the status to Skip Update if you do not want to overwrite the object in the target environment. When you choose to toggle an object marked Will be Created, you place an explicit skip on that object and an implicit skip on relations to the objects parents and children. 1. 2. Use the list migration contents (LISTMIG) action to navigate to the List Contents panel. Type TOGGLE on the action line of the object you want to skip. Press Enter.
You cannot toggle objects with an Unchanged status value. If you toggle an entity from Import Will Create to Skip Create, you also toggle the entitys source, keywords, text., and relationships.
Note Caution
Objects on which you have used the toggle action are marked with the word SKIP. Use this action carefully. Examine why you need to toggle migration status values. If you toggle the migration status values for a large number of objects, then it is likely that the objects were not ready to be exported from the source environment.
Options
The toggle import status (TOGGLE) action has no user options.
Result
The migration status of the object changes to Skip <Action> and excludes the object from import processing.
Batch Toggle Utility

You can skip updates, creates, or deletes in the import step by using the TOGGLE action in the list migration contents window. You manually toggle the import status value of the object in question from Import will Update, for example, to Skip Update. This section describes a new utility that lets repository administrators toggle import status values in a batch job rather than manually. Use it when you need to perform frequent migrations that involve a great many objects that need to be left out of the import. The input of the batch job is a sequential file that contains a list of entities and relationships that you want to toggle off. A sample input file follows: 00055 AAZDFF MIGRTN 9 DVT_CICS_RULE
5-41
View Results of Migration
00056 AAZDFF MIGRTN 9 DVT_VIEW_RULE_IO DVT_FLD_ENVIRONMENT The first line contains an entry for the rule DVT_CICS_RULE. The second line contains an entry for the relationship between the view DVT_VIEW_RULE_IO and its child, the field DVT_FLD_ENVIRONMENT. Single blanks separate each item in the entries. The formal structure of the input file is shown in Table 5-14.
Table 5-14 Input file structure Item Metatype Migration id Migration type Version Parent longname Child longname Type definition char(05) char(08) char(07) char(01) char(30) char(30) (relationship only)
The administrator starts the batch toggle by running the TOGGLEB action against the management services entity in the entities window for an ADM project, as shown in Figure 5-37.
Figure 5-37 Management Services Entity using Batch Toggle Utility
Command ===> ______________________________________________________________ Repository: CAPE541 Action toggleb_ ________ ________ ________ ________ V: 5 Project: ADM Level: 1
Entity Management Services Migration Project Repository User
******************** BOTTOM OF DATA **********************
When the Mass Toggle dataset panel is displayed, enter the name of the sequential file that contains the object information for the batch toggle job, as shown in Figure 5-38.
Figure 5-38 Mass Toggle Dataset Panel
Mass Toggle dataset panel Command ===> ______________________________________________________________ Processing option Mass Toggle input Dataset . . . SERMUA.TOGGLE.INPUT__________________

Use the view results (RES) action to see the messages that contain the results of a batch job. The system generates two message types: User messages display the date and time stamps for job start and job end, as well as the final jobstatus value Summary counts contain counts of the objects in a migration package by migration status, migration type, and migration status and type
5-42
Migration Actions
Use these message types to check the number and kind of objects in a migration package, track and resolve problems, and check audit information. If you select the user messages, the View Results panel displays the following data for each job: Date and time the job started Date and time the job ended Time stamp for each routine in the program The values that you selected for the migration attributes Warning and error messages The summary counts track the content of the migration package throughout source and target environment processing. The object count should be the same through the analyze process. After analyze processing has completed, you can exclude categories of objects from Import processing by using the Import Options. Or, you can use the toggle action to exclude specific objects from import processing. 1. 2. 3. 4. Submit an export, analyze, or import job. When the job status attribute has either a <Job> Successful or <Job> Failed value, then the job has finished processing. Navigate to the migration Maintain an Entity panel. Type RES on the command line and press Enter. Select whether you want to browse, print, or delete the results file by typing S, P, or D respectively in the Action field, as shown in Figure 5-39.
Repository File Browser
Repository File Browser Name . . . . . . . : DMC_VER2 Version . . . . . : 1 Select one or more of the following. S=Browse P=Print D=Delete Action Then press ENTER .
Figure 5-39
Method Results File ANALYZE Analyze Results ANALYZE Analyze Count ANALYZE Analyze Detail IMPORT Import Results IMPORT Import Count IMPORT Import Detail ******************************* BOTTOM OF DATA ******************************
S S S S S S
Result
The system generates an online message report.
5-43
5-44
Migration Actions
CHAPTER
MIGRATING AND IMPORTING RUN-TIME APPLICATIONS
This chapter describes how to migrate and import run-time applications into production environments. The COPYAPP action lets you transfer all or parts of AppBuilder run-time applications to be executed in other AppBuilder locations. You can export multiple AppBuilder application environments (batch, CICS and IMS) at the same time. The first part of this document describes the AppBuilder COPYAPP action, which migrates applications to mainframe production environments. Make sure you export the migration entity before you use the COPYAPP action, because the export action creates the data set that COPYAPP uses.
COPYAPP
The COPYAPP action extracts only the executable data needed to run in the target location. The facility extracts AppBuilder run-time application data from a version 5.3x or later release repository, so that the AppBuilder Package Import facility at a target location can install that package onto mainframe CICS, IMS, or batch mainframe environments. When the package has been installed, COPYAPP will have: Link edited all rules, reports, sets, and user components Bound and granted the DB2 application packages and/or plans Updated the run-time AppBuilder processing files Generated PSBs and ACBs (IMS only) Rebuilt the rule/transaction relationship tables and generated rule definitions for CICS or IMS The COPYAPP action produces extracts to tape and chopped, fixed-block, binary-format records on DASD. The chopped, fixed-block, binary-format records are for PC distribution. The second part of this chapter describes how to import the run-time application exported with the COPYAPP action. The import program can run either in an AppBuilder repository or as a stand-alone application that builds run-time package imports.
Migrating and Exporting Using COPYAPP

You migrate and export a run-time application by typing the COPYAPP command next to either a migration or rebuild package entity in the AppBuilder Host Workbench panel, shown in Figure 6-1.
6-1
Export Options
Figure 6-1
AppBuilder Host Workbench panel
COPYAPP
When you issue the COPYAPP command within an AppBuilder repository, a panel is displayed for you to export or import a run-time application (Figure 6-2).
Figure 6-2 Selecting export or import within the repository
Migration Run-time Package Export/Import Options Command =======> ___________________________________________________________
Name . . . . . . . . : CDGN_DEC17 Version . . . . . . : 1 Perform Run-time Export or Import (E/I) E
Selecting export or import displays another panel from which you can choose corresponding options.
Export Options
Selecting export displays the Migration Run-time Package Export Options panel (Figure 6-3).
Figure 6-3 Export Options panel
-------------------------------------------------------------------------------Command =======> ___________________________________________________________ HAXEXPD Migration Run-time Package Export Options Name . . . . . . . . : PHILS_RSI Version . . . . . . : 6
Data Set Prefix for Migration Files Package to Tape 80 Byte Records for PC transfer Add RuleView data in Run-time Package
. SERPHC.RSI_______
_ _ _
Export full load modules (Y) or NoCall modules for re-link (N) Y
____________________________________
.
6-2
Migrating and Importing Run-time Applications
Exporting the Package
The fields on the panel are described in Table 6-1.:

Table 6-1 Field Data Set Prefix for Migration Files Package to Tape Package to 80 Byte Records for PC transfer Add RuleView data in Run-time Package Migration Run-time Package Export Options Description
Enter the data set high-level qualifier required to create the run-time package.
Select this option if the package is to be copied to tape. You can select both tape and chopped, 80-byte records at the same time. Select this option if the package is to be transferred with a PC using OS/2 Communications Manager send and receive commands. Select this option if the application needs to be tested at the target location using AppBuilder RuleView. For environment test and/or production transfers, do not include the RuleView data, as it increases the size of the extract with data needed only for testing. Select (Y) to extract the AppBuilder application load modules or (N) to extract the application Nocall load modules. Enter (N) if the application is to be imported with COPYAPP to a different platform than that of the export. For example, export a CICS AppBuilder application and import it as an IMS application.
Export full load modules (Y) or NoCall modules for re-link (N)
Exporting the Package

The run-time package export executes in two jobs. This first job builds the IEBCOPY and IDCAMS repro input cards for the second job. This second job executes only if there are no errors or warning messages during the first job. The second job has four parts: Part 1 copies the PDS members (such as load modules and DBRMs). Part 2, IDCAMS repros the KEY VSAM data set records. Part 3 reports on the output of the copy and repro jobs. This step only reports on errors or warning messages during the process. Part 4, if selected, chops the export run-time data for PC file transfer, and/or copies the data to tape.
Package Export Messages

Package-export messages are described below. HAX001 W9COPYAPP &LIBNAME MEMBER &IMPNAME NOT IN LOAD LIBRARY, RE-PREPARE. A rule, set, component or report NCAL load member could not be found in the repository load library. Prepare the entity. HAX002 W9COPYAPP &TYPEENT RECORD &IMPNAME IN &FILE FILE NOT FOUND, RE-PREPARE &TYPEENT. The entity data in the following files VIDTEXT, VIEWDEF, rule relationship and/or rule source does not exist. Prepare the entity.
6-3
Installing the COPYAPP Software
HAX003 E9COPYAPP ENTITY FILE DOES NOT EXIST, RE-RUN RUN-TIME EXPORT. The ENTITY file that holds all the relevant information for the export and package import does not exist. Run the COPYAPP action again. HAX004 I9COPYAPP EXTRACT PACKAGE SUBMITTED FOR &OUTTYPE. The package export extract completed successfully and the copy to tape and/or chopped, 80-byte records has been submitted. HAX005 W9COPYAPP EXTRACT PACKAGE NOT SUBMITTED. JCL IN DATASET &FTOUTFIL. If any of the previous warning messages were produced, this message tells you where the JCL is for later execution. HAX006 I9COPYAPP CHECK RESULTS AND SUBMIT JCL EXTRACT &FTOUTFIL IF OK. If any of the previous warning messages were produced, this message tells you where the JCL is for later execution. HAX007 E9COPYAPP FUNCTION &FUNCTION FOR &NAME FAILED WITH RC=&RETCC. This message is produced when there is a severe internal function failure. HAX008 E9COPYAPP ALLOCATE FOR FILE &DDNAME DSN &DSN FAILED WITH RC=&RETCC. File allocation failed. HAX009 I9COPYAPP EXPORT &NAME VERSION &VRSN STARTED AT &TIMESTAMP. HAX010 I9COPYAPP EXPORT &NAME VERSION &VRSN ENDED SUCCESSFULLY AT &TIMESTAMP. HAX011 I9COPYAPP EXPORT &NAME VERSION &VRSN ENDED WITH MESSAGES AT &TIMESTAMP.

The COPYAPP import application is a stand-alone application that can run outside of an AppBuilder repository. It builds run-time package imports from COPYAPP exports created with a migration or rebuild entity. Note
For a full COPYAPP run-time import to install an AppBuilder application without a repository, some repository data sets must be available.
6-4
A list of the required data sets follows: entity Link edits and application run-time execution QUALIFIERS.USRVQUAL.LOADBS/BT/CI/IM QUALIFIERS.MODQUAL.LOADBT/CI/IM/LIB QUALIFIERS.BASEQUAL.LOADBT/CI/IM/LIB CICS or IMS 3270 converse applications Vidtext files QUALIFIERS.VSUVQUAL.HPSRT.VIDTEXTC for CICS QUALIFIERS.VSUVQUAL.HPSRT.VIEWDEFI for IMS RuleView testing Viewdef files QUALIFIERS.VSUVQUAL.HPSRT.VIEWDEFC for CICS QUALIFIERS.VSUVQUAL.HPSRT.VIEWDEFB for Batch Rule Relationship files QUALIFIERS.VSUVQUAL.HPSRT.RLRELATNC for CICS QUALIFIERS.VSUVQUAL.HPSRT.RLRELATNB for Batch QUALIFIERS.VSUVQUAL.HPSRT.RLRELATNI for IMS Rule Source files QUALIFIERS.VSUVQUAL.HPSRT.RULESRCC for CICS QUALIFIERS.VSUVQUAL.HPSRT.RULESRCB for Batch QUALIFIERS.VSUVQUAL.HPSRT.RULESRCI for IMS
Installing Run-time Package Import Extensions

The AppBuilder Run-time Package Import application includes REXX execs, ISPF panels, JCL skeletons and load modules. To import applications to a production environment without a repository, you must first install the Run-time Package Import software extensions. All the data sets must be installed under the same high-level qualifiers as shown: '(highlevel_name).CLIST' '(highlevel_name).INI' '(highlevel_name).LINKCTL' '(highlevel_name).OBJ' '(highlevel_name).SKELS' '(highlevel_name).PANELS' '(highlevel_name).LOADLIB'
6-5
Procedure - Using the Install Facility 1. 2. Create a partitioned data set to hold the installation dialog members. Suggested DCB is FB 80,3120. Required space is TRK(5,1,5). Upload the following five members from the PC to the file created in step 1. CRLF and conversion switches should be ON. haxboot haxpnlb haxpnlc haxsklb readme You can obtain these files from an AppBuilder mainframe run-time development. 3. 4. Edit the member HAXBOOT according to the instructions in the top of the member: Change the string DIALOG.DSNAME to the name of the data set created in step 1. Do not make any other edits. Execute the member HAXBOOT from TSO or from ISPF using the TSO EXECUTE command. A panel will be displayed which prompts for information needed to install the Run-time Import Package application. Enter the tape number and high-level qualifier data set'SEER1.HAXIMP'. After entering the requested information, you will see a job stream displayed for edit in the member HAXUNL. SUBMIT the job. Verify successful completion of the UNLOAD job. All steps should return a condition code of 0.
5. 6. 7.
The following data sets will be created by this job (globqual is the value entered in step 4 for Installation Workbench Dataset Qualifier): globqual.CLIST globqual.CNTL globqual.LINKCTL globqual.LOADLIB globqual.OBJ globqual.PANELS globqual.SKELS If you do not use the install procedure supplied, you must update the REXX exec HAXIMPA to specify the high-level data set qualifier. Do this by setting the variable (DSNAME1) to that high-level qualifier. You should not need any other updates to execute the AppBuilder Run-time Package import application. You will also need to update the exec HAXIMPA DSNAME# if this application is to reside in more than one high-level qualifier library set. For example, if you have updated one or more of the application programs, you need to concatenate the updates in front of the base libraries. Update DSNAME1 to equal the update libraries high-level qualifier, and update DSNAME2 to equal the base high-level qualifier. You can also use DSNAME3 for this. Always set the unused DSNAME#s to the lowest-level concatenation data set high-level qualifier.
6-6
Importing the Run-time Package
Importing the Run-time Package

The Run-time Package Import application has three execution phases: 1. Unload and update the target configuration file. The configuration file for the run-time package import is unloaded first, so the application can get the information it needs to determine which data sets to unload. After the configuration file has been unloaded, you can update it with the Display/Update/Reset Library Configuration option. 2. Unload the import package files and update the application configuration. The application uses the configuration file to determine which data sets are available for unloading. After the package import is unloaded, view the application configuration and update it if needed before continuing with step 3. You can update the application configuration at any time. 3. Install the unloaded package import. The Application Status panel displays all the steps necessary to install the package into the target environment. You can select each step individually to review and edit each job, and optionally select all or some of the link edits, PSB generations, and DB2 plan and package binds. At this point, you can install all steps at the same time. When the package has been installed, the imported application will have completed the following: Link-edited all rules, reports, sets, and user components Bound and granted the DB2 application packages and/or plans Updated the run-time AppBuilder processing files Generated PSBs and ACBs (IMS only) Rebuilt the rule/transaction relationship tables and notified the target system (CICS/IMS) of updates to the application program To start importing the run-time package, go to TSO Option 6 and type the name of the CLIST, HAXIMPA, which displays the panel in Figure 6-4.
Figure 6-4 Selecting the Run-time Package Import application
Migration Run-time Package Export/Import Options Command =======> ___________________________________________________________
Name . . . . . . . . : CDGN_DEC17 Version . . . . . . : 1 Perform Run-time Export or Import (E/I) I
1. 2.
Start the Run-time Package Import application by typing I in the Perform Run-time Export or Import field, as Figure 6-4 shows, and then press Enter. The Installation Header panel shown in Figure 6-5 is displayed.
6-7
Installing the Import Package
Figure 6-5
Installation Header panel
---------------AppBuilder A/E Package Installation Header Panel --------------COMMAND ===> AppBuilder Application Environment Run-time Package Installation This application will install AppBuilder run-time applications that were exported by the AppBuilder Run-time Package Export action. applications can be installed as a step by step operation or automatically. Panels are displayed throughout the process for input or to verify the installation configuration. If you are installing automatically and did not complete the source configuration, you will need to verify and update the configuration details before installation continues. This installation is a 4 stage process. 1) Configuration file unload and update. 2) Unload the Run-time Package and update the configuration as required. 3) Back up the Run-time Package. 4) Install the Run-time Package. You can restore the original execution libraries if necessary.
Enter 3.
END command to Exit install. Press ENTER to continue.
Press Enter to continue.

Press Enter from the Installation Header panel to display the main Run-time Package Installation Information panel of the AppBuilder Run-time Package Import (Figure 6-6).
Figure 6-6 Installation Information panel
------------------- Run-time Package Installation Information ----------------COMMAND ===>
Package Name ==> Install from DASD or tape ==> D (D/T) To data set information Dataset Qualifier ==> SERPHC.RSI.IMP DASD Unit ==> SYSDA Volume (Optional) ==> From tape information Enter data if installing from tape. Unit to read your install tape ==> CART Volume Serial ==> Use bypass label processing ==> (Y/N) From DASD information Enter data if installing from DASD Data 80-byte record chopped fmt ==> Y (Y/N) From data set high-level qual ==> SERPHC.RSI.MIG.CHOPLIB Backup information Backup data set high level qual ==> SERPHC.RSI.BACKUP Configuration file INI mbr name ==> HAXIMPA Jobcard Information ===> //SERPHC2E JOB (DRHS-AZ),'UTILITIES PCOBLEY', ===> // NOTIFY=&SYSUID, ===> // CLASS=A,TIME=1440,MSGCLASS=D,MSGLEVEL=(1,1) ===> //* .$.0 010897 COPYAPP UTILITIES STUFF PCUTILA.JCL PHC 01 Enter END command to exit the installation. Press ENTER to continue.
6-8
The values in Figure 6-6 are illustrative. The fields on the Run-time Package Installation Information panel are described Table 6-2.
Table 6-2 Field Package Name Run-time Package Installation Information Options Description Displays the short name of the package (export system ID) when the migration entity file was exported. The name is created in the AppBuilder repository from which the package was exported. The Package Import facility can install AppBuilder applications from tape, DASD, and DASD chopped, 80-byte, binary-format data sets. The chopped, 80-byte, binaryformat option is for transferring these package applications with the PC, using OS/2 Communications Manager send and receive commands. Specify the target data set high-level qualifier for the run-time package import files, including the DASD unit and volume if necessary. Specify the relevant data if you are installing from tape: Specify the tape unit device for your installation tape. Specify the volume serial number. Specify whether you want to use bypass label processing. Specify the relevant data if you are installing from DASD: If the import is to be installed from a binary-format, 80-byte, chopped data set (uploaded from the PC), specify the full name of the partitioned data set. The chopped data set DCB information must be fixed block, with an logical record length (LRECL) of 80. Each package file must be a member of that data set. Specify the high-level qualifier of the package import data sets. If requested, the target run-time libraries containing any of the import package application are backed up during the installation. You can fully restore the environment at any time. Specify the INI configuration file member name. The member name defaults to a sample INI member, HAXIMPA, that Seer supplies. Edit the Seer data set names in this member to specify the correct high-level qualifiers (highlevel_name.INI) for your site. You need a configuration member name for each environment. Four lines of free-format input allow for the job card information.
Install from DASD or tape
To data set information From tape information Unit to read your install tape Volume Serial Use bypass label processing From DASD information Data 80-byte record chopped fmt From data set highlevel qual Backup data set high level qual
Configuration file INI mbr name Jobcard Information
Package Installation Status Panel

When installing a new package, the Installation Status panel presents a single status line showing that the CONFIG UNLOAD job status is NOT STARTED, as shown in Figure 6-7.
Figure 6-7 Installation Status panel
--------------------- Run-time Package Installation Status --------------------COMMAND ===> Installation Status Information Migration Name Display/Update/Reset library configuration ===> N (Y/N/R) Display/Update/Reset application configuration ===> N (Y/N/R) Backup Required ===> Y (Y/N) Restore ===> N (Y/N) Job Description Job Status Submit(Y) Review(Y) CONFIG UNLOAD NOT STARTED ******************************* BOTTOM OF DATA ********************************
6-9
Type a Y in the Submit(Y) column to run the CONFIG UNLOAD job, which is the run-time package configuration file. Type Y in the Review(Y) column to review and customize the generated JCL for all steps. The status panel is updated when the configuration is unloaded, as shown in Figure 6-8.
Figure 6-8 Status Information panel showing the configuration is unloaded
----------------- Run-time Package Installation Status ----------------- 5320405 COMMAND ===> Installation Status Information Migration Name AL21II Display/Update/Reset library configuration ===> N (Y/N/R) Display/Update/Reset application configuration ===> N (Y/N/R) Backup Required ===> Y (Y/N) Restore ===> N (Y/N) Job Description Job Status Submit(Y) Review(Y) Config File UNLOADED Package Import UNLOADED Load Modules NOT STARTED Vidtext NOT STARTED Rule Relation NOT STARTED Rule Source NOT STARTED DB2 Binds NOT STARTED PSB Generation NOT STARTED System Install NOT STARTED ******************************* Bottom of data ********************************
After the configuration is unloaded, you can display, update, or reset the library configuration by selecting the appropriate choice in the first line of the Installation Status Information. See Configuration Information on page 6-11 for specifics. Type a Y in the Submit(Y) column (Figure 6-8) of the import job to unload all the run-time package import application files. The Installation Status panel is updated to indicate that the import package has been downloaded, as shown in Figure 6-9.
Figure 6-9 Status Information panel showing the import job has unloaded the run-time package files
-------------------- Run-time Package Installation Status ------------------COMMAND ===> Installation Status Information Migration Name AAGXDR Display/Update/Reset library configuration ===> Y (Y/N/R) Display/Update/Reset application configuration ===> N (Y/N/R) Backup Required ===> Y (Y/N) Restore ===> N (Y/N) Job Description Job Status Submit(Y) Review(Y) Config File UNLOADED Package Import UNLOADED Link Edit COMPLETED VIDTEXT COMPLETED VIEWDEF COMPLETED VIEWDEF COMPLETED RULESRC COMPLETED DB2 Binds COMPLETED SYSTEM INSTALL COMPLETED ******************************* BOTTOM OF DATA *******************************
You can select these jobs individually or all at once. You do not need to process the steps in a set order, except you need to update the VIDTEXT file before issuing the SYSTEM INSTALL step for building the rule/relationship table. For example, if the imported AppBuilder applications do not access DB2, and for IMS do not access DL/ I, and RuleView is not required, the status panel is displayed as shown in Figure 6-10.
6-10
Figure 6-10
Sample Status Information panel
--------------------- Run-time Package Installation Status -------------------COMMAND ===> Installation Status Information Migration Name AAGXDR Display/Update/Reset library configuration ===> Y (Y/N/R) Display/Update/Reset application configuration ===> N (Y/N/R) Backup Required ===> Y (Y/N) Restore ===> N (Y/N) Job Description Job Status Submit(Y) Review(Y) Config File UNLOADED Package Import UNLOADED Link Edit NOT STARTED VIDTEXT Update NOT STARTED ******************************* BOTTOM OF DATA *******************************
Note
If the application were to be installed into a batch environment, the VIDTEXT update step would specify VIEWDEF instead.
Configuration Information
After the configuration file has been unloaded, you can select an option in the first field on the Installation Status panel to update or reset the library configuration. Display/Update/Reset library configuration ===> (Y/N/R) Type the letter corresponding to the action to view, update, or reset back to the original values the target package configuration. Select this option when the Config File step has completed. N Y R Do not display the current package installation configuration Display and update the package installation configuration Reset the package installation configuration to the original import settings
If any field values are invalid, the panel in Figure 6-11 is displayed for you to enter information.
Figure 6-11 Import Configuration Information panel
----------- Run-time Package Import Configuration Information ---------- 5320414 COMMAND ===> A/E process type Assembler Options Use RuleView to test PL/I library PL/I library COBOL II library C library DB2 library 1 DB2 installation name DBRM library DB2 Dynamic SQL prog DB2 Dynamic SQL Lib DB2 Bind type DB2 Location id ==> ALL ALL/CICS/IMS/BATCH
==> ASMA90 IEV90/ASMA90 ASM H or High Level ==> Y (Y/N) ==> SEER.PLI.PLIBASE ==> SEER.PLI.SIBMBASE ==> SEER.COB.COB2CICS ==> ==> ==> ==> ==> ==> ==> ==> ==> SEER.PLI.PLILINK ==> SEER.PLI.SIBMLINK ==> SEER.COB.COB2LIB
SEER.C.SEDCBASE ==> SEER.C.SEDCLINK DSN410.SDSNLOAD SYSTEM ID ==> DSN1 HPSINTEG DB2 plan owner name ==> SERPHC SERPHC.DEVL.DBRMLIB HMPTEP2 DB2 Dynamic SQL Plan ==> I33HPS53 HPSINTEG.BASE202.LOADLIB C C=Package or P=Plan HPSINTEG Package Collector ==> PHILPACK
Press ENTER to continue.
6-11
The values in Figure 6-11 are illustrative. If you do not select the RuleView option, the rule relationship (RLRELATN), RuleView definition, VIEWDEF for CICS, and rule source (RULESRC) VSAM files are not loaded. Another panel specific to the target system (CICS, IMS or Batch) is displayed, as shown in the following pages.
CICS Configuration
The values in the CICS Configuration panel in Figure 6-12 are illustrative. Details of CICS and IMS installation definitions can be located in Step 2. Define the Target System for CICS and IMS.
Figure 6-12 CICS Configuration panel
------------------ Run-time Package CICS Configuration ----------------5320407 COMMAND ===> CICS Target load lib CICS system library SYSLIB libraries ==> ==> ==> ==> ==> ==> ==> ==> ==> ==> ==> ==> SERPHC.DEVL.LOADCI SERPHC.DEVL.LOADCI HPSINTEG.USER1.LOADCI HPSINTEG.REP203.LOADCI HPSINTEG.MOD.LOADCI HPSINTEG.BASE202.LOADCI HPSINTEG.BASE202.LOADLIB
VIDTEXT file VIEWDEF file Rule Relation file Rule Source file
SEER.DEVL.HPS021D1.VIDTEXT SEER.DEVL.HPS001D1.VIEWDEF SEER.DEVL.HPS004D1.RLRELATN SEER.DEVL.HPS003D1.RULESRC
Install GROUP for HPS ==> PHILGRP
Enter
END command to exit. Press ENTER to continue.
IMS Configuration
The values in the IMS Configuration panel (Figure 6-13) are illustrative.
Figure 6-13 IMS Configuration panel
------------------ Run-time Package IMS Configuration ------------------ 5320407 COMMAND ===> IMS target load lib IMS BASE load lib IMS Res library SYSLIB libraries ==> HPSQA2.USER2.LOADIM ==> HPSQA2.BASE.LOADIM ==> SYS1.IMS.RESLIB ==> HPSQA2.USER2.LOADIM ==> HPSQA2.MOD.LOADIM ==> HPSQA2.REP.LOADIM ==> HPSQA2.BASE.LOADIM ==> HPSQA2.BASE.LOADLIB ==> VIEWDEF file ==> HPSQA2.USER2.HPI001D1.VIEWDEF Rule Relation file ==> HPSQA2.USER4.HPI004D1.RLRELATN Rule Source file ==> HPSQA2.USER4.HPI003D1.RULESRC PSB load library ==> HPSQA2.USER2.PSBLIB IMS MACLIB library ==> IMS.MACLIB Perform IMS ACB gen ==> Y ACB library ==> HPSQA2.USER2.ACBLIB DBD load library 1 ==> HPSQA2.BASE.DBDLIB DBD load library 2 ==> HPSQA2.BASE.DBDLIB IMS Stage 1 input definitions Transaction msg class ==> 3 Transaction processing limit ==> 99
6-12
The IMS stage-one input parameters generate application/transaction definition defaults.
Batch Configuration
Figure 6-14 shows an example of the values used for batch configuration.
Figure 6-14 Batch Configuration panel
----------------- Run-time Package Batch Configuration ----------------- 5320405 COMMAND ===>
Target Load Library Syslib libraries
==> SERPHC.DEVL.LOADBT ==> ==> ==> ==> ==> ==> HPSINTEG.USER1.LOADBT HPSINTEG.REP203.LOADBT HPSINTEG.MOD.LOADBT HPSINTEG.BASE202.LOADBT HPSINTEG.BASE202.LOADLIB
VIEWDEF data set name ==> SEER.DEVL.BATCH.VIEWDEF Rule Relationship data set name ==> SEER.DEVL.BATCH.RLRELATN Rule Source datset name ==> SEER.DEVL.BATCH.RULESRC
Enter
END command to exit. Press ENTER to continue.
Restrictions
Be careful when using COPYAPP for multiple process type applications, for example if the AppBuilder application contains batch, CICS, IMS, 3270 converse and cooperative rule entities. Using TIP application supplied with the mainframe repository installation, the following lists what you can and cannot achieve when exporting and importing multiple process applications with the COPYAPP method.
COPYAPP Export with RuleView

TIP Application with RuleView data. All DBRMs are extracted. All NCALL load modules are extracted. CICS/IMS VIDTEXT records are extracted. CICS/BATCH View definition records are extracted. All Rule Relationship records are extracted. All Rule Source records are extracted.
6-13
COPYAPP Import with RuleView to Batch

TIP Application with RuleView data. All Batch and CICS applications can be run in batch except for the following: IMS specific entities cannot be run in batch since an old entity View definition record is not created. Batch needs this record for the frontier rule. Process type specific functions, such as CICS specific rules and components. CICS 3270 converse rule applications. Full cooperative applications Some of the above can be run within Batch Ruleview to test single rule logic.
COPYAPP Import with RuleView to CICS

TIP Application with RuleView data. All Batch/CICS and IMS entities can be run in CICS except for the following: Process type specific functions, such as IMS and batch-specific rules and components. Batch and IMS applications cannot be part of RuleView, as batch entity records are not part of the VIDTEXT definition records, and IMS entity records are not part of the old View definition records. RuleView in CICS will run IMS applications.
COPYAPP Import with RuleView to IMS

TIP Application with RuleView data. All Batch/CICS and IMS entities can be run in IMS except for the following restrictions: Process type-specific functions, such as CICS and batch-specific rules and components.
COPYAPP Export without RuleView

TIP Application without RuleView data. All DBRMs are extracted. All NCALL load modules are extracted. CICS/IMS VIDTEXT records are extracted. BATCH View definition records extracted.
6-14
COPYAPP Import without RuleView to Batch

TIP Application without RuleView data. All Batch and CICS applications can be run in batch except for the following: Only Batch entities can be run in batch as batch run-time needs the frontier rules View definition record to process. These records are not created for CICS and IMS when Ruleview is not selected.
COPYAPP Import without RuleView to CICS

TIP Application without RuleView data. Batch and CICS entities can be run in IMS except for the following: Process type specific functions, such as CICS or batch specific rules and components.
Configuration Options
You can select an option in the second field on the Installation Status panel to update or reset the application configuration. Display/Update/Reset Application Configuration ===> (Y/N/R) AppBuilder applications associated with DB2 have DB2 plans and/or packages associated with them. Both DB2 and IMS applications using components to access DL/I have transaction codes associated with them. You can view these associations to update or reset them to their original imported values. Type the letter corresponding to the action to view, update, or reset to the original values the application configuration: N Y N Do not display the application configuration Display and/or update the current application configuration Reset the application configuration to the original package import settings
The panel in Figure 6-15 is displayed when you type Y to update the application configuration.
6-15
Figure 6-15
Update Plan/Package/Trans-action Code panel
------------- SEER Technologies, Inc. - High Productivity S ROW 1 TO 17 OF 21 ------------AppBuilder A/E Application Run-time Configuration options --------COMMAND ===> Update Plan/Package/Transaction Code Imp Name SDSSUPFN SDSSINI SDSSDTA SDSSFINI SDSSDNAI SDSSGVAL SDSSLOG SDSSGORD SDSSORNM SDSSREPM SDSSGETP SDSSDRET Long Name SDSS_UPD_MLRE_FNAME SDSS_INI SDSS_DATA_RETRIEVE_FRONTIER SDSS_PUT_FILE_INI SDSS_PUTDNA_IF SDSS_GET_VARVAL SDSS_TRACE_LOG SDSS_GETORD_SERVER_M SDSS_ORDNUM_SEL_ORDER SDSS_REPLY_SERVER_M SDSS_GETORD_SERVER_FRONTIER SDSS_DATA_RETRIEVE_M Plan Name AAAHPLNC AAATPLNC AAAWPLNC AAA4PLNC AAA5PLNC AABCPLNC AABEPLNC AABFPLNC AABGPLNC AABHPLNC AABOPLNC AABRPLNC
Package
TXN Update AAAHPLNC N AAATPLNC N AAAWPLNC N AAA4PLNC N AAA5PLNC N AABCPLNC N AABEPLNC N AABFPLNC N AABGPLNC N AABHPLNC N AABOPLNC N AABRPLNC N
Only the frontier rules for the import are displayed if you do not select RuleView and DB2 plan binds are used. Each line contains a rule name (implementation name first, followed by its long name) that within its hierarchy uses DB2, or for IMS uses a component that has DL/I access. Therefore, a DB2 plan name and/ or system transaction code must be associated with the rule. A plan or package will not be associated with IMS DL/I (non-DB/2) access rules. Any value you enter in this field is automatically blanked out. DB2 PACKAGE COLLECTOR Type a value in the Package Collector field to allow a rule to be bound to a package collection name. DB2 PLAN NAME A DB2 plan name must exist for each rule displayed. DB2 plan names do not need to be unique. TRANSACTION CODE The TXN column lists the transaction code that will be assigned to the rule. IMS uses the rules PSB name as the default DB2 plan name. The PSB name and the transaction code are the same for AppBuilder applications. To enable all the imported applications to be run with the same transaction code and plan name, you can set the same DB2 plan name and transaction code for all rules. Unless IMS is updated to attach a PSB to a plan with a different name, keep the transaction code and plan names the same. For IMS, any changes to a rules IMS transaction code will ultimately affect the name of the rules imported PSB. Details of this are explained in PSB and ACB Application Specification Block (IMS).
6-16
Link the Import Package

The first field on the Package Import Configuration target system panel lets you choose the types of link edit (Batch, CICS or IMS) to be performed. Table 6-3 shows the types of link edits available.
Table 6-3 Types of link edits CICS link Yes N/A N/A Dynamic Yes Yes Yes Static No Yes Yes Environment CICS IMS Batch
Select D for Dynamic link edit if you are using RuleView. On the Installation Status panel type Y in the Submit(Y) column of the LINK step to initiate the linkedit process of the run-time package import. Job Description Job Status Submit(Y) Review(Y) Link Edit NOT STARTED For imported user component, the NCAL load module must resolve all external references to nonAppBuilder programs or the link will fail. You may need to update the link-job JCL to accomplish this. A Y in the Review(Y) column will display all the entities available to be link-edited. You can select some or all of them for link edit. The review option also displays the generated JCL for you to update if necessary. If you type Y in the Review(Y) field, the panel in Figure 6-16 is displayed.
Figure 6-16 Link Edit Selection panel
--------------------- Run-time Package Link Edit Selection -------------------COMMAND ===> Imp Name SDSSDNAI SDSSDREF SDSSDRET SDSSDTA SDSSFINI SDSSGETP SDSSGORD SDSSGVAL SDSSINI SDSSLOG SDSSORMC COMPONE Long Name SDSS_PUTDNA_IF SDSS_CK_DEREF SDSS_DATA_RETRIEVE_M SDSS_DATA_RETRIEVE_FRONTIER SDSS_PUT_FILE_INI SDSS_GETORD_SERVER_FRONTIER SDSS_GETORD_SERVER_M SDSS_GET_VARVAL SDSS_INI SDSS_TRACE_LOG SDSS_MACHINE_SEL_ORDER USER_COMPONENT_ONE Entity Component Type Language RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE COMPONENT COBOL
Selection Y Y Y Y Y Y Y Y Y Y Y Y
Note that the language type of user component entities is displayed. Load Modules When the Load module option is selected on the COPYAPP export, this option copies the new load modules to the required target load library.
Update Entity and View Definition (VIDTEXT) File

The VIDTEXT Update job on the Installation Status panel updates the rule, component, and window entity definitions in the VIDTEXT VSAM files (HPS021D1 for CICS and HPI001D1 for IMS).
6-17
Job Description Job Status VIDTEXT NOT STARTED
Submit(Y)
Review(Y)
If any of the rule transaction codes are changed, the rule view records are updated to reflect these new codes. A new rule/transaction relationship table is created from this file to enable AppBuilder run-time to schedule the correct transaction for a frontier rule during cooperative, 3270 Converse, or RuleView processing. This enables an AppBuilder application to be attached to any transaction that is already defined to the system.
Update the Rule Relationship and Rule Source Files

The rule relation and the rule source jobs update the RLRELATN and the RULESRC files, if you exported the RuleView data and selected the RuleView option for the Package import. Job Description Job Status Submit(Y) Review(Y) Rule Relation NOT STARTED Rule Source NOT STARTED
Bind and Grant the DB2 Plans and Packages

The DB2 Binds job binds and grants all the DB2 Package/Plans for the package import applications. Job Description Job Status Submit(Y) Review(Y) DB2 Binds NOT STARTED You can update the rule plans, packages, and transaction codes by selecting the Application Run-time Configuration options before requesting this step.
PSB and ACB Application Specification Block (IMS)

Rules that access DB2 or DL/I within their hierarchy will have transaction codes other than the default assigned to them. Therefore, you need a PSB generated for these rules. For non-DB2 or DL/I AppBuilder applications, the frontier rule will be assigned the AppBuilder run-time default transaction code, so a PSB is not needed. The PSB generation job generates the PSB. A new PSB will be generated, and you can type a Y the Review(Y) column to edit the source. Job Description Job Status Submit(Y) Review(Y) PSB generation NOT STARTED If a rules PSB source is not part of the package import, a default PSB is created. For example, a run-time package export could have been extracted from a CICS defined application, thus no PSBs are available. Only one PSB is generated if all the rules have been assigned the same IMS transaction code. Figure 6-17 shows the IMS PSB Selection panel.
6-18
Installing the Target System on CICS and IMS
Figure 6-17
IMS PSB Selection panel
----------------AppBuilder A/E Package IMS PSB Selection Panel ---------------COMMAND ===> Imp Name SDSSUPFN SDSSINI SDSSDTA SDSSFINI SDSSDNAI SDSSGVAL SDSSLOG SDSSGORD SDSSORNM SDSSREPM SDSSGETP SDSSPSC SDSSQORD Long Name SDSS_UPD_MLRE_FNAME SDSS_INI SDSS_DATA_RETRIEVE_FRONTIER SDSS_PUT_FILE_INI SDSS_PUTDNA_IF SDSS_GET_VARVAL SDSS_TRACE_LOG SDSS_GETORD_SERVER_M SDSS_ORDNUM_SEL_ORDER SDSS_REPLY_SERVER_M SDSS_GETORD_SERVER_FRONTIER SDSS_PSC_MLREFILE SDSS_QRYORD_SERVER_M PSB name/ Txn Code AAAHPLNC AAATPLNC AAAWPLNC AAA4PLNC AAA5PLNC AABCPLNC AABEPLNC AABFPLNC AABGPLNC AABHPLNC AABOPLNC AABUPLNC AABVPLNC
Create Y Y Y Y Y Y Y Y Y Y Y Y Y
Edit

CICS and IMS rule/transaction relationship tables and installation definitions must be generated to finish installing the run-time package import. Note
Do not select this option until you have updated the VIDTEXT file for the package import, as the complete file is used to build the relationships.
Submit the SYSTEM INSTALL job to display the current AppBuilder rule/transaction relationships for the whole system. Job Description Job Status Submit(Y) Review(Y) SYSTEM INSTALL NOT STARTED After you submit the install job, the panel in Figure 6-18 is displayed.
Figure 6-18 Rule/Transaction Table panel
HPS Rule/Transaction Table COMMAND ===> Generate IMS definitions and Rule Name -----------------------------R_RUNM_AA_ABA R_RUNM_AA_ABAA PSB_MCF_TEST1 JKA_IMS_RULE R_RUNM_AA_ABB R_RUNM_AA_ABC R_RUNM_AA_ABE R_RUNM_AA_ABCA R_RUNM_AA_ABEA R_RUNM_AA_ABEAA R_RUNM_AA_ABD R_RUNM_AA_ABDA R_RUNM_AA_ABDAA R_RUNM_AC_ABA R_RUNM_AC_ABC R_RUNM_AC_ABCA ROW 1 TO 18 OF 63 SCROLL ===> PAGE
E (Browse/Edit) the result System Id Tran Code Impl Name ---------------------AAAC7Z QA00M1AA AAAC7Z AAAD7Z TIP0M1AF AAAD7Z AAA8MF PSBPM1AA AAA8MF AAA9BB TIP0M1AI AAA9BB AADI7Z QA00M1AB AADI7Z AAIN7Z QA00M1AC AAIN7Z AAIN8G QA00M1AE AAIN8G AAIO7Z TIP0M1AG AAIO7Z AAIO8G TIP0M1AJ AAIO8G AAIP8G QA00M1AU AAIP8G AAN77Z QA00M1AD AAN77Z AAOA7Z TIP0M1AI AAOA7Z AAQ17Z TIP0M1AH AAQ17Z ABFSNR QA00M1AG ABFSNR ABFWNR QA00M1AI ABFWNR ABFXNR QA00M1AP ABFXNR
6-19
The AppBuilder Rule/Transaction table panel displays all rules assigned to specific non-AppBuilder default transaction codes. You can sort each column in ascending alphanumeric order. If you press F1, the panel in Figure 6-19 is displayed.
Figure 6-19
HELP COMMAND ===>
Rule/Transaction table help panel

Rule/Transaction Table
This panel displays the contents of the Vidtext VSAM file.
Primary SORTR SORTS SORTT SORTI GENH GEND
Commands: - Sort the - Sort the - Sort the - Sort the
list list list list
by by by by
Rule name. System Id. Transaction Code. Implementation Name.
- Generate the Rule/Tran table creation job and submit it. - Generate CICS IMS transaction definitions.
You need to perform two more steps to complete the installation process: Step 1. Generate the Rule/Transaction Relationship Table Step 2. Define the Target System for CICS and IMS
Step 1. Generate the Rule/Transaction Relationship Table

For both IMS and CICS, you need to generate the rule/transaction relationship table to make the latest updates available. Type GENH at the command prompt to generate the JCL that assembles and link-edits the new table. The table will be link-edited into the target load library specified in the configuration.
CICS
The region will need to be stopped and restarted for the new table to take affect. Make sure that the table load module, HPSTBLE1, is in the correct CICS start-up region library.
IMS
For 3270 converse applications, the transaction processing (TP) region needs to be stopped and restarted. For cooperative AppBuilder applications, either the IMS control region should be restarted, or you can manually enter a transaction to tell the terminal routing exit, DFSCMTR0, to load a new copy of the table. That transaction is as follows: UTBL0000 ++11000000
Load new copy of AppBuilder rule/txn tables
The HPITBL1 load module must be copied into both the TP regions load library and the user RESLIB libraries. This could be the same data set name.
6-20
Step 2. Define the Target System for CICS and IMS

The final step is to define the target system (CICS/IMS) application. Type GEND at the command prompt to generate the definitions.
CICS
A sample of the definitions generated for CICS follows. Use this output as part of the CICS definition input for the new imported package to take effect. * AppBuilder RULE SDSS_RET_PAF DEFINE PROGRAM(SDSSPAF) GROUP(SS0210) LANGUAGE(COBOL) DESCRIPTION(SDSS_RET_PAF) DEFINE TRANSACTION(AABW) GROUP(SS0210) PROGRAM(SDSSPAF) * AppBuilder RULE SDSS_UPD_STAT DEFINE PROGRAM(SDSSUPST) GROUP(SS0210) LANGUAGE(COBOL) DESCRIPTION(SDSS_UPD_STAT) DEFINE TRANSACTION(AABX) GROUP(SS0210) PROGRAM(SDSSUPST) * AppBuilder RULE SDSS_CK_DEREF DEFINE PROGRAM(SDSSDREF) GROUP(SS0210) LANGUAGE(COBOL) DESCRIPTION(SDSS_CK_DEREF) DEFINE TRANSACTION(AABY) GROUP(SS0210) PROGRAM(SDSSDREF)
COPY GROUP(SS0210) TO(SDSS) REPLACE DELETE GROUP(SS0210)
IMS
A sample of the definitions generated for IMS follows. If these transactions have not already been defined to IMS, add them as part of the IMS stage-one generation input. * AppBuilder RULE R_RUNM_AA_ABB APPLCTN PSB=QA00M1AB,PGMTYPE=TP TRANSACT MODE=SNGL,PROCLIM=(,6),CODE=QA00M1AB, MSGTYPE=(MULTSEG,RESPONSE,),PRTY=(10,12,10) * AppBuilder RULE R_RUNM_AA_ABC APPLCTN PSB=QA00M1AC,PGMTYPE=TP TRANSACT MODE=SNGL,PROCLIM=(,6),CODE=QA00M1AC, MSGTYPE=(MULTSEG,RESPONSE,),PRTY=(10,12,10) * AppBuilder RULE R_RUNM_AA_ABD APPLCTN PSB=QA00M1AD,PGMTYPE=TP TRANSACT MODE=SNGL,PROCLIM=(,6),CODE=QA00M1AD, MSGTYPE=(MULTSEG,RESPONSE,),PRTY=(10,12,10) * AppBuilder RULE R_RUNM_AA_ABE APPLCTN PSB=QA00M1AE,PGMTYPE=TP TRANSACT MODE=SNGL,PROCLIM=(,6),CODE=QA00M1AE, MSGTYPE=(MULTSEG,RESPONSE,),PRTY=(10,12,10) * AppBuilder RULE R_RUNM_AA_ABF
6-21
Rollback Import
APPLCTN PSB=QA00M1AF,PGMTYPE=TP TRANSACT MODE=SNGL,PROCLIM=(,6),CODE=QA00M1AF, MSGTYPE=(MULTSEG,RESPONSE,),PRTY=(10,12,10) Restore the application from back-up data sets
If you requested the Restore option on the Installation Status panel, the application will restore all the data that was copied to the back-up libraries. Backup Required ===> Y (Y/N) Restore ===> N (Y/N) To review the restore JCL, type a Y in the Review(Y) column next to the appropriate job description.
Modifying the Data Set Size

The data sets created to install the run-time package import are set to sizes in the CONFIG procedure within the HAXIMPA REXX EXEC. If a data set is not large enough to accept the unload, increase the size of the data set DCB information variable. For example, the VIDTEXT file is not large enough to accept all the import VIDTEXT data. Change the VIDTEXT space variable from: VIDSPACE = "TRK,100,RLSE" to a larger size.
Rollback Import
The rollback import feature lets you back up existing application run-time libraries in the target environment, and then restore them after COPYAPP import has completed. You cannot roll back updated preparation timestamps (see Updating Preparation Timestamps). Backing Up the Existing Application Restoring the Backed-up Application
Backing Up the Existing Application

At the Backup dataset prompt in the COPYAPP import package window, enter a high-level qualifier for the datasets to which the existing application will be copied, as shown in Figure 6-20.
6-22
Rollback Import
Figure 6-20
Specifying the Backup Data Set
------------------- Runtime Package Installation Information ---------------COMMAND ===>
Package Name ==> Install from DASD or tape ==> D (D/T) To data set information Dataset Qualifier ==> SERPHC.SRI.IMP DASD Unit ==> SYSDA Volume (Optional) ==> From tape information Enter data if installing from tape. Unit to read your install tape ==> CART Volume Serial ==> Use bypass label processing ==> (Y/N) From DASD information Enter data if installing from DASD Data 80-byte record chopped fmt ==> Y (Y/N) From data set high-level qual ==> SERPHC.RSI.MIG.CHOPLIB Backup information Backup data set high-level qual ==> SERPHC.SRI.BK Configuration file INI mbr name ==> HAXIMPA Jobcard Information ===> //SERPHC2E JOB (DRHS-AZ),'UTILITIES PCOBLEY', ===> // NOTIFY=&SYSUID, ===> // CLASS=A,TIME=1440,MSGCLASS=D,MSGLEVEL=(1,1) ===> //* .$.0 010897 COPYAPP UTILITIES STUFF PCUTILA.JCL PHC 01 Enter END command to exit the installation. Press ENTER to continue.
Specify Y at the Backup required prompt in the COPYAPP import status window for each part of the application you submit for import, as shown in Figure 6-21. You can back up load modules, viewdef files, vidtext files, DB2 binds, and PSBs. If you are importing with RuleView data, you can also backup the rule relationship and rule source files. A backup dataset with the specified high-level qualifier is created for each part of the application you submit.
Figure 6-21
COMMAND ===> Runtime Installation Status Information Migration Name AL21II Display/Update/Reset library configuration ===> N Display/Update/Reset application configuration ===> N Backup Required ===> Y (Y/N) Restore ===> N
Specifying the Backup or Restore
(Y/N/R) (Y/N/R) (Y/N)
Job Description Job Status Generate JCL (Y) Config File UNLOADED Package Import UNLOADED Load Modules NOT STARTED Vidtext NOT STARTED Rule Relation NOT STARTED Rule Source NOT STARTED DB2 Binds NOT STARTED PSB Generation NOT STARTED System Install NOT STARTED Prepare Status NOT STARTED ****************************** Bottom of data ********************************
Restoring the Backed-up Application

Specify Y at the Restore prompt in the COPYAPP import status window for each part of the application you want to restore, then resubmit the job for that part, as shown in Figure 6-21. (COPYAPP automatically switches the Backup setting to N when the Restore setting is Y.) When the restore job completes, the job status changes from COMPLETED to RESTORED. For DB2 binds using packages, the restore function will bind the packages and perform the grants. If you are not using packages, only the DBRMs in the application will be restored. Generate the binds and grants for the DB2 plans manually.
6-23
Updating Preparation Timestamps
Note that to restore the transaction table and CICS definitions, (System Install), you must first restore your vidtext files. As a precaution against inadvertent imports, backup datasets are not deleted automatically after the application is restored. If you rerun COPYAPP import with backups, and use the same high level qualifier for the backup dataset names, COPYAPP will try to append to the existing backup datasets. This may cause copy failures or space allocation errors in your job output. Rename the backup datasets or delete them.

Suppose you migrate your application source code to a repository on the target environment, and then use COPYAPP to import your executables into the same environment. Since the executables for the application already exist on the target, it makes no sense to rebuild the application. Suppose further that you change an object in the application and then try to rebuild it: because none of the objects in the application was ever rebuilt on the target, rebuild analyze marks not only the changed object (and the objects it affects) for preparation, but every other object in the application. The preparation timestamp feature in AppBuilder lets you avoid this problem by generating preparation timestamps as if each preparable object in your executable had been rebuilt. For each such object, COPYAPP generates a timestamp that matches the time the executable was imported. You generate preparation timestamps for your application by submitting a Prepare Status job at COPYAPP import, as shown in Figure 6-22. All previous COPYAPP import jobs must have completed successfully before you can submit a Prepare Status job.
Figure 6-22
COMMAND ===> Runtime Installation Status Information Migration Name AL21II Display/Update/Reset library configuration ===> N Display/Update/Reset application configuration ===> N Backup Required ===> Y (Y/N) Restore ===> N
(Y/N/R) (Y/N/R) (Y/N)
Job Description Job Status Generate JCL (Y) Config File UNLOADED Package Import UNLOADED Load Modules COMPLETED Vidtext COMPLETED Rule Relation COMPLETED Rule Source COMPLETED DB2 Binds COMPLETED PSB Generation COMPLETED System Install COMPLETED Prepare Status NOT STARTED ****************************** Bottom of data ********************************
Note that you need not have migrated the source code for the application to the target environment before using this feature. We reommend you use the feature in sync with source code migration, to avoid situations in which an object you change in the source environment, and subsequently migrate to the target environment, is treated by Rebuild/Analyze as if it did not need to be reprepared, because it already has a COPYAPP-generated timestamp.. Note
You cannot roll back updated preparation timestamps.
6-24
CHAPTER
SETTING UP THE ENVIRONMENT
The migration environment-control variables control various aspects of migration processing. A thorough understanding of these variables and their effect on migration processing allows you to customize the Migration Facility to suit your environment. Since the values that you select change how you process migrations, tell all Migration Facility users which values you select for the variables. Although the installation team selects values for each variable during initial software installation, you can change them later. All values are stored in the @MIGENVn INI file (where n is the repository version) that is generated during the initial installation. (Rebuild environment-control variables are stored in the @RBDENVn INI file.) You can use the AppBuilder Installation Workbench to change the value of each variable. Refer to Enterprise Installation Guide for instructions on using the Installation Workbench. You can also modify the INI file directly, using the ISPF utilities. Table 7-1 lists the variables that appear in the @MIGENVn INI file. See Table 7-2 for information about the variables that affect automate migration (MIGRATE) action processing. Table 7-1 lists the migration environment-control variables in alphabetical order. Please note that this is not the order in which they appear in the @MIGENVn INI file.
Variables in the @MIGENVn INI file

For a list of these variables in the order in that they appear during Migration Facility installation, see Installing on an MVS Host. The impact column indicates whether the option affects an entire repository (R) or an instance of a migration entity (M).
Table 7-1 Name AMI_APPR Migration environment-control variables Description Do not change this migration state value. Valid values This value must be 2005. Any number greater than 0. 0- The rollback of any analyze failure will be performed at the migration level. Any error encountered during the processing will result in the rollback of all objects processed and the termination of the migration. Default value is 50. Impact R
AMI_COMMIT
Specify how often objects are committed. A value of 50 means that a DB2 commit is performed after every 50 objects and their parts.
7-1
Table 7-1 Name AMI_SUB AMI_EXEC AMI_FAIL AMI_PASS
Migration environment-control variables (Continued) Description Do not change this migration state value. Do not change this migration state value. Do not change this migration state value. Do not change this migration state value. Valid values This value must be 2001. This value must be 2002. This value must be 2003. This value must be 2004. S - The analyze step checks for collisions by system ID. If the name does not match, the target is updated with the source value, unless another target object has that name with a different system ID. In this case a collision is marked. L - The analyze step checks for collisions by long name. A collision is marked if either the name or system ID of the source and target objects do not match. Default value is L. Impact R R R R
ANALYZEKEY
Specify whether the analyze step checks for collisions by system ID or long name.
CHECK_REPOSIT
Validate migration from Source REPOSIT to Target REPOSIT. Specify if migration commands will respect predefined repository paths specified by the Administrator in the Repository to Repository relationship. A locked object may not be updated by another user or process until the original lock has been released. (Y) indicates that current locks will be honored and an (N) indicates that no locks will be honored which may result in lost changes. Specify the processing option used for the field containing the CICS transaction ID. This option only takes effect when the SEEREXIT variable is set to Y.
Y or N
CICSTRX
S - Take the value from the source migration data. T - Keep the existing target environment value. B - Set the value to blanks (no processing for field). Default value is T. Y - Collisions are errors. N - Collisions are not errors. Default value is Y. Y - Allow the migration entity to be deleted. N - Do not allow any user to delete any instance of the migration entity. Default value is N. Up to 30 characters. All characters must be upper case only. Default value is BLANK (no value).
CONSIDER_ COLLISION_AN_ERROR
Specify whether analyze marks collisions as an error.
DELMIG
Specify if the migration entity can be deleted by a user.
DESCRIPTION1
Define the user-defined QA status value used in selective export.
7-2
Setting Up the Environment
Table 7-1 Name
Migration environment-control variables (Continued) Description Define the user-defined QA status value used in selective export. Valid values Up to 30 characters. All characters must be upper case only. Default value is QA OK. Up to 30 characters. All characters must be upper case only. Default value is IN DEV. Up to 30 characters. All characters must be upper case only. Default value is IN DEV. Any number greater than 0. 0- The rollback of any export failure will be performed at the migration level. Any error encountered during the processing will result in the rollback of all objects processed and the termination of the migration. Default value is 0. This value must be 1001. This value must be 1002. This value must be 1003. This value must be 1004. Impact
DESCRIPTION2
DESCRIPTION3
DESCRIPTIONn
EXP_COMMIT
Specify whether export should be committed by number of objects or by migration.
EXP_SUB EXP_EXEC EXP_FAIL EXP_PASS
Do not change this migration state value. Do not change this migration state value. Do not change this migration state value. Do not change this migration state value. Specify whether the AppBuilder environment automatically runs a delta report with the analyze step when using Fastpath. You can run a delta report manually, regardless of how you set this variable.
M M M M
FAST_PATH_RUN_DELTA
Y - Run delta report with analyze. N - Do not run delta report with analyze. Default value is N.
IMP_COMMIT
Specify whether import should be committed by number of objects or by migration.
Any number greater than 0. 0- The rollback of any import failure will be performed at the migration level. Any error encountered during the processing will result in the rollback of all objects processed and the termination of the migration. Default value is 0. This value must be 3001. This value must be 3002. This value must be 3003. This value must be 3004.
IMP_SUB IMP_EXEC IMP_FAIL IMP_PASS
Do not change this migration state value. Do not change this migration state value. Do not change this migration state value. Do not change this migration state value.
M M M M
7-3
Table 7-1 Name
Migration environment-control variables (Continued) Description Specify the processing option used for the field containing the DB2 plan name. This option takes effect only when the SEEREXIT variable is set to Y. Specify the name of the command list (CLIST) or REXX EXEC to be executed after the completion of each migration job. The CLIST or REXX EXEC gains control, receives input indicating the function performed and the return code, which is how the jobs status is reported. A blank value indicates that no user CLIST or REXX EXEC is executed at the end of the jobs. Specify the data set high-level qualifier used for data sets accessed during migration processing. This is the default value if the user does not specify a value when maintaining the migration entity. The user must have allocate authorization for this qualifier when the export is performed. All other migration commands require read authorization. Do not change this value. It is an internal migration software version number that is not to be modified. Specify minimum explode DB2 CRUDs kept in memory when freeing memory. Specify minimum entity DB2 CRUDs kept in memory when freeing memory. Specify minimum entity ISPF CRUDs kept in memory when freeing memory. Specify minimum relation DB2 CRUDs kept in memory when freeing memory. Specify minimum relation ISPF CRUDs to be kept in memory when freeing memory. Specify maximum explode DB2 CRUDs kept in memory before memory is freed. Specify maximum entity DB2 CRUDs to be kept in memory before memory is freed. Valid values S - Take the value from the source migration data. T - Keep the existing target environment value. B - Set the value to blanks (no processing for field). Default value is T. Impact
IMSTRX
MIG_EXIT
The name must be a valid CLIST or REXX EXEC that is in the SYSPROC concatenation of the migration job. Default value is N/A.
MIG_FILE_ID
Any value that has a maximum length of eight and is a valid data set qualifier. Default value is HPSOUT.
MIGREL
Not for user modification. Default value is MHPS53AR.
MNBCRUD
A value between 1 and 99. Default value is 55. A value between 1 and 99. Default value is 35. A value between 1 and 99. Default value is 30. A value between 1 and 99. Default value is 35. A value between 1 and 99. Default value is 30. A value between 1 and 99. Default value is 60. A value between 1 and 99. Default value is 40.
MNECRD
MNEISPF
MNRCRUD
MNRISPF
MXBCRUD
MXECRUD
7-4
Table 7-1 Name MXEISPF
Migration environment-control variables (Continued) Description Specify maximum entity ISPF CRUDs to be kept in memory before memory is freed. Specify maximum relation DB2 CRUDs to be kept in memory before memory is freed. Specify maximum relation ISPF CRUDs kept in memory when freeing memory. Specify whether the user can override the default value for the Import will Create processing option. Specify whether the user can override the default value for the Import will Delete processing option. Specify whether the user can override the default value for the Process Keywords import option. Specify whether the user can override the default value for the Process Source import option. Specify whether the user can override the default value for the Process Text import option. Specify whether the user can override the default value for the Import will Update processing option. Specify the default value to be used for the Import will Create processing option. Valid values A value between 1 and 99. Default value is 45. A value between 1 and 99. Default value is 40. A value between 1 and 99. Default value is 35. Y - The user can override the option. N - The user cannot override the option. Default value is N. Y - The user can override the option. N - The user cannot override the option. Default value is N. Y - The user can override the option. N - The user cannot override the option. Default value is N. Y - The user can override the option. N - The user cannot override the option. Default value is N. Y - The user can override the option. N - The user cannot override the option. Default value is N. Y - The user can override the option. N - The user cannot override the option. Default value is N. Y - Process creates during the import. N- Do not process creates during the import. Default value is Y. Y - Process deletes during the import. N - Do not process deletes during the import. Default value is Y. Y - Process keywords during migration processing. N - Do not process keyword during migration processing. Default value is Y. Y - Process source during migration processing. N - Do not process source during migration processing. Default value is Y. Impact R
MXRCRUD
MXRISPF
OVCREATE
OVDELETE
OVKEYS
OVSOURCE
OVTEXT
OVUPDATE
PRCREATE
PRDELETE
Specify the default value to be used for the Import will Delete processing option.
PRKEYS
Specify the default value to be used for the Process Keywords option.
PRSOURCE
Specify the default value to be used for the Process Source option.
7-5
Table 7-1 Name
Migration environment-control variables (Continued) Description Valid values Y - Process text during migration processing. N - Do not process text during migration processing. Default value is Y. Y - Process updates during the import. N - Do not process updates during the import. Default value is Y. Y - Store job results in file. N - Do not store job results in file. Output instead goes to SYSOUT in the held output queue. Default value is Y. Y - Respect lock. N - Do not respect lock. Default value is Y. Y - Run collision detection with analyze. N - Do not run collision detection with analyze. Default value is N. Impact
PRTEXT
Specify the default value to be used for the Process Text option.
PRUPDATE
Specify the default value to be used for the Import will Update processing option.
RES_TO_FILE
Specify whether job results should be stored in a file.
RESPECT_IMP_ LOCK
Locked objects are not imported or whether locked objects are overridden. Specify whether the AppBuilder environment runs collision detection with the analyze step. Specify whether the AppBuilder environment runs a count report of objects included in the migration package. You can run a count manually, regardless of how you set this variable. Specify whether the AppBuilder environment automatically runs a delta report with the analyze step. You can run a delta report manually, regardless of how you set this variable.
RUN_COLLISION
RUN_COUNT
Y - Run count with each method. N - Do not run count with each method. Default value is Y.
RUN_DELTA
Y - Run delta with analyze. N - Do not run delta with analyze. Default value is N.
RUN_DETAIL
Specify whether the AppBuilder environment automatically runs a Y - Run detail with analyze. detail report with the analyze step. N - Do not run detail with analyze. You can run a detail report Default value is N. manually, regardless of how you set this variable. Specify whether the AppBuilder environment runs import even if collisions have been found. Specify whether the AppBuilder environment analyzes rebuild impact during the analyze job. You can run an analyze impact manually, regardless of how you set this variable. Y - Run import even if collisions have been found. N - Do not run import if collisions have been found. Default value is N.
RUN_IMP_IF_ COLLISION
RUN_RB DETECTOR
Y - Analyze rebuild impact. N - Do not analyze rebuild impact. Default value is N.
7-6
Automate Migration (MIGRATE) Action Variables
Table 7-1 Name
Migration environment-control variables (Continued) Description Specify whether Seer-supplied exits should be executed during the analyze migration impact (ANALYZE) action. This will determine the pending record to be used for updating the target repository. If SEEREXIT and USEREXIT are both enabled, SEEREXIT is processed first. Specify whether the analyze migration impact (ANALYZE) action requires another user to approve the migration prior to continuing to the import step. If this is set to Y, the Automated Migration Facility will fail before submission of the import job. Specify whether the import (IMPORT) action requires another user to approve the migration prior to continuing to the rebuild analyze step. If this is set to Y, the Automated Migration Facility will fail before submission of the rebuild analyze. Specify whether rebuild analyze requires another user to approve rebuild processing before continuing to the rebuild prepare step. If this is set to Y, the Automated Migration Facility will fail before submission of the rebuild prepare. Specify whether user-developed exits should be executed during the analyze migration impact (ANALYZE) action. This will determine the pending record to be used for updating the target repository. Specify a user-defined QA status value used in selective export. Specify a user-defined QA status value used in selective export. Specify a user-defined QA status value used in selective export. Valid values Y - Execute the Seer exit during the analyze process. This variable is required if the CICSTRX or IMSTRX variables are enabled. N - Do not execute the Seersupplied exit during analyze processing. Default value is Y. Y - The analyze step requires a second user to sign off prior to the import step. N - No sign-off of the analyze step is required prior to executing the import step. Default value is N. Y - The Import step requires a second user to sign off prior to the rebuild analyze step. N - No sign-off of the import step is required prior to executing the rebuild analyze step. Default value is N. Impact
SEEREXIT
SIGNAMI
SIGNIMP
SIGNRBD
Y - The rebuild analyze step requires a second user to sign off prior to rebuild prepare. N - No sign-off is required. Default value is N.
USEREXIT
Y - Execute the user exits during analyze processing. N - Do not execute the user exits during analyze processing. Default value is N. One-character value. Default value is blank (no value). One-character value. Default value is A. One-character value. Default value is B.
VALUE1 VALUE2 VALUE3
M M M

Use the variables in Table 7-2 to customize the automate migration (MIGRATE) action to your own environment. The automate migration action automates all of (or any segment of) migration
7-7
processing. The Impact column indicates whether the option affects an entire repository (R) or an instance of a migration entity (M).
Table 7-2 Name MIGRATE variables Description Valid values Y - Import the migration package during automated migration processing. N - Do not import the migration package during automated migration processing. Default value is N. Y - Analyze the rebuild package during automated migration processing. N - Do not analyze the rebuild package during automated migration processing. Default value is N. Y - Prepare the rebuild package during automated migration processing. N - Do not prepare the rebuild package during automated migration processing. Default value is Y. Y -Install the rebuild package during automated migration processing. N - Do not install the rebuild package during automated migration processing. Default value is Y. Y - Export the rebuild package during automated migration processing. N - Do not export the rebuild package during automated migration processing. Default value is Y. Y - The user can override the option. N - The user cannot override the option. Default value is N. Y - The user can override the option. N - The user cannot override the option. Default value is Y. Y - The user can override the option. N - The user cannot override the option. Default value is Y. Y - The user can override the option. N - The user cannot override the option. Default value is Y. Impact
RUNIMP
Specify the default value to be used for the Import Migration option.
RUNRBDA
Specify the default value to be used for the Analyze Rebuild Package option.
RUNRBDPR
Specify the default value to be used for the Prepare Rebuild Package option.
RUNRBDIN
Specify the default value to be used for the Install Rebuild Package option.
RUNRBDEX
Specify the default value to be used for the Export Rebuild Package option.
OVIMP
Specify whether the user can override the default value for the Import Migration option. Specify whether the user can override the default value for the Analyze Rebuild Package option. Specify whether the user can override the default value for the Prepare Rebuild Package option. Specify whether the user can override the default value for the Install Rebuild Package option.
OVRBDA
OVRBDPR
OVRBDIN
7-8
APPENDIX
MIGRATION STATUS VALUES
This appendix lists the migration status values used by the Migration Facility and the Rebuild Facility.
Migration Status Value Codes

Table A-1 lists the migration status value internal codes and descriptions; Table A-2 lists the rebuild status value internal codes and descriptions.
Table A-1 Migration status values Description Packaged Exported Loaded Not Packaged Not Exported Not Loaded Unchanged Import will Update Import will Create Import will Delete Collision Explicit Skip Unchanged Explicit Skip Update Explicit Skip Create Explicit Skip Delete Explicit Skip Collision Implicit Skip Unchanged Implicit Skip Update Implicit Skip Create Implicit Skip Delete Implicit Skip Collision Unchanged, Not Imported Internal Code 11 12 13 14 15 16 101 102 103 104 160 201 202 203 204 260 301 302 303 304 360 401
A-1
Table A-1
Migration status values (Continued) Description Update, Not Imported Create, Not Imported Delete, Not Imported Successful Unchanged Successful Update Successful Create Successful Delete Partial Unchanged of Partial Update of Partial Create of Successful Selective Delete Failed Unchanged Failed Update Failed Create Failed Delete Rolled Back Unchanged Rolled Back Update Rolled Back Create Rolled Back Delete
Internal Code 402 403 404 501 502 503 504 601 602 603 604 701 702 703 704 801 802 803 804
Table A-2 lists the rebuild status value internal codes and descriptions.
Table A-2 Rebuild status values Description Prepare Successful Prepare Incomplete Prepare Failed Prepare Executing Prepare Submitted Prepare Selected Prepare Needed Install Successful Install Incomplete Install Failed Install Executing Install Submitted Install Selected Install Needed Install Static Link Successful Install Static Link Incomplete Install Static Link Failed Install Static Link Executing Internal Code 6400 6404 6408 6410 6412 6413 6414 6500 6504 6508 6510 6512 6513 6514 6600 6604 6608 6610
A-2
Table A-2
Rebuild status values (Continued) Description Install Static Link Submitted Install Static Link Selected Install Static Link Needed Install Copy Successful Install Copy Incomplete Install Copy Failed Install Copy Executing Install Copy Submitted Install Copy Selected Install Copy Needed Install Top Bind Successful Install Top Bind Incomplete Install Top Bind Failed Install Top Bind Executing Install Top Bind Submitted Install Top Bind Selected Install Top Bind Needed Install LU2 Successful Install LU2 Incomplete Install LU2 Failed Install LU2 Executing Install LU2 Submitted Install LU2 Selected Install LU2 Needed Install Intermediate Bind Successful Install Intermediate Bind Incomplete Install Intermediate Bind Failed Install Intermediate Bind Executing Install Intermediate Bind Submitted Install Intermediate Bind Selected Install Intermediate Bind Needed
Internal Code 6612 6613 6614 6700 6704 6708 6710 6712 6713 6714 6800 6804 6808 6810 6812 6813 6814 6900 6904 6908 6910 6912 6913 6914 7000 7004 7008 7010 7012 7013 7014
A-3
A-4
APPENDIX
MIGRATION TABLES AND FILES
Migration data is stored in tables and files on the host. The content, structure, and layout of those tables and files are described in this appendix.
Migration Tables
All of the information required to process a migration and to review the status of objects in the migration is kept in the following control tables. ENT_LOGKEY E_MIGRTN R_MIGXX REL_LOGKEY
ENT_LOGKEY
MIG_ID MIG_TYPE LOGKEYP SYSTEMID LONGNAME META_TYPE META_ID MIG_STATUS RETURN_CODE REBUILD_IND SCOPE_TYPE TIME_STAMP VERSION PROJECT CHAR ( 8) NOT NULL CHAR ( 7) NOT NULL INTEGER NOT NULL CHAR (30) NOT NULL CHAR (30) NOT NULL WITH DEFAULT SMALLINT NOT NULL SMALLINT NOT NULL SMALLINT NOT NULL WITH DEFAULT INTEGER NOT NULL WITH DEFAULT CHAR ( 1) NOT NULL WITH DEFAULT CHAR ( 2) NOT NULL WITH DEFAULT TIMESTAMP NOT NULL WITH DEFAULT CHAR ( 1) NOT NULL WITH DEFAULT CHAR (10) NOT NULL WITH DEFAULT
B-1
Migration Tables
E_MIGRTN
SYSTEMID NAME DESCRIPTION MIG_DSN MIG_STATE RETURN_CODE PROCESSING_VERSION CREATION_DATE CREATION_TIME CREATED_BY DATE_MAINTAINED TIME_MAINTAINED MAINTAINED_BY PROJECT PROJ_LOCK_TYPE LOCK_ID CHANGE_N OWNER_ID QA_STATUS LOCAL_DATE LOCAL_TIME LOCAL_PROJECT LOCAL_USER_ID VERSION INMIG MIG_ID MIG_TYPE LOGKEYP META_TYPE META_ID LOGKEY_TYPE MIG_STATUS REBUILD_CHG_SEV RETURN_CODE REVISION_CHK DATA_CRC REBUILD_CRC TARGET_CRC TIME_STAMP VERSION CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR ( 8) (30) (30) (44) ( 4) ( 4) ( 1) ( 8) ( 5) ( 8) ( 8) ( 5) ( 8) (10) ( 2) ( 8) ( 4) ( 8) ( 2) ( 8) ( 8) (10) ( 8) ( 1) NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT
CHAR ( 8) CHAR ( 7) INTEGER SMALLINT SMALLINT SMALLINT SMALLINT SMALLINT INTEGER INTEGER INTEGER INTEGER INTEGER TIMESTAMP CHAR ( 1)
NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
WITH WITH WITH WITH WITH WITH WITH WITH
DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT
B-2
Migration Tables and Files
Migration Tables
R_MIGXX
Y_ENTITY_TYPE Y_INSTANCE_ID SEQNO X_ENTITY_TYPE X_INSTANCE_ID SEP_ID SCOPE_TYPE SEED_STATUS HAS_REUSE CREATION_DATE CREATION_TIME CREATED_BY DATE_MAINTAINED TIME_MAINTAINED MAINTAINED_BY CHANGE_N QA_STATUS LOCAL_DATE LOCAL_TIME LOCAL_PROJECT LOCAL_USER_ID VERSION CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR CHAR ( 7) (30) ( 3) ( 7) (30) ( 3) ( 2) ( 4) ( 1) ( 8) ( 5) ( 8) ( 8) ( 5) ( 8) ( 4) ( 2) ( 8) ( 8) (10) ( 8) ( 1) NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH WITH DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT DEFAULT
REL_LOGKEY
MIG_ID MIG_TYPE REL_LOGKEYP Y_LOGKEYP X_LOGKEYP SEQNO SEP_ID META_TYPE META_ID MIG_STATUS RETURN_CODE TIME_STAMP VERSION CHAR ( 8) CHAR ( 7) INTEGER INTEGER INTEGER CHAR ( 3) CHAR ( 3) SMALLINT SMALLINT SMALLINT INTEGER TIMESTAMP CHAR ( 1) NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL
WITH DEFAULT WITH DEFAULT
WITH WITH WITH WITH
DEFAULT DEFAULT DEFAULT DEFAULT
B-3
Migration Files
Migration Files
Migration control information and data are stored in migration files with the structures and layouts described in the Header and Row Structures and File Layouts. Please note the following: Short integers are converted to CHAR(05) Long integers are converted to CHAR(10) Integers being represented as character strings are padded with leading zeros Character strings are left-justified and padded with trailing blanks Entity and relation data records are formatted according to data dictionary definitions based on object type, platform, and release
Header and Row Structures

This section describes the structure of the headers and rows in the migration files: File Header Data Header Audit Header Entity Logkey Row Relation logkey row Inmig Row
File Header
EYE_CATCHER BLANK_DELIMITER MIG_TYPE BLANK_DELIMITER MIG_ID BLANK_DELIMITER META_TYPE BLANK_DELIMITER REP_ID BLANK_DELIMITER VERSION BLANK_DELIMITER PLATFORM BLANK_DELIMITER TIME_STAMP CHAR(07) CHAR(01) CHAR(07) CHAR(01) CHAR(08) CHAR(01) CHAR(04) CHAR(01) CHAR(02) CHAR(01) CHAR(01) CHAR(01) CHAR(08) CHAR(01) CHAR(26)
B-4
Migration Files
Data Header
EYE_CATCHER BLANK_DELIMITER LOGKEY_TYPE BLANK_DELIMITER LOGKEYP BLANK_DELIMITER META_ID BLANK_DELIMITER DATA_LENGTH CHAR(07) CHAR(01) CHAR(05) CHAR(01) CHAR(10) CHAR(01) CHAR(05) CHAR(01) CHAR(10)
Audit Header
EYE_CATCHER BLANK_DELIMITER CREATION_DATE BLANK_DELIMITER CREATION_TIME BLANK_DELIMITER CREATED_BY BLANK_DELIMITER DATE_MAINTAINED BLANK_DELIMITER TIME_MAINTAINED BLANK_DELIMITER MAINTAINED_BY BLANK_DELIMITER PROJECT BLANK_DELIMITER PROJECT_LOCK_TYPE BLANK_DELIMITER LOCK_ID BLANK_DELIMITER CHANGE_NUMBER BLANK_DELIMITER OWNER_ID BLANK_DELIMITER QA_STATUS EYE_CATCHER CHAR(07) CHAR(01) CHAR(08) CHAR(01) CHAR(05) CHAR(01) CHAR(08) CHAR(01) CHAR(08) CHAR(01) CHAR(05) CHAR(01) CHAR(08) CHAR(01) CHAR(10) CHAR(01) CHAR(02) CHAR(01) CHAR(08) CHAR(01) CHAR(05) CHAR(01) CHAR(09) CHAR(01) CHAR(02) CHAR(07)
B-5
Migration Files
Entity Logkey Row

MIG_ID BLANK_DELIMITER MIG_TYPE BLANK_DELIMITER LOGKEYP BLANK_DELIMITER SYSTEMID BLANK_DELIMITER LONGNAME BLANK_DELIMITER META_TYPE BLANK_DELIMITER META_ID BLANK_DELIMITER MIG_STATUS BLANK_DELIMITER REBUILD_IND BLANK_DELIMITER SCOPE_TYPE BLANK_DELIMITER TIME_STAMP BLANK_DELIMITER VERSION BLANK_DELIMITER PROJECT CHAR(08) CHAR(01) CHAR(07) CHAR(01) CHAR(10) CHAR(01) CHAR(30) CHAR(01) CHAR(30) CHAR(01) CHAR(05) CHAR(01) CHAR(05) CHAR(01) CHAR(05) CHAR(01) CHAR (01) CHAR(01) CHAR(02) CHAR(01) CHAR(27) CHAR(01) CHAR(01) CHAR(01) CHAR(10)
Relation logkey row

MIG_ID BLANK_DELIMITER MIG_TYPE BLANK_DELIMITER REL_LOGKEYP BLANK_DELIMITER Y_LOGKEYP BLANK_DELIMITER X_LOGKEYP BLANK_DELIMITER SEQNO BLANK_DELIMITER SEP_ID BLANK_DELIMITER META_TYPE BLANK_DELIMITER META_ID BLANK_DELIMITER MIG_STATUS BLANK_DELIMITER TIME_STAMP BLANK_DELIMITER VERSION CHAR(08) CHAR(01) CHAR(07) CHAR(01) CHAR(10) CHAR(01) CHAR(10) CHAR(01) CHAR(10) CHAR(01) CHAR(03) CHAR(01) CHAR(03) CHAR(01) CHAR(05) CHAR(01) CHAR(05) CHAR(01) CHAR(05) CHAR(01) CHAR(27) CHAR(01) CHAR(01)
B-6
Migration Files
Inmig Row
MIG_ID BLANK_DELIMITER MIG_TYPE BLANK_DELIMITER LOGKEYP BLANK_DELIMITER META_TYPE BLANK_DELIMITER META_ID BLANK_DELIMITER LOGKEY_TYPE BLANK_DELIMITER MIG_STATUS BLANK_DELIMITER REBUILD_CHG_SEV BLANK_DELIMITER RETURN_CODE BLANK_DELIMITER REVISION_CHK BLANK_DELIMITER DATA_CRC BLANK_DELIMITER REBUILD_CRC BLANK_DELIMITER TARGET_CRC BLANK_DELIMITER TIME_STAMP BLANK_DELIMITER VERSION CHAR(08) CHAR(01) CHAR(07) CHAR(01) CHAR(10) CHAR(01) CHAR(05) CHAR(01) CHAR(05) CHAR(01) CHAR(05) CHAR(01) CHAR(05) CHAR(01) CHAR(05) CHAR(01) CHAR(10) CHAR(01) CHAR(10) CHAR(01) CHAR(10) CHAR(01) CHAR(10) CHAR(01) CHAR(10) CHAR(01) CHAR(27) CHAR(01) CHAR(01)
B-7
Migration Files
File Layouts
This section describes the layouts of the migration files: Mainframe File Name: MIG.ELOGKEY Mainframe File Name: MIG.RLOGKEY Mainframe File Name: MIG.INMIG Mainframe File Name: .MIGXX Mainframe File Name: .MIGCNTL Mainframe File Name: .ENTITY Mainframe File Name: .RELATE Mainframe File Name: .TEXT Mainframe File Name: .KEYWORD Mainframe File Name: .SOURCE Mainframe File Name: .SRCBHDR Mainframe File Name: .SRCBDAT
Mainframe File Name: MIG.ELOGKEY Workstation File Name: ELOG.FIL FILE HEADER ENTITY LOGKEY ROW (1) ENTITY LOGKEY ROW (2) to ENTITY LOGKEY ROW (n) Mainframe File Name: MIG.RLOGKEY
Workstation File Name: RLOG.FIL FILE HEADER RELATION LOGKEY ROW (1) RELATION LOGKEY ROW (2) to RELATION LOGKEY ROW (n) Mainframe File Name: MIG.INMIG Workstation File Name: INMIG.FIL FILE HEADER INMIG ROW (1) INMIG ROW (2) to INMIG ROW (n)
B-8
Migration Files
Mainframe File Name: .MIGXX Workstation File Name: MIGXX.FIL FILE HEADER Data Record (defined by data dictionary) Mainframe File Name: .MIGCNTL Workstation File Name: MIGCNTL.FIL (MIGCNTL) REPNAME=Value PRKEY=Value PRSOURCE= Value PRTXT= Value PRREL= Value PRENT= Value PCCODEPG=Value MFCODEPG= Value MIGREL=Value HPSREL=Value TIME=Value DATE=Value V=Value Mainframe File Name: .ENTITY Workstation File Name: ENT.FIL FILE HEADER DATA HEADER (1) Data Record (1) DATA HEADER (2) Data Record (2) to DATA HEADER (n) Data Record (n) Mainframe File Name: .RELATE Workstation File Name: REL.FIL FILE HEADER DATA HEADER (1) Data Record (1) DATA HEADER (2) Data Record (2) to DATA HEADER (n) Data Record (n)
(Repository name) (Y or N) (Y or N) (Y or N) (Y or N) (Y or N) (PC code page number) (MF code page number) (Migration release) (APPBUILDER release)
B-9
Migration Files
Mainframe File Name: .TEXT Workstation File Name: TEXT.FIL FILE HEADER DATA HEADER (1) AUDIT HEADER (1) Data Record (1) DATA HEADER (2) AUDIT HEADER (2) Data Record (2) to DATA HEADER (n) AUDIT HEADER (n) Data Record (n) Mainframe File Name: .KEYWORD Workstation File Name: KEY.FIL FILE HEADER DATA HEADER (1) AUDIT HEADER (1) Data Record (1) DATA HEADER (2) AUDIT HEADER (2) Data Record (2) to DATA HEADER (n) AUDIT HEADER (n) Data Record (n) Mainframe File Name: .SOURCE Workstation File Name: SRCT.FIL FILE HEADER DATA HEADER (1) AUDIT HEADER (1) Data Record (1) DATA HEADER (2) AUDIT HEADER (2) Data Record (2) to DATA HEADER (n) AUDIT HEADER (n) Data Record (n) Mainframe File Name: .SRCBHDR Workstation File Name: SRCBHDR.FIL
B-10
Migration Files
FILE HEADER DATA HEADER (1) AUDIT HEADER (1) DATA HEADER (2) AUDIT HEADER (2) to DATA HEADER (n) AUDIT HEADER (n) Mainframe File Name: .SRCBDAT Workstation File Name: SRCBDAT.FIL Data Record (1) Data Record (2) to Data Record (n)
B-11
Migration Files
B-12
APPENDIX
MIGRATION EXITS
The Migration Facility exits, also called hooks, are points in Migration Facility software where you have the option of exiting to a routine to perform specialized processing.
Using Migration Facility Exits

An exit can be thought of as a door that you can open to pass control to a custom routine. After the custom routine finishes processing, the exit routine closes the door and returns control to the Migration Facility. The Migration Facility has three types of exits, which are listed in Table C-1.
Table C-1 Exit type System Exit User Exit Migration Facility exit options Description Exit to a routine written by Seer Technologies. Exit to a routine written by you or another user. See Sample Exit Code. Exit to a command list (CLIST) you invoke each time the job state of a migration entity is updated. For example, you might use the CLIST exit to exit to a third-party or user-written routine that notifies a particular TSO user ID of the status of a Migration batch job.
CLIST Exit
System Exit
The system exit lets you exit to a subroutine written and delivered by BluePhoenix Solutions. At this time, there is only one system exit. You cannot change the functionality of the system exit. The system exit lets you determine the pending transaction ID value for a rule entity. Your decision to implement the system exit option depends on your broader strategy for assigning CICS/IMS transaction IDs or DB2 plan names. Figure C-1 shows the attributes of a rule entity, which includes the CICS/IMS/DB2 Plan Name attribute.
C-1
System Exit
Figure C-1
Attributes of a rule entity
Rule Attributes: Name . . . . . . . . System Id . . . . . . Execution Environment CICS / IMS / DB2 Plan DBMS Usage . . . . . Description . . . . . Execution Mode . . . Implementation Name . Package . . . . . . . Isolation Mode . . .
. . . . . . . . . Name . . . . . . . . . . . . . . . . . .
. : . : . . . . . .
Audit Attributes: Date Created . . . . . . . : Time Created . . . . . . . : Created by . . . . . . . . : Date Maintained . . . . . . : Time Maintained . . . . . . : Maintained by . . . . . . . : Project . . . . . . . . . . : Change # . . . . . . . . . : Owner Id . . . . . . . . . : Local Maintenance Date . . : Local Maintenance Time . . : Local Maintenance Project . : Local Maintenance User . . : Version . . . . . . . . . . :
When you use the Migration Facility to copy software from a source to a target environment, you often find entities with the same name or system ID attribute in the source and target environments. The system exit allows you to select whether you want the pending import value to be the source value, the target value, or a blank value. The system exit is always processed first. If you implement both the Seer and the user exit options, the system exit is processed first and the user exit second. When you install AppBuilder software, you define values for environment-control variables. A subset of these variables controls the Migration Facility environment (see Chapter 7, Setting Up the Environment). To enable the system exit option, modify the migration environment-control variables through the host AppBuilder Installation Workbench. See the Enterprise Installation Guide for detailed instructions on using the AppBuilder Installation Workbench. Note
You can also use your system editor to open the @MIGENVn INI file and modify the variables directly.
Find the SEEREXIT variable and select one of the values listed in Table C-2..
Table C-2 Value N SEEREXIT variable Description Disables the system exit. Default value.
C-2
Migration Exits
User Exit
Table C-2 Value Y
SEEREXIT variable (Continued) Description Enables the system exit. Do not switch this variable to Y until you fully develop and test your custom routine.
Then find the CICSTRX and IMSTRX variables and, for each one, specify one of the three values described in Table C-3. The CICSTRX and IMSTRX variables override all Migration Facility options but take effect only when you set the SEEREXIT variable to Y.
Table C-3 Value S T B CICSTRX and IMSTRX variable values Description Takes the source value (in the migration package) and overwrites the plan name value in the target environment. This is the default value. Keeps the existing target environment value. Refreshes the target value to blank.
User Exit
You can write a customized routine that is invoked during analyze migration impact (ANALYZE) action processing to modify the pending import value of a specific attribute. The attribute can be unique to one entity or relationship type or common to all entity and relationship types. You can choose to perform the exit routine on any entity or relationship type, but not on all attributes. Note
You cannot use an exit routine to alter either the name or system ID value of an object.
For example, suppose you want to modify the Owner ID attribute value before import. The Owner ID attribute is common to all entity and relationship types that specifies the TSO user ID of the individual who either created or currently has ownership of the object. Figure C-2 shows the attributes of a rule entity. Suppose that for every object in a migration package, you want to change the existing Owner ID attribute value to a new value at import. You could change the Owner ID value for a specific object type or all object types. So, for example, you could specify that any object with the Owner ID value XX102 be changed to XX100 before import. You could also specify that only rule entities have their Owner ID changed to that value.
C-3
User Exit
Figure C-2
Attributes of a rule entity
Rule Attributes: Name . . . . . . . . System Id . . . . . . Execution Environment CICS / IMS / DB2 Plan DBMS Usage . . . . . Description . . . . . Execution Mode . . . Implementation Name . Package . . . . . . . Isolation Mode . . . Audit Attributes: Date Created . . Time Created . . Created by . . . Date Maintained . Time Maintained . Maintained by . . Project . . . . . Change # . . . . Owner Id . . . . Local Maintenance Local Maintenance Local Maintenance Local Maintenance Version . . . . . Note
. . . . . . . . . Name . . . . . . . . . . . . . . . . . .
. : . : . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Date . Time . Project User . . . . .
. . . . . . . . . . . . . .
: : : : : : : : : : : : : :
The exit is invoked for every object analyzed in a migration package. To minimize unnecessary performance overhead, the exit should contain only pertinent processing. The more processing required for each record, the greater the demand on system performance.
To create your own Migration Facility exit routine: 1. 2. Design and code your exit routine. Seer provides the sample structure required to create the exit; however, it is your responsibility to develop and maintain the specific program required. Gather the following information: Documentation on the available functionality, usage, limitations, and guidelines. Record formats for all entities and relationships. Each object has a different structure representing its record type. See Appendix D, Migration Processing Attributes for a list of attributes for each entity and relationship type. Sample code. 3. 4. Call the exit routine GLXUSER. The exit routine must be a C function, declared as type void(). Compile the function using the same C370 compiler version as the one required by AppBuilder software for run-time libraries. Make this data set available to the compiler by concatenating it in the JCL compile job. Link the exit routine into the GALOAD load module in the BASE.CICS.LOADLIB data set. Use the GALOAD link member, found in BASE.LINKBASE. This data set contains a member for each load module. The GALOAD link member already contains an entry for GLXUSER when delivered. You must relink this load module as specified by Installing on an MVS Host for performing maintenance.
5.
C-4
Migration Exits
User Exit
6.
If your program contains any SQL, it must be bound to a package. The collection of packages must be prefixed by HPS5.* (where HPS5.* is the plan name used for AppBuilder system software). Under normal circumstances HPS5 is prefixed by a customer-designated plan prefix. You must do this manually because AppBuilder software does not perform the bind job. Perform a unit test before you test your program with the AppBuilder Migration Facility. You can perform the test by using a test harness that calls the GLXUSER function. Note that all cases should be tested, including records of the same and different object type that do not require change. Only when your program has been fully unit tested should you relink it (and bind if necessary) into AppBuilder software. Then test it further to ensure its reliability. To view the pending data, use the migration REP action to generate a delta report. To see whether your exit routine processed successfully, look in the delta report. The letter e in this column indicates that the value resulted from user exit processing, rather than from standard migration processing, which is indicated by an asterisk (*). See Generate a Delta Report on page 5-29 for information about generating and viewing a delta report.
7.
8.
9.
Maintain the exit program. You are responsible for updating the exit program in response to changes to the data record format made by Seer Technologies. Seer reserves the right to change the record formats at any time. Seer Technologies provides only record formats for migration data that support exit processing. Seer does not support processing of any other types of information.
Sample Exit Code

The following sample code can assist you in developing your custom user exit routine.
******************************** TOP OF DATA ********************************** ********************************************************************/ 00010000 * Migration User Exit */ 00020001 * */ 00030000 * 001 */ 00031000 * 002 523 93/10/18 arc changed blank option from R to B */ 00032000 * */ 00040000 ********************************************************************/ 00050000 include <stdio.h> 00060000 include <stdlib.h> 00070000 include <string.h> 00080000 00090000 00110000 *********************************************************************/ 00120000 * External Routines */ 00130000 *********************************************************************/ 00140000 00170000 *********************************************************************/ 00180000 * individual custom exits */ 00190000 *********************************************************************/ 00200000 int ux_erule (char *,char); 0021000 0023000 /*********************************************************************/ 0050100 /* Global Variables */ 0050200 /*********************************************************************/ 0050300 0050400 /*********************************************************************/ 0051000 /*********************************************************************/ 0052000 /***** E X I T D R I V E R S *****/ 0053000 /*********************************************************************/ 0054000 /*********************************************************************/ 0055000 0056000 /*********************************************************************/ 0057000 /***** U S E R E X I T D R I V E R *****/ 0058000 /*********************************************************************/ 0059000 /* Routine: UserExit */ 0060000 /* Purpose: Migration entity exit allows the user to manipulate */ 0061000
C-5
CLIST Exit
/* the incomming data. */ /* */ /* */ /* Inputs: short Object type - ent or rel */ /* short Object meta id - rule comp rulrul */ /* char *Data record */ /* char TargetVersion */ /* */ /*********************************************************************/ int UserExit(short ObjectType, short MetaId, char *DataRecord, char TargetVersion) { #include "glxmeta.h"
0062000 0063000 0064000 0065000 0066000 0067000 0067100 0068000 0069000 0070000 0070100 0071000 0072000 0073000 0073100 0073200 if (MetaId == METAID_RULE ) 0074000 return(ux_erule(DataRecord,TargetVersion)); 0074010 0076000 } /* end UserExit */ 0077000 0078000 /*********************************************************************/ 0119000 /*********************************************************************/ 0120000 /***** C U S T O M E X I T S *****/ 0121000 /*********************************************************************/ 0122000 /*********************************************************************/ 0123000 0124000 /*********************************************************************/ 0125000 /***** R U L E E X I T *****/ 0126000 /*********************************************************************/ 0127000 /* Routine: ux_erule */0128000 /* Purpose: Specific rule processing: */ 0129000 /* */ 0132000 /* Inputs: record from the source repository */ 0133000 /* target version */ 0135000 /* */ 0135100 /*********************************************************************/ 0136000 int ux_erule(char *data_rec,char TargetVersion) 0137000 { 0139000 #include "mgrule.h" 0140000 struct xerule *rule_rec; 0144000 int rc=0; 0146000 0146100 rule_rec = (struct xerule *)data_rec; 0147000 0149000 /*****************************************************************/ 0155000 /* testing */ 0156000 /*****************************************************************/ 0159000 /* 0159300 memcpy(rule_rec->RULE_SOURCE, 0161000 "TESTING ", 0162000 sizeof(rule_rec->RULE_SOURCE)); 0163000 */ 0193950 return(rc); 0193960 0194000 } /* end ux_erule */ 0195000 0196000 ******************************** BOTTOM OF DATA *******************************
CLIST Exit
One of the things you might want to use the CLIST exit for is to invoke a function to send a message to a TSO user ID regarding the status of a migration batch job. The function may be either third-party or written by you to notify another migration project user of the following: The progress of a large migration batch job An approved analyze migration impact (ANALYZE) job
C-6
Migration Exits
CLIST Exit
1.
You activate the CLIST exit option by entering a specific name value for the MIGSTATE migration environment-control variable (see Table C-4). The default value is blank.
STATEXIT variable Description Specifies the name of the CLIST to be run after the completion of migration action processing. The default value is blank.
Table C-4 Value
Optional Exit CLIST Name (No default)
2. 3.
If you specify a CLIST name, the system invokes the CLIST each time that a migration batch job state is posted. The CLIST must include the parameters listed in Table C-5. These variables are passed as parameters and can therefore be accessed by the CLIST. The STATUS1 variable is set following the completion of all migration processing. The migration return codes, which are held in the R_INMIG table, are already updated before the invocation of the CLIST.
Table C-5
CLIST variables and values Values GMP (PACKAGE) EXP (EXPORT) LMP (LOAD) AMI (ANALYZE) IMP (IMPORT) RBD (REBUILD) 0000 1001 1002 1003 1004 2001 2002 2003 2004 2005 3001 3002 3003 3004 0000 1001 1002 1003 1004 6100 6104 6300 6304 6308 6310 6312 6400 6404 6408 6410 6412 6500 6504 6508 6510 6512 N/A Export Job Submitted Export Job Executing Export Job Failed Export Successful Analyze Job Submitted Analyze Job Executing Analyze Job Failed Analyze Successful Analyze Approved Import Job Submitted Import Job Executing Import Job Failed Import Successful N/A Export Job Submitted Export Job Executing Export Job Failed Export Successful Seeded Exceptions Seeded Rebuild Analyze Successful RBDA Successful w/Excepti Rebuild Analyze Failed Rebuild Analyze Executing Rebuild Analyze Submitted Rebuild Prepare Successful Rebuild Prepare Incomplete Rebuild Prepare Failed Rebuild Prepare Executing Rebuild Prepare Submitted Rebuild Install Successful Rebuild Install Incomplete Rebuild Install Failed Rebuild Install Executing Rebuild Install Submitted
CLIST variables
MIGMTH Characters signifying the action or method just run.
MIGSTATE A code that signifies the state of the action or method just executed.
RBDSTATE A code that signifies the state of the action or method just executed.
C-7
CLIST Exit
Table C-5
CLIST variables and values (Continued) Values Migration entity system ID value, which has a maximum value of seven characters. The first character is always alphabetic and the remaining six can be either alphabetic or numeric. The version of the repository in which you created the migration object; always one number.
CLIST variables SYSTEMID The system ID of the migration object the action or method was executed against. V
4.
Place the CLIST in the MOD.CLIST data set so that it is available for the Migration Facility actions.
C-8
Migration Exits
APPENDIX
MIGRATION PROCESSING ATTRIBUTES
For migration purposes, entity and relationship attributes are logically split into two types: Significant attributes Insignificant attributes For significant attributes, changes in value between the source values and target values of result in target repository updates. For insignificant attributes, changes in value between source values and target values of do not result in target repository updates. This appendix discusses the Audit Attributes and how the enterprise and Freeway Migrations are handled when data is migrated between the two repositories. It also provides a list of the significant and insignificant attributes for all repository objects in Object Attribute Listings.
Audit Attributes
You can satisfy your audit and change control requirements by reconciling when objects were modified (with maintenance data) and how they were introduced into the repository (with local repository data). The following sections contain the audit information processing for create, maintenance, and repository data. Create Data Maintenance Data Repository Data
D-1
Audit Attributes
Create Data
The following attributes represent the create data fields the enterprise server will update for an object: CREATED DATE CREATED TIME CREATED BY MAINTAINED DATE MAINTAIN TIME MAINTAINED BY PROJECT OWNER ID They are updated when the object is created by a repository function such as create and upload from a personal repository. These values will remain the same on the source, and will be updated on the target when the object is migrated. Migrations considers these significant attributes, so any change between the source values and the target values will update the target repository with the source values.
Maintenance Data
The following attributes represent the maintenance data fields the enterprise server will update for an object: MAINTAINED DATE MAINTAINED TIME MAINTAINED BY They are updated when the object is created or maintained by a repository function such as maintain, prepare, and upload from a personal repository. These values will remain the same on the source, and will be updated on the target when the object is migrated. Migrations will consider these significant attributes, so any change between the source values and the target values will update target repository with the source values.
Repository Data
The following attributes represent the repository data fields the enterprise server will update for an object: CHANGE NUMBER LOCAL MAINTENANCE DATE LOCAL MAINTENANCE TIMEc LOCAL USER LOCAL PROJECT
D-2
Migration Processing Attributes
Freeway Migrations
They are updated when the object is created or maintained by a repository function or moved by a migration. Migrations will consider these insignificant attributes, so any change between the source value and the target value will not update the target repository.
Freeway Migrations
Freeway repositories do not update the same audit block as the enterprise repository. When an entity or relationship object is updated in a Freeway repository, the enterprise repository audit information is not updated. When the same object is migrated back to the enterprise repository, the maintenance information remains unchanged. The enterprise repository will update the LOCAL stamp, which represents when the object was migrated. However, any information that the object was maintained in the Freeway repository is lost. When the source, text, or keyword object is being updated, the enterprise repository will modify the maintenance data (MAINTAINED DATE, MAINTAIN TIME, and MAINTAINED BY) along with the repository data, which are insignificant attributes. The other fields in the audit block remain unchanged. When the source, text, or keyword object is being created, the enterprise repository will modify all the fields in the audit block (maintenance, repository, and create data). The current time and date stamps will be used for the time and date fields. The OWNER-ID field is populated with the user who is performing the migration. The PROJECT field is populated with the current project defined for the repository. They are updated when the object is created or maintained by a repository function such as maintain, prepare and upload from a personal repository. These values will remain the same on the source, and will be updated on the target when the object is migrated. Migrations will consider these significant attributes, so any change between the source values and the target values will update target repository with the source values. This appendix lists the attributes with four columns of information, as described in Table D-1
Object Attribute Listings

Table D-2 lists the object attributes and descriptions of their values and definitions, while Table D-2 lists the definitions of the column headings in the attributes table.
Table D-1 Heading Object type System name Attribute name Significant or Insignificant Appendix D column headings Description This value is either ENTITY or RELATE (relationship). The system name of an entity or relationship type. For example, APPCFG is the system name for the application configuration entity type. The attribute name used on the user interface panels. If this value is Y, the attribute is significant. If the value is N, the attribute is insignificant.
D-3
Table D-2
Object Attributes and Descriptions System Name APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG APPCFG Attribute Name System Id Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP
System Id Name Assumption Type Priority Act Start Plnd Start Conf Level Risk Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N
D-4
Table D-2
Object Attributes and Descriptions (Continued) System Name ASSUMP ASSUMP ASSUMP ASSUMP ASSUMP Attribute Name Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY
ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB ATTRIB
System Id Name Derived Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP
System Id Name Type Implementation Name Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id
Y Y Y N N Y Y Y Y Y Y Y N N
(Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy)
D-5
Table D-2
Object Attributes and Descriptions (Continued) System Name BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP BITMAP Attribute Name Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP BMPIMP
System Id Name Country Language X Resolution Y Resolution Format Type Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
(Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy)
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ
System Id Name Description Type Date Created Time Created Created by Date Maintained
Y Y Y Y Y Y Y Y
D-6
Table D-2
Object Attributes and Descriptions (Continued) System Name BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ BUSOBJ Attribute Name Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST CAPLST
System Id Customer Group Id Customer Group Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
CELL CELL CELL CELL CELL CELL
System Id Name Protocol Date Created Time Created Created by
Y Y Y Y Y Y
D-7
Table D-2
Object Attributes and Descriptions (Continued) System Name CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL Attribute Name Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT
System Id Name Type Implementation Name Protocol Server Link Type Server Start Type Server Cell Rank Owner Qualifier Plan Name Collection Id Isolation Mode Minimum Transaction Id Maximum Transaction Id Unit Of Work Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change #
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N
D-8
Table D-2
Object Attributes and Descriptions (Continued) System Name CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT CFGUNIT Attribute Name Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT COLLECT
System Id Name Type Nature Number Of Elements Number Of Groups Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN
System Id Name Implementation Name Column Format Column Length Column Fraction Average Length Date Created Time Created
Y Y Y Y Y Y Y Y Y
D-9
Table D-2
Object Attributes and Descriptions (Continued) System Name COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN COLUMN Attribute Name Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP
System Id Name Execution Environment Info Src Language Subroutine DBMS Usage Description Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N
(Hierarchy) (Hierarchy) (Hierarchy) (Object) (Hierarchy) (Hierarchy) (Hierarchy)
(Hierarchy)
D-10
Table D-2
Object Attributes and Descriptions (Continued) System Name COMP Attribute Name Version Significant? N
Object Type ENTITY
CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP CSTGRP
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS CURSYS
System Id Name Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project
Y Y Y Y Y Y Y Y Y Y N N N Y N N N N
D-11
Table D-2
Object Attributes and Descriptions (Continued) System Name CURSYS CURSYS Attribute Name Local Maintenance User Version Significant? N N
Object Type ENTITY ENTITY
CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST CUST
System Id Customer Id Customer Name Customer Title Customer Code Business Telephone Number Business Telephone Extension Home Telephone Number Profile Filename Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA
System Id Name Data Format Data Length Data Fraction Date Created Time Created Created by Date Maintained Time Maintained Maintained by
Y Y Y Y Y Y Y Y Y Y Y
D-12
Table D-2
Object Attributes and Descriptions (Continued) System Name DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA DATA Attribute Name Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS DATABAS
System Id Name Implementation Name Type Machine Name Database Directory Path Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY
DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG
System Id Name Drawing Type Date Created Time Created
Y Y Y Y Y
D-13
Table D-2
Object Attributes and Descriptions (Continued) System Name DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG DRAWNG Attribute Name Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT ENT
System Id Name Entity Type Expected Minimum Rows Expected Maximum Rows Activity Period Average Inserts for Period Average Deletes for Period Average Updates for Period Expected Rows Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N
D-14
Table D-2
Object Attributes and Descriptions (Continued) System Name ENT ENT Attribute Name Local Maintenance User Version Significant? N N
Entity Type Name Screen Description Entity Code Implementation Name Migration File Name Implementation Storage Exit Routine Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT
System Id Name Description Event Type Event Class Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project
Y Y Y Y Y Y Y Y Y Y Y Y
D-15
Table D-2
Object Attributes and Descriptions (Continued) System Name EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT EVENT Attribute Name Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE FILE
System Id Name File Type Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
(Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy)
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
FLD FLD FLD FLD FLD FLD FLD FLD
System Id Name Field Picture - Storage Field Picture - Display Screen Literal - Long Field Format Field Length Field Fraction
Y Y Y Y Y Y Y Y
(Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy)
D-16
Table D-2
Object Attributes and Descriptions (Continued) System Name FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD FLD Attribute Name Range - Minimum Value Range - Maximum Value Reference Table Name Screen Literal - Short Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy)
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM FORM
System Id Name Form Environment Base Country Language Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date
Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N
(Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy)
D-17
Table D-2
Object Attributes and Descriptions (Continued) System Name FORM FORM FORM FORM Attribute Name Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N
Object Type ENTITY ENTITY ENTITY ENTITY
FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME FSCHEME
System Id Name Description Mutually Exclusive Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC
System Id Name Business System Id Menu Description Sub-Process Menu Type Application Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type
Y Y Y Y Y Y Y Y Y Y Y Y Y N
(Object) (Object) (Object) (Object) (Object) (Object)
D-18
Table D-2
Object Attributes and Descriptions (Continued) System Name FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC FUNC Attribute Name Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE FVALUE
System Id Name Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP
System Id Name Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project
Y Y Y Y Y Y Y Y Y Y
D-19
Table D-2
Object Attributes and Descriptions (Continued) System Name GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP Attribute Name Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP
System Id Name Format Description Country Language Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT
System Id Name Country Language Date Created Time Created Created by Date Maintained
Y Y Y Y Y Y Y
(Hierarchy) (Hierarchy) (Hierarchy)
D-20
Table D-2
Object Attributes and Descriptions (Continued) System Name HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT HLPTXT Attribute Name Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y N N N Y N N N N N N
IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT IDENT
System Id Name Type Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
KEY KEY KEY KEY KEY KEY
System Id Name Implementation Name Type Unique Flag Delete Method
Y Y Y Y Y Y
D-21
Table D-2
Object Attributes and Descriptions (Continued) System Name KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY KEY Attribute Name Update Method Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG LANG
System Id Name Language Abbreviation Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY
LOC
System Id
D-22
Table D-2
Object Attributes and Descriptions (Continued) System Name LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC LOC Attribute Name Name Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO LOGPRO
System Id Name Description Type Mode Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User
Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N
D-23
Table D-2
Object Attributes and Descriptions (Continued) System Name LOGPRO Attribute Name Version Significant? N
Object Type ENTITY
MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE MACHINE
System Id Name Implementation Name Operating System OS Release Machine Group Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP MCGRP
System Id Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date
N N N N N N N N N N N N N N N
D-24
Table D-2
Object Attributes and Descriptions (Continued) System Name MCGRP MCGRP MCGRP MCGRP Attribute Name Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N
Object Type ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN MIGRTN
System Id Name Description Data Set Prefix Migration State Return Code Processing Version Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
N N N N N N N Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG ORG
System Id Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id
Y Y Y Y Y Y Y Y Y N N
D-25
Table D-2
Object Attributes and Descriptions (Continued) System Name ORG ORG ORG ORG ORG ORG ORG ORG Attribute Name Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL PANEL
System Id Name Coordinate System X-Resolution Y-Resolution Description Country Language Base GUI Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
(Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy)
ENTITY ENTITY ENTITY ENTITY ENTITY
PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT
System Id Name Event Description Event Type Event Class
Y Y Y Y Y
(Hierarchy) (Hierarchy)
D-26
Table D-2
Object Attributes and Descriptions (Continued) System Name PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT PHYEVT Attribute Name Event Scope Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y N N N Y N N N N N N (Hierarchy)
PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES PROCES
System Id Name Description Menu Description Work Station Group Id Sub-Process Menu Type Execution Environment Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project
Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N
(Object) (Object) (Object) (Object) (Object) (Object) (Object)
D-27
Table D-2
Object Attributes and Descriptions (Continued) System Name PROCES PROCES Attribute Name Local Maintenance User Version Significant? N N
PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT PROJCT
System Id Project Name Project Id Type Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG
System Id Name Description Rebuild Package State Return Code Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change #
Y Y Y Y Y Y Y Y Y Y Y Y N N N
D-28
Table D-2
Object Attributes and Descriptions (Continued) System Name RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG RBDPKG Attribute Name Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL REL
Relationship Type Name Relationship Code Y Description X Description Implementation Name Migration File Name Exit Routine Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
REPORT REPORT REPORT REPORT REPORT REPORT REPORT
Report Id Name Execution Environment Page Size Line Size Left Margin Top Margin
Y Y Y Y Y Y Y
(Hierarchy) (Hierarchy) (Hierarchy) (Object) (Object) (Object) (Object)
D-29
Table D-2
Object Attributes and Descriptions (Continued) System Name REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT REPORT Attribute Name Printer Type Orientation Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N (Object) (Object) (Hierarchy)
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT REPOSIT
System Id Name Description Type Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project
Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N
D-30
Table D-2
Object Attributes and Descriptions (Continued) System Name REPOSIT REPOSIT Attribute Name Local Maintenance User Version Significant? N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN RLN
System Id Name Complex Expected Minimum Rows Expected Maximum Rows Activity Period Average Inserts for Period Average Deletes for Period Average Updates for Period Expected Rows Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE
System Id Name Execution Environment DB2 Plan Name DBMS Usage Description Execution Mode CICS / IMS Transaction Id Implementation Name Package
Y Y Y Y Y Y Y N Y Y
(Object) (Object) (Hierarchy) (Object)
D-31
Table D-2
Object Attributes and Descriptions (Continued) System Name RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE RULE Attribute Name Isolation Mode Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y N N N Y N N N N N N (Object)
SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK SDSAPK
System Id Name Release Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
N N N N N N N N N N N N N N N N N N N N
ENTITY
SDSPAK
System Id
D-32
Table D-2
Object Attributes and Descriptions (Continued) System Name SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK SDSPAK Attribute Name Name Total Orders Licensed Orders Remaining Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N N N N N N N N N N N N N N N N
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD SDSPCD
System Id Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
N N N N N N N N N N N N N N N N N N N
D-33
Table D-2
Object Attributes and Descriptions (Continued) System Name SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC SDSPSC Attribute Name System Id Name Extract to File Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N N N N N N N N N N N N N N N N
SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV SECENV
D-34
Table D-2
Object Attributes and Descriptions (Continued) System Name Attribute Name Significant?
Object Type
SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN SECTN
System Id Name Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
(Hierarchy) (Hierarchy) (Hierarchy)
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER
System Id Name Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User
Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N
D-35
Table D-2
Object Attributes and Descriptions (Continued) System Name SERVER Attribute Name Version Significant? N
Object Type ENTITY
SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET
System Id Name Field Picture - Storage Set Format Set Length Set Fraction Implementation Name Style Representation Length Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
(Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy) (Hierarchy)
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB
System Id Name Description Implementation Name Implementation Storage Migration File Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by
D-36
Table D-2
Object Attributes and Descriptions (Continued) System Name SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB SOURCEB Attribute Name Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE STATE
System Id Name Description Type Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
STORE STORE STORE STORE STORE STORE STORE
System Id Name Description Date Created Time Created Created by Date Maintained
Y Y Y Y Y Y Y
D-37
Table D-2
Object Attributes and Descriptions (Continued) System Name STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE STORE Attribute Name Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y N N N Y N N N N N N
SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL SYMBOL
System Id Name Define Encoding Display Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY
TABLE TABLE TABLE TABLE
System Id Name Table Or View Table Creator
Y Y Y Y
D-38
Table D-2
Object Attributes and Descriptions (Continued) System Name TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE TABLE Attribute Name Implementation Name Expected Minimum Rows Expected Maximum Rows Activity Period Average Inserts For Period Average Deletes For Period Average Updates For Period Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS TRANS
System Id Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time
Y Y Y Y Y Y Y Y Y N N N Y N N N
D-39
Table D-2
Object Attributes and Descriptions (Continued) System Name TRANS TRANS TRANS Attribute Name Local Maintenance Project Local Maintenance User Version Significant? N N N
Object Type ENTITY ENTITY ENTITY
TXT TXT TXT TXT TXT TXT
System Id Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y N N N N N
(Object)
USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER USER
System Id Name User Name User Id JOB Accounting Information User Location JOB Name JOB Options Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
ENTITY ENTITY ENTITY ENTITY
VALUES VALUES VALUES VALUES
System Id Name Value Date Created
Y Y Y Y
(Object) (Object) (Object)
D-40
Table D-2
Object Attributes and Descriptions (Continued) System Name VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES VALUES Attribute Name Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y N N N Y N N N N N N
Object Type ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY ENTITY
VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW VIEW
System Id Name Description Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
(Hierarchy)
ENTITY ENTITY
WINCON WINCON
System Id Name
Y Y
D-41
Table D-2
Object Attributes and Descriptions (Continued) System Name WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON WINCON Attribute Name GUI Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y N N N Y N N N N N N (Hierarchy)
WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW WINDOW
System Id Name Description Implementation Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Project Lock Type Lock Id Change # Owner Id QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
(Hierarchy)
D-42
Table D-2
Object Attributes and Descriptions (Continued) System Name ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU ACHACU Attribute Name Parent Type Application Config. Long Name Sequence Number Child Type Configuration Unit Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP ADPPAP
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
RELATE
ATTATT
Parent Type
D-43
Table D-2
Object Attributes and Descriptions (Continued) System Name ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT ATTATT Attribute Name Business Attribute Name Sequence Number Child Type Business Attribute Name Separator Id Occurs Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT ATTDAT
Parent Type Business Attribute Name Sequence Number Child Type Data Type Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE
BMHABI
Parent Type
D-44
Table D-2
Object Attributes and Descriptions (Continued) System Name BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI BMHABI Attribute Name Parent Long Name Sequence Number Child Type Child Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO BOBRBO
Parent Type Business Object Long Name Sequence Number Child Type Business Object Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE
BOOWXX BOOWXX
Parent Type Business Object Name
Y Y
D-45
Table D-2
Object Attributes and Descriptions (Continued) System Name BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX BOOWXX Attribute Name Sequence Number Child Type Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX CECOXX
Parent Type Cell Long Name Sequence Number Child Type Child Long Name Separator Id Machine Implementation Name Cell Manager Communication Gateway Application Server Network Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N
D-46
Table D-2
Object Attributes and Descriptions (Continued) System Name CECOXX Attribute Name Version Significant? N
Object Type RELATE
COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM COMCOM
Parent Type Component Long Name Sequence Number Child Type Sub-Component Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL CSGCPL
D-47
Table D-2
Object Type
CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG CSGCSG
CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST CSGCST
D-48
Table D-2
Object Attributes and Descriptions (Continued) System Name CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX CSGCXX Attribute Name Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV CSTENV
Parent Type Parent Id QA Status Sequence Number Child Type Child Id Separator Id Login ID Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y N Y Y Y Y Y Y Y Y Y Y Y N N N N N N
D-49
Table D-2
Object Attributes and Descriptions (Continued) System Name CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX CUECXX Attribute Name Parent Type Configuration Unit Long Name Sequence Number Child Type Child Long Name Separator Id Preparation Time Implementation Name Service Name Significant Time Link Type Owner Id Qualifier Plan Name Collection Id Version Id Isolation Mode Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT
Parent Type Data Type Name Sequence Number Child Type Data Type Name Separator Id Occurs Date Created Time Created Created by
Y Y Y Y Y Y Y Y Y Y
D-50
Table D-2
Object Attributes and Descriptions (Continued) System Name DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT DATDAT Attribute Name Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET DATSET
Parent Type Data Type Name Sequence Number Child Type Set Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB
Parent Type Database Long Name Sequence Number Child Type Table Long Name Separator Id Expected Minimum Rows Expected Maximum Rows Activity Period Average Inserts
Y Y Y Y Y Y Y Y Y Y
D-51
Table D-2
Object Attributes and Descriptions (Continued) System Name DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB DBHATB Attribute Name Average Deletes Average Updates Done To Do Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y N N N N N N N
ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT ENTATT
Parent Type Business Entity Name Sequence Number Child Type Business Attribute Name Separator Id Optional Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
RELATE RELATE
ENTIDE ENTIDE
Parent Type Business Entity Name
Y Y
D-52
Table D-2
Object Attributes and Descriptions (Continued) System Name ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE ENTIDE Attribute Name Sequence Number Child Type Identifier Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y N N N N N N N
ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1 ENTLO1
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Create Flag Read Flag Update Flag Delete Flag Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N
D-53
Table D-2
Object Attributes and Descriptions (Continued) System Name ENTLO1 Attribute Name Version Significant? N
Object Type RELATE
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2 ENTLO2
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Master Indicator Variant Indicator Partitioned Indicator Replicated Indicator Subset Data Reorganized Data Teleprocessing (Remode Data) Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN
Parent Type Business Entity Name Sequence Number Child Type Business Relation Name Separator Id Chief Executive Cardinality Optionality Dependant Abstract
D-54
Table D-2
Object Attributes and Descriptions (Continued) System Name ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN ENTRLN Attribute Name Role Minimun Cardinality Maximum Cardinality Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX EVCAXX
Parent Type Event Name Sequence Number Child Type Name Separator Id Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE
EVHARU EVHARU EVHARU
Parent Type Rule Long Name Sequence Number
Y Y Y
D-55
Table D-2
Object Attributes and Descriptions (Continued) System Name EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU EVHARU Attribute Name Child Type Event Long Name Separator Id Action Type Action Host View Mapping Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO EVILBO
Parent Type Event Name Sequence Number Child Type Business Object Name Separator Id Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
D-56
Table D-2
Object Attributes and Descriptions (Continued) System Name FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM FILECM Attribute Name Type Long Name Sequence Number Child Type Child Id Separator Id Component Usage Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N (Object)
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD FORWRD
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Store and Forward Update Rule Store and Forward Delete Rule Store and Forward Insert Rule Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N (Object) (Object) (Object)
D-57
Table D-2
Object Attributes and Descriptions (Continued) System Name FORWRD FORWRD Attribute Name Local Maintenance User Version Significant? N N
Object Type RELATE RELATE
FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV FSHAFV
Parent Type FSDM Scheme Long Name Sequence Number Child Type FSDM Value Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR FUNCPR
Parent Type Business Function Long Name Sequence Number Child Type Business Process Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User
Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N
D-58
Table D-2
Object Attributes and Descriptions (Continued) System Name FUNCPR Attribute Name Version Significant? N
Object Type RELATE
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT FUNENT
Parent Type Business Function Long Name Sequence Number Child Type Entity Long Name Separator Id Create Flag Read Flag Update Flag Delete Flag Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC
Parent Type Business Function Long Name Sequence Number Child Type Location Long Name Separator Id Major Involvement in Function Minor Involvement in Function Comments Date Created Time Created Created by Date Maintained Time Maintained
Y Y Y Y Y Y Y Y Y Y Y Y Y Y
D-59
Table D-2
Object Attributes and Descriptions (Continued) System Name FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC FUNLOC Attribute Name Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS FVCLFS
Parent Type FSDM Value Long Name Sequence Number Child Type FSDM Scheme Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP
Parent Type Parent Long Name Sequence Number Child Type Child Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by
D-60
Table D-2
Object Attributes and Descriptions (Continued) System Name GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP GRPGRP Attribute Name Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ GRPPRJ
Parent Type Parent Long Name Sequence Number Child Type Child Long Name Separator Id Method Name Scope Scope Mode Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N (Object) (Object) (Object)
GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id User Authority level Field Authority level Date Created Time Created
Y Y Y Y Y Y Y Y Y Y
D-61
Table D-2
Object Attributes and Descriptions (Continued) System Name GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR GRPUSR Attribute Name Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT IDEATT
Parent Type Identifier Name Sequence Number Child Type Business Attribute Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id File Key type Date Created Time Created
Y Y Y Y Y Y Y Y Y (Object)
D-62
Table D-2
Object Attributes and Descriptions (Continued) System Name KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY KEYDBY Attribute Name Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y N N N N N N N
KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO KYHACO
Parent Type Key Long Name Sequence Number Child Type Column Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL
Parent Type Logical Long Name Sequence Number Child Type Physical Long Name Separator Id Date Created Time Created Created by
Y Y Y Y Y Y Y Y Y
D-63
Table D-2
Object Attributes and Descriptions (Continued) System Name LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL LOIBRL Attribute Name Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y N N N N N N N
LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX LPAFXX
Parent Type Logical Process Name Sequence Number Child Type Name Separator Id Create Read Update Delete Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE RELATE
LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU
Parent Type Logical Process Long Name Sequence Number Child Type Rule Long Name
Y Y Y Y Y
D-64
Table D-2
Object Attributes and Descriptions (Continued) System Name LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU LPIBRU Attribute Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC MCCAMC
Parent Type Parent Machine Name Sequence Number Child Type Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE RELATE RELATE
MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id
Y Y Y Y Y Y
D-65
Table D-2
Object Attributes and Descriptions (Continued) System Name MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV MCHENV Attribute Name Security Type Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG MCINMG
RELATE RELATE RELATE RELATE RELATE RELATE
MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX
Parent Type Migration Id Sequence Number Child Type Child Id Separator Id
Y Y Y Y Y Y
D-66
Table D-2
Object Attributes and Descriptions (Continued) System Name MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX MGPRXX Attribute Name Child Name Located In Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX MIGXX
Parent Type Parent Id Sequence Number Child Type Child Id Migration Status Scope type Seed Status Has Reuse Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
RELATE RELATE
ORGENT ORGENT
Parent Type Organization Long Name
Y Y
D-67
Table D-2
Object Attributes and Descriptions (Continued) System Name ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT ORGENT Attribute Name Sequence Number Child Type Entity Long Name Separator Id Create Flag Read Flag Update Flag Delete Flag Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN
Parent Type Organization Long Name Sequence Number Child Type Business Function Long Name Separator Id Responsible for Function Major Involvement in Function Minor Involvement in Function Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N
D-68
Table D-2
Object Attributes and Descriptions (Continued) System Name ORGFUN ORGFUN ORGFUN ORGFUN ORGFUN Attribute Name Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE
ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO ORGPRO
Parent Type Organization Long Name Sequence Number Child Type Business Process Long Name Separator Id Responsible for Function Major Involvement in Function Minor Involvement in Function Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET
Type Long Name Sequence Number Child Type Set Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained
D-69
Table D-2
Object Attributes and Descriptions (Continued) System Name OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET OWNSET Attribute Name Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N N N N N
PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS PAHAPS
PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Description Inclusive Flag Exclusive/Or Sequence number Date Created Time Created Created by
Y Y Y Y Y Y Y Y Y Y Y Y (Object) (Object) (Object)
D-70
Table D-2
Object Attributes and Descriptions (Continued) System Name PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP PRODEP Attribute Name Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y N N N N N N N
PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT PROENT
Parent Type Business Process Long Name Sequence Number Child Type Entity Long Name Separator Id Create Flag Read Flag Update Flag Delete Flag Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
PROLOC PROLOC PROLOC PROLOC PROLOC
Parent Type Business Process Long Name Sequence Number Child Type Location Long Name
Y Y Y Y Y
D-71
Table D-2
Object Attributes and Descriptions (Continued) System Name PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC PROLOC Attribute Name Separator Id Major Involvement in Function Minor Involvement in Function Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y N N N N N N N
PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO PROPRO
Parent Type Business Process Long Name Sequence Number Child Type Sub-Business Process Long Name Separator Id Conditional Flag Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N (Object)
RELATE RELATE
PRORUL PRORUL
Parent Type Business Process Long Name
Y Y
D-72
Table D-2
Object Attributes and Descriptions (Continued) System Name PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL PRORUL Attribute Name Sequence Number Child Type Rule Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y N N N N N N N
REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP REPREP
Parent Type Parent Long Name Sequence Number Child Type Child Long Name Separator Id Source Version Target Version Direction Logical Key Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
D-73
Table D-2
Object Type
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC REPSEC
Parent Type Report Long Name Sequence Number Child Type Section Long Name Separator Id Type Break Sequence Number Page Placement Break Field Break Qualifier Left Margin Print Option Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N (Object) (Object) (Object) (Object) (Object) (Object) (Object)
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN
Parent Type Business Relation Name Sequence Number Child Type Business Relation Name Separator Id Chief Executive Cardinality Optionality Dependant Abstract Role Date Created
Y Y Y Y Y Y Y Y Y Y Y Y Y
D-74
Table D-2
Object Attributes and Descriptions (Continued) System Name RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN RLNRLN Attribute Name Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM RPHAFM
Parent Type Parent Long Name Sequence Number Child Type Child Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX
Parent Type Parent Id Sequence Number Child Type Child Id Migration Status Install Action Install Status
Y Y Y Y Y Y Y Y
D-75
Table D-2
Object Attributes and Descriptions (Continued) System Name RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX RPINXX Attribute Name Install for Platform Operating System Data Base Type Configuration Unit Row Selected Install Start Time Stamp install Stop Time Stamp Return Code Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX
Parent Type Parent Id Sequence Number Child Type Child Id Migration Status Application Configuration Scope type Seed status Has Reuse Is a Root Entity Is a Refined Entity Has Hierarchy Changed Affected Entity (Not Analyzed) Date Created Time Created Created by Date Maintained Time Maintained
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
D-76
Table D-2
Object Attributes and Descriptions (Continued) System Name RPXX RPXX RPXX RPXX RPXX RPXX RPXX RPXX Attribute Name Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N N N N N
RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM RULCOM
Parent Type Rule Long Name Sequence Number Child Type Component Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Description Inclusive Flag Exclusive/Or Sequence number Date Created Time Created Created by
Y Y Y Y Y Y Y Y Y Y Y Y (Object) (Object) (Object)
D-77
Table D-2
Object Attributes and Descriptions (Continued) System Name RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP RULDEP Attribute Name Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y N N N N N N N
RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP RULREP
Parent Type Rule Long Name Sequence Number Child Type Report Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL
Parent Type Rule Long Name Sequence Number Child Type Sub-Rule Long Name Separator Id Date Created Time Created Created by Date Maintained
Y Y Y Y Y Y Y Y Y Y
D-78
Table D-2
Object Attributes and Descriptions (Continued) System Name RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL RULRUL Attribute Name Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND RULWND
Parent Type Rule Long Name Sequence Number Child Type Window Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV
Parent Type Rule Long Name Sequence Number Child Type Event Long Name Separator Id Rule Trigger Type Trigger Condition View Mapping Date Created Time Created
D-79
Table D-2
Object Attributes and Descriptions (Continued) System Name RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV RUTREV Attribute Name Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y N N N N N N N
SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP SAHASP
SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Separator Id Separator Id Separator Id
Y Y Y Y Y Y Y Y Y
D-80
Table D-2
Object Attributes and Descriptions (Continued) System Name SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD SDSORD Attribute Name Separator Id Separator Id Separator Id Separator Id Separator Id Separator Id Separator Id Separator Id Separator Id Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM SDSPCM
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Command to Invoke Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time
Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N
D-81
Table D-2
Object Attributes and Descriptions (Continued) System Name SDSPCM SDSPCM SDSPCM Attribute Name Local Maintenance Project Local Maintenance User Version Significant? N N N
Object Type RELATE RELATE RELATE
SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL SETVAL
Parent Type Set Long Name Sequence Number Child Type Value Long Name Separator Id Symbol Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N (Hierarchy)
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP SPRQSP
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time
Y Y Y Y Y Y Y Y Y Y Y Y N N N N
D-82
Table D-2
Object Attributes and Descriptions (Continued) System Name SPRQSP SPRQSP SPRQSP Attribute Name Local Maintenance Project Local Maintenance User Version Significant? N N N
Object Type RELATE RELATE RELATE
SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL SRVRUL
Parent Type Server Long Name Sequence Number Child Type Rule Long Name Separator Id Entry Type Object Name Service Name Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT STOENT
Parent Type Data Store Long Name Sequence Number Child Type Entity Long Name Separator Id Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change #
Y Y Y Y Y Y Y Y Y Y Y Y Y N
D-83
Table D-2
Object Attributes and Descriptions (Continued) System Name STOENT STOENT STOENT STOENT STOENT STOENT Attribute Name QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE
SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV SVDESV
Parent Type Table Long Name Sequence Number Child Type Table Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN
Parent Type Current System Long Name Sequence Number Child Type Business Function Long Name Separator Id Currently Supported Planned Support Comments Date Created Time Created Created by Date Maintained Time Maintained
Y Y Y Y Y Y Y Y Y Y Y Y Y Y
D-84
Table D-2
Object Attributes and Descriptions (Continued) System Name SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN SYSFUN Attribute Name Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y N N N N N N N
SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO SYSPRO
Parent Type Current System Long Name Sequence Number Child Type Business Process Long Name Separator Id Currently Supported Planned Support Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO
Parent Type Current System Long Name Sequence Number Child Type Data Store Long Name Separator Id Create Flag Read Flag Update Flag
Y Y Y Y Y Y Y Y Y
D-85
Table D-2
Object Attributes and Descriptions (Continued) System Name SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO SYSSTO Attribute Name Delete Flag Comments Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB TBBOTB
Parent Type Table Long Name Sequence Number Child Type Table Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
TBHACO TBHACO TBHACO TBHACO TBHACO
Parent Type Table Long Name Sequence Number Child Type Column Long Name
Y Y Y Y Y
D-86
Table D-2
Object Attributes and Descriptions (Continued) System Name TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO TBHACO Attribute Name Separator Id Null Distinct Distinct Type Update Percentage Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY TBHAKY
Parent Type Table Long Name Sequence Number Child Type Key Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE RELATE
TBRBKY TBRBKY
Parent Type Table Long Name
Y Y
D-87
Table D-2
Object Attributes and Descriptions (Continued) System Name TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY TBRBKY Attribute Name Sequence Number Child Type Key Long Name Separator Id Referential Integrity Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR TRIGGR
Parent Type Parent Id Sequence Number Child Type Child Id Separator Id Description Inclusive Flag Exclusive/Or Sequence number Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
D-88
Table D-2
Object Type
USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW USESVW
Type Long Name Sequence Number Child Type Child Id Separator Id Usage Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS VUOWNS
Parent Type View Long Name Sequence Number Type Long Name Separator Id Occurs Number of Times Null Indicator for DB2 Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project
Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N (Object) (Object) (Hierarchy)
D-89
Table D-2
Object Attributes and Descriptions (Continued) System Name VUOWNS VUOWNS Attribute Name Local Maintenance User Version Significant? N N
Object Type RELATE RELATE
WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP WNCHLP
Parent Type Instance Sequence Number Child Type Instance Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL WNCPNL
Parent Type Instance Sequence Number Child Type Instance Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User
Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N
D-90
Table D-2
Object Attributes and Descriptions (Continued) System Name WNCPNL Attribute Name Version Significant? N
Object Type RELATE
WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC WNDWNC
Parent Type Instance Sequence Number Child Type Instance Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV XXCMEV
Parent Type Name Sequence Number Child Type Event Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
D-91
Table D-2
Object Type
XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP XXCMLP
Parent Type Name Sequence Number Child Type Logical Process Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY XXCTSY
D-92
Table D-2
Object Attributes and Descriptions (Continued) System Name XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX XXCTXX Attribute Name Parent Type Parent Long Name Sequence Number Child Type Child Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP XXDPLP
Parent Type Name Sequence Number Child Type Logical Process Name Separator Id Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
D-93
Table D-2
Object Attributes and Descriptions (Continued) System Name XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM XXHABM Attribute Name Parent Type Parent Long Name Sequence Number Child Type Child Long Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT XXHAHT
RELATE
XXHSST
Parent Type
D-94
Table D-2
Object Attributes and Descriptions (Continued) System Name XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST XXHSST Attribute Name Name Sequence Number Child Type State Name Separator Id Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV XXITEV
Parent Type Name Sequence Number Child Type Event Name Separator Id Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
RELATE
XXPCST
Parent Type
D-95
Table D-2
Object Attributes and Descriptions (Continued) System Name XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST XXPCST Attribute Name Name Sequence Number Child Type State Name Separator Id Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP XXPRGP
Parent Type Rule Long Name Sequence Number Child Type Sub-Rule Long Name Separator Id Profile Type Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
D-96
Table D-2
Object Attributes and Descriptions (Continued) System Name XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST XXRIST Attribute Name Parent Type Event Context Long Name Sequence Number Child Type State Long Name Separator Id Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version Significant? Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N
Object Type RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP XXTRLP
Parent Type Name Sequence Number Child Type Logical Process Name Separator Id Description Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
D-97
Table D-2
Object Type
RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE RELATE
XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA XXUSLA
Parent Type Parent Long Name Sequence Number Child Entity Type Child Long Name Separator Id Short Value Long Value Date Created Time Created Created by Date Maintained Time Maintained Maintained by Change # QA Status Local Maintenance Date Local Maintenance Time Local Maintenance Project Local Maintenance User Version
Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N (Object) (Object)
D-98
Index
INDEX
A
actions add entity 5-3 add keywords to entity 5-2, 5-6 add relation 5-1 add text to entity 5-3, 5-10 add text to relation 5-3, 5-11 analyze migration impact 5-1, 5-11 approve analyze results 5-1, 5-16 automate migration 5-17 AUTOSAVE 5-1 browse entity 5-1 browse entity text 5-1 browse keywords 5-1 browse relation 5-1 change entity ownership 5-2 change projects 5-3 clean-up migration information 5-2, 5-18 compare objects 5-2 copy migration files 5-2, 5-20 count migration contents 5-2, 5-15, 5-21 define user entity method 5-3 define user relation method 5-3 delete entity 5-2 delete relation 5-2 deleting migration information
options 5-19 detect objects to be rebuilt 5-3, 5-22 display entities 5-2 display INI files 5-2 export migration package 5-2 exporting to DASD 5-22, 5-23 generate delta report 5-29 generate report 5-3, 5-30 import migration package 3-8, 5-2, 5-31 import migration package options 5-31 import run-time applications 6-1 list entity type 5-2 list migration contents 5-2, 5-33 list relations 5-2, 5-36 lock entity 5-2 maintain entity 5-2, 5-39 migrate run-time applications 6-1 report on migration 5-15 search keywords 5-3, 5-7 toggle import status 5-3, 5-40 unlock entity 5-3 update user profile 5-3 view migration results 5-3, 5-41 add text to entity action 5-3 add text to relation action 5-3 ADDE (add entity) action 5-3 adding a relationship migration to root entity overview 1-3 adding an entity migration source environment processing 1-3 target environment processing 1-5 ADDR (add relation) action 2-8, 5-1 result 2-20 AMIAUTH variable 7-2 ANALYZE (migration impact) action 5-1, 5-11 ANALYZE (migration impact) options 5-12 APPROVE (analyze results) action 5-1, 5-16
attributes data set prefix 5-4 migration name 5-9 system-generated 5-10 system-generated audit 5-5, 5-6 system-generated migration state 5-5 user-defined 5-4 audit attribute 5-5 audit attributes 1-3, 1-6 automate migration action 5-17 processing prerequisites 4-2 AUTOSAVE action 5-1
DR (delete relation) action 5-2 DR action 5-22
E
enterprise repository 2-2 ENTITY (display entities) action 5-2 entity ownership action 5-2 EW (extended where-used report) action 5-2 exit processing CLIST exit C-6 System exit C-1 user exit C-3 sample code C-5 EXPORT (migration package) action 2-17, 4-4, 5-2, 5-22 selective export 5-23 export options 6-2 exporting runtime package messages 6-3 extended where-used action 5-2
B
BE (browse entity) action 5-1 BK (browse keywords) action 5-1 BR (browse relation) action 5-1 BTXE (browse text) action 5-1
C
change projects action 5-3 CICSTRX variable 7-2 CLEANUP action 5-2 clean-up migration info action 5-2, 5-18 CO (change entity owner) action 5-2 COMMIT variable 7-3 COPYAPP action 6-1 COPYMIG (copy migration files) action 5-2, 5-20 COUNT (migration contents) action 5-2, 5-15, 5-21
F
filters for migration contents 5-33
G
generate delta report 5-2, 5-29 report 5-3, 5-30
H D
data set prefix attribute 5-4 DE (delete entity) action 5-2 DEBUG (update debug profile) action 5-2 define user entity method action 5-3 define user relation method 5-3 delete relation action 5-2 delete entity action 5-2 delivery steps QA environment 1-5 DELMIG variable 7-2 DELTA (compare objects) action 5-2 description attribute 5-4 detect objects to be rebuilt action 5-3, 5-22 development environment delivery steps 1-2 DFTIMP variable 7-5 DFTKEY variable 7-5 DFTTEXT variable 7-6 Has-Root-Entity Name attribute 5-9 host names 5-41
I
IMPORT (migration package) action 5-2, 5-31 IMPORT migration package options 5-31 importing configuring runtime applications 6-11 migration package 3-8 importing runtime applications 6-1 INIDISP (display INI files) action 5-2 input file structure definitions 5-41 ISPF Primary Options menu 2-2
K
K (add keywords to entity) action 5-2, 5-6
Index
ii
L
LE (list entity type) action 5-2 list migration contents 5-33 migration contents filtering 5-33 list relation action 5-10 list relations 5-2, 5-36 list summary counts of migration 5-15 LISTMIG (list migration contents) action 5-2, 5-33 LOCK (entity) action 5-2 LR (list relations) action 5-2
M
maintain entity action 5-2, 5-39 MGFILEID variable 7-4 MIGENV CLIST implement APPROVE action 7-7 modify CICS/IMS/DB2 plan name 7-7 SEEREXIT variable C-1 override default action values 7-5, 7-8 process CLIST exit C-6 process user exit C-3 rollback import 7-3 secure common actions DELMIG variable 7-2 secure migration actions 7-2 select CICS transaction ID 7-2, C-3 select IMS transaction ID C-3 specify data set name 7-4 specify default attribute value 7-5, 7-6 MIGRATE (automate migration) action 4-4, 5-2 migrating runtime applications 6-1 migrating run-time applications 1-8 migration 4-4 analyze impact processing 3-5 analyze options 5-12 analyzing the impact of 1-6 checking state values 2-19, 3-6 clean-up actions 5-18 creating target for package 3-4 creating the package 1-3 deleting information 5-19 exporting migration package 2-17 importing package 3-8 prerequisites 2-2 processing 2-1 scope 2-12 selecting objects 2-8 selective export 5-23 status values 5-13 viewing the imported package 3-10
migration attributes 1-3, 1-6 migration entity attributes 5-4 audit 5-6 data set prefix 5-4 description 5-4 migration state 5-5 relation attributes 5-9 scope relation attributes 5-9 system ID 5-5 system-generated attributes 5-5, 5-10 user-defined relation attributes 5-8 user-defined values 5-8 migration entity attributes user-defined 5-4 migration entity method 6-1 migration package creating 2-4 exporting 1-4 importing 1-7 migration scope 5-9 MIGREL variable 7-4 MNBCRUD variable 7-4 MNECRD variable 7-4 MNEISPF variable 7-4 MNRCRUD variable 7-4 MNRISPF variable 7-4 MXBCRUD variable 7-4 MXECRUD variable 7-4 MXEISPF variable 7-5 MXRCRUD variable 7-5 MXRISPF variable 7-5
N
naming standards 1-3, 1-6
O
options export 6-2 OVRIMP variable 7-8 OVRKEYKW variable 7-5 OVRSRC variable 7-5 OVRTEXT variable 7-5
P
PROJECTS (change) action 5-3
R
RD (detect objects to be rebuilt) action 5-3 REFRESH (screen) action 5-3
Index
iii
relation attributes migration name 5-9 relationships definition 1-4 REP (migration report) action 5-3, 5-15 RES (view results) action 5-3, 5-20, 5-23, 5-32, 5-41 root entity 2-12 creating relations from 2-14
S
scope controlling migration 5-9 limiting in migration 5-31 search for keywords actions 5-3 security model migrating 2-11 SEEREXIT variable 7-7 selective export 5-23 SIGNAMI variable 7-7 SIGNIMP variable 7-7 SIGNRBD variable 7-7 source environment processing 2-1 SRCH (search keywords) action 5-3 STATEXIT variable C-6 status values 5-13 system-generated attributes migration state 5-5 system-generated audit attributes 5-5
T
TOGGLE (import status) action 5-3, 5-40 TXE (add text to entity) 5-10 TXE (add text to entity) action 5-3 TXR (add text to relation) 5-11 TXR (add text to relation) action 5-3
U
UMETH (define user entity method) action 5-3 UNLOCK (entity) action 5-3 UPROF (update user profile) action 5-3 URMETH (define user relation method) action 5-3 user-defined description 5-4 user-defined values 5-4
V
view migration results action 5-41
Index
iv

App Builder Enterprise Migration

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

App Builder Enterprise Migration

Hochgeladen von

Copyright:

Verfügbare Formate

BluePhoenix AppBuilder 2.0.3.

Enterprise Migration Guide

AppBuilder 2.0.3.1 Enterprise Migration Guide

Migrating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Source Environment Processing

Target Environment Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Automated Migration Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

AppBuilder 2.0.3.1 Enterprise Migration Guide

Migrating and Importing Run-time Applications . . . . . . . . . . . . . . . . . . . 6-1

Setting Up the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Migration Status Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1

Migration Tables and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Migration Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1

Migration Processing Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D-1 D-1 D-2 D-2 D-2

AppBuilder 2.0.3.1 Enterprise Migration Guide

AppBuilder 2.0.3.1 Enterprise Administration Guide

AppBuilder 2.0.3.1 Enterprise Administration Guide

Source Environment Steps

The migration process is described in the steps listed in Table 1-1.

Target Environment Steps

Source Environment Steps

Source Environment Steps

Creating the Migration Package

Deliverable The migration entity is added to the source enterprise repository.

Selecting Objects for Migration

AppBuilder 2.0.3.1 Enterprise Administration Guide

Source Environment Steps

Exporting the Migration Package

Target Environment Steps

Target Environment Steps

Creating the Target for the Migration Package

AppBuilder 2.0.3.1 Enterprise Administration Guide

Target Environment Steps

Deliverable The migration entity is added to the target enterprise repository.

Analyzing the Impact of the Migration

Target Environment Steps

Importing the Migration Package

AppBuilder 2.0.3.1 Enterprise Administration Guide

Migrating Run-time Applications

Migrating Run-time Applications

SOURCE ENVIRONMENT PROCESSING

AppBuilder 2.0.3.1 Enterprise Migration Guide

AppBuilder 2.0.3.1 Enterprise Migration Guide

Preparing for Migration

Preparing for Migration

Accessing the Enterprise Repository

Source Environment Processing

Preparing for Migration

ISPF/PDF Primary Option menu

The number of options available depends on which options are installed.

AppBuilder 2.0.3.1 Enterprise Migration Guide

Creating the Migration Package

Creating the Migration Package

Source Environment Processing

Creating the Migration Package

Creating the migration package

AppBuilder 2.0.3.1 Enterprise Migration Guide

Creating the Migration Package

Naming the migration entity

Source Environment Processing

Creating the Migration Package

Maintaining the migration entity