Explanation
(MVS, VM, and VSE) The number of CPUs is
excessive; sssssss is the serial number of the first excess CPU.
The following are possible reasons for the message:
- The data sets being processed contain records from an excessive
number of CPUs, and the EREP controls do not include a valid combination
of CPU or MOD selection parameters or SYSIMG control statements.
OR
- EREP has found CONTROLLER, DASDID or SHARE statements specifying
too many processors (CPUs) for the requested report.
The system summary report defaults to a maximum of 10
processors; all other reports can show up to 16, with the following
exceptions:
- System exception reports on a maximum of 255 processors
- Event history reports on a maximum of 256 processors
- PRINT=PT reports on an unlimited number of processors
- Threshold reports on an unlimited number of processors
To increase the maximum number of processors for system summary
to 16, see
LINELEN — Line Length (Processing Parameter).
System action
If it is a case of the data sets being processed
containing records from an excessive number of CPUs, processing continues
but the output does not show all possible processors, only the maximum
allowed for the requested report.
If it is a case of CONTROLLER,
DASDID or SHARE statements specifying too many processors, processing
is terminated.
Programmer response
If excessive CPUs have been encountered,
code the SYSIMG control statement and rerun the job. This reduces
the number of CPUs to the actual number of system images. If you
still have excessive CPUs, you may have to code the CPU or MOD selection
parameter in addition to the SYSIMG control statement. This restricts
the number of processors whose records can be processed.
If
too many CPUs are defined in the control statements, recode the control
statements using only one CPU serial number per system image and rerun
the job. (Refer to the individual control statement descriptions for
additional information.)