app builder enterprise migration

8/14/2019 App Builder Enterprise Migration

1/260

BluePhoenix AppBuilder 2.0.3.1

Enterprise Migration Guide


2/260

BluePhoenix AppBuilder 2.0.3.1Enterprise Migration Guide

September, 2002

Corporate Headquarters

BluePhoenix Solutions

Vlierwerf 7B4704 SB Roosendaal

The Netherlands+31 (0) 165 399 401

+31 (0) 165 396 308 faxwww.bluephoenixsolutions.nl

USA Headquarters

BluePhoenix Solutions USA, Inc.

8000 Regency ParkwayCary, NC 27511

United States+1 919.380.5100

+1 919.380.5111 faxwww.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 trademarksof, their respective owners.

Portions of this product may be covered by U.S. Patent Numbers 5,495,222 and 5,495,610 and variousother 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 anymeans, electronic or mechanical, except as provided in the licensing agreement.

BluePhoenix Solutions has made every effort to ensure that the information contained in this documentis accurate; however, there are no representations or warranties regarding this information, including

warranties of merchantability or fitness for a particular purpose. BluePhoenix Solutions assumes noresponsibility 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 byBluePhoenix Solutions or its representatives.
http://www.bluephoenixsolutions.com/http://www.bluephoenixsolutions.com/http://www.bluephoenixsolutions.com/http://www.bluephoenixsolutions.com/


3/260

AppBuilder 2.0.3.1 Enterprise Migration Guide 3

TABLE OF

CONTENTS

Table of Contents

AppBuilder 2.0.3.1 Enterprise Migration Guide

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

Source Environment Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Creating the Migration Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Selecting Objects for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Exporting the Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Target Environment Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Creating the Target for the Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Analyzing the Impact of the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Importing the Migration Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Migrating Run-time Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

2 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-8Creating Relations From the Migration Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Migrating a Security Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11Creating Relations from the Root Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Exporting the Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

3 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

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

Before You Migrate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Automated Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Overnight Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Status Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4


4/260

Table of Contents 4

Using the Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Preparing for Automatic Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Sample Automated Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

After You Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

5 Migration Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Migration Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Add Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Add Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Add Relation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Add Text to Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Add Text to Relation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Analyzing the Migration Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Approve Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Automate Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17Migrating Without Migration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

Clean-up Migration Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19

Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

Copy Migration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

Count Migration Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

Delete Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

Delete Relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21


5/260

Table of Contents 5

Detect Objects to be Rebuilt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22

Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22

Export Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22

Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

Selective Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

Generate a Delta Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29

Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30

Generate a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31

Import Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31

Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32

List Migration Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33

Using Filters to List Migration Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

6 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-3Package 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


6/260

Table of Contents 6

Installing the Import Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8Package Installation Status Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15

Link the Import Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17

Update Entity and View Definition (VIDTEXT) File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17Update the Rule Relationship and Rule Source Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18Bind 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-19Step 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-22Restoring the Backed-up Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23

Updating Preparation Timestamps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24

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

Variables in the @MIGENVn INI file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Automate Migration (MIGRATE) Action Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

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

Migration Status Value Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1

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

Migration Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1ENT_LOGKEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

E_MIGRTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2R_MIGXX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

REL_LOGKEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Migration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4Header and Row Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

File Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8

C 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


7/260

Table of Contents 7

D Migration Processing Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Audit Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Create Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2Maintenance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Repository Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Freeway Migrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

Object Attribute Listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i


8/260

8 AppBuilder 2.0.3.1 Enterprise Migration Guide


9/260

AppBuilder 2.0.3.1 Enterprise Administrat ion Guide 1-1

CHAPTER

1

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 sourceis the placefrom whichdata is copied, and

the targetis the place to whichthe data is copied.

Figure 1-1 Basic Migration Processing

Typically, the Migration Facility is used to copy or upgrade an application, for example, from adevelopment 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


10/260

1-2 Migrating Applications

Source Environment Steps

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

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-2illustrates the steps required to create and export a migration package.

Figure 1-2 Source environment processing

Table 1-1 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


11/260



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 createaction 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 migrationentity 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

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. Choose the repository, version, and projectfromwhich you are migrating.

