• The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
Menu
  • The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
  • Admin Alert: A Skeleton Checklist for Performing Power i Upgrades

    March 10, 2010 Joe Hertvik

    A checklist is a great foundation for performing a complex job. Properly constructed, checklists allow you to quickly perform all necessary tasks to accomplish a goal. This week, I’ll present a skeleton checklist for performing Power i upgrades, listing off universal tasks that must be completed for a successful hardware or software upgrade. Use this checklist as a starting point for your own upgrades, adding specific tasks as needed.

    The Skeleton Checklist

    The skeleton checklist was created to ensure that whenever my shop undertook a hardware upgrade–whether it was a small upgrade or a complete system replacement–that we didn’t forget to perform the common tasks along with our specific upgrade task. My iSeries, System i, and Power i checklist consists of the following steps, representing common tasks to be accomplished during a variety of upgrade situations.

    1. Complete and file all the necessary paperwork.
    2. Make sure everyone knows what’s going on.
    3. Publish the upgrade schedule (or schedules) to all interested parties.
    4. Inventory any hardware components or software media that will be installed in your machine.
    5. Place any scheduled jobs on hold that will be affected by the upgrade.
    6. If necessary, put daily or weekly backups on hold.
    7. If your machine has a Capacity BackUp (CBU) system, ensure that the CBU will have comparable capabilities with the source machine after the upgrade is finished.
    8. Make sure your CBU is ready to stand in for your production box, if necessary.
    9. Make sure any outside vendors participating in the upgrade are authorized to enter the building.
    10. Make sure there’s an active System Service Tools (SST) user ID and password that can be used by outside installers.
    11. Make sure one of the installers knows the Hardware Management Console (HMC) user ID and password.
    12. Ensure you have a system shutdown plan in place.
    13. Have a post-installation test plan ready to go.

    The Detailed Checklist

    However, while you can use my checklist to stage your upgrades, sometimes you need more information about exactly what you’re checking off to begin with. Here’s the checklist again, but this time I fleshed out its details to demonstrate the rationale behind each checkpoint.

    1.Complete and file all the necessary paperwork. This includes in-house paperwork (system change documentation, test plan, etc.) as well as external paperwork for regulatory or certification requirements (Sarbanes-Oxley, PCI Data Security Standard, etc.). Remember to file your paperwork with the proper authorities.

    2.Make sure everyone knows what’s going on. This includes the following people:

    • IT Management–Do your boss and your staff know what you’re doing?
    • Data owners–Are critical users aware of the change and do they know what to do when it’s finished?
    • Vendors performing the work–Do outside contractors working on the project know exactly what you want them to do?

    3.Publish the upgrade schedule to all interested parties. Do your installers know when to show up? Do your users know when the machine won’t be available? If Web sites interface with your upgrading i/OS partition, make sure to put a notice on the Web page telling your customers about Web site availability.

    4.Inventory hardware components or software media that will be installed in your machine. Make sure all ordered parts have arrived undamaged well in advance of the installation date. It’s better to find out if something is missing before the install, rather than during the install.

    5.Place scheduled jobs on hold that will be affected by the upgrade. If your upgrade maintenance window conflicts with a processing window, hold or reschedule any critical jobs that would normally run during that window.

    6.If necessary, put daily or weekly backups on hold. Conflicting scheduled backups must be accounted for if you’re going to take the machine down for an upgrade. Reschedule accordingly.

    7.If your machine has a Capacity BackUp (CBU) system, ensure that the CBU will have comparable capabilities with the source machine after the upgrade is finished. Make sure you have enough CBU resources (especially disk) to allow it to adequately replace your production box after an upgrade. If not, you may have to upgrade the CBU alongside the production box.

    8.Make sure your CBU is ready to stand in for your production box, if necessary. If a production system upgrade will take more than a few hours, consider switching processing over to a CBU for continued operation. If your CBU isn’t ready to stand in for your production, check out my two-part article on preparing a CBU for live fail over. Part one can be read by clicking here, and part two can be found here.

    9.Make sure any outside vendors are authorized to enter the building. If your iSeries, System i, or Power i box resides at a hosting center, call and place the installer on the site’s Let In and Let Out (LILO) list so they can enter and leave the building. If the machine is located in your on-site data center, make any necessary arrangements for the vendor to enter and leave the building.

    10.Make sure there’s an active System Service Tools (SST) user ID and password that can be used by outside installers. Most hardware upgrades will require the installer to enter SST, which will require someone to sign into the SST function to implement hardware changes or to look up information. You can either give your vendor the QSECOFR SST user ID and password or you can create a separate SST user profile for temporary users who need to get into SST.

    11.Make sure someone on site knows the Hardware Management Console (HMC) user ID and password. Just like SST, someone may need to get into the HMC to check information or make changes relating to your upgrade.

    12.Ensure you have a system shutdown plan in place. Unlike Windows servers, which can be rebooted many times per year, many i/OS boxes can go several months or even a year or more without IPLing. During an upgrade process, you will probably have to IPL your machine at least once so make sure you have an IPL pre-planning and post-planning checklist available.

    13.Have a post-installation test plan ready to go. Create a short document detailing out your test plan for making sure that the upgrade worked. Use the plan to test the upgrade and to document the results for later usage.

    While no checklist is perfect, if you follow the items presented here, they will help you remember to perform the common tasks that support all system upgrades. If you have any suggestions for other items to flesh out this skeleton even more, feel free to email me via the IT Jungle Contact Web page.

    RELATED STORIES

    The Road to Live CBU Fail Over, Part 2

    The Road to Live CBU Fail Over, Part 1

    i5 IPL Pre-Planning and Post-Planning Checklists



                         Post this story to del.icio.us
                   Post this story to Digg
        Post this story to Slashdot

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    Tags:

    Sponsored by
    iTech Solutions

    Choose Your Own IBM i OS Upgrade Adventure

    Choice 1:

    • Plan for 3 months
    • Check hardware & software compatibility
    • Check Lan Console, MQ, Domino, SMB, Ciphers, WebSphere, Java
    • Test, test, and test again
    • Prepare for potential downtime
    • Hope the OS Upgrade goes smoothly
     

    Choice 2:

    • Strategically plan alongside a team of IBM i experts
    • Work with experienced system admins to ensure hardware & software compatibility
    • Receive full analysis of Lan Console, MQ, Domino, SMB, Ciphers, WebSphere, Java
    • Know which PTFs are required for the upgrade
    • Relax, and let iTech handle the rest

    Not every OS Upgrade has to be an adventure. We make the process easy for you.

    Having completed thousands of upgrades, we have the experience, know-how, and expertise to get the job done seamlessly. We know what can go wrong, what to plan for, and can act quickly if problems arise.

    No matter where you are in your journey, we’re here to help. Take a look at the video below to ensure you’re on the right path when it comes to your next IBM i OS Upgrade.

    [Video] What You Need to Know to Successfully Upgrade to IBM i 7.4 and 7.5

    An IBM i OS upgrade isn’t complete until all the boxes are checked. Is your list up to date?

    In this video, Pete Massiello covers what’s new on IBM i 7.5, planning tips, pre-requisites, and post-installation requirements for a successful OS Upgrade.

    [ Watch Now ]

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    Sponsored Links

    RevSoft:  Enterprise solutions for data transfers, messaging and scheduling
    Linoma Software:  IBM i Encryption and Tokenization with Crypto Complete 2.20
    COMMON:  Join us at the annual 2010 conference, May 3 - 6, in Orlando, Florida

    IT Jungle Store Top Book Picks

    Easy Steps to Internet Programming for AS/400, iSeries, and System i: List Price, $49.95
    The iSeries Express Web Implementer's Guide: List Price, $49.95
    The System i RPG & RPG IV Tutorial and Lab Exercises: List Price, $59.95
    The System i Pocket RPG & RPG IV Guide: List Price, $69.95
    The iSeries Pocket Database Guide: List Price, $59.00
    The iSeries Pocket SQL Guide: List Price, $59.00
    The iSeries Pocket Query Guide: List Price, $49.00
    The iSeries Pocket WebFacing Primer: List Price, $39.00
    Migrating to WebSphere Express for iSeries: List Price, $49.00
    Getting Started With WebSphere Development Studio Client for iSeries: List Price, $89.00
    Getting Started with WebSphere Express for iSeries: List Price, $49.00
    Can the AS/400 Survive IBM?: List Price, $49.00
    Chip Wars: List Price, $29.95

    ABI Says RFID Spending Old Code Meets New Ideas in Latest App Modernization Projects

    Leave a Reply Cancel reply

