How to set keywords for autoconfiguration policies

To set the autoconfiguration policies by means of keywords, perform the following:

• Select Edit profile options and policies from the HCD Primary Task Selection panel to invoke the Profile Options and Policies menu (Figure 81).
  Figure 81. Profile Options and Policies

  *--------------- Profile Options and Policies ----------------*
  |                                                             |
  |                                                             |
  | Select type of data to define.                              |
  |                                                             |
  |     1.  HCD profile options                                 |
  |     2.  Autoconfiguration policies                          |
  |     3.  LP groups for autoconfiguration                     |
  |     4.  OS groups for autoconfiguration                     |
  |                                                             |
  |                                                             |
  |  F1=Help     F2=Split    F3=Exit     F9=Swap    F12=Cancel  |
  *-------------------------------------------------------------*

• Select Autoconfiguration policies.
• This invokes the Autoconfiguration Policies dialog which displays the current value settings for autoconfiguration policy keywords as they are either explicitly set in the HCD profile data set or as they are defaulted by HCD. Use this dialog to revise or change the displayed keyword values.

  The autoconfiguration policies are saved in the HCD profile (see also Defining an HCD profile for information on how to edit the HCD profile data set).

  Figure 82. Autoconfiguration Policies

  *------------------------- Autoconfiguration Policies ------------------------*
  |                                                   Row 1 of 13 More:       > |
  | Command ===> ___________________________________________ Scroll ===> CSR    |
  |                                                                             |
  | Edit or revise autoconfiguration policies.                                  |
  |                                                                             |
  | HCD Profile : DOCU.HCD.PROFILE                                              |
  |                                                                             |
  | / Policy keyword           P Value +                                        |
  | _ AUTO_CHPID_EXCLUDE       N SYSA.0,00-09                                   |
  | _ AUTO_CHPID_INCLUDE       N SYSA.1,1A-1F                                   |
  | # AUTO_MATCH_CU_DEVNUM     Y YES                                            |
  | # AUTO_SS_ALTERNATE        Y 1                                              |
  | # AUTO_SS_DEVNUM_SCHEME    Y PAIRING                                        |
  | # AUTO_SUG_CU_RANGE        Y 0001-FFFE                                      |
  | # AUTO_SUG_DEV_RANGE       Y 0001-FFFF                                      |
  | # AUTO_SUG_DYN_CHPIDS      Y 2                                              |
  | # AUTO_SUG_LPGROUP         N ____________________________________________   |
  | # AUTO_SUG_OSGROUP         N ____________________________________________   |
  | # AUTO_SUG_STAT_CHPIDS     Y 6                                              |
  | _ AUTO_SWAD_EXCLUDE        N 1A                                             |
  | _ AUTO_SWAD_INCLUDE        N ____________________________________________   |
  | ***************************** Bottom of data ****************************** |
  *-----------------------------------------------------------------------------*

Column P is set to Y (for yes), if a change of the policy key value is active immediately. Value N denotes that the value change only becomes active with a new discovery. For more information, refer to How to change autoconfiguration policies during the autoconfiguration process.

You can scroll to the right in this list to see a Description column for each policy keyword. This column may display an existing user comment, which you can change, or you can specify a new comment.

For keywords that you may specify multiple times with different values, for example, AUTO_CHPID_EXCLUDE, actions Add and Delete are available from the context menu.

To retrieve an online explanation of a keyword, move the cursor into its Value column and press the F1 key.

The subsequent topics list and explain the available keywords for defining your desired autoconfiguration policy.

Exclude CHPIDs from the discovery

AUTO_CHPID_EXCLUDE

This policy specifies a single CHPID number or a range of CHPID numbers that are excluded from being used for discovery or channel path assignment for a specific channel subsystem (by giving its ID) or all channel subsystems (by specifying *) of a certain processor. The keyword can occur multiple times.

The following example specifies that CHPIDs 04, 20 to 2F, and 42 are not used for channel subsystem PROCA.0. CHPID 42 is also not used for all other channel subsystems of processor PROCA.

AUTO_CHPID_EXCLUDE = PROCA.0,04
AUTO_CHPID_EXCLUDE = PROCA.0,20-2F
AUTO_CHPID_EXCLUDE = PROCA.*,42

Include CHPIDs for the discovery

AUTO_CHPID_INCLUDE

This policy specifies a single CHPID number or a range of CHPID numbers that should be considered for discovery and channel path assignment for a specific channel subsystem (by giving its ID) or all channel subsystems (by specifying *) of a certain processor. The keyword can occur multiple times. If this option is specified, no other channel paths are considered.

The following example specifies that CHPIDs with numbers 04, 20 - 2F, and 42 are used for discovery and definition from channel subsystem PROCA.0. CHPID 42 may also be used from all other channel subsystems of processor PROCA. No other unspecified CHPID number for processor PROCA is considered for discovery and definition.

AUTO_CHPID_INCLUDE = PROCA.0,04
AUTO_CHPID_INCLUDE = PROCA.0,20-2F
AUTO_CHPID_INCLUDE = PROCA.*,42

If no value is specified for a given channel subsystem, all CHPID numbers (00 - FF) are considered for discovery and channel path assignment.

