WARNING: DataStage has found more CPU's on your system (12)

akrzy · Post by **akrzy** » Thu Mar 24, 2005 7:10 am

Hi,

How can I use DS on "bigest" system (12 CPU) than license (4 CPU)?

Anka

roy · Post by **roy** » Thu Mar 24, 2005 7:45 am

Hi,
no you can't!
I guess it is against the whole idea of per CPU price.

it will give you those till you install a suficiant CPU license.

or work on a machine with CPU count matching bought license.

akrzy · Post by **akrzy** » Thu Mar 24, 2005 7:55 am

I have some idea.
... to isolate 4 CPU ("virtual machine") and then ...
What do you think?

chulett · Post by **chulett** » Thu Mar 24, 2005 8:12 am

Sure, if you can manage that it would be fine. As long as you are constraining it so that DataStage only has access to the number of CPUs you are licensed, for the warnings will stop.

For example, we all live on a HP Superdome. (man, I really wanted to put 'yellow' in there.

). It has umpty CPUs but has been broken up into several 'lpars', logical partitions that look like separate machines to anything sitting on them. The one our DataStage server sits on has 8 CPUs because that's what they licensed. Would be nice to have more, but The Powers That Be choose otherwise.

roy · Post by **roy** » Thu Mar 24, 2005 9:01 am

hmmm,
Interesting Craig (I've yet yo work with DS on HP)
does this logical partition funtion as an entirely independant machine?
with it's own configuration/IP and so on?
can anything on that logical partition not use more CPUs?
if so I think my words still stand.

not long ago one of our customers tried to restrict DS with 2 CPU license on a unisys (don't know exact hardware model) no luck there.
as long as DS sees more CPUs your in the same situation.
as I said before they tried: "go for it, though I doubt it will work"

Can you really blame anyone for this ? I think it can be well understood by all why it is so.

chulett · Post by **chulett** » Thu Mar 24, 2005 9:59 am

roy wrote:does this logical partition funtion as an entirely independant machine? with it's own configuration/IP and so on? can anything on that logical partition not use more CPUs? if so I think my words still stand.

Yes. Yes. No. Exactly.

In essence, they look like individual machines - IP, config, CPU, RAM, etc - which is why it works.

ray.wurlod · Post by **ray.wurlod** » Thu Mar 24, 2005 4:14 pm

Ascential would counsel you to purchase licences for 12 CPUs.

ogmios · Post by **ogmios** » Fri Mar 25, 2005 10:03 am

Version 7.5 complains on the number of CPU's but happily seems to continue working (must be a bug in the software

).

We also had problems with dual-core cpu's which Ascential counts as 2 separate cpu's.

Ogmios

chulett · Post by **chulett** » Fri Mar 25, 2005 10:19 am

Oh, it works all right - it just that every job finishes with at least one warning. In other words, no job ever gets a plain old 'Finished' status.

Or are you saying that it works differently under 7.5?

ogmios · Post by **ogmios** » Fri Mar 25, 2005 11:02 am

chulett wrote:Oh, it works all right - it just that every job finishes with at least one warning. In other words, no job ever gets a plain old 'Finished' status.

Or are you saying that it works differently under 7.5?

In the version I have no warnings. But my hunch is that it's because of the dual core cpu's: the installation application sees double the amount of physical cpu's but the run-time engine doesn't seem to use the same way of finding the number of CPU's (hence warning on installation, no warning at runtime). But I'm not going to check with Ascential whether this is the case.

An idea of one of our wacky administrators was - if required - to manipulate the shared library path of DataStage so that it finds "adapted" shared libraries that return any cpu count you want

Ogmios

chulett · Post by **chulett** » Fri Mar 25, 2005 11:29 am

Interesting... when I was testing on one of the SuperDome lpars with "too many" cpus I got the warning during installation and during every job run. Lucky you with the 'no warnings in my jobs' problem.

Don't think I should comment on your wacky admin.

ogmios · Post by **ogmios** » Fri Mar 25, 2005 11:34 am

Personally I think the counting of 1 dual core cpu as 2 single core cpus by DataStage is kind of a rip off. If you look at optimal performance (read benchmarks) you will see that 1 dual-core (for Sun e.g.) has the performance of about 1.5 single core cpu's.

Ogmios

shawn_ramsey · Post by **shawn_ramsey** » Fri Mar 25, 2005 11:50 am

ogmios wrote:Personally I think the counting of 1 dual core cpu as 2 single core cpus by DataStage is kind of a rip off. If you look at optimal performance (read benchmarks) you will see that 1 dual-core (for Sun e.g.) has the performance of about 1.5 single core cpu's.

Ogmios

Are you talking Dual core or Hyper-threading? With the Dual Core there are actually two CPUs and with Hyper-threading there is only one and it fakes the system into thinking there are two. We have had an issue with our Windows server being hyper-threaded and getting this error and Ascential just gave us keys for twice as many processors. If it is truly a dual core then I believe that they have the right to count those as two processors since they really are.

ogmios · Post by **ogmios** » Fri Mar 25, 2005 12:56 pm

Are you talking Dual core or Hyper-threading?

Dual core, but I'd rather have 2 single core cpu's, then 1 dual core. Performance wise they're not the same.

Anyway Ascential sales just ask for the number of cpu's, and don't ask these "technical" questions as dual-core, single-core, hyper-threading. So some customers will be suprised by the warnings.

Ogmios

chinek · Post by **chinek** » Mon Mar 28, 2005 6:58 pm

chulett wrote:Interesting... when I was testing on one of the SuperDome lpars with "too many" cpus I got the warning during installation and during every job run. Lucky you with the 'no warnings in my jobs' problem.

Don't think I should comment on your wacky admin.

Yes it does behave this way in v7.5, the earlier versions didn't behave this way. That caused us problems because we had some job controls that would abort if there are warnings.