RPG Enhancements for i5/OS V6R1 Revealed

October 15, 2007 Dan Burger

Early in 2008, we’ll be seeing another upgrade to the i5/OS operating system, V6R1. IBM previewed some of its features in the upcoming software. Speculation regarding what will be in V6R1 is already at least knee-deep, and you can expect it to get much deeper in the final months of 2007. Those with greatest curiosity are generally the RPG programmers. And for them, IBM has nailed down exactly what a few new features will be.

The source of this information is George Farr, IBM’s worldwide product line manager for WebSphere Development Studio, WebSphere Development Studio Client, and the RPG compilers for the System i. In his keynote address at the RPG & DB2 Summit put on by System i Developer, Farr turned over three of the V6R1 cards that IBM had been holding close to its vest. The RPG-oriented conference was held in Minneapolis, Minnesota, in early October.

Here’s what you can expect to see: local file support for subprocedures, increased size limits for character fields, and multithreading capability when developing programs. If you’re not building applications for the Internet, these enhancements are probably less exciting than your new wringer washing machine or high fidelity phonograph. Those of you who know a thing or two about ILE RPG, Web services, and Internet programming should find this of greater interest.

As more people become familiar with ILE, the support for local files and subprocedures will become a bigger benefit. Subprocedures make RPG code easier to write, easier to maintain, and easier to reuse. Farr told this RPG-savvy crowd that “by defining an F-spec after beginning a subprocedure, that file becomes local to the subprocedure.” That obvious shortcut drew a round of applause. Most RPG programmers who are writing new code use subprocedures to externalize database processing.

Increasing the size limits for character fields will come into play when handling XML documents. I checked in with Paul Tuohy, an RPG expert and one of the session leaders at the RPG & DB2 Summit, to get his read on this benefit. He told me the capability to import XML directly into fields using qualified data structures in an RPG program in one operation was introduced in V5R4, but that most standard-sized XML documents won’t fit in the 64 KB restriction that existed.

“There are quite a few people dealing with 16 MB XML documents,” Tuohy says. “With V6R1, it will be a one-step operation to import a 16 MB document.” As a way of handling the larger and more common document size, Tuohy says people are using third-party solutions to avoid the complexity of coding them directly into applications. After upgrading to V6R1, the third-party solutions won’t be necessary for this task.

The increased size limits are a result of the way people are writing RPG now, he says. “Once people start to dabble in ILE, the mentality becomes more of a PC mentality, which is to load everything into memory, manipulate it, and then write it out again.”

To illustrate this by example, Tuohy compares it to the typical way of writing an order entry application. He describes that as “a records-based procedure with an order header, the order details, the subfiles, and all that process. Doing that now involves defining a user space in QTEMP and having massive data structure arrays, and when the user confirms the order it gets written out to the database. In SOA or Web services, when an XML request come in, the RPG program generates an XML document, which it can do in a 16 MB package and sends it back to the requester.”

The support for multiple threads in V6R1 was noted by Farr as stemming from bottlenecks that sometimes occur in RPG serialized threads. This update positions RPG business logic to be easily called from the Web without risk of corrupting data. In addition, developers retain the option of selecting specific procedures to be serialized.

IBM Previews i5/OS V6R1, Due in 2008

IBM Upgrades High-End System i Server with Power6

Performance of Function Subprocedures

Parameter Passing and Performance

Call RPG Subprocedures from CL

Subprocedures: Better than Subroutines

                     Post this story to del.icio.us
               Post this story to Digg
    Post this story to Slashdot

Tags: Tags: mtfh_rc, Volume 16, Number 40 -- October 15, 2007

Best Practices for Doing IBM i Cloud Backup & DRaaS Right

In the technology business for 30+ years including more than a decade in cloud backup and disaster recovery, we’ve learned a few things along the way. Here are best practices to follow – and land mines to avoid.

RELIABILITY. Up to 71% of restores from tape contain failures.

BEST PRACTICE: Use disk-to-disk technology for backups.

With disk-to-disk technology, your backup data resides on disk drives, proven to be far more reliable than tapes. When your backup completes, you know the data is secure and accessible on the disk drive. With tapes you never really know if your data is usable until you try to restore it, at which point it’s too late.

BREADTH OF OFFERING. Choice in product and service offerings meet your business’ needs.

BEST PRACTICE: Don’t settle for less than what you need.

Vendor offerings vary widely. Some are designed primarily for consumers and others for enterprise data centers. Choose a solution that scales and offers the features you need to provide the level of service you expect. De-duplication and delta-block technologies will improve performance, reduce your data footprint and save you money. Find out if their de-duplication offering is at the file level or the block level. Make sure the solution can back up servers, PCs, and laptops as well your applications.

SECURITY. 60% of organizations using tapes don’t encrypt their backups.

BEST PRACTICE: End-to-end encryption with no “back door.”

Using encryption with tape makes backups run slowly and often takes too long to fit within a backup window. As a result, most people simply turn encryption off, creating a security risk. Even with the physical safety of disk-to-disk backup, encryption is essential. Look for 256-bit AES. Find a solution that encrypts your data during transmission and storage. Make certain there isn’t a “back door” that would let someone else view your data.

