|
OK, let me summarize what I've seen so far and provide my feelings about it. I'm not trying to be a pain and I am stirring the pot somewhat, but IMHO I've not seen a compelling reason to use the IXS yet. 1) Ability to replace "system" drive from remote site by moving new image from AS/400 to AS/400. -- OK, I'll give you that one, interesting idea. 2) Ability to do AS/400 side save/restore. -- Last I knew the only save/restore you could do from the AS/400 side of an integrated server was a save/restore of the entire drive image, the same ideas as SAV/RSTSTG. There is no way, AFAIK, to save/restore individual objects in the windows space, no? 3) Remote reboot. -- I'll assume you mean when the remote machine is hung so we'll rule out the simple administrative methods. While the integrated server would provide that option so would a $400 powerstrip from APC that allows me via SMNP, HTTP and telnet to power on and off outlets on the strip. 4) Password sync -- Available w/o integrated servers 5) Management -- I'd use MS's tools over ops nav to manage my pcs, no? Who do you think has better access to the server internals? Distribute disk -- ok fair, but you still need to do a lot on the W2K server too, no? W2K doesn't just magically say "oh my more disk!" and go off and use it. So why is it easier? 6) Management central -- I guess I can't comment until someone tells me what I can do via MC to my W2K box. 7) User Policies -- The old .pol policies are dead in W2K in favor of group policies so I don't think you'd gain anything there. 8) Data exchange doesn't go over the network -- SO? 9) No additional hardware -- Huh? Isn't the integrated server additional hardware? 10) 24x7 maintenance -- Again huh? How does running W2K in an iSeries enable that? 11) Software deployment -- ok, by can't you do the same w/o integrated servers? 12) Get a SAN for W2K w/o SAN (Shark) knowledge. Maybe, but you'd have to understand SANs from the W2K side anyway, no? ------------ Walden H Leverich III President Tech Software (516)627-3800 x11 WaldenL@TechSoftInc.com http://www.TechSoftInc.com -----Original Message----- From: Walden H. Leverich [mailto:WaldenL@TechSoftInc.com] Sent: Tuesday, December 18, 2001 18:10 To: 'midrange-l@midrange.com' Subject: WHY would I run Windows on my iSeries? OK, I mean this in all seriousness. 1) I understand why the iSeries is a stable machine -- it's got great hardware and software that were married at the design stage and just plain old doesn't crash. 2) I understand why you MIGHT want to combine multiple iSeries machines into one physical footprint via lpar -- you can share cpu and memory across multiple machines load balancing as needed. I don't always agree with this, but I certainly understand it. 3) I understand why you might want to run Linux on the iSeries -- you're at the mercy of Linux, but at least you get the stability of AS/400 disk AND CPU AND Memory in one nice box. Hell, you can even telnet into the Linux partition from a green screen to manage it. 4) But I can't understand the advantage of the integrated xSeries. Why would I want to run W2K in an iSeries? The only advantage I can think of is a smaller footprint in the computer room and given that I can fit 42 W2K servers in a rack using 1U optimized servers I don't really accept that reason. You don't get to use the CPU or Memory of the machine. You can't manage it from the greenscreen. While you can use iSeries disk you can get just as reliable disk on a PC in the form of Shark and the like. I doubt you get any advantage from the io processors since there is no OS knowledge to drive them. I don't see a stability or manageability advantage. So... Why would I do this? Silly answers like "because windows crashes all the time and putting it in an iSeries would help" aren't accepted. WHY would it help? -Walden ------------ Walden H Leverich III President Tech Software (516)627-3800 x11 WaldenL@TechSoftInc.com http://www.TechSoftInc.com _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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
