RE: New application using remote databases from RPG program

["McGovern, Sean" <Sean.McGovern@xxxxxxxxxxxx>]

The issue that I have with DDM is that if you wanted to access 100
tables on another system, you have to setup/maintain 100 DDM files.

With DRDA, just one Connect statement is needed.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: 04 February 2010 22:38
To: Midrange Systems Technical Discussion
Subject: Re: New application using remote databases from RPG program

Interesting you recommend this article - because Elvis points out the 
same thing I did - this is all doable with DDM RLA.

I have no problem with using embedded SQL (DRDA) other than the extra 
code to manage all the connections. With DDM, that is implicit in the 
DDM files. The code will be cleaner, seems to me.

Now the OP could use USROPN on the DDM files, too. Whether using DDM or 
embedded SQL, seems to me he will be processing one remote system at a 
time. It's kind of a wash, but I'd still lean toward DDM for its 
simplicity and robustness - hey, it's legacy!! It ain't gonna break!! 
Probably!!

Multiple simultaneous connections don't seem to gain anything here, so 
far as I can tell.

:-)

McGovern, Sean wrote:
> Go for DRDA !
>  
> Check
>  
http://forums.systeminetwork.com/isnetforums/showthread.php?t=65101&high
light=connect
>  
>
> ________________________________
>
> From: midrange-l-bounces@xxxxxxxxxxxx on behalf of Vern Hamberg
> Sent: Thu 04/02/2010 19:14
> To: Midrange Systems Technical Discussion
> Subject: Re: New application using remote databases from RPG program
>
>
>
> If I'm not mistaken, he can have names for DDM files that differ but
> point to the same-name PF on different machines, right? Then he can
list
> them all in his RPG and open them all if he wants. You still have to
> read each one on its own, but this seems like a VERY simple thing to
do.
> And simple makes for much better maintenance down the road.
>
> Legacy-phlegacy!! Go for DDM!!
>
> JMHO
> Vern
>
> Nathan Andelin wrote:
>   
> > Okay, it sounds like SQL may be the best way to retrieve the remote
data in this case.  Whether you use SQL / DRDA or RPG Record Level
Access / DDM may also depend on how normalized the remote files are.
But, it sounds like SQL / DRDA may work best in your case.
> > -Nathan.
> >
> >
> >
> > ----- Original Message ----
> > From: sjl <sjl_abc@xxxxxxxxxxx>
> > To: midrange-l@xxxxxxxxxxxx
> > Sent: Thu, February 4, 2010 10:30:24 AM
> > Subject: Re: New application using remote databases from RPG program
> >
> > Nathan -
> >
> > We are gathering inventory balances and cost from the appropriate JDE
files
> > in all affiliates.
> >
> > This information, once gathered into one comma or tab-delimited file
in the
> > special environment, will then be FTP'd to be processed by a BI
application
> > running on a PC server.  Once the data is successfully obtained from
/all/
> > 52 environments, the client (another department within the company)
wants
> > the aggregated data sent all at once, not 52 separate times...
> >
> > - sjl
> >
> >
> > Nathan wrote:
> >   Steve,
> >
> >   What would be the purpose of transferring the data to the "local"
system?
> >   Why not just read remote data and output it to the client?
> >   Are we talking 5250 or browser?
> >   Would the new application be updating remote data, or just inquiry?
> >
> > Nathan.
> >
> >
> >      
> >  
> >     
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
>