Displays a chronological list of transactions performed on a
CMS library. You can limit the number of transactions that are
displayed by specifying different parameters and qualifiers on the
command.
Format:
SHOW HISTORY [object-expression]
1 – Command Parameters
object-expression
Specifies an object about which history information is to be
displayed. The object expression can be one or more class names,
element names, group names, a wildcard expression, or a list of
any of these, separated by commas. If you do not specify an object
expression, CMS lists all classes, elements, and groups in the
library.
2 – Description
The SHOW HISTORY command lists information about CMS library
transactions. CMS records all transactions that update the
library. The following transactions are not logged in the library
history:
ANNOTATE SET LIBRARY
DIFFERENCES SHOW commands
FETCH (no remark) VERIFY (no qualifiers)
RETRIEVE ARCHIVE
The SHOW HISTORY command displays a chronological list of
transactions. The transaction records are displayed in the
following format:
date time username command remark
A space separates each item in the transaction record. Each item
is explained below.
date
Displays the date the command was issued, in the following
format:
[d]d-mmm-yyyy
For example:
9-JUN-1988
time
Displays the time the command was issued, in the following
format:
hh:mm:ss
For example:
17:12:12
09:02:33
username
Displays the user name of the person who issued the command.
command
Identifies the command that was issued. The string "CMS" does
not appear as part of the command. The command name, option
name (if any), and any parameters are displayed. If the command
operates on a particular generation of an element, the element
name is followed by the generation number enclosed in parentheses;
for example, SEMANTICS.PAS(3). Qualifiers that indicate some
modification of the library are logged; for example, the /NAME
qualifier with a MODIFY command.
remark
Specifies a character string that was logged in the history file
with this command, usually used to explain why the command was
entered. The remark is enclosed in quotation marks. If no remark
was entered, a null remark ("") is displayed.
The following is an example of one transaction record:
11-AUG-1988 11:54:15 TAYLOR REPLACE SYNTAX.PAS(3) "RECORD and FOR
loop syntax compatible"
This record shows that on August 11, 1988, at 11:54, user TAYLOR
issued the REPLACE command on SYNTAX.PAS, which created generation
3.
For any command that caused an unusual occurrence, CMS displays an
asterisk in the first column.
Note that because transaction records for elements, groups, or
classes deleted from a library are retained (see DELETE ELEMENT,
DELETE GROUP, and DELETE CLASS), SHOW HISTORY can display records
for elements and classes that do not currently exist. If a deleted
name is reused, SHOW HISTORY does not distinguish between the old
and the new histories.
3 – Qualifiers
3.1 /APPEND
Controls whether CMS appends the command output to an existing
file, or creates a new file. If you specify /APPEND and the output
file does not exist, CMS creates a new file. If you do not provide
an output file specification (see the description for /OUTPUT),
the output is appended to SYS$OUTPUT.
3.2 /BEFORE=date-time
Lists all history information prior to a specified date. By
default, the time is the current date and time. The time value
can be an absolute, delta, or combination time value, or one of
the following keywords: TODAY, TOMORROW, or YESTERDAY.
3.3 /OCCLUDE[=option,...]
Controls whether CMS selects the first instance of the specified
object, or all instances of the specified object in the library
search list. The options field contains one or more keywords
associated with the name of the object. The options field can
contain the following keywords:
ALL--equivalent to OTHER
OTHER (D)
NOOTHER
NONE--equivalent to NOOTHER
You can specify either ALL, NONE, or the [NO]OTHER keyword.
By default, CMS performs occlusion for all objects; that is, CMS
selects only the first occurrence of a specified object.
3.4 /OUTPUT[=file-specification]
Directs CMS to write output to the specified file, except for any
warning and error messages, which are written to SYS$OUTPUT and
SYS$ERROR. CMS creates a new file if you do not specify /APPEND.
If you omit the /OUTPUT qualifier (or if you specify /OUTPUT
but do not provide a file specification), CMS directs output to
the default output device (SYS$OUTPUT). If you omit either the
file name or the file type component, CMS supplies the missing
component from the default specification.
3.5 /SINCE=date-time
Specifies that only those history entries dated on or after the
given time are to be displayed. The time value can be an absolute,
delta, or combination time value, or one of the following
keywords: TODAY, TOMORROW, or YESTERDAY. When the /SINCE qualifier
is omitted, all transactions that occurred since the library was
created are displayed. If you specify the /SINCE qualifier but do
not specify a value, CMS defaults to /SINCE=TODAY.
3.6 /TRANSACTIONS=(keyword,...)
3.7 /NOTRANSACTIONS=(keyword,...)
Displays all transaction records generated by a specific command.
You can specify the following keywords with this qualifier:
ACCEPT FETCH REMOVE
ALL INSERT REPLACE
CANCEL MARK RESERVE
COPY MODIFY REVIEW
CREATE REJECT SET
DELETE REMARK UNRESERVE
VERIFY
If you specify more than one keyword, you must enclose the keyword
list in parentheses. The /TRANSACTIONS qualifier directs CMS
to list transaction records for only the listed keywords. The
/NOTRANSACTIONS qualifier directs CMS to list transaction records
for all keywords except the listed keywords.
3.8 /UNUSUAL
Controls whether transactions recorded as unusual occurrences
are displayed. If you specify /UNUSUAL, only unusual transactions
are displayed. By default, /NOUNUSUAL displays all transactions,
including unusual occurrences. The following CMS transactions are
defined as unusual occurrences:
o A RESERVE command specifying an element that is already
reserved
o A concurrent replacement
o A VERIFY/RECOVER command
o A VERIFY/REPAIR command
o A CONVERT LIBRARY command
o A REMARK/UNUSUAL command
3.9 /USER=username
Lists the transactions executed by the specified user.
4 – Example
CMS> SHOW HISTORY
History of CMS Library DISKX:[PROJECTLIB]
15-JAN-1988 08:45:15 SNOW CREATE LIBRARY [PROJECTLIB] "code library"
25-JAN-1988 10:23:42 SNOW CREATE ELEMENT STRING.LIB(1) "string defs"
25-JAN-1988 13:37:57 SCHULTZ CREATE ELEMENT SIGNAL.LIB(1) "signaling
defs"
25-JAN-1988 14:09:37 PADDOCK CREATE ELEMENT CONVRT.BLI(1) "gen
conversion util"
26-JAN-1988 13:59:16 PADDOCK DELETE ELEMENT CONVRT.BLI "wrong format"
27-JAN-1988 10:51:05 PADDOCK CREATE ELEMENT CNVNUM.BLI(1) "conversion
routines"
10-FEB-1988 10:51:48 SNOW CREATE ELEMENT SYSUTL.BLI(1) "general
utilities"
21-FEB-1988 11:11:55 SNOW RESERVE STRING.LIB(1) "change definitions"
23-FEB-1988 11:22:31 SNOW REPLACE STRING.LIB(2) "added characters"
23-FEB-1988 11:23:41 PADDOCK RESERVE CNVNUM.BLI(1) "change constant
values"
23-FEB-1988 12:15:21 SNOW FETCH STRING.LIB(1) "check differences"
23-FEB-1988 12:20:42 PADDOCK REPLACE CNVNUM.BLI(2) "constant values
changed"
.
.
.
This command shows part of the early history of a library.