ACCESSIBILITY. Companies waste thousands of hours waiting on tapes.

BEST PRACTICE: Ensure that you can get your data back with minimal delay.

You should have direct access to your backups, with no time spent on physical transport (no trucks, no warehouses). Restores should take minutes, not hours or days. Set yourself up to work with your data, not wait for it. Make sure your solution provider can meet your Return-to-Operations (RTO) and Recovery Point Objectives (RPO) which determine how quickly you can recover your data and maintain business continuity. Inquire about onsite and offsite replication that provide both improved performance and a solid disaster recovery strategy.

CYBER SECURITY. More than 80 percent of U.S. companies have been successfully hacked, according to a Duke University/CFO Magazine Global Business Outlook Survey.

BEST PRACTICE: Regular cyber security training and phishing tests for all employees using company email are essential to your organization.

Your end-users are the weak link in your network security. Today, your employees are frequently exposed to advanced phishing attacks. Trend Micro reported that 91% of successful data breaches started with a spear-phishing attack. Be sure your vendor of choice includes cyber security training as part of their backup and DR package.

SCALABILITY. Some backup systems can’t scale readily.

BEST PRACTICE: Invest in a data protection architecture that can grow with your business.

You should be able to back up your data no matter how large it grows. Starting small? Look for an option that handles your backups automatically. Then, as you grow, gives you tools to manage complex environments. Look for “changes-only” and compression technologies to speed backups and save space. And insist on bandwidth throttling to balance traffic and ensure network availability for your other business applications. Make sure that their solution offerings rely on common technology to scale easily as your business––and data––grow.

COST-EFFECTIVENESS

BEST PRACTICE: Calculate the true total cost of tape-based back up.

A 2019 Server OS Reliability Survey found that one hour of downtime costs at least $100K for 98% of companies to over $5 million for 34% of surveyed companies. When you do the math, the dollars make sense: Go with disk-to-disk. Unlike tape, there are close to zero handling costs—no rush deliveries, loading, accessing, locating, or repeated steps. And there’s one benefit you can’t factor directly: Reputation. Reliability and security can make an incalculable difference with just one avoided breach or failure.

COMPLIANCE. Most companies have problems satisfying privacy, security, and data retention regulations.

BEST PRACTICE: Choose a data protection partner who has deep know-how about compliance, and the technology to ensure it.

Disaster Recovery. Most companies lack a comprehensive, tested plan for disasters.

BEST PRACTICE: Find a vendor that delivers a complete DR solution.

You can’t say your data protection is complete until you have a disaster recovery plan that is itself complete and tested. Your backup vendor should have both the product mix and professional services team to help you prepare for a worst-case scenario. Make sure they can help configure your backups so you rebound quickly. Best bet: A vendor who can train you to deal with disasters confidently, based on your company’s actual configuration.

EASE OF USE. Some companies don’t —or can’t—manage their backups from one place.

BEST PRACTICE: Get control and reporting you can use anywhere, with ease. Managing your backup environment should be simple, and the software you use should eliminate any guesswork that could lead to lost data. You should know at all times if your data is protected across your entire network—including remote offices—by simply looking at a dashboard. The software should be simple to configure using wizards, yet powerful enough to meet your specific needs with customizable views, job propagation, and roles-based security.

OPERATING SYSTEM AND PLATFORM SUPPORT. Most backup vendors support a limited range of OS, server types, and applications.

BEST PRACTICE: Look for broad and deep technology that supports your complete environment. Your backup solution should accommodate your environment, not vice versa.

CUSTOMER SUPPORT. Backup vendors’ product support varies widely.

BEST PRACTICE: Find a vendor whose support is passionate, maybe even slightly obsessed. Customer support should be one of your vendor’s main selling points. You shouldn’t have to wonder if they’ll be there to help when you need them most. Do they offer phone support or email only, and who exactly are you talking to when you call that 800 number? Find a vendor that will treat your data as if it were their own.

REPUTATION. Does your backup vendor have a quality reputation and the financial resources to stay in business for the long haul?

BEST PRACTICE: Find a vendor with strong financial backing and customer references. There are a lot of vendors that have come and gone. When you consider a service provider, look for one that has strong financial backing, a solid business plan and the ability to be in business as long as your data needs to be stored. Ask for customer references and case studies as their customers are the best validation you can get.

Visit VAULT400.com/proposal to receive a FREE analysis and proposal

DOWNLOAD SOLUTIONS BRIEF:
Best Practices for IBM i Cloud Backup & Recovery

DURING THIS UNPRECEDENTED TIME, DON’T WAIT FOR YOUR BUSINESS
TO SUFFER A DISASTER TO TAKE ACTION.

Serving the US, Canada, & Latin America

VAULT400 Cloud Backup & DRaaS is an IBM Server Proven Solution.

800.211.8798 | info@ucgtechnologies.com| ucgtechnologies.com/cloud

To the First Responders serving on the front-lines during the COVID-19 pandemic,
we extend our heartfelt gratitude.