Flat packing an IDMS database

I am still looking for a solution that will flat pack an IDMS database
prefereably to a readable file on a PC or UNIX and still make it
readable if required. The organization I am working for will be getting
off the mainframe (and IDMS) shortly. They are not migrating any of
their archived data but there may be a sllight business/lagal need to
gain access to that data.

There is a strong preference for the solution to be 1. PC or UNIX based
2. Not require a lot of programming to pump the data out 3. Quick to
implement.

I would be interested to hear any proposals/recommendations from vendors
or IDMS0Lers with experience in this area.

I am still looking for a solution that will flat pack an IDMS database
prefereably to a readable file on a PC or UNIX and still make it readable if
required. The organization I am working for will be getting off the
mainframe (and IDMS) shortly. They are not migrating any of their archived
data but there may be a sllight business/lagal need to gain access to that
data.

There is a strong preference for the solution to be
1. PC or UNIX based
2. Not require a lot of programming to pump the data out
3. Quick to implement.

I would be interested to hear any proposals/recommendations from vendors or
IDMS0Lers with experience in this area.

Normal
Re: lines of ADS code
"My simple mind came up with a thought to punch out the dialog processes
from the dictionary into a pds, then edit out the idd statements, and
then look at the ISPF editor line count. Of course adso provides built
in functionality that comes with the software from the vendor, and i
dont know a way to count that. screen displays for example, would
require many lines of code in CICS command level coding, that in
adso/mapping would be done automagically. Ah, the beauty of IDMS.