OOPS! My bad ...
After doing a SET SCHEMA QTEMP, I tried to create a variable and I get:
Additional Message Information Message ID . . . . . . : SQL0707 Severity . . . . . . . : 30 Message type . . . . . : Diagnostic Message . . . . : Name INDIST in QTEMP not allowed. Cause . . . . . : Name INDIST is not allowed for one of the following reasons: -- Distinct type, array type, sequence, or global variable INDIST in QTEMP cannot be created or dropped. Either the name is a reserved word or the schema is specified as QSYS, QSYS2, SYSIBM or QTEMP. Distinct types, array types, sequences, and global variables cannot be created in QSYS, QSYS2, SYSIBM, SYSPROC, or QTEMP. -- Savepoint INDIST cannot have a name that starts with SYS. Recovery . . . : Change the name to a non-reserved word, or create the user-defined data type, sequence or global variable in a schema other than QSYS, QSYS2, SYSIBM, SYSPROC, or QTEMP. Bottom Press Enter to continue. F3=Exit F6=Print F9=Display message details F10=Display messages in job log F12=Cancel F21=Select assistance level
On Thursday, November 2, 2023 at 05:41:47 PM EDT, Mark Waterbury <mark.s.waterbury@xxxxxxxxxxxxx> wrote:
Hi, folks ...
I think in STRSQL or equivalent you can do:
set schema qtemp
and then if you create stuff like that, this is where it should go?
HTH ...
Mark S. Waterbury
On Thursday, November 2, 2023 at 05:34:38 PM EDT, Dan <dan27649@xxxxxxxxx> wrote:
I was not aware! Thanks for that tip!
I agree that that is a mess. Does this mean I can create the variable in
one session and another user can use that same variable? This really
should be created in QTEMP.
- Dan
On Thu, Nov 2, 2023 at 5:00 PM <smith5646midrange@xxxxxxxxx> wrote:
Be aware that when I do this it creates a "*SRVPGM" with that name in
QGPL.
I would be interested to know if there is a way to change the library so
it creates it in QTEMP and it automatically gets cleaned up.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Dan
Sent: Thursday, November 2, 2023 4:55 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Run SQL Scripts: Define variables whose values are prompted
After refining my search, I found I can use:
CREATE OR REPLACE VARIABLE @inDistrict char default 'WAZ'; CREATE OR
REPLACE VARIABLE @inRegion char default 'C12'; then change the :in*
references to @in*. This works for me.
- Dan
As an Amazon Associate we earn from qualifying purchases.