Fujitsu V4 (COBOL97) - Build Fails

Anyone with experience using Fujitsu V4 (COBOL97) on W/2K? I'm looking
for tips or tricks to get this to work for batch oriented code, not
OOCOBOL.

What is happening is, my compiles run clean, but the Linker apparently
fails to output an .EXE. What I get is a message about "the respository
file" nor "source information analysis information file" was found.
"Database file generation is terminated."

I have installed the M/S Tool kit. I can't seem to determine why the
system "thinks" I'm doing OOCOBOL and not giving it any class info (or
whatever).

Again, what I am doing is building a batch oriented program.

Now it is interesting that I am using W/2K that has recently been
upgraded to SP4. Apparently prior to this upgrade, batch oriented
compiles had worked. [Meanwhile, Fujitsu says that V4 won't install on
W/2K and will complain that SP3 hasn't been installed. However, it did
install, and it did work fine several months ago when I was actively
working on developing a different COBOL based application.]

Again, if anyone has any tips as to what I need to feed the Linker or
change in the compile options, I'd be glad to hear it.
Regards,
Steve.T

> I have installed the M/S Tool kit.

Perhaps it has installed a new version of LINK.EXE that is incompatible
with the Fujitsu Cobol system.  Try changing the PATH in the
environment so that it uses the Fujitsu supplied LINK.

"steve.t" <sthompson@ix.netcom.com> wrote in message
news:1102909407.265351.117530@z14g2000cwz.googlegroups.com...
> Anyone with experience using Fujitsu V4 (COBOL97) on W/2K? I'm looking
> for tips or tricks to get this to work for batch oriented code, not
> OOCOBOL.
>
> What is happening is, my compiles run clean, but the Linker apparently
> fails to output an .EXE. What I get is a message about "the respository
> file" nor "source information analysis information file" was found.
> "Database file generation is terminated."
>
> I have installed the M/S Tool kit. I can't seem to determine why the
> system "thinks" I'm doing OOCOBOL and not giving it any class info (or
> whatever).
>

You ARE doing OO COBOL. It is an OO COBOL compiler...(The fact that your
source uses no OO COBOL constructs doesn't change it.)

You need to build this using the Project Manager so it can create the
necessary supplementary files it needs for proper linkage. If you run the
compile and the link as separate standalone activities it cannot be
guaranteed to work.


> Again, what I am doing is building a batch oriented program.
>

Are you "building" it? If you are, can you post a copy of the output from
the build?

Do you have the debugging option set? Is there a .SVD file produced?

> Now it is interesting that I am using W/2K that has recently been
> upgraded to SP4. Apparently prior to this upgrade, batch oriented
> compiles had worked. [Meanwhile, Fujitsu says that V4 won't install on
> W/2K and will complain that SP3 hasn't been installed. However, it did
> install, and it did work fine several months ago when I was actively
> working on developing a different COBOL based application.]
>
> Again, if anyone has any tips as to what I need to feed the Linker or
> change in the compile options, I'd be glad to hear it.
> Regards,
> Steve.T
>

I could probably help you, but I need to see more information.

Pete.

Gentlepeople:

Were I working in person with one or two others, I doubt that I would
be so blind and miss things like I am. I'm starting to feel like I did
back in the '70s when I started doing this kind of thing on S/360 &
S/370 machines.

So that there is no doubt, when I say I'm building something, then yes
I am BUILDing it. The following is from the .LOG file (with my comments
and before I fixed it):

Build Start.
DEL C:\VSSTRATEGIESSOFTWARE\OSPRPG2.EXE
DEL OSPRPG2.OBJ
C:\FSC\COBOL97\COBOL32.EXE -iC:\FSC\COBOL97\COBOL.CBI -M OSPRPG2.COB
STATISTICS: HIGHEST SEVERITY CODE=I, PROGRAM UNIT=1
C:\FSC\COBOL97\LINK.EXE  /OUT:C:\VSSTRATEGIESSOFTWARE\OSPRPG2.EXE
<<<<<   @C:\VSSTRATEGIESSOFTWARE\RPG_COM_TRANS\O
SPRPG2.001
Microsoft (R) 32-Bit Incremental Linker Version 5.02.7132
Copyright (C) Microsoft Corp 1992-1997. All rights reserved.
OSPRPG2.OBJ
C:\FSC\COBOL97\F3BICIMP.LIB
C:\FSC\COBOL97\LIBC.LIB
C:\FSC\COBOL97\KERNEL32.LIB
C:\FSC\COBOL97\PROJECT.RES
Build End.

Now that I've fixed it, I can move on to testing and debugging.

I'm starting to think I should just retire and go back to driving
semis...

Later,
Steve.T

> I have installed the M/S Tool kit.

Perhaps it has installed a new version of LINK.EXE that is incompatible
with the Fujitsu Cobol system.  Try changing the PATH in the
environment so that it uses the Fujitsu supplied LINK.

"steve.t" <sthompson@ix.netcom.com> wrote in message
news:1102909407.265351.117530@z14g2000cwz.googlegroups.com...
> Anyone with experience using Fujitsu V4 (COBOL97) on W/2K? I'm looking
> for tips or tricks to get this to work for batch oriented code, not
> OOCOBOL.
>
> What is happening is, my compiles run clean, but the Linker apparently
> fails to output an .EXE. What I get is a message about "the respository
> file" nor "source information analysis information file" was found.
> "Database file generation is terminated."
>
> I have installed the M/S Tool kit. I can't seem to determine why the
> system "thinks" I'm doing OOCOBOL and not giving it any class info (or
> whatever).
>

