• If the Reset indicator (EI22RSET) is set on by the UIM for a VSAM data set during a logical data set dump, DFSMSdss resets the data-set-changed flag in the VTOC if the data set is successfully serialized and processed. DFSMSdss will not reset the data-set-changed flag for data sets dumped with RLS access and BWO data sets, even if EI22RSET is set on by the UIM.
• If the DB2® Source Bypass indicator (EI22DB2) is set on by the UIM during a logical data set copy operation, and RENAMEU is specified for a DB2 VSAM linear data set, then DFSMSdss does not verify that the old component duplicates the DB2 naming convention when it derives the new component name. Alternatively, if the EI22DB2 bit is set on, DFSMSdss generates a DB2 component name for the target component—provided the new cluster name (specified in the RENAMEU parameter) matches the DB2 naming convention.
• If the IMS™ indicator (EI22IMS) is set on, the caller is IMS.
• If the Shared SYSDSN ENQ indicator (EI22SSYS) is set on by the UIM for a VSAM data set during logical data set dump, DFSMSdss attempts to obtain a shared SYSDSN enqueue. If EI22SSYS is not set on, then the type of SYSDSN enqueue (shared or exclusive) that DFSMSdss attempts to obtain depends upon whether or not the SHARE keyword was specified.
• If the Mark-As-Recovery-Required indicator (EI22RRB) is set on by the UIM during logical restore, DFSMSdss marks the target data set as recovery required, provided that the target data set is SMS-managed.
• If the Log Information Passed indicator (EI22LINF) is set on by the UIM during a logical restore, then DFSMSdss uses the log parameter (EI22LPRM), the log stream ID (EI22LSID) and the LOGREPLICATE indicator (EI22LREP) as the log information for the target data set, provided that the target data set is SMS-managed. If EI22LINF is not set, or the target data set is not SMS-managed, then the contents of EI22LPRM, EI22LSID and EI22LREP are ignored.
• If the BWO_ALLOWED Passed indicator (EI22BWOP) is set on by the UIM during a logical restore, the DFSMSdss uses the BWO_ALLOWED field (EI22BWOA) for the target data set, provided the target data set is SMS-managed. If EI22BWOP is not set or the target data set is not SMS-managed, then the contents of EI22BWOA are ignored.
• Serialization is bypassed if the UIM exit turns on the Bypass Serialization indicator, EI22BSER. Serialization is bypassed for the source data set for copy and dump processing, and for the target data set for copy and restore processing. DFSMSdss assumes that all necessary serialization has been performed by the invoker of DFSMSdss, but does not ensure that this is true. DFSMSdss performs normal serialization if the UIM exit does not turn on the bypass serialization indicator.

  DFSMSdss does not delete or uncatalog data sets that were bypassed for serialization even if the DELETE or UNCAT keywords are specified. If a preallocated data set is not large enough during a data set restore operation and the bypass serialization indicator is on, DFSMSdss does not scratch and reallocate that target data set and the restore operation fails.

• RACF® verification and all other data set security checking is bypassed if the UIM exit turns on the Bypass RACF indicator, EI22BSEC. If EI22BSEC is set on, DFSMSdss checks to ensure that the application program is authorized to bypass RACF and security processing. The application program is authorized to bypass RACF and security processing if NOPASS was specified on the PPT statement of the SCHEDxx parmlib member. If the EI22BSEC indicator is on and NOPASS was specified, RACF verification and all other data set security processing including password checking is bypassed. DFSMSdss does not do any RACF authorization checks. DFSMSdss does not create any RACF profiles for the copied or restored target data set. DFSMSdss assumes that all necessary RACF authorization and security checking has already been performed by the invoker of DFSMSdss. For a copy or restore operation, RACF profiles are not created for the target data set.

  If the user turns on the bypass RACF indicator and PASS was specified on the PPT statement of the SCHEDxx parmlib member, DFSMSdss sets the error flag, EIXERR, on in the exit identification block and invokes the UIM again. If the user sets the bypass RACF indicator again, DFSMSdss issues error message ADR772W and processing continues as normal. DFSMSdss still allows serialization to be bypassed and tolerates migrated volume serial number processing if those indicators are set.

  DFSMSdss performs normal RACF and security processing if the UIM exit does not turn on the bypass RACF indicator.

