Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avoiding hard-coding libraries on CREATE, etc. statements

Status
Not open for further replies.

cjkoontz

MIS
Aug 9, 2000
102
US
With the SQL commands:

DROP FUNCTION
CREATE FUNCTION
DROP VIEW
CREATE VIEW

And the option to specify EXTERNAL objects --

Is there a way to specify a library for each (i.e., CREATE FUNCTION MYLIB/MYFUNC), without having to do it on the CREATE, etc. statements?

I see where that you can create an object, by default, in the CURRENT LIBRARY, if you don't specify the library on the CREATE statement.

But what about CREATE VIEW?

The IBM literature I've read seems to indicate that if you don't specify a library, then the first library assumed in the SUBSELECT is used.

Anyway around that?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top