You can take a look at a couple IBM examples for inspiration such as:
- Enterprise COBOL Developer Trial
- CICS Transaction Server for z/OS Developer Trial
Another possibility available for certain types of products is to provide
Internet access (preferably via an encrypted connection) to an
Makes me curious of the lists opinion on if z/OS LPARs are usually able to
contact an internet site, or are commonly isolated?
I seem to have formed the impression that it's quite common to have a path
out/in (typically via firewalling...) is that impression accurate?
It would seem to me that
Bill Soper wrote:
It would seem to me that having a product work during initialization, then
contacting a license server using, say, the CPUID just as vendor keys often
do, to see if this is a licensed install would potentially be an option too?
What will you do if your bread-and-butter
This has been an interesting discussion. I understand why vendors lock
software to specific machines and dates. Especially in the non-corporate
world. But I had another evil thought. I wonder how many z/OS system exist
which are not connected to the Internet. Not accessible to the Internet,
but
On 03/28/2014 07:39 AM, John McKown wrote:
This has been an interesting discussion. I understand why vendors lock
software to specific machines and dates. Especially in the non-corporate
world. But I had another evil thought. I wonder how many z/OS system exist
which are not connected to the
On Fri, Mar 28, 2014 at 9:06 AM, Joel C. Ewing jcew...@acm.org wrote:
snip
I seem to recall a case where the vendor wanted to change contract terms
at renewal in a way that was unacceptable to our corporate management
and it took several months of negotiations past the formal expiration of
It sure seems like Chicago-Soft has achieved a license mechanism for
QuickRef with near-minimal inconvenience:
On their website you specify a CPU and request a key(1).
They send an email with a binary attachment.
You transfer that attachment to a z/OS dataset on DASD.
It's
On Fri, Mar 28, 2014 at 6:44 AM, Bill Soper sop...@au1.ibm.com wrote:
Makes me curious of the lists opinion on if z/OS LPARs are usually able to
contact an internet site, or are commonly isolated?
There are some systems that are totally disconnected. Maybe 1-10%?
On 3/26/2014 11:38 PM, Ed Jaffe wrote:
On 3/26/2014 9:20 AM, Charles Mills wrote:
Right. Good input. Thanks. I have shipped software with a hard-coded
expiration date. What I am looking for is a floating expiration date
that
would be 30 days after installation, whether installed today or a year
Steve Comstock wrote:
Also, what about the shop that tries to locate the end date and zap it? You
may say it doesn't happen but I have heard tales...
True. I also heard it via grapevine.
Some software does integrity checks [CRC check?] on that date to prevent
zapping. Rather, you can replace
On Thu, Mar 27, 2014 at 12:38 AM, Ed Jaffe edja...@phoenixsoftware.comwrote:
On 3/26/2014 9:20 AM, Charles Mills wrote:
Right. Good input. Thanks. I have shipped software with a hard-coded
expiration date. What I am looking for is a floating expiration date
that
would be 30 days after
John McKown wrote:
I don't know if the Binder API can do a load and go like this or not.
It can. You can invoke Binder from a program using ATTACH EP=IEWBLDGO and LOAD
EP=IEWBLDGO.
SubCapacity job does that similar thing. You use EXEC PGM=LOADER with your list
of software used and a SYSLIN
Speaking for myself only, I agree 100% with Phil. I HATE with a passion
mainframe vendor software with license keys, codes, all the myriad ways
they use to make my life difficult, adds work to my team, and puts my
company at risk if a vital piece of our infrastructure fails for
licensing
Steve Comstock wrote:
Also, what about the shop that tries to locate the
end date and zap it? You may say it doesn't happen
but I have heard tales...
OK, I know this is going to turn into a religious issue, but here's my $0.02.
In 30+ years I've never seen this. I've seen ONE case where a
A bit OT for this, but I buy e-books (PDF) from a publisher who has some
really good stuff. It is not DRM'ed. But what the publisher does is take my
order on the Web. And I must pay for it with a credit card. No big deal.
But that means that he knows my name. A short time later, I get an email
W dniu 2014-03-27 15:37, Mark Jacobs pisze:
Speaking for myself only, I agree 100% with Phil. I HATE with a
passion mainframe vendor software with license keys, codes, all the
myriad ways they use to make my life difficult, adds work to my team,
and puts my company at risk if a vital piece of
It is common in the PC world for software to be offered for a 30-day trial
that works automatically. You download the software, install it, and it
somehow knows when it was installed and quits 30 days later unless
purchased. Typically, it knows by hiding some magic file or registry entry
somewhere
I just happen to be installing a SAS upgrade as I am writing.
A (90 day) temp key is provided (with the distribution - no request needed) to
support the installation (SAS used to install SAS).
On/before the end of that period a regular perm key must be installed.
snip
Has anyone ever seen
Charles Mills wrote:
It is common in the PC world for software to be offered for a 30-day trial
that works automatically. You download the software, install it, and it
somehow knows when it was installed and quits 30 days later unless
purchased. Typically, it knows by hiding some magic file or
/openbeta/
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Charles Mills
Sent: Wednesday, March 26, 2014 10:36 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Ever see automatic 30-day trials for mainframe software?
It is common in the PC world
[mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Mullen, Patrick
Sent: Wednesday, March 26, 2014 9:07 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ever see automatic 30-day trials for mainframe software?
The CICS Betas released over the last few releases (I believe betas were/are
available for 4.2
On 26 March 2014 12:20, Charles Mills charl...@mcn.org wrote:
Right. Good input. Thanks. I have shipped software with a hard-coded
expiration date. What I am looking for is a floating expiration date that
would be 30 days after installation, whether installed today or a year from
today.
It
automatic 30-day trials for mainframe software?
The CICS Betas released over the last few releases (I believe betas were/are
available for 4.2, 5.1 5.2) have built in expiry dates. IBM states that
the betas Contain a disabling device that will prevent it from being used
after the test period ends
W dniu 2014-03-26 16:36, Charles Mills pisze:
[...]
Has anyone ever seen mainframe software that automatically expired 30 days
after installation? If so, any rough idea how that worked? (Presumably, not
a magic hidden file LOL.)
Yes. How does it work? It depends, I've seen various methods. One
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of R.S.
Sent: Wednesday, March 26, 2014 3:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ever see automatic 30-day trials for mainframe software?
W dniu 2014-03-26 16:36, Charles Mills pisze
On Mar 26, 2014, at 10:36 AM, Charles Mills wrote:
Has anyone ever seen mainframe software that automatically
expired 30 days
after installation? If so, any rough idea how that worked?
(Presumably, not
a magic hidden file LOL.)
Charles:
I have. Its *USUALLY* hidden in the key . Its
On 27/03/2014 2:36, Charles Mills wrote:
On the mainframe side, I don't think I've ever seen an automatic 30-day
trial, largely because magic hidden files are of course greatly frowned
upon in this space. Mainframe 30-day trials in my experience require vendor
administration to generate some
The Sterling Software division I worked for did this, on VM, not MVS. The CPUID
file was very robust, had in it:
- Soft expiration (start warning)
- Expiration (warn loudly)
- Hard expiration (stop working)
The file could contain keys for multiple CPUs, so you
In
3253568952062076.wa.elardus.engelbrechtsita.co...@listserv.ua.edu,
on 03/26/2014
at 10:55 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za
said:
They're also called 'nagware'. They're nagging constantly,
Those are the ones that I decide not to buy.
interrupting your work,
The
On Mar 26, 2014, at 6:44 PM, Andrew Rowley wrote:
On 27/03/2014 2:36, Charles Mills wrote:
On the mainframe side, I don't think I've ever seen an automatic
30-day
trial, largely because magic hidden files are of course greatly
frowned
upon in this space. Mainframe 30-day trials in my
On 27/03/2014 14:40, Ed Gould wrote:
This is not quite the same but something remotely similar.
A LONG time ago (GT 40) years a vendor who thought he as clever needed
to store a jobname in low memory.
That's why I specified using standard, documented interfaces. It might
be as simple as
On 3/26/2014 9:20 AM, Charles Mills wrote:
Right. Good input. Thanks. I have shipped software with a hard-coded
expiration date. What I am looking for is a floating expiration date that
would be 30 days after installation, whether installed today or a year from
today.
Our trial software
32 matches
Mail list logo
