Re: DSPLICKEY not showing keys (but LICENSE_INFO does!)

[Don Brown <DBrown@xxxxxxxxxx>]

One of the systems we look after was ordered inclusive of 5 years HW and 
SW maintenance.

The order shows 

IB5733-SPO      5733-SPO        1       Ibm Sw Maintenance For Ibm I And 
Selected Products -  3-year Extended Registration

Swma Uplift To 5 Years: 
IB5733-SPP      5733-SPP        2       Ibm Software Maintenance For Ibm I 
And Selected Products -  1-year Registration

So we have the 3 year SW + 2 x 1 Year extensions = Total 5 Years

IBM loaded the order so the additional years ran concurrently with years 1 
and 2.

Apparently this happened to quite a few systems in 2014-2015 time range by 
one IBM employee.

Now you would expect this would be a relatively simple thing to resolve - 
well it has been over 2 weeks and still going.

Lucky you get 70 days grace on license keys!!

Cheers


Don Brown
 



From:   "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
To:     midrange-l@xxxxxxxxxxxxxxxxxx
Date:   16/03/2019 03:49 AM
Subject:        Re: DSPLICKEY not showing keys (but LICENSE_INFO does!)
Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>



Well, heck, this is a non-starter.  The LICENSE_INFO view (like the 
WRKLICINF command) shows everything EXCEPT ... <drum roll>... the actual 
license key.  So now we're battling through the ESS site which of course 
decided today to suffer sudden onset amnesia  and tell us we have no 
keys for ANY of our machines.

Hmm.

Is someone trying to tell us something?


On 3/14/2019 1:31 PM, Joe Pluta wrote:
> Exactly my plan.  I should end up with a table that looks like the 
> *OUTFILE for DSPLICKEY.
>
> On 3/14/2019 1:28 PM, Rob Berendt wrote:
> > If saved the output of that service to a different table you could 
> > read every row and issue a call to QCMDEXC to redo the ADDLICKEY.
> > Just wrap your sql statement with
> > Create table mylib.lickeys as (
> > <existing sql statement here>
> > ) with data;
> >
> > This kind of stuff was an inspiration for me to learn SPL.
> >
> > -----Original Message-----
> > From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of 
> > Joe Pluta
> > Sent: Thursday, March 14, 2019 1:39 PM
> > To: Midrange Systems Technical Discussion 
> > <midrange-l@xxxxxxxxxxxxxxxxxx>
> > Subject: DSPLICKEY not showing keys (but LICENSE_INFO does!)
> >
> > Okay, this is a brand new one for me.  I've got several machines/LPARs.
> > They have varying combinations of products: HA/replication LPARs should
> > be the same, and the DEV box obviously has a somewhat different
> > configuration.  Had some unexpected license messages come up and so I
> > decided to compare keys.  On one of the LPARs, DSPLICKEY returns 
CPF9E58
> > License key information not found.  Now I expect this when looking for 
a
> > key that is not there, but with DSPLICKEY PRDID(*ALL) LICTRM(*ALL)
> > FEATURE(*ALL) I definitely don't expect to see that error; that implies
> > that there are NO KEYS on this machine!  AHHHHH!  PANIC!
> >
> > Now I know that the fine folks at IBM continue to provide us with new
> > services and I wondered if there was one for keys and lo and behold, 
the
> > LICENSE_INFO view does just that.  When run on the working LPARs, it
> > shows me the same information I get from DSPLICKEY.  But on the
> > misbehaving LPAR, LICENSE_VIEW shows me the keys I expect, even though
> > DSPLICKEY shows nothing!
> >
> > So now I'm stumped.  Looks to me like I've got some internal tables
> > munged up and a call to IBM may be in order.  But before I do that, I
> > thought I'd reach out to the collective community. Anybody else ever 
see
> > something like this?