MKS Implementer 2006 Administration Guide

Chapter 6: Third Party Integrations
320
3 Define the Initial Library List parameter as follows, and press ENTER.
Add the AS/SET object library (ASSETO is the default) before the AS/SET file
library (ASETF is the default).
Add the AS/SET object library and AS/SET file library before the Implementer
library.
Add the QTEMP library in any position on the library list.
Special Command Setup
You must define the AS/SET Dependency Check as a special command attached to the *TST
environment to run automatically after check out.
To define the special command
1 From Work with Environments, select the *TST environment with option 19=Special
commands. The Work with Environment Special Commands panel displays (the panel
may display existing commands).
2 Press F6=Add. The Expanded Command Display panel displays.
3 Define the special command as follows:
In the For Action field, type 6 (Checkout).
In the When to do field, type 2 (After-OK).
In the Command field, type:
ICHKADKDEP MBROBJ(#OBJECT)
OBJCODE(#OBJCOD)
FRMENV(#FRMENV)
TOENV(#TRGENV)
4 Press ENTER.
BPCS Integration
To use Implementer with SSA/BPCS software, you must make special compile changes.
These changes involve setting up required object codes within Implementer, and possibly
making changes to your environment setup. These setup tasks are explained next.
Compile Considerations
The first consideration for performing BPCS compiles within Implementer is to determine
whether all compiles are BPCS compiles, or whether some compiles are BPCS compiles and
others are not performed through BPCS commands or programs (for example, DSPF).