Based on the first migration of this function, if the SQL record and its
alternate specification record are available, the migration tool converts any
!itemColumnNames to the corresponding SQL column name based on the SQL record
or, if applicable, its alternate specification record.
| If the SQL record and its alternate specification record are not
available, the migration tool does the following:
- Uses !itemColumnNames for any column name variables.
- Issues an error message that the function needs to be reviewed.
|
Potential Problem: A problem only arises if there are two
records with the same name (generally in different subsystems) that have
different SQL column names corresponding to an !itemColumnName.
Possible Solution: Make a copy of the function for use in
the second subsystem and modify the new function to use the correct SQL column
names. Disadvantage: This has the potential to ripple
back into functions that use this I/O function.
|
Potential Problem 1: A problem arises for any modified SQL
statement or any SQL statement that uses Execution Time Statement
Build.
Solution: Review the list of error messages for any
messages related to !itemColumnNames. Modify the SQL I/O function to
include the correct column names based on the SQL row record.
Potential Problem 2: The same potential problem and
solution as shown for Migrating with the associated part
apply.
|