User`s guide

Before running the Configure Utility, use the CLI> SHOW DEVICES command to
verify the list of devices that are currently connected to the HS array controller,
as shown in the following example. The example shows the Configure Utility as it
is run on an HSJ or HSD30 array controller. The text of the prompts may change
slightly when run on other controllers from the HS array controller family.
Note
Program names are limited to six characters. Therefore, to run this
program, use RUN CONFIG as your command.
HSJ> SHOW DEVICES
No devices
HSJ> RUN CONFIG
Config Local Program Invoked
Config is building its tables and determining what devices exist
on the subsystem. Please be patient.
add disk DISK100 1 0 0
add disk DISK120 1 2 0
add disk DISK140 1 4 0
add disk DISK210 2 1 0
add disk DISK230 2 3 0
add disk DISK500 5 0 0
add disk DISK520 5 2 0
add tape TAPE600 6 0 0
add tape TAPE610 6 1 0
Config - Normal Termination
HSJ>
HSJ> SHOW DEVICES
Name Type Port Targ Lun Used by
------------------------------------------------------------------------------
DISK100 disk 1 0 0
DISK120 disk 1 2 0
DISK140 disk 1 4 0
DISK210 disk 2 1 0
DISK230 disk 2 3 0
DISK500 disk 5 0 0
DISK520 disk 5 2 0
TAPE600 tape 6 0 0
TAPE610 tape 6 1 0
HSJ>
After you run the Configure Utility, you may have to initialize your containers
using the INITIALIZE command as described in Appendix B.
If a device somewhere in the cluster already has the PTL that the Configure
utility plans to assign, the program will assign an alpha character after the
numbers. For example, if another device is called DISK100, the utility assigns
the name DISK100A to the new device. (The utility compares this DISK100A to
the other PTLs in the cluster, and if DISK100A has already been used, the utility
increments to DISK100B and so forth). This avoids assigning duplicate device
names in the same controller.
7–58 Diagnostics and Utilities