z/OS DFSMShsm Implementation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Defining data formats for DFSMShsm operations

z/OS DFSMShsm Implementation and Customization Guide
SC23-6869-01

Because DFSMShsm moves data between different device types with different device geometries, the format of data can change as it moves from one device to another.

There are three data formats for DFSMShsm operations:
  • The format of the data on DFSMShsm-owned volumes
  • The blocking of the data on DFSMShsm-owned DASD volumes
  • The blocking of data sets that are recalled and recovered

You can control each of these format options by using SETSYS command parameters. The parameters control the data compaction option, the optimum DASD blocking option (see Optimum DASD blocking option), the use of the tape device improved data recording capability, and the conversion option. You can also use DFSMSdss dump COMPRESS for improved tape utilization. Refer to z/OS DFSMShsm Storage Administration for additional information about invoking full-volume dump compression. Figure 1 lists sample SETSYS commands for defining data formats.

Figure 1. Sample Data Format Definitions for a Typical DFSMShsm Environment
 
/***********************************************************************/
/*               SAMPLE DFSMSHSM DATA FORMAT DEFINITIONS               */
/***********************************************************************/
/*
SETSYS COMPACT(DASDMIGRATE NOTAPEMIGRATE DASDBACKUP NOTAPEBACKUP)
SETSYS COMPACTPERCENT(30)
SETSYS OBJECTNAMES(OBJECT,LINKLIB)
SETSYS SOURCENAMES(ASM,PROJECT)
SETSYS OPTIMUMDASDBLOCKING
SETSYS CONVERSION(REBLOCKTOANY)
SETSYS TAPEHARDWARECOMPACT
/*
 

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014