Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Microfocus COBOL 3.2.43 (16bit) 1

Status
Not open for further replies.

Contractor42

Programmer
Dec 20, 2006
1
CH
One of my current contract tasks is to put a old, vulnerable application based on 16bit code on a firmer footing by researching, documenting and testing changes to it.
Build architecture is Windows NT4 SP4, Microfocus COBOL 3.2.43, Gupta SQL Pre-Compiler 2.5.2, SLQ*Base9.
Prod. platform is NT4 SP6, XP SP1. Will be XP SP2 in 2007, and likely to be Vista before the system is decommissioned.

Yes I realise this is stone age stuff but there is no budget to re-compile as 32bit COBOL or rewrite using Visual Studio.

Have had some success understanding the components that need to be in place to amend, pro-compile, compile and link and built a second working build PC.
Will be trawling though the help files next (there are no manuals).

It would be great to get in touch with anyone who is using a 16bit version of Microfocus COBOL, or who has used it relatively recently.

The Client, an Global Insurer, appreciate the situation is risky - that's why I'm onsite! If anyone knows of any immiment dangers presented by staying with 3.2.43 I would especially like to hear from them.
 
No budget to upgrade the compiler/runtime but there is money to upgrade to Vista? Go to your boss and ask or an assistent. His name has to be "Sancho Panza".....

The only thing you need to worry about fighting these windmills is installing the old compiler/runtime on those "modern" operating systems. I remember trying to install MF4 workbench (32bit sorry) on XP. These are options to tell the O.S. that it is dealing with a win95 application. That solved the issue back then. When that does not work try to arrange for a virtual-NT4 machine and install you run-time there.

Once you've got the software installed your cobol-worries are over. The good-old-16 bit MFcobol is rock-solid. As long as you are dealing with cobol-code that is: you must examine the source for acient API calls. I remember 16-bit cobol calling 16-bit API's on a 32-bit O.S. But that was OS2-warp, they do not make them as good as that any more....

Hey! It is no windmill, it's a GIANT. Attack attack!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top