Measurement session data report

The Measurement Session Data Report enables you to validate the Performance Profile and helps you focus your effort to improve application performance. The Measurement Session Data report contains the following sections:

• Job Environment
• Measurement Parameters
• Measurement Statistics
• Report Parameters

Measurement Session Data Report

AutoStrobe monitoring message

If the measurement was initiated by the AutoStrobe monitoring function, a message appears on the top of the Measurement Session Data report indicating the reason AutoStrobe monitoring initiated the measurement. The reason can be for:

• Batch applications: excessive elapsed time, excessive TCB time, or abnormal I/O activity.
• CICS transactions: excessive CPU time, excessive response time, or excessive execution rates.

Refer to the Using-Strobe-to-measure-online-applications-and-batch-programs for more information about AutoStrobe monitoring and measurement candidate processing.

Job environment

The Job Environment section enables you to confirm that the Performance Profile represents the job and program you intended to measure. It provides additional information, such as system identification and model number of the CPU, which can help you diagnose errors.

PROGRAM MEASURED

The name of the program in which execution of the target program or subsystem was initiated.

JOB NAME

The name of the job under which the target program or subsystem was executed.

JOB NUMBER

The Job Entry Subsystem (JES) number of the target job.

ADDRESS SPACE ID

The system-assigned identifier of the address space in which the target program or subsystem executed.

STEP NAME

The name of the job step, or of the procedure step and job step, in which the program or subsystem was executed. For nested procedures, the procedure step name in the invoking procedure and the step name of the invoked procedure appear. For further information about specifying the job step, Refer to the Using-Strobe-to-measure-online-applications-and-batch-programs.

DATE OF SESSION

The calendar date on which Strobe began measurement. The format of the date depends on the date format specified by the Strobe system programmer in the Strobe parameter dataset.

TIME OF SESSION

The time of day at which Strobe began measurement. The format of the time depends on the time format specified by the Strobe system programmer in theStrobe parameter dataset.

CONDITION CODE/COMPLETION CODE

The condition code or the completion code. If the target program terminated normally while it was being measured, this field shows the condition code. If the target program terminated abnormally, this field shows the completion code. The field does not appear if the measurement completes before the target program completes.

SYSTEM

The version and release level of the operating system that executed the target program or subsystem. Sometimes, to understand all aspects of performance you need to know the specific operating system version and release level.

DFP (or) DFSMS

The version, release, and modification level of DFP (Data Facility Product) or DFSMS (Data Facility Storage Management Subsystem) under which the measurement was performed.

SUBSYSTEM

The name of the subsystem and the parameters chosen when Strobe uses one of its options to measure a subsystem. Subsystem-specific reports appear only if this field contains the subsystem information. If you measured a subsystem application, verify that Strobe collected the appropriate subsystem data.

CPU MODEL

The model number of the central processing unit (CPU) that executed the target program or subsystem. Sometimes, to understand certain aspects of performance you need to identify the manufacturer’s CPU timing information for the specific CPU identified in the measurement session.

SMF/SYSTEM ID (or) SYSTEM ID

The System Management Facility (SMF) ID and MVS system name on which the measurement session was performed. If you are not using Strobe in a multisystem environment, the label SYSTEM ID appears with the value of the four-character SMF ID.

COUPLING FACILITY NAMES

For systems connected to MVS coupling facilities, the coupling facility names that were in use system-wide during the measurement. This field records a maximum of 32 coupling facility names.

LPAR

For OS/390 systems running in LPAR mode, the name of the logical partition in which the target job executed.

64-BIT ARCHITECTURE ENABLED

Indicator whether the zSeries operating system 64-bit architecture has been enabled at IPL time.

NUMBER OF zAAPs

The number of zAAPs (z-Series Application Assist Processors) on the measured LPAR. Appears when the LPAR on which a measured Java application ran used zAAP processors.

NUMBER OF zIIPs

The number of zIIPs (Z-Series Integrated Information Processors) on the measured LPAR. Appears when the LPAR on which a measured application ran used zIIP processors.

REGION SIZE BELOW 16M

The size of the region below the 16-megabyte address line available during the measurement session.

REGION SIZE ABOVE

The size of the region above the 16-megabyte address line available during the measurement session.

MEASUREMENT RELEASE

The release of the components of Strobe that gather performance data about the measurement application.

REPORTER RELEASE

