Rochade DB2BUS Migration Utility for Legacy Data

Transcription

1 Rochade DB2BUS Migration Utility for Legacy Data Version 1.0 December 2005 Page 1

2 Contents: 1 Introduction Long Rochade Item Names for DB2BUS Data Prerequisites for Using Long Rochade Item Names for DB2BUS Data DB2BUS Migration Procedures for Legacy Data How to run DB2BUS Migration for Legacy Data Page 2

3 1 Introduction ASG-Rochade (referred to as Rochade in the remainder of this paper) releases before version 6 supported names limited to 32 characters only, and each item type spanned exactly one namespace for all items of that particular type. Limitations faced with that concept are: Difficulties in mapping fully qualified items o Datasets, DB2 columns, Java identifiers, No support for hierarchical namespace structures o Java identifiers, ER and UML modeling, Unintentional versioning of items of the same type that have been assigned identical names (homonyms) Alias names cannot be qualified. Starting with release 6, Rochade supports item names with up to 512 characters, herein called long Rochade item names. Furthermore, items may span a namespace, and naming groups are introduced to specify a context in which an item name is used. The advantages of the Rochade XNS (extended Name Service) concept are: Mapping of fully qualified items is no problem. Hierarchical namespace structures preclude naming conflicts. Isolation of contents of different applications via separate naming groups. Alias names can be qualified (typed alias). For further information, see the XNS White Paper located in ASG s ISP search in ASG- Rochade Technical Documentation for ASG-Rochade New Naming Features Introduced in Rochade 6.0. Page 3

4 2 Long Rochade Item Names for DB2BUS Data Starting at V8.20, DB2BUS for ASG-Rochade (herein called DB2BUS) contains functionality to support long Rochade item names. This functionality supports qualified item names but not hierarchical namespace structures. On the MVS (OS/390, z/os) platform, hierarchical concepts are not commonly used for navigation. Full qualification is predominant, instead. Therefore, for the case of MVS metadata, it was decided to switch to a purely flat naming structure and retain the existing technology. Bearing the aspect of compatibility in mind, conversion to long Rochade item names is carried such that data may seamlessly continue to be processed with the same applications as before. These item types are affected: Columns - DB2/COLUMN Constraints - DB2/CONSTRAINT Referential Constraints - DB2/REFERENTIAL-CONSTRAINT Prior to the DB2BUS long Rochade item name concept, potentially long item names were stored as follows: Identifiers obtained from DB2BUS were truncated to 32-character item names. The original name was stored in the attributes o o DB2/COLUMN_NAME for column items. DB2/CONSTRAINT-NAME for items of type constraints or referential constraints. With the long Rochade item name concept enabled, DB2BUS will use the original name which may be greater than 32 characters. Consequently a migration of existing DB2BUS data is required before this feature is enabled. Note that the DB2BUS long Rochade item name support will always build column item names with the table name included. This shift in the column item name is supported by the migration facility as well. The migration facility avoids mass re-scanning of the DB2BUS data already stored in Rochade. It is described and explained in the next chapters Page 4

5 3 Prerequisites for Using Long Rochade Item Names for DB2BUS Data As a prerequisite for using long Rochade item names for DB2BUS legacy applications, Rochade Client/Server version 6.20 or higher must be installed. We recommend the most recent release ( as of Dec. 2005). To ensure the full benefit of the long item names, the DB2BUS migration should only be carried out if WebAccess or Metability is available as GUI for the Rochade repository. While AutoPilot has been supporting long names to some extent since version , it cannot be extended to provide complete functionality for long item names: functionality such as Rename or Save as is not possible and the content of link attributes are shown only with kernel-generated synthetic 32-character item names. Furthermore, if namespaces are used in various Rochade repository applications, complete navigation is only available through WebAccess and Metability. The following minimum release levels are required to enable long Rochade item name support: Rochade ( recommended as of December 2005) I-RIM ( recommended as of December 2005) DB2BUS (requires procedures ROUTIL ) If you have one or all of the following Rochade interfaces that support metadata transfer for the traditional MVS environment, it is strongly recommended to include them into migration considerations: SCANASM MVS (OS/390, z/os) Assembler scanner SCANCOB MVS (OS/390, z/os) IBM Cobol scanner SCANPLI - MVS (OS/390, z/os) IBM PL/I scanner SCANMVS - MVS (OS/390, z/os) JCL scanner Please use the ASG-Intelligent Support Portal and download the ASG-Rochade XNS Migration Utility for Legacy Scanners that provides functionality to migrate items from traditional 32-character names to long Rochade item names. Detailed instructions can be found in the paper Rochade XNS Migration Utility for Legacy Scanner Applications as contained in the TechDoc folder of that utility package. Page 5

