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



Granted, I don't add the library to my LIBL.  =)  Inside the Sysi Nav
tool I do.  Maybe thaaaaaaat's why - LOL!!!  

Yep - it works.  Duh - that was an easy one.  Thanks. 


--
Justin C. Haase - Solution Engineer
IBM Certified Systems Expert - System i
Kingland Systems Corporation

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Holden Tommy
Sent: Thursday, December 28, 2006 8:25 AM
To: Midrange Systems Technical Discussion
Subject: RE: Annoying default library behavior in interactive SQL

Weird...as long as I have the library in my LIBL I have never had to
specify a library for any SQL statement (even before V4R5..) 


Thanks,
Tommy Holden


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Haase, Justin C.
Sent: Thursday, December 28, 2006 8:14 AM
To: Midrange Systems Technical Discussion
Subject: RE: Annoying default library behavior in interactive SQL

I've always had to define libs when using interactive SQL.  Through Sysi
Nav or ODBC it works as per the standards suggest.  Had to do it since
V4R5 all the way to V5R4. 


--
Justin C. Haase - Solution Engineer
IBM Certified Systems Expert - System i
Kingland Systems Corporation

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Cawthon
Sent: Wednesday, December 27, 2006 8:33 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Annoying default library behavior in interactive SQL

Hi.

Somehow I have managed to make interactive SQL forget how to use the
library list to find a file.  For example:
    SELECT * FROM SOMEFILE
elicits the following response:
    SOMEFILE in CMIDEV type *FILE not found.

CMIDEV happens to be the name of the system; in addition, there is a
library on the system actually called CMIDEV.  That library is not in my
*LIBL, nor is it my *CURLIB.

Interactive SQL behaves in this annoying fashion regardless of whether I
am using *SYS or *SQL naming.

When I run "SELECT CURRENT SCHEMA FROM SYSIBM/SYSDUMMY1" I get "*LIBL"
in response, which is what I expected to see, although SQL is apparently
not using this.

In fact, when I "SET CURRENT SCHEMA = DMCLIB" (or any other library that
exists on the system) and try a SELECT statement without a library
qualifier, I get the same annoying message.  It is as if SQL is ignoring
the value of CURRENT SCHEMA...?

When I sign on under a different user profile I get "SOMEFILE in *LIBL
type *FILE not found." which is what I wish I was seeing under my main
profile.

This is a V5R3M5 box in case it matters... although I am pretty sure it
is just a boneheaded config change I must've made a while back.  I just
can't figure out what I did!

Any help would be greatly appreciated.

Thanks,
David Cawthon
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



CONFIDENTIALITY NOTICE:  This e-mail communication, including
attachments, is covered by the Electronic Communications Privacy Act, 18
U.S.C. 2510-2521, is confidential, and may be legally privileged.  If
you are not the intended recipient or believe you received this
communication in error, please reply to the sender indicating that fact
and delete the copy you received.  In addition, retention,
dissemination, distribution, copying, or otherwise use of the
information contained in this communication is strictly prohibited.
Thank you.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.