MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2014

RE: Change Management for small shops



fixed

I don't know about the others, but Aldon uses the object control level to
maintain the link between the development log and the object itself. It can
be seen when using the *SERVIVE parameter of DSPOBJD. The IBM compiler
doesn't maintain that field, so Aldon stamps it with the last create info
from it's development log.

The verify reports make those discrepancies stick out like a sore thumb.

Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike
Cunningham
Sent: Wednesday, July 23, 2014 3:56 PM
To: Midrange Systems Technical Discussion
Subject: RE: Change Management for small shops

DSPOBJ on the application. Get username and date for who compiled the object
and the source it was compiled from. Go to our checkout log for the source
code. Show the request from the user associated with the source checkout and
who checked it out.

What we would fail on is proving that programmer X does not have authority
to production objects. They do. What we can show is that we log every change
to every object

If one did have a purchased package are you required to answer the question
"Prove to me your purchased package process actually does what it says it
does." You, as the one being audited, have no way to answer than without
access to source code. Although you can say here is the audited statement
from the vendors auditors saying it is.

SOX is not something we have to audited on.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Monnier, Gary
Sent: Wednesday, July 23, 2014 4:44 PM
To: Midrange Systems Technical Discussion
Subject: RE: Change Management for small shops

The cost will depend on how you answer the auditor's "Prove to me"
questions.

Questions like "Prove to me this production object has not been altered
outside approved channels.", "Prove to me your home-grown process actually
does what you say it does." And "Prove to me your procedures satisfy SOX
compliance."


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike
Cunningham
Sent: Wednesday, July 23, 2014 1:34 PM
To: Midrange Systems Technical Discussion
Subject: RE: Change Management for small shops

Without revealing any vendor secrets, what does a change management with
deployment cost ? upfront and yearly. We only have 6 developers who all sit
within 20 feet of each other and talk daily and they manager is also in the
same space so never really found the cost to be justified and our auditors
have been OK with it in the past. But auditors have different opinions
sometimes and we just got someone new for the financial audit.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Thomas Garvey
Sent: Wednesday, July 23, 2014 2:46 PM
To: Midrange Systems Technical Discussion
Subject: Re: Change Management for small shops

TD/OMS (formerly known as Tight As a Drum) handles all of that: source and
object control, IFS documents (everything), complete life cycle management,
and excels at roll-outs and roll-backs to multiple targets.





Thomas Garvey
<http://www.unpath.com/>




On 7/23/2014 1:09 PM, rob@xxxxxxxxx wrote:
And a good change management product will tell you when you try to
roll out a printer file from development to production if someone
changed any attributes on the production, like changing default
printer, overflow line, etc. Stuff that you don't even need to recompile
for.


Rob Berendt

--
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.

--
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.

--
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.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact