Cam,
CP Query DASD FREE only displays mainframe DASD which is not currently ATTACHED
(to system, or a guest).
That display does not mean that the DASD is available for allocation. A DASD
could be allocated to a guest which is not logged on at the moment, and the
DASD is not attached to the sy
Really -- hardly anything to say on this? Surprisingly few responses,
less than I've received for any other queries. Is there no story here,
media migration just ... works? Nothing to see here, not worth writing
about? Or are some aspects worth addressing?
On 6/16/2014 23:42, Gabe Goldberg wrote:
That's why I love this forum. When I have a question that on the surface
may appear to be pretty simple, you guys educate me in that with enterprise
technologies, nothing is simple. These answers have been extremely
insightful. The main guy that sets our physical environment up chimed in
and and
Ah, yes, "DASD volumes"...
(chuckles)
I spent a LOT of time doing AIX support-- both before p5 hypervisors and
after-- so, really, what is a "DASD volume"?
Is it a physical volume? (Which, using a hypervisor, may be mapped into a
logical volume, or, via a SAN, is declared "physical" also despit
>>> On 6/22/2014 at 08:37 AM, John Campbell wrote:
> Ah, yes, so Q DASD FREE will report on free space... but will it return
> CONTIGUOUS free space (ISTR minidisk granularity is in "cylinders")? Or
> will it just be the count of cylinders (or whatever "granularity" the
> device, like FBA, which
Ah, yes, so Q DASD FREE will report on free space... but will it return
CONTIGUOUS free space (ISTR minidisk granularity is in "cylinders")? Or
will it just be the count of cylinders (or whatever "granularity" the
device, like FBA, which might not be reported in cylinders) that haven't
been alloca
Cameron:
When I set up the system back in the beginning, the standard was to be
that any volume which was totally free was given a volume serial of
FR, where was its physical device address. Are you saying that
Alan or Rich are doing something different? David maintained this
standard as
If you do a Q DASD DETAILS against the address -- and see a null for
VOLSER= - then it has no label and hasn't been initialized .. if you see
VOLSER=FREE then it's been initialized and given a label of FREE.
Scott Rohling
On Sat, Jun 21, 2014 at 9:43 PM, Cameron Seay wrote:
> So when I s
>>> On 6/22/2014 at 12:43 AM, Cameron Seay wrote:
> So when I see free that is not a sysprog assigned label, but an indication
> of being uninitialized?
Possibly. The guy who maintains our System z box will run cpfmtxa on a DASD
volume that has been released from use and assign a volser of FRE
