ACS Run SQL Script - Work with source physical file member / GENERATE_SQL stored procedure output into the IFS Merged

with the GENERATE_SQL stored procedure and the ACS Wizard Generate SQL, SQL scripts for the selected database object can be stored within a source physical file member. The GENERATE_SQL stored procedure even does not allow to save the result anywhere else.
For recreating the database object the generated SQL script can be executed with the RUNSQLSTM CL command.
But there is no way to open a source physical file member with in the ACS Run SQL script facility for modifying or rerunning the SQL statements.
In this way:
1. ACS Run SQL script facility should be enhanced so source physical file members can be opened
2. The GENERATE_SQL stored procedure should be enhanced so that the generated SQL statements could be alternatively stored in the IFS.

I like to save the SQL scripts for my generated database objects.
After having created the database objects, the SQL script is saved (currently in a source physical file member with the GENERATE_SQL stored procedure).
After I delete the generated database object and run my SQL script, just to make sure source and object are identical.
While RPG and other sources can be stored in the IFS, GENERATE_SQL will only write into source physical file members. If we want to save everything in the same environment, we have to copy the member into the IFS.
If I want to run the SQL code from a source physical file member, I cannot use ACS Run SQL Script, but have to execute the RUNSQLSTM CL command, which is much less flexible than ACS. For example if you try to drop an non-existing object, RUNSQLSTM will crash, ACS can ignore this error.