2. Type in ADDE (Add Entity) to open the Add an Entity panel.

3. Specify values for all user-definable attributes.

4. Add text and keywords to further define the migration package.

5. 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.

Note The repository administrator(s) should establish naming standardsfor migration entities that are consistent with the naming standards established for development project

entities.


12/260



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 youwant 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. List the entities or entity hierarchies that you want to export.

2. Use the add relation action to add a relationship between the migration entity and each entity that

you want to migrate.

3. Specify values for the user-definable attributes.

4. 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.


13/260



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 updatingobjects in a target environment.

To export the generated migration package:

1. Run the export action for the selected migration entity.

2. Accept or change the default export options to reflect the purpose of the migration.

3. Check the migration state on the migration Maintain an Entity panel.

4. If the migration state is Export Failed, find out why the job failed, correct the problem, and run the

job again.

5. 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.


14/260



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 targetfor

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 generatesothers.

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 sameas the data set name assigned to the source migration

entity.

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. Choose the repository, version, and project to which you are migrating.

2. Use the add entity action to generate the blank Add an Entity panel.

3. Specify values for all user-definable attributes.

4. Enterthe DSN given to the sourcemigration entity.

5. Add text and keywords to further define the migration package.

6. 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:

Note The repository administrator(s) should establish naming standards for migration entities that are consistentwith the naming standards established for development project entities.


15/260



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. Run the Analyzeaction for a selected migration entity.

2. Accept or change the default analyze options to reflect the purpose of the migration.

3. Check the migration state on the migration Maintain Entity panel or Browse Entity panel.

4. If the state is Analyze Failed, find out why the job failed, correct the problem, and run the job again.

5. 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.


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 statusvalue. 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.


16/260


Migrating Run-time Applications

To import a migration package:

1. Run the Importaction.

2. Accept or change the default import options to reflect the purpose of the migration.

3. Check the migration state on the migration Maintain an Entity panel.

4. 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.

5. 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 ApplicationsOnce 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 run-

time application involves two steps:

1. Use the COPYAPPaction to extract and export all or parts of run-time applications.

The COPYAPPaction 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) ofupdates to the application program


17/260

AppBuilder 2.0.3.1 Enterprise Migration Guide 2-1

CHAPTER

2

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




Figure 2-1 Source Environment Processing

univers


18/260

2-2 Source Environment Processing



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 havechosen. 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 theView 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 targetversion.

Accessing the Enterprise Repository

When you are ready to migrate, access the enterprise repository by following these steps:

1. Following your site procedure, log on to the Time Sharing Option (TSO) system.

2. 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 repositoryand 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.

Note Check with your repository administrator for other requirements before migrating.


19/260



Figure 2-2 ISPF/PDF Primary Option menu

3. To access the enterprise repository, select option 1, ER, from the System Options menu and press

Enter. See Figure 2-3.

Figure 2-3 System Options menu

Note The ISPF/PDF Primary Option menu shown in Figure 2-2is a sample and includes site-specific options(for example, FORTE and PANVALET). The equivalent panel at your site may look different.

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


20/260


21/260



Figure 2-5 Creating the migration package

This section describes how to add a migration entity.

1. 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.)

2. Type ADDEon the Migration action line (Figure 2-6) and press Enter.

Figure 2-6 Creating the migration entity

3. On the blank Add an Entity detail panel, type the name and the description (Figure 2-7).

univers

ADDE


22/260



Figure 2-7 Naming the migration entity

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. Therepository 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 Fileson page 5-17for 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 system-

defined 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 byovertyping values and then typing SAVEon the command line again.

AppBuilder Host Workbench

Repository: SUNRISE V: 1 Project: DEV Level: 1

Action Entity________ Field

________ File________ Form

________ FSDM Scheme________ FSDM Value________ Function

________ Help Text________ Identifier________ Key

________ Location________ Logical Process________ MachineADDE____ Migration________ Organization________ Physical Event________ Process________ Rebuild Package


23/260



Figure 2-8 Maintaining the migration entity

7. Type TXEon the command line to add text to the entity. The text describes the purpose and scopeof the migration package to other Migration Facility users (Figure 2-8shows sample text). You

