The SAT parameter file contains all information needed to permit SAT to start with specific settings in the next session. The settings can be made by the user IDs with the privilege SAT-FILE-MANAGEMENT and by the security administrator.
SAT parameters are not automatically stored in the SAT parameter file; this must be done explicitly with the SAVE-SAT-PARAMETERS command (see SAVE-SAT-PARAMETERS command). When the parameters are stored, it is possible to specify which values (*STANDARD or *CURRENT) are to be transferred to the parameter file.
Depending on the privilege possessed by the caller, the following parameters are saved in the SAT parameter file:
EVENT-PRESELECTION (with the privilege SECURITY-ADMINISTRATION)
ALARM-CONDITIONS (with the privilege SECURITY-ADMINISTRATION)
FILTER-CONDITIONS (with the privilege SECURITY-ADMINISTRATION)
SAT-FILE-ATTRIBUTES (with the privilege SAT-FILE-MANAGEMENT)
SAT-SUPPORT (with the privilege SECURITY-ADMINISTRATION)
The SAT parameter file $SYSAUDIT.SYSPAR.SAT is created on the HOME pubset as an ISAM file with the attributes:
ACCESS=READ, BLKSIZE=(STD,2), DESTROY=YES and AUDIT=ALL.
The SAT parameter file is opened when the SATCP subsystem is initialized (at STARTUP), and the parameters stored in this file are read. If no SAT parameter file exists at this time, one is created and SAT starts with the default values.
The SAT parameter file remains open as long as the SATCP subsystem is active. All accesses to the SAT parameter file are executed under the control of a system task (SATP task). This is done to prevent unauthorized access to the SAT parameter file.
If an error occurs while opening the SAT parameter file, SAT proceeds as follows. If the error occurred in DMS or in the SATP task environment (SAT subsystem), SAT attempts to recover the SAT parameter file and then tries to open it again. If this cannot be done, the current file is closed (if possible) and the SATP task environment is released. This is indicated by a message on the console. The SAT file manager can then access the SAT parameter file in order to determine the cause of the error and take appropriate steps.
An error in the SAT parameter file does not affect SAT logging or the SAT alarm function. In such an event, however, the default settings are used instead of the values stored in the parameter file.
The error could be eliminated by the following measures:
The SAT file administrator catalogs the errored SAT parameter file under a new name in order to make it available for diagnostic purposes. Should this not be possible, the administrator deletes the file.
The SAT file administrator then restarts the system. If no SAT parameter file is found to exist at this time, SATCP creates this using default values.
Finally, the SAT file administrator sets new current SAT parameter values and saves them by using the /SAVE-SAT-PARAMETERS command and specifying *CURRENT for the desired operands.
Initial installation of SAT
When the system is first started up after initial installation of SAT, there is as yet no SAT parameter file. In this case the SATCP subsystem starts up with the default values and automatically creates a SAT parameter file with those values. In all subsequent sessions SATCP starts up with the values that have been stored in the SAT parameter file.
Changing to a new version
The SAT parameter file contains the SAT parameters for the next session. If a newer version is installed before the next session is started, this newer version recognizes the old format and adapts the old file as follows:
Old parameters are copied and remain unchanged. The copies are changed to match the new version.
Newly added parameters are set to their default values.
Note
If the old SAT parameter file contains types (e.g. *STANDARD, *CURRENT), rather than concrete values, as operand values, then these are transferred without change to the new version. SAT does not check whether these types have different meanings in the new version.
Examples of SAT parameter files
Changing the SAT parameter file
In the current session values for event selection have been changed with the /MODIFY-SAT-PRESELECTION command, and the file attributes of the SATLOG file have been changed by means of the /CHANGE-SAT-FILE command. The alarm and filter conditions as well as the SAT support parameters have not been changed in this session.
The security administrator stores the currently valid values for event selection and the alarm function in the SAT parameter file with the following command:
|
The next session would begin with the following settings:
EVENT-PRESELECTION | Values valid when the SAVE-SAT-PARAMETERS command was input |
ALARM-CONDITIONS | Values as in the last session, because they were not changed during execution of the SAVE-SAT-PARAMETERS command |
FILTER-CONDITIONS | Values as in the last session, because they were not changed during execution of the SAVE-SAT-PARAMETERS command |
SAT-FILE-ATTRIBUTES | Values as in the last session, because the values set with /CHANGE-SAT-FILE were not stored |
SAT-SUPPORT | Values as in the last session, because they were not changed during execution of the SAVE-SAT-PARAMETERS command |
The SAT file manager would also like to transfer the changes made to the attributes of the logging file to the SAT parameter file. This is done with the following command:
/save-sat-parameters sat-file-attributes=*current
The next session therefore begins with the following settings:
EVENT-PRESELECTION | as above |
ALARM-CONDITIONS | as above |
FILTER-CONDITIONS | as above |
SAT-SUPPORT | as above |
SAT-FILE-ATTRIBUTES | Values valid when the SAVE-SAT-PARAMETERS command was input |