|
And one software developer asked at his conference if the users would have a problem if they stopped supporting releases earlier than XYZ. The users cheered and applauded. Now they had justification to management to upgrade their 400's. Surprised the developer to no end. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Bob Cozzi \(RPGIV\)" To: <RPGIV@yahoogroups.com> <cozzi@rpgiv.com> cc: <rpg400-l@midrange.com> Sent by: Fax to: rpg400-l-admin@mi Subject: RE: [RPGIV] Survey question - reality check drange.com 02/19/2002 12:04 PM Please respond to rpg400-l Reeve, Today, virtually ALL OS/400 shops are being told to use the new features of the compiler. Yet they are "stuck" on V4R5 and earlier releases. Therefore, virtually all software vendors need to code for the lowest common denominator. They avoid using the new features, therefore perpetuating the problem of end-users not moving to new releases. I've been in software house that have 3 or 4 AS/400 systems sitting there for backward compatibility. And as we all know, the way the software houses go, so goes end-user development. Bob Cozzi cozzi@rpgiv.com Visit the on-line Midrange Developer forum at: http://www.rpgiv.com > -----Original Message----- > From: Reeve Fritchman [mailto:reeve@ltl400.com] > Sent: Tuesday, February 19, 2002 10:49 AM > To: RPGIV@yahoogroups.com > Subject: [RPGIV] Survey question - reality check > > Bob, this is a provocative question. But I have my own: what's in this for > IBM? > > Selling new features is a continuing source of revenue for software vendors. > Who knows how many OS/400 upgrades have been triggered by the DP manager's > desire to get his/her hands on some new utility or free-form RPG? > > I'm not an internals guy, so I don't know what percentage of RPG functions > are tied to OS and/or TIMI functions; I'd suspect not much. This may be a > practical consideration. > > Would I like this requirement? Absolutely. Would this policy promote > iSeries and RPG development? Yes. Do I think it would slow RPG > development? Yes. Do I think it's likely to happen? No. > > The RPG/languages gang in Toronto isn't part of the Mid-Market Server Group; > this is mainly a dollars-and-cents question. > > Regards, > Reeve > > -----Original Message----- > From: Bob Cozzi (RPGIV) [mailto:cozzi@rpgiv.com] > Sent: Tuesday, February 19, 2002 10:29 AM > To: rpgiv@yahoogroups.com; rpg400-l@midrange.com > Subject: [RPGIV] question on survey question > > In next week's Midrange Developer, my 10-second survey is going to be > something like this: > > Should IBM be required to base all future versions of the compilers on > V5R1, thus allowing future code to be compiled as TGTRLS(*V5R1M0)? > > > My question to you all is this: > Is this a viable question, and is it clear enough? > > My thinking is that this will change the way IBM does things, so that if > they add a built-in function in V5R2, you and I who are still on V5R1 > can use that built-in function for our V5R1 applications. > > Today, if you want to compile to *PRV you have to have actually > installed the V4R5 compiler on your V5R1 machine. I'd like to see IBM > move away from that model, and instead, create enhancements to the > existing compiler but require that enhanced compiler to run on the base > Version release. Meaning for the entire life of V5 the V5R1 compiler > would both compile and be able to target V5R1. Even if there were a V5R7 > the identical "binaries" would be installed on V5R7 and V5R1 and > everything in between. > > So basically this means that the compile would allow you to produce code > that runs on V5R7 or V5R1 and the only time a source member would not > compile is if there were an operating system-dependant feature used in > your code. Such as a new data type that may be in the database and in > RPG but not back-release compatible. Otherwise, if they add a new opcode > or a new built-in function it would work on V5R1 and later. > > Comments > > > Bob > > > > http://www.rpgiv.com/forum -- For free support on any questions about AS/400 > and iSeries programming. > http://www.rpgiv.com/seminars -- For on-site education offerings on RPG IV > or CGI Web Applications with RPG IV. > ---------------------------------------------------- > To unsubscribe from this list send an email to: > mailto:rpgiv-unsubscribe@yahoogroups.com > ---------------------------------------------------- > > > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ > > > > ------------------------ Yahoo! Groups Sponsor ---------------------~--> > Sponsored by VeriSign - The Value of Trust > Do you need to encrypt all your online transactions? Find > the perfect solution in this FREE Guide from VeriSign. > http://us.click.yahoo.com/vCuuSA/UdiDAA/yigFAA/saFolB/TM > ---------------------------------------------------------------------~-> > > http://www.rpgiv.com/forum -- For free support on any questions about AS/400 > and iSeries programming. > http://www.rpgiv.com/seminars -- For on-site education offerings on RPG IV or > CGI Web Applications with RPG IV. > ---------------------------------------------------- > To unsubscribe from this list send an email to: > mailto:rpgiv-unsubscribe@yahoogroups.com > ---------------------------------------------------- > > > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ > _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.