RE: COBOL File Specs to DDS or SQL

Food for thought - Put your COBOL specs into an empty COBOL program and
compile it with the *MAP option.

That will take the following record definition:

01 TEST-RECORD.
05 TEST-KEY PIC X(10).
05 TEST-DATA.
10 TEST-DATA1 PIC X(01).
10 TEST-DATA2 PIC 9(01).
10 TEST-DATA3 PIC S9(03) COMP-3.
10 TEST-DATA4 PIC S9(03)V9(02) COMP-3.

and produce the following results in the compile listing:

STMT LVL SOURCE NAME SECTION DISP LENGTH TYPE I-NAME
16 01 TEST-RECORD FS 00000000 17 GROUP .D006540
17 02 TEST-KEY FS 00000000 10 AN .D0065B6
18 02 TEST-DATA FS 00000010 7 GROUP .D006628
19 03 TEST-DATA1 FS 00000010 1 AN .D00669C
20 03 TEST-DATA2 FS 00000011 1 ZONED .D006710
21 03 TEST-DATA3 FS 00000012 2 PACKED .D006794
22 03 TEST-DATA4 FS 00000014 3 PACKED .D00681A

At least the second listing is easier to parse!

Have fun!
Richard

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Thursday, August 16, 2012 1:41 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: COBOL File Specs to DDS or SQL

On 16 Aug 2012 06:30, DrFranken wrote:

Suppose I had some COBOL specifications that defined a file layout.
Could I take those and programatically turn it into either DDS or an
SQL statement to create the file? The Specs are available in a file.

Thing is the record is 12,000 bytes wide and the COBOL specs are
4,500 lines long! Many are redefines and sub-fields which are not
needed. Doing this by hand seems daunting and fraught with peril.
Incoming file needs to be read, processed and then returned to
customer with delimiters between fields.

Help?