Subject: SYSTEM-F-ACCVIO, access violation, reason mask=04

[minnu]

I got the following access violation error.

%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=000000007FFC
FB82, PC=0000000000041A24, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
CUSTUPLD CUSTUPLD CUSTUPLD 483 000000001A24 0000000000041A24
CUSTUPLD 0 00000000000B6E40 00000000000B6E40
0 FFFFFFFF8026DEF4 FFFFFFFF8026DEF4.

line 483 is where i'm trying to move a value to linkage section variable.Actually this Cobol program is called by a java program.It is working fine if it called by another cobol program.But this error occurs when ever i'm trying to call it from a Java program.Kindly help me.

[Wim Van den Wyngaert]

Posting the java code and variable declaration might be a good idea.

Wim

[Volker Halle · Accepted solution]

Your program tries to write to virtual address 7FFCFB82 in P1 space, which user-mode code is not allowed to write to.

Consider setting $ SET PROC/DUMP before you run your program, this should cause an image dump to be written (imagename.DMP), if this problem occurs. You can then look at the image dump ($ ANAL/PROC) to find out the failing instruction, the instruction stream and the relevant source code.

Volker.

[minnu]

thanks for ur prompt replies.
I have used dmp to know the error and it showed this.

%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=000000007FFC
FB82, PC=0000000000041A24, PS=0000001B
break on unhandled exception at CUSTUPLD\%LINE 483+24
%DEBUG-W-UNAOPNSRC, unable to open source file VOL090:[IFS_SKUMAR.FMSSRCE]CUSTUP
LD.COB;2
-RMS-F-DEV, error in device name or inappropriate device type for operation
483: Source line not available
DBG> exit

here is the error i got when i used SOAP and WSIT for java programming

ERROR:CustomerUploadSoapBindingImp1:Failed in Customer Upload Module in JAVA program: com.hp.wsi.WsiServerException: %CMA-F-EXIT_THREAD, current thread current thread has been requested to exit.

[Wim Van den Wyngaert]

Again, please post the Java stuff. Access violations in cobol most often mean a mismatch in declaration.

Wim

[Wim Van den Wyngaert]

And read this too
http://h71000.www7.hp.com/wizard/wiz_7543.html

Wim

[Volker Halle]

You need to use the DBG> SET SOURCE directory command to point to the correct source file directory - assuming you have the source files available on the system, where the image dump is being analyzed. Note that the logical VOL090: does not seem to be defined in the proces, from which you analyzed the process dump.

Consider to also look at the failing instruction with:

DBG> EXA/INS @PC

Look at the instruction stream with:

DBG> EXA/INS @PC-24:@PC

Creating a COBOL listing file including /MACHINE (machine code listing) may also help iunderstand, which access fails.

Volker.

[Hein van den Heuvel]

>> line 483 is where i'm trying to move a value to linkage section variable.

Is that the line "MOVE "Y" TO LK_CUST_FLAG."
In 1000-PROGRAM-INITIALIZATION?

So that is the first time any linkage field is use, write or read. Correct?

Since callign from Cobol works, we must for now assume that the attached cobol is not really intersting, at least approximately right. The trouble is likely in how java passes the parameter.

Cobol expects a single pointer to a 5*150+1 byte variable. Is that what is being passed?

When you run under debug control, can you 'see' the argument?

Hein.


I Could not help but notice some intersting (lack of) error handling in the attached cobol:

1)
"MOVE CUSTPROF-FILE-STATUS TO CUSTPROF-FILE-STATUS."

Just in case?!

2)
>> IF HITSLOG-FILE-STATUS = "92"
GO TO 1110-OPEN-HITS-IO

Testing for a locked record with hard loop?
Just as well that OPEN can not possibly return status 92.


3) main logic in a 'close section'
PERFORM 1111-WRITE-HITS-IO THRU 1111-EXIT ?


4) files opened and closed on every activation?

[minnu]

thanks
sorry that i cudn't reply soon.

i got the error at this line
MOVE "Y" TO LK_CUST_FLAG.

yeah files are opened and closed at every activation.

i got this error even when i'm running it as a stand alone cobol program with out java.i cannot proceed further. :(

[minnu]

I thank all of u for your valuable suggestions.I will come back to this forum if i have any trouble further.