To create an HFS data set,
follow these steps:
- To allocate the HFS data set, specify HFS in
the DSNTYPE
parameter and the number of directory blocks in the SPACE parameter,
in either the JCL or the data class. If you do not specify the number
of the directory blocks, the allocation fails. The value of the
number has no effect.
_______________________________________________________________
- Define a data class for HFS data sets. Although you can create
uncataloged HFS data sets, they must be cataloged when they are mounted.
These data sets can expand to as many as 255 extents of DASD space
on multiple volumes (59 volumes maximum with 123 extents per volume).
_______________________________________________________________
- Log on as a TSO/E user and define additional directories, as described
in Creating Additional Directories.
_______________________________________________________________
The following example creates an SMS-managed HFS data set:
//FSJOB JOB
//STEP1 EXEC PGM=IEFBR14
//MKFS1 DD DSNAME=FILE.SYSTEM.FS0001,DISP=(NEW,KEEP),
// DSNTYPE=HFS,SPACE=(CYL,(100,100,1)),DATACLAS=FILESYS,
// MGMTCLAS=NEVER,STORCLAS=SECURE
The
following example creates a non-SMS-managed HFS data set:
//FSJOB JOB
//STEP1 EXEC PGM=IEFBR14
//MKFS1 DD DSNAME=FILE.SYSTEM.FS0001,DISP=(NEW,CATLG),
// DSNTYPE=HFS,SPACE=(CYL,(100,100,1)),DATACLAS=FILESYS,
// MGMTCLAS=NEVER,VOL=SER=XXXXXX,UNIT=SYSDA
The hierarchical
file system can use first-in-first-out (FIFO)
special files. To allocate a FIFO special file in a z/OS UNIX file
system, specify PIPE in the DSNTYPE parameter and a path name in the
PATH parameter.
Requirement: RACF
or an equivalent security
product must be installed and active on your system to use z/OS UNIX
data sets. You cannot use a UNIX data set until someone with appropriate
RACF authority uses the TSO MOUNT command to allocate DASD space and
logically mount the file system.