We do not qualify the objects in our SQL Scripts, i.e. we set the default
schema (DFTEDBCOL) in the RUNSQLSTM command:
RUNSQLSTM SRCFILE(YOURSRCLIB/YOURSRCF)
SRCMBR(YOURSRCMBR)
COMMIT(*NONE)
DATFMT(*ISO)
MARGINS(132)
DFTRDBCOL(YOURDFTLIB)
... but keep in mind when setting a default/current schema, everything that
is not in the default/current schema must be specified qualified!
The library list is no longer considered.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"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)
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
smith5646midrange@xxxxxxxxx
Sent: Dienstag, 15. Februar 2022 18:06
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Question for migrations of SQL source / objects
We have stumbled over a problem and I am curious how it is normally handled.
The libraries in our environments have different names based on the
environment. For example, the libraries for dev testing might be DATADEV1,
DATADEV2, etc. while the library for user testing might be DATAUSR1,
DATAUSR2, etc.
When there is source to create stored procedures, views, etc., how do
companies deal with the varying library names when they need to be included
in the definition because they are not part of the normal library list?
I'm also curious about how packages like Turnover, Aldon, etc. handle this
if anyone knows that.
I know there are better ways to handle this by "fixing" the environment
library lists and such but I can't turn the barge with an oar so the
environment is what it is and I have to work within the current parameters.
Thanks in advance for any insight you can provide.
--
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.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
