Hi,

The DSTAT command has not kept up with larger LDEV numbers and longer
disk model numbers. Currently LDEV numbers in DSTAT are restricted to
3 digits and model numbers are limited by 7 characters.  See output
below:

 :dstat all
    LDEV-TYPE    STATUS      VOLUME (VOLUME SET - GEN)
   ----------   --------    --------------------------
   1-C2474S      MASTER      MEMBER1         (MPEXL_SYSTEM_VOLUME_SET-0)
   2-C2474S      MEMBER      MEMBER2         (MPEXL_SYSTEM_VOLUME_SET-0)

The current version of DSTAT doesn't display model numbers that are
greater than 7 characters, for example the model ST118273WC.

The MPE Lab wants to fix these problems in DSTAT as well as provide
some additional information related to our new High Availability
disks, like the Nikes. We appreciate your feedback on this topic.

1) Is it preferred to not change the starting column for the MODEL and
   STATUS fields even if the data cannot fit the existing field width?

2) If 1) is 'yes' then is it ok to indicate truncation of the LDEV
   field with "***", and the model number field as 7 (or 11 - we have
   space for 11 characters) bytes with a "$" appended (per SHOWPROC,
   SHOWWG, LISTFILE,8 and HPEDIT).

2A) We have 11 bytes available for the model number. Is it ok to
    extend the model number to 11 characters in the existing output
    and only truncate if the model is longer than 11 chars? As of now
    we display only the first 7 characters of the model number.

3) If 1) is 'yes' then a new format is needed to display larger LDEVs
   and model numbers. Adding FORMAT=xxxx is consistent with several
   CI commands. The new syntax could be:

     DSTAT [ ldev | all ] [;format=detail ]

 *Note* the current dstat output would still be the default.
 ~~~~~~

4) We also want to display HAFO (High Availability failover)
   information. The question is should the HAFO output be included in
   the new format or should there be another command parm to indicate
   that the user wants to see hafo data? My preference now is to
   include the HAFO data with the new format.

5) If 1) is 'yes' then we need to propose a new output. The model
   numbers can be up to 38 bytes and ldevs can be up to 5 digits.

 The actual model number from the device consists of the following:

 Vendor          8 bytes
 Product #      16 bytes
 Revision level  4 byte
 HP Specific    10 bytes

 We can only display vendor and product number.

 The field names and their maximum widths in the proposed new output
 -------------------------------------------------------------------

 LDEV: nnnnn (5)
 MODEL: xxxxxxxxxxxxxxxxxxxxxxxx (24)
 VOLNAME: xxxxxxxxxxxxxxxx (16)
 VOLTYPE: MEMBER/MASTER/LONER/SCRATCH/PENDING/DISABLED/ERROR (8)
 VOLSET-GEN: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-nnnnn (38)
 PRIMARY PATH: xxxxxxxxxxxx (9)          Bigger for PCI and Fibrechannel
 PRIMARY STATUS: xxxxxxxxxx (8)
 ALT PATH: xxxxxxxxxxxx (9)              Bigger for PCI and Fibrechannel
 ALT STATUS: xxxxxxxxxx (8)
 EVENT TIME: hh:mm:ss (8)

 The above data includes all of the DSTAT info and all of the HASTAT
 info. This could be combined into a new "detail" DSTAT output.

 Important HAFO related fields
 -----------------------------

  PRIMARY PATH - path string for ldev

  ALTERNATE PATH - alternate path (DAM path) to which I/O will be
  rerouted for failover.

  PRIMARY STATUS - status or operational readiness of primary path.
  Status could be: array failure, failover failed, ready, test failover,
  unknown failure, unknown status

  ALTERNATE STATUS - status for alternate path. Status could be:array
  failure, failover failed, ready, unknown failure, unknown status, not
  validated

  EVENT TIME - formatted date and time of failover event. Events will
  be loged in the sysdiag file with additional time information.

 Here is a suggestion taking into consideration that DSTAT should be
 extensible to accomodate bigger PCI and Fibrechannel paths and bigger
 model names.

 The ALT PATH, ALT STATUS and EVENT line will be displayed only for
 HAFO devices. HAFO will be part of FOS.

 Here's what it would look like for several devices -- some HAFO,
 others not:

 :dstat all;format=detail

 LDEV:           31
 MODEL:          C2490AM-NIKE
 VOLNAME:        MEMBER1
 VOLTYPE:        MASTER
 VOLSET-GEN:     MPEXL_SYSTEM_VOLUME_SET-0
 PRIMARY PATH:   8.0.0
 PRIMARY STATUS: ready
 ALT PATH:       16.0.0
 ALT STATUS:     ready
 EVENT TIME:

 LDEV:           32
 MODEL:          C2390AM
 VOLNAME:        MEMBER2
 VOLTYPE:        MEMBER
 VOLSET-GEN:     MPEXL_SYSTEM_VOLUME_SET-0
 PRIMARY PATH:   8.0.1
 PRIMARY STATUS: ready
 ALT PATH:
 ALT STATUS:
 EVENT TIME:

 LDEV:           31
 MODEL:          C2490AM-NIKE
 VOLNAME:        MEMBER1
 VOLTYPE:        MASTER
 VOLSET-GEN:     MPEXL_SYSTEM_VOLUME_SET-0
 PRIMARY PATH:   9.0.0
 PRIMARY STATUS: failover
 ALT PATH:       17.0.0
 ALT STATUS:     ready
 EVENT TIME:     09:09:09


6) Is this format OK? Can you suggest some alternate formats?

7) Is there any other info. that you would like to see included as
   part of the DSTAT command?

Regards
Narayan ( Remove the q's from the address to reply )