OS Upgrade

 Why we perform an OS Upgrade?

http://www-947.ibm.com/systems/support/i/planning/upgrade/suptschedule.html
OS Upgrade
Features of OS Upgrade.

Refer to memo to user guide

 Operating system contains new release changes to basic operating system functions.
It includes changes to systems management functions, such as configuration and
tailoring the system and changes that could affect the way things operate or appear in
the new release.

 Options provides information about new release changes that affect specific program
options of the operating system.

 Licensed programs contains new release changes that might affect existing
applications. These changes might also affect applications saved on a V6R1 system
to be restored on a previous release server.
OS Upgrade

KEY POINTS TO REMEMBER WHEN PLANNING FOR AN UPGRADE:

 Have the OS images ordered.

 Ensure you have enough space for the image files. Check WRKSYSSTS, make sure the
space is at a maximum of 80-85% after image files have been uploaded (before upgrade).

 Verify the from and to OS version and the LIC space requirements. If necessary, you
MUST complete the option to “Allocate Additional space for LIC” by taking the option
from the Prepare to install screen. An IPL must be performed to complete this step.

 Review your APARs and OS upgrade planning package for special considerations.
II14149: REQUIRED PTFS FOR UPGRADING TO V5R3Mx
II14131: REQUIRED PTFS FOR UPGRADING TO V5R4Mx
II14310: REQUIRED PTFS FOR UPGRADING TO V6R1Mx
http://www-01.ibm.com/support/docview.wss?uid=nas26cf800ceaf8376c3862573e70041ec63
OS Upgrade
Upgrade planning:
 Hardware compatibility
http://www-947.ibm.com/systems/support/i/planning/upgrade/v6r1/hardware.html
 IBM i 6.1 support of existing hardware I/O features
IBM i 6.1 generally supports the existing hardware I/O features that are supported by
IBM i 5.4. Clients upgrading from IBM i 5.4 should be able to continue to use their
supported I/O hardware features with IBM i 6.1.

 Software compatibility
Check the following link for Products & Functions not supported by OS V6R1 and
remove or replace them before the upgrade.
http://www-947.ibm.com/systems/support/i/planning/upgrade/v6r1/software.html
OS Upgrade
OS Upgrade
 Check the following link to make sure the FSP firmware level is supported with the
new OS V6R1.
http://www-912.ibm.com/8625680A007CA5C6/1AC66549A21402188625680B0002037E/C69799B70A28578C8625712C004FE06B

Analyze Object Conversion

After you run the ANZOBJCVN command, you receive information to
help you determine the impact that object conversions will have
on your system. The ANZOBJCVN command analyzes the following
types of object conversions:

1) Conversion of program objects in libraries.

2) Conversion of Java programs attached to stream files.
3) Conversion of spooled files.
4) Conversion of integrated file system names in file systems
that are not case-sensitive.

ANZOBJCVN OPTION(*COLLECT)
ANZOBJCVN OPTION(*REPORT) RPTTYPE(*CVNPRB)
ANZOBJCVN OPTION(*REPORT) RPTTYPE(*LIBSUM)

Program Conversion Problems.txt Lib Sumary report.txt

OS Upgrade
Checking Console Bits in DST
 An Operations Console directly attached to the system is not supported in IBM i 6.1.

 On the system that is being upgraded you need to change the system into Manual mode and
request a DST on the system console.

 Go into DST environment, then system device, then console to verify the console bits. If it’s
LAN, also verify the ip configuration with the LAN console PC setup.

Select Console

Select one of the following:

Console type . . . . . . . . . . . . . . . . 4
1. Twin axial
2. Operations console(Direct)
3. Operations console(LAN)
4. Hardware management console(HMC)

Allow console to be taken over by another console . . . . . . . . . . . . . . . . 1 1=Yes, 2=No

OS Upgrade
OS Upgrade
PREPARE FOR INSTALL PLANNING

 NOTE: THIS STEP SHOULD BE COMPLETED AT LEAST ONE WEEK PRIOR TO

