Article View: comp.lang.cobol
Article #144Re: DAT and IDX files
From: Ed Guy
Date: Wed, 21 Aug 2002 20:36
Date: Wed, 21 Aug 2002 20:36
42 lines
2763 bytes
2763 bytes
James J. Gavan wrote: > > Ed Guy wrote: > > > Joanna �wik�a wrote: > > > > > > Hello, > > > > > > I am not a COBOL programmer, and I don't know much about this language :-) > > > but there is a big problem with it. I'm working on a program in C, which has > > > to process data contained in COBOL indexed files. I have .DAT and .IDX file, > > > and file specification, i.e. > > > 5 FIELD1 > > > 10 FIELD11 9(2) > > > 10 FIELD12 9(2) > > > etc. > > > Now my question: how to translate DAT files into text files? Is this a valid > > > DAT specification? Are there any non-commercials translators? > > > > I don't know about FREE translators, but ParseRat (http://www.parserat.com/) is only > > $49.95. It will quite happily translate your DAT files (look in the help file for > > "binary files"). > > > > As others have noted, the IDX files are indices - normally when you move a database > > table from one system to another you need to re-generate the indices in the new system. > > > > Just as a point of interest Ed, as Judson just mentioned it. Will Parserat handle Micro > Focus data compression ? Sorry, it won't - I don't have the algorithm. Also, of course, Micro Focus COBOL is not the only system which uses the DAT extension so it would be a bit tricky to assume that every DAT file came from it. -- Ed Guy P.Eng,CDP,MIEE Information Technology Consultant Internet: ed_guy@NOSPAMguysoftware.com remove NOSPAM from email address. http://www.guysoftware.com "Check out HELLLP!, WinHelp author tool for WinWord 2.0 through 2000, PlanBee Project Management Planning and Scheduling and ParseRat, the File Parser, Converter and Reorganizer"
Technical Details
Message-ID:
<3D63F9D1.278A@paralynx.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!nntp.itservices.ubc.ca!paralynx!van-bc!deep!not-for-mailReferences:
<ajvgid$gu3$2@news.tpi.pl> <3D63A99C.16D0@paralynx.com> <3D63CFF0.E443439B@shaw.ca>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII X-Google-Thread: 10ff81,333b89d2ebd0bce3 X-Google-Attributes: gid10ff81,public X-Google-Thread: 10d15b,333b89d2ebd0bce3 X-Google-Attributes: gid10d15b,public X-Google-Thread: 10585b,333b89d2ebd0bce3 X-Google-Attributes: gid10585b,public X-Google-ArrivalTime: 2002-08-21 13:40:14 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!nntp.itservices.ubc.ca!paralynx!van-bc!deep!not-for-mail Message-ID: <3D63F9D1.278A@paralynx.com> Date: Wed, 21 Aug 2002 13:36:33 -0700 From: Ed Guy <ed_guy@paralynx.com> Organization: Guy Software X-Mailer: Mozilla 2.02 (Win95; I; 16bit) MIME-Version: 1.0 Newsgroups: comp.lang.cobol,fj.comp.lang.cobol,ibm.ibmvm.cobol.cforum Subject: Re: DAT and IDX files References: <ajvgid$gu3$2@news.tpi.pl> <3D63A99C.16D0@paralynx.com> <3D63CFF0.E443439B@shaw.ca> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Lines: 42 NNTP-Posting-Host: l103.nwm.dial.mindlink.net X-Trace: deep 1029962139 2474 204.174.30.103