Taking the second question (b) first. We code one PATHIN DEVICE(uuuu,uuuu,uuuu,...) statement that contains all of CTC devices for all the 'other' members of the sysplex. Same for PATHOUT. I suppose that you can code as many devices as there are members in the sysplex, so any limit would be the sysplex size.
As for question (a), I'm pretty sure there is no limit because we code one PATHIN STRNAME(xxx) for each sysplex communication structure. There is no limit on those as the size varies according to CLASS. IBM recommends a modest number of CLASSes (we have three) but you could create a whole bunch if you wish. Unless someone else has hit a limit in practice, I'm guessing that there is no architectural limit. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Vernooij, Kees (ITOPT1) - KLM Sent: Tuesday, January 31, 2017 6:29 AM To: [email protected] Subject: (External):COUPLExx syntax question. Hello group, Is there a limit on: a) The number of PATHIN or PATHOUT statements in COUPLExx? b) The number of CTC devnums per PATHIN or PATHOUT DEVICE(devnum,devnum...) statement? Init and Tuning of z/OS V2.2 does mention any limit. Thanks, Kees. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
