|
Thanks Joel - I don't think they intentionally delete the source: they just remove their personal library and everything in it...not realizing they have production objects operating from their personalized source files. Where I do get bent is them not copying the tested object into the live source file for re-compilation into production. SO MANY people, who have been around for SO MANY years, totally blind to the importance of change management...this particular problem is just a very good example of that.
From: Joel Fritz <JFritz@sharperimage.com> Reply-To: midrange-l@midrange.com To: "'midrange-l@midrange.com'" <midrange-l@midrange.com> Subject: RE: RPG III - Object to Source DE-Compiler Date: Wed, 2 Oct 2002 16:51:10 -0700 For relatively short programs if they're compiled with debug information, STRISDB is the cheapest alternative. You can cut and paste screen by screen. Nice folks that delete the source when they leave. > -----Original Message----- > From: Rick Rayburn [mailto:the400man@hotmail.com] > Sent: Wednesday, October 02, 2002 4:51 PM > To: midrange-l@midrange.com > Subject: RPG III - Object to Source DE-Compiler > > > Hello there everybody - > > Well, we have some old RPG III programs, left behind by those "dearly > departed" craftsman from yesteryear, that are still in > production...but have > no source to be found anywhere to support them (you > know...P/A's create > QRPGSRC in library JOELIB...compile from there into > production...then take > it with them when they are replaced). > > Hence...reverse object to source DE-compilers. I think there > are some out > there...can anybody offer some experience with this topic? > Recommendations? > Quality? You know. > > Thanks much people. > > Rick Rayburn > > > _________________________________________________________________ > Join the world's largest e-mail service with MSN Hotmail. > http://www.hotmail.com > > _______________________________________________ > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > NOTICE: All e-mail sent to or from this e-mail address will be received or otherwise recorded by The Sharper Image corporate e-mail system and is subject to archival, monitoring, review by and/or disclosure to Sharper Image security and other management. This message is intended only for the use of the addressee and may contain information that is privileged and confidential. The contents of this message may contain personal views which are not the views of The Sharper Image. If you are not the intended recipient, dissemination of this communication is prohibited. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
_________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com
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.