11.01.2013 Views

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Large format data sets<br />

Large format data sets are sequential data sets that can grow beyond the size limit <strong>of</strong> 65 535<br />

tracks (4369 cylinders) per volume that applies to other sequential data sets. Large format<br />

data sets can be system-managed or not. They can be accessed using QSAM, BSAM, or<br />

EXCP.<br />

Large format data sets reduce the need to use multiple volumes for single data sets,<br />

especially very large ones such as spool data sets, dumps, logs, and traces. Unlike<br />

extended-format data sets, which also support greater than 65 535 tracks per volume, large<br />

format data sets are compatible with EXCP and do not need to be SMS-managed.<br />

You can allocate a large format data set using the DSNTYPE=LARGE parameter on the DD<br />

statement, dynamic allocation (SVC 99), TSO/E ALLOCATE, or the access method services<br />

ALLOCATE command.<br />

Basic format data sets<br />

Basic format data sets are sequential data sets that are specified as neither extended-format<br />

nor large-format. Basic format data sets have a size limit <strong>of</strong> 65 535 tracks (4369 cylinders) per<br />

volume. They can be system-managed or not, and can be accessed using QSAM, BSAM, or<br />

EXCP.<br />

You can allocate a basic format data set using the DSNTYPE=BASIC parameter on the DD<br />

statement, dynamic allocation (SVC 99), TSO/E ALLOCATE, or the access method services<br />

ALLOCATE command, or the data class. If no DSNTYPE value is specified from any <strong>of</strong> these<br />

sources, then its default is BASIC.<br />

Objects<br />

Objects are named streams <strong>of</strong> bytes that have no specific format or record orientation. Use<br />

the object access method (OAM) to store, access, and manage object data. You can use any<br />

type <strong>of</strong> data in an object because OAM does not recognize the content, format, or structure <strong>of</strong><br />

the data. For example, an object can be a scanned image <strong>of</strong> a document, an engineering<br />

drawing, or a digital video. OAM objects are stored either on DASD in a DB2® database, or<br />

on an optical drive, or on an optical or tape storage volume.<br />

The storage administrator assigns objects to object storage groups and object backup<br />

storage groups. The object storage groups direct the objects to specific DASD, optical, or tape<br />

devices, depending on their performance requirements. You can have one primary copy <strong>of</strong> an<br />

object and up to two backup copies <strong>of</strong> an object. A Parallel Sysplex allows you to access<br />

objects from all instances <strong>of</strong> OAM and from optical hardware within the sysplex.<br />

z/<strong>OS</strong> UNIX files<br />

z/<strong>OS</strong> UNIX <strong>System</strong> Services (z/<strong>OS</strong> UNIX) enables applications and even z/<strong>OS</strong> to access<br />

UNIX files. Also UNIX applications also can access z/<strong>OS</strong> data sets. You can use the<br />

hierarchical file system (HFS), z/<strong>OS</strong> Network File <strong>System</strong> (z/<strong>OS</strong> NFS), zSeries File <strong>System</strong><br />

(zFS), and temporary file system (TFS) with z/<strong>OS</strong> UNIX. You can use the BSAM, QSAM,<br />

BPAM, and VSAM access methods to access data in UNIX files and directories. z/<strong>OS</strong> UNIX<br />

files are byte-oriented, similar to objects.<br />

Chapter 2. Data set basics 21

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!