We use the MKS product because our vendor uses it to deploy application upgrades. In our scenario the libraries are grouped by general system categories, one for source, one for programs, one for custom mods, one for data, one for user files with multiple applications residing in each library. A test environment mimic's the library names with a T appended. When we get a new tape, the delivery gets enrolled and we can deploy it to test, prod, or both. The MKS environments are configured to deploy each application across the libraries then it moves on to the next application.
Kevin Brake, MSSE
IT Application Developer
Information & Technology Services
City of Goodyear - All America City
190 N. Litchfield Rd.
Goodyear, AZ 85338
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Thursday, January 16, 2014 11:44 AM
To: Midrange Systems Technical Discussion
Subject: Re: Implementer question
Vern's correct that this is a question best answered by MKS Support...
And while having no experience myself doesn't make me the best person to throw out an answer, I'll do it anyway. :)
I suspect that Implementer offers functionality similar to Aldon. Given my experience with Aldon, the answer would be it depends.
It depends on what your intent is and how you've configured you CMS to meet that intent.
A simple config would have multiple copies of the source one for each library, assuming the rest of the objects in the library are unique.
Basicaly each library would represent a unique (set of) application(s).
Now, if instead each library represents different versions of the same application, the configuration would be different and you can probably just have one copy of the source.
I onced worked at a place where we installed Aldon. We had two version of the app, call them parent and child. In the child version, it would sometimes use a file in the parent, sometimes it had it's own copy of the file (same format) as the parent, and sometimes it had it's own version (different format) of a file that existed in the parent. After some false starts, we finally came up with configuration that supported that usage.
One key thing I've learned with Aldon is to make sure my "production"
libraries are not defined directly in Aldon. In other words, my production libraries are always deployed to as if they are on a remote machine even though with only a single machine, I could have "promoted" directly into them.
On Thu, Jan 16, 2014 at 11:36 AM, Cyndi Bradberry <CyndiB@xxxxxxxx> wrote:
If you have Implementer, A Question: we have identical files in
several libraries. Currently, we maintain identical DDS in those
libraries to keep all the files in sync. I suggested using one library
for the source instead of maintaining multiple copies.
We have Implementer, but not started using it yet. Is there a way to
do my suggestion with Implementer in the mix ?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l
All messages created in this system belong to the City of Goodyear and should be considered a public record subject to disclosure under Arizona Public Records Law (A.R.S. 39-121). City employees, City public officials, and those who generate E-mail to them, should have no expectation of privacy related to the use of this technology. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.