Hi all,
we have a file that uses file translation across multiple different environments (the translation table is the same across all environments) but the record format is not consistent. For example:
ENV1_LIB/FILE1 (Format: XXXZZZ111RRRR)
ENV2_LIB/FILE1 (Format: XXXZZZ111RRRR)
ENV3_LIB/FILE1 (Format: XXXZZZ111RRR0)
My program is an overarching service that maintains 4 key fields on this file. The 4 fields I want to look at are always present but because the record format is different I can't declare it like a normal file in the RPG program because it will level check - therefore the decision to use SQL has been made.
In the RPG programs that read/write to this file the file translation is declared in **FTRANS compile time data segment. If I still include this in my program will the SQL pickup the file translation?
we have a file that uses file translation across multiple different environments (the translation table is the same across all environments) but the record format is not consistent. For example:
ENV1_LIB/FILE1 (Format: XXXZZZ111RRRR)
ENV2_LIB/FILE1 (Format: XXXZZZ111RRRR)
ENV3_LIB/FILE1 (Format: XXXZZZ111RRR0)
My program is an overarching service that maintains 4 key fields on this file. The 4 fields I want to look at are always present but because the record format is different I can't declare it like a normal file in the RPG program because it will level check - therefore the decision to use SQL has been made.
In the RPG programs that read/write to this file the file translation is declared in **FTRANS compile time data segment. If I still include this in my program will the SQL pickup the file translation?
Comment