Diagnostic aids

SHC-OSD is a dynamically reloadable subsystem which is decoupled from BS2000.
The tasks generated by SHC-OSD have the job name SHCUSERT.
The POSIX shared memory segment generated by SHC-OSD cannot be uniquely identified by its ipcs key: it uses the key 0 (PRIVATE).

The following documents are required for diagnostic purposes when problems occur in the SHC-OSD environment:

1. SHC-OSD executive and error traces and tables which can be found in POSIX in the following files, see "Creating diagnostic documentation using MODIFY-SHC-PROCESSING":

   /var/shcosd/log/dumptrac-<yyyymmdd-hhmm>.txt
/var/shcosd/log/dumptabl-<yyyymmdd-hhmm>.txt

2. CONSLOG file

3. Trace listing of the SHC-OSD command

4. Logging files of SHC-OSD from the /var/shcosd/log directory (see "Logging files of SHC-OSD")

5. Logging files of StorMan (see "Diagnostic aids") and possibly logging files of the SMI-S Provider

6. Dump of the SERSLOG file (in particular if problems occur when starting the subsystem):
   Serious errors or errors which cannot be stored in their own error trace will be entered in the SERSLOG file. The same identification, NDE2000 (“Internal error”), is always used here. The areas specified (one or two) are variable and come from the error trace entry.

7. The REP file SYSREP.SHC-OSD.<ver> which is used and the loader status of BS2000 and of the NKVD subsystem

8. If required, system dump

Creating diagnostic documentation using MODIFY-SHC-PROCESSING

The /MODIFY-SHC-PROCESSING SAVE-TRACES=*YES, SAVE-TABLES=*YES command writes SHC-OSD diagnostic data (traces and tables) from the executing system to the two files dumptrac--<yyyymmdd-hhmm>.txt and dumptabl-<yyyymmdd-hhmm>.txt in the POSIX directory /var/shcosd/log.

As these may be very large, they should be saved externally and then deleted in POSIX.

Logging files of SHC-OSD

The logging entries of SHC-OSD are written to a separate logging file. The logging file is created anew each day.
The file name is: /var/shcosd/log/shcosd-<yyyymmdd>.log.

Logging of SHC-OSD is performed in a separate task (fork) of the SHC-OSD user task (SHCUSERT). The user task is not blocked by SHC-OSD logging.

SHC-OSD logging files can grow to a considerable size (up to 1 MB per day). When the associated file system is full, this is reported by POSIX.

Obsolete SHC-OSD logging files are automatically deleted. The number of days before a logging file is deleted can be set in the SHC-OSD parameter file, see section "Configuration of SHC-OSD".

StorMan logging files

To diagnose errors, it is necessary to save the StorMan logging files and the repository, see the "StorMan" manual [15].