Updating Libraries › Deleting and Renaming Managed Private Libraries

Deleting and Renaming Managed Private Libraries

Whenever you delete or rename a library, regardless of whether CA PMO is managing it, follow this procedure:

1. Stop all batch jobs, TSO sessions, and started tasks that have opened the library (except for CA PMO).
2. Delete or rename the library (if you plan on moving it, you must then reallocate it).
3. Restart the jobs, sessions, or started tasks that you stopped.

When you delete or rename a library that CA PMO manages, CA PMO detects the update and temporarily stops managing the library. CA PMO may issue an offline report for the library depending on the value you specified for the EXCLREPT parameter. Messages PMO370I and PMO396I are written to your system log.

Notes:

• If you fail to stop a batch job, TSO session, or started task that has a library open, the first directory search after the move may produce a system abend 106 or 806. The abend occurs because the OPEN service creates a DCB and a DEB control block for the library, and the DEB contains the locations of the library. Once the library has been moved, its location may change, and SVC 18 may not be able to locate it. You can receive this type of abend even if you do not have CA PMO.
• If a managed library is deleted shortly before CA PMO is stopped, CA PMO may experience a system abend 314 or C03. This is a timing problem and is of no serious consequence to your site since CA PMO recovers from these abends and is able to quiesce cleanly.