• If the Tolerate-Migrated-Volser indicator is set on by the UIM, DFSMSdss takes special action to support the restoration of a non-VSAM data set with a volume serial number of MIGRAT for a logical data set restore operation in an SMS-managed environment or when the CATALOG option has been specified. DFSMSdss ignores the EI22BMIG indicator for copy and dump operations and VSAM data sets.
  When DFSMSdss is restoring a non-VSAM data set and the Tolerate-Migrated-Volser indicator is set on, a catalog LOCATE is issued to determine the status of the data set being restored. Based on the result of that LOCATE, different actions are taken.

  No catalog entry is found:

  The data set being restored is not considered to be migrated. A normal DFSMSdss logical restore is performed. The Tolerate-Migrated-Volser indicator is ignored.

  A catalog entry is found but the VOLSER is not MIGRAT:

  The data set being restored is not considered to be migrated. Normal processing continues as though the indicator had not been set.

  A catalog entry is found and the VOLSER is MIGRAT:

  The data set is migrated and requires special processing. Instead of cataloging the data set after allocating it, DFSMSdss alters the existing MIGRAT volume serial number entry to the actual volume the data set was restored to. Once the catalog entry has been changed from MIGRAT to the new data set’s volume serial numbers, the restore continues as normal.

  Note: Because the migrated data set is not recalled during this restore, the user of this interface is responsible for deleting the migrated copy of the data set and updating the necessary control files.

  DFSMSdss performs normal non-VSAM data set cataloging if the UIM exit does not turn on the tolerate-migrated-volser indicator.

• If the Extent Reduction bit (EI22EXTR) is set on by the UIM for a given data set and DFSMSdss is running in an SMS-managed environment, DFSMSdss tries to allocate the original volume where the data set was dumped.
• If the Restore-To-Like-Device bit (EI22LIKE) is set on by the UIM for a given data set and DFSMSdss is running in an SMS-managed environment, DFSMSdss tries to allocate the target data set on a device whose unit is the same as that of the source data set. If DFSMSdss can not allocate the target data set on a device whose unit type matches that of the source, the data set is not processed.
• Serialization by enqueuing on the major name of SYSDSN for a data set is bypassed if the UIM exit turns on the bypass SYSDSN indicator, EI22NSYS; other enqueues for a data set (for example, SYSVSAM) are not bypassed. The SYSDSN-level of enqueue serialization is bypassed for the source data set for DUMP and the target data set for RESTORE. DFSMSdss performs normal serialization if both EI22BSER and EI22NSYS are turned off.

  DFSMSdss does not delete or uncatalog data sets if EI22NSYS is set, even if the DELETE or UNCATALOG keywords are specified. If EI22NSYS is on and the preallocated data set is too small, the data set is not scratched and reallocated, and the RESTORE fails.

If the UIM has set the "set reconnect" flag on, DFSMSdss then sets the reconnect flag in the catalog on. DFSMSdss ignores the EI22SFSM flag for VSAM data sets.

If the UIM exit sets the return code to EIRC16 but fails to turn on any of the bypass verification indicators, DFSMSdss ignores all bypass options and performs normally. If the UIM exit sets the return code to EIRC16 for a VSAM data set and turns on the tolerate-migrated-volser indicator, DFSMSdss does not treat it as an error condition and ignores the tolerate-migrated-volser indicator.

If a list of storage groups is passed by the UIM (EI22SGP) then the list is used to allocate SMS managed data sets during logical data set copy and restore. Users must take care to ensure that the storage groups passed do not conflict with the storage groups that would be assigned based on the storage class of the data set. A user may pass a maximum of 15 storage groups in the list. If the target data set is not SMS-managed then the storage groups passed are ignored.

If an ACS environment is passed by the UIM (EI22ACSEN), it is used in place of the DFSMSdss default environments (ALLOC for logical data set copy or RECOVER for logical data set restore). The ACS environment passed in is used when calling the management class and storage class ACS routines unless BYPASSACS indicates that one or both of the ACS routines should not be called. It is also passed to SMS on the allocation request. If EI22ACSEN specifies SPMGCLTR and a list of storage groups was not passed, DFSMSdss continues to process the data set in the default environments (ALLOC for logical data set copy or RECOVER for logical data set restore).

Refer to EIRC36 in Data set verification (Eioption 21) for details on ending spheres.