|
View previous topic :: View next topic
|
| Author |
Message |
naveensrimf
New User
Joined: 04 Oct 2005
Posts: 34
|
|
|
|
| While Moving the CICS-DB2 program into Production. Do we need New Copy first or BIND Plan? |
|
| Back to top |
|
 |
Stefan
Active User
Joined: 12 Jan 2006
Posts: 110
Location: Germany
|
|
|
|
Both should be done in synch. So the sequence does not really matter.
But to be absolutely sure you could do something like:
1. Assure that DB2 package versioning is active.
2. Bind the package.
3. If it fails, no problem occured concerning the productive application.
4. Save the load module.
5. Copy the new load module to the DFHRPL library.
6. Issue a PHASEIN or NEWCOPY.
7. If it fails, copy the save version back to the DFHRPL library.
8. If everything was OK you could delete the save copy of the load module and free the old package.
Hope this helps |
|
| Back to top |
|
|
kapil_tv
New User
Joined: 02 Aug 2007
Posts: 3
Location: Pune
|
|
|
|
Bind should be done first.
Once bind is done. Then we can copy the load module in the library and do a NEWC. This is very important in the environment of multiple DB2/CICS region. For a single region environment the order doesn't matter.
Kapil |
|
| Back to top |
|
|
daveporcelan
Active Member
Joined: 01 Dec 2006
Posts: 792
Location: Pennsylvania
|
|
|
|
There is obviously more than one correct way to do this.
In our shop we:
1) Move Load and DBRMLIB members
2) Bind and Newcopy each DB2/CICS region
We realize there is a possibility of a -805 if user activity is high.
For this reason, we try to do our Production Deployments for CICS at 3am. |
|
| Back to top |
|
|
|
|
