Cobol programs won't compile after installing .net visual studio 2003

We have two developers that have an old version of cobol installed on their workstations to support a couple of old programs. However we are moving to .net and they recently installed all the new .net software and it has caused cobol to stop working.

They installed:
.net visual studio 2003
SQL server developer & SP3a
Visio 2003
and local IIS
On a windows 2000 pro sp4 machine.

The version of cobol is Micro Focus cobol 4 for windows (98/NT) but it works on 2k.

The error pops up when trying to compile a program using a batch file and the command:

CBLLINK %1 C:\ORAnt\PRO80\LIB\SQLLIB80.LIB,c:\cobol32\lib\cobintfn.obj

These are the errors:

ERROR: (1) Cannot open file :  adis.obj
ERROR: (1) Cannot open file :  adisinit.obj
ERROR: (1) Cannot open file :  adiskey.obj
ERROR: (1) Cannot open file :  adisdyna.obj
ERROR: (1) Cannot open file :  mffh.obj
ERROR: (1) Cannot open file :  xfhname.obj

Anyone have any ideas?

Thanks!
Mike
LVL 1
tonkajeep34Asked:
Who is Participating?
 
reginabConnect With a Mentor Commented:
have you tried reinstalling the cobol, and that has failed, it seems the install has removed or altered the .obj's have you looked them up, are they still where they were?  did the .net install alter your path, you might need a manual adjustment to the path so the cobol files are found correctly.
0
 
tonkajeep34Author Commented:
I have not tried reinstalling yet, we did check and the files are still there(they could be corrupted though). ALso .net did alter the path to add it's info, however the cobol directories are still there. Which is what i thought the problem was...

 I'm looking for the CD's to resinstall, Any other suggestions while i'm looking?

Thanks
Mike

0
 
reginabCommented:
well the other thing I was thinking about the path is that the cobol stuff might have been higher before, the .net stuff may have put themselves before it, and perhaps they have the some of the same files, and this could be a problem too. so you would want to locate the cobol stuff higher then.  but if that does not help then the files are likely corrupted.  and then I hope you find your disk :D
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

 
tonkajeep34Author Commented:
I'll have to try that and see what happens.

Yeah i hate it when software grows legs....
0
 
tonkajeep34Author Commented:
I tried moving the path with c:\cobol32\lib and c:\cobol32\exedll to the front of the path and after a reboot it still does not work. I found the CD's, however running the install keeps failing at the very end.

Any other Ideas?

TIA

Mike
0
 
reginabCommented:
hmmm that is very interesting, well I wonder if there is an upgrade of the cobol install, since you have found the cd's likely they would have any code on or near them that you may or may not need.  is that a possible option.  I think you have some kind of compatibility issue here, were there any strange things with the install of
.net visual studio 2003
SQL server developer & SP3a
Visio 2003
and local IIS
On a windows 2000 pro sp4 machine.

wonder also if there is not a place, an options or a configurations where you could manually set these paths, if they are corrupted that might be an option too.  sorry not to be of more help.
0
 
tonkajeep34Author Commented:
Yes there is a newer version of the cobol software, however we are only using this for a product that we are phasing out and we don't want to spend $30,000 on it when we won't need it in another year....

I tried the install on an xp machine, really blew up there.

I'm now trying it on a windows 98 machine to make sure it works... Maybe i'll just put a 98 computer over there for them to use.

As far as the strange issue with .net and the other software, they went in just like they should and work fine.

Mike

0
 
reginabCommented:
yep that is a shame, I hate it when they forget backwards compatibility, really burns me up.  I hope it goes together for you on the 98 machine.
0
 
tonkajeep34Author Commented:
It appears that .net and cobol (older versions anyways) do not play well together. I've installed it on a fresh 2k machine and it's working... they'll just have to deal with seperate machines.

Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.