SMS considerations when using PDSEs with SMPTLIB data sets

If you do not use SMS…

If you are not using Storage Management Subsystem (SMS) to manage your storage, you can skip this topic.

If you let SMP/E dynamically allocate SMPTLIB data sets (instead of preallocating them yourself or predefining the DSNTYPE value to be used), SMP/E determines whether to allocate the SMPTLIB data set with a DSNTYPE value of PDS or LIBRARY, based on the format of the corresponding RELFILE data set. If SMP/E cannot determine the DSNTYPE of the RELFILE data set, SMP/E allocates the SMPTLIB data set using the DSNTYPE value specified in the SMPTLIB DDDEF. In either case, SMP/E specifies the DSNTYPE value to use for the SMPTLIB dynamic allocation and, as a result, any DSNTYPE value from the IGDSMSxx default is not used.

If SMP/E cannot determine what DSNTYPE value to use by either of the previously described methods, SMP/E does not pass a DSNTYPE value to dynamic allocation. The DSNTYPE is, in this case, determined by the system default or by the SMS subsystem.

Note: You should disable any existing ACS filter routines that force the allocation of an SMPTLIB data set with a particular DSNTYPE, because such routines will interfere with SMP/E's ability to specify the correct DSNTYPE itself.