On rare occasions a member in our Endevor Base library is edited from outside Endevor thereby destroying the Endevor footprint. Is there any way to preserve the member’s history before deleting it?
Preserve a member’s history by using the Endevor Archive and Restore actions.
SCL example:
STEPS would be as follows:
1 - Use the Endevor ARCHIVE action - sample SCL would be as follows:
000020 //ARCH1 DD DISP=SHR, DSN=BST.XXX.ARCH03
000021 //BSTIPT01 DD *
000022 ARCHIVE ELEMENT XXX123
000023 FROM ENVIRONMENT 'XXXENV' SYSTEM 'XXXTEST' SUBSYSTEM 'XXXSUB1'
000024 TYPE 'TEST1' STAGE *
000025 TO DDNAME ARCH1
000026 OPTIONS OVERRIDE SIGNOUT BYPASS ELEMENT DELETE .
2 - After checking to make sure the ARCHIVE has been successful - delete the member
3 - Using the Endevor Restore action - sample SCL would be as:
000018 //ARCH1 DD DISP=SHR,DSN=BST.XXX.ARCH03
000019 //*********************************************************************
000020 //* REQUEST DATA SET *
000021 //*********************************************************************
000022 //BSTIPT01 DD *
000023 RESTORE ELEMENT 'XXX123’'
000024 FROM DDN ARCH1 ENV 'XXXENV' SYS 'XXXTEST' SUB 'XXXSUB1'
000025 TYPE 'TEST1' STA NUM 1
000026 TO ENV 'XXXENV' SYS 'XXXTEST' SUB 'XXXSUB1' TYPE 'TEST1' STAGE NUM1
For more information on the ARCHIVE and RESTORE actions please refer to the Endevor documentation WIKI’s.