On Tue, Dec 8, 2015 at 6:37 PM, Shmuel Metz (Seymour J.) < [email protected]> wrote:
> In > <caajsdjgdcfhh4eonuruomvc7ovkk4wu8eado_yimw6fspnw...@mail.gmail.com>, > on 12/08/2015 > at 03:21 PM, John McKown <[email protected]> said: > > > I do not really agree that not including the volser in the SYSDSN > >enqueue is a "flaw". If it were done, then their could need to be > >multiple ENQs, one for each volume in a multi-volume DSN. > > The ENQ is for a PDS member; a PDS can't be multivolume. > > >But remember this was designed in OS/360 > > Which didn't allow a multi-volume PDS. > > -- > Shmuel (Seymour J.) Metz, SysProg and JOAT > OK, I've managed to confuse myself. You want the ENQ for SYSDSN to include the volser if and only if the DSORG is a PDS, otherwise to omit it? That is, if DSORG=PO then rname=dsn||volser else rname=dsn? Again, think 360/30(?) running OS/360 MFT. That's more code in allocation, which means less core for the user's program. -- Schrodinger's backup: The condition of any backup is unknown until a restore is attempted. Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
