Lines Matching full:record

30 The guard in the servers is for managing a record of faulty components to keep
33 record or manage the record will be decided by the respective component. Some of
39 can be isolated. The decision to create a record is based on the type of error,
41 system in a usable state. The record which gets created to isolate the component
42 is named as Guard Record. The guard record will be deleted after a repair action
44 record since the host is responsible for the initialization and use of the
50 various guard record sources.
58 - When user requests, create a record in the right guard record repository,
60 - An option should be given to user to create guard record for DIMM and
62 - An option should be given to the user to delete a guard record.
72 - The sub-system which owns the hardware resource will apply the guard record
76 - There should be a mapping between key in the guard record to the key used in
95 - Create Guard: Create guard record for a DIMM or Processor core Inputs: -
98 - Delete Guard: Delete an existing guard record Deleting the guard record D-Bus
99   entry should delete the underlying record.
112 - ID: Id of the record which is part of the entry object path.
138 interface should map between entry to the underlying guard record in the
139 original guard record store.
145 Creating manual gurad record, set the "Enabled" property to "false" to manually
175 ### Listing the guard record
215 isolatable to prevent any damage to the hardware or data. Once the record is
235   the guard record management by the user. A request for standardization is