HP NonStop Availability Stats And Performance (ASAP)
Copyright(C) 2012-1999 - Hewlett-Packard Company
README - READ BEFORE INSTALLATION 

Product Name: ASAP CLIENT 3.2

Product ID: 
SE30V3  G-series
HSE30V3 H-series
QSE30V3 J-series
                          
Components:   
T0400V03^AAN ASAP CLIENT 3.2.2112 
T8481V3115   CSG 3.3.22
T8487V30     OIL 
T8486V30     OEM
T0407V01     OVO SPI

I.  Basic Product Installation Instructions

1. Ensure that requirements for using this product are met (see Section II Product Requirements below).

2. Ensure that prerequisites for the installation utility and any product-specific installation requirements are met (see Section III Installation Prerequisites below).

3. Follow the installation instructions in Section IV below, to install the product on your workstation.

4. Follow the post-installation instructions in Section V below, after installing this product.

II. Product Requirements:

Client Requirements
Required Hardware:   1 GHz PC or faster
Memory Requirement:  1 GB
Minimum Disk Space: 30 MB
Minimum Windows version: 
- Windows 7 
- Windows Server 2008
- Windows Vista 
- Windows XP 

Server Requirements
Required Hardware:  Sierra, Integrity, Blade systems
Minimum OS Release: NonStop D42, G06, H06, J06-series
Minimum OS Gateway: SSGCOM T8488AAB 31MAR97 or later

III. Installation Prerequisites:

NONE

IV.  Installation Instructions:

1. Download ASAP Setup or put ASAP client CD in PC.

2. Run ASAP SETUP. Follow directions displayed in the Setup.  

3. Once ASAP is installed, start ASAP. If you encounter the message “Unexpected error; quitting”; then shutdown ASAP, rightmouse ASAP.exe, select Run As Administrator, and repeat the action. This allows ActiveX server components to be registered correctly. 

V.   Post-Installation Instructions:

1. See INSTALLATION and STARTUP sections of ASAP.DOC or ASAP.HLP for detailed info on getting started.

2. Review ReadMe addendum sections:
- "Summary"
- "Overview"
- "New Feature History"
- "Problems Corrected History" for a complete list of new features and problem fixes in this release.

3. HP OpenView Smart Plug-In for ASAP is included on the ASAP Client CD. This Smart Plug-In (SPI) allows you to share ASAP object states with HP OpenView. This Smart Plug-In is NOT required in order to install or use ASAP, but can be used to share ASAP availability stats and performance info with HP OpenView Operations.

To install HP OpenView SPI for ASAP see to the "OpenView SPI" directory in the ASAP Client CD.

4. HP Systems Insight Manager (SIM) and ASAP integration is provided as part of ASAP Client. 

To install ASAP into SIM, check the SIM check box on the ASAP Notify control panel. For more info about ASAP-SIM click the HELP button on the ASAP Notify control panel or see ASAP client documentation for the Notify control panel.

VI.  Manuals Installed by this CD

ASAP ..\Program Files\Tandem\ASAP\ASAP.DOC
ASAP ..\Program Files\Tandem\ASAP\ASAP.HLP
CSG  ..\Program Files\Tandem\CSG\CSGUser.DOC
ICON ..\Program Files\Tandem\IconServ\IconServ.DOC
OEM  ..\Program Files\Tandem\OEM\OEMServ.DOC
OIL  ..\Program Files\Tandem\OIL\OIL.DOC
OVSPI..on ASAP Client CD in \OpenView SPI\..

VII. CD-ROM Root Directory Contents

AUTORUN.INF: Standard Windows Autorun file. Will start Setup.EXE if Autorun is enabled for your PC.

LICENSE.TXT: File containing limited-use Software Licensing Agreement with the licensing terms governing this product.

README.RTF/TXT: File containing product and installation information.

SETUP.EXE: Standard Windows 95/NT SETUP. Run Setup to install product.

ASAP Client: Subdirectory containing miscellaneous client info.

OpenView SPI: Subdirectory containing OpenView Smart Plug-In for ASAP. Includes all files needed to share ASAP object state information with OpenView Operations for Windows.
__________________________________

ADDENDUM

- Summary
- Overview
- New Feature History
- Problems Corrected History

Summary

ASAP Client Version 3.2 Summary
- Setup supports 32/64-bit Windows 7, 2008, Vista, XP
- Client digital signature by Hewlett-Packard Company 
- CSG 3.3.22 is included in the ASAP Client Setup 3.2
- Selecting OEM object now displays details in client

ASAP Client Version 3.1 Summary

- CPU entity provides IPUs count in logical J-series CPU     
- PROCESS entity add average Busy across IPUs in CPU
- PROCESS entity add IPU Affinity, IPU number, IPU Backup
- ProcessBusy entity add average Busy across IPUs in CPU
- ProcessBusy entity add IPU number of running process
- CLIM entities CIPCLIM, CIPMonitor, CIPProvider added
- CIPCLIM entity provides CLIM Interface stats
- CIPMonitor entity provides CLIM Monitor stats
- CIPPRovider entity provides CLIM Provider stats
- RDL defines relationships between CLIM sub-entities

ASAP Client Version 3.0 Summary

