Lizette Koehler wrote: <snip>
In my mind this is a lot of work. I would side with others that indicate that SMS is the easiest and least painful way of creating your datasets. However, if you are intent on the other road, take a look at the process in Serverpac to see how it setups the SYSRES volumes. You might get some ideas out of it.
<snip>
The ServerPac algorithm for target libraries is loosely based on the SMP/E element types associated with each data set, and the priority order was intended to try to consolidate the data sets needed for IPL and ISPF on as few volumes as possible to speed recovery if you had to restore the target volume set due to disk failure or DR testing (or, heaven forfend, actual DR). DLIBs are just put on whatever volumes they fit on, with no regard to type. Free space and secondary allocation amounts are taken from the defaults or from any increases specified in the dialog, and the process tries to use as few volumes as possible to achieve this goal overall. One likely result is more free space on the last volume than on the others in the volume set.
(With today's disk sizes, it's more sensible in my view to just put all the target libraries on one volume, but what do I know?)
If what the OP is looking for is a working example that "does something using a metadata file," it should serve well. But it's a poor example of how one might try to spread the peanut butter evenly from space or performance objective points of view, because it does neither one.
SMS might be the OP's friend here, as others have suggested. -- John Eells z/OS Technical Marketing IBM Poughkeepsie ee...@us.ibm.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
