MKS Implementer 2006 Administration Guide

Chapter 6: Third Party Integrations
330
Implementer supports only one copy of LANSA product libraries per installation. If you
use separate copies of LANSA on a single system where each copy has its own data and
program libraries, for example, one copy for development and/or QA and another copy
for production, each LANSA copy must point to a different copy of Implementer. For
information on troubleshooting problems with this usage, see the related messages in job
MON_BK0516. For information on installing parallel versions of Implementer, see the
MKS Implementer 2006 Installation Guide.
Defining Environments and Loading the Repository
The set up activities associated with managing LANSA applications include setting up the
environments that manage LANSA objects. You must associate each of these environments
with a partition where the LANSA applications reside.
In Work with Environments, establish the environment as a LANSA environment by
specifying an existing LANSA partition in the LANSA partition name field.
In the Copy LANSA object in check out field, specify whether to copy LANSA objects to
this environment during check out.
Do not specify the same partition for a From environment and target environment if the
environments are used for the same check out or promotion session. The special
environment type displays on the second Change Environments panel. If you remove
the partition name, the environment type reverts to a standard environment.
If you use a LANSA environment only for LANSA definitions, set the Compile required
field to N.
The export step exports LANSA objects on the request to a save file. You can set
promotion processing to automatically submit through the export step only. In the
Change Environment panel, specify Y in the Auto submit in create rqs field, and type
1=Expt in the Through step field.
To verify successful completion of the export, review the export reports generated by
LANSA, or use data area IMLNMSG as described in “Ending Promotions Based on
Message ID” on page 331.
To use an environment group for LANSA objects, the primary environment must be a
LANSA environment. LANSA objects are moved to other environments in the group
only if they have a special environment type of LANSA.
To archive LANSA objects, each LANSA environment must specify the archive library
and the number of archive versions to retain. For information on how to archive and
recover LANSA requests, see the MKS Implementer 2006 User Guide.
Run the Build List to create the list of LANSA objects in the partition associated with the
LANSA environment. Implementer analyzes the LANSA repository and retrieves the list
of LANSA objects.