should do this step, although it is optional. Press F3to return to the Maintain an Entity panel.

Figure 2-9 Adding text to the migration entity

8. Type Kon the command line to add keywords to the entity. Keywords describe the purpose andscope of the migration package to other Migration Facility users. Figure 2-10shows sample

keywords. We recommend that you do this step, although it is optional. Press F3to return to the

Maintain an Entity panel.

Note If the Autosave option is turned on, the information you enter is saved as soon as you press F3to return tothe 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.

Note Separate each keyword with a space and do not exceed 240 characters for all the keywords for a singleentity.

Maintain an Entity More: +


Migration Attributes:

Name . . . . . . . . . . . . DMC_VER2______________________System Id . . . . . . . . . : AA4FNR

Description . . . . . . . . . MIGRATE DMC_APP_1 FROM V1 TO V2Data Set Prefix . . . . . . . SEEROUT.M00016NR_Migration State . . . . . . : 14 N/A

Audit Attributes:Date Created . . . . . . . : 95/05/12

Time Created . . . . . . . : 09:13Created by . . . . . . . . : SS0222Date Maintained . . . . . . : 95/10/02Time Maintained . . . . . . : 09:13Maintained by . . . . . . . : SS0222Project . . . . . . . . . . : DEVChange # . . . . . . . . . : 0001Owner Id . . . . . . . . . : SS0222Local Maintenance Date . . : 95/10/02

User modifications to object have been Saved.Command ===> _______________________________________________________________

--------- SS0222.SS0196.MOD.STK ------------------------------ COLUMNS 001 072TEXT for Migration

Name . . . . . . . : DMC_VER2Version . . . . . : 1

****** ***************************** TOP OF DATA ******************************000001 USED TO MIGRATE DMC_APP1 (PAYROLL) FROM VERSION 1 TO VERSION 2 IN SUNRISE.****** **************************** BOTTOM OF DATA ****************************


24/260


25/260



Figure 2-11 Selecting objects for migration

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.)

univers


26/260



2. On the AppBuilder Host Workbench panel, type LEon the Migration action line and press Entertonavigate to the AppBuilder List Facility for Entity Migration panel.

3. Type ADDRon the action line of your migration entity (Figure 2-12) and press Enter.

Figure 2-12 Creating the relation from the migration entity

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

Figure 2-14provides a list of all the relation types available:

List Facility for Entity Migration


Action Name System Id________ DC_MIG01 AA37NR

ADDR____DMC_VER2 AA4FNR

________ GETCAPPS AAAYNR________ GETVIREQ AAAWNR________ GET524S AAAXNR

________ JXL_ADM_OBJECT_ALL JXLADMO________ LAI_PFDEFAULT AAAMNR

________ MIG_DNAGE AA1WNR________ MIG_DNA0000 AA1NNR________ MIG_FDFAULT AAABNR

________ MIG_FGBL01 AA1MNR________ MIG_FREPORT AAANNR________ MIG_NRV1TO_NRV2 AA3ONR

________ MIG_QCLBWIND AA24NR________ MIG_TCFLVIEW AA1YNR

-------------------------- Action Information -------------------------| More: + || Action . . . . . . . . . . . : Add a Relation || Use . . . . . . . . . . . . . . 1 Name || Entity Type . . . . . . . . . : Migration || Name/System Id . . . . . . . . DMC_VER2______________________ || || Relation Type . . . . . . . . . 32 1. Has-Root Application Config. |

| 2. Has-Root Attribute |

| 3. Has-Root Bitmap || 4. Has-Root Business Object |

| 5. Has-Root Cell || 6. Has-Root Collection || 7. Has-Root Column |

| 8. Has-Root Component || |


27/260


AppBuilder 2.0.3.1 Enterprise Migrat ion Guide 2-11

Figure 2-14 Relation Types

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. In the ADM project, create a migration entity.

2. 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. Run the ADDR action against the group to be migrated. One of the options under ADDR is:

3. Is-a-Root-of Migration

4. Run Export to migrate the security model.

Has-Root Application Config. Has-Root Identifier

