|
Not necessarily. As I understand it, AM Generals boxes are basically all alike. That's got to be easier to admin than a few hundred unique boxes. Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121
-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Monday, October 16, 2006 10:15 AM To: Midrange Systems Technical Discussion Subject: Re: MIDRANGE-L Digest, Vol 5, Issue 1976 I think IBM has a project called "Multiples". These are the SERIOUS players. Like the AM Generals that buy the i5's by the THOUSANDS. Be a bear if you find out they get by with 1 or 2, eh? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Ashok.Dave@xxxxxxxxxxxxxxx Sent by: midrange-l-bounces+rob=dekko.com@xxxxxxxxxxxx 10/16/2006 09:59 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To midrange-l@xxxxxxxxxxxx cc Subject Re: MIDRANGE-L Digest, Vol 5, Issue 1976 Thanks guys, this is great feedback. We have 109 systems (mixture of LPARs and separate machines) and only four sys admins, two at a junior level. I am trying to justify more headcount. Our ops (3 shifts of 3) manage day to day ops requirements. We have no printing. --------------------------------------------- Ashok Dave Operations Manager, LeasePlan Infrastructure Services, Leaseplan House, Level 2, Central Park, Leopardstown, Dublin 18, Ireland -------------------------------------------- midrange-l-request@xxxxxxxxxxxx Sent by: midrange-l-bounces@xxxxxxxxxxxx 16/10/2006 14:54 Please respond to midrange-l@xxxxxxxxxxxx To midrange-l@xxxxxxxxxxxx cc Subject MIDRANGE-L Digest, Vol 5, Issue 1976 Send MIDRANGE-L mailing list submissions to midrange-l@xxxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit http://lists.midrange.com/mailman/listinfo/midrange-l or, via email, send a message with subject or body 'help' to midrange-l-request@xxxxxxxxxxxx You can reach the person managing the list at midrange-l-owner@xxxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of MIDRANGE-L digest..." *** NOTE: When replying to this digest message, PLEASE remove all text unrelated to your reply and change the subject line so it is meaningful. Today's Topics: 1. Re: iSeries Support Question (rob@xxxxxxxxx) 2. Re: iSeries Support Question (rob@xxxxxxxxx) 3. RE: iSeries Support Question (Burns, Bryan) 4. Re: iSeries Support Question (Richard ECUYER) 5. RE: Disk failure procedure (Wilt, Charles) 6. RE: Disk failure procedure (Ingvaldson, Scott) ---------------------------------------------------------------------- message: 1 date: Mon, 16 Oct 2006 09:44:54 -0400 from: rob@xxxxxxxxx subject: Re: iSeries Support Question We had 2 dozen as/400's at one time. No problem. I did the "high tech" stuff. Coworker did the mundane like user profiles, backups. Note, she hasn't written a line of code, including CL, in years. We've consolidated down to 4 now. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Ashok.Dave@xxxxxxxxxxxxxxx Sent by: midrange-l-bounces@xxxxxxxxxxxx 10/13/2006 06:28 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To midrange-l@xxxxxxxxxxxx cc Subject iSeries Support Question Hello all, does anyone know of any benchmarking or best practice regarding number of system admin. staff required per system? Eg. is the ratio 5 systems/sysadmin, or 9 systems per sysadmin, etc. thanks Ashok -- 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. ------------------------------ message: 2 date: Mon, 16 Oct 2006 09:48:01 -0400 from: rob@xxxxxxxxx subject: Re: iSeries Support Question Then again, we have NO system printers, users submit their own batch jobs. Like, the payroll submits their check run, AP does their own, plant clerks do their period end, etc. Now, if your definition of system admin requires they do that... Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Ashok.Dave@xxxxxxxxxxxxxxx Sent by: midrange-l-bounces@xxxxxxxxxxxx 10/13/2006 06:28 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To midrange-l@xxxxxxxxxxxx cc Subject iSeries Support Question Hello all, does anyone know of any benchmarking or best practice regarding number of system admin. staff required per system? Eg. is the ratio 5 systems/sysadmin, or 9 systems per sysadmin, etc. thanks Ashok -- 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. ------------------------------ message: 3 date: Mon, 16 Oct 2006 08:49:15 -0500 from: "Burns, Bryan" <Bryan_Burns@xxxxxxxxxxxx> subject: RE: iSeries Support Question So what's your title Rob? You seem to be quite knowledgeable in both coding and operations/administration. Bryan ECHO, Inc. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx Sent: Monday, October 16, 2006 8:45 AM To: Midrange Systems Technical Discussion Subject: Re: iSeries Support Question We had 2 dozen as/400's at one time. No problem. I did the "high tech" stuff. Coworker did the mundane like user profiles, backups. Note, she hasn't written a line of code, including CL, in years. We've consolidated down to 4 now. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Ashok.Dave@xxxxxxxxxxxxxxx Sent by: midrange-l-bounces@xxxxxxxxxxxx 10/13/2006 06:28 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To midrange-l@xxxxxxxxxxxx cc Subject iSeries Support Question Hello all, does anyone know of any benchmarking or best practice regarding number of system admin. staff required per system? Eg. is the ratio 5 systems/sysadmin, or 9 systems per sysadmin, etc. thanks Ashok ------------------------------ message: 4 date: Mon, 16 Oct 2006 15:32:41 +0200 from: "Richard ECUYER" <recuyer@xxxxxxx> subject: Re: iSeries Support Question solar time perhaps ? ----- Original Message ----- From: "Turnidge, Dave" <DTurnidge@xxxxxxxxxxxxxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Monday, October 16, 2006 3:15 PM Subject: RE: iSeries Support QuestionWOW!! 27x7!! -----Original Message----- From: midrange-l-bounces+dturnidge=oldrepublictitle.com@xxxxxxxxxxxx[mailto:midrange-l-bounces+dturnidge=oldrepublictitle.com@midr ange.com]On Behalf Of Jones, John (US) Sent: Monday, October 16, 2006 8:14 AM To: Midrange Systems Technical Discussion Subject: RE: iSeries Support Question Oh, it's real time. If I happened to be awake I could callat 3AM onChristmas Day and get an operator. I've gotten calls fromthem at 1AMin the past when there were issues with backups. The service provider we use has a fair number of otheriSeries clients,including other global companies. They themselves have multiple facilities and teams of staff, not just a couple of individuals. At least one of their technical staff monitors this listand replies onoccasion. John A. Jones, CISSP Americas Information Security Officer Jones Lang LaSalle, Inc. V: +1-630-455-2787 F: +1-312-601-1782 john.jones@xxxxxxxxxx -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jonathan Mason Sent: Monday, October 16, 2006 7:56 AM To: 'Midrange Systems Technical Discussion' Subject: RE: iSeries Support QuestionOperations - 27x7 monitoring for system messages, tape handling, backupsand offsite tape rotation, scheduledprocedures, some calls to IBM support (mostly forhardware issues likefailed disks). Is that real time or what Operations would have you believe... ;-) -- This is the Midrange Systems Technical Discussion(MIDRANGE-L) mailinglist 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 amoment to review the archives athttp://archive.midrange.com/midrange-l.This email is for the use of the intended recipient(s) only. If you have received this email in error, please notify the senderimmediatelyand then delete it. If you are not the intended recipient,you must notkeep, use, disclose, copy or distribute this email withoutthe author'sprior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carryout your ownvirus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. The information contained in this communication may beconfidential and maybe subject to the attorney-client privilege. If you are the intended recipient and you do not wish to receive similar electronic messages from us in the future then please respond to the sender tothis effect.-- This is the Midrange Systems Technical Discussion(MIDRANGE-L) mailinglist 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 amoment to review the archives athttp://archive.midrange.com/midrange-l.-- This is the Midrange Systems Technical Discussion(MIDRANGE-L) mailing listTo 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.------------------------------ message: 5 date: Mon, 16 Oct 2006 09:52:53 -0400 from: "Wilt, Charles" <CWilt@xxxxxxxxxxxx> subject: RE: Disk failure procedure Nope, IIRC the concurrent maintenance capability was a function of the drive cage. Whereas the RAID capability was a function of the disk controller card. Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf OfHaase, Justin C.Sent: Monday, October 16, 2006 9:07 AM To: Midrange Systems Technical Discussion Subject: RE: Disk failure procedure Thought if it had RAID it was concurrent-enabled. -- Justin C. Haase - iSeries System Engineer IBM Certified Systems Expert - System i Kingland Systems Corporation -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles Sent: Monday, October 16, 2006 8:07 AM To: Midrange Systems Technical Discussion Subject: RE: Disk failure procedure Note that concurrent maintenance was optional on the 270. You may have to shut down the box to replace the drive. Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf OfHaase, Justin C.Sent: Monday, October 16, 2006 9:00 AM To: Midrange Systems Technical Discussion Subject: RE: Disk failure procedure Concurrent maint Remove DDxxx Concurrent maint Add DDxxx Disk recovery menu Rebuild disk unit data Select disk to rebuild Wait an hour WRKDSKSTS, F11 to ensure no longer "FAILED" and now "ACTIVE" Done! Parity will auto-recover as will the ASP part. -- Justin C. Haase - iSeries System Engineer IBM CertifiedSystems Expert- System i Kingland Systems Corporation -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren Sent: Saturday, October 14, 2006 6:19 PM To: Midrange Systems Technical Discussion Subject: Re: Disk failure procedure Yes. I checked the system builder, too. I was justworried that Iwas going to pull the wrong unit. OK, with that cleared up, are there instructions forreplacing a diskunit somewhere? I looked at the Backup and Recoveryguide and theSystem Builder but I don't see any step by step. I guess Ineed to do"Concurrent Maintenance" on the unit to remove it. Put thenew one inand then ? Just add it back into the ASP and start parityprotection?Pete Haase, Justin C. wrote:And looking in my handy-dandy system builder... D05 is the fifth from the left on the skinny 270. D01 ison the leftand D06 is on the right. If you have the expansion attached, the disk numberingstarts at thebottom of that with D08 and goes to the top with D20. -- Justin C. Haase - iSeries System Engineer IBM CertifiedSystems Expert- System i Kingland Systems Corporation -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf OfPete HelgrenSent: Saturday, October 14, 2006 4:50 PM To: Midrange Systems Technical Discussion Subject: Disk failure procedure I have a disk that has failed on my model 270. I am justa littlefuzzy on the the replacement. I have another drive that I can install. My problem is that I don't know which driveto replace.System Operator message queue has the following: Unit 6 with device parity protection not fully operational. Cause . . . . . : Unit 6 is part of a disk unitsubsystem withdevice parity protection. Unit 6 requires service. Thedata has beensaved. Reduced performance, machine checks, and possibledata loss canoccurif this condition is not corrected. The following information identifies the unit requesting service: Disk serial number: 68-0CF6ADE Disk type: 6718 Disk model: 070 Device resource name: DD006 Disk status shows the following: Serial Resource Hardware ASP Unit Number Type Model Name Status 1 1 02-35300 6718 074 DD001 DPY/Unprotected 1 2 02-015B2 6718 074 DD004 DPY/Unprotected 1 3 02-03760 6718 074 DD002 DPY/Unprotected 1 4 02-03423 6718 074 DD003 DPY/Unprotected 1 5 68-0D0E009 6718 070 DD005 DPY/Unprotected 1 6 02-0CF6ADE 6718 070 DD006 DPY/Failed Do the unit #'s listed here represent the position in the"cage" thesedrives are in? The only reason I ask is that when Ilook at thehardware details for unit #6 I see the following: Type. . . . . . . . . . . . : 6718 Model . . . . . . . . . . . : 070 Level . . . . . . . . . . . : 5 Serial Number . . . . . . . : 02-0CF6ADE Resource Name . . . . . . . : DD006 Physical location: Frame ID . . . . . . . . . : 1 Card position. . . . . . . : D05 Device position. . . . . . : "Card Position" D05 seems to point me to the 5th slot inthe cage,rather than the 6th. I don't want to yank the wrong one. Also, where do I find the "serial number" that is listed in thedetail?The serial number reported in QSYSOPR message queue isdifferent thanthe detail on disk status (68-0CF6ADE .vs 2-0CF6ADE) Isit on thedrive itself so I can double check the it before I replace it? Thanks. Pete Helgren -- This is the Midrange Systems Technical Discussion(MIDRANGE-L) mailinglist To post a message email: MIDRANGE-L@xxxxxxxxxxxx Tosubscribe,unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting,please takea moment to review the archives athttp://archive.midrange.com/midrange-l.CONFIDENTIALITY NOTICE: This e-mail communication, includingattachments, is covered by the Electronic CommunicationsPrivacy Act,18 U.S.C. 2510-2521, is confidential, and may be legallyprivileged.If you are not the intended recipient or believe youreceived thiscommunication in error, please reply to the senderindicating thatfact and delete the copy you received. In addition, retention, dissemination, distribution, copying, or otherwise use of the information contained in this communication is strictlyprohibited.Thank you.-- This is the Midrange Systems Technical Discussion(MIDRANGE-L) mailinglist To post a message email: MIDRANGE-L@xxxxxxxxxxxx Tosubscribe,unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting,please takea moment to review the archives at http://archive.midrange.com/midrange-l. CONFIDENTIALITY NOTICE: This e-mail communication, including attachments, is covered by the Electronic CommunicationsPrivacy Act,18 U.S.C. 2510-2521, is confidential, and may be legallyprivileged.If you are not the intended recipient or believe youreceived thiscommunication in error, please reply to the senderindicating thatfact and delete the copy you received. In addition, retention, dissemination, distribution, copying, or otherwise use of the information contained in this communication is strictlyprohibited.Thank you. -- 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 takea moment to review the archives at http://archive.midrange.com/midrange-l.-- This is the Midrange Systems Technical Discussion(MIDRANGE-L) mailinglist 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. CONFIDENTIALITY NOTICE: This e-mail communication, including attachments, is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential, and may be legally privileged. If you are not the intended recipient or believe you received this communication in error, please reply to the sender indicating that fact and delete the copy you received. In addition, retention, dissemination, distribution, copying, or otherwise use of the information contained in this communication is strictly prohibited. Thank you. -- 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.------------------------------ message: 6 date: Mon, 16 Oct 2006 08:52:01 -0500 from: "Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx> subject: RE: Disk failure procedure Use iSeries Navigator! Go to your system > Configuration and Service > Hardware > Disk Units > By Location. Right click Frame/Unit Fr01 and click Graphical View. Choose the Active Disk Unit view and you can highlight each unit and see it's position. The bad unit might even be in red, I don't recall. Regards, Scott Ingvaldson iSeries System Administrator GuideOne Insurance Group -----Original Message----- date: Sat, 14 Oct 2006 15:49:54 -0600 from: Pete Helgren <Pete@xxxxxxxxxx> subject: Disk failure procedure I have a disk that has failed on my model 270. I am just a little fuzzy on the the replacement. I have another drive that I can install. My problem is that I don't know which drive to replace. System Operator message queue has the following: Unit 6 with device parity protection not fully operational. Cause . . . . . : Unit 6 is part of a disk unit subsystem with device parity protection. Unit 6 requires service. The data has been saved. Reduced performance, machine checks, and possible data loss can occur if this condition is not corrected. The following information identifies the unit requesting service: Disk serial number: 68-0CF6ADE Disk type: 6718 Disk model: 070 Device resource name: DD006 Disk status shows the following: Serial Resource Hardware ASP Unit Number Type Model Name Status 1 1 02-35300 6718 074 DD001 DPY/Unprotected 1 2 02-015B2 6718 074 DD004 DPY/Unprotected 1 3 02-03760 6718 074 DD002 DPY/Unprotected 1 4 02-03423 6718 074 DD003 DPY/Unprotected 1 5 68-0D0E009 6718 070 DD005 DPY/Unprotected 1 6 02-0CF6ADE 6718 070 DD006 DPY/Failed Do the unit #'s listed here represent the position in the "cage" these drives are in? The only reason I ask is that when I look at the hardware details for unit #6 I see the following: Type. . . . . . . . . . . . : 6718 Model . . . . . . . . . . . : 070 Level . . . . . . . . . . . : 5 Serial Number . . . . . . . : 02-0CF6ADE Resource Name . . . . . . . : DD006 Physical location: Frame ID . . . . . . . . . : 1 Card position. . . . . . . : D05 Device position. . . . . . : "Card Position" D05 seems to point me to the 5th slot in the cage, rather than the 6th. I don't want to yank the wrong one. Also, where do I find the "serial number" that is listed in the detail? The serial number reported in QSYSOPR message queue is different than the detail on disk status (68-0CF6ADE .vs 2-0CF6ADE) Is it on the drive itself so I can double check the it before I replace it? Thanks. Pete Helgren -- DISCLAIMER: This message and accompanying documents are covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and contains information intended for the specified individual(s) only. This information is confidential. If you are not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, copying, or the taking of any action based on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. ------------------------------ -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest 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. End of MIDRANGE-L Digest, Vol 5, Issue 1976 ******************************************* -- 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. -- 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.