call pgm(qsfwinv) parm(*print) can be used to print a list of the license
keys and the expiration date of each. Chris had a good point; we used to
have a DR/Backup box, too, at a former employer. We got out of synch on one
product (can't remember why) that, while all other licenses expired on, say,
20101231, this one expired on 20100331. So I had to call twice a year for
Jerry C. Adams
IBM i Programmer/Analyst
I believe in unions and I believe in non-unions. -President George H.W. Bush
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Shannon ODonnell
Sent: Monday, April 23, 2012 12:04 PM
To: Midrange Systems Technical Discussion
Subject: Missing License Keys
Here's a curious thing that happened that I have never seen before and I'm
wondering if anyone else has ever had this happen or can offer suggestions
on how it could have happened.
On a development box (a 520 running V5R4) we use every day, the license
keys to our development toolset (5722WDS) expired.
This is a box we've been doing RPG development on daily for the last three
+ years. To our knowledge, no one has restored system data on this box
or otherwise modified the license expiration date.
I have just never heard of license keys expiring like this on their own. I
had thought that once you applied the keys you were done.
It makes me wonder if someone might have been playing around with the
license info and changed the date and then maybe just forgot about it or
something along those lines.
Anyone else ever have this happen?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l