On Mon, 3 Mar 2008 08:46:40 -0600, Chase, John wrote:
>> >
>> the authoring tools than for using their product.  For
>> example, a separate license is needed for the C compiler,
>> but, since LE, the code the compiler produces can be run on
>> the base OS.
>
>Arguably, *any* code that can be written at all can be written in
>Assembler, for which a license is delivered with the operating system
>license.  Likewise for any API.  "In the end", compilers produce
>"executable code", which most easily can be "untranslated" into
>Assembler source.
>
The concern here is with the C Runtine Library.  My understanding
is that nowadays that's all incorporated in LE delivered with the
base OS, so that concern vanishes.

>3.  Would a "sharp" customer programmer who figures out how to write and
>successfully execute an SRB enclave on a zIIP without first obtaining
>the "zIIP API license" be guilty of "software piracy" of some sort?
>Think SHOWZOS.......
>
The vernacular for this is "Clean Rooom".  IANAL.  Is the ISV forbidden
to distribute source code, possibly including comments which explain
how the interfaces are being used?  Are the interfaces wrapped in
copybook members?

So I buy a car; I don't buy the cruise control feature, which is
nonetheless present in the engine control embedded software, merely
disabled.  Then I buy a third party performance upgrade which
incidentally enables cruise control (the vendor innocently assumed
that all his customers would have chosen cruise control, or just
never had an opportunity to test on a non-cruise-control platform.)
Who has broken what agreement?  IANAL.  Perhaps I've legitimately
purchased the feature from a third party.  Perhaps that third
party has violated an agreement with the original vendor.

We have a software product (not mainframe) licensed from a vendor
who includes an SLQ database licensed from a subcontractor.  I do
not believe we are entitled to use that SQL except as part of the
immediate supplier's product.  In the course of troubleshooting,
that supplier sometimes instructs us to issue native SQL commands
and report the results.  I could do a lot of reverse engineering
and/or refer to the subcontractor's end user documentation (if I
could get it legally).  No moral issue here; I don't need an SQL
database today.

-- gil

----------------------------------------------------------------------
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