Re: New application using remote databases from RPG program

Evan

Are you sure about needing an RDB entry when setting up a DDM file to connect with *IP? I just looked at the CRTDDMF help text, and there is no mention of RDB entries. Here is a snippet from the help text -


The remote location can take several forms:
- IP address in dotted decimal form. Specify an internet protocol address in the form nnn.nnn.nnn.nnn where each nnn is a number in the range 0 through 255. If this form is used, the address type of this parameter must be specified as *IP. - IP host domain name. Specify an internet host domain name of up to 254 characters in length. If this form is used, the address type of this parameter must be specified as *IP.
- If *IP is specified for the address type, the DDM server at the remote location must support the use of TCP/IP, and the DEV, LCLLOCNAME, RMTNETID, and MODE parameters will be ignored.

I just tested this - on the target machine, I ran this command to make it work -

CHGDDMTCPA AUTOSTART(*YES) PWDRQD(*NO)

That was all. Yes, this assumes a very closed system with trusted security. There are other settings, of course. Not related to RDB entries, though, right? Or is *ENCRYPTED related to those entries? I don't know offhand.

On the local machine I ran this command to create the DDM file -

CRTDDMF FILE(VERN/TESTDDM) RMTFILE(RJSIMAGE/DOCS00) RMTLOCNAME('xx.xx.xx.xx' *IP)

I verified that we do NOT have an RDB entry for this remote box.

It all works - I executed DSPPFM VERN/TESTDDM and came up with the right display.

Vern

Evan Harris wrote:

Hi Vern

Don't forget that there is maintenance required to make the DDM files simple
to set up.

If you set up the DDM files to operate over TCP you need to set up Remote
Database entries and you also need to be sure you've got the user
authentication entries set up.

If you use the DDM files via a SNADS connection then you have to set up the
SNADS stuff if it hasn't been done already and that is not a trivial job.
It's not unusual for lot of the SNADS utilities to have fallen by the
wayside over the years in favour of TELNET and FTP etc so the underlying
SNADS stuff that we tend to take for granted may not be as usable as
expected.

Of course if they have an existing SANDS infrastructure then you are 100%
right.

In terms of the original question I think I'd want to know how much data was
involved and whether it was practical for the other machines to extract the
required data and transmit it as an alternative to going out and collecting
it.

Regards
Evan Harris

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: Saturday, 6 February 2010 3:26 a.m.
To: Midrange Systems Technical Discussion
Subject: Re: New application using remote databases from RPG program

I agree - and I think I'm willing to pay that price. You pays your money, you takes your choice. Either approach has its benefits and drawbacks.

I think maintenance on DDM files is a minimal exercise - once set up, there's not usually a reason to do much with them. I'd hope that kind of thing is a one-time thing.

OTOH, with DRDA you have to define all those remote database entries. They need maintenance, too.

So the code might be simpler and shorter with DRDA, because of what you say - with DDM, you have to explicitly name each file - unless you can do overrides to a DDM file - haven't tried that.

So we go in with our eyes wide open and consider all the factors we can know, then pick something.

Time to leave for work
Vern