how can I map Cobol programs?

                Tal Systems' COBOL FD Analyzer - COBFD
                         Version 1.50 August 1999
                   by Michael Mattias dba Tal Systems
 
COBFD is a tool for COBOL programmers. Very simply, what it does is parse
a COBOL source file (either a copylib or complete source), identifies all
group and  elementary data items, then breaks down all '01' and subordinate
group items into their components and produces a report file showing the
size in bytes and the offset within the '01' record of every subordinate
data item. All group and elementary data items are included. The user has
an option to include the input file in the report output (follows analysis).
 
COBFD supports all levels of REDEFINES and OCCURS: REDEFINES which OCCUR,
OCCURS which OCCUR while REDEFINE'ing an item which OCCURS; OCCUR'ing
group items with mixed data types. These are typically the greatest
challenges to counting bytes "by hand".
 
COBFD runs on MS-DOS and compatible PC's and requires DOS 2.0 or higher.
It will run in a DOS session under Windows(r).It is a single user 
program; there is no provision for sharing files, but the program has 
been run on a network.
 
The program creates and deletes an internal workfile, COBFD@@.WRK, in
the  user's current directory.
 
Both the input and output files are user-specified at run time. The output
file is 80 bytes per record, formatted, with page headers (all text).
The user must provide a file viewer/printer for screen or printed output.
 
COBFD is not intended as a general-user-community product. It is provided
for COBOL programmers who have a need for detailed offset information about
datanames. Typical uses include writing reports in SyncSort, checking data
during conversions and adding new REDEFINES datanames into existing software.
 
It is also intended as advertising for the author.
 
To use the COBFD program interactively:
 
   COBFD <Enter>
 
You will be given a screen with boxes for input file and output file.
(The mouse is not enabled on this screen).
 
For the input file, the user may simply type the name of the input file.
Drive and/or path may be included in the filename. Pressing ALT+D will
bring up a pickbox of files; while in the pickbox, the user may "navigate"
directories by pressing <Enter> or clicking the mouse on a highlighted
directory entry.  The user's "current" directory is unaffected.
 
The user must type the name of the output file; drive and/or path are optional.
 
Processing is initiated by pressing F10. A brief "Processing" message is
displayed. 
 
After a source file is processed, the user will be asked if he wants to
do another file; if yes, the input and output files must be reentered.
 
The output file is always opened "new" and will erase any previous file
with that name. The presence of an existing file with the same name as
the user output file is NOT CHECKED.  To append to an existing output
file, you must run in command mode.
 
To use the COBFD program from the command line or in a batch file, enter
four parameters separated by semicolons, commas or spaces:
 
[drive]:[path]COBFD SourceFile;OutputFile;IncludeSource;Append;CompStorage
 
SourceFile     = Cobol input file, drive/path optional 
OutputFile     = Disk File for report, drive/path optional
IncludeSource  = Y or N (any other character is an error)
Append         = Y will append the report to the specified output file 
                 if found, or create a new output file if not found.
                 N will always open the report file OUTPUT, erasing
                 any previous report file.
CompStorage    = Used for COMP, COMP-4 and COMP-5 only. B is byte storage;
                 storage is based on the minimum bumber of whole bytes
                 required. W is Word storage; data sizes are rounded 
                 up to the next 2, 4 or 8 bytes.
                 For reference: IBM mainframe COBOL uses WORD storage;
                 Microfoucus Personal Cobol for MS-DOS uses BYTE storage.
                 Consult your COBOL system manual and/or compile scripts
                 for the option used with your programs.
 
                 For upgraders from versions of COBFD prior to 1.50:
                 Previous versions used BYTE storage only.
 
If drive and path are not specified, the current directory is used.
 
If any parameter is in error, COBFD exits with a return code (DOS errorlevel)
greater than zero. A return code of '8' indicates an error with the command line
 
COBFD /H   or COBFD /?
Displays the syntax for the command-line options.
 
Sample Batch files:
 
COBFD  File1.cbl;Report1.txt;Y;N;W
COBFD  File2.Cbl;Report1.txt;Y;Y:B
 
Reports on File1.cbl and file2.cbl. When doing file1.cbl, the append
option is "N" so the report file report1.txt is created new. Byte storage
is assumed.
When doing file2.cbl, the append option is "Y" so the report is appended
to file report1.txt. Word Storage for COMP items is assumed.
 
Another batch file:
 
IF exist LIBFILE.TXT del libfile.txt
FOR %%F IN (*.cbl) DO COBFD %%F;LIBFILE.TXT;Y;Y;W
 
Print one report file, LIBFILE.TXT, containing all *.cbl files in 
the current directory.(word storage)
 

What Tal Systems' COBFD COBOL FD Analyzer assumes:
 
A valid COBOL FD. If PICTURE clauses are missing or illegal, sentences are
not terminated with a period, or levels are inconsistent, the program
will return unreliable data, generally without a warning.
 
If column seven (7) of the input file is non-blank, the line is a comment.
 
