MKS Implementer 2006 Administration Guide

Appendix A: Implementer Data Areas and User Exit Programs
410
Regardless of the data area value the field values can be overridden during check out. You
can also set Implementer to bypass the display of the Delete Member/Objects While
Rejecting window and enforce the rules set by the IMREJECT data area. For details, see
“Bypass Window on Reject From QA (IMBYPSRJW)” described next.
Bypass Window on Reject From QA (IMBYPSRJW)
The IMBYPSRJW data area allows you to control the display of the Delete Member/Objects
While Rejecting window when rejecting items from a *QAC environment.
The default data area value *NO enables the window display. Set the value to *YES to bypass
the window display. For example, if source and object always remains in QA when rejecting
and developers are not allowed to override the rule, set the IMREJECT data area to *NO, and
set the IMBYPSRJW data area to *YES.
Reclaim Group (IMRCLAGRP)
When exiting the Implementer main menu, the Reclaim Activation Group (RCLACTGRP)
command automatically executes. If you use activation groups or ASC Sequel, the command
causes user programs that use activation groups to fail, and causes ASC Sequel to fail after
Implementer runs and ends in an iSeries session.
The IMRCLAGRP data area allows you to control execution of the RCLACTGRP command
when exiting the Implementer main menu. The default data area value is ‘*YES’. Change
the value to ‘*NO’ to bypass execution of the RCLACTGRP command.
Return File and Member ID After Promotion (IMRETFILID)
The IMRETFILID data area allows you to retain existing file and member IDs when
promoting physical files and logical files. The data area is located on both the host system
and the remote systems.
The default value *NO deactivates the feature. Set the value to *YES on both the host and
remote to retain the file and member IDs on both systems. The file and member IDs are taken
out of the from file and applied to all target files. If the file exists in the From environment,
the file and member IDs are derived from that file. If the file does not exist in the From
environment, the file and member IDs are derived from the object created in the Implementer
work library. Exceptions to this general rule are:
When a PF and related LFs do not exist in the From environment and a request is created
for the PF with the LFs added as related objects, the file and member IDs for the PF come
from the object created in the Implementer work library, and the file and member IDs for
the LFs come from the target logical files.
When targeting a remote environment that has the source library/compile location set to
R (remote), the compile option must be set to N to retain the file and member IDs.