Re: Censoring SQL access -- ideas?

Sure it can be done with SQL. You set up an RDB entry pointing to the
other system and use CONNECT to access the data on the remote system.

Thanks,
Tommy Holden



From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/16/2011 10:24 PM
Subject: Re: Censoring SQL access -- ideas?
Sent by: midrange-l-bounces@xxxxxxxxxxxx



On 3/16/2011 1:27 PM, rob@xxxxxxxxx wrote:

Joe,

True on the ORDER BY limit in a view, but you might want to take a look

at

the enhancements done to CREATE INDEX.
CREATE INDEX, with the RCDFMT clause and the WHERE clause is a beautiful
thing. I believe that the index fields and the fields added in the

RCDFMT

clause can be UDF's.

http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/db2/rbafzxcindx.htm

Rob Berendt

Yeah, I've been reading about that. It has its limitations as well; as
far as I can tell you're stuck with the layout of the underlying table.
One of the primary benefits of the view is to select and omit columns,
and the INDEX ... WHERE doesn't give you that. Logical files still do
the combined sort, select and reformat better than any one tool in the
SQL toolkit.

One other thing - you can't do SQL on a DDM file. There are
circumstances where getting at a table on another i is required. With
RLA, it's CRTDDMF and I'm done. With SQL, it's impossible. (Yes, it
can be done with ODBC/JDBC, but not with standard SQL.)

Joe