On 11/25/2022 6:22 AM, Don Parrott wrote:
We created a DASD only SYSPLEX about 3(?) years ago on a z/14 primarily to facilitate
PDSE sharing between the PROD and DEVL lpars. I would have rather had a coupling
facility for a full sysplex, but we did not have one. There was a ton of work to
setup the CTC pairs between the three lpars, the final one being our maintenance
lpar. GRS will have to be reviewed carefully. We have had zero issues since
implementation. Feel free to write me directly for specific questions.
[email protected]<mailto:[email protected]>
No doubt setting up CTC connections is more work than simply setting up
a CF messaging structure, but they're good to have in case you want to
use/test GRS ring, push VTAM or XCF traffic through a dedicated
resource, connect to non-z/OS LPARs such as z/VM or z/VSE without going
through an OSA, etc.
Years ago, Skip Robinson gave a nice explanation (perhaps at SHARE?
perhaps here on IBM-MAIN?) on the naming convention they used at SCE to
keep it all straight. The upper nybble indicates whether a guzzinta or a
guzzoutta, the next two nybbles represent the LPAR number, and the last
nybble is the device number 0-F. Having this naming convention makes it
trivially easy to know which LPARs the control units and devices should
be connected to since the LPAR number is part of the device number.
We have only six LPARs (1, 2, 3, 4, 5 & 8), so it doesn't look too bad.
Clearly, if you have 85 LPARs on the box it will take longer to define
them, but still be just as easy to get it right.
----------Device------ --#--- --------Control Unit Numbers + --------
Number Type + CSS OS 1--- 2--- 3--- 4--- 5--- 6--- 7--- 8---
4010,16 FCTC 1 2 4010 ____ ____ ____ ____ ____ ____ ____
4020,16 FCTC 1 2 4020 ____ ____ ____ ____ ____ ____ ____
4030,16 FCTC 1 2 4030 ____ ____ ____ ____ ____ ____ ____
4040,16 FCTC 1 2 4040 ____ ____ ____ ____ ____ ____ ____
4050,16 FCTC 1 2 4050 ____ ____ ____ ____ ____ ____ ____
4080,16 FCTC 1 2 4080 ____ ____ ____ ____ ____ ____ ____
5010,16 FCTC 1 2 5010 ____ ____ ____ ____ ____ ____ ____
5020,16 FCTC 1 2 5020 ____ ____ ____ ____ ____ ____ ____
5030,16 FCTC 1 2 5030 ____ ____ ____ ____ ____ ____ ____
5040,16 FCTC 1 2 5040 ____ ____ ____ ____ ____ ____ ____
5050,16 FCTC 1 2 5050 ____ ____ ____ ____ ____ ____ ____
5080,16 FCTC 1 2 5080 ____ ____ ____ ____ ____ ____ ____
The only real drawback I can see to using CTCs like this is the "chewing
up" of device numbers in environments with a shortage of them.
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/
--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