The release of the Strobe reporter program. The Reporter is the component of Strobe that transforms Strobe measurement data into the reports in the Strobe Performance Profile.

PTF LEVEL

The number of the highest Program Temporary Fix (PTF), if any, applied to the Strobe system:

• 
  
  • The first number in the PTF level information indicates the highest PTF number for modules executed during the measurement session.
  • The second number indicates the highest PTF number for modules executed during reporting.
  • The third number indicates the PTF level that was supplied on your distribution media.

SAMPLE DATA SET

The name Strobe created and recorded internally for the sample dataset. If you renamed the sample dataset, the new name does not appear.

Measurement Parameters

This section identifies the parameters that Strobe applied to the request, specified by the user with an ADD, a CHANGE, or a SEND command, or on the appropriate Strobe/ISPF panel. Verify this section to ensure that Strobe applied the correct values to the measurement and attempted to collect the appropriate data. Some of these fields are optional—they appear only if you specify the associated operands on the appropriate Strobe/ISPF panel or on the ADD operation.

ESTIMATED SESSION TIME

The estimated duration of the measurement session, in minutes.

TARGET SAMPLE SIZE

The selected sample size. This value is the number of samples you requested Strobe to take during the estimated session time.

REQUEST NUMBER

The number that Strobe assigned to the measurement request. (A) indicates an active request, and (Q) indicates a queued request. An active request is a measurement request for a program that, at the time of the request, was currently executing. A queued request is a measurement request for a program that, at the time of the request, was not yet executing.

FINAL SESSION ACTION

The action that Strobe took when it reached the target sample size in its last measurement session. It gives the number of sample datasets created (blank if 1) followed by the final session action. The following session actions appear if you requested the measurement through Strobe/ISPF or specified the action through the Strobe command language:

• 
  
  • QUIT (stop sampling and terminate the request)
  • STOP (stop sampling and suspend the request).

REQUESTED START DATE

For scheduled measurement requests, the date you specified for the measurement to be submitted. The format of the date depends on the date format specified by the Strobe systems programmer in the Strobe parameter dataset. This field appears only if you are using the AutoStrobe scheduling function.

REQUESTED START TIME

For scheduled measurement requests, the time you specified for the measurement request to be submitted. The format of the time depends on the time format specified by the Strobe systems programmer in the Strobe parameter dataset. This field appears only if you are using the AutoStrobe scheduling function.

RETRY TIME INTERVAL

For scheduled active requests, the number of minutes that you want Strobe to wait before trying to initiate the measurement session again if Strobe initially cannot find the target job. This field appears only if you are using the AutoStrobe scheduling function.

RETRY INTERVAL COUNT

For scheduled active requests, the number of times you want Strobe to attempt to initiate the measurement session if Strobe initially cannot find the target job. The number in this field is the number of times remaining from the number of measurement session initiation attempts that you requested. This field is not shown in Measurement Session Data Report and appears only if you are using the AutoStrobe scheduling function.

REQUEST GROUP

The name of the request group of which this measurement request is an element. A request group is a collection of measurement requests that have been saved together under one name with the AutoStrobe measurement request group function. This field appears only if you are using this AutoStrobe function.

CONCURRENT SET NAME

The name of the concurrent set to which this request group element belongs. A concurrent set consists of two types of request group elements: a trigger request and one or more related requests. The trigger request is denoted with (T). This field appears only if you are using the AutoStrobe measurement request group function.

CONCURRENT SET ELEMENTS

The job names of the request group elements that comprise the concurrent set. The trigger request, if present, is denoted with (T), which appears to the left of the trigger request jobname. Strobe lists a maximum of 20 request group elements in this field. If the concurrent set contains more than 20 request group elements, a plus sign (+) appears to the right of the last request group element. This field appears only if you are using the AutoStrobe measurement request group function.

SYS REQ

The system(s) on which you selected to run your measurement request when you operate Strobe in a multisystem environment. If you specified that this request can run on any system in the SYSPLEX, this field will contain ALL SYSTEMS. If you select a list of systems, the list will appear in this field. If you chose to submit the request on all systems in the SYSPLEX except specified systems, a list of the excluded systems will appear with the label ALL SYSTEMS EXCEPT.

MODULE MAPPING BASELINE

The value of the BASELINE operand that you specified on the Module Mapping panel. Strobe does not map load modules with a percentage of execution samples less than this value. This field appears only if specified. For more information on module mapping, refer to the Using-Strobe-to-measure-online-applications-and-batch-programs.

