Source: http://www.google.fr/patents/US8631175
Timestamp: 2018-01-16 16:02:57
Document Index: 493294453

Matched Legal Cases: ['art 2', 'art 3', 'art 4', 'art 1', 'art 1', 'Application No. 12']

Brevet US8631175 - Facilitating transport mode input/output operations between a channel ... - Google Brevets
A method of performing an input/output operation includes: generating by a channel subsystem at least one command message including one or more device command words (DCWs), at least one DCW including a data count and a suppress-length indication (SLI) configured to instruct a control unit whether to...http://www.google.fr/patents/US8631175?utm_source=gb-gplus-shareBrevet US8631175 - Facilitating transport mode input/output operations between a channel subsystem and input/output devices
Numéro de publication US8631175 B2
Numéro de demande US 13/780,711
Date de publication 14 janv. 2014
Date de dépôt 28 févr. 2013
Date de priorité 30 juin 2011
Autre référence de publication CA2821233A1, CN103562893A, CN103562893B, EP2593874A1, US8473641, US20130007300, US20130246661, WO2013000603A1
Numéro de publication 13780711, 780711, US 8631175 B2, US 8631175B2, US-B2-8631175, US8631175 B2, US8631175B2
Inventeurs Susan K. Candelaria, Scott M. Carlson, Daniel F. Casper, John R. Flanagan, Roger G. Hathorn, Matthew J. Kalos, Louis W. Ricci, Dale F. Riedy, Harry M. Yudenfriend
Citations de brevets (254), Citations hors brevets (166), Classifications (11), Événements juridiques (2)
Facilitating transport mode input/output operations between a channel subsystem and input/output devices
US 8631175 B2
A method of performing an input/output operation includes: generating by a channel subsystem at least one command message including one or more device command words (DCWs), at least one DCW including a data count and a suppress-length indication (SLI) configured to instruct a control unit whether to continue to perform the I/O operation in response to an incorrect length condition; forwarding the at least one command message to the control unit; receiving an incorrect length (IL) value from the control unit and storing an IL indicator in a subchannel-status word, the IL indicator representing the IL value, the IL value being a first IL value in response to a first SLI value and the data count not matching the amount of data required, the IL value being a second IL value in response to a second SLI value and the data count not matching the amount of data required.
1. A method of performing an input/output (I/O) operation initiated by an I/O operation instruction at a host computer system configured for communication with a control unit, the control unit in communication with one or more devices, the method comprising:
generating at least one command message specifying an I/O operation by a channel subsystem of the host computer system, the at least one command message including one or more device command words (DCWs), each DCW associated with an I/O command, wherein at least one DCW of the one or more DCWs includes a data count and a suppress-length indication (SLI), the SLI configured to instruct a control unit whether to continue to perform the I/O operation in response to the control unit detecting an incorrect length condition, the incorrect length condition detected in response to the data count not matching an amount of data required to perform the I/O operation command, wherein the data required is one of data available at the control unit for a read operation command and data required by the control unit for a write operation command;
forwarding the at least one command message to the control unit;
receiving an incorrect length (IL) value from the control unit, the IL value being a first IL value in response to the SLI being a first SLI value and the data count not matching the amount of data required, the IL value being a second IL value in response to the SLI being a second SLI value and the data count not matching the amount of data required; and
responsive to receiving the IL value from the control unit, storing an IL indicator in a subchannel-status word, the IL indicator representing the IL value.
2. The method of claim 1, wherein the at least one DCW includes a command chaining flag indicating that a subsequent DCW is logically connected to the at least one DCW and is to be performed by the control unit after the control unit executes the at least one DCW, and the SLI instructs the control unit to continue command chaining and execute the subsequent DCW in response to the control unit detecting the incorrect length condition.
3. The method of claim 1, wherein the SLI is a value in an SLI field in the at least one DCW, the value being one instructing the control unit to continue the I/O operation when the incorrect length condition is detected, and the value being zero instructing the control unit to terminate the I/O operation when the incorrect length condition is detected.
4. The method of claim 1, wherein the at least one DCW includes the SLI including an SLI field having a value of one in response to the SLI being the second SLI value and a value of zero in response to the SLI being the first SLI value, and the channel subsystem is configured receive a transport response message returned from the control unit in response to executing or terminating the I/O operation, the transport response message including the IL value in an incorrect length (IL) field that indicates whether the I/O operation was terminated due to the incorrect length condition, the IL field having a value of one in response to the SLI being the first SLI value and the data count not matching the amount of data required, the IL field having a value of zero in response to at least one of the SLI being the second SLI value and the data count matching the amount of data required.
5. The method of claim 4, wherein the transport response message includes a DCW Offset field that indicates which of the plurality of DCWs caused the incorrect length condition to be detected.
sending a process login (PRLI) request message to the control unit, the PRLI request message configured to initialize a link between the channel subsystem and the control unit, the PRLI request message including a header having a value that indicates whether the channel subsystem supports use of the SLI; and
receiving a (PRLI) response message from the control unit, the PRLI response message including a header having a value that indicates whether the control unit supports use of the SLI indication.
This application is a continuation of U.S. patent application Ser. No. 13/173,754 filed Jun. 30, 2011, the entire disclosure of which is incorporated herein by reference.
The present disclosure relates generally to input/output (I/O) processing, and in particular, to providing features to facilitate transport mode I/O operations.
The channel subsystem and I/O device may operate in a transport mode that supports the transfer of one or more command control blocks to transfer data between the I/O devices and memory. A transport control word (TCW) specifies one or more I/O commands to be executed. For commands initiating certain I/O operations, the TCW designates memory areas associated with the operation, the action to be taken whenever a transfer to or from the area is completed, and other options.
Another embodiment includes a method of performing an input/output (I/O) operation initiated by an I/O operation instruction at a host computer system configured for communication with a control unit, the control unit in communication with one or more devices. The method includes: generating at least one command message specifying an I/O operation by a channel subsystem of the host computer system, the at least one command message including one or more device command words (DCWs), each DCW associated with an I/O command, wherein at least one DCW of the one or more DCWs includes a data count and a suppress-length indication (SLI), the SLI configured to instruct a control unit whether to continue to perform the I/O operation in response to the control unit detecting an incorrect length condition, the incorrect length condition detected in response to the data count not matching an amount of data required to perform the I/O operation command, wherein the data required is one of data available at the control unit for a read operation command and data required by the control unit for a write operation command; forwarding the at least one command message to the control unit; receiving an incorrect length (IL) value from the control unit, the IL value being a first IL value in response to the SLI being a first SLI value and the data count not matching the amount of data required, the IL value being a second IL value in response to the SLI being a second SLI value and the data count not matching the amount of data required; and responsive to receiving the IL value from the control unit, storing an IL indicator in a subchannel-status word, the IL indicator representing the IL value.
Additional features and advantages are realized through the techniques of the present embodiment. Other embodiments and aspects are described herein and are considered a part of the claimed invention. For a better understanding of the invention with the advantages and features, refer to the description and to the drawings.
FIG. 2 depicts one embodiment of a transport control word (TCW);
FIG. 3 depicts one embodiment of a transport command control block (TCCB);
FIG. 4 depicts one embodiment of a transport command information unit (IU) that includes the TCCB of FIG. 3;
FIG. 5 depicts one embodiment of a transport command header of the transport command IU of FIG. 4;
FIG. 6 depicts one embodiment of a transport command area header (TCAH) of the TCCB of FIG. 4;
FIG. 7 depicts one embodiment of a transport command area (TCA) of the TCCB of FIG. 4;
FIG. 8 is a table describing exemplary determinations of various data counts for uni-directional data transfer operations;
FIG. 9 is a table describing exemplary determinations of various data counts for bidirectional data transfer operations;
FIG. 10 depicts one embodiment of a device command word (DCW);
FIG. 11 depicts one embodiment of a control flags field of the DCW of FIG. 10;
FIG. 12 depicts exemplary command codes and flags for DCWs;
FIG. 13 depicts one embodiment of a transport command area extension (TCAX);
FIG. 14 depicts one embodiment of a CBC-offset block;
FIG. 15 is a flow chart illustrating an embodiment of a method of performing a transport mode I/O operation;
FIG. 16 depicts embodiments of transport-data IUs used to transport input and output data between a channel and a control unit and/or I/O device;
FIG. 17 depicts an embodiment of an interruption-response block (IRB) including a Subchannel-Status Word (SCSW);
FIGS. 18A-18D depict exemplary status qualifiers for the SCSW of FIG. 17;
FIG. 19 depicts one embodiment of a transport response IU; and
FIG. 20 depicts one embodiment of a status area of the transport response IU of FIG. 19.
Embodiments of the present invention facilitate input/output (I/O) processing in a computer system. In one embodiment, transport commands are provided to manage the I/O operation and the transfer of data via a channel path. Transport commands transfer command meta-information (TCMI) that is used to manage data transfer checking and the transfer of additional DCWs. TCMI may be specified by a transport control word (TCW) is defined in one or more data transport information units (IUs) for defining, specifying and verifying information regarding data to be transferred in an I/O operation. Transport commands may include an interrogate command, a transfer-CBC-Offset Block (TCOB) command, and transfer-TCA Extension (TTE) command.
In one embodiment, I/O processing is facilitated by enabling a host computer to increase the number of commands that can be sent to a device for an I/O operation. For example, TCMI in the form of a Transport Command Area Extension (TCAX) can be sent from the host to a device to increase the number of commands that can be associated with an I/O operation. In one embodiment, the TCAX may be specified by a TCW and is sent via a device command word (DCW), referred to as a Transfer TCA Extension (TTE) DCW, that includes commands to be performed in addition to commands sent in a Transport Command Area (TCA). In one embodiment, the TCAX is specified by the TTE DCW and is sent as output data to the control unit.
I/O processing can also be facilitated by providing a means by which an I/O device can continue an I/O operation when an incorrect length record is encountered. For example, a DCW-incorrect-length and FCX-incorrect length indication facility may be installed in the host system and a control unit or device. The facility provides for Incorrect Length (IL) checking that may be performed by a control unit. A suppress-incorrect-length or Suppress Length Indication (SLI) field may be added to a DCW sent to a device. When this bit is activated, DCW chaining is permitted to continue when an incorrect length condition is detected by the control unit.
I/O processing can also be facilitated by providing a means for sending both read and write commands to a device in a single I/O operation. Prior art TCW channel programs specify either all write commands or all read commands. A bi-directional operation can be specify by setting one or more flags in a transport command header (TCH) of a command IU, e.g., by setting both read and write flags to one and providing both a read and a write data count. In addition, a flag in an initiation or login message such as a Process Login (PRLI) request message can be set to indicate that the channel subsystem supports bidirectional data transfer. A response message such as a PRLI accept message can include a flag that can be set to indicate whether the device supports bi-directional data transfer. If bi-directional data transfer is supported by both the host and the control unit, the device will not report an error if both read and write flags are set in the command IU. This capability is an improvement over prior art Fibre Channel protocols, which do not support bi-directional data transfer operations. As described herein, “bi-directional data transfers” are transfers of both input and output data that are performed within a single TCW I/O operation, e.g., sending and executing both read and write commands within a single TCW I/O operation.
FIG. 1 illustrates an exemplary embodiment of an I/O processing system 100 that includes a host computer system 102 that includes a data storage and/or processing system such as a zSeries® mainframe computer by International Business Machines Corporation (IBM®). IBM is a registered trademark of International Business Machines Corporation, Armonk, N.Y., USA. Other names used herein may be registered trademarks, trademarks or product names of International Business Machines Corporation or other companies. The host computer system 102 includes various processing, storage and communication elements. In one embodiment, the host computer system 102 includes one or more central processing units (CPUs) 104, memory components such as a main storage or memory 106, an expanded storage or memory 108, one or more operating systems (OSs) 110 that are executed by one or more of the CPUs 104. For example, one CPU 104 can execute a Linux® operating system 110 and/or a z/OS® operating system 110 as different virtual machine instances. CPU 104 is the controlling center of the I/O processing system 100. It contains sequencing and processing facilities for instruction execution, interruption action, timing functions, initial program loading, and other machine-related functions. CPU 104 is coupled to the main memory 106 and/or expanded memory 108 via a connection 113, such as a bidirectional or unidirectional bus.
The host computer system 102 also includes a channel subsystem 114 that provides a communication interface between the host system 101 and various I/O devices 116, which may controlled by one or more control units 118. I/O devices include equipment such as printers, magnetic-tape units, direct-access-storage devices, displays, keyboards, communications controllers, teleprocessing devices, and sensor-based equipment. In the description herein, the terms “control unit” and “device” may be used interchangeably, or a control unit may be considered to include one or more devices. The channel subsystem 114 directs the flow of information between the I/O devices 116 and the host computer system 102. It relieves the CPUs 104 of the task of communicating directly with the I/O devices 116 and permits data processing to proceed concurrently with I/O processing. The channel subsystem 114 is coupled to the CPUs 104, the main memory 106 and/or the expanded memory 108 via a connection 120, such as a bus.
In one embodiment, the channel subsystem 114 is connected to each I/O device 116 via a respective “channel path” 122 that connects the channel subsystem 114 to each control unit 118 via a connection 124 such as a serial or parallel link. Control units 118 may be attached to the channel subsystem 114 via more than one channel path 122, and an I/O device 116 may be attached to more than one control unit 118 and/or I/O device 116. In all, an individual I/O device 116 may be accessible by multiple channel paths. A channel path can use various types of connections, such as a parallel interface, a serial-I/O interface and a FICON I/O interface. For example, a serial channel path may include one or more optical fibers connected to a control unit 118 via, e.g., a dynamic switch 126 in a Fibre channel fabric, and a parallel interface may include a number of electrical or fiberoptic conductors.
In one embodiment, the channel subsystem 114 includes one or more individual channels 128 that are each connected to one or more control units 118 and/or I/O devices 116 via one or more channel paths 122. Each channel 128 includes processing electronics such as a local channel microprocessor 130 and a local channel memory 132 that is connected to and accessible by the local channel microprocessor 130. The local channel memory 132 may include information such as a channel-program designation, a channel-path identifier, a device number, a device count, status indications, as well as information on path availability and functions pending or being performed.
Also located within each channel 128 are one or more subchannels. Each subchannel is a data structure located within a channel memory 132 that provides information concerning an associated I/O device 116 and its attachment to the channel subsystem 114. The subchannel also provides information concerning I/O operations and other functions involving the associated I/O device 116. The subchannel is the means by which the channel subsystem 114 provides information about associated I/O devices 116 to the CPUs 104. In one embodiment, the number of subchannels provided by the channel subsystem is independent of the number of channel paths 122 to the associated I/O devices 116. For example, a device 116 accessible through alternate channel paths 122 still is represented by a single subchannel.
Each control unit 118 provides logic to operate and control one or more I/O devices 116 and adapts, through the use of common facilities, the characteristics of each I/O device 116 to the link interface provided by a channel 128. The common facilities provide for the execution of I/O operations, indications concerning the status of I/O devices 116 and the control unit 118, control of the timing of data transfers over a channel path 122 and certain levels of I/O device control. A control unit 118 may be housed separately, or may be physically and logically integrated with an I/O device, the channel subsystem, or a CPU.
One or more of the above components of the I/O processing system 100 are further described in “IBM® z/Architecture Principles of Operation,” Publication No. SA22-7832-08, 9th Edition, August 2010, which is hereby incorporated herein by reference in its entirety.
I/O operations are described as any operation that involves the transfer of data between the host computer system 102 and I/O devices 116. As described herein, an I/O operation includes the communications between the channel subsystem 114 and a device 116 (via, in one embodiment, a control unit 118) in which a single command (e.g., a channel command word or CCW), a single command message including multiple commands (e.g., a transport command information unit or transport command control block (TCCB)), or multiple chained commands (e.g., multiple CCWs) are sent from the channel subsystem 114 to a device. The I/O operation may also include one or more response messages generated by the device 116 or an associated control unit 118 in response to receiving and/or executing the command or chained commands.
In one embodiment, I/O operations are initiated with a device 116 by the execution of I/O instructions generated by an OS 110 that designate the subchannel associated with the device 116. Such instructions are executed in the host system by a CPU 104 by sending parameters to a channel 128 or subchannel to request that the channel subsystem 114 perform various functions in an I/O operation.
For example, the CPU 104 executes a “START SUBCHANNEL” instruction by passing parameters to the target subchannel requesting that the channel subsystem 114 perform a start function with the I/O device 116 associated with the subchannel. The channel subsystem 114 performs the start function by using information at the subchannel, including the information passed during the execution of the START SUBCHANNEL instruction, to find an accessible channel path to the device 116, and to execute the I/O operation once a channel path has been selected.
When an instruction such as a START SUBCHANNEL instruction is executed by the CPU 104, a channel 128 commences performing the I/O operation. In one embodiment, the channel subsystem 114 operates under a High Performance FICON (HPF) protocol for communication between the channel subsystem 114 and the devices 116 and/or control units 118. FICON and HPF are described further in “Fibre Channel: Single-Byte Command Code Sets Mapping Protocol-4 (FC-SB-4),” T11 Project 2122-D, Revision 3.00, Sep. 22, 2009, which is hereby incorporated herein by reference in its entirety.
In one embodiment, execution of the START SUBCHANNEL instruction passes the contents of an operation request block (ORB) to the channel subsystem 114. The ORB specifies a channel program that includes an address of one or more command words (e.g., a channel command word or a transport command word described further below). There are two modes of subchannel operation. In one embodiment, the host computer system 102 operates in a command mode and specifies command word(s) in the form of a channel command word (CCW). In another embodiment, the host system operates in a transport mode and specifies command word(s) in the form of a transport command word (TCW).
A subchannel may enter transport mode when an FCX (Fibre Channel Extensions) facility is installed and the start function is set at the subchannel as the result of the execution of a START SUBCHANNEL instruction that specifies a TCW channel program. The subchannel remains in transport mode until the start function is reset at the subchannel. At all other times, the subchannel is in command mode.
In command mode, the channel executes a CCW channel program that include a single channel-command word or a sequence of channel-command words executed sequentially that control a specific sequence of channel operations. A control unit executes a CCW I/O operation by decoding, accepting, and executing CCW commands by an I/O device. One or more CCWs arranged for sequential execution form a CCW channel program and are executed as one or more I/O operations, respectively.
The fibre-channel-extensions (FCX) facility is an optional facility that provides for the formation of a transport mode channel program that is composed of a transport control word (TCW) that designates a transport-command-control block (TCCB) and a transport-status block (TSB). The TCCB includes a transport-command area (TCA) which contains a list of one or more (e.g., up to 30) I/O commands that are in the form of device-command words (DCWs). A TCW and its TCCB may specify either a read or a write operation. In one embodiment, a FCX-bidirectional-data-transfer facility may be installed in a system that supports transport mode operations, that allows the host computer system 102 to specify transfer of both input and output data in a single transport mode I/O operation if the connected device 116 and control unit 118 supports bidirectional-data transfer. When a control unit 118 recognizes bi-directional data transfers, a TCW and its TCCB may, depending on the device, specify both read and write data transfers.
In the transport mode, a single transport command word (TCW) specifies a location in memory of a TCCB (as well as a location in memory 106 or 108 of one or more data areas) that is sent in a single message instead of separate individual CCWs in the command mode. A control unit 118 executes a transport mode I/O operation by decoding, accepting, and executing a TCCB and the individual DCWs included therein. If the ORB specifies a TCW channel program, the channel subsystem 114 uses information in the designated TCW to transfer the TCCB to a control unit 118. The contents of the TCCB are ignored by the channel subsystem 114 after the TCCB is transferred to the control unit 118 and only have meaning to the control unit 118 and the associated I/O device 116.
In an exemplary embodiment, the control unit 118 generates a response message in response to executing the channel program. The control unit 118 may also generate a response message without executing the channel program under a limited number of communication scenarios, e.g., to inform the channel subsystem 114 that the channel program will not be executed. The control unit 118 may include a number of elements to support communication between the I/O communications adapter and I/O devices, as well as in support of channel program execution. For example, the control unit 118 can include control logic to parse and process messages, in addition to one or more queues, timers, and registers to facilitate communication and status monitoring.
FIG. 2 illustrates an embodiment of a transport-control word (TCW) 140, which is stored in the host system (e.g., main memory 106) and specifies at least one control block that is to be transferred to a control unit 118 from a channel 128. In one embodiment, the control block is a transport-command-control block (TCCB) whose contents are to be transported to the control unit 118 and I/O device 116 for processing. When the TCW 140 specifies a TCCB, the TCCB includes a TCA that specifies one or more device-command words (DCWs) and associated options. For a DCW that specifies a command which initiates the transfer of data (with the exception of control data contained within the TCCB), the TCW 140 designates one or more storage areas where the data is located.
In one embodiment, the TCA includes a Transfer TCA Extension (TTE) command that is provided to transfer additional DCWs and/or control data in addition to those that can be accommodated in the TCCB. The TTE transfers a TCA extension (TCAX) to a control unit (which includes at least one DCW) and is considered a logical extension of the TCA to which it is associated, by, for example chaining the last DCW of the TCCB to the first DCW of the TTE.
Referring again to FIG. 2, and embodiment of the TCW 140 is a 64-byte control block that is designated on a 64-byte boundary. The TCW includes various fields described below.
For example, a number of flag fields 142 indicate whether direct or indirect data addressing is being used to locate input data, output data or the TCCB. An Output transport-indirect-data addressing (TIDA) field indicates whether output data is directly or indirectly addressed. For example, when word 0, bit 7 of the TCW 140 is zero and output data is specified, an output-data-address field 144 designates an output data location in absolute storage. When bit 7 is one, the output-data-address field 144 designates an absolute address of a TIDA word (TIDAW) or the first TIDAW in a list of TIDAWS (a TIDAL) that designates the output storage location or locations, respectively. An Input TIDA field indicates whether input data is directly or indirectly addressed. For example, when word 0, bit 5 is zero and input data is specified, an input-data-address field 146 designates the absolute address of the input storage location (i.e., where input data is to be stored. When bit 5 is one, the input-data-address field 146 designates the absolute address of a TIDAW or the first TIDAW in a TIDAL that designates the input storage location or locations. A Transport-command-control-block TIDA (TCCB-TIDA) field indicates whether the TCCB is directly or indirectly addressed. For example, when word 0, bit 6 is zero, a TCCB-address field 148 designates the absolute address of the TCCB for the TCW, and when bit 6 is one, the TCCB-address field 148 designates the absolute address of a TIDAW or TIDAL that designate the location or locations of the TCCB.
The TCW 140 also includes a Transport-Command-Control-Block Length (TCCBL) field 150 that specifies the length in bytes of the TCCB. For example, the TCCBL field includes an unsigned integer whose value (e.g., when added to 20 for unidirectional data transfers or when added to 24 for bidirectional data transfers) specifies the length of the TCCB in bytes.
A Read Operations (R) field 152 is non-zero (e.g., bit 14 of word 1 is one) when indicating the number of bytes to be transferred into main memory 106. A Write Operations (W) field 154 is non-zero (e.g., bit 15 of word 1 is one) when indicating the number of bytes to be transferred from main storage. If the R-field 152 and the W-field 154 are both one, a program-check condition is recognized, unless the target device 116 and control unit 118 support bi-directional data transfer. If the W-bit is one and the TCW is an interrogate TCW, a program-check condition is recognized.
The Output-Data Address field 144 indicates the location in storage of any output data to be sent to a device. For example, when bit 15 of word 1 (the W-field bit 154) is one and bit 7 of the flags field 142 (the output-TIDA flag) is zero, words 2-3 designate the 64-bit output location in absolute storage. When the W-bit is one and the output-TIDA flag is one, words 2-3 designate the 64-bit location in absolute storage of a TIDAW or list of TIDAWs that designate the output storage location or locations. The Input-Data Address field 146 indicates the location to which any input data is to be stored when received from a device. For example, when the bit 14 of word 1 (the R-field bit 152) is one and bit 5 of the flags field 142 (the input-TIDA flag) is zero, words 4-5 designate the 64-bit input location in absolute storage. When the R-bit is one and the input-TIDA flag is one, words 4-5 designate the location in absolute storage of a TIDAW or list of TIDAWs that designate the input storage location(s).
A Transport-Status-Block Address 156 specifies a location in storage of a transport-status block for the TCW. For example, words 6-7 designate the 64-bit location in absolute storage of the transport-status block for the TCW.
A Transport-Command-Control-Block Address field 148 specifies one or more (direct or indirect) addresses of the TCCB. For example, if the TCCB-TIDA bit (bit 6 of the flags field) is zero, words 8-9 designate 64-bit location in absolute storage of the TCCB. When the TCCB-TIDA bit is zero, the TCCB is specified to reside in a contiguous area of storage. If the transport-command-control-block-TIDA bit is one, words 8-9 designate the 64-bit location in absolute storage of a TIDAW or list of TIDAWs that designate the location in absolute storage of the TCCB. When the TCCB-TIDA bit is one, the TCCB may be specified to reside in noncontiguous areas of storage
The Output Count field 158 specifies the number of output bytes for the TCW. For example, when bit 15 of word 1 (the W-bit) is one, word 10 contains the unsigned integer total count of output bytes for the TCW. The Input-Count field 160 specifies the number of input bytes for the TCW. For example, when bit 14 of word 1 (the R-bit) is one, word 11 contains the unsigned integer total count of input bytes for the TCW.
If the TCW specifies an interrogation operation, an Interrogate-TCW Address field 162 indicates a location in storage of an Interrogate TCW. For example, when a START SUBCHANNEL instruction designates a TCW, word 15 of the TCW is not checked. However, when a CANCEL SUBCHANNEL instruction designates a subchannel that is start pending for a TCW channel program and is not status pending, bits 1-31 of word 15 of the TCW designated by START SUBCHANNEL specify the 31-bit location in absolute storage of the interrogate-TCW that is used to initiate an interrogate operation for the subchannel. If word 15 contains zeros when CANCEL SUBCHANNEL is issued, an interrogate operation is not initiated. When CANCEL SUBCHANNEL is issued, bit 0 of word 15 must be zero, otherwise a program-check condition is recognized with interrogate-failed status indicated. When CANCEL SUBCHANNEL is issued and bits 1-31 of word 15 do not contain zeros, bits 1-31 of word 15 must designate a storage location on a 64-byte boundary, otherwise a program-check condition is recognized with interrogate-failed status indicated. Word 14 may be reserved for extending the interrogate-TCW-address field to 64 bits.
Referring to FIGS. 3 and 4, the transport-command-control block (TCCB) 170 includes one or more individual commands as part of a TCW I/O operation, and is sent to a control unit 118 and/or device 116 by a channel 128 via a channel path. The TCCB 170 relieves the channel of having to send multiple messages or information units, and also transfers the responsibility of executing the operation to the control unit and removes the need for the control unit 118 to send responses for each command. Instead, the control unit 118 can execute all of the commands and send a response upon completion of the operation.
The TCCB 170 is variable in length, may contain header and trailer information, and one or more (e.g., from 1 to 30) commands as device-command words (DCWs) that are logically linked (e.g., chained) such that they are executed by the control unit 118 in a sequential manner. The TCCB 170 may reside as a single block of contiguous storage or may reside as multiple blocks of noncontiguous storage. For example, the TCCB-TIDA flag in the TCW 140 described above is used to specify whether the TCCB resides in contiguous storage.
Examples of a TCCB are shown in FIGS. 3 and 4. As shown in FIG. 4, the TCCB 170 may be sent from a channel 128 to a control unit 118 as part of a transport command information unit (IU) 172 that is sent to the control unit 118 to initiate an I/O operation. In one embodiment, the transport command IU 172 is made up of an 8-byte SB-4 header 174, followed by a 4-byte transport command header (TCH) 176, and the TCCB 170. The TCCB 170 includes a 16-byte transport-command-area header (TCAH) 178, a variable length transport-command area (TCA) 180, and a transport command area trailer (TCAT) 182. The TCAT 182 may further include a 4-byte LRC field 184, a 4-byte data-transfer length (DL) field 186, and for bidirectional operations, a 4-byte bidirectional read data-transfer length (BRDL) field 188. These fields are described further below.
Referring to FIG. 4, the SB-4 header 174 provides FC-4 addressing information to identify the logical path and the device 116 for the data transfer. The SB-4 header 174 provides information including a channel image ID and a control unit ID for a logical path between a channel 128 and a control unit 118, as well as a device ID.
Referring to FIG. 5, the TCH 176 includes information about the TCCB 170 and the associated device operations. In one embodiment, the TCH 176 contains 4 bytes and immediately follows the SB-4 header 174 in the transport command IU 172. The TCH 176 includes fields such as a length field (“L1”) 190, a read field (“R”) 192 and a write field (“W”) 194. The L1 field (located at e.g., bits 24-29), specifies the length, in words, of the TCA 180 plus the 1-word LRC field 184 that directly follows the TCA 180. For example, for control units 118 that do not support bidirectional operations, the total amount of data transferred in the transport command IU 172 is equal to the L1 field plus 8 (that is, the L1 field plus the 2-word SB-4 header, the 1-word TCH, the 4-word TCAH and the 1-word DL); otherwise, the control unit recognizes a transport-command IU integrity error due to a data count error. For control units that support bidirectional operations, the total amount of data transferred in the transport-command IU 172 is equal to the L1 field plus 8 (that is, the L1 field plus the 2-word SB-4 header, the 1-word TCH, the 4-word TCAH and the 1-word DL) or the L1 field plus 9 (that is, the L1 field plus the 2-word SB-4 header, the 1-word TCH, the 4-word TCAH, the 1-word DL, and the 1-word BRDL for a bidirectional operation); otherwise, the control unit shall recognize a transport-command IU integrity error due to a data count error. If a transport-command IU integrity error is not recognized, the location of the LRC in the TCCB is located based on the L1 field and the LRC check can be performed.
The Read (R) field 192 specifies that the TCA 180 includes one or more read or input commands. In the embodiment of FIG. 5, the R field 192 is an R bit, bit 30, that indicates, when set to one, that the TCA 180 contains one or more commands that transfer read data. When the R bit is set to zero, the TCA 180 does not contain any commands that transfer read data. When the R bit is one and the W bit (e.g., bit 31) is zero, the operation is referred to as a read operation. When both the R and W bits are set to zero, the TCA 180 does not contain any commands that transfer read or write data, indicating that the I/O operation does not perform data transfer. When both the R and W bits are set to one, the TCA 180 may contain commands that transfer both read and write data, and the operation is referred to as a bidirectional operation. The device 116 or control unit 118 recognizes a TCH content error due to a read-write conflict if a bidirectional operation is specified and the control unit 118 does not support bidirectional operations, or the control unit 118 supports bidirectional operations but the transport-command IU 172 does not contain the BRDL field 188. When the R bit is zero and the control unit 118 or device 116 encounters a command in the TCA 180 that attempts to transfer read data, a TCCB content error is recognized due to an invalid read attempt.
The Write (W) field 194 specifies that the TCA 180 includes one or more write or output commands. In the embodiment of FIG. 5, the W field is a W bit, bit 31, that, when set to one, indicates the TCA 180 includes one or more commands that transfer write data. When the bit is set to zero, the TCA does not include any commands that transfer write data. When the W bit is one and the R bit (bit 30) is zero, the operation is referred to as a write operation. When the W bit is zero and the control unit 118 or device 116 encounters a command in the TCA 180 that specifies a write command, a TCCB content error is recognized due to an invalid write condition.
Referring to FIG. 6, an embodiment of the TCA Header (TCAH) 178 includes information about the TCA 180 and the operations described therein, such as the TCA length and device indications. In this embodiment, Byte 3 of word 1 is an “L2” length field 196 that contains an unsigned binary integer that specifies the length, in bytes, of the TCA 180 plus words 2 and 3 of the TCA header, plus the 4-byte LRC field 184 that directly follows the TCA 180. A Service-Action Code field 198 (e.g., bytes 0-1 of word 2) includes an unsigned integer value that specifies the type of operation specified by the TCCB. For example, a Hex value of ‘1FFE’ indicates a SB-4 Device I/O operation, and a Hex value of ‘1FFF’ indicates SB-4 Device support functions. The Priority Number field 200 (e.g., byte 3 of word 2) includes the control unit I/O priority number.
Referring to FIG. 7, the transport-command area (TCA) 180 is a variable length area that contains one or more (e.g., from 1 to 30) commands as device-command words (DCWs) 202. The length of the TCA 180, in one embodiment, is an in integral number of 4-byte words. For DCWs 202 that specify device control data, the TCA 180 also contains the control data associated with each DCW 202. Each DCW 202 that specifies control data reduces the maximum-DCW capacity by one or more DCWs, depending on the size of the command-associated data. For DCWs 202 that specify input or output data, the TCW 140 designates the associated storage area or areas and the DCW designates the count of bytes to transfer. In one embodiment, the maximum size of the TCA is 240 bytes. As shown in the embodiment of FIG. 7, when sufficient space exists in the TCA 180 for the entire DCW 202, the DCW 202 begins on the word boundary that follows the previous DCW 202 or the control data associated with the previous DCW 202. When the last DCW 202 in the TCA 180 specifies control data that is not an integral number of words, the subsequent LRC field 184 begins on the word boundary that follows the control data.
For some devices, the list of DCWs 202 may extend beyond what will fit in the TCA 180. In such instances, a TCA extension (TCAX) field may be specified that includes additional DCWs and transferred as if the TCAX were output data (e.g., transferred as part of an output transport-data IU). However, the TCAX is treated as a logical continuation of the TCA 180 instead of as transfer data. The TCAX is specified in the TCA 180 by a transfer-TCA-extension (TTE) DCW. The TCAX and TTE DCW are described further below, and embodiments of the TCAX are shown in FIGS. 12 and 13.
As shown in FIGS. 3 and 4, the TCCB may include a transport-command-area trailer (TCAT) 182 that provides additional information about the TCCB, including various count information. In one embodiment, when uni-directional data transfer is specified (either the R-bit or the W-bit is set to one) or no data transfer is specified (both the R-bit and W-bit in the TCW are set to zero), the TCAT 182 is two words in length. When bidirectional data transfer is specified (both the R-bit and the W-bit in the TCW are set to one), the TCAT 182 is three words in length.
For example, when uni-directional data transfer is specified, the transport count or data length (DL) field 186 specifies the 32-bit unsigned integer count of total data to be transferred (the “transport count value”). When a read operation is specified (the TCW R-bit is one), the value in the transport-count field in the TCAT may be determined by summing the count field values in the DCWs 202 that each specify a read-type command. The sum is rounded upwards to the nearest multiple of 4, and the rounded sum is increased by 4 to arrive at the transport-count value. When a read operation is specified, the transport count value should be equal to the value in the TCW input-count field 160, rounded upwards to the next multiple of 4, plus 4.
When a write operation is specified (the W-bit in the TCW is one), the count field values in the DCWs 202 that specify a write command are summed. In addition, the count field values in all transport-command DCWs (described further below) that specify the transfer of transport command-meta information (TCMI), plus the size of the reserved fields in the TCMI are added to the sum. (Note that the size of a TCMI reserved field may be zero). The total of the counts of any TIDAW-specified control block check (CBC) or cyclical redundancy check (CRC) bytes and padding bytes is added to the sum. The sum is rounded upwards to the nearest multiple of 4, and the rounded sum is increased by 4 giving the transport-count value. When a write operation is specified, the transport count value should be equal to the value in TCW output-count field 158, rounded upwards to the next multiple of 4, plus 4. When neither a read nor a write operation is specified (both the W-bit and R-bit in the TCW are zero), the transport count value should be zero.
When bidirectional data transfer is specified, the DL field 186 is the write count and specifies the 32-bit unsigned integer count of total output data to be transferred. The transport count value in the DL field (write-count field) in the TCAT 182 is determined as described above for a write operation. The bi-directional read data length (BRDL) field 188 specifies the 32-bit unsigned integer count of total input data to be transferred. The transport count value for the BDRL field 188 is determined as described above for read operations.
In one embodiment, for a write operation or bidirectional operation, the DL field shall contain a 4-byte unsigned binary integer that specifies the number of bytes to be transferred by the channel to the control unit for the operation and includes all intermediate and final pad and CRC bytes, and if a COB is included in the first transport-data IU of the write operation, it also includes the COB, any COB pad bytes and the COB CRC bytes. If a TTE DCW is present in the TCA, the DL field also includes the TCAX, any TCAX pad bytes and TCAX CRC bytes.
FIGS. 8 and 9 are tables summarizing the determination of the TCW input-count, output-count, and the TCAT transport count values for unidirectional and bi-directional transfers, respectively.
For a bidirectional operation, a bidirectional-read-data-length (BRDL) field includes a 4-byte unsigned binary integer that specifies the number of bytes to be transferred by the control unit to the channel for the operation and includes any pad bytes required to round to a word boundary if not already on a word boundary plus 4 bytes for CRC. For operations that are not bidirectional operations, the device shall recognize a TCH content error due to a read-write conflict if the transport-command IU contains the BRDL field.
Referring to FIG. 10, a device-command word (DCW) 202 specifies a command to be executed. For commands initiating certain I/O operations, it designates the count of bytes on which the operation is performed, the action to be taken whenever transfer to or from storage is completed, and other options. The storage area or areas associated with a DCW data-transfer operation are designated, depending on the operation specified by the command, by the input-data-address field 146 or the output-data-address field 144 of the TCW 140 that designates the TCCB 170 that includes the DCW 202. Whether the input-data-address field 146 or the output data-address field 144 designates the storage directly or indirectly is specified by the input-TIDA and output-TIDA flags in the TCW 140.
In one embodiment, the DCW 202 is an 8-byte control block that is designated in the TCW 140 on a word boundary. The DCW 202 includes fields such as a command code field 204, a control flags field 206, a control data count 208 and a DCW data count 210.
The Command Code field 204 (e.g., bits 0-7 of word 0) specifies the operation to be performed. Whether a command is valid is device dependent and dependent on the value of the service-action code field 198 in the TCAH 178. Basic commands include read, write, control, sense and transport. The channel subsystem 114 distinguishes among the following operations: control, output forward (write), input forward (read, sense, sense ID), input backward (read backward), branching (transfer in channel) and transport. Some commands, when executed, do not result in the transfer of data but cause the device to chain and start execution of the next command when all of the conditions for command chaining are satisfied. Each of the basic operations is described below.
A read command initiates execution of a device operation that performs device-to-channel data transfer. A write command initiates execution of a device operation that performs channel-to-device data transfer. A control command initiates execution of a device operation that makes use of control data provided in the DCW. The sense command is similar to a read command, except that the data is obtained from sense indicators rather than from a record source. Control commands and associated control data are provided for management of the specific I/O device and control of the device during execution of an I/O command. A transport command is provided to manage the I/O operation and the transfer of data via a channel path, and is not device specific. Such commands manage the transport of control block checking data such as cyclical redundancy check (CRC) data and the transport of additional DCWs in transport-data IUs.
The Control-Data (CD) Count field 208 specifies the number of control data bytes associated with a DCW 202. For example, byte 3 of word 0 specifies the length of the control data, in bytes. If the command code specifies a command that requires control data and byte 3 of word 0 specifies a control-data count that is less than required for the command, a unit-check condition or TCCB content error is recognized. If the command code specifies a command that requires control data and byte 3 of word 0 contains zero or contains a value that specifies data past the end of the TCA (or past the end of the specified TCAX), a device-detected-program check condition or TCCB content error is recognized.
The DCW Data Count field 210 specifies the byte count of the data (e.g., data to be transferred for the read or write operation, i.e., customer data) designated by the TCW for the present DCW 202. For example, the DCW data count is included in word one of the DCW 202 of FIG. 10, and specifies the 32-bit unsigned integer count of bytes in the storage area designated by the TCW for this DCW. The DCW data count field 210 indicates the number of bytes to be transferred between the channel and control unit during execution of the DCW, not including any pad or CRC bytes.
Referring to FIG. 11, in one embodiment, the DCW 202 includes various control flags 206. A chain-command (CC) flag 212 specifies an intent to perform chaining of commands. Upon normal completion of the current device operation and after recognition of device end at the device, chaining of commands causes the next DCW 202 in the TCA 180 to be executed. The CC flag 212 is set to zero in the last DCW in the TCA. In the embodiment of FIG. 10, bit 9 of word 0 (the CC bit), when one, specifies the chaining of commands. When one, the bit causes the operation specified by the next DCW to be initiated upon normal completion of the current DCW. When the control-data count is zero, the next DCW immediately follows the DCW in the TCA or in a TCAX. When the control-data count is not zero, the next DCW immediately follows the control-data, rounded to a word boundary, specified for the DCW. When the chain-command flag is one, in one embodiment, the next DCW location in the TCA or in a TCAX is determined by adding eight and the value in the CD count field to the location of the current DCW and rounding upwards to the nearest word boundary. If the chain-command flag is one in a DCW in a TCA, and the next DCW location is past the end of the TCA, and a TCAX is specified, the next DCW is at the beginning of the specified TCAX.
The control flags field, in one embodiment, include a Suppress Length Indication (SLI) field 214. When the DCW-incorrect-length facility is supported by a channel 128 and a control unit 118, a bit (e.g., bit 2) is provided in the SLI flag field 214 that controls whether command chaining is to occur on an incorrect-length condition and whether incorrect length is to be indicated in a transport-response IU by the control unit when an incorrect-length condition is detected by the control unit 118. An incorrect-length condition is detected by the control unit if the DCW data count does not match the amount of data required by the device for a write DCW or if the DCW data count does not match the amount of data available at the device for a read DCW. When the DCW-incorrect-length facility is not supported by the channel and control unit, bit 2 is reserved and set to zero by the channel and ignored by the control unit.
When the SLI flag 214 is one, incorrect-length indication is suppressed. When both the CC and SLI flags are ones, command chaining takes place regardless of the presence of an incorrect-length condition. When the SLI flag 214 is one and an incorrect-length condition exists for the current DCW, command chaining, if indicated, shall be permitted and the control unit continues execution of the next following DCW. In one embodiment, The SLI flag bit should be set to one or otherwise activated in all DCWs where suppression of the incorrect-length indication is desired.
If the SLI flag is zero and an incorrect-length condition exists for a DCW, command chaining, if indicated, is not permitted and the control unit 118 aborts the I/O operation. In the channel subsystem 114, if the SLI flag is zero and an incorrect-length condition exists, processing of the TCA 180 is terminated and the subchannel is made status pending with incorrect length indicated in the subchannel status. When an incorrect-length condition exists for a DCW 202 and the SLI flag 214 in the DCW is set one, data transfer is performed as described below, otherwise the operation is terminated and an abnormal termination condition shall be reported for the operation.
For a read DCW 202, if the DCW data count is greater than the amount of data available at the device 116 for the command, then the following applies. If the CC flag 212 is one (chaining is indicated), the data available at the device 116 is transferred to the channel 128 and pad bytes (which are set to zero) are transferred so that the amount of data transferred for the DCW 202 is equal to the DCW data count. All data transferred, including pad bytes, are included in any computation of CRC required for the operation. If the CC flag 212 is zero (chaining is not indicated), the data available at the device shall be transferred to the channel and either no additional data shall be transferred or pad bytes (set to zero) are transferred so that the amount of data transferred for the DCW is equal to the DCW data count. The data transferred plus any pad bytes shall be included in the computation of CRC required for the operation. It is model dependent whether pad bytes are transferred for this case. If the DCW data count is less than the amount of data available at the device for the command, only an amount of data equal to the DCW data count is transferred to the channel 128 for the DCW 202. Only the data transferred shall be included in the computation of CRC required for the operation.
For a write DCW 202, if the DCW data count is greater than the amount of data required by the device 116 for the command, then the following applies. If the CC flag 212 is one (chaining is indicated), the amount of data specified by the DCW data count shall be transferred to the control unit 118. The data transferred shall be used in the computation of any CRC required for the operation, and data not required by the device 116 is discarded. If the CC flag is zero (chaining is not indicated), the amount of data required by the device 116 is transferred to the control unit 118. Additional data is transferred up to the next intermediate CRC word or until the data count for the DCW is exhausted. All data transferred is used in the computation of any CRC required for the operation. If the DCW data count is less than the amount of data required by the device 116 for the command, the amount of data specified by the DCW data count is transferred to the control unit 118. The data transferred is used in the computation of any CRC required for the operation.
For a write DCW 202 in which the DCW data count is greater than the amount of data required by the device 116 for the command and the CC flag 212 is zero (chaining is not indicated), the amount of data required by the device 116 is transferred. Data then continues to be transferred until the next CBC is specified to be inserted or until the total amount to be transferred is equal to the DCW data count. Exemplary command codes are shown in FIG. 12, which illustrates six TCW commands and indicates which flags are defined for each command. A transport-command DCW is a type of DCW that does not specify a specific data transfer command (i.e., customer data that is requested to be transferred by a host computer instruction), but rather specifies a transport command that performs a support function associated with a transport-mode I/O operation. A transport-command DCW may specify control data and may also specify the transfer of transport-command-meta information (TCMI). TCMI includes data that is utilized to control transfer functions in the I/O operation, such as the status of an I/O operation at a device, information regarding additional DCWs that do not fit in or can be accommodated by a current TCCB, and control block checking (CBC) information such as cyclical redundancy check (CRC) data.
When a transport-command DCW specifies the transfer of TCMI to a device, the TCMI is transferred as output data (e.g., in a transport-data IU). The size of the TCMI is command dependent and is, for example, a multiple of 4. The TCMI may be extended by 4 reserved bytes when the size of the TCMI is an even multiple of 4, TIDAWs are used to specify the output storage areas, the insert-CBC flag is one in the last TIDAW used to specify the storage containing the TCMI, the chain-command bit is one in the transport command DCW that specifies the TCMI, and a subsequent DCW specifies the transfer of a TCMI or output data. Note that when a transport command specifies the transfer of a TCMI to a device and the TCMI is extended by 4 reserved bytes because all of the preceding conditions are met, the 4 reserved bytes are not included in the data-count value in the transport command DCW but are included in the following: the count value in the last TIDAW used to specify the storage containing the TCMI, the output-count value in the TCW and the transport-count value in the associated TCCB (for unidirectional data transfers or the write-count value in the associated TCCB for bidirectional transfer).
In one embodiment, TCMI includes interrogate information (via an Interrogate DCW), a CBC-Offset Block (via a Transfer-CBC-Offset Block DCW) and a TCA extension (via a Transfer-TCA Extension DCW).
FIG. 13 illustrates an embodiment of data specified by one type of transport-command DCW, referred to as a Transfer TCA Extension (TTE) command, which is included in a TCA 180 of a TCCB 170 and specifies a TCA extension (TCAX) 220 that is to be transferred to a control unit 118. The TCAX is considered a logical extension of the TCA 180. For some devices 116, the list of DCWs 202 associated with an I/O operation exceeds the number of DCWs that can be accommodated in the TCA 180. In such an instance, a TTE DCW may be included at the end of the TCW 140, which specifies a TCAX 220 that is transferred as output data (e.g., in a data-transport IU). The content of the TTE DCW may include a command code that includes the transfer-TCA extension command (e.g., value of 50 hex)
For example, a TCA 180 is variable in length with a maximum size of 240, and a DCW is 8 bytes. Thus, in this example, a maximum of 30 DCWs may be transmitted in a TCCB 170. However, for DCWs 202 that specify control commands that require control data, the control data immediately follows each DCW 202 in the TCCB. Thus, TCCBs 170 containing such commands are limited to less than 30 DCWs. The TTE DCW may be used to specify additional DCWs needed for the I/O operation that do not fit in the TCA 180.
As shown in FIG. 13, The TCA Extension (TCAX) is a variable-length area that is the logical continuation of the TCA 180 in another transport-command IU or TCCB, and includes a list of DCWs and associated control data. The TCAX contains one or more additional DCWs and associated control data for a TCW I/O operation (in addition to those transferred in an initial TCCB), and can be sent in another TCCB or in a transport-data IU to extend a list of DCWs required for an I/O operation. In one embodiment, the length of the TCAX is an integral multiple of 4.
As shown in FIG. 13, in one embodiment, the TCAX 220 includes a DCW 202 and/or control data for a previous DCW 202. When the last information in the TCAX 220 is a DCW 202, the end of that DCW 202 defines the end of the meaningful information in the TCAX 220. When the last information in the TCAX 220 is control data and the control data ends on a 4-byte boundary, the end of the control data defines the end of the meaningful information in the TCAX 220. When the last information in the TCAX 220 is control data and the control data does not end on a 4-byte boundary, padding bytes are appended to the control data to reach a 4-byte boundary and the end of the padding bytes define the end of the meaningful information in the TCAX 220. When the size of the meaningful information in the TCAX 220 divided by four is an odd number, there are no reserved bytes; otherwise, the four bytes immediately following the meaningful information in the TCAX 220 are reserved and should contain zeros. When control data for the last DCW 202 in the TCA 180 is contained in the TCAX 220, that control data is the first data in the TCAX 220. Additional DCWs and control data in the TCAX 220 are processed as defined for the TCA 180.
In one embodiment, when a TCOB DCW (described further below) is not present in the TCA 180, the TTE DCW is the first DCW 202 in the TCA 180. When a TCOB DCW is present in the TCA 180, the TTE DCW is the second DCW 202 in the TCA 180. The TTE DCW data count specifies the length of the TCAX 220 and may be an integral multiple of four bytes. The TTE DCW control-data count is zero and the chain command flag in the TTE DCW is set to one. The TTE DCW data does not include the TCAX CRC or TCAX pad bytes.
A TTE command (TTE DCW) should be sent to a device that indicates support for the TTE command and is sent when the TCA length has a certain maximum (e.g., 60 words) and the control data for the last DCW in the TCA extends beyond the last byte in the TCA, or the TCA length is greater than, e.g., 58 words, and one or more additional DCWs are required for the I/O operation. When a COB is provided in the write transport-data IU, the TCAX shall follow the COB CRC. When a COB is not provided, the TCAX shall be sent in the first write transport-data IU of the I/O operation.
Another type of DCW is a Transfer CBC-Offset Block (TCOB) DCW, which is a command that transfers a CBC Offset Block (COB) to a control unit. CBC data refers to control block checking data that is used to verify that the correct amount of input or output data is being transferred in an I/O operation. In one embodiment, the CBC data is cyclical redundancy check (CRC) data, the COB is a CRC Offset Block, and the TCOB DCW is a Transfer CRC-Offset Block DCW. Generally, a cyclic redundancy check (CRC) is an error-detecting code configured to detect accidental changes to raw data being sent between a channel 128 and a control unit 118. A CRC-enabled device (e.g., the channel 128) calculates a short, fixed-length binary sequence for each block of data to be sent or stored and appends it to the data, forming a codeword or “CRC word”. For example, when CRC generation is provided, the channel 128 generates a CRC on the data sent and inserts the value calculated at the end of the last data byte. When a CRC word is received or read, the receiving device (e.g., the control unit 118) either compares its check value with one freshly calculated from the data block, or equivalently, performs a CRC on the whole codeword and compares the resulting check value with an expected residue constant. If the check values do not match, then the block contains an error in the transferred data. Although the CBC data is described in the embodiments herein as CRC data, it is not so limited.
An exemplary TCOB DCW specifies that a COB is transported to a device. This exemplary TCOB has a command code that contains a transfer CRC-Offset Block command (e.g., a value of 60 hex). The chain-command flag is one. When the CD Count 208 of the TCOB DCW is not zero, the COB immediately follows the TCOB DCW in the TCA 180 and the CD Count 208 specifies the number of CRC Offsets in the COB multiplied by four. When the CD Count 208 is zero, the COB is specified as TCMI in the output data, the location of the COB is specified by the output-data-address field 146 in the TCW, and the count field specifies the number of CRC offsets in the COB multiplied by four.
As shown in FIG. 14, a COB 222 specifies the location of intermediate CRC words within the transport data for a write or read data transfer (e.g., in a transport-data IU). In one embodiment, a COB is provided when the first DCW 202 in a TCA 180 contains the TCOB command, i.e., is a TCOB DCW. Intermediate CRC offsets are CRC words located between data in a data transfer IU and located before the end of the IU. The COB 222 contains a list of 1-word values, referred to as CRC Offsets 224, each of which identify the byte offset of each intermediate CRC word in the transport data. For example, the COB is a variable-length control block that includes a list of 4-byte entries, each of which identifies the offset of a CRC specified by a TIDAW to be inserted in the output data.
In the embodiment shown in FIG. 14, the COB 222 includes 1 to N+1 words (CRC Offset words 224) of intermediate-CRC offsets. If the COB 222 is provided in a transport-data IU, then the COB may also includes 0 or 1 words of pad bytes and 1 word of CRC. Pad bytes may be provided so that the word containing the CRC will be on a word boundary that is not on a doubleword boundary. The last word of the COB shall contain a CRC that covers intermediate CRC offsets 0 through N and the pad word, if present. If the COB is provided as control data for the TCOB DCW, then there shall be no COB padding or CRC and the control-data count shall be equal to 4 times the number of intermediate-CRC-offset fields in the COB.
For write operations, the TCOB DCW specifies that a COB is transported to a device 116. The TCOB DCW command code includes the TCOB command which is a value of, e.g., 60 hex. The location of the COB is determined by the control-data count and may be provided in either the first write transport-data IU of an I/O operation or as control data following the TCOB DCW of an I/O operation. For example, when the CD count of the TCOB DCW is not zero, the COB 222 immediately follows the TCOB DCW in the TCA 180 and the CD count specifies the number of CRC offsets in the COB multiplied by 4. When the CD count is zero, the COB 222 is specified as TCMI that is transferred with the output data, and the location of the COB is specified by the output-data-address field 144 in the TCW 140.
Each intermediate-CRC offset 224 in the COB 222 indicates the relative offset, in bytes, from the first byte of data in a transport-data IU. If the COB 222 is provided in a transport-data IU, the first byte of data for the write transfer is either the first byte following the COB CRC if a TCAX 220 is not being provided or the first byte following the TCAX CRC if a TCAX is being provided. If the COB is provided in the TCA 180 as DCW control data, the first byte of data for the write transfer is either the first byte in the transport-data IU if a TCAX 220 is not being provided or the first byte following the TCAX CRC if a TCAX 220 is being provided. When provided in a transport-data IU, the COB is provided in the first write transport-data IU of an I/O operation.
Yet another type of transport-command DCW is an interrogate DCW that is used to determine the state of a TCW I/O operation at a device 116. The interrogate command does not initiate an operation at the device 116, does not affect the state of the device 116 and does not reset allegiances associated with the device 116 and an associated logical path. An exemplary interrogate DCW includes an interrogate command code (e.g., contains a value of 40 hex). With the exceptions of the command code, SLI flag, count and CD-count fields, all other fields in the DCW should contain zeros, otherwise a device-detected program-check condition. If the CD count of the interrogate DCW is greater than zero, interrogate data is specified.
An interrogate operation is performed on a logical path and device 116 that has a TCW I/O operation in progress in order to obtain information regarding the state of the operation at the device 116. In one embodiment, the TCCB 170 for an interrogate operation includes a single DCW with an interrogate device command code (e.g., X′40). The TCAH 178 for an interrogate operation may contain the R bit set to one to specify a read data transfer for the operation. An interrogate operation is recognized at the control unit 118 when the control unit 118 accepts a transport-command IU that specifies the interrogate command. When an interrogate operation has been recognized at the control unit 118 and the control unit 118 is able to successfully perform the interrogate command, the control unit 118 may provide status in a transport-response IU that includes interrogate extended status describing the state of the logical path and device address specified by the interrogate transport-command IU.
Referring to FIG. 15, an embodiment of a method of performing a transport mode I/O operation 300 is shown. The method includes one or more stages 301-305. In one embodiment, the method includes the execution of all of the stages 301-305 in the order described. However, certain stages may be omitted, stages may be added, or the order of the stages changed.
In stage 301, the host computer (e.g., the OS 110) executes an instruction (e.g., START SUBCHANNEL) that causes an ORB to be transferred to a channel subsystem 114, that specifies a TCW 140. In one embodiment, program-check conditions related to the validity of TCW fields specific to capturing status and transporting a specified TCCB 170 are checked by the channel subsystem 114 to determine whether to transport the TCCB 170 to an I/O device 116. If such a program-check condition exists, the TCCB 170 is not transported and the program-check condition is recognized. For example, the TCCB-address field 148 is checked that it designates an available storage location. If the TCCB-TIDA flag is one, the TCCB-address field 148 is also checked that it designates an address that is on a quadword boundary. Additional program check conditions are further described below.
In stage 302, a TCW I/O operation is initiated with an I/O device (via, for example, a control unit 118) when a channel 128 transfers a transport-command IU 172 that includes a control block, such as a transport-command-control block (TCCB) 170 and associated control information for a TCW 140 to a selected device 116. In one embodiment, information associated with the execution of an I/O operation and the operation of a device (e.g., commands, input data and output data) is transferred between the channel 128 and the control unit 118 as Information Units (IUs). In one embodiment, the IUs are in the form of SB-4 Information Units (IUs).
In one embodiment, IUs or other messages are sent between the channel and the control unit via one or more exchanges. An exchange pair consisting of two unidirectional exchanges, one used by a channel 128 to send IUs and one used by a control unit 118 to send IUs, are required for all SB-4 link-control functions and for all SB-4 device-level functions that are executed in command mode. A single bi-directional exchange, referred to as a transport exchange, is used for device-level functions executed in transport mode. IUs that a channel 128 sends during the execution of an SB-4 link-control function or the execution of an SB-4 device-level function in command mode are restricted to one exchange, and IUs which a channel receives during the operation are restricted to a different exchange. The exchange on which the channel 128 sends IUs is referred to as the outbound exchange, and the exchange on which the channel 128 receives IUs is referred to as an inbound exchange. When both an outbound exchange and an inbound exchange simultaneously exist between a channel 128 and a control unit 118 for the execution of the same link-level or device-level function, an exchange pair is said to exist, and the control unit 118 is said to be connected to the channel 128. A channel program which is executed in a single connection uses only one exchange pair. If the connection is removed by the closing of the exchanges during the channel program, a new exchange pair is generated to complete the channel program. A channel 128 can initiate an exchange pair by sending an IU which opens a new exchange (or, an initiation IU) as an unsolicited command or unsolicited control information category. A control unit 118 can initiate an exchange pair by sending an initiation IU as an unsolicited control or unsolicited data information category.
UIs, which a channel and control unit send during the execution of an I/O operation that is performed in transport mode are restricted to a single, bi-directional exchange referred to as a transport exchange. A channel 128 opens a transport exchange by sending a transport-command IU as an unsolicited command category (an Initiation IU). A channel 128 may open multiple transport exchanges, each for a different device 116 or for the same device 116 on different logical paths. A new transport exchange may be opened for a specific device on a logical path when a transport exchange already exists for that device and logical path to perform an interrogate operation; otherwise, the channel 128 waits for the existing transport exchange or exchange pair to be closed before initiating a new transport exchange for the device on the logical path.
In stage 303, the control unit 118 receives the TCCB 170 and transport-command IU 172, and may accept the TCCB 170 if certain conditions are met. When a transport-command IU 172 is accepted, the TCCB 170 is considered current at the control unit 118 until execution of the TCCB 170 at the control unit 118 is considered completed. If the transport-command IU 172 is not accepted because of an error condition, a transport-response IU is returned to the channel 128 with an initial status flag set to one to indicate that the error occurred prior to initiating execution of the TCCB 170 at the device 116. The control unit 118 may provide error information in status and I/O extended status fields in the transport-response IU (described below) to identify the transport-command IU error. In one embodiment, the exemplary conditions described below should be satisfied in order for the transport-command IU 172 to be accepted at the control unit 118:
1) The transport-command IU satisfies the following integrity checks:
a) For control units that do not support bidirectional operations, the L1 field in the TCH plus 8 shall specify an amount of data that is equal to the amount of data received by the control unit for the transport-command IU, otherwise, a transport-command IU integrity error due to a data count error shall be recognized;
b) For control units that support bidirectional operations, the L1 field in the TCH plus either 8 or 9 shall specify an amount of data that is equal to the amount of data received by the control unit for the transport-command IU, otherwise, a transport-command IU integrity error due to a data count error shall be recognized; and
c) The LRC field in the TCCB shall be valid, otherwise a transport-command IU integrity error due to invalid LRC error shall be recognized.
2) The specified logical path shall be established, otherwise a logical-path-not-established error shall be recognized;
3) For those commands that require the device to be installed and ready, the device address shall specify a device that is installed and ready, otherwise an address-exception condition shall be recognized;
4) The R and W bits shall not both be set to one in the TCH if bidirectional data transfer is not supported by the control unit or the transport-command IU does not contain the BRDL field; otherwise a TCH content error shall be recognized;
5) The TCCB in the transport-command IU shall satisfy all of the following conditions, otherwise, a TCCB content error shall be recognized:
a) The L2 field shall specify a length that is exactly 8 bytes greater than the L1 field and contain a value that is at least 20 bytes and not more than 252 bytes;
b) Byte 1 of word 0 of the TCAH shall be zero;
c) The format control field in the TCAH shall be equal to hex ‘7F’;
d) The service-action code in the TCAH shall contain a valid value (see 8.13.4.4);
e) If the R and W bits are both set to zero, the data-length (DL) field shall be zero; and
6) If another TCW I/O operation is in progress for the logical path and device address specified in the transport-command IU, the service-action code shall specify hex ‘1FFF’ and the command code in the first DCW of the TCA shall specify the interrogate command code, otherwise a non-interrogate-second-operation error shall be recognized.
In one embodiment, the channel 128 considers a connection to exist when the transport-command IU 172 is sent, and the control unit 118 considers a connection to exist when the transport-command IU 172 is accepted. The channel 128 is thus not aware of whether the control unit 118 has accepted the TCCB 170 or of the progress of the I/O operation at the device 116 until the I/O operation is terminated by the control unit 118 with a transport-response IU. In one embodiment, the channel 128 can set a time window for which to receive a response from the control unit, so that if the channel does not receive a transport-response IU within the window, the channel recognizes a transport command timeout.
In stage 304, when the TCCB 170 has been accepted, the control unit 118 processes the TCA 180 and executes each DCW 202. The DCW 202 being executed is recognized as the current DCW. A DCW 202 becomes current when it is the first DCW of a transport mode program (i.e., the first DCW in a TCCB) and has been selected by the I/O device 116 for execution or when, during command chaining, a subsequent DCW 202 takes over control of the I/O operation. The first DCW to be executed may be considered to be located at offset zero of the TCA 180 in the TCCB 170. Each additional DCW in the channel program is located in the TCA 180 (or in a TCAX 220) and is used when the DCW is needed by the I/O device 116.
Command chaining is controlled by the DCW chain command (CC) flag in the DCW. This flag specifies the action to be taken upon the exhaustion of the current DCW. Chaining takes place between successive DCWs within the TCA. When a TCAX is specified, chaining also takes place between the last DCW in the TCA and the first DCW in the TCAX, and between successive DCWs within the TCAX. When the current DCW specifies command chaining and no unusual conditions have been detected during the operation, the completion of the current DCW causes the next DCW to become the current DCW and be executed by the device. If a TCAX is specified and the offset of the next DCW is past the end of the TCA, chaining continues with the first DCW of the TCAX whose TCAX offset is determined by subtracting the TCA length from the calculated offset. Thus, command chaining proceeds in ascending order of TCA offsets, and then TCAX offsets when a TCAX is specified. If a condition such as attention, unit check, unit exception, or incorrect length has occurred (unless a SLI field 214 in the DCW is activated), the sequence of operations is concluded, and the status associated with the current operation causes an interruption condition to be generated. The new DCW in this case is not executed.
Data that is requested to be transferred via the I/O operation are sent between the channel 128 and control unit 118 via one or more transport-data IUs during processing of the DCWs 202 in a TCCB 170. A read operation performs only a read data transfer, a write operation performs only a write data transfer and a bi-directional operation may perform both a read and write data transfer.
Referring to FIG. 16, for a write or bidirectional operation, the channel 128 sends one or more transport-data IUs 310 to the control unit 118 to transfer write data 312 for the operation. For a read or bidirectional operation, the control unit 118 sends at least one transport-data IU 314 to the channel 128 to transfer read data 316 specified for the operation. Pad bytes 318 may be included in the last word of a data area for which CRC is to be calculated and are used to pad the data area to the next word boundary when the data area to be covered is not an integral number of data words. This applies to data areas to be covered by COB, intermediate and final CRC. The value used for a pad byte is model dependent.
A final CRC field 320 is included in a transport-data IU 310, 314 when the transport-data IU is the last transport-data IU sent by the channel 128 or control unit 118 for a TCW I/O operation. In one embodiment, the final-CRC field 320 includes a word-aligned 32-bit redundancy-check code. For read or write operations, the DL field in the TCCB 170 specifies the amount of data to be transferred during an operation, which may includes all required pad and CRC bytes. For bidirectional operations, the DL field in the TCCB 170 specifies the amount of data to be transferred for the write data transfer portion of the operation and the BRDL field specifies the amount of data to be transferred for the read data transfer portion of the operation. These amounts may include all required pad and CRC bytes.
During a write data transfer, data is transferred in one or more transport-data IUs 310 to the control unit 118 on the transport exchange associated with the TCW I/O operation. In one embodiment, except for the first write transport-data IU 310 of an operation, the channel 128 requires a transfer-ready IU from the control unit 118 prior to sending each transport-data IU 310. The control unit 118 may request additional data by sending additional transfer-ready IUs until it has requested all the data specified by the DL field 186 of the TCCB 170 for the write operation. For a write operation, the next IU sent by the control unit 118 following completion of the data transfer specified by the DL field in the TCCB is a transport-response IU. For a bidirectional operation, the next IU sent by the control unit 118 following completion of the data transfer specified by the DL field in the TCCB may be a transport data IU or a transport-response IU.
During a read data transfer, data is transferred in one or more transport-data IUs 314 to the channel 128 on the transport exchange associated with the TCW I/O operation. The amount of data sent in each transport-data IU is determined by the control unit 118 and may be set to any value as long that the total amount of data transferred in all transport-data IUs 314 for the operation does not exceed the value in the DL field 186 or, for bidirectional operations, the value in the BRDL field 188. For read operations, if the quantity of data sent by the control unit is less than the DL field in the TCCB, the DL residual count in the transport-response IU shall be the difference between the quantity of data sent by the CU and the DL field in the TCCB. The channel recognizes a device-level protocol error if the residual count provided by the control unit in the transport-response IU does not match the difference between the DL and the number of bytes actually received by the channel. For bidirectional operations, if the quantity of data sent by the control unit is less than the BRDL field in the TCCB, the BRDL-residual count in the transport-response IU shall be the difference between the quantity of data sent by the CU and the BRDL field in the TCCB. The channel recognizes a device-level protocol error if the residual count provided by the control unit in the transport-response IU does not match the difference between the BRDL and the number of bytes actually received by the channel.
As shown in FIG. 16, one or more intermediate CRC words 320 may be present in a transport-data IU 310 sent by the channel 128. The intermediate CRC 320 words provide CRC checking of data areas prior to transmission of the entire data area specified by the TCA 180. A COB CRC word 322 may be present in a transport-data IU 310 when a COB 222 is being transferred in the transport-data IU.
Referring again to FIG. 15, in stage 305, the TCW I/O operation is ended by either the channel 128 or the control unit 118. The channel 128 may initiate the ending of a TCW I/O operation as the result of an abnormal condition or a program-initiated termination. The control unit 128 may initiate the ending of the operation as the result of the completion of the execution of the operation or as the result of an abnormal condition detected during the execution of the command. The control unit 128 may initiate the end of a TCW I/O operation by sending a transport-response IU or, in the case of certain errors, by aborting the exchange. In one embodiment, the control unit 118 may initiate the ending of a TCW I/O operation under any of the following circumstances: all of the DCWs 202 in the TCA 180 (and a TCAX if specified) having been executed; an incorrect-length condition having been detected for a DCW when the DCW-incorrect length facility is supported and the SLI flag 214 is set to zero; a unit check condition has been detected; an abnormal condition such as a transport error; or another error was recognized that required the exchange to be aborted.
Referring to FIG. 17, in one embodiment, when an I/O operation or sequence of I/O operations initiated by the execution of START SUBCHANNEL is ended, the channel subsystem and the device generate status conditions. The generation of these conditions can be brought to the attention of the program by means of an I/O interruption or by means of the execution of a TEST PENDING INTERRUPTION instruction. The status conditions, as well as an address and a count indicating the extent of the operation sequence, are presented to the program in the form of a subchannel-status word (SCSW) 400. The SCSW 400 is stored in an interruption-response block (IRB) 402 during the execution of a TEST SUBCHANNEL instruction. When a transport-mode IRB is stored, additional information describing the status of the operation is also stored in the transport-status block.
Normally an I/O operation is being performed until the device signals primary interruption status. Primary interruption status can be signaled during initiation of an I/O operation, or later. An I/O operation can be terminated by the channel subsystem performing a clear or halt function when it detects an equipment malfunction, a program check, a chaining check, a protection check, or an incorrect-length condition, or by performing a clear, halt, or channel-path-reset function as a result of the execution of CLEAR SUBCHANNEL, HALT SUBCHANNEL, or RESET CHANNEL PATH instructions, respectively. I/O interruptions provide a means for the CPU to change its state in response to conditions that occur at I/O devices or subchannels. These conditions can be caused by the program, by the channel subsystem, or by an external event at the device.
The conditions causing requests for I/O interruptions to be initiated are called I/O-interruption conditions. When an interruption condition is recognized by the channel subsystem, it is indicated at the appropriate subchannel. The subchannel is then said to be status pending. The subchannel becoming status pending causes the channel subsystem to generate an I/O interruption request. An I/O-interruption request remains pending until it is accepted by a CPU in the configuration, is withdrawn by the channel subsystem, or is cleared by means of the execution of a TEST PENDING INTERRUPTION, TEST SUBCHANNEL, or CLEAR SUBCHANNEL instruction, or by means of subsystem reset. When a CPU accepts an interruption request and stores the associated interruption code, the interruption request is cleared. When the pending interruption is cleared by the execution of TEST PENDING INTERRUPTION, the subchannel remains status pending until the associated interruption condition is cleared when TEST SUBCHANNEL or CLEAR SUBCHANNEL is executed or when the subchannel is reset.
An I/O-interruption condition is normally cleared by means of the execution of a TEST SUBCHANNEL instruction. If TEST SUBCHANNEL is executed, designating a subchannel that has an I/O-interruption request pending, both the interruption request and the interruption condition at the subchannel are cleared. The interruption request and the interruption condition can also be cleared by CLEAR SUBCHANNEL. A device-end status condition generated by the I/O device and presented following the conclusion of the last I/O operation of a start function is reset at the subchannel by the channel subsystem without generating an I/O-interruption condition or I/O-interruption request if the subchannel is currently start pending and if the status contains device end either alone or accompanied by control unit end. If any other status bits accompany the device-end status bit, then the channel subsystem generates an I/O-interruption request with deferred condition code 1 indicated. When an I/O operation is terminated because of an unusual condition detected by the channel subsystem during the command-initiation sequence, status describing the interruption condition is placed at the subchannel, causing it to become status pending. If the unusual condition is detected by the device, the device-status field of the associated SCSW identifies the condition. When command chaining takes place, the generation of status by the device does not cause an interruption, and the status is not made available to the program.
When the channel subsystem detects any of the following interruption conditions, it initiates a request for an I/O interruption without necessarily communicating with, or having received the status byte from, the device:
1) A programming error associated with the contents of the ORB passed to the subchannel by the previous execution of START SUBCHANNEL;
2) A suspend flag set to one in the first CCW fetched that initiates a CCW channel program execution for either START SUBCHANNEL or RESUME SUBCHANNEL, and suppress suspended interruption not specified in the command-mode ORB; or
3) A programming error associated with the first CCW, TCW, TIDAW, TCCB fetch, data fetch, IDAW, or MIDAW.
These interruption conditions from the subchannel, except for the suspended condition, can be accompanied by other subchannel-status indications, but the device-status indications are all stored as zeros.
The channel subsystem issues the clear signal to the device when status containing unit check is presented to a subchannel that is disabled or when the device is not associated with any subchannel. However, if the presented status does not contain unit check, the status is accepted by the channel subsystem and discarded without causing the subchannel to become status pending.
The subchannel-status word (SCSW) 400 provides to the program indications describing the status of a subchannel and its associated device. When a transport mode IRB 402 is stored, additional information describing the status of the operation and the associated device may also be stored in the transport-status block associated with the operation. If performance of a halt, resume, or start function has occurred, the SCSW may describe the conditions under which the operation was concluded.
In one embodiment, the SCSW is stored when TEST SUBCHANNEL is executed and the designated subchannel is operational. The SCSW is placed in words 0-2 of the IRB that is designated as the TEST SUBCHANNEL operand. When STORE SUBCHANNEL is executed, the SCSW is stored in words 7-9 of a subchannel-information block.
The SCSW includes various fields, such as a Deferred Condition Code (CC). The deferred condition code, if not zero, is used to indicate whether conditions have been encountered that preclude the subchannel becoming subchanneland-device active while the subchannel is either start pending or suspended. In one embodiment, when deferred condition code 1 is set, the secondary-status bit is one, and the primary-status bit is zero, the status present may be related to a command-mode channel program specified by the START SUBCHANNEL instruction (or implied by the RESUME SUBCHANNEL instruction) that preceded the most recently executed START SUBCHANNEL and that most recently executed START SUBCHANNEL specified a transport-mode channel program. For such a case, status modifier may also be one in the device-status field.
A Subchannel-Status Field is included in the SCSW 400 and is used to indicate subchannel-status conditions by the channel subsystem. For example, the subchannel-status field is contained in bit positions 8-15 of word 2 of the SCSW. Subchannel-status conditions are detected and indicated in the SCSW by the channel subsystem. Except for the conditions caused by equipment malfunctioning, they can occur only while the channel subsystem is involved with the performance of a halt or start function. The subchannel-status field is meaningful whenever the subchannel is status pending with any combination of primary, secondary, intermediate, or alert status. When the subchannel is status pending with deferred condition code 3 indicated, the contents of the subchannel-status field are not meaningful.
An exemplary subchannel status condition is an Incorrect length condition, which occurs when the number of bytes contained in the storage areas assigned for the I/O operation is not equal to the number of bytes requested or offered by the I/O device. When the FCX-incorrect-length-indication facility is not installed and an incorrect-length condition is detected, the processing of the transport-mode channel program is terminated with program-check status. When the FCX-incorrect-length-indication facility is installed, the device supports incorrect-length indication, incorrect-length-indication is not being suppressed, and an incorrect-length condition is detected, incorrect length is indicated for one of the following reasons:
1) Long Block on Input: During a read or sense operation, the device attempted to transfer one or more bytes to main storage after the assigned main storage areas were filled, or the device indicated that more data could have been transferred if the count had been larger. The extra bytes have not been placed in main storage. The count in the TSB header (TSH) is zero.
2) Long Block on Output: During a write operation, the device requested one or more bytes from the channel subsystem after the assigned main-storage areas were exhausted, or the device indicated that more data could have been transferred if the count had been larger. The count in the TSH is zero.
3) Short Block on Input: The number of bytes transferred during a read or sense operation is insufficient to fill the main-storage areas assigned to the operation. The count in the TSH is not zero.
4) Short Block on Output: The device terminated a write before all of the information contained in the assigned main-storage areas was transferred to the device. The count in the TSH is not zero.
The incorrect-length indication is suppressed when the current DCW has the SLI flag set to one. The incorrect-length indication is not meaningful when the count field of the TSH is not meaningful. Presence of the incorrect-length condition suppresses command chaining unless the SLI flag in the DCW is one.
The subchannel-extended-status field is included in the SCSW 400 (e.g., in bit positions 24-31 of word 2 of the SCSW). This field may contain information used to further qualify the reason for any the following conditions, when indicated in the subchannel-status: interface-control check, channel-control check, channel-data check, program check, and protection check. If none of these bits are active in the subchannel-status byte, the fields of the subchannel-extended-status contain no meaningful information. When more than one condition is indicated, the interface-control check takes priority over the other conditions.
The subchannel-extended-status field may also include an Interrogate Failed (F) (e.g., at bit 24) operation bit. When set to one, the F bit indicates that an interrogate operation failed because of a program check, channel-control check, or interface-control check.
The subchannel-extended-status field may also include a Subchannel-Extended-Status Qualifier (SESQ) (e.g., bits 25-31). When the subchannel-status field indicates program check, interface-control check, channel-subsystem retry failed, protection check, data check, or channel-control check, this field may contain additional information. Exemplary SESQ values and their associated meanings are shown in FIGS. 18A-18D.
FIGS. 19-20 illustrate an exemplary transport response IU 330 that may be sent by a control unit 118. The Transport Response IU 330 provides status for a TCW I/O operation, which may include a normal ending status or, when an abnormal condition has been detected, termination status that indicates the cause for abnormal termination of the operation. The transport response IU 330 may also include an extended status field that provides further status for the operation. A transport-response IU may or may not close a transport exchange. In one embodiment, whether or not the exchange has been closed by a transport-response IU is indicated in the FC-FS-3 header. If the transport exchange has not been closed by the transport-response IU, the channel may send a transport-confirm IU that closes the exchange after receiving the transport-response IU.
In one embodiment, the transport-response IU 330 includes a SB-4 header 332 followed by a status field 334, a status LRC 344, and an optional extended-status field 346 containing from, e.g., 32 to 64 bytes. When extended status is provided, a 4-byte extended-status LRC field 340 may be provided as the last word of the transport-response IU 330. Pad bytes are added to the extended status to round to the next word boundary if the number of extended-status bytes is not on a word boundary. The SB-4 header 332 has a format similar to that of the transport command IU and is set equal to the SB-4 header in the transport command IU for this exchange.
Referring to FIG. 20, an embodiment of the status area 334 is, e.g., 20 bytes and contains information about the TCW I/O operation. A “status flags 1” field 336 includes one or more exception codes that are set by the control unit 118 to report an abnormal condition detected during a TCW I/O operation. Exemplary codes include:
0—Device-level exception due to an address-exception condition;
2—Link-level reject due to a logical-path-not-established condition;
3—Resetting event notification—a resetting event has occurred on the logical path and the device associated with the transport-command IU. When this code is set in the transport-response IU, the control unit requests status confirmation for the status. If status confirmation is received, the resetting event condition is reset at the device for the logical path; otherwise, the resetting-event condition remains pending;
4—Device-detected program check/IFCC—the control unit has detected a condition that may result in a program check or IFCC to be reported. Errors that fall into this category include errors that indicate the transport-command IU arrived in a corrupted state (e.g., TCCB integrity error), invalid CRC detected for write data, and receipt of a second I/O operation for a logical path and device address that is not an interrogate operation.
5—Device-detected program check—the control unit has detected an error in the content of the TCH
In one embodiment, the status flags 1 field 336 includes an Incorrect Length (IL) flag 338. When the DCW-incorrect-length facility is supported by the channel and control unit, bit 0 is the IL flag and, when set to one, shall indicate that the TCW I/O operation was terminated due to an incorrect-length condition for the DCW indicated by the DCW offset. An incorrect length is detected by the control unit 118 if the DCW data count does not match the amount of data required by the device for a write DCW or if the DCW data count does not match the amount of data available at the device for a read DCW.
In one embodiment, if the DCW 202 includes an SLI flag 214, the IL flag 338 is set to one only when the SLI flag 214 is zero and when the device status includes channel-end status without unit-check status. When the IL flag 338 is set to one in a transport-response IU, the DCW offset identifies the DCW containing the incorrect-length condition and the DCW residual count indicates the amount of data transfer, if any, that was transferred for the incorrect-length DCW. Data transfer, if any, for DCWs that preceded the incorrect-length DCW in the TCA shall have completed and all CRC checking on transferred data shall have been performed as described below.
When the DCW containing the incorrect-length condition is a read DCW, the last transport-data IU sent to the channel INCLUDES CRC for all read data transferred to the channel during the TCW I/O operation. If write DCWs preceded the incorrect-length read DCW in the TCA, the data for those write DCWs shall have been received by the control unit and CRC checking shall have been performed on the data. Data for write DCWs in the TCA that follow the incorrect-length read DCW shall be transferred to the control unit as necessary to obtain the CRC for the write data and to perform the CRC checking.
The incorrect-length condition is not recognized by an interrogate command, a transfer-CRC-offset command or a TTE command regardless of whether the incorrect length facility is supported by the channel and the control unit.
The transport response IU 330 may also include a Data Length Residual Count (DLRC) field 340. For write and bidirectional operations, the DL-residual count is a 32-bit, unsigned binary integer that specifies the difference between the DL field in the transport-command IU and the number of bytes actually received from the channel. For read operations, the DL-residual count is a 32-bit, unsigned binary integer that specifies the difference between the DL field in the transport-command IU and the number of bytes actually sent to the channel.
For bidirectional operations, a BRDL residual count field 342 may also be included in the transport-response IU 330. For bidirectional operations, the BRDL-residual count is a 32-bit, unsigned binary integer that specifies the difference between the BRDL field in the transport-command IU and the number of bytes actually sent to the channel.
A Status Flags3 field 344 can be used by the control unit 118 to provide additional information about the associated transport-mode operation. This field may include an Extended Status Sent (ESS) bit to indicate that extended status, including possible sense data, has been sent in the transport-response IU. The extended status includes extended status (ES) Flags that include fields such as an ES Type Code field. Type codes include I/O status (the extended-status area contains valid ending status for the transport-mode I/O operation), I/O Exception (the extended-status area contains information regarding termination of the transport-mode I/O operation due to an exception condition), and Interrogate status (the extended-status area contains status for an interrogate operation).
When the ES-type code in the ES Flags is an I/O exception, the ES includes reason codes (RC). Exemplary reason codes include:
1—TCCB integrity error: the control unit has determined that the TCCB arrived in a corrupted state (provided when exception code 4 is indicated in the status flags 1 field);
2—Invalid CRC detected: invalid CRC was detected on received data (provided when exception code 4 is indicated in the status flags 1 field);
3—Incorrect TCCB length specification (provided when exception code 5 is indicated in the status flags 1 field);
4—TCAH specification error (provided when exception code 5 is indicated in the status flags 1 field);
5—DCW specification error: there is an error with the DCW designated by the DCW-offset field in the extended status (provided when exception code 5 is indicated in the status flags 1 field);
6—Transfer-direction specification error: the command specified by the DCW designated by the DCW-offset field in the extended status specifies a direction of data transfer that disagrees with the transfer direction specified in the TCH or both the R and W bits are set to one in the TCH and bidirectional data transfer is not supported by the control unit (provided when exception code 5 is indicated in the status flags 1 field);
7—Transport-count specification error (provided when exception code 5 is indicated in the status flags 1 field);
8—Two I/O operations active: While an I/O operation is active at the device a second non-interrogate TCCB has been transported to the device for execution. The RCQ field has no meaning. This reason code is provided when exception code 4 is indicated in the status flags 1 field; and
9—One or more entries in the CRC-offset block indicate that an intermediate CRC is not at a location that is appropriate for the device and/or command being executed provided when exception code 4 is indicated in the status flags 1 field.
The Extended Status may also provide a Reason Code Qualifier (RCQ) that provides additional information about the reason(s) for the I/O exception. Different reason code qualifier types may be used for different types of errors, such as TCCB integrity errors, Output Data CRC Errors, Incorrect TCCB Length Specifications, TCAH Specification Errors and DCW Specification Errors. Exemplary RCQs for a TCCB integrity error include:
0—No additional information;
1—Data Count Error—the amount of data transferred for the transport-command IU is not equivalent to the amount of data specified by the L1 field plus 8 in the TCH for control units that do not support bidirectional operations or is not equivalent to the amount specified by the L1 field plus either 8 or 9 for control units that do support bidirectional operations; and
2 LRC error—the LRC on the transport-command IU is invalid.
Exemplary RCQs for a DCW specification error include:
1—Reserved-field specification error: A reserved field in the DCW that is required to contain zeros contains a non-zero value;
2—Flags-field command-chaining specification error: The command-chaining bit is one and the offset of the next DCW is such that all or part of the next DCW extends past the end of the TCA, or the command-chaining bit is zero and more than 3 unused bytes remain in the TCA;
3—Control-data count specification error: The CD count specifies control data past the end of the TCA;
4—TCOB DCW location error: The first TCOB DCW is not the first DCW in the TCA;
5—TCOB DCW duplication error: More than one TCOB DCW is specified in the TCA;
6—TCOB DCW multiple-count specification error: Both the CD count and the DCW data count are either zero or non-zero;
7—TCOB DCW direction error: A TCOB DCW is specified in the TCA and the W bit in the TCH is zero;
8—TCOB DCW chaining error: The chain-command bit in the TCOB DCW is zero, i.e., the TCOB DCW is the only DCW in the TCA;
9—TCOB count-specification error: A TCOB DCW has a nonzero CD count or a data count that is not a multiple of 4;
10—TTE DCW location error: A TCOB DCW was not specified and a TTE DCW was encountered that was not the first DCW in the TCA or a TCOB DCW was specified and the first TTE DCW encountered was not the second DCW in the TCA;
11—TTE DCW duplication error: More than one TTE DCW was encountered in the TCA;
12—TTE DCW CD-count specification error: The control-data count in the TTE DCW specifies a value that is not zero;
13—TTE DCW data-count specification error: The data count in the TTE DCW specifies a value that is less than 8 or a value that is not a multiple of 4;
14—TTE DCW direction error: A TTE DCW is specified and the W bit in the TCH is zero;
15—TTE DCW chaining error: The chain-command bit in the TTE DCW is zero; and
16—TCAX specification error: A TTE DCW is specified and either of the following is true:
The length of the TCA is 58 words or less, or
The length of the TCA is 59 words, the last DCW in the TCA specifies control data and the length of the control data extends beyond 59 words, or
The length of the TCA is the maximum length of 60 words and the last word in the TCA contains the first word of a DCW.
Exemplary RCQs for a Transfer-Direction Specification Error include:
1—Read-direction specification error: The DCW specifies an input operation and the R bit in the TCH is zero;
2—Write-direction specification error: The DCW specifies an output operation and the W bit in the TCH is zero. Note—A DCW specification is recognized when a TCOB or TTE DCW is specified and the W bit in the TCH is zero;
3—Read-Write conflict: Both the R and W bits in the TCH are one and the control unit does not support bidirectional operations or the control unit supports bidirectional operations but the transport-command IU did not contain the BRDL field, or both the R and W bits are not one and the transport-command IU contains the BRDL field;
Exemplary RCQs for a Transport-Count Specification Error include:
1—Read-count specification error: for read operations, the DL field in the TCCB specifies a value that is not equivalent to the total count of data bytes specified by the DCWs in the TCA plus pad bytes and CRC; for bidirectional operations, the BRDL field in the TCCB specifies a value that is not equivalent to the total count of data bytes specified by the read DCWs in the TCA plus pad bytes and CRC; and
2—Write-count specification error: The DL field in the TCCB specifies a value that is not equivalent to the total count of data bytes specified by the write DCWs in the TCA plus intermediate pad bytes, intermediate CRC, final pad bytes and final CRC bytes, and if a COB is included in the first transport-data IU of the write data transfer, the count includes the COB, any COB pad bytes and the COB CRC bytes. If a TTE DCW is present in the TCA, the count also includes the TCAX and TCAX CRC bytes.
A program check occurs when programming errors are detected by the channel subsystem. For a transport mode operation, programming errors may also be detected by the I/O device 116 and are reported as program checks. A program check condition can be due to any of the following reasons:
Invalid TCW Specification: When any of the following conditions is detected, an invalid TCW specification is recognized:
1. A reserved field that is checked for zeros in the TCW does not contain zeros.
2. A non-zero value is specified in the TCW format field.
3. The read and write bits in the TCW are both one, bit 10 of the TCW flags field is zero, and either the FCX-bidirectional-data-transfer facility is not installed or the specified device does not support bi-directional data transfers.
4. The bit 10 of the TCW flags field is zero and the TCCB-length field in a TCW specifies a length that is less than 12 or greater than 244.
5. Bit 10 of the TCW flags field is one and the write operations (W) bit of the TCW is zero, the read operations (R) bit of the TCW is zero, or both are zero.
6. Bit 10 of the TCW flags field is one and the designated subchannel is not associated with a control unit that has been configured to transport fibre-channel-services requests.
When a TTE DCW is used, a device-detected program check is recognized when any of the following conditions exist:
1. When a TCOB DCW is not specified, the TTE DCW is not the first DCW in the TCA. When a TCOB DCW is specified, the TTE DCW is not the second DCW in the TCA.
2. The TTE DCW is specified and a write operation is not specified (that is, the W-bit in the TCW is zero).
3. The chain-command flag in the TTE DCW is zero.
4. More than one TTE DCW is specified
5. The control-data-count field in the TTE DCW does not contain zero.
6. The count field contains less than 8 or a value that is not a multiple of 4.
7. Any of the following are true for the TCA:
The TCA does not contain at least one DCW that is not a transport-command DCW.
The TCA contains one or more DCWs that are not transport-command DCWs and the chain-command flag in the last DCW of the TCA is zero.
When a TTE DCW is used and additional TCMI and/or output data follows the TCAX, the following should be true; otherwise, a device-detected program check may be recognized:
The output-TIDA flag (flags bit 7) in the TCW must be one; or
When TIDAWs are used for the transfer of a TCAX and for the transfer of data, the insert-CBC control must be set to one in the last or only TIDAW that is used to transfer the TCAX. When TIDAWs are used for the transfer of only the TCAX, it is not necessary to set the insert-CBC control in the last or only TIDAW.
During the processing of a TCA, a TCCB content error may be recognized when any of the following conditions are detected:
1. The first TCOB DCW encountered is not the first DCW in the TCA;
2. a second TCOB DCW is encountered in the TCA;
3. a TCOB DCW is encountered in the TCA when the W bit in the TCAH is zero;
4. a TCOB DCW does not have the chaining flag set;
5. a TCOB DCW is encountered in which both the CD count and data count are zero;
6. a TCOB DCW is encountered in which both the CD count and data count are non-zero;
7. a TCOB DCW is encountered in which the CD count is zero and the data count is not a multiple of 4;
8. a TCOB DCW is encountered in which the data count is zero and the CD count is not a multiple of 4;
9. A TCOB DCW is not specified and the TTE DCW is not the first DCW in the TCA or a TCOB is specified and the TTE DCW is not the second DCW in the TCA;
10. A TTE DCW is encountered in the TCA when the W bit in the TCAH is zero;
11. A TTE DCW does not have the chaining flag set;
12. A second TTE DCW is encountered in the TCA;
13. A TTE DCW is encountered in which the CD count is non-zero;
14. A TTE DCW is encountered in which the data count is zero or is not a multiple of 4;
15. A TTE DCW is specified and any of the following is true: the length of the TCA is 58 words or less; the length of the TCA is 59 words, the last DCW in the TCA specifies control data and the length of the control data extends beyond 59 words; or the length of the TCA is the maximum length of 60 words and the last word in the TCA contains the first word of a DCW;
16. A DCW contains a command that requires control data and the CD count field is zero or contains a value that specifies data past the end of the TCA;
17. A DCW contains a CD count field that is non-zero and the command does not allow control data to be provided;
18. During a write operation, the device encountered a command in the TCA that attempted to perform a read data transfer;
19. During a read operation, the device encountered a command in the TCA that attempted to perform a write data transfer;
20. The CC bit is zero in a DCW and more than 3 unused bytes remain in the TCA;
21. The CC bit is one in a DCW and next DCW location is determined to be less than 8 bytes from the end of the TCA indicating and a TCAX has not been provided, or a TCAX has been provided and the next DCW location is determined to be less than 8 bytes from the end of the TCAX;
22. For a read or bidirectional operation, when a read DCW in the TCA becomes current, the sum of the data counts for all previous read DCWs and the current DCW plus all pad and CRC bytes exceeds the DL field in the TCCB or, for bidirectional operations, exceeds the BRDL field in the TCCB;
23. For a read or bidirectional operation, when the last DCW in the TCA becomes current, the sum of the data counts for all read DCWs plus all pad and CRC bytes is not equal to the DL field in the TCCB or, for bidirectional operations, is not equal to the BRDL field in the TCCB;
24. For a write or bidirectional operation, when a DCW in the TCA becomes current, the sum of the data counts for all write DCWs plus all pad and CRC bytes (including all intermediate pad and CRC bytes), and if a COB is included in the transport-data IU, the COB, COB pad and COB CRC bytes, and if a TCAX is present, the TCAX, TCAX pad, and TCAX CRC bytes, exceeds the DL field in the TCCB; or
25. For a write operation or bidirectional operation, when the last DCW in the TCA becomes current, the sum of the data counts for all write DCWs plus all pad and CRC bytes (including all intermediate pad and CRC bytes), and if a COB is included in the transport-data IU, the COB, COB pad and COB CRC bytes, and if a TCAX is present, the TCAX, TCAX pad, and TCAX CRC bytes, is not equal to the DL field in the TCCB.
In one embodiment, prior to performing command mode or transport mode operations, links between the channel subsystem 114 and control units 118 and/or devices 116 are established. Each channel 128 in the I/O system that has a physical connection with one or more control units can be referred to as a “N_Port” that has a unique identifier (a “N_Port_ID”). Likewise, each control unit 118 can also be referred to an a N_Port having an associated N_Port_ID. Both a channel 128 and a control unit 118 may include multiple channel images or control unit images, respectively. Each N_Port includes an address identifier that is assigned during initialization and the performance of a login procedure. Explicit N_Port login may be performed by means of the N_Port login (PLOGI) extended link service during the initialization process. When an N_Port has performed N_Port login with another N_Port, that N_Port is said to be logged in with the other N_Port.
In one embodiment, link initialization between the channel subsystem and control units is performed using the process login (PRLI) extended link service (ELS) protocol. General aspects of the PRLI ELS, including the format of the PRLI ELS request and response, are given in FC-LS-2 with specific settings for FC-SB-4 defined in the sections below.
During a PRLI procedure, a channel 128 that supports PRLI sends a request to each control unit 118 in its configuration that also supports the process login ELS to determine whether the control unit 118 supports transport-mode operations. In one embodiment, the PRLI request is sent during channel initialization prior to establishing logical paths and may also be sent as the result of a process logout (PRLO). The PRLI ELS is used to exchange process login service parameters between a channel 128 and control unit 118. Parameters may be exchanged between a channel and control unit via a PRLI request and a PRLI response.
The PRLI request includes a service parameter page, which may include a Type Code field that identifies the FC-4 protocol (e.g., is set to hex‘1B’ to indicate the SB-4 protocol). A FC-SB-4 Flags (e.g., Byte 3 of word 3 of the PRLI request page) includes one or more flags described below:
0—Transport Mode Supported. When bit 0 is set to zero, the channel does not support transport-mode operations. When bit 0 is set to one, the channel supports transport-mode operations.
1—Reserved.
2—DCW Incorrect Length (IL) Facility Supported. For example, when an IL flag is active (e.g., when bit 2 is set to one), the DCW IL facility is supported by the channel 128. When bit 2 is set to zero, the DCW IL facility is not supported by the channel 128. The DCW IL facility includes support for the suppress-length-indicator (SLI) flag 214 and the incorrect-length flag 338. When the transport mode-supported bit (bit 0) is equal to zero, bit 2 shall be set to zero.
5—Bidirectional Data Transfer Supported. When a bi-directional transfer indication is active (e.g., bit 5 is set to one) bidirectional data transfer is supported by the channel 128. When bit 5 is set to zero, bidirectional data transfer is not supported by the channel. This bit is only meaningful when the transport mode-supported bit is equal to one.
7—First Transfer Ready Disabled Supported. When bit 7 is set to one, first-transfer-ready-disabled operation is supported by the channel. When bit 7 is set to zero, first-transfer-ready disabled operation is not supported by the channel. When the transport-mode-supported bit (bit 0) is equal to zero, bit 7 shall be set to zero.
In one embodiment, the PRLI response includes a PRLI Accept Service Parameter Page, which may include a Type Code field that identifies the FC-4 protocol (e.g., is set to hex‘1B’ to indicate the SB-4 protocol), and a FC-SB-4 Flags field (e.g., Byte 3 of word 3) that includes one or more flags defined described below:
0—Transport Mode Supported. When bit 0 is set to zero, the control unit 118 does not support transport-mode operations. When bit 0 is set to one, the control unit 118 supports transport-mode operations.
2—DCW Incorrect Length (IL) Facility Supported. When bit 2 is set to one, the DCW-incorrect-length (IL) facility is supported by the control unit 118. When bit 2 is set to zero, the DCW IL facility is not supported by the control unit 118. The DCW-incorrect-length facility includes support for the SLI flag 214 and the incorrect-length flag 338. When the transport-mode-supported bit (bit 0) is equal to zero, bit 2 shall be set to zero.
5—Bidirectional Data Transfer Supported. When a bi-directional data transfer indication is active (e.g., bit 5 is set to one), bidirectional data transfer is supported by the control unit 118. When bit 5 is set to zero, bidirectional data transfer is not supported by the control unit 118. This bit is only meaningful when the transport-mode-supported bit is equal to one.
7—First Transfer Ready Disabled Supported. When bit 7 is set to one, first-transfer-ready-disabled is supported by the control unit. When bit 7 is set to zero, first-transfer-ready-disabled operation is not supported by the control unit. When the transport-mode-supported bit (bit 0) is equal to zero, bit 7 shall be set to zero.
Technical effects and benefits of exemplary embodiments include the ability to transfer transport support data as well as additional commands to the control unit, in addition to I/O commands and device support data located in a TCCB. Technical effects also include the ability to continue processing of DCWs despite detection of an incorrect length condition, which allows a control unit to continue to process I/O commands without the need to terminate an I/O operation. Other technical effects include the ability to transport both input and output data between a channel and a control unit during a single I/O operation.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wire line, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
US3693161 9 juil. 1970 19 sept. 1972 Burroughs Corp Apparatus for interrogating the availability of a communication path to a peripheral device
US3943283 17 juin 1974 9 mars 1976 International Business Machines Corporation Bidirectional single wire data transmission and wrap control
US4004277 5 mai 1975 18 janv. 1977 Gavril Bruce D Switching system for non-symmetrical sharing of computer peripheral equipment
US4080649 16 déc. 1976 21 mars 1978 Honeywell Information Systems Inc. Balancing the utilization of I/O system processors
US4207609 8 mai 1978 10 juin 1980 International Business Machines Corporation Method and means for path independent device reservation and reconnection in a multi-CPU and shared device access system
US4374415 14 juil. 1980 15 févr. 1983 International Business Machines Corp. Host control of suspension and resumption of channel program execution
US4380046 21 mai 1979 12 avr. 1983 Nasa Massively parallel processor computer
US4414644 3 avr. 1981 8 nov. 1983 International Business Machines Corporation Method and apparatus for discarding data from a buffer after reading such data
US4455605 23 juil. 1981 19 juin 1984 International Business Machines Corporation Method for establishing variable path group associations and affiliations between "non-static" MP systems and shared devices
US4497022 19 oct. 1982 29 janv. 1985 International Business Machines Corporation Method and apparatus for measurements of channel operation
US4564903 5 oct. 1983 14 janv. 1986 International Business Machines Corporation Partitioned multiprocessor programming system
US4760518 28 févr. 1986 26 juil. 1988 Scientific Computer Systems Corporation Bi-directional databus system for supporting superposition of vector and scalar operations in a computer
US4779188 19 oct. 1987 18 oct. 1988 International Business Machines Corporation Selective guest system purge control
US4837677 14 juin 1985 6 juin 1989 International Business Machines Corporation Multiple port service expansion adapter for a communications controller
US4843541 29 juil. 1987 27 juin 1989 International Business Machines Corporation Logical resource partitioning of a data processing system
US4866609 21 sept. 1988 12 sept. 1989 International Business Machines Corporation Byte count handling in serial channel extender with buffering for data pre-fetch
US4870566 27 août 1984 26 sept. 1989 International Business Machines Corp. Scannerless message concentrator and communications multiplexer
US5016160 15 déc. 1988 14 mai 1991 International Business Machines Corporation Computer system having efficient data transfer operations
US5031091 8 nov. 1989 9 juil. 1991 Pfu Limited Channel control system having device control block and corresponding device control word with channel command part and I/O command part
US5040108 23 avr. 1990 13 août 1991 Nec Corporation Information processing system having microprogram-controlled type arithmetic processing unit with clock synchronization instruction
US5170472 28 mars 1991 8 déc. 1992 International Business Machines Corp. Dynamically changing a system i/o configuration definition
US5185736 12 mai 1989 9 févr. 1993 Alcatel Na Network Systems Corp. Synchronous optical transmission system
US5237325 19 juil. 1990 17 août 1993 Klein Hans Christoph Process and system for gathering and evaluating measured data
US5263240 16 avr. 1992 23 nov. 1993 Nippon Cmk Corp. Method of manufacturing printed wiring boards for motors
US5297262 21 oct. 1992 22 mars 1994 International Business Machines Corporation Methods and apparatus for dynamically managing input/output (I/O) connectivity
US5301323 30 oct. 1992 5 avr. 1994 International Business Machines Corp. Data processing system including dynamic channel path management
US5317739 30 mars 1992 31 mai 1994 International Business Machines Corp. Method and apparatus for coupling data processing systems
US5325492 11 juin 1993 28 juin 1994 International Business Machines Corporation System for asynchronously delivering self-describing control elements with a pipe interface having distributed, shared memory
US5386512 9 déc. 1993 31 janv. 1995 International Business Machines Corporation System for deriving and testing mutual capability set after receiving updated capability from other processors and before requesting service information
US5388219 2 mars 1992 7 févr. 1995 International Business Machines Corporation Efficient channel and control unit for host computer
US5410727 22 nov. 1993 25 avr. 1995 International Business Machines Corporation Input/output system for a massively parallel, single instruction, multiple data (SIMD) computer providing for the simultaneous transfer of data between a host computer input/output system and all SIMD memory devices
US5414851 15 juin 1992 9 mai 1995 International Business Machines Corporation Method and means for sharing I/O resources by a plurality of operating systems
US5434980 23 déc. 1992 18 juil. 1995 International Business Machines Corporation Apparatus for communication between a device control unit having a parallel bus and a serial channel having a serial link
US5440729 2 déc. 1994 8 août 1995 Nec Corporation Method for handling error information between channel unit and central computer
US5452455 15 juin 1992 19 sept. 1995 International Business Machines Corporation Asynchronous command support for shared channels for a computer complex having multiple operating systems
US5461721 14 avr. 1993 24 oct. 1995 International Business Machines Corporation System for transferring data between I/O devices and main or expanded storage under dynamic control of independent indirect address words (IDAWs)
US5465359 1 nov. 1993 7 nov. 1995 International Business Machines Corporation Method and system for managing data and users of data in a data processing system
US5500942 1 juin 1995 19 mars 1996 International Business Machines Corporation Method of indicating parallel execution compoundability of scalar instructions based on analysis of presumed instructions
US5517670 30 déc. 1992 14 mai 1996 International Business Machines Corporation Adaptive data transfer channel employing extended data block capability
US5526484 10 déc. 1992 11 juin 1996 International Business Machines Corporation Method and system for pipelining the processing of channel command words
US5528755 22 déc. 1992 18 juin 1996 International Business Machines Corporation Invalid data detection, recording and nullification
US5539918 26 mai 1995 23 juil. 1996 International Business Machines Corporation Extension of data block capability in a data transfer channel
US5546533 16 oct. 1995 13 août 1996 Fujitsu Limited Dynamic device reconfiguration having restricted main storage access for subsystem employing magnetic units
US5548791 25 juil. 1994 20 août 1996 International Business Machines Corporation Input/output control system with plural channel paths to I/O devices
US5561809 11 avr. 1995 1 oct. 1996 International Business Machines Corporation In a multiprocessing system having a coupling facility, communicating messages between the processors and the coupling facility in either a synchronous operation or an asynchronous operation
US5564040 8 nov. 1994 8 oct. 1996 International Business Machines Corporation Method and apparatus for providing a server function in a logically partitioned hardware machine
US5568648 6 juin 1995 22 oct. 1996 International Business Machines Corporation Indirect addressing of channels via logical channel groups
US5584039 8 nov. 1993 10 déc. 1996 International Business Machines Corporation System for coordinating execution of multiple concurrent channel programs without host processor involvement using suspend and resume commands to control data transfer between I/O devices
US5600793 20 déc. 1994 4 févr. 1997 International Business Machines Corporation Method and system of bi-directional parallel port data transfer between data processing systems
US5600805 15 juin 1992 4 févr. 1997 International Business Machines Corporation Pass-through for I/O channel subsystem call instructions for accessing shared resources in a computer system having a plurality of operating systems
US5613163 18 nov. 1994 18 mars 1997 International Business Machines Corporation Method and system for predefined suspension and resumption control over I/O programs
US5640600 31 janv. 1995 17 juin 1997 Hitachi, Ltd. Storage controller and bus control method for use therewith
US5640603 28 janv. 1994 17 juin 1997 International Business Machines Corporation Logical path scheduler for disconnecting currently connected paths to enable logical paths awaiting connection to connect based on path control tables thereof
US5644712 5 juin 1991 1 juil. 1997 International Business Machines Corporation Indirect addressing of channels via logical channel groups
US5671441 29 nov. 1994 23 sept. 1997 International Business Machines Corporation Method and apparatus for automatic generation of I/O configuration descriptions
US5680580 28 févr. 1995 21 oct. 1997 International Business Machines Corporation Remote copy system for setting request interconnect bit in each adapter within storage controller and initiating request connect frame in response to the setting bit
US5758190 9 avr. 1996 26 mai 1998 International Business Machines Corporation Control unit threshold timeout controls for software missing interrupt handlers in operating systems
US5768620 9 avr. 1996 16 juin 1998 International Business Machines Corporation Variable timeout method in a missing-interrupt-handler for I/O requests issued by the same operating system
US5787071 6 nov. 1995 28 juil. 1998 International Business Machines Hop-by-hop flow control in an ATM network
US5793983 22 janv. 1996 11 août 1998 International Business Machines Corp. Input/output channel interface which automatically deallocates failed subchannel and re-segments data block for transmitting over a reassigned subchannel
US5812877 15 mars 1996 22 sept. 1998 Adaptec, Inc. I/O command block chain structure in a memory
US5831985 5 août 1997 3 nov. 1998 Emc Corporation Method and apparatus for controlling concurrent data transmission from multiple sources in a channel communication system
US5845146 5 sept. 1996 1 déc. 1998 Hitachi, Ltd. Extending system of input/output channel
US5860022 21 juil. 1995 12 janv. 1999 Hitachi, Ltd. Computer system and method of issuing input/output commands therefrom
US5894583 9 avr. 1996 13 avr. 1999 International Business Machines Corporation Variable timeout method for improving missing-interrupt-handler operations in an environment having I/O devices shared by one or more systems
US5907684 23 mai 1996 25 mai 1999 International Business Machines Corporation Independent channel coupled to be shared by multiple physical processing nodes with each node characterized as having its own memory, CPU and operating system image
US5918028 8 juil. 1997 29 juin 1999 Motorola, Inc. Apparatus and method for smart host bus adapter for personal computer cards
US5996026 4 avr. 1997 30 nov. 1999 Hitachi, Ltd. Method and apparatus for connecting i/o channels between sub-channels and devices through virtual machines controlled by a hypervisor using ID and configuration information
US6125399 17 avr. 1998 26 sept. 2000 Hitachi, Ltd. Computer system including a plurality of nodes for transferring through a data transfer network messages having distinguishing fields used for distinguishing the messages and controlling receipt thereof
US6125411 13 sept. 1995 26 sept. 2000 Hitachi, Ltd. System storing plural I/O arrangement information wherein each I/O arrangement information corresponding to each operating system is created in response to more than two operating systems
US6195330 5 nov. 1998 27 févr. 2001 Edmund K. Cher Method and system for hit-less switching
US6230218 14 oct. 1998 8 mai 2001 International Business Machines Corporation Apparatus for transferring execution of certain channel functions to a control unit and having means for combining certain commands and data packets in one sequence
US6249787 22 févr. 2000 19 juin 2001 Cisco Systems, Inc. Method and apparatus for transmitting images and other objects over a computer network system
US6263380 9 oct. 1998 17 juil. 2001 Mitutoyo Corporation Measurement data processing unit
US6338105 14 mai 1998 8 janv. 2002 Kabushiki Kaisha Enterprises Data transmission method and game system constructed by using the method
US6343335 29 oct. 1998 29 janv. 2002 International Business Machines Corporation System for repositioning an I/O device to a predetermined position to retry a program without knowledge of which part of the program caused the retry
US6347334 6 janv. 1999 12 févr. 2002 Mcdata Corporation Self-description extended link service for networks
US6351779 12 mars 1999 26 févr. 2002 Agilent Technologies, Inc. Extension library to standard visa library for support of complex I/O functions
US6353612 19 juin 1998 5 mars 2002 Brocade Communications Systems, Inc. Probing device
US6401223 21 mai 1999 4 juin 2002 Unisys Corporation Programmable system for invalidating pending requests within a data processing system
US6460087 24 févr. 1999 1 oct. 2002 Kdd Corporation Method of transferring file
US6466590 12 nov. 1999 15 oct. 2002 Samsung Electronics Co., Ltd. Device and method for processing cell group in a common memory switch
US6484217 20 avr. 1999 19 nov. 2002 International Business Machines Corporation Managing shared devices in a data processing system
US6546435 12 juin 2000 8 avr. 2003 Matsushita Electric Works, Ltd. Portable programming device for supervisory remote control system
US6584511 24 mars 2000 24 juin 2003 Unisys Corporation Loop initialization procedure exception handling for fibre channel transmissions
US6594785 28 avr. 2000 15 juil. 2003 Unisys Corporation System and method for fault handling and recovery in a multi-processing system having hardware resources shared between multiple partitions
US6609161 1 juin 2000 19 août 2003 Adaptec, Inc. Two-dimensional execution queue for host adapters
US6609165 27 sept. 1999 19 août 2003 International Business Machines Corporation Method and apparatus for using fibre channel extended link service commands in a point-to-point configuration
US6647016 9 déc. 1999 11 nov. 2003 Canon Kabushiki Kaisha Communication control method, communication control apparatus, and storage medium
US6651125 28 sept. 1999 18 nov. 2003 International Business Machines Corporation Processing channel subsystem pending I/O work queues based on priorities
US6658603 17 avr. 2000 2 déc. 2003 International Business Machines Corporation Method and apparatus for efficiently generating and implementing engine error codes and verifying the correctness of the implementation of the engine error codes
US6687766 12 janv. 2000 3 févr. 2004 International Business Machines Corporation Method and apparatus for a fibre channel control unit to execute search commands locally
US6693880 20 juin 2001 17 févr. 2004 International Business Machines Corporation System of controlling the flow of information between senders and receivers across links being used as channels
US6694390 11 sept. 2000 17 févr. 2004 Intel Corporation Managing bus transaction dependencies
US6751680 25 févr. 2002 15 juin 2004 Network Appliance, Inc. Protected control of devices by user applications in multiprogramming environments
US6751683 29 sept. 2000 15 juin 2004 International Business Machines Corporation Method, system and program products for projecting the impact of configuration changes on controllers
US6769009 20 avr. 2000 27 juil. 2004 Richard R. Reisman Method and system for selecting a personalized set of information channels
US6772207 28 janv. 1999 3 août 2004 Brocade Communications Systems, Inc. System and method for managing fibre channel switching devices
US6826661 30 août 2002 30 nov. 2004 Veritas Operating Corporation Methods and systems for storage architectures
US6839773 17 oct. 2003 4 janv. 2005 Emc Corporation Method for enabling overlapped input/output requests to a logical device using assigned and parallel access unit control blocks
US6862322 19 mai 2000 1 mars 2005 International Business Machines Corporation Switchable-bandwidth optical receiver
US6898202 27 juin 2001 24 mai 2005 International Business Machines Corporation Method, apparatus and computer program for informing a requesting device of port configuration changes in a computer network switching device
US6915378 23 avr. 2003 5 juil. 2005 Hypernova Technologies, Inc. Method and system for improving the performance of a processing system
US6950888 29 sept. 2000 27 sept. 2005 International Business Machines Corporation Method, system and program products for determining whether I/O constraints exist for controllers of a computing environment
US7000036 12 mai 2003 14 févr. 2006 International Business Machines Corporation Extended input/output measurement facilities
US7003700 8 mai 2002 21 févr. 2006 International Business Machines Corporation Halting execution of duplexed commands
US7020810 10 juil. 2003 28 mars 2006 Intel Corporation Method and apparatus for propagating error status over an ECC protected channel
US7035540 5 janv. 2004 25 avr. 2006 Ciena Corporation Optical fiber ring communication system
US7058735 2 juin 2003 6 juin 2006 Emulex Design & Manufacturing Corporation Method and apparatus for local and distributed data memory access (“DMA”) control
US7085860 11 janv. 2002 1 août 2006 International Business Machines Corporation Method and apparatus for a non-disruptive recovery of a single partition in a multipartitioned data processing system
US7100096 30 sept. 2003 29 août 2006 Hewlett-Packard Development Company, L.P. Special encoding of known bad data
US7111130 12 avr. 2006 19 sept. 2006 International Business Machines Corporation Coherency management for a “switchless” distributed shared memory computer system
US7120728 31 juil. 2002 10 oct. 2006 Brocade Communications Systems, Inc. Hardware-based translating virtualization switch
US7124207 14 août 2003 17 oct. 2006 Adaptec, Inc. I2O command and status batching
US7133988 25 févr. 2004 7 nov. 2006 Hitachi, Ltd. Method and apparatus for managing direct I/O to storage systems in virtualization
US7149823 29 août 2003 12 déc. 2006 Emulex Corporation System and method for direct memory access from host without processor intervention wherein automatic access to memory during host start up does not occur
US7155569 28 juin 2002 26 déc. 2006 Lsi Logic Corporation Method for raid striped I/O request generation using a shared scatter gather list
US7164425 21 déc. 2004 16 janv. 2007 Qlogic Corporation Method and system for high speed network application
US7174274 11 mai 2005 6 févr. 2007 International Business Machines Corporation Gathering I/O measurement data during an I/O operation process
US7202801 11 déc. 2002 10 avr. 2007 Geospatial Technologies, Inc. Method and apparatus for an automated location-based, dynamic notification system (ALDNS)
US7277387 30 janv. 2003 2 oct. 2007 Wind River Systems, Inc. Package manager
US7315911 11 juil. 2005 1 janv. 2008 Dot Hill Systems Corporation Method for efficient inter-processor communication in an active-active RAID system using PCI-express links
US7373435 18 nov. 2005 13 mai 2008 International Business Machines Corporation Extended input/output measurement block
US7382733 12 févr. 2004 3 juin 2008 International Business Machines Corporation Method for handling reordered data packets
US7395284 21 janv. 2005 1 juil. 2008 Hitachi, Ltd. storage system
US7398335 22 nov. 2004 8 juil. 2008 Qlogic, Corporation Method and system for DMA optimization in host bus adapters
US7484021 12 janv. 2006 27 janv. 2009 Cisco Technology, Inc. Technique for implementing virtual fabric membership assignments for devices in a storage area network
US7500023 10 oct. 2006 3 mars 2009 International Business Machines Corporation Facilitating input/output processing by using transport control words to reduce input/output communications
US7500030 30 août 2006 3 mars 2009 International Business Machines Corporation Control of information units in fibre channel communications
US7502873 10 oct. 2006 10 mars 2009 International Business Machines Corporation Facilitating access to status and measurement data associated with input/output processing
US7512133 3 déc. 2001 31 mars 2009 International Business Machines Corporation Method and apparatus for obtaining multiple port addresses by a fibre channel from a network fabric
US7516248 28 déc. 2007 7 avr. 2009 International Business Machines Corporation Obtaining extended queue measurement data for a range of logical control unit queues
US7539777 25 oct. 2002 26 mai 2009 Cisco Technology, Inc. Method and system for network time protocol forwarding
US7543087 14 avr. 2003 2 juin 2009 Alacritech, Inc. Freeing transmit memory on a network interface device prior to receiving an acknowledgement that transmit data has been received by a remote device
US7555554 6 août 2004 30 juin 2009 Microsoft Corporation System and method for generating selectable extension to media transport protocol
US7558827 14 oct. 2004 7 juil. 2009 Nippon Telegraph And Telephone Corporation Mail distribution system, mail distribution method, and mail distribution program
US7564791 29 déc. 2003 21 juil. 2009 Intel Corporation Monitoring packet flows
US7577772 8 sept. 2004 18 août 2009 Qlogic, Corporation Method and system for optimizing DMA channel selection
US7577773 9 sept. 2005 18 août 2009 Qlogic, Corporation Method and system for DMA optimization
US7594057 9 janv. 2006 22 sept. 2009 Qlogic, Corporation Method and system for processing DMA requests
US7599360 26 déc. 2001 6 oct. 2009 Cisco Technology, Inc. Methods and apparatus for encapsulating a frame for transmission in a storage area network
US7600053 28 déc. 2007 6 oct. 2009 International Business Machines Corporation Emulation of extended input/output measurement block facilities
US7711871 30 août 2004 4 mai 2010 Crossroads Systems, Inc. Interface device and method for command processing
US7743197 11 mai 2006 22 juin 2010 Emulex Design & Manufacturing Corporation System and method for virtualizing PCIe devices
US7765336 11 juin 2007 27 juil. 2010 Emulex Design & Manufacturing Corporation Autonomous mapping of protected data streams to fibre channel frames
US7826349 30 mai 2006 2 nov. 2010 Intel Corporation Connection management mechanism
US7840717 14 févr. 2008 23 nov. 2010 International Business Machines Corporation Processing a variable length device command word at a control unit in an I/O processing system
US7840718 14 févr. 2008 23 nov. 2010 International Business Machines Corporation Processing of data to suspend operations in an input/output processing log-out system
US7840719 25 févr. 2009 23 nov. 2010 International Business Machines Corporation System and program products for facilitating input/output processing by using transport control words to reduce input/output communications
US7856511 29 juil. 2008 21 déc. 2010 International Business Machines Corporation Processing of data to suspend operations in an input/output processing system
US7941570 14 févr. 2008 10 mai 2011 International Business Machines Corporation Bi-directional data transfer within a single I/O operation
US20010030943 20 juin 2001 18 oct. 2001 International Business Machines Corporation System of controlling the flow of information between senders and receivers across links being used as channels
US20020032810 17 juil. 2001 14 mars 2002 Wagner Richard Hiers Open network system for I/O operation including a common gateway interface and an extended open network protocol with non-standard I/O devices utilizing device and identifier for operation to be performed with device
US20020062407 10 janv. 2002 23 mai 2002 Jiro Tateyama Data communication apparatus and method
US20020099967 28 juin 2001 25 juil. 2002 Hiroshi Kawaguchi Transmission method, transmission system, transmission apparatus and transmission control apparatus
US20020152338 27 août 2001 17 oct. 2002 Elliott Joseph C. Method, system and program product for detecting lost sequences within an exchange on fibre channel
US20020178404 22 mars 2001 28 nov. 2002 International Business Machines Corporation Method for prioritizing bus errors
US20030002492 27 juin 2001 2 janv. 2003 International Business Machines Corporation Method, apparatus and computer program for informing a requesting device of port configuration changes in a computer network switching device
US20030056000 24 juil. 2002 20 mars 2003 Nishan Systems, Inc. Transfer ready frame reordering
US20030084213 28 sept. 2001 1 mai 2003 International Business Machines Corporation Low overhead I/O interrupt
US20030103504 3 déc. 2001 5 juin 2003 International Business Machines Corporation Method and apparatus for obtaining multiple port addresses by a fibre channel from a network fabric
US20030158998 19 févr. 2002 21 août 2003 Hubbert Smith Network data storage-related operations
US20030187627 29 mars 2002 2 oct. 2003 International Business Machines Corporation I/O velocity projection for bridge attached channel
US20030188053 1 avr. 2002 2 oct. 2003 Chun-Nan Tsai Method for verifying clock signal frequency of computer sound interface
US20030208581 2 mai 2002 6 nov. 2003 Behren Paul D. Von Discovery of fabric devices using information from devices and switches
US20040030822 9 août 2002 12 févr. 2004 Vijayan Rajan Storage virtualization by layering virtual disk objects on a file system
US20040054776 12 sept. 2003 18 mars 2004 Finisar Corporation Network expert analysis process
US20040113772 11 déc. 2002 17 juin 2004 Y. Hong Chou Method and apparatus for an automated location-based, dynamic notification system ( ALDNS)
US20040125960 30 août 2001 1 juil. 2004 Fosgate James W. Method for apparatus for audio matrix decoding
US20040136241 9 oct. 2003 15 juil. 2004 Lockheed Martin Corporation Pipeline accelerator for improved computing architecture and related system and method
US20040151160 30 janv. 2003 5 août 2004 Michael Sanders Package manager
US20040193968 14 mars 2003 30 sept. 2004 International Business Machines Corporation Transfer of error-analysis and statistical data in a fibre channel input/output system
US20040210719 10 mai 2004 21 oct. 2004 Bushey Robert D. Method for evaluation of scalable symmetric multiple processor cache coherency protocols and algorithms
US20040230706 12 mai 2003 18 nov. 2004 International Business Machines Corporation Extended input/output measurement facilities
US20040260851 22 août 2003 23 déc. 2004 Chun-Yen Tu Data transmission method for microprocessors in a programmable logic controller
US20050018673 20 juil. 2004 27 janv. 2005 Dropps Frank R. Method and system for using extended fabric features with fibre channel switch elements
US20050102456 5 nov. 2004 12 mai 2005 Samsung Electronics Co., Ltd. Command transmission method and command transmission apparatus in pipeline bus system
US20050105456 18 nov. 2003 19 mai 2005 Cookson Christopher J. Double-sided optical disc
US20050108251 24 déc. 2004 19 mai 2005 Microsoft Corporation Stateless distributed computer architecture with server-oriented state-caching objects maintained on network or client
US20050175341 19 déc. 2003 11 août 2005 Shlomo Ovadia Method and architecture for optical networking between server and storage area networks
US20050204069 11 mai 2005 15 sept. 2005 International Business Machines Corporation Gathering I/O measurement data during an I/O operation process
US20050216617 11 mai 2005 29 sept. 2005 International Business Machines Corporation Obtaining queue measurement data for a range of logical control unit queues
US20050223291 24 mars 2004 6 oct. 2005 Zimmer Vincent J Methods and apparatus to provide an execution mode transition
US20050229033 24 mars 2005 13 oct. 2005 Kabushiki Kaisha Toshiba Disk array controller and information processing apparatus
US20050257118 13 mai 2004 17 nov. 2005 Shin-Lin Shien Cyclic redundancy check modification for message length detection and error detection
US20060036769 30 avr. 2004 16 févr. 2006 Frey Robert T Storage switch task processing synchronization
US20060050726 3 sept. 2004 9 mars 2006 Ahmed Ali U Transmit adaptive equalization for communication system with one or more serial data channels
US20060075154 18 nov. 2005 6 avr. 2006 International Business Machines Corporation Extended input/output measurement block
US20060085595 4 oct. 2005 20 avr. 2006 Slater Alastair M Identifying performance affecting causes in a data storage system
US20060159112 14 janv. 2005 20 juil. 2006 Cisco Technology, Inc. Dynamic and intelligent buffer management for SAN extension
US20060224795 2 juin 2005 5 oct. 2006 Junichi Muto Data processing system, data processing method and program
US20070005838 30 juin 2005 4 janv. 2007 Naichih Chang Serial ATA port addressing
US20070016554 17 juil. 2006 18 janv. 2007 Dapp Michael C Hardware accelerated validating parser
US20070061463 8 nov. 2005 15 mars 2007 Hitachi, Ltd. Data processing system
US20070072543 1 sept. 2006 29 mars 2007 Nokia Corporation Enhanced signaling of pre-configured interaction message in service guide
US20070079022 1 sept. 2006 5 avr. 2007 Carlson Scott M Gathering I/O Measurement Data During an I/O Operation Process
US20070079051 1 sept. 2006 5 avr. 2007 Naoki Tanaka Data reading device
US20070091497 8 déc. 2005 26 avr. 2007 Makio Mizuno Control of storage system using disk drive device having self-check function
US20070162631 28 déc. 2005 12 juil. 2007 International Business Machines Corporation Method for selectable software-hardware internet SCSI
US20070174544 16 mars 2006 26 juil. 2007 Hitachi, Ltd. Data processing system and data processing method
US20070239944 16 févr. 2007 11 oct. 2007 Emulex Design & Manufacturing Corporation Apparatus for performing storage virtualization
US20070294697 23 avr. 2007 20 déc. 2007 Microsoft Corporation Extensible job submission
US20080040519 1 mai 2007 14 févr. 2008 Alacritech, Inc. Network interface device with 10 Gb/s full-duplex transfer rate
US20080043563 15 août 2006 21 févr. 2008 International Business Machines Corporation Flexibly controlling the transfer of data between input/output devices and memory
US20080059638 30 août 2006 6 mars 2008 International Business Machines Corporation Persistent information unit pacing
US20080103754 28 déc. 2007 1 mai 2008 International Business Machines Corporation Emulation of Extended Input/Output Measurement Block Facilities
US20080103755 28 déc. 2007 1 mai 2008 International Business Machines Corporation Extended Input/Output Measurement Word Facility, and Emulation of that Facility
US20080109580 28 déc. 2007 8 mai 2008 International Business Machines Corporation Obtaining extended queue measurement data for a range of logical control unit queues
US20080147889 10 oct. 2006 19 juin 2008 International Business Machines Corporation Facilitating input/output processing by using transport control words to reduce input/output communications
US20080147890 10 oct. 2006 19 juin 2008 International Business Machines Corporation Facilitating access to status and measurement data associated with input/output processing
US20080183877 22 oct. 2007 31 juil. 2008 International Business Machines Corporation Establishing a logical path between servers in a coordinated timing network
US20080235553 2 juin 2008 25 sept. 2008 At&T Mobility Ii Llc Data Link Layer Tunneling Technique for High-Speed Data in a Noisy Wireless Environment
US20080256264 20 juin 2008 16 oct. 2008 Junichi Muto Data processing system, data processing method and program
US20080273518 10 avr. 2008 6 nov. 2008 Hart Communication Foundation Suspending Transmissions in a Wireless Network
US20080307122 11 juin 2007 11 déc. 2008 Emulex Design & Manufacturing Corporation Autonomous mapping of protected data streams to Fibre channel frames
US20090049241 27 oct. 2008 19 févr. 2009 Hiroshi Ohno Method for controlling storage system, and storage control apparatus
US20090055585 24 août 2007 26 févr. 2009 Datadirect Networks, Inc. Method for auto-correction of errors in a raid memory system
US20090144586 3 févr. 2009 4 juin 2009 International Business Machines Corporation System and program products for facilitating access to status and measurement data associated with input/output processing
US20090172203 25 févr. 2009 2 juil. 2009 International Business Machines Corporation System and program products for facilitating input/output processing by using transport control words to reduce input/output communications
US20090210557 14 févr. 2008 20 août 2009 International Business Machines Corporation Determining extended capability of a channel path
US20090210559 14 févr. 2008 20 août 2009 International Business Machines Corporation Processing a variable length device command word at a control unit in an i/o processing system
US20090210560 14 févr. 2008 20 août 2009 International Business Machines Corporation Cancel instruction and command for determining the state of an i/o operation
US20090210561 14 févr. 2008 20 août 2009 International Business Machines Corporation Processing of data to perform system changes in an input/output processing system
US20090210562 14 févr. 2008 20 août 2009 International Business Machines Corporation Processing communication data in a ships passing condition
US20090210563 14 févr. 2008 20 août 2009 International Business Machines Corporation Providing indirect data addressing for a control block at a channel subsystem of an i/o processing system
US20090210564 29 juil. 2008 20 août 2009 International Business Machines Corporation Processing of data to suspend operations in an input/output processing system
US20090210570 14 févr. 2008 20 août 2009 International Business Machines Corporation Extended measurement word determination at a channel subsystem of an i/o processing system
US20090210571 14 févr. 2008 20 août 2009 International Business Machines Corporation Processing of data to monitor input/output operations
US20090210572 14 févr. 2008 20 août 2009 International Business Machines Corporation Computer command and response for determining the state of an i/o operation
US20090210573 14 févr. 2008 20 août 2009 International Business Machines Corporation Computer command and response for determining the state of an i/o operation
US20090210576 14 févr. 2008 20 août 2009 International Business Machines Corporation Providing indirect data addressing in an input/output processing system where the indirect data address list is non-contiguous
US20090210579 14 févr. 2008 20 août 2009 International Business Machines Corporation Open exchange limiting in an i/o processing system
US20090210580 14 févr. 2008 20 août 2009 International Business Machines Corporation Early termination of an i/o operation in an i/o processing system
US20090210581 14 févr. 2008 20 août 2009 International Business Machines Corporation Bi-directional data transfer within a single i/o operation
US20090210582 14 févr. 2008 20 août 2009 International Business Machines Corporation Providing extended measurement data in an i/o processing system
US20090210583 14 févr. 2008 20 août 2009 International Business Machines Corporation Reserved device access contention reduction
US20090210584 14 févr. 2008 20 août 2009 International Business Machines Corporation Exception condition determination at a control unit in an i/o processing system
US20090210585 14 févr. 2008 20 août 2009 International Business Machines Corporation Processing of data to suspend operations in an input/output processing log-out system
US20090210768 14 févr. 2008 20 août 2009 International Business Machines Corporation Exception condition handling at a channel subsystem in an i/o processing system
US20090210769 14 févr. 2008 20 août 2009 International Business Machines Corporation Multiple crc insertion in an output data stream
US20090210884 14 févr. 2008 20 août 2009 International Business Machines Corporation Processing of data to determine compatability in an input/output processing system
US20090307388 9 juin 2009 10 déc. 2009 Yves Constantin Tchapda Methods of providing access to i/o devices
US20100014526 18 juil. 2008 21 janv. 2010 Emulex Design & Manufacturing Corporation Hardware Switch for Hypervisors and Blade Servers
US20100030919 31 juil. 2008 4 févr. 2010 International Business Machines Corporation Transport control channel program message pairing
US20100030920 * 31 juil. 2008 4 févr. 2010 International Business Machines Corporation Transport control channel program chain linking
US20100064072 9 sept. 2008 11 mars 2010 Emulex Design & Manufacturing Corporation Dynamically Adjustable Arbitration Scheme
US20110173640 * 8 janv. 2010 14 juil. 2011 International Business Machines Corporation Controlling operations according to another system's architecture
DE3931514C2 21 sept. 1989 25 janv. 1996 Hitachi Ltd Kanaladapter
GB1264096A Titre non disponible
GB2291990A Titre non disponible
JP63236152A Titre non disponible
JP2010140127A Titre non disponible
WO2006102664A2 23 mars 2006 28 sept. 2006 Qualcomm Incorporated Method and system for encoding variable length packets with variable instruction sizes
1 "Information Technology-Fibre Channel Protocol for SCSI, Third Version (FCP-3)," T10 Project 1560-D, Revision 4g, Sep. 13, 2005.
2 "Protocol for Insochronous Traffic Over Fiber Channel Switching"; IBM Technical Disclosure Bulletin; vol. 37, No. 06B; Jun. 1994. pp. 377-380.
3 "z/Architecture-Principles of Operation," IBM Publication No. SA22-7832-04, 5th Ed., Sep. 2005.
4 Aboda et al.; Network Working Group; "Securing Block Storage Protocols Over IP"; ACM Digital Library; RFC3723; Apr. 2004.
5 ANSI INCITS 433-2007, Information Technology Fibre Channel Link Services (FC-LS), Jul. 2007.
6 Azimi et al.; "miNI: Reducing Network Interface Memory Requirements with Dynamic Handle Lookup"; ACM Digital Library; pp. 261-272; Jun. 2003.
7 Behrs, JR, "Adaptive Prediction Minimizes Data Overrun and Underrun", IBM, Nov. 1994, pp. 1-3. http://priorartdatabase.com/IPCOM/000114189.
8 Cakmakci, Melih, et al. "Bi-Directional Communication amoung "Smart" Compoents in a Networked Control System", University of Michigan: Department of Mechanical Engineering, 2005 American control conference, Jun. 8-10, 2005, Portland, OR, pp. 627-632.
9 Dauby et al. "Contention Resolution Between Two Processors"; IBM Technical Disclosure Bulletin; vol. 26; No. 10A; Mar. 1984; 3 pages.
10 DeVeer, J.A.; "Control Frame Multiplexing on Serial I/O Channels"; IBM Technical Disclosure Bulletin; vol. 32; No. 10A; Mar. 1990; pp. 39-40.
11 Emulex Corporation; "Install the LP850 Host Adapter"; GOOGLE/Emulex Corporation, LightPulse LP850 Fibre Channel PCI Host Adapter Manuals; pp. 1-10, 1999.
12 Fibre Channel Single Byte Command Code Sets-2 Mapping Protocol (FC-SB-3), T11/Project 1357-D/Rev 1.6, INCITS Mar. 2003.
13 Final Office Action for U.S. Appl. No. 12/030,912 mailed Oct. 6, 2010.
14 Foong et al.; "Towards Ssd-Ready Enterprise Platforms"; Google/Intel Corporation; 2008-2009.
15 Golasky, Richard; "Link-Level Error Recovery With Tape Backup"; Dell Power Solutions; Aug. 2005; pp. 88-91.
16 Hewlett-Packard Company; "HP A5149 PCI Ultra2 CSI Host Bus Adapter—Service and User Guide", Edition 2; GOOGLE/H-P; 2001.
17 Hewlett-Packard Company; HP A4800A PCI FWD SCSI Host Bus Adapter—Service & User Guide, Edition 6; GOOGLE/H-P; 2001.
18 IBM, "Method and Apparatus to Monitor Pav Utilization", Feb. 2005, pp. 1-3. http://priorartdatabase.com/IPCOM/000082878.
19 IBM® z/Architecture Principles of Operation, Publication No. SA22-7832-05, 6th Edition, Apr. 2007. 1,215 pages separated into 4 electronic attachments. Part 2.
20 IBM® z/Architecture Principles of Operation, Publication No. SA22-7832-05, 6th Edition, Apr. 2007. 1,215 pages separated into 4 electronic attachments. Part 3.
21 IBM® z/Architecture Principles of Operation, Publication No. SA22-7832-05, 6th Edition, Apr. 2007. 1,215 pages separated into 4 electronic attachments. Part 4.
22 IBM® z/Architecture Principles of Operation, Publication No. SA22-7832-05, 6th Edition, Apr. 2007. 1,215 pages separated into 4 electronic attachments-Part 1.
23 IBM® z/Architecture Principles of Operation, Publication No. SA22-7832-05, 6th Edition, Apr. 2007. 1,215 pages separated into 4 electronic attachments—Part 1.
24 Ichikawa et al. "Bi-Directional OFDM Transmission using Adaptive Modulation that spreads Data Symbols". Power Line Communications and its Applications, 2006, IEEE International Symposium on, vol., No., pp. 202-207.
25 International Search Report and Written Opinion for PCT/EP2009/051447 dated Jul. 1, 2009.
26 International Search Report and Written Opinion for PCT/EP2009/051483 dated Jul. 27, 2009.
27 International Search Report; International Application No. PCT/EP2009/059184; International Filing Date: Jul. 16, 2009; Date of mailing: Jan. 14, 2010; 9 pages.
28 Iren et al.; "The Transport Layer: Tutorial and Survey"; ACM Computing Surveys; vol. 31, No. 4; Dec. 1999; pp. 360-405.
29 Jiang, J.-et al.; "The Role of FCoE in I/O Consolidation"; ACM Digital Library/International Conf on Advanced Infocomm Technology '08; Jul. 2008.
30 Josephson, WK.-et al.; "DFS: A File System for Virtualized Flash Storage"; ACM Digital Library; vol. 6, No. 3, Article 14, Sep. 2010.
31 Laudon et al. •System Overview of the SGI Origin 200/2000 Product Line, 1997, iEEE Publication pp. 150-156.
32 LSI Corporation; "PCI Express to 6Gb/s SAS Host Bus Adapters"; GOOGLE; Chapter 1, Introduction/Overview; LSI User Guide; Oct. 2009.
33 LSI; "ScsiPortGetDeivceBase"; GOOGLE/LSI; Apr. 2003.
34 Magoutis, K.; "The Optimistic Direct Access File System: Design and Network Interface Support"; Division of Engineering & Applied Science, Harvard Univ.; Feb. 2002.
35 Meritt, A.S. And J.H. Sorg, "Correction of Channel Measurement Data Caused by Control Unit Queuing," IBM Technical Disclosure Bulletin, vol. 33, No. 11, Apr. 1991, pp. 100-103.
36 Miller et al.; "Motivating Future Interconnects: A Differential Measurement Analysis of PCI Latency"; ACM Digital Library; pp. 94-105; Oct. 2009.
37 Moore et al., Reconfiguration of Storage Elements to Improve Performance, IBM, Dec. 1983, pp. 1-3. http://priorartdatabas.com/IPCOM/000047719.
38 Network Storage Systems; GOOGLE; Oct. 2007.
39 Nordstrom.; "Sequence Reception Method for a Fibre Channel Protocol Chip"; IBM Technical Disclosure Bulletin; vol. 38, No. 12; Dec. 1995; pp. 267-269.
40 Patent No. 7,000,036 Non-Final Office Action dated Jul. 15, 2005.
41 Patent No. 7,000,036 Notice of Allowance dated Feb. 3, 2006.
42 Patent No. 7,174,274 Non-Final Office Action dated Jun. 21, 2006.
43 Patent No. 7,174,274 Non-Final Office Action dated Jun. 8, 2006.
44 Patent No. 7,174,274 Notice of Allowance Dec. 27, 2006.
45 Patent No. 7,174,274 Notice of Allowance Sep. 13, 2007.
46 Patent No. 7,373, 435 Non-Final Office Action Sep. 13, 2007.
47 Patent No. 7,373,435 Non-Final Office Action Jun. 11, 2007.
48 Patent No. 7,373,435 Notice of Allowance dated Apr. 30, 2008.
49 Patent No. 7,516,248 Notice of Allowance Feb. 20, 2009.
50 Patent No. 7,600,053 Non-Final Office Action dated Mar. 17, 2009.
51 Patent No. 7,600,053 Notice of Allowance dated Aug. 26, 2009.
52 Petersen et al.; "DIF/DIX Aware Linux SCSI HBA Interface"; Google; Oracle Linux Engineering; Jul. 2008.
53 Peterson; "Information Techonology, Fibre Channel Protocol for SCSI, Fourth Version (FCP-3)", Draft Proposed American National Standard, Jun. 2004; pp. 1-142.
54 POU920070218US1, U.S. Appl. No. 12/030,938, Notice of Allowance Mailed Aug. 8, 2011.
55 POU920080042US1, U.S. Appl. No. 12/030,989, Notice of Allowance Mailed Aug. 5, 2011.
56 Sachs, M.W.; "I/O Marker Changing"; IBM Technical Disclosure Bulletin; vol. 37, No. 02A; Feb. 1994; pp. 75-76.
57 Satran et al.; Network Working Group; "Internet Small Computer Systems Interface (iSCSI)"; ACM Digital Library; RFC3720; Apr. 2004.
58 SCSI Primary Commands—4 (SPC-4); Project T10/1731-D. Rev 11. INCITS Apr. 14, 2010.
59 Simmons et al.; "A Performance Comparison of Three Supercomputers: Fujitsu VP-2600, NEC SX-3, and Cray YMP"; ACM, Conference on High Performance Networking and Computing, Proceedings of the 1991 ACM/IEEE conference on Supercomputing, Albuquerque, New Mexico; Jul. 1991; pp. 150-157.
60 Snively et al.; Fibre Channel Single Byte Command Code Sets-3 Mapping Protocol (FC-SB-3); T11/Project 1357-D/Rev. 1.6, INCITS; Mar. 2003; pp. 1-206.
61 Snively, et al.; "Fibre Channel, Framing and Signaling"; (FC-FS) Rev. 1.70; NCITS Working Draft Proposed American National Standard for Information Technology; Feb. 2002; pp. i-575.
62 Srikrishnan et al.; "Sharing FCP Adapters Through Virtualization"; IBM J. Res. & Dev., vol. 51, No. 1/2; Jan./Mar. 2007; pp. 103-118.
63 Stone et al.; "When the CRC and TCP Checksum Disagree"; SIGCOMM '00, Stockholm, Sweden; Jul. 2000; 10 pages.
64 Sun, Oracle; "Sun Storage 6 Gb SAS PCIe HBA, External-Installation Guide for HBA Models"; GOOGLE; Revision A; Nov. 2010.
65 Sun, Oracle; "Sun Storage 6 Gb SAS PCIe HBA, External—Installation Guide for HBA Models"; GOOGLE; Revision A; Nov. 2010.
66 Tachikawa, T., et al. "Arq protocols for bi-directional data transmission," Information Networking, 1998 (ICOIN-12) Proceedings., Twelfth International Conference on., vol., No., pp. 468-473, Jan. 21-23, 1998.
67 U.S. App. No. 12/030,920 Non-Final Office Action dated Feb. 23, 2010.
68 U.S. Appl. 12/183,315, Notice of Allowance Mailed on Jun. 15, 2010.
69 U.S. Appl. No. 11/126,728 Non-Final Office Action Apr. 16, 2007.
70 U.S. Appl. No. 11/469,573 Non-Final Office Action dated Apr. 11, 2008.
71 U.S. Appl. No. 11/548,060 Non-Final Office Action dated Apr. 15, 2008.
72 U.S. Appl. No. 11/548,093 Non-Final Office Action dated Apr. 17, 2008.
73 U.S. Appl. No. 11/965,866 Non-Final Office Action dated Jun. 3, 2010.
74 U.S. Appl. No. 12/030,912 Non Final Office Action Mailed Aug. 18, 2011.
75 U.S. Appl. No. 12/030,912 Non-Final Office Action dated Mar. 18, 2010.
76 U.S. Appl. No. 12/030,920 Notice of Allowance Mailed Aug. 23, 2010.
77 U.S. Appl. No. 12/030,920, Notice of Allowance Mailed Dec. 28, 2010.
78 U.S. Appl. No. 12/030,925, Notice of Allowance Mailed Feb. 14, 2008.
79 U.S. Appl. No. 12/030,932 Non-Final Office Action dated Dec. 16, 2009.
80 U.S. Appl. No. 12/030,932, Final Office Action Mailed Jul. 23, 2010.
81 U.S. Appl. No. 12/030,932, Non-Final Office Action Mailed Dec. 16, 2010.
82 U.S. Appl. No. 12/030,932, Notice of Allowance mailed Nov. 1, 2011.
83 U.S. Appl. No. 12/030,939 Non-Final Office Action dated Nov. 16, 2009.
84 U.S. Appl. No. 12/030,939 Notice of Alllowance mailed Jun. 29, 2010.
85 U.S. Appl. No. 12/030,951 Non-Final Office Action dated May 20, 2010.
86 U.S. Appl. No. 12/030,951 Non-Final Office Action dated Nov. 23, 2009.
87 U.S. Appl. No. 12/030,951, Final Office Action Mailed Oct. 26, 2010.
88 U.S. Appl. No. 12/030,951, Notice of Allowance Mailed Apr. 4, 2011.
89 U.S. Appl. No. 12/030,954 Non Final Office Action mailed Jul. 12, 2010.
90 U.S. Appl. No. 12/030,954 Non-Final Office Action dated Jan. 21, 2010.
91 U.S. Appl. No. 12/030,954, Notice of Allowance mailed Dec. 28, 2010.
92 U.S. Appl. No. 12/030,961 Final Office Action mailed Jul. 12, 2010.
93 U.S. Appl. No. 12/030,961 Non-Final Office Action dated Dec. 17, 2009.
94 U.S. Appl. No. 12/030,961 Notice of Allowance Mailed Nov. 5, 2010.
95 U.S. Appl. No. 12/030,967 Notice of Allowance Mailed Oct. 7, 2010.
96 U.S. Appl. No. 12/030,967 Restriction Requirement Mailed Dec. 29, 2009.
97 U.S. Appl. No. 12/030,967, Notice of Allowance mailed Apr. 23, 2010.
98 U.S. Appl. No. 12/030,975 Non-Final Office Action dated Oct. 22, 2009.
99 U.S. Appl. No. 12/030,975, Notice of Allowance Mailed Oct. 19, 2010.
100 U.S. Appl. No. 12/030,975. Final Office Action Mailed May 15, 2010.
101 U.S. Appl. No. 12/030,981 Non Final Office Action Mailed Aug. 2, 2011.
102 U.S. Appl. No. 12/030,985, Notice of Allowance mailed Nov. 24, 2010.
103 U.S. Appl. No. 12/030,989 Final Office Action dated May 24, 2010.
104 U.S. Appl. No. 12/030,989 Non-Final Office Action dated Oct. 22, 2009.
105 U.S. Appl. No. 12/030,993 Non Final Office Action mailed Jun. 28, 2010.
106 U.S. Appl. No. 12/030,993 Non-Final Office Action dated Oct. 28, 2009.
107 U.S. Appl. No. 12/030,993 Notice of Allowance Mailed Dec. 22, 2011.
108 U.S. Appl. No. 12/030,993, Final Office Action Mailed Dec. 10, 2010.
109 U.S. Appl. No. 12/031,021 Non-Final Office Action dated Jan. 8, 2010.
110 U.S. Appl. No. 12/031,021 Notice of Allowance mailed Jul. 8, 2010.
111 U.S. Appl. No. 12/031,021, Notice of Allowance Mailed Apr. 30, 2010.
112 U.S. Appl. No. 12/031,023 Non Final Office Action mailed Jun. 11, 2010.
113 U.S. Appl. No. 12/031,023 Non-Final Office Action dated Oct. 29, 2009.
114 U.S. Appl. No. 12/031,023, Final Office Action Mailed Nov. 18, 2010.
115 U.S. Appl. No. 12/031,023, Non-Final Office Action Mailed Feb. 1, 2012.
116 U.S. Appl. No. 12/031,038 Non-Final Office Action dated Nov. 16, 2009.
117 U.S. Appl. No. 12/031,038, Non-Final Office Action Mailed Apr. 15, 2010.
118 U.S. Appl. No. 12/031,038, Notice of Allowance Mailed Oct. 6, 2010.
119 U.S. Appl. No. 12/031,042, Final Office Action Mailed Oct. 25, 2010.
120 U.S. Appl. No. 12/031,042, Non-Final Office Action Mailed Apr. 5, 2010.
121 U.S. Appl. No. 12/031,042, Non-Final Office Action Mailed Sep. 30, 2011.
122 U.S. Appl. No. 12/031,182 Final Office Action dated Oct. 20, 2011.
123 U.S. Appl. No. 12/031,182 Final Office Action Mailed Jul. 22, 2010.
124 U.S. Appl. No. 12/031,182 Non-Final Office Action dated Jan. 22, 2010.
125 U.S. Appl. No. 12/031,182, Non Final Office Action Mailed Dec. 23, 2010.
126 U.S. Appl. No. 12/031,201 Final Office Action dated Jun. 13, 2011.
127 U.S. Appl. No. 12/031,201 Non-Final Office Action dated Jan. 25, 2010.
128 U.S. Appl. No. 12/031,201, Final Office Action Mailed Aug. 3, 2010.
129 U.S. Appl. No. 12/031,201, Non-Final Office Action Mailed Dec. 27, 2011.
130 U.S. Appl. No. 12/181,662, Notice of Allowance Mailed Aug. 4, 2010.
131 U.S. Appl. No. 12/181,662-Final Office Action dated Jan. 4, 2010.
132 U.S. Appl. No. 12/181,662—Final Office Action dated Jan. 4, 2010.
133 U.S. Appl. No. 12/181,662-Non-Final Office Action dated Jun. 18, 2009.
134 U.S. Appl. No. 12/181,662—Non-Final Office Action dated Jun. 18, 2009.
135 U.S. Appl. No. 12/183,305, filed Jul. 31, 2008.
136 U.S. Appl. No. 12/183,305, Non-Final Office Action Mailed May 11, 2010.
137 U.S. Appl. No. 12/183,305, Notice of Allowance Mailed Nov. 1, 2010.
138 U.S. Appl. No. 12/183,315 Notice of Allowance Mailed Sep. 15, 2010.
139 U.S. Appl. No. 12/183,315, filed Jul. 31, 2008.
140 U.S. Appl. No. 12/183,315, Notice of Allowance Mailed Dec. 13, 2010.
141 U.S. Appl. No. 12/183,323 Non Final Office Action mailed Jul. 19, 2010.
142 U.S. Appl. No. 12/183,323, filed Jul. 31, 2008.
143 U.S. Appl. No. 12/183,323, Non-Final Office Action Mailed Jan. 3, 2011.
144 U.S. Appl. No. 12/183,323, Notice of Allowance Mailed Jun. 23, 2011.
145 U.S. Appl. No. 12/364,615, Non Final Office Action Mailed Oct. 7, 2010.
146 U.S. Appl. No. 12/364615, Notice of Allowance Mailed Mar. 10, 2011.
147 U.S. Appl. No. 12/392,246 Notice of Allowance mailed Jul. 15, 2010.
148 U.S. Appl. No. 12/946,514, Non-Final Office Action Mailed Jun. 23, 2011.
149 U.S. Appl. No. 13/024,468, Non Final Office Action Mailed Jan. 26, 2012.
150 U.S. Appl. No. 13/075,993 Non Final Office Action Mailed Aug. 31, 2011.
151 U.S. Appl. No. 13/075,993, Final Office Action Mailed Feb. 13, 2012.
152 U.S. Appl. No. 13/150,583, Non-Final Office Action Mailed Feb. 3, 2012.
153 U.S. Appl. No. 13/173,733, Non-Final Office Action Mailed Feb. 7, 2012.
154 U.S. Appl. No. 13/173,772 Non Final Office Action Mailed Feb. 3, 2012.
155 U.S. Application No. 12/0303,985, Non Final Office Action Mailed May 5, 2010.
156 URL, http://en.wikipedia.org/wiki/FICON, FICON, Wikipedia, USA, Wikimedia Foundation, Inc., Aug. 9, 2011.
157 Vaghani, SB.; "Virtual Machine File System"; VMWare Inc./ACM Digital Library; pp. 57-69; 2008-2009.
158 Written Opinion and International Search Report for PCT/EP2009/051445 dated Jun. 25, 2009.
159 Written Opinion and International Search Report for PCT/EP2009/051446 dated Jun. 25, 2009.
160 Written Opinion and International Search Report for PCT/EP2009/051450 dated Jul. 7, 2009.
161 Written Opinion and International Search Report for PCT/EP2009/051459 dated Jun. 23, 2009.
162 Written Opinion and International Search Report for PCT/EP2009/051461 dated Sep. 22, 2009.
163 Written Opinion and International Search Report for PCT/EP2009/051462 dated Jul. 1, 2009.
164 Written Opinion and International Search Report for PCT/EP2009/051463 dated Jul. 22, 2009.
165 Z/Architecture • Principles of Operation SA 22/7832-01 International Business Machines Corporation, 2nd Edition, Oct. 2001.
166 Z/Series ''Input/Output Configuration Program users Guide for IYP 10CP, SB10-7029-03c. International Business Machines Corporation, Jun. 2003.
Classification aux États-Unis 710/62, 710/15, 710/8, 710/5, 710/2
Classification internationale G06F3/00, G06F13/00
Classification coopérative G06F3/0683, G06F3/061, G06F13/42, G06F3/0659
1 mars 2013 AS Assignment
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CANDELARIA, SUSAN K.;CARLSON, SCOTT M.;CASPER, DANIEL F.;AND OTHERS;SIGNING DATES FROM 20121009 TO 20130227;REEL/FRAME:029903/0374