5.1.2. RTM Detail
The
RTM Detail
window displays a snapshot of the details of the selected RTM requests from the
RTM
Summary List
window. This may contain information from multiple servers, Gatekeeper, Core and
Mover. The actual data displayed will be different for each server type and is displayed in a tree
structure. Each node of the tree can be expanded/collapsed by clicking the mouse on the tree node
indicator. A new snapshot can be taken and added to the display by pressing the
Snapshot
button. The
tree can be cleared by pressing the
Clear
button.
Each detailed snapshot taken for an RTM request will contain the date and time the snapshot was taken at
the top of the tree. Below the date and time there will be an
rtm_req_detail_entry_t.
The fields contained in the
rtm_req_detail_entry_t
structure are;
ReqId.
The RTM request identifier.
UserName.
The printable username associated with this request (if available).
PathName.
The HPSS pathname of the file associated with this request (if available).
Oldest_StartTimeDelta.
Of all the RTM request records with this
ReqId
, this field holds the
age of the oldest when the snapshot was taken.
Newest_UpdateTimeDelta.
Of all the RTM requests records with this
ReqId
, this field holds
the age of the request most recently updated by its server when the snapshot was taken.
Oldest_ServerName.
The server holding the RTM request with the oldest age or
Oldest_StartTimeDelta
.
Newest_ServerName.
The server holding the RTM request with the most recent update age or
Newest_UpdateTimeDelta
.
Each server type that generates RTM request records (Gatekeeper, Core and Mover) has a server specific
RTM data structure which will be displayed as a tree node below the
rtm_req_detail_entry_t
node.
These structures are only displayed if there is a server of that type involved in the RTM request. There
will be multiple entries if there are more than one server involved in the RTM request.
The server specific RTM records are called;
rtm_gk_detail_entry_t (Gatekeeper)
rtm_core_detail_entry_t (Core)
rtm_mvr_detail_entry_t (Mover)
The server specific data structures each have a
Common
and
ReqInfo
structure embedded in them. The
Common
structure will contain the same fields for each server type.
The
Common
fields are;
HPSS Management Guide
November 2009
Release 7.3 (Revision 1.0)
146
Summary of Contents for RELEASE 7.3
Page 14: ...HPSS Management Guide November 2009 Release 7 3 Revision 1 0 14...
Page 195: ...HPSS Management Guide November 2009 Release 7 3 Revision 1 0 195...
Page 210: ...HPSS Management Guide November 2009 Release 7 3 Revision 1 0 210...
Page 215: ...HPSS Management Guide November 2009 Release 7 3 Revision 1 0 215...
Page 222: ...HPSS Management Guide November 2009 Release 7 3 Revision 1 0 222...
Page 266: ...HPSS Management Guide November 2009 Release 7 3 Revision 1 0 266...
Page 293: ...HPSS Management Guide November 2009 Release 7 3 Revision 1 0 293...
Page 367: ...HPSS Management Guide November 2009 Release 7 3 Revision 1 0 367...
Page 372: ...HPSS Management Guide November 2009 Release 7 3 Revision 1 0 372...
Page 384: ...HPSS Management Guide November 2009 Release 7 3 Revision 1 0 384...
Page 388: ...HPSS Management Guide November 2009 Release 7 3 Revision 1 0 388...