Tweet
SQL static View shows as a Logical File - recompile considerations
Hello,
I am a new IBMi programmer working in small shop with primarily legacy code. As part of our efforts to modernize, we want to take advantage of SQL static Views when creating reports that use sets of data. I created a SQL static View that uses fields from 4 different Physical Files. We use Aldon Change Management (LMI) tool to create and move our objects. After creating the SQL static View object via Aldon Change Management tool, it shows as a Logical File for each of the 4 different Physical Files that were used to create the View. This would make sense since the View it's like an unkeyed Logical File. My question is: if we change any of these 4 different Physical Files, will we need to delete and recreate the View (since we typically delete and recreate all Logical Files when changing the Physical File) ? Any other recompile considerations I might need to be aware of?
I am a new IBMi programmer working in small shop with primarily legacy code. As part of our efforts to modernize, we want to take advantage of SQL static Views when creating reports that use sets of data. I created a SQL static View that uses fields from 4 different Physical Files. We use Aldon Change Management (LMI) tool to create and move our objects. After creating the SQL static View object via Aldon Change Management tool, it shows as a Logical File for each of the 4 different Physical Files that were used to create the View. This would make sense since the View it's like an unkeyed Logical File. My question is: if we change any of these 4 different Physical Files, will we need to delete and recreate the View (since we typically delete and recreate all Logical Files when changing the Physical File) ? Any other recompile considerations I might need to be aware of?
Comment