Remote Analyst

Remote Analyst is all about NonStop analytics in the Cloud (public or private), and off platform.  Its objective is to:

• Detect issues before they become a problem and affect your business
• Assist you with quick investigative work should you need to resolve a concern
• Help you plan for growth, and to ensure you have enough computing resources
• Improve your productivity

Remote Analyst uses a simple architecture:  https://vimeo.com/207817954 .

Performance and availability metrics are continuously collected on NonStop Servers and securely forwarded at regular intervals to an automated cloud platform.  This may be a secure public cloud, or one internal to your company.

Once at Remote Analyst, data is populated into various database Tables and types.  As applicable, analytics start immediately for RA to look for trends and exceptions.

This all happens with no human intervention and at speeds required to meet your computing and business demands.

You may also securely connect to Remote Analyst from any device, and with ease, drill down through mountains of data, or schedule analyses to be emailed automatically to you and your colleagues.

Trailing topics here cover every aspect of your online experience.  Write us at support@remoteanalyst.com if we may be of further assistance.

Remote Analyst has two classes of users:

• Admin – Has access to metrics for all Servers and may add other users (Admin or Staff), and set certain general criteria (defined below).
• Staff – May access only Servers previously authorized by an Admin user. Certain other restrictions may also apply.

General screen format is as follows:

• Top toolbar – Allows one click access to certain features which are always available. Available icons are:
  • RA Shop – Opens a dialogue where you can setup application or other metrics to be displayed on Web ViewPoint Enterprise (a separate product). See RA Shop later in this document for more details.
  • Scanners – Open windows to scan Files, Processes, and Programs.  See Scanners on description of how each works.
  • Download Data from archives – Select days from past to import back into Remote Analyst database. A Calendar is displayed showing the number of hours per day for which data is available in Archives.  Select a From and To date & time, and submit a request.  You will receive an email when retrieval is completed.
  • Upload Collected Data – Upload Measure or EMS Log files to Remote Analyst. A popup display offers the following options:
    • Measure File(s)– Upload Measure files. You may upload in original or PAKed (compressed using PAK on NonStop).  Check the “Multi Archived” option, if you PAKed on NonStop using this option.
    • EMS Log file(s) – Upload EMS log files. Only PAKed files are accepted.   Check the “Multi Archived” option, if you PAKed on NonStop using this option.

Drag and drop your files on to the highlighted area.  They will each start uploading as soon as your drop them there.

• Excel – Export (available where applicable) current screen content to a new Excel workbook.
• My Profile – Review your user profile data, and:
  • Change your password – Click on the displayed yellow icon
  • Multi Server – If you have more than one NonStop Server on RA, here you can decide if you want the Multi-Server screen be displayed first, which Servers should be included, and whether they should be displayed 1 or 2 across.
  • Order of Servers on left panel – Select the order (top to bottom) of the Servers on the left panel. Click and hold the icon next to the Server name, and push it up or down to the desired location.

Click Save to save your updated profile.

• Help – Access online Help.
• Support – Contact RA support, review release history, or download the latest collector.
• Logoff – Terminate the current session.

