Micro Focus Server Enterprise Edition for UNIX > Enterprise Server > Enterprise Server Configuration and Administration > Monitoring Enterprise Server > Collecting and Viewing Data on Transactions > Viewing HSF Information as a .csv File

Viewing HSF Information as a .csv File

If you have enabled the collection and writing of HSF records to disk, you can view details of individual runs of transactions in comma-separated files that you can import into a spreadsheet. These files contain one HSF record per line. The filenames are cashsf-a.csv and cashsf-a.csv.

Once the active file is full, or when you click the the Switch button in ESMAC, records are then written to the alternate file until the maximum file size is reached or the Switch button is clicked.

The files are saved in the system directory.

The .csv files have the header

#HSFVer=01
Type,PID,Task,Date,Time,Tran,User,LU,Prog,Latent,Resp,API,SQL,IMS,File1,Count1,Time1,File2,Count2,Time2,File3,Count3,Time3,File4,Count4,Time4,File5,Count5,Time5,TS1,Count1,Time1,TS2,Count2,Time2,TS3,Count3,Time3,TS4,Count4,Time4,TS5,Count5,Time5

and contain the following fields.

Important:

This version of the product generates cashsf-n.csv files that start with the line:

#HSFVer=01

HSF output from earlier versions of the product does not have this line.

Earlier .csv files do not have the IMS field, and have this header:

Type,PID,Task,Date,Time,Tran,User,LU,Prog,Latent,Resp,API,SQL,File1,Count1,Time1,File2,Count2,Time2,File3,Count3,Time3,File4,Count4,Time4,File5,Count5,Time5,TS1,Count1,Time1,TS2,Count2,Time2,TS3,Count3,Time3,TS4,Count4,Time4,TS5,Count5,Time5

Type

The type of task. One of:

CICS
IMS
JCL
WEB
CGI

PID

Process ID of the SEP which ran the task.

Task

A unique task number.

Date

The date the task started to run, in the format yyyymmdd.

Time

The time the task started to run, in the format hhmmsscc.

Tran

The name of task:

for CICS and IMS tasks, the transaction ID
for JCL, the job name
for Web services, the service name
for CGI programs, the program name

User

The ID of the user that initiated the task.

LU

for CICS tasks, the logical unit or net name (the identifier of the terminal used to initiate the task).
for JCL, either the step name, the JOBSTART constant indicator, or the job return code depending on the JCL record type. All three of these record types are generated for each JCL job.

Prog

for CICS and IMS tasks, the program name
for JCL, the program name or the job number, depending on the JCL record type

Latent

The time, in hundredths of a second, between Enterprise Server receiving the request and the task beginning to run.

Resp

The time, in hundredths of a second, that the task ran for (not including latency time).

API

The time, in hundredths of a second, spent in CICS API (EXEC CICS statements) for this task.

SQL

The time spent, in hundredths of a second, in SQL API (EXEC SQL statements) for this task.

IMS

The time spent, in hundredths of a second, in IMS DL/I API for this task.

The following additional fields may be repeated up to five times:

File(x): The name of a file that the transaction accessed.
Count(x): The number of times the transaction accessed this filex.
Time(x): The time, in hundredths of a second, the transaction spent accessing filex.
Ts(x): The name of a temporary storage queue (TSQ) that the transaction accessed.
Count(x): The number of times the transaction accessed Tsx.
Time(x): The time, in hundredths of a second, the transaction spent accessing Tsx.

Sample content viewed in Microsoft Excel