Bonnie,

The 6.1 mentioned is OS version, not BPCS release

Yan Shargorodsky
Y&Y Solutions,Inc.
Phone: (267)934-8327
E-mail: Yshargorodsky@xxxxxxxxxx
-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On
Behalf Of Bonnie Bryant
Sent: Friday, April 15, 2011 10:38 AM
To: bpcs-l@xxxxxxxxxxxx
Subject: Re: [BPCS-L] BPCS-L Digest, Vol 9, Issue 48

You definitely need to use the new menu structure in v6+. It's much easier
to manage.
In v4.05 the menus were called by a SYS pgm. This is changed in the v6
versions.

I have a question.... why stop at v6.1? At this level you will need to
adapt to AS/SET code. Any mods will need to be made using AS/SET. You will
need to purchase ADK to get the source, etc. If you jump to Lx you bypass
the AS/SET phase. When you decide to move up to newer release, all of the
AS/SET is gone and your investment along with it.

With Lx, you will also bypass the GUI versions of CEA (G/L) and Load Build.
Lx can be run almost 100% (FRW excepted) green screen. You can also take
advantage of the Web Top (totally optional) if you choose.
Not to mention, Lx provides a lot of new functionality as well.

Just curious.

Bonnie Bryant
GCD Consulting



-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On
Behalf Of bpcs-l-request@xxxxxxxxxxxx
Sent: Friday, April 15, 2011 12:00 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: BPCS-L Digest, Vol 9, Issue 48

Send BPCS-L mailing list submissions to
bpcs-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/bpcs-l
or, via email, send a message with subject or body 'help' to
bpcs-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
bpcs-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of BPCS-L digest..."


*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is meaningful.

Today's Topics:

1. BPCS V405CD and OS V6R1 (Les Mittman - SBC)
2. Re: BPCS V405CD and OS V6R1 (rob@xxxxxxxxx)
3. Re: BPCS V405CD and OS V6R1 (Darryl Frankel)


----------------------------------------------------------------------

message: 1
date: Thu, 14 Apr 2011 13:52:55 -0500
from: "Les Mittman - SBC" <lmittman@xxxxxxxxxxxxx>
subject: [BPCS-L] BPCS V405CD and OS V6R1

I have a client who is on BPCS V405CD and on Infor Maintenance. They are
going to be upgrading the iSeries OS to V6R1.

We have a separate LPAR where we are going to perform the upgrade testing.
We have reviewed the IBM and Infor documents and have identified the steps
that must be followed.

We have reviewed the objects that will not convert from the current OS to
V6R1 and are determining a resolution for each.



On the BPCS side, there are BPCS Security-related Objects that are
non-observable and will not convert to V6R1. Infor provides BMR's 73619 and
73684 which are to be installed. These BMR's contain replacements for the
Security-related Objects and these will convert to V6R1. However, they also
contain new Infor BPCS Licensing programs. So, there is a change to
security and to licensing for V405CD with the upgrade to V6R1.



Included in the BMR are replacements for every BPCS Menu CL Program (e.g.
SSAE00, etc.). However, only the compiled object is provided. There is no
CL Source.

As with most BPCS Customer, changes have been made to many of the BPCS Menus
and new custom menus have been created using the standard BPCS security
logic.

Therefore, we need the source code for the BPCS Menus in order to apply the
custom changes that have been made. And, for the new custom menus, we will
need to revise the processing logic to use the new BPCS security process.

However, without the source code for the CL programs, our hands are tied.



The Customer has discussed this issue with Infor and received a reply that
they cannot receive the CL source code, they are not entitled to it. Yet,
they currently do have the source code.

We are pursuing this issue further with Infor, but I thought that I would
reach out to others to see if anyone has also encountered this issue.

If so, were you able to resolve it?

Also, for anyone who has successfully upgraded to V6R1 from BPCS V405CD, are
there any specific problems or concerns that we should be aware of?



Thanks for any comments. You can contact me offline in needed.



Les Mittman

847-858-5235

BPCS Consultant with over 20 years of experience





------------------------------

message: 2
date: Fri, 15 Apr 2011 07:31:14 -0400
from: rob@xxxxxxxxx
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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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