HP Archive Backup System for OpenVMS Guide to Operations

HP Archive Backup System for OpenVMS Guide to Operations HP Archive Backup System for OpenVMS Guide to Operations

h71000.www7.hp.com
from h71000.www7.hp.com More from this publisher
06.11.2014 Views

User Interfaces 6.1 Graphical User Interface Once the results screen is displayed, you can sort the report using any field by clicking on the field’s header. You can reverse-sort the same field by clicking on the field header again. Figure 6–9 Report View Selection Criteria Example Figure 6–10 Report View Results Screen 6-12 User Interfaces

6.1.13 Viewing MDMS Audit and Event Logging 6.1.14 Errors User Interfaces 6.1 Graphical User Interface To examine past operations in MDMS, you can use the event view to view the MDMS audit and event logfile. There are five pre-configured options and a fully flexible custom option to allow you to select what you wish to see from the MDMS logfile. The five pre-configured options all apply to the MDMS Database Server logfile and show all operations (auditing and events) for the following amounts of time before the current time: • The last minute • The last 10 minutes • The last hour • The last 24 hours • The last 72 hours If you wish to see the logfile using other selection criteria, you can use the “Custom” setting. By clicking on “Custom”, a selection screen appears that allows you to select the entries to be displayed as follows: • Node selection: You can choose the default of the DB server (which contains the most complete information), or select a specific client node. Note that request IDs are not supported on client nodes, and nor is selection by low and high request IDs. • Selection Options: You can select a range of entries in the logfile to display by one of: – Elapsed time in minutes (default of 60 minutes) -OR- – Before and/or since dates (specified as an absolute time) -OR- – Low and high request IDs (for DB server only) • Severity Options: For audit completion entries, you can select that only entries of a certain combinations of completion status are displayed. You can select one or more of: – Success (S) – Informational (I) – Warning (W) – Error (E) – Fatal (F) After entering the selection criteria, you click on the Show button to display. Depending on the size of the log file, this operation may take several seconds to complete. You may want to regularly reset your log files to avoid long response times. The code has been written to scan previous versions of log files if the date and or request selections are not in the latest log file. The Refresh button at the bottom of the screen refreshes whatever selection is currently on the screen. The Cancel button allows you to enter a new selection. MDMSView can report two types of errors: • Those generated by MDMSView itself: these typically appear in a dialog box and in the status bar at the bottom of the screen. These errors normally explain an illegal user operation. • Those generated by the MDMS server on the log-in node. These errors appear in a dialog box with the standard MDMS DCL syntax. These errors are documented in the MDMS Reference Guide. User Interfaces 6–13

6.1.13 Viewing MDMS Audit and Event Logging<br />

6.1.14 Errors<br />

User Interfaces<br />

6.1 Graphical User Interface<br />

To examine past operations in MDMS, you can use the event view <strong>to</strong> view the MDMS audit and<br />

event logfile. There are five pre-configured options and a fully flexible cus<strong>to</strong>m option <strong>to</strong> allow<br />

you <strong>to</strong> select what you wish <strong>to</strong> see from the MDMS logfile. The five pre-configured options all<br />

apply <strong>to</strong> the MDMS Database Server logfile and show all operations (auditing and events) <strong>for</strong><br />

the following amounts of time be<strong>for</strong>e the current time:<br />

• The last minute<br />

• The last 10 minutes<br />

• The last hour<br />

• The last 24 hours<br />

• The last 72 hours<br />

If you wish <strong>to</strong> see the logfile using other selection criteria, you can use the “Cus<strong>to</strong>m” setting. By<br />

clicking on “Cus<strong>to</strong>m”, a selection screen appears that allows you <strong>to</strong> select the entries <strong>to</strong> be displayed<br />

as follows:<br />

• Node selection: You can choose the default of the DB server (which contains the most complete<br />

in<strong>for</strong>mation), or select a specific client node. Note that request IDs are not supported<br />

on client nodes, and nor is selection by low and high request IDs.<br />

• Selection Options: You can select a range of entries in the logfile <strong>to</strong> display by one of:<br />

– Elapsed time in minutes (default of 60 minutes) -OR-<br />

– Be<strong>for</strong>e and/or since dates (specified as an absolute time) -OR-<br />

– Low and high request IDs (<strong>for</strong> DB server only)<br />

• Severity Options: For audit completion entries, you can select that only entries of a certain<br />

combinations of completion status are displayed. You can select one or more of:<br />

– Success (S)<br />

– In<strong>for</strong>mational (I)<br />

– Warning (W)<br />

– Error (E)<br />

– Fatal (F)<br />

After entering the selection criteria, you click on the Show but<strong>to</strong>n <strong>to</strong> display. Depending on the<br />

size of the log file, this operation may take several seconds <strong>to</strong> complete. You may want <strong>to</strong> regularly<br />

reset your log files <strong>to</strong> avoid long response times. The code has been written <strong>to</strong> scan previous<br />

versions of log files if the date and or request selections are not in the latest log file.<br />

The Refresh but<strong>to</strong>n at the bot<strong>to</strong>m of the screen refreshes whatever selection is currently on the<br />

screen. The Cancel but<strong>to</strong>n allows you <strong>to</strong> enter a new selection.<br />

MDMSView can report two types of errors:<br />

• Those generated by MDMSView itself: these typically appear in a dialog box and in the status<br />

bar at the bot<strong>to</strong>m of the screen. These errors normally explain an illegal user operation.<br />

• Those generated by the MDMS server on the log-in node. These errors appear in a dialog<br />

box with the standard MDMS DCL syntax. These errors are documented in the MDMS Reference<br />

<strong>Guide</strong>.<br />

User Interfaces 6–13

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!