Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
Moving from Endevor Stage B to D

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CA Products
View previous topic :: :: View next topic  
Author Message
mkk157

Active User


Joined: 17 May 2006
Posts: 310

PostPosted: Tue Mar 11, 2008 2:10 pm    Post subject: Moving from Endevor Stage B to D
Reply with quote

When a cobol-db2 program moves from Endevor stage B to D then what are all the actions will be taken at the back-end like deleting or updating the entries for PLAN in PLAN_TABLE or anything others.
Back to top
View user's profile Send private message

HappySrinu

Active User


Joined: 22 Jan 2008
Posts: 195
Location: India

PostPosted: Tue Mar 11, 2008 4:47 pm    Post subject: Reply to: Moving from Endevor Stage B to D
Reply with quote

Hi,
It completely depends up on your site installation.
Usualy when you move an element it creates a component list and moves to your target stage. then deletes from sending stage (Depend on your site again) .

This component list does have input/output fields information
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6968
Location: porcelain throne

PostPosted: Tue Mar 11, 2008 5:15 pm    Post subject:
Reply with quote

endevor does not directly modify db2 sys tables. at our site, since there is a different db2 creator at each stage, as modules are promoted, their corresponding bind elements are re-bound (if necessary) otherwise not.

endevor controls components of run-units. as far as db2 is concerned, the plan tables, etc... are only updated thru execution of binds.

If the module is not recompiled and the creator for the db does not change there are no required updates to the plan-table. but, in an environment like mine, binds are executed - which updates the db2 sys tables.
Back to top
View user's profile Send private message
Mistermind
Warnings : 2

New User


Joined: 08 Feb 2008
Posts: 46
Location: Dublin

PostPosted: Thu Mar 13, 2008 1:47 am    Post subject:
Reply with quote

Assuming you merely MOVE but do NOT recompile from stage B to stage D, an automated delete of DB2 package at stage B will mean that in any future Unit retest at stage B, the loadmodule will be availablve via concatenation from stage D, but the DB2 plan will be gone, i.e. falling back to a retest in B to compare against D will not be possible without rebind.

If DBRM is also deleted by ENDEVOR, then recompile as well as rebind will be necessary. If Unit re-test does not uncover a need for program change, then B-to-D re-promotion without change will be necessary -- quite a lot of wasted work.
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 -> CA Products All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Moving values to a variable of copybo... Vignesh Sid COBOL Programming 6 Wed Sep 06, 2017 1:04 pm
No new posts CA-Endevor Admin - 3 years minimum vasanthz Mainframe Jobs 0 Tue Apr 04, 2017 5:36 am
No new posts Moving a PD to PD spoorni DFSORT/ICETOOL 8 Fri Oct 07, 2016 9:52 pm
No new posts Moving character data to smallint in db2 rikdeb DB2 5 Thu Jul 14, 2016 12:38 am
No new posts Endevor error C1UU999E during cast Musab Ahmed CA Products 3 Wed Jun 29, 2016 12:41 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us