You need to ensure that you have the latest version of the JAVA based IBM i Access Client Solutions product on your PC before starting the upgrade to 7.3. Your choice since 7.2 has been one of two consoles, HMC or LAN Console. This prevents any conflict between the existing console and the Operations Console. If you are upgrading to 7.3 and you want to replace an existing console with a LAN attached Operations Console, upgrade the system before you migrate the console. The IBM i Access for Windows client doesn’t need to be removed from the PC but be aware the IBM i Access for Windows console will not continue working if the system is upgraded to 7.3.
Note: The LAN console feature in the IBM i Access for Windows client will work for a D-mode install because SSL ciphers aren’t used during the D-mode IPL but on the following A-mode IPL the IBM i Access for Windows LAN console will fail to connect.
You must upgrade to the new Java based Access Client Solutions product before upgrading to 7.3. This release is no different but you need to go another step.
It has always been the recommendation that administrators upgrade the LAN Console software on the PC being used as the console prior to upgrading the OS. Net, the company's multilanguage IDE, to create Web services applications that will run on the. While we are on the subject of hardware, if you are using iSCSI IBM i 7.3 will not support iSCSI connected System x hardware, as that product has been stabilized. Also, IBM i 7.3 isn’t supported on the IBM Flex System p260 and p460 Compute nodes for POWER7 or POWER7+ (Make sure you understand this is just IBM Flex Systems), nor Blades PS700, PS701, PS702, PS703, or PS704. In addition, Power6 BladeCenter models JS12, JS22, JS23, and JS43 machines can’t run 7.3. IBM i 7.3 is not supported on Power6 systems. Every company’s IBM i environment is unique, and careful consideration and planning must be done for each upgrade to ensure there is no interruption to the business. While IBM i 7.3 contains many cool new features and functions, the upgrade has several points that you need to be aware of. These are a few of the items that I want to bring to your attention, and certainly not all the concerns that must be examined before an upgrade. We want to bring to your attention a few items and pre-requisites that you need to consider before you start your upgrade to 7.3. Reading the IBM i Memo to Users and the upgrade guide will help ensure you are on the right path to a successful upgrade. You may have to add this system name to your local hosts file or your DNS server, if you have access to that.As with any upgrade, the success is in the preparation. You'll find this in the NetServer properties screen in iSeries Navigator. Keyboard map does not convert automatically, but can be converted. While it makes an easy install, I found a number of times it just did not work, and I had to install the 'old' Client Access. Many systems like to put a Q in front of the name as the netserver name. I have been using it for a couple of years, with mixed results. You can use the NET USE command, right-click on my computer and map a drive, or type the address in your explorer window like \\NetServerName\Ī big issue to consider is the name of your net server does not have to be the same as the name of your AS/400. You can start it from iSeries Navigator or using the following AS/400 command if it isn't running: STRTCPSVR SERVER(*NETSVR)Īfter that, you map just like any Windows server. You also need to have the netserver job running on the AS/400.
Ask your AS/400 server admin, or someone with enough authority to create the share. If Python3 isn’t there, click the Available Packages tab. At this point, a list of currently installed Open Source packages will be displayed.
From Access Client Solutions, IBM’s free GUI for managing your IBM i: Go to the IBM i Tools menu Open Source Package Management. To map to an IFS folder from a Windows machine on the network, you must first share it using iSeries Navigator. Step 2: Install the Python package with YUM.