MKS Implementer 2006 Administration Guide

Host System Scenarios
changes to the modified member. Review the Merge report and respond to any
messages. Compile the member and perform testing. Ensure the PTF development
library is on the library list for testing.
5 Promote any modified items to testing. Promote any modified items that now contain
the PTF to Mods quality assurance.
6 Promote all PTF items to testing. Promote all items changed from the vendor PTF
development environment to the vendor quality assurance environment.
7 Promote modified items to modified custom Mods production. After testing, promote
any modified items from Mods quality assurance to custom Mods production.
8 Promote PTF objects to base application. After testing, promote all vendor objects from
vendor testing to the vendor base production.
Apply the New Release From the Vendor
These tasks require the use of NewVersion, a separately-licensed MKS product.
1 Load the new release from the application vendor. Use the instructions supplied by the
application software vendor. The vendor should supply instructions to install the
changes into test libraries, rather than directly into your custom Mods production
version of that software. The directions from the vendor may be as simple as telling you
which libraries to restore from tape, using the Restore Object (RSTOBJ) or Restore
Library (RSTLIB) command. The vendor may provide installation utilities that you must
run as described by the vendor.
2 Analyze the new release libraries. Complete this step using the NewVersion functions
“Define Target Libraries” and “Build Target Object Entries” to analyze the libraries. Use
the “Print Action Messages” function to print a list of action or exception messages to
review or resolve. Use the “Print Object Report” function to determine which objects
require merging.
3 Check out the objects that NewVersion has determined require merging. This checks out
from the custom modifications production environment (with an automatic copy from
the vendor base production, if needed) to a development environment. At this point, you
might encounter members/objects that are already checked out. If you have some of
these members/objects checked out already, check them out to a different development
environment or library. Implementer considers this concurrent development.
Concurrent development requires you to resolve conflicts before or during creation of
the promotion request. The library you check out to must be the same library as the
target library defined to NewVersion.
The check out being performed is simply securing a lock on each of the members/
objects. The source that is copied as part of this check out is replaced with the source
merged in the next step.
35