zSecure Alert operator commands
- CRSH
This command causes an immediate abend of the C2POLICE started task, without any recovery. It is intended for IBM® internal testing only.
- STOP
- Stop execution of the zSecure Alert started
task. This results in an orderly shutdown of the task. Some memory
remains reserved after termination of the task to enable reuse of
some critical system resources during a subsequent restart of the
started task. The effect of the STOP MODIFY command
is identical to that of the MVS STOP command.
The STOP command does not support any additional keywords.
- RESTART
- This command results in an orderly shutdown of zSecure Alert processing,
followed by an immediate reinitialization. The address space in which
the started task is running is not terminated. No additional console
operator command is needed to reactivate zSecure Alert processing.
The main difference between a restart and a STOP command
followed by a START command for the started task is the preservation
of the ASID. Also, possible changes in the started task procedure
cannot be effected during RESTART processing. During the time required
to process the RESTART command, alert situations are not
recognized, and no reports are generated.
Because the STOP/START sequence results in marking the address space as non-reusable, the RESTART command is preferred in most situations. This command prevents loss of potentially critical system resources.
The RESTART command does not support any additional keywords.
- REFRESH
- This command results in the reprocessing of
the command and parameters specified in the PARMLIB and a refresh
of some subtasks. Not all PARMLIB commands can be processed. The OPTION
command is not supported during a REFRESH. The preprocessing subtask
is started and the reporting task is ended and restarted. Because
the alert generating reporting task can only be restarted after completion
of the preprocessing task, it might take several minutes for the refresh
process to complete. During this period, alerts are still generated
according to the existing configuration.
During the time that the zSecure collect process is running, the REFRESH command is accepted, but most processing is delayed. When the collect process has finished, subtask start and restart processing as described is performed.
The REFRESH command does not support any additional keywords.
- COLLECT
- This command results in an immediate, synchronized execution of
the zSecure Collect started
task. Processing is identical to that resulting from the normal scheduled
start of the zSecure Collect task.
The name of the started task is controlled by the CollectSTCName parameter.
The regular scheduled start of the STC is not affected and remains
at the time specified by CollectTime.
While the zSecure Collect process is running, the reporting task remains active. Alerts continue to be issued as usual. The preprocessing task might be delayed until the collect task has completed.
The COLLECT command does not support any additional keywords.
- SIPL
- This command is to be used only in emergency situations. It results
in freeing all in-memory data structures, loss of a system level LX,
that is, linkage index, and marking the address space as non-reusable.
System level LX's are a limited resource, and cannot be
recovered without an IPL of the system. When upgrading from one release
of zSecure Alert to
another, the installation instructions require that you shut down
the previous version using this SIPL command.
The SIPL command does not support any additional keywords.
- DISPLAY
- This command results in a display of the status and options of zSecure Alert processing.
It shows the current options, the buffer space used, the buffer number
in use at the time, and the status of several error indicators if
set.
The DISPLAY command does not support any additional keywords.
- REPORT
- This command enables you to set the values for the keywords that control processing of the captured data. The new values are used the next time that the program refers to them. Values specified through an operator MODIFY command are overwritten by values from PARMLIB during the next REFRESH, which might be started by the console operator, or automatically at the end of each Stage1Interval.
- FILTER
- This command enables you to set the filtering criteria for the
SMF-records and the WTO-messages before they are captured in the in-memory
buffers. Efficient use of these filter criteria can significantly
reduce the amount of buffer space needed. The new filter criteria
are effective immediately. For a complete description of all keywords,
see FILTER command.
Note: Values specified through an operator MODIFY command are overwritten by values from PARMLIB during the next REFRESH, which might be started by the console operator, or automatically at the end of each Stage1Interval.
- DEBUG
- This command controls the diagnostic and monitoring messages that can be generated by the program. All messages are described in IBM Security zSecure: Messages Guide. The command is effective immediately. For a complete description of all keywords, see DEBUG command.
- DIAGNOSE
- This command is used to display detailed information or perform diagnostic tasks. It allows dumping some internal control blocks and tables for problem determination. The control blocks displayed are intended for IBM support personnel to diagnose certain problems. For a complete description of all keywords, see DIAGNOSE command.