|
For example, I had to give up on ORD500. Every other line of code seemed to refer to a literal, which had to be looked up some place else (the technique was used to support non-English content). The whole program was approx 1/3 million source code lines, and called 10 other programs almost as large ... what is it like now?
Another example was in the rounding ... there was a systemic problem with fields of size 15.9 xxx,xxx.xxxxxxxxx in math against each other with no space to handle the "carry" digits, which had the result of sometimes getting what IBM called unpredictable results like
zero times positive one = negative 999,999.99999998 I found this in the Costing and Accounting Has that been fixed?
That is correct, but in the switch-over, what we get is AS/SET generated RPG. SSA claims to have removed over 10 million lines of code by cleaning up the AS/SET generator (I figure their developers were looking for the bus too!). Jim - Can you notice that the code is any cleaner? Debbie Ivey -----Original Message----- From: Kobie Jooste Subject: RE: [BPCS-L] ERP LX I thought SSA categorically stated that from 8.3 ERP LX no AS/Set will be used, only RPG? Doug, where's that bus? Kobie Jooste Tel: +2711 758 5387 / Mobile: +2783 798 3155 / Fax: +2711 758 5301 -----Original Message----- From: Doug_McLauchlan@xxxxxxxxxx Is it just me, or are there other developers out there who feel it will be preferable to walk in front of a bus rather that face a world where we have to modify AS/SET generated RPG ??!! I still remember V4 ! Doug McLauchlan BPCS Support Planar Systems, Inc. Office: (503) 748-5988 Cell: (503) 706-7525 "Jim Mergen" So far, the LX portion seems pretty stable. We encountered a couple issues during implementation, but I believe if you are upgrading to the LX portion only, shouldnt have too many problems. One issue is the use of ASSET. 8.3(base) was generated using ASSET, but all mods done afterward were done to the ASSET-Generated RPG. If you chose to continue using ASSET, you are kinda on your own in that SSA modifies the RPG code, and not ASSET, so you wont be at the same source level. TO stay current you are forced to make in-house mods to the RPG source. Because of the size of ASSET-generated RPG code, some programs cannot be modified using the standard SEU because the source members are too large. We have chosen to interface 8.3 LX with the new FM module. The FM module is actually Masterpiece(SSA bought Computer Associates). We did encounter some problems initially interfacing with FM due to a learning curve. SSA consultants, while having knowledge of LX, didnt have experience with FM. On the FM side, those consultants, having come from C/A, didnt have experience with LX....so there was a learning curve for all, consultants as well. Hope this helps. Let me know if you have any other questions. Jim -----Original Message----- From: Norman.Boyd@xxxxxxxxxxxxxxxxx Jim, While we are looking at the possibility of upgrading to the latest version of BPCS we don't exactly want to be on the cutting edge. Usually those on the cutting edge get burned a little. I'm simply looking for some input on the overall stability of the application at large and the ease of implementation. We are currently at version 6.00.04. Thank you Norman K. Boyd MIS Administrator Showa Aluminum Corp. of America
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
