VTOC: 1800 Tracks ( 11 %Used) 80398 Free DSCB'S 9354 Data sets
VOL: 150255 Tracks ( 81 %Used) 15 Tracks/cylinder 0 ALT Tracks
FREE: 1738 Cyls (MAX= 1012) 29054 Trks (MAX= 15180) 795 Free Xtnts
--------- D A T A S E T N A M E ---------- Org Trks %Used XTS= Status
A345677.CREATE.DATASET.ZERO.SPACE ?? 0 0 0
I understood from your reply that these kind of dataset has minimal usage in jobs. The only place that I am thinking of this dataset will be of use is when we need to check for file existence criteria in JCL to execute desired step.
Can also be used with IEFBR14, DISP=(MOD,DELETE), the technique to delete a dataset if it exists, otherwise to create and delete it at the same time, saving a JCL error if instead using DISP=(OLD,DELETE).
Once you have your dataset with no space, you can actually use it in JCL by specifying a different SPACE parameter in the step outputting to the file. This will temporarily override what it has been catalogued with, but will not change the catalogued value.
DSCB is Data Set Control Block. A control block in the VTOC that describes data set characteristics. However, if your site is SMS managed (and which site is not these days) this is not needed these days.
In my site, while creating GDG version I use to code without giving DSCB in DCB as it is managed by SMS.
I observed that some of the jobs are running in production has DSCB model specified in DCB parameter for GDG versions. When I checked the attributes of those versions in production, they are in SMS. Does this means that SMS will ignore DSCB?. I was checking the manuals from IBM site. Couldnot get my way to understand.