Product Lines

Ruminations on the System i Market

July 8, 2008

The New, the Old, and the Beachhead: A Conversation with ASNA's Eduardo Ross

Modernization is on the minds of System i masters even as mature applications keep moving the platform along. What exactly are ASNA's clients and System i prospects looking for? "It’s hard to sell the old applications to new customers," points out Eduardo Ross, president of ASNA. The System i applications of yesterday may not seem as user friendly as the Windows applications of today, and new customers may want an application that will work with systems other than the i. Thus, vendors often look toward long-term strategies such as extending the System i platform to .NET. "Vendors are in a bind, though, as they seek avenues to extend the market while keeping up support for existing customers," Ross adds. In the case of his company, ASNA has been selling software for 25 years. "Now we’re providing more services in addition to offering products. IT is into the fiber of all businesses -- virtually no business today operates without the help of IT."

Customers express concerns, Ross says, about how to expand the resources on the System i platform. "Screen scraping and superficial interfacing with other systems can only go so far," he notes. "Customers come to us asking how they can extend the applications beyond simple cosmetic makeovers." Ross says improvements have to happen while the past is still alive. "Major surgery on legacy applications is complex and requires planning, energy, and a broad skill set," he points out. "But without this surgery, the patient dies."

Citing the example of a payroll system, he notes that today’s businesses need far more than the recording of basic payroll information. "Shops are looking for agility beyond the back-office environment of the past," Ross explains. "They need features such as interoperability with business partners via web services, web-based queries, and the ability to provide an intuitive user interface. You can only do so much with the intrinsic System i RPG platform. But, using this core platform as a beachhead, you can extend portions to the .NET platform to provide many application modernization opportunities. In reality, a lot of applications written in RPG still represent the core of the new environment."

Meanwhile, application software vendors such as ASNA find it hard to see an extending System i market. “It’s a pity because the platform, at its core, is so good,” Ross adds.



Posted by vhamende at July 8, 2008 2:09 PM

Comments

The first thing we need to do to OS/400 (i5/OS, i) or whatever you want to call it is go back to the base of our databases and fix our physical and logicals so other applications can work with them. For example, we have a much ignored DSPDBR command that IBM provided us with and we seem to have forgot how to use it. I don't know how many shops I go into that have 150 to 200 logicals over a physical file (tables) and only 10 logicals (views)are being used and they are having performance to other interfaces.

We need to perform analysis and then carefully delete the logicals that are not being used so information can be uploaded to the physical file to be shared, used, altered or maintained by these new interfaces we build to different systems. Its not that the information will not update/modify etc..., its just that it's so slow when we have so many unused relationships (keys) attached. Physical Files by nature are huge of the i systems. 10, 15 to 25 gig single physicals are not unheard of. Then we put on 200 logicals which are keyed but not being used and the performance trouble starts, not to mention the disk space that is consumed by these none used logical files because of the key(s). Remember we are working with a system that has adapted through a number of programmer skillsets and the CPY* command in itself takes years to understand. We threw so many types and generations of programmers and Business enhancements at that box in the last 29 years, it's no wonder the databases need to be refreshed to work with new applications.

In my opinion IBM created this monster years ago when they said and say you don't need a DBA on this BOX. The companies that see value in staffing at least 1 senior person skilled in systems programming, security, Disaster Recovery, Hardware/Software, Network and DBA administrator working on the iSeries are very unfortuate and smart companies.

Posted by: Raymond Rhyno at July 9, 2008 9:48 PM

I think you meant to say in the last sentence:

The companies that see value in staffing at least 1 senior person skilled in systems programming, security, Disaster Recovery, Hardware/Software, Network and DBA administrator working on the iSeries are very -fortunate- and smart companies.

Posted by: D B at July 14, 2008 11:27 AM

Hi DB,

Thanks for picking that up. Actually fortunate or unfortunate depends on which side we are on but absolutely I made a mistake. I am on the OS/400 side and did mean fortunate.

Posted by: Raymond Rhyno at July 18, 2008 5:11 PM

Post a comment




Remember Me?

(you may use HTML tags for style)

Acceptable Use Policy

Blog Feed

January 2009
Sun Mon Tue Wed Thu Fri Sat
        1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31

Blog Policy

We welcome your comments and opinions and encourage lively debate on the issues. However, Penton Media reserves the right to delete or move any content that it may determine, in its sole discretion, violates or may violate its Terms of Use or is otherwise unacceptable. For more information, see Penton Media's Terms of Use.

ProVIP Sponsors