CP will read the label at IPL time, when a device is detached from a
user, and when it is varied online. In between those times, it does not
know of any volume serial other than the last one it recorded.
When your system was IPLed, device 613C was available but CP was unable
to read its label. At some point, a label was written from some other
system, so CP was unaware of its being written. When you detached the
device, CP read the label successfully and was able to supply the volume
serial in responses and messages,
Regards,
Richard Schuh
________________________________
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Michael MacIsaac
Sent: Monday, February 04, 2008 5:49 AM
To: [email protected]
Subject: Label names in some kind of cache?
OK, there has to be a logical explanation for this (and I should
probably know it):
A DASD's label seems to change after attaching then detaching
it:
==> q 613c
DASD 613C FREE
^^^^
==> att 613c *
DASD 613C ATTACHED TO MAINT 613C WITH DEVCTL
==> q 613c
DASD 613C ATTACHED TO MAINT 613C R/W
==> det 613c
DASD 613C DETACHED BY MAINT
==> q 613c
DASD 613C DM613C
^^^^^^
So 613C's label seems to change from "FREE" to "DM613C"
Previously I had formatted 613C (and a host of others) with
CPFMTXA and did set the label to DM613C. But I had logged off MAINT
before this session - so it would not seem that the old label name
should be in any type of cache.
Any help will be appreciated. Thanks.
"Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061
