QMQry Created File vs Qry400 created file

I just ran into a situation where I sent output to an output file from a QMQRY. I had already generated the file from the Qry400 query that I am replacing and used that figuring the file had to exist beforehand.

We use ETU to send data to the LAN which worked fine in test.

When I moved it to production, I didn't bring the output file over and the job promptly bombed. Called ETU support. At this point we didn't realize what happened. Then, I brought the file from the test environment to production and it worked fine.

Back to development: Deleted the file [after copying it] and let the QMQry build it from scratch which it did, but the transfer using ETU failed. Rebuilt from the original Qry400 query. Good to go, again.

So, why did this happen? I looked at the file and object descriptions - looked the same.

ETU support thinks it has something to do with sharing or missing DDS. There is no DDS for the file that works, so I don't think that's it.

There was an interesting post about using the INSERT command within the SQL.
I could do that, but would I still have to build the file first?

Right now, though, what's the difference between how the files are generated?
Thanks,


Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404
Frances.Denoncourt@xxxxxxxxxxxxxxxxx
Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email