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



*SQL naming uses a dot (.) as a separator.
*SYS naming uses a slash (/) as a separator.
This ought to work:

db2 'select * from t37files.vinlot'

Also, you might want to search the archives. Scott has posted a rather
comprehensive description on QSHELL behavior and associated environmental
attributes.

Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com

-----Original Message-----
Subject: QSHELL db2 command

List,
I am attempting to use the db2 utility in QSHELL to run an SQL command from
CL.
When I enter the command, I get an error indicating that it can not find the
file that I want to display.
It seems to be using SQL naming syntax.

db2  'select * from vinlot'              
                                         
 **** CLI ERROR *****                    
         SQLSTATE: 42704                 
NATIVE ERROR CODE: -204                  
VINLOT in VAIJY type *FILE not found.    

Can I specify *SYS naming convention?
If not how do I qualify the file to the library that I am using?

When I use the command:
db2  'select * from t37files/vinlot' 

I get the following error:
 **** CLI ERROR *****                 
         SQLSTATE: 42833              
NATIVE ERROR CODE: -5016              
Qualified object name VINLOT not valid.

TIA,
 
Jeff Young




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.