Re: SQL *SYSTEM naming default schema rule?

Again supposing the intent is to get the CREATE VIEW to create the
view in QGPL [as the effective current library] much like most other
CRTxxx commands or many other CREATE statements would for an unqualified
object-name, consider the following revised script which uses a
compound-statement with a variable to assign the library name in a fully
dynamic statement:

<code>
begin
declare bsv_libl varchar(276) default '*SAME' ;
declare cur_lib varchar( 10) default '*SAME' ;
set bsv_libl = 'libsql1 libsql2' ;
set cur_lib = 'qgpl' ;
call qcmdexc ( 'chglibl (' concat bsv_libl concat ')'
concat ' (' concat cur_lib concat ')' )
;
-- following creates into QGPL
create table table_master
( id int
, text char(25)
, foreign_key int
)
;
-- following creates a table in 2nd lib in *LIBL
create table libsql2.table_child2
( id int
, text char(25)
)
;
-- following creates into QGPL rather than LIBSQL2
execute immediate
'create view ' concat cur_lib concat
'.' concat 'view_two_subselect
(m_id, m_text, c_id, c_text)
as (select m.id, m.text, m.foreign_key
, (select text from table_child2)
from table_master m
)'
;
end
</code>

Note: As a compound statement, the ease of the full script error
handling being controlled by the ever-simple Severity Level (ERRLVL)
parameter of RUNSQLSTM is lost; the above has no SQLEXCEPTION or any
other [continue] handlers to deal with errors, such as -601 "already
exists." The scripting could be redefined in some creative ways to make
only the setup\execution of the CREATE VIEW statement(s) run under
compound statements.

Note: As I noted in another message, because I can not test, the above
execute immediate may require [still on v7r2] the same as on v7r1,
whereby the /expression/ must be a variable; coded above, as though the
support is there, as I infer from the docs, to specify just a
character-string instead of a variable name.