All PICTURE, OCCURS, REDEFINES, USAGE DISPLAY|COMP|SIGN SEPARATE and other
COBOL keywords appear in columns 13-72 . These clauses may, however, span
multiple physical lines with comment lines interspersed. The order in which
keywords appear is immaterial. A COBOL sentence is not terminated until
a non-quoted period is found.
 
The QUOTE character is the first double-quote (") or apostrophe (') found
in a non-comment input record. The QUOTE character is redefined for each
file processed during a program run; i.e., the user can process multiple
files, some using quote and others using apostrophe as the literal delimiter.
 
A REDEFINES clause below the '01' level assumes that the area being
redefined is the same size as the redefined area. (Not an ANSI COBOL
requirement). If this is not true, the program will appear to finish
normally, but the data may be erroneous. REDEFINES is ignored at the
'01' dataname level.
 
When parsing the input file, if the first two words in a non-comment line
are PROCEDURE and DIVISION, the program stops looking for data; however,
if printing the input file, it prints the entire file.
 
RENAMES ('66-level') clauses are not supported
 
SYNC clauses are not supported.
 
PICTURE clauses containing "P" (scaled numeric) are not supported.
 
POINTER and PROCEDURE POINTER data items are not supported
 
USAGE BINARY is considered USAGE COMPUTATIONAL.
 
USAGE PACKED-DECIMAL is considered USAGE COMPUTATIONAL-3
 
COMP, COMP-4 AND COMP-5 are used for Binary integers. COMP-3 is
Binardy-coded-decimal, often called "packed."
 
Only EJECT, SKIP1, SKIP2, COPY and ++INCLUDE are recognized as
compiler directives (treated as comments). Other directives may
cause the program to insert an extra SYSTEM-GENERATED-01-DATANAME
in the output following the directive. The offset information should
not be affected unless the unsupported directive is contained within
the physical boundaries of an explicit or implicit '01' dataname.
 
No form of COPY is supported; but copylibs themselves may be analyzed.
 
If an '01' record is not found as the first COBOL data item, the system
creates one with the name SYSTEM-GENERATED-01-DATANAME. This allows the
program to be used with copylibs not containing an '01 -level' dataname.

A FEW EXTRA NOTES:
 
The mouse is enabled in the file pickoff box, but not in the input screen.
The mouse may not work under Windows 98; it appears to be sensitive to
when, if ever, an MS-DOS mouse driver is loaded during the Windows boot.
 
The file COBELEM.COB is included. This is an FD containing most of the possible
elementary numeric data types. In as much as the author does not have
access to all types of operating systems and/or COBOL compilers, he provided
this so that the user can see what the size of elementary items are. Should
some system(s) require additional numeric data types, notify the author
and they will be considered for a future release.
 
COBFD is a copyright product. It may be freely used and distributed without
payment or registration. However, it may not be distributed for monetary
consideration, either standalone or "bundled" with other utilities,
applications or instructional material without the permission of the
copyright owner.
 
Distribution to individual programmers is encouraged.
 
Copyright 1996, 1998 Michael C. Mattias dba Tal Systems, Racine WI USA.
 
HISTORY:
v 1.0  August 1996. Never released to the public.
v 1.1  September 1996. Never released to the public.
v 1.2  November 1996 (released).
v 1.21 December 1996 Fixed bug: bad offset when dataname level drops
       directly from, say, '07' to '03' and a dataname at an intervening
       level (e.g.,'05') since the last '03' had an OCCURS clause.
v 1.30 May 1997. Supports 15 character picture clauses, supports COMP at 
       the group item level, does not display each dataname, fixed bug
       I thought was fixed in 1.21, fixed limitation of 32767 maximum
       size of any data item, fixed data type of display numeric with "V"
       in PICTURE IS clause to be "numeric" rather than "numeric edited," 
       cosmetic output changes, update this document.
v 1.40 November 1998. Added support for command-line operation;
       updated this document.
v 1.41 March 1999. Added support for PACKED-DECIMAL (treated as COMP-3);
       updated this document. Not released to public pending beta tests.
v 1.50 August 1999. Added options for Byte and Word storage of COMP
       data items; minor cosmetic changes; updated this document.
 
The author would appreciate any comments, remarks, bug reports, or
desired enhancements be submitted to:
 
Michael C. Mattias dba Tal Systems
5329 Charles St. 
Racine, WI 53402-2119 USA
414-681-3895
EMail  michael.mattias@gte.net
                                              

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:
126:
127:
128:
129:
130:
131:
132:
133:
134:
135:
136:
137:
138:
139:
140:
141:
142:
143:
144:
145:
146:
147:
148:
149:
150:
151:
152:
153:
154:
155:
156:
157:
158:
159:
160:
161:
162:
163:
164:
165:
166:
167:
168:
169:
170:
171:
172:
173:
174:
175:
176:
177:
178:
179:
180:
181:
182:
183:
184:
185:
186:
187:
188:
189:
190:
191:
192:
193:
194:
195:
196:
197:
198:
199:
200:
201:
202:
203:
204:
205:
206:
207:
208:
209:
210:
211:
212:
213:
214:
215:
216:
217:
218:
219:
220:
221:
222: