MKS Implementer 2006 Administration Guide

LANSA Integration
You manage LANSA objects with LANSA environments. A LANSA environment type is
established by associating an Implementer environment with a valid LANSA partition. This
ensures any changes to objects in a partition are managed using the associated environment.
Specific object codes accomplish the check out and promotion of LANSA objects to and from
the LANSA environments. The Check Out function locks the name of the LANSA object
and—depending on the environment definition—copies (export and import) the LANSA
objects to the development environment.
Promotion prepares the LANSA objects for export and moves (imports) the objects into the
target environment. Distribution of LANSA objects to remote locations is supported.
LANSA objects are archived in the archive library specified for the target environment.
Implementer supports using LANSA task tracking to manage the development of LANSA
objects and related issues.
All reports and inquiries track the LANSA objects managed by Implementer.
Setting Up the Interface
The following information applies to setting up the integration. For more information, see
“LANSA Prerequisites” on page 107.
In System Control Maintenance, verify the LANSA installed field is set to Y.
Change the Implementer job description (MWIJOBD) to include the LANSA product
libraries in the library list.
IMPORTANT The job description must include the LANSA libraries to avoid the
promotion of LANSA definitions ending abnormally.
Verify the Implementer user profile MWIPROD has authority to modify and delete the
definitions for all LANSA objects managed with Implementer.
Implementer provides the IMLNPSO data area that allows you to store the name of the
LANSA partition security officer. Implementer runs the LANSA command for export/
import using the partition security officer profile to prevent migration failures caused by
insufficient authority to the LANSA command and the items being exported. For details
on the data area, see “LANSA Partition Security Officer (IMLNPSO)” on page 408.
If distributing LANSA objects to remote locations using the Implementer Receiver,
Implementer uses the IMPJOBD job description (in library MKSIR) on the remote system
to set the library list for remote jobs. This requires you add the LANSA product libraries
DC@PGMLIB, DC@DTALIB, and DC@DEMOLIB to the IMPJOBD library list. If you
renamed the LANSA product libraries, add the renamed libraries to the initial library list
of the IMPJOBD job description.
329