What is equivalent of STATE option ?
Michael R Linn
Does anyone know what the COBOL 2 equivalent is for the "STATE" compiler
option that was used in VS COBOL?
(With the STATE compiler option, if the program ABENDs
(such as division by zero), the run-time listing will show the actual
COBOL statement number where the ABEND occurred).
I tried using "FDUMP", but it didn't seem to tell me which statement it
was. I also tried "TEST" which yielded nothing new.
Finally I tried "TEST(ALL,SYM)" and "TEST(STMT)", and the compiler
rejected them as invalid compiler options.
Anyone know?
...
J Lenz
If you are using FDUMP and OPTIMIZE, then you will not get a line number
for the ABEND, but rather the HEX address (offset, perhaps) of where the
error occurred. Use that address to compare to you compile listing, and
you should be able to locate the line within the compile listing where
the error occurred. Also, FDUMP will display the value of program
variables at the time the ABEND occurred. We are a VSE/ESA shop.
Joseph Lenz
TTI, Inc.
Fort Worth, TX
bu...@bellatlantic.net
In article <33DE79...@arlington.net>,
just to add something to the confusion. sometimes, if not most of the
time, the HEX address given is the next instruction to be processed and
not the actual address. so when you check the compile listing, look for
the address just before (or less than) the given address.
Rob Canuel
-------------------==== Posted via Deja News ====-----------------------
http://www.dejanews.com/ Search, Read, Post to Usenet
Kevin Cabral
To really not directely answer the question, I would highly recommend
purchasing a dump formatter such as Abend-Aid. This will solve your
problem and provide other assistance. This tool runs under the
operating system and provides hooks which are used when an abend
occurs. I have used this for many years, and the productivity time
increases--particularly when its 2:00 am.
Good Luck
Kevin
Jeff Raben
>> Michael R Linn wrote:
>> >
>> > Does anyone know what the COBOL 2 equivalent is for the "STATE" compiler
>> > option that was used in VS COBOL?
>> for the ABEND, but rather the HEX address (offset, perhaps) of where the
>just to add something to the confusion. sometimes, if not most of the
>time, the HEX address given is the next instruction to be processed and
>
>
Adding more to the confusion...
You have to find the program origin via link/load maps.
Then you can find the problem.
JR
and stir with a Runcible spoon...