MKS Implementer 2006 Administration Guide

Appendix A: Implementer Data Areas and User Exit Programs
404
Delete User Programs and User Source During Promotion
(IMDLTFRMUP and IMDLTFRMUS)
For AllFusion 2E CM users, the IMDLTFRMUP and IMDLTFRMUS data areas allow you to
control whether to remove user programs (IMDLTFRMUP) and user source (IMDLTFRMUS)
in the from library after successful promotion. You can delete programs and display files
without removing database files from development or test libraries to retain test data.
The data areas exist on both the host and remote system. On the remote, the data areas
control whether user programs and user source are removed from the remote QA
environment during promotion to the remote. This is beneficial when both QA and
production environments exist on both the host and remote systems.
Valid values for the data areas are *YES or *NO enclosed in single quotes. The default value is
‘*YES’. The value *NO overrides the value specified on a promotion request.
NOTE
If using these data areas to enable Implementer’s remote QA environment
cleanup feature, you must also set up a special command to run as part of the
promotion. For details, see “Clearing Remote QA Environments” on page 384.
For traditional member/objects and IFS objects, this functionality is available
using object code overrides. For details, see “Object Code Overrides” on page 91.
Delete Locks (IMDLTLOCK)
The IMDLTLOCK data area allows you to set default values on the Confirm Delete of Locks
panel that displays when you select a member/object with option 4=Delete from the
Workbench.
You can specify different values for the deletion of locks, source, and objects. The valid data
area values are *YES or *NO. The default value *YES sets the value to Y for all options. The
value *NO sets the value to N for all options.
You can also specify a three-character string consisting of a combination of Y and N to
individually set each value. For example, if IMDLTLOCK is set to YYN, the result is Delete
locks = Y, Delete sources = Y, Delete objects = N. If IMDLTLOCK is set to NYN, the result is
Delete locks = N, Delete sources = Y, Delete objects = N.
NOTE Users must have lock maintenance rights set to Y in the environment for
authority to override these defaults. This is defined in Work with Environments,
User Capabilities.
Delay Evoked Jobs (IMDLYJOB)
The IMDLYJOB data area allows you to place an evoked job into a delay state once the job
becomes active. Working with remote jobs can be difficult, as a batch job on one machine
initiates the job on another machine. Developers typically use this feature to capture specific