Re: new os -- BPCS-L

This is correct the offsets changed in V5R1. If you are coming from V4RX
and going to V5R2, you will need to address any trigger programs that you
may be running.

Thanks,
Glen Langston

(843) 664-4263          
glangston@xxxxxxxx




"Clare Holtham" <Clare.Holtham@xxxxxxxxxxxxxx>
Sent by: bpcs-l-bounces@xxxxxxxxxxxx
04/14/2004 09:47 AM
Please respond to "SSA's BPCS ERP System"

 
        To:     "SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>
        cc: 
        Subject:        Re: new os


Hi James,

I believe the changes came in at V5R1 - can anyone confirm that?

Clare

----- Original Message ----- 
From: "Reinardy, James" <jreinardy@xxxxxxxxxxxxxxx>
To: "SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>
Sent: Wednesday, April 14, 2004 2:17 PM
Subject: RE: new os


> Clare,
> 
> Would you please clarify your statement about trigger programs?  We have
> introduced these to our environment since going on V5R1.  Do we need to
> rewrite them for V5R2, or does this apply only when going from V4?
> Thanks!
> 
> James Reinardy
> Director-Information Systems
> Badger Meter, Inc.
> Milwaukee, WI 53223
> 
> 
> -----Original Message-----
> From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx]
> On Behalf Of Clare Holtham
> Sent: Wednesday, April 14, 2004 2:33 AM
> To: SSA's BPCS ERP System
> Subject: Re: new os
> 
> Mitch,
> 
> If you are going from V4 you need to change QAQQINI as per the IBM
> instructions otherwise some SQL statements in BPCS may fall over, also
> you should allow extra time for the upgrade, and run a RCLSTG and a
> STROBJCVN across all objects, otherwise the system will convert
> dynamically and this could cause locking in BPCS. If you are going from
> V5R1 then you've already done this! And if you have any trigger programs
> they may need rewriting.
> Make sure you get all the PTFs first, especially the Database Group.
> Good luck,
> 
> cheers,
> 
> Clare
> 
> ----- Original Message -----
> From: "Damon, Mitch" <MDamon@xxxxxxxxxxxxxxxxx>
> To: "AAA-BPCS users listserve" <BPCS-L@xxxxxxxxxxxx>
> Sent: Tuesday, April 13, 2004 7:22 PM
> Subject: new os
> 
> 
> We are going to OS V5R2 using a highly modified BPCS 6.0.04.  Has anyone
> ever done this and are there any gotcha?
> 
> Mitch Damon, CPIM
> Planning Systems Manager
> Birds Eye Foods
> Rochester, NY
> (585) 383-1070 x 250
> 
> _______________________________________________
> This is the SSA's BPCS ERP System (BPCS-L) mailing list To post a
> message email: BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change
> list options,
> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives at
> http://archive.midrange.com/bpcs-l.
> 
> 
> _______________________________________________
> This is the SSA's BPCS ERP System (BPCS-L) mailing list To post a
> message email: BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change
> list options,
> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives at
> http://archive.midrange.com/bpcs-l.
> 
> 
> 
> _______________________________________________
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.

_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.




--------------------------------------------------------------------------------------------------------------------
This communication and any files transmitted with it contain information which 
is confidential and which may also be privileged. It is for the exclusive use 
of the intended recipient(s). If you are not the intended recipient(s), please 
note that any disclosure, copying, printing or use whatsoever of this 
communication or the information contained in it is strictly prohibited. If you 
have received this communication in error, please notify the author and then 
delete the e-mail together with any copies of it.

Information or opinions in this message that do not relate to the business of 
ESAB shall be treated as neither given nor endorsed by it.  ESAB does not 
accept liability for any changes which may occur in transmission due to 
network, machine or software failure or manufacture or operator error. Although 
this communication and any file(s) transmitted with it are believed to be free 
of any virus or any other defect which might affect any computer or IT system 
into which they are received and opened, it is the responsibility of the 
recipient to ensure that they are virus free and no responsibility will be 
accepted by ESAB for any loss or damage arising in any way from receipt or use 
thereof.