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 >>> [EMAIL PROTECTED] 10/4/2006 11:19 AM >>> The following CP command displays the size of a DASD device. CP Q DASD DETAILS rdev >
