User`s guide

SHOW
compiles, and can print the reports at the terminal, line printer, or store the
reports in a file you specify. If you type the SET dd: NOSUCCESS command
before you use the Error Logger, the Error Logger compiles statistics on only
the errors that occurred, not the successful I/O transfers. Therefore, the reports
generated when you type SHOW ERRORS will list only the errors that occurred.
For complete descriptions of the reports ERROUT creates, see the Error Logging
chapter in the RT–11 System Utilities Manual.
ERRORS Displays a full report on each I/O transfer that has
occurred in addition to each I/O, memory parity, and
cache memory error that has occurred.
ERRORS/ALL Same as SHOW ERRORS.
ERRORS/FILE:filespec Displays a full I/O transfer and error report from
the file you specify. The file you specify must be of
the same format that the Error Logger uses for its
statistical compilations.
ERRORS/FROM:date Displays a full I/O transfer and error report for errors
that occurred starting from the date you specify.
Enter the date as dd:mmm:yy, where:
dd specifies a two-digit day.
mmm specifies the first three characters of a
month’s name.
yy specifies the last two digits of a year.
ERRORS/TO:date Displays a full I/O transfer and error report for errors
that occurred up to the date you specify.
ERRORS/OUTPUT:filespec Enters the I/O transfer and error report in the output
file you specify. This is useful if you want to save the
error-logging reports.
ERRORS/PRINTER Displays the I/O transfer and error report at the line
printer.
ERRORS/SUMMARY Displays a summary error report at the terminal.
The summary error report lists only the errors that
occurred, not the successful I/O transfers.
ERRORS/TERMINAL Displays the I/O transfer and error report at the
terminal. /TERMINAL is the default setting.
JOBS
Displays data about the jobs that are currently loaded. This option also tells the
following:
• Job name and number (if you have not enabled system-job support on your
monitor, the foreground job name appears as FORE, and its priority is 1)
• Console the job owns (with a nonmultiterminal monitor, this space is blank)
• Priority level of the job
• Job’s running state (running, suspended, or done but not unloaded)
• Low and high memory limits of the job
RT–11 Command Descriptions 305