Volume 10, Number 9 -- March 10, 2010
THIS ISSUE SPONSORED BY:

WorksRight Software
SEQUEL Software
CNX

Table of Contents

  • A Case for CASE
  • Job Descriptions: Underused and Underappreciated
  • Admin Alert: A Skeleton Checklist for Performing Power i Upgrades

Content archive

  • The Four Hundred
  • Four Hundred Stuff
  • Four Hundred Guru

Recent Posts

  • IBM i 7.3 TR12: The Non-TR Tech Refresh
  • IBM i Integration Elevates Operational Query and Analytics
  • Simplified IBM i Stack Bundling Ahead Of Subscription Pricing
  • More Price Hikes From IBM, Now For High End Storage
  • Big Blue Readies Power10 And IBM i 7.5 Training for Partners
  • IBM Delivers More Out-of-the-Box Security with IBM i 7.5
  • Groundhog Day For Malware
  • IBM i Community Reacts to IBM i 7.5
  • Four Hundred Monitor, May 11
  • IBM i PTF Guide, Volume 24, Number 19

Subscribe

To get news from IT Jungle sent to your inbox every week, subscribe to our newsletter.

Pages

  • About Us
  • Contact
  • Contributors
  • Four Hundred Monitor
  • IBM i PTF Guide
  • Media Kit
  • Subscribe

Search

Copyright © 2022 IT Jungle

loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.