We enforce Endevor by simply not letting the programmers update anything above TEST. Moves into MDOF or PROD must be done by an authorized Endevor administrator. Basically, this is our Production Control staff as a part of controlling production.
On Tue, Feb 12, 2013 at 12:07 PM, Staller, Allan <[email protected]>wrote: > <snip> > BTW, there is no CA Endevor in this picture -- I just thought that > whatever Endevor administrators did might work for my customer. > </snip> > > FWIW, it has been my experience that most people do not perform their > entire development cycle within Endevor. Most, however, insist > that production migrations occur via Endevor. No other method allowed. > > This is normally accomplished by protecting the target libraries > w/RACF/ACF2,... to prevent anyone other than Endevor from writing to > the target libraries. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
