× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Ah, v5r2.
I've had that problem. The solution was to delete the keys and key them in
again.
Did you try that?

On Thu, 8 Sept 2022 at 19:33, Jay B <orcljsb@xxxxxxxxx> wrote:

Oops - I captured that but forgot to paste it in the original email... I
do see 5050 in there:

Message ID . . . . . . : CPF9E72

Date sent . . . . . . : 09/08/22 Time sent . . . . . . :
08:18:07


Message . . . . : Usage limit of 0 exceeded. Grace period expires in 66
days
on 11/12/22.



Cause . . . . . : You received this message for one of the following

reasons:

-- A user was added, but the usage limit for product 5722WDS, license
term
V5R2M0, feature 5050, was exceeded. Users have until the specified date
(66
more days) to use this product. When this date is reached, the grace
period
expires and all users exceeding the usage limit are released.

-- The evaluation period for product 5722WDS, license term V5R2M0,
feature
5050, is ending. Users have until the specified date (66 more days) to
use
this product.

Recovery . . . : Contact your software provider to assist you in
receiving

More...

The confusing part for me is whether the V5R2 5050 license I entered is "in
scope" for V5R2M0 5050 (shown in the output above).


(a rollup to subsequent replies)

I used the suggestion to look at QSFWINV and noticed that the licenses I
had previously entered did not appear for V5R2M0. Interesting findings:

DSPLICKEY shows all licenses that I added with ADDLICKEY.
QSFWINV doesn't show any that I added with ADDLICKEY.
All added with ADDLICKEY show grace period countdowns in QSFWINV.
5722WDS in QSFWINV shows no key and the grace period shows a value.

Only the one license I had entered with WRKLICINF Option 1 appears in
QSFWINV (5722SS1).

I went to WRKLICINF, entered a 1 to enter a key for each item in the list
(PT1, QU1, ST, XW1) and only then did their licenses appear in QSFWINV.
This worked great for all licenses except 5722WDS.
When I try to enter the 5722WDS license through WRKLICINF the same way as I
did for the others, the tool says the 5722WDS license is not valid.

The list of licenses I have all show a license term of V5R2, and 5722SS1
has a V5R2M0 row (with the same license key as V5R2), and the XW1 has only
V5R2M0.

I created a prompted version of the command - V5R2 works, but V5R2M0 does
not.

Works:
*NLVLIBL/ADDLICKEY LICKEYINP(*PROMPT) PRDID(5722WDS) LICTRM(V5R2)
FEATURE(5050) SERIAL(104916M) PRCGRP(P10) LICKEY(IIIIII BBBBBB MMMMMM)
USGLMT(*NOMAX)

Does not work (with M0):
*NLVLIBL/ADDLICKEY LICKEYINP(*PROMPT) PRDID(5722WDS) LICTRM(V5R2M0)
FEATURE(5050) SERIAL(104916M) PRCGRP(P10) LICKEY(IIIIII BBBBBB MMMMMM)
USGLMT(*NOMAX)


last weekend I did a wipe-and-reinstall using I_BASE and the B_ and L_
media. The V5R2M0 version appeared from the start, so perhaps the M0 media
I have is "too new" to apply the V5R2 WDS license. I don't have any CDs
that say V5R2.

thanks


On Thu, Sep 8, 2022 at 10:09 AM Rob Berendt <rob@xxxxxxxxx> wrote:

And is the message for feature 5050 or another feature?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Jay
B
Sent: Thursday, September 8, 2022 11:39 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: 5722WDS Usage limit of 0 exceeded but successfully entered

[You don't often get email from orcljsb@xxxxxxxxx. Learn why this is
important at https://aka.ms/LearnAboutSenderIdentification ]

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.


Hello,

I receive a message "Usage limit of 0 exceeded. Grace period expires in
66
days..." when using STRPDM, however the license is shown as (what I
interpret to be) "valid" status.

OS/400 version is V5R2M0.

When I display licenses there appears to be nothing wrong with the
5722WDS
key:

Product identifier . . . . : 5722WDS

License term . . . . . . . : V5R2

Feature . . . . . . . . . . : 5050

Description . . . . . . . . : Websphere Development Studio



System serial number . . . : 10....M



Processor group . . . . . . : P10



License Key . . . . . . . . : xyz123 xyz123 xyz123



Usage limit . . . . . . . . : *NOMAX



Expiration date . . . . . . : *NONE



Vendor data . . . . . . . . : *NONE


... but the warning appears every time I use PDM.

I have licenses for 5722SS1 as V5R2 and V5R2M0 and have entered both of
them (I don't know if this makes a difference). I got the same error
with
only the 5722SS1 V5R2 license entered, so I added the V5R2M0 license
(which
was the same key number).

My primary interest is understanding why this is happening for 5722WDS.
All of the other licenses I entered appear to be in good status and no
warnings for other products are found in DSPLOG except for 5722WDS.


Ideally, I'd prefer to not wipe and reinstall every 70 days when I have
what I believe to be a valid license key. Just trying to learn a bit.
Any
advice would be greatly appreciated.


Thanks
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2023 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.