Has-Root Attribute Has-Root Key

Has-Root Bitmap Has-Root Location

Has-Root Business Object Has-Root Logical Process

Has-Root Cell Has-Root Machine

Has-Root Collection Has-Root Organization

Has-Root Column Has-Root Physical Event

Has-Root Component Has-Root Process

Has-Root Config. Unit Has-Root Project

Has-Root Current System Is-A-Root-Of Rebuild Package

Has-Root Data Store Has-Root Relationship

Has-Root Data Type Has-Root Report

Has-Root Database Has-Root Rule

Has-Root Drawing Has-Root Section

Has-Root Entity Has-Root Server

Has-Root Event Has-Root Set

Has-Root Field Has-Root State

Has-Root File Has-Root Table

Has-Root Form Has-Root Transition

Has-Root Function Has-Root User

Has-Root FSDM Scheme Has-Root Value

Has-Root FSDM Value Has-Root View

Has-Root Group Has-Root Window

Profiles Group

Note The STATIC_LINK_DEFAULT configuration unit is provided as part of the default repository to maintain arelationship indicating that a rule should be statically linked automatically during the rebuild process.


28/260



5. In the target environments ADM project, import the security model.

6. The system generates a blank Add a Relation panel with the Migration Name field filled in. In the

Has-Root Name field, type the name of the root entity that you want to add to the

migration package (Figure 2-15).

Figure 2-15 Adding a relation to the root entity

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 Scope Types

See Add Relationon page 5-7for 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.

Action Description

Entity Only

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.

Entity HierarchyThe entityas well as all of its child objectsare part of the migration package.

This scope is useful for copying new branches of an application.

Prepare HierarchyThe entityand the child objects needed to prepare itare part of the migration

package. This scope is useful for copying fixes to an existing application.

One Level

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.

DrawingA drawing and objects contained in the drawing are included in the package. It isuseful 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.

Add a Relation More: +


Migration

Name . . . . . . . . . . . . DMC_VER2______________________

Has-Root ProcessName . . . . . . . . . . . . VER2_DMC_APP_1_________________

Relationship Attributes:

Scope type . . . . . . . . . 2 1. Entity Only2. Entity Hierarchy3. Prepare Hierarchy

4. One Level5. Drawing

Audit Attributes:Date Created . . . . . . . :Time Created . . . . . . . :

Created by . . . . . . . . :Date Maintained . . . . . . :

Command ===> _______________________________________________________________

Type the name

of the root entity

to be added

Select a

scope type


29/260



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 savedappears in the command area (Figure 2-17).

Figure 2-17 Saving the relation

After a relation is saved, you can change the user-defined attributes by overtyping values and then

typing SAVEon the command line again.

9. To add text to the relation, typeTXRon the action line and press Enter. Use the text to describe thepurpose of the relation to other project users. You should do this step, although it is optional. See

Figure 2-18.

Figure 2-18 Adding text to the relation

To add another root entity of the sametype to the migration package from the active Maintain a Relation

panel, tab to the Has-Root 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 themessage, User modifications to object have been saved.

To add a root entity of anotherentity type, pressF3to exit the active panel. Then repeat steps 2 through7, until you have included all the objects you want to migrate.

Press F3to 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.

Maintain a Relation More: +


MigrationName . . . . . . . . . . . . DMC_VER2______________________

Has-Root ProcessName . . . . . . . . . . . . VER2_DMC_APP_1_________________

Relationship Attributes:Scope type . . . . . . . . . 2 Entity Hierarchy


Time Created . . . . . . . : 09:26Created by . . . . . . . . : SS0222Date Maintained . . . . . . : 95/10/02

Time Maintained . . . . . . : 09:26Maintained by . . . . . . . : SS0222

Change # . . . . . . . . . : 0001

Local Maintenance Date . . : 95/10/02User modifications to object have been Saved.

Command ===> _______________________________________________________________

--------- SS0222.SS0196.MOD.STK ------------------------------ COLUMNS 001 072

TEXT for Relations

Name . . . . . . . : VER2_DMC_AP_1

Version . . . . . : 1

