Auto: Re: GRS setup for MONOPLEX to SYSPLEX
Je suis absent le 26 juin 2023. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
While my advice is not to do it at all, that doesn't meant hat it isn't possible without a plex, just that it's really (really) not a good idea. I have been at sites that were okay with the exposure, and if you are really, really careful;, you will still occasionally have issues, but for the most part, unless you are really careless, you will likely be okay. But it's so darn cheap to grab a couple ficon cards (even on ebay) and do it right. If the OP is correct that you can use the built-in IFB ports or some other internal connection, then that's worth giving it a try. I am very interested to hear how it goes for them without using FICON, it could be very interesting. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
Amen to that. I used to share PDSE, but it was "last resort" and for single action. IMHO the only way to safely share PDSE data is to IEBCOPY it to PDSU (PS file) and IEBCOPY to PDSE. (context is cross-sysplex) -- Radoslaw Skorupka Lodz, Poland W dniu 20.06.2023 o 14:24, Allan Staller pisze: Classification: Confidential Not my dog, but I would not do that, except under extreme duress. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gibney, Dave Sent: Monday, June 19, 2023 4:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRS setup for MONOPLEX to SYSPLEX [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] Even PDSE can be safely shared. If updates only occur from one LPAR and read-only everywhere else. And, said updates may not be reflected immediately (or until next IPL) in the other read-only LPARs -Original Message- From: IBM Mainframe Discussion List On Behalf Of Radoslaw Skorupka Sent: Monday, June 19, 2023 1:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRS setup for MONOPLEX to SYSPLEX Yes, PDSE do require SYSPLEX. Not GRS-plex, not CA-MIM (or MII), but SYSPLEX. Reason: PDSE use sysplex communication, not GRS facilities. Regarding to the topic: in order to share datasets you need ...nothing. No parallel sysplex No base sysplex Not even GRSplex No SMSplex Simply nothing except DASD available from several systems. Of course, the more mentioned facilities you have the better sharing is. And yes, in order to share PDSEs (properly) you still have sysplex. However you can share ICF BCSes (catalogs), VSAM, PS, PDS, etc. Note: there are various flavours of sharing. Shared DASD as a data transport method, shared PDSes with jobs, REXX tools, etc. - it can be shared easily, because it is not heavily used. Batch datasets - assuming proper batch windows it is also can be shared easily. For frequent sharing it is good to think about ICF ECS or RLS, etc. -- Radoslaw Skorupka Lodz, Poland W dniu 19.06.2023 o 17:03, Michael Babcock pisze: Beware of PDSEs. I’m not 100% sure but I think the sandbox needs to be in the plex to share them. Updating a PDSE outside of the plex can cause corruption. We have our sandbox in the plex just to avoid issues. On Mon, Jun 19, 2023 at 9:25 AM Paul Gorlinsky wrote: We have a sandbox system that references TSO user and ISV catalogs and datasets. The sandbox has a unique master catalog but shares virtually everything else. It does have access to the couple facility that the Sysplex is using ... But it is not a member of the Sysplex. Is it possible for a monoplex z/OS system to share DASD, user cats, etc., with a SYSPLEX via GRS management and coupling facility? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
Some folks have mentioned 'backplane' etc. There is no such thing as 'backplane' connectivity. One solution for a FICON CTC within a SINGLE CEC/CPC is to use a 'jumper cable' between 2 FICON ports - either on the same FICON card or 2 different ones. More about using and spec of the jumper cable in Planning Fiber Links manual - GA23-1409. Regards Parwez Hamid From: IBM Mainframe Discussion List on behalf of Dana Mitchell Sent: 22 June 2023 13:22 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRS setup for MONOPLEX to SYSPLEX Where are you seeing this or what is it called? The only shortcut I of know is: https://www-40.ibm.com/servers/resourcelink/lib03010.nsf/0/D78D2E0FE578329485258194006D1387/$file/SB10-7174-00.pdf With FICON partition-to-partition communication technology, communication between logical partitions of a single physical system can be achieved utilizing only a single physical FICON channel attached to a FICON Director switch. On Thu, 22 Jun 2023 00:19:21 -0500, Brian Westerman wrote: >According to the manual, you can configure them to be connected apparently >without wires. I believe it does the route internally, but I can't really >tell from the manual. There is probably a better manual because I seem to be >seeing just the overview, bur it does appear to not need any cabling. > >Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
what else would you expect to see in the FICON CTC reference guide :) You need to look at the technical guide for the specific hardware box that you want to implement on. I think that starting with the z13 that they allowed. There may have been some other methods previous to the z13, but this was the first that I came aware of something other than CF's and FC-CTCs. PSIFB - Parallel Sysplex InfiniBand ICA - Integrated Coupling Adapter IC - Internal Coupling link and then also FC-CTC which we already discussed. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
Where are you seeing this or what is it called? The only shortcut I of know is: https://www-40.ibm.com/servers/resourcelink/lib03010.nsf/0/D78D2E0FE578329485258194006D1387/$file/SB10-7174-00.pdf With FICON partition-to-partition communication technology, communication between logical partitions of a single physical system can be achieved utilizing only a single physical FICON channel attached to a FICON Director switch. On Thu, 22 Jun 2023 00:19:21 -0500, Brian Westerman wrote: >According to the manual, you can configure them to be connected apparently >without wires. I believe it does the route internally, but I can't really >tell from the manual. There is probably a better manual because I seem to be >seeing just the overview, bur it does appear to not need any cabling. > >Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
According to the manual, you can configure them to be connected apparently without wires. I believe it does the route internally, but I can't really tell from the manual. There is probably a better manual because I seem to be seeing just the overview, bur it does appear to not need any cabling. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
Presumably a FICON wrap-around cable. From: IBM Mainframe Discussion List on behalf of Dana Mitchell Sent: Wednesday, June 21, 2023 3:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRS setup for MONOPLEX to SYSPLEX On Wed, 21 Jun 2023 09:10:05 -0500, Paul Gorlinsky wrote: >Thanks everyone ... I will try the Backplane method and post results > Sorry, what exactly do you mean by 'Backplane method'? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
On Wed, 21 Jun 2023 09:10:05 -0500, Paul Gorlinsky wrote: >Thanks everyone ... I will try the Backplane method and post results > Sorry, what exactly do you mean by 'Backplane method'? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
Thanks everyone ... I will try the Backplane method and post results -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
Classification: Confidential I would tak a couple of FICON cables and string them between ports. Not sure about the z/14 hardware design. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Paul Gorlinsky Sent: Tuesday, June 20, 2023 8:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRS setup for MONOPLEX to SYSPLEX [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] Can we use the back plain of the z/14 to do the CTC thing? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
Yes, from the z13 up you are supposed to be able to create the connections. I have not tried it, but it seems to be outlined int he manuals. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
Can we use the back plain of the z/14 to do the CTC thing? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
Classification: Confidential Not my dog, but I would not do that, except under extreme duress. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gibney, Dave Sent: Monday, June 19, 2023 4:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRS setup for MONOPLEX to SYSPLEX [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] Even PDSE can be safely shared. If updates only occur from one LPAR and read-only everywhere else. And, said updates may not be reflected immediately (or until next IPL) in the other read-only LPARs -Original Message- From: IBM Mainframe Discussion List On Behalf Of Radoslaw Skorupka Sent: Monday, June 19, 2023 1:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRS setup for MONOPLEX to SYSPLEX Yes, PDSE do require SYSPLEX. Not GRS-plex, not CA-MIM (or MII), but SYSPLEX. Reason: PDSE use sysplex communication, not GRS facilities. Regarding to the topic: in order to share datasets you need ...nothing. No parallel sysplex No base sysplex Not even GRSplex No SMSplex Simply nothing except DASD available from several systems. Of course, the more mentioned facilities you have the better sharing is. And yes, in order to share PDSEs (properly) you still have sysplex. However you can share ICF BCSes (catalogs), VSAM, PS, PDS, etc. Note: there are various flavours of sharing. Shared DASD as a data transport method, shared PDSes with jobs, REXX tools, etc. - it can be shared easily, because it is not heavily used. Batch datasets - assuming proper batch windows it is also can be shared easily. For frequent sharing it is good to think about ICF ECS or RLS, etc. -- Radoslaw Skorupka Lodz, Poland W dniu 19.06.2023 o 17:03, Michael Babcock pisze: > Beware of PDSEs. I’m not 100% sure but I think the sandbox needs to > be in the plex to share them. Updating a PDSE outside of the plex can > cause corruption. > > We have our sandbox in the plex just to avoid issues. > > On Mon, Jun 19, 2023 at 9:25 AM Paul Gorlinsky wrote: > >> We have a sandbox system that references TSO user and ISV catalogs >> and datasets. The sandbox has a unique master catalog but shares >> virtually everything else. >> >> It does have access to the couple facility that the Sysplex is using ... >> But it is not a member of the Sysplex. >> >> Is it possible for a monoplex z/OS system to share DASD, user cats, >> etc., with a SYSPLEX via GRS management and coupling facility? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
There really is no "safe" way to share DASD without some sort of PLEX, either a full sysplex (with the CF's) or a baisc (baby) sysplex with Ficon adapters as CTC's. Otherwise, Catalog sharing is problematic and PDS/e sharing is not possible, and actually neither is standard PDS sharing of members because multiple people can end up overlaying each other. The reserves alone that will happen in a Sandbox are probably already affecting your other LPARs and you might not even realize it. HSM backups are a good example of something that issues reserves that can slow things down for the systems that aren't doing the backups, but are using those volumes. There are many more issues, too many to list. Can you get away without some sort of Plex? The answer is, if you are careful and don't mind the ENQ's, yes, until you do something that you should not have, in which case you can have a really bad day. The best you can hope for in that situation is that you lock out the other system(s), the worst is that you end up with wrong or corrupt data. It's far too easy (and cheap) to at least set up a basic plex (with ficon ports) than to expose yourself to problems. Honestly, you can use extra Ficon ports or buy a (or a couple) ficon cards on ebay or from some third party hardware (re)seller and have them installed. Connecting things up is extremely easy and quick, plus (since GRS is free) you end up with not only safety, but the ability to route commands from any system to any other system and several other niceties. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
Even PDSE can be safely shared. If updates only occur from one LPAR and read-only everywhere else. And, said updates may not be reflected immediately (or until next IPL) in the other read-only LPARs -Original Message- From: IBM Mainframe Discussion List On Behalf Of Radoslaw Skorupka Sent: Monday, June 19, 2023 1:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRS setup for MONOPLEX to SYSPLEX Yes, PDSE do require SYSPLEX. Not GRS-plex, not CA-MIM (or MII), but SYSPLEX. Reason: PDSE use sysplex communication, not GRS facilities. Regarding to the topic: in order to share datasets you need ...nothing. No parallel sysplex No base sysplex Not even GRSplex No SMSplex Simply nothing except DASD available from several systems. Of course, the more mentioned facilities you have the better sharing is. And yes, in order to share PDSEs (properly) you still have sysplex. However you can share ICF BCSes (catalogs), VSAM, PS, PDS, etc. Note: there are various flavours of sharing. Shared DASD as a data transport method, shared PDSes with jobs, REXX tools, etc. - it can be shared easily, because it is not heavily used. Batch datasets - assuming proper batch windows it is also can be shared easily. For frequent sharing it is good to think about ICF ECS or RLS, etc. -- Radoslaw Skorupka Lodz, Poland W dniu 19.06.2023 o 17:03, Michael Babcock pisze: > Beware of PDSEs. I’m not 100% sure but I think the sandbox needs to > be in the plex to share them. Updating a PDSE outside of the plex can > cause corruption. > > We have our sandbox in the plex just to avoid issues. > > On Mon, Jun 19, 2023 at 9:25 AM Paul Gorlinsky wrote: > >> We have a sandbox system that references TSO user and ISV catalogs >> and datasets. The sandbox has a unique master catalog but shares >> virtually everything else. >> >> It does have access to the couple facility that the Sysplex is using ... >> But it is not a member of the Sysplex. >> >> Is it possible for a monoplex z/OS system to share DASD, user cats, >> etc., with a SYSPLEX via GRS management and coupling facility? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
It's possible to share some things, but others can only be safely shared within a sysplex. From: IBM Mainframe Discussion List on behalf of Paul Gorlinsky Sent: Monday, June 19, 2023 10:25 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: GRS setup for MONOPLEX to SYSPLEX We have a sandbox system that references TSO user and ISV catalogs and datasets. The sandbox has a unique master catalog but shares virtually everything else. It does have access to the couple facility that the Sysplex is using ... But it is not a member of the Sysplex. Is it possible for a monoplex z/OS system to share DASD, user cats, etc., with a SYSPLEX via GRS management and coupling facility? Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
Yes, PDSE do require SYSPLEX. Not GRS-plex, not CA-MIM (or MII), but SYSPLEX. Reason: PDSE use sysplex communication, not GRS facilities. Regarding to the topic: in order to share datasets you need ...nothing. No parallel sysplex No base sysplex Not even GRSplex No SMSplex Simply nothing except DASD available from several systems. Of course, the more mentioned facilities you have the better sharing is. And yes, in order to share PDSEs (properly) you still have sysplex. However you can share ICF BCSes (catalogs), VSAM, PS, PDS, etc. Note: there are various flavours of sharing. Shared DASD as a data transport method, shared PDSes with jobs, REXX tools, etc. - it can be shared easily, because it is not heavily used. Batch datasets - assuming proper batch windows it is also can be shared easily. For frequent sharing it is good to think about ICF ECS or RLS, etc. -- Radoslaw Skorupka Lodz, Poland W dniu 19.06.2023 o 17:03, Michael Babcock pisze: Beware of PDSEs. I’m not 100% sure but I think the sandbox needs to be in the plex to share them. Updating a PDSE outside of the plex can cause corruption. We have our sandbox in the plex just to avoid issues. On Mon, Jun 19, 2023 at 9:25 AM Paul Gorlinsky wrote: We have a sandbox system that references TSO user and ISV catalogs and datasets. The sandbox has a unique master catalog but shares virtually everything else. It does have access to the couple facility that the Sysplex is using ... But it is not a member of the Sysplex. Is it possible for a monoplex z/OS system to share DASD, user cats, etc., with a SYSPLEX via GRS management and coupling facility? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
That’s exactly what we do. We share the SMS config though. On Mon, Jun 19, 2023 at 11:04 AM Paul Gorlinsky wrote: > I think I will do the same ... put in it the PLEX but run with a different > master catalog, spool, etc. > > Thanks > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
I think I will do the same ... put in it the PLEX but run with a different master catalog, spool, etc. Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
Beware of PDSEs. I’m not 100% sure but I think the sandbox needs to be in the plex to share them. Updating a PDSE outside of the plex can cause corruption. We have our sandbox in the plex just to avoid issues. On Mon, Jun 19, 2023 at 9:25 AM Paul Gorlinsky wrote: > We have a sandbox system that references TSO user and ISV catalogs and > datasets. The sandbox has a unique master catalog but shares virtually > everything else. > > It does have access to the couple facility that the Sysplex is using ... > But it is not a member of the Sysplex. > > Is it possible for a monoplex z/OS system to share DASD, user cats, etc., > with a SYSPLEX via GRS management and coupling facility? > > Thanks > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRS setup for MONOPLEX to SYSPLEX
Yes but the monoplex needs to communicate over CTCs to the SYSPLEX. Sent from my iPhone > On Jun 19, 2023, at 10:25 AM, Paul Gorlinsky wrote: > > We have a sandbox system that references TSO user and ISV catalogs and > datasets. The sandbox has a unique master catalog but shares virtually > everything else. > > It does have access to the couple facility that the Sysplex is using ... But > it is not a member of the Sysplex. > > Is it possible for a monoplex z/OS system to share DASD, user cats, etc., > with a SYSPLEX via GRS management and coupling facility? > > Thanks > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
GRS setup for MONOPLEX to SYSPLEX
We have a sandbox system that references TSO user and ISV catalogs and datasets. The sandbox has a unique master catalog but shares virtually everything else. It does have access to the couple facility that the Sysplex is using ... But it is not a member of the Sysplex. Is it possible for a monoplex z/OS system to share DASD, user cats, etc., with a SYSPLEX via GRS management and coupling facility? Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
