Not to beat a dead horse.

Our rep sent us the following link to calculate value units
https://www-112.ibm.com/software/howtobuy/passportadvantage/valueunitcalculator/vucalc.wss

It?s up to us to determine what we have.

Kevin
_____________________________________________
From: "Bell, Charles (Chip)" [mailto:Chip.Bell AT BHSALA DOT COM] 
Sent: Monday, July 09, 2007 11:46 AM
To: ADSM: Dist Stor Manager
Subject: Re: [ADSM-L] Lost in TSM licensing

We were audited. We simply trued-up, reporting the most recent client/TDP
deployments (which were quite a few). At least that was my understanding.
They did want a look at our entire environment. Anyone else want to comment?
:)

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Monday, July 09, 2007 10:29 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Lost in TSM licensing

Just out of curiosity, how many people have been audited?  Did your entire
environment have to comply with the new per processor licensing or only items
purchased since the new process went into effect?

Debbie Haberstroh
TSM Administrator

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Thomas Denier
Sent: Tuesday, July 03, 2007 2:43 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Lost in TSM licensing


As I noted in a previous posting, I did some experiments where I
collected processor count information remotely by executing a command
with a return code equal to the number of processors. I have gotten
a request to share the code I used.

My experiments were done in 2004. I don't know whether all of the
commands will work with newer OS levels.

The process always involved a scheduled event with 'action=command'
and 'object' parameter consisting of an 'exit' command followed by
something that evaluates to the number of processors.

For Windows I used:

object="exit %number_of_processors%"

I don't think this works correctly with hyperthreading processors;
I think it reports the total number of hyperthreads rather than the
number of processors.

For Linux I used:

object="exit `grep ^processor /proc/cpuinfo|wc -l`"

This has the same problem with hyperthreading as my Windows code.
However, the /proc/cpuinfo psuedo-file also contained 'sibling'
lines reporting the number of hyperthreads per processor. I
captured this number using the following:

object="exit `grep ^siblings /proc/cpuinfo|head -1|cut -d: -f2`"

This code assumes that all of the sibling values are the same.
As far as I know, nobody is marketing systems that violate
this assumption.

For HP-UX I used:

object="exit `/etc/ioscan -kC processor|grep processor|wc -l`"

For AIX I used:

object="exit `lsdev -Cc processor|wc -l`"

For Solaris I used:

object="exit `/usr/sbin/psrinfo|wc -l`"

The Web search that turned up this command also turned up a
warning that no known method of querying processor counts
works on all Solaris releases. My notes don't indicate theOS level of the
system I tested this code on.

-----------------------------------------
Confidentiality Notice:
The information contained in this email message is privileged and
confidential information and intended only for the use of the
individual or entity named in the address. If you are not the
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this information is strictly
prohibited. If you received this information in error, please
notify the sender and delete this information from your computer
and retain no copies of any of this information.