• Your company’s logo – Your company’s logo is displayed above the list of Servers on the left panel. Click on the logo to see your Servers’ performance (all or selected – See “My Profile” above, in one screen.  Functions on each Server’s graphic are similar to how they operate individually off the tree.  However, note that:
  • Selections on the top toolbar (e.g. Date, forward/backward, Entity selection) apply to all displayed Servers.
  • You may still click on any graph point to “Drill down” to more detail data for the selected Server at the selected time.
  • You may click on the Duplicate/Open icon on each graph (placed on the upper right) to open a new Window in a full-display format, where that Server is opened.
• Left Panel – It has your company’s logo on top, and one entry for each of your HPE NonStop Servers licensed for Remote Analyst. Click on each Server to open its submenus:
  • Review – Browse through performance metrics, with links to related objects, and their metrics, and history. For instance, you may go from a CPU to a Process, to Files it opened, to other processes which opened those files, to history of each those processes, …. Following Entities are available for review
    • System
      • CPU
      • IPU
      • Process
      • Disk
    • Network
      • TCP
      • IPV6
      • SLSA
      • Expand
    • Applications – CPU Busy vs. Disk IO
    • Pathways – CPU Busy vs. Server transactions
    • User Defined Counters – Generic format cover all Measure User Defined metrics you may have defined on your Server.
    • Transactions – Transaction count and associated CPU usage of your applications.
    • Exceptions – Activities for CPU, IPU, Disk, or Storage where RA has noticed an exception from the normal activities for the given hours and days. Navigation and links are self-explanatory.
    • Batch – Review Batch sequence activities for predefined Batch Sequence profiles. See Batch for more details.
  • Analyze – Enables you to generate any of the available analyses on demand or browse through archives of those generated earlier.
  • Admin – This includes a set of Administrative tasks, which are tailored to your specific user class:
    • Analysts – Admin user only – Select Analysts from previously authorized company to access your Servers’ info on RA.
    • Applications – Admin user only – Define criteria for applications running on your Servers.
    • Batch – Admin user only. Define profile for daily Batch runs.
    • Capacity Profile – Admin user only – Define transaction profiles of your applications.
    • Process Watch – Admin user only – Define automated Process monitoring requirements.
    • Program – Program profiles to be used for program/process monitoring reports.
    • Users – Admin user only – Add/maintain user profiles.
    • Workdays – Admin user only – Set your workdays, hours, and exceptions.
  • Right Panel – Has various content depending of the submenu selected on the left panel. This is described in detail in the following segments.

This section is about reviewing past metrics, and where applicable, link to related information.  Except for Transactions, which are described separately, metrics are displayed on the right panel, using a graph/grid combination.  Here are the important things to know:

• Display starts with the last 24 hours of metrics.
• Graph
  • Uses two Y axis. You control what each axis should show.
  • Graph title shows the time period covered by the graph.
  • There are two icons, one on the top right, and another on the top left part of the graph. Click to show or hide the content for each axis.
  • Click on ‘Show average’, available on the top left, to view the ‘Peak values’ and ‘CPU average’ for the period of time displayed.
  • You may click on an item on the legend displayed below the graph, to show/hide graph line/bar associated with that legend item.
• Below are functions of items displayed on the Toolbar above the graph.
  • Entity & Metric selection boxes – There are two, one on the left, and another on the right side. Click open to see the list of available Entities, displayed on the top.  Click on an Entity to see a list of available Counters.  Click on a counter, and then on the Submit Button.  This displays the specific metric for the Y axis associated with the box (Left for Y1, Right for Y2).  Click on the up-arrow next to the list box to close it.
  • Graph icons are displayed next to each list box.  They represent bar and line graph types.  Click them to switch the displayed graph content associated with that Y axis from one type to another.
  • Click the “Prev” or “Next” Buttons to move to previous or next time period, for the period of time displayed. When you first access a section of Review, data is displayed for the last 24 hours. A click on the “Prev” shows metrics since the beginning of the current day. Second click and after moves the content back one day (if content displayed is for one day) at a time.
  • Click on the Calendar to see the list of available days for which data is available. Select a day, and whether you want to see information for a day, or a week (Sunday through Friday), or a month (full month from day 1 to end of the month or current day for current month).  Click on submit to display metrics for the selected period.  Note that displayed resolution is at interval (as collected on your server), when you select a 24-hour period, and hourly resolution, when you select weekly or monthly.
  • Click on the time controls to set the hours of the day. Default is the full 24 hours.  You may set it to a narrower window of time to focus on a shorter daily span of time.  This option affects display for daily, weekly, and monthly views.
• For all System Metrics, you may click on the graph to display in a new Window, detail/history for the selected item. That window in turn has links to other related metrics and objects.  This opens a near-endless series of data, enabling you to quickly review both cause and symptoms associated with any metric.
• Of course, clicking on the Excel icon on the toolbar saves all metrics displayed on your screen in a new Excel workbook and downloads the file to your device.

System Review covers essential Measure metrics. See here on how to navigate the screen.

Entities & Counters available are:

• CPU
  • Busy – % CPU busy; this is the average of % Busy of all IPUs per CPU
  • Queue – Queue length
  • Memory – GB memory used
  • DP2 – % of CPU busy used by DP2/Disk processes
• IPU
  • Busy – % IPU busy
  • Queue – Queue length
• Process
  • Busy – % Busy of busiest Process per CPU
  • Memory – highest memory consumer Process per CPU
  • Trans
• Disk
  • IO – Total Disk IO, and the Disk with the highest IO, both per second
  • Queue – Total Queue length of all Disks, and the disk with the highest Queue
  • Cache – Average Cache hit rate of all Disks, and the disk with the lowest rate
  • DP2 – Average DP2 busy of all Disks, and the disk with the highest DP2 Busy

Metrics are displayed per collected interval, at 24-hour scope, and hourly at weekly and monthly scopes.

In many instances, monthly and weekly scopes offer the option to choose from average or peak values.  Note that while this screen is kept open, and display scope is at interval level, its content is automatically updated every 5 minutes.

Any of the displayed items on the graph may be clicked to link to more details and related content.

Network Review covers essential network metrics, collected via interface to NonStop’s SCF (Subsystem Control Facility). See here on how to navigate the screen.

Available objects and metrics are:

• TCP
  • Process – Total (Sent + Received) bytes per second, per TCPIP Process
  • Subnet – Total (Sent + Received) Packets per second, per TCPIP Process
• IPV6
  • Process – Total (Sent + Received) bytes per second, per TCPIP V6 Process
  • Subnet – Total (Sent + Received) Packets per second, per TCPIP V6 Process
• PIF – Total (Sent + Received) octets per second, per physical interface.
• Expand
  • Transmit – Transmit rate, per Expand path (logical connection between two adjacent nodes, can consist of multiple lines)
  • Retransmit – Retransmit rate, per Expand path

Application Review shows % CPU busy and rated Disk IO for all predefined applications.  Activity is summed for all processes belonging to each application.  Process to Application assignment is based on how the application was defined earlier.

Metrics are displayed per collected interval, at 24-hour scope, and hourly at weekly and monthly scopes.  Where applicable, you may switch between Peak or Average values, by clicking on the Button displayed next to the list box on either side.

Click on a CPU graph line for an application to see a list of Processes, and their CPU Busy, of that specific application for the time you clicked on.  As with other Process lists, you have click access to other relevant information.

Click on a Disk bar to see a history of that Disk’s IO activity over time.  For the specific time you selected (on click), a list of files on that Disk showing IO rates and number of processes of which had it open.  Click on a File name to see its history and openers at that time.  Click on the opener count to see a list of all processes which had that file opened, including those from the selected application.

See here on how to navigate the screen.

Pathways Review shows % CPU busy and rated Server transaction, per Pathway environments.  % CPU busy is derived from sum of all Processes (Pathmon, TCPs, Server Processes), and transactions are obtained from Server Linkmon statistics.

See here on how to navigate the screen.

Metrics are displayed per collected interval, at 24-hour scope, and hourly at weekly and monthly scopes.  Where applicable, you may switch between Peak or Average values, by clicking on the Button displayed next to the list box on either side.

User Defined Counters shows metrics collected by Measure, for specific “User Defined Counters” your applications recorded.

See here on how to navigate the screen, but note the following exceptions:

• Only interval level information is available
• There are no Entity/Counter selections. Instead you choose from the list of your Defined Counters, displayed on the list boxes on either side.
• Processes reporting metrics (User Defined Counters) to Measure are listed below the graph. Click on any Process to see its details and trend/history.

This is where you can compare transaction activities of your various applications.  It is based on Application Profiles you define in Capacity Model.  Here you can select one or more Profiles, and review their recorded transaction rate, vs. % CPU Busy.  Transaction rates are calculated based on how the Profile was earlier defined.  In general, it measures IO rates against one or more files, and calculates CPU resources used associated with those transactions.

Parameters displayed on the right panel allow you to control what should be displayed:

• From Date & Scope – Date to start, and period to show
• CPU Display – Whether % CPU busy should be displayed, and if so, how
• Weekdays – Which weekdays should be included
• Hours – Select which hours of each day should be included in the display. Choices are:
  • All – all hours
  • Peak CPU Busy – Only the hour where average CPU Busy of all CPUs reached its peak
  • Peak TPS Rate – Only the hour where transaction rate (of selected profiles) reached its peak
  • Only – select specific hours
• Profiles – Select one or more of predefined Application Profiles
• Show business transactions as a percent of total – This enables you to separate what you consider to be business transactions from overall transaction rates.

Click on Submit to see the transaction trend based on your selection criteria.

From there you can access CPU & Process Scanners or export the displayed content to Excel.

You can also click on the CPU Busy graph to open a new window showing you details on that exact point in time.

This is where you can see system activities which were outside the norm. 

Over time, Remote Analyst learns about your system’s behavior.  It knows what should be expected for different times of different days & weekdays.  It also takes to consideration, your specific instructions for different weekdays, hours, and how sensitive it should be.  For more on this, see Admin – Workdays.

Exceptions are shown for CPU, IPU, and Disk activities, as well as Disk storage levels.

For each, Remote Analyst displays the hour of the day when an exception occurred, what was expected, and what the actual value was.  Color coding, yellow and red (minor and major), signify how far off expectation they were.  This is based on the value you set for that Server in Thresholds of Admin – Workdays. You have customized the sensitivity factors, for different categories (business, batch, other).  What this means, is that Remote Analyst not only looks at System’s behavior, but also pays attention to your custom settings, before it identifies activity levels as exceptions, norm, or within expectations.

Date controls on the toolbar allow you to check for expectations on different days.

Each Exception note also comes with a hyperlink to more detail!

TBD.

In this section you can generate new Analyses to be emailed to you and others.  You may also review status and list of those generated earlier and download any of them to your device.

Here is where you can request Analyses to be emailed to you and others.  To see a list of all available Metrics, per day and interval, click on the calendar icon on top right.  A new window shows each day of the month for the current year, and number of hours for which metrics are available.  A list of tabs on top allow you quick access to each type of report to view available data.

Available Analyses  are:

This is the most detail analyses of your system activities offered by Remote Analyst.  It includes over 90 different charts and reports.  Below are the selection criteria:

• From & To: Date and time period the analyses should cover
• Email to: List of people who should receive the analyses
• Audit Volumes: List of volumes used for TMF activities. By default, RA preselects all volumes with “AUDIT” in their name
• Allow: If a Measurement is started when Processes are already running, and their files are already open, MEASURE may record the DISCOPEN or FILE entities BEFORE recording the PROCESS entities; this effect can be significant on a busy system with many entities under measurement. This parameter allows one to specify by how many seconds a DISCOPEN or FILE entity recording can precede its opening PROCESS entity recording, in order to allow it still to be matched to its opening PROCESS.

Too small a value may result in DISCOPENs or FILEs not being matched to their opening Processes; too large a value may result in DISCOPENs or FILEs being matched to the wrong PROCESS if there is significant transient processing and Process IDs (s) are “re-used”.

Values range from 0.00 to 99.99 seconds; the default value is 5 seconds.

Example: ALLOW 15

• Exclude: Several charts and reports exclude “low-activity” entities from their output, in order to minimize the amount of data presented; this parameter lets the user set the exclusion threshold. The “unit of measure” varies from report to report, but it is typically a percentage utilization (e.g. CPU Busy), a percentage of some global total (e.g. of total logical disc file I/O’s), or a rate of events per second (e.g. logical I/O’s per second). Reports exclude entities whose activity is below (less than) the threshold. Each report shows its EXCLUDE value and “unit of measure” at the bottom of every page.

Values range from 0.00 to 99.99; the default is 0.1.

Example: EXCLUDE 0.01

• Flag: Some reports flag “transient” entities with an asterisk. Examples of transient entities include: processes that lived for less than the report “window”, and files that were open for less than the opening process’s life. This parameter allows the user to specify the percentage of the window or life for which the entity must have existed before it is considered “transient”; the entity is flagged if it lived for less than this percentage of the window or opening process’s life.

Values range from 1 to 99 percent; the default value is 90 percent.

Example: FLAG 95

• IO Factor: Some reports attempt to apportion Disk Process CPU time to the files/partitions accessed, or to the programs accessing the files/partitions.

This parameter specifies how much more CPU-costly a Physical I/O (Driver Call Minus Cache Hit) is than a Cache Hit. Values range from 0.0 to 99.9; the default value is 2.0.

Example: IOFACTOR 2.5″;

• Msgs: The “Program Overview” chart and the “Application Program Profiles” report show program resource consumptions and wait times per “unit of measurement”. One MESSAGE RECEIVED is often a good unit of measurement for “server” processes.

Other processes (e.g. batch processes), however, may receive only process-creation messages such as the STARTUP message, a PARAM message and one or more ASSIGN messages. A MESSAGE RECEIVED is not usually an appropriate unit of measurement for such processes.

MINMSGS allows the user to specify the minimum number of messages a process must receive in order for “Program Overview” and “Application Program Profiles” to show program resource consumptions and wait times PER MESSAGE RECEIVED. If the average number of messages received by processes run from a given program file is below MINMSGS, “Program Overview” and “Application Program Profiles” will instead show program resource consumptions and wait times PER SECOND of the average “lifetime” of one of these processes.

Values range from 1 to 9999; the default value is 10.

Example: MINMSGS 15

• Needle: The “Low Selectivity SQL Table Access” report is intended to show the openers of files (NonStop SQL Tables) whose accesses exhibit low selectivity; that is, relatively small values for the records used to records accessed ratio.

Use this parameter to specify the selectivity threshold; the unit of measure is records used as a percentage of records accessed. “Low Selectivity SQL Table Access” will only show opens that exhibit selectivity equal to or less than this percentage.

Values range from 0.0001 to 99.9999 percent; the default value is 1.0000 percent (one record used for every one hundred records accessed).

Example: NEEDLE 0.0001 (one in a million!)

Max rows: maximum number of rows to be included per Excel sheet. 

Given availability of collected data, this covers all TCP/IP (Process, link, subnet), PIF, IPV6, and Expand activities.  Selection criteria is simple.  Select date and time period to be covered, and to whom the analyses should be emailed to.

This is a general review of your system activities, with insights to issues, as well as recommendations on how to enhance the performance and overall utilization.

.  Below are the selection criteria:

• From & To: Date and time period the analyses should cover.
• Email to: List of people who should receive the analyses.
• Minimum Process Busy: Minimum value used for inclusion in analysis reporting
• Disk Queue Length: Minimum Threshold for Alerts
• Disk File Transient Opens: Minimum Threshold for Alerts
• Minimum Total Transient Transactions: Minimum number of processes an Ancestor must have before it can be included in “Transient Processes” reports.
• Disk File Requests Blocked: Minimum Threshold for Alerts
• Low PIN sub-volumes: Identify programs in these sub-volumes (, separated) that are running processes at low PIN.
• Compare Against: You may have RA to select any of the prior Quick Tuner reports, and ask RA to compare

Two types of analyses are available:

• Summary – Covers overall capacity and growth, for total storage, as well as at disk level.
• Detail – Has all Summary contents, but also breaks down usage per Group, User, and Sub volume.

Select the one you want, and to whom the analyses should be emailed to.

Two types of Trend reports are available.:

• Weekly – 7-day (Sunday – Monday) trend at collected interval level resolution.
• Monthly – Full month trend, at hourly resolution.

Given the date you specify; they each go back a week (Sunday through Monday), or a month (beginning of the month of the selected month).

Both reports include trends for:

• CPU
• IPU
• Process
• Disk
• TMF

Select the date period, whether Low PIN/ High PIN data should be included for specific subvolumes, , and to whom the analyses should be emailed to.

Select one or more Applications from those previously defined.

Select a date and time period, and to whom the reports should be emailed to.

Report includes each Application’s CPU busy and Disk IO activity for the selected time period.

Select whether you want to see Pathway analyses, or limit it to only conditions which constitute an alert.  This covers all Pathways covered by host based parameters (selection of Pathmon programs).

Select a date period and to whom the reports should be emailed to.

This is the most detail analyses of your system activities offered by Remote Analyst.  It includes over 90 different charts and reports.  Below are the selection criteria:

• From & To: Date and time period the analyses should cover
• Email to: List of people who should receive the analyses
• Audit Volumes: List of volumes used for TMF activities. By default, RA preselects all volumes with “AUDIT” in their name
• Allow: If a Measurement is started when Processes are already running, and their files are already open, MEASURE may record the DISCOPEN or FILE entities BEFORE recording the PROCESS entities; this effect can be significant on a busy system with many entities under measurement. This parameter allows one to specify by how many seconds a DISCOPEN or FILE entity recording can precede its opening PROCESS entity recording, in order to allow it still to be matched to its opening PROCESS.

Too small a value may result in DISCOPENs or FILEs not being matched to their opening Processes; too large a value may result in DISCOPENs or FILEs being matched to the wrong PROCESS if there is significant transient processing and Process IDs (s) are “re-used”.

Values range from 0.00 to 99.99 seconds; the default value is 5 seconds.

Example: ALLOW 15

• Exclude: Several charts and reports exclude “low-activity” entities from their output, in order to minimize the amount of data presented; this parameter lets the user set the exclusion threshold. The “unit of measure” varies from report to report, but it is typically a percentage utilization (e.g. CPU Busy), a percentage of some global total (e.g. of total logical disc file I/O’s), or a rate of events per second (e.g. logical I/O’s per second). Reports exclude entities whose activity is below (less than) the threshold. Each report shows its EXCLUDE value and “unit of measure” at the bottom of every page.

Values range from 0.00 to 99.99; the default is 0.1.

Example: EXCLUDE 0.01

• Flag: Some reports flag “transient” entities with an asterisk. Examples of transient entities include: processes that lived for less than the report “window”, and files that were open for less than the opening process’s life. This parameter allows the user to specify the percentage of the window or life for which the entity must have existed before it is considered “transient”; the entity is flagged if it lived for less than this percentage of the window or opening process’s life.

Values range from 1 to 99 percent; the default value is 90 percent.

Example: FLAG 95

• IO Factor: Some reports attempt to apportion Disk Process CPU time to the files/partitions accessed, or to the programs accessing the files/partitions.

This parameter specifies how much more CPU-costly a Physical I/O (Driver Call Minus Cache Hit) is than a Cache Hit. Values range from 0.0 to 99.9; the default value is 2.0.

Example: IOFACTOR 2.5″;

• Msgs: The “Program Overview” chart and the “Application Program Profiles” report show program resource consumptions and wait times per “unit of measurement”. One MESSAGE RECEIVED is often a good unit of measurement for “server” processes.

Other processes (e.g. batch processes), however, may receive only process-creation messages such as the STARTUP message, a PARAM message and one or more ASSIGN messages. A MESSAGE RECEIVED is not usually an appropriate unit of measurement for such processes.

MINMSGS allows the user to specify the minimum number of messages a process must receive in order for “Program Overview” and “Application Program Profiles” to show program resource consumptions and wait times PER MESSAGE RECEIVED. If the average number of messages received by processes run from a given program file is below MINMSGS, “Program Overview” and “Application Program Profiles” will instead show program resource consumptions and wait times PER SECOND of the average “lifetime” of one of these processes.

Values range from 1 to 9999; the default value is 10.

Example: MINMSGS 15

• Needle: The “Low Selectivity SQL Table Access” report is intended to show the openers of files (NonStop SQL Tables) whose accesses exhibit low selectivity; that is, relatively small values for the records used to records accessed ratio.

Use this parameter to specify the selectivity threshold; the unit of measure is records used as a percentage of records accessed. “Low Selectivity SQL Table Access” will only show opens that exhibit selectivity equal to or less than this percentage.

Values range from 0.0001 to 99.9999 percent; the default value is 1.0000 percent (one record used for every one hundred records accessed).

Example: NEEDLE 0.0001 (one in a million!)

• Max rows: maximum number of rows to be included per Excel sheet.
• Include Macro Generated Reports – For many of its charts, DPA can produce a complete set of detail data. These are then placed as hidden data in the workbook.  You will then have the option on these specific reports (marked with a flower icon) to click on a displayed graph entry and see the detail data behind it and as it relates to the graph item you clicked.  One caveat is that generation of this much data, more than doubles the amount of time required to generate the DPA report, and also doubles the size of the workbook.  By default, this option is set to No (no hidden data will be produced).  You may set this to Yes, should you require the second level of details, and do not mind the extra report generation time, and workbook size.

 Next, select from a list of Reports & Charts to be include in the analyses.  Given that these are rather detail analytic, it is recommended that you include only those you are interested.  It will allow for quicker delivery of analyses.

Note that each report or chart requires metrics for certain Entities to be available for the selected date/time period.  During the generation process, DPA will look for these data, and if unavailable will still create the work-sheet but will write “No data to report”.  Again to save time, click on the button labeled “Verify Entity Availability”.  It checks for available data for the selected date & time period, and then only displays the list of reports and charts for which data is available.

TBD.

This is where you can review a list of reports/analyses scheduled for distribution, and add new ones as needed.

List of previously defined schedules are listed on the right panel.  You may filter out displayed list, using the analyses Type options on the top.  You may also choose to only see a list of analyses scheduled to go to a specific person by selecting the person’s name from the displayed list box on the top right.

To Edit or Delete a schedule, click on the appropriate Button on its row.

To add a new schedule, click on the Add Button above the list and on top right.

On the new Window:

• Type: Select a Report / Analyses Type. Choices are:
  • Daily – Daily emails of prior day’s performance and alert conditions. Choose what time the report should be generated, and whether it should e for a specific time period. You also have the option to set the parameter “Alert on Exception”.  By default, this is set to No.  It means that Remote Analyst highlights items on the Daily email, based on hard thresholds.  For instance, CPU Busy is highlighted in yellow when between 80% and 89%, and highlighted in red, when at 90% or more.  Should you set the “Alert on Exception” to Yes, then it highlights objects and values if they are outside of “normal” (based on certain tolerance) for the specific hour of the weekday being reported.  In this scenario, Remote Analyst compares the current value over the activity for the same hour and weekday over the past month.  It highlights the current value, if it considers it an “exception”, and different from what was expected.  Note however, that it also has a built-in tolerance for different hours. Tolerance is 5% during “business” hours, 10% during “batch” hours, and 12% for other hours.  Should the current value be outside of the accepted tolerance for that hour.  For instance, if CPU Busy of a CPU is normally at 82% during batch hour on a Tuesday, then a value of 88% will not raise and alert, and Remote Analyst will not highlight the value to alert you.
  • Weekly – Weekly emails of prior 7-day performance and alert conditions. Choose what day the report should be generated, and whether it should be for a specific daily time period.  You may select to include analyses of Low PIN / high PIN
  • Monthly – Monthly emails of prior month’s performance and alert conditions. Choose what day of the month the report should be generated, and whether it should e for a specific daily time period.
  • Quick Tuner – General to detail analyses of system performance. Set whether you want this analysis generated weekly or monthly.  More options are displayed on exact day/time and coverage.  These vary between weekly and monthly options, and are self-explanatory.  There are several other parameters, specific to Quick Tuner, which you may set in advance.  For a full description check section Quick Tuner of Generate earlier in this document.
  • DPA – – This is the most detailed analyses of your system performance offered by Remote Analyst. Set whether you want this analyses generated weekly or monthly.  More options are displayed on exact day/time and coverage.  These vary between weekly and monthly options, and are self-explanatory.  There are several other parameters, specific to DPA, which you may set in advance.  For a full description check section DPA of Generate earlier in this document.
  • Network – – This is a review of your network activities, and its trend, resource utilization, and distribution over time. This covers all TCP/IP (Process, link, subnet), PIF, IPV6, and Expand activities.  Set whether you want this analyses generated daily, weekly or monthly.  More options are displayed on exact day/time and coverage.  These vary between daily, weekly and monthly options, and are self-explanatory.
  • Storage – Two types of analyses are available:
    • Summary – Covers overall capacity and growth, for total storage, as well as at disk level.
    • Detail – Has all Summary contents, but also breaks down usage per Group, User, and Sub volume.

Select frequency: daily/weekly/monthly, and at the time/day when the report should be produced.

• Email: For any of the above, select whom (one or more) should receive the Report/Analyses.

Note that you can ask for as many analyses as you require, which you can have emailed to as many people as you wish.

Right panel shows a list of all analyses generated, or in the process of being generated.

There are three controls on the top bar:

• Analyses type – By default, all are selected. Click on any to unselect and filter the displayed list.
• Since: Select a date to narrow down the list to only produced since that date.
• By: Has a list of all persons who had requested analyses. Narrow down the list, by selecting a name from this list.

You may also use the sort icons and list boxes above each column to sort, and filter out the content.

Click on the “i” icon to display detail time stamps and steps associated with the generation of the report.

Click on the download icon next to each entry to download the analyses to your device.

This is where you can set parameters to receive future capacity forecasts.  It is based on Application Profiles you define in Capacity Model. 

Select any profile from the list box, and set the following parameters:

• Base model on: Select date and time (hours of day) period, weekdays, and CPUs, to use as a model. Remote Analyst looks back at the activity of these selected CPUs, on selected hours and weekdays of the selected date period.  This is then used as the basis for forecasting future activity.  It enables you to focus your forecast to specific business hours, days, and CPUs which matter for your business and selected Profile.
• Assume: Remote Analyst uses its organic growth algorithms for future forecasts. However, you can overwrite that here, and specify what your expected future growth is.
• Keep: Choose an upper threshold for CPU busy. Remote Analyst will highlight the day and hour, when future growth takes CPU busy above this value.  It will also recommend additional CPU resources to keep up with the demand, and will analyze what the expected usage will be with and without the additional CPUs.
• Summarize: Choose whether you want to see analyses based on Average or Peak values.
• Business Transaction: specify what percentage of transactions from the set Profile you expect to be from Profile/business.
• Forecast at: Set whether Remote Analyst should present its findings at interval (as collected) or hourly resolution.

Click on Submit Button when ready.  Analyses will be emailed to you shortly thereafter.

This is where you can ask Remote Analyst to forecast what the resource utilization will be like, should you employ a different Server with varying performance and available resources.

Note that currently this is a work in progress.  As of release 2017.7, you may select only two items:

1. CPU performance – You may set your new CPUs to be from 1.00 to 10.00 times faster (e.g. 1.25 times faster, meaning 25% faster).
2. Memory – You may set higher memory per CPU by selecting from the displayed options.

You may set either value by itself, or combine the two.  For instance, my new CPUs will be 25% faster, or my new CPUs will have 64 GB of memory, or my new CPUs will be 25% faster, and will have 64 GB of memory.

When you access this feature, Remote Analyst displays settings of your current Server.  You may then “create a Server” by giving it a name (I shall call it), and decide on memory and CPU speedup options (other features will be implemented in future releases).

Then select to forecast for either any date from past (as far back as you have data on Remote Analyst) to future, and whether the forecast should be for a single day, week or month.  Considering your selections for your “dream machine”, Remote Analyst will go to that point in time, and show how the “Dream machine” will performed or would have performed (if you select a prior date).

Submit your criteria, and shortly after Remote Analyst will email you its finding in the form of an Excel workbook, as described below.

Upgrade Analyses

Below is a description of the analyses content, as of release 2017.7.  Note that the analyses vary slightly, depending of the forecast period you selected:

1. Obviously, a Day forecast covers a day, Week covers a week (Sunday through Saturday), and Month covers a month from 1^st to last day.
2. Analyses resolution for a day report is at collected interval, whereas the resolution for the week and month forecast is at the hour level.

Analyses are organized into tabs:

• About – Gives information about the parameters used for this analysis, its generation date & time, and the version of the report generator used. Notice what is shows as your current Server, and how they compare to the “dreamer” server you selected.
• CPU Busy – Compares average and peak % CPU Busy of the two servers at the noted resolution. Three graphs are employed: one to show the overall average and Peak CPU Busy of the two Servers over time, and two more one for each Server, which displays the CPU % Busy for each Server, per CPU.  These highlight the differences when a faster processor is employed.
• CPU Queue length – Compares average and peak % CPU Queue length of the two servers at the noted resolution. Three graphs are employed: one to show the overall average and Peak CPU Queue length of the two Servers over time, and two more one for each Server, which displays the CPU Queue length for each Server, per CPU.  These highlight the differences when a faster processor is employed.
• Swap Rate – Compares average and peak Swap rate of the two servers at the noted resolution. Three graphs are employed: one to show the overall average and Peak Swap rate of the two Servers over time, and two more one for each Server, which displays the Swap rate for each Server, per CPU.  These highlight the differences when there is more memory available per Processor, and hence less swapping may be needed to allocate memory for code or data.

Memory – Compares average and peak memory usage (shows GB and % free) of the two servers at the noted resolution.  Three graphs are employed: one to show the overall average and Peak (least) available memory of the two Servers over time, and two more, one for each Server, which display the available memory for each Server, per CPU.  These highlight the differences when there is more memory available per Processor, and hence less swapping may be needed to allocate memory for code or data.

Remote Analyst can keep an eye out on Processes running on your Server, and send our alerts, if and when your requirements are not met.

List of previously defined settings are listed on the right panel.

To Edit or Delete a setting, click on the appropriate Button on its row.

To add a new setting, click on the Add Button above the list and on top right.

On the new Window:

• Alert Name: Give your Alert setting a name.
• Program File: Enter a Program name, whose Processes you want monitored.
• Runs on: Select weekdays. All weekdays are selected by default.
• Recipient(s): Select one or more Recipients who should be notified if alert conditions are met.
• No Process starts by: Set hour/minute time threshold if no processes of this program are running.
• All Processes do not stop by: Set hour/minute time threshold where you want no processes of this program running.
• More than ..: Set maximum number of Processes of this program which should be active simultaneously. This applies to the time period set earlier.
• CPU Balance: Set a value for where any process I out of balance, when compared to other Processes of the same program.
• Abort % – If Processes perform TMF transactions, set a threshold for % of transactions aborted (per collected interval).

This is where you select which Analysts should have access to your Remote Analyst data.  List of companies is displayed on the left side of the right panel.  When you click on a company, list of the Analysts which have access to your systems’ metrics (on Remote Analyst) will be displayed on the right side.  To remove an Analyst, click on the Delete button next to her/is name.  Note that this removes the Analyst access from all your systems.

List of companies and their analysts are maintained by Idelji Corporation.  Write Support@10.0.1.128 if you have questions, or if you want a new Company and/or Analyst added.

To add an Analyst to have access to your data, click on an Analyst company name, and then click on Add icon on the right side of the toolbar.  From here, select one or more from the list of displayed Analysts.

Note that an Analyst with access to your systems on Remote Analyst, has no access to any of the Admin features, except for scheduling reports for herself/himself.

Their purpose will be to do investigative and analyses work only.  They can review the metrics online, and ask to receive analysts on demand, or on scheduled.

This is where you may specify criteria for one or more “Applications” running on this Server.  Criteria you set here groups Processes matching your criteria, as being part of the application you name.  Remote Analyst then calculates and shows (online & reports) their usage of CPU resource.  This enables you to review their comparative CPU usage over time, growth of each application, and whether there are potentials for bottleneck.

Left side of the right panel shows a list of applications you had previously defined.

To add a new application, click on the Add Button above the list.

To copy configurations of one or more applications from one NonStop Server to another, click on the Copy Button, also above the list.

To select an application, click on its name on the list) first one is selected by default.  When selected, its criteria is listed on the right side.  Click on Delete or Edit Buttons next to each entry, as appropriate.