****** ***************************** TOP OF DATA ******************************000001 DMC_VER2 HAS ROOT PROCESS VER2_DMC_APP_1.000002 SCOPE IS ENTITY HIERARCHY BECAUSE THE APPLICATION IS BEING

000003 MIGRATED TO VERSION 2 FOR THE FIRST TIME.****** **************************** BOTTOM OF DATA ****************************


30/260


31/260



Figure 2-21 Additional relation types

5. The system generates a blank Add a Relation panel with the Has-Root Name field

filled in. Type the name of your migration entity in the Migration Name field (Figure 2-22).

Figure 2-22 Naming the migration entity

The name you type in the Migration Name field must match the name of your existing

migration entity.

6. Tab to the Scopefield, and select the migration scope.

See Add Relationon page 5-7for 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 savedappears in the command area (Saving the relationon page 2-16).

-------------------------- 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 |

| |

Add a Relation More: +


MigrationName . . . . . . . . . . . . DMC_VER2______________________

Has-Root ProcessName . . . . . . . . . . . . DMC_FUNC2_____________________

Relationship Attributes:

Scope type . . . . . . . . . 2 1. Entity Only2. Entity Hierarchy

3. Prepare Hierarchy4. One Level5. Drawing

Type the name of the

existing migration

entity

Select the

scope type


32/260


33/260



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.

Exporting the Migration PackageThe 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

This section describes how to export the migration package.

1. On the AppBuilder Host Workbench panel, type LEon the Migration action line to navigate to theAppBuilder List Facility for Entity Migration panel.

2. Type EXPORTon the action line of your migration entity (Figure 2-26) and press Enter.

univers


34/260



Figure 2-26 Selecting the migration entity to export

3. On the Export Options panel, the object parts you can include are displayed with the letter Sin theselection field (see Figure 2-26). Press Enterto keep the selected options. Type a space over the Stodeselect 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 Exporton page 5-23for more information.

Figure 2-27 Selecting migration export options

.

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

Note Some repository administrators do not permit users to override the default processing options. See youradministrator if you have any questions.



Action Name System Id

________ DC_MIG01 AA37NREXPORT__ DMC_VER2 AA4FNR________ GETCAPPS AAAYNR

________ GETVIREQ AAAWNR________ GET524S AAAXNR________ JXL_ADM_OBJECT_ALL JXLADMO

________ LAI_PFDEFAULT AAAMNR________ MIG_DNAGE AA1WNR________ MIG_DNA0000 AA1NNR________ MIG_FDFAULT AAABNR________ MIG_FGBL01 AA1MNR________ MIG_FREPORT AAANNR________ MIG_NRV1TO_NRV2 AA3ONR________ MIG_QCLBWIND AA24NR________ MIG_TCFLVIEW AA1YNR

Command ===> _____________________________________________________________

Migration Export Options

Name . . . . . . . . : DMC_VER2Version . . . . . . : 1

Type 's' to select an option or type a space to deselect. Then press ENTER.

Processing OptionsObject Parts to Process . . . . . . . S Text

S Source

S Keywords

Data Set Prefix for Migration Files . SEEROUT.M00016NR_

Selective Export . . . . . . . . . . . 2 1. Yes2. No

Command =======> ___________________________________________________________


35/260



reduces the processing time. See Migrating Without Migration Fileson page 5-17for more

information.

See Selective Exporton page 5-23for 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

4. Press Enterto 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 forProcessed.

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).

Figure 2-29 Checking the migration state value

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-5for 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.

Note 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-20for more information.

Note To see the migration state change, refresh the screen: press F19, or type REFRESHon the commandline and press Enter.

___________________ Confirm Request ____________________| || Do you wish to use SEEROUT.DMCMIG01 as your || migration Data Set Prefix? || || || || 11. Yes || 2. No || |

| Command ===> ________________________________________ ||________________________________________________________|



Migration Attributes:Name . . . . . . . . . . . . DMC_VER2______________________System Id . . . . . . . . . : AA4FNRDescription . . . . . . . . . MIGRATE DMC_APP1 FROM V1 TO V2

