Patch Name: PHSS_20496 Patch Description: s700_800 10.20 PerfView C.01.00/C.01.00.01 cumulative Creation Date: 99/12/16 Post Date: 00/01/19 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: PerfView C.01.00 C.01.00.01 Filesets: PerfView.PV PerfView.PV-PLATFORM-HP Automatic Reboot?: No Status: General Release Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_20496 Symptoms: PHSS_20496: SR 5003447581 / RPMmb00398: Data seems to change when zooming in on PerfView graphs for some DSI datasources. When the "Points Every" setting is changed to 5 minutes, the graph becomes truncated to the right even though there is more data. SR 8606109659 / JAGab82359: The number of data sources to which you can connect is limited to 128. SR 8606113870 / JAGac12390: PerfView may exit when you draw more than one Class Compare or a Class Detail graph. PHSS_19657: SR 5003447581 / RPMmb00398: PerfView does not draw the graph correctly when the frequency of collecting DSI data is set to less than once every 5 minutes. SR 5003455477 / RPMlj01785: Printing from PerfView using DAZEL spooler is not supported. SR 5003467571 / RPMlj02099: PerfView aborts when zooming in on the right-most part of the graph. SR D500422741 / RPMmb00365: PerfView versions C.01.00 and C.00.01 do not support PA-RISC 1.0. SR H553000012 / RPMmb00431: PerfView aborts when trying to connect to MWA with transaction names longer than 60 characters. Defect Description: PHSS_20496: SR 5003447581: DDTS RPMmb00398: The fix for problems caused by the collecting of DSI data was removed with this patch. An extensive description of the duplicate timestamps problem with possible workarounds is described in this section. DSI logfiles should contain one row of summarized data metrics per each summarization interval. The problem is caused when DSI logfiles contain multiple rows per summarization interval. An example of a DSI logfile that exhibits the problem, with a summarization interval of 5 minutes (RECORDS PER HOUR 12), exporting the data (extract -xp): DATE & TIME size in KB used in KB free in KB 08/14/99 03:15:00 1018382 593436 363844 08/14/99 03:15:00 1018382 593436 363844 08/14/99 03:20:00 1018382 593436 363844 08/14/99 03:20:00 1018382 593436 363844 Possible causes and corrections for this problem: 1. Execution of a new dsilog process for each arriving input data row. The dsilog code is designed to receive a continuous stream of data rows as input. This stream of input is summarized by dsilog according to the specification directives for each class, and one summarized data row is logged per requested summarization interval. However, some scripts are coded in such a way so as to execute a new dsilog process for each arriving input row. Example: ------------ Begin example script code ----------------- while : do feed_one_data_row | dsilog sdlname classname sleep 50 done ---------------- End example script code ----------------- Workaround: =========== Re-write the script code so that one dsilog process receives a continuous stream of input data, for example: --------------- Begin example script code --------------- # Begin data feed function feed_one_data_row() { while : do # Perform whatever operations necessary to produce one # row for feed to a dsilog processof data sleep 50 done } # End data feed function # Script mainline code feed_one_data_row | dsilog sdlname classname --------------- End example script code ----------------- 2. The problem with DSI logs can also occur when: a.) The data feed to dsilog contains a timestamp, and dsilog is being run with the "-timestamp" option. AND b.) The "-s 0" option is used to suppress dsilog summarization. Workaround: =========== When feeding timestamped data to dsilog with the "-timestamp" option, do not use the "-s 0" option. 3. To correct a DSI logfile set that contains multiple rows of data per summarization interval, create an "input file" from the existing DSI logfile set and then use dsilog to re-create the DSI logfile set from the input file, summarizing the data without duplicates): a.) Stop the DSI logging process and associated rep_server process. b.) Create a new "input file" using the following syntax: extract -xp -l sdlname -C classname detail -ut -h -f \ filename Create a unique input file for each data class associated with the DSI logfile set. c.) Back up the DSI logfile set. d.) Remove the DSI logfile set with the following syntax: sdlutil sdlname -rm all e.) Recreate the DSI logfile set with the following syntax: sdlcomp specfile_name sdlname Run sdlcomp as many times as necessary with unique specfiles to recreate each data class associated with the DSI logfile set. f.) Reload the data for each class with the following syntax: dsilog sdlname classname -i filename -timestamp NOTE: the "-timestamp" option is critical for this to work correctly. g.) Correct the data feed to dsilog as indicated above before restarting logging. SR 8606109659: DDTS JAGab82359: You can now connect to 1024 data sources. SR 8606113870: DDTS JAGac12390: You can now draw more than one Class Compare or a Class Detail graph. This will no longer cause PerfView to exit. PHSS_19657: SR 5003447581: DDTS RPMmb00398: MeasureWare's measurement interval of DSI data sampling is once every 5 minutes. To avoid aborting, set the frequency of collecting data in the class specification file to 5 or more minutes by setting the RECORD PER HOUR to 12 or less. SR 5003455477: DDTS RPMlj01785: Command Line field was added to the Setup Printer window, into which you can enter switches to enable printing from PerfView using the DAZEL spooler. When you set up printers, type the commands you want to be executed when printing into the Command Line field. When the Command Line field is not empty, all other buttons, except Color and Pattern, are disabled. Command line strings: - string will be replaced with the name of the selected printer. Instead of this string you can also enter the name of the printer. - string will be replaced with the file PerfView automatically generates. If you don't enter this string, the file will be appended to the end of the command line. Note: If you are using lp spooler, you must enter the -c switch. Example: lp -c -d Commands you type in the Command Line field will be saved together with the printer information. SR 5003467571: DDTS RPMlj02099: PerfView no longer aborts when zooming in on the right-most part of the graph. SR D500422741: DDTS RPMmb00365: Only PA-RISC 1.1 was supported with PerfView versions C.01.00 and C.00.01. With this patch PA-RISC 1.0 is supported. SR H553000012: DDTS RPMmb00431: To avoid aborting when PerfView is trying to connect to MWA with transaction names longer than 60 characters, drill down to transaction is disabled in the Drill Down window. SR: 5003447581 5003455477 5003467571 D500422741 H553000012 8606109659 8606113870 Patch Files: /opt/perf/bin/pv /opt/perf/bin/pvalarmd /opt/perf/bin/pvcomm /opt/perf/bin/repinfo /opt/perf/bin/pvprinters.sh /opt/perf/lib/nls/msg/C/pvmsgs what(1) Output: /opt/perf/bin/pv: pv C.01.03.01 12/16/99 HP-UX 10.20+ =*= /opt/perf/bin/pvalarmd: pvalarmd C.01.03.01 12/16/99 HP-UX 10.20+ =*= /opt/perf/bin/pvcomm: pvcomm C.01.03.01 12/16/99 HP-UX 10.20+ =*= /opt/perf/bin/repinfo: repinfo C.01.03.01 12/16/99 HP-UX 10.20+ =*= /opt/perf/bin/pvprinters.sh: pvprinters.sh C.01.03.01 09/22/99 =*= /opt/perf/lib/nls/msg/C/pvmsgs: None cksum(1) Output: 2854315137 4734468 /opt/perf/bin/pv 1188168987 597031 /opt/perf/bin/pvalarmd 4205305840 724272 /opt/perf/bin/pvcomm 3494414594 321392 /opt/perf/bin/repinfo 220899184 2887 /opt/perf/bin/pvprinters.sh 912233630 45811 /opt/perf/lib/nls/msg/C/pvmsgs Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_19657 Equivalent Patches: PHSS_19676: s700: 11.00 s800: 11.00 Patch Package Size: 6340 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_20496 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_20496.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_20496. 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_20496.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_20496.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None