Nothing fancy. Most stored procedures are external RPG code doing native IO and returning a single result set

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Wednesday, April 27, 2011 2:32 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Moving from V5R4 to V7R1

If you're doing anything fancy with stored procedures, pay close attention to the part about the SQL0338 error messages.

I have a customer whose programmer thought he'd try to save some time by not using brackets everywhere they were supposed to be used. This brought down an entire mission critical application.

This was discovered on a Friday morning. The poor kid had to miss his flight to Bombay, scheduled for Saturday morning.

Paul Nelson
Office 512-392-2577
Cell 708-670-6978

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Wednesday, April 27, 2011 1:12 PM
To: Midrange Systems Technical Discussion
Subject: Moving from V5R4 to V7R1

Are there any "must read" documents for moving from V5R4 to V7R1? I found the V6R1 memo to users and the V7R1 memo to users. Also have the Getting Ready for 6.1 and beyond manual. And the 7.1 Technical Overview. Is anyone aware of a document/memo specific to skipping V6R1?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by 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].