To move an IODF from one system to another, there are various methods as others 
have suggested. We have always used an HCD native process that 

1. creates an offload copy of the source IODF
2. submits a second job to transmit the unload to the target site
3. runs the second job at the target site, calling program CBDMGHCP to recreate 
the IODF

This procedure requires that the target site be up and running but does not 
require any intervention at the target site. It's very important for us that 
the target copy be bit for bit identical to the source. 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
[email protected]

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
kekronbekron
Sent: Friday, July 10, 2020 10:25 PM
To: [email protected]
Subject: (External):Re: Two Processors and One IODF

CAUTION EXTERNAL EMAIL

To get the IODF across... what you'd need to do depends on who manages DR at 
the other side:
if it's you, setup an email job on your primary system to email you the IOCP 
when a new config is activated.
If it's IBM or some such, setup an email job on your primary system to email 
the vendor/partner the IOCP when a new config is activated.

- KB

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, July 11, 2020 10:51 AM, kekronbekron 
<[email protected]> wrote:

> The trouble with using same CU and units at both sites is ... unnecessary 
> risk of varying/initializing a unit on the wrong side. Could be a major 
> whoopsie.
> Best to use a few ranges on this side, and a few ranges on the other, so it's 
> very easy to know what's where.
>
> -   KB
>
>     ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>     On Friday, July 10, 2020 11:49 PM, Michael Babcock [email protected] 
> wrote:
>
>
> > We are in the process of bringing DR back in-house and have a new
> > z15-T02 in our new facility (our current "home" machine is a z14-ZR1).
> > I want to be able to manage both processors from a single IODF.  I'd 
> > like to have the same CHPIDs, CUs, and Device addresses both at home and
> > in our DR machine.   I have the new processor defined in our current
> > IODF and have used the CHPID mapping tool to map the PCHIDs to CHPIDs.
> > I have tested adding devices with the same address to both 
> > processors and that seems to work (as long as I define the CUs to 
> > both processors first.  I tested adding a range of 16 tape drives).
> > My questions are this:
> > 1.  Is this something we even want to do (same IODF, same device addresses)?
> > 2.  What's the best way to move the IODF at home to the DR machine?
> > 3.  Are there any gotchas we need to watch out for?
> > 4.  We have IBM DS8886s and are using Metro Global Mirror 
> > Multi-Target w/Practice.  Any concerns here?
> > 5.  Am I crazy for even entertaining this idea?
> > 6.  Any alternatives I need to consider?
> >
> > For IBM-MAIN subscribe / signoff / archive access instructions, send 
> > email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to