The SHARE control statement directs EREP to combine errors for any device that is shared between processors or systems. The report associates all the errors for that device with the device address rather than with the different processors.
You can use SHARE statements to influence the way EREP assigns hexadecimal identifiers to the processors shown in the reports. See How EREP Assigns Numbers to CPUs for details.
Indicates
The paths to devices shared by processors.
Syntax
.-,-------------------------------. V | >>-SHARE=--(----+-----+--cpuser.--+-ccua------+-+--)----------->< '-XA.-' +-ccuX------+ '-ccua-ccua-'
- [XA.]cpuser
- Is a six-digit hexadecimal CPU serial number (digits 0–F). Use cpuser to indicate that the processor is running in 370 mode. Use XA.cpuser to indicate that the processor is running in 370XA mode.
- ccua
- Is a three- or four-digit hexadecimal channel-control unit-device address 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 (0–F) 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.
If you omit this control statement, EREP presents each device’s error records by device type.
If a device is shared between processors
or systems and you omit this control statement:
- The EREP reports present the error records by processor and device type.
- The message, IFC221I NO SHARE CARD is generated and the job completes with a return code of 4 (RC=4).
Coding
- SHARE must be the first word in the statement, followed by the equal sign and the desired values in parentheses.
- You must put at least two entries (cpuser.ccua|ccuX|ccua-ccua) in each statement.
- You may need more than one SHARE statement to show all the possible
paths to one device. If so, repeat the first entry in the statements
for the remaining paths, because EREP equates all the paths in the
SHARE statement to the one you specify first. For example:
SHARE=(011111.01F0,022222.0330,022222.06F0,022222.0FF0) SHARE=(011111.01F0,033333.03F0,033333.0630,033333.0F30) - The cpuser values in SHARE statements override the hexadecimal identifiers assigned by EREP for the CPUs in the report. See How EREP Assigns Numbers to CPUs for details.
- Once you have specified a range (cpuser.ccua-ccua) in a SHARE statement, you must specify that range the same way each time you use it in any other SHARE statement.
- The combined number of CPUs, cpuser, specified in all of your control statements cannot exceed 255.
- 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. - If more than one address range is specified on one SHARE statement, the total number of addresses specified in each range must match.
Notes
- The SHARE control statements are not used for DASD devices that provide product identifiers within their sense (For example: 3990/3390).
- When you include SHARE statements in your EREP controls, each report indicates whether a particular set of error data represents a device that you have specified in SHARE statements.
Examples
The
following sections give you more detailed instructions and examples:
- Using SHARE Statements to Combine Data in EREP Reports describes how to set up share statements for the devices in your system.
- How EREP Assigns Numbers to CPUs describes how to control the numbers EREP assigns to the CPUs.