× 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.



Hi Darryl,

Most things I do in ACS need to use the library list in traditional
fashion, so I configure the naming convention to be *SYS, so the *LIBL gets
used. *SQL naming is irritating to me since it doesn't use the library
list to locate unqualified objects. For what reason(s) are you using *SQL
naming?

As far as where to place a procedure or function being created, you can
precede the create command with "set schema MY_SCHEMA" or "set current
schema MY_SCHEMA" to place the object in MY_SCHEMA. Or, you can hard code
the schema in the create command. "set schema default" or "set current
schema default" will remove the current schema setting.

I highly doubt IBM would allow you to directly UPDATE any of the system
catalog tables, although I've never tried that. Nor do I think they should
allow that.

I handle where to place created objects a bit differently, and rarely use
ACS to create them. I embed custom schema variable strings in the source
code in place of where you'd hard code them, use an SQL replace function to
replace the variables with an actual schema (just prior to the create), and
feed the resulting (now complete) SQL string to the database for execution
of the create command. This way, I'm not frequently fiddling with SET
SCHEMA commands, and don't have to remember to run a SET SCHEMA DEFAULT to
revert to using a *LIBL.

Mike


date: Thu, 14 Dec 2017 11:06:58 -0500
from: a4g atl <a4ginatl2@xxxxxxxxx>
subject: Problems creating stored procedures in ACS.

Is there a way to get the creating of a stored procedure in ACS to default
to *LIBL for the program library. I use *SQL naming.

Setting up a session with *SYS each time I have to create a SP is
cumbersome.

If I do not change the session defaults to *SYS, it defaults the program
library to be my default library. The company standard here is to use *LIBL
for the library.

For now, I have to use the 5250 SQL session and switch it to *SYS with F13
and then back.

I have not tried this, but could you use UPDATE to change the value in
QSYS2.SYSPROCS?

TIA

Darryl Freinkel


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.