Overview
Large iSeries applications can have hundreds of screens defined. The mapping of the static text, dynamic data fields and other screen characteristics can be tedious if performed manually. The iSeries Source Capture tool automates the capture of the relevant definitions found in existing iSeries source modules. By automating the capture of definitions, projects benefit from lower cost as well as ensured accuracy of the resulting application model.
Many iSeries applications have source code available that describes the screens in the application as well as the logic. When the source is available for the screen layouts, known as Display Data Description Specifications (DDS), a new plug-in module for Screen Viewer Studio will provide capture of the information in the source as well as ongoing change management.
- The Source Capture utility maintains one or more folders corresponding with iSeries source libraries.
- The Import, Bind and Sync Wizards manage the relationship between the captured source definitions and the Flynet Viewer screen definition files.
- Capture of the definitions as well as synchronization and change management is automated; higher productivity and reduced errors are the result.
Source Capture
Full development life-cycle benefits are achieved. Starting with the automated capture of existing screen definitions the iSeries Source Capture and Change Management feature then continues to add value with the detection and synchronization of changes to the host application.
Using an FTP customized for use with the iSeries FTP support, the source capture facility can create any number of iSeries source folders on the developer's workstation. Each source folder is associated with a corresponding iSeries library, so that multiple libraries as well as multiple iSeries systems can be supported from a single developer's desktop.
From each library, the developer can chose which modules to download and keep track of using the change management facility. Using a strong encryption capability, the FTP userid and password are stored in the target folder in a properties file, so that ongoing checks (for change management purposes) can be made in batch mode. This ensures that changes affecting the application can be caught automatically without the need for the developer to initiate a "check" on the host source.
Import Wizard
Using the source modules maintained on the workstation, a plug-in "Wizard" for the Flynet Viewer Studio provides the ability to run a customized parser through the source, identifying all screen definitions and providing the necessary resolutions for externally defined fields. The definitions from the DDS source are then used to create Screen, FieldMap, Field and Label definitions.
A rules-based engine is then run on the imported Screens to automate and optimize grouping and recognition of the screens. The grouping and recognition engine uses an external file that can be optimized by the developer to modify the provided rules as well as add additional rules. An example of a grouping rule is to group all menu display screens into one group named "Menus".
The result is a screen definition file fully editable in the Flynet Viewer Studio for further management. For example, field names can be quickly and easily "upgraded" from their typically cryptic iSeries form to one friendlier to developers on the modernization project. A separate property, ExtName is maintained from the original import operation so that the Sync Wizard can be used at a later time.
Bind WizardFor existing definitions, the Bind wizard can be used to match DDS-defined screens to the corresponding screens, fieldmaps and fields. The bind wizard uses the recognition criteria in the definition to match screens between the two sources. It then uses field location and length to match individual fields. The ExtName property, a new property introduced in Flynet Viewer 4 definitions, is then set in order to facilitate later use of the Sync Wizard.
Sync Wizard
The Sync Wizard uses a linkage file that matches existing screen definitions in a definition file with one or more DDS folders. When the Sync Wizard is run, any changes in the DDS files are reflected against the corresponding screens, fields and labels in the definition file. An example of a change would be one or more fields moving on the screen. Using the ExtName property set with either the Import or Bind wizard, the Sync Wizard will update the field locations without manual intervention.
Action Reports
Each wizard produces an HTML-based report of each execution, so that results can easily be monitored and understood by members of the development team.
Ongoing Development Life-Cycle Benefits
The Sync Wizard can also be run in batch mode, driving the source capture objects to:
- Identify and download any iSeries source modules with a date more current than the last download
- Differencing the files downloaded against a reference folder
- For any files that have differences, running a sync operation to update any definitions affected by the change
- E-mailing the Sync HTML report link to one or more email addresses at completion
< Previous >