Abstract: An enhanced mechanism for providing data protection for variable length records utilizes high performance block storage metadata. In an embodiment, an emulated record that emulates a variable length record, such as a Count-Key-Data (CKD) record or an Extended-Count-Key-Data (ECKD) record, is generated by a Host Bus Adapter (HBA) of a mainframe system. The emulated record comprises a sequence of extended fixed-length blocks, each of which includes a data block and a footer. A confluence of the footers defines a high performance block storage metadata unit associated with the emulated record and includes a checksum that covers all data blocks and all footers of the entire emulated record. In one embodiment, the checksum is checked during transit of the emulated record between a HBA and a storage subsystem (e.g.

Abstract: An enhanced mechanism for providing data protection for variable length records utilizes high performance block storage metadata. In an embodiment, an emulated record that emulates a variable length record, such as a Count-Key-Data (CKD) record or an Extended-Count-Key-Data (ECKD) record, is generated by a Host Bus Adapter (HBA) of a mainframe system. The emulated record comprises a sequence of extended fixed-length blocks, each of which includes a data block and a footer. A confluence of the footers defines a high performance block storage metadata unit associated with the emulated record and includes a checksum that covers all data blocks and all footers of the entire emulated record. In one embodiment, the checksum is checked during transit of the emulated record between a HBA and a storage subsystem (e.g.

Abstract: A sequence of fixed-size blocks defines a page (e.g., in a server system, storage subsystem, DASD, etc.). Each fixed-size block includes a data block and a footer. A high performance block storage metadata unit associated with the page is created from a confluence of the footers. The confluence of footers has space available for application metadata. In an embodiment, the metadata space is utilized to record a “write activity level” metric, and a timestamp. The metric indicates the write frequency or “hotness” of the page, and its value changes over time as the activity level changes. Frequently accessed pages may be mapped to higher performance physical disks and infrequently accessed pages may be mapped to lower power physical disks.

Abstract: An enhanced mechanism for the allocation, organization and utilization of high performance block storage metadata provides a stream of data (e.g., in a server system, storage system, DASD, etc.) that includes a sequence of fixed-size blocks which together define a page. Each of the fixed-size blocks includes a data block and a footer. A high performance block storage metadata unit associated with the page is created from a confluence of the footers. Each footer in the confluence of footers has space available for application metadata, which are provided as one or more information units. At least one of the footers includes a Checksum field containing a checksum that covers at least the confluence of footers. This approach is advantageous in that it provides data integrity protection, protects against stale data, and significantly increases the amount of metadata space available for application use.

Abstract: Providing extended or end-to-end data integrity through layers of a system. In one aspect, information is to be transmitted between an application end of the system and a physical storage medium that stores the information for a database of the system, the information to be transmitted via a database server in a database server layer of the system. At least a portion of data protection is provided for the information, the data protection causing the information to be protected from corruption between a system layer and the physical storage medium, where the system layer is a separate layer provided closer to the application end of the system than the database server layer.

Abstract: A sequence of fixed-size blocks defines a page (e.g., in a server system, storage subsystem, DASD, etc.). Each fixed-size block includes a data block and a footer. A high performance block storage metadata unit associated with the page is created from a confluence of the footers. The confluence of footers has space available for application metadata. In an embodiment, the metadata space is utilized to record a “write activity level” metric, and a timestamp. The metric indicates the write frequency or “hotness” of the page, and its value changes over time as the activity level changes. Storage subsystem performance may be enhanced by mapping frequently accessed pages to higher performance physical disks and mapping infrequently accessed pages to lower power physical disks. This approach is advantageous in that the metric is recorded on a non-volatile basis and may be readily communicated between system components (e.g., between a host computer and a storage subsystem).

Abstract: A data storage system writes data supplied from a host to data storage in accordance with write I/O of an owning application. A workload manager directs the processing of the supplied data in accordance with the write I/O of the owning application, provides service workload identification describing the write I/O, a storage subsystem control adds the service workload identification to record set information for the data, and a journal management system stores the record set information in a journal. The journaled information, for example, may be employed for performing forensic analysis of data corruption events or to perform security audits, etc.

Abstract: A data storage system writes data supplied from a host to data storage in accordance with write I/O of an owning application. A workload manager directs the processing of the supplied data in accordance with the write I/O of the owning application, provides service workload identification describing the write I/O, a storage subsystem control adds the service workload identification to record set information for the data, and a journal management system stores the record set information in a journal. The journaled information, for example, may be employed for performing forensic analysis of data corruption events or to perform security audits, etc.

Abstract: An enhanced mechanism for providing data protection for variable length records utilizes high performance block storage metadata. In an embodiment, an emulated record that emulates a variable length record, such as a Count-Key-Data (CKD) record or an Extended-Count-Key-Data (ECKD) record, is generated by a Host Bus Adapter (HBA) of a mainframe system. The emulated record comprises a sequence of extended fixed-length blocks, each of which includes a data block and a footer. A confluence of the footers defines a high performance block storage metadata unit associated with the emulated record and includes a checksum that covers all data blocks and all footers of the entire emulated record. In one embodiment, the checksum is checked during transit of the emulated record between a HBA and a storage subsystem (e.g.

Abstract: An enhanced mechanism for providing data protection for variable length records utilizes high performance block storage metadata. In an embodiment, an emulated record that emulates a variable length record, such as a Count-Key-Data (CKD) record or an Extended-Count-Key-Data (ECKD) record, is generated by a Host Bus Adapter (HBA) of a mainframe system. The emulated record comprises a sequence of extended fixed-length blocks, each of which includes a data block and a footer. A confluence of the footers defines a high performance block storage metadata unit associated with the emulated record and includes a checksum that covers all data blocks and all footers of the entire emulated record. In one embodiment, the checksum is checked during transit of the emulated record between a HBA and a storage subsystem (e.g.

Abstract: An enhanced mechanism for the allocation, organization and utilization of high performance block storage metadata provides a stream of data (e.g., in a server system, storage system, DASD, etc.) that includes a sequence of fixed-size blocks which together define a page. Each of the fixed-size blocks includes a data block and a footer. A high performance block storage metadata unit associated with the page is created from a confluence of the footers. Each footer in the confluence of footers has space available for application metadata, which are provided as one or more information units. At least one of the footers includes a Checksum field containing a checksum that covers at least the confluence of footers. This approach is advantageous in that it provides data integrity protection, protects against stale data, and significantly increases the amount of metadata space available for application use.

Abstract: Providing extended or end-to-end data integrity through layers of a system. In one aspect, information is to be transmitted between an application end of the system and a physical storage medium that stores the information for a database of the system, the information to be transmitted via a database server in a database server layer of the system. At least a portion of data protection is provided for the information, the data protection causing the information to be protected from corruption between a system layer and the physical storage medium, where the system layer is a separate layer provided closer to the application end of the system than the database server layer.

Abstract: A data storage system writes data supplied from a host to data storage in accordance with write I/O of an owning application. A workload manager directs the processing of the supplied data in accordance with the write I/O of the owning application, provides service workload identification describing the write I/O, a storage subsystem control adds the service workload identification to record set information for the data, and a journal management system stores the record set information in a journal. The journaled information, for example, may be employed for performing forensic analysis of data corruption events or to perform security audits, etc.

Abstract: A data storage system writes data supplied from a host to data storage in accordance with write I/O of an owning application. A workload manager directs the processing of the supplied data in accordance with the write I/O of the owning application, provides service workload identification describing the write I/O, a storage subsystem control adds the service workload identification to record set information for the data, and a journal management system stores the record set information in a journal. The journaled information, for example, may be employed for performing forensic analysis of data corruption events or to perform security audits, etc.

Abstract: A pressure support system that comprises a patient circuit, a docking assembly, and a tank. The patient circuit delivers a pressurized flow of breathable gas to a patient. The docking assembly has an inlet and an outlet that is adapted to receive the pressurized flow of breathable gas, and is also adapted to be connected with the patient circuit. The tank is constructed and arranged to be removably connected with the docking assembly, and enables the pressurized flow of breathable gas to pass therethrough. The tank is also adapted to contain a liquid such that a humidity level of the pressurized flow of breathable gas is elevated as the pressurized flow of breathable gas passes therethrough.

Abstract: A hand-grippable adhesive tape applicator is provided for building construction and other environments. Pressure feedback and integrated slidable cutting mechanism features are included which provide improved tape application performance. Unique tape supply spool and take-up reel assemblies also are provided which enhance tape applicator performance. A patterned applicator roller also is provided to allow tape application to be performed with reduced user-applied force.

Abstract: A fastener driving device includes a housing containing an engine for driving a fastener through a flooring board and into a sub-floor, a nosepiece through which fasteners are driven, a magazine for supplying a plurality of fasteners for the engine to drive, and a shoe mounted for movement relative to the nosepiece. The shoe locates the engine relative to the flooring board so that the fastener is driven into the flooring board at an angle. The shoe includes a bottom workpiece engaging surface for engaging a top surface of the flooring board, and the nosepiece includes a forward workpiece engaging surface for engaging a front surface of the flooring board. The forward surface extends a distance below the bottom surface. One of the bottom surface and the forward surface is movable with respect to the other to adjust the distance that the forward surface extends below the bottom surface.

Abstract: A kettle for heating water or other liquid may have a container with a top portion made separately from a lower portion and permanently secured thereto. The top portion may have a fill opening that may be registered with an opening in the lower portion and receive a lid to cover the fill opening. A spout liner may extend from the container and be at least partially surrounded by a spout jacket. The spout liner may have a rolled or flanged portion that forms a seal between the spout liner and the spout jacket or that engages with the spout jacket. A handle may be integrally formed with the spout jacket and/or the top portion, e.g., molded together in a unitary form.

Abstract: A kettle for heating water or other liquid has a lid and lid actuator to move the lid between open and closed positions. The lid actuator may be connected to the container and movable relative to the opening about a pivot that is below a pivot about which the lid may move between the closed and open positions. The lid actuator may also lock the lid in position, such as in the open or closed position. The lid and lid actuator may also be arranged for movement independent of each other.