Subscribe to this APAR
By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.
| APAR (Authorized Program Analysis Report) |
Abstract
V7R2 INFOR LX AND BPCS REQUIRED PTF LIST
Error Description
**Last updated 04/30/2015 **
This informational APAR contains information regarding PTFs
required when running Infor's BPCS and LX products on the
on IBM i 7.2.
PTFs are not listed out individually below once they are
part of the latest group PTF or cumulative release. Therefore,
it is STRONGLY recommended that you put in place a process
to regularly obtain and apply the latest update of the
Group PTF for SQL and Database to your system.
Any PTFs required by BPCS programs which are NOT included in
the database group PTF or latest Cumulative, are listed
separately below.
The most current R720 CUM and HIPER PTFs are recommended.
The latest HIPER Group PTF can be found at this link:
http://www-912.ibm.com/s_dir/sline003.nsf/7f02fa4a8460c21f86256c
450052b184/954e847578ba4e9f86257cc900501edc?OpenDocument&Highlig
ht=2,SF99719
Do a WRKPTFGRP SF99709{R720 PTF} and this will show you the
level
of the installed HIPER Group PTF on your system.
The latest DB2 UDB Group PTF can be found at this link:
http://www-912.ibm.com/s_dir/sline003.nsf/7f02fa4a8460c21f86256c
450052b184/34cd5d96c41a6e4186257cc90055b43e?OpenDocument&Highlig
ht=2,SF99702
Do a WRKPTFGRP SF99702 and this will show you the
level of the installed DB2 UDB Group PTF your system.
********************************************************
Various BPCS and LX programs do not convert
********************************************************
--------------------------------------------------------
Affected BPCS versions: LX 8.3.0, 8.3.1, 8.3.2, 8.3.3
8.2.00, 8.1.00, 8.0.00,
6.1.00, 6.0.04, 6.0.02
BPCS CD
--------------------------------------------------------
Starting in R610 many secured source programs fail to convert
to the new operating system because they are not observable.
Obtain BMR 73619 and BMR 73684 to install updated copies
of these objects. A new license key is required when
installing BMR 73684.
********************************************************
Unable to log into BPCS Client/Server
********************************************************
--------------------------------------------------------
Affected BPCS versions: 8.2.00, 8.1.00, 8.0.00,
6.1.00, 6.0.04, 6.0.02
--------------------------------------------------------
Starting in R610 many NEWI, DOCA or ALAUNCH library objects
will fail to convert to the new operating system because they
are not observable.
Please obtain the proper objects for your BPCS release from
BMR 73959 from Infor365 Support.
********************************************************
SQL Warnings Cause Errors in Many BPCS Programs
********************************************************
--------------------------------------------------------
Affected BPCS versions: 6.0.02, 6.0.04
--------------------------------------------------------
Two BPCS releases require the following QAQQINI file setting
to be activated for support with R720:
QAQQINI SQL_SUPPRESS_WARNINGS *YES
For BPCS to be supported, users must setup a QAQQINI file
for use by all BPCS jobs on the system. By default, all
jobs on the system will load the QAQQINI file from library
QUSRSYS. Individual jobs can change the library used to load
this file by using the CHGQRYA (Change Query Attributes)
command and the QRYOPTLIB parameter.
The following command shows how to setup this option
using the QAQQINI file in library QUSRSYS:
1) Create a QAQQINI file in library QUSRSYS. This step can be
skipped if the file already exists (or the command will fail
and the error can be ignored):
> CRTDUPOBJ OBJ(QAQQINI) FROMLIB(QSYS)
OBJTYPE(*FILE) TOLIB(QUSRSYS) DATA(*YES)
2) Add the option for suppressing SQL warnings to the QAQQINI
QAQQINI file in library QUSRSYS. The following SQL statements
should be run in an interactive SQL session which can be
started via the STRSQL command. The first statement may fail
with a message about "row not found" which is normal:
> DELETE FROM QUSRSYS/QAQQINI
WHERE QQPARM='SQL_SUPPRESS_WARNINGS'
> INSERT INTO QUSRSYS/QAQQINI
VALUES('SQL_SUPPRESS_WARNINGS', '*YES', default)
--------------------------------------------------------
Affected BPCS versions: 6.1.00, 8.0.00
--------------------------------------------------------
Please login to http://www.inforxtreme.com.
Select Downloads/Patches and select Search for a BPCS
Modification Request for a list of BPCS BMRs
and cumulative releases for releases 6.1.00 and 8.0.00
that will correct the SQL problem so that the IBM code
for suppressing SQL warnings is not required to be activated.
If you choose not to apply these fixes you will need to
activate the SQL_SUPPRESS_WARNINGS option.
NOTE that BPCS 8.1 and higher releases do NOT require
the SQL_SUPPRESS_WARNINGS to be activated and it is
NOT recommended as a general practice to activate this
option.
********************************************************
RPG Compiler Error Compiling Large BPCS Programs
********************************************************
--------------------------------------------------------
Affected BPCS versions: 6.1.00, 6.0.04, 6.0.02
--------------------------------------------------------
ODTs are exceeded when certain 6.x BPCS programs are compiled
into OPM RPG at V4R5 and higher releases of OS/400.
This issue is corrected by use of ILE RPG in BPCS 8.0 and higher
releases. The suggested workaround on prior product releases
is to recompile the program manually into ILE RPG.
Infor Xtreme has a utility available on the FTP site called
CVTCMPILE which will help to automate this task. From the
InforXtreme.com main page select Downloads/Patches and select
BPCS/ERPLX FTP to access the FTP site.
********************************************************
MCH6801 in ADK
********************************************************
An MCH6801 is received when running the AS/SET ADK development
tool at Security Level 40 or 50. This is due to some
of the AS/SET programs being compiled prior to V2R3. The
BMR 62901 re-delivers these programs. The workaround is
to reduce system security to level 30. This affects all
versions of AS/SET up to those included with BPCS 8.2.00.
Problem Summary
Problem Conclusion
Temporary Fix
Comments
INFO
Circumvention
PTFs Available
Affected Modules
Affected Publications
Summary Information
| Status............................................ | CLOSED CAN |
| HIPER........................................... | No |
| Component.................................. | |
| Failing Module.......................... | |
| Reported Release................... | R720 |
| Duplicate Of.............................. |
System i Support
IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information
Document Information
Modified date:
01 May 2015