Data Set Prefix . . . . . . . SEEROUT.M00016NR_Migration State . . . . . . : 9 Export Job Executing


Time Created . . . . . . . : 09:13Created by . . . . . . . . : SS0222Date Maintained . . . . . . : 95/10/02

Time Maintained . . . . . . : 09:55Maintained by . . . . . . . : SS0222Project . . . . . . . . . . : DEV

Change # . . . . . . . . . : 0004Owner Id . . . . . . . . . : SS0222

Local Maintenance Date . . : 95/10/02Local Maintenance Time . . : 09:55:05Command ===> _______________________________________________________________


36/260



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 Migrationon 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 seethe 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


37/260


CHAPTER

3

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


After You Import


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-1illustrates 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 entityduring source-environment processing. You can find the prefix on the Maintain an Entity panel for the

source migration entity.


38/260

3-2 Target Environment Processing


Figure 3-1 Target Repository Processing

1. Navigate to the AppBuilder Host Workbench panel of the repository, version, and projectto which

you are migrating. (To change projects, use the change projects (PROJECTS) action.)

2. Type ADDEon the Migration action line (Figure 3-2) and press Enter.

Figure 3-2 Creating the target migration entity

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.

univers

AppBuilder Host Workbench


Action Entity________ Field________ File

________ Form________ FSDM Scheme________ FSDM Value________ Function________ Help Text________ Identifier________ Key________ Location________ Logical Process________ Machine

ADDE____ Migration________ Organization________ Physical Event

________ Process________ Rebuild Package

Command ===>_______________________________________________________________


39/260



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.

Figure 3-3 Naming the target migration entity

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 system-

defined 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 byovertyping values and then typing SAVEon the command line again.

Figure 3-4 Maintaining the target

5. Type TXEon the command line to add text to the entity. The text describes the purpose and scopeof the migration package to other Migration Facility users (Figure 3-5shows sample text). This step

is optional. Press F3 to return to the Maintain an Entity panel.

Note The Data Set Prefix entry mustexactly match the name of the export data set prefix you are importing.

Add an Entity More: +


Migration Attributes:Name . . . . . . . . . . . . DMC_VER2______________________System Id . . . . . . . . . :

Description . . . . . . . . . TARGET OF DMC_AP1 FROM V1 TO V2Data Set Prefix . . . . . . . SEEROUT.M00016NR_

Migration State . . . . . . : 1. Analyze Approved2. Export Successful3. Import Successful4. Import Job Submitted5. Export Job Submitted6. Export Job Failed7. Analyze Job Failed8. Analyze Job Executing

9. Export Job Executing10. Analyze Successful

11. Analyze Job Submitted12. Import Job Failed13. Import Job Executing

Command ===>_______________________________________________________________



Migration Attributes:Name . . . . . . . . . . . . DMC_VER2______________________System Id . . . . . . . . . : AA4HNR

Description . . . . . . . . . TARGET FOR DMC_AP1 FROM V1 TO V2Data Set Prefix . . . . . . . SEEROUT.M00016NR_Migration State . . . . . . : 14 N/A


Time Created . . . . . . . : 11:10Created by . . . . . . . . : SS0222

Date Maintained . . . . . . : 95/10/02Time Maintained . . . . . . : 11:10Maintained by . . . . . . . : SS0222

Project . . . . . . . . . . : DEVChange # . . . . . . . . . : 0001Owner Id . . . . . . . . . : SS0222Local Maintenance Date . . : 95/10/02

User modifications to object have been Saved.Command ===>_______________________________________________________________


40/260



Figure 3-5 Adding text to the migration entity

6. Type Kon the command line to add keywords to the entity. Keywords describe the purpose andscope of the migration package to other Migration Facility users (Figure 3-6shows sample

keywords). This step is optional. Press F3to return to the Maintain an Entity panel.

Figure 3-6 Adding keywords to the entity

7. Return to the Maintain an Entity panel.

8. Press F3 to exit the Maintain an Entity panel. You can use the maintain entity (ME) action to displaythis panel if you want to check or change the entity attribute values.

9. 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.

Note Separate each keyword with a space, and do not exceed 240 characters for all the keywords for a singleentity.

