Date: Mon, 27 Feb 2006 16:43:54 -0500
Reply-To: CICS List <CICS-L@LISTSERV.UGA.EDU>
Sender: CICS List <CICS-L@LISTSERV.UGA.EDU>
From: Joseph Fatula <jfatula@AESSUCCESS.ORG>
Subject: Fw: Migration running two versions
Content-Type: text/plain; charset=us-ascii
I would not change the macros which are referenced by the CICS
compiles/assemblies for the application programmers, whether they be via
proc or SCLM, until after you have migrated to the new version of CICS and
you have been stable in production for at least a month.
Otherwise, there are issues with the modules. For example, the newly
compiled modules would not be supported in the "old" version CICS
regions--whether they would work or not--but not a good thing.
For example, if you were going from 2.2 to 3.1, 2.2 modules could run
in 3.1 regions, but 3.1 modules in 2.2 regions would not be supported.
If you have to backout a set of regions--you don't want to have to
recompile the modules.
There may be some installations that change their macros while the
upgrade is in progress--but it is not easy to manage and the benefits are
usually not worth it.
Be aware that, normally, the CICS modules (User Replaceable Programs
and exits)--*** are *** changed for each release and it would normally be
advisable to have two sets of these load modules if in the middle of a
If anything is unclear, please repost. Many of us have been through
a million of these migrations.
----- Forwarded by Joseph Fatula/PHEAA on 02/27/2006 04:33 PM -----
Sent by: "CICS CICS-L@LISTSERV.UGA.EDU
Migration running two versions
Please respond to
Please bear with me, but this is my first CICS installation and will be my
first time to deal with a migration strategy dealing with running a new
version of CICS in a "test" region, with an older version of CICS running
in its "production" region, both on the same LPAR.
I have successfully installed CICS on our TEST LPAR, and have placed the
new CICS version in LPA and LNKLST. From there, I know I can successfully
bring up two regions at different levels - got that. BUT, my question now
has to do with the applications staff on the our PROD LPAR. They would
like me to bring up their "test" region at the new level. They would then
proceed to test there while going about business as usual. They may do
compiles there, I don't know. Anyway, if they do and that module is
compiled with the new level libraries, what happens if they need to move it
to the "production" region, at the lower level? Is my only concern that
they recompile it with the production's lower level?
I'm sure many of you have had to follow some sort of strategy/backout in
this scenario, and am looking forward to your experienced suggestions.
This message contains privileged and confidential information intended for the above addressees only. If you
receive this message in error please delete or destroy this message and/or attachments.
The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging
in the unauthorized use of this message.