Diagnostic components

This section contains information on the various components that make up the Diagnostic Subsystem environment.

Diagnostic controller
The Diagnostic Controller function is started when the root user enters the diag command. Various flags that allow operations to be performed directly may be specified as input. For example, a flag may specify that the system or a particular resource is to be tested or that the system is to be run unattended. If no flags are specified, then the Diagnostic Controller presents menus to determine what the user wants to do.
Diagnostic applications
This topic describes the applications that are supported by the Diagnostic subsystem.
Tasks and service aids
The Diagnostic Package contains programs that are called Tasks. Tasks can be thought of as performing a specific function on a resource; for example, running diagnostics, or performing a Service Aid on a resource.
Application test units
Application Test Units (TU) are used by the Diagnostic Applications to test a device. Typically, due to either their large size or their functional composition, TUs are more appropriately written as applications as opposed to being included within device drivers.
Test unit 64-bit porting guideline
This porting guideline describes the required changes to the test units and SLIH in order to function under a 64-bit kernel.
Diagnostic kernel extension
This section describes the use of and programming interfaces to the Diagnostic Kernel Extension (PDIAGEX) and device configuration services.
Diagnostic library
This section provides information on application programming interfaces to administrative and user applications. The calls described are contained in the /usr/lib/libdiag.a diagnostic library.
Diagnostic object classes
This topic describes the types of various Diagnostic ODM object classes.
Diagnostic header files
All variables used by this guide should be found in one of the diagnostic header files.
Diagnostic user interface
The following sections describe how Diagnostic Applications and Diagnostic Tasks should use the interfaces provided in the Diagnostic Library to display the different screen types. The Diagnostic Subsystem supports various display environments. The menu interfaces are designed to be display environment independent, with the library routine(s) building the correct menu structures depending on the display environment.
Examples: Diagnostic menus
This topic describes the various examples of Diagnostic menu options.

Parent topic: Understanding the Diagnostic Subsystem for AIX

Related concepts

SLIH conversion required changes