MKS Implementer 2006 Administration Guide

Chapter 4: Remote Distribution Concepts and Setup
190
This feature is useful when you have related development activities spread across multiple
systems, or a development system and a distribution system centrally located with
distribution to many remote systems. You accomplish this with DDM (Distributed Data
Management).
Before using this feature you need to decide which system has the primary version of
Implementer. This should be the system Implementer is most heavily used on.
You must set the default user profile on the communications entry to have *ALL rights to the
Implementer database files on the primary system. By default, DDM jobs run from the
remote system under user profile QUSER and require access to the Implementer files. For
details on the communications entry, see the MKS Implementer 2006 Installation Guide.
Starting and Ending Remote Database Support
A secondary system is prepared for multiple system development by using the Start Remote
Database (STRRMTDB) command. This command changes the Implementer database files
(PFs and LFs) to DDM files. You can convert all files or functional subsets (for example, only
lock and conflict processing). An example of the command is:
STRRMTDB RMTLOCNAME(remote_location_name)
RMTPRDLIB(remote Implementer library)
MODE(IMPMODD)
LCLLOCNAME(*LOC)
RMTNETID(*LOC)
FILESCVT(*ALL) JOBQ(*PRODUCT)
Specify the location name of the remote system and the name of the Implementer library on
that system. If the mode description, local location name, or remote network ID do not match
the defaults, specify the correct values. Prompt the command to show valid values for these
parameters. The default converts all Implementer files to remote databases. Alternatively,
you can specify *LOCKS and/or *PROJECTS. For further information, see “Performance
Considerations” on page 191.
After you validate the connection to the remote system (for example, remote location name,
mode, local location name, and remote net ID are valid), a batch job submits to the JOBQ
specified to perform the conversion. The Implementer files on the local system should not be
in use when this job runs.
When you no longer need to use this feature, use the End Remote Database (ENDRMTDB)
command to change the DDM files on the secondary system back to physical and logical files.
Once you issue this command, the Implementer database files contain the original
information as before the initial Start Remote Database command was issued.
You must install Implementer on the host system and the Implementer Receiver on each
remote system used for development or that receives changes from the host system.