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

Endevor - Signouts set at final stage


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

Active User


Joined: 10 May 2007
Posts: 147
Location: India

PostPosted: Tue Aug 05, 2008 4:03 pm
Reply with quote

Hi All,

We are facing the below problem in Endevor.

Problem:
Signout is getting set at production (final) stage (which shouldn't happen) at very few times for few element types.

Environment:
The elements are moved to production through Rexx and Endevor environment.

I know this is a very vague question to ask. I would like to know whether any of you have faced the similar scenario and suggestions/inputs regarding the same is invited
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


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

PostPosted: Tue Aug 05, 2008 4:35 pm
Reply with quote

yes, have encountered this problem with my co-workers that don't bother to familiarize themselves with their environment, or read, or even look at the panel presented.

when you move (migrate) an element, there is an ACTION OPTION (y/n) RETAIN SIGNOUT. (right side of the panel).
Back to top
View user's profile Send private message
senjay

Active User


Joined: 10 May 2007
Posts: 147
Location: India

PostPosted: Tue Aug 05, 2008 4:48 pm
Reply with quote

Hi,

Sorry that i didn't provide more info in my previous mail. I already loooked in to that option also. Currently we are moving the elements to production stage through Batch mode (JCL).

one more point i didn't mention in my previous post is, the element is moved to production first and then after few days, the sign out is set.

Sorry again
Back to top
View user's profile Send private message
HappySrinu

Active User


Joined: 22 Jan 2008
Posts: 194
Location: India

PostPosted: Tue Aug 05, 2008 5:04 pm
Reply with quote

Senthil,
Check the last action of the element which you see the element signed out, I guess it should be "SIGN OUT" instead of "MOVE" which you done from dev to production.


If you want that element to work for your project now, you can always retrieve that element and can work of placing the option "OVER RIDR SIGN OUT = N" . this action will not disturb any others work in Endevor.

Usualy every site would have set that in defaults of setting Endevor, it would have been set that retain signout =n for move actions in Endevor. especially to Production.

Hope it helps.
Back to top
View user's profile Send private message
HappySrinu

Active User


Joined: 22 Jan 2008
Posts: 194
Location: India

PostPosted: Tue Aug 05, 2008 5:05 pm
Reply with quote

forgot to add, for better information, you contact your Endevor product support team at your site.
Back to top
View user's profile Send private message
senjay

Active User


Joined: 10 May 2007
Posts: 147
Location: India

PostPosted: Wed Aug 06, 2008 11:39 am
Reply with quote

HI Srinu,

Thanks for your reply. Of course you are correct in the way that the 'Override signout' option can set the signout at production.

For us, this is also one of the cause. But we found out that major problem lies in our REXX environment.

Thanks all for your info and time.
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