To add new criteria, click on the Add Button on the top right of the list.

On a new window, select available options are select a “Type” from the top bar.  Choices are:

• Object file: Processes running a given program object file. You may use wildcards.
• Process: Specific processes. You may use wildcards.
• User ID: Processes owned by a specific user ( group.user ). No wildcard.
• Home Terminal: Processes with a specific Home Terminal. No wildcard.
• Priority: Processes running at a specific priority. No wildcard.
• OSS Names: Processes running specific OSS program name objects. No wildcard.
• Ancestor Program Name: Processes running with an Ancestor running a specific object file. No wildcard.

Set any of the conditions, and select whether these criteria be optional (OR), or required (AND), when added to other criteria of this application.  Check the “Add another” box to keep the window open, after you click the Save Button.

TBD.

This is where you set Capacity Model / Profiles which can later be used to forecast future capacity requirements.

A Capacity Model calculates IO rates against one or more files, by one or more Programs/Processes, and the associated CPU usage.  In effect, it calculates CPU cost of completing a transaction within the profile you specify.

Right panel shows a list of Profiles you had previously defined.

To remove a previously defined Profile, click on the Delete Button for the row it is displayed.  Note that there are no Edit options.  This is due to the fact, that substantial analytics are performed, and new Tables are created when you add a new Profile.  These tables and their content are continuously updated as new data comes in, and old metrics are archived.  To go back through the archives and rebuild a Profile is impractical with possible negative impacts.