BASELINE OVERRIDE

The names of modules for which Strobe obtained control section mapping information regardless of the percentage of execution samples gathered. Strobe maps these modules even if their execution of samples is less than what you specified for the MODULE MAPPING BASELINE field. This field appears only if specified.

LIBRARY

The names of the libraries specified in which Strobe located module mapping data. This field appears only if specified.

MAPPED SVCS

The SVC numbers for which you requested detailed reporting. Execution and wait within the modules invoked by the SVCs appears in subsequent reports in the Performance Profile. This field appears only if specified.

OPTIONS

The attribution or data collector operands that you specified. Review these options to verify those that you specified in your measurement request. For more information on specifying data collector options, refer to the Using-Strobe-to-measure-online-applications-and-batch-programs.

Measurement statistics

The Measurement Statistics section provides the highest-level summary of the system resources used during the measurement session. Verify this section to determine if Strobe collected enough data for you to improve performance and to guide your further investigation.

EXEC TIME PERCENT

The percentage of time during which the central processing subsystem (comprising one or more CPUs) was in use by application tasks executing within the measured job step. Strobe computes the value as the ratio of samples in which it observed one or more sites of execution to the total number of samples taken. A high execution time percent alerts you to focus on these reports:

• 
  
  • Program Section Usage Summary report
  • Program Usage by Procedure report
  • Attribution of CPU Execution Time reports
  • Most Intensively Executed Procedures report
  • Subsystem-specific reports that provide CPU consumption information.

WAIT TIME PERCENT

The percentage of time during which the central processing subsystem was available but was not in use by application tasks executing within the measured job step. The value is the ratio of wait samples to total samples. A high wait time percent alerts you to focus on these reports:

• 
  
  • Time Distribution of Activity Level report
  • Resource Demand Distribution report
  • Data Set Characteristics report
  • Data Set Characteristics Supplement report
  • VSAM LSR Pool Statistics report
  • I/O Facility Utilization Summary report
  • DASD Usage by Cylinder report
  • Attribution of CPU Wait Time report
  • Subsystem-specific reports that provide CPU wait time information.

RUN MARGIN OF ERROR PCT

The margin of error at a confidence level of 0.95 for the percentages shown in the Performance Profile reports that detail run time. The reports in the Performance Profile that detail run time are reliable within a range of plus or minus the RUN MARGIN OF ERROR PCT reported. A RUN MARGIN OF ERROR PCT of less than 2% usually reflects a reliable measurement. Check that this value is 2% or less to verify that you have collected enough samples to have a valid measurement.

CPU MARGIN OF ERROR PCT

The margin of error at a confidence level of 0.95 for the percentages shown in the Performance Profile reports that detail CPU time. The CPU MARGIN OF ERROR PCT signifies that the reports that detail CPU time are reliable within a range of plus or minus the CPU MARGIN OF ERROR PCT reported. A high CPU margin of error does not mean that the Performance Profile is invalid. Rather, it indicates that you should focus your analysis on the reports that detail WAIT TIME.

WAIT MARGIN OF ERROR PCT

The margin of error at a confidence level of 0.95 for the percentages shown in the Performance Profile reports that detail WAIT time. The WAIT MARGIN OF ERROR PCT signifies that the reports that detail WAIT time are reliable within a range of plus or minus the WAIT MARGIN OF ERROR PCT reported. A high WAIT margin of error does not mean that the Performance Profile is invalid. Rather, it indicates that you should focus your analysis on the reports that detail CPU time.

TOTAL SAMPLES TAKEN

The total number of samples collected during the measurement session.

TOTAL SAMPLES PROCESSED

The total number of samples selected for processing. This number may be lower than the value in TOTAL SAMPLES TAKEN. If Strobe collects twice the number of samples specified in TARGET SAMPLE SIZE, Strobe halves its sampling rate. Because Strobe collected more samples while it was sampling at a faster rate, Strobe needs to discard some of the samples collected. Strobe discards enough samples so that the samples processed and the information in the Performance Profile reflect an even distribution of samples over time.

INITIAL SAMPLING RATE

The rate at which Strobe took samples at the beginning of the measurement session, expressed in samples per second to the nearest hundredth. Strobe calculates the initial sampling rate based on the expected session duration and the target sample size (rate=size/duration). Strobe does not allow the sampling rate to exceed 500 samples per second.