- HP ASAP 3.0 can optionally integrate with HP SIM
- 3.0 can host one/more realtime local/proxy websites
- ASAP 3.0 client supports 1.x, 2.x, 3.x servers
- Add ASAP3 Factory.EDL, Asap3sys, Asap3app files
- Updated CPU entity EDL to include new memory stats
- Add 1 new SWAP entity to EDL and icon library
- Add 7 new Tcp* sub-entities to EDL and icon library
- New TCP: Arp, Icmp6, Ip6, Igmp, Loop, MonGQ, Sock
- Add Unique Batch jobs attribute to Spooler entity EDL 
- Add support for HP Systems Insight Manager (SIM)
- Add FILE 'SAVE HTML as Entity Icon-Graph' menu item
- Add FILE 'SAVE HTML as Multi-Entity Icon-Graph' report
- Add New NOTIFY Content Entity-Attribute Grid reports
- Add 12 new NOTIFY Content report option controls
- Add new 'SIM' checkbox for ASAP and SIM integration
- Add new 'Root File' options for auto-website support
- Add new 'Shell File' option for auto-website maint
- Add AsapMail support for icons/graphs in HTML email
- Show tool tip on mouse over 'current entity' toolbar 
- Click 'current entity' => single-entity html reports
- Click 'current entity' => multi-entity html reports
- Notify Short checkbox now suppresses PC name+session
- Add Date/Time check boxes to EDL IDE FIND dialog box
- Fix no data for last entity object remove housekeeping
- Fix "more" and "+" trigger detection in datastream
- Fix AsapMail to support very large log histories
- Fix Graphics-Server single-object 2D-Black-Graphs

Overview

HP Availability Stats And Performance (ASAP) provides availability monitoring infrastructure and automated recovery actions for applications, subsystems, utilities, and hardware components on HP NonStop and LINUX Servers.

ASAP provides the following features: 
- Fault-tolerant monitoring infrastructure
- Engineered for HP NonStop Servers 
- Alerts/Reports via email, phone, pager
- Automated corrective actions based on user defined service-level goals
     
Normalized state model combines: 

- Availability state info: Up, Down, Warning, Critical
- Performance state info:  Low, Medium, High, Critical
- Service-Level objective states: Upper/Lower bound thresholds

ASAP Infrastructure allows monitoring:

- SYSTEM objects such as: Cpu, Comm, Disk, Expand, Comm, Node, System, Tape, Tcp/IP, TelServ, more..
- SUBSYSTEM domains such as: File, Process, Remote DB, RDF, Spooler, TMF, and more..
- APPLICATION domains such as: ATMs, Funds,  Accounts, Customers, Orders, and more..

- ASAP components are fully fault-tolerant, include Monitor/Collect process-pairs, fault tolerant relational database, and automated GOAL/ACTION servers

- Historical database automatically keeps history of availability and performance

- Service-Level Objectives are stored in fault-tolerant, audited database

- Components automatically restart and reconfigure, when processors go up/down, or are installed

ASAP has additional interfaces to:
- Tokenized Event Management (EMS)
- Simple Mail Transfer Protocol (SMTP)
- Phone/Pager notification interfaces
- Interactive conversational interfaces
- Graphical user analysis interfaces
- Provider and consumer APIs
- Published 3rd-normal database 
- Fat/Thin client interfaces
- WebViewpoint interface
- HP OpenView interface
- Enterprise Management Frameworks
- XML ActiveX contextual interface
- HP Systems Insight Manager (SIM)

** The following provides New Feature History details associated with ASAP Client & associated components.

New Feature History

** [3.2.2112] ASAP 3.2 Setup now supports either 32/64 bit Windows 7, 2008, Vista, and XP versions.

** [3.2.2112] CSG version 3.3.22 is distributed with ASAP Client Setup 3.2.

** [3.1.1020] HP ASAP 3.1 Availability Statistics And Performance (ASAP) EDL has been enhanced to provide the following additional stats about J-series NonStop blade systems:

* CPU entity attributes added:
  - IPUs count in logical J-series CPU     

* PROCESS entity attributes added:
  - Average Busy across IPUs in CPU
  - IPU Affinity
  - IPU number
  - IPU Backup number

* ProcessBusy entity attributes added:
  - Average Busy across IPUs in CPU
  - IPU number of running process

* CLIM sub-entity attributes added:
  - CIPCLIM - CLIM Interface stats
  - CIPMonitor - CLIM Monitor stats
  - CIPPRovider - CLIM Provider stats
  - RDL relations between CLIM sub-entities

** [3.0.1321] HP ASAP 3.0 Availability Statistics And Performance data can now integrate stats with local or remote websites including optional integration with HP Systems Insight Manager (SIM). To add ASAP statistics to a website:

a) Click WEBSITE on Notify control panel
b) Select content: Score, Alerts, Detail, ..
c) Select options: Graphs, Icons, Shade,..
d) If SIM website, check SIM checkbox
e) Click OK or APPLY to commit website into production.

A single client can maintain multiple web sites by configuring multiple user profiles. For more info about ASAP websites click the HELP button on the ASAP Notify control panel, or see documentation about the ASAP Client Notify control panel.

** [3.0.1311] HTML Entity-Attribute Grid reports. You can now obtain a range of HTML reports by clicking on the current Entity toolbar button.  This button is located immediately below the Entity dropdown.  Report details depend on whether the Entity toolbar is visible. Display of the entity toolbar can be controlled by the 'Wrench' button. Example, if the entity toolbar is not displayed, then HTML reports are only for the current entity.  Whereas, if the enabled entity toolbar buttons are displayed (wrench depressed) then the HTML Entity-Attribute Grid report is for all enabled entities.

Report columns are controlled with ASAP Property sheets along with the client drop-down controls that appear across the top of the main client window:
- Node drop-down - selects node(s)
- Entity drop-down - selects entity
- Object drop-down - wildcards allowed
- Samples drop-down - depth of history
- State drop-down - state filtering

HTML reports are useful for composite analysis and/or to e-mail selected information for reporting purposes.  

To do copy a report, once the report is displayed in IE select: 
- EDIT... Select All... 
- EDIT... Copy
- And paste into an HTML editor.

To e-mail reports via IE select:
- FILE
- SEND
- PAGE by E-Mail...

** [3.0.0330] New Notify/Website options on the Notify Content tab include:

- Entity-Attribute Grid reports: provides HTML color-encoded, state-icon, graph-grid tables for use in live ASAP websites.  Also used for HP SIM integration, and also used for iconified email notifications.

- GRAPHS checkbox: enables color-coded embedded, scaled, horizontal graphs.

