Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*question\s+on\s+license\s+and\s+keys\s+for\s+ADSM\/6000\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*question\s+on\s+license\s+and\s+keys\s+for\s+ADSM\/6000\s*$/: 3 ]

Total 3 documents matching your query.

1. question on license and keys for ADSM/6000 (score: 1): Author: Susan McClure <smcclure AT IS.RICE DOT EDU>; Date: Thu, 8 Feb 1996 09:57:00 -0600; I am confused by this license-key thingy in the ADSM/6000 world. I just upgraded the ADSM/6000 server from V1 to V2, and it says the license is not in compliance on the q status command. With the sof; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1996-02/msg00090.html (11,008 bytes)
2. Re: question on license and keys for ADSM/6000 (score: 1): Author: Tom Geniusz <andaz AT EN DOT COM>; Date: Thu, 8 Feb 1996 12:19:56 -0500; Yes that registration sheet is confusing. You are correct in using the reg license adsm command. However you have to use it multiple times! For the client registration you have to enter multiple regi; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1996-02/msg00092.html (11,977 bytes)
3. Re: question on license and keys for ADSM/6000 (score: 1): Author: Susan McClure <smcclure AT IS.RICE DOT EDU>; Date: Thu, 8 Feb 1996 12:20:56 -0600; Tom Thanks for the info on licensing. No- although I saw the info about the compression problem, I haven't gotten the message from any clients. Actually, our clients are really other AIX nodes in an; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1996-02/msg00098.html (12,956 bytes)

Current List: 1 - 3
Page: [1]