FINAL SAMPLING RATE

The rate at which Strobe took samples at the end of the measurement session, expressed in samples per second to the nearest hundredth. If this rate is lower than the initial sampling rate, Strobe has automatically reduced the sampling rate at least once after collecting more than twice the target number of samples. Strobe processes measurements according to the sampling rate in effect at the end of the session. To maintain this distribution, it discards the appropriate number of samples taken at higher sampling rates. These discards do not affect the validity of the measurement, but a final sampling rate lower than the initial sampling rate suggests that you should increase your estimate of the program’s run time for later measurement requests. Strobe does not allow the sampling rate to exceed 500 samples per second.

CPU TIME

The amount of CPU time consumed by tasks executing in the measured job step, exclusive of the measurement task itself, expressed in minutes and seconds to the nearest hundredth. Because you are usually billed for the CPU time used, it is considered the most important measure of system resource time.

AS ENCLAVE TIME

Address Space enclave time, representing CPU consumed in a given address space for an enclave that is not included in the CPU TIME field.

SRB TIME

The time, expressed in minutes and seconds to the nearest hundredth, during which the system was executing Service Request Blocks (SRBs). SRBs represent high-priority service routines. Strobe provides SRB time for your information and does not detail it in subsequent reports. Because Strobe measures while running in task mode, it cannot measure activity running under an SRB. CPU time, which is the aggregate task time for all Task Control Blocks (TCBs) in the address space, does not include SRB time. SRB time that is high relative to CPU time could indicate an unusual or atypical type of processing and may warrant further investigation with other tools.

IND ENCLV TM

The amount of CPU time observed in independent enclaves. An independent enclave represents a complete transaction. Its performance goal is assigned based on the service class to which it is classified when the enclave is created. Each independent enclave starts in period 1 of its service class and switched periods based on the service consumed by dispatchable units belonging to the enclave.

DEP ENCLV TM

The amount of CPU time observed in dependent enclaves. A dependent enclave represents the continuation of an existing address space transaction under a new set of dispatchable units. Its performance goal is inherited from the existing address space transaction based on the service class (or PGN) and period being used to manage the address at the instant that the dependent enclave is created. CPU service consumed by a dependent enclave is treated as if it were consumed by the address space transaction, and can cause the address space along with the dependent enclave to switch to later periods.

SERVICE UNITS

The amount of CPU execution time that Strobe observed during the measurement session, not including the measurement task itself. A service unit is a machine-independent unit of work consisting of a fixed number of instructions.

SESSION TIME

The actual duration of the measurement session, expressed in minutes and seconds to the nearest hundredth. If Strobe could not close the sample dataset properly (for example, because execution of the job in the address space was canceled), a warning message appears in place of this field and no values appear in the remaining fields.

EXEC TIME

The amount of run time during the measurement session that one or more CPUs were executing tasks in the measured job step, exclusive of the measurement task itself, expressed in minutes and seconds to the nearest hundredth.

WAIT TIME

The estimated portion of run time during which no task within the measured address space was able to make use of the CPU time available to it, expressed in minutes and seconds to the nearest hundredth.

STRETCH TIME

The estimated amount of time that the CPU was unavailable to process programs executing in the measured address space because of demands made by higher-priority address spaces and by service request blocks (SRB) processing time for all address spaces. Stretch time may be high when multiple logical partitions (LPARs) are executing on the same complex of processors.

The value in the STRETCH TIME field reported on Measurement Session Data reports can vary widely, even when you run Strobe several times under what seem to be identical conditions. This discrepancy may result from a variation in system load.

MULTIPROCESSOR RATIO

The amount of CPU time consumed divided by the execution run time, expressed as a decimal number to the nearest hundredth.

ELIG JAVA EXECUTED ON zAAP

For Java programs, the percentage of Java eligible for processing on the zAAP processor that actually was executed on the zAAP processor.

EXCPS

The number of EXCP requests (direct invocations of execute channel programs, representing I/O) issued from the measured address space during the measurement session and the average rate at which they were issued. If a timing control table (TCT) was not in use during the measurement session, this value is zero.

A high EXCP rate correlated with high wait time alerts you to look for the causes of excessive I/O activity in the following reports:

