« Return to Thread: VM system disk arrangement
Re: VM system disk arrangement
by pfg504
::
Rate this Message:
The best arrangement would be to keep each product on it's own 3350 (could be less than 555 cyls). This would allow development to replace one disk for a given product rather than to replace everything.
As far as an operational system, keep user stuff separate from system stuff, keep perm away from temp(SPOOL, PAGE, TDISK).
The goal would be to update the smallest amount of disk as possible for any given change.
Paul
--- In H390-VM@..., Thomas Kern <tlk_sysprog@...> wrote:
>
> I like the idea of a single iplable volume without any of the
> non-operations minidisks and then spreading out the non-operational
> minidisks across more non-filled compressed Hercules volumes.
>
> Disk 1: Iplable: MAINT(190,191,19E), OPERATOR, AUTOLOG1, CPWATCH,
> Some Temp, Tdisk
> Disk 2: Rest of MAINT's minidisk
> Disk 3: RSCS, RSCS1, CMSBATCH, Other SVMs, CMSUSER
> ALGOL, BREXX, COBOL, DOSVS, OSBASIC, PLI, PL360,
> RPG, SCRIPT, TAPEMAC, WATFIV
> Disk 4: GCCCMS
> Disk 5: ALGOL, BREXX, COBOL, DOSVS, OSBASIC, PLI, PL360,
> RPG, SCRIPT, TAPEMAC, WATFIV
> Disk 6: REGINA
> Disk 7: Temp
> Disk 8: Tdisk
> Disk 9: etc
>
> I also like putting the Waterloo Mods onto a separate volume.
>
> /Tom Kern
>
> Robert O'Hara wrote:
> > I am looking at reworking the arrangement of disks in the VM 5-pack system.
> >
> > I have looked at the current disk utilization of MAINT, and I believe
> > that all of his minidisks can comfortably fit on a single 3350. Also,
> > all of the VM system disks (PERM, TDSK, TEMP) can fit on a single 3350.
> >
> > Now of course on a real mainframe we would want these disks spread out
> > over several channels, but it seems to me that with Hercules it does not
> > matter. Is that a correct assumption?
> >
> > I propose:
> >
> > disk 1: PERM, TEMP, TDSK
> > disk 2: all of MAINT's disks
> > disk 3: OPERATOR, RSCS, RSCS1, CPWATCH, AUTOLOG1, CMSBATCH,
> > ALGOL, BREXX, COBOL, DOSVS, OSBASIC, PLI, PL360, RPG,
> > SCRIPT, TAPEMAC, WATFIV
> > disk 4: GCCCMS
> > disk 5: REGINA, CMSUSER
> >
> > Comments on this layout?
> >
> > Thanks, Bob
>
As far as an operational system, keep user stuff separate from system stuff, keep perm away from temp(SPOOL, PAGE, TDISK).
The goal would be to update the smallest amount of disk as possible for any given change.
Paul
--- In H390-VM@..., Thomas Kern <tlk_sysprog@...> wrote:
>
> I like the idea of a single iplable volume without any of the
> non-operations minidisks and then spreading out the non-operational
> minidisks across more non-filled compressed Hercules volumes.
>
> Disk 1: Iplable: MAINT(190,191,19E), OPERATOR, AUTOLOG1, CPWATCH,
> Some Temp, Tdisk
> Disk 2: Rest of MAINT's minidisk
> Disk 3: RSCS, RSCS1, CMSBATCH, Other SVMs, CMSUSER
> ALGOL, BREXX, COBOL, DOSVS, OSBASIC, PLI, PL360,
> RPG, SCRIPT, TAPEMAC, WATFIV
> Disk 4: GCCCMS
> Disk 5: ALGOL, BREXX, COBOL, DOSVS, OSBASIC, PLI, PL360,
> RPG, SCRIPT, TAPEMAC, WATFIV
> Disk 6: REGINA
> Disk 7: Temp
> Disk 8: Tdisk
> Disk 9: etc
>
> I also like putting the Waterloo Mods onto a separate volume.
>
> /Tom Kern
>
> Robert O'Hara wrote:
> > I am looking at reworking the arrangement of disks in the VM 5-pack system.
> >
> > I have looked at the current disk utilization of MAINT, and I believe
> > that all of his minidisks can comfortably fit on a single 3350. Also,
> > all of the VM system disks (PERM, TDSK, TEMP) can fit on a single 3350.
> >
> > Now of course on a real mainframe we would want these disks spread out
> > over several channels, but it seems to me that with Hercules it does not
> > matter. Is that a correct assumption?
> >
> > I propose:
> >
> > disk 1: PERM, TEMP, TDSK
> > disk 2: all of MAINT's disks
> > disk 3: OPERATOR, RSCS, RSCS1, CPWATCH, AUTOLOG1, CMSBATCH,
> > ALGOL, BREXX, COBOL, DOSVS, OSBASIC, PLI, PL360, RPG,
> > SCRIPT, TAPEMAC, WATFIV
> > disk 4: GCCCMS
> > disk 5: REGINA, CMSUSER
> >
> > Comments on this layout?
> >
> > Thanks, Bob
>
« Return to Thread: VM system disk arrangement
| Free embeddable forum powered by Nabble | Forum Help |
