×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
The SET SCHEMA statement will do it, but, RUNSQL only allows one command to be given, so, your SBMJOB would succeed in changing the current schema and then nothing else. So, I suppose you'd have to build a string of statements in a source file, and then use RUNSQLSTM. That makes putting the script in QTEMP difficult, so, I don't have a slick answer for you there.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Wednesday, May 8, 2019 3:20 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Setting CURRENT SCHEMA
Is there a way to set CURRENT SCHEMA in RUNSQLSTM, EXESQL or some other like feature?
CURRENT SCHEMA is defaulted to the current library with the current user of the job. Not the job's current library. Therefore doing tricks like wrapping RUNSQL in a SBMJOB with a CURLIB set to the desired value fails.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
--
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@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