UPGRADE

 Ensure virtual optical drive ( OPVRT01) exists on server. If not create one.

 Make sure the OPTVRT01 is active by typing the following command:

 WRKDEVD DEVD(*OPT) or WRKCFGSTS CFGTYPE(*DEV) CFGD(OPT*)

 Type the following command:

 CHGMSGQ MSGQ(QSYSOPR) DLVRY(*BREAK) SEV(95)

OS Upgrade
 Type WRKIMGCLG in command line
OS Upgrade
 The image catalog that is to be used must be loaded into the virtual optical drive.
 LODIMGCLG IMGCLG(OSV6R1) DEV(OPTVRT01) OPTION(*LOAD)
 Take opt 8 to load on WRKIMGCLG
OS Upgrade
 Take opt 10 to verify the Image catalog
 Note: Verify type should be *UPGRADE if we perform OS upgrade and Sort Image catalog is
set to *YES
OS Upgrade
 Type WRKIMGCLG in command line
 Check the status of Device . It should be Active after loading the Image Catalog in Virtual Optical
drive
OS Upgrade
 Take opt 12 to Work with entries
OS Upgrade
 On the command line, enter ‘GO LICPGM’ and press enter.
 Then take option 5 “Prepare for install”. The following screen will appear.
OS Upgrade
 Place an option 1 beside the first field entitled “Work with license programs for
target release” and pressEnter.
 The following screen will appear. In the Field “Generate list from”, enter a “1” for
Distribution media. Enter OPTVRT01 as your Optical device and enter your Target
Release, i.e.: V6R1M0
 The license information will be verified from the CD.
OS Upgrade
OS Upgrade
 The next screen will show all the software that is to be upgraded represented with a 1 beside it.
If you want to load additional software, place a 1 beside the software product version and then
press enter to return to the “Prepare for Install” screen.
OS Upgrade
OS Upgrade
 Place an option 1 beside the field entitled “Work with license programs to delete” and press
enter.
 The displayed screen may list some products that no longer exist.
 Do not delete these products until the upgrade has been completed. For now, just press enter to
get the completion acknowledgement.
OS Upgrade
 From the “Prepare for Install” screen, Place an option 1 beside the field entitled “List license
programs not found on media” and press enter.
 Note: If anything shows up on the list you must contact IBM as the upgrade in relation to the
missing software could be compromised. If there is nothing on the list, press enter.
OS Upgrade
 From the “Prepare for Install” screen, place an option 1 beside the field entitled “Display license program for target release” and
press enter. The screen should look something like the example below.
 All products that are to be added or replaced (upgraded) should be present. Check the list. If the list is correct, press enter. If it is
NOT correct, go back and review your software list to be upgraded and confirm that you have selected everything with a ‘1’
OS Upgrade
 From the “Prepare for Install” screen, place an option 1 beside the field entitled “Work with
software agreements” and press enter. The screen should look something like the example
below. Notice the “Accept Status” field is NO.
OS Upgrade
OS Upgrade
.
 Press F15 to accept the license agreement. This must be done for each product. Once all of the
products are accepted, you will see the “Accept status” field set to YES for each product.
Ensure all products have been accepted and Press Enter
OS Upgrade
OS Upgrade
 From the “Prepare for Install” screen, place an option 1 beside the field entitled “Work with
user profiles” and press enter. If you want to delete user profiles as part of the upgrade, you
can do so here. If not (which is RECOMMENDED), press enter.
OS Upgrade
 From the “Prepare for Install” screen, place an option 1 beside field entitled “Verify system
objects” and press enter. No screen will be displayed.
OS Upgrade
 From the “Prepare for Install” screen, place an option 1 beside field entitled “Estimate storage
requirements for system ASP” and press enter. A screen will appear stating the required size,
thenpress enter. If you ensured that your space was below 80% you should be okay.
OS Upgrade
OS Upgrade
 From the “Prepare for Install” screen, place option 1 beside the field entitled “Allocate
additional space for LIC” and press enter
 The following screen will appear. Change the allocate space field to VxRxMx and press enter.
During the next IPL the required space will be allocated.
OS Upgrade
 From the “Prepare for Install” screen, place option 1 beside the field entitled “Keep Disk
