Hello Peter . Lets start by asking what z/OS Service Calls are You issuing in CICS ? ANd I hope these service calls are issued under an OPNE TCB and NOT the QR TCB. . . ---------- Original Message ---------- From: Peter Ten Eyck <[email protected]> To: [email protected] Subject: z/OS Connect and CICS question Date: Tue, 9 Jul 2024 14:10:00 -0500
Any suggestions on how to handle this use case: Two CICS regions: A and B. A is an inquiry and update region and runs all the time except when the nightly batch cycle is underway. B is an inquiry region and runs 24/7. We want all z/OS service calls to run in region A, when region A is down, we want them to run in region B (this will be inquiry only). The service caller does not know when region A will be down. The backend CICS region to be used is control by definitions within the z/OS Connect server.xml file. For example, an entry like: zosconnect_cicsIpicConnection id="TXsmg" will determine what port is use: port="3152". The port is uniquely defined to a given CICS region, say region A. I wish I could have some logic within the server.xml file.... Thoughts? Notes - Running on: z/OS 2.5 z/OS Connect 03.00.77 CICS TS 5.5 ---------------------------------------------------------------------- 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