- ICONS checkbox: show state Icons.

- BORDER checkbox: show borders.

- Color options for graphs:
( ) Color Gray - all graphs gray.
( ) Color Max  - graphs for object
    object row match the highest
    attribute state color.
( ) Color Each - each graph for 
    each attribute is set to state
    color of each attribute.

- SHADE Checkbox: alternately shade the background of every other row.

- PAGES Checkbox: separate web pages for each entity report type.

- SHELL SHOW Checkbox: show shell launch window for each shell (for debugging purposes only)

- Shell File: optional file to be executed (shelled) at the end of each notification. Allows website, Mail, FTP push, or analysis code to do post notification processing. Clicking the [..] button after the Shell File name displays shell file dialog wizard to create an example set of shell files suitable for updating local/remote web sites.
        
- Root File: is root path/file prefix to website. May be either in ASAP directory, or may be in HP SIM dir.
      
- SIM Checkbox: integrates ASAP with HP Systems Insight Manager (SIM). Checking this checkbox invokes a wizard that prompts you how you want ASAP integrated with SIM. 

** [3.0.1311] ASAP 3.0 client supports 8 new entities (1 Swap and 7 TCP*). The client also includes changes to the Spooler EDL.  New ASAP 3 factory entity definitions are defined in the file named ASAP3SYS.EDL.  This new EDL describes 34 entities and 1600+ attributes. 

** [3.0.1311] The EDL IDE FIND dialog box now includes two new Time/Date check boxes. This allows searching Times in the form of hh:mm or Dates in the form of yyyy/mm/dd. These new check boxes allow searching and replacing dates and times contained EDL source via the EDL IDE window.

** [2.8.1021] ASAP 2.8 client now includes support for 12 new entity types and 600 new statistical attributes. The factory Entity Definition Language file named ASAP2SYS.EDL now describes statistical attributes associated with the new TCP and TELSERV entities monitored by the new ASAP TCP/IP plug-in (SE35 T0406).  

The new factory EDL file also includes new attributes for Cpu, Expand, File, and Process entities including Blade count and Blade status, as well as Expand preferred primary Cpu.

** [2.8.1015] New Show Related Measurement menu item appears on a rightmouse popup when objects are selected in grid/graph.

Selecting this menu item displays a new control panel that allows you to start detailed measurements of entities such as Cpu, Disk, File, Process entities.  

The following new options are provided:

Node   - Dropdown selects measure node 
Entity - Dropdown selects measure entity 
Object - Dropdown selects measure object
TopN   - Dropdown selects the number of busiest objects to display. Eg if DISK and TopN is 10 then shows 10 busiest files and the 10 busiest process file openers for the selected Disk volume.
Second - Dropdown is measure interval.
Sync   - Checkbox syncs Measure & ASAP.
START  - Button starts the measurement.
HELP   - Button displays help.

Measure reports appear in normal ASAP report windows and the progress bar shows measure progress.  You can also click the Report window status bar and select Correlate as .. for correlation analysis of ASAP and Measure data.

(soln 10-060501-6195)

** [2.8.1015] Show Related Measurement now removes any commas from output so Correlate in Excel display is correct.
     
** [2.8.1021] Persistent Sorts. Previously when View... Sort ... was selected from the main client window, and you clicked column headings, rows would be sorted by column selected alternately in ascending or descending order.  However, whenever updates occurred, row order reverted to the default <node> <object> order. 

Now when you click a column heading, rows remain sorted as long as that view is displayed. Thus now all sorts remain persistent even if you switch from sort view to grid-view and back to sort-view. Even subsequent updates are sorted and re-displayed after each sample update.  

Example: selecting columns such as Busy% or Full% will keep the display sorted in order as long as that view is displayed. 

Note persistent sorts must be reset if entity or attribute views are altered via ASAP property sheets or if an EDL compile occurs.

** [2.8.1021] The SORT View now autosizes columns on a best fit basis. You can change the column sizing algorithm by clicking on the area above the columns while in Sort View and then selecting one of the following size algorithms:

- Size Columns To Contents + Headings
- Size Columns To Contents Only
- Size Columns To Window
- Size Columns To Default

** [2.8.1021] If 'State Upgrades Monitored' is checked on the OSC tab of the ASAP Properties window, ASAP Notifications will now occur on state improvements.
 
Thus if an object was down, and then its state improves, eg if it goes up, a notification will now be generated if State Upgrades Monitored is checked. Previously, notifications on state improvements did not occur.  This new behavior optionally allows pager, phone, email, or HTML notifications to be sent when object states improve.

** [2.8.1020] The Entity Definition Language (EDL) has been extended to support 2 new statement types (RELATION and MAP) which define abstract hierarchical relations between entities. The new RDL statements define hierarchical relationships between TCPIP and TELSERV sub-entities. These new RDL statements are located at the end of the standard ASAP factory EDL file named 'ASAP2 Factory.EDL'. 

** [2.8.1021] Twelve new ICONs have been added to ASAP Client and to existing IconServer BitMap libraries:
- 9 new TCP...  ICONs
- 3 new TELSERV ICONs
      
** [2.8.1019] A new 'Copy Special' popup menu has been added to Report windows. This funtion copies report window text to the windows clipboard without header, trailer, or <cr> <lf> characters.  This function can also be accessed via CTL-S.

** [2.8.1019] ASAP 2.8 requires and installs AsapEDLL.DLL version 2.9.28. This new EDL DLL is installed with the ASAP 2.8 setup. Older versions of ASAPEDLL.DLL are not compatible with ASAP 2.8 enhanced EDL language capabilities.
     
** [2.8.1015] A new "Delete Removed" objects dropdown has been added to the General tab of the Properties window. You can use this dropdown to specify when removed objects should be deleted from the client. 

Certain entities such as App, Disk, File, Process, ... can have transient objects. Where a transient object is an object that at one time existed but is later removed. For example File or Process objects are created whenever applications are started, but when a program shuts down, the objects may be removed.