--------- SS0222.SS0196.MOD.STK ------------------------------ COLUMNS 001 072TEXT for Migration

Name . . . . . . . : DMC_VER2Version . . . . . : 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

--------- SS0222.SS0196.MOD.STK ------------------------------ COLUMNS 001 072

KEYWORDS for Migration

Name . . . . . . . : DMC_VER2

Version . . . . . : 2

****** ***************************** TOP OF DATA ******************************000001 MIGRATION

000002 DMC000003 VER2000004 SS0222000005 DMC_CUSTOMER_MAINTENANCE000006 DMC_CUSTOMER_RESERVATION****** **************************** BOTTOM OF DATA ****************************

Command ===> ______________________________________________ Scroll ===> PAGE


41/260




Before importing into the target repository, you must perform an impact analysis. This impact analysis

is a what ifreport 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 targetenvironment, 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. On the AppBuilder Host Workbench panel, type LEon the Migration action line to navigate to theAppBuilder List Facility for Entity Migration panel.

2. Type ANALYZE on the action line of your migration entity (Figure 3-7) and press Enter.

Figure 3-7 Selecting the migration entity to analyze

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).

Figure 3-8 Selecting analyze options

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).



Action Name System IdANALYZE_ DMC_VER2 AA4HNR________ GET_NRV1V2 AA3YNR________ MIG_FDFAULT AA12NR

________ MIG_FREPORT AA13NR________ WMM_MIG_PHY_EVT AA2INR***************************** BOTTOM OF DATA ********************************

Migration Analyze Options


Enterprocessing information and press ENTER.

Processing OptionData Set Prefix for Migration Files . SEEROUT.M00016NR_

You can type a

different name

here to check

a different set

of files


42/260



Figure 3-9 Changing the Data Set Prefix

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 Impacton page 5-11for a discussion on rerunningand restarting the analyze job.

Figure 3-10 Selecting the Reload or Restart option

4. Press Enterto 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 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).

___________________ Confirm Request ____________________| || Do you wish to use SEEROUT.AXPMIG01 as your |

| migration Data Set Prefix? || || |

| || 1 1. Yes |

| 2. No || || Command ===> ________________________________________ |

|________________________________________________________|

Migration Analyze Options


Enterprocessing information and press ENTER.

Processing OptionData Set Prefix for Migration Files . SEEROUT.M00016NR_Execution Option . . . . . . . . . . . _ 1. Reload Migration Files

2. Restart


43/260



Figure 3-11 Checking the migration state value

6. You cannot continue until the migration state registers a value of Analyze Successful.See Table 5-

3 on page 5-5for 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.

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 @MIGENVnINI 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 Impacton 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 listmigration 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.

Note To see the migration state change, refresh the screen: press F19, or type REFRESHon the command

line and press Enter.

Note When you run the analyze job again, you can choose to rerun or restart the job. See Analyzing theMigration Impact on page 5-11for a more detailed discussion on rerunning and restarting the analyze job.



Migration Attributes:Name . . . . . . . . . . . . DMC_VER2______________________

System Id . . . . . . . . . : AA4HNRDescription . . . . . . . . . TARGET FOR DMC_AP1 FROM V1 TO V2

Data Set Prefix . . . . . . . SEEROUT.M00016NR_Migration State . . . . . . : 10 Analyze Successful

Audit Attributes:Date Created . . . . . . . : 95/05/12Time Created . . . . . . . : 11:10

Created by . . . . . . . . : SS0222Date Maintained . . . . . . : 95/10/02Time Maintained . . . . . . : 11:10Maintained by . . . . . . . : SS0222Project . . . . . . . . . . : DEVChange # . . . . . . . . . : 0003Owner Id . . . . . . . . . : SS0222Local Maintenance Date . . : 95/10/02Local Maintenance Time . . : 11:10Command ===> ______________________________________________________________


44/260



The resulting list has a migration will preparemessage by each object to be prepared. You must

first set the RUN_RBDETECTOR variable to Y for Yes in the @MIGENVnINI 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

app builder enterprise migration

Documents