If this is not the appropriate forum, could someone please let me know?
Thanks.
I'm part of a very heterogeneous distributed development team, and a
clash of cultures is causing some very significant problems. It's
taking us far too long to get the people with the proper permissions to
compile and bind COBOL stored procedures on our MVS DB2 test and
deployment environments. The bureaucratic hurdles to getting these
permissions ourselves have for months been insurmountable, and I
recently had what I hope is a brainstorm. (Maybe it's just a
brain-tropical depression, though. :-) )
I would like to duplicate our database on a local Windows version of
DB2, and compile and bind the COBOL to this instance. Then the
bureacrats can take as long as they like about the deployment
environment, and we can still do our development.
I've found some DB2 documentation [1] that explains how to connect Micro
Focus COBOL and IBM COBOL to DB2. We have an older, unsupported,
version of Micro Focus, but it might do in a pinch. My concern is that
using this involves invoking "nmake", a tool I know nothing about. And
spending the time chasing down and learning a build tool in order to
speed up our development process seems... well, counterproducti ve.
So I was wondering if anyone knew of relatively straightforward ways of
connecting COBOL stored procedures to DB2 inside Windows; any free or
inexpensive COBOL compiler is okay, but I'd love to use an open-source
one if possible. We are running DB2 UDB v7.
Thanks for any help you can offer.
-- Scott Sauyet, sc***@sauyet.co m
[1] http://tinyurl.com/2hy6u
https://aurora.vcu.edu/db2help/db2ax/frame3.htm#embed
and many similar pages