The "Delete Removed" dropdown can be used to control how long any removed objects continue to be displayed by the client.
      
Dropdown options include:
- NEVER delete removed objects
- IMMEDIATELY delete removed objects
- AFTER N minutes or hours where N = 5, 15, 30 minutes or N = 1, 2, 4, 8, 24 hours.

If AFTER N is specified the value of N should typically be greater than or equal to the value of AGE N specified in EDL.  

** [2.8.1021] The ASAP2SYS.EDL file for the File, Process, Tcp*, and Telserv* entities has been updated so the EDL COMMAND property now uses a new ASAP CI AGE option. This allows removed objects to be deleted entirely from the client based on the value of the new "Delete Removed" dropdown on the General tab of ASAP property sheet.
     
** [2.8.1026] The ASAP2SYS.EDL file for the CPU entity has been updated to include Blades, BladesState, and Blade mask detail. Mouse over these properties for context sensitve help.

** [2.8.1026] The ASAP2SYS.EDL file for the EXPAND entity has been updated to include primary Cpu and preferred primary cpu state. Mouse over these properties for context sensitive help.

** [2.8.1015] VIEW... GRAPH NODES, and Tile Graph Windows now are sensitive to the size, location, and visibility of the Windows TASKBAR.  

** [2.8.1013] Dropdowns now size to the width of the widest text in a number of dropdown controls within the ASAP client. This includes extreme widths in dialog boxes such as Show Related Measurement.

** [2.8.1012] Show Related Measurement shows simple object name when complex logical file or process object names are selected.

** [2.8.1011] Icon of the Show Related Measurement is now a ruler for report windows involved in measurements, indicating that additional functions are available for this type of window.

** [2.8.1010] Only update report windows if refresh is enabled, previously these windows could be reused if another I/O completed after the full report was received and the window became dormant. This condition no longer occurs

** [2.8.1009] Remote node security errors are now displayed in Report windows.

** [2.8.1008] When only one entity attribute is graphed, and graph type is 2D histogram, a full width 2D histogram if that one attribute is now displayed.

** [2.8.1007] Allow Interval seconds on SSG tab of ASAP properties to now be set to seconds for ASAP Fast entities (requires ASAP fast sampling or a FAST EDL entity).

** [2.8.1006] X1 Toolbar button can be used to increase number of samples displayed in browse window by +10 samples on each click of the "X1" button. Repeated click adds samples til the max rows per object limit is reached. Samples wrap back to 1 when max rows per object is reached.

** [2.8.1005] Multiple clients can be run from same workstation, to do this Copy and Paste entire client directory as a different directory name and then also give the ASAP.EXE a different exe name such as ASAPTWO".  Different exe names and directories allow different registry values, different EDLs, and different CI context on NonStop servers.  

** [2.8.1004] A new State Filter Toolbar allows single-click State Filtering. The new toolbar appears as a list of state Icons with the current minimum state filter value highlighted. 

The new State Filter Toolbar appears in the upper right area of the browse window and provides another reminder of the state selected, if any.

To change the minimum state filter you can either click one of the state icons or you can continue to use the existingState Filter drop-down.

** [2.8.1004] Previously selection of the ABOUT close box during startup did not stop the client.  Now if you click the close box on the About box during client startup it stops the client, eg behaves the same as the "CANCEL" button.

(soln 10-050301-5120)

** [2.8.1003] Limits on max Attributes per entity in EDL have been removed.  This limit previously was 100 attributes per entity.  The limit has been removed to support new TCP and TELSERV entities which have 170 or more attributes associated with a single entity.

** [2.8.1002] CSG version 3.1.15 is now distributed in the latest Client Setup. If you do not want to use this new CSG, do not click Install CSG button during Setup.  This new CSG is now correctly branded with HP logo. This CSG supports strong passwords and user alias logons.

** [2.8.1001] When intermediate levels in OIL are selected, and there are adjacent domains that partially match on the name these adjacent names could also appear in the graph/grid portion of the client. This behavior no longer occurs.

** [2.8.1001] A new OEM context drop-down list has been added to the OEM tab of the ASAP properties window. This allows the following new OEM context options:

- Normal Context (default)
- Full Context as XML
- Full Context as CSV

The XML and CSV (Comma separated values) options allow data associated with ASAP objects to be shared with OEM and user written adapters.

** [2.8.81001] Newer versions of Windows such as Windows XP use registry setting "ForegroundLockTimemout".  This setting may prevent applications from taking focus during normal callback processing if objects in OIL or OEM are selected. Whether this is a problem or a feature is subject to interpretation.  If you consider this a problem, the behavior can be changed by download and install of Microsoft TweakUI control panel from:

http://www.microsoft.com
/ntworkstation
/downloads
/powertoys
/networking
/nttweakui.asp 

** [2.5.1125] A new menu item "Dashboard" has been added to the browse window. This new menu item allows you to name, save, and display graphic dashboards consisting of a variety of graph types and node, entity, object combinations. Select View... Dashboard to name, save or display a dashboard.

Using this new menu item you can define a wide variety of App, Cpu, Disk, Expand, File, Process, RDF, Spooler, TMF, ... graphics.  Dashboards can be named, saved, and displayed when you want to graphically review particular area(s) of your system.

There are a variety of ways that new graphs may be created from the main ASAP Client Browse (graph/grid) window. See ASAP Client documentation for complete details.  One easy way to create new graph views is as follows:

1) Compose the view you want to create in the browse window using the Node, Entity, Object, Samples, MinState drop down controls.

2) Optionally use 'Graph Object History' popup menu item to define the amount of history desired.

3) Double click the column "NodeName" heading in the grid area of browse window to create a new graph window.

4) Repeat this process for each element you want to add to the dashboard.

