IN FOCUSMFJAMS REPRO: Primary-Key Ranges, Replacement Rules, and Ignored IDCAMS Operands
MFJAMS REPRO supports targeted sequential and VSAM copying, but primary-key selection, default NOREPLACE, alternate-key maintenance, and silently ignored operands require careful validation. [1] [2] [3]
Read the full briefing
MFJAMS REPRO: Copying Records Is Not the Same as Rebuilding a VSAM Definition
Scope: Rocket Enterprise Developer 12.0 for Eclipse (UNIX), documenting mainframe utility emulation used with Enterprise Server.
Rocket's MFJAMS emulates a documented subset of mainframe IDCAMS access-method services. Its REPRO command copies records between sequential and VSAM data sets, making it useful for loading a VSAM file from a sequential source, copying one VSAM file into another, or extracting VSAM records into a sequential file. MFJAMS supports KSDS, ESDS, and RRDS management operations, and can run from a JCL jobstream or REXX exec. See VSAM Access Method Services (MFJAMS).
Understand what REPRO controls
REPRO accepts either a DD-name-based input, INFILE(ddname), or a named data set, INDATASET(data-set-name); the two are mutually exclusive, and one is required. Output similarly requires exactly one of OUTFILE and OUTDATASET.
For a KSDS, FROMKEY chooses the first primary key to copy; if it is absent, processing starts at the next higher key. TOKEY establishes the upper boundary, using the matching key, nearest higher key, or end of file. Neither option searches alternate indexes. SKIP specifies records to bypass and COUNT limits how many are copied. These controls permit a targeted record copy without redefining the source dataset. See REPRO.
The replacement and index nuances
For VSAM targets, REPLACE allows an incoming record to replace an existing record with the same primary key. NOREPLACE is the default; the two options cannot be combined. Separately, REUSE and NOREUSE determine whether the target can be opened as a reusable data set.
An easily overlooked behavior: MFJAMS automatically adds alternate-key entries to the output data set when those alternate keys were previously defined. That is different from using alternate indexes to select the input range; FROMKEY and TOKEY operate on the primary key only. See REPRO.
JCL wiring and compatibility boundaries
MFJAMS requires a SYSIN DD containing commands (in-stream input is allowed) and a SYSPRINT DD for its listing. SYSPRINT must have an LRECL of at least 121. REPRO can also use input and output DD statements with valid names corresponding to its INFILE and OUTFILE parameters. See DD Statements.
Do not assume every accepted IDCAMS operand has an effect. In REPRO, DBCS, INSERTSHIFT, INSERTALL, MERGECAT, SKIPDBCSCHECK, TOADDRESS, ENCIPHER, and DECIPHER are among the parameters parsed but ignored. ENTRIES/LEVEL and FILE are unsupported. More generally, Rocket warns that MFJAMS supports only its documented subset: unspecified functionality may be ignored or may cause failure. See REPRO and VSAM Access Method Services (MFJAMS).
Takeaway: When adapting IDCAMS REPRO jobs, verify primary-key range behavior, replacement policy, DD allocation, and every operand against MFJAMS's documented support—not merely whether the command parses.