...@sco.idaho.gov
wrote:
Should PIPEDDR work with attached DASD or does it only support MDISKs?
The documentation doesn't seem to say. I get an error with attached DAS
D
but it works fine with a full pack MDISK of the same DASD volume when
doing a dump/restore over TCPIP.
Using attached DASD
Sometimes you have to vary the device off and on before the system detects a
new VOLSER.
-Original Message-
From: Bruce Hayden bjhay...@gmail.com
Sent: Apr 5, 2011 3:33 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: PIPEDDR and attached DASD
I don't know why the mdisk works
On Wednesday, 04/06/2011 at 10:57 EDT, Dave david_v_le...@earthlink.net
wrote:
Sometimes you have to vary the device off and on before the system
detects a
new VOLSER.
When a guest DETACHes a volume, CP re-reads the volser.
(btw, Dave, you have reply-to: set to your id.)
Alan Altmark
z/VM
Should PIPEDDR work with attached DASD or does it only support MDISKs?
The documentation doesn't seem to say. I get an error with attached DASD
but it works fine with a full pack MDISK of the same DASD volume when
doing a dump/restore over TCPIP.
Using attached DASD will avoid label
anything differently for attached DASD, it just
passes the virtual address you specified to the trackread or
trackwrite stage of Pipelines.
On Tue, Apr 5, 2011 at 1:20 PM, Brian Nielsen bniel...@sco.idaho.gov wrote:
Should PIPEDDR work with attached DASD or does it only support MDISKs
On Tue, 5 Apr 2011 13:55:57 -0400, Bruce Hayden bjhay...@gmail.com wrot
e:
PIPEDDR should work fine with attached DASD. I just tried it on the
latest version and some older levels and they all worked fine with a
3390-3 with both the source disk and target disk attached. I have the
latest
On Tue, Apr 5, 2011 at 10:07 PM, Brian Nielsen bniel...@sco.idaho.gov wrote:
PIPTCQ1015E ERRNO 54: ECONNRESET.
PIPMSG004I ... Issued from stage 3 of pipeline 3 name iprestore.
PIPMSG001I ... Running tcpdata.
PIPUPK072E Last record not complete.
PIPMSG003I ... Issued from stage 2 of pipeline
Additional note: After this failed transfer the receiving DASD has a
label of SCRTCH. I would expect it to be SYSDRL after cyl 0 is transfere
d.
det 6607
DASD 6607 DETACHED
Ready; T=0.01/0.01 14:15:13
q 6607
DASD 6607 SCRTCH
Ready; T=0.01/0.01 14:15:15
Brian Nielsen
On Tue, 5 Apr 2011
On Tue, 5 Apr 2011 22:15:31 +0200, Rob van der Heij rvdh...@gmail.com
wrote:
On Tue, Apr 5, 2011 at 10:07 PM, Brian Nielsen bniel...@sco.idaho.gov
wrote:
PIPTCQ1015E ERRNO 54: ECONNRESET.
PIPMSG004I ... Issued from stage 3 of pipeline 3 name iprestore.
PIPMSG001I ... Running tcpdata.
I don't know why the mdisk works and the attached disk doesn't. If
the label is still SCRTCH, then nothing was written on the disk.
That seems like the TCP/IP connection wasn't established correctly.
We should take this offline to work on it further.
On Tue, Apr 5, 2011 at 4:27 PM, Brian Nielsen
10 matches
Mail list logo
