RE: Implementer & SQL indexes, views, etc

I was just looking at some CLI code and dealt with an issue where type of
SQL naming mattered.  In my case if I use *SYS-tem naming, library list was
used, but if I used *SQL naming, only the default library was used.

I see that RUNSQLSTM has a NAMING keyword.  Maybe you can change that to
*SYS and library list would be searched?

Elvis

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
phillip.groschwitz@xxxxxxxxx
Sent: Friday, February 27, 2004 9:33 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Implementer & SQL indexes, views, etc

Anyone using Implementer _and_ using it to install SQL indexes and views?

Implementer uses RUNSQLSTM to create the object.

I'm trying but I run into problems with the library.  If I change the
DFTRDBCOL to the library where the table resides (it's already installed),
the view gets created but the source doesn't get copied and it ends in
error.  If I change the DFTDBCOL to be #FILLIB, which is the temporary
implementer library, then RUNSQLSTM can't find the table because it's only
looking in the temporary library - not the library list.  If I leave it at
*NONE, it searches the current library which is QGPL.

I'm trying to find out if this can work and I'm doing something wrong, or
if this is simply a shortcoming that I have deal with.

Thanks!

Phil

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.