RE: V5R2

This seems to be a standard CYA but the solution (for those that have 
source) should be to scan your source for SQL statements and ensure they 
conform to V5R2.  Easy for me to say - we upgraded to SP4 earlier this 
year.

Richard




"Prill, Steve" <sprill@xxxxxxxxxxxxx>
Sent by: system21-bounces@xxxxxxxxxxxx
09/23/2003 10:05 AM
Please respond to System 21 Users

 
        To:     System 21 Users <system21@xxxxxxxxxxxx>
        cc: 
        Subject:        RE: [SYSTEM21]   V5R2



Below is the response that I received from Answerlink regarding upgrading 
to
OS400 V5R2 with a System 21 version prior to SP4.  She is basically 
stating
not to upgrade to V5R2 if you are not at SP4.

I don't understand why Geac can't provide a list of the programs that need
to be changed and exactly what needs to be modified.  Does this seem to be
an unreasonable request?

Steve
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Geac response via Ansewerlink:

Customers who are below Service Pack 4 of the System21 software are having
issues going to V5R2 however because this OS release is more restrictive
with the SQL statements. The embedded SQL statements within System21
programs have been reworked and are fine if you are at Service Pack 4.

For example, some of our older version programs would open a CURSOR for
update but not be specific to add the command FOR UPDATE OF. In V5R2 it 
must
be specific. Since Service Pack 3 and 4, most of all of the programs with
embedded SQL statements have been corrected to accommodate this.

At Service Pack 3 you will have a few areas that could cause a problem. If
you do encounter a program that is opening a cursor for update without the
FOR UPDATE OF, you could conceivably run into issues where the files do 
not
get updated. This will definitely compromise your database and I cannot in
good conscience recommend it.

For these reasons, we are recommending that any customer upgrading to V5R2
be at Service Pack 4. As I have answered your question, I will go ahead 
and
close this case at this time.

Regards,

Teri Willoughby/Geac S21 Support

-----Original Message-----
From: Grinstead, Scott [mailto:SAGrinstead@xxxxxxxxxxxxxx] 
Sent: Tuesday, September 23, 2003 10:33 AM
To: 'System 21 Users'
Subject: RE: [SYSTEM21] V5R2

A word of warning.  Search all source members (even the ones that have a
type of RPG and not SQLRPG).  When Rocky upgraded our processor we ran 
into
a couple of source files that were RPG when in fact they had SQL code.

Scott Grinstead
Sr. Programmer/Analyst
Rocky Shoes & Boots

 -----Original Message-----
From:            Dan Thomas [mailto:dthomas@xxxxxxxxxxx] 
Sent:            Tuesday, September 23, 2003 10:20 AM
To:              'System 21 Users'
Subject:                 RE: [SYSTEM21]   V5R2

We are on v3.5.0 (heavily modified) and are going through a migration from 
a
620 v4r5 to an 810 v5r2.  We are in test mode at this time.  So far
everything is working fine (and very fast).  My understanding of the SQL
problem is that it will make affected programs run slower, but they will
still run.  I am not an RPG techie, but I believe programs with embedded 
SQL
code are identified as SQLRPG instead of just RPG.  Shouldn't be that hard
to find affected programs and make the change...assuming of course you 
have
source code.  A consulting firm quoted us two weeks to handle this for us,
and we may still use them, but two weeks did seem high to me.

We'll share with the group what we find and hope everyone else will do 
that
same.

Dan Thomas
Director of Information Technology
MDI
4500 Progress Blvd
Louisville, KY  40218
(502) 318-1208

This message is a privileged and confidential communication protected by 
the
Electronic Communications Act and is intended for the designated 
recipients
only.  Duplication or distribution of this email beyond the intended
recipients without prior written consent of the sender is strictly
prohibited.


-----Original Message-----
From: Prill, Steve [mailto:sprill@xxxxxxxxxxxxx]
Sent: Tuesday, September 23, 2003 8:43 AM
To: System 21 Users
Subject: FW: [SYSTEM21] V5R2


Kevin,

I don't believe anyone provided any details on what exactly needed to be
changed if someone wants to move to OS400 V5R2 from a system 21 version
prior to SP4.

Ram and I are both interested in getting this information.  I submitted 
this
to Answerlink yesterday and if I get any details I will provide it to this
group.

Below is the response from Teri Willoughby.

Steve


-----Original Message-----
From: Eva SooHoo [mailto:EvaS@xxxxxxxxxxxxx] 
Sent: Wednesday, August 27, 2003 11:59 AM
To: 'System 21 Users'
Subject: RE: [SYSTEM21] V5R2


This is the answer supplied to me by Teri Willoughby. (via my support
liaison)

 
The customer must be at v3.5.2 SP4 before moving to V5R2.  There are 
issues
with some SQL statements prior to SP4.  When an SQL cursor is open for
update, some of the previous versions of programs have left off the "FOR
UPDATE OF".  This causes problems with V5R2 as IBM is more stringent with
SQL now.

-----Original Message-----
From: Glenn Schreiner [mailto:Gschrein@xxxxxxxx]
Sent: Tuesday, August 26, 2003 7:56 AM
To: 'system21@xxxxxxxxxxxx'
Subject: [SYSTEM21] V5R2

We are currently running System 21 version 3.5.0 on V5R1, but will be
upgrading to V5R2 very soon.  Is anyone currently running System 21 
version
3.5.0 on V5R2?  If so, did you have any problems when you upgraded to 
V5R2?

Thanks for the help.

Glenn R. Schreiner
Hach Company
Sr. Programmer Analyst
Email:  gschrein@xxxxxxxx
Phone: (970) 663-1377, ext. 2509
Fax: (970) 669-2932

_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.
_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.
_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.
_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.
_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.
_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.