|
I have a Notes document with the following in it. May look bug ugly coming in through the email list. I can paste it into a notes database if you're a Notes shop, or maybe a word document if you are not. And send the attachment off list, if you so desire. As early as possible - 1 to 2 months prior. Order any new hardware, new software or new levels of operating systems. This does not include PTF's. As soon as the new hardware comes in, call IBM and notify them. Unless it is a customer installed upgrade they will want to inventory the new equipment. As soon as the new software comes in run it through the Software Installation process to check for missing program products. See the manual 'Software Installation'. Two weeks prior - Two Fridays before downtime Get a rough estimate of downtime. If it has some major changes planned, such as a hardware or OS upgrade, and might need additional personnel, line them up now. Send out an email to the department reminding them of the downtime and who is scheduled to work. Initialize all tapes needed for downtime. I am open to the idea of putting lots of detail here if desired. One week prior - The Friday before downtime Send out an email to the department reminding them of the downtime and who is scheduled to work. On GDISYS do an ENDRMTSPT late on Friday afternoon in case anyone had IBM dial in recently. Monday before downtime At this time we used to apply existing PTF's permanently. IBM recommends this as a space saver. However we don't do this for a number of reasons: 1) We do not want to apply Domino or LEI ptf's permanently. Therefore on AS/400's with those products you cannot use LICPGM(*ALL), you have to apply each licensed program seperately. Turns out, that all of our iSeries are running Domino at this time. Therefore we had to apply each individual program product. 2) Often we have test ptf's applied. Applying those permanently is a no-no. IBM may send us a new ptf instead of a refresh. If the ptf is permanently applied the only way to remove it is to remove the LPP. Not worth it. Go to the web site: http://www-912.ibm.com/s_dir/slkbase.nsf/recommendedfixes QSF98530 Latest cum _________________ Next cum date _________________ You need to check out the cum cover letter to see what level of cum is out. Compare this to the level of cum on each installed 400 with the command DSPPTF The first TL line should be what cum we are on. For example TL02071 means we are on year 02 and julian day 071 level of cum. GDI Cum ______________ Current (Y/N) __ GDIHQ Cum ______________ Current (Y/N) __ GDISYS Cum ______________ Current (Y/N) __ GDWEB Cum ______________ Current (Y/N) __ MAILTWO Cum ______________ Current (Y/N) __ Go to the web site: http://www-912.ibm.com/n_dir/nas4apar.nsf/51d11a683a56a5cc862564c000763b23/5bec79aa96bcec4e86256eb6003c7d7f?OpenDocument&Highlight=2,bpcs V5R3 PTF's required _____________________________________________________________ We'll call these 'BPCS -530' Read the informational APAR carefully. There will probably be some manual steps you'll have to take to take advantage of these ptf's. Go to the web site: http://www-1.ibm.com/servers/eserver/iseries/access/casp.htm Fill in the boxes below. You will use these numbers later to order them. Version of Client Access (next table) Service Pack Client Access Express V5R3 CAE530 Go to the web site: http://as400service.rochester.ibm.com/supporthome.nsf/Document/10000031 Select 'All Group PTFs by Release'. Select R530. Review the list carefully. If any of them sound sexy to you then update the following table, and the downtime instructions. V5R3 PTF's required SF99529, SF99503, SF99282, SF99275, SF99269, SF99185, SF99139, SF99099 ___________________________________ Go to the web site for Domino ptf's: http://www-1.ibm.com/servers/eserver/iseries/domino/support/ptf.htm Check at the bottom to see if there are any PTF's listed for 5722-999, 5722-SS1 or 5722-TC1 which are NOT available on a cum. Write these down. We'll call these 'dom ptfs-530'. Go to the web site for Sametime ptf's: http://www-1.ibm.com/support/docview.wss?rs=477&context=SSKTXQ&q=ptf+iseries&uid=swg21089996&loc=en_US&cs=utf-8&lang=en http://www-1.ibm.com/support/docview.wss?rs=0&q=iseries%2Bsametime&uid=sim1a862d335ed543b2885256c40005a192a Check to see if there are any ptf's for V5R3 of the operating system which are NOT available on a cum. Add these to the following list. V5R3 PTF's required __________________________________________________________ __________________________________________________________________________________ Go to the web site: http://www-912.ibm.com/supporthome.nsf/document/22645318 To get a list of DASD fixpacks. Although it seems like it's been awhile since this has been updated. Go to this web site to get a list of TCP/IP stack ptf's: http://www-912.ibm.com/s_dir/slkbase.nsf/c31a59769d9825d586256839004eeebe/d890cb0927aa56ad86256a3100633d95?OpenDocument PTF's required ____________________________________________________________________ ____________________________________________________________________ Go to this web site and shoot through all applicable products: http://www-912.ibm.com/s_dir/slkbase.nsf/recommendedfixes PTF's required _________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ Not only do we use iSeries Navigator to compare PTF's on systems, but we used to use it to distribute them. Now we will just reorder them. The reason we do that is to allow all systems to use the ftp download method. Lot less manual labor. Use iSeries Navigator to compare PTF's with all machines. Open up Management Central. Open up Endpoint Systems. Right click on GDISYS. Select Fixes. Select Compare and Update. Your model system should be GDISYS. Your target systems should be: GDI, GDIHQ, GDIHQ2, GDWEB and MAILTWO. Deselect 5763XC1 - Client Access/400 for Windows 3.1 Select 'Show compare results only'. If prompted to refresh inventory, please do so. Open up Management Central. Open up task activity. 'Collect Inventory' is the task you want to open up. During this time you should also have another window which opened when you started the compare. The title of this window is Compare Results. When the activity is done let's focus on this window. Check out each system for missing PTF's. Ignoring any 'marker' ptf's. These marker PTF's begin with: TAP, TCP, TLP. Examples include: tap006, tcp006, tlp006. Normally machines which have the PTF, like GDI and GDISYS were once on a beta version of the OS. Machines which do not have the marker ptf's, like GDIHQ, were never on a beta version of the OS. It might be advisable to pick another system as a model system and repeat these steps. This will search for PTF's which were sent directly to a development machine and might not be on GDISYS. Write down all Missing/Extra ptf's: _______________________________________________________________________________________ _______________________________________________________________________________________ _______________________________________________________________________________________ _______________________________________________________________________________________ _______________________________________________________________________________________ Now we'll ftp downloads of these ptf's. Sometimes IBM makes you order the cume separately from the rest. Therefore you might have to do two orders. http://www-912.ibm.com/supporthome.nsf/document/10000083 You might have to first register at http://as400service.rochester.ibm.com/ - Using known ptf numbers - Advanced options - Enter in the ptf numbers - Check the following: - Include all requisite PTFs - For FTP, or CD_ROM media, include requisite PTFs so they can be applied to multiple systems - Reorder the ptfs even if they exist on the system - Uncheck the following: - Order only the PTFs required for products that exist on the system - Uncheck Immediate Download over the Internet (HTTP) - Change our line speed to T1 or faster - Check only Download CD-ROM image to FTP server (FTP) - Do NOT check Mail order on CD-ROM if the total size exceeds the limits you selected above - Select Western Hemisphers Submit order now You will get an email with ftp instructions. While you are waiting for the email on each iSeries do the following (some of these steps might already be done): md '/fixes' CRTDEVOPT DEVD(OPTVRT01) RSRCNAME(*VRT) ONLINE(*YES) TEXT('Virtual optical drive for image catalog') VRYCFG CFGOBJ(OPTVRT01) CFGTYPE(*DEV) STATUS(*ON) CRTIMGCLG IMGCLG(PTFCATALOG) DIR('/fixes') TEXT('PTF image catalog') We're probably still waiting on the email(s). While doing so, we will order all of the above ptf's on media as a backup. http://service.software.ibm.com/as400.us.reg/orderptfmedia?lang=english|1 You might have to first register at http://as400service.rochester.ibm.com/ Set delivery priority to 1. Set address 2 to DOCK 108. Set address 3 to PTF's. If you have to order the cume separate, then one CUME and the other OTHER PTF'S. Set order number to PTF. If you have to order the cume separate, then one CUME and the other PTFS. You will get 3 emails from IBM for each order placed. The first email will be a confirmation of your order. This is where we match up our order number, (PTFS or CUME/PTFS) and the IBM order numbers. The second email will tell you the assigned Airborne tracking number. The third email will repeat this information along with the time and date that Airborne picked up the order. Now, if you don't receive the orders in a timely fashion do one or more of the following probably in this order: track the order via WWW.AIRBORNE.COM, call the mail room if we've supposed to have received it, reorder, or just trust the FTP download. Once you get the email and ftp the files down into this '/fixes' directory you'll have to do the following for each binary file(s) received: ADDIMGCLGE IMGCLG(PTFCATALOG) FROMFILE('/fixes/TheFtpFileNameHere') TOFILE(*FROMFILE) REPLACE(*INSERT) You might be able to do the following on a system to get the ftp'ed file from a central system. Let's say you ftp'ed them to GDISYS. Then on GDI you'd do: MD '/QFileSvr.400/GDISYS' ADDIMGCLGE IMGCLG(PTFCATALOG) FROMFILE('/QFileSvr.400/gdisys/fixes/C5227074_05') TOFILE(*FROMFILE) REPLACE(*INSERT) replacing C5227074_05 with whatever you ftp'ed down. When you've repeated this for each binary you've downloaded then you can do: LODIMGCLG IMGCLG(PTFCATALOG) DEV(OPTVRT01) VFYIMGCLG IMGCLG(PTFCATALOG) TYPE(*PTF) SORT(*YES) WRKIMGCLGE PTFCATALOG GO PTF 8. Install program temporary fix package Install Options for Program Temporary Fixes System: GDI Type choices, press Enter. Device . . . . . . . . . OPTVRT01 Name, *SERVICE Automatic IPL . . . . . . N Y=Yes N=No Restart type . . . . . . *SYS *SYS, *FULL PTF type . . . . . . . . 1 1=All PTFs 2=HIPER PTFs and HIPER LIC fixes only 3=HIPER LIC fixes only 4=Refresh Licensed Internal Code Other options . . . . . . N Y=Yes N=No <enter> Let it do it's thing. When back to the menu; F3=Exit LODIMGCLG IMGCLG(PTFCATALOG) DEV(OPTVRT01) OPTION(*UNLOAD) WRKIMGCLGE PTFCATALOG 4=Remove, repeat for each entry VRYCFG CFGOBJ(OPTVRT01) CFGTYPE(*DEV) STATUS(*OFF) WRKLNK '/fixes/*' Delete any files that you are completed with. Verify that we have latest versions of Trend Micro products. The pattern files get automatically updated. This leaves us three areas of concern. Patches, the Scan Engine, and the software itself. To display what Scan Engine we have do the following. Carefully browse the log.nsf around the time of the last starting of the server. You should see something like the following: 02/07/2004 19:19:40 Trend ScanMail(R) Mail Scanner, Release 2.51, June 2002 02/07/2004 19:19:40 MailScan Build 1079, Jan 23 2003 10:34:19 02/07/2004 19:19:42 RepScan Using VSAPI 6.810-1024 02/07/2004 19:19:42 Repscan is using pattern file version 757 The first line is the version of Scan Mail we are using. The third line is the version of the scan engine we are running. The fourth line is the pattern file loaded when the server was last started. This may have been updated while the server continued to run therefore we may have an even newer pattern file loaded. This is not important to these immediate downtime preparations. Go to http://www.antivirus.com/ Select Support, Update Center, Scan Mail for Lotus Notes, Software itself: Write down the version of Product Available ____________. If this is different than the version we are running , download it and apply it. Sometimes it comes packaged with an older version of the scan engine and you might have to download a newer version of the scan engine seperately. If prompted our complete entire serial number is (edited for security). The first 6 characters are (edited for security). Scan Engine: Write down the version of Scan Engine available: ____________ If this is different than the scan engine we are running, download it and apply it. Patches: If the date on this is applicable then download this and apply it. If you've done a Trend version upgrade, for example from 2.51 to 2.6, then you should test with the sample virus. To do so complete the following: Right click on your virus engine in your PC tray and select I/O scan off. Go to the following web site: http://www.trendmicro.com/en/security/test/overview.htm and download the Eicar test virus. Send that in an email to an associate on the same mail server as you've upgraded. In the email they should get a virus notification. If they fail to do so, call Trend support. Last time it was a serial number issue. Turn on your virus engine in your PC tray. Monday or Tuesday before downtime There are several documents on //GDSNT/DOWNTIME we need to modify. But first, let's make sure we have archive copies of all of the previous downtimes documents. Right click on Start. Select Explore. Click on the dropdown to the right of Address. Select My Network Places. Expand My Network Places. Expand Entire Network. Expand Microsoft Windows network. Expand Dekko-1. Expand GDSNT. Open up Downtime. Open up the archive directory. See if there is a zip file for the previous downtime, for example ARCH20011214.zip. If not, create one and store all documents in the Downtime directory in it. For a list of these documents and what they are, click -->>. Print off one copy of downtime.doc. Burst the copy by CPU. On the first page of each CPU write down the password for QSECOFR. Store these in a secure place. On GDIHQ we need to verify the list of job queue's which will be held or released. The commands JOBQHLD and JOBQRLS will be used during downtime. We need to update the file of exceptions. UPDDTA ROUTINES/JOBQCTL. An H record means do not hold this library when holding all others. An R record means do not release this library when releasing all others. Wednesday or Thursday before downtime - or as soon as you have all Airborne packages Once you've received all of the Airborne packages sort them by the CPU in Address 3. If you've ordered a cume then it should be on it's own set of CD's. The groups and individual ptf's you ordered should be on the other set. To see what is on that set pop the first CD of that set into your PC. Open the README directory. Open the ORDLIST.TXT file. Verify that you've received all that you ordered. Secure them in the computer room. Make sure that people assigned to admin building know how to work all tape drives. Friday, day of downtime Remove Thursday night tapes. Clean all tape drives. Get tapes ready for regular weekend backup. Monday following downtime On the remaining 400's Look for any APPC devices for the old machine. Look for any remote controllers for the old machine. WRKLNK '/QFileSvr.400/*' WRKRDBDIRE WRKCFGL and check out QAPPNRMT. Clean up WRKDIRE CFGDSTSRV and remove the old routing table and distribution queue. Clean up file ROUTINES/SYSNAMEALL Clean up file GDISYS/AVAILTIME On all 400's do the following: WRKMSGD MSGF(ROUTINES/SCNMSGF) and assign new downtime. How long did the IPL take? On each system: DSPLOG PERIOD((*AVAIL *BEGIN)) MSGID(CPF0930 CPF0934) UPDDTA ROUTINES/SYSDOWN Page Up twice should go to the last record. Verify, then change the date/time of the start and end of the IPL. STRQMQRY QMQRY(ROUTINES/SYSDOWNQM1) SETVAR((PROMPTDATE '''2003-05-01''')) That's three apostrophe's on both sides of the date. Write down these new durations on the downtime instructions so that we may modify accordingly the next downtime. Check for license keys: DSPLOG PERIOD((*AVAIL *BEGIN)) MSGID(CPI9E75 CPI9E77 CPF9E7D CPF9E72 CPF9E17) Clean up the image catalogs WRKOBJ OBJ(*ALL) OBJTYPE(*IMGCLG) For each entry: LODIMGCLG IMGCLG(...) DEV(OPTVRT01) OPTION(*UNLOAD) WRKIMGCLGE IMGCLG(...) 4=Remove DLTIMGCLG IMGCLG(...) KEEP(*NO) WRKLNK '/fixes/*' 4=Remove for each file, leaving only the directory '/fixes' there. On GDISYS do a UPDDTA ROUTINES/SYSDOWN and key in this last downtime. You will get that information by checking messages for one of the following: QSYSOPR, QSECOFR, PEGGY, CHRIS, ROB. Investigate the DSPLOG to determine when tape changes occurred. This will allow us to give better time estimates. In the DSPLOG look for when a message(s) appeared telling you that a tape change was needed. Then look for the matching message(s) when the message was responded to. The difference between these two is slack time and may throw our save estimates way off. For example if we started a save at TLA the message came up to change tapes while we were out to dinner then we don't want to count all that time. Write down these times - important! The log will not last 60 days! We need these times to use in the next periods downtime instructions to give accurate estimates. For example, DSPLOG PERIOD((1700 020802) (0800 021002)) MSGID(CPA4088) and got: Load next tape volume on device TAP04. (C G) Load next tape volume on device TAP04. (C G) Load next tape volume on device TAP04. (C G) Load next tape volume on device TAP04. (C G) The first message was when it asked for another tape. The second message was when we put in the tape and answered the message. The third message was when it asked for another tape. The fourth message was when we put in the tape and answered the message. We can position our cursor on each message and get the date and time. There was a 6 minute lapse from when we needed the first tape and when we put in the tape and answered the message. There was a 8 minute lapse from when we needed the next tape and when we put in the tape and answered the message. On GDISYS add GDISYS and ROUTINES to your library list. CALL DSPDWNALLC to refresh the list of downtimes. View Query ROUTINES/SYSDOWN to check list. Modify the Query SYSDOWNLST to just select this last downtime. Print this Query off. Give this printout to Peggy Stolte. Print another copy and store these with the downtime instructions for this last downtime. Staple the list of tape changes to the query SYSDOWNLST. Store this with the master, unburst copy of downtime instructions. There is one document on //GDSNT/DOWNTIME we need to modify. But first, let's make sure we have archive copies of all of the previous downtimes documents. Right click on Start. Select Explore. Click on the dropdown to the right of Address. Select My Network Places. Expand My Network Places. Expand Entire Network. Expand Microsoft Windows network. Expand Dekko-1. Expand GDSNT. Open up Downtime. Open up the archive directory. See if there is a zip file for this previous downtime, for example ARCH20031017.zip. If not, create one and store all documents in the Downtime directory in it. For a list of these documents and what they are, click -->>. Now modify the DOWNTIME.DOC document. And put the new save/reclaim times in there. Change the password for QSECOFR on all 400's. Store the list of the old QSECOFR passwords in a sealed envelope with the tapes off site. After all, it will do us no good to try to restore from these tapes if we don't know the password to QSECOFR. Assume that we are restoring in a new building because the systems building is a pile of ashes. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Condon, Mike" <M1C@xxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 10/29/2004 03:28 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> cc Fax to Subject PTF Documentation/Training I'm looking for a good resource or resources for training my reports on the PTF/APAR story, what they do, how to acquire them, how to apply them, etc. Any suggestions on exceptional resources for use as training/reference materials? -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