6 Support for long Rochade item names by DB2BUS since V8.20 is provided in two modes, compatibility and standard. Specific catalog extract modules are delivered to support each mode. compatibility mode - uses the naming limits of DB2 V7 and older DB2 releases standard mode - uses the enhanced naming limits of DB2 V8. Item Type V7 naming limit V8 naming limit TABLE COLUMN VIEW SYNONYM INDEX ALIAS TRIGGER SEQUENCE DISTINCT-TYPE REFERENTIAL CONSTRAINT CONSTRAINT STORAGE-GROUP SCHEMA for Trigger, Distinct-Type, Sequence When using DB2BUS since V8.20 with an older DB2 release (DB2 V7 and prior), only compatibility mode is supported and therefore only one catalog extract module is delivered for each older DB2 release. Note that if Rochade DB2 data populated by DB2BUS V8.20 running in standard mode is to be used with existing Rochade DB2 data, the existing data will not be compatible and must first be migrated. The migration process is explained in the next chapter When installing and preparing to run DB2BUS since V8.20, a careful distinction must be made between the enhanced DB2 naming limits starting with DB2 Version 8 and the use of the Rochade long item names starting with DBV2BUS In addition, starting with DB2 Version 8, the DB2 system catalog may be setup in either ASCII/UNICODE or EBCDIC code thus providing another DB2BUS 8.20 dependency which must be considered. Page 6

7 Review the scenarios illustrated in the table next below to determine: the appropriate catalog extract module link/bind to be performed the corresponding value to be reflected in the setting of &RIROXNS = YES / NO in member RIDBCUST of the <HLQ>.RIKOMP.REXX library. Criteria to consider Jobs to run during installation DB2 desired Data Link with VersionRochademigration item required a)ascii names b)ebcdic V8 V8 limited byno 32 char long item names yes Bind with a)ascii b)ebcdic Option to choose during execution RIDBCUST Modules involved Module as delivered a)ascii b)ebcdic Load Module a)dbblink8a)dbbbind8&riroxns=no a)ridbx118 RIDBU118 b)dbblinf8 b)dbbbine8 b)ridbe118 a)dbblin28 a)dbbbin28 &RIROXNS=YESa)RIDBX218 RIDBU218 b)dbblinf8 b)dbbbinf8 b)ridbe218 Comment only recommended if the customer uses V8 DB2 within the DB2 naming limits as of V7 or prior the long term preferred V7 V7 limited byno 32 char long item names yes DBBLINK7 DBBBIND7 &RIROXNS=NO RIDBX117 RIDBU117 the standard before DB2BUS 8.20 DBBLINK7 DBBBIND7 &RIROXNS=YESRIDBX117 RIDBU117 not yet explained in the User s Guide but proofed in recent testing V6 V6 limited byno 32 char long item names yes DBBLINK6 DBBBIND6 &RIROXNS=NO RIDBX116 RIDBU116 the standard before DB2BUS 8.20 DBBLINK6 DBBBIND6 &RIROXNS=YESRIDBX116 RIDBU116 not yet explained in the User s Guide but proofed in recent testing All other combinations are not supported (even if they work theoretically). Page 7

8 4 DB2BUS Migration Procedures for Legacy Data This chapter introduces the procedures used to migrate items from traditional 32- character names to long Rochade item names. The following procedures are provided by ASG for DB2BUS data migration: RO-DB2BUS-MIGRATION RO-DB2BUS-MIGRATE.COLUMNS RO-DB2BUS-MIGRATE.CONSTRAINTS These procedures provide the following functionality: migrating data for a given AutoPilot application (subject area or project) updating the application's control data to properly reflect the FLAT name structure options to run a preview and execute an estimate of how long the migration is likely to take. Additionally, ASG supplies a control item ROSHELL-SYSTEM RO-DB2BUS-MIGRATION. The main procedure, RO-DB2BUS-MIGRATION, can either be called from the command line in AutoPilot or in batch mode. Make sure the application (subject area or project) that contains the legacy DB2BUS data is open. If called from the command line, progress will be displayed in the GUI and logging information will be written to a file. If called in batch, the logging information will be written to the DESCRIPTION attribute of a ROSHELL-SYSTEM named RO-DB2BUS-MIG-<[PRV EST REN]_YYMMDD_HHMMSS>. The suffix is indicating the mode ([PRV EST REN]) the procedure was called with and the date and time (YYMMDD_HHMMSS) the log was created (for details, see below). You can open it in the AutoPilot Administration. If execution is canceled by user request or aborted for some reason, it can be restarted without losing data integrity. The log information of an aborted run is lost, but that of a canceled run will be available. Page 8

