If an element exists in Endevor, a "RETRIEVAL" (through FOREGROUND Option)
must done first. The person "signing out" the element is then responsible
for placing it back into Endevor. Select the following options from the TSO
Primary Menu:
E - ENDEVOR or 3.PP.E
5 - CLAIMS
2 - FOREGROUND
3 - RETRIEVE (Example below:)
----------------------------- RETRIEVE ELEMENTS -----------------------------
OPTION ===> r
ELEMENT DISPLAY OPTIONS:
blank - Element list S - Summary B - Browse H - History
R - Retrieve element M - Master C - Changes
FROM ENDEVOR: ACTION OPTIONS:
ENVIRONMENT ===> CLAIMS CCID ===>
SYSTEM ===> ACES EXPAND INCLUDES ===> N (Y/N)
SUBSYSTEM ===> ACES SIGNOUT ELEMENT ===> N (Y/N)
ELEMENT ===> othirpt1 OVERRIDE SIGNOUT ===> N (Y/N)
TYPE ===> COBOL REPLACE MEMBER ===> N (Y/N)
STAGE ===> 2 1 - CLAIMS1 2 - CLAIMS2
COMMENT ===> update per request
TO ISPF LIBRARY: LIST OPTIONS:
PROJECT ===> otxx94 DISPLAY LIST ===> Y (Y/N)
LIBRARY ===> end WHERE CCID EQ ===>
TYPE ===> source WHERE PROC GRP EQ ===>
MEMBER ===> othirpt1 BUILD USING MAP ===> N (Y/N)
FIRST FOUND ===> Y (Y/N)
TO OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>
-----------------------------------------------------------------------------------
Retrieve the program to yourid.LIB.SOURCE.
If two or more people are changing the same program, the second person can get
a copy of the existing production version by retrieving it from Endevor but
changing SIGNOUT ELEMENT (under ACTION OPTIONS) from "Y" to "N". The second
person should retrieve it to a PDS other than yourid.LIB.SOURCE. This kind of
retrieval makes a copy of the program but it is still signed out to the first
person.
If the second person must put in his/her change before the first person, an
approver can override the original signout. The approver perfroms the ADD
action to put second person's version to Stage U by changing OVERRIDE SIGNOUT
(under ACTION OPTIONS) from "N" to "Y".
No comments:
Post a Comment