Alan & Schuh
Damned.
It was not a question but just a post to a previous opened thread called
'DASD VOLUME SIZES'. I probably did a wrong manipulation since I thought to
give a 'proof' of what I said... a 3380-3 seen with 3339 cyls through the cp
q da details cmd.
Alain
Le 26/11/08 19:32, « Alan Altmark » <[EMAIL PROTECTED]> a écrit :
> On Wednesday, 11/26/2008 at 12:48 EST, Alain Benveniste
> <[EMAIL PROTECTED]> wrote:
>> here is an example about what was reported to IBM.
>
> Alain, you posted some output without a question. It looks like you
> changed the label on disk volume attached to a guest and you expect QUERY
> DASD DETAILS to give you the current label. If you want CP to refresh the
> label, vary it off and back on. When you VARY ON a disk, the label,
> allocation map, and any configuration data (e.g. size) are read and cached
> (for CP's use).
>
> I think there's a special case where we detect the guest has rewritten the
> label if it is via a minidisk that overlaps cyl 0, but I'm not sure. I
> wouldn't expect CP to catch a label change on a dedicated device since CP
> isn't remapping cylinder numbers and could, potentially, be unaware
> (because of I/O assist) of any label change. Same problem if someone
> relabels the volume from another system.
>
> Alan Altmark
> z/VM Development
> IBM Endicott
>
