|
At first what you were saying is that some people can't afford a new package, budget-wise, so instead they use all custom software. Interesting. What I now want to discuss is: What defines an OS, in your case, as still supported? The following? http://www-912.ibm.com/supporthome.nsf/document/29853352 Which means you support only V5R1 and V5R2, which I suppose isn't too bad. Although some of those datastructure options... Whatever you are allowed to use as the minimum for TGTRLS? Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Buck" <buck.calabro@xxxxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 11/24/2003 12:23 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To rpg400-l@xxxxxxxxxxxx cc Fax to Subject Re: RPG IV release levels and complexity > But the standard question, is how many people > are buying new packages for their iSeries when > their version of release is two versions back? The standard question tends to ignore the fact that it is much easier for a data centre to put a 4,000 dollar a month software maintenance budget item in than it is to put the price for a new package plus installation plus training plus conversion... Having said that, the standard reply is 'not many.' But they ARE paying us support and maintenance fees for their existing software. And when Federal regulations mean a change in the code base, we have to make those changes in such a way that our customers on older (and still supported) OS releases can use the 'new' code. So we code for the least common denominator, and warn customers in advance that when their OS release becomes unsupported, they will pay a LOT of money for us to support their now custom code base. Whilst the pace of change has certainly quickened, the vast majority of RPG programmers work on a single iSeries, at a single OS release, and don't have a problem trying to keep things straight. The biggest issue for them is not being able to use code they find online and in articles and books. Which really becomes an issue for those of us posting that code. I suggest putting the version the code was tested against in the comments at the top of the code. Would I like to be able to send my object code back to an earlier release level (without needing TGTRLS())? You bet! That would be the best! But I think I understand the situation. Because RPG uses lots of system hooks, going back a version of OS400 is more like trying to move a Win32 program back to Win16 or even back to DOS. The OS400 changes are apparently that significant, despite the VRMxvz numbering scheme. So for now, it will remain least common denominator for me. --buck _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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 copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.