Overview of test privileges

The test privileges control the executability of software and hardware diagnostic activities in BS2000. The main user is the debugger AID.

The test privileges are split into read and write privileges. A user’s write privilege may not be greater than his/her read privilege. Read and write privileges are defined hierarchically from 1 (low) to 9 (high):

A privilege with the value n implicitly covers the access permissions on the lower privilege levels 1 to n-1.

Systems support defines the maximum test privileges for a user ID using the ADD-USER or MODIFY-USER ATTRIBUTES command. System-wide maximum values for the read and write privileges can be defined using the system parameters RDTESTPR and WRTESTPR. These are set for a specific task using the MODIFY-TEST-OPTIONS command.

Test privileges with AID

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. 

Read test privileges for AID read accesses

Value	Characteristics
1	Access to the pages in the user’s own user address space1 and in the system addressspace2 which are readable with the access rights of the normal user and are not secret pages3 Access to the user PCBs of the user’s own task
2	Additional access to the TCB of the user’s own task
3	Additional access to the secret pages in the user’s own user address space which are readable with the access rights of the normal user
4	Not assigned
5	Not assigned
6	Additional access to the pages in the user’s own user address space which are only readable with the access rights of the operating system and are not secret pages Additional access to the system PCBs of the user’s own task and to the XVT
7	Not assigned
8	Additional access to all pages in the system address space, all secret pages and all pages of other tasks Additional access to the user PCBs, system PCBs and TCBs of other tasks
9	Not assigned

Table 10: Read test privileges for AID read accesses

1	Program space and data spaces of the user
2	System space and data spaces of the system
3	Pages protected against diagnostic accesses

Write test privileges for AID write accesses

Value	Characteristics
1	Access to the pages in the user’s own user address space1 which can be written using the access rights of the normal user and are not secret pages2 Additional access to the user’s local task pages in the user’s own program space which are “only readable”3 with the access rights of the normal user and are not secret pages or “trusted UTM”4 pages Access to the user PCBs of the user’s own ask
2	Not assigned
3	Additional access to the secret pages in the user’s own user address space which can be written using the access rights of the normal user Additional access to the user’s local task secret pages in the user’s own program space which are “only readable” with the access rights of the normal user and are not “trusted UTM” pages
4	Not assigned
5	Not assigned
6	Additional access to the pages in the user’s own user address space which can be written using the access rights of the operating system and are not secret pages
7	Not assigned
8	Additional access to all pages in the system address space5, all secret pages and all pages of other tasks Additional access to the XVT and to the user PCBs, system PCBs and TCBs of all tasks
9	Not assigned

Table 11: Write test privileges for AID write accesses

1	Program space and data spaces of the user
2	Pages protected against diagnostic accesses
3	The page attribute “only readable” is ignored by AID in this case
4	Pages of user jobs which run with the system privilege SECURE-OLTP
5	System space and data spaces of the system

Note on OWN-UID-DEBUGGING

The “static AID test with low test privilege” can be permitted for other tasks 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.

Test privileges for the other software diagnostic products

Read test privileges

Value	Product	Characteristics
3	CDUMP	System dump may be taken under a normal user ID
8	ANITA	Active system may be diagnosed with DAMP and other user programs which use ANITA