In some situations employees leave companies and the organization has not fully prepared for their exit. One specific scenario when an employee leaves that causes a great deal of extra work on IBM Cognos administrators involves the ex-employee's scheduled jobs, reports, etc.
Let's say that Ed has configured many scheduled jobs and reports that go out to a number of people, but he has left the company. Shortly after Ed's last day, several of these people are not receiving their scheduled Cognos reports. These employees contact their administrator. The administrator investigates and sees that these specific failed reports are attempting to use Ed's account and since he has left the company, his account in LDAP is inactive, causing the reports to fail.
In IBM Cognos, schedules are associated with a "credential," which is a security token that is associated with a Cognos user. In this case, Ed's schedules execute and authenticate through his credential. His stored credential passes to the authentication source (e.g. LDAP, Active Directory, etc.) to get logged in. After an employee leaves, their account becomes inactive in LDAP, AD, or the like, and all of their many scheduled jobs and reports will fail. The Cognos admin is then tasked with figuring out how to find and then reassign all of the ex-employee's schedules.
In Cognos, there is no easy way to do this. There is no search feature that allows you to find all schedules that use a specific Cognos user's credential.