Configuration” and press enter.
Change the keep disk configuration field to *YES and press enter. Make sure there is enough
disks for the upgrade.
OS Upgrade
 Allocate extra LIC space:

 If upgrading from V5R4M0, use WRKDSKSTS to verify the load source disk size is
bigger than 17G.
 Use the Allocate Licensed Internal Code Space API (QLPALCSP) to find out if enough
reserved storage is available, to allocate the additional space when necessary, and to
correct any other possible errors. Enter the following:
 CALL PGM(QLPALCSP) PARM('V6R1M0' '1')
 Run the same command again after the IPL and review the job log. If you see the
following information message, you do not need to perform an IPL as you have the
required space necessary.
CALL PGM(QLPALCSP) PARM('V6R1M0' '1')
 Allocating additional space is not necessary.
 Additional Message Information
Message ID . . . . . . : CPI3DBF
Date sent . . . . . . : 12/22/10 Time sent . . . . . . : 13:17:42
Message . . . . : Allocating additional space is not necessary.
OS Upgrade
OS Upgrade
OS Upgrade
 If you are performing an IPL NOW, do the following:
 ENDSBS SBS(*ALL) OPTION(*CNTRLD) DELAY(180)
 PWRDWNSYS DELAY(300) RESTART(*YES) IPLSRC(B)
 Otherwise, perform the IPL on the weekend at the regularly scheduled time.

Permanently apply PTFs

 Permanently apply Licensed Internal Code and operating system PTFs by using the following
commands as recommended before all installations

 Change the system values to have the system IPL into restricted state. Use the following
command ‘CHGIPLA STRTCP(*YES) STRRSTD(*YES)

 Perm apply all the PTFs on the target system before the upgrade weekend.
 APYPTF LICPGM(*ALL) SELECT(*ALL) APY(*PERM) DELAYED(*YES)

 With the system in restricted state perform the IPL.

PWRDWNSYS DELAY(300) RESTART(*YES) IPLSRC(B)
OS Upgrade
START THE UPGRADE:
 Sign on as QSECOFR.
 A full system saves must be performed prior to starting the upgrade.
 Check the Server Health, Backup logs and retain the Tapes in the Tape Library and
