Re: EOF location?


"HeyBub" <heybubNOSPAM@xxxxxxxxx> wrote in message
news:127m0hs2180amf2@xxxxxxxxxxxxxxxxxxxxx
Pete Dashwood wrote:
I've got copy books with both conditions and I suspect this
inconsistency is screwing up PowerCOBOL's "#INCLUDE" commands. (I
suspect this because I get the dreaded "...error in .SVD file
according to INCLUDE or COPY turnip...")

Fell into the old PowerCOBOL #include trap, huh :-)... best avoided.
I used it for a while then completely scrapped it.

I was advised to use #INCLUDE in the DATA DIVISION and COPY in the
PROCEDURE DIVISION by a factotum at Fijutsu some time back.

Yes, I wasted several weeks following the advice I received regarding
undocumented dialogs appearing out of COM components written in PowerCOBOL.
In the end I solved it myself by rewriting the whole lot in OO NetCOBOL.

Their support has been abysmal and it is one of the reasons I didn't
upgrade.


Be that as it may, I've diligently gone through the program at issue,
replacing all #INCLUDE and COPY statements with their corresponding source
modules. I *still* get the error:

"An error was found in the debug information file. File
name=BISNS310A.svd Please correct a program when corresponding to notes of
#INCLUDE and COPY."

Have you tried compiling with debug options off? (Turn OFF TEST)
Have you made sure that the .SVD file is in the SAME DIRECTORY as the
executable?
Check comments in your INCLUDE file. Make sure that asterisks or NOTE
statements are in the right place and legal.
If you are compiling some of the app. from a Fujitsu COBOL Project and other
parts of it from external files, this can be problematic. Best to include
all required modules in the Project and let it generate the appropriate MAKE
file.


What's the circumvention? (I've tried the extremes of cursing and prayer.)
If none of the above Band Aids help, mail me the Project File, with the
#INCLUDEs and COPY statements expanded as you noted. I can establish whether
the problem is in your environment or the source code.

Pete.


.