Hello,

Under what operation system are you running?
What type of executable are you running: linked executable, .int, .gnt, separate executable and .dll (or .so)?

I tested this here under Windows using our latest product release V10.0 and when physical cancel is set and the called program is dynamically loaded (.dll, .so, int, or gnt)  the memory will no longer be accessible, after a cancel, because the program is removed from memory. If the two programs are linked together into the same executable file, the addresses of data items in the canceled program will still be accessible, but in this case it doesnt actually do a physical cancel.

However, I would not depend on this behavior, always working like this.

A physical cancel of a program containing a data item defined as EXTERNAL in both the called and callee, these data items will still be available in the calling program.

I have not tested with 3.0 yet until I know under which OS you are running?

Hi Chris , we are running on a POWER server under AIX 7.2  (UNIX).

we run  executables.gnt and data are not external defined, 

It seems to me like under V3.0, even though the tunable was set for physical cancels that perhaps a logical cancel was actually being done.

Are you certain this was actually doing a physical cancel? Could you see that memory was released after the CANCEL was issued?