RE: Creating host variables in QTEMP using RSS

That's exactly the point. Bob might want to set testvar in his script to 'PRD09A', whereas John might want to set testvar in his script to 'QAB02'. Bob and John are running the same script in their own RSS sessions. Being able to define testvar in QTEMP would ensure one's setting isn't plowing over the other's.

- Dan Bale

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Charles Wilt
Sent: Wednesday, October 8, 2025 1:01 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Creating host variables in QTEMP using RSS

QTEMP would be unique to each connection...

Not sure how that'd be useful to multiple people.

Charles

On Wed, Oct 8, 2025 at 10:52 AM Dan Bale <dan.bale@xxxxxxxxxxxxxxxxxxxxx>
wrote:

Seems I learn something new every day in SQL / RSS. Today, I
discovered I can do this in a script:

create variable dbale/testvar varchar(30); set testvar = 'PRD09A';
select * from ACXDSPPRB where Server = testvar ;

Originally, I had a colon in front of testvar on the select statement,
but RSS prompted me for a value instead of using the value I set in
the prior statement. It would be nice if I could use the colon so
that I can easily copy the statement into RPG and not have to remember
to prefix all host variables with ':' after I paste it into the RPG
source. I'm guessing there's no way around this, but I would love to be surprised.

Also, IBM explicitly prohibits creating a variable in QTEMP. Bleahh.
This would be extremely useful for RSS scripts that are used by
multiple people simultaneously. Can anyone think of a reason why this
shouldn't be allowed, at least for RSS scripts? If I don't hear any
reasonable objections, I'll create an idea for it.

- Dan Bale

*** CONFIDENTIALITY NOTICE: The information contained in this communication may be confidential, and is intended only for the use of the recipients named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. ***