U.S. patent application number 16/538879 was filed with the patent office on 2021-02-18 for replacing components of a data processing system.
The applicant listed for this patent is International Business Machines Corporation. Invention is credited to Michael Becht, Giovanni Cautillo, Daniel Johannes Klodt, Philip A. Sciuto, Martin Troster.
Application Number | 20210049216 16/538879 |
Document ID | / |
Family ID | 1000004301182 |
Filed Date | 2021-02-18 |
United States Patent
Application |
20210049216 |
Kind Code |
A1 |
Troster; Martin ; et
al. |
February 18, 2021 |
REPLACING COMPONENTS OF A DATA PROCESSING SYSTEM
Abstract
A computer implemented method for replacing components of a data
processing system, comprising in response to a detection of a newly
added component at a specific location; reading its customization
data from a data storage and querying a persistent database to
determine if functional capabilities according to customization
data are specified for this specific location; depending on a
result of determining the functional capabilities and of querying
the database if it contains customization data either: disabling
the component; or enabling the component and storing in the
database the customization data; or enabling the component and
replacing the customization data in the database; or storing the
customization data in the data storage of the component and
enabling the component.
Inventors: |
Troster; Martin; (Renningen,
DE) ; Sciuto; Philip A.; (POUGHKEEPSIE, NY) ;
Klodt; Daniel Johannes; (Altdorf, DE) ; Becht;
Michael; (Stuttgart, DE) ; Cautillo; Giovanni;
(Herrenberg, DE) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
International Business Machines Corporation |
Armonk |
NY |
US |
|
|
Family ID: |
1000004301182 |
Appl. No.: |
16/538879 |
Filed: |
August 13, 2019 |
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G06F 16/9032 20190101;
G06F 16/901 20190101; G06F 16/90335 20190101 |
International
Class: |
G06F 16/903 20060101
G06F016/903; G06F 16/9032 20060101 G06F016/9032; G06F 16/901
20060101 G06F016/901 |
Claims
1. A computer implemented method comprising: detecting a newly
added component at a specific location in a data processing system;
determining whether customization data corresponding to a component
similar to the newly added component at the specific location
exists in data storage; querying a persistent database in the data
processing system to determine if the functional capabilities,
according to the customization data, are specified for this
specific location; and system responsive to determining the data
storage of the component contains customization data and the
database does not contain customization data for a component
similar to the newly added component, enabling the respective
functional capabilities of the newly added component and storing,
in the database, the customization data of the newly added
component together with data representing the newly added
component's specific location in the data processing system
responsive to determining the data storage of the component
contains customization data and the database does not contain
customization data for a component similar to the newly added
component.
2. The method according to claim 1, further comprising: disabling
the component at the specific location responsive to determining
the data storage of the component does not contain customization
data and the database does not contain customization data for a
similar component.
3. The method according to claim 1, further comprising: enabling
the respective functional capabilities of the component and
replacing the customization data of the database with the
customization data of the newly added component responsive to
determining the data storage of the component contains
customization data and the database contains customization
data.
4. The method according to claim 1, further comprising: storing the
customization data in the data storage of the newly added component
and enabling the respective functional capabilities of the newly
added component responsive to determining the data storage of the
component does not contain customization data and the database
contains customization data.
5. The method according to claim 4, wherein in response to
detection of the newly added component where the data storage of
the component does not contain customization data, the component is
enabled to operate with the same functional capabilities as a
component with the previous customization data at the specific
location.
6. The method according to claim 1, further comprising: adding a
second newly added component to a specific location of the data
processing system; detecting the second newly added component in
the specific location by the firmware; reading a type of the second
newly added component from the data storage of the component;
determining if this type of the second newly added component is
supported with customization data; and responsive to determining
the type of second newly added component is supported with
customization data, reading customization data from the data
storage.
7. The method according to claim 1, further comprising disabling an
operation of a component where the data storage does not contain
customization data.
8. The method according to claim 7, further comprising associating
the customization data of a newly added component to its specific
location in the data processing system.
9. The method according to claim 7, further comprising detecting if
a new component is added to the data processing system.
10. The method according to claim 7, further comprising checking a
last known type of component being used in the same specific
location of the data processing system.
11. The method according to claim 1, wherein the database of the
data processing system comprises configuration rules for possible
customization data of replaceable components.
12. The method according to claim 11, further comprising checking
the customization data of the newly added component against the
configuration rules stored in the database.
13. The method according to claim 1, wherein the component is an
input/output card.
14. A computer program product for replacing components of a data
processing system comprising replaceable components wherein the
components comprise a data storage for computer-readable
customization data representing their respective functional
capabilities, and wherein the functional capabilities can be
enabled or disabled for use in the data processing system, the
computer program product comprising: one or more computer readable
storage media and program instructions stored on the one or more
computer readable storage media, the program instructions
comprising instructions to: detect a newly added component at a
specific location in the data processing system; determine whether
customization data corresponding to a component similar to the
newly added component at the specific location exists in data
storage; query a persistent database in the data processing system
to determine if the functional capabilities according to the
customization data are specified for this specific location; and
enable the respective functional capabilities of the newly added
component and storing in the database the customization data of the
newly added component together with data representing its specific
location in the data processing system responsive to determining
the data storage of the component contains customization data and
the database does not contain customization data for a component
similar to the newly added component.
15. The computer program product according to claim 14, wherein the
component is an input/output card.
16. The computer program product according to claim 14, wherein the
database of the data processing system comprises configuration
rules for possible customization data of replaceable
components.
17. The computer program product according to claim 14, further
comprising instructions to disable an operation of a component
where the data storage does not contain customization data.
18. A computer system for replacing components of a data processing
system comprising replaceable components wherein the components
comprise a data storage for computer-readable customization data
representing their respective functional capabilities, and wherein
the functional capabilities can be enabled or disabled for use in
the data processing system, the computer program product
comprising: one or more computer processors; one or more
computer-readable storage media; program instructions stored on the
computer-readable storage media for execution by at least one of
the one or more processors, the program instructions comprising
instructions to: detect a newly added component at a specific
location in the data processing system; determine whether
customization data corresponding to a component similar to the
newly added component at the specific location exists in data
storage; query a persistent database in the data processing system
to determine if the functional capabilities according to the
customization data are specified for this specific location; and
enable the respective functional capabilities of the newly added
component and storing in the database the customization data of the
newly added component together with data representing its specific
location in the data processing system responsive to determining
the data storage of the component contains customization data and
the database does not contain customization data for a component
similar to the newly added component.
19. The computer system according to claim 18, wherein the database
of the data processing system comprises configuration rules for
possible customization data of replaceable components.
20. The computer system according to claim 18, further comprising
instructions to disable an operation of a component where the data
storage does not contain customization data.
Description
BACKGROUND
[0001] The present invention relates in general to data processing
systems, in particular, to a computer implemented method for
replacing components of a data processing system, comprising
replaceable components, wherein the components comprise a data
storage for computer-readable customization data representing their
respective functional capabilities, and wherein the functional
capabilities can be enabled or disabled for use in the data
processing system, as well as a computer program product and a data
processing system.
[0002] Computer systems are composed of many components, namely,
circuit boards or parts that can be easily removed from the
computer system and replaced, even by someone lacking in-depth
product knowledge of the computer system. These components
typically include one or more of power supply units, motherboards,
socketed microprocessors, primary storage modules (e.g., Random
Access Memories, or RAMs), secondary storage devices (e.g., hard
drives and optical drives), video cards, sound cards, I/O adapters
and peripherals such as keyboards, mice and printers.
[0003] Many of these components have Vital Product Data (VPD)
stored thereon that is used during the setup or configuration of
the computer system. The VPD is a collection of configuration and
informational data associated with a particular set of hardware
(e.g., a component), to allow for the component to be administered
at a system or network level. VPD may include product model
numbers, unique serial numbers, product release levels, maintenance
levels, and other information specific to the hardware, as well as
user-defined information, such as the building and department
location of the hardware.
SUMMARY
[0004] A computer implemented method is proposed for replacing
components of a data processing system comprising replaceable
components, wherein the components comprise a data storage for
computer-readable customization data representing their respective
functional capabilities, and wherein the functional capabilities
can be enabled or disabled for use in the data processing system.
The method comprises (i) in response to a detection of a newly
added component at a specific location in the data processing
system reading its customization data from the data storage and
querying a persistent database in the data processing system to
determine if the functional capabilities according to the
customization data are specified for this specific location; (ii)
depending on a result of determining the functional capabilities
according to the customization data specified for this specific
location and of querying the database if it contains any
customization data for the same specific location in the data
processing system already, either a) in case, the data storage of
the component does not contain customization data and the database
does not contain customization data for a similar component,
disabling the component at the specific location; or b) in case,
the data storage of the component contains customization data and
the database does not contain customization data for a similar
component, enabling the respective functional capabilities of this
component and storing in the database the customization data of the
newly added component together with data representing its specific
location in the data processing system; or c) in case, the data
storage of the component contains customization data and the
database contains customization data, enabling the respective
functional capabilities of this component and replacing the
customization data of the database with the customization data of
the newly added component; or d) in case, the data storage of the
component does not contain customization data and the database
contains customization data for a similar component, storing the
customization data in the data storage of the newly added component
and enabling the respective functional capabilities of this
component.
[0005] Advantageously a transparent and non-interactive method may
be proposed to customize generic replacement hardware into a
specific function based on persisted information about what type
and function was last plugged in the same plug position in a
computer system. The computer system may be a data processing
system extendable with additional adapters, e.g., input/output
adapters.
[0006] Further asset protection may advantageously be provided
correlating empty customization write attempts and error callouts
to prevent unintended customization of parts.
[0007] Further, a computer program product is proposed for
replacing components of a data processing system comprising
replaceable components, wherein the components comprise a data
storage for computer-readable customization data representing their
respective functional capabilities, and wherein the functional
capabilities can be enabled or disabled for use in the data
processing system.
[0008] The computer program product comprises a computer readable
storage medium having program instructions embodied therewith, the
program instructions executable by the computer system to cause the
computer system to perform a method comprising: (i) in response to
a detection of a newly added component at a specific location in
the data processing system reading its customization data from the
data storage and querying a persistent database in the data
processing system to determine if the functional capabilities
according to the customization data are specified for this specific
location; (ii) depending on a result of determining the functional
capabilities according to the customization data specified for this
specific location and of querying the database if it contains any
customization data for the same specific location in the data
processing system already, either a) in case, the data storage of
the component does not contain customization data and the database
does not contain customization data for a similar component,
disabling the component at the specific location; orb) in case, the
data storage of the component contains customization data and the
database does not contain customization data for a similar
component, enabling the respective functional capabilities of this
component and storing in the database the customization data of the
newly added component together with data representing its specific
location in the data processing system; or c) in case, the data
storage of the component contains customization data and the
database contains customization data, enabling the respective
functional capabilities of this component and replacing the
customization data of the database with the customization data of
the newly added component; or d) in case, the data storage of the
component does not contain customization data and the database
contains customization data for a similar component, storing the
customization data in the data storage of the newly added component
and enabling the respective functional capabilities of this
component.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
[0009] The present invention together with the above-mentioned and
other objects and advantages may best be understood from the
following detailed description of the embodiments, but not
restricted to the embodiments.
[0010] FIG. 1 depicts schematics of a data processing system with
involved hardware and firmware components according to an
embodiment of the invention for replacing components of the data
processing system comprising replaceable components, wherein the
components comprise a data storage for computer-readable
customization data representing their respective functional
capabilities.
[0011] FIG. 2 depicts a flowchart of a firmware implementation for
adding a new component to a data processing system according to an
embodiment of the invention.
[0012] FIG. 3 depicts a flowchart of a firmware implementation for
replacing a component in a data processing system according to an
embodiment of the invention.
[0013] FIG. 4 depicts a flowchart of a firmware implementation for
adding and replacing a component in a data processing system
according to an embodiment of the invention.
[0014] FIG. 5 depicts an example embodiment of a data processing
system for executing a method according to the invention.
DETAILED DESCRIPTION
[0015] Currently, if the VPD of a component is corrupted, the
component cannot be used even if the physical hardware of the
component is functioning properly. In addition, since the VPD is
not replaceable, users need to buy a new component if the VPD
becomes corrupted. While existing mechanisms to protect the VPD are
available, most require the addition of redundant hardware to the
component that increases the cost of the component.
[0016] In the drawings, like elements are referred to with equal
reference numerals. The drawings are merely schematic
representations, not intended to portray specific parameters of the
invention. Moreover, the drawings are intended to depict only
typical embodiments of the invention and therefore should not be
considered as limiting the scope of the invention.
[0017] The illustrative embodiments described herein provide a
method for replacing components of a data processing system
comprising replaceable components, wherein the components comprise
a data storage for computer-readable customization data
representing their respective functional capabilities, and wherein
the functional capabilities can be enabled or disabled for use in
the data processing system.
[0018] The illustrative embodiments may be used for the proposed
method comprising (i) in response to a detection of a newly added
component at a specific location in the data processing system
reading its customization data from the data storage and querying a
persistent database in the data processing system to determine if
the functional capabilities according to the customization data are
specified for this specific location; (ii) depending on a result of
determining the functional capabilities according to the
customization data specified for this specific location and of
querying the database if it contains any customization data for the
same specific location in the data processing system already,
either a) in case, the data storage of the component does not
contain customization data and the database does not contain
customization data for a similar component, disabling the component
at the specific location; or b) in case, the data storage of the
component contains customization data and the database does not
contain customization data for a similar component, enabling the
respective functional capabilities of this component and storing in
the database the customization data of the newly added component
together with data representing its specific location in the data
processing system; or c) in case, the data storage of the component
contains customization data and the database contains customization
data, enabling the respective functional capabilities of this
component and replacing the customization data of the database with
the customization data of the newly added component; or d) in case,
the data storage of the component does not contain customization
data and the database contains customization data for a similar
component, storing the customization data in the data storage of
the newly added component and enabling the respective functional
capabilities of this component.
[0019] FIG. 1 depicts schematics of a data processing system 210
with involved hardware and firmware components according to an
embodiment of the invention for replacing components 10 of the data
processing system 210 comprising replaceable components 10, wherein
the components comprise a data storage 12 for computer-readable
customization data 14, representing their respective functional
capabilities. The functional capabilities can be enabled or
disabled for use in the data processing system 210. The embodiment
depicted in FIG. 1 for simplicity only exhibits one component
10.
[0020] The schematics of the data processing system 210 depicted in
FIG. 1 comprise a controller 34 with a firmware 32. The controller
is connected to an input/output drawer 36 with specific plug
positions as specific locations 20, 22, 24 for components 10.
[0021] As an example, the specific location 20 in the data
processing system 210 may be an input/output adapter, particularly
a PCI Express adapter, such that an input/output card 10 may be
plugged in the plug position 20. A persistent database 30 is
connected to the controller 34 comprising configuration rules 40
for possible components 10 with different customization, e.g.,
"Spare", "Coupling", "RoCE", to be used with the data processing
system 210 with different customization data 16. "Spare", e.g., may
be used for spare parts, "Coupling" for long distance coupling,
"RoCE" for Remote Direct Memory Access Over Converged Ethernet. The
persistent database 30 also comprises customization data 16 for
different components 10 which have been used in different plug
positions 20, 22, 24 as is indicated in the customization data 16
with data 26 representing the specific location 20, 22, 24.
[0022] The input/output card as component 10 comprises a data
storage 12, e.g. in an Electrically Erasable Programmable Read-Only
Memory (EEPROM), for computer-readable customization data 14
representing its respective functional capabilities, which can be
enabled or disabled for use in the data processing system 210. This
data storage 12 contains Vital Product Data (VPD) comprising
customization data 14, as e.g. a component type "CommonCard", a
hardware level "10" and a customization type "Coupling". Thus the
customization data 14 of the component 10 may be part of the VPD of
the component 10.
[0023] According to embodiments of the invention a single Part
Number may be defined for a card 10 representing all given
functions.
[0024] A field (record) may be defined in the card EEPROM 12 which
contains function specific customization information 14. Initially
this field may be set to zero during the card assembly process.
[0025] Function specific customization information 14 may be
written at any point before shipping the card to the customer for
installing it into a data processing system 210, which may be
executed as part of a new data processing system 210 or as an
upgrade to an existing data processing system 210.
[0026] The firmware 32 installed on the data processing system 210
requires any such card 10 to be properly customized and prevents
the operation of a non-customized card 10. For any card 10 of this
type, the firmware 32 may persist the specific customization
information 14 on a local controller 34 or medium and may associate
this information 14 with the card's plug position 20 in the data
processing system 210.
[0027] The spare parts stock may also use the non-customized
versions of the card 10, effectively avoiding the redundant
stocking of cards 10.
[0028] During replacement of a card 10 in the customer data
processing system 210, a non-customized spare part may be installed
in the same plug position as a specific location 20 as the original
card, e.g. a potentially defective card as part of a repair
action.
[0029] The firmware 32 may detect the installation of a
non-customized spare card 10 in the data processing system 210. The
firmware 32 may check the last known type of card 10 plugged in the
same plug position 20. If that last card was of the same type as
the newly installed spare card 10, the previous customization value
16 of that card 10 may be written into the VPD 12 of the spare card
10, effectively customizing it to the same function.
[0030] FIG. 2 depicts a flowchart of a firmware implementation for
adding a new component 10 to a data processing system 210 according
to an embodiment of the invention. The hardware and firmware
schematics may be implemented as depicted in FIG. 1.
[0031] According to the embodiment of the invention, the method
comprises adding the new component 10 to a specific location 20 of
the data processing system 210; detecting the component 10 in the
specific location 20 by the firmware 32; reading a type 18 of the
component 10 from the data storage 12 of the component 10;
determining if this type of component 10 is supported with
customization data 14; and if this is the case, reading
customization data 14 from the data storage 12. The firmware 32
detects if a new component 10 is added to the data processing
system 210.
[0032] The sequence for adding the new component 10 starts with
step S100. A card as a new component 10 is plugged into a specific
location 20 in step S102. The card 10 is detected by the firmware
32 in the plug position 20 in step S104.
[0033] The firmware 32 associates the customization data 14 of a
newly added component 10 to its specific location 20 in the data
processing system 210. In response to the detection of the newly
added component 10 at the specific location 20 in the data
processing system 210 its customization data 14 may be read from
the data storage 12 and the persistent database 30 in the data
processing system 210 may be queried to determine if the functional
capabilities according to the customization data 14 are specified
for this specific location 20. For this purpose in step S106 the
card type may be read from the data storage 12 on the EEPROM. Next
in step S108 it may be detected that it is a type with
customization support, followed by reading customization data 14
from the data storage 12 in step S110.
[0034] Then it is queried in step S112 if customization data 14
exist in the data storage 12 on the EEPROM. If this is not the case
the flow continues with step S226 described in FIG. 3 below.
[0035] The customization data 14 of the newly added component 10
are checked against the configuration rules 40 stored in the
database 30. Thus, if customization data 14 exists it is checked in
step S114 if customization is supported at the specific location 20
of the data processing system 210. If the functional capabilities
are not specified for the specific location 20 in the data
processing system 210, the respective functional capabilities of
the component 10 at the specific location 20 are disabled. The
sequence is ended by disabling the operation of the component 10,
and logging the configuration error in step S132 and ending in step
S124.
[0036] In response to the detection of the newly added component 10
with functional capabilities that are specified for the specific
location 20 in the data processing system 210, the respective
functional capabilities of this component 10 are enabled and the
database 30 is queried if it contains any customization data 16 for
the same specific location 20 in the data processing system 210
already. Thus, if customization is supported at the specific
location 20 it is queried in the database 30 if previous
customization data 16 exists, step S116.
[0037] If this is the case, the previous customization data 16 is
replaced with the customization data 14 of the newly added
component 10 by erasing the previous customization data 16 from the
database 30 in step S118. In step S120, the customization data 14
of the newly added component 10 is stored in the database 30
together with data 26 representing its specific location 20 in the
data processing system 210. The functional capabilities are then
enabled in the component 10 and the component 10 is then set to
operational in step S122, followed by ending the sequence in step
S124.
[0038] This method by this way also allows for moving a component
10 with customization data 14 from one specific location 20 to
another specific location 22, 24 or even to another data processing
system 210.
[0039] FIG. 3 depicts a flowchart of a firmware implementation for
replacing a component 10 in a data processing system 210 according
to an embodiment of the invention. The hardware and firmware
schematics may be implemented as depicted in FIG. 1.
[0040] According to an embodiment of the invention a potentially
defective component of the data processing system 210 may be
replaced with a newly added component 10 where the data storage 12
of the component 10 does not contain customization data 14, such a
component 10 being a general usage spare component. For replacing
the potentially defective component of the data processing system
210 the new component 10 without customization data 14 may be added
to the same specific location 20 as the potentially defective
component.
[0041] The sequence in FIG. 3 then starts with step S200. The steps
S202 to S212 with plugging in the component 10 and reading
component type and customization data 14 correspond to steps S102
to S112 described with the sequence in FIG. 2 and are therefore not
described in more details any more.
[0042] If a component 10 with customization data 14 was used, the
sequence proceeding with step S114 described in FIG. 2 would be
applicable.
[0043] The firmware 32 checks a last known type of component 10
being used in the same specific location 20 of the data processing
system 210. In response to detecting a newly added component 10
where the data storage 12 of the component 10 does not contain
customization data 14 (step S212), the database 30 is queried, if
it contains customization data 16 for the same specific location 20
in the data processing system 210 already, steps 226 and S228. If
this is the case, the customization data 16 are stored in step S230
in the data storage 12 of the newly added component 10, followed by
enabling the component 10 in step S222 to operate with the same
functional capabilities as a component with the previous
customization data 16 at the specific location 20.
[0044] If the database 30 does not contain previous customization
data 16 for the same location 20, the component 10 at the specific
location 20 is disabled in step S232, followed by ending the
sequence in step S224.
[0045] FIG. 4 depicts an overall flowchart of a firmware
implementation for adding and replacing a component 10 in a data
processing system 210 according to an embodiment of the invention.
The hardware and firmware schematics may be implemented as depicted
in FIG. 1. Components 10 may be added to the data processing system
210 where the data storage 12 of the component 10 may contain
customization data 14 or may not contain customization data 14.
[0046] The sequence for adding the new component 10 starts with
step S300. A card as a new component 10 is plugged into a specific
location 20 in step S302. The card 10 is detected by the firmware
32 in the plug position 20 in step S304.
[0047] The firmware 32 associates the customization data 14 of a
newly added component 10 to its specific location 20 in the data
processing system 210. In response to the detection of the newly
added component 10 at the specific location 20 in the data
processing system 210 its customization data 14 may be read from
the data storage 12 and the persistent database 30 in the data
processing system 210 may be queried to determine if the functional
capabilities according to the customization data 14 are specified
for this specific location 20. For this purpose in step S306 the
card type may be read from the data storage 12 on the EEPROM. Next
in step S308 it may be detected that it is a type with
customization support, followed by reading customization data 14
from the data storage 12 in step S310.
[0048] Then it is queried in step S312 if customization data 14
exist in the data storage 12 on the EEPROM. The customization data
14 of the newly added component 10 are checked against the
configuration rules 40 stored in the database 30. Thus, if
customization data 14 exist it is checked in step S314 if
customization is supported at the specific location 20 of the data
processing system 210. If the functional capabilities are not
specified for the specific location 20 in the data processing
system 210, the respective functional capabilities of the component
10 at the specific location 20 are disabled. The sequence is ended
by disabling the operation of the component 10, and logging the
configuration error in step S332 and ending in step S324.
[0049] In response to the detection of the newly added component 10
with functional capabilities that are specified for the specific
location 20 in the data processing system 210, the respective
functional capabilities of this component 10 are enabled and the
database 30 is queried if it contains any customization data 16 for
the same specific location 20 in the data processing system 210
already. Thus, if customization is supported at the specific
location 20 it is queried in the database 30 if previous
customization data 16 exist, step S316.
[0050] If this is the case, the previous customization data 16 is
replaced with the customization data 14 of the newly added
component 10 by erasing the previous customization data 16 from the
database 30 in step S318. In step S320 the customization data 14 of
the newly added component 10 is stored in the database 30 together
with data 26 representing its specific location 20 in the data
processing system 210. The functional capabilities are then enabled
in the component 10 and the component 10 is then set to operational
in step S322, followed by ending the sequence in step S324.
[0051] This method by this way also allows for moving a component
10 with customization data 14 from one specific location 20 to
another specific location 22, 24 or even to another data processing
system 210.
[0052] If a new component 10 is added where the data storage 12
does not contain customization data 14, another branch of the
sequence is followed. The firmware 32 checks a last known type of
component 10 being used in the same specific location 20 of the
data processing system 210. In response to detecting a newly added
component 10 where the data storage 12 of the component 10 does not
contain customization data 14 (step S312), the database 30 is
queried, if it contains customization data 16 for the same specific
location 20 in the data processing system 210 already, steps S326
and S328. If this is the case, the customization data 16 are stored
in step S330 in the data storage 12 of the newly added component
10, followed by enabling the component 10 in step S322 to operate
with the same functional capabilities as a component with the
previous customization data 16 at the specific location 20.
[0053] If the database 30 does not contain previous customization
data 16 for the same location 20, the component 10 at the specific
location 20 is disabled in step S332, followed by ending the
sequence in step S224.
[0054] Referring now to FIG. 5, a schematic of an example of a data
processing system 510 is shown. Data processing system 510 is only
one example of a suitable data processing system and is not
intended to suggest any limitation as to the scope of use or
functionality of embodiments of the invention described herein.
Regardless, data processing system 510 is capable of being
implemented and/or performing any of the functionality set forth
herein above.
[0055] In data processing system 510 there is a computer
system/server 512, which is operational with numerous other
general-purpose or special-purpose computing system environments or
configurations. Examples of well-known computing systems,
environments, and/or configurations that may be suitable for use
with computer system/server 512 include, but are not limited to,
personal computer systems, server computer systems, thin clients,
thick clients, handheld or laptop devices, multiprocessor systems,
microprocessor-based systems, set top boxes, programmable consumer
electronics, network PCs, minicomputer systems, mainframe computer
systems, and distributed cloud computing environments that include
any of the above systems or devices, and the like.
[0056] Computer system/server 512 may be described in the general
context of computer system executable instructions, such as program
modules, being executed by a computer system. Generally, program
modules may include routines, programs, objects, components, logic,
data structures, and so on that perform particular tasks or
implement particular abstract data types. Computer system/server
512 may be practiced in distributed cloud computing environments
where tasks are performed by remote processing devices that are
linked through a communications network. In a distributed cloud
computing environment, program modules may be located in both local
and remote computer system storage media including memory storage
devices.
[0057] As shown in FIG. 5, computer system/server 512 in data
processing system 510 is shown in the form of a general-purpose
computing device. The components of computer system/server 512 may
include, but are not limited to, one or more processors or
processing units 516, a system memory 528, and a bus 518 that
couples various system components including system memory 528 to
processor 516.
[0058] Bus 518 represents one or more of any of several types of
bus structures, including a memory bus or memory controller, a
peripheral bus, an accelerated graphics port, and a processor or
local bus using any of a variety of bus architectures. By way of
example, and not limitation, such architectures include Industry
Standard Architecture (ISA) bus, Micro Channel Architecture (MCA)
bus, Enhanced ISA (EISA) bus, Video Electronics Standards
Association (VESA) local bus, and Peripheral Component Interconnect
(PCI) bus.
[0059] Computer system/server 512 typically includes a variety of
computer system readable media. Such media may be any available
media that is accessible by computer system/server 512, and it
includes both volatile and non-volatile media, removable and
non-removable media.
[0060] System memory 528 can include computer system readable media
in the form of volatile memory, such as random access memory (RAM)
530 and/or cache memory 532. Computer system/server 512 may further
include other removable/non-removable, volatile/non-volatile
computer system storage media. By way of example only, storage
system 534 can be provided for reading from and writing to a
non-removable, non-volatile magnetic media (not shown and typically
called a "hard drive"). Although not shown, a magnetic disk drive
for reading from and writing to a removable, non-volatile magnetic
disk (e.g., a "floppy disk"), and an optical disk drive for reading
from or writing to a removable, non-volatile optical disk such as a
CD-ROM, DVD-ROM or other optical media can be provided. In such
instances, each can be connected to bus 518 by one or more data
media interfaces. As will be further depicted and described below,
memory 528 may include at least one program product having a set
(e.g., at least one) of program modules that are configured to
carry out the functions of embodiments of the invention.
[0061] Program/utility 540, having a set (at least one) of program
modules 542, may be stored in memory 528 by way of example, and not
limitation, as well as an operating system, one or more application
programs, other program modules, and program data. Each of the
operating system, one or more application programs, other program
modules, and program data or some combination thereof, may include
an implementation of a networking environment. Program modules 542
generally carry out the functions and/or methodologies of
embodiments of the invention as described herein.
[0062] Computer system/server 512 may also communicate with one or
more external devices 514 such as a keyboard, a pointing device, a
display 524, etc.; one or more devices that enable a user to
interact with computer system/server 512; and/or any devices (e.g.,
network card, modem, etc.) that enable computer system/server 512
to communicate with one or more other computing devices. Such
communication can occur via Input/Output (I/O) interfaces 522.
Still yet, computer system/server 512 can communicate with one or
more networks such as a local area network (LAN), a general wide
area network (WAN), and/or a public network (e.g., the Internet)
via network adapter 520. As depicted, network adapter 520
communicates with the other components of computer system/server
512 via bus 518. It should be understood that although not shown,
other hardware and/or software components could be used in
conjunction with computer system/server 512. Examples, include, but
are not limited to: microcode, device drivers, redundant processing
units, external disk drive arrays, RAID systems, tape drives, and
data archival storage systems, etc.
[0063] The present invention may be a system, a method, and/or a
computer program product. The computer program product may include
a computer readable storage medium (or media) having computer
readable program instructions thereon for causing a processor to
carry out aspects of the present invention.
[0064] The computer readable storage medium can be a tangible
device that can retain and store instructions for use by an
instruction execution device. The computer readable storage medium
may be, for example, but is not limited to, an electronic storage
device, a magnetic storage device, an optical storage device, an
electromagnetic storage device, a semiconductor storage device, or
any suitable combination of the foregoing. A non-exhaustive list of
more specific examples of the computer readable storage medium
includes the following: a portable computer diskette, a hard disk,
a random access memory (RAM), a read-only memory (ROM), an erasable
programmable read-only memory (EPROM or Flash memory), a static
random access memory (SRAM), a portable compact disc read-only
memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a
floppy disk, a mechanically encoded device such as punch-cards or
raised structures in a groove having instructions recorded thereon,
and any suitable combination of the foregoing. A computer readable
storage medium, as used herein, is not to be construed as being
transitory signals per se, such as radio waves or other freely
propagating electromagnetic waves, electromagnetic waves
propagating through a waveguide or other transmission media (e.g.,
light pulses passing through a fiber-optic cable), or electrical
signals transmitted through a wire.
[0065] Computer readable program instructions described herein can
be downloaded to respective computing/processing devices from a
computer readable storage medium or to an external computer or
external storage device via a network, for example, the Internet, a
local area network, a wide area network and/or a wireless network.
The network may comprise copper transmission cables, optical
transmission fibers, wireless transmission, routers, firewalls,
switches, gateway computers and/or edge servers. A network adapter
card or network interface in each computing/processing device
receives computer readable program instructions from the network
and forwards the computer readable program instructions for storage
in a computer readable storage medium within the respective
computing/processing device.
[0066] Computer readable program instructions for carrying out
operations of the present invention may be assembler instructions,
instruction-set-architecture (ISA) instructions, machine
instructions, machine dependent instructions, microcode, firmware
instructions, state-setting data, or either source code or object
code written in any combination of one or more programming
languages, including an object oriented programming language such
as Smalltalk, C++ or the like, and conventional procedural
programming languages, such as the "C" programming language or
similar programming languages. The computer readable program
instructions may execute entirely on the user's computer, partly on
the user's computer, as a stand-alone software package, partly on
the user's computer and partly on a remote computer or entirely on
the remote computer or server. In the latter scenario, the remote
computer may be connected to the user's computer through any type
of network, including a local area network (LAN) or a wide area
network (WAN), or the connection may be made to an external
computer (for example, through the Internet using an Internet
Service Provider). In some embodiments, electronic circuitry
including, for example, programmable logic circuitry,
field-programmable gate arrays (FPGA), or programmable logic arrays
(PLA) may execute the computer readable program instructions by
utilizing state information of the computer readable program
instructions to personalize the electronic circuitry, in order to
perform aspects of the present invention.
[0067] Aspects of the present invention are described herein with
reference to flowchart illustrations and/or block diagrams of
methods, apparatus (systems), and computer program products
according to embodiments of the invention. It will be understood
that each block of the flowchart illustrations and/or block
diagrams, and combinations of blocks in the flowchart illustrations
and/or block diagrams, can be implemented by computer readable
program instructions.
[0068] These computer readable program instructions may be provided
to a processor of a general-purpose computer, special-purpose
computer, or other programmable data processing apparatus to
produce a machine, such that the instructions, which execute via
the processor of the computer or other programmable data processing
apparatus, create means for implementing the functions/acts
specified in the flowchart and/or block diagram block or blocks.
These computer readable program instructions may also be stored in
a computer readable storage medium that can direct a computer, a
programmable data processing apparatus, and/or other devices to
function in a particular manner, such that the computer readable
storage medium having instructions stored therein comprises an
article of manufacture including instructions which implement
aspects of the function/act specified in the flowchart and/or block
diagram block or blocks.
[0069] The computer readable program instructions may also be
loaded onto a computer, other programmable data processing
apparatus, or other device to cause a series of operational steps
to be performed on the computer, other programmable apparatus or
other device to produce a computer implemented process, such that
the instructions which execute on the computer, other programmable
apparatus, or other device implement the functions/acts specified
in the flowchart and/or block diagram block or blocks.
[0070] The flowchart and block diagrams in the Figures illustrate
the architecture, functionality, and operation of possible
implementations of systems, methods, and computer program products
according to various embodiments of the present invention. In this
regard, each block in the flowchart or block diagrams may represent
a module, segment, or portion of instructions, which comprises one
or more executable instructions for implementing the specified
logical function(s). In some alternative implementations, the
functions noted in the block may occur out of the order noted in
the figures. For example, two blocks shown in succession may, in
fact, be executed substantially concurrently, or the blocks may
sometimes be executed in the reverse order, depending upon the
functionality involved. It will also be noted that each block of
the block diagrams and/or flowchart illustration, and combinations
of blocks in the block diagrams and/or flowchart illustration, can
be implemented by special-purpose hardware-based systems that
perform the specified functions or acts or carry out combinations
of special-purpose hardware and computer instructions.
[0071] The descriptions of the various embodiments of the present
invention have been presented for purposes of illustration, but are
not intended to be exhaustive or limited to the embodiments
disclosed. Many modifications and variations will be apparent to
those of ordinary skill in the art without departing from the scope
and spirit of the described embodiments. The terminology used
herein was chosen to best explain the principles of the
embodiments, the practical application or technical improvement
over technologies found in the marketplace, or to enable others of
ordinary skill in the art to understand the embodiments disclosed
herein.
REFERENCE NUMERALS
[0072] 10 component [0073] 12 data storage [0074] 14 customization
data [0075] 16 customization data [0076] 18 card type [0077] 20
location [0078] 22 location [0079] 24 location [0080] 26 data
representing location [0081] 30 database [0082] 32 firmware [0083]
34 controller [0084] 36 IO drawer [0085] 40 configuration rules
[0086] 510 data processing system [0087] 512 computer system/server
[0088] 514 external devices [0089] 516 CPU/data processing unit
[0090] 518 IO Bus [0091] 520 network adapter [0092] 522 IO
interfaces [0093] 524 display [0094] 528 memory [0095] 530 RAM
[0096] 532 cache [0097] 534 storage system [0098] 540
program/utility [0099] 542 program modules [0100] S100 Start [0101]
S102 Add component [0102] S104 Detect newly added component [0103]
S106 Read component type from data storage [0104] S108 Detect
component type with customization support [0105] S110 Read
customization from data storage [0106] S112 Check if customization
exists [0107] S114 Check if customization is supported [0108] S116
Check if previous customization exists [0109] S118 Erase previous
customization from the database [0110] S120 Store customization in
the database [0111] S122 Set component to operational [0112] S124
End [0113] S132 Disable functional capabilities and log
configuration error [0114] S200 Start [0115] S202 Add component
[0116] S204 Detect newly added component [0117] S206 Read component
type from data storage [0118] S208 Detect component type with
customization support [0119] S210 Read customization from data
storage [0120] S212 Check if customization exists [0121] S222 Set
component to operational [0122] S224 End [0123] S226 Query
customization data for specific location from the persistent
database [0124] S228 Check if previous customization exists [0125]
S230 Store previous customization data in the data storage of the
new component [0126] S232 Disable functional capabilities and log
configuration error [0127] S300 Start [0128] S302 Add component
[0129] S304 Detect newly added component [0130] S306 Read component
type from data storage [0131] S308 Detect component type with
customization support [0132] S310 Read customization from data
storage [0133] S312 Check if customization exists [0134] S314 Check
if customization is supported [0135] S316 Check if previous
customization exists [0136] S318 Erase previous customization from
the database [0137] S320 Store customization in the database [0138]
S322 Set component to operational [0139] S324 End [0140] S326 Query
customization data for specific location from the persistent
database [0141] S328 Check if previous customization exists [0142]
S330 Store previous customization data in the data storage of the
new component [0143] S332 Disable functional capabilities and log
configuration error
* * * * *