IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Bypassing a stage in Endevor


IBM Mainframe Forums -> CA Products
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
CHALLY

New User


Joined: 07 Jul 2006
Posts: 4
Location: Texas

PostPosted: Sat Aug 26, 2006 2:15 am
Reply with quote

There are 5 stages in the Endevor installation that we have in our project. Can I bypass the 3rd stage and directly move the source code from 2nd stage to the 4th stage?
Kindly clarify.
Back to top
View user's profile Send private message
Archana_MF

New User


Joined: 21 Jul 2006
Posts: 49
Location: California

PostPosted: Sat Aug 26, 2006 3:00 am
Reply with quote

Hi,

Yes U can bypass the stage with below conditions,

TEST ENVIRON
STAGE 1 : DEV ( this is entry stage where u move ur code from ur librray to Endevor
STAGE 2: QA stage under the same Envrion

PROD ENVIRON
STAGE 1 : some stage of ur PROD ENVIRON
STAGE 2 : PRD ur Production Application in PROD ENVIRON

U can skip Stage 1 of PROD ENVIRON provided ur final Dest is Stage 2 of PROD ENVIRON.
That is in short, u shuld always exit an ENVIRON at Stage 2 and U can enter the Next ENVIRON at Stage 1 or 2

Hope its not tooo confusing
So, check the ENVIRONS of ur 5 stages. by the way what are these 5 stages???
Back to top
View user's profile Send private message
vkumard

New User


Joined: 13 Dec 2005
Posts: 9

PostPosted: Wed Jan 10, 2007 11:41 am
Reply with quote

Anothe options to bypass the Stage:

For example, let have the following stages

Development:
Stage 1
Stage 2
Certification:
Stage 3
Stage 4
Model office:
Stage 5
Stage 6
Production :
Stage P.

As per Endevor setup, normal code move will happen from Dev --> Cert ---> Model ---> Prod.

For bypassing the stage, we can use the term TRANSFER in Endevor.

Options :

Select Batch;Build SCL;Transfer
1;1;9.

Give your element present in which stage.
Mention the target region need to move and make ensure you choose "Y" for options WITH HISTORY. Otherwise all the verison history details of element will be surprassed.

WITH HISTORY ===> Y (Y/N)

This transfer option is not advisable since it breaking the endevor stages.. and you should need to take care of backward processing of modules/links and any bind(if required).
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> CA Products

 


Similar Topics
Topic Forum Replies
No new posts Updating endevor JCLs CA Products 5
No new posts Finding the plan when code compiled u... DB2 2
No new posts CA-Endevor Admin - 3 years minimum Mainframe Jobs 0
No new posts Endevor error C1UU999E during cast CA Products 3
No new posts SE37 while adding element to endevor CA Products 5
Search our Forums:

Back to Top