Start linkage AUDIT mode
Component: | BS2000 |
Functional area: | AUDIT mode control |
Domain: | PROGRAM |
Privileges: | STD-PROCESSING |
Function
This command controls the subroutine trace (linkage AUDIT mode) for processor state TU (task unprivileged), TPR (task privileged) or TPR and SIH. The branch destination addresses are recorded in the linkage AUDIT table on execution of the BASR, BALR, BASSM and BAKR instructions.
If the linkage AUDIT mode is in the “HOLD” state (after the corresponding command), it is activated again by means of START-LINKAGE-AUDIT. If any save table is present, it continues to be used.
Availability of AUDIT function
Systems support can make the AUDIT function globally available using the parameter service (AUDALLOW=YES) and it can control whether a user is authorized to start the linkage AUDIT mode or not via the user entry.
Each user can prohibit or allow the hardware AUDIT mode within his or her task by means of the MODIFY-TEST-OPTIONS command (effective only if the authorization in the user entry allows it).
Privileged functions
Systems support (TSOS privilege) can also control the subroutine trace for the TPR or TPR/SIH processor state.
If the processor-local linkage AUDIT is also to be used during the startup phase, it must be activated with the aid of the parameter service (see the “Introduction to System Administration” [14]). This function is also unrestrictedly available for multiprocessors, i.e. on all CPUs.
The only way to view the processor-local linkage AUDIT table is to use a dump and the DAMP interactive dump analyzer. Interactive output with SHOW-LINKAGE-AUDIT is not possible.
Format
START-LINKAGE-AUDIT | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Operands
STATE =
Processor state for which the linkage AUDIT is to be activated.
STATE = *USER(...)
The linkage AUDIT is to be activated for the nonprivileged processor state TU.
SCOPE = *OWN-JOB / *PROGRAM-LEVEL / *TID(...) / *TSN(...)
Scope of the linkage AUDIT function.
SCOPE = *OWN-JOB
The request applies to the user’s own task.
SCOPE = *PROGRAM-LEVEL
The request applies to the PCB-specific function relating to the highest interrupted
PCB. If a task-wide linkage AUDIT is activated (SCOPE=*OWN-JOB), a PCB-specific request is refused. If a PCB-specific linkage AUDIT at a lower PCB is activated, the new request is accepted in addition.
SCOPE = *TID(...)
Only a task that is identified by means of an internal task number (TID) is to be monitored by linkage AUDIT. Nonprivileged users can only specify tasks running under their own user ID.
TID = <alphanum-name 1..8>
Task identifier that is assigned to the task which is to be monitored.
SCOPE = *TSN(...)
Only a task that is identified by means of its task sequence number (TSN) is to be monitored by linkage AUDIT. Nonprivileged users can only specify tasks running under their own user ID.
TSN = <alphanum-name 1..4> / <c-string 1..4>
TSN that is assigned to the job which is to be monitored.
BUFFER-SIZE = 0 / <integer 0..16 4Kbyte>
Number of pages in 4KB units additionally required for the linkage AUDIT to protect it against cyclic overwriting.
STATE = *SYSTEM(...)
Only privileged users are allowed to select this operand value.
The linkage AUDIT is to be started for the privileged processor state TPR.
SCOPE = *OWN-JOB / *PROGRAM-LEVEL / *ALL-JOBS / *TID(...) / *TSN(...)
Scope of applicability of the linkage AUDIT function.
SCOPE = *OWN-JOB
The request applies to the user’s own (TSOS) task.
SCOPE = *PROGRAM-LEVEL
The request applies to the PCB-specific function which is associated with the highest interrupted PCB. If a task-wide linkage AUDIT has been activated (SCOPE=*OWN-JOB), a PCB-specific request will be rejected. If a PCB-specific linkage AUDIT has been activated for a lower PCB, the new request will be accepted as an addition.
SCOPE = *ALL-JOBS
All the jobs currently on the system are to be monitored by the linkage AUDIT.
SCOPE = *TID(...)
The linkage AUDIT is to monitor a single task, identified by its internal task identifier (TID).
TID = <alphanum-name 1..8>
Task identifier of the task.
SCOPE = *TSN(...)
The linkage AUDIT is to monitor a single task, identified by its task sequence number (TSN).
TSN = <alphanum-name 1..4> / <c-string 1..4>
TSN of the task.
STATE = *PROCESSOR(...)
Only privileged users are allowed to select this operand value.
The linkage AUDIT is to be activated for the local processor only, for the privileged states SIH and TPR.
SCOPE = *INTERRUPT-HANDLING / *SYSTEM-LEVEL
Scope of applicability of the linkage AUDIT function.
SCOPE = *INTERRUPT-HANDLING
The request applies to the processor state SIH only.
SCOPE = *SYSTEM-LEVEL
The request applies to both privileged processor states, SIH and TPR.
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
0 | CMD0001 | Command executed without error | |
1 | 0 | CMD0001 | Linkage AUDIT already running, local linkage AUDIT already running, |
1 | CMD2201 | PCB not present. Command rejected | |
64 | CMD0216 | User does not have required authorization | |
64 | IDA0033 | Linkage AUDIT running with SCOPE=*OWN-JOB; SCOPE=*PROGRAM-LEVEL rejected | |
64 | IDA0038 | Specified task does not exist | |
64 | IDA0041 | Linkage AUDIT not available on this system (HSI) | |
64 | IDA0043 | Linkage AUDIT is running in processor-local mode; STATE=*SYSTEM rejected | |
64 | IDA0044 | Linkage AUDIT running with STATE=*SYSTEM; STATE=*PROCESSOR rejected | |
64 | IDA0052 | Linkage AUDIT not available because the user entry does not contain an authorization | |
64 | IDA0053 | Linkage AUDIT not available because the current test option settings for the active task | |
64 | IDA0060 | AUDIT functions globally not available in this session | |
130 | IDA0045 | Central AUDIT management currently locked |