SMS-related considerations

In a system managed by the storage management subsystem (SMS) you need to choose one of the following alternatives:

• The IODF data set is not managed by SMS. You can then specify the IODF volume serial number when creating an IODF.
• The IODF data set is managed by SMS. The automatic class selection (ACS) routines must be set up to automatically place the IODFs on the IODF volume. In this case SMS ignores the specified volume serial number except to pass it as a symbol to the ACS routines. The ACS routines, especially the storage group ACS routine, can use the volume serial number and the unit name to decide the SMS classes and the storage group.

You also have to consider that HCD dynamically allocates some data sets (with fixed naming conventions). These data sets are:

• The data set used for the activity log. For more information see Activity logging and change logging. If an ACTLOG data set does not yet exist, HCD dynamically allocates one, using ESOTERIC system defaults (ALLOCxx of SYS1.PARMLIB, respectively the UADS entry). You have to make sure that the entries in your ACS routines do not conflict with the SMS provided defaults. For example, if your ACTLOG data set name is not managed by SMS, whereas your default ESOTERIC defines an SMS managed volume, an allocation error might result. If you want to use a specific volume, specify a volume serial number to allocate a new activity log in the HCD profile (see Defining an HCD profile).
• The data sets used by HCD for the migration of IOCP/MVSCP/HCPRIO data (HCDPRINT, HCDASMP, HCDUT1, HCDUT2, HCDUT3). For detailed information refer to Insufficient data set sizes.
• The data sets used when building an HCPRIO or IOCP input data set (both named HCDDECK), and the data set used when creating JES3 Initialization Stream Checker data (named HCDJES3).