#IBM z/OS Dataset Migration Using DFSMSdss

#Quick reference

• 1. Pre-Migration Planning
• 2. Source System Preparation
• 3. Compress Dump Dataset with TERSE
• 4. Transfer TERSE File via FTP
• 5. Unpack TERSE File on Target System
• 6. Target System Preparation
• 7. Restore Datasets on Target System
• 8. Post-Migration Tasks

---

#1. Pre-Migration Planning

#a. Inventory and Classification

• Identify datasets to be migrated.

• Classify by type, usage, and criticality.

• Document dataset names, volumes, and associated catalogs.

#b. Catalog and Alias Review

• List all user catalogs and their aliases.

• Identify any shared catalogs or aliases that need to be recreated.

#c. Identify if any New Catalogs need to be Created

↑ Return to Quick reference

#2. Source System Preparation

#a. Quiesce or Backup

• Quiesce applications using the datasets or ensure consistent backups.

• Use ENQ/RESERVE monitoring to confirm no active usage.

#b. Logical Dump with DFSMSdss

//DUMP EXEC PGM=ADRDSSU,REGION=0M
//SYSPRINT DD SYSOUT=*
//DUMPIN DD DUMMY
//DUMPOUT DD DSN=your.dump.dataset,DISP=(NEW,CATLG),
// UNIT=SYSDA,SPACE=(CYL,(100,50))
//SYSIN DD *
DUMP DATASET(INCLUDE(**your.dataset.list**))
LOGICAL
OUTDD(DUMPOUT)
BYPASSACS
TOL(ENQF)
SPHERE
CATALOG
/*
[↑ Return to Quick reference](#quick-reference)

↑ Return to Quick reference

#3. Compress Dump Dataset with TERSE

//TERSE EXEC PGM=AMATERSE,PARM='PACK'
//SYSUT1 DD DSN=your.dump.dataset,DISP=SHR
//SYSUT2 DD DSN=your.dump.terse,DISP=(NEW,CATLG),UNIT=SYSDA,
// SPACE=(CYL,(50,10))
[↑ Return to Quick reference](#quick-reference)

//SYSPRINT DD SYSOUT=*

↑ Return to Quick reference

#4. Transfer TERSE File via FTP

• Use binary mode to transfer the your.dump.terse file to the target z/OS system.

• Ensure FTP user has appropriate permissions.

↑ Return to Quick reference

#5. Unpack TERSE File on Target System

//UNTERSE EXEC PGM=AMATERSE,PARM='UNPACK'
//SYSUT1 DD DSN=your.dump.terse,DISP=SHR
//SYSUT2 DD DSN=your.dump.dataset,DISP=(NEW,CATLG),UNIT=SYSDA,
// SPACE=(CYL,(100,50))
[↑ Return to Quick reference](#quick-reference)

//SYSPRINT DD SYSOUT=*

↑ Return to Quick reference

#6. Target System Preparation

#a. Catalog Setup if new catalogs are needed

• USERCAT1

• USERCAT2

#Sample JCL to Create Catalogs

//IDCAMS EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE UCAT(NAME(USERCAT1) VOLUME(WRK001) -
CYLINDERS(5 1) -
RECORDS(100 50) -
SHAREOPTIONS(3,3) -
INDEX)
DEFINE UCAT(NAME(USERCAT2) VOLUME(WRK002) -
CYLINDERS(5 1) -
RECORDS(100 50) -
SHAREOPTIONS(3,3) -
INDEX)
/*

#b. Alias Setup

//IDCAMS EXEC PGM=IDCAMS
//SYSIN DD *
DEFINE ALIAS(NAME(your.alias) RELATE(your.user.catalog))
/*

#c. Storage Class and ACS Review

• Ensure storage class, management class, and data class definitions exist or are adapted.
• Review ACS routines to ensure compatibility.

↑ Return to Quick reference

#7. Restore Datasets on Target System

//RESTORE EXEC PGM=ADRDSSU,REGION=0M
//SYSPRINT DD SYSOUT=*
//DUMPIN DD DSN=your.dump.dataset,DISP=SHR
//SYSIN DD *
RESTORE DATASET(INCLUDE(**your.dataset.list**))
LOGICAL
INDD(DUMPIN)
SPHERE
[↑ Return to Quick reference](#quick-reference)

CATALOG
REPLACE
BYPASSACS
/*

↑ Return to Quick reference

#8. Post-Migration Tasks

#a. Validation

• Verify dataset integrity and accessibility.

• Confirm catalog entries and aliases are correct.

• Run test jobs or applications to validate functionality.

#b. Security Reapplication

• Reapply RACF or other security profiles.

• Validate access permissions.

  Note: All RACF-related work should be done via batch jobs to allow ease of recreation and auditing.

#c. Cleanup

• Archive or delete dump datasets.

↑ Return to Quick reference