E1: UPG: How to - Legacy AS400 Applications Don't Find Tables After Upgrade Table Conversions - Issue Matching Table Name And Record Format Name
Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version SP24 and later
IBM i on POWER Systems
However, before DB2 was integrated into the AS400 operating system, applications used the "record format name" to identify tables. These names are still defined within the table definition so older programs can still use the them to connect to the table. If the record format name does not match the table name, programs that specifically use record format name to find the table will not work. Newer applications, like EnterpriseOne, use the table name and therefore do NOT have problems finding the table. Again, all is fine if the table name and record format name match, which they would with a new table creation.
Therefore, because of the way we do our Table Conversions - creating the new temp table and then renaming it - this causes the table name and the record format name to be out of synch. IBM does not have any functionality to rename the record format name of a table. Therefore, after a table conversion, the record format name is the name of the temporary table. I.e. F010100001 record format name for the F0101 table.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms