At my work they just define GDG and its work I guess.
Yup, this is used at all of my recent clients.
Suggest you talk with your storage management people as different organizations have different standards - and the standards should be followed (regardless of what the z/OS system might let you do). _________________ Have a good one
Very rarely used, and only if your system is NOT SMS-managed (highly unlikely).
Going back to the OS/360 world, if there was no model DSCB, the system would not allocate the data set unless the JCL specified a model DSCB data set name. But this is no longer the case.
If you use IDCAMS to create the GDG base, and if your SMS ACS routines are correctly set up then any GDG that is created - SMS or NONSMS, DASD or tape will not need any model gdg or model dscb associated with it.
As i mentioned earlier, you should talk with your storage management people to learn if these are even used in your environment. . . _________________ Have a good one
Joined: 09 Aug 2008 Posts: 1631 Location: Mumbai, India
Posted: Wed May 16, 2012 7:40 pm Post subject:
Yes the tutorial is not wrong, check if there was some foot-note about DFSMS; MODEL is no longer required if DFSMS is installed and tailored correctly, as mentioned already. Also, realize that only one model will ever need to be created, and that your storage administrators will have already created it.
On the other hand, model data just needs to be a VTOC entry, it does not need to actually use up disk space. It is possible to create a different model dataset for every possible DCB combination, and some sites actually do that, but this needs a lot of effort to maintain. Many sites use a single model dataset, and then override the DCB information to build the correct type of file. To create a model DCB, use a dummy IEFBR14 job like this
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum