This example illustrates output in S variables as a function of the privileges of the caller. It does not represent a situation lifted from actual practice; it is rather an artificial, simplified example designed specially to show the principles involved.
The following privileges exist:
Case
Case
or OPERATINGCase
The following configuration exists:
the global nonprivileged subsystem AA V04.6 has the status CREATED; one task is connected (TID=00010054, TSN=0123)
the global, privileged subsystem XX V01.0 has the status CREATED: one task is connected (TID=0002006F, TSN=0BFC)
the global, privileged subsystem XX V02.0 has the status IN-DELETE: two tasks are connected (TID=00070015, TSN=0CMM and TID=00010057, TSN=00AP)
A compound variable of the type “list” with the name DATA is declared and assigned to the S variable stream SYSINF.
|
Case 1: The caller has only the privilege STD-PROCESSING
|
(1) | The names, versions and statuses of all global, nonprivileged subsystems and of all local subsystems are output to SYSOUT. In our specially constructed example, only the global subsystem AA is nonprivileged. It is output - together with the local subsystem AA. |
(2) | Output in the S variable DATA explicitly contains the subsystem type “global” or “local”. |
(3) | The restriction concerning output to subsystem AA does not result in any changes in the output to SYSOUT, in contrast to (1). |
(4) | The restriction concerning output to subsystem AA does not result in any changes in the output to the S variable DATA in contrast to (2). |
Case
2: The caller has the privileges STD-PROCESSING and SUBSYSTEM-MANAGEMENT and/or OPERATING
|
(5) | The names, versions and statuses of all global and local subsystems are output to SYSOUT. In other words, information is provided on all subsystems loaded in the current system. In our specially constructed example, this refers to the global subsystems XX (privileged, two versions) and AA (nonprivileged) and to the local subsystem AA. |
(6) | Output in the S variable DATA explicitly contains the subsystem type “global” or “local”. |
(7) | The restriction affecting the output to subsystem AA does not result in any changes as compared with (1): any tasks connected to a subsystem are shown together with their TSN and TID. The total number of tasks connected to this subsystem since startup is likewise output to SYSOUT. |
(8) | Output from the subsystems AA in the S variable DATA contains the same information as in the output to SYSOUT, as well as additional information concerning the subsystem type “global” or “local”. |
Case
3: The caller does not have the privilege STD-PROCESSING but does have one of the privileges SUBSYSTEM-MANAGEMENT or OPERATING
|
|
(9) | The names, versions and statuses of all global subsystems are output to SYSOUT. In our specially constructed example, this refers to the global subsystems XX (privileged, two versions) and AA (nonprivileged). |
(10) | Output in the S variable DATA contains the same information as in output to SYSOUT. |
(11) | The restriction concerning output to the subsystem XX produces the following changes as compared with (9): any tasks connected to a subsystem are displayed with their TSN and TID. The total number of tasks connected to this subsystem since startup is likewise output to SYSOUT. |
(12) | Output from the subsystems XX in the S variable DATA contains the same information as in output to SYSOUT, with the addition of information concerning the subsystem type “global”. |