Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

What is Production, Development & Testing Region?

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> All Other Mainframe Topics
View previous topic :: :: View next topic  
Author Message
sandip_datta

Active User


Joined: 02 Dec 2003
Posts: 151
Location: Tokyo, Japan

PostPosted: Fri Sep 10, 2004 2:15 pm    Post subject:
Reply with quote

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?

Regards,
Sandip.
Back to top
View user's profile Send private message

mmwife

Super Moderator


Joined: 30 May 2003
Posts: 1592

PostPosted: Sat Sep 11, 2004 11:24 pm    Post subject:
Reply with quote

Hi Vikas,

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.
Back to top
View user's profile Send private message
mmwife

Super Moderator


Joined: 30 May 2003
Posts: 1592

PostPosted: Sun Sep 12, 2004 1:47 am    Post subject:
Reply with quote

Hi Vikas,

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.
Back to top
View user's profile Send private message
sandip_datta

Active User


Joined: 02 Dec 2003
Posts: 151
Location: Tokyo, Japan

PostPosted: Mon Sep 13, 2004 1:05 pm    Post subject:
Reply with quote

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.

regards,
Sandip.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> All Other Mainframe Topics All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Testing rerad cursor for status with ... John F Dutcher DB2 8 Fri May 19, 2017 9:35 pm
No new posts IMS region inactive - User abend code... gthmrj IMS DB/DC 5 Tue Mar 07, 2017 12:29 pm
No new posts Determine Region with max bandwidth f... seahawk789 COBOL Programming 3 Mon Feb 27, 2017 8:26 pm
No new posts JCL to get submitted once dataset has... vinu78 JCL & VSAM 17 Thu Feb 16, 2017 7:32 am
This topic is locked: you cannot edit posts or make replies. COBOL Software Development Lead at Fi... shally Mainframe Jobs 0 Fri Jan 20, 2017 5:21 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us