Date: Thu, 6 Sep 2007 13:57:16 -0700
Reply-To: CICS List <CICS-L@LISTSERV.UGA.EDU>
Sender: CICS List <CICS-L@LISTSERV.UGA.EDU>
From: Trivers Software <trivers3708@SBCGLOBAL.NET>
Subject: Re: CICS TS 2.2 to 3.1 Migration - Another CSD query
In-Reply-To: <OFEF1AE9BB.E329BBA7-ON8025734E.0039BB9E-8025734E.003AF593@hsbcib.com>
Content-Type: text/plain; charset="us-ascii"
We use Automon/RDO from Unicom to mask the inter-release changes.
-----Original Message-----
From: CICS List [mailto:CICS-L@LISTSERV.UGA.EDU] On Behalf Of David White
Sent: Thursday, September 06, 2007 3:44 AM
To: CICS-L@LISTSERV.UGA.EDU
Subject: CICS TS 2.2 to 3.1 Migration - Another CSD query
We're about to migrate our CICS regions from TS 2.2. to TS 3.1 running on
z/OS 1.8. We have regions across 4 Sysplexes (1 non-production and 3
Production), with a single CSD per production sysplex, and 3 (for Dev, OA
and UA) on the non-prod. Updates to the production CSDs is via DFHCSDUP
only, for the non-prod CSDs read-write access is limited to only 1 region
for each CSD.
While looking into various options for managing our CSDs the following
question came up.
What are the cts 3.1 code requirements for using a cts 3.1 dfhcsd in a cts
2.2 region? Do we have to install the CICS early code even if only cts 2.2
regions will be running on that lpar, or even sysplex?
Any advice, opinions, views are welcome.
Regards
David White
************************************************************
HSBC Bank plc
Registered Office: 8 Canada Square, London E14 5HQ
Registered in England - Number 14259
Authorised and regulated by the Financial Services Authority
************************************************************
-----------------------------------------
SAVE PAPER - THINK BEFORE YOU PRINT!
This E-mail is confidential.
It may also be legally privileged. If you are not the addressee you
may not copy, forward, disclose or use any part of it. If you have
received this message in error, please delete it and all copies
from your system and notify the sender immediately by return
E-mail.
Internet communications cannot be guaranteed to be timely secure,
error or virus-free. The sender does not accept liability for any
errors or omissions.
