Yep. I get exactly the same results when I follow those steps.
I agree that this thing must not be designed with the 400 in mind.
Note that the "resource" and "path" associated with the "unknown table" error
refer to the pc file, not the selected table. Like the syntax checker is
looking for the table on the PC or something.
Also, there still seems to be a fundamental disconnect between the way this
thing is "working" for us, and the way it is described in the Quantum User's
Guide. The guide specifically says "The SQL Query Editor is a view..." and has
a screen shot of a view with "SQL Query Editor" as a title on the tab in the
view, much like what we normally see in the "Quantum SQL Queries View". That's
not what I'm seeing. All I see is the file opened with the little scroll icon
indicating that it is opened in the Quantum SQL Query Editor.
I don't know if the "libraries=*LIBL" is case sensitive, but I do have it set
up the way I just typed it, so it couldn't hurt to try, I guess.
|-----Original Message-----
|From: wdsci-l-bounces@xxxxxxxxxxxx [
mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
|Behalf Of AGlauser@xxxxxxxxxxxx
|Sent: Tuesday, April 24, 2007 8:45 AM
|To: Websphere Development Studio Client for iSeries
|Subject: Re: [WDSCI-L] Question for Quantum users
|
|Greg Fleming wrote on 23/04/2007 17:13:41:
|
|> I think my trouble is that I don't seem to have the "SQL Editor View"
|> available when I select Window-->Show View-->Other.
|>
|> If I understand the Quantum Help correctly, the "SQL Editor View" is
|> different from the "Quantum SQL Queries View".
|>
|> Hmmm...
|
|I figured out that if you create a file on your PC with an extension of
|.sql, you can choose 'Open With -> Quantum SQL Editor'. However, the
|'libraries=*libl' option doesn't seem to work (is it case sensitive?), and
|the syntax checking still fails in a strange way ... if I do the following
|(<key> means push the specified key, 'text' means type exactly that text,
|without the quotes)
|
|1. Create a file on my PC (using the 'Local' connection in RSE) named
|testSQL.sql
|2. Right-click, Open With -> Quantum SQL Editor
|3. Type <enter>, 's' <ctrl-space>
|4. Choose select, <enter>
|5. Now 'select' is typed by Quantum. I type <space>,'*',<enter>,
|'from',<space>,<ctrl-space>
|6. Now a list of physical files in my bookmark comes up (I've limited my
|bookmark to three libraries to make it a bit quicker).
|7. I choose a PF from the context-sensitive help list - say 'DSP070DBR'
|(an outfile from DSPDBR)
|8. Quantum fills in the query with my chosen table name.
|9. I right-click, then choose 'Check Syntax'
|10. I get an 'Unknown table' entry in the Problems view (which I have to
|open using Window->Show View ... it's under General)
|
|WTF? If context sensitive help knows about it, how come the syntax
|checking doesn't? I'm starting to suspect that Quantum doesn't play that
|well with the jt400.jar JDBC driver.
|
|Any thoughts appreciated,
|Adam
|
|Attention:
|
|The information contained in this message and or attachments is
|intended only for the person or entity to which it is addressed and may
|contain
|confidential and/or privileged material. Any review, retransmission,
|dissemination or other use of, or taking of any action in reliance upon,
|this
|information by persons or entities other than the intended recipient is
|prohibited. If you received this message in error, please contact the
|sender and
|delete the material from any system and destroy any copies. Thank you for
|your
|time and consideration.
|
|Attention:
|
|Le contenu de ce message et(ou) les fichiers ci-joints s'adressent
|exclusivement à la personne ou -entité à laquelle ils sont destinés. Ils
|peuvent
|contenir de l'information confidentielle, protégée et(ou) classifiée. Il
|est
|strictement interdit à toute personne ou entité autre que le(la)
|destinataire
|prévu(e) de ce message d'examiner, de réviser, de retransmettre ou de
|diffuser
|cette information, de prendre une quelconque action en fonction ou sur la
|base
|de celle-ci, ou d'en faire tout autre usage. Si vous avez reçu ce message
|par
|erreur, veuillez communiquer avec l'expéditeur(trice), supprimer ce message
|et
|les fichiers ci-inclus de tout système, et en détruire toutes copies,
|qu'elles
|soient électroniques ou imprimées. Nous vous remercions de votre entière
|collaboration.
midrange.com
