VisualAge Generator to Enterprise Generation Language Migration Guide
- The migration tool correctly converts SQL keywords used as column names
within the SQL record structure. However, the migration tool does not
handle SQL keywords used as column names within the SQL defaultSelectCondition
for a record or within the SQL clauses for a function. The workaround
is to modify the SQL defaultSelect Condition or SQL clause as described in SQL reserved words requiring special treatment . This section provides a list of SQL keywords and
details of the syntax required for the SQL defaultSelectCondition and SQL I/O
statements.
- The migration tool converts SQL I/O with execution time statement build to
a prepare statement. However, if any host variables in the SQL
statement are smallint, int, bigint, binary, or decimal fields, the prepare
statement is not correct. The workaround is to change the prepare
statement by replacing each host variable with the ? symbol and then adding
the variable names in a using clause for the execute, open, or get statement
that is associated with the prepare statement. Refer to the "prepare"
topic in the online helps for examples of the correct syntax.
- If you select the preference to Convert shared data items to
primitive item definitions, the migration tool correctly converts the
item definitions. However, it does not remove the corresponding import
statements. You can reduce the time it takes to build a project by
removing any import statements that are not required for other part
references.
- Parts are sorted alphabetically by VAGen part name within the part
type.
- Bind control parts incorrectly add a DBRMLIB named
%ELA%.NEW.SELADBRM. The correct name is
%ELA%.SELADBRM.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.