Syntax

The complete syntax for the SETIOS command is:
 
SETIOS [MIH[,class=mm:ss[,class=mm:ss]...]
           [,MOUNTMSG={YES|NO}]
           [,DEV=([/]devnum[,[/]devnum]...[,[/]lowdevnum-[/]highdevnum]...)]
                  [,TIME=mm:ss]
                  [,IOTIMING=mm:ss]
           [,DCCF={MESSAGE|WAIT_STATE}
           [,MSGONLY={YES|NO}]
           [,IOTHSWAP={YES|NO}[,IOTTERM={YES|NO}]]
       [DCM={ON|OFF|REFRESH}]
       [MIDAW={YES|NO}]
       [FICON,STATS={YES|NO}]
       [CAPTUCB,PROTECT={YES|NO}]
       [STORAGE,IOSBLKS={24|31}]
       [HYPERPAV={NO|YES|BASEONLY}]
       [EKM[,PRIMARY={host_name[:port|,PRIPORT=port]}   ]
                     {ipv4_address[:port|,PRIPORT=port]}
                     {ipv6_address[,PRIPORT=port]}
                     {NONE}
           [,SECONDARY={host_name[:port|,SECPORT=port]}   ]
                       {ipv4_address[:port|,SECPORT=port]}
                       {ipv6_address[,SECPORT=port]}
                       {NONE}
           [,MAXCONN=dd1]
           [,MAXPCONN=dd2]
       [RECOVERY[,LIMITED_RECTIME=ss]
                [,DEV={DASD|IOTIMING}]
                [,PATH_SCOPE={CU[,PATH_INTERVAL=nn]  }]
                                [,PATH_THRESHOLD=nnn]
                             {DEVICE}
       [ZHPF={YES|NO}]
Start of change       [HYPERWRITE={YES|NO}]End of change

       	 
Note:
  1. The SETIOS command does not have an abbreviation.
  2. DEV and TIME together specify a user device class for one or more devices.
  3. DEV and IOTIMING together specify a user device class for one or more devices.
  4. During IPL (if the device is defined to be ONLINE), or during the VARY ONLINE process, some devices may present their own MIH timeout values, via the primary/secondary MIH timing enhancement contained in the self-describing data for the device. The primary MIH timeout value is used for most I/O commands. However, the secondary MIH timeout value may be used for special operations such as long-busy conditions or long-running I/O operations. Any time a user specifically sets a device or device class to have an MIH timeout value that is different from the IBM-supplied default for the device class, that value will override the device-established primary MIH time value. This implies that if an MIH time value that is equal to the MIH default for the device class is explicitly requested, IOS will NOT override the device-established primary MIH time value. To override the device-established primary MIH time value, you must explicitly set aside a time value that is not equal to the MIH default for the device class.

    Note that overriding the device-supplied primary MIH timeout value may adversely affect MIH recovery processing for the device or device class.

    Please refer to the specific device's reference documenatation to determine if the device supports self-describing MIH time values.

  5. IOTHSWAP and IOTTERM together specify how an I/O timing timeout condition is handled with respect to triggering a HyperSwap®.