9 The migration procedure can be executed with the following command: RO-DB2BUS-MIGRATION <mode> [flag] mode = [PREVIEW ESTIMATE RENAME] flag = [NIL REPAIR] PREVIEW Provides a log of what has to be done during migration. Optionally, there is a repair functionality to remove items that are orphans but duplicates of other items. ESTIMATE Delivers an estimate in hours of how long the RENAME operation is likely to take. It is based on statistical calculations and simulates the rename operation in the database. For that purpose, for all items to be renamed, the number of usages and the number of links in the referencing link attributes are counted. It can be executed in OPTIMISTIC, NORMAL or PESSIMISTIC mode depending on the settings in the control item. Note that the estimate is based on a simulation so it cannot guarantee that the RENAME function will finish within the time frame returned by the estimate. Nevertheless, mode NORMAL should deliver an estimate for the time that the migration is most likely to take. The modes OPTIMISTIC and PESSIMISTIC deliver estimates that span a range of time within which the migration is likely to finish. This range of time can be considered an indicator of how the migration time may vary based on factors that depend on how closely the real item structure in the database compares to the assumptions made in the estimate. This estimate cannot speculate on how conditions regarding system resources may differ from the time the estimate is executed to the time the migration will take place. RENAME Actually executes the migration from 32-character names to long Rochade item names and will write a log about renamed items and detected conflicts. If RENAME completes successfully, the application control information will be updated that the migrated subject area or project will consequently be considered as having a FLAT name structure. The procedure RO-DB2BUS-MIGRATION is invoking the requested functionality for the individual item types: RO-DB2BUS-MIGRATE.COLUMNS for item type DB2/COLUMN. RO-DB2BUS-MIGRATE.CONSTRAINTS for item types DB2/CONSTRAINT or DB2/REFERENETIAL-CONSTRAINT. Those procedures provide the standard functionality required for migration. If you have to migrate customized DB2BUS data that requires asdditional migration activities, just make a copy (with different name) of this procedure and adjust the settings in the control item ROSHELL-SYSTEM RO-DB2BUS-MIGRATION (see below) accordingly. In such a situation it is recommended to get in contact with ASG Customer Support for additional assistance. Page 9

10 The control item ROSHELL-SYSTEM RO-DB2BUS-MIGRATION will be delivered with the following contents in the DESCRIPTION attribute (Lines starting with semicolon are comments): ##################################################################################### Control item for DB2BUS Migration Format: Defines section: - saves variables used. - declares type and attributes names required. Creator section: - declares whether the item names are built with creator name as suffix, prefix or without, depends on the following DB2BUS options &RIDBCNAM and &RIDBCSUF used: /* USE CREATOR AS PREFIX FOR ROCHADE DOCUMENT NAMES == */ /* OF TABLES, INDEXES, COLUMNS ETC: YES/NO ==== */ SET &RIDBCNAM = YES /* USE SUFFIX INSTEAD OF PREFIX FOR ROCHADE DOCUMENT NAMES ==== */ /* IF YES: -NAMES OF TABLES, VIEWS, SYNONYMS, INDEXES, ALIASES ==== */ /* ARE BUILT AS <NAME>.<CREATOR> ==== */ /* -NAMES OF INDEXPARTS ==== */ /* ARE BUILT AS <NAME>.<CREATOR>.NN ==== */ /* -NAMES OF CONSTRAINTS, REFERENTIAL CONSTRAINTS ==== */ /* ARE BUILT AS <TABLE>.<CREATOR>.<CONSTRAINT> ==== */ /* -NAMES OF COLUMNS ==== */ /* ARE BUILT AS <COLUMN>.<TABLE>.<CREATOR> ==== */ /* -NAMES OF TRIGGERS, SEQUENCES, PROCEDURES ==== */ /* ARE BUILT AS <NAME>.<SCHEMA> ==== */ /* -NAMES OF PARAMETERS ==== */ /* ARE BUILT AS <NAME>.<SCHEMA>.<PARAM> ==== */ SET &RIDBCSUF = NO <CREATOR=[NIL PREFIX SUFFIX]/> Column name section: - declares whether the column item names are built with table name or without, depends on the following DB2BUS option: /* GENERATE ROCHADE DOCUMENT NAMES FOR COLUMNS WITH OR WITHOUT == */ /* TABLE NAME PREFIX ==== */ /* IF NO: COLUMN NAMES ARE MADE UNIQUE USING NUMERIC SUFFIX ==== */ SET &RIDBCTNA = YES <COLNAME=[NIL TABNAME]/> Page 10

