RE: DDM experiences

I have a somewhat-related question.
Today, we have a single box with production and test libraries. It works,
but is scary sometimes. During the next upgrade cycle (6-12 months away) we
plan to either 1) upgrade to a bigger box to LPAR or 2) upgrade a little
less and get a separate development machine.
I am interested in a strategy to refresh the test database from production.
I'm leaning toward DDM, but haven't used it before. Does it make near
real-time updates, or batched? Can it be batched or periodic updates? We
have some fairly large and high-volume files we would keep updated. I'm not
looking toward a mirroring solution today, just a way to get data from a
production machine/partition to a test machine/partition.

TIA,
Loyd

-----Original Message-----
From: Buck Calabro [mailto:Buck.Calabro@commsoft.net]
Sent: Thursday, June 06, 2002 2:12 PM
To: midrange-l@midrange.com
Subject: RE: DDM experiences


>I am looking for some feedback and/or
>experiences with DDM files.

Classic trade-off between 'fast to deploy', 'easy to use' and 'fast
performance'.  Pick any two and the other one suffers.

>My previous experience using them
>was so-so and at least 8 years
>ago or so.

'So-so' doesn't really describe the issues you encountered.  Fundamentally,
DDM files are unchanged from S/38 days.  There are a few more objects that
DDM can use, but nothing mind-boggling.

We have a low-volume in-house application that used to run on machine A.
Then we got machine B and some developers sign on to that box exclusively.
DDM files were the simplest answer to this conundrum (database on one box,
programs on two.)  When I say low volume, I mean a few hundred transactions
a day.  Hasn't needed changes since it was implemented 6 years ago.
  --buck
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.