HP 3000 Manuals HP 3000 Manuals
Changes from Version A to Version B.00.00 Command-Driven User Interface/Changes to Batch Files The command-driven user interface for UTILITY and EXTRACT replaces the prompt-and-answer dialog used in earlier versions of these programs. If you are using these programs in batch mode, you must alter your batch jobs to include the appropriate command syntax. See chapters 4 and 5 for more information.
NOTE Significant enhancements to the UTILITY and EXTRACT programs make it easier to conduct unattended batch operations. (For examples, see the WEEKLY, MONTHLY, and YEARLY EXTRACT commands.)
New Log File Formats Log file formats have changed to add more performance metrics. These changes require that existing log files 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 files will be altered by the conversion process. If you did not back up your log files when you installed this release, you should back them up before you convert them. See chapter 1.
Disc Space Metrics With this release of Performance Collection Software, you can elect to log disc space information by adding the DISCSPACE parameter to the LOG command in the PARM file. A new log file named LOGDISC is created when initial DISCSPACE logging takes place.. Disc space information is captured and logged once a day. The new DAILYTIME command lets you choose the time of day. A new program in the SCOPE.SYS group allows you to log disc space information. The name of the disc collector you use depends on your host operating system: * For MPE V, use SCOPE2. * For MPE/iX, use SCOPEXL2. Changes to the PARM File You need not change your PARM file unless you want to log disc space information or take advantage of the new THRESHOLD parameters or the new WAIT THRESHOLD directive. The THRESHOLD parameter's default values are listed in table 3-2. WAIT THRESHOLD. Use this directive to mark a process as interesting and log it if it spends too much of time waiting for a key system resource. 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 effect of a system bottleneck. Parameters of the WAIT THRESHOLD directive follow. CPU, DISC, MEMORY, IMPEDE. 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. New THRESHOLD Parameters. New THRESHOLD parameters follow. NONEW, NOKILLED. Use these parameters to prevent the logging of processes that are interesting only because they are new or killed but are otherwise uninteresting. NOSHORT. Use the NOSHORT parameter to reduce the disc space used for SHORT processes. A SHORT process is one that is created and terminated within a specified interval. Since a system might run many short processes each day, these processes could occupy a significantly large part of the process log file. MINTHINK, MAXTHINK. Use these parameters to fine-tune the algorithm SCOPE(XL) uses to filter terminal transactions. MINTHINK specifies the minimum user think time necessary to eliminate hardware-generated transactions, such as terminal status reads. MAXTHINK filters out the first transaction following a prolonged absence from the terminal, since such transactions might not be representative. Generally, you should not alter MINTHINK or MAXTHINK without careful planning, since you might drastically alter the transaction rates and response times reported by Performance Collection Software. QUEUE. Use this parameter to select processes for an application based on the dispatcher queue (L, A, B, C, D, E) in which they are executing. This is used in addition to the selection by program name, job or session type, and user logon. OR. Use this parameter to apply more than one application definition to the same application. This gives you more flexibility in defining the processes that belong to a given application. DISCGROUP, GROUP. Use these parameters to define disc-space logging groups. If no disc groups are defined, disc space will be logged at the account level. SCOPE(XL) Changes The functions of SCOPE(XL) remain the same, but the log files SCOPE(XL) creates are not backward compatible with HP LaserRX/MPE, version A. Many new performance and system-management metrics are logged without a significant increase in disc space used or the CPU overhead. The SCOPE.SYS group can contain the following new files: LOGDISC This disc space log file is created whenever the LOG DISCSPACE command is found in the PARM file. It can also be created using UTILITY, if you choose a size other than the default. STATUS This file appears automatically to log noteworthy events in the life of SCOPE(XL): starting, stopping normally or abnormally, resizing a raw log file, etc.. The file is a circular ASCII file and can be printed using the FCOPY command or the MPE/iX PRINT command. The file can be resized to hold more or less data, but be careful to preserve its characteristics (circular, record length, and other parameters). SCOPE2 This is the daily disc space collection program for MPE V. SCOPEXL2 This is the daily disc space collection program for MPE/iX. SCOPEIN This is a message file used for communicating between the UTILITY and SCOPE(XL) programs. SCOPEOUT This message file appears whenever UTILITY is awaiting a response from SCOPE(XL). It is purged automatically when the UTILITY program terminates. The SCOPEOUT file is created in the LOGON group of the user that runs UTILITY. It can be purged manually, if it remains after UTILITY is executed. Table 8-0. (cont.) HCLSnnnn These files are created when a remote connection HCLSTnnn is made by Performance Collection Software or when the UTILITY program's VERSION command is executed. These files 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 files. UTILITY Changes The following enhancements are made to the UTILITY program's functions: * You no longer have to scan log files before resizing. * You can specify log file resizing in days, in megabytes, or both. * More information is reported while scanning a log file: * You can list application definitions and names in a detailed report. * You can generate an application summary report showing the number of application records plus the percentage of the total CPU, disc, and terminal transactions for each application defined. * You can generate a process summary report showing the number of process records logged for each interest reason. You can use this report to fine-tune the PARM file THRESHOLD and WAIT THRESHOLD directives. * You can scan a portion of a log file by specifying the start and stop dates for SCAN. * You can display additional log file parameters and track their changes during a detailed SCAN. These new parameters include: Type of host system (3000/950, 3000/68, and so on). System serial number (or software serial number on MPE/iX). Operating system release (A.30.00). Total size of main memory. Number of processors (for multiprocessor MPE/iX systems). New parameters for the THRESHOLD and WAIT THRESHOLD directives in the PARM file. * You can list user- and SCOPE-generated notes. * You can use the CREATE command to create individual log files 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 files from the format of the earlier release to that of the current release. * Examine a PARM file and report any errors. This report also indicates how much room is left for defining applications. The resulting parameters can be listed, including any default values not specified in the PARM file. * Execute MPE commands without leaving the UTILITY program. * Use the VERSIONS command to print the version numbers of all the host Performance Collection Software files. It can also report any critical programs that are missing. * Communicate with SCOPE(XL) using the UTILITY program. You can perform the following actions: * Determine whether SCOPE(XL) is running. If it is running, then print out the current PARM file parameters and the percent-full values for the global, application, and process files. * Stop SCOPE(XL), and verify that it has terminated. * Use the SCOPE NOTE command to send a user note to the global log file. This note can be printed during the SCAN operation. It stays with the data even when it is extracted. * Have SCOPE(XL) resample its PARM file without stoping and restarting the collection process. Any PARM file value can be changed except the system ID. 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 files, optionally subset or summarize the data extracted, and write it to a new extracted log file. Existing functions are enhanced as follows: * Date and time formats can be customized to other languages using MPE's native language support (NLS) features. * Disc space data can be extracted. * MPE commands can be executed without leaving EXTRACT. * The process used to append data to an existing extracted log file was reworked significantly, maintaining the integrity and viability of the resulting log file. Maximum user flexibility is allowed as long as it does not produce a log file that is misleading or that can cause display errors. New EXTRACT functions include the following: * You can extract data using the WEEKLY, MONTHLY, and YEARLY commands. These functions give the extracted log file a unique name for each week, month, or year, and match the start and end of the extraction to the calendar week, month, or year. These functions simplify unattended remote extractions and help in archiving Performance Collection Software log file data.