Viewing HSF Information as a .csv File

Restriction: This topic applies only when the Enterprise Server feature is enabled.

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-b.csv.

Once the active file is full, or when you click 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=02
Type,PID,Task,Date,Time,Tran/Job,User/DDName/CC,LU/Step,Prog/DSName,Latent/ReadCount,Resp/WriteCount,
API/RewriteCount,SQL/DeleteCount,IMS/DSDeleteCount,DSType,DSAccessType,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,TD1,Count1,Time1,TD2,Count2,Time2,TD3,Count3,Time3,TD4,
Count4,Time4,TD5,Count5,Time5

and contain the following fields.

Important:

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

#HSFVer=02

HSF output from earlier versions of the product may either not have this line at all, or start with:

#HSFVer=01

Earlier .csv files do not have the DSType and DSAccessType fields, and either have this 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

or, without the IMS field:

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 record. One of:

WEB - for Web services

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/Job

The name of task:

For Web services, the service name.

Latent/ReadCount

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

Resp/WriteCount

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

SQL/DeleteCount

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

DSType

This field is blank for all records

DSAccessType

This field is blank for all records

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.
Count(x): The number of times the transaction accessed TDx.
Time(x): The time, in hundredths of a second, the transaction spent accessing TDx.

Viewing HSF Information as a .csv File

Sample content viewed in Microsoft Excel