Subtypes 47 and 49–User Resource Consumption Interval and Cumulative Record

Subtype 49 record is produced each time a user logs out from TIBCO Object Service Broker. It is also produced for all users logged in at the time of Data Object Broker shutdown. Subtype 47 is its corresponding interval record. Subtypes 47 and 49 have the same layout.

These subtypes report, in Data Object Broker units of work, the services provided to the Execution Environment user’s session. Session totals accumulate from login through logout or shutdown and are produced when the user exits from TIBCO Object Service Broker or when the Data Object Broker is shut down.

Corresponding Execution Environment Subtype

The subtype 49 record (produced by the Data Object Broker) corresponds to the Execution Environment record described in Subtype 62–Session Termination Statistics. Both records refer to the user and the session by these same parameters:

•

In subtype 49, the user ID can be found in the HU49UID field. The session number can be found in the HU49SSN# field.

•

In subtype 62, the user ID can be found in the HSRUUID field. The session number can be found in the HSRUNQID field.

The unique session identifier is assigned by the Data Object Broker at session initialization time. This identifier can be used to aggregate SMF data from both the Data Object Broker and the Execution Environment.

These fields enable the Data Object Broker to identify multiple and subsequent sessions by the same user across multiple Execution Environments. If the Data Object Broker has been recycled, use the RECORD TIME and RECORD DATE fields in subtype 62 with the T.O.D. WHEN DOB READY field in subtype 49. For specific details, refer to member TOD2YMD in the CLIST data set.

The unique session identifier is also published on the following records:

•

Data Object Broker: SMF 47 HU47SSN# field (session interval User Resource Consumption record). The identifier is assigned by the Data Object Broker at session initialization time. This field can be used to aggregate SMF data collected by the Execution Environment.

•

Execution Environment: SMF 60 HSRUNQID (Session Startup).

•

SMF 61 HSRUNQID (Session Termination).

•

SMF72 HSRUNQID (Execution Environment Transaction Statistics).

Further Discussion

Within an Execution Environment, data is seen logically as tables and rows. Session requests are passed to the Data Object Broker for execution and are tracked as follows:


User Event On Table	EE Request	Counted In Field ¹
Retrieve	Query	HU49QRY
Insert	Commit	HU49CMIT
Modify	Commit	HU49CMIT
Delete	Commit	HU49CMIT

HU49QRY + HU49CMIT = Inter-Region Message Count

Logical Requests are implemented by making physical TIBCO Object Service Broker page accesses.

Logical Requests


Logical Request	Physical Request	Counted in Field
Query	Data/Index/Rules Page Gets ¹	HU49GET
Query	Rules Page Gets	HU49RULE
Commit	Data/Index/Rules Page Puts	HU49PUT
Query/Commit	Input/Output	HU49READ HU49WRITE

For each page or rules Get, the required page could already be resident in the Data Object Broker Page Pool. Otherwise, required pages are fetched from DASD.

Physical Writes

MetaStor update activity is pooled, therefore physical writes cannot be attributed directly to a particular user. To estimate a fair cost for processing, the shared costs are distributed over all active users based on the number of logical puts they requested. This form of estimation is used to set HU47SRB, HU47FCPU, and HU47WRIT fields in the SMF subtype 47 and 49 records.

For Field name HU47SSN#, the identifier is assigned by the Data Object Broker at session initialization time. This field can be used to aggregate SMF data collected by the Execution Environment for a session. See the HSRUNQID field in EE SMF records 60, 61, 62, and 72.

The SMF record layouts are shipped in machine-readable format as assembler copybooks. For these subtypes, refer to HSMF45 in the MACRO data set shipped with TIBCO Object Service Broker. For details on how to print and use the record layouts and for a layout of this record type, see Using SMF Record Layouts Supplied as Assembler Macros.