Re: BPCS V405CD and OS V6R1

Hi Rob,

Thanks for the information.  The results of the ANZOBJCVN report revealed some
issues, but most are with the BPCS security programs and Infor is providing
replacements for them that will convert.  Our main concern is with the BPCS
menus and the security logic that is used in the menu CL's.
* Did you have issues with the BPCS menus?
* Were you able to obtain source code for the menu CL programs?
* OR, did you have to convert everything to the user-defind menuing system as
Darryl Freinkel suggested in his reply?
The client does currently have source code for all BPCS menus so I am not quite
sure why Infor said that they do not want to provide it for the OS V6R1 upgrade
unless the issue is that the new security system and licensing is embedded in
the menu CL's and therefore Infor will not provide source code.

Thanks for your insights.

Les Mittman
847-858-5235
BPCS Consultant with over 20 years experience.

 

________________________________
From: "rob@xxxxxxxxx" <rob@xxxxxxxxx>
To: BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
Sent: Fri, April 15, 2011 6:31:14 AM
Subject: Re: [BPCS-L] BPCS V405CD and OS V6R1

We originally upgraded from V5R4 to 6.1 with 405CD.  We led the pack and
went through the pain.  We had a lot of modifications.  However, we didn't
customize anything we weren't supposed to.  Be careful of BMRs.  They
probably have it ironed out now but early on in the process, even though
their site states they are not supported releases of the OS older than "x"
the machine they were compiling their bmr's on was older than 'x' and I
was getting BRMs that wouldn't work on that release.

We eventually ran fat, dumb and happy on 405CD on 6.1 and then 7.1.  Now
we are on LX.

Other than the ANZOBJCVN concerns the only other one that I recall was we
had modified a SQLRPGLE program that accessed the FRT file.  We had to
change the sql from
SELECT RID, ...
to
SELECT "RID", ...
because RID is now a sql reserved word.  The upgraded wouldn't have broken
any compiled code with the old SQL.  You only noticed the error on a
recompile.


Rob Berendt