Contractor42
Programmer
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.
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.