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
Joined: 20 Oct 2006 Posts: 6968 Location: porcelain throne
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.
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.