The IO command invokes I/O analysis of all peripherals.
Syntax
┌◄─────────────────┐
── IO ─┬─────────────────────────────────┬─┴─┬──────────────┬─┴────────┤
│ ┌◄────────────────────────────┐ │ ├─ SUMMARY ────┤
└─┴─┬─/1\─<unit spec>─────────┬─┴─┘ ├─ RESULTQ ────┤
└─/1\─ UINFO ─┬─────────┬─┘ ├─ GLOBALINFO ─┤
├─ NAMES ─┤ ├─ NOPHYS ─────┤
└─ ALL ───┘ └─ ACTIVE ─────┘<unit spec>
──┬─ UNIT ─┬────────────┬─<decimal number>────┬────────────────────────┤ │ ├─ INTERNAL ─┤ │ │ ├─ LOGICAL ──┘ │ │ ├─<unit type>──────────────────────┤ │ ├─ CATALOG ────────────────────────┤ │ ├─ OFFLINEUNIT ────────────────────┤ │ ├─ VOLUNIT ────────────────────────┤ │ ├─ TAPEUNIT ───────────────────────┤ │ ├─ VSUNIT ─────────────────────────┤ │ ├─ FAKEUNITS ──────────────────────┤ │ └─ BASEPACKS ──────────────────────┤ ├─ CHANNEL ─┬────────────┬─<decimal number>─┤ │ └─ INTERNAL ─┘ │ ├─ TAP ── INTERNAL ──<decimal number>───────┤ ├─ STSYS ─┬────────────┬─<decimal number>───┤ │ └─ INTERNAL ─┘ │ ├─ IOP ─┬───────────────────────────────────┤ │ └─<decimal IOP number>──────────────┤ ├─ SERVICE ─┬───────────────────────────────┤ │ └─ NOPHYS ──────────────────────┤ ├─ RECON ─┬─────────────────────────────────┤ │ └─ OUTSTANDING ───────────────────┤ └─ FAMILY ──<diskpack family name>──────────┘
<unit type>
──┬─ MT ──┬────────────────────────────────────────────────────────────┤ ├─ PK ──┤ ├─ DK ──┤ ├─ CD ──┤ ├─ HC ──┤ ├─ DC ──┤ ├─ DP ──┤ ├─ LBP ─┤ ├─ NP ──┤ ├─ VC ──┤ ├─ SC ──┤ ├─ LP ──┤ ├─ CP ──┤ ├─ CR ──┤ ├─ IP ──┤ ├─ HY ──┤ ├─ SP ──┤ └─ TSP ─┘
<AX options>
── ? ── AX ─┬─ BRK ───┬────────────────────────────────────────────────┤
├─ WHERE ─┤
├─ STOP ──┤
└─ SKIP ──┘Explanation
The following text describes the meaning of each construct.
IO
Analyzes each I/O peripheral and displays the result queues. Information global to the IO module is also extracted from the dump and analyzed.
IO CHANNEL INTERNAL <decimal number>
IO CHANNEL <decimal number>
This form of the IO command causes the presentation of the analysis of the channel-related MCP table associated with the selected number.
Use INTERNAL to indicate whether the decimal number is an internal channel number. If INTERNAL is not specified, the <decimal number> refers to an external channel number.
This form of the command is only valid for IOA systems.
IO TAP INTERNAL <decimal number>
This form of the IO command causes the presentation of the analysis of the tap-related MCP table associated with the selected number. This number only specifies an internal tap number.
This form of the command is only valid for IOA systems.
IO STSYS <decimal number>
IO STSYS INTERNAL <decimal number>
This form of the IO command causes the presentation of the analysis of the various storage system-related tables associated with the <decimal number>. Use INTERNAL to indicate whether the storage system number is an internal number. If you do not specify INTERNAL, the decimal number specifies an external storage system number.
This form of the command is only valid for IOA systems.
IO UNIT <decimal number>
IO UNIT INTERNAL <decimal number>
IO UNIT LOGICAL <decimal number>
Analyze the designated I/O peripheral. Each I/O peripheral is associated with a unique physical unit number. Enter that number as the decimal number.
Use INTERNAL or LOGICAL, respectively, to indicate whether the unit number is an internal or a logical unit number. If you specify neither INTERNAL nor LOGICAL, the decimal number specifies an external unit number.
The following example specifies an internal unit number:
IO UNIT INTERNAL 27
IO UNIT <unit type>
Analyzes all peripherals of the designated I/O peripheral unit type.
IO UNIT CATALOG
IO UNIT OFFLINEUNIT
IO UNIT VOLUNIT
IO UNIT TAPEUNIT
Provide specific table information about catalog units, off-line units, volume units, or tape units. To give significant information, these forms of the command must be followed by a UINFO option.
IO UNIT VSUNIT
Provides specific table information about the dummy unit used for the Volume Directory.
IO UNIT BASEPACKS
This form of the IO command provides unit information for all disk or pack directory (base) units. Unit information is presented in ascending logical unit order.
IO IOP <decimal IOP number>
This form of the IO command causes the presentation of the analysis of the various IOP-related MCP tables associated with the selected number:
<decimal IOP number>
This form of the command is valid only for IOA and IOP systems.
IO SERVICE
IO SERVICE NOPHYS
On IOA systems, this form of the IO command causes the presentation of the analysis of service units. If NOPHYS is specified, then the unit analysis excludes the physical IO table analysis.
IO RECON
IO RECON OUTSTANDING
Unit and path analysis is limited to those devices marked as “INVOLVED IN RECONFIGURATION” in MCP tables. OUTSTANDING further limits the analysis to only those devices for which UNITLASTIOOUTSTANDING is 1, meaning that the last MCP check for IOOUTSTANDINGONUNIT returned TRUE for this device.
IO FAMILY <diskpack family name>
This form of the IO command produces unit information for all disk or pack units that belong to the diskpack family as specified by <diskpack family name>. Unit information is presented in family member order, with the family directory (base) unit presented first.
IO UINFO
IO UINFO NAMES
IO UINFO ALL
If the UINFO option is specified by itself, provides a unit information analysis. A basic analysis of each I/O peripheral, identical to that provided by the IO form of the IO command, is given; in addition, a UINFO entry for each peripheral is given. The UINFO option lists the contents of each UINFO entry as an uninterpreted array.
When the UINFO NAMES option is used, it provides a columnar listing of the entries and the purpose of each word. The mass-storage lists and other arrays attached to the UINFO entry are not printed. These lists can be obtained by using the UINFO ALL option. The UINFO ALL option applies only to pack and disk.
IO ACTIVE
Specifying ACTIVE causes analysis of hardware active IOCBs to be included for each device analyzed. If SUMMARY is not specified, each active IOCB is fully analyzed. If both ACTIVE and SUMMARY are specified, most active IOCBs are output in brief form.
IO RESULTQ
Analyzes result queues that are otherwise suppressed. The following example analyzes all magnetic tape units, including the result queues:
IO UNIT MT RESULTQ
Basic IO analysis in the absence of a <unit spec.> includes a final section where each IOCB in the result queue is analyzed in brief. This section is the same as the output from a RESULTQ command specifying SUMMARY. Adding an explicitly RESULTQ specifier to a basic IO request causes each IOCB in the result queue to be analyzed in full, provided that SUMMARY was not also specified. If the presence of a <unit spec.> limits IO analysis to a particular device or devices, those IOCBs in the result queue for a particular device will be analyzed, either in full or in brief, as part of each individual device analysis. Adding RESULTQ causes the entire result queue section to be added after all individual device analyses.
IO SUMMARY
Provides a skeleton analysis of each specified I/O peripheral unit. The following example provides a skeletal analysis of all magnetic tape units, including the result queues.
IO UNIT MT RESULTQ SUMMARY
Specifying SUMMARY causes IOCB analysis to be completely omitted in some cases. Thus, a basic IO SUMMARY request completely omits analysis of IOCBs in the result queue. Most IOCBs that are analyzed will be output in brief rather than full form.
IO GLOBALINFO
Causes information that is global to the IO module to be extracted from the dump and analyzed. The following example input results in the analysis of all magnetic tape units and inclusion of the global IO module information in the output:
IO UNIT MT GLOBALINFO
IO NOPHYS
Reports on UNIT word and UINFO array (if selected). Suppresses reporting of physical I/O information and queued IOCBs.
<AX options>
Monitors and controls the display after you enter an IO ACTIVE command. The following table shows the AX options:
|
?AX Option (IO command) |
Description |
|
?AX BRK ?AX STOP |
Either of these options will cause DUMPANALYZER to abort the current command. DUMPANALYZER cancels the search without saving information from the search, and prompts you with the following message: :READY |
|
? AX WHERE |
Displays the location of the search, the number of the physical unit now being searched, and the number of active IOCBs found so far. The search occurs from the high end of memory toward 0; thus, memory indices printed in response to ?AX WHERE decrease. |
|
? AX SKIP |
Stops the search of the current unit, and skips to the next unit, if any. |
Example 1
The following example shows a portion of the output from an IO command for a tape unit.
Example 2
The following example shows partial output from an IO command with the NAMES option.
Example 3
The following example shows an example of UNIT record output that includes enhanced data recording capability (EDRC). Note that the example shows only the unit table record part of the display.
INPUT: IO UNIT 1360 UINFO ALL
########### MT 1360 INTERNAL UNIT 143 LOGICAL UNIT 57 ##########
0 3C8008 02C100 UNIT[039] MT 1360 (HALF-INCH CARTRIDGE / 38000 BPI)
LABEL READ, SCRATCH, WRITE RING, COMPRESSION:EDRCExample 4
The following is the display for the Storesafe control information, which is included in the IO UNIT display:
0 000000 000000 UNIT2[03A]
0 000033 010021 SSUINFO [03A]
000033 010021 000000 002001 STORESAFE STATUS STORESAFE ALERTS BEING ENFORCED or
STORESAFE ALERTS NOT BEING ENFORCED STORESAFE VOLUME IS BYPASSED
PK LSNI MIT MBR IX STATE SITENAME
nnnnn l i xxxxxx ssss(o) Where:
|
nnnnn |
External unit number |
|
1 |
Local Site Name Index (LSNI) (range 1–4) |
|
i |
MIT Member Index (range 0–3) |
|
xxxxx |
SUSPENDED, ALERT, MISSING, RUNNING |
|
ssss |
Storesafe Site Name (1–17 characters) |
|
(o) |
Site Name was overridden |
Sample display for a normal Storesafe volume:
(Two member Storesafe mirrored set (180, 181))
INPUT: IO UNIT 180
0 000033 010021 SSUINFO [03A]
000033 010021 000000 002001 STORESAFE STATUS STORESAFE ALERTS BEING ENFORCED
PK LSNI MIT MBR IX STATE SITENAME
180 1 0 RUNNING FIRST
181 2 1 RUNNING SECOND Sample display for a Storesafe volume in an alert:
(Two member Storesafe mirrored set (180, 181) where unit 181 has a Storesafe alert)
INPUT: IO UNIT 180
0 800233 010021 SSUINFO [03A]
800233 010021 000000 002001 STORESAFE STATUS STORESAFE ALERTS BEING ENFORCED
PK LSNI MIT MBR IX STATE SITENAME
180 1 0 SUSPENDED FIRST
181 2 1 ALERT SECOND The two words of SSUINFO information are displayed only if the specified unit is Storesafe named or a member of a Storesafe volume.
Example 5
The following is a partial example of the IO UNIT display for a non-mirrored unit whose unique site name is TR:
0 000000 000000 UNIT2[03A] 0 000033 010021 SSUINFO [03A] 000033 010021 000000 002001 STORESAFE SITE NAME IS: TR 0 000000 000000 UNITINFO[0080] UNIT INHIBIT TEST WAIT COUNT = 0, MODE = 0, TIMEOUT VALUE = DEFAULT
The two words of SSUINFO information and its site name are displayed only if the specified unit is storesafe named.
Example 6
The following is a partial example of the IO UNIT display for a mirrored disk whose unique site name equals MV:
0 000000 000000 UNIT2[03A] 0 000033 010021 SSUINFO [03A] 000033 010021 000000 002001 STORESAFE SITE NAME IS: MV MIRRORED UNIT, UNIT_MIT_INDEX=1158 SERIAL NUMBER = 00000802 MIT_ARRAY INFORMATION: UINFO LOGICAL UNIT = 143 (PK 802)
