z/VM is indeed smarter than you: you can code any device type you like, CP
finds the real one out when it is varied online. Remark that CP's DEFINE
DEVICE doesn't even has a parameter to define the device type. Example:
define device 1200-123f unit_address 00 cu_number 1200
z/OS that's anothe
works well.
Not a problem with VMSEUCRE.
Hans
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of C. Lawrence Perkins
Sent: January-26-10 5:08 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: CP FLASHCOPY command fails to work on z/VM 5.4
Thank you, Mr. Schmiedge, I shall do that.
I noticed when I do a "Q DASD DETAILS " against the source and target in
z/VM 3.1, it reports the "CUTYPE" as a "3990-E9" even though I
specify "2105" in the IOCP of the 9672 that's running my z/VM 3.1 system.
When I do the same "Q DASD DETAILS" agai
You might look at UM32894, in the PSP bucket for RSU903. It was the
only thing that came up (resolves two APARs) when I searched IBMLink
for "flashcopy z/VM 5.4"
Ron
On Tue, Jan 26, 2010 at 1:51 PM, C. Lawrence Perkins
wrote:
> Yes, I just went "live" with z/VM 5.4 at RSU 901 and I'm experiencin
Yes, I just went "live" with z/VM 5.4 at RSU 901 and I'm experiencing the
exact same problem.
There's no "Command started" message, there IS a "Command completed"
message, and the FLASHCOPY doesn't run, it can't be seen with a Q FLASHCO
PY
and it can't be seen in the Copy Services GUI of the S