** [2.5.1125] Dashboard graphic properties are now all saved upon client shutdown. Properties saved include Node, Entity, Object, Samples, MinState, as well as window location, size, and Graph Type. Upon client startup all graphic elements and associated properties are restored and become active elements.

** [2.5.1125] "Graph Type" is a new cascade menu item on Dashboard Graphic windows. To select Graph Type, rightmouse on the existing graphic.  When you select the Graph Type menu item, it displays a list of different graph types, selecting one changes the display accordingly. Graph type is now retained upon shutdown/startup and various node, entity, object graphs can have different graph types.

** [2.5.1024] NOTIFY - ASAP can now notify you via email, pager, phone, or internet browser when objects change state, or at certain times of the day provide you with detailed availability stats and performance reports.

Notifications are configured using a new ASAP Notify control panel. This control panel allows you to configure ASAP to automatically generate reports and alerts.

Notifications can occur:

- When Objects change state. For example when objects go down, or when their state becomes critical, or when a process becomes too busy you can receive mail and/or have reports automatically displayed.

- At periodic intervals. For example you can specify when you would like to receive detailed reports e.g. every 1, 2, 4, ... hours.

- At specific times of the day. For example you can specify exact times when you would like to receive detailed reports e.g. every 1, 2, 4, ... hours.

A wide range of notification reports are possible. You can customize notify rules and have multiple alert/report profiles.

- Alerts Profile. You can configure a profile named "Alerts" to send alerts to your wireless phone notifying you of recent critical object state changes whenever critical/down object state changes occur.

- Report Profiles. You can also configure other profiles to periodically send high-level as well as detailed reports to systems management personnel at various user-defined times of the day. For example, you can specify one profile to report hourly, another to report semi-hourly with a different set of report criteria, and yet another to report at specific time intervals with varying degrees of detail.

- Custom Profiles. You can also configure "background" profiles to send alerts, scoreboards, and detailed reports as web content. Using this technique reports can be viewed from web servers.  Directories such as inetpub/wwwroot/ can be auto updated. Web content reports can be generated for any Profile via the File field.

Notify rules are configured by clicking the "Notify" button on the Object State Change (OSC) Tab of the ASAP Properties window.

New secure ASAP property sheet features described below allow you to secure the Notify control panel as well as any other property sheet.

For a detailed discussion of Notify control panel options see ASAP client help.  Help is accessed via the HELP button on the new Notify control panel.

** [2.5.1024] A new Auto Restart Session check box has been added to the SSG tab of the ASAP properties window.

This new checkbox is enabled by default allowing ASAP client to automatically restart the client/server gateway in the event of a CSG session failure. If you do not want the client to auto recover from session failures uncheck this checkbox.  This option works best when the Host service is SSGCOM. To setup a SSGCOM host service on your server, enter HELP SET VERIFYUSER from within SSGCOM ci on the server.  To configure a SSGCOM service from the CSG on your workstation, enter View... Options..., and then click help.

** [2.5.1021] New FILE... SAVE ... functions have been added to the main browse window. SAVE DATA, SAVE HTML, SAVE EXCEL have all been added and now automatically spawn the process associated with each file type, eg NotePad, Internet Explorer, or Excel.

An EDIT... COPY HTML menu item has also been added to the EDIT menu.  These menu items allow you to save, display, and copy data in HTML format for use from Browsers, Excel, email, etc...

** [2.5.1003] Secure Property sheets. You can now password protect ASAP property sheets.

To password protect specific property sheet tabs, click on the Set Password button on the General TAB of the ASAP properties window.  When Set Password dialog box is displayed, select check boxes corresponding to the property sheets that you want protected. Then enter a password and click the Set Password button.

To access protected property sheets, display the ASAP properties window, and select the tab of a property sheet as you would normally.  If a property sheet is protected, you will be prompted for a password to unlock the property sheets. Enter the correct password to unlock all property sheets until the properties window is closed.

Considerations:
- if you specify a password with no tabs protected, then you "own" the Set Password dialog box even thou there are no tabs protected.
- if you specify no password and no tabs protected, then you have reset property sheet protection. And anyone can enable property sheet protection.

** [2.5.1002] Time-State Deactivation. The time-state of a domain that has been deactivated now appears gray. This is consistent with the color of the operational status of an object being gray when deactivated. Before, time-state appeared green even when a domain was deactivated using ASAP the RANK <domain>, DEACTIVATE option.

Now when state determination is set to UseStateGraphState for the statepair attributes for a given entity, the overall domain will appear gray when it is deactivated.

Note - If late-data integrity checks are enabled (OSC Tab of ASAP property sheet); And if a domain is late with its reporting of stats, that domain's time-state will be alerted in RED even when the domain is deactivated. This allows you to be aware of late data conditions even if a domain is deactivated.

** [2.5.1001] EDL IDE file browser loads
      files up to 10x faster due to new
      fileload method.

** [2.5.1011] EDL DOWNLOAD and COMPILE. You can now let ASAP client automatically download AND compile server EDL files. There are a variety of new ways that server EDL can be downloaded and compiled some automatic, so that you don't really need to worry about EDL synchronization anymore.

1) To download and compile server EDL in a single step, select:
a) FILE... Compile Server EDL... from main ASAP client window.
b) Select the file to download, and click the DOWNLOAD button to initiate download and compile.

2) When an EDL entity version mismatch occurs, a new dialog box now allows you automatically synchronize EDL. Click Yes to initiate an automatic EDL download and compile.

3) You can now also download EDL from the server into the EDL development window to analyze, edit, and compile the server EDL in the interactive development environment (EDL IDE).
a) Select FILE... IMPORT EDL... from the main ASAP client window.
b) Select FILE... DOWNLOAD EDL... from the ASAP EDL IDE window. Or click Download toolbar button.
c) Select the desired file to download.
d) Click the DOWNLOAD button.

** [2.5.1010] Whenever the EDL download dialog is displayed, the client allows you to automatically download all ASAP server EDL, including files such as the ASAPnSYS, ASAPnAPP, and ASAPUSER EDLs.