11 Type section: - lists the types to be migrated: Columns, Constraints and Referential Constraints - each type my have a procedure <pre-proc> assigned that runs the migration process for each item of that type. This procedure has to support the modes PREVIEW ESTIMATE RENAME and gets passed the following arguments: ARG1 = item type ARG2 = item short name ARG3 = item long name ARG4 = Mode PREVIEW RENAME ESTIMATE ARG5 = wa with attribute list - those attributes will be excluded during orphan identification (PREVIEW only) ARG6 = log WA ARG7 = wa to store remove commands ARG8 = variable to store number of items to be changed RETCODE: [T IGNORE CANCEL] T - ok and continue processing IGNORE - stop processing just for that item, continue with the next item CANCEL - stop entire processing Constraints and Referential Constraints share the same procedure - each type may have attributes assigned that will be ignored by orphan identification. Orphans are items that are not referenced and do not have any other attribute different from those to be ignored. Set name structure option: - when processiong for option RENAME is finshed then the subject areas or projects control data will be set to FLAT name structure unless option SET-NAME-STRUCT is set to NO. <SET-NAME-STRUCT=[YES NO]/> Estimate option: - The estimate given is based on statistical calculations and simulates the rename operation in the database. - Mode NORMAL (recommended and default) delivers a close estimate for the time the migration is likely to take. - Mode OPTIMISTIC and PESSIMISTIC deliver estimates that span a range of time in which the migration is likely to finish. This range of time can be considered as indicator how the migration time may vary based on factors that depend on how close the real item structure in the database is compared to the assumptions made in the estimate. <ESTIMATE=[OPTIMISTIC NORMAL PESSIMISTIC]/> ##################################################################################### Page 11

12 <DEFINES> save variables #R&O-SAVE-VARIABLE DEFCOL DEFTAB DEFCST DEFREF #R&O-SAVE-VARIABLE DEFT2COL DEFT2CST DEFT2REF #R&O-SAVE-VARIABLE DEFNMCOL DEFNMCST item type for column #$MAKE DEFCOL DB2/COLUMN item type for table #$MAKE DEFTAB DB2/TABLE item type for constraint #$MAKE DEFCST DB2/CONSTRAINT item type for referential constraint #$MAKE DEFREF DB2/REFERENTIAL-CONSTRAINT link attribute for table -> columns #$MAKE DEFT2COL DB2/HAS-COLUMN link attribute for table -> constraints #$MAKE DEFT2CST DB2/HAS-CONSTRAINT link attribute for table -> referential constraints #$MAKE DEFT2REF DB2/HAS-REF-CONSTRAINT attribute name for original column name #$MAKE DEFNMCOL DB2/COLUMN_NAME attribute name for original constraint name #$MAKE DEFNMCST DB2/CONSTRAINT-NAME </DEFINES> <CREATOR=NIL/> <CREATOR=PREFIX/> <CREATOR=SUFFIX/> <COLNAME=TABNAME/> <COLNAME=NIL/> <TYPES> #$PUTWD. :DEFCOL RO-DB2BUS-MIGRATE.COLUMNS DEFINITION #$PUTWD. :DEFCST RO-DB2BUS-MIGRATE.CONSTRAINTS DEFINITION #$PUTWD. :DEFREF RO-DB2BUS-MIGRATE.CONSTRAINTS DEFINITION </TYPES> <ESTIMATE=NORMAL/> <ESTIMATE=OPTIMISTIC/> <ESTIMATE=PESSIMISTIC/> <SET-NAME-STRUCT=YES/> <SET-NAME-STRUCT=NO/> Page 12

