I issue TPROT 0(R06),0

The value in R06 is X'00006F50'.
I am running in primary, key 0, AMODE 31, DAT on.

The page at X'00006F50' is viewable in an SVC dump.

But I get a condition code of 3.

What is going on?

BTW, The address is in a CICS region.

TIA. Pierre.

:>I issue TPROT 0(R06),0

:>The value in R06 is X'00006F50'.
:>I am running in primary, key 0, AMODE 31, DAT on.

:>The page at X'00006F50' is viewable in an SVC dump.

:>But I get a condition code of 3.

The fact that it is in an SVCDUMP does not mean that it was paged in at the
time the TPROT was issued.

If you wish to simply get the key, use IVSK. Of course, IVSK will PIC-10/11 if
the page is not assigned.

If you wish to verify that a specific virtual address is assigned, use VSMLOC.

--

http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel

It means that at the instant of TPROT, the
address was not translatable by the hardware.
Use a key 0 access, like "CLI 0(R6),0" or an
IVSK instruction to force a page-in, then
immediately the TPROT.

==================
        SPKA  0           disable key protection
LOOP    BR    0           purge cache
        CLI   0(R6),0     force a page-in
        TPROT 0(R6),0     test
        BO    LOOP        oops, paged-out
==================

Under a heavy system load, the CLI may page-in,
then an interrupt occurs and eventually the page
goes out again before the TPROT is executed. So,
use a loop. If for some reason you don't want to
set key zero, then you can also use IVSK to force
a page-in.

If the page is logically invalid (bad address),
then the CLI will barf as usual and your ESTAEX
can handle that situation.

You are right. If the memory is paged out, that's what happens. Thanks.