Using Measurement Session Data Reports


The Measurement Session Data report (see Measurement Session Data Report) describes the environment during a measurement session. When Strobe measures a job step that is executing Natural, the SUBSYSTEM field of the report shows the name and version number of the Natural nucleus program.

The format of the SUBSYSTEM field varies, however, depending on the number of different Natural releases running in the address space that is being measured. The formats are as follows:

Number of different Natural releases

Format

One

NATURAL X.X.X

Two

NATURAL XXX, XXX

Three

NAT XXX,XXX,XXX

More than three

NAT XXX,XXX,XXX+

(In this case, the three highest releases are shown, with the + indicating the presence of additional releases.)

In Measurement Session Data Report, the SUBSYSTEM field shows that there are two different releases of Natural running in the measured address space. The report additionally indicates that Strobe for CICS was invoked in conjunction with Strobe for Adabas/Natural by also showing the name and release level of CICS in the SUBSYSTEM field. If the program measured is using Natural for Db2 to access Db2 data and Strobe for Db2 is installed, the name and release level of Db2 would appear in the SUBSYSTEM field.

Choosing Between the Execution and Wait Reports

Wait time for a typical Natural 4GL application program is relatively high when there is intensive database I/O activity. Therefore, the value of EXEC TIME PERCENT may be much smaller than the WAIT TIME PERCENT value. Strobe for Adabas/Natural attributes wait time for Natural 4GL programs running under batch or TSO. For all other programs, use the Program Usage by Procedure reports to identify performance improvement opportunities. If you are:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Strobe 21.01