VisualAge Generator to Enterprise Generation Language Migration Guide

XFER

VisualAge Generator: The XFER statement can be used with both maps and UI records to send output to the user and then transfer to another program or transaction when the user enters input data.

EGL: The show statement is used for sending a form to the user at a terminal and then transferring to another program or transaction when the user enters input data. This release of EGL does not support web transactions, UI records, or a replacement for XFER with a UI record. However, the forward statement is expected to be the replacement for XFER with a UI record. The forward statement is used for sending a UI record to a user in a browser window and then transferring to another program or transaction when the user enters input data.

Associated part needed for migration: Map that is used in the XFER statement. If a map with the name specified on the XFER statement is not available, the migration tool converts the XFER statement as described in the Migrating without the associated part column of the following table.

Figure 51. XFER

Migrating with the associated part
Migrating without the associated part
Based on the first migration of this function, the tool migrates as follows:
  • If the second argument is a map, the tool migrates to a show statement.
  • If the second argument is a UI record, the tool migrates to a forward statement.
If the map or UI record is not available, the migration tool does the following:
  • If (NONCSP is included on the XFER statement, the tool migrates to a show statement.
  • If the target of the XFER is ' ', the tool migrates to a forward statement.
  • If the name of the second argument is longer than 8 characters, the tool migrates to a forward statement because only UI records can have a name longer than 8 characters.
  • If the name of the second argument is 8 or fewer characters, the tool migrates to the forward statement because XFER with a UI record is more common than XFER with a map. The tool also issues a warning message.

Potential Problem: A problem arises for any program that uses a UI record when the migration tool migrated based on a map or vice versa. Preprocessing for the program will fail.

Solution: If the function was migrated based on a map, create a second function that contains the forward statement for the UI record. Change any program that uses a UI record to use this new function. This has the potential to ripple back into any function that invokes the original function.

The same problem listed under the Migrating with the associated part column can occur. You can use the same solution.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]