dick scherrer wrote:Hello,
A storage violation is caused by an attempt to use storage that is not accessable.
Which would mean that it is not in the dump. You need to determine the problem instruction and then look in the dump for the address that is being referenced.
How would looking at TS queue data help solve this?
hello I ain't stupid I wanted to find the TS queue to see the length of the queue record that was retrieved but I found it and it was not the cause of the storage violation so then I looked harder and found more things wrong. (yes there are many coding issues with this program).
However issue now is to find the working storage for the offending program in the Storage Vioaltion dump.
I have resolved MANY storage vioaltions and SVC dump not all of us with funny names are junior programmers or windows experts converting to Mainframe.
I have found the offending instructions now im trying to find the datafields so I can check table indexes etc so I can see why it occurred.
a 2K table managed to write over 27k of storage until I see the index value I have no clues as to what went wrong.