PDSE
The newer kind of library. It reuses space by itself and its directory grows as needed.
Also written library extended
Why it matters. New libraries on a real system are usually PDSEs. You make them the same way and meet fewer space problems.
Syntax
ALLOCATE DATASET('name') NEW DSNTYPE(LIBRARY)
//ddname DD DSN=name,DISP=(NEW,CATLG),DSNTYPE=LIBRARY- DSNTYPE(LIBRARY)
- Makes a PDSE.
- DSNTYPE(PDS)
- Makes a classic PDS.
- No DIR needed
- The directory grows as members are added.
- Program objects
- A PDSE can hold program objects. A PDS holds load modules.
- Compress
- Not needed on a PDSE.
Try it ALLOC
- 1
Make a new library, ZB0001.DEV.CPYLIB, as a PDSE.
ALLOC DSN('ZB0001.DEV.CPYLIB') NEW DSNTYPE(LIBRARY) - 2
Look at the details of the new library.
LISTDS 'ZB0001.DEV.CPYLIB'
Remember
- PDSE is a different layout on disk, with the old PDS limits taken away.
- It reuses the space of a replaced member by itself.
- DSNTYPE(LIBRARY) makes one.
The usual mistake
Running a compress job on a PDSE
A PDSE gives back space as it goes. The compress is for an old PDS and is not needed here.
Compress only a classic PDS that has run out of room
On real z/OS
Mainframe101 sim: MF/OS shows PO for a PDSE and a PDS alike and does not model the difference. Real LISTDS shows the dataset type, and a PDSE needs storage management set up.
Where can I practise PDSE?
Right here, at ZedBank. You take a junior job at a simulated bank and use PDSE in real work, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- Partitioned datasetA dataset that works like a library or folder, holding many separately named members inside one dataset.
- MemberOne named item inside a partitioned dataset, such as a single program, job or copybook within a library.
- DatasetWhat a mainframe calls a file: a named collection of records with a defined structure, rather than a loose stream of bytes.
- Load moduleThe runnable form of a program, stored in a library, which JCL executes by name.