× 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.



Darryl,

I'm having a tough time understanding your last statement. Are you saying
that you can't use something like
create table rob.scrapme as (
SELECT * FROM gdihq.rob.brms WHERE LIBRARY = '*IFS')
with data
because of either of two reasons:
1 - This is all done locally on the 2 LPARs.
2 - There is no code other than native IBM_i code here.

I have done this between two lpars on the same machine. And between lpars
of machines in two different cities. So, what you are saying doesn't
compute with me. Or, were you trying to say that you're using a small
data set and it's local so efficiency is not a concern? That, maybe I
could understand. Coding for some efficiency, as long as you don't get
too extreme, isn't a bad habit to get into. What you code for a small
local sample seems to be the same code that someone will copy and modify
for a large dataset between different platforms between different
continents. I'm not saying you need to seriously bit twiddle but
definitely cover this big bang for the buck stuff.

Looking at your second statement: "There is no code other than native
IBM_i code here."
I suppose that leaves out any RPG solutions since you have to buy a
compiler for that.
Then maybe using the ibm command RUNSQL is an option?
RUNSQL SQL('create table rob.scrapme as (SELECT * FROM gdihq.rob.brms WHER
E LIBRARY = ''*IFS'') WITH DATA') COMMIT(*NONE) NAMING(*SQL)
or putting the statement into a source member and using RUNSQLSTM against
that source member?

Or by "native" did you limit yourself from any imbedded SQL programming?
If that is the case, are you limited from any imbedded SQL programming
because you do not have "5770ST1-IBM DB2 Query Manager and SQL Development
Kit for i"? If you do not have that product many people use SQL-CLI or
sql call level interface. Which, at first glance, seems really different,
unless you have done some sql within other languages.

Or by "native" do you mean some philosophical thing that if it couldn't
have been coded on a S/36 or earlier then that is just too new fangled and
won't be accepted in your shop?

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.