Abstract for DFSMShsm Implementation and Customization Guide
Summary of changes
Summary of changes
z/OS Version 2 Release 1 summary of changes
Implementing DFSMShsm
Introduction
How to implement DFSMShsm
Starter set
Starter set adaptation jobs
Functional verification procedure (FVP)
Installation verification procedure
DFSMShsm data sets
Control and journal data sets
Preventing interlock of control data sets
Migration control data set
Migration control data set size
MCDS size work sheet
Example of a MCDS calculation
Estimating the number of data sets (mds) using DCOLLECT
Backup control data set
Backup control data set size
BCDS size work sheet
Example of a BCDS calculation
Estimating the number of data sets (bver) using DCOLLECT
Offline control data set
Offline control data set size
OCDS size work sheet
Example of an OCDS calculation
Enabling the use of extended TTOCs
Journal data set
Journal data set size
Migrating the journal to a large format data set
Updating IFGPSEDI for the enhanced data integrity function
Specifying the names of the backup data sets
Defining the backup environment for control data sets
Steps for defining the CDS and journal backup environment
Improving performance of CDS and journal backup
Monitoring the control and journal data sets
Reorganizing the control data sets
Control data set and journal data set backup copies
Storage guidance for control data set and journal data set backup copies
Size of the control data set and journal data set backup copies
Considerations for DFSMShsm control data sets and the journal
Backup considerations for the control data sets and the journal
Migration considerations for the control data sets and the journal
Volume allocation considerations for the control data sets and the journal
RACF considerations for the control data sets and the journal
Translating resource names in a GRSplex
Determining the CDS serialization technique
Using VSAM record level sharing
Requirements for CDS RLS serialization
Multiple host considerations
Required changes to the CDS before accessing RLS
VSAM RLS coupling facility structures recommendations
Required CDS version backup parameters
Invoking CDS RLS serialization
Using multicluster control data sets
Considerations for using multicluster control data sets
Converting a multicluster control data set from VSAM key range to non-key-range
Determining key ranges for a multicluster control data set
Multicluster control data set conversion
Steps for converting to a multicluster control data set
Changing the number of clusters of a multicluster control data set
Changing only the key boundaries of a multicluster control data set
Updating the startup procedure for multicluster control data sets
Updating the DCOLLECT JCL for multicluster control data sets
Using VSAM extended addressability capabilities
Converting control data sets to extended addressability with either CDSQ or CDSR serialization
DFSMShsm problem determination aid facility
Problem determination aid log data sets
Planning to use the problem determination aid (PDA) facility
Determining how long to keep trace information
Problem determination aid (PDA) log data set size requirements
Controlling the problem determination aid (PDA) facility
Allocating the problem determination aid (PDA) log data sets
Printing the problem determination aid (PDA) log data sets
DFSMShsm logs
DFSMShsm log data set
DFSMShsm log size
Optionally disabling logging
Printing the DFSMShsm log
Edit log data sets
Printing the edit log
Activity log data sets
Activity log information for the Storage Administrator
Activity log information for the System Programmer
Controlling the amount of information written to the activity logs
Controlling the device type for the activity logs
Considerations for creating log data sets
DFSMShsm small-data-set-packing data set facility
Preparing to implement small-data-set-packing data sets
Defining the size of a small user data set
Allocating SDSP data sets
Specifying the SDSP parameter on the ADDVOL statement
Data mover considerations for SDSP data sets
VSAM considerations for SDSP data sets
Multitasking considerations for SDSP data sets
System data sets
Data set with DDNAME of MSYSIN
Data set with DDNAME of MSYSOUT
User data sets
User data sets supported by DFSMShsm
Physical sequential data sets
Physical sequential data sets and OSAM
Direct access data sets and OSAM
Direct access data sets
Hierarchical file system data sets
zFS data sets
Exceptions to the standard MVS access methods support
Size limit on DFSMShsm DASD copies
Supported data set types
Data set type support for space management functions
Data set type support for availability management functions
Specifying commands that define your DFSMShsm environment
Defining the DFSMShsm startup environment
Allocating DFSMShsm data sets
Establishing the DFSMShsm startup procedures
Primary address space startup procedure
Secondary address space startup procedure
Establishing the START command in the COMMNDnn member
Establishing SMS-related conditions in storage groups and management classes
Writing an ACS routine that directs DFSMShsm-owned data sets to non-SMS-managed storage
Directing DFSMShsm temporary tape data sets to tape
Establishing the ARCCMDxx member of a PARMLIB
Modifying the ARCCMDxx member
ARCCMDxx member for the starter set
Issuing DFSMShsm commands
Implementing new DFSMShsm ARCCMDxx functions
Defining storage administrators to DFSMShsm
The RACF FACILITY class environment
The DFSMShsm AUTH command environment
Defining the DFSMShsm MVS environment
Specifying the job entry subsystem
JES3 considerations
Specifying the amount of common service area storage
Selecting values for the SETSYS CSA command subparameters
Selecting the value for the MAXIMUM subparameter
Setting CSALIMIT to protect other applications
Setting CSALIMIT as an early warning
Selecting the value for the ACTIVE subparameter
Selecting the value for the INACTIVE subparameter
Selecting the value for the MWE subparameter
WAIT and NOWAIT MWE considerations
Specifying the size of cell pools
Specifying operator intervention in DFSMShsm automatic operations
Specifying data set serialization
Specifying the swap capability of the DFSMShsm address space
Specifying maximum secondary address space
Defining the DFSMShsm security environment for DFSMShsm-owned data sets
Determining batch TSO user IDs
Specifying whether to indicate RACF protection of migration copies and backup versions of data sets
Specifying security for scratched DFSMShsm-owned DASD data sets
Erase-on-scratch considerations
Defining data formats for DFSMShsm operations
Data compaction option
Compaction tables
Compaction percentage
Compaction considerations
Optimum DASD blocking option
Data Set Reblocking
Defining DFSMShsm reporting and monitoring
Controlling messages that appear on the system console
Controlling the output device for listings and reports
Controlling entries for the SMF logs
Defining the tape environment
Defining the installation exits that DFSMShsm invokes
Controlling DFSMShsm control data set recoverability
Defining migration level 1 volumes to DFSMShsm
Parameters for the migration level 1 ADDVOL commands
Using migration level 1 OVERFLOW volumes for migration and backup
User or system data on migration level 1 volumes
Defining the common recall queue environment
Updating the coupling facility resource manager policy for the common recall queue
Determining the structure size of the common recall queue
Altering the list structure size
How to alter the common recall queue list structure size
How to rebuild the common recall queue list structure size
Defining common SETSYS commands
DFSMShsm starter set
Basic starter set jobs
Starter set objectives
Starter set configuration considerations
Setup requirements
Steps for running the starter set
HSMSTPDS
HSM.SAMPLE.CNTL
STARTER
Starter set example
Adapting and using the starter set
ARCCMD90
ARCCMD01
ARCCMD91
HSMHELP
HSMLOG
HSMEDIT
ALLOCBK1
ALLOSDSP
HSMPRESS
DFSMShsm sample tools
ARCTOOLS job and sample tool members
Functional verification procedure
Preparing to run the functional verification procedure
Steps for running the functional verification procedure
FVP parameters
Small-data-set-packing parameters
VSAM data set migration parameter
Tape support parameter
Dump function parameter
Jobs and job steps that comprise the functional verification procedure
Cleanup job
Job step 1: Allocate a non-VSAM data set and a data set to prime VSAM data sets
Job step SDSPA: Create small-data-set-packing (SDSP) data set
Job step 2: Print the data sets created in STEP 1 of job ?AUTHIDA
Job step 3 (JOB B): Performing data set backup, migration, and recall
Job step 4: IDCAMS creates two VSAM data sets
Job step 5 (JOB C): Performing backup, migration, and recovery
Job steps 6, 7, and 8: Deleting and re-creating data sets
Job step 9 (JOB D): Recovering data sets
Job steps 10 and 11 (JOB E): Listing recovered data sets and recalling with JCL
Job step 12 (JOB F): Tape support
Job step 13 (JOB G): Dump function
FVPCLEAN job
Authorizing and protecting DFSMShsm commands and resources
Identifying DFSMShsm to RACF
Creating user IDs
Specifying a RACF user ID for DFSMShsm
Specifying a RACF user ID for ABARS
Associating a user ID with a started task
Method 1–RACF started procedures table (ICHRIN03)
Method 2–RACF STARTED class
Configuring DFSMShsm to invoke DFSMSdss as a started task
Identifying DFSMShsm to z/OS UNIX System Services
Authorizing and protecting DFSMShsm commands in the RACF FACILITY class environment
RACF FACILITY class profiles for DFSMShsm
Protecting DFSMShsm commands with RACF FACILITY class profiles
Protecting DFSMShsm storage administrator commands with RACF FACILITY class profiles
Protecting DFSMShsm user commands with RACF FACILITY class profiles
Protecting DFSMShsm user macros with RACF FACILITY class profiles
Creating the RACF FACILITY class profiles for ABARS
ABARS comprehensive RACF FACILITY class authorization
ABARS restricted RACF FACILITY class authorization
Creating RACF FACILITY class profiles for concurrent copy
Activating the RACF FACILITY class profiles
Authorizing commands issued by an operator
Protecting DFSMShsm resources
Protecting DFSMShsm data sets
Protecting DFSMShsm activity logs
Protecting DFSMShsm tapes
Defining RACF TAPEVOL resource classes
Method 1—Protecting with a single profile
Method 2—Protecting with multiple profiles
Defining the RACF environment to DFSMShsm
User-protecting tapes with RACF
Protecting scratched DFSMShsm-owned data sets
Authorizing users to access DFSMShsm resources
Protecting DFSMShsm commands in a nonsecurity environment
Authorizing and protecting DFSMShsm resources in a nonsecurity environment
Implementing DFSMShsm tape environments
Tape device naming conventions
SMS-managed tape libraries
Steps for defining an SMS-managed tape library
Determine which functions to process in a tape library
Set up a global scratch pool
Define a storage class
Define a data class
Define a storage croup
Set up the ACS routines
Information passed to an ACS routine
Define the DFSMShsm tape library environment in the ARCCMDxx PARMLIB member
Example: Defining a DFSMShsm environment for SMS-managed tape libraries
Converting to an SMS-managed tape library environment
Inserting DFSMShsm tapes into a tape library
Identifying tape library tapes
Tape connected sets
Looking at your tape library with the LIST command
Introducing tape processing functions to the library
Scenario 1–Implementing migration processing in an automated tape library
Implementing migration processing in a manual tape library
Scenario 2–Implementing backup processing in an automated tape library
Implementing backup processing in a manual tape library
Scenario 3–Implementing control data set backup in an automated tape library
Implementing control data set backup in a manual tape library
Defining the tape management policies for your site
DFSMShsm tape media
Single file cartridge-type tapes
Multiple file reel-type tapes
Obtaining empty tapes from scratch pools
Global scratch pools
Specific scratch pools
Selecting output tape
Tape hardware emulation
Initial tape selection for migration and backup tapes
Subsequent tape selection for migration and backup tapes
Initial and subsequent selection of dump tapes
Selecting a scratch pool environment
Performance tape environment with global scratch pool for library and nonlibrary environments
Tape-capacity optimization tape environment with global scratch pool for library and nonlibrary environments
Media optimization for DFSMShsm-managed nonlibrary tape environment
Performance optimization for DFSMShsm-managed nonlibrary tape environment
Implementing a recycle schedule for backup and migration tapes
When to initiate recycle processing
Number of scratch tapes needed
Number of recycle tasks to run
Tape drive contention
Generated messages
How long to run recycle processing
Number of required scratch tapes
Maximum percentage of valid data
Tape drive contention
Recycle performance
Returning empty tapes to the scratch pool
Reducing the number of partially full tapes
Protecting tapes
RACF protection
Using RACF DATASET class profiles
Conversion from RACF TAPEVOL to RACF DATASET class profiles
Expiration date protection
Defining expiration date protection for tapes
Password protection
Dump tape security considerations
Removing the security on tapes returning to the scratch pool
Communicating with the tape management system
Defining the environment for the tape management system
Data set naming conventions
Managing tapes with DFSMShsm installation exits
Defining the device management policy for your site
Tape device selection
Nonlibrary tape device selection
Library tape device selection
Restricting tape device selection
Optimizing cartridge loaders by restricting output to devices with cartridge loaders
Summary of esoteric translation results for various tape devices
Tape device conversion
Reading existing data on new device types after a device conversion in a nonlibrary environment
Converting from 3480 to 3490 devices in a nonlibrary environment
Converting from 3420 to 3480 devices in a nonlibrary environment
Specifying whether to suspend system activity for device allocations
Specifying the WAIT option
Specifying the NOWAIT option
Specifying how long to allow for tape mounts
Specifying the tape mount parameters
Specifying the length of time before DFSMShsm takes action
Implementing the performance management policies for your site
Reducing tape mounts with tape mount management
Doubling storage capacity with enhanced capacity cartridge system tape
Doubling storage capacity with extended high performance cartridge tape
Defining the environment for enhanced capacity and extended high performance cartridge system tape
Utilizing the capacity of IBM tape drives that emulate IBM 3490 tape drives
Defining the environment for utilizing the capacity of IBM tape drives that emulate IBM 3490 tape drives
Tape selection
Drive selection
Remote site compatibility
IBM 3590 capacity utilization considerations
Specifying how much of a tape DFSMShsm uses
Implementing partially unattended operation with cartridge loaders in a nonlibrary environment
Defining the environment for partially unattended operation
Improving device performance with hardware compaction algorithms
Specifying compaction for non-SMS-managed tape library data
Specifying compaction for tape library data
Creating concurrent tapes for on-site and offsite storage
Duplex tape creation
Duplex tape status
Duplex tape supported functions
Considerations for duplicating backup tapes
TAPECOPY of specific backup tapes
TAPECOPY of nonspecific backup tapes
Initial device selection
Tape eligibility when output is restricted to a specific nonlibrary device type
Tape eligibility when output is not restricted to a specific nonlibrary device type
Tape eligibility when output is restricted to specific device types
Allowing DFSMShsm to back up data sets to tape
Switching data set backup tapes
Fast subsequent migration
DFSMShsm in a multiple-image environment
Multiple DFSMShsm host environment configurations
Example of a multiple DFSMShsm host environment
Defining a multiple DFSMShsm host environment
Defining a primary DFSMShsm host
Defining all DFSMShsm hosts in a multiple-host environment
DFSMShsm system resources and serialization attributes in a multiple DFSMShsm host environment
Resource serialization in a multiple DFSMShsm host environment
Global resource serialization
Serialization of user data sets
Serialization of control data sets
Serialization of control data sets with global resource serialization
CDSQ keyword of the DFSMShsm startup rrocedure
CDSR keyword of the DFSMShsm startup procedure
CDSSHR keyword of the DFSMShsm startup procedure
Serialization of control data sets without global resource serialization
Serialization of DFSMShsm functional processing
Choosing a serialization method for user data sets
DFHSMDATASETSERIALIZATION
Performance considerations
Volume reserve considerations
USERDATASETSERIALIZATION
Converting from volume reserves to global resource serialization
Setting up the GRS resource name lists
Example: DFSMShsm serialization configuration
Alternate example: DFSMShsm serialization configuration
DFSMSdss Considerations for dumping the journal volume
DFSMShsm data sets in a multiple DFSMShsm host environment
CDS considerations in a multiple DFSMShsm host environment
Preventing interlock of DFSMShsm control data sets
VSAM SHAREOPTIONS parameters for control data sets
Method 1—VSAM SHAREOPTIONS(2 3)
Method 2—VSAM SHAREOPTIONS(3 3)
Considerations for VSAM SHAREOPTIONS
CDS backup version considerations in a multiple DFSMShsm host environment
DASD CDS backup versions
Tape CDS backup versions
Journal considerations in a multiple DFSMShsm host environment
Monitoring the control and journal data sets in a multiple DFSMShsm host environment
Problem determination aid log data sets in a multiple DFSMShsm host environment
DFSMShsm log considerations in a multiple DFSMShsm host environment
Edit log data set considerations in a multiple DFSMShsm host environment
Small-data-set-packing data set considerations in a multiple DFSMShsm host environment
SDSP data set share options
Maintaining data set integrity
Serialization of resources
Volume considerations in a multiple DFSMShsm host environment
JES3 considerations
Running automatic processes concurrently in a multiple DFSMShsm host environment
Multitasking considerations in a multiple DFSMShsm host environment
Performance considerations in a multiple DFSMShsm host environment
MASH configuration considerations
Customizing DFSMShsm
DFSMShsm in a sysplex environment
Types of sysplex
Sysplex support
Single GRSplex serialization in a sysplex environment
Resource serialization in an HSMplex environment
Enabling single GRSplex serialization
Identifying static resources
Translating static resources into dynamic resources
Compatibility considerations
Secondary host promotion
Enabling secondary host promotion from the SETSYS command
Configuring multiple HSMplexes in a sysplex
Additional configuration requirements for using secondary host promotion
When a host is eligible for demotion
How secondary host promotion works
Promotion of primary host responsibilities
How auto functions affect secondary host promotion
Promoted host is not an automatic backup host
Promoted host is an automatic backup host
Configuring automatic backup hosts in an HSMplex
Promoted host is not an automatic dump host
Promoted host is an automatic dump host
Configuring automatic dump hosts in an HSMplex
Promotion of SSM host responsibilities
How the take back function works
The promoted host gives up the promoted responsibilities
The original host waits for the promoted host
Emergency mode considerations
Considerations for implementing XCF for secondary host promotion
Control data set extended addressability in a sysplex environment
Using VSAM extended addressability in a sysplex
Extended addressability considerations in a sysplex
Common recall queue configurations
Calculating DFSMShsm storage requirements
DFSMShsm address spaces
Storage estimating considerations
Storage guidelines
Adjusting the size of cell pools
DFSMShsm libraries and procedures
DFSMShsm libraries
Procedure libraries (PROCLIB)
Parameter libraries (PARMLIB)
Creating alternate DFSMShsm parameter library members
Commands for PARMLIB member ARCCMDxx
Command sequence for PARMLIB member ARCCMDxx
Sample libraries (SAMPLIB)
DFSMShsm procedures
DFSMShsm startup procedure
Startup procedure keywords
CMD (default = 00)
EMERG (default = NO)
LOGSW (default = NO)
STARTUP (default = NO)
UID (default = HSM)
HOSTMODE (default = MAIN)
SIZE
DDD
HOST=x
PRIMARY (default = YES)
RESTART
CDSQ
CDSR
CDSSHR
CELLS (default = (200,100,100,50,20))
PDA (default = YES)
RNAMEDSN (default = NO)
STR
Using the RESTART keyword to automatically restart DFSMShsm after an abnormal end
Startup procedure DD statements
Using DD statement AMP parameters to override DFSMShsm default values
Example of using a DD statement to override default values stored in the ACB
ABARS secondary address space startup procedure
DFSMShsm installation verification procedure (IVP) startup procedure
DFSMShsm functional verification procedure (FVP)
HSMLOG procedure
HSMEDIT procedure
User application interfaces
Data collection
Planning to use data collection
Choosing a data collection method
Choosing a report creation method
Choosing the type of report you want
The data collection environment
Data sets used for data collection
MCDS
BCDS
Snap processing data set
Collection data set
Data collection records
Data collection record header
Migrated data set information record
Backup version information record
DASD capacity planning records
Tape capacity planning records
Related reading
Invoking the DFSMShsm data collection interface
Invoking the ARCUTIL load module with the access method services (AMS) DCOLLECT function
Direct invocation of ARCUTIL load module
Invoking the ARCUTIL load module with a user-written program
Example of invoking ARCUTIL with a user-written program
Sample REXX program DCOLREXX
Data collection exit support
The ARCUTILP data area
Required parameters
Optional parameters
Output parameters
ARCUTIL return codes and reason codes
Tuning DFSMShsm
Tuning patches supported by DFSMShsm
Changing DFSMShsm backup and migration generated dataset names to reduce contention for similar names and eliminating a possible performance degradation
Migrating and scratching generation data sets
Migrating generation data sets
Allowing password-protected generation data sets to be migrated, then scratched without checking the password at roll-off time
Scratching of rolled-off generation data sets
Scratching non-SMS generation data sets at roll-off time regardless of expiration dates
Generation data set scratch summary
Disabling backup and migration of data sets that are larger than 64K tracks to ML1 volumes
Disabling, in JES3, the delay in issuing PARTREL (partial release) for generation data sets
Using DFSMShsm in a JES3 environment that performs main device scheduling only for tapes
Shortening the prevent-migration activity for JES3 setups
Replacing HSMACT as the high-level qualifier for activity logs
Changing the allocation parameters for an output data set
Changing the unit name
Changing the primary space quantity
Changing the secondary space quantity
Changing the limiting of SYSOUT lines
Using the DFSMShsm startup PARMLIB member
Buffering of user data sets on DFSMShsm-owned DASD using optimum DASD blocking
Changing parameters passed to DFSMSdss
Invoking DFSMSdss for a full-volume dump
Setting on compress for dumps and ABARS
Setting off ALLEXCP for dumps
Setting off ALLDATA for dumps
Requesting DFSMShsm volume dumps with a 32 KB block size
Processing partitioned data sets with AX cells
Enabling ABARS ABACKUP and ARECOVER to wait for a tape unit allocation
Changing the RACF FACILITY CLASS ID for the console operator’s terminal
Handling independent-software-vendor data in the data set VTOC entry
Allowing DFSMShsm automatic functions to process volumes other than once per day
Running automatic primary space management multiple times a day in a test environment
Example of redefining a day for automatic primary space management of SMS volumes
Processing interval considerations for automatic primary space management
Reasons why automatic primary space management can appear not to be running
Running automatic backup multiple times a day
Phase 1: Backing up the control data sets
Phases 2 and 3: Moving backup versions and backing up migrated data sets
Phase 4: Backing up DFSMShsm-managed volumes with the automatic backup attribute
Processing interval considerations for automatic backup
Reasons why automatic backup can appear not to be running
Example of automatically backing up the same set of SMS volumes twice a day with two different hosts
Running automatic dump multiple times a day in a test environment
Processing interval considerations for automatic dump
Reasons why automatic dump can appear not to be running
Changing the frequency of running interval migration
Making the interval less frequent than one hour
Making the interval more frequent than one hour
Changing the frequency of running on-demand migration again on a volume that remains at or above the high threshold
Reducing enqueue times on the GDG base or on ARCENQG and the fully qualified GDS name
Modifying the migration queue limit value
Changing the default tape data set names that DFSMShsm uses for tape copy and full volume dump
Default tape data set names for DFHSM Version 2 Release 6.0
Default tape data set names for DFHSM releases prior to Version 2 Release 6.0
Preventing interactive TSO users from being placed in a wait state during a data set recall
Preventing ABARS ABACKUP processing from creating an extra tape volume for the instruction data set and activity log files
Preventing ABARS ABACKUP processing from including multivolume BDAM data sets
Specifying the amount of time to wait for an ABARS secondary address space to initialize
Patching ABARS to use NOVALIDATE when invoking DFSMSdss
Patching ABARS to provide dumps whenever specific errors occur during DFSMSdss processing during ABACKUP and ARECOVER
Routing ABARS ARC6030I message to the operator console
Filtering storage group and copy pool ARC0570I messages (return code 17 and 36)
Allowing DFSMShsm to issue serialization error messages for class transitions
Enabling ARC1901I messages to go to the operator console
Changing the notification limit percentage value to issue ARC1901I messages
Patching to prevent ABARS from automatically cleaning up residual versions of ABACKUP output files
Enabling the serialization of ML2 data sets between RECYCLE and ABACKUP
Changing the default number of recall retries for a data set residing on a volume in use by RECYCLE or TAPECOPY processing
Changing the default number of buffers that DFSMShsm uses to back up and migrate data sets
Changing the compaction-ratio estimate for data written to tape
Enabling the takeaway function during TAPECOPY processing
Changing the delay by recall before taking away a needed ML2 tape from ABACKUP
Disabling delete-if-backed-up (DBU) processing for SMS data sets
Requesting the message issued for SETSYS TAPEOUTPUTPROMPT processing be WTOR instead of the default WTO
Removing ACL as a condition for D/T3480 esoteric unit name translation
Restricting non-SMS ML2 tape volume table tape selection to the SETSYS unit name of a function
Changing the amount of time ABACKUP waits for an ML2 volume to become available
Changing the amount of time an ABACKUP or ARECOVER waits for a resource in use by another task
Preventing deadlocks during volume dumps
Modifying the number of elapsed days for a checkpointed data set
Running concurrent multiple recycles within a single GRSplex
Patching to force UCBs to be OBTAINed each time a volume is space checked
Running conditional tracing
Using the tape span size value regardless of data set size
Updating MC1 free space information for ML1 volumes after an return code 37 in a multi-host environment
Allowing DFSMShsm to use the 3590-1 generic unit when it contains mixed track technology drives
Allowing functions to release ARCENQG and ARCCAT or ARCGPA and ARCCAT for CDS backup to continue
Suppressing SYNCDEV for alternate tapes during duplex migration
Patching to allow building of a dummy MCD record for large data sets whose estimated compacted size exceeds the 64 KB track DASD limit
Allowing DFSMShsm to honor an explicit expiration date even if the current management class retention limit equals 0
Using the generic rather than the esoteric unit name for duplex generated tape copies
Modifying the allocation quantities for catalog information data sets
Enabling volume backup to process data sets with names ending with .LIST, .OUTLIST or .LINKLIST
Prompting before removing volumes in an HSMplex environment
Returning to the previous method of serializing on a GDS data set during migration
Special considerations
Backup profiles and the RACF data set
Increasing VTOC size for large capacity devices
DFSMShsm command processor performance considerations
Incompatibilities caused by DFSMShsm
Volume serial number of MIGRAT or PRIVAT
IEHMOVE utility
TSO ALTER command and access method services ALTER command
TSO DELETE command and access method services DELETE command
Data set VTOC entry date-last-referenced field
VSAM migration (non-SMS)
RACF volume authority checking
Accessing data without allocation or OPEN (non-SMS)
RACF program resource profile
Update password for integrated catalog facility user catalogs
Processing while DFSMShsm is inactive
DFSMShsm abnormal end considerations
Recovering DFSMShsm after an abnormal end
Recovering from an abnormal end of a DFSMShsm subtask
Recovering from an abnormal end of the DFSMShsm main task
Restarting DFSMShsm after an abnormal end
Suppressing duplicate dumps
Duplicate data set names
Debug mode of operation for gradual conversion to DFSMShsm
Generation data groups
Handling of generation data sets
Access method services DELETE GDG FORCE command
ISPF validation
Preventing migration of data sets required for long-running jobs
SMF considerations
DFSMSdss address spaces started by DFSMShsm
Health Checker for DFSMShsm
DFSMShsm work sheets
MCDS size work sheet
BCDS size work sheet
OCDS size work sheet
Problem determination aid log data set size work sheet—Short-term trace history
Problem determination aid log data set size work sheet—Long-term trace history
Collection data set size work sheet