MKS Implementer 2006 Administration Guide

System Control Maintenance
NOTE If MKS Source integration is enabled, the native revision number scheme
applies only to objects and items not archived in MKS Source. If MKS Source
integration is not enabled, the native revision number scheme applies to all items.
Versioning program Specify the name of a custom versioning program to call to perform
object version stamping. Required if versioning is active and the Assign
native version number at field is set to 3=user defined.
IMPORTANT If the custom program references objects, for example, files or data
areas, the library list for the Implementer job description MWIJOBD and each
user’s interactive library list must include the library containing those objects.
Library Specify the library location of the custom versioning program. Required if
versioning is active and the Assign native version number at field value
is 3=user defined. Valid options are a specific library name, *LIBL, or
*CURLIB.
Concurrent
Development Scope
System Control Maintenance Field Descriptions: Panel 3
Field Description
Specify which locks establish concurrent development—either all locks
from all production environments, or only those locks from the same
production environment as the current check out From environment.
1=All Production Env:
Concurrent development is based on locks from all production
environments. Activates concurrent development for the current check
out, if, among all existing locks, a lock exists for the same member/
object and object code.
2=Per Production Env:
Concurrent development is based only on locks from the same
production environment as the check out From environment. Activates
concurrent development for the current check out if a lock exists for the
same member/object and object code and the same production
environment as the current check out From environment. This is the
default value.
To define a user’s environment capabilities for concurrent development,
see “Locks” on page 110. To further customize concurrent development
processing, see “Customizing Implementer” on page 414.
71