Or, if primary interest is to download USER entity definitions, you can select the ASAPUSER file. (note the EDL filename input field in the EDL download dialog is a dropdown list).

** [2.5.1010] The EDL Properties window has a new combo box labeled: "On EDL Compile..." This combo currently has two options:
- Do not inherit prior entity properties
- Inherit prior entity enabled property

If you select "Inherit prior entity enabled property" the previous ENABLED property for pre-existing entities will be automatically retained regardless of the ENABLED property settings.

For example, if you had an entity named TICKETS that was previously defined and enabled, then whenever you import and compile that entity, the ENABLED property setting will be retained regardless of the ENABLED property in the compiled EDL file.

When compiling EDL from within the EDL interactive development environment, this option is deliberately ignored. Thus EDL IDE source settings take precedence when compiled from the EDL IDE window.

** [2.5.1007] EDL IDE settings can now be restricted by password protecting the Entity tab of the ASAP property sheet as described in the next new feature.

For environments where you do not want server EDL to be downloaded, uncheck the "Enable FILE... Compile Server EDL..." check box on the EDL Properties window.

NOTICE** access to all property sheet settings can now be password protected.

Problems Corrected History

** [3.2.2112] Previously clicking an object in the OEM view did not always display object detail in ASAP Client. This problem has been corrected.

** [3.0.1311] Previously version dependent I/O datastreams could add spurious <crlf> to the end of the i/o and "+" or "more?" were not detected.  This problem has been corrected.

** [3.0.1311] Previously if there was no data for the last entity enabled removed object housekeeping did not occur in the OIL/OEM. This problem has been corrected.

** [3.0.1311] Previously the Notify Short checkbox on the Notify control panel did not suppress the PC name+session. This problem has been corrected.

** [3.0.0515] Previously if the ASAPMAIL server log file exceeded 64kb of log data, only the first 64kb was displayed. Now the full log is displayed and auto updates when it changes while viewing.

** [3.0.0322] Previously if 2D graph type and only one object was graphed, the attribute color could be black instead of the associated state color. This
issue has been fixed and is actually a bug in the Graphics-Server control itself.  This was fixed by using a different color addressing mode.

SOLN 10-070105-1495

** [2.0.2116] Previously when the regional locale of a workstation did not match comma/period usage for decimal and thousand separator on the NonStop server, a regional locale dialog box would appear at startup and request that workstation settings be changed to match NonStop server locale settings.

There is now a new Regional Locale dialog box that provides the following options:

- Change PC Regional Settings to be the same as NonStop Server

- Keep Current Regional Settings

- Keep Current Regional Settings and NEVER show this dialog again

Regardless of the setting selected, fractional numbers in EDL DATA statements should always use a period character to delimit the decimal point, since EDL files are shared and cross compiled on both NonStop servers and Windows workstations.

** [2.0.2116] Previously the Client would not scale and graph values correctly when workstation locale settings for the use of decimal and numeric grouping separators were different than definitions used by NonStop server.

ASAP Client can now operate with different regional locale settings. The old Locale dependent conversion functions have been replaced by new locale independent functions. Thus scaling and graphic interpretation of all values now works correctly regardless of regional settings.

** [2.0.2116] Previously redundant Unicode to Ansi conversions could occur. Now redundant conversions are eliminated when compiling EDL Entity and Attribute statements. This change improves EDL compiler performance by at least 4x.

** [2.0.2116] Previously the client accepted server initiated I/O flow control but would not by default initiate I/O flow control itself.

However, server initiated flow control only occurs when the ASAP ci SET IOCONTROL option has a nonzero value. If option SET IOCONTROL 0 was added to file $System.System.ASAPCONF, flow control was turned off.

This problem has been corrected by making the Client default be: Enable Flow Control.  To control this option setting from the main ASAP Client browse window:
- Select VIEW... OPTIONS...
- Click on the SSG Tab
- Click on the Advanced button
- Select I/O Control options

** [2.0.2116] Previously, the OEM was not always displayed when it was first started from ASAP. The OEM is now always displayed on startup and the default view is the Custom Alerts view. If the user has not configured a custom alerts view, ASAP will create one for the user and attempt to place it in the ..\Oem\Views\Alerts.Oem file.

