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 Pipelines runtime module, if that makes a difference. PIPEDDR
>doesn't really do anything differently for attached DASD, it just
>passes the virtual address you specified to the trackread or
>trackwrite stage of Pipelines.
I updated both systems PIPEDDR from 1.4.10 to 1.5.12 and the Pipelines
runtime from 1.0111 to 1.0112.
pipe query
PIPINX086I CMS/TSO Pipelines, 5654-030/5655-A17 1.0112
(Version.Release/Mod) - Generated 3 Dec 2010 at 11:10:08.
It still fails the same way (but there are now progress messages on the
sending side):
--------------------
q 6607
DASD 6607 ATTACHED TO BNIELSEN 6607 R/W VZ6607
Ready; T=0.01/0.01 13:36:07
pipeddr restore * 6607 11000 (listen noprompt
Connecting to TCP/IP. Enter PIPMOD STOP to terminate.
Waiting for connection on port 11000 to restore BNIELSEN 6607.
Sending user is BNIELSEN at VMP2
Receiving disk BNIELSEN 9D5E from 172.16.64.45
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 1.
PIPMSG001I ... Running "unpack".
Data restore failed.
Ready(01015); T=0.01/0.02 13:39:17
-------------------------
q 9d5e
DASD 9D5E ATTACHED TO BNIELSEN 9D5E R/W SYSDRL
Ready; T=0.01/0.01 13:32:49
pipeddr dump * 9d5e 172.16.64.44 11000
Dumping disk BNIELSEN 9D5E to 172.16.64.44
PIPTCQ1015E ERRNO 32: EPIPE.
PIPMSG004I ... Issued from stage 9 of pipeline 1 name "ipread".
PIPMSG001I ... Running "tcpclient 172.16.64.44 11000 linger 10 reuseaddr
U".
Cylinder 133 of 3339 completed (3%)
Cylinder 266 of 3339 completed (7%)
Cylinder 400 of 3339 completed (11%)
Cylinder 533 of 3339 completed (15%)
Cylinder 666 of 3339 completed (19%)
Cylinder 800 of 3339 completed (23%)
Cylinder 933 of 3339 completed (27%)
Cylinder 1066 of 3339 completed (31%)
Cylinder 1200 of 3339 completed (35%)
Cylinder 1333 of 3339 completed (39%)
Cylinder 1466 of 3339 completed (43%)
Cylinder 1600 of 3339 completed (47%)
Cylinder 1733 of 3339 completed (51%)
Cylinder 1866 of 3339 completed (55%)
Cylinder 2000 of 3339 completed (59%)
Cylinder 2133 of 3339 completed (63%)
Cylinder 2266 of 3339 completed (67%)
Cylinder 2400 of 3339 completed (71%)
Cylinder 2533 of 3339 completed (75%)
Cylinder 2666 of 3339 completed (79%)
Cylinder 2800 of 3339 completed (83%)
Cylinder 2933 of 3339 completed (87%)
Cylinder 3066 of 3339 completed (91%)
Cylinder 3200 of 3339 completed (95%)
Cylinder 3333 of 3339 completed (99%)
Dump failed.
Ready(01015); T=4.77/6.30 13:37:11
************************
I verified that both DASD volumes are the same size (Mod-3's w/3339 cyls)
:
---------------
q dasd details 6607
6607 CUTYPE = 2105-E8, DEVTYPE = 3390-0A, VOLSER = VZ6607, CYLS =
3339
CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY
-SUBSYSTEM Y Y Y - N N
-DEVICE Y - - Y N N
DEVICE DETAILS: CCA = 07, DDC = --
DUPLEX DETAILS: --
PAV DETAILS: BASE VOLUME WITH 01 ALIAS VOLUMES
CU DETAILS: SSID = 6600, CUNUM = 6600
Ready; T=0.01/0.01 13:48:14
---------------
q dasd details 9d5e
9D5E CUTYPE = 2105-E8, DEVTYPE = 3390-0A, VOLSER = SYSDRL, CYLS =
3339
CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY
-SUBSYSTEM Y Y Y - N N
-DEVICE Y - - Y N N
DEVICE DETAILS: CCA = 5E, DDC = --
DUPLEX DETAILS: --
CU DETAILS: SSID = 450D, CUNUM = 9D00
Ready; T=0.01/0.01 13:44:11
***************
Are there any options that might help?
Brian Nielsen
