Maxed Out

Because the System i can run at redline speed all day long . . .

November 1, 2007

V6R1 Program Conversion Details Percolating Out

IBM plans to ship its next release of i5/OS -- V6R1 -- in early 2008. With this new release, IBM says it will require the conversion of all programs created under previous releases that use the i5/OS Machine Interface (MI). The conversion will upgrade and refresh programs to take advantage of the latest system enhancements, including upgraded system integrity, improved performance, and a range of new operating system and processor capabilities, IBM says. The company has posted a conversion Q&A site online as well as a new Redpaper Draft titled "i5/OS Program Conversion: Getting ready for i5/OS V6R1."

Basically, even though program conversion is something you've got to pay attention to, IBM is downplaying the scope, saying an "upgrade" or "refresh" is more descriptive of the process. The last time the System i world saw a similar conversion was in 1995 when customers upgraded from 48-bit to 64-bit addresses, though a change also occurred in 1988 in the move from System/38 to AS/400.

"This conversion will be simpler than previous ones. Most other types of objects are not changing this time, for example. Program conversions should also be much faster this time," IBM reports.

Here's a more detailed snip from IBM:

In order for a program to be converted, its creation data (sometimes referred to as observability) must be available. Programs created for V5R1 or later automatically retain creation data sufficient for conversion. Clients and ISVs with programs created for OS/400 V4R5 and earlier need to ensure that creation data is available for the conversion process.

IBM will provide the Analyze Object Conversion (ANZOBJCVN) tool for i5/OS V5R3 and V5R4 to help you plan for program conversion. This tool helps you identify potential conversion difficulties, if any, and estimates the time required for program conversion.

In addition, the transcript to iSociety's "Getting Ready for V6R1" fireside chat with IBM's Paul Godtland, held in September, offers some program conversion nuggets plus some other V6R1 planning concerns.

FYI: I'm working on nailing down an interview with IBM to tease out a bit more detail and perspective on the issue, so if you have any special questions to ask, post them here and I'll add them into my interview notes.

Posted by cmaxcer at November 1, 2007 8:27 AM

Comments

Isnt this a case where only if you have removed observability from a program, it will not convert to v6r1? Back in the day shops did this for various reasons ( reduce object size, security concerns that no longer/probably never applied, handcrafting the MI code of the program ). Nowadays no one in their right mind removes observability from code that runs on their system.

As I understand it, it is system i software vendors that continue to use this technique. Ostensibly to protect their IP, but likely the actual reason is to wring as many upgrade dollars from the end user customer as can be gotten away with. Would be great if IBM engineers could come up with a work around. In this instance customers would pay extra to IBM rather than blackmail to an application vendor.

-Steve

Posted by: Steve Richter at November 1, 2007 10:38 AM

Would like a time frame as when they plan to GA 6.1 instead of the will be release in early 2008.

[Note From Chris: You might be able to get a firmer date -- month -- from an IBM Business Partner/Reseller that you have a relationship with, or possibly from IBM (but IBM itself may not know for sure yet either). In terms of the media, we'll likely get a firm date from IBM a bit in advance, but it'll also come with a legal nondisclosure agreement we'll have to sign, although on occasion IBM does let the cat out of the bag early. Sorry I don't have better details for you, Bill.]

Posted by: bill Swann at November 1, 2007 12:31 PM

Actually the reason programs are shipped with observability stripped is in fact to protect their IP - do you think that it would be wise for a software company to give you observable programs which, for example, take user licenses for their software? They are in business to make money, of course, so don't be daft. Preventing you from getting around your end-user license agreement by hacking their software is the reason the source code is not shipped and the reason the object is stripped of debuggability and observability. Most iSeries vendors will provide recompiled versions of older non-observable programs on their old releases in order to allow customers to upgrade to V6R1, rather than 'force' you to upgrade to a new vendor software release. Will they potentially ask you to pay maintenance fees for obtaining said programs ? - Quite likely. But then, it IS maintenance. And software companies do not exist only for your benefit as a charity - they exist to make money. Having to pay maintence fees to your old software vendors once every 10 years can't be that hard, can it? If you don't like it - invent your own iSeries ERP system, archiving solution, warehousing system etc.! Just be glad this isn't Microsoft or you'd be going through this every other year or so.

Posted by: Joe at November 1, 2007 1:57 PM

Besides having the latest and greatest, what woukd be the upside to installing V6? Haven't heard anything on it besides needing to convert.

Posted by: Frank at November 2, 2007 5:47 AM

"Besides having the latest and greatest, what would be the upside to installing V6?"

Keep in mind that V6 hasn't been formally announced yet, only previewed, so publicly available information is somewhat limited. That said, check out http://www.ibm.com/systems/i/os/i5os/v6r1preview/ and you'll get a pretty good idea of the highlights. Descriptions include enhancements in virtualization, business resilience, security and performance.

Posted by: Kurt at November 2, 2007 12:44 PM

Post a comment




Remember Me?

(you may use HTML tags for style)

Chris Maxcer
August 2008
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

Our blogs are editorial content of System iNetwork. We welcome your comments and opinions and encourage lively debate on the issues, and we reserve the right to edit all postings for clarity, length, civility of tone, and appropriateness to the topic under discussion. Comments consisting of product or job solicitations and other spam, profanity, and extreme rudeness will be deleted. We also reserve the right to publish excerpts from the blogs in our e-mail newsletters and print magazine.

ProVIP Sponsors