Dana, when we had the CTCs defined going through a set of switches we did not have the Serial-# field coded in HCD. When we defined new CTCs without the switches we at first did not code the Serial-# And things didn't seem to want to "connect" up properly. We then coded the Serial-# in HCD and things connected up properly.
Here are a few other thoughts on the subject of the base sysplex setup. I can understand the idea of trying to save money. We all have to deal with management wanting not to spend money. So you do what you can with what you have. The idea of using existing channels with DASD or TAPE at the other end for the CTC connections can be done, I'm just not a fan of that support. If possible I would rather see the CTCs have their own channels. That is how I've set it up over the years. I help support two base sysplex environments and one parallel sysplex. The two base sysplex have three lpars each. We use the XCF/CTC setup to support GRS and a few other things for the base sysplex. From what I see GRS ring works better when it lets XCF do the signaling management. Naturally the overhead of GRS will vary depending on how busy it gets. That also holds true for XCF. Like I say I think GRS ring works better with XCF in the picture. Thanks.. Paul Feller GTS Mainframe Technical Support -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Dana Mitchell Sent: Tuesday, June 02, 2020 8:35 AM To: [email protected] Subject: Re: Base SYSPLEX setup [EXTERNAL] On Sun, 31 May 2020 12:19:16 +0000, Feller, Paul <[email protected]> wrote: > We found out the hard way when we converted off of FICON switches you > need to code a serial number in the control unit definition to make the > connection work properly. > Does lack of a serial number really prevent these from working? I've always had them coded, but I just assumed they were just so HCD could make out what the physical connections were, for reporting purposes and whatnot. Dana ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