To add a new Profile, click on the Add Button above the list.

To copy configurations of one or more Profiles from one NonStop Server to another, click on the Copy Button, also above the list.  On the new Window:

• Profile Name: Name your profile
• Data Files: Specify a file or a group of files, using wildcards. Remote Analyst will measure IO rates against these files.
• Opener: Choose whether you want to measure IO requests coming from any process, only processes of a specific program(s) (wildcard allowed), or processes (wildcard allowed)
• I/Os: Choose whether all IOs (Read and Write) should be counted, or only Reads or Writes.
• 1 Transaction is: Set the relationship between IOs and transactions.  For instance, you could set that each transaction requires 3 IOs to this file.
• Recipient(s): One you submit your selection, Remote Analyst goes through all available metrics in its history to produce an analysis of this model, and its resource requirements.  Depending on the depth of historical data, this could take several minutes to an hour.  Select names of persons who should receive this analysis, once ready.

Remote Analyst can keep an eye out on Processes running on your Server, and send our alerts, if and when your requirements are not met.

List of previously defined settings are listed on the right panel.

To Edit or Delete a setting, click on the appropriate Button on its row.

To add a new setting, click on the Add Button above the list and on top right.

On the new Window:

• Alert Name: Give your Alert setting a name.
• Program File: Enter a Program name, whose Processes you want monitored.
• Runs on: Select weekdays. All weekdays are selected by default.
• Recipient(s): Select one or more Recipients who should be notified if alert conditions are met.
• No Process starts by: Set hour/minute time threshold if no processes of this program are running.
• All Processes do not stop by: Set hour/minute time threshold where you want no processes of this program running.
• More than ..: Set maximum number of Processes of this program which should be active simultaneously. This applies to the time period set earlier.
• CPU Balance: Set a value for where any process I out of balance, when compared to other Processes of the same program.
• Abort % – If Processes perform TMF transactions, set a threshold for % of transactions aborted (per collected interval).

