How do I remove from my VL repository task IDs that have already been FINished or deleted from LANSA for iSeries?

Date:1 April 2009
Product/Release:Visual LANSA 
Abstract:What is the best way to remove tasks from a VL slave system when the tasks are already set to FINished or have already been deleted on LANSA for iSeries.?
Submitted By:LANSA Technical Support

What is the best way to remove tasks from a VL slave system when the tasks are already set to FINished or have already been deleted on LANSA for iSeries.

The technique is different depending on whether the tasks are already deleted on LANSA for iSeries or are set to FINished but still exist.

This request can be split into two parts.

1. Tasks currently set to FINished on LANSA for iSeries but have not been deleted.

The recommended approach is to do the following:

  • Create a repository group in PCMAINT for each slave repository (for example, in a VL slave server and network Client environment, you would create 1 repository for the slave server repository)
  • Change the following options in the partitions definitions (for every partition you want the task deletes to be propagated to)
  • Ignore Propagated Deletes NO
  • Check Before Propagating YES
  • In VL, perform a system initialization of the partition definitions
  • Once you delete a FINished or closed task on iSeries, it will be propagated to the VL repository(s)

Refer to 4.3 Repository Synchronization for more details.

Hint: after setting up the repository group and performing the system initialization, you can quickly test and view the propagation of tasks as follows

  • Create a a dummy task on LANSA for iSeries (this task is going to be created, closed, finished and deleted as part of the test)
  • Log into the VL IDE (in a partition that has the partition definitions set as above)
  • Start the host monitor and bring the Propagation tabsheet to the front. You should see the new task being propagated to VL
  • Set the task to closed in LANSA for iSeries
  • Perform a checkin or check out of any object to "kick start" the propagation. You should see the new task being propagated to VL with a status change (this status change can be viewed in VL under Repository -> Tasks)
  • Set the task to FINished in LANSA for iSeries
  • Perform a checkin or check out of any object to "kick start" the propagation. You should see the new task being propagated to VL with a status change (this status change can be viewed in VL under Repository -> Tasks)
  • Delete the task from LANSA for iSeries
  • Perform a checkin or check out of any object to "kick start" the propagation. You should see the new task being deleted in the propagation tabsheet
  • Open Repository -> Tasks in VL. The task is no longer listed.

2. Tasks already deleted on LANSA for iSeries.

Setting up repository synchronization and Propagate Deletes right now won't remove from VL any tasks that have already been deleted from LANSA for iSeries. The repository synchronization and Propagate Deletes will only start working for tasks deleted after its set up. You can contact your local support group to obtain steps to remove tasks that have been deleted on LANSA for iSeries but still exist in slave repositories.