|
I love it, but my Soundoff remarks (assuming that I choose to go to Soundoff, which has been a subject of some debate) are already outlined, and are currently beyond the time limit. IBM(*WIPEBROW). You guys go for it. 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 Larry Bolhuis <lbolhuis@arbsol.co To: MIDRANGE-L@midrange.com m> cc: Sent by: Subject: Re: Displaying License Keys owner-midrange-l@mi drange.com 05/06/01 04:17 PM Please respond to MIDRANGE-L There actually IS a software serial number for each system. This number is SO top secret that not only do virtually all customers not know what their's is, they don't even know that it exists. Way back in the V3R1 days when IBM created the conditions that would require a new 'System Password', (I'm not sure that's the correct term but it's what's required to complete an IPL after certain significant upgrades or extended power off times) we needed that 'password'. Well as a Business Partner we had access to some forms to fill out and one of them was a request for this 'password'. On the form was a place for the software serial number. As I didn't have it I rattled my local branch and they got it for me but only specifically because I needed for that form. I was later told that a) I was Never supposed to have that serial number, b) The IBMer who gave it to me could have been fired, c) there is no way to see it on the system, d) it is Never printed on any documents that come with the system. And interestinly a couple days later that form dissapeared from the BP area on IBMLINK as well. I just can't imagine IBM requiring a customer to provide THEM with the number because you never have it. We have had many run-ins with the key center but never one such as this where IBM is requiring a customer to have something IBM will not give them! Sounds like a very good item for Sound Off. Will you be at COMMON? - Larry Neil Palmer wrote: > > Well, if that's what it is I can't name a single customer of ours that > kept that after a release was installed. :-( > > ...Neil > > "Alex A Moore" <alexm@ELLISHOSIERY.COM> > Sent by: owner-midrange-l@midrange.com > 2001/05/06 04:50 > Please respond to MIDRANGE-L > > > To: <MIDRANGE-L@midrange.com> > cc: > Subject: RE: Displaying License Keys > > Neil, > > I believe that IBM is refering to the serial number that is > printed on the > document that looks like a "packing slip", and is shipped with software > orders. It looks like the hardware serial number, 5 to 7 alpha numeric. > It > may also be on the "media report" that is also shipped with the software. > > HTH > > Alex > > -----Original Message----- > From: owner-midrange-l@midrange.com > [mailto:owner-midrange-l@midrange.com]On Behalf Of Neil Palmer > Sent: Saturday, May 05, 2001 11:30 PM > To: MIDRANGE-L@midrange.com > 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 > +--- -- Larry Bolhuis | Cogito ergo mercari iSeries Arbor Solutions, Inc. | (616) 451-2500 | (I think, therefore I buy iSeries.) (616) 451-2571 -fax | lbolhuis@arbsol.com | #3 1951-2001 +--- | 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.
midrange.com
