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.

Charles


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 ?

Cyndi B.
Boise, ID
--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.