That restriction cracks me up (well actually it makes me want to throw up).
IBM wants (needs) a large pool of ISV's writing products for z/OS, yet, in
order to do this, the ISV must either:
1 - Get a full z/OS license in order to run any "Production" software, ie
customer defect tracking, company web site, billing, etc.
2 - Purchase a non z box (ie Windows or Unix) and run the above functions on
it.  

Seems like the same problem IBM ran into with Universities.
Wayne Driscoll
Product Developer
JME Software LLC
NOTE: All opinions are strictly my own.
 

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Steve Comstock
Sent: Thursday, March 16, 2006 2:13 PM
To: [email protected]
Subject: Re: FLEX-ES

Edward E. Jaffe wrote:
> Jay Howard wrote:
> 
>> We are a small shop running a zSeries/890 (capacity 130) and 
>> management is looking at using a FLEX-ES system for disaster recovery 
>> purposes. Is there anyone that has or is doing this that would be 
>> willing to share their experiences? You can reply directly to me if 
>> you like.
>>   
> 
> 
> Does Flex-ES support z/Architecture for production use?
> 

Sure, if you pay the standard license fees for the z/OS base and any
products you use. It's only us developers who get the software gratis and
are thus forbidden to use it for production. At least that's my
understanding.

It's also my understanding that those fees can be pretty high.

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the
archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to