SYSTEM_REPORT.COM, UTILITIES, Generates textual- and HTML configuration report
Name: SYSTEM_REPORT
Version: V1.8
Release Date: 25-APR-2008
Language: DCL
Operating System: OpenVMS
Minimal OS version tested: V7.3
Maximal OS version tested: V8.3
Architecture: VAX, Alpha, IA64(untested)
This is from the help function (@SYSTEM_REPORT ?)
-------------------------------------------------
SYSTEM_REPORT V1.8
Usage: @SYSTEM_REPORT [Func1[,Func2,...]] [INCLUDE|EXCLUDE]
SYSTEM_REPORT analyzes the local node/cluster and creates two
configuration reports (.TXT,.HTML).
The amount of data collected, location of report files ... can
be customized via parameter P1 or the config file
SYSTEM_REPORT.CONF (search for #CUST).
P1: list of functions to call (default: call all functions)
Possible functions are:
CLUSTER display cluster infos including SCACP...
CONFLOG display some logicals
CONSVARS display console variables
CRASH display crash infos
DISKS display disk infos
GETSYI display F$GETSYI data
LAT display LAT infos
LICENSE display license information
NETWORK display network info
NETVARS display detailed network controller info
NODES list nodes with OS-Version, Boottime...
QUEUES display queue infos
RDB display RDB related infos
RECOVERY display recovery information
SAM display administrator accounts
SOFTWARE display software infos
USER display user accounts
P2: modify P1 meaning
INCLUDE - defaults all functions to FALSE (do not call)
and calls only P1 functions (default if P1 defined)
EXCLUDE - defaults all functions to TRUE (do call them)
and skips only P1 functions (default if P1 undefined)
The reports are put in a backup saveset afterwards for archiving purposes, named
'cluname'_SR_yyyyddmm.BCK.
Two external utilities are used (if available):
o DFU (from HP engineering) to create fragmentation reports (see customization s
If DFU is not available, the fragmentation report is skipped.
o ZIP to compress to backup saveset containing the report.
If RDB is selected and installed, the utility SYS$SHARE:RDB$SHOVER.COM
is used.
In clusters, SYSTEM_REPORT works on all voting clusternodes.
Non-voting nodes are treated, if a logical name
SYSTEM_REPORT_START_ON_node is defined.