The prefix.MICS.PARM member SRLDEVS is used to associate a
failure impact level, a vendor name, and a device description
with one or more of the devices attached to a specific CPU or
processor. It also allows data for devices with multiple
paths from one or more processors to be related to a single
device address. Entries in this member are optional.
The SRLDEVS member contains two types of statements, the
CPUSERIAL and the DEVICE statement. Each is described below
in detail. Figure 7-3 is a worksheet to aid in collecting
the data with which to complete prefix.MICS.PARMS(SRLDEVS).
As with most CA MICS PARMS members, the format of the
statements is free-form, but positional. There are no
default values; so if a statement is to be coded, all
parameters must be coded and not left blank. Comments are
coded by beginning the statement with an '*'. Blank
statements are allowed.
Modify the sample SRLDEVS member supplied with the
prefix.MICS.PARMS library distributed with the CA MICS system
rather than code it from scratch. Starting with an existing,
correct specification may spare you annoying syntax errors.
An example SRLDEVS member is shown below.
Example 1:
*
* SYSTEM RELIABILITY (SRL) DEVICE TABLE
*
CPUSERIAL 069604
DEVICE 760 160 N IBM TSO STORAGE VOLUME
DEVICE 170 170 I IBM INSURANCE CLAIMS FILES
DEVICE 840 240 C IBM PRIMARY PAGING VOLUME
DEVICE 950-957 350 N IBM PROGRAMMER WORK VOLUMES
DEVICE 570 570 C IBM IMS LOG TAPE
CPUSERIAL 054130
DEVICE 760 160 N IBM TSO STORAGE VOLUME
DEVICE 170 170 I IBM INSURANCE CLAIMS FILES
DEVICE 840 240 C IBM PRIMARY PAGING VOLUME
DEVICE 950-957 350 N IBM PROGRAMMER WORK VOLUMES
DEVICE 570 570 C IBM IMS LOG TAPE
CPUSERIAL Statement
A CPUSERIAL statement identifies a specific CPU or processor
by its 6 hexadecimal character serial number.
The format of the CPUSERIAL statement is:
CPUSERIAL cpuser
or
CPUSERIAL SHARED
or
CPUSERIAL cpuser1 cpuser2 cpuser3 ... cpuser8
where the parameter is:
cpuser = CPU serial number. The serial number is the number
stamped on the frame of the processor and is the
number returned from executing the instruction
'Store CPU ID'. The serial number may contain any
combination of the digits 0-9 and the hexadecimal
characters A-F. It can be 6 digits long.
If your site has devices shared across multiple
CPUs, then you can take advantage of the SHARED
keyword and avoid specifying the CPUSERIAL number
and DEVICE specifications for each of the shared
CPUs by coding just one set of CPUSERIAL and DEVICE
control statements. Note however that is a
possibility for the devices belonging to a nonshared
CPU being classified under SHARED if the device
addresses match those of the devices specified for
the CPUSERIAL SHARED statement and if the devices
belonging to this CPU are not defined in SRLDEVS.
Another way of specifying the CPUSERIAL statement
for devices that are shared across several CPUs is
to specify the CPUSERIAL statement, followed by a
list of the CPU serial numbers (up to a maximum of
eight) and listing the devices that are shared
across those CPUs using DEVICE statements below it.
Example 1 above shows the simplest form of coding
the CPUSERIAL and DEVICE statements. Example 2
shows how to use the SHARED keyword of the CPUSERIAL
statement and Example 3 shows you how the coding of
Example 1 can be simplified by specifying multiple
CPU Serial numbers on the CPUSERIAL statement for
devices shared by the CPUs.
Example 2:
CPUSERIAL 069604
DEVICE 760 160 N IBM TSO STORAGE VOLUME
DEVICE 170 170 I IBM INSURANCE CLAIMS FILES
DEVICE 840 240 C IBM PRIMARY PAGING VOLUME
DEVICE 950-957 350 N IBM PROGRAMMER WORK VOLUMES
DEVICE 570 570 C IBM IMS LOG TAPE
CPUSERIAL SHARED
DEVICE 760 160 N IBM TSO STORAGE VOLUME
DEVICE 170 170 I IBM INSURANCE CLAIMS FILES
DEVICE 840 240 C IBM PRIMARY PAGING VOLUME
DEVICE 950-957 350 N IBM PROGRAMMER WORK VOLUMES
DEVICE 570 570 C IBM IMS LOG TAPE
Example 3:
CPUSERIAL 069604 054130
DEVICE 760 160 N IBM TSO STORAGE VOLUME
DEVICE 170 170 I IBM INSURANCE CLAIMS FILES
DEVICE 840 240 C IBM PRIMARY PAGING VOLUME
DEVICE 950-957 350 N IBM PROGRAMMER WORK VOLUMES
DEVICE 570 570 C IBM IMS LOG TAPE
DEVICE Statement
The DEVICE statements following a CPUSERIAL statement are
assumed to represent devices normally associated with that
processor. Each DEVICE statement contains a physical device
address or range of addresses, a logical device address, a
failure impact level, a vendor name, and an installation
device description. There can be more than one DEVICE
statement per CPUSERIAL statement.
The format of the DEVICE statement is:
DEVICE ppp-ppp lll f vendor description
where the parameters are:
ppp-ppp = Physical address. The single device address or
range of addresses used to identify one or more
devices attached to the processor. The device
address(es) must contain 4 valid hexadecimal
characters. If a range is specified, the pair
of addresses must be separated by a '-', must
have no imbedded blanks, and the first three
characters of the addresses must have the same
channel and control unit values. For a range,
the device addresses must also be specified in
ascending order. For example, the range 0230-
0237 would be valid. The address pair 0237-
0230 would not be valid because the device
addresses are not in ascending order.
lll = Logical address. The 4 hexadecimal character
address to which the physical address is mapped
if a single device address is specified in
PHYSICAL ADDRESS. If a range of addresses is
specified in PHYSICAL ADDRESS, this value is
the starting address for the mapped range of
addresses and the third digit of this address
must match the third digit of the address
specified in the first address of the range.
For example, the range 830-837 would be mapped
to the address 230 in the following manner:
830->230, 831->231,832->232,...,837->237. The
range of addresses 458-45F could not be mapped
to the starting address 250 because the device
addresses '0' and '8' do not match.
f = Failure impact. The single character code for
the impact to the installation caused by a
failure on the device(s) at the address(es)
specified in PHYSICAL ADDRESS. The value must
be N for no impact or not specified, C for
critical, I for impacting, or W for warning.
This value is carried in the data base and is
available for use by reporting programs.
vendor = The 1- to 8-character name of the vendor
supplying the device described by this
statement. The name may not contain any
embedded blanks.
description = Device description. This is the 1- to 22-
character description of the device(s)
described by this statement. The description
may contain embedded blanks but should not
exceed 22 characters in length. Note that the
actual description should be from the
installation's point of view, the device's use,
importance, etc. The description of the device
from a hardware point of view (e.g., 3390 Model
3) is already known and maintained by the
CA MICS system. The description provided here
is carried in the data base, but is not used by
the CA MICS system.
NOTE ON USAGE:
The statements in this parameter are all optional and need
not be specified. All CA MICS elements for devices having no
SRLDEVS statements are set to blank or a value meaning 'not
specified'. You may wish to 'comment out' or provide dummy
values for this parameter until a later date. If you wish to
change one or more of these parameters at some later time,
then you must execute prefix.MICS.PARMS(SRLPGEN) to rebuild
the formatting procedures.
+--------------------------------------------------------------------------+ | INSTALLATION PREPARATION WORKSHEET: System Reliability Device Table | | | | PARMS Library Member is SRLDEVS | | Reference Sections: 7.3.3 | +--------------------------------------------------------------------------+ | | | CPUSERIAL ______ | | | | Physical Logical Failure | | Address* Address Impact Vendor Device Description | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | | | | | CPUSERIAL ______ | | | | Physical Logical Failure | | Address* Address Impact Vendor Device Description | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | DEVICE ___-___ ___ _ ________ ______________________ | | | | * NOTE: Physical Address can be a single address or a range | | of addresses. | +--------------------------------------------------------------------------+ | ....5...10...15...20...25...30...35...40...45...50...55...60...65...70.. | +--------------------------------------------------------------------------+
Figure 7-3. System Reliability Component Device Definition Worksheet
|
Copyright © 2014 CA.
All rights reserved.
|
|