Joined: 02 Dec 2003 Posts: 150 Location: Tokyo, Japan
Vikas,
Your questions are logical than technical.
Let us know what is your opinion about four or more different regions and what will be the sequence - first production and then development or reverse?
Before I answer your ques please note that there is a CICS forum on this site. Please take the time before posting to familiarize yourself with this site before posting.
Now to your ques:
Suppose you're tasked to change a CICS module. You've coded the change and you are ready to unit test. This testing is performed in the Test Region.
One you're satisfied with that testing, you "migrate" the module to the prod libraries and the next execution of the module (with your changes) is performed in the Production Region.
If the change you wrote does not execute properly the module with the change you wrote is "backed out" and the original code is used to execute in the Prod Region.
At this point you research the problem and devise a solution, then the cycle outlined above is performed once again.
I'm not familiar with the Emergency Region you cite. My experience is with an "Emergency Migration" where "Emergency Libraries" are used to facilitate a quick 'backout" process. I can't imagine a shop having 2 production level CICS Regions, one of which handles "emergency changes", but then some shops may have special requirements.
Before I answer your ques please note that there is a CICS forum on this site. Please take the time before posting to familiarize yourself with this site before posting.
Now to your ques:
Suppose you're tasked to change a CICS module. You've coded the change and you are ready to unit test. This testing is performed in the Test Region.
One you're satisfied with that testing, you "migrate" the module to the prod libraries and the next execution of the module (with your changes) is performed in the Production Region.
If the change you wrote does not execute properly the module with the change you wrote is "backed out" and the original code is used to execute in the Prod Region.
At this point you research the problem and devise a solution, then the cycle outlined above is performed once again.
I'm not familiar with the Emergency Region you cite. My experience is with an "Emergency Migration" where "Emergency Libraries" are used to facilitate a quick 'backout" process. I can't imagine a shop having 2 production level CICS Regions, one of which handles "emergency changes", but then some shops may have special requirements.
Joined: 02 Dec 2003 Posts: 150 Location: Tokyo, Japan
We have one emergency library for modules. In case of emergency(when there is no time for usual promotion and necessary approval, we generally go for this). The modules then go to emergency load library. And while picking up the module during execution in production, the sequence is Emergency Library --> Production Library.
Next day, we nee to regularise the changes i.e., need to move the load from Emergency library to production library with necessary approvals. That means, usually there should not be any module in emergency load library after 1 day.
Usually, we have 3 different regions -
Development - Developer have all access - Read, Write, Update, Delete.
UAT - Access is Read, All others by jobs only by operator upon approval.
Production - Nothing after than viewing the source code. We need to restore the files to development for further access. This restoration is done by operator after approval.