13 <DEFINES> section: For each type involved, the types section contains statements to initialize variables with the appropriate item type names and attributes names that may vary form the standard C-RIM names in case your environment is customized. Please verify that the assignments fit to the specific DB2BUS RIM definitions in use at your Rochade installation. You definitely need to adjust this section if item types and attributes are involved that differ from those delivered with the C-RIM. <TYPES> section: For each type to be processed, the <TYPES> section contains one line with the following format: #$PUTWD. :<type_var> <type_proc> DEFINITION [attr_1[attr_2 [attr_n]]] You may modify the <TYPES> section to exclude/include item types from processing. The item type is pecified by the <type_var> as declared in the <DEFINES> section. If necessary adjust the name of the processing procedures <type_prc>. Optionally, a list of attributes is passed to the preprocessor procedure via arguments. If items are identified as duplicates (duplicates are items to which an identical long name is assigned), their orphans are determined. An item is considered an orphan if it is not referenced by any other item via a link and if it contains no attributes other than the ones that appear on the list of those passed to the preprocessor procedure. Consequently, those attributes should be included on this list that are not of interest from the point of view of metadata, but are administered with the item only for technical reasons. <CREATOR> option: This option declares whether the existing item names are built by DB2BUS with creator name as suffix, prefix or without: <CREATOR=[NIL PREFIX SUFFIX]/> It depends on the DB2BUS options &RIDBCNAM and &RIDBCSUF used during import of the DB2BUS legacy data, see member RIDBCUST of the <HLQ>.RIKOMP.REXX library. Note, in case CREATOR=NIL, i.e., the creator name is neither used as prefix nor suffix items of the types DB2/CONSTRAINT or DB2/REFERENETIAL-CONSTRAINT are not subject of any migration. <COLNAME> option: This option declares whether the column item names are built with a table name part or without. <COLNAME=[NIL TABNAME]/> It depends on the DB2BUS option & RIDBCTNA used during import of the DB2BUS legacy data, see member RIDBCUST of the <HLQ>.RIKOMP.REXX library. Note, in case COLNAME=NIL, i.e., the table name is not part of the column item name, all items of type DB2/TABLE are subject of migration to make the table name part of the name of all column items. Page 13

14 <ESTIMATE= [OPTIMISTC PESSIMISTC NORMAL] > option: The estimate simulates the rename operation in the database using the following approach: The number of items to be renamed will be identified. For those items, both the usages and the number of links in the referencing link attributes are counted. The ESTIMATE option specifies which statistical calculation shall be applied to define the test data that are to be used to simulate the migration: Mode NORMAL delivers a close estimate for the time the migration is likely to take. Mode OPTIMISTIC and PESSIMISTIC deliver estimates that span a range of time in which the migration is likely to finish. This range of time can be considered as indicator how the migration time may vary based on factors that depend on how close the real item structure in the database is compared to the assumptions made in the estimate. The simulation creates a sample of 1,000 items to be renamed having an environment as defined by the estimate mode. These items are renamed and the time this takes is measured. Then the final time estimate is proportional to the actual number of items to be renamed. All the items created for the simulation are removed afterwards. Note: This is only a rough estimate. There is no guarantee that the RENAME runs in the same time frame as the estimate. The estimate also cannot speculate about how conditions regarding system resources may differ between the time the estimate is executed and the time the migration takes place. <SET-NAME-STRUCT=[YES NO]/> option: This option controls whether or not the application's internal control flag will be set to indicate a FLAT name structure for the subject area or project after the migration completed successfully. YES is the default and is recommended. Page 14

