Technical article 126150

CPU numbering is not consistent across the OpenServer 6 command set.

OpenServer 6.0.0

Written · Last revised

Problem

CPU numbering is not consistent across the OpenServer 6 command set. Some commands number CPUs from 1 and others from 0.

Solution

OpenServer 6.0.0 contains both "legacy" OpenServer commands like cpuonoff(ADM), sar(ADM) and mpstat(ADM) and new SVR5 kernel commands like psrinfo(ADM), psradm(ADM) and rtpm(ADM).

In order to maintain backward compatibility with scripts that may use the legacy OpenServer commands we number CPUs from 1 such that on a dual CPU system, the CPUs would be numbered as CPU 1 and CPU 2.

However, the new SVR5 commands number CPUs starting at 0 (zero) such that on a dual CPU system, the CPUs would be numbered as CPU 0 and CPU 1.

This inconsistency has been reported to SCO Engineering.

From the Xinuos technical article database, record 126150. Reproduced with permission. The original is at www.sco.com/ta/126150, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.