• 
  
  • Data Set Characteristics report
  • Data Set Characteristics Supplement report
  • VSAM LSR Pool Statistics report
  • I/O Facility Utilization Summary report
  • DASD Usage by Cylinder report.

Report parameters

Verify this section to ensure that you have produced the Strobe Performance Profile with the detail that enables you to conduct your analysis efficiently. The following fields always appear in this section: DASD, DASDGAP, SORTSIZE, LINES/PAGE, and REPORT RESOLUTION. Examine these fields to validate modifications to the expected appearance of reports. The remaining fields appear only if specified. Refer to the Using-Strobe-to-measure-online-applications-and-batch-programs for additional information about these fields.

REPORT RESOLUTION

For a non-iStrobe profile, the specified target size in bytes for the codeblocks into which Strobe collected consecutive instructions for detailed reporting. The default value is 64 bytes. For more information, see Program-Usage-by-Procedure-report.

SORTSIZE

The specified sort core size available to the system sort/merge program.

LINES/PAGE

The maximum number of lines to be printed on each page of the Performance Profile. The default value is 60 lines per page.

DETAIL
The system modules or control sections the DETAIL parameter specified. Strobe normally combines all activity within system modules into pseudo-entities, printing a single line for each control section of a system module. For the specified modules, the DETAIL parameter overrides the compression of the specified modules. Refer to the Using-Strobe-to-measure-online-applications-and-batch-programs for a detailed description of the reporting parameters.

COMPRESS

The module prefixes that were specified to be compressed into pseudo-sections with the COMPRESS option.

DASDGAP

The number of inactive contiguous cylinders that Strobe can pass over while continuing to accrue resource use as reported on the DASD Usage by Cylinder report. A larger value in this field will make the DASD Usage by Cylinder report more concise. The report always  shows this parameter. The default value is five.

DASD=nn.n%

The baseline specified percentage of DASD usage that a cylinder must exhibit for Strobe to print a separate section in the DASD Usage by Cylinder report. The report always shows this parameter. The default value is 2%.

DDIODATE

Indicator whether a DDIO file should be used to index a source module when its date and time does not match that of the measured CSECT.

DDIOPCT=nn.n%

The minimum percentage of CPU activity a CSECT must exhibit to determine whether it should be indexed using a specified DDIO file.

DDFAVCPU=nn.nnnnn

The minimum average CPU time threshold (in seconds) that must be met or exceeded, before the activity of an SQL executing statement appears on the DDF reports. There is no default.
An executing statement executes SQL statements on behalf of a target statement.

DDFAVEXE=nn.nnnnn

The minimum average execution time threshold (in seconds) that must be met or exceeded, before the activity of an executing SQL statement appears on the DDF reports. There is no default.
An executing statement executes SQL statements on behalf of a target statement.

DDFCORID=xxxxxxxxxxxxCfv2ch3.fm

The maximum 12-character DDF correlation ID by which DDF reports are filtered. The DDF correlation ID must have been specified as a measurement parameter to use the DDFCORID report filter.

DDFDBRM=xxxxxxxx

The maximum eight-character DBRM name by which DDF reports are filtered.

DDFONLY= [YES|NO]

Indicator whether all Strobe reports for a Strobe for Db2 DDF measurement session are suppressed, except for the Measurement Data Session and the DDF reports: DDF SQL CPU Usage Summary, DDF SQL CPU Usage by SQL Statement, and SQL Statement by DBRM by Requester.

The default value is DDFONLY=YES, which suppresses reporting and is the recommended value.

DDFREQL=xxxxxxxxxxxxxxxx

The maximum 16-character DDF requester location by which DDF reports are filtered. The DDF requester location must have been specified as a measurement parameter to use the DDFREQL report filter.

DDFPRMID=xxxxxxxx

The maximum eight-character DDF primary authorization ID by which DDF reports are filtered. The DDF primary ID must have been specified as a measurement parameter to use the DDFPRMID report filter.

DDFSCDID=xxxxxxxx

The maximum eight-character DDF secondary authorization ID by which DDF reports are filtered. The DDF primary ID must have been specified as a measurement parameter to use the DDFSCDID report filter.

DDFTLCPU=nn.nnnnn

The minimum total CPU time threshold (in seconds) that must be met or exceeded, before the activity of a target SQL statement appears on the DDF reports. The default is DDFTLCPU=0.0.
A target statement is a user’s SQL statement.

DDFTLEXE=nn.nnnnn

