I would like to capture the SQLIN file created during the ETL process by data migrator. Doing a filedef in EDASPROF does not work, any other suggestions?
I received this information from a project manager regarding your question:
The SQLIN is not a real file. The output from the select statement (SQLIN) becomes the input to a modify, without ever getting written to disk as a file. If you want an intermediate flat file, you could always disable automatic pass through, slowing things down a bit.
Hope this helps.
|Powered by Social Strata|