SQL Connect v DDM Files

Greetings from sunny Florida.





I recently had to modify one selection and one file generation program to
use a "different file" than the one in the original design (in programs
which have been running great since being implemented). The new file
resides on an EDI dedicated system and is accessed via DDM. Problem is that
the programs are using this "different file" in SQL statements. Two other
files on this system are output files for EDI and use overrides in the CL
successfully. All three files are on the EDI box and the programs are run
from the main production box. SQL and DDM don't mix.



My options are to modify the SQL select statements not to use this file,
then chain to it to determine if the other file should be used or bypassed.
Or I can use SQL Connect which will require me to take the overrides for the
output EDI files out of the CL and to clear them and output to them within
the RPG program.



I would prefer to use SQL Connect. There are no examples on the system at
present but I know what to code and where. Is there anything I must be
aware of to use SQL Connect successfully?







Robert Munday

Munday Software Consultants

Montgomery, AL

On assignment in Jacksonville, FL