> -----Original Message-----
> From: IBM Mainframe Discussion List
> [mailto:[email protected]] On Behalf Of Timothy Sipples
> Sent: Wednesday, November 18, 2009 8:46 PM
> To: [email protected]
> Subject: Re: compiling Java question - z/OS jar(s) on non-z/OS?
>
> >That's why I was asking. I don't want to take a chance
> >of violating our license. But, what is the difference
> >between actually copying the file from z/OS to my Linux
> >desktop, for the purpose of compilation, versus making
> >the jar files available via NFS exports on the z/OS
> >system to the Linux system?
>
> We can leave "z/OS" out of this discussion, because it isn't germane.
> Insert (machine-licensed) "Oracle Database," for example, and
> it'll be the
> same answer. Software which is licensed to a particular
> machine is for that
> machine. If you want to run it on another machine, you need a
> license for
> that machine. (With narrow exceptions if they're permitted in
> the license
> agreement, such as disaster recovery. There is certain
> permitted use of the
> ISPF Workstation Agent, to pick another example.)
>
> The technical means of copying the file(s) don't matter.
> Floppy disk, NFS,
> BitTorrent... doesn't matter. Whole product or one file...
> doesn't matter.
> The license agreement doesn't permit you to do any of those
> things without
> a license for the target machine.
Looks like I didn't explain at all well. The software will not be RUNNING on
another system. It resides on another system simply so that I can do the
equivalent of a "composite link" of it into software that I am writing on the
PC. The software which is being written and compiled on the PC will eventually
run on z/OS and nowhere else. But, in order to do this compile and create a JAR
file, the java compiler on the PC needs __READ__ access to the support jars.
Again, the software will run only on the licensed machine and nowhere else.
But, at this point, I'm going to say "nevermind". It is getting to complicated.
I'm just going to drop the idea of learning about using Java on CICS entirely.
I simply cannot do it on the mainframe. Management simply WILL NOT be
understanding of my "wasting" of CPU resources, even if they are not being used
for anything else and even if it does not in any way affect our costs. 'Nuff
said about that.
>
> If you obtain the particular file in question from the vendor
> through a
> vendor-authorized avenue, with a valid license agreement for
> the target
> machine, then you're fine. Kirk described a vendor download path which
> looks OK.
>
> >Your point is well taken. Which is why I have not done
> >anything before determining what is allowed by the
> >license.
>
> Thank goodness. At least one of my customers was not so prudent. :-(
>
> If you're in doubt about permitted use, just ask the vendor
> first. I don't
> speak for IBM, but in my experience at least IBM is quite
> reasonable when
> handling such questions and situations.
I don't have the authority. And since this is strictly for my learning purposes
and not a requirement, management would not be open to asking "frivolous"
questions of IBM.
>
> I'm sorry to hear about the corporate politics, with one IT group
> apparently determined to manage critical assets
> inefficiently, knowingly,
> to the apparent detriment of the company's own business
> interests. I have
> occasionally seen such behaviors. There are some ways to handle them.
firearms are not allowed in the building. <grin>
>
<snip>
Thanks for your cautions. I'm just giving up. It was a "stupid" idea anyway.
("Stupid" being defined as "unimportant to management" and so not relevant or
worthy of any consideration)
>
> - - - - -
> Timothy Sipples
--
John McKown
Systems Engineer IV
IT
Administrative Services Group
HealthMarkets(r)
9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * (817)-961-6183 cell
[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: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
