REPRO Parameters

Before you begin: Be familiar with the following information before using REPRO parameters:

• Partial copying of linear data set clusters is not permitted. The entire linear data space must be copied. A linear data set cluster can be copied to or from a physical sequential data set if the control interval size of the linear data set is equal to the logical record length of the physical sequential data set.
• Using REPRO to copy linear data sets that are managed outside of VSAM and that do not abide to VSAM standards may produce unpredictable results. Such data sets include those managed by system logger. See z/OS MVS Diagnosis: Reference for more information.
• Attributes of data sets created by REPRO follow the same rules as those created by the JCL or by other utilities. Specifications of blocksize, logical record length, and blocking factors must be consistent with the type of data set and its physical characteristics. For more information, see the following documentation:
  • z/OS MVS JCL Reference
  • z/OS MVS JCL User's Guide
  • z/OS DFSMS Using Data Sets
• You cannot use REPRO to copy into a whole partitioned data set, but you can copy an individual member of a PDS or PDSE. You identify the member on the DD statements or dynamic allocations. If you copy a load module or a program object, the result will not be executable. This is because REPRO does not copy the control information.
• If you want to copy a KSDS that is larger than 4GB to a system that does not support extended addressability, you must use the FROMKEY and the TOKEY, or COUNT parameters to reduce the size of the data set or to create several smaller data sets.
• If you use the REPRO command to copy compressed files, the record count information is not provided and message IDC005I is not displayed.
• REPRO copies the records of a VSAM recoverable data set. However, the locks used for VSAM record-level sharing (RLS) are not transferred. For the correct procedure to use when copying or moving data sets with pending recovery, see “Using VSAM Record-Level Sharing” in z/OS DFSMS Using Data Sets.
• For VSAM data sets defined with SHAREOPTIONS (4 x), a default of 2 buffers will be chosen vs an increased buffer count calculated by CIs per CA.