VisualAge Generator to Enterprise Generation Language Migration Guide

EZESYS

VisualAge Generator: EZESYS is generally used in IF, WHILE, and TEST statements with literal values specified by VisualAge Generator. However, EZESYS is permitted in other statements.

EGL: The EGL system variable systemType has different values from VisualAge Generator. When EZESYS is used in statements other than IF, WHILE, and TEST, the migration tool does not know what values the program might be expecting and so must use the original VAGen values. The EGL system library function getVGSystemType provides the old VAGen values.

Associated part needed for migration: Not applicable.

Figure 52. EZESYS

Migrating with the associated part
Migrating without the associated part
When migrating any program, the migration tool always does the following:
  • Includes the declaration:
    <custPrefix>EZESYS
    
  • Includes a statement to initialize the value of
    <custPrefix>EZESYS
    
    to the old VAGen value using the system library function.

The migration tool does the same thing as mentioned in the Migrating with the associated part column.

Based on the first migration of the function, the migration tool does the following:

  • If EZESYS is used in an IF, WHILE, or TEST statement, the migration tool converts EZESYS to
    sysVar.systemType
    

    The migration tool converts the EZESYS values to their EGL equivalent value. If the EZESYS value does not have an equivalent EGL value, the migration tool migrates it "as is". For example, the migration tool converts MVSBATCH to the EGL equivalent zosbatch. The migration tool migrates OS2 and NTCICS to the same value as in VisualAge Generator. See Figure 101 for specifics of which values are converted.

  • If EZESYS is used in any other statement, the migration tool does the following:
    • Issues a warning message that this use will result in the old VAGen EZESYS values
    • Uses
      <custPrefix>EZESYS
      

      to replace EZESYS in the statement.

The migration tool does the same thing as mentioned in the Migrating with the associated part column.

Potential Problem 1: A problem arises for EZESYS values that migrate as they are and for the EGL equivalent values (for example, imsvs and imsbmp) that are not supported in this release. There will be an error on the Tasks list.

Possible Solution 1: Modify the function and change the logic so that sysVar.systemType is not checked for values that are not valid in EGL.

Potential Problem 2: A problem arises if you want to use the new EGL values in statements other than if and while.

Possible Solution 2: Modify the function and change the logic to use sysVar.systemType instead of

<custPrefix>.EZESYS

Be sure to change the old VAGen values to the new EGL values in any data tables that you use for comparisons

The same potential problems mentioned in the Migrating with the associated part column apply. You can use the same solutions.


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