15 5 How to run DB2BUS Migration for Legacy Data Please read this paper completely before starting the migration. If you have any questions or concerns, contact ASG Customer Support before running any migration steps. You may also decide to request assistance from ASG Professional Services. Before working on the migration, make sure you have a backup of your databases. Identify all procedures you may have written that rely on the traditional mechanism to truncate item names to 32 characters. In AutoPilot, you can find them if you invoke the Procedure Manager (menu: Development Procedure Development) and search for any usage of the procedures R&0-GET-SHORTNAME or R&0-GET-FULLNAME. Adjust those procedures to use the procedure RO-CONVERT-NAME instead: RO-CONVERT-NAME ARG1 = type in (L / I / S) L= long name S=short name I=item Id ARG2 = type out (L / I / S / D) L= long name S=short name I=item Id D=display format ARG3 = item type / nil ARG4 = item name / item id ARG5 = optional result variable for item type ARG6 = optional result variable for item name ARG7 = CREATE / CREATEOLD / nil ARG8 = if ARG7 = CREATE: value attribute name ARG9 = if ARG7 = CREATE: value attribute value ARG10 = name group flag A = use AutoPilot naming group numeric = naming group other = use system naming group $NMGRP OUTPUT : Converts item name (from an existing item) and writes it either into the current work area or in the optional result variable. If ARG1 = I, then also the type is set or is written into the current work area. The item has to exist. FUNKTION: Converts item names between long name, ID or short names as requested. The procedure RO-CONVERT-NAME supports converting a long item name to a synthetically 32-character name. Furthermore, you have to ensure that all write operations to a link attribute either are done with $MPUT or are using synthetic, kernel-generated 32-character names whenever long names may be involved. You may also decide to develop a different approach, based on RPL commands, directly to retrieve the complete item name where required. In this case you can use the procedures RO-CONVERT-NAME as a template. If you do so, the adjustments to your procedures will work consistently only after the migration is done. Consequently, a test environment is recommended for trying it out. If you cannot adjust these procedures yourself, contact ASG Customer Support. Please do not modify procedures delivered by ASG if in doubt, also contact ASG Customer Support. Page 15

16 It is recommended that you execute the migration within a test environment first. Follow the same approach as described below in "Migration Steps". After the test migration is completed successfully, you should check the data integrity carefully. If data integrity is confirmed in the test environment, you are ready to run the migration of your production environment as described in "Migration Steps" (below). Migration Steps: 1. Before executing the migration, make sure you have a backup of your databases. 2. Identify which of the following products you are using and what item types are involved: o SCANASM - SCN/MACRO for inner macros o SCANCOB - SCN/SECTION for program sections o SCANPLI - SCN/PROCEDURE for PL/I procedures o SCANMVS - SCN/DSN for datasets (including UNIX path names) If any of these products is in use Please use the ASG-Intelligent Support Portal and download the ASG-Rochade XNS Migration Utility for Legacy Scanners that provides functionality to migrate items from traditional 32-character names to XNS names. Detailed instructions can be found in the paper Rochade XNS Migration Utility for Legacy Scanner Applications as contained in the TechDoc folder of that utility package and follow those instructions. Especially make sure the procedure packages that provide long Rochade item names support for the legacy scanners are installed: o o SCANASM & SCANMVS require ROSCAN package version or higher. SCANPLI & SCANCOB require ROSCAN3 package version or higher. 3. Verify that you have the standard C-RIM in use, i.e., check if the item type and attribute names used in the <DEFINES> section of the control item ROSHELL- SYSTEM RO-DB2BUS-MIGRATION match to your installation. If this does not hold true for the item or attribute types, adjust them in the <DEFINES> section of the ROSHELL-SYSTEM RO-DB2BUS-MIGRATION control item accordingly. 4. Adjust your naming options used for DB2BUS in the ROSHELL-SYSTEM RO- DB2BUS-MIGRATION control item accordingly, standard delivery contains: o o <CREATOR=PREFIX/> <COLNAME=TABNAME/> 5. Ensure that you have exclusive access to the items you will migrate. At a minimum, you must have exclusive access to the application (subject area or project) that contains the legacy scanner data. Be aware that items in other applications are potentially affected and that renaming will impact all versions of an item and all items having links to that particular instance. To be safe, it is recommended that you have exclusive access to the database containing those data. Page 16

17 6. Run the migration procedure in PREVIEW mode: o RO-DB2BUS-MIGRATION PREVIEW The resulting log will contain information about the items to be renamed, and it will report potential conflicts, i.e., different items that are supposed to have the same long name. The log is similar to the example presented below. The header Duplicates: Lvl shortname long name precedes the table of conflicts found. The table is followed by a list that indicates for each Lvl number whether or not the involved items have attributes different from the DEFINITION attribute, and whether they are referenced by other items. The attributes investigated may vary depending on the settings in the <TYPES> section as explained in the previous chapter. Page 17

