Excellent explanation, John Scott ford www.identityforge.com
On May 9, 2012, at 8:05 AM, "McKown, John" <[email protected]> wrote: > Not all .NET runs on Mono. Mono is reverse engineered and so may not > implement everything 100% like Microsoft does. Also, it tends to "lag" .NET > because it cannot implement the .NET functionality until after Microsoft has > documented it. And, like IBM and z/OS, there may be some parts of .NET which > are not publically documented but are used by those who can afford to license > the information for a competitive advantage. > > Well written (is there such?) C/C++ code could likely be ported to z/Linux. > Of course, z/Linux and Solaris are different, so they speak a similar but > different "language". Like a drunken Cockney talking to a drunken Texan, they > both thing they're speaking English, but the meaning is likely to be quite > different. Eh? > > -- > John McKown > Systems Engineer IV > IT > > Administrative Services Group > > HealthMarkets(r) > > 9151 Boulevard 26 * N. Richland Hills * TX 76010 > (817) 255-3225 phone * > [email protected] * www.HealthMarkets.com > > Confidentiality Notice: This e-mail message may contain confidential or > proprietary information. If you are not the intended recipient, please > contact the sender by reply e-mail and destroy all copies of the original > message. HealthMarkets(r) is the brand name for products underwritten and > issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake > Life Insurance Company(r), Mid-West National Life Insurance Company of > TennesseeSM and The MEGA Life and Health Insurance Company.SM > >> -----Original Message----- >> From: IBM Mainframe Discussion List >> [mailto:[email protected]] On Behalf Of George Henke >> Sent: Tuesday, May 08, 2012 6:02 PM >> To: [email protected] >> Subject: Re: It's feeding time in Jurassic Park . . . >> >> John, >> >> Thank you for the tip about MONO. >> >> It appears that with MONO, .NET applications can be run under >> zLinux, zVM. >> >> This would be preferable to x86 zBx, because the CHPID, not >> the IFL, does >> the I/O, more bang for the buck. >> >> Why would I NOT port all .NET to zLinux instead of x86 zBx? >> >> If so, what does that leave to run on zBx x86, other than >> some C/C++ code? >> >> >> >> On Fri, May 4, 2012 at 2:39 PM, McKown, John >> <[email protected]>wrote: >> >>>> -----Original Message----- >>>> From: IBM Mainframe Discussion List >>>> [mailto:[email protected]] On Behalf Of George Henke >>>> Sent: Friday, May 04, 2012 1:02 PM >>>> To: [email protected] >>>> Subject: It's feeding time in Jurassic Park . . . >>>> >>>> and the dinosaurs are very hungry. >>>> >>>> I need to migrate 50 Solaris servers to zLinux under z/VM on >>>> a z114 and >>>> about the same number of Windows servers to zBx. >>> >>> Congrats! >>> >>>> >>>> Does anyone have experience with this, some ideas? >>> >>> Experience, no. Ideas, sure! Why not? <grin> >>> >>>> >>>> Need a migration path. >>>> >>>> Some questions: >>>> >>>> Can z114 be upgraded to include zBx or must I upgrade to a >>>> z196 for that? >>> >>> I am not sure. >>> >>>> Can zBx be SYSPLEXed between 2 CECs? >>> >>> No. a zBx can be attached to at most 1 CEC. >>> >>>> If not, how do I eliminate the SPF, how do I do failover >> for the blade >>>> servers? >>> >>> SPF? Single point of failure? You need to have multiple >> z114s with and >>> associated zBX. >>> I think you'd do failover just like you would with any other "racked >>> mounted" servers. >>> If the rack fails, all the servers fail. So you need the >> same techniques >>> with a zBX "rack". >>> I'm not a PC person, but I think this involves TCP >> connections between a >>> server and it's failover >>> twin. >>> >>>> How do I convert Solaris to zLInux under z/VM? Solaris is >>>> not supported by >>>> zBx. >>>> Must I recompile the applications running under Solaris to >>>> run them under >>>> zLinux? >>> >>> Yes, you must recompile. z/Linux runs on the z/Architecture >> instruction >>> set. Solaris runs on >>> Intel or SPARC(?). You can't run Intel or SPARC instructions on a z. >>> However there are two exceptions >>> that I can think of which __may__ not need recompilation. >> The first is >>> Java code. The .jar and .class >>> files should run on any compatible JVM, regardless of the underlying >>> hardware architecture. Another >>> possibility is .NET applications. They __might__ run on a >> z/Linux using >>> Mono. Again, because they >>> don't run "native", but on an instruction emulator. Shell >> scripts may need >>> some changing. Perl, Python, Ruby >>> and other intepreted language may need some changing, >> depending on the >>> levels of the intepreter >>> on z/Linux versus the one on Solaris. >>> >>>> >>>> >>>> -- >>>> George Henke >>>> (C) 845 401 5614 >>> >>> I wish we were doing something like this. But we're z/OS only and IT >>> management would like to go MS-Windows only. >>> >>> -- >>> John McKown >>> Systems Engineer IV >>> IT >>> >>> Administrative Services Group >>> >>> HealthMarkets(r) >>> >>> 9151 Boulevard 26 * N. Richland Hills * TX 76010 >>> (817) 255-3225 phone * >>> [email protected] * www.HealthMarkets.com >>> >>> Confidentiality Notice: This e-mail message may contain >> confidential or >>> proprietary information. If you are not the intended >> recipient, please >>> contact the sender by reply e-mail and destroy all copies >> of the original >>> message. HealthMarkets(r) is the brand name for products >> underwritten and >>> issued by the insurance subsidiaries of HealthMarkets, Inc. >> -The Chesapeake >>> Life Insurance Company(r), Mid-West National Life Insurance >> Company of >>> TennesseeSM and The MEGA Life and Health Insurance Company.SM >>> >>> >>> >>> >> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO IBM-MAIN >>> >> >> >> >> -- >> George Henke >> (C) 845 401 5614 >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> >> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
