If data is loaded (dynamically) from a read-protected file and if the read password was not specified, an “execute only” situation exists. Testing with AID is not possible in an “execute-only” situation, regardless of the test privileges set.
Value | Characteristics |
1 |
|
2 |
|
3 |
|
4 | Not assigned |
5 | Not assigned |
6 |
|
7 | Not assigned |
8 |
|
9 | Not assigned |
Table 51: Read test privileges for AID read accesses
Value | Characteristics |
1 |
|
2 | Not assigned |
3 |
|
4 | Not assigned |
5 | Not assigned |
6 |
|
7 | Not assigned |
8 |
|
9 | Not assigned |
Table 52: Write test privileges for AID write accesses
Key
1) Program space and data spaces of the user
2) System space and data spaces of the system
3) Pages protected against diagnostic accesses
4) The page attribute “read only” is ignored by AID in this case.
Note on OWN-UID-DEBUGGING
The “static AID test with low test privilege” can be permitted for other taks which run under the user’s own user ID by means of the OWN-UID-DEBUGGING operand in the MODIFY-TEST-OPTIONS command. If this is the case, the same privileges as for accessing your own user address space are sufficient for the read accesses to this task’s user address space.
A write privilege of at least 2 is required for write accesses to this task’s user address space; in addition, the same test privileges apply as for write accesses to the user address space of the user’s own task. In the case of write accesses to these tasks’ memory pool pages, write privilege 8 is always required.