Starting SHC-OSD

After the external components and SHC-OSD have been installed, the SHC-OSD subsystem can be started:
/START-SUBSYSTEM SUBSYSTEM-NAME=SHC-OSD,VERSION=<ver>

Only default values are allowed for the other operands of this command.

Due to POSIX dependency, SHC-OSD is not started automatically after SYSTEM READY, but must be started by the system administrator or in CMDFILE.

The following prerequisites must be met to start SHC-OSD successfully:

• All necessary files are installed.

• The version of SHC-OSD matches the BS2000 version and the StorMan version (ETERNUS DX/AF).

• POSIX and POSIX-SOCKETS are available, and POSIX has been started.

• Package POSIX-BC and POSIX-SH must be installed.

• PTHREADS is installed.

• For ETERNUS DX/AF:
  StorMan has been installed, configured, and started, and defined in the SHC-OSD parameter file. SHC-OSD or the StorMan client and the StorMan server can communicate via LAN. The SMI-S Provider in the storage system has been enabled, configured in StorMan, and can be reached from StorMan via LAN.

  The StorMan server can also be started later. Because of the length of the initialization phase, the storage systems may not be visible immediately. The StorMan server can also be terminated and restarted while SHC-OSD is running.

• The batch job started by SHC-OSD is active and message NDE1201 indicates that SHC-OSD has been initialized successfully.

• The USER-ADDRESS-SPACE-LIMIT (see /SHOW-USER-ATTRIBUTES) set for the TSOS user is checked by SHC-OSD when loaded, and if the setting is too low the start is rejected with the message NDE1200.