User Guide - ARCAD Transformer DB Online Help

North America & LATAM EMEA (HQ) Asia Pacific70 Main Street, Suite 105Peterborough NH 03458USA1-603-371-90741-800-676-4709 (toll free)[email protected]

55 Rue Adrastée – Parc Altaïs74650 Chavanod/AnnecyFrance

+33 450 578 [email protected]

c/o Pramex Intl Ltd1 Austin Rd West Intl Commerce Centre7107B 71/F KowloonHong Kong

[email protected]

Publication Date: April, 2021

Prepared by the ARCAD Documentation Team

User GuideARCAD-Transformer

DBVersion 13.1

ARCAD-Transformer DB v13.1User Guide |

Copyright © 1992-2021 by ARCAD. All rights reserved.

The following terms are names owned by International Business Machines Corporation in the United States,other countries, or both: AS/400®, ClearCase, ClearQuest®, DB2, DB2 Connect™, DB2 Universal Database™,ibm.com, IBM i, iSeries, System i, OS/400, Rational®, SP2, Service Pack, WebSphere. Java and all names basedon Java are owned by Oracle Corp. in the United States, other countries, or both. Eclipse is a registeredtrademark of Eclipse Foundation, Inc. Other names of companies, products or services are the property of theirrespective owners.

Page 2 / 126ARCAD • Copyright © 2021 • All Rights reserved. • arcadsoftware.com

http://www.arcadsoftware.com/

ARCAD-Transformer DB v13.1Contact ARCAD | User Guide

Contact ARCAD

Headquartered in France at the foot of the Alps, ARCAD offers global services and has offices andpartners all over the world. ARCAD partners with leading-edge companies throughout the world tooffer full services, close to home.

Visit our website to Contact Us and find out more about our company and partners, or to request ademo.

The ARCAD Customer Portal is intended for current and potential customers that have full or trialversions of ARCAD software. If you already use or are interested in using an ARCAD product, the portallets you view all of your current licenses and generate your own temporary license keys for mostARCAD products. It grants you access to the ARCAD product knowledge base (new releases, releasenotes and current documentation).

Do you have a request for change or have you encountered a bug? Log into the ARCAD Helpdesk andcreate a ticket.

ARCAD guarantees consultant support 24 hours a day, 5 days a week (24/5) to registered members.Calls received are redirected, according to the hour, to put you in contact with a support team in or nearyour timezone.

Country Address Account Contact Support Contact

FranceARCAD Software (HQ)55 Rue Adrastée74650 Chavanod +33 4 50 57 83 96

[email protected]

Worldwide 24/7:+1 603 371 3256

France only:+33 450 57 28 00

[email protected]

ARCAD Helpdesk

GermanyARCAD Software Deutschland GmbHc/o Pramex International GmbHIm Trutz, Frankfurt 55 60322

China

ARCAD Software Products Private LmtdRoom D07, Floor 34, No.32, Zhujiang EastRoadTianhe District, Guangzhou

+86 (020)22324643+86 (020)[email protected]

IndiaARCAD SoftwareD-280/281/282, Vibhuti KhandGomti Nagar, Lucknow

Hong Kong

ARCAD Software Asiac/o Pramex Intl Ltd1 Austin Rd West Intl Commerce Centre7107B 71/F KowloonHong Kong

+852 3618 6118

USAARCAD Software Inc.70 Main Street, Suite 105Peterborough, NH 03458

+1 (603) 371-9074+1 (800) [email protected]

Table 1: Contact ARCAD


https://arcadsoftware.com/about/contact/

https://customer.arcadsoftware.com/

https://akuiteo.arcadsoftware.com/akuiteo.clients

mailto:[email protected]


https://akuiteo.arcadsoftware.com/akuiteo.clients





ARCAD-Transformer DB v13.1User Guide | Preface

Preface

Document purposeThis document is intended to guide you through configuring and using ARCAD-Transformer DB.

Intended audienceThis document is intended for all ARCAD-Transformer DB users. It is recommended that users befamiliar with ARCAD-Skipper and preferably other ARCAD products as well.

Related documentationARCAD technical documentation can be accessed from the product's online help or by logging into theCustomer Portal on our website.

Related documentation

ARCAD-Transformer DB Best Practices Guide

ARCAD Release Notes

ARCAD General Documentation

ARCAD-Skipper documentation

ARCAD-Observer documentation

ARCAD-Audit documentationTable 2: Related documentation

Publication recordUnless stated otherwise, all content is valid for themost current version of ARCAD-Transformer DBlisted as well as every subsequent version.

Productversion

Documentversion

Publicationdate Update record

≥ 13.1 1.7 April, 2021Updated all icons and screenshots to comply with new UI.Updated the configuration preferences Configuring the ARCAD-Transformer DB perspective

13.0 1.6 December,2020 Added Installing the ARCAD-Transformer DB Eclipse plug-in

12.2 1.5 September,2020 Updated Configuring the ARCAD-Transformer DB perspective on page 31

12.0 1.4 March, 2020 No functional changes.

11.0 1.3 June, 2019 No functional changes.

10.9 1.2 June, 2018 LFSHRPFFMT parameter updated

10.6 1.1 February,2016

Modified description of Transformation Process layout.Improved process description and added examples.

10.6 RC 1.0 November,2015 Initial publication

Table 3: ARCAD-Transformer DB User Guide publication record


https://arcadsoftware.com/customer/


ARCAD-Transformer DB v13.1Contents | User Guide

Contents

Contact ARCAD 3

Preface 4

Contents 5

Tables 8

Figures 9

INTRODUCTION1 About ARCAD-Transformer DB 111.1 Business context 121.2 Functional description 121.3 Functional constraints 13

2 Simplified concepts 14

3 About transformation strategies 163.1 ARCAD’s full-conversion transformation strategy 163.2 IBM’s LF surrogate transformation strategy 18

INSTALLATION4 Installing the ARCAD-Transformer DB Eclipse plug-in 204.1 Prerequisites 204.2 Installing 204.3 Updating 214.4 Uninstalling 22

GETTING STARTED5 Overview of the ARCAD-Transformer DB perspective 255.1 Accessing the ARCAD-Transformer DB perspective 255.2 The Transformer DB Explorer 255.3 The Conversion Projects view 265.4 The Component Repository view 265.5 The Transformation Process view 275.5.1 The DDS File Conversion List view 27

5.5.2 The Conversion Audit: Aggregated Results view 28

5.5.3 The Engine Execution view 28

5.5.4 The Conversion Validation view 28

5.6 The Renaming Fields view 29

CONFIGURATION6 Configuring the ARCAD-Transformer DB perspective 316.1 Define the number of files to display in a conversion list 316.2 Define the default macro to propagate files in a conversion list 31



ARCAD-Transformer DB v13.1User Guide | Contents

7 Configuring the ARCAD-Check Data Integrity default parameters 33

SETTING UP THE TRANSFORMATION PROCESS

8 Working with conversion projects 378.1 Accessing the Conversion Projects view 378.2Overview of conversion projects 388.3 Creating new conversion projects 418.4 Duplicating existing projects 418.5 Modifying conversion projects 428.5.1 Prompt the ACVTSQLPRJ command 43

8.6 Accessing a project's conversion list 438.7 Accessing a project's aggregated audit 438.8 Accessing the list of dependent components affected by transformation 448.9 Validating a project's transformation(s) 448.10 Clearing the contents of a conversion project 458.11 Deleting conversion projects 45

9 Working with conversion lists 469.1 Accessing the DDS File Conversion List view 469.2Overview of DDS file conversion lists 479.3 Adding DDS files to a conversion list 519.4 Holding and releasing files 519.5 Launching integrity checks 529.6 Executing the transformation process 529.7 Viewing a file's current source code 529.8 Viewing a file's simulated transformed source code 539.9 Managing the audit of an individual file 539.10 Viewing a file's primary keys 549.11 Viewing a file's database links 559.12 Removing a file from a conversion list 55

10 Verifying data integrity 5610.1 Accessing data integrity checks in ARCAD-Transformer DB 5710.2 Auditing data integrity 5810.3 Auditing journal integrity 5910.4 Auditing relationship integrity 6010.5 Accessing the job execution monitoring view 6110.6 Viewing audit results (reports) 61

MANAGING CHANGES

11 Simulating transformations 6411.1 Transforming single files 6511.2 Transforming multiple files 6511.3 Transforming en-mass (all files) 6511.4 Steps to complete after transformation 66



ARCAD-Transformer DB v13.1Contents | User Guide

12 Resolving problems prior to transformation (conversion audit) 6712.1 Accessing the Conversion Audit - Aggregated Results view 6712.2Overview of the Conversion Audit view 6812.3 Resolving problems with primary keys 6912.3.1 Resolve non-unique primary key problems (PF_KEY1) 70

12.3.2 Create keys in SQL for DDS files without keys (PF_KEY2) 70

12.3.3 Create keys in SQL for DDS files with keys incompatible with SQL (PF_KEY3) 71

12.4 Resolving problems with multi-member files 7212.5 Imposing or removing attributes 72

13 Changing or adding field names 7413.1 Preparing files to rename fields 7413.2Overview of the renaming fields view 7513.3 Renaming short names (*NAME zones) 7613.3.1 Accept proposed new short names 77

13.3.2 Create new short namesmanually 77

13.4 Renaming long names (*ALIAS zones) 7813.4.1 Accept proposed new long names 78

13.4.2 Create new long namesmanually 78

13.5 Confirming that a file's fields have been renamed 79

14 Managing changes required for dependent components 8014.1 Reviewing the details of the changes required for dependents 8014.1.1 Overview of the Modifications to Impacted Dependent Components view 81

14.1.2 Viewing the details of the changes to dependent components 82

14.2 Applying the changes required for dependent components 8314.2.1 Accessing the Engine Execution view 84

14.2.2 Launching the engines 84

FINALIZING THE TRANSFORMATION PROCESS

15 Validating transformations 8715.1 Accessing the Conversion Validation view 8715.2Overview of the Conversion Validation view 8815.3 Attaching maintenance reports to validated conversion projects 8915.4 Validating the DDS to SQL transformations 9015.5 Validating the changes to dependent components 9015.6 Verifying the transformations in the target version 91

APPENDICESThe ACVTDDSSQL command 93

The ACHKFILDTA and ACHKDBRFLD commands 103

List of diagnostic messages 117

Glossary 119

F.A.Q. 125



ARCAD-Transformer DB v13.1User Guide | Tables

Tables

Table 1: Contact ARCAD 3Table 2: Related documentation 4Table 3: ARCAD-Transformer DB User Guide publication record 4Table 4: Validity Check Execution Information Parameters 34Table 5: Validity Check Temporary List Cleanup parameters 35Table 6: The ACVTSQLPRJ command parameters (conversion project properties) 38Table 7: Options to clear a conversion project 45Table 8: Parameters for individual files to transform 48Table 9: Individual file audit report 54Table 10: Fields view: common information 76Table 11: Fields view: renaming short names 76Table 12: Fields view: renaming long names 78Table 13: Description of the list of dependents impacted by transformation 81Table 14: Description of the line-by-line details in the Transformer Entry Details view 82Table 15: Description of the list of files to validate 88Table 16: The ACVTDDSSQL command parameters (Conversion Process properties) 93Table 17: The ACHKFILDTA and ACHKDBRFLD common parameters 103Table 18: The ACHKFILDTA and ACHKDBRFLD *JRNmode parameters 115Table 19: The ACHKDBRFLD-specific parameters 116



ARCAD-Transformer DB v13.1Figures | User Guide

Figures

Figure 1: ARCAD-Transformer DB in the ARCAD Group product suite 11Figure 2: The LF surrogatemodernization strategy 18Figure 3: The Transformer DB Explorer view 26Figure 4: The application Component Repository view 27Figure 5: General preferences 31Figure 6: Rename fields preferences 32Figure 7: ARCAD-Check Data Integrity preferences 33Figure 8: Access the Conversion Projects view 38Figure 9: The DDS File Conversion List 47Figure 10: Launching the transformation from the conversion list 52Figure 11: Audit messages for an individual file 54Figure 12: Accessing the data integrity check options (conversion list) 57Figure 13: Accessing the data integrity check options (component repository) 58Figure 14: The Command Execution Information view 61Figure 15: The data integrity report 62Figure 16: Launching the Transformation Process 65Figure 17: Accessing the Conversion Audit - Aggregated Results view 68Figure 18: Accessing user actions in the Conversion Audit view 69Figure 19: Analyze the cross references in DDS files before renaming fields 75Figure 20: The Fields view 76Figure 21: Manually remove the invalid question mark character from a suggested new name 77Figure 22: Accessing theModifications to impacted dependent components view 80Figure 23: Accessing the Engine Execution view 84Figure 24: Example of an engine in progress 85Figure 25: Accessing the Conversion Validation view 88Figure 26: Validating the conversion of DDS files to SQL 90



INTRODUCTION

ARCAD-Transformer DB v13.11 About ARCAD-Transformer DB | User Guide

1 About ARCAD-Transformer DB

Modernize your database and convert to SQL