send BRMS report to team
STRRCYBRM PERIOD((*AVAIL) (*AVAIL *CURRENT))
STRSBS QSYSWRK and IP to move the two DR reports (QP1ARCY &
QP1A2RCY) to a PC.
 Make sure the LIC space is expaned and all pre-req PTFs have been applied
 CALL PGM(QLPALCSP) PARM('V6R1M1' '1‘)
 Check “GO LICPGM” and take option 10 to make sure the products are in the
correct state (CHKPRDOPT). The installed status should be Installed or
Compatible.
OS Upgrade
OS Upgrade
 Load the OS image catalog into the virtual optical drive, using the following command:

 LODIMGCLG IMGCLG(OSV6R1) DEV(OPTVRT01) OPTION(*LOAD)

 VFYIMGCLG IMGCLG(OSV6R1) SORT(*YES)

 You should receive a message stating the verification was successful.

 Note: Make sure the Images are sorted in order

 If you have a large number of spooled files on your system, set the compress job tables IPL
attribute to none. To do this, use the Change IPL Attributes command:

 CHGIPLA CPRJOBTBL(*NONE)

 Run DSPSRVA to make sure there is no individual profiles there, and if there is any, make sure
the profiles still exist on the system
OS Upgrade
 Ensure the system value QSYSLIBL has no secondary languages listed in it. I.e: QSYS2932. If
it does, remove it.

 CHECK SYSVAL QSYSLIBL and QUSRLIBL, Do not remove QSYS, QGPL, QUSRSYS,
QTEMP, or QSYS2 and remove if any others.

 Make a note of the startup program name and change to *NONE

 CHGSYSVAL QSTRUPPGM VALUE(*NONE)

 Ensure QALWOBJRST is set *ALL,

 QVFYOBJRST is set to 3

 QFRCCVNRST is set to 0. No conversion will happen during the upgrade. Use STROBJCVN
after the upgrade for V6R1 conversion.

 Ensure that the AS400 panel for this system or partition is set to B N.
OS Upgrade
 Ensure the system is in restricted state by entering the following command:
 ENDSBS SBS(*ALL) OPTION(*CNTRLD) DELAY(180)
 Run the Reclaim Storage - RCLSTG SELECT(*DBXREF)
 Start the upgrade by running the command
 PWRDWNSYS DELAY(300) RESTART(*YES) IPLSRC(*IMGCLG) IMGCLG(XXXX)
 After the PWRDWNSYS command, the system will go through the normal D codes to
shutdown, then it will show the following SRCs, which indicate the status of the new LIC load.
 C6xx41DC is a status reference code that indicates the progress of the Licensed Internal Code
decompression. The xx indicates the percent that is decompressed. No action is required.
 C6xx41CC is a status reference code that indicates the progress of the Licensed Internal Code
installation. The xx indicates the percent of the Licensed Internal Code that is installed. No
action is required.
 After the new LIC is loaded and the system booted from B side, You will be monitoring the OS
& LPP upgrade progress on the system console. Depends on the number of LPPs, this might take
1-3 hours.
OS Upgrade
OS Upgrade
OS Upgrade
OS Upgrade
 Installing the LPP
OS Upgrade
OS Upgrade
 Once the upgrade is completed and the system IPLed there should be a Signon screen. Log
on as QSECOFR.

 Enter the command GO LICPGM and take option 50. It should state the automatic upgrade
completed successfully and a message for each license product should be present stating that the
product was upgrade or installed successfully.
 Note: If any of the LPP is failed validate the product then save and Restore the LPP from
other OS 6 SYSTEM
 check the status of INZSYS, which should be completed successfully during OS automatic
upgrade. Otherwise, run the command manually in strict mode.
 Run CHKPRDOPT PRDID(*OPSYS)then “GO LICPGM” and take option 10 to make sure
the products are in the correct state. The installed status should be installed or Compatible.
 Make sure that the BRMS Product is Initialize if not use command
INZBRM OPTION(*RUNPRDINZ)
 Note: The Appx time to complete the above command is 1 Hour
 And 'Check BRMS status by running any BRMS command, eg: WRKMEDBRM' right after the
BRMS product initialization
OS Upgrade
 Enter the command: “GO LICPGM" and take option 20. If there is a secondary language installed,
perform a normal secondary language install via opt 21 with the image catalog file at the new version or
◦ Restore the QSYS29xx library on the target system using the Restore Library (RSTLIB) command,
where xx represents the national language version feature code for the secondary language.
◦ Restore the licensed programs on the target system using the Restore Licensed Program
(RSTLICPGM) command, specifying 29xx for the LNG parameter and *LNG for the RSTOBJ
parameter. For example:

 RSTLICPGM LICPGM(5722WDS) DEV(OPTVRT01) RSTOBJ(*LNG) LNG(29xx)

ENDOPT(*LEAVE)

 Apply the CUM/Group PTF

 Submit the OBJECT conversion job when OS upgrade and CUM load have finished. This will convert
all the objects on the system to V6R1 format. [Use QSECOFR to submit the below command
 SBMJOB CMD(STROBJCVN OPTION(*CONVERT) LIB(*ALLUSR) OBJ(/) JOB(STROBJCVN)
JOBQ(QSYS/QSYSNOMAX)
OS Upgrade
POST UPGRADE TASKS:

 The system values must be changed back the value prior to the upgrade.
 Run the following commands to disable the V6 FTP enhanced feature, EPAVS & EPORT

 CRTDTAARA DTAARA(QUSRSYS/QTMFTPEPSV) TYPE(*LGL) AUT(*USE) - disables

EPASV

 CRTDTAARA DTAARA(QUSRSYS/QTMFTPPASV) TYPE(*LGL) AUT(*USE) -

disables PASV

 CRTDTAARA DTAARA(QUSRSYS/QTMFTPEPRT) TYPE(*LGL) AUT(*USE) -

disables EPORT with PTF SI33243 applied to the system - no ptf is needed for releases after
R610.
 http://www-912.ibm.com/__8625680a007ca5c6.nsf/1ac66549a21402188625680b0002037e/dace92df240295dc8625742500565275?OpenDocument&ExpandSection=-
1
OS Upgrade
 Disable the QIBMHELP from start automatically
It can be set to not auto start via the QUSRSYS/QATOCSTART file
 On the operating system command line type the following:

WRKMBRPDM QATOCSTART. Press the Enter key.

Select Option 18 on the Servers member.
Page down to *IBMHELP.
Set the Auto start parameter to *NO.

 CHGLICINF PRDID(5761XW1) LICTRM(V6) FEATURE(5050) USGLMT(*NOMAX)

THRESHOLD(*USGLMT) if target version is V6

 WRKPTFGRP to make sure all the group levels are up-to-date.

 Deleting the images:
Use the command DLTIMGCLG IMGCLG(*******) KEEP(*NO).
 Enter the IBM and Third Party keys if not already completed.
 You can also download the license keys from IBM ESS webstie
OS Upgrade
 Object conversion command - STROBJCVN OPTION(*CONVERT) LIB(*ALLUSR)
OBJTYPE(*ALLPGM) OBJ(/)

 Change authority on QBATCH Jobd to PUBLIC *USE

 Ensure the Auto start job QSTRRMTWTR exist under subsystem QSPL after the OS upgrade, if
not add it using the command.
ADDAJE SBSD(QSYS/QSPL) JOB(QSTRRMTWTR) JOBD(QGPL/QSPLSTRWTR)

CHGPRTF QPPGMDMP HOLD(*YES)

CHGPRTF QPJOBLOG HOLD(*YES)

INZBRM *ESTPRDINZ

CFGPFRCOL INTERVAL(15.00) LIB(QMPGDATA) DFTCOLPRF(*STANDARD)

RETPERIOD(00007 *DAYS) CRTDBF(*YES)
OS Upgrade
Summary

Preparation:

 Upload & Install pre upgrade PTF image

 Run CHKPRDOPT. Delete old LPP that not supported by V61
 Upload OSV6R1 OS image catalog and verify
 Prepare for Install
 Load source disk must have a minimum capacity of 17GB
 Permanently apply Licensed Internal Code and operating system PTFs Before weekly backup.
 Check the console type bits on DST make sure matches current setup
 Change IPL bit to restrict mode *YES and Set Startup program to *None
MAIN ACTIVITIES

 Run BRMS Weekly Full system save at V5R4 level(system IPL into restricted state)
 Check the Server Health, Backup logs and retain the Tapes in the Tape Library and send BRMS
report to team
 Run Reclaim - Database cross reference in restricted state
 Upgrade the system to V6R1M1 via Image Catalog
 INZBRM *RUNPRDINZ will Automatically after the OS upgrade and apply OS61 perm keys
 Start the CUM and Group PTF Installation
 Check the JOBLOG for successful installation
 Verify OS installation [INZSYS, INZBRM ]+ PTFs applied
 Run second BRMS Weekly system save at V6R1M1 level with IPL back to normal + Post IPL
checks
 Run the STROBJCVN command with the *CHECK
POST ACTIVITIES

 Change authority on QBATCH Jobd to PUBLIC *USE

 Ensure the Auto start job QSTRRMTWTR exist under subsystem QSPL after the OS upgrade, if
not add it using the command.
 CHGPRTF QPPGMDMP HOLD(*YES)
 CHGPRTF QPJOBLOG HOLD(*YES)
 INZBRM *ESTPRDINZ
 INZBRM *RUNPRDINZ
 CFGPFRCOL INTERVAL(15.00) LIB(QMPGDATA) DFTCOLPRF(*STANDARD)
RETPERIOD(00007 *DAYS) CRTDBF(*YES)
OS Upgrade
Some important links for reference

 http://www-912.ibm.com/s_dir/sline003.nsf/sline003home

 https://www-912.ibm.com/e_dir/eServerPrereq.nsf/HW2/Hardware~iSeries~8338?OpenDocument

 http://www-947.ibm.com/systems/support/i/planning/upgrade/v6r1/software.html

 http://www-912.ibm.com/s_dir/sline003.NSF/2d3aff1c6b4d6ce086256453000d971e/
65dfd582843bdaab8625740800632e51?OpenDocument

 http://www-947.ibm.com/systems/support/i/planning/upgrade/suptschedule.html
OS Upgrade

Thank you