RE: Run SQL Scripts: Define variables whose values are prompted

Even though a global Variable is a Service Program, a SQL global variable works like a data area in the QTEMP.
So, the same variable (within the same schema) can be set to different values in different jobs/connections.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser
Modernization – Education – Consulting on IBM i

IBM Champion since 2020

"Shoot for the moon, even if you miss, you'll land among the stars." (Les Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them and keeping them!"
"Train people well enough so they can leave, treat them well enough so they don't want to. " (Richard Branson)
"Learning is experience … everything else is only information!" (Albert Einstein)

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Dan
Sent: Thursday, 2 November 2023 22:34
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Run SQL Scripts: Define variables whose values are prompted

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

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.