Thanks
That did show ending gaps, but dirmap isn't a rexx exec that I could
modify....
I have diskmap modified to display the device type and the VSE volid,
for minidisks:
VOLUME USERID CUU DEVTYPE START END SIZE
VM300B $ALLOC$ 300B 3380 00000 00000 00001
3380-3
Y2KESA2 144 3380 00001 02225 02225
TOTAL1
DOSESA2 14D 3380 02226 03109 00884
CODE02
TSTESA5 228 3380 03110 03330 00221
DB2STR
3331 3337 7
GAP
$ENDPAK$ 300B 3380 03338 03338 00001
3380-3
I do have to keep the user direct updated with the proper VSE volsers
and $alloc$ with the proper device model (nothing magical happening
behind the covers),
but it sure serves the purpose I intended.
Tom Duerbusch
THD Consulting
>>> [EMAIL PROTECTED] 10/4/2006 2:04 PM >>>
DISKMAP was created in the times that DIRMAP was not standard available
in
VM, it was part of IPF, later CUF, available at extra cost.
Forget about DISKMAP and use DIRMAP. DIRMAP will report gaps at
end-of-volume, and it does not report fullpack mindisks as overlap.
DIRMAP
gives a non-zero returncode when it finds overlaps, etc
We define a user FULLPACK that has a fullpack minidisk for each volume,
user FULLPACK is exclude in all our backup templates. MAINT 123 no
longer
exists, but is a LINK to FULLPACK xxxx.
Kris,
IBM Belgium, VM customer support
The IBM z/VM Operating System <[email protected]> wrote on
2006-10-04 18:51:31:
> Now that is worth something.....
> It comes back with the number of cylinders, not just model.
> It use to be that model ment something....the number of cylinders
you
> could expect. But I've hit too many times, and I've done it also,
had
> the dasd system create small packs. Perhaps it was due to a small
> amount of space left over in the raid. Perhaps there as a real lock
> file that only needed to be a few cylinders in size.
> One of the first things I do with a new or upgraded VM system is to
> create a $END$ user that specifies the last cylinder of the pack.
Then
> diskmap will show the gap between the last mdisk and the end off the
> pack.
> Perhaps we could get the diskmap support people to use this command
to
> query how many actual cylinders there are and report the ending "gap"
if
> there is one.
> I came across one VM site (little VM usage, mostly for guest
machines,
> hence never hired a qualified VM systems programmer before), that
only
> used 1/3 of their disk. They had 3390-3 defined, but when VM was
laided
> down as only using 1113 cylinders, and diskmap didn't show the
remaining
> 2226 cylinders, they only used the first third of each pack.
> Tom Duerbusch
> THD Consulting