Control unit number should match base device number

AUTO_MATCH_CU_DEVNUM

This policy specifies whether for autoconfiguration definitions a control unit number should match the starting base device number.

If you specify YES (which is the default), the first base device is set to the same number as the control unit. If NO is specified, the device number of the first base device and the control unit number do not necessarily need to match.

Alternate subchannel set for proposed alias devices

AUTO_SS_ALTERNATE

This policy specifies the ID of the subchannel set in which newly discovered PAV alias devices are defined during an auto-definition process, provided that free device numbers are available in this subchannel set, and processors that have access to the device range, support alternate subchannels.

The default subchannel set ID is 1.

Subchannel set device numbering scheme

AUTO_SS_DEVNUM_SCHEME

This policy defines the scheme for assigning device numbers to PAV alias devices in an alternate subchannel set.

Supported schemes are:

CONSECUTIVE

The alias device numbers in an alternate subchannel set are consecutive to the base device numbers.

DENSE

The device numbers in an alternate subchannel set are densely assigned, that is, the next free device numbers in the assigned device number range are used.

PAIRING

Base and alias device numbers are assigned alternatively starting with, for example, device numbers xx00 and xx80 for base devices versus xx80 and xx00 for alias devices.

NONE

Device and control unit numbers are not automatically applied. Instead, HCD presents the new discovered control units with a control unit number 0000 in the Proposed Control Unit List and the new devices with starting device number 0000 in the subsequent Proposed Control Unit / Device List. You can thus manually insert free control unit numbers, respectively device numbers on the according lists, which are validated by HCD. HCD issues a message to notify you to assign the numbers.

If you work in attended operation mode, (that is, Show proposed definitions has been set to Yes in Figure 83), HCD once more offers you the opportunity to review your input by redisplaying both lists with the updated numbers after you pressed enter. All actions are now available on the lists as in any other setting of the AUTO_SS_DEVNUM_SCHEME policy.

Otherwise, if you work in unattended fast-path operation mode, HCD accepts the numbers you entered and processing proceeds.

PAIRING is the default.

Control unit number range for auto proposal

AUTO_SUG_CU_RANGE

This policy specifies the range of control unit numbers from which numbers for auto-defined control units are taken. If no value is specified, range 0001-FFFE is taken as default.

Specify the range according to the following syntax:

   nnnn-mmmm,   where:  nnnn is the lower range boundary,
                        mmmm is the upper range boundary.

Device number range for auto proposal

AUTO_SUG_DEV_RANGE

This policy specifies the range of device numbers from which device numbers for auto-defined devices are taken. If no value is specified, range 0001-FFFF is taken as default.

Note:

For AUTO_SUG_DEV_RANGE and AUTO_SUG_CU_RANGE, I/O Autoconfiguration avoids using device and control unit numbers in the 0000-00FF range in subchannel set 0. If you have no alternative number ranges available, you must configure the CUs or devices manually in this range.

Number of static CHPIDs to be assigned

AUTO_SUG_STAT_CHPIDS

This policy specifies the number of static channel paths to be assigned to a control unit definition, if it is auto-defined. At least one and not more than 8 static channel paths can be defined.

The default is 6.

Maximum number of dynamic CHPIDs

AUTO_SUG_DYN_CHPIDS

This policy specifies the number of dynamically managed channel paths allowed on a control unit definition, if it is auto-defined. A maximum number of 7 dynamic channel paths is allowed, however, the sum of AUTO_SUG_STAT_CHPIDS and AUTO_SUG_DYN_CHPIDS must not exceed 8.

The default is 2.

LP group for autoconfiguration

AUTO_SUG_LPGROUP

This policy specifies the name of a group of logical partitions to which discovered devices are assigned. If no name is set, devices are assigned to all partitions of the active sysplex. The reserved group name ALL signals this during autoconfiguration processing.

OS group for autoconfiguration

AUTO_SUG_OSGROUP

This policy specifies the name of a group of OS configurations to which discovered devices are assigned. If no name is set, devices are assigned to all OS configurations which correspond to the active LP group.

Exclude switch addresses from the discovery

AUTO_SWAD_EXCLUDE

This policy specifies a single switch address or a range of switch addresses that are excluded from being used for discovery or channel path assignment. Note that switch addresses have to be specified rather than switch IDs. The keyword can occur multiple times.

The following example specifies that switches with addresses 14 and 20 to 2F are not used for discovery and channel path assignments:

AUTO_SWAD_EXCLUDE = 14
AUTO_SWAD_EXCLUDE = 20-2F

If no value is specified, no switch is excluded from discovery and channel path proposal.

Include switch addresses for the discovery

AUTO_SWAD_INCLUDE

This policy specifies a single switch address or a range of switch addresses that can be used for discovery and channel path assignment. Note that switch addresses have to be specified rather than switch IDs. The keyword can occur multiple times.

The following example specifies that switches with addresses 14 and 20 to 2F can be used for discovery and channel path assignments. No other unspecified switch address is considered for discovery and channel path assignments.

AUTO_SWAD_INCLUDE = 14
AUTO_SWAD_INCLUDE = 20-2F

If no value is specified, all switch addresses in the range 00 to FF can be used for discovery and channel path proposal.