Patch Name: PHSS_16640 Patch Description: s700_800 10.20 PerfView cumulative patch Creation Date: 98/10/29 Post Date: 98/11/05 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: PerfView C.00.04 Filesets: PerfView.PV Automatic Reboot?: No Status: General Release Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_16640 Symptoms: PHSS_16640: Multiple symptoms are fixed with this patch: 1. The begin date switch is ignored for PerfView batch execution when the metric switch is also used. 2. When using the command line or command files to draw a graph in batch mode, and when only the ending date is specified (no beginning date is specified), the range of dates displayed is incorrect. 3. PerfView can terminate abnormally when attempting to draw an Application History graph when connected to data sources with a large number of instances. 4. PerfView can terminate abnormally when connecting to a data source that has a large number of instances. 5. PerfView can terminate abnormally when attempting to draw a System Compare graph when connected to data sources with a large number of instances. 6. PerfView terminates abnormally with the message, "attempted to set Doodad timer twice" when two or three mouse buttons are pressed simultaneously over a PerfView scrollbar (either vertical or horizontal). 7. Memory leaks when displaying graphs and drilling down on data of logs with large number of instances, which can cause PerfView to terminate abnormally. PHSS_15575: Multiple symptoms are fixed with this patch: 1. PerfView terminates abnormally when drawing a PerfView graph from a MeasureWare system that has a large number of disks. 2. Expanding a PerfView graph to the left using the left double arrow on the scroll bar causes data to display on the graph as 10 times greater than their actual values. Tabular (drill-down) data displays accurately. 3. If the total number of systems is exactly 198, 298, or a higher number ending in 98, PerfView terminates abnormally on startup. 4. For System Compare, Class Compare, Class Detail, and Create Graph, customer would like text to display in alphabetical order in the Class List, Instance List, and Metric List windows. 5. PerfView takes a long time to connect. 6. DCE times out when PerfView connects to MeasureWare Agent. 7. Under certain specific conditions, PerfView terminates abnormally when you zoom in on the right-most portion of a graph after the graph has been updated since it initially displayed. 8. PerfView terminates abnormally after clicking on a Help menu item twice in succession or after closing Help using the Enter key. 9. Under certain conditions, PerfView graphs truncate if both Exclude Weekends and Exclude Holidays are selected and no shifts are selected. Tabular (drilldown) data displays accurately. 10. Error message 12-5, indicating that the requested metrics are not available on the data source, does not display immediately if you save a Class Compare graph, then open it from another system that does not have those metrics. 11. In some cases, PerfView can terminate abnormally if you have deleted all log files before starting PerfView. Defect Description: PHSS_16640: The following defect descriptions are for PHSS_16640: 1. PerfView did not start the graph on the correct date under certain specific circumstances. This problem was solved by changing the code so that the first date of the graph is correct. 2. PerfView did not start the graph on the correct date under certain specific circumstances. This problem was solved by changing the code so that the first date of the graph is correct. 3. PerfView had very high memory requirements for Application History graphs with many instances in a class. These memory requirements have been reduced. 4. PerfView had very high memory requirements for connecting to data sources with many instances in a class. These memory requirements have been reduced. Code has been changed to: - establish a default maximum number of instances - allow users to override the default limit as necessary - significantly reduce the memory required to connect to data sources with large numbers of instances - improve the data connection speed for data sources with many instances Additionally, memory checks have been added. 5. PerfView terminated abnormally when attempting to draw a System Compare graph for systems that had large numbers of class instances. These memory requirements have been reduced. 6. PerfView could not accommodate multiple simultaneous mouse clicks. The code has been changed so that simultaneous mouse clicks do not cause PerfView to terminate abnormally. 7. PerfView memory leaks were causing it to terminate abnormally. These leaks were particularly noticeable when drawing the System Compare, Class Compare, and Class Detail graphs, and when displaying drill down windows. PHSS_15575: The following defect descriptions are for PHSS_15575: 1. PerfView could not correctly graph more than 512 metrics. This problem was solved by changing the code that displays graphs so that PerfView can accommodate a greater number of metrics. 2. PerfView went into an incorrect state. Code has been changed so that this state is avoided. 3. The array processes associated with sorting systems were not correctly handling such total numbers of systems. Code changes were made so that PerfView can now accommodate these total numbers of systems. 4. Code has been changed so that in System Compare, Class Compare, Class Detail, and Create Graph, the Class List, Instance List, and Metric List windows display text in alphabetical order. One side effect of this change is that for DSI data sources only, the column order of Drill Down Numbers and Drill Down Class data will change: - For DSI data sources, Drill Down Numbers data will show columns in alphabetical order - For DSI data sources, Drill Down Class data (for example, Global) will show columns in the order that MeasureWare passes the data to PerfView 5. If the log files are large, it can take a long time for PerfView to connect to MeasureWare. PerfView was doubling this connect time by making an unnecessary call for information. This PerfView call has been eliminated. 6. We have increased the default time-out value and thus PerfView will wait longer for the connection to MeasureWare to succeed. 7. This problem was reproducible under these conditions: A graph was produced for a summarization level of 3 or 6 hours that occurred after 1 p.m. but before 3 p.m., you scrolled all the way to right, allowed graph information to update at the time of the summarization interval, and then attempted to zoom in on the right-most portion of the graph. PerfView would terminate abnormally. The code was changed so that when graph information updates, PerfView now redisplays the graph in its original state, allowing the zoom feature to function correctly. 8. This is a defect in HyperHelp, the help-system software. The HyperHelp manufacturer has been contacted about fixing the problem. There is no workaround for the first problem, clicking on a Help menu item in succession. If you mistakenly click Enter to close Help, directly after clicking Enter you can execute the following command from the UNIX shell prompt: xprop -root -remove HyperHelpAtomV40 This will prevent PerfView from terminating abnormally. If you execute the above command and more than one PerfView is running, the other PerfView(s) starts up HyperHelp. Note: The correct way to close Help windows is to choose Close from the pull down menu. 9. This problem occurred under the following circumstances: 1) you excluded weekends and holidays from the graph, 2) you did not specify a shift for either the Start date or Stop date, and, 3) you specified at least two holidays, one or more of which was at least one month prior to the Start date, and one or more of which was after the date range specified. PerfView did not correctly handle the excluded holidays and thus did not display all data on the graph. The code has been fixed so that data displays accurately. 10. PerfView erroneously displayed a Class List or Instance List window, even though metrics were not available for the data source. The code has been changed so that Error Message 12-5, "Requested Metrics not available from data source" displays in such instances. 11. PerfView was unable to correctly process information when no data had been logged in the log file. The code has been fixed so that PerfView can display even though the log files contain no data. SR: D500350868 D500350561 D500355214 5003379867 D500358325 D500359208 D500368498 D500356147 1653241208 D500369082 D500365940 D500357509 5003430777 D500382523 D500380030 D500389718 5003415075 D500390898 Patch Files: /opt/perf/bin/pv /opt/perf/bin/pvsysdb what(1) Output: /opt/perf/bin/pv: pv C.00.08 10/28/98 HP-UX 10.10+ =*= /opt/perf/bin/pvsysdb: pvsysdb C.00.08 10/28/98 HP-UX 10.10+ =*= cksum(1) Output: 3698933666 4135922 /opt/perf/bin/pv 1933988323 489835 /opt/perf/bin/pvsysdb Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_15575 Equivalent Patches: PHSS_16641: s700: 11.00 s800: 11.00 Patch Package Size: 4580 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_16640 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_16640.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHSS_16640.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_16640. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHSS_16640.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_16640.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None