April 2012 Newsletter
i can do anything with iTech Solutions
In this issue of the newsletter, I want to focus on IPLs, as I have been talking with quite a few customers lately about IPLs, how often, when, how, and I thought this would be a good theme for this month. One question that I get asked often is how often should I IPL. My answer to this, is no less than quarterly. What? Yes, just one IPL every few months is all that you need. If you are a heavy user of temporary storage, you might need to monitor this, and perhaps do it more often, but the reason why you don’t want to IPL too much is performance. To be more precise, database performance. Why would this be. The SQL Plan Cache is cleared during each IPL. The Plan Cache is a repository that contains the access plans for queries that were optimized by SQE. The Plan Cache is interrogated each time a query is executed in order to determine if a valid access plan exists that satisfies the requirements of the query. If a valid access plan is found, it is
used to implement the query. Otherwise a new access plan is created and stored in the Plan Cache for future use. Note, with the latest Database Group PTF, the size of the Plan cache can now be larger holding more information to make the database performance better. See, it pays to be on the latest release, at the latest PTF level.
This issue of our newsletter has five articles. In the first, we will discuss IPLs, how often, when, and how. The second article is about one of my favorite commands used during IPLs. The third article lists some of the upcoming events in which iTech Solutions will be participating. The fourth article is about recent IBM hardware announcements. The last article is for your reference with updated PTF information. Please note that we have added a new PTF group to our recommended list, which is the High Availability Group. If you are an iTech Solutions PTF Maintenance customer, you will receive this on your next application of PTFs.
If you are still on V5R4, send Pete an email and he can help you upgrade to 6.1 or 7.1. With over 380 6.1/7.1 upgrades done to date you know iTech Solutions has the expertise and know how.
iTech Solutions can help you improve performance, perform security audits; implement a High Availability solution; perform health checks, systems management, remote administration, PTF management, blade installations, iSCSI configurations, backup/recovery; upgrade an existing machine; or upgrade to a new machine. If you are thinking of LPAR or HMC, then think iTech Solutions. We have the skills to help you get the most out of your IBM i.
Let’s start with what it is. Some people also refer to this as a “Reboot” of your system. It reinitializes your system, reloading the operating system. You may need to reinitialize your system after some types of hardware or software upgrades. You do this with an IPL. An IPL resets system storage (cleans out what was there and replaces it with new data). In other words, IPL means start your system
When you perform an initial program load (IPL), the process resets your system’s storage. It causes the system to recognize changes in the system environment, such as changes in the following:
We can usually do this a few ways. When the system is up and running, we could issue the command PWRDWNSYS RESTART(*YES). If the system/partition was off we could press the white button on a non-LPARed machine, or activate a partition from an HMC.
There are four modes for an IPL, but we are only going to discuss two of them, Normal and Manual.
You can use the type and mode together for various combinations, and various reasons. I hope this explains what happens during an IPL, and the options that you have.
|Change IPL Attributes.
|The Change IPL Attributes Command, CHGIPLA, is used to change attributes or functions on the next IPL. I like to use this when I don’t want the system to startup after an IPL, I use the last parameter Start to Restricted State, and I change it’s default of *NO to *YES. This prevents any of the subsystems from starting, and I come back to a restricted state after an IPL. I find this very handy to run this command after I have loaded all my PTFs, and now I want to IPL to apply them all. Then when the IPL is complete, I can check to make sure everything applied, and then perform my save. I think you will also find some great uses of this command when you want to IPL but not have the system restart after the IPL.
Here are all the parameters.
Restart type (RESTART)
Specifies the point from which the initial program load (IPL) restarts when RESTART(*YES) or RESTART((*YES *IPLA)) are specified on the Power Down System (PWRDWNSYS) command. Specifying *SYS rather than *FULL can reduce the time required to restart the system. The initial (shipped) value for this parameter is *SYS.
Keylock position (KEYLCKPOS)Specifies the keylock position. A change to this attribute takes effect immediately. The following restrictions apply when the keylock position is being changed:
Hardware diagnostics (HDWDIAG)Specifies whether certain hardware diagnostics should be performed during the IPL. The list of diagnostics is pre-determined by the system and cannot be modified by the user.
On a partitioned system, this IPL attribute can only be changed from the primary partition or the hardware management console.
The initial (shipped) value for this attribute is *MIN.
Compress job tables (CPRJOBTBL)Specifies when the job tables should be compressed to remove excess unused entries. The Display Job Tables (DSPJOBTBL) command can be used to determine the number of unused entries in the job tables. Excessive unused entries can indicate that job tables need to be compressed. However, compression can take a significant amount of time during IPL. The initial (shipped) value for this attribute is *NONE.
Check job tables (CHKJOBTBL)Specifies when particular damage checks on the job tables should be performed. The initial (shipped) value for this attribute is *ABNORMAL.
Rebuild product directory (RBDPRDDIR)Specifies when the product directory information should be fully rebuilt. A full rebuild is required during the IPL following the install of the operating system. This attribute is overridden during that IPL. The initial (shipped) value for this attribute is *NONE.
Mail Server Framework recovery (MSFRCY)Specifies whether Mail Server Framework recovery is done during abnormal IPLs. The initial (shipped) value for this attribute is *NONE.
Display status (DSPSTS)Specifies whether the status of OS/400 IPL steps is displayed at the console during IPL. Status is not displayed during install IPLs or when the console is not powered on. The initial (shipped) value for this attribute is *ALL.
Start TCP/IP (STRTCP)Specifies whether the Start TCP/IP (STRTCP) command is automatically submitted at the completion of IPL and when the controlling subsystem is restarted to bring the system out of the restricted state. The STRTCP command is not submitted during install IPLs or when the system is starting to the restricted state. See the STRTCP command help for more information. The initial (shipped) value for this attribute is *YES.
Clear job queues (CLRJOBQ)Specifies whether or not to clear the jobs from all job queues. The initial (shipped) value for this attribute is *NO. This attribute is reset to its initial value after each IPL.
Clear output queues (CLROUTQ)Specifies whether or not to clear all output queues, thus removing all spooled output from the system. The initial (shipped) value for this attribute is *NO. This attribute is reset to its initial value after each IPL.
Clear incomplete joblogs (CLRINCJOB)Specifies whether or not to delete the joblogs for jobs that were active at the time of the last system power down. The initial (shipped) value for this attribute is *NO. This attribute is reset to its initial value after each IPL.
Start print writers (STRPRTWTR)Specifies whether or not print writers should be started at IPL time. The initial (shipped) value for this attribute is *YES. This attribute is reset to its initial value after each IPL.
Start to restricted state (STRRSTD)Specifies whether or not the system should be started to the restricted state, which means that only the system console will be active. The initial (shipped) value for this attribute is *NO. This attribute is reset to its initial value after each IPL.
June 10 to 12, COMMON Europe www.comeur.org in Vienna Austria.
July 20th OCEAN User group www.ocean400.org of Southern California.
September 18 – Vermont User Group www.vtmug.org
September 19 – The New England Midrange Users Group www.nemug.com of Rhode Island.
New IBM Hardware recently announced.
IBM last month announced some new hardware for Power Systems (The machine that used to be called an AS/400 or an iSeries). There are some really nice enhancements that I would like to summarize, most of them deal with improving performance, virtualization, and physical footprint. If you need help with hardware, contact either Glenn or Paul for help.
IBM has withdrawn the SDMC, and will continue to enhance and support the HMC. This is a great statement of direction, as the HMC is a great management interface for any Power Systems.
The EXP30 Ultra SSD I/O Drawer provides an ultra-dense and ultra-high-performance option for solid state drives (SSDs). Up to thirty 387 GB Enterprise Multi-Level Cell (eMLC) solid state drives can be installed inside the EXP30, only occupying 1U of 19-inch rack space. In addition, there is an imbedded pair of SAS disk controllers built directly into the disk draw. This attaches directly to the GX++ slots of your Power7 machine. Note, that you can’t use this if you have a P05 class machine.
A new low profile PCIe Gen2 SAS adapter (#ESA2) for the 2U PCIe Riser card of the Power 720/740. It supports SSDs providing RAID 0, 5, 6 and 10 capabilities using a single PCIe slot. There is also a full high version (#ESA1) is available for taller Power Systems PCIe Gen2 slots. Though its overall SSD performance capacity is lower than that of the #5913 PCIe2 1.8GB Cache RAID SAS Adapter it only uses one PCIe slot, and and a lower cost than it’s older brother the 5913. Be careful, as these controllers have ZERO write cache.
SSD capacity and performance are doubled for SFF SAS bays with a 387 GB eMLC solid state drive (#ES0A/ES0B/ES0C/ES0D). These SSDs have twice the capacity of the existing 177GB SSDs (#1775/1787/1793/1794) but are also more money.
The new PCIe2 4-port 1Gb Ethernet Adapter offers four copper/UTP Ethernet ports at a significantly lower price than the existing 4-port UTP adapters (#5271/5717).
A new 4-port 1Gb LAN adapter, which will replace the 2-port 1Gb LAN adapter, currently in the “C” models of Power 720/740 machines.
IBM plans that POWER6 servers running the IBM i release following 7.1 will not support the older, slower HSL/RIO attached I/O drawers. This planning statement does not impact POWER7 clients or IBM i 7.1 clients. POWER7 servers do not support HSL/RIO I/O drawers and there is no change to IBM i 7.1 HSL/RIO support. IBM i clients who have an HSL/RIO-attached I/O drawer or tower such as the #5094/5294, #0595/5095, #0588/5088, #5790, or #5791/5794 should plan on moving to newer 12X-attached I/O drawers on their POWER6 server before moving to the release following IBM i 7.1. There is also an option to have these towers owned by a 6.1 or 7.1 host, and then virtualize them to the next release of the operating system with IBM i hosting IBM i.
We can help you make the most of your investment, because we know and understand the hardware, the direction, and what will become obsolete. Understanding this, insures that when you use iTech Solutions for your IBM Power System purchases, you will be able to leverage your investment into the future.
|Release levels and PTFs|
People are always asking me how often they should be performing PTF maintenance, and when is the right time to upgrade their operating system. I updated this article from last month with the current levels of PTFs. Let’s look at PTFs. First, PTFs are Program Temporary Fixes that are created by IBM to fix a problem that has occurred or to possibly prevent a problem from occurring. In addition, some times PTFs add new functionality, security, or improve performance. Therefore, I am always dumbfounded as to why customers do not perform PTF maintenance on their machine at least quarterly. If IBM has come out with a fix for your disk drives, why do you want to wait for your disk drive to fail with that problem, only to be told that there is a fix for that problem, and if you had applied the PTF beforehand, you would have averted the problem. Therefore, I think a quarterly PTF maintenance strategy is a smart move. Many of our customers are on our quarterly PTF maintenance program, and that provides them with the peace of mind of knowing their system is up to date on PTFs. Below is a table of the major group PTFs for the last few releases. This is what we are installing for our customers on iTech Solutions Quarterly Maintenance program.
7.1 6.1 V5R4 V5R3
Cumul. Pack 12115 12122 12094 8267
Tech. Refresh 4
Grp Hipers 60 120 177 169
DB Group 14 26 33 24
Java Group 8 19 29 23
Print Group 5 24 46 20
Backup/Recov. 14 27 44 33
Blade/IXA/IXS 9 23 15 –
HTTP 13 25 31 17
TCP/IP 6 14 21 16
Security 17 30 25
High Availability 1 1
The easiest way to check your levels is to issue the command WRKPTFGRP. They should all have a status of installed, and you should be up to the latest for all the above, based upon your release. Now there are more groups than the ones listed above, but these are the general ones that most people require. We can help you know which group PTFs you should be installing on your machine based upon your licensed programs. Here is a nice tidbit. The Cumulative PTF package number is broken down as YDDD, where Y is the year and DDD is the day it was released. Therefore, if we look at the cumulative package for V5R4, the ID is 9104. We can determine that it was created on the 104th day of 2009, which is April 14, 2009. Look at your machine and this will give you a quick indication of just how far out of date in PTFs you may be. I left V5R1 & V5R2 off the list, because if you are on V5R1 or V5R2, you don’t need to be worrying about PTFs, you really need to be upgrading your operating system. The same can be said for V5R3, but there are still customers who are on those releases.
If you have an HMC, you should be running V7R7.4 with SP2 or V7R7.5 with efix MH01312. If your HMC is a C03, then it should stay at V7R3.5 SP4.
For your Flexible Service Processor (FSP) that is inside your Power 5 or Power5+ (520, 515, 525, 550, 570), the code level of the FSP should be 01_SF240_417. Power 6 (940x M15, M25, & M50 machines, and 8203-E4A & 8204-E4A) customers should be running EL350_118. For Power6 (MMA, 560, and 570 machines) your FSP should be at EM350_118. If you have a Power6 595 (9119) then you should be on EH350_120.
Depending on which POWER7 model & generation (B or C). The firmware level is AL730_078 for 8202-E4B & 8205-E6B (710, 720, 730, 740), AL730_078 for 750 (8233-E8B) & 755 (8236-E8C). Use AM730_078 for 770 (9117-MMB) & 780 (9179-MHB). The firmware level is AL740-077 for 8202-E4C & 8205-E6C (710, 720, 730, 740). Use AM740_077 for 770 (9117-MMC) & 780 (9179-MHC).
If you need help with upgrading your HMC or FSP just give us a call. We will be happy to perform the function for you or assist you in doing it. Contact Pete Massiello.