MKS Implementer 2006 Administration Guide

Distribution Steps
Move Steps
Distribution Steps
Based on the distribution method selected, the steps vary slightly but basically consist of the
following sub-steps:
Save the Implementer work libraries. For tape distribution, the save is to tape. For other
methods, the work libraries are saved to save files.
Send the Implementer work libraries (occurs differently for SNADS and SDMCom).
Receive the Implementer network file (occurs only for SNADS for distribution).
Restore the work files from the save files (occurs for all distribution methods). Once this
sub-step completes the distribution step is complete. The move step is next.
You can initiate the move step from either the host or remote system.
On the host system you can initiate the move step from: the Workbench, Work with Objects,
Move Request menu option, Move Requests by System/Environment, or the Move Request
(IMOVRQS) command. This invokes a communications program on the remote that
performs the promotion on the remote. The promotion steps are the same as on the local
system. When the move step completes, the time and date that the objects were placed into
production is transmitted back to the host to update the Implementer database.
On the remote system you can initiate the move step from the Work with Requests function,
or the Move Remote Request (IMOVRMTRQS) command on the Implementer Receiver menu
or the command line. Many users embed the command in an end of day job on the remote
system.
TIP Issue the IMOVRMTRQS command with the request number value *ALL to
complete the promotion of all requests distributed since the last time the command
was issued.
Multiple System Development
Implementer supports multiple system development, a feature that allows Implementer to
run on multiple systems while sharing the same database.
189