Abstract: A computer-implemented method according to one embodiment includes receiving at an encryption daemon a key request from a storage device; implementing, by the encryption daemon, a secure communications channel between the encryption daemon and an encryption key server; sending the key request from the encryption daemon to the encryption key server, utilizing the secure communications channel; receiving, from the encryption key server at the encryption daemon, an encrypted response, utilizing the secure communications channel; decrypting, by the encryption daemon, the encrypted response to obtain the requested key, and sending the requested key from the encryption daemon to the storage device.

Abstract: A computer-implemented method according to one embodiment includes receiving at an encryption daemon a key request from a storage device; implementing, by the encryption daemon, a secure communications channel between the encryption daemon and an encryption key server; sending the key request from the encryption daemon to the encryption key server, utilizing the secure communications channel; receiving, from the encryption key server at the encryption daemon, an encrypted response, utilizing the secure communications channel; decrypting, by the encryption daemon, the encrypted response to obtain the requested key, and sending the requested key from the encryption daemon to the storage device.

Abstract: A computer processor subsystem, e.g. called a “target”, in response to receiving an update to vital product data of the system from a source computer processor subsystem, examines the update to detect the vital product data of the target computer processor subsystem stored by the source computer processor subsystem; and, in response to the detected vital product data being incorrect, the target computer processor subsystem forwards its correct vital product data to the source computer processor subsystem having the incorrect vital product data. A computer processor subsystem is the authoritative reference for its vital product data.

Abstract: A computer processor subsystem, e.g. called a “target”, in response to receiving an update to vital product data of the system from a source computer processor subsystem, examines the update to detect the vital product data of the target computer processor subsystem stored by the source computer processor subsystem; and, in response to the detected vital product data being incorrect, the target computer processor subsystem forwards its correct vital product data to the source computer processor subsystem having the incorrect vital product data. A computer processor subsystem is the authoritative reference for its vital product data.

Abstract: A method to coordinate requests submitted to a data storage and retrieval system from two or more operator input stations, whereby an initialization request comprising a requested operation is provided at a first time to the data storage and retrieval system. At that first time the method provides a current history of previously-submitted commands to perform the requested operation. The method also generates a request history token at that first time. The first history is displayed to the user. The user then determines if the current history includes the requested operation. If the first history does not include the requested operation, the user at a second time submits a command to perform the requested operation. The method generates at that second time a current history token, and determines if the current history token matches the request history token. If the current history token matches the request history token, then the method performs the requested operation.

Abstract: A method to coordinate requests submitted to a data storage and retrieval system from one or more operator input stations, whereby an initialization request comprising a requested operation is provided at a first time to the data storage and retrieval system. At that first time the method provides a current history of previously-submitted commands to perform the requested operation. The method also generates a request history token at that first time. The first history is displayed to the user. The user then determines if the current history includes the requested operation. If the first history does not include the requested operation, the user at a second time submits a command to perform the requested operation. The method generates at that second time a current history token, and determines if the current history token matches the request history token. If the current history token matches the request history token, then the method performs the requested operation.