USER DIRECT nitpicking

[s390guy]

USER DIRECT nitpicking

[BobBolch]

1. Changing these to NOLOG: ALGOL,BREXX,FORTRAN,COBOL,OSBASIC,PLI,PL360,RPG,SCRIPT,TAPEMAP,WATFIV,XCOMPARE
2. The only IDs I see without a 19D are server machines and NOLOG IDs.
3. VM/CE does not include any 3380s.
4. Rearranged to specify OPTIONS, IPL, CONSOLE, SPOOL devices, DEDICATEs, LINKS, then MDISKS.
5. Addressed in issue #12
6. I will ask on the list about DOSVS procedures.
7. I made this change for the MAINT minidisks that cover the real system volumes, but the other minidisks, are only present so that DISKMAP can identify disk space that is in user. What advantage would changing those addresses supply?

[jgeorge44]

3. VMCE supports 3380 DASD though, and I'd like to hope at some point VMCE might grow from a bunch of 3350 disks to perhaps fewer larger capacity disks, so I thought the couple of hundred bytes wasted for future formatting might be worth it.
4. No real advantage, honestly, I said it was nitpicking. It seems easier for me to look at the virtual CUUs in the directory than to look at the volser, but certainly not worth arguing the point. :)

[BobBolch]

3. I do not see the benefit of fewer larger disks. Please elaborate. With 3350, one can use the calculations and procedures in the manuals for disk space.

[g4ugm]

I can see definite advantages to having more smaller disks, even down to one per product.
For a start you can have smaller distributions. Folks who need the product disks them can download them.
If you need extra space there will always be space on the product pack.
This also means the directory will stay "clean" and you won't get the mess Joe describes.
I dislike 3380's Whilst they are bigger than a 3350 the real pay-back was floor space. Each "box" had two HDAs each with two sets of heads, So in a real machine you get around 2.5 GB per unit, but to the mainframe it looked like four 4 x 650mb drives...

[BobBolch]

Some items are fixed in V1 R1.1