The CONTROLLER control statement provides EREP with channel control unit addresses (CUAs) or device numbers for the I/O devices attached to a control unit, allowing EREP to total the error counts for the control unit.
CONTROLLER control statements are:
- Used with the system summary report and the threshold report.
- Necessary when there are more than 16 devices on a control unit.
- Not used for DASD devices that provide product identifiers within their sense.
Indicates
The CUAs attached to a control unit.
Syntax
.-,----------------------. V | >>-CONTROLLER=--(----cpuser.--+-ccua------+-+--)--------------->< +-ccuX------+ '-ccua-ccua-'
- cpuser
- Is a six-digit hexadecimal CPU serial number (digits 0–F).
- ccua
- Is a three- or four-digit hexadecimal channel CUA or device number (digits 0–F). The first digit is the channel designated to the operating system as the primary CUA for the device.
- ccuX
- Is a two- or three-digit hexadecimal channel-control unit number with X indicating all the device addresses attached to that control unit.
- ccua-ccua
- Is a range of continuous addresses. The low end of the range must be first. The range must be at least one, and cannot exceed 32.
Defaults
None.
Coding
- CONTROLLER must be the first word in the statement, followed by an equal sign and the desired values in parentheses. No embedded blanks are allowed.
- Each entry on the CONTROLLER statement defines a controller grouping (the range of devices on a particular control unit). Additional entries on this and other CONTROLLER statements define other controller groupings.
- The combined number of CPUs (cpuser), specified on all of your control statements cannot exceed 16.
- Each control unit summary is limited to 16 device addresses unless CONTROLLER statements indicate otherwise.
- You can specify up to 32 CUAs for a single control unit.
- Every entry on a CONTROLLER statement must define the complete set of devices attached to that control unit.
- When a CONTROLLER statement specifies part of a 0–F range of device addresses and physical devices are attached to addresses in the remaining portion of the range, use another CONTROLLER entry to define the remaining devices, to prevent misleading output.
- You cannot overlap device address ranges on two CONTROLLER statements.
- Specify a range of addresses (cpuser.ccua-ccua) the same way each time you use it.
- If you specify a processor-device address combination on a CONTROLLER statement, you cannot specify a range that includes that combination on any other CONTROLLER statement.
- When you code a range of device addresses (ccua-ccua):
If the control unit digit, u, in the low CUA For Example Is odd, the high CUA must have the same ccu digits. 0350–0357 is valid 0358–0367 is not valid Is even, the high CUA must have the same even ccu digits, or the next greater odd u digit. 0368–036F is valid 0368–0377 is valid 0368–0388 is not valid Note: The channel identifier can be one or two digits.
Notes
- You can combine CONTROLLER statements with SHARE statements to make EREP combine the errors for shared devices by control unit. See SHARE Control Statements.
- The CPU entries that appear on CONTROLLER statements override the default number identifier assignments EREP makes for processors that appear in reports. See How EREP Assigns Numbers to CPUs for details.
Examples
The following example illustrates
the use of the CONTROLLER statement to define a controller grouping
containing the full range of 32 devices:
CONTROLLER=(011111.0480–049F)