Data, Data Sets, and Unix files
Part Two - Challenge #09
Background:
You will learn how to allocate 7 unique z/OS data set types
You will allocate 7 unique z/OS data set types
Edit and submit JCL JOB with the following modifications:
- Modify DD operation DSORG parameter to allocate a sequential data set
- Modify DD operation DSORG parameter to allocate a partitioned data set
- Modify DD operation DSORG and DSNTYPE parameter to allocate a partitioned data set extended
- Modify IDCAMS utility program DEFINE CLUSTER control statement to allocate a VSAM KSDS cluster
- Modify IDCAMS utility program DEFINE CLUSTER control statement to allocate a VSAM ESDS cluster
- Modify IDCAMS utility program DEFINE CLUSTER control statement to allocate a VSAM RRDS cluster
- Modify IDCAMS utility program DEFINE CLUSTER control statement to allocate a VSAM LDS cluster
Useful Information About z/OS Data and the Variety of z/OS Data Sources:
- z/OS disk storage space is allocated in 'extents'
- An extent is a contiguous area on disk with an absolute starting and ending location
- z/OS data sets have 1 primary extent
- When the primary extent is full, then a secondary extent is automatically allocated
- The number of secondary extents depends upon the type of data set
- The size of a primary extent and subsequent secondary extents are determined by a SPACE attribute
See References drop down Data Set Allocation and Disk Storage Summary
- z/OS stores data in a variety of organization types categorized as NON-VSAM and VSAM
NON-VSAM includes
1) Sequential
2) PDS, Partitioned Data Set
3) PDS/E, Partitioned Data Set/Extended
VSAM includes
1) KSDS, Key Sequences Data Set
2) ESDS, Entry Sequenced Data Set
3) RRDS, Relative Record Data Set
4) LDS, Linear Data Set - Unix file systems
- Unix filesystem is a stream of bytes
- Physical VSAM LDS formatted for Unix filesystem stream of byte processing - Databases
DB2 is a relational database
DB2 data is stored in a VSAM LDS, formatted, and managed by DB2
IMS Hierarchical DB uses special access method data sources which are excluded from the contest - Data Set attribute syntax includes:
LRECL, Record Length
DSORG, Data Set Organization
- PS Physical Sequential
- PO Partitioned Organization
- VS VSAM
RECFM, Record Format
- F Fixed Length Records
- FB Fixed Length Blocked Records
- V Variable Length Records
- VB Variable Length Blocked Records
- U Undefined Length Records
Challenge:
Information to help you find the correct parameters for successful execution of CH09JCL
Edit Z#####.JCL member name CH09JCL
NOTE: All occurrences of &SYSUID. are automatically replaced by your ID when submitted.
Change all occurrences of the @ symbols with appropriate parameters to accomplish the following:
- &SYSUID..CH9.SEQ created as a sequential data set type
- &SYSUID..CH9.PDS created as a partitioned data set type
- &SYSUID..CH9.PDSE created as a partitioned data set extended type
- &SYSUID..CH9.KSDS created as a VSAM Key Sequenced Data Set type
- &SYSUID..CH9.ESDS created as a VSAM Entry Sequenced Data Set type
- &SYSUID..CH9.RRDS created as a VSAM Relative Record Data Set type
- &SYSUID..CH9.LDS created as a VSAM Linear Data Set type
Submit JCL member name CH09JCL and view the output for successful execution.
If unsuccessful, then correct and submit again.
To complete challenge #09 - create member name #09 in P2.OUTPUT with successful results
View CH09JCL output DDNAMEs
Use XDC to print content of DDNAME SYSTSPRT StepName RESULT to P2.OUTPUT member name #09 as follows:
Use XDC to print content of DDNAME SYSTSPRT StepName RESULT to P2.OUTPUT member name #09 as follows:


Browse P2.OUTPUT(#09) to validate data set name allocation attributes for the 7 unique data set types
are in the #09 member name.
Congratulations! You know more about z/OS than the average person