Better yet, walking away from a carpentry job when you learn that they'll
only let you use left-handed hammers.
:-)
The bottom line is that SEQUEL works, and it lets you fulfill user requests
far faster than you can with grunt programmers. The users don't care if
something is "elegant" under the covers.
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul
Nelson
Sent: Wednesday, February 18, 2015 10:43 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Is there an easy way to identify all the save files on a
system?
Isn't that like walking out of an interview when learning the shop uses
COBOL instead of RPG?
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
It
Sent: Wednesday, February 18, 2015 10:33 AM
To: Midrange Systems Technical Discussion
Subject: RE: Is there an easy way to identify all the save files on a
system?
Jim
You have to use the *LOCALSYS server for SEQUEL to use SQE - if you have
lots of views built over time, they are not likely to be set for that
server.
If you want to use IBM i syntax, set the SYNTAX parameter to server when
SERVER is *LOCALSYS
Vern,
While you are partially correct, that *LOCALSYS will allow SQL statements to
go to SQE, the problem is that SEQUEL attempts to translate the SEQUEL
syntax into a valid DB2 for i syntax, but the translation is messy at best
and does not utilize the latests join techniques.
Not that I don't like the product, but I have immediately walked out in the
middle of an interview when I was told that SEQUEL was their primary tool.
Jim
As an Amazon Associate we earn from qualifying purchases.