|
midrange.com
We would (hopefully) never modify a base GEAC file either, however it would be
nice to have the cross referencing for research. For example, where and how
often a field is being updated before making an external modification that
updates it. Without it the only way to know is to scan all of the source
members, which takes time and isn't reliable.
Stefan is correct that this probably falls outside the scope of change
management. Using Hawkeye & Turnover so often in conjunction in the past I
thought of them as a single entity.
-----Original Message-----
From: GEAC/JBA System 21 Users <jbausers-l@midrange.com>
Sent: Wednesday, January 15, 2003 11:09 AM
To: GEAC/JBA System 21 Users <jbausers-l@midrange.com>
Subject: RE: [SYS21] Change Management
A cross reference would only be needed if you were planning to change base
System 21 application files. We have Aldon and yes they only index what we
have modified. As a standard practice we do not modify base application
data files.
Dave Barry
<richard.evans@del
taapparel.com> To:
<jbausers-l@midrange.com>
Location of cc:
Author: Subject: RE: [SYS21] Change
Management
Sent by:
jbausers-l-bounces
@midrange.com
01/15/03 10:30 AM
Please respond to
GEAC/JBA System 21
Users
You are correct -- however the cross referencing does tie into source
control.
As I recall Softlanding Turnover would look and automatically check out
appropriate program objects whenever a file was checked out, but this may
have
been an interface to Hawkeye. It has been too long since I've used change
management!
-----Original Message-----
From: GEAC/JBA System 21 Users <jbausers-l@midrange.com>
Sent: Wednesday, January 15, 2003 8:59 AM
To: "GEAC/JBA System 21 Users" <jbausers-l@midrange.com>
Subject: RE: [SYS21] Change Management
You're talking about apples and oranges here, Richard, but I think it's a
worthwhile discussion.
Change management helps ease the pain of migrating custom (bespoke) objects
from
environment to environment (dev to QA to live, for instance). It also
helps
manage multiple development requirements for one program, by allowing you
to
merge two sets of mods together. The leading products in this area are
from
Aldon, Silvon, and SoftLandings.
The file/field/program relationships you're talking about are documented by
a
Cross Reference utility, offered by Hawkeye and ASC, among others.
I've participated in using both Aldon, Silvon, and Hawkeye products at JBA
installations. There are several ways to work around the library
situation.
You can either specify a replacement library list, for the utility to look
through when it can't find OSLINX3, or you can just recompile your entire
system, which is a bit scary but a good exercise if you have the time.
Richard, feel free to contact me off line if you would like more
information
about what it takes to do this.
Stefan Jansson
stefan.jansson@eljer.com
Eljer (not a S/21 customer)
P.S. You're right that it would be nice for JBA/Geac to offer or have
offered
assistance in this area. As a matter of fact, I pushed for that when I was
with
The Firm, but to deaf ears. I guess they feel like their technical
documentation is sufficient.
-----Original Message-----
From: richard.evans@deltaapparel.com
[mailto:richard.evans@deltaapparel.com]
Sent: Wednesday, January 15, 2003 8:36 AM
To: jbausers-l@midrange.com
Subject: [SYS21] Change Management
Has anyone with source successfully configured a change management system
to
index all of the file/field/program relationships in GEAC? Given the
number of
libraries, and that PTFs are compiled from non-existent ones (although
source
is hopefully moved to the appropriate location) , I would think the initial
mapping would be a nightmare if not impossible. However, if successful,
time
saved on research might make up for it.
I searched the archives prior to posting and did find one company (Fossil)
using
Aldon but, as I interpreted it, they were only indexing modified objects.
Another company (Sara Lee) was beginning the mapping process last May.
If successful I'd like to know the package, how difficult the
configuration
was, and whether the vendor assisted with the mapping (wouldn't it be nice
if a
vendor offered a GEAC template?)
Thanks,
Richard
Richard.Evans@DeltaApparel.com
_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.
_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.
<< File: RFC822.TXT >>
_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.
_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.
<< File: RFC822.TXT >>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
