× 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 can easily handle files across partitions - just use WRKRDBDIRE to add relational database directory entries for your other partitions. Then you can connect to any of them, albeit one at a time.

SQL CLI would need to use the same relational database directory entries - CLI is just another way of doing SQL - it is still SQL, just a lot more work. So do your embedded stuff, get to know SET CONNECTION and CONNECT TO and it all just works.

HTH
Vern

frank kolmann wrote:
Hi Nathan

OK.
Don't like DDM. It seems unstable to me. Cant use SQL via DDM files.
Dont know why but when I try to use DDM it works fine for a while then I get
the wierdest errors and it does not recover untill I find the bachground job
with the problem and cancel it. Thats all I am going to say about DDM.

What is SQL CLI (command line interface?), if so I am very interested in
knowing how use use this to update files ACROSS partitions. I am fine with
updating files that reside SOLELY within a partition.

It seems to me that Iseries SQL is crippled in that it cannot easily deal
with files across partitions.
"Better" is unfettered SQL access to update files in one partition using
data from files in any partition.

The method of using SQL, that I described, to pass record level data across
Partitions is very limited when you consider what SQL is capable of.

I am using parameters to pass data structures, where each data structure
contains a record.
I am tossing up ideas like perhaps passing a MODS populated by an SQL result
set that can be then dropped into a file in QTEMP. I was just wondering if
someone has done something like that.

Further I have an issue with Remote SQL requiring a PROFILE and PASSWORD at
COMPILE!!! time. And the password is not even hidden. My opionions on the
RPG SQL precompiler are well known.

We use Implementer, and for the life of me, I cannot work out how to do
Implementer Source Control for Remote SQL programs. The creation of the SQL
packages on the remote sites is a mystery to me, I do not understand it , I
just muddle along till I get it to work.

Regards
Frank Kolmann


date: Fri, 12 Dec 2008 07:20:54 -0800 (PST)
from: Nathan Andelin <nandelin@xxxxxxxxx>
From: frank kolmann
I was wondering if someone has a better way of doing this.

Just some rhetorical questions. A better way? Define "better". Is this a
pattern you're interested in applying to other >applications? Or is this a
one time application? I really don't know of a better way. I can think of
alternative ways.
You could define the remote file as a DDM file and use CHAIN to fetch a
record. You could use SQL CLI as an alternative to >embedded SQL. You
could evoke a Web service to return the data.
Perhaps "better" in this case is what you feel most comfortable with.

Nathan.

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.