Remove an Environment from Endevor
search cancel

Remove an Environment from Endevor

book

Article ID: 399326

calendar_today

Updated On:

Products

Endevor

Issue/Introduction

We have an environment that has been decomissioned - is there any best practice on how to remove it from Endevor? 

Environment

All supported releases 

 

Resolution

You do not need to remove inventory structures (systems, subsystems, types and so on) from the MCF. Just make sure to remove all the elements to prevent orphan catalog entries. The inventory structures only exist as records within the MCF and are not referenced from anywhere else so they absolutely end their existence once the environment is removed from C1DEFLTS.  Follow the below steps to remove an Environment that is no longer needed.  As always it is recommended that you reach out to your local Broadcom Endevor Support team prior to performing these actions. 

  1. Perform these actions during off hours when there are no users on Endevor
  2. Backup all your Endevor Files 
  3. Archive and delete all the elements (highly recommended in-case you need to restore) 
  4. Do not delete any of the files (mcf/base/delta/etc..)  
  5. Run BC1JCSYN with PARM='BC1PCSYNUPDATE' to remove any orphans 
  6. Run BC1JACMO (ACMQ orphan delete) 
  7. Update the C1DEFLTS
    1. remove the environment
    2. ensure that the Next ENV is set correctly

*Note: If you use package element locking, you may need to first delete or reset any package that could be locking any elements in order to delete them, but nothing else.

*Note:  If you use LSERV, remove the MCF datasets from under LSERVs control