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.
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? > 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 conflicts and also avoids maintaining > hardcoded MDISKs with DEVNO's in the directory. Unfortunately, the DEFINE > MDISK command doesn't have a DEVNO option. > > > Here is what the failure looks like from the receiving and sending sides > using attached DASD at both ends: > > --------- > > pipeddr restore * 6930 11000 (listen noprompt > Connecting to TCP/IP. Enter PIPMOD STOP to terminate. > Waiting for connection on port 11000 to restore BNIELSEN 6930. > Sending user is BNIELSEN at VMP2 > Receiving data 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.01 08:58:15 > > ---------------- > > 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 7 of pipeline 1 name "ipread". > PIPMSG001I ... Running "tcpclient 172.16.64.44 11000 linger 10 reuseaddr > U". > Dump failed. > Ready(01015); T=0.02/0.03 07:54:34 > > **************** > > > If I create full pack MDISKs via DEFINE MDISK (starting at cyl zero) it > works fine, as shown below. > > ------------ > > pipeddr restore * 6930 11000 (listen noprompt > Connecting to TCP/IP. Enter PIPMOD STOP to terminate. > Waiting for connection on port 11000 to restore BNIELSEN 6930. > Sending user is BNIELSEN at VMP2 > Receiving data from 172.16.64.45 > 41 MB received. > Data restored successfully. > Ready; T=4.04/4.54 09:34:18 > > > ----------- > > pipeddr dump * 9d5e 172.16.64.44 11000 > Dumping disk BNIELSEN 9D5E to 172.16.64.44 > -- All data sent to BNIELSEN AT VMP1 -- > 41 MB transmitted. > Dump completed. > Ready; T=6.27/8.21 08:30:37 > > ------------ > > Brian Nielsen > -- Bruce Hayden z/VM and Linux on System z ATS IBM, Endicott, NY
