× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Rob,

Infor does not maintain a list of PTF fixes or even specific BMRs done due to changes at various IBM releases in any internal Infor documents nor on the Infor support website -- the IBM Info APAR for BPCS is the sole document that was always used to track these operating system-related issues as it seemed the most logical place. The SSA Global support center (used to? unclear if much is being done in that department now) work jointly with IBM support to keep it updated. I notice that the document has not been touched in awhile to update it to the latest cumulative levels. However the list of required Infor BMRs for BPCS remains true and any old PTFs listed are still required, as are the QAQQINI file settings. Whether or not any new IBM PTFs have been encountered for issues affecting BPCS since the document was last updated in 2007 is the only outstanding question.

And some of those Client/Server runtime BMRs as previously mentioned if ordered now will bring in new user licensing BMRs with them as that is now tied into the Client/Server runtime (and you may have encountered this if your upgrade to V6R1M0 happened after July of last year, which may be part of what you are recalling beyond the fact that the KRSO secured source programs were recompiled and redelivered). V6R1M0 does indeed involve more planning.

If anyone needs help with such any operating system upgrade and BPCS let me know as I am very well versed in it.

PS - I can also confirm that the aforementioned Info APAR for BPCS is indeed for V5R4 and if you are moving to V5R4M5 you may need to ask IBM to research any equivalent PTF numbers in that Info APAR for the M5 release. I can confirm any encountered BPCS related problems are all the same on the M5 release and that we (back then I was with SSA Global and Infor) encountered no other differences between the M5 release and the main V5R4 release since the hardware enabling changes did not affect BPCS or SQL.

Take care,

Genyphyr Novak
iSeries Technical Consultant
France
+33 662 15 02 02




________________________________

-----Inline Message Follows-----

Technically you'll be running V5R4M5 not V5R4M0. I'd have your
technicians upgrade you to that now before the hardware comes in to
minimize time to do the hardware upgrade. The M5 is needed to support
Power 6. The base OS or 5722SS1 will still say V5R4M0 but if you look at
the "licensed internal code" or 5722999 that will say V5R4M5.

See informational document II14189 from IBM regarding V5R4 and BPCS.
http://www-912.ibm.com/n_dir/nas4apar.nsf/c79815e083182fec862564c00079d117/f1914289734d926e8625719c003c6f97?OpenDocument&Highlight=2,bpcs,r540

Basically some recommended ptf's and some query settings in a parameter
file.

I am sure that somewhere in the bowels of Infor's website they have a
similar document.

By the way, there's a matching informational document for 6.1, II14421
http://www-912.ibm.com/n_dir/nas4apar.nsf/c79815e083182fec862564c00079d117/2ed784e875e77a4586257490003c6d39?OpenDocument

Always helps to have something "official", then backed up with real world
experiences, like the other replies to your question.

Actually, our upgrade to 5.4 was so long ago we forgot most of the bumps.
We're an all 6.1 shop now. Let me tell you - that was a MOTHER of an
upgrade to BPCS! Do 6.1 carefully or have your resume' updated.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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.