Accessing the output from a hardware event data collection run

For authorized programs using the HISSERV interface, output from a collection run is delivered in storage. See z/OS MVS Programming: Authorized Assembler Services Reference EDT-IXG for details on the HISSERV interface and z/OS V2R1 MVS Data Areas Volume 2 (DDRCOM -IEFALCXT) for information on the HISYSERV, HISYEXIT, and HISYSMPX mapping macros. During a HIS Profiler run that requested counter-set data collection, the system writes the raw data to SMF record type 113, subtypes 1 and 2 at an interval defined by the SMFINTVAL parameter on the MODIFY hisproc,BEGIN command. The HIS Profiler may also write data to one or more of the following z/OS® UNIX System Services output files:

• Delta counter data file, which is optional. The system writes the delta data to the z/OS UNIX System Services .CNT output file at the end of the run. The delta data is the data from between when the instrumentation run was initiated and the end of the run, showing the delta incremental values of the instrumentation run on the specified processor. You can request that the system not create the .CNT file by specifying the CNTFILE=NO parameter on the MODIFY hisproc,BEGIN command.
• Load map file, which is optional. The system creates one .MAP file, if requested, at the end of the data collection run. This file contains the load module mapping information for the active system on which the data collection was done. The results will be more complete if the tracking of directed load modules is enabled with the SETPROG TRACKDIRLOAD command. See Tracking directed load modules.
• Sample data files, which are optional. The system creates one .SMP sample file for each active logical processor in the system. Sample data contains the addresses of the instructions being executed and the state information about a specific logical processor. Sample data is written out continuously when the data collection buffers become full.

For each data collection run, the system may generate one or more z/OS UNIX System Services output files in the HOME directory or the user-specified directory that follow the naming conventions below:

SYSHISyyyymmdd.hhmmss.xxx.CNT
SYSHISyyyymmdd.hhmmss.xxx.MAP
SYSHISyyyymmdd.hhmmss.xxx.SMP.cpu#

The files your data collection run generates will depend on the MODIFY hisproc parameters you specify when you start the run.

yyyymmdd

The year, month, and day when the MODIFY hisproc command was processed.

hhmmss

The hour, minute, and second when the MODIFY hisproc command was processed.

xxx

The sequence number of the collection run interval. This starts at 000 and is incremented by one for every state change detected during a collection run when the action specified for a detected state change is SAVE. For more information about collection run intervals, see the STATECHANGE parameter in Starting, configuring, and stopping hardware event data collection.

CNT | MAP | SMP.cpu#

Identifies the file, as follows:

• CNT identifies a counter set data file
• MAP identifies a load module mapping output file
• SMP.cpu# identifies a sampling function data file. cpu# is the CPU number, in hexadecimal. There is one .SMP file for each active CPU.

For example, the system creates the following z/OS UNIX System Services files for a system with 3 CPUs at 11:30:16 on 2007/05/15:

SYSHIS20070515.113016.000.CNT	
SYSHIS20070515.113016.000.MAP 
SYSHIS20070515.113016.000.SMP.0  (for CPU 0)
SYSHIS20070515.113016.000.SMP.1  (for CPU 1)
SYSHIS20070515.113016.000.SMP.2  (for CPU 2) 

Table 1 shows when the HIS Profiler generates the .CNT, .MAP, and .SMP files, based on the MODIFY hisproc,BEGIN parameters you specify:

To access the output the HIS Profiler generates in your z/OS UNIX file system in your HOME directory or the user-specified directory, use the OBROWSE command on the file, or else use the OGET command to copy the files to MVS™ and access the output data there.