When the IMPORT file is missing BTEQ issues an error and continues with the next SQL Statement in the Network attached system. In the mainframe systems this ab ends the script. This behaviour in the network system causes concerns and makes me wonder how other folks deal with this issue. I don't like the idea of writing a script to make sure that the IMPORT files exist before the BTEQ. Is there a way to handle this within the BTEQ script?
*** Error: The following occurred during an Access Module open:
Requested file not found.
*** Importing deactivated
Even the next Using-SQL-Statement issues an Error but is not caught by the ERRORCODE
*** Error: Use IMPORT to open a file first before
trying to read from it.
Thanks..
Forums: