POSIX is terminated explicitly by a user with the SUBSYSTEM-MANAGEMENT or OPERATING privilege, or automatically during shutdown of the BS2000 operating system. If a fatal error occurs, POSIX is terminated abnormally.
Explicit POSIX subsystem termination
The POSIX subsystem is terminated by the BS2000 system support or the operating with the following command:
/STOP-SUBSYSTEM SUBSYSTEM-NAME=POSIX
If users are still linked to the POSIX subsystem and FORCEDTERM=0 is set in the POSIX information file when POSIX is terminated, DSSM cancels termination. You can then force termination as follows:
/STOP-SUBSYSTEM SUBSYSTEM-NAME=POSIX, -
/ SUBSYSTEM-PARAMETER=‘FORCED-BY-SUBSYSTEM‘
The entry for the parameter is not case-sensitive but may not be abbreviated.
If FORCEDTERM=1 is set in the POSIX information file, POSIX is always terminated immediately. No second STOP-SUBSYSTEM command is then required.
The POSIX subsystem cannot be halted with the command /HOLD-SUBSYSTEM POSIX. The command is rejected and the current POSIX session is not interrupted.
When the POSIX subsystem is terminated, the following message appears on the screen:
POS3010: SUBSYSTEM POSIX HAS BEEN TERMINATED.
POSIX subsystem termination during shutdown of the BS2000 operating system
DSSM terminates the POSIX subsystem implicitly during shutdown so that the POSIX files are kept consistent.
Abnormal termination of POSIX
If a fatal error occurs, POSIX is terminated abnormally. In this case, BS2000 subsystem administration and POSIX cooperate closely. All programs using POSIX are terminated abnormally and the BS2000 resources used by POSIX are released.
If the initialization process terminates itself during a POSIX session, an abnormal POSIX termination is initiated, since the initialization process has a central control function in POSIX and is therefore essential for error-free operation.