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. 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 other methods of data movement when concurrent copy cannot be used or fails:

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 dump operation, you can also specify the NOTIFYCONCURRENT keyword, as follows:

NOTIFYCONCURRENT: Specifies that DFSMSdss is to issue an informational message for each 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 included in the concurrent copy operation.

Note:

Do not specify NOTIFYCONCURRENT with CONCURRENT(STANDARD | NONE).
You cannot use CONCURRENT(ANYPREF | ANYREQ | CACHEPREF | CACHEREQ |VIRTUALPREF | VIRTUALREQ) with the DELETE, UNCATALOG, or FCWITHDRAW keywords.
The RESET keyword is ignored if you specify CONCURRENT(ANYPREF | ANYREQ | CACHEPREF | CACHEREQ |VIRTUALPREF | VIRTUALREQ), unless you apply a patch to allow the reset function.
The use of concurrent copy and virtual concurrent copy with the DFSMSdss DUMP command is controlled by the RACF® FACILITY class profile, STGADMIN.ADR.DUMP.CNCURRNT.

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