TBD.

This feature is available to “Admin” users, where they can add other users.

List of current users is displayed on the right panel.  As appropriate, click on the Buttons Edit/Delete/Change Password.  To add a user, click on the “Add” Button on the top right of the right panel.   Here are the fields for a new user profiles:

• First & last name, and email address
• Password – 8 characters’ minimum. Must contain at least one upper case and a number.
• Status – Active or inactive; by default, a new user is set to “Active”. Users cannot logon when “Inactive”.
• Type – Admin or Staff (default). Admin has exclusive access to Admin features:
  • Workdays
  • Capacity Profile
  • Process Watch
  • Schedules (to set schedules for self and all others; Staff can only add schedules for her/himself.
  • Users
• Access – Select list of NonStop Servers, this user should have access to.

Click on the Add button to add the new user.

Here is where you tell Remote Analyst about your business as it relates to this NonStop Server.  This information is used by Remote Analyst to set its forecasts, and also to determine exceptions at different hours/days.

The right panel has two segments, and a Threshold setting button:

1. Top – Where you set (click on save to save your settings!):
   1. Workdays – Simply click on the days that are considered workdays for your business.
   2. Hours of the day where online business or batch activities take place. There are two rows, one for business and another for batch hours.  Simply click on each hour for a row to set for business or batch.  Those not clicked will be considered as “other”.
2. Main/lower – Where you select from an annual calendar to set your expected exceptions. These are days which you expect abnormal activity based on the type of business you have (e.g. New Year, Christmas, a national holiday). For instance, depending on your type of business, a specific upcoming holiday may mean more (or less) business activities.  Simply click on that day of the calendar, and set your expectations.  Those already set are shown in red, if activity is set to increase, or yellow if lower activity is expected.

Set your expectations only for future dates.

Thresholds – This button is displayed below and to the left of the top grid.  Click to open a new window, showing the sensitivity level for each of the three daily periods of: Business, Batch, and Other.

Note that from its knowledge of past, Remote Analyst has certain expectation about how the Server should behave for different time periods and days.  It is expected to highlight, through the Dailies emails, periods of time where resource utilization varied significantly from what Remote Analyst had expected.  This is what defines an exception.  Here you define how sensitive Remote Analyst should be to variations from expected behavior, before it calls it a Minor or Major condition (There are two settings of Minor and Major for each item being monitored.).

Your setting options are:

• CPU % Busy & Queue
• IPU % Busy & Queue Length
• Disk Queue length and % full

Default values are displayed for each of the time periods.  You may change them as you see fit for your environment.  Arrow icons on top may be used to copy settings from one time period to the next (one direction only).

Click on the Save button to save the updated settings.

It’s a reflection of what Remote Analyst knows about your profile, and which NonStop Servers you have access to.  It’s also where you can change your password.

There are three Scanner features which assist you in reviewing past history of Files, Processes, and Processes of given program object codes.  Below are details on each:

File scanner looks for processes opening and writing to files you specify, for the period of time you set.  Here are the search options:

• File – Enter a name of a single file, or use wildcards to cover many.
• Opener in CPU – Select any specific CPU to look for openers. Default is all CPUs.
• Start at / On: Set a start date and time.
• Stop at – Optionally, set a stop start date and time.
• Display Top – Choose from one of the displayed options to set how many matching entries should be displayed at once. A Next Button is displayed to allow you to display more, if more matches are found.
• Scan – Choose whether Remote Analyst should scan forward or backward in time, from the start time you set.

Click on the Scan Button to start scanning.  You may click on Stop Button at any time to halt the scan.

Matching entries are displayed on a grid.  You may click on the File name (if wildcards were used to search) to see the history of that file, or Openers count to see the list of Processes which had opened that file, and from there to more details on each Process.

Process scanner looks for processes matching the search criteria you set.  Here are the search options, for Processes:

• In CPU: Running in a specific CPU. Default is all CPUs.
• Start at / On: Set a start date and time.
• Stop at: Optionally, set a stop start date and time.
• Process: Search for Processes:
  • Ancestor: Ancestor Process name match. Wildcard is ok.
  • CPU Busy >= : Which use more % CPU busy than a specific value you set here.
  • Mem Mb >= “ Which use more MB memory than a specific value you set here.
  • Owner: Owned by a specific Group.User ID.
  • PIN: Process Identification Number. Use it in conjunction with a CPU selection (In CPU).
  • Priority >=: Running at or higher a priority value.
  • Process (default selection): Matching a name. Wildcard is ok.
  • Program File: Running a specific program object name.
• Summarize: Select whether each matching Process at each interval should be displayed individually, or summed with other matching Processes.
• Display Top: Choose from one of the displayed options to set how many matching entries should be displayed at once. A Next Button is displayed to allow you to display more, if more matches are found.
• Scan: Choose whether Remote Analyst should scan forward or backward in time, from the start time you set.

Click on the Scan Button to start scanning.  You may click on Stop Button at any time to halt the scan.

Matching entries are displayed on a grid.  On the displayed list, you may click on the:

• Process name, to see the history of that Process, and its detail at that interval.
• IPU, to see all matching Processes running in that IPU.
• Program file, to see a list of all Processes running that Program.
• Priority, to see a list of all Processes running at that Priority.
• User – to see a list of all Processes owned by that user ID

Program scanner looks for processes running under matching Program name.

Here are the search options:

• In CPU: Processes running in a specific CPU. Default is all CPUs.
• Start at / On: Any Process running after this date/time.
• Stop at: Optionally, any Process running before this date/time, but after the date/time entered above.
• Program File: Processes running a specific or matching program name(s). Wildcard is ok.
• Summarize: Select whether each matching Process at each interval should be displayed individually, or summed with other matching Processes.
• Display Top: Choose from one of the displayed options to set how many matching entries should be displayed at once. A Next Button is displayed to allow you to display more, if more matches are found.
• Scan: Choose whether Remote Analyst should scan forward or backward in time, from the start time you set.

Click on the Scan Button to start scanning.  You may click on Stop Button at any time to halt the scan.

Matching entries are displayed on a grid, showing:

• Date/Time: Date & Time of each interval where matching Processes where found.
• Total Count: Total Process count.
• Transient Count: Number of Processes which ran for less than the interval time.
• Static count: Number of Processes which ran for more than on interval.
• CPU Busy: Average % CPU Busy of all matching Processes during that interval.
• Peak CPU Busy: % CPU Busy of the busiest matching process.

On the displayed list, you may click on the:

• Process name to see the history of that Process, and its detail at that interval.
• IPU to see all matching Processes running in that IPU.
• Program file, to see a list of all Processes running that Program.
• Priority, to see a list of all Processes running at that Priority.
• User – to see a list of all Processes owned by that user ID

Four Browser features give quick and informative views into system performance.  Each of these Browsers give links to other related objects and metrics, thereby creating an endless array of possibilities.  These features are instrumental in investigative work.

Shows CPU, Process, and Disk performance metrics for a given interval, in sections:

• Main graph on the top left shows % CPU Busy and Queue Length for each CPU. Click on any CPU to get more detail.  Click on Next or Previous Buttons on the right top or left of the graph to display metric values for the next or previous interval.
• IPU Busy graph, for the selected CPU, shows IPU/Core busy for each IPU of the selected CPU. Click on any IPU to see a list of Processes running on that IPU.
• Memory GB, for the selected CPU, using a pie chart shows % of Memory used and available.
• Disk IO/Sec, for the selected CPU, shows Disks channeled running through that CPU, and % of Cached vs Physical IOs.
• Processes, for the selected CPU, shows number of Processes, and % of static, vs. dynamic Processes. A Dynamic Process is one which runs for less than the interval period.
• A grid below shows more detail on all Processes running on the selected CPU. They are:
  • Name: Process Name. Click on the name for a full history of that Process.
  • CPU/IPU: CPU (only if all CPUs are selected), and IPU where the Process was running. Click on IPU for a full list of Processes.
  • Busy%: % Process busy, at IPU level.
  • Mem(MB): Memory consumed by the process in MB.
  • Program: Object Program name of the Process. Click on Program name for a list of all Processes running that Program.
  • Priority: Priority of Process. Click on Priority value to see a list of all Processes running at that Priority.
  • S/T: Whether this Process was Static (S), or Dynamic (D).  .  A Dynamic Process is one which runs for less than the interval period.
  • Duration: In mm:ss, time which the Process was running.
  • Owner: Process Owner.

On the top toolbar, click on:

• Search, to change different date/time, or CPU, or all CPUs.
• Dig icon, to ask for detail & specific DPA analyses. A new window is displayed:
  • Top bar shows a 60-minute timeline where the current interval is selected (red bar). Assuming your collection interval is less than 60 minutes, you may click on either side of the bar to expand the timeline in either direction and inside the bar to shrink it. Maximum allowed is 60 minutes to keep the report generation time within a reasonable period.
  • Select one or more of the available DPA Charts & Reports.
  • Select any one or more email addresses to send the analyses to.
  • Click on the Submit button to initiate the Analyses, which will be emailed upon completion.
• Scanner icon, icon to scan for Files and Processes.
• Excel icon to export the screen content to an Excel file. Each section will be represented in a sheet of the newly generated workbook.
• Help icon. Displays this document.
• Duplicate icon, to duplicate the displayed Window. You may do this to enter different criteria, and view displayed information side by side on two separate windows.

There are two separate Windows showing Disk metrics:

Here information for a selected Disk is displayed for a given interval.

Main graph shows two metrics (Y1 and Y2) for the selected period, and highlights (X) a specific point in time, for which File activity is displayed on the grid below, with more disk level metrics displayed above the grid.

Toolbar on top allows selection of metrics to display on Y1 and Y2, as well as a calendar to select date periods.  Here is more detail:

• Each list box (one on left, and another on right) offers the choice of following metrics:
  • Cache Hit Rate
  • Disk: Logical IO
  • Disk: Physical IO
  • DP2 Busy
  • File: Logical IO
  • File: Physical IO
  • Queue Length
• Calendar allows you to select a date, and choose to see activity for:
  • 24 hours – By default, last 24 hours, when you first open this Window. Thereafter, when you click Prev or Next Buttons, a 24-hour period from beginning of each day.
  • Week – Sunday through Monday for the week of the day you select.
  • Month – Beginning to end (or current day) of the month for the day of the month you select.
• Click on Next or Previous buttons to show the data for the next selected time period/
• Dig icon, to ask for detail & specific DPA analyses. A new window is displayed:
  • Top bar shows a 60-minute timeline where the current interval is selected (red bar). Assuming your collection interval is less than 60 minutes, you may click on either side of the bar to expand the timeline in either direction and inside the bar to shrink it. Maximum allowed is 60 minutes to keep the report generation time within a reasonable period.
  • Select one or more of the available DPA Charts & Reports.
  • Select any one or more email addresses to send the analyses to.
  • Click on the Submit button to initiate the Analyses, which will be emailed upon completion.
• Help icon. Displays this document.

On the list of busiest files, click on any File name to open and display its history over time.

Shows metrics for all Disks, and top files for each, for a selected interval.

A list box on top offers the following metrics to choose from:

• Busiest File, Logical IO
• Busiest File, Physical IO
• Cache Hit Rate
• DP2 Busy
• Disk, Logical IO Rate
• Disk, Physical IO Rate
• Queue Length

Select an item, and the graph below it shows the top 10 (Exception: Cache Hits shows the bottom 10) matching Disks, and Others.  Click on any Disk on the graph to see its history/trend.

For each of the Disks on your NonStop Server, a row on the grid, below the graph shows:

• Physical IOs per second
• Logical IOs per second
• Queue Length
• Cache Hit Rate
• % DP2 Busy
• Busiest file, based on Physical IO, and its IO rate
• Busiest file, based on logical IO, and its IO rate

Click on any file to see its history/trend.

On the top toolbar, click on:

• Duplicate icon to duplicate the displayed Window. You may do this to enter different criteria, and view displayed information side by side on two separate windows.
• Search, to change different date/time, or CPU, or all CPUs.
• Scanner icon to scan for Files and Processes.

There are two separate Windows showing Process metrics:

Shows a graphical display of history of a selected Process.  It represents % CPU busy and memory usage at each interval, by this Process.

A selected interval is highlighted on the graph with an X indicator.  You may click on any point on the graph to change the selected interval.  On the toolbar:

• Use the Calendar to switch to a different day.
• Click on Next & Prev. Buttons to move a day forward or back.
• Click on the Excel icon to export the displayed content to Excel.

More identifiable information is displayed below the Graph, and a list below shows a list of file this Process had open during the selected interval.  For each file, it displays:

• File: Click on the File name to see Process detail and history.
• Reads/Sec: Reads per second by this Process, against the selected File.
• Writes/Sec: Writes per second by this Process, against the selected File.
• Opens: Number of Opens by the Process against this File.

Shows metrics for a set of Processes, for a selected interval.  The set is based on your prior selection.  For instance, if you click on a User ID, then the set includes processes running under that User ID (selected or all CPUs).  Similarly, you may click on a specific Priority, an IPU, or other hyperlinks on other screens to see the list of related Processes.

Following tools are available on the toolbar:

• Duplicate icon, to duplicate the displayed Window. You may do this to enter different criteria, and view displayed information side by side on two separate windows.
• Scanners – Open windows to scan Files, Processes, and Programs.  See Scanners on description of how each works.
• Search, to change different date/time, or CPU, or all CPUs.

Next and Prev Button show matching Process list for the next or previous interval.

Number of Processes matching the criteria is displayed below the Prev Button.

Selection criteria is displayed below the Next Button.

The Table below, shows the following information per Process (where applicable):

• Name: Process Name. Click on the name for a full history of that Process.
• CPU/IPU: CPU (only if all CPUs are selected), and IPU where the Process was running. Click on IPU for a full list of Processes.
• Busy%: % Process busy, at IPU level.
• Mem(MB): Memory consumed by the process in MB.
• Program: Object Program name of the Process. Click on Program name for a list of all Processes running that Program.
• Priority: Priority of Process. Click on Priority value to see a list of all Processes running at that Priority.
• S/T: Whether this Process was Static (S), or Dynamic (D).  A Dynamic Process is one which runs for less than the interval period.
• Duration: In mm:ss, time which the Process was running.
• Owner: Process Owner.

Shows a graphical display of history of a selected File.  It represents IO rate at each interval, separating Read and Write read totals (rated) by all processes which had it open at that interval.  Number of openers is also reflected on the graph.

A selected interval is highlighted on the graph with an X indicator.  You may click on any point on the graph to change the selected interval.  Use the slide bar area below the graph to move back and forth in time and expand or contract your view.  A list below the grid shows the list of Processes which had it open and that time, along with the following information:

• Process: Click on the Process name to see Process detail and history.
• Program: Click on the Program name to see a list of Processes running during that interval.
• CPU/PIN: CPU and Process Id Number where the Process was running.
• Reads/Sec: Reads per second against the selected File.
• Writes/Sec: Writes per second against the selected File.
• Opens: Number of Opens by the Process against this File.
• Lock Wait: Number of times the Process had to wait for IO against this file due to record locks.
• Total Reads: Total reads for the selected period.
• Total Writes: Total Writes for the selected period.

More identifying and self-explanatory data are displayed on the left panel of this Window.

TBD

TBD.

TBD.

TBD.

TBD.

TBD.