IBM Support

Planning to upgrade to IBM i 7.1 (Planning statements)

General Page

Planning to upgrade to IBM i 7.1 (Planning statements)

Planning statements provide insight into IBM's current plans, directions, and intent, and are subject to change or withdrawal without notice. Any reliance on these planning statements is at the relying party's sole risk and will not create liability or obligation for IBM.

Planning statements

IBM i support for POWER5, December 2010

IBM plans for IBM i 7.1 to be the final release to be supported on POWER5 systems 9405-520, 9406-520, 525, 550, 570, 595, and 9407-515.

IBM Business Solutions (5722-BZ1), October 2010

IBM will no longer deliver IBM Business Solutions for IBM i V5R4 and later releases starting October 2010. IBM Business Solutions was formerly delivered with all IBM i orders and upgrades. It included a set of enterprise Web application examples built to run on the J2EE platform provided by IBM WebSphere Application Server for i. IBM Business Solutions consisted of three applications:

AT&T dial accounts, April 2010

IBM plans to withdraw the AT&T dial accounts for connecting to IBM for electronic customer support requests. These AT&T dial accounts will no longer be available for use with the release following IBM i 7.1. If you were creating your service configuration with a local dial or remote dial connection type and using the IBM-supplied AT&T telephone numbers, you will be affected by this change. It is recommended to connect to IBM with a direct internet connection for electronic customer support requests. If you must continue to use a dial account, you will need to use your own Internet Service Provider (ISP) beginning with the release after i 7.1. You can make this change now with the current IBM i release you are running on your system.

Communications Trace Analyzer, April 2010

IBM plans for i 7.1 to be the final release to support the Communications Trace Analyzer plug-in to IBM i Navigator. An enhancement in the i 6.1 release (PTF SI33685) allows a communications trace to be dumped into the Packet Capture (PCAP) format used by other trace analysis tools. It is recommended that you use a tool that can analyze the communications trace data in PCAP format rather than the communications trace analyzer. In the i 6.1 release, you need to create a data area named QCMNTRCPCP in library QGPL prior to issuing the Dump Communications Trace (DMPCMNTRC) CL command. The existence of this data area will result in the data being dumped in the PCAP format. In the i 7.1 release, the DMPCMNTRC command has a new Stream file format keyword, FORMAT, where *PCAP can be specified.


Additional resources

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000C4BAAU","label":"IBM i"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0"}]

Document Information

Modified date:
28 April 2022