You ARE doing OO COBOL. It is an OO COBOL compiler...(The fact that your
source uses no OO COBOL constructs doesn't change it.)

You need to build this using the Project Manager so it can create the
necessary supplementary files it needs for proper linkage. If you run the
compile and the link as separate standalone activities it cannot be
guaranteed to work.


> Again, what I am doing is building a batch oriented program.
>

Are you "building" it? If you are, can you post a copy of the output from
the build?

Do you have the debugging option set? Is there a .SVD file produced?

> Now it is interesting that I am using W/2K that has recently been
> upgraded to SP4. Apparently prior to this upgrade, batch oriented
> compiles had worked. [Meanwhile, Fujitsu says that V4 won't install on
> W/2K and will complain that SP3 hasn't been installed. However, it did
> install, and it did work fine several months ago when I was actively
> working on developing a different COBOL based application.]
>
> Again, if anyone has any tips as to what I need to feed the Linker or
> change in the compile options, I'd be glad to hear it.
> Regards,
> Steve.T
>

I could probably help you, but I need to see more information.

Pete.

Gentlepeople:

Were I working in person with one or two others, I doubt that I would
be so blind and miss things like I am. I'm starting to feel like I did
back in the '70s when I started doing this kind of thing on S/360 &
S/370 machines.

So that there is no doubt, when I say I'm building something, then yes
I am BUILDing it. The following is from the .LOG file (with my comments
and before I fixed it):

Build Start.
DEL C:\VSSTRATEGIESSOFTWARE\OSPRPG2.EXE
DEL OSPRPG2.OBJ
C:\FSC\COBOL97\COBOL32.EXE -iC:\FSC\COBOL97\COBOL.CBI -M OSPRPG2.COB
STATISTICS: HIGHEST SEVERITY CODE=I, PROGRAM UNIT=1
C:\FSC\COBOL97\LINK.EXE  /OUT:C:\VSSTRATEGIESSOFTWARE\OSPRPG2.EXE
<<<<<   @C:\VSSTRATEGIESSOFTWARE\RPG_COM_TRANS\O
SPRPG2.001
Microsoft (R) 32-Bit Incremental Linker Version 5.02.7132
Copyright (C) Microsoft Corp 1992-1997. All rights reserved.
OSPRPG2.OBJ
C:\FSC\COBOL97\F3BICIMP.LIB
C:\FSC\COBOL97\LIBC.LIB
C:\FSC\COBOL97\KERNEL32.LIB
C:\FSC\COBOL97\PROJECT.RES
Build End.

Now that I've fixed it, I can move on to testing and debugging.

I'm starting to think I should just retire and go back to driving
semis...

Later,
Steve.T

Glad you sorted it, Steve.

Pete.


"steve.t" <sthompson@ix.netcom.com> wrote in message
news:1102952760.319839.158310@f14g2000cwb.googlegroups.com...
> Gentlepeople:
>
> Were I working in person with one or two others, I doubt that I would
> be so blind and miss things like I am. I'm starting to feel like I did
> back in the '70s when I started doing this kind of thing on S/360 &
> S/370 machines.
>
> So that there is no doubt, when I say I'm building something, then yes
> I am BUILDing it. The following is from the .LOG file (with my comments
> and before I fixed it):
>
> Build Start.
> DEL C:\VSSTRATEGIESSOFTWARE\OSPRPG2.EXE
> DEL OSPRPG2.OBJ
> C:\FSC\COBOL97\COBOL32.EXE -iC:\FSC\COBOL97\COBOL.CBI -M OSPRPG2.COB
> STATISTICS: HIGHEST SEVERITY CODE=I, PROGRAM UNIT=1
> C:\FSC\COBOL97\LINK.EXE  /OUT:C:\VSSTRATEGIESSOFTWARE\OSPRPG2.EXE
> <<<<<   @C:\VSSTRATEGIESSOFTWARE\RPG_COM_TRANS\O
SPRPG2.001
> Microsoft (R) 32-Bit Incremental Linker Version 5.02.7132
> Copyright (C) Microsoft Corp 1992-1997. All rights reserved.
> OSPRPG2.OBJ
> C:\FSC\COBOL97\F3BICIMP.LIB
> C:\FSC\COBOL97\LIBC.LIB
> C:\FSC\COBOL97\KERNEL32.LIB
> C:\FSC\COBOL97\PROJECT.RES
> Build End.
>
> Now that I've fixed it, I can move on to testing and debugging.
>
> I'm starting to think I should just retire and go back to driving
> semis...
>
> Later,
> Steve.T
>
>