openpower-pels/registry/README.md

27 the SRC reason code field for `BD` SRCs, or in the standalone `ComponentID`
28 field.
56 This field is part of the PEL User Header section, and is used to specify the
59 the time of PEL creation using the 'PEL_SUBSYSTEM' AdditionalData field. In this
68 This field is used by scripts that build documentation from the message registry
70 using the 'Subsystem' field. It is mutually exclusive with the 'Subsystem'
71 field.
79 This field is part of the PEL User Header section, and is used to specify the
80 PEL severity. It is an optional field, if it isn't specified, then the severity
109 This is an optional field and is used to override the Severity field when a
119 This field is part of the PEL User Header section, and is used to specify the
129 This field is part of the PEL User Header section, and is used to specify the
140 This field is part of the PEL User Header section, and is used to specify the
144 severity or if there are any callouts. As such, this is an optional field and if
157 This is an optional field and is used to override the Action Flags field when a
167 this is an optional field and if not present the value will be taken from the
178 the 8 character ASCII string field of the PEL. The allowed types are `BD`, for
198 the same as the first byte of the component ID field in the Private Header
209 string. This field in the message registry allows one to choose which SRC words
210 to use in addition to the ASCII string field to form the symptom ID. All words
226 specify which AdditionalData property field to get the data from, and also to
272 This field is used by the BMC's PEL parser as the description of the error log.
285 This optional field is required when the Message field contains the %X
308 This is an optional free format text field for keeping any notes for the
324 AdditionalData property field. Callouts will be added to the PEL in the order
440 #### Callouts example based on an AdditionalData field
484 AdditionalData field. When PROC_NUM was 0, the FRU at P1-C5 was called out. When
489 the AdditionalData field, one can use CalloutsWhenNoADMatch. In the following
531 This field can be used to modify the failing component type field in the callout
577 The 'JournalCapture' field has two formats, one that will create one UserData
579 any number of journal snippets based on the journal's SYSLOG_IDENTIFIER field.