|
sounds like they mixed up the terms. from the info center: Software license key sheet With each keyed product that you order, you receive a software license key sheet that contains the following information: The 18-character license key information Product identification number Product name Version, release, and modification Associated system serial number Usage limit Other pertinent information However - they may be referring to a serial # on the install cd? if this was not a pre-loaded? jim ----- Original Message ----- From: "Neil Palmer" <neilp@dpslink.com> To: <MIDRANGE-L@midrange.com> Sent: Saturday, May 05, 2001 11:30 PM Subject: Re: Displaying License Keys > Jim, > > Thanks for the suggestion - that was what I had tried first before a few > others mentioned how to display the actual keys. > Turns out even that isn't good enough for IBM - I'm being told they won't > add the software to the customers order record without the "software > serial number". Working with the 400 since 1988 that's the first I've > ever heard of a software serial number. Anyone else know what they're > talking about ? > > ...Neil > > > > > > > "Jim Franz" <franz400@triad.rr.com> > Sent by: owner-midrange-l@midrange.com > 2001/05/05 19:52 > Please respond to MIDRANGE-L > > > To: <MIDRANGE-L@midrange.com> > cc: > Subject: Re: Displaying License Keys > > > neil - would suggest either a print key of WRKLICINF (work license info) > detail screen: > or the option 6 to print detail. - it includes the system name. If system > name not same as serial#, > then printkey the QSRLNBR sysval (will have same system name). Support > could > also easily dial in > thru ECS to verify. > since it would be impossible for this screen to indicate your licensed, > had > key not been given. > jim > Display License Information > S103587A > 05/05/01 > 22:35:55 > Product ID . . . . . . . . : 5769PW1 > License term . . . . . . . : V4R4M0 > Feature . . . . . . . . . . : 5050 > Description . . . . . . . . : Application Development ToolSet/400 -SEU > > Compliance type . . . . . . : *KEYED > Usage type . . . . . . . . : *CONCURRENT > > Usage limit . . . . . . . . : *NOMAX > Last update . . . . . . . . : 09/18/99 12:17:32 > > Threshold . . . . . . . . . : *NOMAX > > Usage count . . . . . . . . : 0 > > Peak Usage Information: > Peak usage . . . . . . . : 1 > Last peak . . . . . . . . : 09/18/99 14:20:25 > ----- Original Message ----- > From: "Neil Palmer" <neilp@dpslink.com> > To: <MIDRANGE-L@midrange.com> > Sent: Saturday, May 05, 2001 3:20 PM > Subject: Re: Displaying License Keys > > > > ? > > > > ...Neil > > > > > > > > > > > > barsa@barsaconsulting.com > > Sent by: owner-midrange-l@midrange.com > > 2001/05/04 21:44 > > Please respond to MIDRANGE-L > > > > > > To: MIDRANGE-L@midrange.com > > cc: > > Subject: Re: Displaying License Keys > > > > > > > > No, it doesn't happen. > > > > Al > > > > Al Barsa, Jr. > > Barsa Consulting Group, LLC > > > > 400>390 > > > > 914-251-1234 > > 914-251-9406 fax > > > > http://www.barsaconsulting.com > > http://www.taatool.com > > > > > > > > > > > > > > neilp@dpslink.com > > Sent by: To: > MIDRANGE-L@midrange.com > > owner-midrange-l@mi cc: > > drange.com Subject: Displaying > > License Keys > > > > > > 05/04/01 03:14 AM > > Please respond to > > MIDRANGE-L > > > > > > > > > > > > > > Anyone know of a way to display the 18 byte license key that has been > > entered via ADDLICKEY ? > > (Maybe a DMPOBJ of the *PRDLOD object - although I can't seem to see it > > there). > > > > We have a customer who has licensed RPG & Dev Tools. As is all too > > common, IBM's records are screwed up and they don't show the customer > > having Dev Tools - yet the license key has been entered on the system > with > > *NOMAX for users - and who else BUT IBM could have given them the > license > > key in the first place ? I figure if we tell them the license key > they'll > > have to admit the customer must have been licensed for it and fix their > > records. I wouldn't have thought they would have made it difficult to > > display the key - after all, it's only good on the system you would be > > displaying it from. > > > > Yes the customer screwed up and can't locate the paper with the license > > key or the "proof of purchase" document that IBM ships in that garish > pink > > & black striped cover (hoping I suppose that it will be seen and kept - > > but maybe it was spotted by the fashion police and thrown out). > > > > ...Neil > > > > > > > > +--- > > | This is the Midrange System Mailing List! > > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: > david@midrange.com > > +--- > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.