Software development, photography, jokes, ....

Sites by me

 
tas-logoTransportation Administration System
snoezelkussen-logo-kleinstSnoezelkussens voor verstandelijk gehandicapten
ikzoekeenbegeleider-logoBegeleiders voor gehandicapten
Laat uw hond het jaarlijkse vuurwerk overwinnen
logo 50x50Hey Vos! Je eigen naam@vos.net emailadres?
Kunst in huis? Nicole Karrèr maakt echt bijzonder mooie dingen
nettylogo2Kunst in huis? Netty Franssen maakt ook bijzonder mooie dingen
Salarisadministratie en belastingadvies bij De Zaak Loont
Zutphense Bomenstichting

Hosting Favorites

 
ANU Internet Services
XelMedia .internet Services
register.com

Blogroll

 
Bomenstichting
LassoSoft
MacFreak
Quality that computes
The Economy of Motion
Wheel 2.0
IntrAktv



Website Hosting bij Xel Media

Marc's Place

1 DIAGNOSE

DIAGNOSE [/interface] [/interactive] [infile [...]] [/qualifier[...]] DECevent is the interface between the system user and the operating system's event logging system. DECevent allows users to produce reports derived from system events using the following modes of operation: o /TRANSLATE Default, translates events using the system event log file if no file is specified or a specified event log file. o /BINARY Copies selected entries (for example, disk events) from one binary file to a new file. o /CONTINUOUS Specifies that events are reported as they are logged by the system. Events are viewed in real time. o /DUMP Displays event data in a side-by-side hexadecimal and ASCII byte-by-byte representation without text messages. o /ANALYZE Analyzes and isolates faults on the operating system 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 /INTERACTIVE Tells DECevent to enter the command line interface (CLI). It allows the user to start a DECevent session. It causes the DECevent prompt to be displayed, "DIA>". DIA/INTERACTIVE 2 /INTERFACE Allows the user to tell DECevent which user interface to run. The user can specify a command line interface (CLI) or a graphical user interface (GUI). DIA/INTERFACE= interface_name interface_name can be either CHARACTER_CELL or DECWINDOWS. 2 /TRANSLATE Performs bit-to-text translation of the event log specified by the infile parameter. If no file is specified, then the system default event log or the file that is explicitly set by the SET EVENT command is used. /TRANSLATE [infile [,...]] [/qualifier [,...]] infile: Name of the event log file to be used. 3 /BEFORE Selects and formats all event reports that occurred before the time specified. Time can be specified as an absolute time or it can be specified by the keywords TODAY (default) or YESTERDAY. /BEFORE [=time] time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC) 3 /BRIEF Specifies that the minimal amount of information for each selected event report should be provided. 3 /ENTRY Selects events for reporting starting with the event record specified by the keyword START and ending with the event record specified by the keyword END. If no number is specified, then all event records from the starting number to the end of the file are selected. /ENTRY=(START:start [,END:end]) start: Entry numbers end: 3 /EXCLUDE Allows users to exclude event records meeting specific criteria. The criteria can be specified as a list consisting of device name(s) and/or keyword(s). /EXCLUDE=([device-name][,...][,keyword][,...]) 4 keywords ATTENTIONS BUGCHECKS BUSES CACHE CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS MEMORY NODES OS or OPERATING_SYSTEMS PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS SYNC_COMMUNICATIONS TAPES TIMEOUTS UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES 4 device-names 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/TRANSLATE/EXCLUDE=(DKA,TAPES,MEMORY) Excludes from the report all devices that have the controller and unit designator of DKA, and also exclude from the report all TAPE and MEMORY events. 3 /FSTERR Provides a quick, one line per entry report from the event log for disk and tape devices only. 3 /INCLUDE Allows users to include event reports meeting specific criteria. The criteria can be specified as a list consisting of device name(s) and, or keyword(s). /INCLUDE=([device-name][,...][,keyword][,...]) 4 keywords ATTENTIONS BUGCHECKS BUSES CACHE CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS MEMORY NODES OS or OPERATING_SYSTEMS PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS SYNC_COMMUNICATIONS TAPES TIMEOUTS UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES 4 device-names 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 example $ DIAGNOSE/TRANSLATE/INCLUDE=(DKA,TAPES,MEMORY) Includes in the report all devices that have the controller and unit designator of DKA, and also include in the report all TAPE and MEMORY events. 3 /LOG Controls the displaying of informational messages. The informational messages, which are by default not displayed, consist of the number of event reports selected and rejected while processing a file. The default is /NOLOG. /LOG /NOLOG 3 /NODE Allows users to select event records based upon node name. If more 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 /OUTPUT Controls the output of the formatting command. The default is the standard output device (SYS$OUTPUT). /OUTPUT= output_file output_file: File specification to receive the command output. 3 /REVERSE Specifies that event records are translated in reverse chronological order, with the most recent events displayed first. The default is to display events in forward chronological order. 3 /SINCE Selects and formats all event records that occurred since the time specified. Time can be specified as an absolute time or it can be specified by the keywords TODAY (default) or YESTERDAY. /SINCE [=time] time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC) 3 /SUMMARY Produces a summary of the selected event reports. 3 /TERSE Specifies that the registers and header of each event records are formatted using the standard report format, but the contents of each register are not translated into readable messages. 3 /FULL Performs a full translation of events in the default event log file or specified input file. !3 /REPORT ! The /REPORT qualifier allows the user to choose a special report ! type when formatting event reports. ! ! /REPORT=<report_type> ! ! The <report_type> parameter is the name of a special report. ! ! 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 Examples The following are examples using /TRANSLATE mode: $ DIAGNOSE/TRANSLATE Performs bit-to-text translation using the system default event log. The Report will be displayed to screen. $ DIAGNOSE/TRANSLATE/SINCE=YESTERDAY/INCLUDE=(DISK,TAPE) ALPHA.SYS Performs bit-to-text translation using the event log file ALPHA.SYS. Include only disk and tape events that occurred since yesterday. $ DIAGNOSE/TRANSLATE/INCLUDE=(DK)/OUTPUT=DK_ERR.RPT ALPHA.SYS Performs bit-to-text translation using the event log file ALPHA.SYS. Includes only those events that are disk errors on DK device designators and write the report to the file DK_ERR.RPT. 2 /BINARY Copies event records from infile(s) that match the provided selection criteria and writes them to a binary output file. The name of the binary output file is specified as a parameter to the /BINARY qualifier. 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. infile: The name of the event log file(s) to be used. 3 /BEFORE Selects and formats all event reports that occurred before the time specified. Time can be specified as an absolute time or it can be specified by the keywords TODAY (default) or YESTERDAY. /BEFORE [=time] time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC) 3 /ENTRY Selects events for reporting starting with the event record specified by the keyword START and ending with the event record specified by the keyword END. If no number is specified, then all event records from the starting number to the end of the file are selected. /ENTRY=(START:start [,END:end]) start: Entry numbers end: 3 /EXCLUDE Allows users to exclude event records meeting specific criteria. The criteria can be specified as a list consisting of device name(s) and/or keyword(s). /EXCLUDE=([device-name][,...][,keyword][,...]) 4 keywords ATTENTIONS BUGCHECKS BUSES CACHE CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS MEMORY NODES OS or OPERATING_SYSTEMS PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS SYNC_COMMUNICATIONS TAPES TIMEOUTS UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES 4 device-names 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) Excludes from all devices that have the controller and unit designator of DKA, and also exclude all TAPE and MEMORY events. 3 /INCLUDE Allows users to include event reports meeting specific criteria. The criteria can be specified as a list consisting of device name(s) and, or keyword(s). /INCLUDE=([device-name][,...][,keyword][,...]) 4 keywords ATTENTIONS BUGCHECKS BUSES CACHE CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS MEMORY NODES OS or OPERATING_SYSTEMS PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS SYNC_COMMUNICATIONS TAPES TIMEOUTS UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES 4 device-names 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/INCLUDE=(DKA,TAPES,MEMORY) Includes all devices that have the controller and unit designator of DKA, and also include all TAPE and MEMORY events. 3 /LOG Controls the displaying of informational messages. The informational messages, which are by default not displayed, consist of the number of event reports selected and rejected while processing a file. The default is /NOLOG. /LOG /NOLOG 3 /NODE Allows users to select event records based upon node name. If more 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 /REJECTED Places all entries that failed the selection criteria for a command in a binary output file. The name of the binary output file is specified as a parameter to the /REJECTED qualifier. /REJECTED [= reject_file ] reject_file: An optional output file where the rejected event records are stored. 3 /REVERSE Specifies that event records are translated in reverse chronological order, with the most recent events displayed first. The default is to display events in forward chronological order. !3 /SID_REGISTER ! ! Specifies the value obtained from the system ID register. To ! 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 /SINCE Selects and formats all event records that occurred since the time specified. Time can be specified as an absolute time or it can be specified by the keywords TODAY (default) or YESTERDAY. /SINCE [=time] time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC) 3 Examples The following are examples using /BINARY mode: $ 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. $ DIAGNOSE/BINARY=DISK.BIN/REJECTED=REJ.BIN/INCLUDE=(DISK)/SINCE=TODAY Creates a binary file, DISK.BIN, that contains only disk errors that have been logged to the system default event log since today. Place all other events in the rejected binary file, REJ.BIN. $ DIAGNOSE/BINARY=CPU.BIN/LOG/INCLUDE=(CACHE,MC,PARITY) REJ.BIN Uses the REJ.BIN binary file and creates a binary file of all CPU type errors. 2 /CONTINUOUS Specifies that events are formatted as they are logged by the operating system event logger in real time. The output by default is displayed on the screen. Output can also be directed to a file by the /OUTPUT qualifier. /CONTINUOUS [/qualifier [,...]] 3 /BRIEF Specifies that the minimal amount of information for each selected event report should be provided. 3 /EXCLUDE Allows users to exclude event records meeting specific criteria. The criteria can be specified as a list consisting of device name(s) and/or keyword(s). /EXCLUDE=([device-name][,...][,keyword][,...]) 4 keywords ATTENTIONS BUGCHECKS BUSES CACHE CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS MEMORY NODES OS or OPERATING_SYSTEMS PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS SYNC_COMMUNICATIONS TAPES TIMEOUTS UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES 4 device-names 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/CONTINUOUS/EXCLUDE=(DKA,TAPES,MEMORY) Excludes from the report all devices that have the controller and unit designator of DKA, and also exclude from the report all TAPE and MEMORY events. 3 /FULL Performs a full translation of events in the default event log file or specified input file. 3 /FSTERR Provides a quick, one line per entry report from the event log for disk and tape devices only. 3 /INCLUDE Allows users to include event reports meeting specific criteria. The criteria can be specified as a list consisting of device name(s) and, or keyword(s). /INCLUDE=([device-name][,...][,keyword][,...]) 4 keywords ATTENTIONS BUGCHECKS BUSES CACHE CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS MEMORY NODES OS or OPERATING_SYSTEMS PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS SYNC_COMMUNICATIONS TAPES TIMEOUTS UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES 4 device-names 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 example $ DIAGNOSE/CONTINUOUS/INCLUDE=(DKA,TAPES,MEMORY) Includes in the report all devices that have the controller and unit designator of DKA, all TAPE and MEMORY events. !3 /NODE ! The /NODE qualifier allows the user to select event records based ! upon node name. If more then one node is specified the names must ! be separated by commas and enclosed in parentheses. Node names ! length must conform to current version of VMS. ! ! /NODE = (<node-name>[,...]) ! ! <node-name> is a valid node name. ! 3 /OUTPUT Controls the output of the formatting command. The default is the standard output device (SYS$OUTPUT). /OUTPUT= output_file output_file: File specification to receive the command output. !3 /REPORT ! The /REPORT qualifier allows the user to choose the special report ! type when formatting event records. ! ! /REPORT=<report_type> ! ! The <report_type> parameter is the name of a special report. ! ! FSTERR is currently the only valid special report. ! !3 /SID_REGISTER ! Specifies the value obtained from the system ID register. To ! 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 /TERSE Specifies that the registers and header of each event records are formatted using the standard report format, but the contents of each register are not translated into readable messages. 3 Examples 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 /DUMP Dumps the contents of the infile in hexadecimal and ASCII formats. /DUMP [infile] [/qualifier [,...]] infile: The name of the event log file to be used. 3 /BEFORE Selects and formats all event reports that occurred before the time specified. Time can be specified as an absolute time or it can be specified by the keywords TODAY (default) or YESTERDAY. /BEFORE [=time] time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC) 3 /ENTRY Selects events for reporting starting with the event record specified by the keyword START and ending with the event record specified by the keyword END. If no number is specified, then all event records from the starting number to the end of the file are selected. /ENTRY=(START:start [,END:end]) start: Entry numbers end: 3 /EXCLUDE Allows users to exclude event records meeting specific criteria. The criteria can be specified as a list consisting of device name(s) and/or keyword(s). /EXCLUDE=([device-name][,...][,keyword][,...]) 4 keywords ATTENTIONS BUGCHECKS BUSES CACHE CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS MEMORY NODES OS or OPERATING_SYSTEMS PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS SYNC_COMMUNICATIONS TAPES TIMEOUTS UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES 4 device-names 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/DUMP/EXCLUDE=(DKA,TAPES,MEMORY) Exclude from the report all devices that have the controller and unit designator of DKA, and also exclude from the report all TAPE and MEMORY events. 3 /INCLUDE Allows users to include event reports meeting specific criteria. The criteria can be specified as a list consisting of device name(s) and, or keyword(s). /INCLUDE=([device-name][,...][,keyword][,...]) 4 keywords ATTENTIONS BUGCHECKS BUSES CACHE CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS MEMORY NODES OS or OPERATING_SYSTEMS PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS SYNC_COMMUNICATIONS TAPES TIMEOUTS UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES 4 device-names 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 example $ DIAGNOSE/DUMP/INCLUDE=(DKA,TAPES,MEMORY) Includes in the report all devices that have the controller and unit designator of DKA, and also include in the report all TAPE and MEMORY events. 3 /LOG Controls the displaying of informational messages. The informational messages, which are by default not displayed, consist of the number of event reports selected and rejected while processing a file. The default is /NOLOG. /LOG /NOLOG 3 /NODE Allows users to select event records based upon node name. If more 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 /OUTPUT Controls the output of the formatting command. The default is the standard output device (SYS$OUTPUT). /OUTPUT= output_file output_file: File specification to receive the command output. 3 /REVERSE Specifies that event records are translated in reverse chronological order, with the most recent events displayed first. The default is to display events in forward chronological order. !3 /SID_REGISTER ! Specifies the value obtained from the system ID register. To ! 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 /SINCE Selects and formats all event records that occurred since the time specified. Time can be specified as an absolute time or it can be specified by the keywords TODAY (default) or YESTERDAY. /SINCE [=time] 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.ERROR Dumps the contents of the event file ALPHA.ERROR. $ DIAGNOSE/DUMP ALPHA.ERROR /REVERSE Dumps the contents of the event file in reverse chronological order. 2 /ANALYZE Provides the capability to either manually or automatically analyze entities on an operating system. Notification to individuals on selected mailing lists, as to the results of the analysis, is also supported. /ANALYZE [infile [,...]] [/qualifier [,...]] 3 /BEFORE Selects and formats all event reports that occurred before the time specified. Time can be specified as an absolute time or it can be specified by the keywords TODAY (default) or YESTERDAY. /BEFORE [=time] time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC) 3 /ENTRY Selects events for reporting starting with the event record specified by the keyword START and ending with the event record specified by the keyword END. If no number is specified, then all event records from the starting number to the end of the file are selected. /ENTRY=(START:start [,END:end]) start: Entry numbers end: 3 /EXCLUDE Allows users to exclude event records meeting specific criteria. The criteria can be specified as a list consisting of device name(s) and/or keyword(s). /EXCLUDE=([device-name][,...][,keyword][,...]) 4 keywords ATTENTIONS BUGCHECKS BUSES CACHE CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS MEMORY NODES OS or OPERATING_SYSTEMS PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS SYNC_COMMUNICATIONS TAPES TIMEOUTS UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES 4 device-names 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/ANALYZE/EXCLUDE=(DKA,TAPES,MEMORY) Excludes from analysis all devices that have the controller and unit designator of DKA, and also exclude from analysis all TAPE and MEMORY errors. 3 /INCLUDE Allows users to include event reports meeting specific criteria. The criteria can be specified as a list consisting of device name(s) and, or keyword(s). /INCLUDE=([device-name][,...][,keyword][,...]) 4 keywords ATTENTIONS BUGCHECKS BUSES CACHE CONFIGURATIONS CONTROL_ENTRIES CPUS DEVICE_ERRORS DEVICE_NAME DEVICE_NODE DEVICE_NUMBER DISKS ENVIRONMENTAL_ENTRIES HOSTS INFORMATIONALS IOS or IO_SUBSYSTEMS MCHKS or MACHINE_CHECKS MEMORY NODES OS or OPERATING_SYSTEMS PWR or POWER SEQUENCE_NUMBERS SWI or SOFTWARE_INFORMATIONALS SYNC_COMMUNICATIONS TAPES TIMEOUTS UNKNOWN_ENTRIES UNSOLICITED_MSCP VMS_ENTRIES VOLUME_CHANGES 4 device-names 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 example $ 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 /LOG Controls the displaying of informational messages. The informational messages, which are by default not displayed, consist of the number of event reports selected and rejected while processing a file. The default is /NOLOG. /LOG /NOLOG 3 /NODE Allows users to select event records based upon node name. If more 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 /OUTPUT Controls the output of the formatting command. The default is the standard output device (SYS$OUTPUT). /OUTPUT= output_file output_file: File specification to receive the command output. 3 /SINCE Selects and formats all event records that occurred since the time specified. Time can be specified as an absolute time or it can be specified by the keywords TODAY (default) or YESTERDAY. /SINCE [=time] time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC) 2 SHUTDOWN Halts the DECevent process on an operating system performing automatic analysis. SHUTDOWN node-name node-name: A valid VMS node name. 2 START 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] help_req: The help topic string. For example, SET provides help information on the SET command. 2 Additional_Commands A number of additional interactive commands exist. They can be executed at DIA> prompt or DCL prompt. 3 ADD Allows the users to add information to DECevent. Valid ADD commands are: ADD USER ADD EXTERNAL !4 ANALYSIS ! The ADD ANALYSIS command provides the fault manager with information, ! contained in a compiled ruleset file, required to perform analysis of ! a device type. ! ! ADD ANALYSIS file-name ! ! file-name: Is a compiled analysis ruleset. !4 NOTIFICATION ! The ADD NOTIFICATION command provides the fault manager with the ! ability to do different types of notification. This information is ! contained in a compiled ruleset. ! ! ADD NOTIFICATION file-name ! ! file-name: Is a compiled notification ruleset. 4 USER Adds a user name to one or all of the notification mailing lists. User names can be added to any of the mailing lists except the SICL mailing list which is reserved for Digital use only. ADD USER user-name [mail-list] 5 user-name Is the user name to be added to the specified mailing list. 5 mail-list Valid notification mailing lists for the ADD USER command are: - CUSTOMER - FSE - MONITOR - SICL 4 EXTERNAL Adds an entry to one external notification lists. ADD EXTERNAL entry_name list_name 5 entry_name On OpenVMS systems, is a logical name that points to a command procedure. On Digital Unix systems, is the name of a script file. 5 list_name Can be one of CUSTOMER or RESERVED. !4 CANONICAL ! The ADD CANONICAL command adds support for canonical translation ! for new device types. This enables the fault manager to translate ! event records from any device that writes information to the event ! log file. ! ! ANALYZE/ERROR ADD CANONICAL <file_name> [<library_name>] ! ! <file_name> parameter is a file containing event report ! canonical rules ! ! <library_name> parameter is an optional library name ! ! !4 SELECTION ! The ADD SELECTION command allows users to specify ! criteria for the selection of events for formatting. ! The command associates a <sel_name> with a <path> to a ! specify item for selection. ! ! ANALYZE/ERROR ADD SELECTION <sel_name> <path> <item>=<value> ! ! <sel_name> parameter is a name to associate with the ! selection path ! ! <path> parameter is a path to a selection field of an event ! ! <item> is the name of data item in the ruleset to use while ! 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 <file_name> [<library_name>] ! ! <file_name> parameter is a file containing event report ! translation rules ! ! <library_name> parameter is an optional library name ! 3 REMOVE 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: ! 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 ! ! ruleset: A valid path name to a ruleset. !4 NOTIFICATION ! The REMOVE NOTIFICATION command removes notification knowledge ! about a specific device. ! ! REMOVE NOTIFICATION ruleset ! ! ruleset: A valid path name to a ruleset. 4 REPAIRED Removes repair information entered by a service engineer for a specific device. This allows the repair database to be trimmed, enhancing the usability of the information. Repair entries deleted from the database are no longer available to the fault manager and cannot be recovered. REMOVE REPAIRED dev-name dev-name: A valid device name. 4 SYSTEM_INFO Removes information about a system under the fault manager's domain. REMOVE SYSTEM_INFO node-name node-name: A valid node name. 4 USER Removes a user name from one or more of the notification mailing lists. A valid user name must be specified. If no mailing list is specified then the specified user name will be removed from all of 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-list Valid notification mailing lists for the REMOVE USER command are: - CUSTOMER - FSE - MONITOR - SICL 3 FLUSH Clears out saved event information for a particular device. FLUSH dev-name dev-name: Is a valid device name. 3 SHOW Displays information about 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 SHOW SICL SHOW THRESHOLD SHOW REPAIRED SHOW SETTINGS SHOW SUMMARY SHOW TYPES 4 EXTERNAL Displays the contents of the external notification lists. If a list_name isn't provided, the contents of all external lists is shown. SHOW EXTERNAL list_name 5 list_name Can be one of CUSTOMER or RESERVED. 4 KNL 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 files to allow knowledge files to be distributed separatly. The report format is: Knowledge File Version Information File name Version Build Date Platform =================================================================== 4 MAILING_LIST Displays accounts that receive mail when different types of 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 - SICL 4 PARAMETERS Displays all settings related to notification. Valid show parameters are as follows: - The telephone number for Digital Services (SET PHONE) - The serial number of each registered system (SET SYSTEM_INFO) - The type of each registered system (SET SYSTEM_INFO) - 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. Information is displayed using the following format: Device Time Of Repair Comment ======= ================= ================== dev-nm dd-mmm-yyyy:hh:mm Engineer's comment SHOW REPAIRED [dev-name] dev-name: Specifies the name of a valid device. 4 SETTINGS Displays the current status of an individual settings parameter. If the setting parameter is omitted, then all setting parameters are displayed. SHOW SETTINGS [setting] setting: The name of parameter to be displayed. 4 SELECT Used to show the selections defined by the user. Each selection is shown as a selection name and selection path pair, for example, 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 Displays the current state of SICL (System Initiated Call Logging). 4 SUMMARY Displays a list of all devices that have crossed their assigned notification threshold. SHOW SUMMARY The output has the following format: Device Class State Count Time ====== ===== ===== ===== ==== dev-nm class curr-state err-cnt time-occured 4 THEORY Displays a list of all devices that have indicated faults. SHOW THEORY The output of this command has the following format: Device Theory Time Reported ====== ======== =============== dev-nm the-nm date-time 4 THRESHOLD Displays current threshold values for a specific device or device type. Threshold values determine when analysis and notification occur. If no qualifiers are present, SHOW THRESHOLD will list thresholds for all devices and device types. Output from this command has the following format: ---Hard--- ---Soft--- ---Info--- ---Media--- Device Cnt DSE Cus Cnt DSE Cus Cnt DSE Cus Cnt DSE Cus ================================================================= device cnt DSE Cus Cnt DSE Cus Cnt DSE Cus Cnt DSE Cus SHOW THRESHOLD [/NAME=dev-name][/TYPE=dev-type] 5 /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. 5 /TYPE /TYPE=dev-type The /TYPE qualifier provides a device type for the command, where dev-type is a valid device type. Issue SHOW TYPES to 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 subsystems for the SHOW TYPES command: - CPU - IOS 3 SET Allows users to customize system settings. All SET commands must be executed from the interactive command shell. The following are valid set commands: SET DEFAULT REPORT SET LOCALE SET EVENT SET PHONE_NUMBER SET SICL SET SYSTEM_INFO SET THRESHOLD !4 COMMAND ! Allows users to customize the style of the keyboard user interface ! used to enter commands. Individual users may set the keyboard user ! 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 REPORT Sets the default report used during translation. The report is specified by giving a path name of a report generation ruleset. SET DEFAULT REPORT rule_name rule_name: Name of ruleset. For example, TRANSLATION.DEFAULT_REPORT 4 EVENT Allows users to select an event log file from which event reports are formatted. This allows a user, in the interactive command shell, 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 file_name: Name of an event log to be used for formatting report. 4 LOCALE Allows users to override the locale file previously set for the current system. This is done for internationalization reasons so that natural language conventions can be added in the future. SET LOCALE location location: String defining the location of the user in terms of the locale preferences available, for example, AMERICAN_ENGLISH. ! ! NOTE: ! When adding these command make sure that "3 ADD" gets updated ! 4 PHONE_NUMBER The SET PHONE_NUMBER command sets the phone number of the Customer Support Center for a particular customer site, allowing the customer notification mail message to provide the customer with the correct number to call for service. Change the phone number in interactive mode. Once changed, 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-number phone-number: Is the valid CSC phone number. 4 SICL 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 Provides information to the fault manager about a system under its domain. 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-name The valid VMS node-name of the system. This qualifier is required. 5 system type A required parameter that is a quoted string that describes the system, for example, "DEC 4000" 4 THRESHOLD Alters threshold triggering for monitored devices. Thresholds can be entered either by device name or by device type. SET THRESHOLD - [/NAME=dev-name][/TYPE=dev-type]/CLASS=severity[/DSE][/CUSTOMER] count 5 /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. 5 /TYPE /TYPE=dev-type Provides a device type for the command, where dev-type is a valid device type. Issue SHOW TYPES to list the valid device types. 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 data) - SOFT (A device that may have recovered data) - INFO (Indicates informational events on a device) - MEDIA (Indicates events related to storage media) 5 /DSE Performed analysis when a device crosses this threshold. When thresholds are crossed, the external notification procedures are invoked. Thresholds are set for different severity levels of events. Either the /DSE or /CUSTOMER qualifier must be present. 5 /CUSTOMER Notifies the customer when a device crosses this threshold. When thresholds are crossed, the external notification procedures are invoked. Thresholds are set for different severity levels of events. Either the /DSE or /CUSTOMER qualifier must be present. 5 count 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 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 the last customization file was saved. This command does not make sense when the fault manager is passed a command from the operating system command line. For this reason it is only supported in the interactive command shell. RESTORE SETTINGS 4 SYSTEM SETTING Allows users to cancel customizations previously set and saved in 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 ! The DELETE TRANSLATION command DELETEs a translation ruleset. ! The result of this is that the fault manager will no longer be ! able to translate events that required that ruleset to be ! translated. The ruleset to be DELETEd from the fault manager ! is specified by a path to the ruleset. ! ! ANALYZE/ERROR DELETE TRANSLATION <path> [<library_name>] ! ! The <path> parameter is a period separated list of rulesets ! stored in a hierarchy. The name on the left of a ! period is the parent of the ruleset on the right ! side of the period. ! ! For example: HEADER.DISK.RA90 ! ! The <library_name> parameter is the optional library name. ! !4 CANONICAL ! The DELETE CANONICAL command DELETEs a canonical ruleset. The ! result of this is that the fault manager will no longer be ! able to translate events that required that ruleset to be ! translated. The ruleset to be DELETEd from the fault manager ! is specified by a path to the ruleset. ! ! ANALYZE/ERROR DELETE CANONICAL <path> [<library_name>] ! ! The <path> parameter is a period separated list of rulesets ! stored in a hierarchy. The name on the left of a ! period is the parent of the ruleset on the right ! side of the period. ! ! For example: HEADER.DISK.RA90 ! ! The <library_name> parameter is the optional library name. ! !3 SETI ! The SETI is a hidden command to set any integer parameter. ! ! ANALYZE/ERROR SETI <parameter> <integer> ! ! The <parameter> parameter is the location where a new integer ! value is to be set. ! ! The <integer> 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 <parameter> <string> ! ! The <parameter> parameter is the location where a new string ! value is to be written. ! ! The <string> parameter is the new string value for the ! parameter. ! 3 DIRECTORY Returns a list of all the event or canonical rulesets known to DECevent. DIRECTORY EVENTS DIRECTORY CANONICAL 4 EVENTS 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 the ! 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 valid device type. Issue SHOW TYPE to list the valid device types. Either the /TYPE or /NAME qualifier must be present. 3 RECOGNIZE Reverses the effect of the IGNORE command, forcing the fault 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 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 valid device type. Issue SHOW TYPE to list the valid device types. Either the /TYPE or /NAME qualifier must be present. 3 REPAIR Resets the analysis information for a repaired device, allowing the fault manager to start fresh analysis of the device. Failure to enter this command after repairing a device causes the fault manager to suppress notification of new problems or to incorrectly call out a nonexistent fault. REPAIR /NAME=dev-name /DATE=time "repair-action" 4 /NAME /NAME=dev-name Indicates the name of the device that is repaired or replaced. This qualifier is required. 4 /DATE /DATE=time Indicates the date and time a repair action was performed. Time can be specified as an absolute time or it can be specified by the keywords TODAY or YESTERDAY. This qualifier is required. time: (DD-MMM-YYYY:HH:MM:SS.CC) or (DD-MMM-YYYY HH:MM:SS.CC) 4 repair action A quoted string that describes the repair action, for example, "Replaced drive with new one. Fred Smith" 3 TEST Tests notification functions on a system. The following are valid test commands: TEST EXTERNAL TEST MAIL TEST SICL 4 EXTERNAL Tests a user-written external notification message. User-written external notification messages are sent when analysis is performed or when a device crosses a customer-defined threshold. TEST EXTERNAL destination destination: Can be either CUSTOMER or RESERVED. 4 MAIL Tests whether all users specified on mailing lists can receive mail. A test message is sent to all members of a specified mail list. If mail cannot be sent, the mail transport reports errors for sending mail to a particular user. TEST MAIL mail-list 5 mail-list The following mail lists are tested with this command: - CUSTOMER - FSE - MONITOR 4 SICL Ensures the proper installation of the System Initiated Call Logging feature. !3 REGISTER SICL ! The REGISTER SICL command registers a system with Digital as a ! site supported by SICL.

© 1997- Marc Vos (and others) Contact Me