On Mon, Nov 17, 2008 at 11:49 AM, Trevor Perry <trevor@xxxxxxxxxx> wrote:
Steve,
When I said "crying does not help", it was not an invitation to cry.
You are making a lot of assumptions, and the one that is the worst is "IBM
does not want to invest in IBM i". Is that a truth, or simply your opinion?
IBM does not disclose what it is investing in, what it is working on.
How many IBMers are working on the RPG compiler? On ILE? On CL?
Integrating of the SQL procedure language into ILE? The trade pubs
don't ask. I try to ask questions about features missing from IBM i
software products on the iSociety chats, but the gatekeeper does not
let them thru.
I base my comment on the lack of investment in IBM i on the paucity of
improvements I see in each release of the OS. Consider that service
programs and procedures are just as difficult for programmers to use
as they were when released 15+ years ago. In a strategic OS that the
owning company has been investing in, there is no need for binding
source or PR copybooks or signature violations. Create the service
program, then add procedures and I guess modules to it. Use the
SRVPGM.WorkWithProcedures command ( notice the command name on a
modern IBM i OS is longer than 10 characters ;) ) to mark the
procedure as exported or not. There are no signature violations
because the OS will find the procedure being called by name instead of
ordinal postion. PR copybooks are not needed because the SRVPGM can
reflect its contents to the compiler.
midrange.com
