HP Performance Collection Software User's Manual (for MPE Systems) ABCDE HP Part No. 50700-90022 Printed in U.S.A.
Notice Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and tness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard.
Printing History Updates are new editions or complete revisions of the manual. A software code may be printed before the date; this indicates the version level of the software product at the time the manual was issued. Many product updates and xes do not require manual changes and, conversely, manual corrections may be done without accompanying product changes. Therefore, do not expect a one-to-one correspondence between product updates and manual updates.
Introduction to Performance Collection Software The HP Performance Collection Software captures performance data from HP 3000 MPE V and MPE/iX computer systems. It logs this data automatically and continuously while consuming only minimal system resources. The rich detail of the collected data allows for short term performance diagnosis while the compact storage allows long term trending from a single data source.
Related Documents User information for HP LaserRX/MPE consists of the data analysis and display documentation included with your PC software and the Performance Collection Software manual included with your host software. Each manual is described brie y below: For HP LaserRX/MPE users: HP LaserRX/MPE User's Manual: Analysis Software describes how to analyze performance data using your PC.1 HP Performance Collection Software User's Manual (for MPE Systems) describes the HP 3000 software.
More about the Collection Software User's Manual The HP Performance Collection Software has three components: SCOPE (or SCOPEXL, if you are using an MPE/iX system), UTILITY, and EXTRACT. SCOPE(XL) is the performance data collector for MPE Systems. It continuously collects and summarizes performance data. UTILITY and EXTRACT are the host programs that let you interact with SCOPE(XL) and manage the data that it collects.
Conventions Used in this Manual Computer font Italics UPPERCASE 45 4Return5 or 4Enter5 Represents screen text, including prompts and messages appearing on the screen. Identi es variable parameter values in command syntax statements. Identi es commands and parameters that are to be entered exactly as shown in command syntax statements. It also identi es the names of reference programs, commands, and les. Uppercase is also used to reference program, command, and le names.
Within Syntax Statements Within Syntax Statements fg [] Punctuation [ ... ] viii Braces enclose required elements. When several elements are stacked within braces, you must select one. Brackets enclose optional items. When several elements are stacked within brackets, you can select any one element or none. Except for braces, brackets, and ellipses, all punctuation characters must be entered exactly as shown.
Within Syntax Statements Using This Manual This manual is designed to help you begin to use the Performance Collection Software and to support your continued use. Chapter 1 Installing HP Performance Collection Software Describes hardware and software requirements, and explains how to install or update Performance Collection Software on your host system.
Within Syntax Statements Chapter 8 Appendix A Appendix B Appendix C Glossary x What's New|Changes to Performance Collection Software Describes changes made to the software since version A of the HP LaserRX/MPE release. MPE/iX Metric Information Gives additional metric information for MPE/iX users. Service Level Agreements Describes the Service Level (SLA) enhancement to the SCOPEXL performance data collection program.
1 Installing HP Performance Collection Software Introduction This chapter tells you how to install the HP Performance Collection Software on an HP 3000 MPE V or MPE/iX system. Whether you are a new or existing user of HP Performance Collection Software you should follow these instructions to install or update Performance Collection Software on your HP 3000 system (or systems). What You Will Need This section describes the hardware and software requirements for the HP 3000 system.
Within Syntax Statements Software Requirements To be able to run Performance Collection Software, your HP 3000 must have the following software installed: One of the following: 3 MPE V G.03.02 (V-Delta-2 MIT) or later (for MPE V systems). or 3 MPE/iX release A.41.00 (2.1) or later (for MPE/iX systems). Local Area Network software, if you use this type of network connection when running the HP LaserRX/MPE analysis software.
Within Syntax Statements Installing or Updating Performance Collection Software Starting with MPE/iX release B.40.00 (4.0) and MPE V release G.23.00 (23), the Performance Collection Software is installed as part of the normal operating system update process. Installation Instructions for first time installations 1. Consider Security and Accounting requirements. Performance Collection Software program les are installed in the SCOPE.SYS group.
Within Syntax Statements A system identi cation record may occur anywhere in the le but there should be only one such record. Any standard text editor may be used to edit the PARM le as long as the nal result is a standard ASCII le with records less than or equal to 100 characters wide. Example: :EDITOR TEXT PARM.SCOPE.SYS ADD .1 ID=HARVEY // KEEP PARM.SCOPE.SYS,unn You may check the validity of the PARM le if desired: :RUN UTILITY.SCOPE.SYS PARMFILE PARM.SCOPE.
Within Syntax Statements Update Instructions These instructions are for installations where previous versions of the Performance Collection Software or HP LaserRX/MPE host software were installed. If the previous release was B.00.00 or later then no further action is required in order to complete the update process. If the previous release was A.00.00 - A.99.99 then your existing log les must be converted to the \B" release format before they can be used.
Within Syntax Statements 4. Examine the SCOPEJOB.SCOPE.SYS job stream and insure it has a CONTINUE command prior to running the SCOPE or SCOPEXL program. This insures the rest of the job stream will be processed even if the collection software terminates abnormally. For MPE/iX systems: .. . !CONTINUE !RUN SCOPEXL.SCOPE.SYS .. . For MPE V systems: .. . !CONTINUE !RUN SCOPE.SCOPE.SYS .. . 5. Restart the performance collection software. :STREAM SCOPEJOB.SCOPE.
Within Syntax Statements If You Need Additional Help Resolving Incompatible Measurement Interface Versions If you try to start collecting data by running the SCOPEXL program, but you have installed the incorrect Performance Collection Software les on the host, you will get an error message similar to the following: ****************************************************** Potentially incompatible Measurement Interface versions exist between Scope/XL and this system. This is Scope/XL version B.06.
2 Performance Collection Software An Overview Introduction Performance Collection Software consists of four basic programs. This chapter discusses how these programs interact, describes the modes in which Performance Collection Software functions, and provides information about softkeys and native language support (special features of the UTILITY and EXTRACT programs). The basic programs are SCOPE (or SCOPEXL, depending on your system), SCOPE2 (or SCOPEXL2), UTILITY, and EXTRACT.
Within Syntax Statements Performance Collection Software Schematic The following schematic diagram shows the relationship between the di erent components of the Performance Collection Software system. The components comprising the host programs are shaded. Figure 2-1.
Within Syntax Statements The Host component contains the following programs and les: SCOPE or SCOPEXL Main performance data-collector program. SCOPE2 or SCOPEXL2 Disc space data-collector program. EXTRACT Program to extract selected data from log les. UTILITY Program to perform various utility functions. DATACOMM Library code to allow work stations to access host log les. PARM le User-generated parameter le that controls data collection. LOG . . . Log les that contain raw performance data.
Within Syntax Statements Caution The command-driven user interface and the new log le formats require that you alter your UTILITY and EXTRACT batch jobs, and that you convert existing log les to the new format. For these reasons, we strongly recommend that you review the information on the UTILITY and EXTRACT programs before you try to use the new versions. The operation of SCOPE(XL) has not changed. The batch job that runs the data collector should not require any changes.
Within Syntax Statements About Performance Collection Software Host Programs Based on the information the PARM le provides to SCOPE(XL), the collector program collects and summarizes system performance metrics, and writes these metrics to raw log les. Because SCOPE(XL) runs continuously, the UTILITY program provides a special set of commands to let you communicate with SCOPE(XL) while it is collecting data.
Within Syntax Statements There are two types of parameters|required parameters (for which there are no defaults) and optional parameters (for which defaults are provided). How Performance Collection Software handles these parameters depends on the mode in which it is running. Parameters in Interactive Mode If an optional parameter is not provided in interactive mode, the program will display the default parameter and let you either con rm it or override it.
Within Syntax Statements The rst parameter|GLOBAL|indicates the type of log le data to be resized. If you do not supply this parameter, the consequent action for interactive and batch users would be the following: Batch users. The batch job would terminate because this parameter has no default. Interactive users. You would be prompted to choose which type of log le data to resize to complete the command. The last parameter|YES|indicates that resizing will be performed unconditionally.
Within Syntax Statements Softkeys and Native Language Support This section explains two additional features of the Performance Collection Software EXTRACT and UTILITY programs: Softkeys. Native language support. Softkeys Most Hewlett-Packard terminals and terminal emulation programs support user-labeled softkeys. When you run EXTRACT or UTILITY, you can use these softkeys as shortcuts for entering frequently used commands.
Within Syntax Statements This is the most useful option, but it is also the most time consuming. Saving and restoring the original softkey information, however, takes only a few seconds and should not concern most users. Do not load or alter softkeys. Use this option with UTILITY or EXTRACT on non-Hewlett-Packard terminals or emulators that do not support the softkey feature.
Within Syntax Statements Performance Collection Software Host Programs The Performance Collection Software host programs are SCOPE(XL), SCOPE(XL)2, UTILITY, and EXTRACT. An overview of each is presented below. For detailed command descriptions, refer to chapters 3 (SCOPE), 4 (UTILITY), and 5 (EXTRACT).
Within Syntax Statements Application Summarized measurements of the processes in each user-de ned group (application) are logged to the le LOGAPPL once every 5 minutes. Users can de ne up to 15 applications on MPE V or 31 applications on MPE/iX. Performance Collection Software reserves an application called OTHER for recording all processes not included in other user-de ned applications. Process Summarized measurements of selected interesting processes are logged to the le LOGPROC once every minute.
Within Syntax Statements Indexing information Information used to rapidly access the log le data when retrieving information is maintained in the LOGINDX le on MPE/iX systems. On MPE V systems this information is kept in each of the other log les so the LOGINDX le is not needed. Caution Never modify the LOGINDX le! You can control how much process history you keep on disc by adjusting the size of each log le with the UTILITY program (see chapter 4). Data collection does not stop when a log le is full.
Within Syntax Statements When to Stop SCOPE(XL) SCOPE(XL) should run continuously. Stop it only under the following conditions: You are shutting down your system. You are updating the Performance Collection Software host software to a new release. You are changing the size of a Performance Collection Software log le. You are performing a system backup and want to include the Performance Collection Software log les.
Within Syntax Statements You can stream SCOPEJOB whenever you want to initiate SCOPE(XL) by including it in your own startup procedure that is executed each time the system comes up. If you restart SCOPE(XL), Performance Collection Software continues to use the same log les and appends new records to the end of the le. If you restart SCOPE(XL) while it is already running, the second SCOPE(XL) job will terminate immediately.
Within Syntax Statements Introduction to UTILITY The UTILITY program serves as a tool for managing and reporting information on log les. The program also lets you display the versions of Performance Collection Software host programs and libraries being used, and control the SCOPE(XL) collection program as it runs. UTILITY Commands UTILITY can be used in either an interactive or a batch mode. Brief descriptions of the major functions are given below.
Within Syntax Statements PARMFILE RESIZE SCAN SCOPE VERSIONS 2-16 Checks the syntax of a Performance Collection Software PARM le and reports any warnings or errors. Resizes Performance Collection Software raw log les (LOGGLOB, LOGAPPL, LOGPROC, and LOGDISC). The RESIZE command requires that a log le be opened. UTILITY is the only program you can use to resize raw log les.
Within Syntax Statements Introduction to EXTRACT The EXTRACT program is a key part of Performance Collection Software data analysis and archiving procedures. The program creates an extracted le that can be either kept on the host system as a remote le or transferred to a PC for local analysis. It can be used in either an interactive or a batch mode. You can extract data without interrupting data collection.
Within Syntax Statements Appending Data to an Existing File You can use EXTRACT to append data to the end of an existing extracted log le, but you will be forced to continue the same data types, subsetting, and summarization used in the initial extraction. The ability to append data to an extracted log le is valuable for archiving log les. You can use extracted log les for archiving Performance Collection Software data in an easily accessible form or for transporting data between systems.
3 Data Collection: SCOPE This chapter details the SCOPE(XL) PARM le directives. It includes a summary of the directives, information on how to change a directive, directions on how to start and stop SCOPE(XL), and an alphabetized reference section. Note Performance Collection Software directives and parameters can be entered through any combination of uppercase and lowercase letters. Only the rst three characters are required. For example, the APPLICATION directive can be abbreviated as APP. The le PARM.
Within Syntax Statements Syntax Summary The following table summarizes PARM le directive syntax. Table 3-1.
Within Syntax Statements Table 3-1. Parameters of Collection Directives (continued) Directive Parameter SERVICE LEVEL SLA FIRST=seconds RESPONSE=seconds ALARM alarmid IF itemid (<,>,<=,>=) itemid FOR duration [MINUTES] THEN alarm action FINISH alarm action REPEAT minimum repeat minutes VAR itemid (+,0,/, 3) itemid DISCGROUP discgroup name GROUP= groupname [,groupname , . . .
Within Syntax Statements If the PARM le is not found in the logon group of the user who is running SCOPE(XL) or a parameter is not speci ed, the default parameters for each directive are used. The directives and their default parameter values are shown in Table 3-2. Table 3-2. Default Parameter Values for Collection Directives Directive Default Parameter Value ID Blanks, the HPTrend system handle, or, if present on an MPE/iX system, the HPSYSNAME system variable.
Within Syntax Statements Modifying Directives You can use a text editor to create or modify PARM.SCOPE.SYS. The following rules and conventions apply: Specify a directive only if you want to override a default parameter. Begin each line in the PARM le with a PARM le directive. PARM le values cannot be entered by themselves. Enter the directives into the PARM le in any order. Order is not important, with the following exceptions: If a directive is entered more than once, the last one entered is used.
Within Syntax Statements Starting SCOPE(XL) Start SCOPE(XL) by streaming the job SCOPEJOB.SCOPE.SYS. Do this by typing the following: STREAM SCOPEJOB.SCOPE.SYS Stopping SCOPE(XL) There are three ways to stop SCOPE(XL) from collecting data: Log on as MANAGER.SYS and run the UTILITY program. Issue the following command: SCOPE KILL You will be asked to con rm your request to stop SCOPE(XL). If you con rm, UTILITY issues a programmatic command to stop data collection.
Within Syntax Statements Reminder Hint SCOPE(XL) should run continuously. You should only stop it if you are preparing to shut down your system, updating the Performance Collection Software host software to a new release, changing the size of a Performance Collection Software log le, or performing a system backup and want to include the Performance Collection Software log les.
Within Syntax Statements ALARM TYPE=typeid ALARM alarmid SEVERITY=severity number The following directives and parameters are discussed in chapter 7: alarmid typeid severity number IF itemid condition itemid FOR duration [MINUTES] THEN alarm action FINISH alarm action REPEAT minimum repeat minutes VAR itemid operator itemid 3-8 Data Collection: SCOPE
Within Syntax Statements APPLICATION APPLICATION FILE= 2 8 lename INTERACTIVE= BATCH= 2 application name 3 2 lename lename 3 3 2 USER= job/session name, 2 QUEUE execution priority OR SERVICE LEVEL 9 38 username.acctname 92 ,groupname 3 3 FIRST=seconds RESPONSE=seconds where: The application name parameter identi es an application that groups multiple program les together and reports on their combined activities.
Within Syntax Statements The parameters for application de nitions fall into three categories: File name: FILE INTERACTIVE BATCH User logon: Execution priority: USER QUEUE If a parameter from a category is used in an application de nition, a process will not belong to that application unless a match for that category is made. If no parameters in a category are used in an application de nition, then a process does not have to match that category.
Within Syntax Statements If a process le is included in more than one application, it is logged in the rst application in which it is de ned. APPLICATION=Order Processing FILE=@.@.OFICPROD,@.@.PAPRPROD,@.@.SUPPLIES APPLICATION=Office Products FILE=@.FURNITUR.OFICPROD,@.ELECTRON.OFICPROD Since @.@.OFICPROD is included in Order Processing, any programs in @.FURNITUR.OFICPROD or @.ELECTRON.OFICPROD will be logged in the Order Processing application, not in O ce Products.
Within Syntax Statements A partially-quali ed le name. For example, SPOOK5 In this case, all groups and all accounts are assumed (SPOOK5.@.@). Multiple le names can be entered on the same line, separated by commas, or in separate FILE parameters. lename The INTERACTIVE parameter acts the same as the FILE parameter except it signi es that only interactive executions of the program (sessions) are included in the application class.
Within Syntax Statements group The groupname speci es the logon group of a particular job or session. It is optional, but if it is included, it must be preceded immediately by a comma. If this parameter is not supplied, all logon group names are matched. Note Since commas are allowed within the parameter string in the USER parameter, they cannot be used to separate one logon string from another.
Within Syntax Statements for a process during the 1-minute sample interval is assumed to have occurred in the new queue and as such is attributed to the application that matches the process at the end of each 1-minute sample interval. OR Use the OR parameter to allow more than one application de nition to apply to the same application. Within a single application de nition, a process must match at least one of each category of parameters.
Within Syntax Statements Sample Application Definition The following is an example of how an application can be de ned: APPLICATION=Program Development INTERACTIVE=EDITOR.PUB.SYS, QEDIT.@.@, VOODOO#, TDP USER=@.TEST @.@,TESTGROUP LABTEST,@.@ SERVICE LEVEL FIRST=1.0 APPLICATION=Other Editors FILE=EDITOR.PUB.SYS, QEDIT.@.@, VOODOO#, TDP APPLICATION=Compilers FILE=COBOL@.PUB.SYS,FORTRAN.PUB.SYS,FTN@.PUB.SYS FILE=PASCAL.PUB.SYS, SPL.PUB.SYS, RPG.PUB.SYS APPLICATION=HP Products FILE=@.PUB.
Within Syntax Statements DAILYTIME 2 DAILYTIME hour :minute 3 where hour is a one- or two-digit number from 1 to 24, and minute is a two-digit number from 00 to 59. Specify the time in a 24-hour-clock format: midnight=00:00 and noon=12:00. The default time for daily collections is DAILYTIME 23:30 (The time, 23:30, is 11:30 pm.) The DAILYTIME directive sets the time for the daily data collection. Certain types of data, such as disc space, are only sampled and logged once a day.
Within Syntax Statements DISCGROUP 8 DISCGROUP= discgroup name 9 The following related parameter is also discussed in this section: 8 GROUP= groupname 9 The DISCGROUP directive de nes a set of MPE ACCOUNTS and GROUPS that will have their disc space usage reported as a unit under the assigned disc group name. The disc group name can be up to 8 characters long and can contain uppercase and lowercase alphanumeric characters. A maximum of 20 disc groups can be de ned.
Within Syntax Statements GROUP 8 2 GROUP= groupname ,groupname, . . . 39 The GROUP parameter lets you specify the MPE ACCOUNTS and GROUPS that are to be included in the set. You can only use GROUP if it is preceded by the DISCGROUP directive. The following are valid groupnames : Simple, fully-quali ed MPE GROUP names, such as PUB.SYS Generic GROUP names, such as WORK#.@ Partially-quali ed GROUP names, such as: PUB In this case, the PUB GROUP in all accounts is assumed (PUB.@).
Within Syntax Statements ID 2 ID= system id 3 where system id is a string of up to 40 characters that identi es your system. If you have multiple systems, use di erent ID strings for each one. The rst 10 characters are displayed on Performance Collection Software graphs. The default for ID is all spaces, with the following exceptions: If HPTrend is con gured on the system, the default is the HPTrend system handle.
Within Syntax Statements LOG 2 LOG GLOBAL 32 APPLICATION 32 PROCESS 32 DISCSPACE 3 The default is LOG GLOBAL PROCESS. GLOBAL If GLOBAL is speci ed, global records are written to the LOGGLOB log le. APPLICATION If APPLICATION is speci ed, application records are written to the LOGAPPL log le. PROCESS If PROCESS is speci ed, interesting processes are written to the LOGPROC log le.
Within Syntax Statements MAINTTIME 2 MAINTTIME hour :minute 3 where hour is a one- or two-digit number from 1 to 24, and minute is a two-digit number from 00 to 59. Specify the time in a 24-hour-clock format with midnight=00:00 and noon=12:00. As the default, daily scheduled maintenance will not be performed. The MAINTTIME directive sets the time for daily maintenance procedures.
Within Syntax Statements THRESHOLD 2 3 CPU=percent 7 6 DISC=rate 7 6 7 6 RESPONSE= seconds 7 6 7 6 7 6 FIRST=seconds 7 6 TRANSACTIONS= count 7 6 THRESHOLD 6 7 7 6 NONEW 7 6 7 6 NOKILLED 3 7 2 6 7 6 NOSHORT =seconds 7 6 5 4 MINTHINK= seconds MAXTHINK=seconds The parameters for THRESHOLD can be entered on the same line (separated by commas) or on separate THRESHOLD lines. The default for THRESHOLD is the following: THRESHOLD CPU=10.0, DISC=10.0, RESPONSE=5.0, FIRST=1.
Within Syntax Statements rate Rate (1{32767) signi es the disc I/O rate in transfers per second. The DISC parameter sets the rate of physical disc I/Os that a process must exceed to become interesting and be logged. For example, DISC=8.0 indicates a process will be logged if it exceeds an average of 8 disc I/Os per second in a 1-minute sample interval. DISC= seconds Seconds (0.1{32767) signi es terminal response time.
Within Syntax Statements count Count (0{32767) signi es the number of terminal transactions. The TRANSACTIONS parameter causes any process that completed more than the speci ed number of terminal transactions during a 1-minute sample to become interesting and be logged. For example, TRANSACTIONS=85 indicates a process will be logged if it exceeds 85 transactions in a 1-minute sample interval.
Within Syntax Statements Use the NOSHORT parameter to reduce the amount of disc space required to hold process information when many short-duration processes are executed. If you use NOSHORT instead of NONEW and NOKILLED, you can eliminate short processes from the log le while still logging the start and stop of longer-running processes. seconds The range for the MINTHINK value is 0.001{60.000 seconds. The MINTHINK parameter sets a lter used in calculating terminal response times.
Within Syntax Statements seconds The range for the MAXTHINK value is 0{86400 seconds (24 hours). The MAXTHINK parameter sets a lter used in calculating terminal response times. Any terminal transaction having a think time greater than the MAXTHINK setting is ignored. All times involved with this transaction (think time, time-to- rst response, and response time) are discarded and a new transaction is begun.
Within Syntax Statements WAIT THRESHOLD 2 3 CPU=percent 6 DISC=percent 7 7 WAIT THRESHOLD 6 4 MEMORY=percent 5 IMPEDE=percent where percent indicates the portion of the 1-minute sample interval during which the process was waiting. The default for WAIT THRESHOLD is the following: WAIT THRESHOLD CPU=50, DISC=50, MEMORY=25, IMPEDE=25 The WAIT THRESHOLD directive sets the time a process must wait for a certain resource before becoming interesting and being logged.
Within Syntax Statements percent This parameter sets how long a process must wait for data transfer to or from a disc drive before becoming interesting and being logged. For example, WAIT DISC=50 indicates a process will be logged if it must wait for disc for more than half (50 percent) of the 1-minute sample interval. DISC= percent This parameter sets how long a process must wait for code or data to be brought into main memory before becoming interesting and being logged.
4 Data Management: UTILITY This chapter gives details on the UTILITY commands. It includes a command syntax summary, a discussion of the SCAN command, and a command reference section. (The reference section lists the commands in alphabetical order.) Note Commands and parameters for UTILITY can be entered with any combination of uppercase and lowercase letters. Only the rst three letters of the command's name are required.
Within Syntax Statements UTILITY Command Syntax Summary The following table contains a summary of UTILITY commands syntax and their parameters. Table 4-1.
Within Syntax Statements Table 4-1. UTILITY Commands: Syntax and Parameters (continued) Command Parameter PARMFILE parm le RESIZE GLOBAL APPLICATION PROCESS DISC DAYS maxdays SIZE maxMB EMPTY days SPACE MB YES NO MAYBE SCAN log le Operation is also a ected by the LIST, START, STOP, DETAIL, ALARMS, and NOTES commands.
Within Syntax Statements ALARMS ALARMS ON OFF You can set the alarms ON or OFF to select whether or not to print individual performance alarm events in the SCAN report. See the description of the SCAN command for information on this report. See also chapter 7 on Performance Alarms. The default is ALARMS=ON if alarm de nitions were found during the last PARMFILE command.
Within Syntax Statements CONVERT 9 8 log le This command converts one or more raw or extracted log les to the current version's format. The MPE log le format was altered starting with the B.00.nn release of Performance Collection Software. Earlier versions of the log les are known as version A log les, whereas the B.00.00 log les are version B log les. Only forward conversion is provided. That is, you can only convert log les of earlier releases to those of this release.
Within Syntax Statements Since the UTILITY program runs on the HP 3000 system, the parent log les of any log le downloaded to the PC should be converted on the HP 3000, then downloaded again. If the parent log le does not still exist on the HP 3000, the log le can be uploaded from the PC if care is taken to transfer BINARY data to a le with the proper MPE le characteristics ( le code, record size, blocking factor, etc.). Once transferred back to the HP 3000, it can be converted then downloaded again.
Within Syntax Statements CREATE 8 GLOBAL > > < 9 > > = APPLICATION DAYS=maxdays CREATE SIZE=maxMB > PROCESS > > > : ; DISC The CREATE command produces the four Performance Collection Software raw log les|LOGGLOB, LOGAPPL, LOGPROC, LOGDISC|before starting SCOPE(XL) for the rst time. These log les must not already exist or any attempt to create them will fail. You can use CREATE to produce a log le with a speci ed maximum size.
Within Syntax Statements Sample CREATE Task The following example shows how to create the four Performance Collection Software raw log les. You must log on to the group where the log les will reside. The maximum size of each le is speci ed in order to override the defaults used by SCOPE(XL). :HELLO SCOPE.
Within Syntax Statements DETAIL DETAIL ON OFF You can control the level of detail printed in the SCAN and PARMFILE reports by setting the detail to ON or OFF. See the descriptions of the SCAN and PARMFILE commands for speci c actions on these reports. The default is DETAIL=ON.
Within Syntax Statements EXIT EXIT or E To terminate the UTILITY program, enter the EXIT command, or press 4F85 if you are using terminal softkeys.
Within Syntax Statements HELP 2 HELP topic 3 Access the online HELP facility interactively by entering the HELP command or pressing 4F75. This facility and the MPE HELP facility work in the same way. You can enter parameters to obtain information on the UTILITY program's commands and tasks, or on HELP itself. If you are using a terminal with HP softkey support, you can get help on a softkey's functions by pressing the softkey while in the HELP subsystem.
Within Syntax Statements LIST 2 LIST device 3 You can change the list device for all UTILITY reports in two ways: You can issue a le equation before running the UTILITY program. :FILE RXLIST;DEV=LP or You can use the LIST command once UTILITY is running. LIST LP The device parameter on the LIST command must represent a valid con gured device on the current HP 3000 system. It should be a device that can be written to (normally a printer).
Within Syntax Statements Sample LIST Task When you print a summary report on the extracted log le RXLOG to the line printer (device LP), the following will occur: LOGFILE RXLOG LIST LP DETAIL OFF SCAN (Opens the RXLOG log le.) (Directs the SCAN report listing to LP.) (Speci es less than full detail in the report.) (Reads RXLOG and produces the report.
Within Syntax Statements LOGFILE 2 LOGFILE log le 3 For many UTILITY program functions, a log le must be opened. This can be accomplished by explicitly issuing the LOG command or implicitly by issuing some other commands. If a log le name is not provided, the default LOGGLOB.SCOPE.SYS is used. You can specify the name of either a raw or extracted log le. If you specify an extracted log le name, all information is obtained from this single le.
Within Syntax Statements You can verify the log le that you opened with the SHOW command, as described later. You can open another log le at any time by entering another LOG or LOGFILE command. Any currently open log le is closed before the new log le is opened.
Within Syntax Statements MENU MENU The MENU command prints a short list of the available UTILITY commands. Command Function Get the information on commands and options. LOGFILE Specify a log le to be analyzed. PARMFILE Specify a Performance Collection Software parameters le to be checked. START Specify a starting date and time for SCAN. STOP Specify an ending date and time for SCAN. DETAIL Enable or disable the printing of details for SCAN.
Within Syntax Statements MPE 3 2 command You can enter an MPE command without exiting UTILITY by entering MPE or a colon (:) followed by a valid MPE V or MPE/iX command. MPE or : MPE SHOWJOB :TELL MANAGER.SYS; HI :EDITOR MPE RUN FCOPY.PUB.SYS Commands that cannot be executed in this fashion are as follows: ABORT BYE CHGROUP DATA DO EOD EOJ EXIT HELP JOB LISTREDO OPTION SETCATALOG SHOWCATALOG REDO RESUME UDCs, COMMAND FILEs, and implicit RUN commands can be executed on MPE/iX but not on MPE V.
Within Syntax Statements NOTES 2 ON 4 NOTES OFF 3 5 level You can add notes to the Performance Collection Software global log le with the UTILITY program's SCOPE NOTE command. The notes added with this command are reported when a SCAN command is executed. The SCOPE(XL) program can also write notes to this le to record important events. The NOTES command can control which of these notes are listed during a SCAN function: If NOTES=OFF, notes are not printed during a scan.
Within Syntax Statements PARMFILE 2 PARMFILE parm le 3 Use the PARMFILE command to check the syntax of a Performance Collection Software PARM le and report any warnings or errors. You can use the PARMFILE command to do any of the following: Examine a Performance Collection Software PARM le for errors or warnings. Discover how much room is left for de ning applications. Discover how much room is left for de ning disc groups. De ne Performance Alarms to be used during the SCAN function.
Within Syntax Statements RESIZE RESIZE 8 GLOBAL > > < 9 > > = APPLICATION DAYS=maxdays SIZE=maxMB > PROCESS > > > : ; DISC 2 3 YES EMPTY=days 4 5 NO SPACE=MB MAYBE Use the RESIZE command to resize raw log les. This is the only program you should use to resize the log les in order to preserve coordination between the les and their internal control structures. If you use other tools, such as FCOPY, you might remove or destroy the validity of these control structures.
Within Syntax Statements The default resizing parameters are shown in table 4-2. Table 4-2. Default Resizing Parameters Parameter If Executed Interactively If Executed in Batch Log le type You are prompted for each available log le type. No default. This is a required parameter. DAYS The current le size. The current le size. The current amount of empty space or enough empty space to retain all data currently in the le, whichever is smaller.
Within Syntax Statements If you do not specify a data type, the batch job terminates (in batch mode), or you are prompted to supply the data type based on those log les that currently exist (in interactive mode). Size Parameters Specify two sizes when you resize a log le: Maximum size of the le (specify DAYS or SIZE). Current amount of empty space required (specify EMPTY or SPACE). DAYS, SIZE, EMPTY, and SPACE parameters can be entered in units of days or megabytes.
Within Syntax Statements le is lled. Using UTILITY to force a certain amount of empty space in a log le will cause a log le to be resized when you want it to be. After resizing, a log le consists of data plus empty space. The data retained is calculated as the maximum le size minus the required empty space. Any data removed during the resizing operation is lost. To save log le data for longer periods of time, use EXTRACT to copy this data to an extracted le before doing the RESIZE function.
Within Syntax Statements The following batch job would accomplish this: :JOB WEEKLY,SCOPE.SYS,SCOPE :RUN UTILITY LOG LOGGLOB.SCOPE.SYS DETAIL OFF SCAN RESIZE GLOBAL EMPTY=10 RESIZE APPLICATION EMPTY=10 RESIZE PROCESS EMPTY=10 RESIZE DISC EMPTY=10 EXIT :EOJ MAYBE MAYBE MAYBE MAYBE Specifying MAYBE instead of YES avoids any resizing operations if 10 or more days of empty space currently exist in any log les. Note that the maximum le size defaults to the current maximum le size for each le.
Within Syntax Statements If the RESIZE is done interactively and one or more parameters are defaults, you can get a preliminary resizing report. This report summarizes the current log le contents and any parameters that were provided. The report is provided to aid in answering questions on the unspeci ed parameters. RESIZE GLOBAL DAYS=20 FILE RESIZING PARAMETERS (BASED ON AVERAGE DAILY SPACE ESTIMATES AND USER RESIZING PARAMETERS) FILE: LOGGLOB.SCOPE.SYS MEGABYTES / DAY: 0.
Within Syntax Statements Sample RESIZE Task The following resizing task resizes the raw PROCESS log le: LOGFILE LOGGLOB.SCOPE.SYS DETAIL=OFF SCAN (The name of the log le to be resized.) The default log le, LOGGLOB.SCOPE.SYS, is speci ed in this case. (The scan report will not give full detail.) (LOGGLOB.SCOPE.SYS will be read and a summary report on its contents will be produced.) The scan is performed before the resize to increase the accuracy of the number-of-days calculations.
Within Syntax Statements SCAN 2 SCAN log le 3 The following related commands are discussed brie y in this section and in more detail elsewhere in this chapter under the command name: LIST, START, STOP, DETAIL, NOTES, and ALARMS. The SCAN command reads a log le and writes a summary report on its contents. The format of this report depends on the commands issued prior to SCAN. For example, The LOGFILE and SCAN commands can create a report on the log le's disc space.
Within Syntax Statements The SCAN command requires that a log le is opened. The log le to be scanned is the rst of one of the following: 1. The log le named in the SCAN command itself. 2. The last log le opened by any previous command. 3. The default log le (LOGGLOB.SCOPE.SYS). In this case, interactive users are prompted to override the default log le name if so desired.
Within Syntax Statements Sample SCAN Tasks Scan the current Performance Collection Software raw log les, and display a report on the logging details. This report includes details on the initial PARM le settings plus any changes to these settings. An overall summary of disc space consumed by each type of logging is also displayed. In this sample, the listing is defaulted to the job or session $STDLIST device. LOGFILE LOGGLOB.SCOPE.SYS DETAIL=ON SCAN (Opens the LOGGLOB.SCOPE.SYS log le.
Within Syntax Statements SCOPE 2 3 STATUS 6 KILL 7 7 SCOPE 6 4 NEWPARM 5 2 3 NOTE message The SCOPE command allows you to communicate with the SCOPE(XL) data collector as it runs. If the Performance Collection Software data collector is not running and logged on to the SCOPE.SYS group, all SCOPE commands indicate that SCOPE(XL) is not running and the commands fail. To issue a command to the SCOPE(XL) data collector, you must have SM or OP capability and execute access to les in the SCOPE.SYS group.
Within Syntax Statements SCOPE STATUS SCOPE with the STATUS parameter asks the currently executing SCOPE(XL) to return its version number and data collection information. Most of this report is similar to part of the SCAN report (initial PARM le global information). Also, a report on the amount of disc space used in the four main log les|LOGGLOB, LOGAPPL, LOGPROC, and LOGDISC|is returned. SCOPE KILL SCOPE with the KILL parameter asks the currently executing SCOPE(XL) to terminate in an orderly fashion.
Within Syntax Statements SCOPE NEWPARM SCOPE with the NEWPARM parameter instructs SCOPE(XL) to reprocess its PARM le. Any changes found in the PARM le are acted upon without stopping and restarting the data collection job. (You cannot change the system ID at this time.) SCOPE NOTE SCOPE with the NOTE parameter places a user note into the Performance Collection Software global log le. Such notes may be viewed by performing a SCAN with NOTES=ON or NOTES=100.
Within Syntax Statements SHOW 2 SHOW ALL 3 The SHOW command lists the names of the les that are open and the status of the UTILITY parameters that can be set, for example, SHOW LOGFILE: LOGGLOB.SCOPE.
Within Syntax Statements START 2 3 date time 2 32 3 START TODAY -days time Use the START command to set a starting date and time for the SCAN function. The default starting date is the date of the earliest record of any type in the log le. The date format depends on the native language con gured on the HP 3000 system being used. If you do not use Native Languages or have set the default language (NATIVE-3000), the date format is mm/dd/yy (month/day/year) such as 02/28/88 for February 28, 1988.
Within Syntax Statements STOP 2 3 date time 2 32 3 STOP TODAY -days time The STOP command can be used to set the date and time for terminating the SCAN function. The default stopping date and time is the last date and time in the log les. The formats for the STOP command are the same as for the START command and depend on the native language being used. If no stop time is given, midnight (12:00 am) is assumed.
Within Syntax Statements VERSIONS 2 VERSIONS group 3 The VERSIONS command attempts to list the version numbers for all HP LaserRX/MPE and Performance Collection Software host programs and libraries. It also checks for the HP Cooperative Services programs used by Performance Collection Software to communicate with the PC software. If no group name is supplied, the Performance Collection Software host programs are expected to be in the same group as UTILITY.
5 Data Management: EXTRACT This chapter details the EXTRACT commands. It includes a syntax summary and a command reference section that lists the commands in alphabetical order.) Note Commands and parameters for EXTRACT can be entered with any combination of uppercase and lowercase letters. Only the rst three letters of the command's name are required. For example, the command APPLICATION DETAIL can be abbreviated as APP DET.
Within Syntax Statements EXTRACT Command Syntax Summary This following table contains a summary of EXTRACT commands syntax and their parameters. Table 5-1.
Within Syntax Statements Table 5-1.
Within Syntax Statements APPLICATION 2 3 ON 6 DETAIL 7 6 7 6 7 APPLICATION 6 SUMMARY 7 6 7 4 BOTH 5 OFF The APPLICATION command selects the type of application data that will be extracted or exported. The default is APPLICATION OFF. DETAIL or ON The DETAIL or ON parameter speci es that raw, 5-minute detail data should be extracted.
Within Syntax Statements BOTH The BOTH parameter speci es that 5-minute detail data and hourly summary data are to be extracted. This option maintains the speed of access gained with hourly summary records, while allowing HP LaserRX/MPE application graphs with points every 5 minutes. The disc space required to extract both detail and summary data is about 10 percent more than the space needed for extracted detail data alone. OFF The OFF parameter speci es that no application data is to be extracted.
Within Syntax Statements AUTO AUTO The AUTO command starts automatic data extraction. No further interaction with EXTRACT is allowed. Commands entered before the AUTO command are honored, if possible. You can enter the default starting data for an extraction by using the run-time ;PARM= parameter. See the START command for more information. If not previously speci ed, the LOGFILE and OUTPUT commands will assume the following defaults when the AUTO command is executed: LOGFILE: LOGGLOB.SCOPE.
Within Syntax Statements CONFIGURATION CONFIGURATION ON OFF The CONFIGURATION command speci es whether or not to export system con guration information. The default is CONFIGURATION OFF. All con guration information collected between the start and stop dates is exported. Shift times and NOWEEKENDS parameters are ignored. Note The CONFIGURATION command a ects only the EXPORT function. It does not a ect the EXTRACT function since the EXTRACT function always extracts system con guration information.
Within Syntax Statements DISC ON DISC OFF The DISC command speci es whether or not to extract or export disc space information. The default is DISC OFF. Specifying DETAIL, SUMMARY, or BOTH is the same as specifying ON, since disc space data is only collected once a day. All disc space data collected between the start and stop dates is extracted. Shift times are ignored, but the NOWEEKENDS parameter is honored.
Within Syntax Statements EXIT EXIT E The EXIT command ends the EXTRACT program. (If you are using terminal softkeys, you can press 4F85).
Within Syntax Statements EXPORT EXPORT The EXPORT command starts the process of exporting data. If not previously speci ed, the LOGFILE and REPORT commands will assume the following defaults when the EXPORT command is executed: LOGFILE LOGGLOB.SCOPE.SYS REPORT REPTFILE.SCOPE.SYS See the discussion of the EXPORT function later in this chapter for more information on how to export les. The settings or defaults for all other parameters are used.
Within Syntax Statements Sample EXPORT Task In this task, you export raw log le data collected yesterday (8:00 am to 5:00 pm) using the default report le. :RUN EXTRACT LOGFILE LOGGLOB.SCOPE.SYS START TODAY-1 8:00 AM STOP TODAY-1 5:00 PM GLOBAL SUMMARY REPORT REPTFILE.SCOPE.
Within Syntax Statements EXTRACT EXTRACT The EXTRACT command starts data extraction. If not previously speci ed, the LOGFILE and OUTPUT commands will assume the following defaults when the EXTRACT command is executed: LOGFILE LOGGLOB.SCOPE.SYS OUTPUT RXLOG,NEW The settings or defaults for all other parameters are used. For details on their actions, see APPLICATION, DISC, GLOBAL, PROCESS, SHIFT, START, and STOP.
Within Syntax Statements Sample EXTRACT Task 3 In this task, you append data from raw log les to the existing RXSUM extracted log le. Original extraction speci cations from the RXSUM le are maintained. Extracting data is stopped on February 28, 1990. LOGFILE LOGGLOB.SCOPE.SYS OUTPUT RXSUM,APPEND STOP 2/28/90 EXTRACT Sample EXTRACT Task 4 In this task, you create a new extracted log le called RXJAN90. Purge any existing le with this name.
Within Syntax Statements OUTPUT ALLDATA,PURGE START 1/1/1 STOP 12/31/99 SHIFT 8:00 AM - 5:00 PM NOWEEKENDS GLOBAL SUMMARY APPLICATION SUMMARY EXTRACT 5-14 Data Management: EXTRACT
Within Syntax Statements GLOBAL 2 3 ON 6 DETAIL 7 6 7 6 7 GLOBAL 6 SUMMARY 7 6 7 4 BOTH 5 OFF The GLOBAL command selects how much global data is extracted or exported. The default is GLOBAL DETAIL. DETAIL The DETAIL parameter speci es that raw detail collected at 5-minute intervals is to be extracted. Detail data must be placed into an extracted le before you can draw any HP LaserRX/MPE global graphs with points every 5 minutes.
Within Syntax Statements BOTH The BOTH parameter speci es that 5-minute detail data and hourly summary data are to be extracted. This option maintains the speed of access gained with the hourly summary records while permitting you to draw HP LaserRX/MPE Global graphs with points every 5 minutes. The disc space required to extract both detail and summary data is about 8 percent more than the space needed for extracted detail data alone.
Within Syntax Statements HELP 2 HELP topic 3 Enter the HELP command to access the online HELP facility interactively. This facility and the MPE HELP facility work in the same way. You can enter parameters to obtain information on EXTRACT commands and tasks, and on the HELP command. If you are using a terminal with HP softkey support, you can get help on the functions of a softkey by pressing the softkey while you are in the HELP subsystem.
Within Syntax Statements LIST 2 LIST device 3 You can change the list device for all EXTRACT reports in two ways: To issue a le equation before running the EXTRACT program, enter :FILE RXLIST;DEV=LP or Once EXTRACT is running, enter LIST LP The device parameter on the LIST command must represent a valid con gured device on the current HP 3000 system. It should be a device that can be written to (normally, this would be a printer).
Within Syntax Statements LOGFILE 2 LOGFILE log le 3 A log le must be opened for all EXTRACT program functions. You can do this explicitly, by issuing the LOGFILE command, or implicitly, by issuing the EXTRACT or AUTO command. If a log le name is not provided, the default LOGGLOB.SCOPE.SYS is used. You can specify the name of either a raw or extracted log le. You cannot specify the name of a le created by the EXPORT command.
Within Syntax Statements Caution Do not rename raw log les! When accessing these les, it is assumed that the standard log le names are in e ect. For example, if you must rename log les to place log les from multiple systems on the same HP 3000 for analysis, you should rst extract the data, then rename the extracted log les. The following is an example of raw log les that have been opened in SCOPE.SYS: GLOBAL FILE: APPLICATION FILE: PROCESS FILE: DISC SPACE FILE: INDEX FILE: SYSTEM ID: COOKIE LOGGLOB.
Within Syntax Statements MENU MENU The MENU command prints a short list of the available EXTRACT commands. HELP LOGFILE OUTPUT START STOP SHIFT GLOBAL APPLICATION PROCESS DISC LIST SHOW EXTRACT WEEKLY MONTHLY YEARLY MPE or : MENU EXIT or E CONFIG REPORT EXPORT Get information on commands and options. Specify a log le to be analyzed. Specify a destination le for extraction. Specify a starting date and time for EXTRACT. Specify an ending date and time for EXTRACT.
Within Syntax Statements MONTHLY yymm MONTHLY mm The MONTHLY command performs data extraction based on a calendar month. When you execute this command, the start and stop dates are set to the proper dates based on the month and year of the data extracted. The name of the output le consists of the letters RXMO followed by the last two digits of the year and the two-digit number of the month being extracted. For example, March 1990 would be output to a le named RXMO9003.
Within Syntax Statements For example, a MONTHLY command is executed on May 7, 1991. This creates a log le named RXMO9105 containing data from May 1 through the current date (May 7). On June 4, 1991, another MONTHLY command is executed. Before the RXMO9106 le is created for the current month, the RXMO9105 le from the previous month is opened. When it is found to be incomplete, data is appended to it to complete the extraction through May 31, 1991.
Within Syntax Statements MPE 3 2 command You can enter an MPE command without exiting EXTRACT by entering MPE or a colon (:) followed by a valid MPE V or MPE/iX command. For example, MPE or : MPE SHOWJOB :TELL MANAGER.SYS; HI :EDITOR MPE RUN FCOPY.PUB.SYS The following commands cannot be executed in this way: ABORT BYE CHGROUP DATA DO EOD EOJ EXIT HELLO JOB LISTREDO OPTION SETCATLOG SHOWCATALOG REDO RESUME UDC, COMMAND FILE, and implicit RUN commands can be executed on MPE/iX but not on MPE V.
Within Syntax Statements OUTPUT 2 3 ,NEW 2 3 4 OUTPUT output lename ,PURGE 5 ,APPEND Use the OUTPUT command to open and, if necessary, to create an extracted log le in which to write extracted SCOPE(XL) records. If you do not provide an output le name, EXTRACT assumes it is RXLOG. The optional second parameter speci es the action to be taken if an output le with the same name exists. NEW PURGE APPEND (Speci es that the output le must be a new le.) This is the default action in batch mode.
Within Syntax Statements PROCESS PROCESS ON OFF The PROCESS command selects whether or not process data will be extracted or exported. The default is PROCESS OFF. ON OFF Note 5-26 (Speci es that process detail data should be extracted.) Process data must be placed into an extracted le in order to display tabular process data by using the zoom process function in the HP LaserRX/MPE Analysis Software. (The OFF parameter speci es that process data should not be extracted.
Within Syntax Statements REPORT 2 32 3 ,SHOW Use the REPORT command to select the de nition le that will be used by the EXPORT function. The default report le is REPTFILE in the same group and account as the EXTRACT program (usually REPTFILE.SCOPE.SYS). REPORT report le ,SHOW (Speci es that the eld positions and starting columns should be listed for all reports contained in the report le.) This report may be used when export les are processed by other programs.
Within Syntax Statements SHIFT SHIFT starttime-stoptime ALL DAY 2 NOWEEKENDS 3 The SHIFT command can be used to limit data extraction to certain hours of the day corresponding to work shifts and to exclude weekends (Saturday and Sunday). The default is ALL DAY (everyday including weekends). The starttime and stoptime parameters are entered in the same format as the time in the START command. Shifts that span midnight are permitted.
Within Syntax Statements SHOW 2 SHOW ALL 3 The SHOW command lists the names of the opened les and the status of the EXTRACT parameters that can be set. For example: SHOW LOGFILE: OUTPUT: THE THE THE LOGGLOB.SCOPE.SYS RXLOG.SCOPE.SYS **NEW OUTPUT FILE** DEFAULT STARTING DATE & TIME = 04/16/90 12:00 AM DEFAULT STOPPING DATE & TIME = 05/16/90 12:00 AM DEFAULT SHIFT = 12:00 AM - 12:00 AM GLOBAL..... BOTH DETAIL & SUMMARY RECORDS APPLICATION...............SUMMARY RECORDS PROCESS..........DETAIL.........
Within Syntax Statements Adding the optional ALL parameter will cause more information about the log le to be printed. For example: LOGFILE: LOGGLOB.SCOPE.SYS GLOBAL FILE: LOGGLOB.SCOPE.SYS APPLICATION FILE: LOGAPPL.SCOPE.SYS PROCESS FILE: LOGPROC.SCOPE.SYS DISC SPACE FILE: LOGDISC.SCOPE.SYS INDEX FILE: LOGINDX.SCOPE.SYS SYSTEM ID: COOKIE PTC Hewlett-Packard SERIES 967 DATA COLLECTOR: XL B.02.
Within Syntax Statements START 2 3 date time 2 32 3 START TODAY -day time Use the START command to set a starting date and time for the EXTRACT function. The default starting date is the date 30 full days before the last date in the log le or the date of the earliest record the log le, if less that 30 days are present. You can control the default starting by using the ;PARM= parameter at run time.
Within Syntax Statements If no start time is given, midnight (12:00 am) is assumed. A starting time of midnight for a given day starts at the beginning of that day (00:00 on a 24-hour clock). The keyword TODAY may be used to represent the current date. TODAY-days speci es the number of days prior to today's date. For example, TODAY-1 indicates yesterday's date.
Within Syntax Statements STOP 2 3 date time 2 32 3 STOP TODAY -day time The STOP command can be used to terminate the EXTRACT function on a speci ed date and time. The default stopping date and time is the last date and time recorded in the log les. The formats for the STOP command are the same as those for the START command and depend on the language being used. If no stop time is given, midnight (12:00 am) is assumed.
Within Syntax Statements WEEKLY yyww WEEKLY ww The WEEKLY command speci es data extraction based on a calendar week. A week is de ned as seven days starting on Monday and ending on Sunday. When this command is executed, the start and stop dates are set to the proper dates based on the week and year of the extracted data. The name of the output le consists of the letters RXWE followed by the last two digits of the year and the two-digit week number for the week being extracted.
Within Syntax Statements For example, a WEEKLY command is executed on Thursday, May 17, 1991. This creates a log le named RXWE9120 containing data from Monday, May 14 through the current date (May 17). On Wednesday, May 23, 1991 another WEEKLY command is executed. Before the RXWE9121 le is created for the current week, the RXWE9120 le from the previous week is opened. When it is found to be incomplete, data is appended to it to complete the extraction through on Sunday, May 20, 1991.
Within Syntax Statements YEARLY yyyy YEARLY yy The YEARLY command speci es a data extraction based on a calendar year. During execution, the command sets the start and stop dates to the proper dates, based on the year being extracted. The name of the output le consists of the letters RXYR followed by the four digits of the year being extracted. Thus, data from 1991 would be output to a le named RXYR1991. Enter one of the following: YEARLY YEARLY yy YEARLY yyyy To extract the current year's data.
Within Syntax Statements For example, a YEARLY command is executed on December 15, 1991. This creates a log le named RXYR1991 that contains data from January 1, 1991 to the current date (December 15). On January 5, 1992, another YEARLY command is executed. Before the RXYR1992 le is created for the current year, the RXYR1991 le from the previous year is opened. When it is found to be incomplete, data is appended to it to complete its extraction until December 31, 1991.
Within Syntax Statements Overview of the Export Action EXPORT copies Performance Collection Software log le data into a form that can be easily accessed without passing through the HP LaserRX/MPE analysis programs. Any valid raw or extracted log le can be the source of this data. The process is summarized in gure 5-1. Figure 5-1. The Export Function Exported les can be used in a variety of ways, such as custom graphics packages, databases, and user-written analysis programs.
Within Syntax Statements How to Export Data In the simplest form, you can export data by specifying the default log le and the default report le, then starting the export. The default report le allows you to export les similar to the current HP LaserRX/MPE EXPORT LOGFILE function. :RUN EXTRACT LOGFILE LOGGLOB.SCOPE.SYS REPORT REPTFILE.SCOPE.SYS EXPORT Exported data is in a le called XFERGLOB in a format suitable for loading into a spreadsheet.
Within Syntax Statements Sample Export Tasks Several sample report les are furnished with the Performance Collection Software. They may be used initially to perform common reporting tasks or as a starting point for custom tasks. Generate a CPU and DISC report on a printer. The REPTHIST report le contains the speci cations to generate a character graph of CPU and DISC usage for a system over time.
Within Syntax Statements Summarize the process data and list the top programs, as ranked by amount of CPU used. While similar to the previous task, this one adds the need to combine multiple executions of a program le, multiple processes, into a summary for the program le. A simple program has been written to combine multiple executions of a program into a single report line. The name of this program is TOPCPU and its source, in COBOL, is in the le TOPCPUS.
Within Syntax Statements Export Data Files Export can create up to seven exported les, depending on the types of data and the report le selected. A log le will not be created if items were not selected for the type of data in the report le or if the EXTRACT program did not receive the proper command prior to the EXPORT command. All seven data les will be purged at the beginning of an EXPORT function regardless of whether or not they will be recreated later.
Within Syntax Statements Creating a Report File The report le contains the following information: 2 3 ASCII ON 4 5 DATAFILE TITLE HEADINGS REPORT title string FORMAT OFF BINARY SEPARATOR=char datatype items 2 3 where: REPORT TITLE (Prints an optional character string and headings.) The following page has more details. FORMAT (Selects the data formats.) ASCII An ASCII format le is similar to the HP LaserRX/MPE analysis software export to DATAFILE format.
Within Syntax Statements HEADINGS SEPARATOR DATA TYPE ITEMS (Selects whether or not to include column headings in the data le (HEADINGS=ON or HEADINGS=OFF).) (Selects the character that is printed between each eld in the DATAFILE format.) The default separator is a blank space, but many programs prefer the eld separator to be a comma. You may set the separator to any printing or nonprinting character. (Selects one of the exportable data types: GLOBAL, APPLICATION, PROCESS, DISCSPACE, or CONFIGURATION.
Within Syntax Statements would generate a report title similar to Export COOKIE data from LOGGLOB.SCOPE.SYS on 02/02/91 08:30 AM An Example of Exporting Data Example: You want to export GLOBAL and APPLICATION data at a rate of one data point per hour for use in creating a custom graph or report. Take the following steps: 1. First, you must determine what data items you will need from each data type and in what format should you access them.
Within Syntax Statements 4. Select the report le generated. REPORT REPORT1 5. Select GLOBAL SUMMARY data and APPLICATION SUMMARY data using standard EXTRACT program commands. GLOBAL SUMMARY APPLICATION SUMMARY 6. Now enter EXPORT|it means \GO". EXPORT ENTER THE LOG FILE NAME (LOGGLOB.SCOPE.SYS) 7. Since you didn't tell the program from where it should get the performance data, the program will prompt you. In this example the default log le is correct, just press RETURN. EXPORTING GLOBAL DATA .........
Within Syntax Statements Data Items for Exporting Data The following data items are available for Data Type GLOBAL: Table 5-2. EXPORT Items for Data Type GLOBAL Record Identi cation Metrics RECORD_TYPE DATE TIME DAY YEAR DATE_SECONDS INTERVAL SAMPLES NUMBER_OF_DISCS BLANK ASCII eld to identify this record type \GLOB". Date in MM/DD/YY format (or custom NLS date). Time in HH:MM 24-hour format. Julian day-of-the-year (1-366). Year (such as 1991). Date in UN3:X format (in seconds, since January 1, 1970).
Within Syntax Statements Table 5-2. EXPORT Items for Data Type GLOBAL (continued) CPU Metrics CPU_SESSION CPU_SESSION_SECONDS CPU_JOB CPU_JOB_SECONDS CPU_SYSTEM CPU_SYSTEM_SECONDS CPU usage by interactive sessions (percentage of total). CPU usage by interactive sessions (time, in seconds). CPU usage by batch jobs (percentage of total). CPU usage by batch jobs (time, in seconds). CPU usage by system processes (percentage of total). CPU usage by system processes (time, in seconds).
Within Syntax Statements Table 5-2.
Within Syntax Statements Table 5-2. EXPORT Items for Data Type GLOBAL (continued) Process Queue Depths (Load Factors) CPUQUEUE DISCQUEUE MEMORYQUEUE IMPEDEQUEUE Average number of processes waiting for or using CPU. Average number of processes waiting for DISC transfers. Average number of processes waiting for MEMORY. Average number of processes waiting for IMPEDES (locks).
Within Syntax Statements Table 5-2. EXPORT Items for Data Type GLOBAL (continued) Terminal Transaction Distributions. Each metric is an array of 10 items. DISTRIBUTION_FIRST DISTRIBUTION_PROMPT DISTRIBUTION_THINK First-response time distribution (10 values). Response-to-prompt distribution (10 values). Transaction think-time distribution (10 values). Individual Disc Metrics. The following elds will be repeated once for every disc on the system.
Within Syntax Statements APPLICATION Data Type Application data type can generate two di erent record layouts. The rst layout writes one record for every application that was active during the time interval. Each application is in a separate record. The second layout writes only one record for each interval. In this layout, a section of the record is reserved for every application. If the application was not active during the interval then its elds will contain zeros.
Within Syntax Statements Table 5-4. EXPORT Items for Data Type APPLICATION (Single Layout) Used with single application layouts: Application ID Metrics INTERVAL SAMPLES APPLICATION_NO APPLICATION BLANK Time covered by this record (in seconds). Number of samples averaged into this record. Sequential application number (matches PARM le). Application name (20-byte ASCII). An empty eld used as a spreadsheet place holder.
Within Syntax Statements Table 5-4. EXPORT Items for Data Type APPLICATION (Single Layout) (continued) Disc Metrics DISC_LINEAR DISC_LINEAR_IO DISC_CS DISC_CS_IO DISC_DS DISC_DS_IO DISC_ES DISC_ES_IO Physical disc IO rate while in linear execution queue (IOs/second). Number of physical disc IOs while in the linear execution queue. Physical disc IO rate while in the \CS" execution queue (Ios/second). Number of physical disc IOs while in the \CS" execution queue.
Within Syntax Statements Table 5-4. EXPORT Items for Data Type APPLICATION (Single Layout) (continued) Average process Wait State Metrics STOPCPU STOPDISC STOPSWAP STOPIMPEDE STOPOTHERIO STOPTERM Time processes spent waiting for CPU (percentage of total). Time processes spent waiting for DISC (percentage of total). Time processes spent waiting for MEMORY (percentage of total). Time processes spent IMPEDED (locked) (percentage of total). Time processes spent waiting for other IO (percentage of total).
Within Syntax Statements Table 5-5. EXPORT Items for Data Type APPLICATION (Multiple Layout) Used with multiple application layouts. The following elds will be repeated once for each application de ned on the system. Application Identi cation Metrics @INTERVAL @SAMPLES @APPLICATION_NO @APPLICATION @BLANK Time covered by this record (in seconds). Number of samples averaged into this record. Sequential application number (matches PARM le). Application name (20-byte ASCII).
Within Syntax Statements Table 5-5. EXPORT Items for Data Type APPLICATION (Multiple Layout) (continued) @DISC_DS_IO @DISC_ES @DISC_ES_IO Number of physical disc IOs while in the \DS" execution queue. Physical disc IO rate while in the \ES" execution queue (IOs/second). Number of physical disc IOs while in the \ES" execution queue.
Within Syntax Statements PROCESS Data Type The following data items are available for the PROCESS data type. There is one record for each interesting process. Table 5-6. EXPORT Items for Data Type PROCESS Record Identi cation Metrics RECORD_TYPE DATE TIME DAY YEAR DATE_SECONDS INTERVAL BLANK ASCII eld to identify this record type \PROC". Date in MM/DD/YY format (or custom NLS date). Time in HH:MM 24-hour format. Julian day-of-the-year (1-366). Year (such as 1991).
Within Syntax Statements Table 5-6. EXPORT Items for Data Type PROCESS (continued) Summary Metrics RUNTIME TOTAL_CPU TOTAL_CPU_SECONDS TOTAL_DISC TOTAL_DISC_IO TOTAL_FIRSTRESP TOTAL_PROMPT TOTAL_THINK TOTAL_TRANS TOTAL_TRANS_COUNT Total process execution time until end of interval. Percentage of CPU usage during process life (percentage of total run time). Time of CPU usage during process life (run time, in seconds). Physical disc IO rate during process life (IOs/second).
Within Syntax Statements Table 5-6. EXPORT Items for Data Type PROCESS (continued) PHYSREAD PHYSREAD_IO PHYSWRITE PHYSWRITE_IO Physical disc read rate during interval (IOs/Second). Number of physical disc reads during the interval. Physical disc write rate during interval (IOs/Second) . Number of physical disc writes during the interval. Terminal Transaction Metrics TRANSACTIONS TRANSACTION_COUNT THINKTIME FIRSTRESP PROMPT Number or rate of transactions completed during interval.
Within Syntax Statements Table 5-7. Codes for Reason of Interest The INTEREST eld consists of 12 independent columns. Each column contains either a blank or a character representing a process INTEREST code, as shown below. Position Character Meaning 1 N 2 K 3 C 4 D 5 P 6 F 7 T 8 c 9 d 10 m 11 i 12 blank New (process is newly created). Killed (process is terminated). CPU percentage exceeded threshold. Disc I/Os exceeded threshold. Response-to-prompt exceeded threshold.
Within Syntax Statements DISC Data Type The following data items are available for the DISC data type. Table 5-8. EXPORT Items for Data Type DISC SPACE Record Identi cation Metrics RECORD_TYPE DATE TIME DAY YEAR DATE_SECONDS BLANK NUMBER_OF_DISCS NUMBER_OF_GROUPS ASCII eld to identify this record type \DISC". Date in MM/DD/YY format (or custom NLS date). Time in HH:MM 24-hour format. Julian day-of-the-year (1-366). Year (such as 1991). Date in UN3X format (in seconds, since January 1, 1970).
Within Syntax Statements Table 5-8. EXPORT Items for Data Type DISC SPACE (continued) Transient (Virtual) Disc Space Metrics1 TRANSIENT_CAPACITY VIRTUAL_CAPACITY* PEAK_TRANSIENT PEAK_VIRTUAL * TRANSIENT VIRTUAL* FREE_TRANSIENT FREE_VIRTUAL * Total disc space reserved for transient or virtual memory. Total disc space reserved for transient or virtual memory. Peak transient/virtual memory usage during the last day. Peak transient/virtual memory usage during the last day.
Within Syntax Statements CONFIGURATION Data Type The following data items are available for the CONFIGURATION data type. There is one record for each collector start-up or NEWPARM. Table 5-9. EXPORT Items for Data Type CONFIGURATION Record Identi cation Metrics RECORD_TYPE DATE TIME DAY YEAR DATE_SECONDS BLANK ASCII eld to identify this record type \CONF". Date in MM/DD/YY format (or custom NLS date). Time in HH:MM 24-hour format. Julian day-of-the-year (1-366). Year (such as 1991).
Within Syntax Statements Table 5-9. EXPORT Items for Data Type CONFIGURATION (continued) Interesting Process Thresholds THRESHOLD_CPU THRESHOLD_DISC THRESHOLD_TRANS THRESHOLD_FIRSTRESP THRESHOLD_RESPONSE THRESHOLD_NOKILLED THRESHOLD_NONEW THRESHOLD_NOSHORT THRESHOLD_MINTHINK THRESHOLD_MAXTHINK WAIT_CPU WAIT_DISC WAIT_MEMORY WAIT_IMPEDE Interesting process CPU threshold setting (percentage). Interesting process DISC threshold setting (IOs/second). Interesting process TRANSACTION threshold (number).
Within Syntax Statements Resulting Exported Files By default, exported les are created with the following characteristics. You may use le equations to override these defaults, if you wish. Table 5-10.
Within Syntax Statements The contents of each le will be: REPORT TITLE LINE HEADING LINE1 HEADING LINE2 (If REPORT Title was speci ed and HEADINGS=ON.) (If HEADINGS=ON.) (If HEADINGS=ON and it is not a binary le.) FIRST DATA RECORD SECOND DATA RECORD Report title and heading lines will not be repeated in the le. FIXED versus VARIABLE Length Record Formats By default, the exported les will be built with variable-length records.
Within Syntax Statements Numerical values will be formatted based on their range of values and internal accuracy. All elds will not be the same length so be sure to decide how you will determine the start of each eld. The user speci ed SEPARATOR character (or the default blank) will be used to separate each eld from the next in ASCII and DATAFILE formats. Blank separators can be visually more attractive if you plan to print the report.
Within Syntax Statements Details on Binary Format Binary format les will write numerical values as 32-bit integers. This format can save space by reducing the overall le size, but it requires a program that is able to read binary les. Copying a binary-format le to a printer or a terminal is not recommended. Non-numerical data will be written the same as it was in the ASCII format except separator characters will not be used.
Within Syntax Statements Consider the header record as an array of 32-bit integers. All data in the data records are aligned to a 32-bit boundary. If the data record contains a numerical value, then the header record will contain its scale factor in the corresponding location. Non-numeric items will have zeros in all corresponding locations in the header record. Negative numbers may be used to indicate an invalid item speci cation.
6 Archiving Strategies E cient analysis of system performance depends on how easily it is to access the performance data you collect. If disc space is not limited, you can keep several years of performance data online. Since usually you can analyze only the most recent data, you do not have to allocate much disc space to collected data. Use the EXTRACT program to specify the type and amount of log le data you will need for later performance analysis.
Within Syntax Statements Recommended Strategy Extract detail data from raw log les into a di erent log le every month by using the MONTHLY command. Name each extracted le to permit identi cation and later restoration from archive tapes. If your system generates more than 30 megabytes of monthly data, you might need to extract data using the WEEKLY command or eliminate process detail data. To save disc space, next extract only global and application summaries into a YEARLY le.
Within Syntax Statements Other Archiving Techniques You can use Performance Collection Software log le data in several ways. Shortly after it is logged, you can use it to diagnose short-term problems on your system (or systems). To do this, you must be able to access the latest log le data quickly and in full detail. If you have direct data communication links between your PC and the host system, the fastest way to access log le data is by opening a raw log le directly as a remote log le.
Within Syntax Statements A typical job stream is as follows: :JOB SUNDAY,SCOPE.SYS,SCOPE :RUN EXTRACT GLOBAL BOTH APPLICATION BOTH PROCESS ON DISC ON WEEKLY EXIT :DSLINE CENTRAL :REMOTE HELLO ARCHIVE.LOGFILES,BERT :DSCOPY RXWEyyww TO ,CENTRAL;MOVE;REP :REMOTE BYE :EOJ Now you can access any week on the BERT system by opening the appropriate log le. (The third week of 1991 for the BERT system is in a le called RXWE9103.BERT.ARCHIVE.
Within Syntax Statements The new batch job would be: :JOB SUNDAY,SCOPE.SYS,SCOPE :RUN EXTRACT;PARM=7 GLOBAL BOTH APPLICATION BOTH PROCESS ON DISC ON OUTPUT RXBERT EXTRACT EXIT :REMOTE HELLO ARCHIVE.LOGFILES;DSLINE=CENTRAL :DSCOPY RXBERT TO ,CENTRAL;MOVE;REP :REMOTE BYE :EOJ TIP You can save disc space and reduce transmission time at the expense of 5-minute data points on the Performance Collection Software graphs by specifying global summaries and application summaries to the EXTRACT program.
Within Syntax Statements Technique Perform a monthly extraction every day immediately before backup. (The MONTHLY extract command creates a single log le for each month, but appends new data to that log le whenever the command is executed.) Perform the following commands immediately before system backup: :RUN EXTRACT GLOBAL DETAIL APPLICATION DETAIL PROCESS ON DISC ON MONTHLY EXIT Remember that the extracted les are generated in the LOGON group.
Within Syntax Statements The following is a typical job stream: :JOB SUMMARY,SCOPE.SYS,SCOPE :RUN EXTRACT GLOBAL SUMMARY APPLICATION SUMMARY PROCESS OFF DISC ON YEARLY EXIT :EOJ You can access the remote log le RXYRyyyy (where yyyy is the year desired) or transfer this le to your PC for local access. Usually, the level of summarization you select will store a year of data in about 5 megabytes of disc space, or less (consistent with the program's other space requirements).
Within Syntax Statements Log File Resizing Strategies When raw log les are lled with data, they are rolled back automatically by the SCOPE(XL) data collection program. When a log le is rolled back, a new log le the same size as the old log le is built, the latest 75 percent of the data from the old le is copied to the new le, the old le is purged, then the new le is renamed with the old le's name. The net e ect is to discard the oldest 25 percent of the data to make room for new data.
Within Syntax Statements You can instruct the SCOPE(XL) collector to resize log les at scheduled times by adding the MAINTTIME directive to the PARM le. The SCOPE(XL) program will resize a log le at the speci ed time if the program expects the le to become full within the next 24 hours. Since log records may accumulate at di erent rates depending on your system's activity, scheduled maintenance may resize log les too early or too late. In such cases, you might want to control log- le resizing more closely.
Within Syntax Statements Combined Recommendations On each system, extract MONTHLY DETAIL and YEARLY SUMMARY data by using the EXTRACT program's MONTHLY and YEARLY commands. If you must access a system's data that is not directly accessible by your PC, perform an additional WEEKLY or DAILY extraction and move that data to a central analysis site where the PC can access it.
Within Syntax Statements * Finally, create the weekly extraction data. * [FOR REMOTE SYSTEMS ONLY] * PROCESS ON (Just in case we turned it o above.) WEEKLY ************************************************************ EXIT :COMMENT *************************************************** :COMMENT FOR REMOTE SYSTEMS, MOVE THE WEEKLY DETAIL DATA :COMMENT TO THE CENTRAL SYSTEM. :COMMENT :REMOTE HELLO THISSYS,REMOTE.
Performance Collection Software 7 Performance Alarms Performance Collection Software performance alarms may be used to identify periods in the logged data when performance met user-speci ed criteria. You can specify up to 50 independent alarms. Each alarm de nition may contain the following: An alarm identi er (up to 40 characters). One or more CONDITIONS that must be satis ed. An ACTION to be performed when the alarm is initiated. An ACTION to be performed when the alarm has ended.
Within Syntax Statements You can specify a minimum time between repetitions to prevent alarms from acting more than once within a given period. If you specify an alarm action such as the streaming of a detailed data collection job, you might want not want the job to be streamed more then once a day, even if the alarm condition continues through the day or is satis ed then becomes active again during the same day. Alarm actions will not be performed while logged data is being examined.
Within Syntax Statements severity number is an integer number indicating the relative severity of this alarm. Any value between 0 and 32767 is acceptable although certain products might place special signi cance on values in certain ranges. The default is zero. IF item1 is the rst item in the comparison. An item can be one of the following: A positive number specifying a literal constant [real numbers are allowed]. A metric name chosen from the Performance Items tables shown later in this chapter.
Within Syntax Statements THEN This is an optional parameter, but if entered it speci es the action to be taken when the alarm is rst satis ed. It will be repeated also if the alarm remains satis ed for a period longer than the speci ed REPEAT period. If the rst character of the action string is a colon (:), the action is interpreted as a single MPE command. Most MPE commands are allowed, including the :RUN command to run programs.
Within Syntax Statements FINISH This is an optional parameter, but if entered it speci es the action to be taken when an alarm is started and then ends (it is no longer satis ed). The options for this action are the same as those for the THEN parameter, above. REPEAT= [MINUTES] speci es the minimum time between repetitions of an alarm before it is allowed to be satis ed again.
Within Syntax Statements Note 7-6 A user variable may include another user variable in its de nition but variables are processed in alphabetical sequence from A through Z . For proper operation you should not reference a user variable unless it precedes the current one, alphabetically.
Within Syntax Statements Item Name TOTAL CPU SYSTEM CPU SESSION CPU BATCH CPU MEM MGR CPU DISPATCH CPU CACHING CPU OTHER CPU CPU PAUSED IDLE CPU PHYS DISC SYSTEM DISC SESSION DISC BATCH DISC MEM MGR DISC LOGICAL DISC DISC UTIL TRANSACT/MIN FIRST RESP RESPONSE ANY LOGL IO ANY PHYS IO ANY MEM IO ANY UTIL CPU QUEUE DISC QUEUE MEMORY QUEUE IMPEDE QUEUE NUM JOBS NUM SESSIONS ACTIVE JOBS ACTIVE SESS Table 7-1. Global Performance Items Description Total percentage of CPU busy.
Within Syntax Statements Performance metrics may be selected for a single application as de ned in the PARM le. The syntax for specifying an application performance item is application name:application item where application name exactly matches one of the APPLICATION= strings de ned earlier in the PARM le (including upper/lower case), and an application item is chosen from the list below. Table 7-2.
Within Syntax Statements Variable Substitutions in Commands You can substitute any performance item or user variable into a THEN or FINISH command before it is executed. To do so, enter an exclamation point (!) followed by the name of the item or letter of the user variable desired. For example, if the global CPU value was 54.3 , the command :TELL MANAGER.SYS; The cpu is now !TOTAL CPU% would execute as :TELL MANAGER.SYS; The cpu is now 54.3% You can make multiple substitutions on a single command line.
Within Syntax Statements Examples VAR A = SYSTEM DISC + SESSION DISC VAR B = A + BATCH DISC (All user disc IO.) ALARM="Session CPU is too High" TYPE=CPU SEVERITY=5 IF SESSION CPU > 70 FOR 20 MINUTES THEN :TELLOP Session CPU = !SESSION CPU% FINISH :TELLOP Session CPU now down to !SESSION CPU ALARM="Disc Rate Bug" TYPE=DISC SEVERITY=10 IF PHYS DISC < VAR B FOR 60; THEN :STREAM DCPJOB.COLLECT.HPPROBE REPEAT=1440 (Compare (But physical disc vs user disc.) don't do it more than once a day.
Within Syntax Statements Using Performance Collection Software Alarms To use an alarm, do the following: 1. Create a PARM le with the desired alarms and user variables. 2. Run the UTILITY program. Enter the PARMFILE command and specify the name of the PARM le containing the alarm de nitions. If any errors are reported, correct them before proceeding. You may specify the Performance Collection Software log le start and end dates, etc., then enter the SCAN command.
Within Syntax Statements Using UTILITY to Filter Log Files You can use the UTILITY program to process alarms against an existing Performance Collection Software log le to decide if the log le contains situations that you will want to study in more detail. While it is easy to perform this operation interactively, as described earlier, it might be best to perform this task in a more automated fashion.
Within Syntax Statements The following batch job will (1) extract the last week's data from the raw log les, (2) scan it using the UTILITY program, then (3) DSCOPY it to a central system for analysis if it is interesting. !JOB SCOPE.SYS,SCOPE !RUN EXTRACT (Extract the last week's data) LOG LOGGLOB.SCOPE.SYS START TODAY-7 OUTPUT RXLOG,PURGE GLOBAL BOTH APPLICATION BOTH PROCESS DETAIL DISCSPACE DETAIL EXTRACT EXIT !RUN UTILITY (Now scan the extracted le.
8 What's New: Changes to Performance Collection Software The rst section of this chapter is intended for current users of HP LaserRX/MPE version A. It contains an overview of the enhancements made to version A to create Performance Collection Software version B.00.00 . Details of these changes were covered in preceding chapters. The changes and enhancements made to Performance Collection Software since the B.00.00 release are described in the second section of this chapter.
Within Syntax Statements New Log File Formats Log le formats have changed to add more performance metrics. These changes require that existing log les be converted to the new format before being used by this release of Performance Collection Software. See chapter 4 for details on the CONVERT command. Caution Your existing log les will be altered by the conversion process. If you did not back up your log les when you installed this release, you should back them up before you convert them. See chapter 1.
Within Syntax Statements The THRESHOLD directive can log a process that is using too much of a resource, whereas the WAIT THRESHOLD directive can log processes that are waiting too long to get access to a resource. This allows you to log the cause and e ect of a system bottleneck. Parameters of the WAIT THRESHOLD directive follow. Use these parameters to specify the percentage of the 1-minute sample interval that a process must wait for a resource (CPU, Disc, Memory, or Impede) before being logged.
Within Syntax Statements Use this parameter to apply more than one application de nition to the same application. This gives you more exibility in de ning the processes that belong to a given application. OR. Use these parameters to de ne disc-space logging groups. If no disc groups are de ned, disc space will be logged at the account level. DISCGROUP, GROUP.
Within Syntax Statements HCLSnnnn HCLSTnnn These les are created when a remote connection is made by Performance Collection Software or when the UTILITY program's VERSION command is executed. These les will be created in the LOGON group and can be purged at any time. A future release of cooperative services should eliminate the creation of these les. UTILITY Changes The following enhancements are made to the UTILITY program's functions: You no longer have to scan log les before resizing .
Within Syntax Statements You can use the CREATE command to create individual log les and specify their size in days or megabytes. New UTILITY functions include: Command-driven user interface. Online help. Terminal softkey support. The new functions enable you to: Direct reports to another output device. Use the CONVERT command to convert raw and extracted log les from the format of the earlier release to that of the current release. Examine a PARM le and report any errors.
Within Syntax Statements EXTRACT Changes EXTRACT and UTILITY have the same user interface. This new interface includes online help, softkey support, and the ability to redirect extract reports. The basic EXTRACT function remains unchanged: to extract data from raw or extracted log les, optionally subset or summarize the data extracted, and write it to a new extracted log le.
Within Syntax Statements Changes from Version B.00.00 to Version B.00.02 The changes and enhancements made to Performance Collection Software since the B.00.00 release are described here. Starting with MPE/iX B.40.00 (4.0) and MPE V G.23.00 (23) the Performance Collection Software can be installed or updated as a normal part of the MPE update procedure. Using the MPE update procedures should make it easier to install.
Within Syntax Statements Default thresholds have been adjusted: Threshold Old Value New Value MINTHINK 0.1 100 100 100 100 0.2 50 50 25 25 WAITCPU WAITDISC WAITIMPEDE WAITMEMORY Host Access to Data A new command, EXPORT, was added to the existing EXTRACT program. This command will create les containing selected Performance Collection Software data in formats suitable either for printing or for further analysis by other programs.
A MPE/iX Metric Information Introduction The MPE V and MPE/iX operating systems and measurement interfaces di er and as a result, performance data collected on the two systems di er. These di erences are discussed below: MPE/iX Measurement Di erences. MPE/iX versus MPE V Data Collection. MPE/iX Measurement Differences Some performance metrics are not available on all releases of the MPE/iX operating system. SCOPEXL is the Performance Collection Software data collector for MPE/iX systems.
Within Syntax Statements MPE/iX versus MPE V Data Collection The collector programs for MPE/iX (SCOPEXL) and MPE V (SCOPE) have identical functions. The programs have di erent names to prevent a user from executing the wrong version of the collector on a system. You can use the same PARM les to de ne applications, identify systems, and set thresholds. The log les created on both systems have the same names: LOGGLOB, LOGAPPL, LOGPROC, LOGDISC, and LOGALRM.
Within Syntax Statements Under MPE V, a logical I/O occurs when the le system requests the I/O system to transfer a block of data to or from a disc le. Under MPE/iX, a read attempt or write attempt occurs whenever a program requests the le system to transfer a block of data. These transfers can occur at each record, at each block (if multirecord I/O is done), or not at all (if mapped les are used).
B Service Level Agreements This enhancement to the SCOPEXL performance data collector adds a new application metric to an existing eld of the application record. No log le format changes are required. This metric can be used for service level agreements that contract for a certain percentage of terminal response times to be at or below a given level. For example, an agreement might specify that 95% of the terminal response times for the Order Entry application will be 1 second or less.
Within Syntax Statements You can easily assess conformance to a service level agreement by plotting the percentage of transactions that met the agreed upon values over time. A service-level violation occurs each time this percentage falls below the threshold value. By monitoring the percentage value before it drops below the threshold value, you might be able to avoid violations of the agreement.
Within Syntax Statements Recommendations 1. If only one application is included in the agreement, specify the SERVICE LEVEL FIRST= and RESPONSE= for that application. 2. If all or a majority of the applications are included in the agreement, specify high interesting process thresholds values|such as THRESHOLD RESPONSE=3000 FIRST=3000|then set the service level thresholds for each application.
C UTILITY SCAN Report Details There are three phases to a UTILITY SCAN report: Initial values. Chronological details. Summaries.
Within Syntax Statements DETAIL, NOTES, and ALARMS Commands Table C-1 shows what information is printed in all SCAN reports and in reports printed with DETAIL=ON, NOTES=ON, or ALARMS=ON commands. Table C-1. Information Contained in SCAN Reports Initial Values: Initial PARM le global information. Initial PARM le application de nitions. Printed only if DETAIL=ON Printed only if DETAIL=ON Chronological Detail: PARM le global change noti cations. PARM le application addition/deletion noti cations.
Within Syntax Statements Initial Values This section contains examples of the following initial values report phases: Initial PARM le global information. Initial PARM le application de nitions. Initial PARM File Global Information You must specify DETAIL=ON. This report lists the contents of SCOPE's PARM le at the time of the earliest global record in the log le. Later global-information change noti cations are based on the values in this report.
Within Syntax Statements Initial PARM File Application Definitions You must specify DETAIL=ON and have APPLICATION data in the log le. This report lists the name and de nition of each application at the time the rst application record is listed in the log les. Any application addition or deletion noti cations you receive are based on this initial list of applications. 01/03/90 12:36 APPLICATION(1)="OTHER" 01/03/90 12:36 APPLICATION(2)="Resource Sharing" FILE=@.PPC.SYS; @.PSPOOLER.SYS; PCLINK.PUB.
Within Syntax Statements Chronological Detail This section contains examples of the following chronological detail report phases: PARM le global change noti cations. PARM le application addition and deletion noti cations. SCOPE OFF time noti cations. Application-speci c summary report. SCOPE-generated notes. USER-generated notes. ALARM events. PARM File Global Change Notifications You must specify DETAIL=ON and have GLOBAL data in the log le.
Within Syntax Statements addition, deletion, or change noti cation. If the name of an application has not changed from that previously reported, it is not listed again. Note Application de nitions are not checked for changes at this time. They are listed when an application name is changed, but any change to an existing application's de nition without an accompanying name change is not detected. 01/31/90 21:11 APPLICATION 4 "COMPILES " WAS ADDED FILE=COBOL@.PUB.SYS; FORTRAN.PUB.SYS; FTN@.PUB.
Within Syntax Statements Application-Specific Summary Report You must specify DETAIL=ON and have APPLICATION data in the log le. This report can help you de ne applications. Use the report to identify applications that are accumulating either too many or too few system resources and those that could be consolidated with other applications. Applications that accumulate too many system resources might bene t by being split into smaller pieces.
Within Syntax Statements SCOPE-Generated Notes (Collector Shutdown) You must specify NOTES=ON (or NOTES=102) and have GLOBAL data in the log le. 01/30/90 10:56 NOTE [102] SHUTDOWN REQUESTED BY PURGING "RUN" FILE SCOPE can enter a note record in the global log le. Typically, it does this to indicate an important event such as its voluntary termination. In the example above, SCOPE notes that it is terminating voluntarily because the RUN le was purged.
Within Syntax Statements Each event listed will show the alarm number, how long the alarm has been active, and the alarm ID.
Within Syntax Statements Summaries This section contains examples of the following summary report phases: Process log reason summary. SCAN START and STOP actual dates and times. Application overall summary. SCOPE coverage summary. Log le contents summary. Log le empty space summary. Process Log Reason Summary You must have PROCESS data in the log le. This report helps you set the interesting process thresholds for SCOPE.
Within Syntax Statements The following is an example of a process log reason summary report: PROCESS SUMMARY REPORT 03/13/90 10:08 AM TO 03/30/90 8:48 AM THERE WERE 382.
Within Syntax Statements The last category, SHORT PROCESSES, is slightly di erent from the others. It lists the number of processes that were logged but that might not have been logged if the NOSHORT threshold had been used. SCAN Start and Stop This summary report will be printed if any valid data was scanned. It gives actual dates and times that the SCAN was started and stopped.
Within Syntax Statements Table C-2. Performance Alarm Summary Alarm Count Minutes 1 1 25 2 3 4 5 1 0 9 0 15 0 80 0 Description CPU is monopolized by sessions. Batch is starved for CPU. Disc utilization. Memory thrashing. Runaway terminal. Collector Coverage Summary This report is printed if any valid global or application data was scanned. It indicates how well SCOPE is being used to capture system activity.
Within Syntax Statements In the previous example, the total time was 108 days, 16 hours, 14 minutes, and 51 seconds. The number of times SCOPE was started is equal to the number of times SCOPE was restarted or the UTILITY command \SCOPE NEWPARM" was issued, plus one . Log File Contents Summary This summary is printed if any valid data was scanned. It includes the log le space and the dates covered. ------TOTAL-----TYPE RECORDS MEGABYTES GLOBAL 29864 10.32 (NOTE RECS) 187 0.01 APPLICATION 113017 11.
Within Syntax Statements The columns can be explained as follows: Column Explanation TYPE The general type of data being logged. Two special types exist: NOTES is the number of NOTES generated (SCOPE notes plus USER notes). These notes are actually kept with the global data but are listed separately in this report. OVERHEAD is the amount of disc space occupied (or reserved) by the log le versus the amount actually used by the scanned data records.
Within Syntax Statements Log File Empty Space Summary This summary is printed for each log le scanned. THE THE THE THE GLOBAL APPLICATION PROCESS DISC SPACE FILE FILE FILE FILE IS IS IS IS NOW 51.6% FULL WITH ROOM NOW 60.1% FULL WITH ROOM NOW 89.1% FULL WITH ROOM NOW 9.
Glossary This glossary contains an alphabetized list of terms associated with Performance Collection Software. alarm action The command that is executed when a performance alarm is started, repeated, or nished. alphanumeric A character set composed of numbers, letters, or a combination of both. application A Performance Collection Software application is a user-de ned group of related processes.
Within Syntax Statements ASCII An acronym for the American Standard Code for Information Interchange. ASCII is a set of standard codes representing letters, numbers, and special characters. ASCII codes are used to exchange information between computers and peripheral devices. ASCII le A text le that contains ASCII code representing letters, numbers, and special characters. The le does not contain any special nonprinting characters.
Within Syntax Statements default An option that is selected automatically by the system if it is not overridden by a user-selected option or an appropriate command. detail data Raw data that is collected every 5 minutes by SCOPE(XL). empty space The di erence between the maximum possible size of a log le and its current size. encryption/decryption A le-security mechanism that alters access to the contents of a le by making its contents unreadable by unauthorized users.
Within Syntax Statements le equations The MPE commands used to redirect the le attributes for programs. For example, you can use a le equation to change the name of an extracted le. FINISH A Performance Collection Software PARM le directive that speci es the alarm action to be taken when a performance alarm is no longer satis ed. global A quali er that implies the entire system. global data The data, logged to Performance Collection Software global log les, that contain measurements of systemwide activity.
Within Syntax Statements interesting process A process, logged into a process log le, that becomes interesting when rst created or terminated, or when it exceeds certain user-de ned thresholds. intervals The speci c Performance Collection Software time periods during which SCOPE(XL) logs data. log les Performance Collection Software data les that are either raw or extracted. Extracted log les are optimized for quick retrieval by the PC programs and can be copied to the PC for local access.
Within Syntax Statements MAINTTIME A Performance Collection Software PARM le directive that sets the time of day at which scheduled maintenance operations will be performed. MAXTHINK A THRESHOLD parameter that sets a lter used in calculating terminal response times. Any terminal transaction where the think time was greater than MAXTHINK seconds is ignored. measurement interface An HP 3000 performance data source used by Performance Collection Software's performance data collection facility.
Within Syntax Statements NOSHORT A THRESHOLD parameter that prevents the logging of any process that was considered interesting only because it was created or terminated and had a run time less than or equal to the NOSHORT parameter. parameters The options used to modify directive and command syntax to customize performance data collection. PARM A Performance Collection Software le that contains parameters that customize Performance Collection Software data collection.
Within Syntax Statements QUEUE A Performance Collection Software PARM le parameter used to select processes for an application based on their CPU execution queue. raw log le A le that contains summarized measurements of system data.
Within Syntax Statements rollback The process of deleting 25 percent of a log le's data, starting with the oldest data, to make room for new data. Rollbacks occur when the SCOPE(XL) program lls a raw log le. RUN le The le created by SCOPE(XL) to control the running of the collector. If the RUN le is purged, SCOPE(XL) will terminate. RXLOG The default le created by the EXTRACT program. This le can be accessed on the host (via remote le access) or downloaded to a PC workstation.
Within Syntax Statements SCOPEXL2 This is the daily, disc-space collection program for MPE/iX. It is run by the SCOPE(XL) program, as needed. SEPARATOR A directive in a report le that speci es the character used to separate elds in an exported le. The report le is used by the EXTRACT program during its EXPORT function. service level An agreement, usually between the data processing department and computer system users, that speci es the levels of acceptable service.
Within Syntax Statements summary data Raw data that is summarized into one data point per hour. It can be graphed on Performance Collection Software more quickly, since fewer data records must be handled to produce a graph. Summarization reduces the size of the global and application data to approximately one-tenth to one-twelfth of the detail data size. swap To transfer some or all of a process's main memory resources to or from slower mass memory (disc).
Within Syntax Statements throughput The number of transactions that occur in a computer during a given period. TODAY A keyword used in the EXTRACT and UTILITY programs to specify a starting or stopping date based on the current calendar date. transaction In Performance Collection Software, a terminal transaction begins when a terminal-user's input is completed (read complete) and ends when the next input can be accepted (initiation of next read to that terminal).
