We have mirrored DASD to our recovery site for 15 years. However, we use 
XRC/SDM rather than PPRC. Not sure if issues are different, but caveat 
emptor. In the early years we were afraid to mirror JES2 data sets. 
Indeed, we actually experienced mirroring errors in the days of ESCON over 
conventional channel extenders (CMT), and pulled out spool and checkpoint 
from the mix. This created all kinds of recovery problems to determine 
where we were in a batch cycle at the time of recovery. We tried various 
cockamamie schemes to solve these problems to little avail. 

We eventually matured to FICON over DWDM. Discovered almost by accident 
that adding JES2 data sets to the mix had truly negligible effect on XRC 
overhead. Since then we've mirrored both checkpoint and spool for all 
recoverable systems. When we IPL in DR, we know exactly where we were at 
the point of last update. Given the performance of modern technology, I 
can't imagine trying to recover without JES. Hard to believe that PPRC 
would alter this opinion. 

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



From:   "Storr, Lon A CTR USARMY HRC (US)" <[email protected]>
To:     [email protected], 
Date:   09/03/2014 09:16 AM
Subject:        JES2 and IBM Global Mirror (UNCLASSIFIED)
Sent by:        IBM Mainframe Discussion List <[email protected]>



Classification: UNCLASSIFIED
Caveats: NONE

Hello List,

I'm interested in experiences regarding the inclusion of JES2 (checkpoint 
and spool) volumes in IBM Global Mirror (i.e. PPRC).

Googling yields pros and cons (the most troubling of which is mentioned in 
a presentation given by Tom Wasik of IBM at Share 118 on 3/12/12).

Any input would be much appreciated.

Thanks,
Alan


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

Reply via email to