During the installation of a subsystem, the references to its satellites are created.
The module library is a mandatory satellite, as no subsystem can be loaded without it.
If an information file or a syntax file is specified in the definition, they will also be given the status of mandatory components, which will prevent the subsystem from being loaded if they are missing.
If a REP file is specified in the definition, this will only be mandatory at load time if this has been explicitly stated in the definition (REP-FILE-MANDATORY=*YES).
A message file can be specified in the definition, but this is not a mandatory component. In other words, loading of the subsystem can be carried out even if the message file is missing.
In following situations, DSSM sends a query to the operator terminal that must be answered by the operator:
the module library of a mandatory subsystem is missing (*AT-DSSM-LOAD or *MANDATORY-AT-STARTUP attribute)
the specified information is declared but not present
the REP file with the REP-FILE-MANDATORY=*YES attribute is missing
Despite a missing file, the operator still has the option of continuing the startup process (e.g. starting the subsystem without the information file). The operator is exclusively responsible for a possible abnormal subsystem or system termination.