IBM Contact info needed

["D.W." <dpalme@xxxxxxxxxxx>]

I have had a request pending with an inside sales rep at IBM for two
weeks on some feature code pricing, I can't get her to return my calls
and so far she hasn't taken the time to get me the pricing.

Does anyone have someone further up the food chain that I can contact?
This is really starting to tick me off.  Support is fantastic,
responsive, etc., but getting sales on the phone is really a pain.

My ex was faster than this and she was so slow that she had cobwebs in
her hair...:) Just kidding folks.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve Landess
Sent: Wednesday, March 09, 2005 7:00 PM
To: midrange-l@xxxxxxxxxxxx
Subject: SQL question


I have found that when using *SQL naming convention when using IBM's
STRSQL, 
the SQL interpreter will not find a file by using the library list. 

Example -
Here is the library list for my interactive job:
                     
Opt   Library       Type
        QSYS         SYS 
        QSYS2        SYS 
        QHLPSYS      SYS 
        QUSRSYS      SYS 
        QSQL         PRD 
        QTEMP        USR 
        ENSHSC       USR 
        ENSDPR       USR 
        FRDTPR       USR 

This SQL statement works just fine:
SELECT * FROM FRDTPR.F01092 

However, If I try this SQL statement (without qualifying the library
name): Select * from F01092

I get the error message:
F01092 in AUSLADTMP type *FILE not found.

I don't have AUSLADTMP specified as my Current library.  
AUSLADTMP is my user profile name...why is interactive SQL assuming the
file is in MY library?

We get the exact same behavior when using a Java program with JDBC to
execute the same SQL statement...

Regards,
Steve 
-- 
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.