VisualAge Generator to Enterprise Generation Language Migration Guide


Appendix E. IWN.xxx messages on the Tasks list

Some IWN.SYN, IWN.VAL, and IWN.XML messages are more likely to occur for EGL source code that was migrated from VisualAge Generator than for code that you develop completely within EGL. This section lists messages that have a special meaning for migrated code.

IWN.VAL.4929.eThe use statement for formGroupName in program programName does not resolve.

Explanation: The program specified a map group in VisualAge Generator but did not have any display or converse I/O options in the program, nor any maps as a called parameter.

User Response: Change the program to do one of the following: Remove the use statement for the formGroup or add an import statement for the package containing the formGroup. You might need to create a formGroup part if one did not exist in VisualAge Generator.

IWN.VAL.5100.esysVar is an invalid qualifier for the xxxxx system word.

Explanation: An EZE word that was valid in VisualAge Generator is not currently supported by EGL. The migration tool migrates the EZE word, making a "best guess" as to what the EGL replacement might be in the future. This preserves your program logic.

User Response: Edit the function and make logic changes so that this value is no longer used. Alternatively, create a new project to preserve migrated functions that cannot currently be used. Move all functions that contain VAGen values that are not currently supported to this new project.

IWN.VAL.5101.emainFunctionName It is invalid to use the xxxxx system word in this statement location.

Explanation: The program that uses that uses the specified main function in turn invokes other functions. One of the functions in the function invocation chain uses the specified system word in a statement. The migration tool always qualifies the EGL system words that are replacements for the VAGen EZE words. If the xxxxx system word is not qualified with sysLib, sysVar, mathLib, or strLib, the most likely causes are as follows:

User Response: Check whether the VAGen program allowed implicit items. If so, validate the program in VisualAge Generator. There will be a message on the VAGen View Messages list that provides the correct definition of the implicit data item. Add the definition for the data item to the declarations section of the program. If the VAGen program did not allow implicit items, create an associates list for the program in VisualAge Generator. From the associates list, use the VAGen References tool to search for the specified data item. The results of the References tool provide a clue to which record, map, or table might be missing from the migration set.

IWN.VAL.5168.exxxxx is not valid for use within an Is/Not expression.

Explanation: In VisualAge Generator, the specified value was a valid value for EZESYS. This value has no corresponding value in EGL. The migration tool migrates the VisualAge Generator values to preserve your program logic.

User Response: Edit the function and make logic changes so that this value is no longer used. Alternatively, create a new project to preserve migrated functions that cannot currently be used. Move all functions that contain VAGen values that are not currently supported to this new project.

IWN.VAL.6620.efunctionName - The variable access xxxxx is ambiguous.

Explanation: Determine if the problem occurs for a call statement and xxxxx is an unqualified data item. If the problem is for a call statement, check to see if the data item is in the Level 77 record associated with the program's inputRecord property. VisualAge Generator gives precedence to Level 77 items in the program's primary working storage record if an unqualified item is used on a CALL statement. However, EGL does not provide the same precedence for the call statement.

User Response: If the problem is for a call statement, you might be able to use the Level 77 record name as the qualification for this item. However, you must be sure that all programs that invoke this function use the same Level 77 record.

IWN.VAL.6695.efunctionName - The state INVISIBLE is not allowed for this item data reference.

Explanation: If state is PROTECT, SKIP, INVISIBLE, BLINK, or a color, the data item is on a print form. VisualAge Generator tolerated setting these attributes for printer forms. EGL does not.

User Response: Modify the function to remove the statement. Alternatively, if the same function is used with both a text form and a print form, you must create a copy of the function for use with print forms.

IWN.XML.3997.eXML Validation Error - Attribute "yyyyy" must be declared for element type "xxxxx".

Explanation: In VisualAge Generator, the option yyyyy is valid for element xxxxx. This combination is not supported by EGL. The migration tool migrates the value even though it is invalid so there will be an error on the Tasks list to remind you to resolve the problem.

User Response: Review the EGL online helps for the options that are valid for xxxxx. When you decide which option (or options) to use, you might need to open the build descriptor file with the Text Editor to be able to make the necessary change.

IWN.XML.3998.eXML Validation Error - Attribute "system" with value "xxxxx" must have a value from the list "ZOSCICS WIN USS ISERIESJ ZOSBATCH AIX LINUX".

Explanation: In VisualAge Generator, the value xxxxx is a valid target environment. This environment is not currently supported by EGL. The migration tool migrates the information for certain target environments to preserve the information for possible future use.

User Response: Create a new project to preserve migrated build descriptors that cannot currently be used. Move all build descriptor parts that contain VAGen values that are not currently supported to this new project. To move the part, use a text editor to open the build descriptor file to copy and paste the part that has the error.

IWN.XML.3999.eXML Validation Error - The content of element type "xxxxx" must match "(listOfValues)".

Explanation: In VisualAge Generator, one or more of the values specified for a resource association is a valid value. This value is not supported by EGL. The migration tool migrates the value even though it is invalid so there will be an error on the Tasks list to remind you to resolve the problem.

User Response: Review the EGL online helps for the options that are valid for xxxxx. When you decide which option to use, you might need to open the build descriptor file with the Text Editor to be able to make the necessary change.


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