Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Diagnostic documentation for a BS2000 system

The following files are required from the BS2000 system for diagnosis:

  • detailed description of the error situation; the sequence of operations is required for a reproducible error

  • CONSLOG: console log

  • the SYSOUT file created (under any name) in the start file by ROBAR

  • SYSPAR.ROBAR-CL. <ver>.MESSAGES
    file for the messages relevant to ROBAR

  • $<userid>.ROBAR.TRACE.<partner>.<date>
    the trace files created by ROBAR-CL-DCAM with date and time

  • user dump, if any.

If you use the HSMS/ARCHIVE program to store these files on tape, also provide the backup listing.

Note

The start procedure for ROBAR-CL-DCAM generates different file names for the SYSOUT output of ENTER jobs:

  • When SDF-P is installed, the SYSOUT file SYSRPT.ROBAR-CL.<ver>.<DCAM-name>.<tsn> is generated for each new TSN. These files must be deleted regularly to avoid saturating the disk space.

  • When SDF-P is not installed, the SYSOUT file SYSRPT.ROBAR-CL.<ver>.<DCAM-name>.SYSOUT is generated. A new file with this name is generated each time ROBAR-CL is started.