MKS Implementer 2006 Administration Guide

Chapter 6: Third Party Integrations
LANSA Task Tracking
Visual LANSA
332
Implementer supports using LANSA task tracking to manage your LANSA development
and related issues.
Task tracking replaces the use of Implementer projects. With task tracking enabled,
Implementer processes LANSA tasks as projects by creating a project record from the
specified task number, if one does not already exist. To support the LANSA task number
format of 8 characters and Implementer’s project number format of 7 characters, the LANSA
task number right-truncates when converted to the Implementer project ID.
Implementer creates a project record for any task number that exists in the LANSA task
definition log file with a status of Open or Work. Implementer also creates a project record if
the task exists in the LANSA TTS object register file and the task number does not exist in the
Implementer project file. If the task does not exist in the TTS object register file, any value
specified in the Project Reference field is processed as a project number by Implementer.
When creating a request, the locked project number defaults in the Project Reference field on
the Create Request panel. During the move, the project number defaults in the TASK_ ID
parameter on the LANSA command for exporting and importing.
The LANSA command allows only one task number; thus, only one task number is allowed
per promotion request. Using project filters guarantees only one task number per request. If
you select records for more than one task number, exit the Create Request panel and clear the
selected objects to omit.
LANSA task tracking is controlled in Implementer by the LANSA Task Usage (IMLNTSK)
data area. The data area value must be *YES to enable task tracking (the default value is
*NO).
To enable LANSA task tracking
Issue the CHGDTAARA command as follows:
CHGDTAARA DTAARA(IMLNTSK) VALUE(*YES)
Implementer provides integration with Visual LANSA for the development of your graphical
and client/server applications in a Windows-based development environment.
Key Considerations
The following information applies to setting up and using Visual LANSA with Implementer.
Environment pathing must be set up for LANSA environments. The test partition is
allowed on only one path.