{
{ CML$IOU_FAILURE_DATA
{
{
{ PURPOSE:
{    This statistic records the failure data captured by the system
{ following corrected or uncorrected IOU errors.
{
{ FREQUENCY: Each time DFT enters data into the maintenance
{            register buffers following each failure occurrence.
{
{ CONTENT:
{
{    The descriptive-data portion of this statistic contains:
{
{    '<mf>.<element>*<product id>*<serial number>*<symptom>'
{
{      where <mf> is the identification of the mainframe in the form
{        $SYSTEM_mmmm_ssss.  Where 'mmmm' is the model number of
{        Central Processor zero (CP0) and 'ssss' is the serial
{        number of that processor.
{
{      where <element> is the name IOU0, for IOU zero, IOU1 for
{        IOU1, etc.
{
{      where <product id> is the model number from the iou's
{        element identification register.
{
{      where <serial number> is the serial number from the
{        IOU's element identification register.
{
{      where <symptom> is the symptom/action statement provided
{        by the system. The text of the possible symptom statements
{        is identical in content to the uppercase text described
{        under counter value 2 below.
{
{    The counter-value portion of this statistic contains:
{
{    1. Operating System (OS) action code as described in section
{       4.2 of the DFT/OS Interface Specification. (DCS # ARH6853)
{
{    2. This word contains a 12-bit DFT analysis code followed by
{       an 8-bit sequence number stored in bits 44-63 of the word.
{       The sequence number indicates the sequential order in which
{       a series of statistics occurred, and ranges from 0-255(10).
{       Dedicated Fault Tolerance (DFT) analysis code is described
{       in section 4.4 of the DFT/OS Interface Specification. The
{       failure data should be analyzed in the order in which the
{       following codes are presented. (It should also be noted
{       that if bit 12 of the 12-bit hexadecimal DFT analysis code
{       is set, the error has occurred more than one time but is
{       being reported only once; e.g. code 003 will become 803.)
{
{       001 DEADSTART ERROR LOG IOU ERROR.
{       006 FATAL IOU ERROR (NIO; NOT PP HALT).
{       008 FATAL IOU ERROR (CIO; NOT PP HALT).
{       004 UNCORRECTED IOU ERROR (NIO PP HALT).
{       009 UNCORRECTED IOU ERROR (CIO PP HALT).
{       003 CORRECTED IOU ERROR (I4 ONLY).
{       007 IOU CHANNEL ERROR (NIO PP).
{       00B IOU CHANNEL ERROR (CIO PP).
{       005 12/16 IOU CONVERSION ERROR (NIO PP).
{       00A 12/16 IOU CONVERSION ERROR (CIO PP).
{
{     The content of words 3-63 is model dependent based upon
{     the DFT error analysis code. Packets of 5 words, each
{     consisting of a header word followed by the contents of 4
{     maintenance registers are stored sequentially. The header
{     word consists of 4 16-bit maintenance register addresses
{     stored from left to right that specify which register
{     contents are stored in the following four words. Sections
{     4.5.7 (code 3001), 4.5.2 (Codes 3007,3006,3004,2005), and
{     4.5.1 (Code 2003) of the DFT/OS Interface Specification
{     defines the maintenance registers and the order in which
{     their contents are stored for IOU errors.
{
  CONST
    cml$iou_failure_data = cmc$min_ecc + 1002;

*copyc cmc$condition_limits