18 DB2BUS-Migration --- Preview Log: Control item: ROSHELL-SYSTEM RO-DB2BUS-MIGRATION Naming option CREATOR: PREFIX Naming option COLNAME: TABNAME --- Section DEFINES --- save variables #R&O-SAVE-VARIABLE DEFCOL DEFTAB DEFCST DEFREF #R&O-SAVE-VARIABLE DEFT2COL DEFT2CST DEFT2REF #R&O-SAVE-VARIABLE DEFNMCOL DEFNMCST item type for column #$MAKE DEFCOL DB2/COLUMN item type for table #$MAKE DEFTAB DB2/TABLE item type for constraint #$MAKE DEFCST DB2/CONSTRAINT item type for referential constraint #$MAKE DEFREF DB2/REFERENTIAL-CONSTRAINT link attribute for table -> columns #$MAKE DEFT2COL DB2/HAS-COLUMN link attribute for table -> constraints #$MAKE DEFT2CST DB2/HAS-CONSTRAINT link attribute for table -> referential constraints #$MAKE DEFT2REF DB2/HAS-REF-CONSTRAINT attribute name for original column name #$MAKE DEFNMCOL DB2/COLUMN_NAME attribute name for original constraint name #$MAKE DEFNMCST DB2/CONSTRAINT-NAME --- End DEFINES --- Application: S DB2BUS TEST Configuration: C 1010 C 100 C 1 Item types processed: DB2/COLUMN DB2/CONSTRAINT Page 18

19 DB2/REFERENTIAL-CONSTRAINT Total time: 10:39:11 till 10:39:11 = 0.1 hours XNS-Migration for DB2/COLUMN items: Preview --- Items checked: 8 Time: 10:39:11 till 10:39:11 Items to be renamed: 3 Items having a different short name for a particular long name (duplicates): Duplicates: 3 Long names involved by duplicates: 1 Duplicates proposed to be removed: 1 The same level indicates identical long names in the table of duplicates. Duplicates: Lvl shortname long name 0001 DSN_FUNCTION_TABLE.SPEC_FUNC_NA1 DSN_FUNCTION_TABLE.SPEC_FUNC_NAME 0001 DSN_FUNCTION_TABLE.SPEC_FUNC_NA3 DSN_FUNCTION_TABLE.SPEC_FUNC_NAME 0001 DSN_FUNCTION_TABLE.SPEC_FUNC_NAM DSN_FUNCTION_TABLE.SPEC_FUNC_NAME Item type: DB2/COLUMN Level: 0001 Long name: DSN_FUNCTION_TABLE.SPEC_FUNC_NAME Page 19

20 Short name: DSN_FUNCTION_TABLE.SPEC_FUNC_NA1 state: T Application specific value attributes: DB2/BITDATA S DB2/COLNO 010 DB2/COLTYPE CHAR DB2/DEFAULT N DB2/IBMREQD N DB2/LENGTH DB2/NULLS N DB2/OWNER-SYSTEM PROD Application specific text/link/binary attributes: DB2/COLUMN_LONG_NAME References & Usage: <-- DB2/TABLE DSN_FUNCTION_TABLE Short name: DSN_FUNCTION_TABLE.SPEC_FUNC_NA3 state: T Application specific value attributes: none Application specific text/link/binary attributes: none References & Usage: <-- DB2/TABLE DSN_FUNCTION_TABLE Short name: DSN_FUNCTION_TABLE.SPEC_FUNC_NAM state: T Application specific value attributes: DB2/BITDATA S DB2/COLNO 010 DB2/COLTYPE CHAR DB2/DEFAULT N DB2/IBMREQD N DB2/LENGTH DB2/NULLS N DB2/OWNER-SYSTEM PROD Application specific text/link/binary attributes: Page 20

21 DB2/COLUMN_LONG_NAME References & Usage: <-- DB2/TABLE DSN_FUNCTION_TABLE Duplicates: items to be removed #$REMOVE DB2/COLUMN DSN_FUNCTION_TABLE.SPEC_FUNC_NA3 Duplicates: items to be preserved DB2/COLUMN DSN_FUNCTION_TABLE.SPEC_FUNC_NA1 DB2/COLUMN DSN_FUNCTION_TABLE.SPEC_FUNC_NAM Items ignored: 1 ### ### Item ignored: DB2/COLUMN DSN_FUNCTION_TABLE.SPEC_FUNC_NA2 does not belong to a table! XNS-Migration for DB2/CONSTRAINT items: Preview --- Items checked: 7 Time: 10:39:11 till 10:39:11 Items to be renamed: 0 Items having a different short name for a particular long name (duplicates): Duplicates: 0 XNS-Migration for DB2/REFERENTIAL-CONSTRAINT items: 0 Page 21

