Data set (IBM mainframe): Difference between revisions

Revision as of 07:06, 5 June 2008

Revision as of 14:46, 11 April 2009

Line 24:

Besides members, a PDS consists also of their directory. Each member can be accessed directly using the directory structure. Once a member is located, the data stored in that member is handled in the same manner as a PS (sequential) data set.

Whenever a member is deleted, the space it occupied is unusable for storing other data. Likewise, if a member is re-written, it is stored in a new spot at the back of the PDS and leaves wasted “dead” space in the middle. The only way to recover “dead” space is to perform frequent file compression, that moves all members to the front of the data space and leaves free usable space at the back. (noteNote that currentin meaningmodern parlance, this kind of operation might be called [[Datadefragmentation]] or [[garbage collection]]; [[data compression|compression]] differsnowadays greatly)refers to a different, more complicated concept.) PDS files can only reside on disk in order to use the directory structure to access individual members, not on tape. They are most often used for storing multiple JCL files, utility control statements and executable modules.

An improvement of this scheme is a Partitioned Data Set Extended (PDSE or PDS/E, sometimes just ''libraries'') introduced with [[MVS/XA]] system.