With a similar system, we purchased Arcad
(
http://www.arcadsoftware.com/) 3 years ago and have been incredibly
happy with it. The product reads and analyses your source files and
creates a repository that cross walks everything including QM queries
and WRKQRY queries. We have the simple green screen version of the
product and it has worked wonders in our shop - giving us a tool to
maintain code that has been in production for over a decade and written
by some twenty or thirty different programmer, most of who are not here
anymore.
-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Buening
Sent: Thursday, October 07, 2010 11:42 AM
To: cobol400-l@xxxxxxxxxxxx
Subject: [COBOL400-L] Cobol/DDS Consulting Groups
Working at a small company that has your basic DDS file structure and
Normal I/O access besides some embedded SQL in COBOL mixed in. We use
IBM
for the server/software, but seems like biggest issues for us is adding
fields to our main files. One issue is for all these years there never
was
a logical layer standard put in place, so most programs read the
physical
directly and some do use logicals. Most logicals were compiled and have
not been look at for years. Just wondering what other places that
mostly
use COBOL have done, do you use a change management system, have a
logical
layer in place, or like us just have to recompile bunch of programs?
Also, does anyone have any good references of companies or consultants
that
have come in and given some recommendations of processes and things you
could change mostly database design?
Thanks,
Jeff
Located in Ohio
midrange.com
