Products   Support   Download   Contact

Registry and History Files

return to contents or index

Abstract

XENTIS is capable of tracking some aspects of usage. This is done with the Registry and History Files.

Q&A:

Question:

Please explain how the Registry and History files differ.

Answer:

Over the years, customers have told us that they have thousands of XENTIS command files (XCFs) scattered over their computer systems. They don't know which XCFs are being used and which ones are junk and can be deleted. The Registry file feature was designed to help customers solve this problem. The Registry file keeps a log of XENTIS Command Files that are being used. Over a period of time, say 15 months, of collecting Registry file data, a XENTIS site will be able to determine if a particular XCF is being used, and if so, how many times has it been used.

The purpose of the History file is a little bit different. Its purpose is to keep a log of resources that XENTIS uses. This allows a XENTIS site to track system usage and helps with capacity planning.

The format of the Registry file is very simple. It is a text file where each line is an entry containing a date, a time, and a filename. Each time an XCF is opened for processing or is created and processed, XENTIS will write a line to the Registry file.

The name of the Registry file is controlled by the Setup file parameter REGISTRY-FILE. The default value of this parameter is SYS$SCRATCH:XENTIS_REGISTRY.DAT. This means by default each user will have a Registry file in their default login directory. If you do not want a Registry file, then set the parameter value to "". For ease of reporting, you can also set the value to point to some central file location..

The System Utilities menu has an entry that allows you to create a report based upon the current Registry file. This report will prompt the user to include only those files whose usage count is above a certain minimum.

 

EXAMPLE:

XENTIS V4.5

REGISTRY FILE REPORT

PAGE1

XENTIS_REGISTRY.DAT  

31-OCT-1997

   

REGISTRY_REPORT.XCF;1

Count Filename

 

69 drive:[dir]DOVER1.XCF

54 drive:[dir]XENTIS.XCF

29 drive:[dir]BRUCE_TEST.XCF

29 drive:[dir]DOVER.XCF

26 drive:[dir.MAXCIM]FREDS_TEST.XCF

24 drive:[dir.MAXCIM]BEN.XCF

24 drive:[dir]A4_ALL_XEN_CUSTS_FILE_CREATE.XCF

24 drive:[dir]SUPPORT_RPT.XCF

23 drive:[dir]DAN.XCF

21 drive:[dir.MAXCIM]ITT.XCF

20 drive:[dir]CREPORT_TEST.XCF

20 drive:[dir]ROBIN.XCF

18 drive:[dir]KEYS.XCF

17 drive:[dir]1.XCF

 

The format of the History file is more complex than the Registry file. The record layout of the History file is documented in Appendix E of the XENTIS Reference Manual. Whereas the Registry file has a line for each XCF used, the History file has a record for report produced. Please note that one report can use multiple XCF's. The information kept in the History file includes:

User Name Terminal Node Name XENTIS Function
Process ID User's UIC Start Time End Time
CPU Used Page Faults Direct I/O Buffered I/O
Select Count File Count XCF Filename Data Filenames

 

EXAMPLE:

Field Name

Data Type

Field Size

User_Name

T Text

12

Terminal

T Text

8

Node_Name

T Text

6

Function

T Text

10

Process_ID

L Long

4

UIC_Member

W Word

2

UIC_Group

W Word

2

Start_Time

DA VMS Date

8

End_Time

DA VMS Date

8

CPU_Used

L Long

4

Page_Faults

L Long

4

Direct_IO

L Long

4

Buffer_IO

2 L Long

4

Select_Count

L Long

4

Primary_Count

W Word

4

File_Count

W Word

4

File_Names

CT2 Text

500

 

User_Name -- The OpenVMS user name.

Terminal -- The name of the terminal where XENTIS was. If used in batch, this field will be blank.

Node_Name -- The Decnet node name.

Function -- The XENTIS function (REPORT, UPDATE, etc.) used.

Process_ID -- The OpenVMS process Id (PID).

UIC_Member -- The member part of the process' UIC.

UIC_Group -- The group part of the process' UIC.

Start_Time -- The date and time XENTIS was started.

End_Time -- The date and time XENTIS completed.

CPU_Used -- The amount of CPU used between the start time the end time, measured in 1/100 second.

Page_Faults -- The number of page faults recorded between the start time and the end time.

Direct_IO -- The amount of direct I/O recorded between the start time and the end time.

Buffer_IO -- The amount of buffered I/O recorded between the start time and the end time.

Select_Count -- The number of records selected.

Primary_Count -- The number of primary data files used.

File_Count -- The number of data files used, not including extra primary files.

File_Names -- A list of filenames delimited by the pound (#) character, where the first name is the XCF filename, followed by the data file names. This field is variable in length.

 

The name of the History file is controlled by the Setup file parameter HISTORY-FILE. Unless specified otherwise the History file is located in the SYS$SCRATCH directory, which is usually a users default login directory. The default value of this parameter is XENTIS_HISTORY.DAT. To disable the usage of the History file, set the value of the parameter to "". For ease of reporting, you can also set the value to some central file location.

Do not type out the contents of the History file. It contains considerable amounts of binary data and will thus appear as garbage. To facilitate reporting on this file a temporary dictionary file can be found in the XENTIS<version>$REPORT$DATA directory. To create a report using the History file, you need to first copy the temporary dictionary file to the same directory as you targeted History file.

© 2020 GrayMatter Software Corporation