** [2.0.2116 Certain versions of Windows use the registry setting "ForegroundLockTimemout".  This prevents applications from taking focus.  Whether this is a problem is subject to user interpretation. If you consider this a problem, it can be overcome by downloading and installing the Microsoft TweakUI control panel from:

http://www.microsoft.com
/ntworkstation
/downloads
/powertoys
/networking
/nttweakui.asp

** [2.0.2115] Previously, when the CSG was configured to use SSGCOM as a telnet service, the connection attempt could fail if SSGCONF file contained more data than typical. This problem has been corrected by incorporating CSG version 3.0.2.

** [2.0.2114] Previously, when the host session was first started, under certain rare circumstances an additional 20-30 second delay would sometimes occur during the initial connection sequence. This problem has been corrected.

** [2.0.2114] Previously, when the Browse window was selected and the tab key was pressed, there was an invisible tab in the tab order.  This problem has been corrected.

** [2.0.2113] Previously, on a Page Down operation the Microsoft Grid control would sometimes return a "memory could not be read error". This problem is fixed.

** [2.0.2112] Previously, fonts were sometimes vertically truncated in the Browse window Data Grid.  This problem has been corrected.

** [2.0.2112] Previously, when POPUP menu item "Show Object Details" was selected for a FILE entity subvolume that had multiple generic peer names, eg: $data.name, $data.namea, $data.nameb; subvol information was returned for all subvols matching the generic name. This problem has been corrected so that only info for the "exact" subvolume is now displayed.

** [2.0.2112] Previously, when POPUP menu item "Show Object Details" was selected for a FILE entity subvolume that had no errors, but contained hundreds of files, all files in that subvol were accidentally displayed.  This problem has been corrected.

** [2.0.2112] Previously, the EDL file for Asap1Sys.edl did not include entity version numbers. This problem has been corrected.

** [2.0.2112] Previously, the EDL IDE window was not documented. A new section, EDL IDE, has been added to ASAP documentation and the online help.

** [2.0.2106] Previously, popup menu "Show Object Details" did not check if the Host Session was enabled. This problem has been corrected.

** [2.0.2105] Previously, the APP entity EDL command did not use the AGGREGATE option.  Now the APP entity displays aggregates.

** [2.0.2105] Previously, the OEM minimum state "spinner" control was not always visible when an OEM alert window was re-sized. Now the minimum state spinner remains visible, even when the custom alert window is resized.

** [2.0.2105] Previously, the OEM minimum state "spinner" control was not present on OEM custom alert windows that had specified selection criteria. Now minimum state spinners are always present.

** [2.0.2105] Previously, popup menu item "Show Related Objectives" only allowed RANK <object>,LIST operation. Now you can select the RANK option:
- INFO for objectives from the DB.
- LIST for objectives from the SGP.

** [2.0.2104] Previously, the browse View...Back/Next function would reset its position when the browse window was updated.  View... Back/Next now maintains it position in the view history, even when updates occur.

** [2.0.2101] Previously, when popup menu item "Show Related Apps" was selected when either the Cpu or ProcessBusy entity is displayed in the browse window, an APP DETAIL command was issued, but the DETAIL option was not supported when the entity is not specified in the APP command. This has been fixed by not requesting a DETAIL option when a Cpu is selected.

** [2.0.2100] Previously, when the OEM or OIL would send Tile/Move window requests to ASAP client, the client did not include the OSC window in the tile/move operation.  This has been corrected.

** [2.0.2100] Previously, ASAP shutdown with Windows 2000 was slower than it should have been due to delays in class terminate events.  This has been corrected.

** [2.0.2100] Previously, you could not save the contents of the Command Wizard window directly to disk (without first copying it). This problem has been addressed by adding a SAVE AS button to the Command Wizard window.

** [2.0.2100] Previously, HELP was missing for certain functions. This has been corrected.  Also HELP for State Determination, the ALL Button, and the Command Wizard was updated.

** [2.0.2099] Previously, APP entities defined with EDL DETAIL or HISTORY options were not properly displayed when the SHOW OBJECT DETAILS or SHOW OBJECT HISTORY popup menu items were selected.  This problem has been corrected.

** [2.0.2099] Previously, the APP entity EDL COMMAND was not properly parsed when the GRAPH OBJECT HISTORY popup menu item was selected. This problem has been corrected.

** [2.0.2097] Previously, the OSC window was not displayed upon startup.  Now if the OSC window was displayed upon shutdown, it will be re-displayed on startup.

** [2.0.2096] Previously, EDL Export of user entities added a misleading comment indicating that these entities could be edited. Now the following comment is displayed instead: User Entity definitions(user defined).

** [2.0.2095] Previously, numeric values such as ' 1' were not aligned the same as '01' in Report windows. The problem has been corrected.

** [2.0.2095] Previously, if an ASAP V2 Client was communicating with an ASAP V1 server, the Show Related Objectives popup menu item was not supported, this problem has been corrected.

** [2.0.2094] ASAP2SYS.EDL was updated to reflect the fact that the Process entity Messages Sent, Messages Received, and Page Faults now are reported as rates per second rather than counts.

** [2.0.2093] Previously, when an entity was disabled from the ASAP Properties sheet, it would not be deleted from the Object Integration Layer (OIL). This problem has been corrected by adding a new method to the OIL, OIL.Object.Clear which clears all entities in the OIL.

** [2.0.2093] Previously, a double refresh could occur when OK/APPLY was clicked from the ASAP Properties window.  Now only a single refresh occurs.

** [2.0.2092] Previously, Max Graph Rows property did not always return the correct number of rows when State Filtering was enabled for the Browse window.  This problem has been corrected.

** [2.0.2092] Previously, when $<numeric> appeared in the ASAP Browse Window grid, it was treated as a number, and right justified, now when $<numeric> appears in the grid, it is left justified.

** [2.0.2092] Previously, report windows displayed the "+" sign prompt at the end of the ListView. The "+" is no longer displayed.

** [2.0.2092] Previously, the default Max Graph Rows drop-down value was 200. The default Max-Graph-Rows drop-down on the Graph Tab of the ASAP properties sheet is now 100.

** [2.0.2091] Previously, when "Late" data was detected, the ASAP Client would only report the time of the late data.  Now that time is reported along with the number of Minutes by which the data is "Late".

For example, if late data were received for 10:30 and the current time as 10:45 in the morning, "Time 10:30" is now reported as "Time 10:30+15".

This indicates that the last time the ASAP Client received data from an object was 10:30 in the morning, and the +15 clarifies the fact that the data is 15 minutes late. In other words, the current time is now 10:30+15=10:45, and the data is 15 minutes "late".

** [2.0.2091] Previously, Client/Server EDL entity Version checking was not performed. Now, version checking is performed whenever the ASAP CI displays the EDL Entity version of the form "Vn.ymmdd" in the first column of the heading of the output for an entity.

When the version string is present in the CI output, the ASAP Client compares the Server EDL Entity version with the Client EDL entity version. If the entity versions match, normal Client operation continues.  However, if entity definition versions do not match, the client will issue a warning dialog indicating the Entity EDL versions for the Client and Server do not match.  The user can then decide whether to continue or abort monitoring.

Notes:

1) Version checks are performed for both System entities and user defined entities. However, version checks are only performed if EDL Entity statements include a Version string property.

2) Version checks are only performed if both the Client and the Server have the an Entity Version string defined.  If either the Client or Server Entity definition does not have a version string defined for that entity, then version checking is suppressed for that entity (this provides a way to suppress version checking for an entity).

