MKS Implementer 2006 Administration Guide

Lawson Software Integration
Emergency development requires a separate emergency development partition. The
emergency partition is allowed on only one path.
All environments on the path require the Copy LANSA objects in check out field set to N.
Visual LANSA requires the use of task tracking within your development model. For
details, see “LANSA Task Tracking” on page 332.
The MWIPROD user profile must have data read authority to the following LANSA files
used by Implementer programs:
DC@F76V1 (TTS Object Event Log)
DC@F75V2 (TTS Task Definition Log)
DC@F74V1 (TTS Object Register)
Change the DC@A07 data area in LANSA to set an Implementer exit program that
executes the LANSA APIs to run a command. This task is described next.
To change the DC@A07 data area in LANSA
Issue the following command:
CHGDTAARA DTAARA(DC@PGMLIB/DC@A07 (689 20)) VALUE('MKSIM
IMLNUSEX')
IMPORTANT Previous releases of the Implementer and Visual LANSA integration
required adding a trigger to LANSA file DC@F76 in library DC@DTALIB. The
DC@A07 data area replaces the need for the trigger; thus, you must remove the
trigger if it exists. Use the following command to remove the trigger:
RMVPFTRG FILE(DC@DTALIB/DC@76) TRGTIME(*ALL) TRGEVENT(*ALL)
Lawson Software Integration
Lawson Software provides a comprehensive and customizable solution that includes
applications for enterprise performance management, distribution, financial statements,
human resources, procurement, retail operations, and service process optimization.
Implementer is compatible with all releases of Lawson Software.
When configuring Implementer for integration with Lawson, two features of the Lawson
modules require additional setup considerations:
Source and object library structure.
LID method of screen and report generation in Lawson 7.
333