We replicate all JES2 data sets (spool, checkpoint, etc) to our remote site, and we have NEVER failed to warm start JES2 using our asynchronous DASD replication solution - a solution which also guarantees consistency.
If the DASD replication solution is valid - that is, that consistency is achieved at the remote site, there is no reason JES2 will fail wam start. I would postulate that a "JES2 failure to warm start" problem would be an indication that the replication solution does not maintain consistency at your remote site, or else you are not including all of JES2's files in the replication solution. Brian On Wed, 26 May 2010 12:52:57 -0500, Hal Merritt wrote: >Some claim to have recovered (fell over) and successfully warm started JES2 with mirrored spool. That has not been our experience, even with flash copy. YMMV, but I would suggest planning for a cold start. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
