پ%ى Librarian A09-19•زيص}ِ ؟‘"ض}ِ lnmm%5DIAGNOSE ­؟‘"ض}ِ  1 DIAGNOSEFDIAGNOSE [/interface] [/interactive] [infile [...]] [/qualifier[...]]DDECevent is the interface between the system user and the operating Isystem's event logging system. DECevent allows users to produce reports Bderived from system events using the following modes of operation:L o /TRANSLATE Default, translates events using the system event log file G if no file is specified or a specified event log file.L o /BINARY Copies selected entries (for example, disk events) from one+ binary file to a new file.J o /CONTINUOUS Specifies that events are reported as they are logged by = the system. Events are viewed in real time.M o /DUMP Displays event data in a side-by-side hexadecimal and ASCII C byte-by-byte representation without text messages.E o /ANALYZE Analyzes and isolates faults on the operating system2 by calling out suspect devices.  +Users specify the user interface by using: ? o /INTERACTIVE Enters the DECevent interactive command shell.? o /INTERFACE Tells DECevent which command interface to use.2 /INTERACTIVEF Tells DECevent to enter the command line interface (CLI). It allowsF the user to start a DECevent session. It causes the DECevent prompt to be displayed, "DIA>". DIA/INTERACTIVE 2 /INTERFACEI Allows the user to tell DECevent which user interface to run. The userJ can specify a comman d line interface (CLI) or a graphical user interface (GUI). DIA/INTERFACE= interface_nameB interface_name can be either CHARACTER_CELL or DECWINDOWS. 2 /TRANSLATEK Performs bit-to-text translation of the event log specified by the infileH parameter. If no file is specified, then the system default event log F or the file that is explicitly set by the SET EVENT command is used.0 /TRANSLATE [infile [,...]] [/qualifier [,...]]4 infile: Name of the event log file to be used. 3 /BEFOREF Selects and formats all event reports that occurred before the time E specified. Time can be specified as an absolute time or it can be 9 specified by the keywords TODAY (default) or YESTERDAY. /BEFORE [=time]D time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC)3 /BRIEFE Specifies that the minimal amount of information for each selected " event report should be provided.3 /ENTRYH Selects events for reporting starting with the event recor d specified I by the keyword START and ending with the event record specified by the J keyword END. If no number is specified, then all event records from the 6 starting number to the end of the file are selected.% /ENTRY=(START:start [,END:end])  start: Entry numbers end: 3 /EXCLUDED Allows users to exclude event records meeting specific criteria. G The criteria can be specified as a list consisting of device name(s)  and/or keyword(s). 0 /EXCLUDE=([devic e-name][,...][,keyword][,...]) 4 keywords5 ATTENTIONS BUGCHECKS BUSES CACHE= CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS5 DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS> ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS9 IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS9 MEMORY NODES OS or OPERATING_SYSTEMS@ PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS8 SYNC_COMMUNICATIONS TA PES TIMEOUTS2 UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES4 device-namesA The /EXCLUDE qualifier can be used to exclude specific devices > or general device categories. Examples, of device names are ! SHEDUA$DUA0, DUA1, DKB, and DK. 4 example5 $ DIAGNOSE/TRANSLATE/EXCLUDE=(DKA,TAPES,MEMORY)D Excludes from the report all devices that have the controller and D unit designator of DKA, and also exclude from the report all TAPE  and MEMORY events. 3 /FSTERRE Provides a quick, one line per entry report from the event log for  disk and tape devices only. 3 /INCLUDEH Allows users to include event reports meeting specific criteria. The H criteria can be specified as a list consisting of device name(s) and,  or keyword(s). 0 /INCLUDE=([device-name][,...][,keyword][,...]) 4 keywords5 ATTENTIONS BUGCHECKS BUSES CACHE= CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS5 DEVICE _NAME DEVICE_NODE DEVICE_NUMBER DISKS> ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS9 IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS9 MEMORY NODES OS or OPERATING_SYSTEMS@ PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS8 SYNC_COMMUNICATIONS TAPES TIMEOUTS2 UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES4 device-namesA The /INCLUDE qualifier can be used to include specific devices > or general device categories. Examples, of device names are ! SHEDUA$DUA0, DUA1, DKB, and DK. 4 example5 $ DIAGNOSE/TRANSLATE/INCLUDE=(DKA,TAPES,MEMORY)B Includes in the report all devices that have the controller and B unit designator of DKA, and also include in the report all TAPE  and MEMORY events.3 /LOGH Controls the displaying of informational messages. The informational I messages, which are by default not displayed, consist of the number of K event reports selected and rejected while processing a file. The default is /NOLOG. /LOG /NOLOG 3 /NODEF Allows users to select event records based upon node name. If more G then one node is specified the names must be separated by commas and  enclosed in parentheses. /NODE = (node-name [,...])% node-name: A valid VMS node name. 3 /OUTPUTD Controls the output of the formatting command. The default is the ' standard output device (SYS$OU TPUT).  /OUTPUT= output_file I output_file: File specification to receive the command output. 3 /REVERSEH Specifies that event records are translated in reverse chronological G order, with the most recent events displayed first. The default is 4 to display events in forward chronological order.3 /SINCEE Selects and formats all event records that occurred since the time E specified. Time can be specified as an absolute time or it can be 9 specified by the keywords TODAY (default) or YESTERDAY. /SINCE [=time]D time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC) 3 /SUMMARY 3 Produces a summary of the selected event reports.3 /TERSED Specifies that the registers and header of each event records are G formatted using the standard report format, but the contents of each 5 register are not translated into readable messages.3 /FULL F Performs a full translation of events in the default event log file  or specified input file. !3 /REPORTC! The /REPORT qualifier allows the user to choose a special report'! type when formatting event reports. !!! /REPORT= !?! The parameter is the name of a special report.!5! FSTERR is currently the only valid special report.!!3 /SID_REGISTER=! Specifies the value obtained from the system ID register. ! )! /SID_REGISTER[=<%XHexadecimal-value>] ! 3 Examples3 The following are examples using /TRANSLATE mode: $ DIAGNOSE/TRANSLATE C Performs bit-to-text translation using the system default event1 log. The Report will be displayed to screen. D $ DIAGNOSE/TRANSLATE/SINCE=YESTERDAY/INCLUDE=(DISK,TAPE) ALPHA.SYSH Performs bit-to-text translation using the event log file ALPHA.SYS.D Include only disk and tape events that occurred since yesterday.? $ DIAGNOSE/TRANSLATE/INCLUDE=(DK)/OUTPUT=DK_ERR.RPT ALPHA.SYSH Performs bit-to-text translation using the event  log file ALPHA.SYS.A Includes only those events that are disk errors on DK device D designators and write the report to the file DK_ERR.RPT. 2 /BINARYH Copies event records from infile(s) that match the provided selection D criteria and writes them to a binary output file. The name of the L binary output file is specified as a parameter to the /BINARY qualifier. K If no infile is specified, then the system default event log or the file : that is explicitly set by the SET EVENT command is used.< /BINARY= bin_outputfile [infile[,...]] [/qualifier [,...]] - bin_outputfile: The binary output file.D infile: The name of the event log file(s) to be used. 3 /BEFOREF Selects and formats all event reports that occurred before the time E specified. Time can be specified as an absolute time or it can be 9 specified by the keywords TODAY (default) or YESTERDAY. /BEFORE [=time]D time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC)3 /ENTRYH Selects events for reporting starting with the event record specified I by the keyword START and ending with the event record specified by the J keyword END. If no number is specified, then all event records from the 6 starting number to the end of the file are selected.% /ENTRY=(START:start [,END:end])  start: Entry numbers end: 3 /EXCLUDED Allows users to exclude event records meeting specific criteria. G The criteria can be specifie d as a list consisting of device name(s)  and/or keyword(s). 0 /EXCLUDE=([device-name][,...][,keyword][,...]) 4 keywords5 ATTENTIONS BUGCHECKS BUSES CACHE= CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS5 DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS> ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS9 IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS9 MEMORY NODES OS or OPERATING_SYSTEMS@ PWR or POWER  SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS8 SYNC_COMMUNICATIONS TAPES TIMEOUTS2 UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES4 device-namesA The /EXCLUDE qualifier can be used to exclude specific devices > or general device categories. Examples, of device names are ! SHEDUA$DUA0, DUA1, DKB, and DK. 4 example; $ DIAGNOSE/BINARY=TEST.BIN/EXCLUDE=(DKA,TAPES,MEMORY)H Excludes from all devices that have the controll er and unit designator6 of DKA, and also exclude all TAPE and MEMORY events. 3 /INCLUDEH Allows users to include event reports meeting specific criteria. The H criteria can be specified as a list consisting of device name(s) and,  or keyword(s). 0 /INCLUDE=([device-name][,...][,keyword][,...]) 4 keywords5 ATTENTIONS BUGCHECKS BUSES CACHE= CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS5 DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS> ENVI RONMENTAL_ENTRIES HOSTS INFORMATIONALS9 IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS9 MEMORY NODES OS or OPERATING_SYSTEMS@ PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS8 SYNC_COMMUNICATIONS TAPES TIMEOUTS2 UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES4 device-namesA The /EXCLUDE qualifier can be used to exclude specific devices > or general device categories. Ex amples, of device names are ! SHEDUA$DUA0, DUA1, DKB, and DK. 4 example; $ DIAGNOSE/BINARY=TEST.BIN/INCLUDE=(DKA,TAPES,MEMORY)D Includes all devices that have the controller and unit designator 6 of DKA, and also include all TAPE and MEMORY events.3 /LOGH Controls the displaying of informational messages. The informational I messages, which are by default not displayed, consist of the number of K event reports selected and rejected while processing a file. The default  is /NOLOG. /LOG  /NOLOG3 /NODEF Allows users to select event records based upon node name. If more G then one node is specified the names must be separated by commas and  enclosed in parentheses. /NODE = (node-name [,...])% node-name: A valid VMS node name. 3 /REJECTEDE Places all entries that failed the selection criteria for a commandA in a binary output file. The name of the binary output file is6 specified as a parameter to the /REJEC!TED qualifier. /REJECTED [= reject_file ] D reject_file: An optional output file where the rejected event & records are stored. 3 /REVERSEH Specifies that event records are translated in reverse chronological G order, with the most recent events displayed first. The default is 4 to display events in forward chronological order.!3 /SID_REGISTER!?! Specifies the value obtained from the system ID register. ToE! reference the SID_REGISTER refer to the" section in the VMS System@! Services Reference manual that describes the $GETSYSI system ! service.! )! /SID_REGISTER[=<%XHexadecimal-value>] !3 /SINCEE Selects and formats all event records that occurred since the time E specified. Time can be specified as an absolute time or it can be 9 specified by the keywords TODAY (default) or YESTERDAY. /SINCE [=time]D time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC) 3 Examples0 The following are exampl#es using /BINARY mode:0 $ DIAGNOSE/BINARY=DEFAULT.BIN /SINCE=YESTERDAY? Creates a binary file, DEFAULT.BIN of all events that have @ been logged to the system default event log since yesterday.H $ DIAGNOSE/BINARY=DISK.BIN/REJECTED=REJ.BIN/INCLUDE=(DISK)/SINCE=TODAYI Creates a binary file, DISK.BIN, that contains only disk errors that H have been logged to the system default event log since today. Place : all other events in the rejected binary file, REJ.BIN.A $ DI $AGNOSE/BINARY=CPU.BIN/LOG/INCLUDE=(CACHE,MC,PARITY) REJ.BINB Uses the REJ.BIN binary file and creates a binary file of all  CPU type errors. 2 /CONTINUOUSJ Specifies that events are formatted as they are logged by the operating J system event logger in real time. The output by default is displayed on C the screen. Output can also be directed to a file by the /OUTPUT qualifier.! /CONTINUOUS [/qualifier [,...]]3 /BRIEFE Specifies that the minimal amount of information f %or each selected " event report should be provided. 3 /EXCLUDED Allows users to exclude event records meeting specific criteria. G The criteria can be specified as a list consisting of device name(s)  and/or keyword(s). 0 /EXCLUDE=([device-name][,...][,keyword][,...]) 4 keywords5 ATTENTIONS BUGCHECKS BUSES CACHE= CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS5 DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS> ENVIRONMENTAL_ENTRIES & HOSTS INFORMATIONALS9 IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS9 MEMORY NODES OS or OPERATING_SYSTEMS@ PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS8 SYNC_COMMUNICATIONS TAPES TIMEOUTS2 UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES4 device-namesA The /EXCLUDE qualifier can be used to exclude specific devices > or general device categories. Examples, of device names 'are ! SHEDUA$DUA0, DUA1, DKB, and DK. 4 example6 $ DIAGNOSE/CONTINUOUS/EXCLUDE=(DKA,TAPES,MEMORY)D Excludes from the report all devices that have the controller and D unit designator of DKA, and also exclude from the report all TAPE  and MEMORY events.3 /FULLF Performs a full translation of events in the default event log file  or specified input file. 3 /FSTERRE Provides a quick, one line per entry report from the event log for  disk and tape devices only. 3 /INC (LUDEH Allows users to include event reports meeting specific criteria. The H criteria can be specified as a list consisting of device name(s) and,  or keyword(s). 0 /INCLUDE=([device-name][,...][,keyword][,...]) 4 keywords5 ATTENTIONS BUGCHECKS BUSES CACHE= CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS5 DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS> ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS9 IOS or IO_SUBSYSTEMS ) MCHKS or MACHINE_CHECKS9 MEMORY NODES OS or OPERATING_SYSTEMS@ PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS8 SYNC_COMMUNICATIONS TAPES TIMEOUTS2 UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES4 device-namesA The /INCLUDE qualifier can be used to include specific devices > or general device categories. Examples, of device names are ! SHEDUA$DUA0, DUA1, DKB, and DK. 4 example6 $ *DIAGNOSE/CONTINUOUS/INCLUDE=(DKA,TAPES,MEMORY)B Includes in the report all devices that have the controller and 5 unit designator of DKA, all TAPE and MEMORY events.!3 /NODED! The /NODE qualifier allows the user to select event records basedE! upon node name. If more then one node is specified the names mustA! be separated by commas and enclosed in parentheses. Node names1! length must conform to current version of VMS.!! /NODE = ([,...])!$! is a +valid node name.! 3 /OUTPUTD Controls the output of the formatting command. The default is the ' standard output device (SYS$OUTPUT).  /OUTPUT= output_file I output_file: File specification to receive the command output. !3 /REPORTE! The /REPORT qualifier allows the user to choose the special report'! type when formatting event records. !!! /REPORT= !?! The parameter is the name of a special report.!5! FSTERR is, currently the only valid special report.!!3 /SID_REGISTER?! Specifies the value obtained from the system ID register. ToE! reference the SID_REGISTER refer to the section in the VMS System@! Services Reference manual that describes the $GETSYSI system ! service.! )! /SID_REGISTER[=<%XHexadecimal-value>] !3 /TERSED Specifies that the registers and header of each event records are G formatted using the standard report format, but the contents of each 5 register are n-ot translated into readable messages. 3 Examples4 The following are examples using /CONTINUOUS mode: $ DIAGNOSE/CONTINUOUS? Monitors events as they are logged by the operating system.( $ DIAGNOSE/CONTINUOUS/INCLUDE=(MEMORY)! Monitors only memory events. + $ DIAGNOSE/CONTINUOUS/EXCLUDE=(DISK,TAPE), Monitors all events except disk or tape.2 /DUMPD Dumps the contents of the infile in hexadecimal and ASCII formats. $ /DUMP [infile] [/qualifier [,...]]4 .infile: The name of the event log file to be used. 3 /BEFOREF Selects and formats all event reports that occurred before the time E specified. Time can be specified as an absolute time or it can be 9 specified by the keywords TODAY (default) or YESTERDAY. /BEFORE [=time]D time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC)3 /ENTRYH Selects events for reporting starting with the event record specified I by the keyword START and ending with the event record spec/ified by the J keyword END. If no number is specified, then all event records from the 6 starting number to the end of the file are selected.% /ENTRY=(START:start [,END:end])  start: Entry numbers end: 3 /EXCLUDED Allows users to exclude event records meeting specific criteria. G The criteria can be specified as a list consisting of device name(s)  and/or keyword(s). 0 /EXCLUDE=([device-name][,...][,keyword][,...]) 4 keywords5 ATTENTIONS BUGCHECKS 0 BUSES CACHE= CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS5 DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS> ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS9 IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS9 MEMORY NODES OS or OPERATING_SYSTEMS@ PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS8 SYNC_COMMUNICATIONS TAPES TIMEOUTS2 UNKNOWN_ENTRIES UNSOLICITED_MSCP 1 VMS_ENTRIES VOLUME_CHANGES4 device-namesA The /EXCLUDE qualifier can be used to exclude specific devices > or general device categories. Examples, of device names are ! SHEDUA$DUA0, DUA1, DKB, and DK. 4 example0 $ DIAGNOSE/DUMP/EXCLUDE=(DKA,TAPES,MEMORY)C Exclude from the report all devices that have the controller and D unit designator of DKA, and also exclude from the report all TAPE  and MEMORY events. 3 /INCLUDEH Allows users to include event reports meeting sp 2ecific criteria. The H criteria can be specified as a list consisting of device name(s) and,  or keyword(s). 0 /INCLUDE=([device-name][,...][,keyword][,...]) 4 keywords5 ATTENTIONS BUGCHECKS BUSES CACHE= CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS5 DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS> ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS9 IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS9 MEMORY NODES 3 OS or OPERATING_SYSTEMS@ PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS8 SYNC_COMMUNICATIONS TAPES TIMEOUTS2 UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES4 device-namesA The /INCLUDE qualifier can be used to include specific devices > or general device categories. Examples, of device names are ! SHEDUA$DUA0, DUA1, DKB, and DK. 4 example0 $ DIAGNOSE/DUMP/INCLUDE=(DKA,TAPES,MEMORY)B Includes 4 in the report all devices that have the controller and B unit designator of DKA, and also include in the report all TAPE  and MEMORY events.3 /LOGH Controls the displaying of informational messages. The informational I messages, which are by default not displayed, consist of the number of K event reports selected and rejected while processing a file. The default is /NOLOG. /LOG  /NOLOG3 /NODEF Allows users to select event records based upon node nam5e. If more G then one node is specified the names must be separated by commas and  enclosed in parentheses. /NODE = (node-name [,...])( node-name: Is a valid VMS node name. 3 /OUTPUTD Controls the output of the formatting command. The default is the ' standard output device (SYS$OUTPUT).  /OUTPUT= output_file I output_file: File specification to receive the command output. 3 /REVERSEH Specifies that event records are translated in reverse chronologica6l G order, with the most recent events displayed first. The default is 4 to display events in forward chronological order.!3 /SID_REGISTER?! Specifies the value obtained from the system ID register. ToE! reference the SID_REGISTER refer to the section in the VMS System@! Services Reference manual that describes the $GETSYSI system ! service.! )! /SID_REGISTER[=<%XHexadecimal-value>] !3 /SINCEE Selects and formats all event records that occurred since the time E sp7ecified. Time can be specified as an absolute time or it can be 9 specified by the keywords TODAY (default) or YESTERDAY. /SINCE [=time]D time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC) 3 Examples. The following are examples using /DUMP mode: $ DIAGNOSE/DUMP ALPHA.ERROR5 Dumps the contents of the event file ALPHA.ERROR.& $ DIAGNOSE/DUMP ALPHA.ERROR /REVERSEB Dumps the contents of the event file in reverse chronological order. 2 /ANALYZE 8F Provides the capability to either manually or automatically analyze B entities on an operating system. Notification to individuals on E selected mailing lists, as to the results of the analysis, is also supported. . /ANALYZE [infile [,...]] [/qualifier [,...]] 3 /BEFOREF Selects and formats all event reports that occurred before the time E specified. Time can be specified as an absolute time or it can be 9 specified by the keywords TODAY (default) or YESTERDAY. /BEFOR9E [=time]D time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC)3 /ENTRYH Selects events for reporting starting with the event record specified I by the keyword START and ending with the event record specified by the J keyword END. If no number is specified, then all event records from the 6 starting number to the end of the file are selected.% /ENTRY=(START:start [,END:end])  start: Entry numbers end: 3 /EXCLUDED Allows users to exclude event re :cords meeting specific criteria. G The criteria can be specified as a list consisting of device name(s)  and/or keyword(s). 0 /EXCLUDE=([device-name][,...][,keyword][,...]) 4 keywords5 ATTENTIONS BUGCHECKS BUSES CACHE= CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS5 DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS> ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS9 IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS9 MEMORY ; NODES OS or OPERATING_SYSTEMS@ PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS8 SYNC_COMMUNICATIONS TAPES TIMEOUTS2 UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES4 device-namesA The /EXCLUDE qualifier can be used to exclude specific devices > or general device categories. Examples, of device names are ! SHEDUA$DUA0, DUA1, DKB, and DK. 4 example3 $ DIAGNOSE/ANALYZE/EXCLUDE=(DKA,TAPES,ME<MORY)B Excludes from analysis all devices that have the controller and B unit designator of DKA, and also exclude from analysis all TAPE  and MEMORY errors. 3 /INCLUDEH Allows users to include event reports meeting specific criteria. The H criteria can be specified as a list consisting of device name(s) and,  or keyword(s). 0 /INCLUDE=([device-name][,...][,keyword][,...]) 4 keywords5 ATTENTIONS BUGCHECKS BUSES CACHE= CONFIGURATIONS CONTROL_ENTRIES CPUS = DEVICE_ERRORS5 DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS> ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS9 IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS9 MEMORY NODES OS or OPERATING_SYSTEMS@ PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS8 SYNC_COMMUNICATIONS TAPES TIMEOUTS2 UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES4 device-namesA The /INCLUDE > qualifier can be used to include specific devices > or general device categories. Examples, of device names are ! SHEDUA$DUA0, DUA1, DKB, and DK. 4 example3 $ DIAGNOSE/ANALYZE/INCLUDE=(DKA,TAPES,MEMORY)@ Includes in analysis all devices that have the controller and @ unit designator of DKA, and also include in analysis all TAPE  and MEMORY errors.3 /LOGH Controls the displaying of informational messages. The informational I messages, which are by default not displayed, ?consist of the number of K event reports selected and rejected while processing a file. The default is /NOLOG. /LOG  /NOLOG3 /NODEF Allows users to select event records based upon node name. If more G then one node is specified the names must be separated by commas and  enclosed in parentheses. /NODE = (node-name[,...])% node-name: A valid VMS node name. 3 /OUTPUTD Controls the output of the formatting command. The default is the ' stan@dard output device (SYS$OUTPUT).  /OUTPUT= output_file I output_file: File specification to receive the command output. 3 /SINCEE Selects and formats all event records that occurred since the time E specified. Time can be specified as an absolute time or it can be 9 specified by the keywords TODAY (default) or YESTERDAY. /SINCE [=time]D time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC) 2 SHUTDOWNI Halts the DECevent process on an operatingA system performing automatic analysis.  SHUTDOWN node-name( node-name: A valid VMS node name. 2 START8 Enables automatic analysis mode on operating systems.  START node-name& node-name: A valid VMS node name.2 HELP& Provides information on help topics. Help [help_req]A help_req: The help topic string. For example, SET provides 4 help information on the SET command.2 Additional_Commands@ A number of additional interactive commaBnds exist. They can be( executed at DIA> prompt or DCL prompt.3 ADD2 Allows the users to add information to DECevent. Valid ADD commands are: ADD USER ADD EXTERNAL !4 ANALYSISI! The ADD ANALYSIS command provides the fault manager with information, I! contained in a compiled ruleset file, required to perform analysis of ! a device type.!! ADD ANALYSIS file-name !5! file-name: Is a compiled analysis ruleset. !4 NOTIFICATION C! The ADD NOTIFCICATION command provides the fault manager with theE! ability to do different types of notification. This information is#! contained in a compiled ruleset.!! ADD NOTIFICATION file-name!8! file-name: Is a compiled notification ruleset.4 USERD Adds a user name to one or all of the notification mailing lists. F User names can be added to any of the mailing lists except the SICL 7 mailing list which is reserved for Digital use only. ADD USER user-name [mail-list] D5 user-name= Is the user name to be added to the specified mailing list. 5 mail-listB Valid notification mailing lists for the ADD USER command are: - CUSTOMER - FSE - MONITOR - SICL 4 EXTERNAL3 Adds an entry to one external notification lists.# ADD EXTERNAL entry_name list_name 5 entry_nameK On OpenVMS systems, is a logical name that points to a command procedure.8 On Digital Unix systems, is the name of a script file. 5 list_name% Can be one of CUSTOMERE or RESERVED. !4 CANONICALC! The ADD CANONICAL command adds support for canonical translationF! for new device types. This enables the fault manager to translate F! event records from any device that writes information to the event ! log file.!;! ANALYZE/ERROR ADD CANONICAL []!:! parameter is a file containing event report! canonical rules! :! parameter is an optional library name ! ! !4 SELECTION5! TheF ADD SELECTION command allows users to specify 7! criteria for the selection of events for formatting.9! The command associates a with a to a ! specify item for selection. !?! ANALYZE/ERROR ADD SELECTION =!8! parameter is a name to associate with the ! selection path!>! parameter is a path to a selection field of an event!>! is the name of data item in the ruleset to use while! G doing selection.!!.! For example: DISK HEADER.DISK DEVTYPE=RA90!!!4 TRANSLATION>! The ADD TRANSLATION command adds support for translation of>! event reports for new device types. This enables the fault;! manager to translate events from any device that writes %! information to the event log file.!=! ANALYZE/ERROR ADD TRANSLATION []!:! parameter is a file containing event report! translation rules! :! parameter is an optional library name !3 REMOVEB Allows the user to remove either compiled rulesets or data from  the fault manager. * The following are valid REMOVE commands:? REMOVE REPAIRED REMOVE SYSTEM_INFO REMOVE USER!! NOTE: E! When adding these command make sure that "3 REMOVE" gets updated! !4 ANALYSIS?! The REMOVE ANALYSIS command remove analysis knowledge about ! a specific device type.!! REMOVE ANALYSIS ruleset!1! r Iuleset: A valid path name to a ruleset.!4 NOTIFICATION A! The REMOVE NOTIFICATION command removes notification knowledge! about a specific device.!! REMOVE NOTIFICATION ruleset!1! ruleset: A valid path name to a ruleset. 4 REPAIRED A Removes repair information entered by a service engineer for a B specific device. This allows the repair database to be trimmed, E enhancing the usability of the information. Repair entries deleted E from the database are no lJonger available to the fault manager and  cannot be recovered. REMOVE REPAIRED dev-name% dev-name: A valid device name.4 SYSTEM_INFO F Removes information about a system under the fault manager's domain. REMOVE SYSTEM_INFO node-name* node-name: A valid node name.4 USER C Removes a user name from one or more of the notification mailing D lists. A valid user name must be specified. If no mailing list is E specified then the specified user name will beK removed from all of 1 the mailing lists except the SICL mailing list.# REMOVE USER user-name [mail-list] 5 user-name> Is the user name listed within the SHOW MAILING_LIST report. 5 mail-listE Valid notification mailing lists for the REMOVE USER command are: - CUSTOMER - FSE - MONITOR - SICL3 FLUSH = Clears out saved event information for a particular device. FLUSH dev-name( dev-name: Is a valid device name.3 SHOW B Displays information about L settings and selection parameters or < recorded data entries from the various product databases.  Valid show command are:; SHOW EXTERNAL SHOW KNL SHOW MAILING_LIST ; SHOW SELECT SHOW THEORY SHOW PARAMETERS 9 SHOW SICL SHOW THRESHOLD SHOW REPAIRED 2 SHOW SETTINGS SHOW SUMMARY SHOW TYPES 4 EXTERNAL; Displays the contents of the external notification lists.5 If a list_name isn't provided, the contents of all  exteMrnal lists is shown. SHOW EXTERNAL list_name 5 list_name% Can be one of CUSTOMER or RESERVED.4 KNLE Displays version information about each knowledge file. The report@ can be used to determine if knowledge files are out of date or? to determine the level of device support in a given knowledge< file. Versioning information was added to knowledge files8 to allow knowledge files to be distributed separatly.  The report format is:0 Knowledge File VersionN Information? File name Version Build Date PlatformE ===================================================================4 MAILING_LIST > Displays accounts that receive mail when different types of D notification messages are sent. If no mail-list is specified then % all of the mailing lists are shown. SHOW MAILING_LIST [mail-list] 5 mail-list< Valid mailing lists for the SHOW MAILING_LIST command are: - CUSTOMER - FSE - MONITOR - SI OCL4 PARAMETERS G Displays all settings related to notification. Valid show parameters  are as follows:9 - The telephone number for Digital Services (SET PHONE)A - The serial number of each registered system (SET SYSTEM_INFO)8 - The type of each registered system (SET SYSTEM_INFO)8 - The name of each registered system (SET SYSTEM_INFO)% - The current SICL state (SET SICL) 4 REPAIRED @ Shows the history of repair actions for the specified device. 6 Information isP displayed using the following format:5 Device Time Of Repair Comment; ======= ================= ==================; dev-nm dd-mmm-yyyy:hh:mm Engineer's comment SHOW REPAIRED [dev-name]6 dev-name: Specifies the name of a valid device. 4 SETTINGS C Displays the current status of an individual settings parameter. C If the setting parameter is omitted, then all setting parameters  are displayed. SHOW SETTINGS [settiQng]5 setting: The name of parameter to be displayed. 4 SELECT E Used to show the selections defined by the user. Each selection is B shown as a selection name and selection path pair, for example, E DISK HEADER.DISK.DEVTYPE. If the select-name is omitted, then all % selection information is displayed. SHOW SELECT [select-name] @ select-name: Parameter is the name of the selection to be  displayed.4 SICL E Displays the curRrent state of SICL (System Initiated Call Logging).4 SUMMARY B Displays a list of all devices that have crossed their assigned  notification threshold.  SHOW SUMMARY& The output has the following format:4 Device Class State Count Time4 ====== ===== ===== ===== ====8 dev-nm class curr-state err-cnt time-occured4 THEORY= Displays a list of all devices that have indicated faults. SHOW THEORY 6 The outpSut of this command has the following format:$ Device Theory Time Reported) ====== ======== =============== " dev-nm the-nm date-time 4 THRESHOLD D Displays current threshold values for a specific device or device I type. Threshold values determine when analysis and notification occur. H If no qualifiers are present, SHOW THRESHOLD will list thresholds for  all devices and device types.4 Output from this command has the following format:B T ---Hard--- ---Soft--- ---Info--- ---Media---B Device Cnt DSE Cus Cnt DSE Cus Cnt DSE Cus Cnt DSE CusC =================================================================E device cnt DSE Cus Cnt DSE Cus Cnt DSE Cus Cnt DSE Cus 1 SHOW THRESHOLD [/NAME=dev-name][/TYPE=dev-type]5 /NAME /NAME=dev-nameC Provides a device name for the command, where dev-name is a validC device name. Either the /TYPE or /NAME qualifier must be present.5 /TYPE /TYPE=Udev-type= The /TYPE qualifier provides a device type for the command,= where dev-type is a valid device type. Issue SHOW TYPES to 9 list the valid device types. Either the /TYPE or /NAME  qualifier must be present.4 TYPES? Displays devices that the fault manager currently recognizes @ under the specified subsystem. If no subsystem is specified, ; then all devices are listed under each of the subsystems. SHOW TYPES [subsystem] 5 subsystem@ The following are valid subsVystems for the SHOW TYPES command:  - CPU - IOS3 SETD Allows users to customize system settings. All SET commands must D be executed from the interactive command shell. The following are  valid set commands:; SET DEFAULT REPORT SET LOCALE SET EVENT A SET PHONE_NUMBER SET SICL SET SYSTEM_INFO  SET THRESHOLD !4 COMMANDF! Allows users to customize the style of the keyboard user interface F! used to enter commands. Individual usWers may set the keyboard user G! style to either UNIX-style or VMS-style commands. The default style $! is based on the operating system.!! SET COMMAND cli-style !,! cli-style: Must be either UNIX or VMS. 4 DEFAULT REPORTB Sets the default report used during translation. The report is A specified by giving a path name of a report generation ruleset. SET DEFAULT REPORT rule_name# rule_name: Name of ruleset. 9 For example, TRANSLATION.DEFAULT_R XEPORT4 EVENTD Allows users to select an event log file from which event reports G are formatted. This allows a user, in the interactive command shell, F to use an event log other than the default system event log without > specifying the file name on all of the subsequent commands. # SET EVENT file_name G file_name: Name of an event log to be used for formatting report.4 LOCALEB Allows users to override the locale file previously set for the C current systYem. This is done for internationalization reasons so ? that natural language conventions can be added in the future. SET LOCALE location B location: String defining the location of the user in terms A of the locale preferences available, for example,! AMERICAN_ENGLISH.!! NOTE: B! When adding these command make sure that "3 ADD" gets updated!4 PHONE_NUMBER E The SET PHONE_NUMBER command sets the phone number of the Customer ZG Support Center for a particular customer site, allowing the customer E notification mail message to provide the customer with the correct  number to call for service.= Change the phone number in interactive mode. Once changed,6 execute the SAVE SYSTEM SETTINGS command to save the phone number.? The current phone number setting can be seen by executing the SHOW PARAMETERS command. SET PHONE_NUMBER phone-number5 phone-number: Is the valid CSC phone number[.4 SICL F The SET SICL command turns the System Initiated Call Logging feature on or off. SET SICL state * state: Can be either ON or OFF.4 SYSTEM_INFO A Provides information to the fault manager about a system under its domain.B SET SYSTEM_INFO /SERIAL_NUMBER=num /NODE=node-name "system type"5 /SERIAL_NUMBER /SERIAL_NUMBER= num < Provides the serial number used for all service contracts. This qualifier is required.5 /NODE /NODE=node-nam\eG The valid VMS node-name of the system. This qualifier is required. 5 system typeB A required parameter that is a quoted string that describes the ! system, for example, "DEC 4000" 4 THRESHOLD D Alters threshold triggering for monitored devices. Thresholds can 5 be entered either by device name or by device type. SET THRESHOLD -H [/NAME=dev-name][/TYPE=dev-type]/CLASS=severity[/DSE][/CUSTOMER] count5 /NAME /NAME=dev-nameD Provides a device name for the command], where dev-name is a valid C device name. Either the /TYPE or /NAME qualifier must be present.5 /TYPE /TYPE=dev-typeD Provides a device type for the command, where dev-type is a valid @ device type. Issue SHOW TYPES to list the valid device types. 6 Either the /TYPE or /NAME qualifier must be present.5 /CLASS /CLASS=severity> The /CLASS qualifier is required. It specifies the level of , severity by one of the following keywords:- - HARD (A device could not recover da^ta)3 - SOFT (A device that may have recovered data)8 - INFO (Indicates informational events on a device)7 - MEDIA (Indicates events related to storage media)5 /DSE: Performed analysis when a device crosses this threshold.C When thresholds are crossed, the external notification proceduresC are invoked. Thresholds are set for different severity levels of events.9 Either the /DSE or /CUSTOMER qualifier must be present. 5 /CUSTOMER? Notifies the customer when a d_evice crosses this threshold. C When thresholds are crossed, the external notification proceduresD are invoked. Thresholds are set for different severity levels of events.= Either the /DSE or /CUSTOMER qualifier must be present. 5 countC The threshold value to be set for the specified device or device  type. 3 SAVE SETTINGS @ Allows users to store their current customization settings in A a default file. DECevent will use these defaults in subsequent commands`.  SAVE SETTINGS 3 RESTORE > Restores customized settings or the system defined settings. RESTORE SETTINGS RESTORE SYSTEM 4 SETTINGS@ Allows users to cancel customizations they may have set since D the last customization file was saved. This command does not make F sense when the fault manager is passed a command from the operating D system command line. For this reason it is only supported in the  interactive command shell.  RESTORE SETTINGS 4 SYSTEM SETTIaNGD Allows users to cancel customizations previously set and saved in G the customer system settings file. The command restores the default  system settings. RESTORE SYSTEM SETTINGS !3 DELETE >! The DELETE command provides the facility for deleting either$! canonical or translation rulesets !!4 TRANSLATION G! The DELETE TRANSLATION command DELETEs a translation ruleset. G! The result of this is that the fault manager will no longer beB! able to t branslate events that required that ruleset to beE! translated. The ruleset to be DELETEd from the fault manager/! is specified by a path to the ruleset.!:! ANALYZE/ERROR DELETE TRANSLATION []!=! The parameter is a period separated list of rulesetsE! stored in a hierarchy. The name on the left of aD! period is the parent of the ruleset on the right'! side of the period.!#! For exam cple: HEADER.DISK.RA90!<! The parameter is the optional library name.! !4 CANONICALG! The DELETE CANONICAL command DELETEs a canonical ruleset. TheC! result of this is that the fault manager will no longer beB! able to translate events that required that ruleset to beF! translated. The ruleset to be DELETEd from the fault manager/! is specified by a path to the ruleset.!?! ANALYZE/ERROR DELETE CANONICAL []!=! The parameter is a period separated list of rulesetsE! stored in a hierarchy. The name on the left of aD! period is the parent of the ruleset on the right'! side of the period.!#! For example: HEADER.DISK.RA90!<! The parameter is the optional library name.!!3 SETI<! The SETI is a hidden command to set any integer parameter.!*! ANALYZE/ERROR SETI !@! The parameter is the location where a new integer %! value is to be set.!:! The parameter is the new integer value for the! parameter.!!3 SETS;! The SETS is a hidden command to set any string parameter.!*! ANALYZE/ERROR SETI !>! The parameter is the location where a new string)! value is to be written.!8! The parameter is the new string value for the! parameter.! 3 fDIRECTORY> Returns a list of all the event or canonical rulesets known  to DECevent. DIRECTORY EVENTS DIRECTORY CANONICAL4 EVENTSB Lists all of the event rulesets that are stored in the event to $ canonical (ETC) knowledge library. DIRECTORY EVENTS 4 CANONICAL= Lists all of the canonical rulesets that are stored in the . canonical to report (CTR) knowledge library. DIRECTORY CANONICALS !4 REPORT!;! The DIRECTORY REPORT command is used to list all of theg! report rulesets.!! DIA> DIRECTORY REPORT 3 IGNORE @ Prevents the fault manager from monitoring a device or device < type. Either the /NAME or /TYPE qualifier must be present.) IGNORE [/NAME=dev-name][/TYPE=dev-type]4 /NAME /NAME=dev-name< Provides a device name for the command, where dev-name is @ a valid device name. Either the /TYPE or /NAME qualifier must be present.4 /TYPE /TYPE=dev-type> Provides a device type for the command, where dev-type is a hE valid device type. Issue SHOW TYPE to list the valid device types. 6 Either the /TYPE or /NAME qualifier must be present. 3 RECOGNIZE ? Reverses the effect of the IGNORE command, forcing the fault A manager to start monitoring a device or device type previously ? ignored. Either the /NAME or /TYPE qualifier must be present.. RECOGNIZE [/NAME= dev-name][/TYPE=dev-type]4 /NAME /NAME=dev-name< Provides a device name for the command, where dev-name is @ a valid device nam ie. Either the /TYPE or /NAME qualifier must be present.4 /TYPE /TYPE=dev-type> Provides a device type for the command, where dev-type is a E valid device type. Issue SHOW TYPE to list the valid device types. 6 Either the /TYPE or /NAME qualifier must be present. 3 REPAIR F Resets the analysis information for a repaired device, allowing the H fault manager to start fresh analysis of the device. Failure to enter D this command after repairing a device causes the fault managerj to E suppress notification of new problems or to incorrectly call out a  nonexistent fault.2 REPAIR /NAME=dev-name /DATE=time "repair-action"4 /NAME /NAME=dev-nameE Indicates the name of the device that is repaired or replaced. This qualifier is required.4 /DATE /DATE=timeF Indicates the date and time a repair action was performed. Time can A be specified as an absolute time or it can be specified by the : keywords TODAY or YESTERDAY. This qualifier is required.kF time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC) 4 repair actionA A quoted string that describes the repair action, for example, - "Replaced drive with new one. Fred Smith" 3 TESTC Tests notification functions on a system. The following are valid test commands: TEST EXTERNAL TEST MAIL TEST SICL 4 EXTERNAL C Tests a user-written external notification message. User-written E external notification messages are sent when analysis is performedl 9 or when a device crosses a customer-defined threshold.  TEST EXTERNAL destination6 destination: Can be either CUSTOMER or RESERVED.4 MAIL A Tests whether all users specified on mailing lists can receive C mail. A test message is sent to all members of a specified mail B list. If mail cannot be sent, the mail transport reports errors ( for sending mail to a particular user. TEST MAIL mail-list 5 mail-list8 The following mail lists are tested with this command: - CUSTOMER - FSE - MONITOR4 SICL? Ensures the proper installation of the System Initiated Call  Logging feature.!3 REGISTER SICL A! The REGISTER SICL command registers a system with Digital as a! site supported by SICL.ww؛«!²أ*ض}ِ  SWIP_CM DIAGNOSE