Google
 

Trailing-Edge - PDP-10 Archives - BB-R775E-BM - subsys/spear.spe
There are 26 other files named spear.spe in the archive. Click here to see a list.
         *******  SPEAR help file -- Mar 3, 1981  *******

IMPORTANT - The purpose of a HELP message is to provide understanding
and direction to the user. They must be clear, complete and unambiguous.
In order to avoid page over flow HELP messages should not exceed twenty
(72 character) lines. The top line should be blank (i.e., a <cr>.

!Search Keys
!edits - Edit descriptions
!switch_help - Help messages for /Switches and @@(indirect files)
!spr_help - Main Spear help messages
!kl_help - KLSTAT help messages
!ana_help - Analyze help messages
!ret_help - Retrieve help messages 
!sum_help - Summarize help messages
!com_help - Compute help messages
!ins_help - Instruct help messages

                *******  This is the /HELP message  *******


!switch_help

@@MODE COMPLETION

At any prompt you can type:

 /BREAK to return to the Spear prompt.

 /REVERSE (or press the BACKSPACE key) to repeat the last prompt.

 /SHOW to display the current prompt/responses list.

 /GO to execute the current prompt/response list.

 /CLEAR to clear listed items, at or subordinate to, the current prompt.
  Listed items are: sequence numbers, entry codes, device types, etc.

 /? to display this list without the explanations.

Press the RETURN key to specify the default or terminate a response.
Press the ESCAPE (or Altmode) key to: display the default, or complete
a partially typed response. There is no default at the SPEAR> prompt.
At the SPEAR> prompt, you may type @HELP for information about
Response Streams and Indirect Files.
@@
You can enter a response stream at the main Spear prompt. A response
stream is a single line of consecutive responses, separated by spaces,
and terminated with a carriage return (use the Escape or Altmode key to
insert defaults). Note: The response stream capability is included only
as a convenience for those Spear users who do not wish to be prompted.
@@INDIRECT FILES

Response Streams - A response stream is a single line of consecutive
responses entered at the main Spear prompt. Separate each responses with
a space, and terminate the line with a carriage return. (Use the Escape
or Altmode key to insert defaults).

  Example:   SPEAR> I I R<cr>  or  SPEAR> INSTRUCT ID REFERENCE<CR>

Indirect Response Files - An Indirect Response File is an ASCII text
file that contains a list of Spear Library responses. Note:

1. Almost any editor can be used to build an Indirect Response File.
2. The responses in the file must pertain to one Spear function only.
3. The responses must be in the correct order and terminate with a /GO.
4. If /GO is omitted you will be prompted for all unsupplied responses.
   Thus, you can build a response file that prompts for specific items.
5. An Indirect Response File can be submitted at any prompt. Proceed the
   file name with an @ sign. (e.g., SPEAR> @WEEKLY.CMD<cr>)
@@

!spr_help - Main Spear help messages

@@SPEAR HELP

Spear is a Software Library that supports three standard maintenance
functions: KLSTAT, RETRIEVE, and SUMMARIZE. In addition, some libraries
support three extended functions: ANALYZE, COMPUTE, and INSTRUCT.

KLSTAT - enables additional error information gathering (TOPS-20 only).
RETRIEVE - extracts and translates (or saves) system event file entries.
SUMMARIZE - summarizes the content of system event files.

ANALYZE - attempts to localize the cause of intermittent system failures.
COMPUTE - calculates system availability and crash and uptime statistics.
INSTRUCT - explains how to use the extended Spear Library functions.


At this, the main SPEAR prompt, you can type:

 1. ? to list the supported Spear Library functions.
 2. the name of the Spear Library function that you want to execute.
 3. /HELP for an explanation of the universal Spear Library switches.
 4. @HELP for information about response streams and indirect files.
 5. EXIT to exit Spear and return to the operating system.
@@



@@

!kl_help - KLSTAT help messages

@@KLSTAT

KLSTAT is a switch that applies only to TOPS-20. You must have special
privileges to use it. The switch directs the operating system to capture
additional error status during CPU, Memory, and Massbus errors. At this
prompt you can:


  1. Type ON to enable the gathering of additional error information.

  2. Type OFF to disable the gathering of additional error information.

  3. Press the RETURN key or type CHECK to check the current state of
     the switch.

NOTES: Capturing the additional status is quite time-consuming and will
slow the system down considerably. Therefore, the switch should be used
only when you feel that the additional information is required to solve
a specific problem. The information that's captured by the KLSTAT switch
is described in the Spear Manual. (Refer to the Spear Manual Index)

For further information type: ? or /Help.
@@

!ana_help - Analyze help messages

@@ANALYZE INPUT

     System Event File ___.   .----------.   .___ Report File
                          |   |  Event   |   |
            Retrieve      |---|  File    |---|
         (binary) File ___|   | Analysis |   |___ Packet File
                              |__________|

          INPUT                 PROCESS             OUTPUT

Analyze reads the specified event file, sorts the records according to
a set of (best guess) theories, and then, produces a report file and a
packet file.  The report file summarizes the theories and presents the
major supporting evidence.  The packet file contains a set of pointers
to the individual records that support each theory.

At this prompt Analyze is waiting for you to specify the name of the
input file. You can specify any binary system event file you want,
including a binary file produced by Retrieve.  The file specification
format is: dev:<user>file.extension.version. Press the RETURN key if you
want to default to the local system event file (ERROR.SYS or ERRLOG.SYS)
For further information type: ? or /Help.
@@


@@ANALYZE TIME FROM 
                        Time From:           Time To:
                 ***********|oooooooooooooooooooo|************
                        02-Mar-81            09-Mar-81
                        18:30:45             23:30:01

You can use the "Time From:" and the "Time To:" prompts to specify the
period during which you want the event file analyzed. At this prompt
Analyze is waiting for you to specify the time at which you want the
file analysis to begin. You can:

 1. Press the RETURN key to default to -1 (yesterday at 00:00:01 hours).

 2. Enter real time. The format is: dd-mmm-yy hh:mm:ss  where dd is the
    numerical day, mmm is the first three letters of the month, yy is
    the year, hh is the hour, mm the minute, and ss the second. If only
    the date is specified, the default time is 1 second after midnight.

 3. Enter relative time. The format is: -dd  where -dd is the number of
    past days. To indicate today at 00:00:01 hours, type: -0

For further information type: ? or /Help.
@@


@@ANALYZE TIME TO

                      Time From:           Time To:
               ***********|oooooooooooooooooooo|***********
                      02-Mar-81            09-Mar-81
                      18:30:45             23:30:01

At this prompt Analyze is waiting for you to specify the time at which
you want the file analysis to end. You can:

  1. Press the RETURN key to default to the LATEST time in the file.

  2. Enter real time. The format is: dd-mmm-yy hh:mm:ss where dd is the
     numerical day, mmm is the first three letters of the month, yy is
     the year, hh is the hour, mm the minute, and ss the second. If only
     the date is specified, the default time is 1 second after midnight.

  3. Enter relative time. The format is: -dd  where -dd is the number of
     past days. To indicate today at 00:00:01 hours, type: -0

For further information type: ? or /Help.
@@


@@ANALYZE REPORT

The big picture is still: Input - Process - Output.   Remember, Analyze
is designed to sort and classify the information contained in the local
system event file.  The result is a report file and a packet file.  At
this prompt Analyze is waiting for you to specify a destination for the
report file. You can:

 1. Press the RETURN key to select the default file specification:
    DSK:Ammdd.RPT. Where mmdd corresponds to the current month and day.

 2. Enter your own unique file specification (e.g., DSK:WEEKLY.RPT).
    The file specification format is: dev:<user>file.extension.version.

 3. Type TTY: in which case the report will be printed on your terminal.
    Understand that if you specify TTY: the file will not be saved.

NOTE: If you save the file, you can use any text editor to review the
report. Of course, you can also print or type the report as you wish.

For further information type: ? or /Help.
@@


@@ANALYZE PACKETS

There is a packet associated with each theory listed in the report file.
The packets are numbered and contain pointers to those records that were
used as evidence to support the theories.  After the file is analyzed,
the packets are put in a common packet file along with the name of the
file that was analyzed.  At this prompt Analyze is waiting for you to
specify a destination for the packet file. You can: 

 1. Press the RETURN key to select the default file specification:
    DSK:Ammdd.PAK. Where mmdd corresponds to the current month and day.

 2. Enter your own unique file specification (e.g., DSK:WEEKLY.PAK).
    The file specification format is: dev:<user>file.extension.version.

 3. Type NUL: to indicate that you don't want the packet file saved.


NOTE: If you choose to save the packet file, then you can use Retrieve
to translate the records listed in the packets. This should be done any
time you question a theory or the evidence that supports it.
For further information type: ? or /Help.
@@

!ret_help - Retrieve help messages 

@@RETRIEVE INPUT 

    Selection Criteria ___________.             .___ Short Report
                         .________|_________.   |___ Full  Report
       Event File ___.   |  Event Retrieval |   |___ Octal Report
                     |___|    Translation   |___|
      Packet File ___|   |   and/or Storage |   |
                         |__________________|   |___ Device History
   Merge File (binary) ___________|                  Files (binary)

Retrieve can be used to generate reports, or it can be used to establish
and maintain device history files.  If you choose to generate a report,
you can select one of three formats: Short, Full, or Octal (Hexadecimal
on VAX/VMS systems). If you choose to generate a device history file you
will be asked if you want to merge it with an existing (history) file.

At this prompt Retrieve is waiting for you to specify the name of the 
input file. You can specify a packet file or any binary event file you
want, including one generated by Retrieve. If you specify a packet file
you will be prompted for packet numbers. Press the RETURN key to select
the default (ERROR.SYS or ERRLOG.SYS). The file specification format is:
dev:<user>file.extension.version. For further information type: /Help.
@@


@@RETRIEVE PACKETS

All theories and many summaries listed in the Analyze report have a
matching packet. The packet is numbered and contains a set of pointers
that identify the records that were summarized or used as evidence to
support the theory. The packet file that was generated in conjunction
with the Analyze report contains the packets and name of the file that
was analyzed.

At this prompt Retrieve is waiting for you to specify the packets that
contain the pointers to the records that you want to select and then
translate or save. The numbers you enter will remain until you type
/CLEAR at this prompt. You can:

  1. Enter a single packet number.
  2. Enter a list of packet numbers separated by commas.

NOTE: If you specify multiple packets the records involved will be
arranged in the order that they appear in the event file. That is
to say, the records will not be grouped by packet number.

For further information type: ? or /Help.
@@


@@RETRIEVE TYPE

Selected events can be either included in, or excluded from, the output
file. The following example illustrates the difference between the two.

                Include(event type C)         Exclude(event type C)

Time:               From        To               From        To
                     :           :                :           :
Input  file:   CABBACBCCAABCABBCAACCBCA     CABBACBCCAABCABBCAACCBCA
Output file:          CC   C   C            CABBACB  AAB ABB AACCBCA

At this prompt Retrieve is waiting for you to indicate whether you want
the events included in, or excluded from, the output file. You can:

  1. Type INCLUDED or press the RETURN key to include the selected
     events in the output file.

  2. Type EXCLUDED to exclude the selected event from the output file.

NOTES: You will be prompted for event types and time parameters later.

@@


@@RETRIEVE CATEGORY

At this prompt Retrieve is waiting for you to specify the first level
of entry selection. You can:

  1. Press the RETURN key or type ALL if you want to select all the
     entries that are in the event file.

  2. Type ERROR if you are interested in either a general class, or a
     specific type of error. Retrieve will then prompt you for more 
     information about the type errors that you are interested in.

  3. Type SEQUENCE if you want to select entries by sequence number.

  4. Type NONERROR if you want to select ALL non-error related entries.

  5. Type CODE if you want to select entries by event code.


NOTE: You will be prompted for time parameters later.

For further information type: ? or /Help.
@@


@@RETRIEVE SEQUENCE

Spear assigns a sequence number to each record in the event file. The
number refers to the records position in the file. (ie, sequence number
1 refers to the first record in the file, sequence number 2 refers the
second record, etc.)  Retrieve prints the sequence number in the header
of each report that it generates. As long as the order of the records in
the file are not changed (partially deleted or merged with an other
file) the sequence numbers used in the report will be current. Thus, in
most cases, you can use the number to refer to a specific record.

At this prompt Retrieve is waiting for you to enter the sequence numbers
that correspond to the records that you wish to select. You can:

   1. Enter a single sequence number.
   2. Enter a list of sequence numbers separated by commas.
   3. Enter a range of sequence numbers separated by a dash.

NOTE: The numbers you enter will remain until you type /CLEAR at this 
      prompt.
@@


@@RETRIEVE CODES
Generally speaking, the TOPS-10, TOPS-20 and VAX/VMS operating systems
handle errors in a similar manner. That is, when an error occurs they
snapshot pertinent hardware and software status (at error). Then, if
applicable, an error retry algorithm is applied. Next, regardless of
whether or not the retry algorithm was successful, a second snapshot
is taken (at end). Finally, the captured status is put into a record,
assigned a code, and appended to the system event file.

The operating systems differ, however, in the way that they snapshot
the status, implement the retry algorithms, and assign codes to the
error or event record. Refer to the Spear Manual for a description of
each TOPS-10, TOPS-20, and VAX/VMS event record. The codes are listed
on the back of the Spear Reference Card.

At this prompt Retrieve is waiting for you to enter the event codes that
correspond to the records that you want to select. You can:

  1. Enter a single event code.
  2. Enter a list of codes separated by commas.

For further information type: ? or /Help.
@@


@@RETRIEVE TIME FROM

                Time From:           Time To:
         ***********|oooooooooooooooooooo|***********
                02-Mar-81            09-Mar-81
                18:30:45             23:30:01

You can use the "Time From:" and "Time To:" prompt to specify the
part of the event file that you want the selected entries extracted or
excluded from. At this prompt Retrieve is waiting for you to enter the
time at which you want the selection process to begin. You can:

  1. Press the RETURN key to default to the EARLIEST time in the file.

  2. Enter real time. The format is: dd-mmm-yy hh:mm:ss where dd is the
     numerical day, mmm is the first three letters of the month, yy is
     the year, hh is the hour, mm the minute, and ss the second. If only
     the date is specified, the default time is 1 second after midnight.

  3. Enter relative time. The format is: -dd  where -dd is the number of
     past days. To indicate today at 00:00:01 hours, type: -0
     For further information type: ? or /Help.
@@


@@RETRIEVE TIME TO

                   Time From:           Time To:
            ***********|oooooooooooooooooooo|***********
                   02-Mar-81            09-Mar-81
                   18:30:45             23:30:01

At this prompt Retrieve is waiting for you to specify the time at which
you want the extraction (or exclusion) process to end. You can:

  1. Press the RETURN key to default to the LATEST time in the file.

  2. Enter real time. The format is: dd-mmm-yy hh:mm:ss where dd is the
     numerical day, mmm is the first three letters of the month, yy is
     the year, hh is the hour, mm the minute, and ss the second. If only
     the date is specified, the default time is 1 second after midnight.

  3. Enter relative time. The format is: -dd  where -dd is the number of
     past days. To indicate today at 00:00:01 hours, type: -0
     For further information type: ? or /Help.
@@


@@RETRIEVE STYLE

Remember, Retrieve is used to translate and/or save selected entries in
the system event file. The result will be either an ASCII report file or
a special purpose binary file. At this prompt Retrieve is waiting for
you to specify the type of output file that you want generated. You can:

  1. Type ASCII or press the RETURN key. The result will be a report
     file. The next prompt will ask you to specify the report format.

  2. Type BINARY. The result will be a binary event file that contains
     only the events that you have specified. If you type binary, the
     the next prompt will ask you if you want to merge these entries
     with an existing binary file. The merge feature is useful if you
     are maintaining a device history file.

NOTE: If you are using the Exclude capability, you will translate or
save all of the entries that are in the input file except for those 
that you selected for exclusion during the time period you specified.

For further information type: ? or /Help.
@@


@@RETRIEVE FORMAT

Retrieve is about to translate the entries that you specified. This
prompt is waiting for you to select the report format that you want.
You can:

 1. Type SHORT. The result will be a set of brief (3 or 4 line) reports
    that list the major symptoms or conditions contained in each entry.

 2. Type FULL. The result will be a set of detailed reports that list
    all of the information contained in each entry.

 3. Type OCTAL. The result will be a set of octal reports that reflect
    the binary contents of each entry. This format is used for program
    debugging and event file verification purposes.

NOTE: Typically, the default format, Short, is used to translate packets
and lengthly system event files. Then, the sequence number listed in the
header of each report, is used to select specific entries for a Full
translation.

For further information type: ? or /Help.
@@


@@RETRIEVE MERGE

You can merge the entries that you have selected with the entries in
an existing binary event file. The entries will be arranged in chrono-
logical order according to the date and time stamps. At this prompt
Retrieve is waiting for you to enter the name of the file that contains
the entries that want these entries merged with. You can:

  1. Press the RETURN key or type NUL: if you do not want to merge these
     entries with an existing (binary) file.

  2. Enter the name of the merge file that contains the entries. The
     standard file specification is: dev<user>file.extension.version.


NOTE: The contents of the merge file will not be affected. If you are
updating a history file and you do not want to keep a backup copy, then
you should specify the name of the merge file at the "Output to" prompt.

For further information type: ? or /Help.
@@


@@RETRIEVE OUTPUT

At this prompt Retrieve is waiting for you to specify a destination for
the output file. You can:

  1. Press the RETURN key to select the default file specification. If
     you requested an ASCII report (Brief, Full or Octal format) the
     default file name will be DSK:RETRIE.RPT. If you requested a Binary
     (history file) the default file name will be DSK:RETRIE.SYS.

  2. Enter your own unique file name. (e.g., DSK:SHORT.TAP. The standard
     file specification format is: dev:<user>file.extension.version.

  3. Type TTY: in which case the file will be printed on you terminal.
     Understand that if you specify TTY: the file will not be saved.


NOTE: If you request and save a report file, then you can use any text
editor to review the report. Of course, you can also type or print the
file as you wish.

For further information type: ? or /Help.
@@


@@ERROR CATEGORY
Retrieve is waiting for you to specify the type of errors that you want
to select. Press the RETURN key to select all errors, or type:

  MAINFRAME ....to select Console Front-end, CPU, or Memory errors.
  DISK......... to select Disk subsystem or individual Drive errors.
  TAPE..........to select Magtape subsystem or individual Drive errors.
  UNITRECORD... to select Card Reader or Line Printer errors.
  COMM ........ to select ALL Communications subsystem errors.
  NETWORK...... to select ALL Network errors.
  SOFTWARE..... to select ALL Software errors.
  CRASH.........to select BUGINF, BUGCHK, BUGHLT, or STOPCODE errors.
  PACKID........to select Disk errors based on Pack or structure IDs.
  REEL-ID.......to select Magtape errors based on Reel or label IDs.

This prompt loops, so you can select as many error types as you want.
Type /CLEAR at the beginning of this prompt clear all previous ERROR
selections. Press the RETURN key at this prompt when you are FINISHED.
Type /SHOW to check your selection. You can enter your selections on a
single line. Use a + sign to separate each error class. Use a colon to
separate error class from device types. Use commas to separate device
types. Example:  DISK:DP220,DP030+TAPE:MT170,MT166 etc
@@


@@ERROR_MAINFRAME

Retrieve defines the mainframe as: the console front-end processor, all
central processing units, and the main memory subsystem. At this prompt
you can:

 1. Press the RETURN key to select ALL mainframe related errors.

 2. Type FE to select errors that pertain to the console processor.

 3. Type CPU to select errors that pertain to the master and (if any)
    all slave central processing units.

 4. Type MEM to select processor detected errors that seem to be related
    to main memory.

NOTE: Error classification at this level is very difficult because of
the complex "cause and effect" relationship between the components. 
Therefore if you're working on an intermittent system problem, you may
be better off translating ALL mainframe errors.

For further information type: ? or /Help.
@@


@@ERROR_DISKS

You can select disk entries by logical or physical name. Logical names
are system dependent. Many systems, however, define the disk subsystem
as DPnx0, where DPn identifies the channel and controller, and x0
identifies a specific drive. At this prompt you can:

  1. Press the RETURN key to select ALL disk entries.
  2. Type DPn   to select all entries that pertain to disk channel n.
  3. Type DPnx0 to select all entries that pertain to a specific drive.
  4. Type physical names to select entries by option type.
     (RM03, RM05, RP04, RP05, RP06, RP07, RP08, RP20, RS04)


NOTE: Type /CLEAR to clear all disk selections and start over again. You
can enter multiple selections on a single line, and you can mix logical
and physical names. Separate each selection with a comma.
For further information type: ? or /Help.

Example:  DP040,DP220,DP150 
Example:  DP030,RP07,DP020,RP20
@@


@@ERROR_TAPES

You can select magtape entries by logical or physical name. Logical
names are system dependent. Most systems, however, define the magtape
subsystem as MTxyz, where x is the channel, y is the master controller,
and z is the drive or slave number. At this prompt you can:

  1. Press the RETURN key to select ALL magtape entries.
  2. Type MTx to select all entries that pertain to a channel (x).
  3. Type MTxy to select all entries that pertain to controller (y).
  4. Type MTxyz to select all entries that pertain to drive (z).
  5. Type physical names to select entries by option type.
     (TE16, TU45, TU70, TU71, TU72, TU73, TU77, TU78)


NOTE: Type /CLEAR to clear all tape selections and start over again. You
can enter multiple selections on a single line, and you can mix logical
and physical names. Separate each selection with a comma.
For further information type: ? or /Help.

Example:   MTA3,MTA7,MTC5
Example:   MT140,TU45,TU78,MT403
@@


@@ERROR_UNIT_RECORD

Unit record equipment refers to line printers and card readers. At this
prompt you can:

   1. Press the RETURN key to select ALL unit record errors.

   2. Type LPT to select ALL line printer errors.

   3. Type CDR to select ALL card reader errors.


For further information type: ? or /Help.
@@

@@ERROR_NET

At this prompt Retrieve is waiting for you to enter the number of the
DECNET Phase III Event Message Class that you want to select.The Classes
are:

 Class     Description
    0     Management layer
    1     Application layer
    2     Session Control layer
    3     Network Services layer
    4	  Transport layer
    5     Data Link layer
    6     Physical Link layer
 007-031  Reserved for Other common event classes
 032-063  Reserved for RSTS specific event classes
 064-095  Reserved for RSX specific event classes
 096-127  Reserved for TOPS-20 specific event classes
 128-159  Reserved for VMS specific event classes
 160-191  Reserved for RT specific event classes
 192-479  Reserved for Future use
 480-511  Reserved for Customer specific event classes
@@
@@ERROR_COMM
     ********* This is an obsolete help message  *******
Specific communications device types.  Example: DH11, DZ11, etc.
Specific devices may not be selected.  The default response is "ALL".
@@

@@ERROR_CRASHES

The TOPS-10, TOPS-20 and VAX/VMS operating systems report software as
well as hardware detected errors. If the system detects an error, or an
unusual software condition, an appropriate message is printed and, in
most cases an entry is recorded in the system event file. Under TOPS-10
these entries are called STOPCODES; under TOPS-20 they are called
BUGINFS, BUGCHKS, and BUGHLTS; under VAX/VMS they are called BUGCHKS,
and BUGHLTS. At this prompt Retrieve is waiting for you to enter the
name of the BUG type or STOPCODE that you want to select. You can:

 1. Press the RETURN key to select ALL entries of this type.

 2. Enter the name of a specific STOPCODE or BUG type.

 3. Enter a list of names separated by commas.


NOTE: TOPS-10 STOPCODES are listed in the TOPS-10 Software Notebooks,
TOPS-20 BUG types are listed in the TOPS-20 Operators Guide and,
VAX/VMS BUG types are listed in the VAX/VMS Software Support Notebook.
For further information type: ? or /Help.
@@

@@ERROR_DISK_PACKS

You can extract or exclude disk entries based on Pack or structure IDs.
The extraction (or exclusion) will be done in addition to any other disk
entries that you may have selected. For example, if you have selected a
disk channel or a specific physical or logical disk drive, then those
entries as well as any entries that you select at this prompt will be
considered part of the inclusion (or exclusion) selection criteria.

At this prompt Retrieve is waiting for you to enter the structure name
or Pack ID that correspond to the disk entries that you wish to select.
You can:

   1. Enter a single structure or Pack ID.

   2. Enter a list of structure names or Pack IDs separated by commas.


For further information type: ? or /Help.
@@


@@ERROR_REEL_IDS

You can extract or exclude tape entries based on label or Reel IDs. The
extraction (or exclusion) will be done in addition to any other magtape
entries that you have selected. For example, if you have selected a tape
channel or a specific physical or logical tape drive, then those entries
as well as any entries that you select at this prompt will be considered
part of the inclusion (or exclusion) selection criteria.

At this prompt Retrieve is waiting for you to enter the label or Reel ID
that correspond to the tape entries that you wish to select. You can:

   1. Enter a single Reel ID.

   2. Enter a list of Reel IDs separated by commas.


For further information type: ? or /Help.
@@

!sum_help - Summarize help messages

@@SUMMARIZE INPUT

     System Event File ___.   .----------.
                          |   |  Event   |
                          |___|  File    |____ Summary Report
           Retrieve       |   | Summary  |
         (binary) File ___|   |__________|

          INPUT                 PROCESS             OUTPUT

Summarize reads the specified event file, summarizes its contents and
produces a report file. The contents are summarized by: event code,
STOPCODE or BUGxxx code types, front-end reloads, channel errors, disk
errors and magtape errors.

At this prompt Summarize is waiting for you to specify the name of the
input file. You can specify any binary system event file you want,
including a binary file produced by Retrieve.  The file specification
format is: dev:<user>file.extension.version. Press the RETURN key if you
want to default to the local system event file (ERROR.SYS or ERRLOG.SYS)
For further information type: ? or /Help.
@@


@@SUMMARIZE TIME FROM 
                        Time From:           Time To:
                 ***********|oooooooooooooooooooo|***********
                        02-Mar-81            09-Mar-81
                        18:30:45             23:30:01

You can use the "Time From:" and the "Time To:" prompts to specify the
period during which you want the event file summarized. At this prompt
Summarize is waiting for you to specify the time at which you want the
file summary to begin. You can:

 1. Press the RETURN key to default to the first event in the file.

 2. Enter real time. The format is: dd-mmm-yy hh:mm:ss  where dd is the
    numerical day, mmm is the first three letters of the month, yy is
    the year, hh is the hour, mm the minute, and ss the second. If only
    the date is specified, the default time is 1 second after midnight.

 3. Enter relative time. The format is: -dd  where -dd is the number of
    past days. To indicate today at 00:00:01 hours, type: -0

For further information type: ? or /Help.
@@


@@SUMMARIZE TIME TO

                      Time From:            Time To:
               ***********|ooooooooooooooooooooo|***********
                      02-Mar-81            09-Mar-81
                      18:30:45             23:30:01

At this prompt Summarize is waiting for you to specify the time at which
you want the file summary to end. You can:

  1. Press the RETURN key to default to the LATEST time in the file.

  2. Enter real time. The format is: dd-mmm-yy hh:mm:ss where dd is the
     numerical day, mmm is the first three letters of the month, yy is
     the year, hh is the hour, mm the minute, and ss the second. If only
     the date is specified, the default time is 1 second after midnight.

  3. Enter relative time. The format is: -dd  where -dd is the number of
     past days. To indicate today at 00:00:01 hours, type: -0

For further information type: ? or /Help.
@@


@@SUMMARIZE REPORT

The big picture is still: Input - Process - Output. Remember, Summarize
is designed to summarize the information contained in the local system
event file.  The result is a report file. At this prompt Summarize is
waiting for you to specify a destination for the report file. You can:

1. Press the RETURN key to select the default file specification:
   DSK:SUMMAR.RPT.

2. Enter your own unique file specification (e.g., DSK:WEEKLY.SUM).
   The file specification format is: dev:<user>file.extension.version.

3. Type TTY: in which case the report will be printed on your terminal.
   The report is 132 columns which may make it difficult to read. Also,
   Understand that if you specify TTY: the file will not be saved.

NOTE: If you save the file, you can use any text editor to review the
report. Of course, you can also print or type the report as you wish.

For further information type: ? or /Help.
@@

!com_help - Compute help messages

@@COMPUTE INPUT

                       .--------------.   .___ Summary Report
                       |  Calculate   |   |
  System Event File ___|    System    |___|___ Availability Report
   (or AVAIL.Ann)      | Availability |   |
                       |______________|   |___ Reload Report


TOPS-10, TOPS-20, and VAX/VMS record entries that are used by Compute
to calculate overall system performance. Under TOPS-10 the entries are
recorded in a file called AVAIL.SYS. Under TOPS-20 and VAX/VMS the
entries are recorded in ERROR.SYS and ERRLOG.SYS respectively.

At this prompt Compute is waiting for you to specify the name of the
file that contains the entries that correspond to the period, during
which you want system performance calculated. You can:

1. Specify a file name. The format is: dev:<user>file.extension.version

2. Press the RETURN key, in which case Compute will determine the input
   file based on the system type (TOPS-10, TOPS-20, or VAX/VMS).
@@COMPUTE PERIOD

At this prompt Compute is waiting for you to specify the period of time
for which you want system performance calculated. You can:

 1. Type THIS-WEEK if you want the report to cover this week; beginning
    with last Sunday at 00:00:01 and continuing thru to the present.

 2. Press the RETURN key or type LAST-WEEK if you want the report to
    cover the 7 days (168 hours) prior to last Sunday at 00:00:01.

 3. Type OTHER if you want the report to cover a period of time other
    than THIS-WEEK or LAST-WEEK. You will be prompted for the date and
    time parameters next.
@@COMPUTE TIME FROM

                       Time From:            Time To:
                ***********|ooooooooooooooooooooo|***********
                       02-Mar-81            09-Mar-81
                       18:30:45             23:30:01

Using the "Time From:" and the "Time To:" prompt, you can specify the
time period during which you want system performance calculated. At
this prompt Compute is waiting for you to enter the time at which you
want the calculation to begin. You can:

  1. Press the RETURN key to default to the earliest time in the file.

  2. Enter real time. The format is: dd-mmm-yy hh:mm:ss where dd is the
     numerical day, mmm is the first three letters of the month, yy is
     the year, hh is the hour, mm the minute, and ss the second. If only
     the date is specified, the default time is 1 second after midnight.

  3. Enter relative time. The format is: -dd  where -dd is the number of
     past days. Enter -0 to refer to today at 00:00:01 hours.
@@COMPUTE TIME TO

                       Time From:            Time To:
                ***********|ooooooooooooooooooooo|***********
                       02-Mar-81            09-Mar-81
                       18:30:45             23:30:01

At this prompt Compute is waiting for you to specify the time at which
you want the calculation to end. You can:

  1. Press the RETURN key to default to the latest time in the file.

  2. Enter real time. The format is: dd-mmm-yy hh:mm:ss where dd is the
     numerical day, mmm is the first three letters of the month, yy is
     the year, hh is the hour, mm the minute, and ss the second. If only
     the date is specified, the default time is 1 second after midnight.

  3. Enter relative time. The format is: -dd  where -dd is the number of
     past days. Enter -0 to refer to today at 00:00:01 hours.
@@COMPUTE TYPE

Compute can generate a single report, or a set of weekly reports, that
reflect system performance. At this prompt Compute is waiting for you
to specify the type of report that you want. You can:

 1. Press the RETURN key or type SINGLE if you want a single report that
    reflects the system performance for the specified period.

 2. Type MULTIPLE if you want the system performance broken down into a
    set of weekly reports. Each report will reflect system performance
    for a 7 day period beginning on Sunday at 00:00:01 and ending on
    the following Sunday at 00:00:00.
@@COMPUTE OUTPUT

Compute generates two reports; a 72 column Summary Report, and a 132
column Availability Report. The Summary Report is automatically output
to your terminal. At this prompt Compute is waiting for you to specify
a destination for the Availability Report. You can:

 1. Press the RETURN key to select the default file specification:
    DSK:COMPUT.RPT.

 2. Enter a unique file specification (e.g., DSK:WK21.RPT). The file
    specification format is: dev:<user>filename.filetype.version.

If you specified multiple reports, then Compute will generate a set of
weekly reports in addition to COMPUT.RPT. The reports will be named
Cmmdd.RPT. Where mmdd corresponds to the month and day of each week.
@@COMPUTE RELOAD

In addition to the Summary and Availability Reports, Compute can also
generate a Reload Report. The Reload Report uses 132 columns and lists
the system name, the operating system version, the number of times the
system was reloaded, and the operators response to the question: "Why
Reload ?". At this prompt you can:

 1. Press the RETURN key to select the default file specification:
    DSK:RELOAD.RPT.

 2. Enter a unique file specification (e.g., DSK:WK21.RPT). The file
    specification format is: dev:<user>filename.filetype.version.

If you specified multiple reports, then Compute will generate a set of
weekly Reload Reports in addition to RELOAD.RPT. The weekly reports will
be named RLmmdd.RPT. Where mmdd corresponds to the month and first day
of each week (i.e., Sunday at 00:00:01).
@@

!ins_help - Instruct help messages
ran_quest_help
quest_help
ans_help
theory_query_help
no_help
text_help
menu_help
fwd_trans_help
rev_trans_help

@@ran_quest_help

Part of Instruct consists of a series of sixty question. The questions
pertain to: the system event files (ERROR.SYS and ERRLOG.SYS), the Spear
Library dialogs, and the Spear Library reports. 

The Random Question feature is primarily a Course Administrators tool.
It allows the Course Administrator to randomly select a few questions
that will help determine a students progress. If the student is able
to answer 8 out of 10 random questions correctly, then chances are he
(or she) understands how to use the Spear Library. If not, then perhaps
a little more study time is needed.

Students can also use the Random Question feature as a self evaluation
tool. To do so, enter a random number in the range of 1 to 60. Instruct
will dispatch to a corresponding random question. Answer the question to
the best of your knowledge. Instruct will evaluate your answer and print
an approprate message. 

At that point you can type: RANDOM and select another random question.
@@
@@quest_help

You are participating in a teaching dialog informally referred to as the
"Rhetorical Approach to Learning". The approach involves a statement
about a subject; in this case the Spear Library. You are to determine
whether the statement is True or False.

If your answer is correct you will receive a short message and then go
on to the next statement. If your answer is incorrect, then the correct
answer will be explained and the statement will be repeated. If you are
not sure whether the statement is True or False, you can press the
RETURN key and the correct answer will be explained.

In addition to the True, False, and RETURN key response, you can type
NEXT if you want to skip to the next statement. You can also press the
BACKSPACE key if you want to return to the menu.
@@
@@ans_help

You have just answered a question either correctly or incorrectly. You
now have three choices. You can:

 1. Press the RETURN key. If you answered the question correctly you
    will continue on to the next sequential question. If, however, you
    answered the question incorrectly, then the question will be
    repeated.

 2. Type NEXT to continue on to the next sequential question regardless
    of whether you answered the last question correctly or not.

 3. Press the BACKSPACE key to repeat the last question regardless of
    whether your answer was correct or not.

Your response please:
@@
@@theory_query_help

You can use Instruct to directly reference any theory report produced by
Analyze. Enter the theory number (including the periods), then press the
RETURN key. Instruct will dispatch directly to that theory description.

For example: To go directly to Theory 1.1.1  type: 1.1.1<cr>

If, after investigating a theory, you decide that you want to go back
and select an other theory; type: QUERY<cr>.


For a complete list of theory numbers type: ?
@@
@@no_help

There really isn't anyway that we can help you at this point. Press the
BACKSPACE key and try reading the text again. If it still doesn't make
sense, then contact:

	The Spear Team
	MR1-2 S37

		Sorry
@@
@@text_help

Instruct is frame oriented. That is, it displays one frame or block of
information at a time. After you have read the frame you can:

1. Press the RETURN key to proceed to the next frame of information.

2. Press the BACKSPACE key to review the previous frame of information.

3. Type MENU if you want to go back to the subject menu.

4. Type QUERY to return to the Theory Query prompt.
@@
@@menu_help

Instruct is organized around a hierarchy of subject menus. The menus
allow you to use Instruct as a reference tool. The top item on the 
menu (item 0) introduces the subjects and explains there relationship.
The remaining items are subjects. You can select any item on the menu
by typing the number that corresponds to the item. You can also press
the RETURN key to automatically proceed to the first subject on the
menu. If you want to go back to the previous menu in the hierarchy you
can type MENU.
@@
@@fwd_trans_help

Instruct is organized around a hierarchy of subject menus. You can use
the RETURN key feature to sequence through the subjects listed on the
menu. Each time you transition from one subject to a other you will
be notified. At this point you can choose to go on by pressing the
RETURN key, or you can choose to go back to the menu and select a
different subject by typing MENU.
@@
@@rev_trans_help

Instruct is designed in such a way that you can go forward and backward 
through the subject matter. Each time you transition from one subject to
another you will be notified. In this case you were notified that you
were about to back into to previous subject on the menu. At this point
you can:

 1. Type MENU to go back to the subject menu.

 2. Press the RETURN key to go back to where you came from.

 3. Press the BACKSPACE key, or type/REVERSE to continue backing up.
    However, if the subject that you are backing into required multiple
    frames of text to explain, then you will back into the last frame.

 4. Type BEGIN to backup to the first frame of the subject that you
    are backing into.
@@


!edits
 (EDITED BY LARRY ON 20-MARCH-81)
 (EDITED BY BOB SMITH ON 05-APRIL-81)
 (EDITED BY BOB SMITH ON 03-MAY-81) Fixed up Compute HELP
 (EDITED BY BOB SMITH ON 05-MAY-81) Added Theory Query HELP 
 (EDITED BY BOB SMITH ON 21-MAY-81) Corrected some Retrieve HELP msgs.
 (EDITED BY LARRY EMLICH ON 7-JUNE-81) Added Summarize
08-Jul-81 by B Smith Added Question and Answer Help messages