Predefined Diagnostic Resource Object Class
The Predefined Diagnostic Resource object class (PDiagRes) identifies the resources supported by diagnostics and provides additional information needed to test the resource.
The PDiagRes object class structure is defined as:
class PDiagRes {
char Uniquetype[48];
short Ports;
short PSet;
short PreTest;
char AttUniquetype[48];
short SupTests;
short Menu;
short DNext;
vchar DaName[255];
char PkgBlock[5];
vchar EnclDaName[255];
vchar SysxApp[255];
vchar SupTasks[255];
long FFC;
short Fru;
long TestSuiteId;
long DiagEnvironment;
vchar KernExt[255];
char Version[5];
};
| Parameter | Description |
|---|---|
| Uniquetype | Predefined device "class/subclass/type." |
| Ports | Indicates if the device will be represented in the Resource
Selection menu by its children. The intent is to use device names
that are well known to the user (for example, printers rather than
serial ports). The values are as follows:
When determining whether a child device should be defined, consider whether the device is self-determining. Will the mkdev command be unsuccessful if the device is not really there? |
| PSet | Identifies the message set in either dcda.cat or the
diagnostic application catalog file reserved for the device. If the Ports field
is not equal to 0, the first message in the set describes the adapter
port. This adapter text is used in place of the real device text so
that the customers are not misled into thinking that they have devices
that are not actually present. The additional messages are used for
reason-code text, which the DAs name when reporting FRUs. The diagnostic application catalog file should be used by all diagnostic applications integrated into the Diagnostic Package. This capability allows for greater flexibility in installing and maintaining the diagnostic code. To use this catalog file, set bit DIAG_DA_SRN in the Menu field. |
| PreTest | Indicates that the device should be tested before the system is brought up. Pretest occurs when the system is initial-program loaded with the key in service position. The keyboard device, native serial ports, and display adapters are normally pretested. |
| AttUniquetype | The device class/subclass/type of the child device to define when the Ports field is set. The device named should include a set of device drivers that contain support for diagnostics. |
| SupTests | Identifies the types of tests supported by the DA. See Staging the Impact of Diagnostics for
more information. More than one of the following types may be specified:
|
| Menu | Identifies the diagnostic menus in which the device should
be included. The values are as follows:
|
| DNext | Indicates the resource to be tested next. The values are as
follows:
|
| DaName | The name of the DA associated with the device. |
| PkgBlock | The block number that includes the DA associated with the device for the Removable Media Diagnostic package. This value should be an "S" if the DA is on a Supplemental Diskette, or a "3S" if the DA is a graphics adapter that can be used as a console device. |
| EnclDaName | This field names a DA that provides missing-device analysis
for an enclosure that is not explicitly represented in the device
configuration, but that needs to be processed before the missing device.
Many enclosures have their own problem-determination procedures for
checking cabling, power, idiot lights, and so on, and frequently,
it is helpful to know if a sibling of the missing device in the same
enclosure is available. The specification of a separate DA to missing-device diagnostics for devices not represented (for example, external enclosures or drawers) centralizes this logic in a single command instead of distributing it among each DA supporting a device that can operate in a bridge box or drawer. For most devices, this field is null. The Diagnostic Controller calls the EnclDaName field, if the user indicates that the device has not been moved or turned off. The EnclDaName field is called before DaName. |
| SysxApp | Identifies the application to invoke that performs a system exerciser function for this resource. While not currently used, this is a reserved field, and should be left blank. |
| SupTasks | Reserved. This field is retained for compatibility and should not be used. For more information, see Predefined Diagnostic Attribute Device. |
| FFC | Failing Function Code for the resource. (may be used to override the PdDv led value) |
| Fru | Field Replaceable Unit indicator. (may be used to override
the PdDv fru value):
|
| TestSuiteId | Bit mask indicating test suite this resource is a member
of:
|
| DiagEnvironment | Bit mask indicating various test mode environments this resource
is capable of running in:
|
| KernExt | ',' separated list of kernel extensions to load for this resource. Each kernel extension may be preceded by a platform type to indicate the platform that the kernel extension should be loaded on. For example, chrp:device_kext, pdiagex would indicate to always load pdiagex, and to conditionally load device_kext only on a 'chrp' platform. The platform name is derived as the output from the lscfg | grep Architecture command. |
| Version | Version change number for this resource stanza. This value should be 1.0. |
Note: All values can be found in header files under /usr/include/diag directory.