18 lines
3.5 KiB
Plaintext
Executable File
18 lines
3.5 KiB
Plaintext
Executable File
tas&marcuskraft&mfusage2&6.0.0&&&mfusage2&&&bcarico@actscorp.com&N.Y.N.N.Y.N.N
|
|
|
|
|
|
|
|
|
|
1.1.o.o.o.N.0&mfusage2.001&mfusage2.002&mfusage2.003&mfusage2.004&mfusage2.005&mfusage2.006&mfusage2.007&mfusage2.008&mfusage2.009&mfusage2.010&mfusage2.011&mfusage2.012&mfusage2.013&mfusage2.016&mfusage2.017&mfusage2.019
|
|
&::1.0:1:1:0&?0=0?1=0?2=0?3=0?4=0?5=0?6=0?7=0?8=0?9=0?10=0?11=0?12=0?13=0?14=0::1.0:2.0:1:0&?0=0?1=0?2=0?3=0?4=0?5=0?6=0?7=0?8=0?9=0?10=0?11=0?12=0?13=0?14=0::1.0:2.0:1:0&::1.0:1:1:0&::1.0:1:1:0&::undefined.0:1:1:0&::2.0:1:1:0&::2.0:1:1:0&?0=0?1=0?2=0?3=0?4=0?5=0?6=0?7=0?8=0::2.0:1:1:0&::4.0:1:1:0&::3.0:1:1:0&::3.0:1:1:0&::3.0:1:1:0&::undefined.0:5.0:1:0&::undefined.0:1:1:0&?0=0?1=0?2=0::undefined.0:1:1:0
|
|
&Computer / IT industry ::Product Manager (SUSE Linux Enterprise Server) &?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?14::Application Development (better: building the <BR>Linux OS distribution) is the single purpose for <BR>5 years (since 2000). So no change occured in the <BR>last two years. &?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?xxx?14::See comment to question 2). No change in purpose. &- ::&- ::&Main purpose of the mainframe was compile, test,
|
|
<BR>and run.
|
|
<BR>Outstanding usage scenario was virtualization of
|
|
<BR>system resources (disk, cpu, memory, channels) to
|
|
<BR>1) separate (isolate) above workloads
|
|
<BR>2) but share resources (work load balancing)
|
|
<BR>
|
|
<BR>I fact we had only a single machine, however
|
|
<BR>optimized usage would not have been possible
|
|
<BR>without the outstanding virtualization
|
|
<BR>capabilities for the zSeries ::&Main purpose is application / Linux OS
|
|
<BR>development (and test/QA).
|
|
<BR>No external customers are served by this machine
|
|
<BR>directly.
|
|
<BR>However the Linux OS we produce (SLES 7/8/9 for
|
|
<BR>S/390) is used on thousands of instances
|
|
<BR>(somewhere between 2.500-5.000) (cannot disclose
|
|
<BR>the excat number). ::&No customer transactions.
|
|
<BR>2 mainframe supporting internal production.
|
|
<BR> ::&?xxx?1?xxx?xxx?xxx?xxx?xxx?xxx?xxx::No IFL (we noeed full sharing of CPU capacity). <BR>No zAAP needed (no java apps). &The machine is exclusivly used for development,
|
|
<BR>test and support for the zLinux market segment.
|
|
<BR>The formula is cost spend for people, machine,
|
|
<BR>support, power and cooled floorspace vs. revenue
|
|
<BR>from zLinux generated business.
|
|
<BR>Difficult to calculate is the ROI of expertise
|
|
<BR>you gain having a mainframe in house (education,
|
|
<BR>training, ...) ::&1) Reliability
|
|
<BR>2) Virtualization / rescource sharing
|
|
<BR> capabilities
|
|
<BR>3) IO capability ::&eg.
|
|
<BR>http://www.novell.com/success/american_fidelity.html
|
|
<BR>
|
|
<BR>Demonstrates how large customers value SLES on
|
|
<BR>mainframe in their environment (eg. server
|
|
<BR>consolidation), also demonstrating intergation of
|
|
<BR>other Novell applications to a solution for the
|
|
<BR>customer. ::&1) increasing capacity (cpu processing power,
|
|
<BR> total avaialble system memory, IO throughput)
|
|
<BR>2) execellent QA and service to maintain
|
|
<BR> operation ::&IBM is fulfilling this promise, however not
|
|
<BR>forgetting to generate revenue from it :) ::&1) ISV/application/solution development on zLinux
|
|
<BR> a) Linux has brought a multitude of solutions
|
|
<BR> to Z, a range survey (product specific)
|
|
<BR> would be interesting
|
|
<BR> b) inhouse developement platform: do zSeries
|
|
<BR> customers buy or develop or do both ?
|
|
<BR> What would be the reasons to buy or
|
|
<BR> develop?
|
|
<BR>
|
|
<BR> ::&?0?1?2::mkraft@suse.de
|
|
Not Scored by Definition
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|