Task Tracking in Master Slave Systems

Visual LANSA Admins

Task Tracking in Master/Slave Systems

If your Visual LANSA System is connected to a LANSA for iSeries Master System, then the following rules will apply:

  • All Task IDs will be created and maintained in the LANSA for iSeries Master System. (Refer to Working with Tasks in the LANSA for iSeries User Guide.)
  • All partition and other task tracking settings are set up in the LANSA for iSeries Master System. (Refer to Task Tracking Settings in the LANSA for iSeries User Guide.)
  • You must have task tracking turned on in the LANSA for iSeries Master System in order to ensure that all objects are properly tracked. Do not turn off task tracking in the Master System if you have Slave systems with active development. (Refer to Create, Review, Change or Delete Partition Definitions of the LANSA for iSeries User Guide.)
  • Task tracking must be used in Visual LANSA. It is a required parameter at logon. (Refer to Logon Parameters.)
  • All user profile and Task ID information must be refreshed in the Slave System whenever a change is made to the LANSA for iSeries Master System. (Refer to Current Task List.)
  • When objects are exported from a Master system, they can be assigned a Task ID and a PC Name. (Refer to How to Export from the IBM i in the Installing LANSA on Windows Guide.
  • When objects are checked out for update from a Master system, they are assigned both a task ID and the PC Name of the PC they are checked out to.

Also See

Share Task IDs

Task Tracking and Repository Synchronization

Task Tracking on Independent Systems

6.2.2 Approaches for using Task Tracking

Maintaining Users and Tasks on Slave Systems.

Ý 6.2.3 Task Tracking Set up