I don't know of a 'classic' definition. To me bronze-plex is a fully functional parallel sysplex that shares little or nothing more than what's required for sysplex, essentially the control data sets plus any others that might be needed for 'qualifying' sysplex exploiters. JES is not on the list. My bronze-plex does indeed contain two different JES(2) nodes that communicate via NJE as if they were 1000s of miles apart.
OTOH I have run configurations before parallel sysplex even existed that contained two separate JES2 nodes. Never had a special name for that other than primary/secondary. In my mind, bronze-plex is a configuration born, like mine, of the need to qualify for parallel sysplex pricing. That actual need has long since disappeared due to configuration changes, but splitting the bronze-plex apart would require additional hardware resources--at least CF engines and maybe memory plus effort to accomplish--that so far have not seemed compelling. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile jo.skip.robin...@att.net > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Ed Jaffe > Sent: Saturday, January 30, 2016 03:16 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: Deleting a dataset that GRS has enqueued. > > On 1/30/2016 8:47 AM, Tom Marchant wrote: > > However, I believe that skip had written in an earlier append that hos > > bronzeplex was a combination of two sysplexes. If that is the case ... > > A "classic" bronzeplex is two or more JESplexes within a single sysplex. > > -- > Edward E Jaffe > Phoenix Software International, Inc > 831 Parkview Drive North > El Segundo, CA 90245 > http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
