May be this would help - this is what i tried and it does work out. The solution is through BTEQ utility, but there are some limitation, read through.
Now that you say you have stored all the SQL generated strings in a table. You could write a bteq script as follows :
/*
.logon tdpid/user,passwd
.export report file=/filenameX
sel SQLstringcol from tablename;
.export reset
.run file=/filenameX skip 2
.logoff
.quit
*/
An explanation :
Line 1: Logon to the particular user
Line 2: The EXPORT command to dump the output of the following SQL statements till you encounter the "export reset" statement. thereby you specify the file where you want the output to be stored
Line 3:The statement which would get all your strings from the table into the file
Line 4:To end the exporting.
Line 5:To run the script that was generated in this case filenameX, the skip <number> is because to skip the column header and the line that follows if you open filenameX you will know what i mean - the first two line
Now to the limitation :
If the strings that you have constructed are more than 254 characters in length then you would have to use the "REPORTWIDE" option at Line 2 rather than the "REPORT" option. The 254 character is a limitation of bteq. Now to the interesting part the REPORTWIDE option has been knocked off from bteq versions above 5.4. So you need bteq version 5.4 or less where you have the REPORTWIDE option.
NOTE: the above is suggested only if the strings are longer than 254 characters.
Regarding executing the same through QueryManager, i cannot answer that because i have not used the QueryManager extensively with the options as above, perhaps you may find options similar to the ones i have specified above in Querymanager - do check it out.
Hope the solution solves the issue.
