Modify task-specific settings for testing and diagnostics
Component: | AIDSYSA |
Functional area: | Program control |
Domain: | PROGRAM |
Privileges: | all privileges bar OPERATING |
Function
The MODIFY-TEST-OPTIONS command allows the user to modify the task-specific test and diagnostic options:
The test and diagnostic privilege values can be modified for the user’s own tasks (PRIVILEGE operand). The maximum possible test privilege values for AID are defined in the user entry and cannot be exceeded.
Users can control the options for requests for user and area dumps for their own tasks and tasks under their own user IDs (USERDUMP-OPTIONS operands). Users can specify whether a dump is to be generated in response to an event that is capable of generating a dump. They can specify the pubset on which the created dumps are to be stored, whether duplicates of dumps are to be suppressed and the maximum number of dumps that are to be created. They can also specify whether a dump is to contain DIV windows and data spaces and swapped in areas of POSIX memory mapping.
Users can permit or prohibit the use of the hardware or linkage audits for their own tasks (AUDIT operand).
The static AID test with a lower test privilege can be permitted or prohibited for other tasks running under the user’s own user ID (OWN-UID-DEBUGGING operand). If testing with reduced privileges is permitted then, in the case of read access to another task, the same test privileges as for the user’s own task are sufficient. In the case of write access, a write privilege >= 2 is required.
Privileged functions
Privileged users (TSOS privilege) can control the dump request options for any task (TSN operand).
Format
MODIFY-TEST-OPTIONS | Alias: MDTSO | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Operands
PRIVILEGE = *UNCHANGED / *PARAMETERS(...)
Test privilege values for testing and diagnostics.
This operand is primarily required for testing using AID.
Values specified here must not exceed the maximum values specified in the user entry. In addition, in the user entry, systems support may specify whether consent of the operator is necessary to increase the values.
See SHOW-USER-ATTRIBUTES command, output fields READ-PRIVILEGE, WRITE-PRIVILEGE and MODIFICATION, grouped under TEST-OPTIONS.
PRIVILEGE = *UNCHANGED
The current specification applies, i.e. the values last set in MODIFY-TEST-OPTIONS, otherwise, the standard system values apply.
PRIVILEGE = *PARAMETERS(...)
READ = <integer 1..9>
Value for read privilege. Default value: 1
WRITE = <integer 1..9>
Value for write privilege. Default value: 1
USERDUMP-OPTIONS = *UNCHANGED / *PARAMETERS(...)
Controls the output of user and area dumps for the user’s own tasks and tasks under the user’s own user ID.
USERDUMP-OPTIONS = *PARAMETERS(...)
TSN = *OWN / <alphanum-name 1..4> / <c-string 1..4>
Specifies the task for which the output of user dumps is to be modified.
TSN = *OWN
The modifications apply to the user’s own task.
TSN = <alphanum-name 1..4> / <c-string 1..4>
TSN of the task to which the modifications are to apply. Nonprivileged callers may only specify tasks running under their own user IDs.
DUMP = *UNCHANGED / *STD / *YES / *NO / *SYSTEM
Specifies whether a user or area dump is actually to be created in the event of a dump request.
DUMP = *UNCHANGED
The current setting applies, i.e. the most recent setting for the specified task made using MODIFY-TEST-OPTIONS. In case no specification was made, the default system setting will be effective (corresponds to the operand value *STD).
DUMP = *STD
The standard control is in effect:
In interactive mode, the system asks: DUMP DESIRED? REPLY (Y=YES, N=NO)If the user answers “N”, the memory dump is suppressed. If the answer is “Y”, the system outputs the memory dump and issues the message
DUMP IN PROGRESS, PLEASE WAIT
In batch mode and in procedures, the memory dump is suppressed and the following message is issued: SYSTEM REGULATIONS PROHIBIT DUMP
DUMP = *YES
Every memory dump is output.
DUMP = *NO
No memory dump is to be output if cause for one occurs during the current job.
DUMP = *SYSTEM
A system dump is generated instead of a user or area dump. However, this conversion to a system dump is performed only if one of the following conditions relating to test privileges is fulfilled:
The task making the DUMP=*SYSTEM setting possesses a read privilege >= 3.
The task in which the dump occurs possesses a read privilege >= 3.
A converted dump is handled in the same way as a genuine system dump, i.e. the control mechanisms that apply to system dumps also apply to such dumps (instead of those applying to user and area dumps).
DUMP-CONTENTS = *UNCHANGED / *PARAMETERS(...)
Determines the content of user dumps for the specified task. These settings do not apply to area dumps.
DUMP-CONTENTS = *PARAMETERS(...)
DATA-IN-VIRTUAL = *STD / *NO / *YES
Specifies whether user dumps also contain DIV windows. The default value is *STD, i.e. DIV windows are included in user dumps if no entry was made in the CDUMP macro.
DATA-SPACES = *STD / *NO / *YES
Specifies whether user dumps also contain data spaces. The default value is *STD, i.e. data spaces are included in user dumps if no entry was made in the CDUMP macro.
MEMORY-MAP = *STD / *NO / *YES
Specifies whether user dumps contain swapped in areas of POSIX memory mapping. The default value is *STD, i.e. POSIX mapping pages are issued in the user dumps if no particular specifications are made in the dump request.
OUTPUT-PUBSET = *UNCHANGED / *DEFAULT-PUBSET / <cat-id 1..4>
Defines the pubset on which any user or area dumps resulting from the specified task are to be created. They are stored on the corresponding pubset either under the task’s user ID or, if the task involves protected data, under the SYSUSER user ID.
OUTPUT-PUBSET = *UNCHANGED
The current setting applies, i.e. the most recent setting for the specified task made using MODIFY-TEST-OPTIONS. If no setting was made then the system defaults apply (OUTPUT-PUBSET=*DEFAULT-PUBSET).
OUTPUT-PUBSET = *DEFAULT-PUBSET
User or area dumps are stored on the default pubset declared for the user ID of the specified task in the user catalog. Dumps involving protected data are stored under the SYSUSER user ID on the default pubset.
OUTPUT-PUBSET = <cat-id 1..4>
Catalog ID of the pubset on which user or area dumps are to be stored.
MAXIMUM-NUMBER = *UNCHANGED / *UNLIMITED / <integer 1..255>
Defines the maximum number of user or area dumps that are to be generated for the specified task.
MAXIMUM-NUMBER = *UNCHANGED
The current setting applies, i.e. the most recent setting for the specified task made using MODIFY-TEST-OPTIONS. If no setting was made then the system defaults apply (MAXIMUM-NUMBER=*UNLIMITED).
MAXIMUM-NUMBER = *UNLIMITED
There is no restriction on the maximum number of user or area dumps.
MAXIMUM-NUMBER = <integer 1..255>
Maximum number of user or area dumps.
SUPPRESS-DUPLICATES = *UNCHANGED / *NO / *YES
Specifies whether the output of a user or area dump for the specified task should be suppressed if these represent duplicates of dumps that have already been created. A dump is treated as a duplicate if a dump with the same interrupt weight has already occurred at the same point within the same program.
SUPPRESS-DUPLICATES = *UNCHANGED
The current setting applies, i.e. the most recent setting for the specified task made using MODIFY-TEST-OPTIONS. If no setting was made then the system defaults apply (SUPPRESS-DUPLICATES=*NO).
SUPPRESS-DUPLICATES = *NO
The output of dump duplicates should not be suppressed.
SUPPRESS-DUPLICATES = *YES
The output of dump duplicates should be suppressed.
AUDIT = *UNCHANGED / *PARAMETERS(...)
Specifies whether hardware audits and linkage audits may be controlled using commands within a task.
HARDWARE-AUDIT = *UNCHANGED / *NOT-ALLOWED / *ALLOWED
Specifies whether the hardware audit may be controlled using commands within the task.
HARDWARE-AUDIT = *NOT-ALLOWED
The hardware audit may not be controlled using commands within the task.
HARDWARE-AUDIT = *ALLOWED
The hardware audit may be controlled using commands within the task. Use of the hardware audit has to be allowed for the user ID.
LINKAGE-AUDIT = *UNCHANGED / *NOT-ALLOWED / *ALLOWED
Specifies whether the linkage audit may be controlled using commands within the task.
LINKAGE-AUDIT = *NOT-ALLOWED
The linkage audit may not be controlled using commands within the task.
LINKAGE-AUDIT = *ALLOWED
The linkage audit may be controlled using commands within the task. Use of the hardware audit has to be allowed for the user ID.
OWN-UID-DEBUGGING = *UNCHANGED / *PARAMETERS(...)
Controls the static AID test with lower test privileges for other tasks running under the user’s own user ID.
If testing with reduced privileges is permitted then, in the case of read access to another task, the same test privileges as for the user’s own task are sufficient. In the case of write access, a write privilege >= 2 is required.
If testing with lower privileges is not permitted then test privilege 8 is required for both reading and writing.
OWN-UID-DEBUGGING = *UNCHANGED
The current setting applies, i.e. the most recent setting for the specified task made using MODIFY-TEST-OPTIONS. If no setting was made then the system defaults apply (ACCEPT-ACCESS=*NO and ENABLE-ACCESS=*NO).
OWN-UID-DEBUGGING = *PARAMETERS(...)
ACCEPT-ACCESS = *UNCHANGED / *NO / *YES(...)
Specifies whether the user’s own task permits testing with lower test privileges by other tasks running under the user’s ID.
ACCEPT-ACCESS = *UNCHANGED
The current setting applies, i.e. the most recent setting for the specified task made using MODIFY-TEST-OPTIONS. If no setting was made then the system defaults apply (ACCEPT-ACCESS=*NO).
ACCEPT-ACCESS = *NO
The user’s own task prohibits testing with a lower test privilege by other tasks running under the user’s own ID.
ACCEPT-ACCESS = *YES(...)
The user’s own task prohibits testing with a lower test privilege by other tasks running under the user’s own ID (observer tasks). It therefore declares itself as the test task.
PASSWORD = *NONE / <c-string 1..8>
Specifies whether a password has to be entered in the event of testing by another task (observer task).
PASSWORD = *NONE
No password is declared. Observer tasks do not have to log on explicitly at the test tasks.
PASSWORD = <c-string 1..8>
Password that has to be used by an observer task for testing (see the ENABLE-ACCESS operand). Only the password last specified by the test task can be used for logon.
ENABLE-ACCESS = *UNCHANGED / *NO / *YES(...)
Specifies whether the user’s own task can identify itself to a test task running under the user’s own ID as an observer task for testing with lower privileges.
ENABLE-ACCESS = *UNCHANGED
The current setting applies, i.e. the most recent setting for the specified task made using MODIFY-TEST-OPTIONS. If no setting was made then the system default applies (ACCEPT-ACCESS=*NO). (ENABLE-ACCESS=*NO).
ENABLE-ACCESS = *NO
Observer task identification is revoked. This makes all previously specified passwords invalid.
ENABLE-ACCESS = *YES(...)
The user’s own task identifies itself to a test task running under the user’s own ID as an observer task. Such a task is only permitted to observe a test task if the test task has not declared any password protection (in this case the setting ENABLE-
ACCESS=*YES is obsolete) or if one of the last 8 passwords entered for observation purposes corresponds to the password of the test task.
PASSWORD = <c-string 1..8>
Password used to identify the task to a test task.
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
0 | CMD0001 | Command executed successfully | |
1 | CMD2201 | Error in function call: function invalid | |
3 | CMD2203 | Error in function call: version invalid | |
1 | IDA0300 | Syntax error | |
32 | CMD0221 | System error | |
64 | CMD0216 | Error: command privilege missing | |
64 | IDA0301 | Semantic error |