|
ASNA WingsRPG™ Reference Manual |
Using ASNA Wings™ Flight Plans
ASNA Wings Flight Plans is a modernization tool integrated into Visual Studio that helps detail of the interrelations of source components (RPG source files and Workstation files) and helps prepare and convert them into .aspx pages. This assists the user in considering and managing bulk modernizations, as well as providing a convenient visual interface and framework for smaller operations. Its main functions are to:
- Help the user visualize the application through the Flight Plan window.
- Help the user organize and segment the application to achieve an ordered modernization using Flight Plan tags.
- Modernize arbitrarily-large groups of display files at a time according to user defined criteria.
- Inject the Handler keyword (
ASNAWINGS) into those RPG sources whose displays have been modernized. - Keep track of which sources, RPG or DDS, have been modernized.
What Flight Plans Can Do
Users can perform a variety of actions with Flight Plans to manage and manipulate their data, a short list of key operations includes:
- Create a Flight Plan.
- Open an existing Flight Plan.
- Add members to a Flight Plan.
- Modernize members:
- Search for a source member in a group of IBM i libraries.
- Define Tags which can be applied to individual source members or groups.
- Group Flight Plan members by Tag value.
- Create and save multiple Groupings to visualize the project more effectively.
- Save a Flight Plan file (.wflp).
Getting Started with Flight Plans
The following are some steps you may want to take when first working with Wings Flight Plans.
Create a new Flight Plan through Visual Studio.
Click the icon that looks like a file with a plus sign (
) to add source members.
Pick your server, files, and members using the built-in
dialogs, and Wings will populate the Flight Plan Window
with your selections.Click on the tag icon (
) to create some
tags that will help you organize your
sources. For example, you may wish to sort your members by the Developer
assigned to a project, which Department they impact, or
which Application they're part of.Click the page-and-pencil icon (
) to open the
edit tags dialog and globally set values for the
key modernization tags by customizing their default values.-
Select members or files from the source view tree on the left and use the Tag Value frame on the right to individually set the key modernization tags for files that need special treatment.
-
Click the list icon (
) and Group the sources
by their tag values. Select a tag from the list on the
left and click the right-arrow on the screen to set it
as a level of the nested grouping, then use the up and
down arrow to select which levels of nesting are higher
or lower. Once the organization is satisfactory, select a group of nodes to convert from the source tree, right click, and then select convert. This will open the Convert Selected Nodes dialog. Some important options can be set here, such as any tag values to change to indicate successful or failed conversion. Click OK.
Wings will attempt to convert the selected nodes into the appropriate format, providing feedback of the process through Visual Studio.
Hint – Wings Flight Plans is designed to be a flexible tool, and your modernization may use only one Flight Plan or it may require many more. As a loose guideline, you should create one Flight Plan for, at most, every 500 full programs to be included. You may also want to create a seperate Flight Plan for each Wings site (one for accounting, one for shipping, one for customer service, and so forth) if you're working with a substantial number of programs. If you create user tags and groupings that are especially suited to multiple projects you can move them from one Flight Plan to another by importing some XML elements from their Flight Plan Schemas.