FTP is running on the iSeries LPAR where you are installing RJSINFOP.
Your account has the required system credentials. Note: If your account does not have the required system credentials, use QSECOFR or another account with *ALLOBJ special authority.
On the FTP server, make sure that NAMEFMT is set to 1, not 0. Note: NAMEFMT is set to 1 on most FTP servers.
If you are using FTP exit programs, create an exception or temporarily disable them during this installation.
No additional license is required when performing an upgrade, assuming the serial, model, and LPAR numbers are the same. If you are upgrading your system as well, please apply for a temporary license.
On a Windows system on the same network as the iSeries, download the zipped RJSINFOP save file.
Unzip RJSINFOP_1.0.1.ZIP to C:\.
Run CRTSAVF FILE(QGPL/RJSINFOP) to create a temporary file on the iSeries to upload RJSINFOP.LIB to.
Back up your existing library
Option 1 Run the following command on an iSeries command line as a security officer. This works well, assuming there are not a lot of object locks on the RJSINFOP library. RNMOBJ OBJ(QSYS/RJSINFOP) OBJTYPE(*LIB) NEWOBJ(RJSINFBAK)
Option 2 Run the following command on an iSeries command line as a security officer. This works well, even if there are locks on the RJSINFOP library; these locks will be forcefully removed when the library is cleared. CPYLIB FROMLIB(RJSINFOP) TOLIB(RJSINFBAK)
Install the new library version
Log in to the iSeries LPAR you are installing RJSINFOP on:
Bring up a command line:
On older versions of Windows, click Start > Run, type cmd, and click OK.
On newer versions of Windows, click Start, type cmd, and press Enter. A Windows Console window opens.
Type ftp 18.104.22.168, where 22.214.171.124 is the IP address of the iSeries LPAR you are installing RJSINFOP on.
Type the user name and password of the account you chose in Before You Install 3.2. Note: If you cannot log in, most likely either your account has a security restriction on the iSeries or you are using FTP exit programs. In both cases, contact your iSeries administrator to rectify.