RE: SQL question on default *LIBL at connection

Jim,

Sounds like you have a library-qualified reference in the stored procedure.
*SQL naming convention uses a period to separate library and object
(table/view/etc) names, while *SYS naming convention uses a slash.

Look for things like:

SELECT * FROM library.GETAGENT

Changing that to:

SELECT * FROM library/GETAGENT

would prevent the SQL5016 error. However, since switching to *SYS naming
convention lets you use the library list, you may want to eliminate the
library reference altogether. Doing that would let you use the same stored
procedure against different libraries (i.e. test vs production) by just
changing the library list.

Have fun!
Richard


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Lowary, Jim
Sent: Thursday, April 30, 2009 1:54 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: SQL question on default *LIBL at connection

Elvis,

No it is *SQL, but when we try and create it with *SYS; we are getting,
Message: [SQL5016] Qualified object name GETAGENT not valid."

So not sure what we might be doing wrong.

Thanks,
-- Jim


message: 7
date: Thu, 30 Apr 2009 11:47:36 -0500
from: "Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>
subject: RE: SQL question on default *LIBL at connection

Was the stored procedure compiled with the *SYS naming convention?

Elvis