This topic describes the status of the name change tasks, how to view tasks in progress, and how to delete a name change task.
After you create a name change task, the task defaults to the Scheduled
status. A scheduled task begins executing on the IBM
® Sametime Community Server at the time specified in the server setting on the Name Change page of the Sametime
® System Console (Sametime System Console
-> Sametime Servers
-> Sametime Community Servers
-> Name Change
). You cannot edit a name change task that has the Scheduled
status. The only way to change a scheduled task is to delete the task and then create a new task in its place.
Once a task begins executing, its status changes from Scheduled
to In Progress
if any of the servers have the name change task with the status that is in progress or scheduled. You cannot delete a task that is in progress. If all the servers have tasks that are marked Check error log
, the name change task can be marked Finished
means the task has completed the name change successfully. At this status level, you can add or delete any task.
Check error log
means there were errors incurred while the task was running. At this stage, you can add or delete a task.
The status column provides only the status of the task running on the server being used; it does not provide a summary of the task across servers and clusters of servers.
You can have only one name change task scheduled or in progress on a IBM
Sametime Community Server. If a name change task is scheduled or in progress, you cannot create another name change task on the Sametime Community Server until the existing name change task completes.
You cannot delete a task that is marked In Progress
. You can delete a task that is marked Scheduled
or Check log status
. There is a log file on the server that collects failures in Name Conversion.
- A user name that is changed in the directory but is not yet changed in the vpuserinfo.nsf database will appear as offline in the contact list and privacy list of another user until the name change task executes on the other user's home Sametime Community Server.
- All members of a changed group appear as offline in the contact list and privacy list of a user until the name change task executes on the user's home Sametime Community Server.
You can view the status of the names being changed. The vpuserinfo.nsf
database includes a view for name change tasks. The task you are running is not marked complete. If several Sametime Community Servers operate as a Community Services cluster, you view the status of a name change task on only one Sametime Community Server in the cluster. The database replicates in real-time among the servers in the cluster. When the name change task changes the vpuserinfo.nsf database on one server, the changes are automatically replicated to the vpuserinfo.nsf databases on all other servers in the cluster.
Below is an example of viewable statuses. In the example, Servers X, Y, and Z are not clustered, and servers A, B, and C are clustered.
|Servers ||task is created on Server X |
|Server X||task appears in Name Change page|
|Server Y||task does NOT appear in Name Change page, but it is in the log file|
|Server Z||task does NOT appear in Name Change page, but it is in the log file|
|Server A||task does NOT appear in Name Change page, but it is in the log file|
|Server B||task does NOT appear in the Name Change page, and it does NOT appear in the log file|
|Server C||task does NOT appear in the Name Change Status page, and it does NOT appear in the log file|
Turn on the sametime.ini
flag if you are working locally: NC_LOCAL_CONVERSION = |
Parent topic: Running the name conversion utility