22 --- Preview --- Items checked: 0 Time: 10:39:11 till 10:39:11 Items to be renamed: 0 Items having a different short name for a particular long name (duplicates): Duplicates: 0 The header Duplicates: items to be removed is followed by a list of the orphans that can be deleted automatically since they have no attribute other than DEFINITION and the attribute with the original name neither are referenced by any other item. The section following the header Duplicates: items to be preserved lists the items that cannot be removed automatically. Page 22

23 7. If conflicts are reported, run RO-DB2BUS-MIGRATION in PREVIEW mode and with the REPAIR flag as an additional parameter: o RO- DB2BUS -MIGRATION PREVIEW REPAIR If you run it in dialog, confirm removing orphans, i.e., the items reported in the previous step as Duplicates: items to be removed. If the procedure is called in batch, the orphans will be removed without additional confirmation. You receive a log that is almost identical to the log from the previous step. The section following the header Duplicates: items to be preserved lists the remaining conflicts. These items cannot be removed automatically. Please review and consolidate attributes of such duplicates as reasonably possible, and remove the obsolete items manually. After you have thus resolved these conflicts manually, run step 7 again. 8. Run the migration procedure using the ESTIMATE mode. o RO-DB2BUS-MIGRATION ESTIMATE Although the estimate with option NORMAL should give an impression of how long the RENAME may take, it is recommended to run the estimate in PESSIMISTIC and OPTIMISTIC modes as well. For that purpose, adjust the ROSHELL-SYSTEM RO-DB2BUS-MIGRATION item accordingly as described in Chapter 4. The following line in the log gives the time estimated: Time estimated for rename processing: <hh.h> hours Note: The estimate is not a guarantee that the RENAME operation will run in the predicted time frame. If the estimate does not convince you that the migration can be executed within a time frame that is available to you, do not continue with the migration, but contact ASG Customer Support instead. Page 23

24 10. If you are satisfied with the estimate and have an appropriate time window for the migration available to you, execute the migration procedure with mode RENAME: o RO-DB2BUS-MIGRATION RENAME You receive a log similar to the following: DB2BUS-Migration --- Rename Log: Control item: ROSHELL-SYSTEM RO-DB2BUS-MIGRATION Naming option CREATOR: PREFIX Naming option COLNAME: TABNAME --- Section DEFINES --- save variables #R&O-SAVE-VARIABLE DEFCOL DEFTAB DEFCST DEFREF #R&O-SAVE-VARIABLE DEFT2COL DEFT2CST DEFT2REF #R&O-SAVE-VARIABLE DEFNMCOL DEFNMCST item type for column #$MAKE DEFCOL DB2/COLUMN item type for table #$MAKE DEFTAB DB2/TABLE item type for constraint #$MAKE DEFCST DB2/CONSTRAINT item type for referential constraint #$MAKE DEFREF DB2/REFERENTIAL-CONSTRAINT link attribute for table -> columns #$MAKE DEFT2COL DB2/HAS-COLUMN link attribute for table -> constraints #$MAKE DEFT2CST DB2/HAS-CONSTRAINT link attribute for table -> referential constraints #$MAKE DEFT2REF DB2/HAS-REF-CONSTRAINT attribute name for original column name #$MAKE DEFNMCOL DB2/COLUMN_NAME attribute name for original constraint name #$MAKE DEFNMCST DB2/CONSTRAINT-NAME --- End DEFINES --- Page 24

25 Application: S DB2BUS TEST Configuration: C 1010 C 100 C 1 Item types processed: DB2/COLUMN DB2/CONSTRAINT DB2/REFERENTIAL-CONSTRAINT Total time: 10:59:57 till 10:59:57 = 0.1 hours XNS-Migration for DB2/COLUMN items: 438 Items processed: 5 Time: 10:59:57 till 10:59:57 Renamed: 1 Failed: 0 Skipped (name already complete): 4 XNS-Migration for DB2/CONSTRAINT items: 7 Items processed: 7 Time: 10:59:57 till 10:59:57 Renamed: 0 Failed: 0 Skipped (name already complete): 7 XNS-Migration for DB2/REFERENTIAL-CONSTRAINT items: 0 Items processed: 0 Time: 10:59:57 till 10:59:57 Renamed: 0 Failed: 0 Skipped (name already complete): 0 The log lists statistics and the items that could not be processed successfully. 11. After the DB2BUS migration is completed, check data integrity. 12. Enable DB2BUS to support long Rochade item names, see chapter 3 and DB2BUS release notes and manuals for guidance. Page 25