3) The display of an Entity Version string is a function of each ASAP CI command. Stated differently, in order for versioning to work, each entity command must include support for the display of the EDL Entity Version string in the command heading.

** [2.0.2091] Previously, when the grid portion of the ASAP Browse window had any column widths resized, ASAP would revert to the old column widths whenever the grid was refreshed. Now, the resized column width is retained for the duration of the ASAP Session.

** [2.0.2091] Previously, the OSC window did not use the FONT BOLD property from the FONT tab of the ASAP Properties window. This problem has been corrected.

** [2.0.2091] Previously, Graph Object History for APP entity didn't work right because SampleCmdMacro didn't reformat the entity command properly.  This problem has been corrected.

** [2.0.2090] Previously, OSC columns could not be re-ordered. Now you can reorder OSC columns by dragging and dropping a column heading.

** [2.0.2090] Previously, the OSC Reason column was the rightmost column, now it is positioned immediately after the Domain-Name column. Note you can reorder OSC columns by dragging and dropping a column heading.

** [2.0.2090] Previously, OSC multi-select mouse click avalanches caused excessive PC cpu usage. A click avalanche detector, now prevents this problem.

** [2.0.2090] Previously, on shutdown the OSC window did not unload until Windows 2000 garbage collection occurred.  ASAP now immediately unloads the OSC window on shutdown.

** [2.0.2089] Previously, when a log item in the OSC window was double clicked, the Browse Node Drop-Down contained a node name that was inadvertently upcased. This problem has been corrected.

** [2.0.2089] Previously, when the Browse window was restored and the OSC window was minimized, the OSC window should have also been restored. This problem has been corrected.

** [2.0.2089] Previously, when the Browse window Object-Domain drop-down was resized the EDL progress bar was not moved. This problem has been corrected.

** [2.0.2089] Previously, the maximum number entities that could be displayed in the OSC scoreboard was 10.  This limit has been removed.

** [2.0.2088] Previously, if an EDL error occurred during startup not enough error detail was displayed.  Now ASAP always provides detailed information about the EDL line and syntax element in error.

** [2.0.2088] Previously, in ASAP2SYS all StatePair attributes had their StateRule set to UseThresholds. Now only attributes with scalar values have their initial default as UseThresholds.  All other StatePair attributes have StateRule set to UseStateGraphState.  Note you can change the StateRule via the ASAP Properties window.

** [2.0.2088] Previously, in ASAP2SYS certain Process selected entity headings were not left aligned for the fields that contained left aligned data. This problem has been corrected by using the ALIGN attribute property for the Process Name, and Program File Name attribute definitions.

** [2.0.2060] A slow Windows memory leak has been corrected.  This leak was caused by a problem in the Microsoft Visual Studio runtime library.  It occurred on Double Byte Character versions of Microsoft Windows, eg Japanese, Chinese, Korean, ...

This problem is identified in the Microsoft support data base as MS Case SRX-000905602446. The case is also known in the Genesis data base as Solution 10-000 831 0034.

** [2.0.2060] Previously, a null filename could be entered in the in Object Filename field of the SSG Advanced dialog.  This problem has been corrected.

** [2.0.2050] Previously, the popup menu "Show Related Objectives" did not do a RANK ..., LIST command. This problem has been corrected.

** [2.0.2050] Previously, the popup menu "Show Related Objectives" was only enabled for the APP entity. Now this menu item is enabled for all entity types.

** [2.0.2050] Previously, the Client EDL Compiler did not check for duplicate attribute names or headings.  Duplicate attribute names or headings are now treated as a grammar error.  The compiler now reports these as a syntax error.

** [2.0.2049] Previously, the Stop EDL compile toolbar button on the EDL IDE window did not stop the compile.  This problem has been corrected.

** [2.0.2049] Previously, the Icons directory path label was truncated when the Icon directory path name was a very long name.  This problem has been corrected.

** [2.0.2048] Previously, the path used for nested INCLUDE statements was based relative to the ASAP\EDL directory.  Now PC File names that contain no path information will use the parent file's directory path instead of always referring back to the ASAP\EDL path. Example:

INCLUDE C:\EDLs\UserEntity\Funds
INCLUDE North.EDL
INCLUDE South.EDL

Will include the following:
C:\EDLs\UserEntity\North.EDL
C:\EDLs\UserEntity\South.EDL

** [2.0.2048] Previously, blanks were not allowed in include file names.  Now you can place quotes around an include file name, and the compiler will allow blanks within the quoted include name.

** [2.0.2047] Previously, the EDL compiler did not look ahead far enough when parsing large amounts of whitespace in an EDL source file.  This problem has been corrected.

** [2.0.2047] Previously, the PRINT menu function under the FILE... menu in the ASAP Browse window did not print correctly.  This problem has been corrected.

** [2.0.2046] Previously, the initial Browse window width for low density screen settings such as 1024 x 768, might be less that the maximum width of the browse window Toolbar.  This caused certain toolbar buttons to be hidden.  This problem has been corrected.

** [2.0.2047] Previously, for an interactive heading rename the "dirty attribute" flag was not being set.  The result was that the EDL was not updated when you clicked OK or APPLY.  Now when you double click an attribute name on the Attribute Tab of the Properties window, and rename the property, the dirty flag is set properly.

** [2.0.2001] Previously, the statistics sample time might not be synchronized to the host time, if one and only one entity was enabled.  For example, if only the App entity were enabled, the Client sample timer might not be in sync with the host update. It was also possible for the host sample time to be a few seconds late when multiple entities were enabled. Both problems have been corrected.

** [2.0.1004] Previously, the max late Time for graphed attributes was 2 x Rate, no matter how large the sample interval.  Thus, if the Rate were 10 minutes, it could take up to 20 minutes to detect that data was late.  Now max late cannot exceed five minutes, regardless of the host sample interval value, and as a result the "late" late problem has been corrected.

Known Problems Remaining:

** None