5.6.2 Manual Analysis
Manual analysis is the user-initiated process of selecting a binary event log file for immediate processing using either the CLI command or the web interface (see Chapter 7).
The wsea ana command performs manual analysis as well as filtered manual analysis on a binary event log file, which can be the system event log, another log from the same system, or a log from a different system:
wsea ana [input inputfile] [out | outhtml outputfile] [notify [OS | CUSTOMER | PROVIDER | WUI | CLI | AUI | VISIBLE | EVERY]]Filtered Manual Analysis—It is possible to create a tailored log file using filters (see Section 5.9 Creating New Binary Event Log Files) and then manually analyze the new file; however, be aware that this can result in incomplete or invalid analysis due to missing data that was filtered out.
To perform manual analysis with another syntax, see Appendix E.
By default, manual analysis processes the system event log. If you want to process a different binary log file, you must use the input keyword and specify the input file. See Section 5.10.1 for more information on input files.
Notification options are defined as follows:
- OS - Operating System ("Indictment").
As of the current release of WEBES, only Alpha operating systems (OpenVMS Alpha) recognize indictments.- CUSTOMER - Customer email, pager, etc., as set up during installation.
As of the current release of WEBES, SNMP (HP SIM), DTCS, MOM, SMTP notification is included in this type of notification.- PROVIDER - Service provider's support organization set up during WEBES installation.
As of the current release of WEBES, the provider notification types include ISEE, OSEM (formerly PRS CSG/QSAP now retired), SNMP (HP SIM), DTCS, MOM, VMSMAIL and SICL/ACHS/DSNlink (now retired) only. The notification types that are enabled for automatic analysis are the ones that will be used for notification if this channel is specified.- WUI - Web User Interface (browser).
- CLI - Command Line Interface (user's console - the default if the notify command is not used).
- AUI - All User Interfaces (WUI and CLI).
- VISIBLE - All visible notification channels, that is, every channel except OS.
- EVERY - All notification channels.
If "notify" is used, one and only one of the above options must be used immediately after it on the command line.
Notification options may be abbreviated to uniqueness. For example, "O" may be used instead of "OS"; "CU" may be used instead of "CUSTOMER" etc.,
Notification and analysis mode information is now displayed in all problem reports. See Appendix A.1 for a sample problem report. The information is positioned above the SEA and WCC Version sections of the report.
The command line options correspond to the notification information on the problem report as follows:
- OS - OS
- CUSTOMER - Customer
- PROVIDER - Support
- WUI - Browser
- CLI - Console
- AUI - AllUserInterfaces
- VISIBLE - Visible
- EVERY - All
For the CUSTOMER, PROVIDER, VISIBLE, and EVERY flags, a problem report will ONLY be sent to the customer or provider notification types (SMTP, ISEE, QSAP (PRS), and SICL (DSNlink)) that are enabled for automatic analysis. In other words, if the customer has enabled SMTP and ISEE notification, but not QSAP or SICL notification, then CUSTOMER sends notification to SMTP only, PROVIDER sends notification to ISEE only, and VISIBLE and EVERY sends both SMTP and ISEE notifications (among other types of notifications). If the user disables SMTP notifications with the "desta smtp off" command, then the CUSTOMER option will have no effect, and email will not be sent using the VISIBLE or EVERY options either. If the user has no provider notifications enabled (ISEE, QSAP, or SICL), then the PROVIDER option will have no effect, and HP Services will not be notified using the VISIBLE or EVERY options either.
For more information on notifications, see Chapter 11 Automatic Notifications. For commands on how to enable/disable notifications, see Section 3.10 Automatic Notifications.
By default, output from manual analysis is displayed on the screen. To save output to a file, use either the out or the outhtml keyword and provide a file name. See Section 5.10.2 for more information on output files.