ARCAD-Transformer DB is a solution included in the ARCAD product suite that helps IBM i DB2Relational DatabaseManagement System users transform DDS files (PF/LF) into SQL scripts(TABLE//INDEX), so as to benefit from the advantages of SQL standards and the DB engine integratedin the OS. This tool brings productivity and automation to the databasemodernization processallowing you to convert en-mass and/or piece-by-piece. The solution compiles associated RPGprograms as well as data.

Database transformation primarily applies to two fields: DDS files into SQL scripts, with automaticconversions of other components (such as DSPF/PRTFs and programs) to resolve themain problemsarising from this conversion.

Conversion projects store all of the applications the necessary for a DB conversion projects, such as:

l the default values for the DDS-to-SQL conversion command,l renamed fields,l themodification version (the target may change in the course of the project, as the DDSconversion may be performed in several steps),

l information for the environment used concerning data integrity and validation.

Many conversion projects may coexist at the same time, either for different applications, or transformdifferent files in the same application.

A working library is generated for each conversion project (library named and created with the project).It is used to store the various files needed for the transformation, including a job list of files impacted bythe project and the SQL source code of the converted files prior to validation.

ARCAD-Transformer DB is designed as a suite of tools, each of which handles a select database-modernization issue:

l Checking data integrityl Auditing transformation options (degree of automation)l Generating a guide to problem resolutionl Converting fromDDS to DDLl Renaming database fieldsl Validating future constraints

To further assist in databasemodernization, ARCAD-Transformer DB can be used in combination withthe ARCAD-Observer solution, for discovery and navigation of the existing database relationshipmodel.

Figure 1: ARCAD-Transformer DB in the ARCAD Group product suite



ARCAD-Transformer DB v13.1User Guide | 1 About ARCAD-Transformer DB

1.1 Business context

Whymodernize your DB2DataBase and convert DDS files to SQL files?

l Technical reasons: your DB2 is integrated into IBM il Performance: SQL is more efficient and immediately enhances program performance when yourvolume of data grows

l Wider and more powerful featuresl Data reliabilityl Simplified development, constraints in the same source code, etc.l Relational integrity and constraintsl Compatibility with all SQL databases and applications: enable external tools and applications toaccess data

l Recruitment: employees with SQL skills are easier to findl Development strategies (sustainability and scalability)l IBM is now focusing on SQL and is only maintaining DDS without introducing any evolutions

To complete themodernization of your applications and obtain themost value from your IBM i, havinga fully relational SQL database is a must. If you still have some data under DDS, you need toprogressively migrate to DDL, but this will impact not only data but also the source code of yourapplication. The objective is to modularize the source code towards amulti-tier application thatmodernizes RPG assets rather than discarding them, while improving overall performance via the use ofJava and SQL.

There aremultiple factors to consider when making the decision to progressively migrate your existingIBM i database into a full relational database. With ARCAD-Transformer DB, this conversion is as easyas 1,2,3.

To take advantage of the full power of the DB2 for i engine, modernize your existing databases bymigrating to a full relationalmodel.

l Standardize SQL language as the solemeans for accessing data.l Render the data architecture readable, including migration toward explicit field names and linksbetween tables.

l Delete a large part of the existing code (replaced by the natural protection offered by the databaseengine).

l Open up the database to update by all external tools and applications, with no integrity risk.

The objective is to modularize the source code towards amulti-tier application that modernizes RPGassets rather than discarding them, while improving overall performance via the use of Java and SQL. Inaddition to SQL conversion, ARCAD-Transformer DB automatically checks for data integrity, andidentifies the causes of any data corruption. It also automates the process of field renaming, to refactora legacy database in order to make use of new capabilities (such as usage of longer field names).

1.2 Functional description

ARCAD-Transformer DB is an Eclipse-based application that enables you to automate thetransformation of your IBM i application's PF, PF38, LF and LF38 files to TABLE and INDEX genericdatabase objects.



ARCAD-Transformer DB v13.11 About ARCAD-Transformer DB | User Guide

ARCAD-Transformer DB interacts seamlessly with the ARCAD Data Integrity Check function, offeringyou a way to verify the stability of your data and the links between your files before performing thetransformation process. This in addition to the automatic post-transformation audit(s) performed onyour files ensures that you will have total confidence in the quality of the transformation and theoutcome.

Transformations aremade outside of the active ARCAD-Repository. Live files are never manipulateduntil the final transformation is validated. The simulated transformations are carried out on copies ofyour repository files that ARCAD-Transformer DB creates in a separate working library.

1.3 Functional constraints

What are the potential problems to face when modernizing a DB2Database?

l Key attributes not supported in SQL (ABSVAL DESCEND DIGIT ZONE).l DDS physical file keys may not be unique.l Column attributes are not supported in SQL (EDTCDE, DATFMT, TIMEFMT, etc.).l PF used in CL commands (CLRPFM, CRTDUPOBJ, etc.).l Multi-member and multi-format files must be treated with care.l If default attribute values of DDS’ are different from those of TABLEs they may not convert.l Corrupted data in PFmay cause conversions to fail.l If a PF is transformed but its LF is not, the child LFwill be recompiled, not transformed into anindex.



ARCAD-Transformer DB v13.1User Guide | 2 Simplified concepts

2 Simplified concepts

After ensuring that your physical files are not active in a particular project or version, thetransformation process can begin.

The principal steps required to set up, execute, review and validate the DB evolution process must becarried out in the following order. Each step is performed in a different Eclipse view, which are allincluded in theARCAD-Transformer DB perspective.

1. Define the transformation parameters by creating conversion projects, which feed a targetARCAD version the final transformed files when they are validated.

Working with conversion projects on page 37

2. Select the PF/LF files to convert from the corresponding ARCAD application and add them tothe project's corresponding conversion list.

Working with conversion lists on page 46

3. Verify the integrity of the data and the links to be transformed.

Verifying data integrity on page 56

4. Execute the conversion simulation(s). This primary transformation is performed outside of thetarget version and is only a simulation. No final modifications have been made and no TABLE orINDEX files have been generated. The simulation is carried out in order to audit the files andensure they are valid and can be transformed.

Simulating transformations on page 64

5. Review the conversions' file-specific or aggregated audit which detect potential problems forthe conversion process, like impossibility to convert, problems concerning primary keys or multi-members files, and problems with attributes contained in files that are not compatible and cannotbe transformed into SQL sources. The audit checks the entire contents of your transformed filesand generates a report pointing to the corrupted records, organized by category. You mustmanually perform the actions required to resolve any problems that occurred during thetransformation simulation in order to ensure that the same problem is solved when the file isvalidated and the final transformation is carried out. This ensures the integrity of the datacontained in the transformed files.

Resolving problems prior to transformation (conversion audit) on page 67

6. Review and prepare the modifications required for the components dependent on themodified PFs or LFs. These interdependent components are automatically singled-out as beingconnected to the transformed files and therefore impacted by the changes made because theircross references must be updated. There are four engines, which must be run manually, that arededicated to preparing dependent components for the changes necessary.

Managing changes required for dependent components on page 80 and Changing or adding fieldnames on page 74

7. Validate the transformation of the PFs and LFs to TABLES and INDEXES and themodifications tothe dependents to transfer all of the transformed and/or modified files and components to anARCAD version and apply themodifications in the target version.



ARCAD-Transformer DB v13.12 Simplified concepts | User Guide

Verify that the old PF/LF component is ‘deleted’ and the new TABLE/INDEX component created bythe conversion process is ‘Type Chg./Src. File Chg’ in the target version components view. If all thisis true, you have successfully completed the transformation.

Validating transformations on page 87

The final, transformed files and their updated dependents are available in the version as checked-outfiles. Use ARCAD-Skipper to finalize the process and check the files into the repository.

ReferenceFor more information about the different views which enable you toperform all of the above, refer to Overview of the ARCAD-TransformerDB perspective on page 25.



ARCAD-Transformer DB v13.1User Guide | 3 About transformation strategies

3 About transformation strategies

There are two different ways to modernize your database. You can either partially transform yourDB using LF surrogates or fully transform it using ARCAD-Transformer DB. Decide if full or surrogatetransformations, or a combination of the two are best for your company and when to use ARCAD-Transformer DB or transformmanually.

Typical advantages of transforming manually are:

l No investment in a new software solution.

Encountered drawbacks are:

l It is necessary to master SQL and DDL language in particular.l It is necessary to comprehend all the potential problems encountered when modernizing a DB2database.

l A large investment in terms of resources.l No guaranties that conversions are standardized.

This method to modernize a DB2 database can only be used on a very small scale. Furthermore, thissolution is not as inexpensive as it seems, especially in terms of man-power.

Typical advantages of transforming with a dedicated tool, such as ARCAD-Transformer DB are:

l Low investment in terms of resources.l The potential problems encountered when modernizing a DB2 database aremastered.l Standardized conversions are guaranteed.l The integrity of data is analyzed beforehand to detect the corrupted recordings (and thecorrupting programs). The analysis can be done by another team (exploitation, etc.) andscheduled.

l The integrity of data is analyzed to set up the repository integrity beforehand.

This method to modernize a DB2 database is perfectly adapted to carry out a complete transformationof a DB2 database project, in one run or step by step (functional areas, etc.).

ReferenceFor more information about IBM’s modernization strategies, refer tothe ARCAD-Transformer DB Best Practices Guide. This document onlydescribes how to transform using ARCAD’s full-conversion strategy.

3.1 ARCAD’s full-conversion transformation strategy

The full-conversion modernization strategy from ARCAD replaces almost all physical files with TABLES,and logical files with INDEXES. It accomplishes this by transforming the characteristic properties of DDSthat are usually incompatible with DDL to SQL conversion. Examples of the elements that ARCAD-Transformer DB can convert, and how it accomplishes these otherwise “impossible conversions” are:

l If a PF does not have a unique key, ARCAD-Transformer DB creates an identifier in the TABLE.l If a PF or LF has FCFO, FIFO and LIFO key attributes which are not supported in SQL andtherefore cannot be converted, only the LF in conserved or the PF is transformed into aTABLE with an extra LF that contains the FCFO, FIFO and LIFO attributes.



ARCAD-Transformer DB v13.13 About transformation strategies | User Guide

l If there are DDS column attributes not supported in DDL, ARCAD-Transformer DB imports theminto the DSPF/PRTF.

l If there aremulti-member files, ARCAD-Transformer DB adds an extra zone to the TABLE todefine themember.

These constraints are clearly highlighted during the audit and require the user to manually choose howto proceed. Then, these choices will be processed by the engines.

ReferenceFor more information about the engines, refer tothe ARCAD-Transformer DB Best Practices Guide.

Typical advantages of this method are:

l The possibility to input long names for fields that will be used when converting PF in TABLE.l Converting all PF into TABLE, including work files (FORMAT keyword), except multi-format files;handling the issues of total conversion.

l Converting almost all the LF into INDEX, with the same format than the related PF; handling theissues of total conversion.

l Converting LFwith a different format than its related PF into INDEX, handling the issues of totalconversion.

l Suggestions to keep the default DDS attributes values of the PF that are different from those ofTABLES or those defined by CRTPF or CHGPF including the one for suppressed recordings (in caseof LIFO, FIFO, etc.).

l Exhaustive suggestions of modifications for the other affected components, when a totalconversion is impossible: key attributes not supported in SQL, when a key is not unique, columnattributes nor supported in SQL.

l Showing affected items by themodification of other components in case of conversion of multi-members PF into TABLE and for the PF used in CL commands (CLRPFM, CRTDUPOBJ, etc.).

l Converting into an ARCAD-Skipper version that bring its solutions in terms of recompilingmodified objects and objects affected by thesemodifications.

Encountered drawbacks are:

l It is necessary to validate the propositions of modifications on the other affected components,when a total conversion is impossible.

l It is necessary to modify the other components based on the propositions made for the affecteditems, when converting multi-members PF into TABLE.

This strategy is a solution for a complete transformation of the DB2 database. It corresponds to thephase 1 of modernization.

Phase 2 is the set up of a data logic (views, triggers, etc.) and an access to data (stored procedures) toisolate the database from the business logic and the UI (service programs).

Phase 3 is the set up of referential integrity (performed by the ARCAD-Observer DB part of thesolution).



ARCAD-Transformer DB v13.1User Guide | 3 About transformation strategies

3.2 IBM’s LF surrogate transformation strategy

The LF surrogate transformation strategy was created by IBM. This strategy replaces physical files withtables, keeping the original format level identifier thanks to an LF surrogate.

Figure 2: The LF surrogate modernization strategy

Typical advantages of this method are:

l No programs aremodifiedl Deleted recordings are eliminatedl Programs are not recompiled

Some drawbacks for this method are:

l increased maintenance of sources, with a consequent amount of them being duplicated,l the format level identifier of the LF surrogatemay sometimes differ from that of the PF,l processes using LIFO, FIFO, etc. file types are impossible to transform because deleted recordingsare eliminated, and

l exclusively converting items that are not potentially problematic such, as work files (FORMATkeyword), becomes necessary even if no programs aremodified.

This method is a minimalist solution for DB2 databasemodernization. It is only a temporary solutionthat provides minimalmodernization with little maintainability, in order to meet the needs of externalapplications.



INSTALLATION

ARCAD-Transformer DB v13.1User Guide | 4 Installing the ARCAD-Transformer DB Eclipse plug-in

4 Installing the ARCAD-Transformer DB Eclipse plug-in

Chapter summary4.1 Prerequisites 204.2 Installing 204.3 Updating 214.4 Uninstalling 22

ARCAD-Transformer DB is an Eclipse plug-in that can be installed on RDi. It is installed via the ARCAD-RDi plug-ins standard installation package.

4.1 Prerequisites

In order to use the transformation tools provided in the ARCAD-Transformer DB perspective, you musthave active licenses for the ARCAD Server and ARCAD-Transformer DB.

The contents of your existing IBM i server(s) must be loaded into a development environment inARCAD-Skipper. Create a version to use for the transformation project.

NoteIt is recommended that you perform a complete analysis of yourexisting database using ARCAD-Observer in order to repair any brokenconnections. Broken references can create problems if they are notfound and fixed before transformation.

ReferenceFor more information about this, refer to the ARCAD-Skipper, ARCAD-Observer and the ARCAD-Repository documentation.

4.2 Installing

Follow the subsequent steps to install the ARCAD-Transformer DB plug-in(s).

Step 1 Download the installation package to your Local Site Repository. ARCAD delivers Eclipse plug-in packages in a .zip file. Save this .zip to your local environment. This location is the local siterepository.

NoteThe PC on which your Eclipse tool is installed must be able toaccess this location. It is recommended to save the installationfiles on the same PC or a shared network that the PC isconnected to. There is no need to unzip this file after you saveit to your local environment.



ARCAD-Transformer DB v13.14 Installing the ARCAD-Transformer DB Eclipse plug-in | User Guide

After installation, it is recommend that you keep thislocation. Eclipse will continue to recognize it, so when updatesare available, you can copy them into this folder.

Step 2 From theHelpmenu of the Eclipse IDE, select Install New Software.

Important!You must be logged in as an administrator.

Step 3 From the Install dialog, click theAdd button.

Step 4 In theAdd Repository dialog, enter a recognizable name, then clickArchive... This creates alink to the Local Site Repository that you can come back to and that will be used for automaticupdates.

Step 5 Navigate to and select the ARCAD plug-ins installation .zip file that you saved to your localenvironment. ClickOK.

Result The Location field in theAdd Repository dialog is set to the .zip file's path. You canadd new versions to this path later to update.

ClickOK.

Step 6 Select the plug-in(s) to install.

ClickNext > to continue.

Step 7 Review the selected features in the Install Details dialog.


Step 8 Review and accept the license agreement

The License Agreement page presents the ARCAD license agreement for you to review.Please read it carefully.

When you have reviewed the agreement, select I accept the terms of the licenseagreements.

Step 9 Review and confirm the trusted certificates.

ClickOK.

Step 10 Click the Finish button to launch the installation.

Step 11 Restart the workbench. Click Yes to restart.

Result ARCAD-Transformer DB is installed and available for use.

4.3 Updating

Updating ARCAD plug-ins is similar to the original installation process. The prerequisites are the sameand you must already have a previous version of the plug-in installed.

NoteWhen there is a major upgrade (as opposed to a simple cumulativepatch) or a name change in one of the ARCAD plug-ins, then it is



ARCAD-Transformer DB v13.1User Guide | 4 Installing the ARCAD-Transformer DB Eclipse plug-in

recommended to uninstall the current plug-in and restart your platformbefore installing the new plug-ins.

Upgrading ARCAD plug-ins only works correctly when the names of theinstallation files have not changed.

NoteIf you try to re-install plug-ins instead of search for updates, as long asthe correct .zip archive is selected, the plug-ins will update instead ofreinstall. However, it is suggested to follow the following procedure toupdate plug-ins.

Follow the subsequent steps to update the ARCAD-Transformer DB plug-in(s).

Step 1 Save the new version of the installation .zip in your Local Site repository (created when you firstinstalled the plug-ins).

Step 2 From theHelpmenu of the Eclipse IDE, select Check for Updates.


Step 3 TheAvailable Updates dialog displays all of the plug-ins found in your update location thatare out of date. Select the plug-in(s) to update.


Step 4 Review and confirm the updates.


Step 5 Review and accept the license agreement

The License Agreement page presents the ARCAD license agreement for you to review.Please read it carefully.

When you have reviewed the agreement, select I accept the terms of the licenseagreements.

Step 6 Review and confirm the trusted certificates.

ClickOK.

Step 7 Click the Finish button to launch the installation.

Step 8 Restart the workbench. Click Yes to restart.

Result ARCAD-Transformer DB is installed and available for use.

4.4 Uninstalling

When there is a major upgrade (as opposed to a simple cumulative patch) or a name change in one ofthe ARCAD plug-ins, then it is recommended to uninstall the current plug-in(s) and restart yourplatform before installing the new plug-in(s).

Follow the subsequent steps to uninstall the ARCAD-Transformer DB plug-in(s).

Step 1 From theHelpmenu of the Eclipse IDE, select Installation Details.



ARCAD-Transformer DB v13.14 Installing the ARCAD-Transformer DB Eclipse plug-in | User Guide


Step 2 Click theWhat is already installed link in the lower right-hand corner of the Install dialog.

Step 3 Select the plug-in(s) to remove and click theUninstall button.

Step 4 Click Finish to confirm.

Step 5 Restart the workbench.

Result The selected plug-in(s) is/are uninstalled.



GETTING STARTED

ARCAD-Transformer DB v13.15 Overview of the ARCAD-Transformer DB perspective | User Guide

5 Overview of the ARCAD-Transformer DBperspective

ARCAD-Transformer DB is an Eclipse plug-in available for RDi and RTC, and pre-packaged in theARCAD-Client RCP. No matter what Eclipse platform you use, the plug-in provides access to theARCAD-Transformer DB perspective.

The ARCAD-Transformer DB perspective contains all of the different views that enable you toorganize and carry out your DDS to SQL transformations.

A perspective defines the initial set and layout of views in the workbench window. Within the window,each perspective shares the same set of editors. Each perspective provides a set of capabilities aimed ataccomplishing a specific type of task or working with specific types of resources. For example, theJavaTM perspective combines views that you would commonly use while editing Java source files, whilethe Debug perspective contains views that you would use while debugging a program. Perspectivescontain views and editors and control what appears in certain menus and tool bars.

Views in ARCAD-Transformer DB are context sensitive. To see a view that is not currently active, open itby accessing the Show View dialog (Window > Show view > Other) and selecting the view. Re-positionviews by dragging and dropping them to the desired location in the studio. Click an edge and drag tore-size a view. Double-click on any view's toolbar to maximize it. This is helpful when a view contains alot of information; maximizing the viewmakes it fill the entire window. Double-click again to minimizethe view.

To re-set the perspective to the default layout, clickWindow > Reset Perspective.

5.1 Accessing the ARCAD-Transformer DB perspective

Follow the subsequent steps to open the ARCAD-Transformer DB perspective in RDi.

Step 1 Click onWindow>Open Perspective and selectOther… in themenu. Select the ARCAD-Transformer DB perspective in theOpen Perspective dialog and clickOK.

Result The ARCAD-Transformer DB perspective is displayed.

5.2 The Transformer DB Explorer

This primary view provides access to all of the applications available on the current IBM i server(s)running the ARCAD repositories. Themenus available in the view are also available in other ARCADproducts, except for the ARCAD-Transformer DB-specific Conversion Projectsmenus.



ARCAD-Transformer DB v13.1User Guide | 5 Overview of the ARCAD-Transformer DB perspective

Figure 3: The Transformer DB Explorer view

5.3 The Conversion Projects view

Manage conversion projects

Define, view and manage conversion projects in this view. Conversion projects can be accessed fromthree levels:

1. from the IBM i server - this list displays all of the projects available for all of the applications on theserver.

2. from each application - this list displays all of the projects available for the current application.

3. from each version - nested in each active version, in the Environments menu, this list displaysall of the projects available for each individual version.

ReferenceFor more information about using this view, refer to Working withconversion projects on page 37.

5.4 The Component Repository view

Add the files to transform to a conversion list




Figure 4: The application Component Repository view

This view lists the DDS files in your application and enables you to load some or all of them into aconversion list. By default, this view displays only the convertible PF, LF, PF38 and LF38 files available inthe selected application.

As a precursor to transformation, use the ARCAD-Observer and ARCAD-Audit tools available in thisview to check the entire contents of your files and generate a report pointing to corrupted records.

Right-click on a component and select Add to conversion list to select an existing list.

Click the Select the target conversion project icon in the toolbar to select the default list to which toadd any component in the repository whenever they are selected and added to a conversion list.

ReferenceFor more information about using this view, refer to Working withconversion lists on page 46.

5.5 The Transformation Process view

There are four tabs included in this viewwhich each, in turn, are required during the transformationprocess.

5.5.1 The DDS File Conversion List view

Execute the DDS to SQL transformation process

This view enables you to manage, edit and generate the conversion simulation for the source PF/LF files(unitary or mass conversions) as well as view the suggested conversion results and access the file-specific audit report after transformation.



ARCAD-Transformer DB v13.1User Guide | 5 Overview of the ARCAD-Transformer DB perspective

ReferenceFor more information about using this view, refer to Working withconversion lists on page 46 and Simulating transformations onpage 64.

5.5.2 The Conversion Audit: Aggregated Results view

Review and verify the conversion results

This view enables you to view and manage the aggregated audit report for all of the transformationscarried out for a conversion project. All of the errors encountered during transformation for each fileconverted are compiled in this list. You can carry out the actions required to fix any issues that requireattention before validating the transformation from this view also.

ReferenceFor more information about the various problems that can be resolvedafter transformation, refer to Resolving problems prior totransformation (conversion audit) on page 67.

5.5.3 The Engine Execution view

Apply modifications to dependent components

When components are transformed, their active dependents often need to be updated also. The impacton these "other" components is analyzed automatically by ARCAD-Transformer DB. The changes to thedependent components aremade automatically when the engine dedicated to the problem detected ismanually launched. Launch the engines to prepare the dependents for modification from this view.

ReferenceFor more information about managing changes necessary forassociated components impacted by transformation, refer to Managingchanges required for dependent components on page 80.

5.5.4 The Conversion Validation view

Validate and check out the transformed files into a version

In order for the transformed files created during the conversion process to be available in a targetARCAD version, they must be validated. Validating an individual file or an entire list of converted fileschecks out the converted files into the ARCAD version.

ReferenceFor more information about checking out the finalized transformedfiles into an ARCAD version, refer to Validating transformations onpage 87.




5.6 The Renaming Fields view

Change field names

This view enables you to modify the values of DDS short names in order to reorganize or improve thelegibility of your DB's column names. Additionally, you can convert and modify the values of DDSaliases into SQL long names or create new long names for each of your database files.

ReferenceFor more information about changing field names, refer to Changing oradding field names on page 74.



CONFIGURATION

ARCAD-Transformer DB v13.16 Configuring the ARCAD-Transformer DB perspective | User Guide

6 Configuring the ARCAD-Transformer DBperspective

The default parameters for certain features in ARCAD-Transformer DB can be configured in thePreferences window (Window > Preferences).

6.1 Define the number of files to display in a conversion list

The default number of files to display in a conversion list is 99,999. If your list contains a lot of files, itmay load slowly. Change themaximum number of files allowed before breaking the list into pages intheARCAD-Transformer DB preference.

Figure 5: General preferences

6.2 Define the default macro to propagate files in a conversion list

The default macro to propagate a file, check cross-references and propose new short and long fieldnames is defined in the Field Renaming section under theARCAD-Transformer Renaming Toolspreference.



ARCAD-Transformer DB v13.1User Guide | 6 Configuring the ARCAD-Transformer DB perspective

Figure 6: Rename fields preferences



ARCAD-Transformer DB v13.17 Configuring the ARCAD-Check Data Integrity default parameters | User Guide

7 Configuring the ARCAD-Check Data Integritydefault parameters

Before using the ARCAD Data Integrity Check options, it is recommended to configure the defaultparameters.

ReferenceFor more information about each of the parameters described below,refer to the appendix: The ACHKFILDTA and ACHKDBRFLDcommands on page 103.

Step 1 Open the RDi Preferences (Window > Preferences).

Step 2 Expand theARCAD-Check Data Integrity Constraint Commands category.

There are a number of sub-categories that each contain different groups of parameters whichcan all be found in the Check data integrity execution dialog or in the Check dataconstraint execution dialog.

Figure 7: ARCAD-Check Data Integrity preferences

Constraints Validity Analysis Command parameters

ReferenceFor more information about these parameters, refer toTable 19: TheACHKDBRFLD-specific parameters.

Data Validity Command Execution parameters > Description and Basic parameters

ReferenceFor more information about these parameters, refer to the Generalparameters.



ARCAD-Transformer DB v13.1User Guide | 7 Configuring the ARCAD-Check Data Integrity default parameters

Data Validity Command Execution parameters > Libraries parameters

ReferenceFor more information about these parameters, refer to theEnvironment Origin (ENV) and Libraries parameters.

Data Validity Command Execution parameters > Mode and Site parameters

ReferenceFor more information about these parameters, refer to the Site (SITE)and Execution Mode (MODE) parameters.

Data Validity Command Execution parameters > Batch-Mode Preparation parameters

ReferenceFor more information about these parameters, refer to the Batch ModePreparation Attribute Parameters (SBMATTR).

Data Validity Command Execution parameters > Receive Batch parametersOnly available if the Site (SITE) parameter is NOT set to *LOCAL.

ReferenceFor more information about these parameters, refer to the Batchparameters for receiving from remote execution (RCVSBMATTR).

Data Validity Command Execution parameters > Remote Batch parametersOnly available if the Site (SITE) parameter is NOT set to *LOCAL.

ReferenceFor more information about these parameters, refer to the Preparationmacro group parameters (PRPMACRO), the Remotemacro groupparameters (RMTMACRO) and the Batch Parameters for remoteexecution (RMTSBMATTR).

Job execution informationThe Execution Information view displays the active or recently completed Integrity Check commands.The following table includes a brief explanation of each of the parameters concerning this view forwhich you can set a default value.

Parameter Description

Refresh Delay Define the delay before starting the automatic refresh of job executioninformation.

Refresh Period Define the length of time between two job execution information refreshes.

Period beforecurrent date

Define the amount of time, in minutes, to subtract from the current date to startthe job execution information selection.

Table 4: Validity Check Execution Information Parameters

Start/End Journal Log Date parameters

ReferenceFor more information about these parameters, refer toTable 18: TheACHKFILDTA and ACHKDBRFLD *JRNmode parameters.



ARCAD-Transformer DB v13.17 Configuring the ARCAD-Check Data Integrity default parameters | User Guide

Temporary list cleanupIf the commands apply to a selection of multiple files or constraints, the check is not performed directlyto the files but on a dynamically-created temporary list of the files, in order to improve the executionefficiency. The following table includes a brief explanation of each of the parameters concerning thistemporary table for which you can set a default value.

Parameter Description

Delete List

Tick this checkbox to activate the automatic deletion of the temporary listcreated when multiple files are selected for a validity check.

Warning!DO NOT set the clean up if you have checksscheduled in the future!

Delay beforecleanup

Define the time, in milliseconds, before the clean up is launched if the Delete Listcheckbox is ticked. The default is 300,000 milliseconds (5 minutes).Table 5: Validity Check Temporary List Cleanup parameters



SETTING UP THETRANSFORMATION

PROCESS

ARCAD-Transformer DB v13.18 Working with conversion projects | User Guide

8 Working with conversion projects

Chapter summary8.1 Accessing the Conversion Projects view 378.2Overview of conversion projects 388.3 Creating new conversion projects 418.4 Duplicating existing projects 418.5 Modifying conversion projects 428.6 Accessing a project's conversion list 438.7 Accessing a project's aggregated audit 438.8 Accessing the list of dependent components affected by transformation 448.9 Validating a project's transformation(s) 448.10 Clearing the contents of a conversion project 458.11 Deleting conversion projects 45

A conversion project is a group of parameters and options assigned to a conversion list, which containsthe PF and/or LF files to transform. It is the visual representation of the ACVTSQLPRJ command, whichcreates or modifies a conversion project.

conversion projects must bemanually defined and files must bemanually added to their conversionlists in order to carry out a single-file or mass conversion. Files cannot be transformed unless they arepart of a project's conversion list. Conversion projects must be assigned a specific parent application,environment and target version.

When the simulated transformations are approved and all of the issues encountered duringtransformation are resolved, the conversion process must be validated to check out the new source filesinto the defined ARCAD version.

An IBM i library attached to the project contains the results of the conversion process: the SQL sourceproduced during transformation and the list of modifications to the other components impacted by theconversion.

The Conversion Projects view displays the already-defined projects to which you can add files totransform.

8.1 Accessing the Conversion Projects view

There are three access points to the Conversion Project view. They are all in the TransformerDB Explorer. Each access point automatically filters the projects displayed in the viewwhen it is openeddepending on the location you opened it from.

1. from the IBM i server - this list displays all of the projects available for all of the applications on theserver.

2. from each application - this list displays all of the projects available for the current application.

3. from each version - nested in each active version, in the Environments menu, this list displaysall of the projects available for each individual version.



ARCAD-Transformer DB v13.1User Guide | 8 Working with conversion projects

Figure 8: Access the Conversion Projects view

Right-click on a project to display the context menu. The options available in the context menu for eachproject are described below.

8.2 Overview of conversion projects

Each column in the Conversion Projects view represents the value for each of the parameters,included in the ACVTSQLPRJ command, defined when the project was created. Some of theseparameters are called into action when the ACVTDDSSQL command is launched.

The following table includes a brief explanation of these parameters.

ReferenceFor more information about the conversion command, refer to theappendix: The ACVTDDSSQL command on page 93.

Field (command) Description

*Project Code(CVTSQLPRJ)

The unique name of the project.

Important!A project's codemust be unique for the currentserver. No two applications can contain projectswith the same name.

Name your project(s) carefully. You cannotchange the name of a project after it is created.

Action (ACTION)

This value is determined automatically according to the action taken to open theManaging Conversion Projectswizard:

l *CRTcreate a new or duplicate an existing conversion project.

l *CHGedit an existing conversion project.

l *DLTTable 6: The ACVTSQLPRJ command parameters (conversion project properties)





delete a conversion project.

l *CLRclear the contents of a conversion project.

l *CHKcheck that the project exists.

*Description(TEXT) The description of the project.

*Application ID(TOENV)

Select the target application's code from the drop-down list.

If a new project was created from an application's or version's ConversionProject view, this value is prepopulated with the parent application.

*Environment ID(TOENV)

Select the target environment's ID from the drop-down list.

If a new project was created from a version's Conversion Project view, thisvalue is prepopulated with the version's parent environment.

*Version Number(TOENV)

Select the target ARCAD version into which to check out the transformed filesfrom the drop-down list.

If a new project was created from a version's Conversion Project view, thisvalue is prepopulated with that version.

*Working Library(WRKLIB)

Enter the destination for the transformed files.

This is the work library, whichmay or may not already exist in the same parentapplication fromwhich the DDS source files to transform come from, into whichthe new files created during transformation, which will contain the transformedcontent, should be saved.

The default value is *GEN which creates a generic library automatically.

*CurrentConversion List(CURLIST)

Enter the name of the conversion list associated with the project.

If the name of the list entered does not already exist, it will be created when theproject is saved.

The default list is LSTCVFILEwhich is created for you automatically.

*Source File(SRCFILE)

The TABLE/INDEX source file into which the new files, created duringtransformation, should be saved.

If the name of the source file entered does not already exist, it will be createdwhen the project is saved.

Warning messages(WNGMSG)

Import warning messages into the source (*YES), or not (*NO).

Thesemessages are stored in a file to be subsequently used for other conversionoperations. Specify whether you want thesemessages to also be inserted intothe SQL source.

Retrieve DDScomments(RTVDDSCMT)

Import DDS comments into the SQL source (*YES), or not (*NO).

Table 6: The ACVTSQLPRJ command parameters (conversion project properties)





Manage sharedformats (SHRFMT)

Manage shared formats (*YES), or not (*NO).

Some physical files share the format of another physical file (FORMAT keywordin the DDS). Specify if you want to convert the DDS from the shared format ordefine the fields explicitly in the SQL source.

Manage referencefields (REFFILE)

Manage the zone directory (*YES), or not (*NO).

Indicate whether to define the fields from their reference file, where specified. Ifnot, fields are defined directly in the SQL source instead of from the reference.

Keep CCSIDOptions(CCSIDOPT)

Conserve CCSID attributes (*YES), or not (*NO), or if the CCSID keywordshould only be added if it is different from the file (*NOTPF).

Remove QualifiedNames(RMVQUAL)

Remove all SQL object qualifications (library names) from the source (*YES), ornot (*NO).

Put File Labels(FILELABEL) Generate the FILE LABEL ON TABLE/INDEX instruction (*YES), or not (*NO).

Share Fmt. PF ifLF has same fields(LFSHRPFFMT)

Specify if you want to convert a logical file to an INDEX when it has a differentformat than the physical file.

Share the PF format, if the LF contains the same zones (*YES), or not (*NO).

l YESLogic files are converted. If a logical file has a different format than thephysical, but with exactly the same fields, unmodified, in the same order, itwill be converted to an INDEX. Conversion message: MSG4144 (LFconverted to INDEX are given a different format).

l NOIf a logical file has a different format name than the physical, even if thefields are exactly the same, not modified, in the same order, it will beconverted to INDEX without sharing the physical format. The physicalzones are added individually with the keyword “add”. The keyword“rcdfmt” is generated with the format of the LF. (LF zones are identical toPF, but the format is different).

ReferentialConstraints(REFCST)

Use the referential constraints created by ADDPFCST (*YES), or not (*NO).

Check Constraints(CHKCST) Use the check constraints created by ADDPFCST (*YES), or not (*NO).

Decimal Point(DECMPT)

Specify the character to use as the integer/decimal separator, if numeric literalsexist in the generated source. See in-line help for IBM command RUNSQLSTMfor more information.

Indicate the type of decimal separator.

l *PERIODl *COMMAl *JOB (use the format defined in the JOB)






l *SYSVAL (the system value)

Rename Fields(RNMFLD)

An additional benefit of the transformation process is that you can rename shortname fields and/or add long name fields. Indicate the type of renaming touse.*NO: No fields are renamed.*NAME: Only Short Names can berenamed.*ALIAS: Only Long Names can be renamed.*BOTH (names andaliases): Both Short and Long Names can be renamed.


8.3 Creating new conversion projects

Follow the subsequent steps to create a new conversion project.

Step 1 Either click the Create icon in the Conversion Project search view or right-click anywhere inthe view and select Create new conversion project to access theManaging ConversionProjectswizard.

Step 2 Define the project's parameters on the first two pages of the wizard.

ReferenceFor more information about the parameters for conversionprojects, refer to Table 6: The ACVTSQLPRJ commandparameters (conversion project properties).

Step 3 Click Finish to save the new project or clickNext > to prompt the ACVTSQLPRJ commandmanually.

ReferenceFor more information about manually running the command,refer to Working with conversion projects on page 37.

Step 4 When the project is created, you are automatically prompted to add all of the *FILE typecomponents included in the parent application's repository to the project's list

Click Yes to automatically populate your project orNo to do this manually later.

ReferenceFor more information about adding files to conversion lists,refer to Working with conversion lists on page 46.

Result The project is created and available in the Conversion Projects view.

8.4 Duplicating existing projects

Duplicating a conversion project is a quick way to apply an existing set of parameters to anotherconversion list or a different application.

Step 1 Right-click on the project to copy in the Conversion Project view and select Duplicateconversion project to access theManaging Conversion Projectswizard.




Step 2 Modify any of the original project’s parameters necessary. The name of the project mustchange in order to save the new project.

TheAction field is automatically changed to *CHG.

Important!The new project's Codemust bemodified because two projectscannot share the same code.


Step 3 Click Finish to save the new project or clickNext > to prompt the ACVTSQLPRJ commandmanually.


Step 4 When the project is created, you are automatically prompted to add all of the *FILE typecomponents included in the parent application's repository to the project's list

Click Yes to automatically populate your project orNo to do this manually later.

ReferenceFor more information about adding files to conversion lists,refer to Working with conversion lists on page 46.

Result The project is created and available in the Conversion Projects view.

8.5 Modifying conversion projects

Any value defined for a conversion project when it was created can bemodified. The samewizard isused to create a project is displayed when editing a project's parameters.

Follow the subsequent steps to edit a conversion project.

Step 1 Right-click on the project to modify in the Conversion Project view and select Updateconversion project to access theManaging Conversion Projectswizard.

Step 2 Modify any of the original parameters as necessary.

TheAction field is automatically changed to *CRT.


Step 3 Click Finish to save the updated project or clickNext > to prompt the ACVTSQLPRJ commandmanually.





Result The project is updated and available in the Conversion Projects view.

8.5.1 Prompt the ACVTSQLPRJ commandARCAD-Transformer DB offers a way to prompt and manipulate the ACVTSQLPRJ command similar to a5250 emulator. IBM i users will recognize the parameters in the command prompt menu. Prompting thecommand manually accomplishes the same task(s) as the wizard.

Follow the subsequent steps to prompt the command.

NoteValues entered in the command prompter are not stored aspreferences.

Step 1 From the third page of theManaging Conversion Projectswizard, click the Prompt thecommand button to display the RDi command prompter.

Step 2 Enter the conversion options.

The values displayed in the command prompter are those defined on the two first pages of thewizard.

Step 3 ClickOK to display the command string.

Step 4 Click Finish to execute this command.

Result Depending on the commands current action status, the results will vary but are always thesame as when theManage a Conversion Project wizard is used.

8.6 Accessing a project's conversion list

Every conversion project contains a conversion list. This list contains all of the IBM i sourced files (DDS)to transform.

To access the DDS File Conversion List view, right-click on the conversion project and selectOpen the transformation process view.

ReferenceFor more information about theDDS File Conversion List view, referto Working with conversion lists on page 46.

8.7 Accessing a project's aggregated audit

After transformation, every conversion project includes an audit report which displays all of theproblems encountered during transformation for each of the files in the project's conversion list. Theaggregated list of problems for all of the project's individual files is accessed from the Open thetransformation process view.A file-specific report can be accessed from the DDS File Conversion




List view.

To access the Conversion Audit: Aggregated Results view, right-click on the conversion projectand select Open the transformation process view.

ReferenceFor more information about aggregated conversion audits, refer toResolving problems prior to transformation (conversion audit) onpage 67.

For more information about managing the audit report for a single file,refer to Working with conversion lists on page 46.

8.8 Accessing the list of dependent components affected bytransformation

After transformation, the active dependencies of the DB files often need to be changed in order tomaintain valid cross references. This is especially true if you renamed fields during the transformationprocess. The impact on these "other" components is analyzed automatically by ARCAD-TransformerDB.

The changes proposed are displayed in the Engine Execution view. ARCAD-Transformer DBprovides IBM i-side engines that correspond to any issue that could be encountered aftertransformation between transformed files and their dependencies. Each enginemust be launched inorder to run it and modify the corresponding issues in the dependencies.

To access the list of dependencies affected by transformation, right-click on the conversion project andselect Open the transformation process view.

ReferenceFor more information about modifying dependencies, refer toManaging changes required for dependent components on page 80.

8.9 Validating a project's transformation(s)

When the transformations are approved and you are sure that the converted files reflect your modifieddatabases, you must validate the changes made to the PF/LF source files and all of their dependencies.Validating the transformations checks in themodified files into the ARCAD version selected in theparent conversion project.

Warning!It is not recommended to validate a project until you are sure all of theissues outlined in the audit are resolved and all of the engines thatmodify the dependencies are run.

ReferenceFor more information about carrying out these steps, refer to Resolvingproblems prior to transformation (conversion audit) on page 67 andManaging changes required for dependent components on page 80.




To access the Conversion Validation view, right-click on the conversion project and select Openthe transformation process view.

ReferenceFor more information about how to validate the transformations in aconversion project, refer to Validating transformations on page 87.

8.10 Clearing the contents of a conversion project

Clearing the contents of a project may be useful in order to reset it. Resetting the simulatedtransformations and any actions taken on the files in a project may be useful if you need to test someproblem resolutions in one setting and then others for a different context. Because all transformationsare only simulations until they are validated, projects can be reset and re-transformed as many times asyou need to confirm that the transformation will be successful.

Follow the subsequent steps to clear a conversion project.

Step 1 Right-click on the project to modify in the Conversion Project view and select Clearconversion project to access theManaging Conversion Projectswizard.

Step 2 Modify the Clear Option field to clear the project.


Audit Messages(*CVTMSG)

Clears only themessages of the conversion attempts in order to reinitialize theTransformation Audit results.

Proposed Changesfor OtherComponents(*FRMCHG)

Clears all the temporary data stored in the temporary library linked to theproject. This means clearing only themodifications proposed for a conversion(new TABLEs/INDEXs replacing PFs/LFs, new INDEX/LF corresponding to useractions, modifications propagated in components of other types, like DSPF,PRTF, RPG etc ...).

Both (*ALL) Clears all. This includes clearing everything mentioned above.Table 7: Options to clear a conversion project

Step 3 Click Finish to save themodified project or clickNext > to prompt the ACVTSQLPRJ commandmanually.


8.11 Deleting conversion projects

Warning!Deleted conversion projects cannot be accessed or recovered.

To delete a conversion project, right-click on it in the Conversion Project view and select Deleteconversion project.

ClickOK to confirm.



ARCAD-Transformer DB v13.1User Guide | 9 Working with conversion lists

9 Working with conversion lists

Chapter summary9.1 Accessing the DDS File Conversion List view 469.2Overview of DDS file conversion lists 479.3 Adding DDS files to a conversion list 519.4 Holding and releasing files 519.5 Launching integrity checks 529.6 Executing the transformation process 529.7 Viewing a file's current source code 529.8 Viewing a file's simulated transformed source code 539.9 Managing the audit of an individual file 539.10 Viewing a file's primary keys 549.11 Viewing a file's database links 559.12 Removing a file from a conversion list 55

Conversion lists are attached and unique to conversion projects. They include the IBM iPF/LF/PF38/LF38 members selected from the parent repository. The DDSmembers to transform aremanaged in this list and can be transformed individually or "en mass" in small groups or all at once.

The DDS File Conversion List view enables you to display and manage the DDSmembers intendedfor conversion. There are often tasks to carry out on individualmembers prior to and post thetransformation process, including managing the errors encountered during the simulation.

ReferenceFor more information about launching the transformation process,refer to Simulating transformations on page 64.

9.1 Accessing the DDS File Conversion List view

To access the DDS File Conversion List view for a specific conversion project, right-click the on theproject in the Conversion Projects view and select Open the transformation process view.



ARCAD-Transformer DB v13.19 Working with conversion lists | User Guide

Figure 9: The DDS File Conversion List

9.2 Overview of DDS file conversion lists

The DDS File Conversion List is separated into two sections:

1. The top half of the view lists all of the PF and/or LFmembers to convert. If there are a lot,click theMore... button to display the hidden members. The number of members to display in thelist by default is defined in the configuration settings (see Configuring the ARCAD-TransformerDB perspective on page 31).

l Members highlighted in magenta in a conversion list are currently checked out in the project'starget version.

Important!It is not recommended to validate the transformation onmembers highlighted in magenta!

When the transformation is validated, you risk overriding anychanges made to themember because themost recentversion of the transformed file overrides the previousversion.

If you must transform a checked out member, it isrecommended to check them back into the in the targetversion first.

l Locked components are currently checked out in other versions, not the conversion project'starget version.

Important!If these files with the are not checked in, the transformed filecannot be validated.




2. The bottom half of the view lists themessages attributed to each file after it is transformed.Double-clicking a file displays the warning message(s) attached to it. SeeWorking with conversionlists on page 46.

ReferenceFor a description of all of the audit messages, refer to the List ofdiagnosticmessages on page 117 in the appendix.

A number of the options available to carry out on individual files in a conversion list are common toother ARCAD products. Right-click on a file to display the context menu.

ReferenceThe options available in the context menu for each file that are specificto ARCAD-Transformer DB are described below.

For more information about the other options, refer to the ARCAD-Skipper or ARCAD-Observer documentation.

Each column in the DDS File Conversion List view represents a parameter to define or informationabout each file in the conversion list.

The following table includes a brief explanation of each file's parameters.

Important!Some options require you to fill in information about the transformedversion of the file, these fields are indicated in green text.

Column Description

Name The name of the DDSmember to convert to SQL.

Source Type The source DDSmember type (PF or LF).

Status

The DDSmember's current transformation status.

l blankThemember has not been converted yet.

l OKThemember was converted successfully at least once.

l *HLDThemember is held and actions for it are suspended.

l *ABNThe conversion process failed.

Description The description of the DDSmember.

Source Library The name of the DDSmember's source library.

Source File The name of the DDSmember's source file.

Creation Library The original DDSmember's compiled object library. The target library into whichthe result of the compilation of the original source file is placed.

Functional A detailed description of the DDSmember.Table 8: Parameters for individual files to transform




Column Description

Description

New Table longSQL name

Enter the new long name for the target table. Text entered here will be the newalias name for the SQL table created during transformation.

The text entered is validated automatically. If the text does not conform to therequirements for an SQL table long name, a warning dialog is displayed thatexplains which requirements were not followed. The new long name is preservedbut proceeded by "??" to indicate that it is invalid. Invalid long names are notsaved and are not applied to the transformed file upon validation.

If the new long name is valid, it is applied to the transformed file when thetransformation process is validated.

New table long names can bemodified at any time before the transformed file isvalidated.

Conversionmessage

If the DDSmember cannot be transformed, this field displays the text *NOT_SQL.

PF_KeyConversion Action

Sometimes, the conversion cannot set the key of the SQL TABLE identically tothe DDS PF key. This is the case when the DDS PF key is not unique or when thekeywords FCFO, FIFO or LIFO are used.

ReferenceRefer to the Action if PF key problem(PFKEYACT) command for more information.

Index/LF newName

If the option *LF/*INDEX is selected for the file, this field contains the name ofthe new LF/INDEX.

ReferenceRefer to the New file name to create (NEWFILE)command for more information.

Multi_MBRconversion action

Multi-members cannot exist in SQL.

ReferenceRefer to the Action if multiplemembers(MULTIMBACT) command in the appendix formore information.

NoteIf *MBRFLD is selected, the parameters for thiszone are defined in the columns with the prefixMulti_MBR.

Multi_MBR newfield name

The new field's name, if theMulti_MBR conversion action column's value is*MBRFLD.

ReferenceRefer to the Info new field for multi-mbrs(MULTIMBINF) command for more information.

Table 8: Parameters for individual files to transform




Column Description

Multi_MBR newfield type

The new field's type, if theMulti_MBR conversion action column's value is*MBRFLD.

Multi_MBR newfield length

The length of the new field, if theMulti_MBR conversion action column's valueis *MBRFLD.

Multi_MBR modelfield name

The name of the existing field that should serve as a template, if theMulti_MBRconversion action column's value is *MBRFLD.

Multi_MBR newfield long name

The new field's long name, if theMulti_MBR conversion action column's valueis *MBRFLD.

Multi_MBR newfield text

The new field's description, if theMulti_MBR conversion action column's valueis *MBRFLD.

Field RenamingData

The status for renaming the fields in the new, transformed file. This column isinformation-only - if the fields in the corresponding file have been changed, youcan right-click on the file and select Rename Fields, then Validate renamedfields to indicate that the task is finished.This status does not impact the renaming process in any way; it is only areminder that the fields in the file have been renamed.

l [blank]Field renaming is not finished or has not been started.

l ConfirmedField renaming is finished.

ReferenceRefer to Changing or adding field names onpage 74 for more information.

Attributes *FILEto impose

PF or LF files often contain specific IBM i attributes that cannot be converted inthe new SQL files. You must choose to either ignore or to impose theseattributes. Imposing an attribute forces it to be conserved and then applied tothe table or index after the transformation is complete.

This column contains the enumeration of the attributes that you must choose toimpose.

The commands specific to DDS, CRTPF, CRTLF, CHGPF, CHGLF file typesenable you to change a number of attributes for each PF or LF. These values donot necessarily correspond to the default values created when the SQL tables orindexes are generated during transformation and they cannot be saved duringthe conversion.

The%EXECA CHGPF/CHGLF FILE(&O/&N) instruction is added to the newsource file in addition to the list of attributes indicated which will modify theobject generated when the table is compiled.

ReferenceRefer to the *FILE attributes to impose(FILEATR) command for more information.

Conversion Date The date themember was most recently transformed.

Conversion Time The time at which themember was most recently transformed.Table 8: Parameters for individual files to transform




9.3 Adding DDS files to a conversion list

The conversion lists that are created automatically when a conversion project is created are empty. Totransform DDS files they must be included in a conversion list. The DDS files are found in theapplication component repository.

NoteIt is recommended to analyze the PF files' data integrity and theintegrity of their database links before transforming them. This can bedone before added files to a conversion list, or after.

ReferenceFor more information about data validity, refer to Verifying dataintegrity on page 56.

Follow the subsequent steps to add DDS files (PFs and LFs) to conversion lists.

Step 1 Click the Components menu under the Repository node to open the parentapplication's Application Component Repository.

Step 2 Select one or more files to add to a conversion list, right-click, then select Add to Conversionlist.

Step 3 If a conversion project is not selected on the global-level, select a pre-defined project from thedialog box. The files selected will be added to the list for that project.

If a conversion project has been defined on the global-level for the entire repository, theproject selection dialog will not display. The selected file(s) will be added directly to theconversion project selected on the global-level.

ReferenceFor more information about selecting a global-level conversionproject for your application's repository, refer to the AboutARCAD-Transformer DB on page 11.

Step 4 If no errors were encountered in the process, a confirmation dialog is displayed. ClickOK.

Result The selected files are added to the conversion list selected and can be accessed in the DDSFiles Conversion list view.

9.4 Holding and releasing files

To prevent a file from being affected by an action carried out on the entire list of files in a conversionlist, "hold" it. Held files are not impacted by any action taken on the list. To remove the hold from a file,release it. This may be useful if you want to execute the transformation process on a very long list offiles but exclude a few.

Suspend the actions carried out on selected files by right-clicking, then selecting Hold File. When afile is held, its status is set to HLD.

Release held files by selecting them, right-clicking, then selecting Release File.




9.5 Launching integrity checks

Integrity checks for a file's data or its constraints can be launched from the conversion list by right-clicking on the file and selecting Data Integrity then Check Data Integrity or Audit journalintegrity.

ReferenceFor more information about data validity, refer to Verifying dataintegrity on page 56.

9.6 Executing the transformation process

The transformation process can be carried out on single files, a group of selected files or all of the files ina conversion list.

Figure 10: Launching the transformation from the conversion list

l To transform a single file, select it, right-click, then select Convert to SQL.l To transform a group of files in a conversion list, select them all (Ctrl+click), right-click then select

Convert to SQL. Click Yes in the dialog that opens to confirm and launch the transformationfor the selected files.

l To transform all of the files in a Conversion list, click the ACVTDDSSQL: convert the list fromDDS to SQL icon.

ReferenceFor more information about the transformation process, refer toSimulating transformations on page 64.

9.7 Viewing a file's current source code

To view a file's pre-transformation DDS source code right-click on the file. From the context menu,select Source Code then Open current source. The file is opened in a separate view and the currentsource code is displayed.




NoteThe current source code view is read-only. You cannot modify thecurrent code here. To modify the current code, use ARCAD-Skipper.

9.8 Viewing a file's simulated transformed source code

After the transformation process has been carried out, you can open the simulated source code foreach individual file in RDi to see what the new code will look like. This is a simulation. The transformedSQL code is only an example of the final transformation that will be applied to the file when the processis validated. The actual transformation will be carried out upon validation.

ExampleUse this view to verify that your DB was correctly transformed or torefer to certain areas in your DB while you analyze and modify anyproblems that the transformation process may have encountered.

NoteThe simulated source code view is read-only. You cannot modify asimulation.

To view a simulation of the converted source code, right-click on the file. From the context menu, selectSource Code then Open simulated source. The file is opened in a separate view and the simulatedsource code is displayed.

9.9 Managing the audit of an individual file

After transformation, every file that was transformed is audited in order to detect any problemsencountered during transformation. There are two versions of this audit:

1. A global report that includes an aggregated list of all themessages for every file in a conversion listcan be accessed from the Conversion Audit view.

2. A file-specific report enables you to check the problems for each individual file in a conversion listby double-clicking on the file in the DDS File Conversion view.

ReferenceFor more information about accessing the aggregated audit report,refer to Working with conversion projects on page 37.

For more information about aggregated conversion audits, refer toResolving problems prior to transformation (conversion audit) onpage 67.

To access the list of warning messages that alert you to problems detected for a file, double-click on thefile in the DDS File Conversion view. The bottom half of the view displays the audit of the individualfile.




Figure 11: Audit messages for an individual file

The following table includes a brief explanation of the bottom half of the DDS File Conversion Listwhen it displays the error messages for a converted file.

Column Definition

Message GroupThe type and ID of the error encountered.

Message ID

Description A short description of the type of error.

Number of Fields The total number of fields affected by the issue.Table 9: Individual file audit report

Double-click on an error message to display the Message Details view. This view provides furtherinformation concerning the error selected including the name of the field affected, if applicable, and thefield's keywords. Right-click on amessage in this view to carry out an action to solve the issue, ifapplicable.

You can also right-click directly on an error in the bottom half of the DDS File Conversion view tocarry out an action to solve the issue, if applicable.


ReferenceFor more information about the user actions that may be required tosolve a problem after transformation, refer to Resolving problems priorto transformation (conversion audit) on page 67.

9.10 Viewing a file's primary keys

Review the current Primary Key(s) for a file to anticipate any changes that may be required for a fileafter conversion.




To access the database links for a file, select it from the conversion list, right-click, then selectPrimary Keys. The AUPDPFKEY commands is launched and the ARCAD-Observer view dedicated todatabase primary keys is displayed.

ReferenceFor more information about how to use the Primary Keys view,refer to the ARCAD-Observer documentation.

For more information about problems that could arise concerning keys,refer to Resolving problems prior to transformation (conversion audit)on page 67.

9.11 Viewing a file's database links

To better understand the relationship(s) a file may have in a database, refer to the DatabaseRelationships view. This view provides various options to review and verify a file's links.

To access the database links for a file, select it from the conversion list, right-click, then selectDatabase Links. The AUPDFLDDBR command is launched and the ARCAD-Observer view dedicated todatabase relationships is displayed.

ReferenceFor more information about how to use the DatabaseRelationships view, refer to the ARCAD-Observer documentation.

9.12 Removing a file from a conversion list

NoteFiles removed from conversion lists can always be added back, howeverif a file was already transformed in a list, then removed, the record ofthe transformation is also deleted.

When a file is added back to a conversion list, you must launch thetransformation process for it again.

To remove a file (or multiple files) from a conversion list, right-click, then select Remove from list.



ARCAD-Transformer DB v13.1User Guide | 10 Verifying data integrity

10 Verifying data integrity

Chapter summary10.1 Accessing data integrity checks in ARCAD-Transformer DB 5710.2 Auditing data integrity 5810.3 Auditing journal integrity 5910.4 Auditing relationship integrity 6010.5 Accessing the job execution monitoring view 6110.6 Viewing audit results (reports) 61

Integrity checks are intended to verify that the data stored in the database files and inside IBM i journalsare not, or never were invalid and that the database links (incoming and outgoing) for each file areaccurate.

Data corruption particularly concerns numeric fields containing non-numeric characters. Initially, it isnecessary to identify and correct corrupted data. However, that is not enough in itself, it is alsonecessary to identify where the data was corrupted.

Important!This step, which takes place prior to the DDS to SQL conversion, isnecessary because corrupt data cannot be put into SQL.

There are two analysis methods available, both of which must be parametrized. Each command can becarried out in Batch or Interactivemode on the local machine but only in Batch mode on a remotemachine.

1. ARCAD's Data Integrity check (ACHKFILDTA) enables you to verify that the data inside yourdatabase's PF files are accurate.

ExampleData is most often considered invalid if a field's content does notcorrespond to the field's type. A numeric field, such a date field ora social security number field contains alpha characters the field'scontent is invalid and will be found via the Data Integrity check.

2. ARCAD's Journal Integrity audit (ACHKDBRFLD) verifies the current DB links and those in the journal.

ExampleDatabase links may be rendered invalid if a program created anyorphans, even temporarily. An orphan may be amissing sourcelink, like an invoice linked to a deleted client, or a temporarybroken link like the content in a purchase order that is deleted byfirst removing the header (the link to the client) and then contentof the order.

Each command can also be carried out on the active data inside PF file(s) (*DATAmode) or on the files'journal record(s) (*JRNmode). You define how far back into the journal's history to check for invalidentries. Checking a file's history may be useful to ensure that data entered into the file is consistentlyaccurate in order to assure that no invalid data will be entered, and refused, when it is converted to atable. It may be necessary to modify the characteristics of the journal to obtain the name of theprogram and its library. They can bemodified using the ASETJRNFIL command.



ARCAD-Transformer DB v13.110 Verifying data integrity | User Guide

NoteIn certain cases an analysis result is only possible when the journalizingof the files was defined in the IMAGES parameter with the *BOTHvalue.

You can check files locally and remotely. There are great benefits to checking that the same files on alocal machine (such as a development machine) and a remotemachine (such as a production machine)are all accurate before launching the database transformation process. This check ensures that yourdevelopment and production content are stable and will react the sameway to the transformed SQLdatabase once it is validated and deployed into production.

The structure for the check is the current file structure (repository) therefore, it is necessary to launchthe analysis after the last change in the file’s structure. Otherwise, all the recordings could beconsidered corrupted.

NoteSQL tables do not require this analysis because the data has alreadybeen checked during execution of the programs.

10.1 Accessing data integrity checks in ARCAD-Transformer DB

Data integrity checks can be run on some or all of the PF files in the application componentrepository or in a conversion list. Database relationship (constraints) audits are run from theDatabase Relationships view.

Figure 12: Accessing the data integrity check options (conversion list)




Figure 13: Accessing the data integrity check options (component repository)

ReferenceFor more information about the repository and conversion lists, refer toWorking with conversion lists on page 46 and Working with conversionlists on page 46.

For more information about the Database Relationships view,refer to the ARCAD-Observer documentation.

10.2 Auditing data integrity

The ACHKFILDTA command, when launched in *DATAmode, checks the integrity of a file's current data.

Step 1 To launch the Data Integrity Check on one or more files in the component repository or aconversion list, select them then right-click. In the context menu, selectData Integrity thenCheck Data Integrity.

- or -

To launch the Data Integrity Check on all of the files in a conversion list, click the CheckData Integrity icon.

NoteThe Data Integrity Check can only be run on PF files becauseLF files do not contain data. In order to run the check on all ofthe files in a conversion list, the list must only contain PF files.If a list contains LF files, the check cannot be run on the entirelist.




You cannot run a check on all of the files in a componentrepository.

Step 2 The ACHKFILDTA command is launched in *DATAmode. The Check Data Validity dialog isdisplayed enabling you to change the parameters for the command. The default parametersfor this command are defined in the preferences menu.

ReferenceFor more information about the parameters, refer to theappendix:Table 17: The ACHKFILDTA and ACHKDBRFLDcommon parameters.

Step 3 Click Execute.

Result The check is launched and the job's progress can bemonitored in the Progress view, whichopens automatically. When finished, click the link available to view the results in theDataIntegrity Report view.

ReferenceFor more information about viewing check results, refer toVerifying data integrity on page 56.

10.3 Auditing journal integrity

The ACHKFILDTA command, when launched in *JRNmode, checks the integrity of the data saved in afile's journals. This method looks for the names of programs that have corrupted a file in the past. Thecheck analyzes the journal entries that index additions and updates to detect any errors, even if theerror has since been overridden or removed.

NoteThis check can only bemade on files that have been journalized andcontain journal entries. Use the ASETJRNFIL command in a nativeemulator to journal a file and modify is characteristics, if necessary. Youmay need to modify a journal in order to find the name of a programand its library.

Step 1 To launch the audit on the journals for one or more files in the component repository or aconversion list, select them, then right-click. In the context menu, selectData Integrity thenAudit journal integrity.

- or -

To launch the audit on all of the files in a conversion list, click the Audit journal integrity iconin the toolbar.

Important!The journal integrity audit can only be run on PF files becauseLF files do not contain data. In order to run the check on all ofthe files in a conversion list, the list must only contain PF files.If a list contains LF files, the check cannot be run on the entirelist.




You cannot audit all of the files in a component repository.

Step 2 The ACHKFILDTA command is launched in *JRNmode. The Check Data Validity dialog isdisplayed enabling you to change the parameters for the command. The default parametersfor this command are defined in the preferences menu.

ReferenceFor more information about the parameters, refer to theappendix:Table 17: The ACHKFILDTA and ACHKDBRFLDcommon parameters andTable 18: The ACHKFILDTA andACHKDBRFLD *JRNmode parameters.


Result The audit is launched and the job's progress can bemonitored in the Progress view, whichopens automatically. When finished, click the link available to view the results in theDataIntegrity Report view.


10.4 Auditing relationship integrity

A constraint is the relationship between a primary key in one table, and a secondary key in anothertable. The ACHKDBRFLD command checks the validity of the active links for the select file(s) or the links inits journals.

Step 1 To launch the Database Constraints Integrity Check on the links defined in ARCAD for one ormore files in theDatabase Relationships view, select them then right-click. In the contextmenu, selectData Integrity then Check relationship integrity for current links in thefiles' data (ex: to find orphans) or Audit journal integrity to check the journal(s) (ex: to findtemporary orphans).

ReferenceFor more information about the Database Relationshipsview, refer to the ARCAD-Observer documentation.

Step 2 The ACHKDBRFLD command is launched. The Check Data Validity dialog is displayed enablingyou to change the parameters for the command. The default parameters for this command aredefined in the preferences menu.

ReferenceFor more information about the parameters, refer to theappendix:Table 17: The ACHKFILDTA and ACHKDBRFLDcommon parameters andTable 18: The ACHKFILDTA andACHKDBRFLD *JRNmode parameters.





Result The check is launched and the job's progress can bemonitored in the Progress view, whichopens automatically. When finished, click the link available to view the results in theDataIntegrity Report view.


10.5 Accessing the job execution monitoring view

The Select Job Execution view displays all of the active commands. To access this view, either click the Job execution monitoring icon in the DDS File Conversion List view (this option is only available

if the list contains only PF files) or right-click in the view then select Open Job Progress view. Thisview is dedicated to monitoring jobs that have been run, are currently running or are planned. Becauseintegrity checks can be run in batch mode or remotely on another IBM i, the analysis may take severalminutes. Double-click a job in the list to view its status.

Figure 14: The Command Execution Information view

The Command Execution Information view displays information relative to the validity processexecution. If a process was launched in *BATCH mode, this view can also be accessed from theProgress view by clicking the link if a check was run in batch mode.

NoteIf the execution occurred on a remote site, refresh remote executioninformation by right-clicking then selecting Refresh remote siteinformation which launches the AUPDCMPDTA command. This option isonly available after the Execution Status passes to *RMT.

Right-click on a process to display the analysis results.

ReferenceFor more information about viewing check results, refer to Verifyingdata integrity on page 56.

For more information about the default settings for this view, refer toTable 4: Validity Check Execution Information Parameters.

10.6 Viewing audit results (reports)

When the analysis is complete, the results are available to you in the form of a comparison report. Thesame comparison detail view is used to analyze the results of file and constraint checks.

There are three ways to access the results:




1. If the check was launched in interactivemode, the Progress view is displayed after the analysisis complete. Click on the link to open the Show audit results.

2. If the check was launched in batch mode, the Progress view and the Command ExecutionInformation view both enable you to access the results after the process is complete.

3. If a file has already been checked, you can always access the results from theData Integrity menuby right-clicking on the file in theDDS Conversion List, theApplication Repository or theDatabase Relationship view.

Right click on the file for which to view the results and select the types of results to display.

The results available for the selected file are displayed. Open one to view the detailed data comparisonview.

Figure 15: The data integrity report



MANAGING CHANGES

ARCAD-Transformer DB v13.1User Guide | 11 Simulating transformations

11 Simulating transformations

Chapter summary11.1 Transforming single files 6511.2 Transforming multiple files 6511.3 Transforming en-mass (all files) 6511.4 Steps to complete after transformation 66

Important!Before launching the transformation simulation, it is recommended toensure that none of the files to transform are currently active in anARCAD version. Because transformations are done on the application-level, and not in a version, if a file is currently being modified in aversion the changes made during transformation may not be taken intoaccount.

NoteIt is recommended to launch the simulation on files that risk beingexceptions to an accurate transformation. Running the simulation onall of the files in a conversion list may clutter your system.

The ACVTDDSSQL conversion command transforms physical and logical DDS files to SQL. The conversionis always made from *FILE type objects with either a PF or LF attribute.

This command is carried out when a conversion is validated but can also be run before validation inorder to view a simulation of the transformation.

PF source types are converted to TABLES. LF source types are converted to INDEX. Only logical fileswhose format is the same as the physical can be converted to a compilable source. Logical files with aformat that is not the same as the physical, multi-format and join logical files cannot be converted.Attempting to convert these kinds of files generates specific diagnosticmessages. An exception ispossible when the logical files have exactly the same fields as the physical, not modified, in the sameorder (refer to the Share Fmt. PF if LF has same fields (LFSHRPFFMT) parameter).

It is possible to use the resulting SQL files without further intervention after the initial conversion iscomplete. However, not all keywords, attributes and parameters can be converted and may not be inyour converted files by default. This is why the primary, simulation conversion is supplemented by ananalysis of all keywords contained in the transformed DDS and all file attributes. Whenever the DDSconversion to SQL is not possible for the whole file, a field or a parameter, messages are stored in a filewhich are then accessed in the audit. The actions to manually carry out to repair the problemsencountered are described in the audit reports.

The default values for this command are defined when a file's parent conversion project is created ormodified. When the command is launched, the command applies all of the parameters to each fileselected.



ARCAD-Transformer DB v13.111 Simulating transformations | User Guide

Figure 16: Launching the Transformation Process

11.1 Transforming single files

When executing the transformation process for a single file in a conversion list, the Convert DDS fileto SQL (ACVTDDSSQL) dialog is displayed. This dialog enables you to change the default parametersdefined in the parent conversion project.

ExampleChanging the default parameters for a single file may be helpful if youneed to change the way that Primary Keys or multi-member files arehandled for one file.

To launch the conversion for a single file, select it in the conversion list, then right-click. The ConvertDDS file to SQL (ACVTDDSSQL) dialog is displayed in which you can change the default conversionparameters for this single transformation.

ReferenceFor more information about the ACVTDDSSQL parameters, refer to theappendix: The ACVTDDSSQL command on page 93.

11.2 Transforming multiple files

When executing the transformation process for multiple files in a conversion list, the Convert DDS fileto SQL (ACVTDDSSQL) dialog is not displayed. The default conversion parameters defined in theparent conversion project are applied to all of the files selected.

To launch the conversion for multiple files in a Conversion list, but not all of the them, select the files(Ctrl+click), then right-click. From the context menu, select Convert to SQL. Click Yes in the dialogthat is displayed to confirm and launch the transformation process.

11.3 Transforming en-mass (all files)

When executing the transformation process for all of the files in a conversion list, the Convert DDS fileto SQL (ACVTDDSSQL) dialog is not displayed. The default conversion parameters defined in theparent conversion project are applied to all of the files selected.



ARCAD-Transformer DB v13.1User Guide | 11 Simulating transformations

To launch the conversion for all of the files in a conversion list at the same time, click the ConvertfromDDS to SQL icon in theDDS File Conversion List view. Click Yes in the dialog that is displayed toconfirm and launch the transformation process.

11.4 Steps to complete after transformation

If the conversion process completes without errors, the transformed files are available for review.

If the process encountered errors, a dialog is displayed that informs you of themessages available inthe Arcad Messages view concerning the error(s) (Window>ShowView>ARCAD Software>ArcadMessages).

There aremultiple options available when the transformation is complete and user actions may berequired if the conversion audit detected problems during transformation.

1. [Optional] View the simulated transformed source code.

SeeWorking with conversion lists on page 46.

2. View the transformation's aggregated audit or the audit for an individual file to access and solveany problems that the process may have encountered.

See Resolving problems prior to transformation (conversion audit) on page 67 and Working withconversion lists on page 46.

3. Manage themodifications necessary for dependent components.

SeeManaging changes required for dependent components on page 80.

4. [Optional] Change the names of a file's fields.

See Changing or adding field names on page 74.

5. Approve the transformations madewhen all of the issues above are corrected by checking out thefile(s) into the ARCAD version selected in the conversion project.

See Validating transformations on page 87.



ARCAD-Transformer DB v13.112 Resolving problems prior to transformation (conversion audit) | User Guide

12 Resolving problems prior to transformation(conversion audit)

Chapter summary12.1 Accessing the Conversion Audit - Aggregated Results view 6712.2Overview of the Conversion Audit view 6812.3 Resolving problems with primary keys 6912.4 Resolving problems with multi-member files 7212.5 Imposing or removing attributes 72

The global audit for the transformations carried out for a selected conversion project are presented bycategory in the Conversion Audit: Aggregated Results view. This audit covers all of the problemsencountered in every transformed file in the project.

Be specifically careful with the category Problems requiring user action (under PF audited and/or LFaudited categories). If there are any conversion problems concerning primary keys, multi-member files,or keywords not existing in SQL, you must choose an appropriate action to resolve the problem(s).

If files cannot be converted and ARCAD-Transformer DB does not suggest a solution in the ConversionAudit view, is it recommended that you revise them in ARCAD-Skipper and perform the transformationprocess again.

12.1 Accessing the Conversion Audit - Aggregated Results view

After transformation, every file that was transformed is audited in order to detect any problemsencountered during transformation. There are two versions of this audit:

1. A global report that includes an aggregated list of all themessages for every file in a conversion listcan be accessed from the Conversion Audit view.

2. A file-specific report enables you to check the problems for each individual file in a conversion listby double-clicking on the file in the DDS File Conversion view.

ReferenceFor more information about accessing the file-specific audit report,refer to Working with conversion lists on page 46.

To access a conversion project's aggregated audit, right-click the on project in the ConversionProjects view and select Open the Transformation Process View.



ARCAD-Transformer DB v13.1User Guide | 12 Resolving problems prior to transformation (conversion audit)

Figure 17: Accessing the Conversion Audit - Aggregated Results view

12.2 Overview of the Conversion Audit view

The Conversion Audit: Aggregated Results view is separated into three sections:

1. The top portion lists all of the possible problems that a transformation project can encounter,listed by category. Themost important category of problems is the "Problems requiring useraction" category.

Important!It is essential that all issues requiring action be resolved before afile's transformation is validated. Validating a file that containsresolvable errors is not recommended.

2. When a category in the tree is double-clicked, the second portion of the view displays the list ofwarning messages that correspond to the selected category.


3. When a category in the tree is double-clicked or when amessage in the second portion of the viewis double-clicked, the third portion of the view displays the list of files currently affected by theproblem corresponding to the selected category.Double-clicking a file listed in this portion of the view opens a detailed explanation of the zonesaffected by the selected issue in the selected file. This view is read-only.




The files in this view follow the same structure as in the conversion list. Additionally, there is a newoption in the context menu when you right-click on a file that requires user action in the thisportion of the view.

Figure 18: Accessing user actions in the Conversion Audit view

Click the corresponding icon to expand or collapse all the results in the audit categories tree.

Select Convert to SQL to run the Conversion Process again for all of the files included in theselected audit category. See Simulating transformations on page 64.

Select Rename Fields then Prepare the Propagation for field renaming to pin all of the files includedin the selected audit category. See Changing or adding field names on page 74.

12.3 Resolving problems with primary keys

For a key problem, themessage group in the second portion of the audit view is PF_KEY1, PF_KEY2 orPF_KEY3,

There are three different types of problems that the transformation process may encounter concerninga DDS file's key:

1. The key is not unique.2. The key's attribute is not taken into account in the a TABLE.3. The key's attribute is not taken into account in SQL.

Important!If there is a problemwith a file's key, youmust carry out the appropriateactions to resolve it before the file's transformation can be validated.




Access the "User Action" resolution for a file by either right clicking on the file in the bottom portion ofthe Aggregated Audit view and selecting User Actions or by following the steps outlined in Workingwith conversion lists on page 46.

12.3.1 Resolve non-unique primary key problems (PF_KEY1)If the parent conversion project does not have a specific parameter set for theAction if PF keyproblem (PFKEYACT) command, and a file has an error concerning a non-unique key, you must resolvethe issuemanually in the aggregated audit.

The user action available is Actions for primary key problems.

Step 1 In the Select the action for key problems dialog, select the action to take to solve the issue.The options are *PRIKEY, *INDEX and *LF.

ReferenceFor more information about these options, refer to the detailsof the Action if PF key problem (PFKEYACT) in the appendixThe ACVTDDSSQL command on page 93.

Step 2 If you select *INDEX or *LF, clickNext to choose the name of the new file to create. TheINDEX/LF Name drop-down list is prepopulated with the names of all the existing LFs in theparent PF.

NoteThe name of the new INDEX must be different than theexisting LFs.

Select an existing LF then change the name or enter a new name for the new file.

Step 3 Click Finish to resolve the issue.

Result The action is carried out for the file and the aggregated audit is refreshed. The file no longerappears in the bottom portion of the audit view.

12.3.2 Create keys in SQL for DDS files without keys (PF_KEY2)If the original DDS file was created without a key, you must resolve the issuemanually in theaggregated audit.


Step 1 In the Select the action for key problems dialog, select the action to take to solve the issue.The options are:

l *NONEThe table is created without a key.

l *INDEXThe table is created without a key and a new index is created which includes the requiredkey.




l *LFInstead of a new index containing the key, a new LF is created containing the key.

Step 2 If you select *INDEX, clickNext to choose the name of the new file to create. The INDEX/LFName drop-down list is prepopulated with the names of all the existing LFs in the parent PF.





12.3.3 Create keys in SQL for DDS files with keys incompatible with SQL(PF_KEY3)

In a PF a key can be filtered by FIFO (first in first out), however SQL requires content for a key to befiltered. If the original DDS file was created with a key such as this, which cannot be transformed intoSQL, you must resolve the issuemanually in the aggregated audit.



Step 1 In the Select the action for key problems dialog, select the action to take to solve the issue.The options are:

l *NONE - The table is created without a key.l *LF - The table is created without a key and a new index is created which includes therequired key and the keywords that could not be converted to SQL.

l *PRIKEY - A primary key is created in the new table.

Step 2 If you select *LF, clickNext to choose the name of the new file to create. The INDEX/LF Namedrop-down list is prepopulated with the names of all the existing LFs in the parent PF.








12.4 Resolving problems with multi-member files

For a problem concerning multi-members, themessage group in the second portion of the audit view isMULTI_MBR.

A PF file can bemulti-member (parameter MAXMBRS > 1). This notion does not exist for SQL tables.When this problem is encountered and the parent conversion project does not have a specificparameter set for theAction if multiple members (MULTIMBACT) command, you must resolve theissuemanually in the aggregated audit.

The user action available is Multiple member Actions.

Step 1 In theMultiple member actions dialog, select the action to take to solve the issue. Theoptions are *NOTSQL, *ONEMBR and *MBRFLD.

ReferenceFor more information about these options, refer to the detailsof the Action if multiplemembers (MULTIMBACT) in theappendix The ACVTDDSSQL command on page 93.

Step 2 If you select *MBRFLD, clickNext to define the additional zone. All of the fields in the secondpage of the dialog aremandatory.

ReferenceFor more information about these options, refer to the detailsof the Info new field for multi-mbrs (MULTIMBINF) in theappendix The ACVTDDSSQL command on page 93.



12.5 Imposing or removing attributes

For attributes in the source PF/LF that cannot be converted to SQL themessage group in the secondportion of the audit view is ATTR.

ARCADmanages the problem caused by these IBM i-specific attributes/keywords and renders themcompatible with SQL by using pre compilation directives in its compilation specificmode. It can usecommands like CRTPF to change the object (not the source) and add themanagement of the non-SQLattributes to the objects generated from newSQL sources.

The commands specific to DDS, CRTPF, CRTLF, CHGPF, CHGLF file types enable you to change anumber of attributes for each PF or LF file. These values do not necessarily correspond to the defaultvalues created when the SQL tables or indexes are generated during transformation and they cannotbe saved during the conversion. When this problem is encountered and the parent conversion projectdoes not have a specific parameter set for the *FILE attributes to impose (FILEATR) command, youmust resolve the issuemanually in the aggregated audit.

The user actions available are Remove Attribute or Impose Attribute.





Imposing an attributemodifies the object which is compiled from a source table. The%EXECACHGPF/CHGLF FILE(&O/&N) instruction is added to the new source file in addition to the list ofattributes indicated which will modify the object generated when the table is compiled.

Removing an attribute will prevent it from being included in the transformation completely.

ReferenceFor more information about these options, refer to the details of the*FILE attributes to impose (FILEATR) in the appendix TheACVTDDSSQL command on page 93.



ARCAD-Transformer DB v13.1User Guide | 13 Changing or adding field names

13 Changing or adding field names

Chapter summary13.1 Preparing files to rename fields 7413.2Overview of the renaming fields view 7513.3 Renaming short names (*NAME zones) 7613.4 Renaming long names (*ALIAS zones) 7813.5 Confirming that a file's fields have been renamed 79

SQL enables field names to bemuch longer than DDS. Renaming the (short) field names and the (long)field aliases in a DDS file that you are converting to SQL may be useful to refresh themeaning of thetitles of your database's columns.

NoteThis option is only available if theRename Fields parameter of theparent conversion project is set to *NAME, *ALIAS or *BOTH. If thisparameter is set to *NO, the option to rename fields for the files in theconversion list is not available.

ReferenceFor more information about the parameters for conversion projects,refer to Table 6: The ACVTSQLPRJ command parameters (conversionproject properties).

If a conversion list's parent conversion project allows fields to be renamed, the context menu for eachof the files in the list contains theRename Fields option. Right-click on a file or select multiple files andright-click to carry out the following actions related to renaming the long and short field names in aDDS file.

Important!There are risks involved in changing the short or long name of a field.

If a name is referenced by a program, changing it will impact thatprogram and make the conversion process more complicated. If youchange the name of a field, refer to Managing changes required fordependent components on page 80.

13.1 Preparing files to rename fields

Before accessing the Renaming Fields view, the DDS files in the conversion list must be prepared.The preparation process checks all of the cross references for the file(s) and determines whichdependent components will be affected by renaming the fields. It prepares amatrix in theRenaming Fields view and proposes replacement names automatically.

ReferenceThe default macro to use to propagate fields is defined in thePreferences: Define the default macro to propagate files in a conversionlist on page 31



ARCAD-Transformer DB v13.113 Changing or adding field names | User Guide

Figure 19: Analyze the cross references in DDS files before renaming fields

To analyze all of the files in a conversion list, click the Prepare files for renaming icon in the DDSFile Conversion List view's toolbar.

To analyze one or multiple files in a conversion list, select them, then right-click. Select Prepare thepropagation to rename the fields.

NoteThis option is only available in the contextualmenu for each PF/LF if theRename Fields parameter of the parent conversion project is set to*NAME, *ALIAS or *BOTH.

Warning!If a file has already been propagated, running it again will override anychanges already made to fields.

If you open the Renaming Fields view to change the names of a file's fields without running thisanalysis, ARCAD-Transformer DB will prompt you to run the analysis. Click Yes in the dialog to run theanalysis.

13.2 Overview of the renaming fields view

To rename the fields for a selected number of files in the list, right-click then select Rename Fields.Select Open the field list to open the file's or files' list of fields in the Fields view.

The Fields view displays the following information common to all of the fields in the DDS file selected.




Figure 20: The Fields view

Column Description

Component Name The name of the DDS file.

Short Name The DDS file's current field name.

L. The length (in characters) of the current field name.

Format The DDS file's format keyword.

Text The description of the DDS file.

Attributes The type of the field. For example, Alpha(6)means alphanumeric, length 6.

Ext. File nameExt. File TypeExt. FormatExt. Field Name

The details concerning the external reference file used to name the original DDSfield, if applicable.

Table 10: Fields view: common information

If the parent conversion project is set to change only *NAME fields or only *ALIAS fields only theoptions corresponding to those fields are displayed in this view. If the project enables you to change*BOTH the name and aliases (long names) of the files in its list, all of the following options are available.

13.3 Renaming short names (*NAME zones)

ARCAD-Transformer DB analyzes a DDS file's current field names and proposes replacement namesautomatically. Renaming a field can be as easy as accepting the new name proposed by the analysis orentering a new namemanually.

TheRenaming Fields view includes five extra columns to modify the short name for a field when thefile is converted to SQL.

Column Description

New Short Name Enter the new short name for the field. Text entered here will be the new shortname for the SQL field.

L. The length (in characters) of the new SQL short name.

Suggested ShortName The short name automatically proposed by ARCAD-Transformer DB.

Accepted If the checkbox in this column is ticked, the short name proposed by ARCAD-Transformer DB will be taken into account when the file is validated.

Status The current status of the renamed field.Table 11: Fields view: renaming short names




13.3.1 Accept proposed new short names

Step 1 Review the name suggested by ARCAD-Transformer DB, displayed in the Suggested ShortName column.

Step 2 Right-click on the field's row and select Change Status then Accept the proposed name,or click the checkbox in theAccepted column.

Step 3 The proposed name automatically includes a question mark at the beginning. Question marksare invalid characters. When the suggested name is automatically filled in, the system detectsthe error and warns you that the name is invalid.

Click OK in theMsg Id: MSG3524 dialog to confirm.

Step 4 The field's status is To be checked because the new name is invalid. Manually remove thequestion mark from the new name field.

Figure 21: Manually remove the invalid question mark character from a suggested new name

Step 5 Press [Enter] or select another field in the view to register the change.

Result The field's status is changed to Input OK if the new short name is valid. The name suggestedby ARCAD-Transformer DB will be applied to the SQL file's short name field when the file isvalidated.

13.3.2 Create new short names manuallyNew short names can bemodified at any time before the transformed file is validated.

Step 1 Review the existing name of the field, displayed in the Field Name column.

Step 2 Enter the new name for the field in theNew Short Name column.

Ensure that the requirements for naming fields are respected. A valid short name:

l cannot contain spaces;l cannot contain SQL invalid characters;l must have a letter as the first character in the name;l must not exceed themaximum number of characters allowed by SQL.


If the new name is valid, the status is changed to Input OK and is applied to the transformedfile when the transformation process is validated.

If the new name is invalid, a warning dialog is displayed which explains which requirement(s)were not followed. The new short name is preserved but proceeded by "??" to indicate that it isinvalid. Invalid names are not saved and are not applied to the transformed file uponvalidation.




Step 4 If the name is invalid, revise it.

Result When it is valid, the name entered will be applied to the SQL file's short name field when the fileis validated.

13.4 Renaming long names (*ALIAS zones)

ARCAD-Transformer DB analyzes a DDS file's current field alias and proposes replacementsautomatically. When converted to SQL, DDS field aliases are transformed into field long names.Renaming an alias can be as easy as accepting the new name proposed by the analysis or entering a newlong namemanually.

TheRenaming Fields view includes five extra columns to modify the long name for a field when the fileis converted to SQL.

Column Description

Long Name If the DDS file has an alias defined for a field, the current alias is displayed here.

New Long Name Enter the new long name for the field. Text entered here will be the new longname for the SQL field.

Suggested LongName

If the file currently has an alias, ARCAD-Transformer DB automatically proposesa new long name.

Accepted If the checkbox in this column is ticked, the long name proposed by ARCAD-Transformer DB will be taken into account when the file is validated.

Status The current status of the renamed field.Table 12: Fields view: renaming long names

13.4.1 Accept proposed new long names

Step 1 Review the name suggested by ARCAD-Transformer DB, displayed in the Suggested LongName column.

Step 2 Right-click on the field's row and select Change Status, then Accept the proposed name,or click the checkbox in theAccepted column.

Step 3 The proposed name automatically includes a question mark at the beginning. Question marksare invalid characters. When the suggested name is automatically filled in, the system detectsthe error and warns you that the name is invalid.

Click OK in theMsg Id: MSG3524 dialog to confirm.

Step 4 The field's status is To be checked because the new name is invalid. Manually remove thequestion mark from theNew Long Name field.


Result The field's status is changed to Input OK if the new long name is valid. The name suggested byARCAD-Transformer DB will be applied to the SQL file's long name field when the file isvalidated.

13.4.2 Create new long names manuallyNewLong Names can bemodified at any time before the transformed file is validated.




Step 1 Review the existing alias, displayed in theAlias Name column, if there is one. If there is nocurrent alias for a field, you can still create a new long name for the SQL file.

Step 2 Enter the new name for the field in theNew Long Name column.

Ensure that the requirements for naming fields are respected. A valid long name:

l cannot contain spaces;l cannot contain SQL invalid characters;l must have a letter as the first character in the name;l must be amaximum of 70 characters.


If the new long name is valid, the Status is changed to Input OK and is applied to thetransformed file when the transformation process is validated.

If the new name is invalid, a warning dialog is displayed which explains which requirement(s)were not followed. The new long name is preserved but proceeded by "??" to indicate that it isinvalid. Invalid names are not saved and are not applied to the transformed file uponvalidation.

Step 4 If the name is invalid, revise it.

Result When it is valid, the name entered will be applied to the SQL file's long name field when the fileis validated.

13.5 Confirming that a file's fields have been renamed

You may have a lot of files in which you must rename fields and each file may havemany fields torename. In order to keep track of the files for which you have completed this task, it is recommended toconfirm that the renaming is complete by changing the status of the task.

Confirming that a file's fields have been renamed is not mandatory. This status does not impact therenaming process in any way; it is only a reminder that the fields in the file have been renamed. You canchange the new name(s) of fields in any file even after confirming that the changes have been made.

To confirm that the new name(s) for the fields in a file have been completed, right-click on the file (ormultiple files) in the DDS File Conversion List view. Select Rename Fields, then Confirm fieldrenaming is complete. The value in the Field Renaming Data column is changed to Confirmed for theselected file(s).

To reset the status for a file, right-click on it in the DDS File Conversion List view. Select RenameFields, then Clear the "confirmed" field renaming status.

TipChange the status for a file if you aremodifying new names in order toensure that the confirmed status is only given to files for which the taskis complete.



ARCAD-Transformer DB v13.1User Guide | 14 Managing changes required for dependent components

14 Managing changes required for dependentcomponents

Chapter summary14.1 Reviewing the details of the changes required for dependents 8014.2 Applying the changes required for dependent components 83

An important part of DDS to SQL transformation is updating the cross references between the filesbeing transformed and their dependencies. ARCAD-Transformer DB automatically isolates the files thatreference the PF/LF files you are transforming and provides engines to automatically update them.

Files that refer to PF or LF source files modified during the conversion process, such as programs(*PGM), service programs (*SRVPGM), printer files (*PRTF) or display files (*DSPF), are all dependentfiles and their references will need to be updated.

The list of dependent components to modify is accessed from the Conversion Validation view.Here you can review the list of dependents impacted by transformation and the line by line detail of thechanges required for each file.

To make the changes, ARCAD-Transformer DB has integrated four dedicated engines thatmust be runin a specific order that each carry out the required updates.

14.1 Reviewing the details of the changes required for dependents

Click theView Proposed Modifications button at the bottom of the Conversion Validation view toaccess the list of files impacted by the transformation and themodifications required to update thedependencies.

Figure 22: Accessing the Modifications to impacted dependent components view



ARCAD-Transformer DB v13.114 Managing changes required for dependent components | User Guide

14.1.1 Overview of the Modifications to Impacted DependentComponents view

The Summary section of this view contains information about the target version selected in the parentconversion project.

The following table includes a brief explanation of the information available for each of the dependentcomponents impacted by transformation in the Modifications to impacted dependentcomponents view.

Column Description

Component Name The name of the dependency to modify.

Component Type The type of the dependency to modify.

Programmer The name of the developer who last edited the component.

Text The description content of the dependency to modify.

Warning If a warning message is applicable to the change(s) required in the file, it isdisplayed here.

Status

The status of the changes required for the file.

l WaitingThe changes have not been applied to the file via the dedicated engines.

l Applied

The changes have been applied to the file via the dedicated engines.

Marked The number of lines in the component marked as impacted by thetransformation but do not need to bemodified.

Updated The number of lines in the component that must bemodified.

Added The number of lines in the component that must be added.

Deleted The number of lines in the component that must be deleted.

Source Library The dependency's Source Library.

Generation date The date the proposed modifications were generated.Table 13: Description of the list of dependents impacted by transformation

Click the Remove icon to remove all of the simulated modifications for the impacted dependents forthe conversion project's target version.

Select a file and either click the Remove selected components icon or right-click then selectRemove Selected Modifications to remove the simulated modifications for the selected impacteddependents for the conversion project's target version.

Warning!Remove or deletemodifications with caution!

Removing an entry deletes the selected proposition(s). There is nomechanism to verify that the set of modifications remains coherent ifyou delete propositions.




Select a file and either click the Open current source icon or right-click then select Open currentsource to view a file's source code before themodification is applied. The file is opened in a separateview and the current source code is displayed.

NoteThe current source code view is read-only. You cannot modify thecurrent code here. To modify the current code, use ARCAD-Skipper.

Select a file and either click the Open simulated source icon or right-click then select Opensimulated source to view a simulation of a file's code after the required modification(s) has/have beenapplied. The file is opened in a separate view and the simulated source code is displayed.

NoteThe simulated source code view is read-only. You cannot modify asimulation.

Click the Display icon to display either only the applied modifications or all modifications proposed inthe list.

Double-click on any dependent component in the list, right-click then select ShowDetail to view theread-only detailed view of the changes required.

14.1.2 Viewing the details of the changes to dependent componentsThe Transformer Entry Details view displays the proposed modifications to the selecteddependency. To access this view, double click on a any dependent component in the Modificationsto impacted dependent components view.

NoteThe content in this view is read-only.

The top portion of the view displays information about the conversion project's target version, the typeof dependent component and the number of lines in the file impacted by the transformation.

The following table includes a brief explanation of the information available for each of the linesimpacted by the transformation in the selected dependency.

Column Description

Line # The number of the line impacted by the transformation.

Action

The type of action required for the line to modify it in order for it to conform tothe transformation made in the referenced file.

Impacted A line that was detected but does not need to bemodified.

Added Added a new line.

Updated An automaticmodification was made.

Deleted The line was deleted.

Change TypeThe code that represents the exact changemade to the line. The following arethemost common types of change:

*MRK CLP lines just marked, because they contain an object nameTable 14: Description of the line-by-line details in the Transformer Entry Details view




Column Description

(useful for Multi-member management)

MRK Miscellaneous lines just marked with no modification

ADDFLD New field added

CHGDEF Change the definition of a field

CHGKEY Change the key list definition

CHGOPE Change the operation code in an instruction

CHGPOS Change position

DB/DSPF Need to evaluate DB field from/to DSPF field

KWDDDS New keyword added in DSPF/PRTF source

NEWDEF Newdefinition of a field

NEWFLD New field added

NEWKEY New field key added

RMVDEF Remove definition of a field from a calculation specification

RNMFLD Rename a field

Source Code The simulation of the new source code after themodifications is applied.

Warning message If a warning message is applicable to the change required, it is displayed here.

Generation date The date the proposed modifications were generated.

Line seq. number The added lines' sequence number.Table 14: Description of the line-by-line details in the Transformer Entry Details view

Select a line and either click the Delete icon or right-click then select Delete Modification toremove the simulated modification from the view.

Warning!Deletemodifications with caution!

Removing an entry deletes the selected proposition(s). If you delete aproposition by mistake, you must clear all the propositions formodifications and launch the process with the different engines againto regenerate the propositions.

Click the Display icon to display either only the applied modifications or all modifications proposed inthe list.

14.2 Applying the changes required for dependent components

To make the changes required for the dependent components impacted by transformation, you mustrun the engines available in the Engine Execution view. The dependent component cannot bevalidated and checked out into the target version until they have been modified via these engines.

There are four categories of changes required to modify dependent components. A separate engine isdedicated to each category. When launched, each engine prepares the impacted components for theautomaticmodification required. When the changes are applied to the components in the Validationview, the problem(s) identified in each dependent are corrected automatically.




1. Renaming short name fields (RNMFLD engine)2. Updating KeyWords in *DSPF and *PRTF files (DSPKWD engine)3. Renaming Components (RNMOBJ engine)4. Adding zones to improvemanagement of multi-member files (MBRFLD engine)

Warning!The four enginesmust be run in the order listed above because the filesare updated after each engine is run and the changes made by the firstenginemay be required for the second engine to function correctly.

14.2.1 Accessing the Engine Execution viewTo access the Engine Execution view for a specific conversion project, right-click the on the projectin the Conversion Projects view and select Open the Transformation Process view.

Figure 23: Accessing the Engine Execution view

14.2.2 Launching the enginesEach of the four engines is available in a separate, dedicated section. To launch the engine and preparethe corresponding components for the transformations required, click the Start the execution icon ineach section.

Important!If there are dependent components affected by the transformation andthe changes required for them correspond to the changes an enginemanages, you must launch that engine.




If no components are affected by the changes managed by an engine,that engine cannot be launched (it is grayed-out).

Warning!The four enginesmust be run in the order listed below because the filesare updated after each engine is run and the changes made by the firstenginemay be required for the second engine to function correctly.

1. Renaming short name fields (RNMFLD engine)2. Updating KeyWords in *DSPF and *PRTF files (DSPKWD engine)3. Renaming Components (RNMOBJ engine)4. Adding zones to improvemanagement of multi-member files

(MBRFLD engine)

While the engine is processing, the Execution Status changes to In Progress and a green status bar isdisplayed in the engine's section.

Figure 24: Example of an engine in progress



FINALIZING THETRANSFORMATION

PROCESS

ARCAD-Transformer DB v13.115 Validating transformations | User Guide

15 Validating transformations

Chapter summary15.1 Accessing the Conversion Validation view 8715.2Overview of the Conversion Validation view 8815.3 Attaching maintenance reports to validated conversion projects 8915.4 Validating the DDS to SQL transformations 9015.5 Validating the changes to dependent components 9015.6 Verifying the transformations in the target version 91

After all of the problems encountered during transformation have been resolved, each of thetransformed files must be validated in order to delete the old DDS PF and/or LF files and replace themwith the generated TABLE/INDEX files. Validating the transformation checks out the transformed filesinto the conversion project's ARCAD version making them available in your application.

Validating carries out three types of actions and must be done in two parts:

Part 1: Validating the conversion of the DDS files to SQL deletes the original PF/LF files and generatesthe final TABLE/INDEX files and transfers them to the target ARCAD version (checks them out into theversion).

Part 2: Validating the changes required to dependent components checks out the dependentcomponents impacted by the transformations into the target ARCAD version and modifies them.

Validation is carried out in the Conversion Validation view.

15.1 Accessing the Conversion Validation view

To access the Conversion Validation view for a specific conversion project, right-click the on theproject in the Conversion Projects view and select Open the Transformation Process view.



ARCAD-Transformer DB v13.1User Guide | 15 Validating transformations

Figure 25: Accessing the Conversion Validation view

15.2 Overview of the Conversion Validation view

The Conversion Validation view is separated into three sections:

1. The top portion lists the details of the target ARCAD version into which the validatedTABLE/INDEX files will be transferred.

You can also upload an existing MR or aWI if the work itemmodewas activated in ARCAD-Skipper. When the project is validated the attachments is saved to the version in order todocument the transformation.

2. Themiddle portion of the view displays the files from the selected conversion project that havebeen transformed. This view does not filter out the files that may still have problems in them.

The following table includes a brief explanation of the information available for each of thetransformed files in theModifications on Files section.

Column Description

Name The name of the DDS file to transform.

Description The description of the DDS file to transform.

Source Type The original file type of the DDS file to transform (PF or LF)Table 15: Description of the list of files to validate




Column Description

Status

The current status of the file to transform. Only files with an 'OK' statusare displayed in this list because any other status means that the filecannot be transformed. If a file is held or has an *ABN failure, it cannot betransformed and therefore the transformation cannot be validated.

l OKThe conversion simulation is ready to be validated and carried out onthe source file.

Source File The original Source File of the DDS file to transform.

New Source Type The new file type of the generated SQL file (TABLE or INDEX).

New Source File The new Source File of the generated SQL file.

Conversion

A brief description of what is validated for each line/file.

l DDS files that are converted to SQL aremarked as "SQL conversion".l Index files that were created to solve problems concerning the keys inPF files (see New file name to create (NEWFILE) on page 100) aremarked as "New index to manage the key for PF...".

l LF files that were created to solve problems concerning the keys in PFfiles (see New file name to create (NEWFILE) on page 100) aremarkedas "New LF to manage the key for PF...".

Table 15: Description of the list of files to validate

3. Right-click on a file in theModifications on Files portion to open the current or simulated sourcecode or validate one or multiple files in the list.

4. The third portion of the view displays the total number of dependent components impacted by thetransformation of the files in the list above as well as howmany lines in those "other" componentswere impacted.

Click theView Proposed Modifications button to access themodifications required for thedependents.

Click theApply button to checkout the impacted files into the project's target version and apply allof the changes to those dependents.

15.3 Attaching maintenance reports to validated conversionprojects

If the conversion project's target version contains Maintenance Reports (MR), they are listed in theAttached MRs drop-down box. To document the checkout of the transformed files into the version,select an MR from the list or enter an existing MR's number to link it to this transformation process.

TheMR attached to the validation should document all the components that are checked out by thevalidation process.



ARCAD-Transformer DB v13.1User Guide | 15 Validating transformations

15.4 Validating the DDS to SQL transformations

NoteThe PF/LF files with an *ABN status are not displayed in this list becausethey cannot be converted.

Suspended files (*HLD status) are not displayed in this list because theirheld status stops them from being converted.

Important!When files that are already available in the project's target version,which are highlighted in magenta, are validated the new version of thefile override and replace the existing version without displaying awarning message.

Important!Files that are checked out into a version other than the project's targetversion cannot be validated until they are released from their currentversion and available to be checked out into the project's targetversion.

If any of the files selected cannot be validated, for any of the above reasons or any other, an errormessage is displayed. The error(s) can be referenced in the Arcad Messages view (Window>ShowView>ARCAD Software>Arcad Messages).

If the validation is completed without errors, a dialog confirms this and the file is checked out into thetarget version.

To validate one or multiple files in the list, select the file(s), right-click and select Apply changes.

To validate all of the files in the list, click the Apply for all files button below the list.

Figure 26: Validating the conversion of DDS files to SQL

15.5 Validating the changes to dependent components

An important part of DDS to SQL transformation is updating the cross references between the filesbeing transformed and their dependencies. ARCAD-Transformer DB automatically isolates the files thatreference the PF/LF files you are transforming and provides engines to automatically update them.

Before validating the completed conversion process, these dependents must be updated using theengine provided.




NoteOnly the information concerning dependent components that havealready been prepared for modification using the engines provided in the Engine Execution view are displayed here.

Click theView Proposed Modifications button at the bottom of the Conversion Validation view toaccess the list of files impacted by the transformation and themodifications required to update thedependencies.

ReferenceFor more information about modifying impacted files, refer toManaging changes required for dependent components on page 80.

When the changes have been made using the engines dedicated to preparing the dependents formodification, click theApply button at the bottom of the Conversion Validation view to check outthe dependents into the conversion project's target version and apply the changes requiredautomatically.

15.6 Verifying the transformations in the target version

Verify that the old PF/LF component is in state ‘deleted’ and the new TABLE/INDEX component createdby the conversion process is in state ‘Type Chg./Src. File Chg’ in the target version components view. Ifyes, you have successfully completed the transformation.



APPENDICES

The ACVTDDSSQL command

The ACVTDDSSQL conversion command transforms physical and logical DDS files to SQL. The conversion is always made from *FILE type objects with either aPF or LF attribute.

The following table includes a brief explanation of each parameter required for the ACVTDDSSQL command. Many of the parameters can recover informationdefined in the parent conversion project (ACVTSQLPRJ). If an option has a default value, it is indicated in bold.

ReferenceFor more information about the parameters for conversion projects, refer to Table 6: The ACVTSQLPRJ command parameters(conversion project properties).

Field(command) Description

File (FILE)

The name of the file to convert to SQL. This file must be of type PF or LF.

The value *LST enables you to process files using a list of sourcemembers.

Select the parent Library.

List (LIST)

The name of an existing list. This must be the name of a list of sourcemembers. Only members of type PF and LFwill be processed.

l *LIBLThe list is searched for in the library list.

l *CURLIBThe list is in the current library for the job. If there is no *CURLIB defined, the QGPL library is used by default.


*ProjectCode(CVTSQLPRJ)

The unique name of the conversion project to process.

l *NONEThe conversion is not attached to a project. This allows you to test a particular conversion by changing various parameters. Warningmessages cannot be used for the conversion of DSPF/PRTF. The *CVTPRJ value cannot be used for any parameter on this command.

Table 16: The ACVTDDSSQL command parameters (Conversion Process properties)

ARCAD-Transformer DB v13.1The ACVTDDSSQL command | User Guide




l Enter the name of an existing conversion project.

Source file(SRCFILE)

The TABLE/INDEX source file into which the new files, created during transformation, should be saved.

If the name of the source file entered does not already exist, it will be created when the project is saved.

l Enter the name of a file.

l *CVTPRJUse the value defined in the parent conversion project.


Member(SRCMBR)

The name of the sourcemember which should contain the converted SQL source.

If themember does not already exist, it will be created.

l Enter the name of amember.l *OBJThe name of the sourcemember is identical to the name of the data file.

Replace ifexisting(REPLACE)

This option specifies that the converted sourcemember should be replaced if it already exists.

l *NOThe sourcemember is not replaced if it already exists. An error message is sent.

l *YESThe sourcemember is replaced if it already exists.

Removequalifiednames(RMVQUAL)

Remove all SQL object qualifications (library names) from the source.

l *YESThe generated source will no longer contain any qualifying library names.

l *NOTable 16: The ACVTDDSSQL command parameters (Conversion Process properties)

ARCAD-Transformer DB v13.1User Guide | The ACVTDDSSQL command




The library names qualifying certain SQL objects are kept.


Warningmessages(WNGMSG)

Import warning messages into the source. Thesemessages are stored in a file to be subsequently used for other conversion operations.Specify whether you want thesemessages to also be inserted into the SQL source.

l *YESThewarning messages are inserted into the SQL source as comments in the form: -- *NOTSQL MSGMessage-text

l *NOThewarning messages are not inserted into the SQL source.


Retrievecommentsfrom DDS(RTVDDSCMT)

Import DDS comments into the SQL source.

l *YESComments are retrieved from the DDS source. In this case, the sourcemember must exist in the file specified in parameter DDS sourcefile (DDSSRCFILE). Otherwise, the value *NO is used.

l *NOComments are not retrieved from the DDS source.


Work withsharedformats(SHRFMT)

Some physical files share the format of another physical file (FORMAT keyword in the DDS). Specify if you want to convert the DDS from theshared format or define the fields explicitly in the SQL source.

l *YES






If necessary, the conversion is done from the shared format. In this case, the sourcemember must exist in the file specified in parameterDDS source file (DDSSRCFILE). Otherwise, the value *NO is used.

l *NOEven if there is a shared format, the fields are defined explicitly in the SQL source.


DDS sourcefile(DDSSRCFILE)

Specify the name of the source file and the library for the DDS to convert.

l *OBJThe name of the source file and the library for the DDS are retrieved from the object attributes.

l *LSTWhen processing a list, the name of the file is retrieved from the Source File field and the library from the Library field, if they aresupplied.


Work withreferencefields(REFFILE)

Indicate whether to define the fields from their reference file, where specified. If not, fields are defined directly in the SQL source instead offrom the reference.

l *YESReference fields are defined based on reference fields.

l *NOReference fields are no longer defined by referencing other fields, they are defined explicitly in the SQL source.


Keep CCSIDattribute Specify the process used for CCSID attributes.






(CCSIDOPT)

l *YESKeyword CCSID is always added to alphanumeric fields.

l *NOKeyword CCSID is never added.

l *NOTPFKeyword CCSID is set only if it is different from the file.


RenameFields(RNMFLD)

An additional benefit of the transformation process is that you can rename short name fields and/or add long name fields. Indicate the typeof renaming to use.*NO: No fields are renamed.*NAME: Only Short Names can be renamed.*ALIAS: Only Long Names can berenamed.*BOTH (names and aliases): Both Short and Long Names can be renamed.


File longname(LONGNAME)

Enter a long name (up to 70 characters) for the SQL file.

l *NONEThe file does not have a long name.

l *LSTWhen processing a list, the long name is retrieved from theAlias field.

l Enter the long name for the SQL file.

Table/Indexgenerationlabel(FILELABEL)

Generate the statement "File label on table" or "File label on index".

l *NOThe "File label on table" or "File label on index" statement is not generated. The component text is editable directly in ARCAD-Skipper; itdoes not need to be included in the sourcemember






l *YESThe "File label on table" or "File label on index" statement is generated.


Share PFformat if LFsame fields(LFSHRPFFMT)

Only the logical files that have the same format as the physical can be converted. If the formats are different a diagnosticmessage isgenerated and the conversion is not completed. However, if the two files have exactly the same fields, unmodified, in the same order, this isa special case only the format name/reference is different, the conversion is possible. In this case, parameter LFSHRPFFMT specifies whetherto perform the conversion.

l *YESIf a logical file has a different format than the physical, but with exactly the same fields, unmodified, in the same order, it will beconverted to an INDEX. The keyword "rcdfmt" is generated with the logical file format name.

l *NOIf a logical file has a different format name than the physical, even if the fields are exactly the same, not modified, in the same order, itwill be not be converted to an INDEX.


ReferentialConstraints(REFCST)

The IBM command ADDPFCST allows for the addition of referential constraints to a physical file.

l *YESThe referential constraints are retrieved and applied using an "Alter table" SQL instruction.

l *NOThe referential constraints are not retrieved.







CheckConstraints(CHKCST)

The IBM command ADDPFCST allows for the addition of check constraints to a physical file.

l *YESThe check constraints are retrieved and applied using an "Alter table" SQL instruction.

l *NOThe check constraints are not retrieved.


Action if PFkey problem(PFKEYACT)

Sometimes, the conversion cannot set the key of the SQL TABLE identically to the DDS PF key. This is the case when the DDS PF key is notunique or when the keywords FCFO, FIFO or LIFO are used.

This parameter defines the action to be taken when this problem occurs.

l *NONEThe TABLE is generated without a key. No INDEX or LF is generated.

l *PRIKEYThe same PRIMARY KEY is created in the TABLE even if there is a risk of creating duplicate keys.

l *INDEXThe TABLE is generated without a key. A new INDEX is generated with the key of the DDS PF. The name of the new INDEX is specifiedin the New file name to create (NEWFILE) parameter.

l *LFThe TABLE is generated without a key. A new LF is generated with the key and, if necessary, the keywords (FCFO, FIFO or LIFO) fromthe DDS PF. The name of the new LF is specified in the New file name to create (NEWFILE) parameter.

l *LSTWhen processing a list, the action to be taken is retrieved from the field "Selection-2" (positions 1 to 10) if it is provided.






New filename tocreate(NEWFILE)

If the Action if PF key problem (PFKEYACT) field is set to *INDEX or *LF, specify the name of the new INDEX or LF to be created.

l *LSTWhen processing a list, the name of the new file is retrieved from the Selection-2 field (positions 11 to 20), if it is provided. If the namedsourcemember already exists, the value of the Replace if existing (REPLACE) parameter determines if it should be replaced.

l Enter the name of the file.

Action ifmultiplemembers(MULTIMBACT)

A PF file can bemulti-member (parameter MAXMBRS > 1). This notion does not exist for the SQL TABLEs. Define the action to be takenwhen this problem occurs.

l *NOTSQLThe TABLE is not generated. The file remains amulti-member PF.

l *ONEMBRThe TABLE is generated. Themembers are not managed.

l *MBRFLDThe TABLE is generated but a new field is added at the beginning to simulate themembers management. The field characteristics arespecified in the Info new field for multi-mbrs (MULTIMBINF) parameter.

l *LSTWhen processing a list, the action to be taken is retrieved from the Selection-3 field (positions 1 to 10) if it is provided.

Info new fieldfor multi-mbrs(MULTIMBINF)

If the Action if multiplemembers (MULTIMBACT) field is set to *MBRFLD, the following options are activated which define thecharacteristics of the field to be added.

Field name

l *LSTWhen processing a list, the field characteristics are retrieved from the Selection-3 and Selection-8 fields if they are provided.

l Enter a name for the new field.






Field type

l CHARl DECIMALl NUMERICl INTEGER

Field length

Enter a number between 1 and 99.

Description

l *DFTThe default text related to the field is "New field for replacement of multi-mbr".

l Enter the text to describe the new field.

Field long name (Alias)

l *NONEThere is no long name of the new field.

l Enter the new field long name.

Model Field Name

l Select or enter the name of the existing PF that should serve as a template.

*FILEattributes toimpose(FILEATR)

The CRTPF, CRTLF, CHGPF and CHGLF commands enable you to changemany attribute values for PF and LF files. These values may be differentfrom the TABLE's and INDEX's default values and cannot be preserved by default during the conversion.

Use this parameter to force these values and to apply them after the TABLE or INDEX is created. The instruction "%EXECA CHGPF/CHGLFFILE(&O/&N)" is inserted with the specified attributes list in the generated source.






l *NONENo attribute is preserved. The TABLE or INDEX is converted with the default attributes.

l *LSTWhen processing a list, the attributes are retrieved from the Selection-9 field if it's provided in the form "FILEATR(ATTR1 ATTR2ATTR3)".

l Enter up to 20 attributes.

DecimalPoint (DECMPT)

Specify the character to use as the integer/decimal separator, if numeric literals exist in the generated source. See in-line help for IBMcommand RUNSQLSTM for more information.

Indicate the type of decimal separator.

l *PERIODl *COMMAl *JOB (use the format defined in the JOB)l *SYSVAL (the system value)


Updatetransfer log(UPDTFRLOG)

Specify whether to update the transfer log (*YES) or not (*NO).





The ACHKFILDTA and ACHKDBRFLD commands

The ACHKFILDTA command checks the integrity of data stored in database files or in journals. This Data Integrity Check is intended to verify that the datainside your database's PF files are accurate according to field type. This largely concerns numeric zones that contain non-numeric characters.

The ACHKDBRFLD command checks the integrity of the links (incoming and outgoing) of a file in your database or its journal. This Database Links IntegrityCheck is intended to verify that the reference links are accurate.

If an option has an out-of-the-box default value, it is indicated in bold in the tables below. You can change the default values in the Preferences menu.

ReferenceFor more information about using these commands, refer to Verifying data integrity on page 56.

For more information about changing the default commands, refer to Configuring the ARCAD-Check Data Integrity defaultparameters on page 33.

Parameters common to the ACHKFILDTA and ACHKDBRFLD commandsThe following table includes a brief explanation of each of the parameters that the ACHKFILDTA and ACHKDBRFLD commands share. Many of the parameterschange the subsequent options available. When the ACHKFILDTA command is run in *DATAmode, only these parameters are included in the Check dataintegrity execution dialog.

Parameter group Field (command) Description

General Search library (FILE)

The name of the library in which to find the file(s) to check.

NoteDepending on the value defined for thisparameter, certain parameters will beavailable or hidden later in the wizard.

l Enter the name of the library in which to search for the file(s).l *LIBLThe file is searched for in the libraries that belong to the IBM i's currentlibrary list. The parameters Exclude libraries (OMTLIB) and ASP group

Table 17: The ACHKFILDTA and ACHKDBRFLD common parameters

ARCAD-Transformer DB v13.1The ACHKFILDTA and ACHKDBRFLD commands | User Guide




for libraries (ASPGRP) are enabled.l *INCLIBThe file to check is searched for in the libraries listed in the Includelibraries (INCLIB) parameter. The ASP group for libraries (ASPGRP) isalso enabled.

l *ENVLIBLThe file to check is searched for in the libraries that belong to theoperational libraries of the application's environment. The parametersEnvironment Origin (ENV) and the Exclude libraries (OMTLIB) areenabled.

l *ENVOPELIBThe file to check is searched for in the libraries that belong to theoperational libraries of the Arcad application. The parametersEnvironment Origin (ENV) and the Exclude libraries (OMTLIB) areenabled.

Description text (TEXT) Enter a description to define the command execution.

Add OK value fields (INCOKVAL)

Define which values are displayed when errors are found.

l *YESAs soon as an error is detected, all of the zones are displayed.

l *NOOnly the values with errors are displayed.

Decimal character separator (DECCHAR)

Define the character that should be used as the decimal separator in thenumeric fields that are to be checked. If the character defined is not usedcorrectly in the fields checked, the systemwill report an error.

l ‘.’

l Enter a character separator


ARCAD-Transformer DB v13.1User Guide | The ACHKFILDTA and ACHKDBRFLD commands




Environment Origin(ENV)

Application Id The ID of the application in which the file(s) are found.

Environment Id

The ID of the environment in which the file(s) are found.

l *CURENVThe last environment used

Version no The number of the version in which the file(s) are found.

Libraries

Exclude libraries (OMTLIB) Enter the name(s) of the library(ies) to exclude from the check.

Include libraries (INCLIB) Enter the name(s) of the library(ies) to include. If the check is made on the*LOCAL Site (SITE), these librariesmust already exist.

ASP group for libraries (ASPGRP)

Enter the name of the ASP group required for the libraries.

l Enter the name of the principal ASP of the group. All of the libraries inall of the ASPs in this group are included.

l *SYSBASThe files are searched for in the libraries that are NOT associated with anASP group.

Site (SITE)

Select the site on which to execute the action.

NoteThe Execution Mode (MODE)may beautomatically defined depending on thevalue defined for this parameter.

l Select the name of the site from the drop-down list. The check is alwaysrun in batch mode and all three of the submission attribute groups areavailable (SBMATTR, RMTSBMATTR and RCVSBMATTR).

l *LOCALThe local site. The check can be run in either batch or interactivemode.






Only the Batch Mode Preparation Attribute Parameters (SBMATTR)submission attribute group is available.

l *REMOTEOnly used when generated automatically for a remote execution.

Execution Mode (MODE)

Define how to execute the check.

l *BATCHThe check is done in batch mode. The Batch Mode Preparation AttributeParameters (SBMATTR) submission attribute group is available. Batchmode allows you to the follow the execution progress.

l *INTERThe check is done in interactivemode. This option is only available whenthe check is run on the *LOCAL Site (SITE).

l *REMOTE

Batch ModePreparation AttributeParameters (SBMATTR)

These parameters are available if the check is run on the *LOCAL Site (SITE) in batch mode. They define the job submissionparameters on the local machine.

Start date DDMMYYY

l *IMMEDThe submission is immediate.

l Enter a date in DDMMYYY format. The submission is run on the dateentered. The datemust be in the future.

Start time HHMMSS


l Enter a time in HHMMSS format. The submission is run at the timeentered on the date set in the Start Date field. The timemust be in thefuture according to themachine's date.

Job (JOB) Define the job name.Table 17: The ACHKFILDTA and ACHKDBRFLD common parameters





l *JOBDThe same as the Job description (JOBD).

l Enter a name.

Job description (JOBD)

Define the job description.

l *USRPRFThe system uses the job description defined in the current user profile'sparameters.

l Enter a description.

Job description library

l *LIBLThe job description is looked for in all of the libraries until the firstdescription with that name is found.

l *CURLIBThe job description is looked for in the current library. If no library iscurrently defined, the QGPL library is used by default.

l Enter the name of the library that contains the job description.

Job queue (JOBQ)

Define the name of the job's queue.

l *JOBDWhen launched the job is placed in the Job description (JOBD) queue.

l Enter the name of a job queue.

Job queue library

l *LIBLThe job queue is looked for in all of the libraries until the first queue withthat name is found.

l *CURLIBThe job queue is looked for in the current library. If no library iscurrently defined, the QGPL library is used by default.






l Enter the name of the library that contains the job queue.

Job priority 1-9 (in jobq) (JOBPTY)

Define the submission's priority in the job queue.

l *JOBDThe priority described in the Job description (JOBD) is used.

l Enter a number (1-9) to define the priority level. 1 is the highest and 9 isthe lowest.

Output priority 1-9 (in jobq) (OUTPTY)

Define the output priority for spooled files produced by the job.



Other submission parametersl *NONEl Enter any number of complementary attributes supported by the

SBMJOB command.

Preparation macrogroup parameters(PRPMACRO)

These parameters are available if the check is NOT run on the *LOCAL Site (SITE). This macro executes on the local machine andprepares the transfer library. It also remotely launches the Remotemacro group parameters (RMTMACRO).

Preparation macro namel SNDCMPDTAThe ARCAD standard macro.

l Enter a macro to replace the standard.

Preparation macro library

l *REFLIBThe "reference" library in the ARREFLIB data area is used.

l *LIBLThemacro will be looked for in the online libraries.

l *CURLIBTable 17: The ACHKFILDTA and ACHKDBRFLD common parameters





Themacro will be looked for in the current library.l Enter the name of a library.

Remote macro groupparameters (RMTMACRO)

These parameters are available if the check is NOT run on the *LOCAL Site (SITE). This macro executes on the remotemachine tolaunch the integrity check and return the results (in the form of updated ARCAD files) to the local machine. If this macro doesn'talready exist on the remotemachine, it can be sent to it.

Remote macro name

l RMTCMPDTAThe ARCAD standard macro.

l Enter a macro to replace the standard.

Remote macro library

l *REFLIBThe "reference" library in the ARREFLIB data area is used.

l *LIBLThemacro will be looked for in the online libraries.

l *CURLIBThemacro will be looked for in the current library.

l Enter the name of a library.

Send macro (SNDMACRO)

If a remote site is used, the remotemacro must be launched on the remotesite. If this macro-command doesn't exist on the remote site, it must be sentthere. Define if the remotemacro must be sent to the remote site, or not.

l *NOThe remotemacro is not sent to the remote site.

l YESThe remotemacro is sent to the remote site.

Batch Parameters forremote execution(RMTSBMATTR)

These parameters are available if the check is NOT run on the *LOCAL Site (SITE). They define the job submission parameters onthe remotemachine.

Delete transfer library (DLTTMPLIB) If executed on a remotemachine, the process uses a job library to transferTable 17: The ACHKFILDTA and ACHKDBRFLD common parameters





the data from one site to the other. This parameters enables you to definewhether or not this library is saved at the end of each transfer.

Tick this checkbox to remove the library after the remote results aretransferred back to the current machine.

Start date DDMMYYY



Start time HHMMSS



Job (JOB)

Define the job name.


l Enter a name.





Job description libraryl *LIBLThe job description is looked for in all of the libraries until the firstdescription with that name is found.








Job queue (JOBQ)




Job queue library


















SBMJOB command.

Batch parameters forreceiving from remoteexecution (RCVSBMATTR)

These parameters are available if the check is NOT run on the *LOCAL Site (SITE). They define the parameters for the reception ofthe check results and the log (sent from the remotemachine to the local machine).

Start date DDMMYYY



Start time HHMMSS



Job (JOB)

Define the job name.


l Enter a name.





Job description library l *LIBLTable 17: The ACHKFILDTA and ACHKDBRFLD common parameters





The job description is looked for in all of the libraries until the firstdescription with that name is found.



Job queue (JOBQ)




Job queue library


















SBMJOB command.


Parameters specific to the Integrity Violation Check (ACHKFILDTA) in *JRN modeWhen the ACHKFILDTA command is run in *JRNmode to search a file's journals and not the current data, the following parameters are required in addition tothe parameters defined in Table 17: The ACHKFILDTA and ACHKDBRFLD common parameters.





Journal entry logdate (PERIOD)

Define the time period for which you want to analyze the journal entries.

Start Date

l *OBJINFThe start date is provided by the file's description and corresponds to either the beginning of thejournalization or the last modification to the file's structure.

l *CURRENTToday's date.

l *BEGINThere is no beginning date selected.

l Enter a date in the future.

Start Hour

l *AVAILThere is no beginning hour defined. This is the only available value if the Start Date is set to *OBJINF or*BEGIN.

l Enter a time in the future in HHMMSS format.

End Date

l *CURRENTToday's date.

l Enter a date in the future. The format must correspond to the format in the job.

NoteThe end date is not available for the Database Constraints Integrity Check(ACHKDBRFLD) command because themost recent journal entries for linkverification are always taken into account.

End Hourl *AVAILThere is no ending hour defined.

l Enter a time in the future in HHMMSS format.

Table 18: The ACHKFILDTA and ACHKDBRFLD *JRN mode parameters




Parameters specific to the Database Constraints Integrity Check (ACHKDBRFLD)


Max numberof records perfile

Themaximum number of records to check will impact the time it takes to carry out the command. 200 is the suggested amount of records tocheck. If there are errors in more than 200 records in a file it is recommended to stop the check and fix the file manually before performingthe check again.

l 200l Enter a number.l *NOMAXThis value is NOT recommended.

Table 19: The ACHKDBRFLD-specific parameters




ARCAD-Transformer DB v13.1List of diagnostic messages | User Guide

List of diagnostic messages

MSG4001 P REUSEDLT(*NO) not retrievedMSG4002 P/L ALTSEQ(&1) not retrievedMSG4003 P/L Parameter &1 not supportedMSG4004 P/L FRCRATIO(&1) not retrievedMSG4005 PMAXMBRS(&1) not supportedMSG4006 P/L LVLCHK(*NO) not retrievedMSG4007 P/L WAITFILE(&1) not retrievedMSG4008 P/L WAITRCD(&1) not retrievedMSG4009 P/L ACCPTHSIZ(*MAX4GB) not retrievedMSG4010 P Field &1 : EDTCDE(&2) not supported AC01MSG4011 P Field &1 : EDTWRD(&2) not supported AC01MSG4012 P Field &1 : DATFMT(&2) not supportedMSG4013 P Field &1 : DATSEP(&2) not supportedMSG4014 P Field &1 : TIMFMT(&2) not supportedMSG4015 P Field &1 : TIMSEP(&2) not supportedMSG4016 P Field &1 : REFSHIFT(&2) not supported AC01MSG4017 P Field &1 : REFFLD(&2) not supportedMSG4018 P Field &1 : Field used as key not uniqueMSG4019 P SIZE(&1) not retrievedMSG4020 L The logical file format is different to the physicalMSG4021 L The SQL generation is impossibleMSG4022 L The logical file has multiple formatsMSG4023 P/L PAGESIZE(&1) not retrievedMSG4024 P/L MAINT(&1) not retrievedMSG4025 P/L RECOVER(&1) not retrievedMSG4026 L The logical file is a join fileMSG4028 P/L Field &1 : Parameter &2 not supportedMSG4029 P/L Field &1 : Parameter &2 not supported AC01MSG4030 P/L FRCACCPTH(*YES) not retrievedMSG4031 P/L ALLOCATE(*YES) not retrievedMSG4032 L FMTSLR(&1) not retrievedMSG4033 P/L UNIT(*SSD) not retrievedMSG4034 PDLTPCT(&1) not retrievedMSG4035 P Field &1 : Type &2 changed to equivalent &3MSG4036 P Field &1 : Type &2 increased as integer of type &3MSG4037 P Field &1 : Type &2 converted to equivalent &3MSG4038 P Field &1 : Non-unique key set to uniqueMSG4039 P Field &1 : Non-unique key generated as INDEX &2MSG4041 P Field &1 : Non-unique key generated as LF &2MSG4042 P Field &1 : &3 generated as INDEX &2MSG4043 L Parameter &1 not supportedMSG4044 P/L Field &1 : Parameter &2 not supportedMSG4045 P Constraint &1 of type &2 not supportedMSG4047 P Field &1 : REFFLD(&2)managed by the conversionMSG4048 P Format shared with &1MSG4049 PMulti-members PF converted in mono-member TABLEMSG4084 P Format level id changed : format of binary field have changedMSG4085 P Format level id changed : referenced fields are used



ARCAD-Transformer DB v13.1User Guide | List of diagnostic messages

MSG4086 P Format level id changed : field added for themulti-memberMSG4091 PMulti-members PF converted with addition of the specific fieldMSG4092 P The SQL generation is impossibleMSG4100 P/L Successful conversion without warningsMSG4105 P Constraint &1 of type &2managed on TableMSG4109 L Logical file without key impossible to convert as INDEXMSG4110 P Physical file with keyMSG4111 P Physical file without keyMSG4112 L Logical file with select/omitMSG4113 L Logical file without select/omitMSG4117 P/L KEEPINMEM(*YES) not retrievedMSG4118 P/L SHARE(*YES) not retrievedMSG4119 P REUSEDLT(*NO) imposed as attributeMSG4121 P/L FRCRATIO(&1) imposed as attributeMSG4122 P/L LVLCHK(*NO) imposed as attributeMSG4123 P/L WAITFILE(&1) imposed as attributeMSG4124 P/L WAITRCD(&1) imposed as attributeMSG4125 P/L ACCPTHSIZ(*MAX4GB) imposed as attributeMSG4126 P SIZE(&1) imposed as attributeMSG4128 P/L MAINT(&1) imposed as attributeMSG4129 P/L RECOVER(&1) imposed as attributeMSG4130 P/L FRCACCPTH(*YES) imposed as attributeMSG4131 P/L ALLOCATE(*YES) imposed as attributeMSG4133 P/L UNIT(*SSD) imposed as attributeMSG4134 PDLTPCT(&1) imposed as attributeMSG4135 P/L KEEPINMEM(*YES) imposed as attributeMSG4136 P/L SHARE(*YES) imposed as attributeMSG4143 L The LF fields are identical to PF fields but the format isMSG4144 L LF converted as INDEX with a different format name



ARCAD-Transformer DB v13.1Glossary | User Guide

Glossary

AB C D E FG H I J K LMNO PQ R S T U VW X Y Z

A

aggregated resultsSee audit reports.

aliasSee names.

auditSee conversion audit.

audit reportsReports generated with the conversion audit that show the results of the audit. There are twotypes of audit reports:

l A global report that includes an aggregated list of all themessages for every file in aconversion list (Conversion Audit view).

l A file-specific report that enables you to check the problems for each individual file in aconversion list (DDS File Conversion view).

See also conversion audit.

B

C

componentsAlso database components. Physical or logical files that constitute your source database. Theyare listed the Component Repository view.

See physical file [PF] and logical file [LF]. See also dependent components.

conversion auditA tool that detects potential problems for the conversion process (impossibility to convert,problems concerning primary keys or multi-members files, and problems with attributescontained in files that are not compatible and cannot be transformed into SQL sources).

The audit checks the entire contents of your transformed files and generates a report pointing tothe corrupted records, organized by category. See audit reports.



ARCAD-Transformer DB v13.1User Guide | Glossary

Manually perform the actions required to resolve any problems that occurred during thesimulation in order to ensure that the same problem is solved when the file is validated and thefinal transformation is carried out. See engines.

This ensures the integrity of the data contained in the transformed files. See data integrity.

conversion listThe list of physical and logical files in DDS format to transform into SQL format.

conversion projectA group of assigned parameters to apply to a conversion list which contains the IBM i artifacts totransform.

conversion simulationA primary transformation performed outside of the target version as a simulation. No final modi-fications aremade and no TABLE or INDEX files are generated. The simulation is carried out inorder to audit the files and ensure they are valid and can be transformed. See conversion audit.

conversion validationThe final step of the transformation process. Validate the transformation of the physical andlogical files to tables and indexes and themodifications to the dependents, in order to transfer allof the transformed and/or modified files and components to an ARCAD version and apply themodifications in the target version.

D

data integrityA tool that performs checks on data to evaluate the integrity of the your files or the links in thedatabase.

DDLData Definition Language.

DDSData Description Specifications.

dependent componentsFiles that refer to source physical or logical files, such as programs (*PGM), service programs(*SRVPGM), printer files (*PRTF) or display files (*DSPF).




E

enginesWhen components are transformed, their active dependents are updated accordingly. ARCAD-Transformer DB analyzes automatically the impact on the dependent components. Use enginesto solve the issues detected by the analysis. Once they aremanually launched, the changes to thedependent components aremade automatically.

See also dependent components.

F

field nameSee names.

G

H

I

indexA data structure that allows you to search for rows of a table, typically by forming a tree structure(B-tree) representing all the values of a particular column or set of columns.

Tables always have a clustered index representing the primary key. They can also have one ormore secondary indexes defined on one or more columns. Depending on their structure,secondary indexes can be classified as partial, column, or composite indexes.

Indexes are a crucial aspect of query performance. Database architects design tables, queries,and indexes to allow fast lookups for data needed by applications.

See also logical file [LF] and table.

integritySee data integrity.




J

K

L

logical file [LF]A database file that describes how data is to be presented or received from a program. A logicalfile contains no data, but it defines record formats for one or more physical files.

long namesSee names.

M

N

namesSQL enables field names to bemuch longer than DDS. ARCAD-Transformer DB allows therenaming of the (short) field names and the (long) field aliases in a DDS file that you are con-verting to SQL.

O

P

physical file [PF]A database file that describes how data is to be presented or received from a program and howdata is actually stored in the database. A physical file contains one record format and one ormoremembers.

primary keyA key that uniquely identifies one row of a database table.

Q

R

reportsSee audit reports.




S

short namesSee names.

simulationSee conversion simulation.

SQLStructured Query Language. A standardized language for defining and manipulating data in arelational database.

T

tableA table is the SQL file type corresponding to the DDS physical file.

See also physical file [PF] and index

transformation simulationSee conversion simulation.

U

V

validationSee conversion validation.

view, viewsWorkspaces within the ARCAD-Transformer DB perspective, that correspond to the differentsteps of the ARCAD-Transformer DB process.

l The Transformer DB Explorer viewl The Conversion Projects viewl The Component Repository viewl The Transformation Process view

l The DDS File Conversion List viewl The Conversion Audit: Aggregated Results viewl The Engine Execution viewl The Conversion Validation view

l The Renaming Fields view




W

working libraryA library created with each conversion project to store the various files needed for the con-version, including a job list of files impacted by the project, and the SQL source code of the con-verted files prior to validation.

X

Y

Z



ARCAD-Transformer DB v13.1F.A.Q. | User Guide

F.A.Q.

If the integrity check feature is going to be used, it uses the journal to grab information aboutthe data to determine what programs may be responsible for writing bad data to thefiles/tables. What journal is being used and how long does it need to be turned on in order togather the information needed for this feature?When we launch the process, we can choose the period (begin and end date/time) for the journal. Thejournaling must have been activated at least during a period, and the journal data must be left on thesystem.

Is the processing involved in scanning the database for bad data done interactively or in batchor can we choose which environment to run the process?All of these options are available since v10.06.

Does ARCAD-Transformer DB handle COBOL long field names in the refactoring?No.

Can we define a list of valid values for the integrity check so they do not show up as bad data?No. The ‘Data integrity check’ is, for themoment, only to check corrupted data (numeric fields thatcontain non-numeric data).

What are the reasons for recompiling the programs or not? When we do not is it true that norecompile objects appear in the version?ARCAD-Skipper has many feature to help you to recompile the dependent programs, but they could benot-recompiled, only when the FMTLVL id doesn’t change (same on PF and TABLE).

How does ARCAD-Transformer DB work with SYNON generated files/table? SYNON creates 2logical files for example with an extension of a 0 and a 1. What will ARCAD-Transformer DB dothat can accommodate SYNON specific items?There will be 2 INDEXes corresponding to the 2 old LFs.

How does ARCAD-Transformer DB convert an existing PF with multi-members to a new TABLE(DDL)?When we choose *MBRFLD:

For each “member name”, we choose to add a field that contains the same “notion”. This field will beadded in the TABLE's key. To manage this wemust

l give a name (and type, length) for this new field;l indicate the name of another existing field in the old file that could be a “model”.

Then the engine will mark:



ARCAD-Transformer DB v13.1User Guide | F.A.Q.

l all the uses of the “file name”, in CLP (where wemanage them for OVRDBFwith themembername…);

l all the uses of the old field.

With this, the developer must continue and complete themodification.

ReferenceRefer to Resolving problems prior to transformation (conversion audit)on page 67.



Documents

User Guide - ARCAD Transformer DB Online Help