System Startup, Configuration, and Shutdown Reference Manual (32650-90907)

Chapter 5
Modifying Input/Output (I/O) Configurations
Using the IOCONFIG Utility
124
[[LMGR =]logicalmgrname]
[[MAXIOS =] maxconcurrentchannelIOs]
Listing an I/O Path with IOCONFIG
An I/O path is the system address assigned to the device interface hardware and the physical path used to
reach an I/O device. The system manager or operator can use the LISTPATH command to display information
about adapters and I/O devices on a specified path in the active configuration. The command lists the
configured I/O paths according to their paths or to their associated I/O manager. The syntax of the LISTPATH
command appears below:
LISTPATH [PATH= [path]
LEVEL= [#]
MANAGER= [manager name,...]
DEST= [OFFLINE] ]
The LEVEL parameter lists I/O paths at the level you specify:
• Enter 1 to display channel adapter information
• Enter 2 to display device adapter information
• Enter 3 to display device information
The MANAGER parameter lists the I/O paths associated with the given manager or managers, if the manager(s)
exist. If not, IOCONFIG displays a warning message.
Use the DEST parameter to send LISTPATH output to the file IOCLIST. This file remains open until you exit
IOCONFIG, at which point the file is closed and printed.
Deleting an I/O Path with IOCONFIG
The system manager or operator can delete an I/O path and all paths below it from the configuration with the
DELETEPATH command. IOCONFIG will only delete a path if it is not currently in use or if it does not have an
associated device. If either is true when you issue the DELETEPATH command, a warning message appears.
The syntax of the command is:
DELETEPATH [PATH =] device path
Currently, the only paths that can be completely deleted are those using a single-ended SCSI adapter.
Updating the Device Class Association Table with IOCONFIG
Many of the configuration commands implicitly update one or more system reserved device classes. For
example, the ADEV command when used to configure a tape device, implicitly adds the new device in TAPE
device class. Also, these commands explicitly update one or more device classes specified with the command.
The device class association information used by the ASSOCIATE and DISASSOCIATE commands is stored in
ASOCIATE.PUB.SYS. This file is built when the system manager runs the program ASOCTBL.PUB.SYS.
Therefore, after you have issued IOCONFIG commands, it is a good idea to update the file
ASOCIATE.PUB.SYS by running ASOCTBL.