CONCURRENT


>>-+----------------------------------------------------------------------+-><
   '-+-CONCurrent-+--+----------------------------+--+------------------+-'   
     '-CC---------'  |    .-+-PREFERRED-+----.    |  +-NOTIFYCONCurrent-+     
                     |    | '-ANYPREF---'    |    |  '-NOTIFYCC---------'     
                     '-(--+------------------+--)-'                           
                          +-CACHEpreferred---+                                
                          +-CPref------------+                                
                          +-VIRTUALpreferred-+                                
                          +-VPref------------+                                
                          +-REQUIRED---------+                                
                          +-ANYREQ-----------+                                
                          +-CACHEREQuired----+                                
                          +-CReq-------------+                                
                          +-VIRTUALREQuired--+                                
                          +-VReq-------------+                                
                          +-NOne-------------+                                
                          +-STANDARD---------+                                
                          '-STD--------------'

The CONCURRENT keyword specifies that the data is to be processed with concurrent copy except when CONCURRENT(STANDARD | NO) is specified. You can specify one of the following optional sub-keywords to indicate the type of concurrent copy to be used and whether DFSMSdss can use standard I/O when concurrent copy could not be used or has failed.

ANYPREFERRED or PREFERRED: Specifies that data is to be processed with concurrent copy. Virtual concurrent copy is attempted first, if the storage subsystem on which the data resides is capable of it and working-space data sets have been defined. Otherwise, cache-based concurrent copy is attempted if the storage subsystem is capable of it. If neither type of concurrent copy is possible or both fail, the data is processed with standard I/O. PREFERRED is the default if you specify the CONCURRENT keyword without a sub-keyword.
ANYREQUIRED or REQUIRED: Specifies that data is to be processed with concurrent copy. Virtual concurrent copy is attempted first, if the storage subsystem on which the data resides is capable of it and working-space data sets have been defined. Otherwise, cache-based concurrent copy is attempted, if the storage subsystem is capable of it. If neither type of concurrent copy is possible or both fail, the data is not processed.
CACHEPREFERRED: Specifies that data is to be processed with cache-based concurrent copy. If cache-based concurrent copy cannot be used or fails, the data is processed with standard I/O. DFSMSdss does not attempt to use virtual concurrent copy.
CACHEREQUIRED: Specifies that data is to be processed with cache-based concurrent copy. If cache-based concurrent copy cannot be used or fails, the data is not processed. DFSMSdss does not attempt to use virtual concurrent copy or standard I/O.
STANDARD or NONE: Specifies that data is to be processed with standard I/O as if the CONCURRENT keyword was not specified.
VIRTUALPREFERRED: Specifies that data is to be processed with virtual concurrent copy. If virtual concurrent copy cannot be used or fails, the data is processed with standard I/O. DFSMSdss does not attempt to use cache-based concurrent copy.
VIRTUALREQUIRED: Specifies that data is to be processed with virtual concurrent copy. If virtual concurrent copy cannot be used or fails, the data is not processed. DFSMSdss does not attempt to use cache-based concurrent copy or standard I/O.

For a logical data set copy operation, you can also specify the NOTIFYCONCURRENT keyword, as follows:

NOTIFYCONCURRENT: Specifies that DFSMSdss is to issue an informational message for every data set that is successfully included in the concurrent copy operation. If you do not specify NOTIFYCONCURRENT, DFSMSdss issues messages only for data sets that are not successfully included in the concurrent copy operation.

Note:

Do not specify NOTIFYCONCURRENT with CONCURRENT(STANDARD | NONE).
You cannot use the CONCURRENT keyword with the DELETE, UNCATALOG, because after the concurrent copy operation starts, the original data might still be updated.
You cannot use the concurrent copy option with FASTREPLICATION(REQUIRED) keyword.
The use of concurrent copy and virtual concurrent copy with the DFSMSdss COPY command is controlled by the RACF® FACILITY class profile, STGADMIN.ADR.COPY.CNCURRNT.
Cache-based and virtual concurrent copy operations are not affected if you specify the FASTREPLICATION(PREFERRED) keyword for the COPY command. If you specify both FASTREPLICATION(PREFERRED) and CONCURRENT keywords, DFSMSdss attempts to use fastreplication first.
Cache-based and virtual concurrent copy operations are not affected by RACF FACILITY class profile STGADMIN.ADR.COPY.FLASHCPY.

For help with determining concurrent copy storage requirements, see Concurrent copy storage requirements.

For more information about virtual concurrent copy and working space data sets, see Performance considerations and z/OS DFSMS Advanced Copy Services.