The minimum total execution time threshold (in seconds) that must be met or exceeded, before the activity of a target SQL statement appears on the DDF reports. There is no default.
A target statement is a user’s SQL statement

NOMEMOBJ

Indicator that the z/OS Memory Objects report was suppressed and will not appear.

NOPROC

Indicator that the Program Usage by Procedure report was suppressed and will not appear.

NODSCS

Indicator the Data Set Characteristics Supplement report was suppressed and will not appear.

NODASD

Indicator that the DASD Usage by Cylinder report was suppressed and will not appear.

NOTRAN

Indicator that the Transaction Usage by Control Section report was suppressed and will not appear.

NOTASK

Indicator that the reporting of the execution of all tasks within the program is combined into a single line in the Time Distribution of Activity Level and Resource Demand Distribution reports. If NOTASK does not appear, these reports show a separate line for each task.

NOCRPT

Indicator that the C/C++ Section Usage Summary and CPU Usage by C/C++ function reports were suppressed and will not appear.

ALLCSECT

Indicator that a report line for each inactive control section that Strobe identified will appear in the Program Section Usage Summary report. If you do not specify ALLCSECT, the report does not list inactive control sections.

ALLTASK

Indicator that all tasks will appear on the Resource Demand Distribution report and the Time Distribution of Activity Level report. If you do not specify this parameter, the reports have separate entries for the six most active tasks, and the remaining tasks are grouped together, with their activity reported under OTHER.

ALLDD

Indicator that all ddnames will appear on the Resource Demand Distribution report and the Time Distribution of Activity Level report. If you do not specify this parameter, the reports have separate entries for eleven of the most active ddnames, and the remaining ddnames are grouped together, with their activity reported under OTHER.

MEISA

Indicator that the Performance Profile includes the Most Extensive Inactive Storage Areas report. The report is suppressed by default and does not appear unless specified.

WAITLOC

Indicator that relevant reports show the locations of wait within the program. If you do not specify WAITLOC, the reports provide the total wait time for each program without noting the locations.

PUBP=nn.n%

The specified baseline percentage of execution samples a codeblock must exhibit for Strobe to print a separate codeblock line in the Program-Usage-by-Procedure-report. The default value is zero.

TUCS=nn.n%

The baseline specified percentage of execution samples that a transaction must exhibit for Strobe to print a separate section in the Transaction Usage by Control Section report. The default value is zero.

ATTR=nn.n%

The baseline percentage of execution or wait samples that a system service must exhibit for Strobe to print an Attribution report. If the system service has less than the specified percentage of samples, Strobe does not print the report. The default value is 2%.

ATTRLINE=nn.n%

The baseline percentage of execution or wait samples an attributed module must exhibit for Strobe to include it in an Attribution report. If the module has less than the specified baseline percentage for a particular system service, Strobe does not print the detail line for the module in the report for the service. The default value is zero.

CRPT=nn.n%

The specified baseline percentage of execution samples a codeblock must exhibit for Strobe to print a separate line in the C/C++ Section Usage Summary and CPU Usage by C/C++ Function reports. The default value is 0.01%.

DATE FORMAT

The date format specified in the Strobe parameter dataset. This format appears on certain Strobe panels and Performance Profile reports.

TIME FORMAT

The time format specified in the Strobe parameter dataset. This format appears on certain Strobe panels and Performance Profile reports.

COLLHIST

Indicator that a measurement session history record was requested for this measurement session when the Performance Profile was produced. You can examine the measurement session history for a specific job step, DBRM, or a transaction. This field appears only if you are using the AutoStrobe history function.

DBRMBASE

The percentage of CPU execution samples a DBRM must exhibit for Strobe to save measurement session information for each DBRM in the history file. If the DBRM has less than the specified baseline percentage, it is not included in the measurement session history. This field appears only if you are using the AutoStrobe history function. The default baseline value is 1%.

TRANBASE

The percentage of CPU execution samples a transaction must exhibit for Strobe to save measurement session information for each transaction in the history file. If the transaction has less than the specified baseline percentage, it is not included in the measurement session history. This field appears only if you are using the AutoStrobe history function. The default baseline value is 1%.

REPJOB

The name specified to replace the job name in the measurement session history record. This field appears only if you are using the AutoStrobe history function.

REPSTP

The name specified to replace the step name in the measurement session history record. This field appears only if you are using the AutoStrobe history function.