Patent Grant
9483433
This invention relates, in general, to input/output processing, and in particular, to processing data associated with or generated by input/output processing.
Input/output (I/O) operations are used to transfer data between memory and I/O devices of an I/O processing system. Specifically, data is written from memory to one or more I/O devices, and data is read from one or more I/O devices to memory by executing I/O operations.
To facilitate processing of I/O operations, an I/O subsystem of the I/O processing system is employed. The I/O subsystem is coupled to main memory and the I/O devices of the I/O processing system and directs the flow of information between memory and the I/O devices. One example of an I/O subsystem is a channel subsystem. The channel subsystem uses channel paths as communications media. Each channel path includes a channel coupled to a control unit, the control unit being further coupled to one or more I/O devices.
The channel subsystem may employ channel command words (CCWs) to transfer data between the I/O devices and memory. A CCW specifies the command to be executed. For commands initiating certain I/O operations, the CCW designates the memory area associated with the operation, the action to be taken whenever a transfer to or from the area is completed, and other options.
During I/O processing, a list of CCWs is fetched from memory by a channel. The channel parses each command from the list of CCWs and forwards a number of the commands, each command in it's own entity, to a control unit coupled to the channel. The control unit then processes the commands. The channel tracks the state of each command and controls when the next set of commands are to be sent to the control unit for processing. The channel ensures that each command is sent to the control unit in it's own entity. Further, the channel infers certain information associated with processing the response from the control unit for each command.
The control unit may also send various messages to the channel, such as acknowledgement messages indicating whether a command has been executed, and status messages providing information regarding the status of an I/O device.
The channel may send commands to the control unit in the form of Information Units (IUs). Various exchanges and sequences occur between the control unit and the channel. For example, the channel may open an exchange with the control unit and send various commands (command data) to the control unit. In response, in addition to performing other functions, the control unit may respond to the channel on the same exchange, or open a new exchange and send a response thereon.
In addition, the control unit may send unsolicited data to the channel, such as a message indicating the status of an I/O device, to which the channel may respond accordingly, such as with an acknowledgement (“ACK”) message.
A condition may arise where a message sent from the channel arrives at the control unit at the same time that a message sent from the control unit arrives at the channel, or the messages otherwise cross paths in a logical path. In this condition, both the channel and control unit receive an unsolicited message in the absence of, or prior to, receiving a response to their respective messages. This condition may be referred to as a “frames passing” or “ships passing” situation.
For ships passing conditions occurring in channel subsysytems using a common link protocol, such as the Fibre Connectivity (FICON) protocol, the inbound (toward the channel) and outbound (away from the channel) exchanges are used to resolve the condition. However, in situations where the channel and control unit use different protocols, there is no way to efficiently discontinue an operation.
Ships passing rules utilized in one protocol or mode may not work with other protocols or modes. For example, a first protocol, such as FICON, may not work with a second link protocol. The second link protocol may not be amiable to the FICON behavior, and thus there may be no way for the channel to efficiently discontinue the second link protocol operation.
Accordingly, there is a need in the art for a method and system for resolving ships passing conditions in channel communications. There is also a need in the art for resolving ships passing conditions among disparate link protocols.
Embodiments of the invention include a computer program product for processing communication data in a ships passing condition, including a storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method. The method includes: obtaining a Transport Command Control Block (TCCB) from a location in memory specified by a Transport Command Control Block address of a Transport Control Word; opening a first exchange and sending, by a channel subsystem, the TCCB in the first exchange to a control unit, the TCCB comprising a first logical path value and a first device value; receiving, by the channel subsystem, an unsolicited first message in a second exchange from the control unit, the unsolicited first message comprising a second logical path value and a second device value, the unsolicited first message opening the second exchange, the second exchange being a different exchange than the first exchange; responsive to the receiving the unsolicited first message and the first exchange and second exchange being opened, determining that the first logical path value is equal to the second logical path value and the first device value is equal to the second device value; and based on the determination, sending, by the channel subsystem, a second message to the control unit in a third exchange, the second message comprising a status of the first message, the second message configured to open and close the third exchange.
Other embodiments include an apparatus for processing communication data in a ships passing condition, including a channel subsystem for communication with a control unit. The channel subsystem includes one or more channels for directing information flow between memory and one or more I/O devices via the control unit, and is configured to perform a method. The method includes: obtaining a Transport Command Control Block (TCCB) from a location in memory specified by a Transport Command Control Block address of a Transport Control Word; opening a first exchange and sending the TCCB in the first exchange to a control unit, the TCCB comprising a first logical path value and a first device value; receiving an unsolicited first message in a second exchange from the control unit, the unsolicited first message comprising a second logical path value and a second device value, the unsolicited first message opening the second exchange, the second exchange being a different exchange than the first exchange; responsive to the receiving the unsolicited first message and the first exchange and second exchange being opened, determining that the first logical path value is equal to the second logical path value and the first device value is equal to the second device value; and based on the determination, sending a second message to the control unit in a third exchange, the second message comprising a status of the first message, the second message configured to open and close the third exchange.
Further embodiments include a method of processing communication data in a ships passing condition. The method includes: obtaining a Transport Command Control Block (TCCB) from a location in memory specified by a Transport Command Control Block address of a Transport Control Word; opening a first exchange and sending, by a channel subsystem, the TCCB in the first exchange to a control unit, the TCCB comprising a first logical path value and a first device value; receiving, by the channel subsystem, an unsolicited first message in a second exchange from the control unit, the unsolicited first message comprising a second logical path value and a second device value, the unsolicited first message opening the second exchange, the second exchange being a different exchange than the first exchange; responsive to the receiving the unsolicited first message and the first exchange and second exchange being opened, determining that the first logical path value is equal to the second logical path value and the first device value is equal to the second device value; and based on the determination, sending, by the channel subsystem, a second message to the control unit in a third exchange, the second message comprising a status of the first message, the second message configured to open and close the third exchange.
Other embodiments include an article of manufacture including at least one computer usable medium having computer readable program code logic to processing communications between a control unit and a channel subsystem in an input/output processing system. The computer readable program code logic performs a method including: sending a command in a first mode from the channel subsystem to the control unit; receiving a message in a second mode from the control unit at the channel subsystem; determining whether the message is responsive to the command; and responsive to the message being not responsive to the command, sending a response to the message to the control unit.
Additional embodiments include an apparatus for processing communications in an input/output processing system. The apparatus includes a channel subsystem of a host computer system in communication with a control unit capable of commanding and determining status of an I/O device. The channel subsystem performs: sending a command in a first mode to the control unit; receiving a message in a second mode from the control unit; determining whether the message is responsive to the command; and responsive to the message being not responsive to the command, sending a response to the message in the second mode to the control unit.
Other additional embodiments include an apparatus for processing communications in an input/output processing system. The apparatus includes a control unit capable of commanding and determining status of an I/O device, the control unit in communication with a channel subsystem of a host computer system. The control unit performs: sending a message in a first mode to the channel subsystem; receiving a command in a second mode from the channel subsystem; determining whether the command is responsive to the message; and responsive to the command being not responsive to the message, determining whether to perform one of i) executing the command and ii) terminating the command.
Further embodiments include a method of processing communications between a control unit and a channel subsystem in an input/output processing system. The method includes: sending a message from the control unit to the channel subsystem; receiving a command from the channel subsystem at the control unit; determining whether the command is responsive to the message; and responsive to the command being not responsive to the message, determining whether to perform one of i) executing the command and ii) terminating the command.
Still further embodiments include a method of processing communications between a control unit and a channel subsystem in an input/output processing system. The method includes: sending a command in a first mode from the channel subsystem to the control unit; receiving a message in a second mode from the control unit at the channel subsystem; determining whether the message is responsive to the command; and responsive to the message being not responsive to the command, sending a response to the message to the control unit.
Other systems, methods, and/or articles of manufacture according to embodiments will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such additional systems, methods, and/or articles of manufacture be included within this description, be within the scope of the present invention, and be protected by the accompanying claims.
The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other objects, features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
The detailed description explains the preferred embodiments of the invention, together with advantages and features, by way of example with reference to the drawings.
Exemplary embodiments provide a system and method for processing data sent between a control unit and channel in a “ships passing” condition. The system allows for the control unit to determine whether to execute or terminate an operation in response to command data from the channel. In an exemplary embodiment, the system and method allow for processing messages sent between the channel and the control unit in a ships passing condition, where the protocol used by the channel is different than the protocol used by the control unit.
I/O processing is facilitated, in one example, by reducing communications between components of an I/O processing system used to perform the I/O processing. For instance, the number of exchanges and sequences between an I/O communications adapter, such as a channel, and a control unit is reduced. This is accomplished by sending a plurality of commands from the I/O communications adapter to the control unit as a single entity for execution by the control unit, and by the control unit sending the data resulting from the commands, if any, as a single entity.
The plurality of commands are included in a block, referred to herein as a transport command control block (TCCB), an address of which is specified in a transport control word (TCW). The TCW is sent from an operating system or other application to the I/O communications adapter, which in turn forwards the TCCB in a command message to the control unit for processing. The control unit processes each of the commands absent a tracking of status relative to those individual commands by the I/O communications adapter. The plurality of commands is also referred to as a channel program, which is parsed and executed on the control unit rather than the I/O communications adapter.
In an exemplary embodiment, the control unit generates a response message including status and extended status information in response to executing the channel program. The control unit may also generate a response message without executing the channel program under a limited number of communication scenarios, e.g., to inform the I/O communications adapter that the channel program will not be executed. The control unit 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 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. The I/O communications adapter parses the response message, extracting the status and extended status information, and performs further calculations using the extracted information, such as determining an extended measurement word.
One example of an I/O processing system incorporating and using one or more aspects of the present invention is described with reference to
Main memory 102 stores data and programs, which can be input from I/O devices 112. For example, the main memory 102 may include one or more operating systems (OSs) 103 that are executed by one or more of the CPUs 104. For example, one CPU 104 can execute a Linux® operating system 103 and a z/OS® operating system 103 as different virtual machine instances. The main memory 102 is directly addressable and provides for high-speed processing of data by the CPUs 104 and the channel subsystem 108.
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 storage control element 106 via a connection 114, such as a bidirectional or unidirectional bus.
Storage control element 106 is coupled to the main memory 102 via a connection 116, such as a bus; to CPUs 104 via connection 114; and to channel subsystem 108 via a connection 118. Storage control element 106 controls, for example, queuing and execution of requests made by CPU 104 and channel subsystem 108.
In an exemplary embodiment, channel subsystem 108 provides a communication interface between host system 101 and control units 110. Channel subsystem 108 is coupled to storage control element 106, as described above, and to each of the control units 110 via a connection 120, such as a serial link. Connection 120 may be implemented as an optical link, employing single-mode or multi-mode waveguides in a Fibre Channel fabric. Channel subsystem 108 directs the flow of information between I/O devices 112 and main memory 102. It relieves the CPUs 104 of the task of communicating directly with the I/O devices 112 and permits data processing to proceed concurrently with I/O processing. The channel subsystem 108 uses one or more channel paths 122 as the communication links in managing the flow of information to or from I/O devices 112. As a part of the I/O processing, channel subsystem 108 also performs the path-management functions of testing for channel path availability, selecting an available channel path 122 and initiating execution of the operation with the I/O devices 112.
Each channel path 122 includes a channel 124 (channels 124 are located within the channel subsystem 108, in one example, as shown in
Also located within channel subsystem 108 are subchannels (not shown). One subchannel is provided for and dedicated to each I/O device 112 accessible to a program through the channel subsystem 108. A subchannel (e.g., a data structure, such as a table) provides the logical appearance of a device to the program. Each subchannel provides information concerning the associated I/O device 112 and its attachment to channel subsystem 108. The subchannel also provides information concerning I/O operations and other functions involving the associated I/O device 112. The subchannel is the means by which channel subsystem 108 provides information about associated I/O devices 112 to CPUs 104, which obtain this information by executing I/O instructions.
Channel subsystem 108 is coupled to one or more control units 110. Each control unit 110 provides logic to operate and control one or more I/O devices 112 and adapts, through the use of common facilities, the characteristics of each I/O device 112 to the link interface provided by the channel 124. The common facilities provide for the execution of I/O operations, indications concerning the status of the I/O device 112 and control unit 110, control of the timing of data transfers over the channel path 122 and certain levels of I/O device 112 control.
Each control unit 110 is attached via a connection 126 (e.g., a bus) to one or more I/O devices 112. I/O devices 112 receive information or store information in main memory 102 and/or other memory. Examples of I/O devices 112 include card readers and punches, magnetic tape units, direct access storage devices, displays, keyboards, printers, pointing devices, teleprocessing devices, communication controllers and sensor based equipment, to name a few.
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-05, 6th Edition, April 2007; U.S. Pat. No. 5,461,721 entitled “System For Transferring Data Between I/O Devices And Main Or Expanded Storage Under Dynamic Control Of Independent Indirect Address Words (IDAWS),” Cormier et al., issued Oct. 24, 1995; and U.S. Pat. No. 5,526,484 entitled “Method And System For Pipelining The Processing Of Channel Command Words,” Casper et al., issued Jun. 11, 1996, each of which is hereby incorporated herein by reference in its entirety. 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.
In one embodiment, to transfer data between I/O devices 112 and memory 102, channel command words (CCWs) are used. A CCW specifies the command to be executed, and includes other fields to control processing. One example of a CCW is described with reference to
One or more CCWs arranged for sequential execution form a channel program, also referred to herein as a CCW channel program. The CCW channel program is set up by, for instance, an operating system, or other software. The software sets up the CCWs and obtains the addresses of memory assigned to the channel program. An example of a CCW channel program is described with reference to
The processing of a CCW channel program is described with reference to
Referring to
The control unit 302 opens an exchange 308 with the channel 300, in response to the open exchange of the channel 300. This can occur before or after locate command 305 and/or read command 306. Along with the open exchange, a response (CMR) is forwarded to the channel 300. The CMR provides an indication to the channel 300 that the control unit 302 is active and operating.
The control unit 302 sends the requested data 310 to the channel 300. Additionally, the control unit 302 provides the status to the channel 300 and closes the exchange 312. In response thereto, the channel 300 stores the data, examines the status and closes the exchange 314, which indicates to the control unit 302 that the status has been received.
The processing of the above CCW channel program to read 4 k of data requires two exchanges to be opened and closed and seven sequences. The total number of exchanges and sequences between the channel and control unit is reduced through collapsing multiple commands of the channel program into a TCCB. The channel, e.g., channel 124 of
One example of a channel program to read 4 k of data, as in
The processing of a TCW channel program is described with reference to
An example of a link protocol used for processing the TCW channel program is a “Transport Mode”, using the FCP link protocol, that allows the collapse of multiple chained CCWs into one TCCB inside a single Transport Command information unit (IU). This IU may send the entire channel program to the control unit in one sequence.
Referring to
In a further example, to write 4 k of customer data, the channel 500 uses the FCP link protocol phases, as follows:
1. Transfer a TCCB in the FCP_CMND IU.
2. Transfer the IU of data, and sequence initiative to the control unit 502.
3. Final status is sent in a FCP status frame that has a bit active in, for instance, byte 10 or 11 of the FCP_RSP IU Payload. The FCP_RSP_INFO field or sense field is used to transport FICON ending status along with additional status information, including parameters that support the calculation of extended measurement words and notify the channel 500 of the maximum number of open exchanges supported by the control unit 502.
By executing the TCW channel program of
The number of exchanges and sequences remain the same for a TCW channel program, even if additional commands are added to the program. Compare, for example, the communications of the CCW channel program of
As depicted in
Turning now to
The CU control logic 802 can access and control other elements within the control unit 110, such as CU timers 806 and CU registers 808. The CU timers 806 may include multiple timer functions to track how much time a sequence of I/O operations takes to complete. The CU timers 806 may further include one or more countdown timers to monitor and abort I/O operations and commands that do not complete within a predetermined period. The CU registers 808 can include fixed values that provide configuration and status information, as well as dynamic status information that is updated as commands are executed by the CU control logic 802. The control unit 110 may further include other buffer or memory elements (not depicted) to store multiple messages or status information associated with communications between the channel 124 and the I/O device 112.
The channel 124 in the channel subsystem 108 includes multiple elements to support communication with the control unit 110. For example, the channel 124 may include CHN control logic 810 that interfaces with CHN subsystem timers 812 and CHN subsystem registers 814. In an exemplary embodiment, the CHN control logic 810 controls communication between the channel subsystem 108 and the control unit 110. The CHN control logic 810 may directly interface to the CU control logic 802 via the connection 120 to send commands and receive responses, such as transport command and response IUs. Alternatively, messaging interfaces and/or buffers (not depicted) can be placed between the CHN control logic 810 and the CU control logic 802. The CHN subsystem timers 812 may include multiple timer functions to track how much time a sequence of I/O operations takes to complete, in addition to the time tracked by the control unit 110. The CHN subsystem timers 812 may further include one or more countdown timers to monitor and abort command sequences that do not complete within a predetermined period. The CHN subsystem registers 814 can include fixed values that provide configuration and status information, as well as dynamic status information, updated as commands are transported and responses are received.
In an exemplary embodiment, the CCW channel program is implemented using a protocol that includes Channel Command Words, for example, a Fibre Connectivity (FICON) protocol. Links operating under this protocol may be referred to as being in a “Command Mode”.
In an exemplary embodiment, the TCW channel program is implemented using a protocol to execute Transport Control Words, for example, the transport mode protocol.
In some exemplary embodiments, the control unit 110 and the channel 124 may operate in different modes, i.e., use different protocols. For example, the channel 124 may operate in transport mode which utilizes the FCP link protocol, and the control unit 110 may operate in command mode that utilizes the FICON protocol.
In a ships passing condition, the control unit 110 and the channel 124 each send a message at approximately the same time, or otherwise send messages that cross paths in a logical path. In such a condition, the channel 124 sends a message (e.g., a command message) to the control unit 110 and receives an unrelated or non-responsive message in return. Similarly, the control unit 110 sends a message (e.g., a status message) to the channel 124 and receives an unrelated or non-responsive message in return.
In an exemplary embodiment, when the channel 124 sends a command message to the control unit 110, and receives an unsolicited message from the control unit 110 that is not responsive to the command message, the channel 124 determines or recognizes that a ships passing condition has occurred. The channel 124 sends a response message to the control unit 110 in response to the message from the control unit being not responsive to the command. In one exemplary embodiment, the response message from the channel 124 indicates that the message has not been accepted.
In this exemplary embodiment, the control unit 110 sends the unsolicited message, and thereafter receives the command message from the channel 124 that is not responsive to the unsolicited message. The control unit thus determines that the command is not responsive to the unsolicited message, and in response determines whether to execute or terminate the command. In another exemplary embodiment, the control unit 110 may wait for a response from the channel 124 that the message was not accepted. If the control unit 110 receives the response, it determines whether to execute the command or terminate the command.
In another exemplary embodiment, after sending the command message in the first mode (e.g., transport mode protocol) to the control unit 110 and receiving a non-responsive message in the second mode (e.g., FICON), the channel 124 sends a message to the control unit 110 in the second mode, in response to the non-responsive message. Upon receiving the response message in the second mode, the control unit 110 may then determine whether to terminate or execute the command message, and send a response message in the first mode.
In an exemplary embodiment, upon receiving a non-responsive message from the control unit 110, such as a status message, the channel 124 stacks the status received. The channel 124 may enable a timer to ensure that the protocol for stacking the status completes in a timely fashion. After the status is stacked, and optionally after the original transport mode operation the channel 124 started completes, the channel 124 may make a request to the control unit 110 for possible stacked status.
In an exemplary embodiment, the channel 124 stacks the status by sending a “stack status” message to the control unit 110 in response to the status message. The stack status message indicates to the control unit 110 that the status message is not accepted. The control unit 110 may then hold the device status information (status flags, status byte, and status parameter) and associated supplemental status, if any, until the status is requested by the channel 124, e.g., via a request-status message, or present the status as the response to the command message. For brevity, a control message indicating stack status is referred to as a stack-status information unit (IU). A stack-status IU may be sent as the first and last sequence of an exchange if it is sent in response to the status message from the control unit 110. The control unit 110 may indicate to the channel 124 that it recognized the stack-status IU by sending a device-level acknowledgement (DACK) IU. The channel 124 may consider the stack-status function to have been performed when it receives a DACK IU in response to the stack-status IU.
In an exemplary embodiment, upon receiving a response to the status message (e.g., a stack-status IU), the control unit 110 may determine whether to terminate the command message or execute the command message. In another exemplary embodiment, if the control unit 110 executes the command, it sends appropriate indications and status to the channel 124 via a response message. If the control unit 110 terminates the command, it sends the original status (included in the original status message) to the channel 124 via the response message. In yet another exemplary embodiment, the control unit 110 may send the response message in the transport mode, as a “Transport Response IU”.
In an exemplary embodiment, the control unit 110 determines whether to execute or terminate the command based on the type of status the control unit 110 has pending pertaining to the device. For example, if the status pertains to a new state of the device, then the control unit 110 may terminate the command and return that status in response to the Transport Command IU. In another example, if the status is some low priority status that does not pertain to the current operational state of the device, then the control unit 110 may execute the command message.
In an exemplary embodiment, the channel 124 sends the command message in the transport mode, and the control unit 110 sends the status message in the command mode. In stacking the status received, the channel 124 may send the stack status message in the command mode, and await a command mode acknowledgement from the control unit 110. In another exemplary embodiment, the channel 124 may send the stack status message in transport mode and the control unit 110 then returns the response message in transport mode.
Exemplary embodiments of the processing of messages and/or programs in a ships passing situation are described with reference to
In the examples described herein, the channel 905, which is operating in transport mode, sends a Transport Command IU that contains the TCCB, using the transport mode protocol, to the control unit. The Transport Command IU may also be referred to as a “TCCB IU”. The control unit 910, which is operating in command mode, sends an unsolicited status IU using the FICON protocol, independently of the command IU. The protocols used, and the information units sent from the channel 905 and control unit 910, are exemplary and provided for illustration purposes. Any suitable messages or protocols may be used in a selected I/O operation.
The unsolicited IU sent by the control unit may take the form of an Asynchronous Device Status IU using the FICON protocol, which is sent to the channel 905 over the same logical path and for the same device. This unsolicited IU is also referred to as a “FICON 85 STATUS” IU.
In these examples, both the channel 905 and the control unit 910 recognize that the TCCB and FICON 85 STATUS IUs have crossed, and thus both the channel 905 and control unit 910 have received messages that are not responsive to their respective messages. In response to this ships passing condition, the channel 905 stacks the status received in the FICON 85 STATUS IU by generating a “Stack Status” IU in the FICON protocol, also referred to as “FICON Stack”.
Examples of embodiments of the method described herein are further described below, with reference to
In the following example, a procedure for processing data in a ships passing condition is illustrated with reference to
1. The control unit 910 opens an exchange 902 and sends the device status in the FICON 85 STATUS IU 911 to the channel 905 on the exchange 902. The control unit 910 may initiate a status timer set at a period of, for example, 1.5 seconds, for receiving an acknowledgement or other response to the FICON 85 STATUS IU 911 from the channel 905.
2. The channel 905 opens an exchange 901 and sends the TCCB IU 912 to the control unit 910 on the exchange 901. The channel 905 may also transfer sequence initiative on the exchange 901 to the control unit 910. The channel 905 may further start a timer, such as a 2 second timer, for receiving a status response IU from the control unit 910. In an exemplary embodiment, the timer period set by the channel 905 is between approximately one and twenty seconds.
3. The channel 905 receives the unsolicited FICON 85 STATUS IU 911 on exchange 902, by which it recognizes that the logical path and device associated with the control unit 910 has AS=1. AS=1 indicates that the “address specific” field in the FICON 85 STATUS IU 911 is valid. A ships passing mode is recognized when the device address field and the logical path in the FICON 85 STATUS IU 911 is equal to the device address field and logical path in the TCCB IU 912 that was sent to the control unit 910.
4. The channel 905 opens and closes an exchange 903 to the control unit 910, to stack the status in the FICON 85 STATUS IU 911 received from the control unit 910 on the exchange 902 and to send a stack status IU 913 on the exchange 903. The channel 905 may start a stack status timer (e.g., two seconds) for receipt of a device level acknowledgement (DACK) IU from the control unit 910. In an exemplary embodiment, the stack status IU 913 is sent to the control unit 910 in FICON format (referred to as “FICON Stack IU 913”).
5. The control unit 910 receives the TCCB IU 912 on exchange 901, by which it recognizes that the logical path and device associated with the channel 905 is in ships passing mode because the TCCB IU 912 is specific to the device address of the FICON 85 STATUS IU 911 that was sent to the channel 905. The control unit 910 waits up to the status timer period set for a response to the FICON 85 STATUS IU 911.
6. The control unit 910 receives the FICON Stack IU 913 on exchange 903 and completes the FICON handshake by sending a response 914, such as a FICON device acknowledgement (“FICON DACK IU 914”). The control unit 910 may also close exchange 902.
7. The control unit 910 has the option, in response to the TCCB IU 912, to i) withdraw the device status sent in the FICON 85 STATUS IU 911 and execute the commands in the TCCB IU 912 received from the channel 905, or ii) send the device status to the channel 905.
In an exemplary embodiment, if the device status is withdrawn, the control unit executes the commands in the TCCB IU 912, and returns a response IU, such as a Status Response IU (RSP IU) IU 915, on the exchange 901. In another exemplary embodiment, if the device status is not withdrawn, the control unit 910 sends the device status in the Status Response IU 915 on exchange 901. The control unit 910 may transfer sequence initiative to the channel 905 if confirmation is requested, or close exchange 901 as appropriate. The device status may be sent in an appropriate field in a response IU (e.g. RSP IU 915), such as a “Device Status” field. In an exemplary embodiment, a “device busy” bit may also be sent along with the device status. In the above embodiments, the control unit 910, which originally sent the status via the FICON protocol, responds to the TCCB IU 912 via the transport mode protocol.
8. If confirmation of the RSP IU 915 is requested by the control unit 910, the control unit 910 may start a confirmation timer. The channel 905 closes exchange 901 with a Status Confirm IU 916 (i.e. “Confirm IU 916”) in response to the RSP IU 915.
9. The channel 905 may present the device status, received from the RSP IU 915, to an I/O program or other location. The channel may also store the channel (or subchannel) status, to alert the software, for example, that the subchannel is primary, secondary and maybe alert status pending.
10. In an exemplary embodiment, the channel 905 may request the possible stacked status from the control unit 910, or otherwise request pending status, e.g., via a request-status IU.
In the following example, a procedure for processing data in a ships passing condition is illustrated with reference to
1. The control unit 910 sends the FICON 85 STATUS IU 911 to the channel 905, the channel 905 sends the TCCB IU 912 to the control unit 910, and the channel 905 recognizes the ships passing mode and stacks the device status, similar to phases 1-4 of Example 1.
2. The control unit 910 receives the FICON Stack IU 913 on the exchange 903 and completes the FICON handshake by sending a response 914, such as the FICON DACK IU 914. The control unit 910 may also close exchange 902.
3. If the channel 905 does not receive a status response IU to the TCCB IU within the status response IU timer period on the exchange 901, i.e., it times out, the channel 905 opens the exchange 904 and sends a request thereon to the control unit 910 to determine the status of the exchange 901, transfers initiative, and starts a request timer (e.g., one second). An example of such a request is an ELS (Extended Link Service) Read Exchange Concise (REC) IU 917.
The REC IU allows the channel 905 to determine the status of an exchange. The channel 905 may send the REC IU 917 to the control unit 910 to determine if the control unit 910 has received the TCCB IU 912 that opened the exchange 901. If the response the channel 905 receives indicates that the control unit 910 knows about the exchange, the channel 905 may then send a new REC IU periodically until an I/O operation is complete.
4. The channel 905 receives an REC response IU 918 from the control unit 910 that closes the exchange, and that informs the channel 905 that the control unit 910 has not received exchange 901. If the channel 905 does not receive the REC response IU 918 (e.g., because the REC or the Response to REC was lost) within the channel timer duration, the channel 905 aborts the exchange 904 (by performing abort sequence 919) and continues.
5. The channel 905 may then wait a selected duration (e.g., 100 ms), and thereafter perform abort sequence 920 to abort exchange 901, and stores the channel (or subchannel) status to alert the software, for example, that the subchannel is primary, secondary and alert status pending with an interface control check (IFCC).
6. In an exemplary embodiment, the channel 905 may request the possible stacked status from the control unit 910, or otherwise request pending status, e.g., via a request-status IU.
In the following example, a procedure for processing data in a ships passing condition is illustrated with reference to
1. The control unit 910 sends the FICON 85 STATUS IU 911 to the channel 905, and the channel 905 sends the TCCB IU 912 to the control unit 910, similar to phases 1-2 of Example 1.
2. If the FICON 85 STATUS IU 911 is lost, the channel 905 does not see a ships passing condition, and in turn, does not send a FICON Stack IU 913 to the control unit 910. The control unit status timer times out, and in turn, the control unit 910 aborts the exchanges 901 and 902 via abort sequences 921 and 922, respectively.
3. The channel 905 detects that the exchange 901 is aborted, and stores the channel (or subchannel) status to alert the software, for example, that the subchannel is primary, secondary and alert status pending with an interface control check (IFCC).
4. The control unit 910 may re-send the unsolicited FICON 85 STATUS IU 911 on the current logical path or on a different path.
In the following example, a procedure for processing data in a ships passing condition is illustrated with reference to
1. The control unit 910 sends the FICON 85 STATUS IU 911 to the channel 905, the channel 905 sends the TCCB IU 912 to the control unit 910, recognizes the ships passing mode and stacks the status. The control unit 910 receives the TCCB IU 912, recognizes the ships passing mode and waits for a response to the FICON 85 STATUS IU 911. This phase is similar to the procedure performed in phases 1-5 of Example 1.
2. If the FICON Stack IU 913 is lost, the control unit status timer times out, and the control unit 910 aborts exchanges 901 and 902 via abort sequences 923 and 924, respectively.
3. The channel 905 detects that exchanges 901 and 902 are aborted, and stores the channel (or subchannel) to alert the software, for example, that the subchannel is primary, secondary and alert status pending with an interface control check (IFCC).
4. The control unit 910 may re-send the unsolicited FICON 85 STATUS IU 911 on the current logical path or on a different path.
In the following example, a procedure for processing data in a ships passing condition is illustrated with reference to
1. The control unit 910 sends the FICON 85 STATUS IU 911 to the channel 905, and the channel 905 sends the TCCB IU 912 to the control unit 910. The channel 905 recognizes the ships passing mode and stacks the status. The control unit 910 receives the TCCB IU 912, recognizes the ships passing mode and waits for a response to the FICON 85 STATUS IU 911. This phase is similar to the procedure performed in phases 1-5 of Example 1.
2. The control unit 910 receives the FICON Stack IU 913 on the exchange 903 and completes the FICON handshake by sending the FICON DACK IU 914 to the channel 905. The control unit 910 may close exchange 902.
3. If the FICON DACK IU 914 is lost, the channel's stack status timer times out on the exchange 902 waiting for the FICON DACK IU 914. The channel 905 aborts both exchange 901 and exchange 902 via abort sequences 925 and 926, respectively.
4. Alternatively, if the control unit 910 sends the Status Response IU 915 on the exchange 901 with confirmation requested, the control unit 910 may also time out (i.e., the confirmation timer times out). The control unit may then abort the exchange 901, via abort sequence 927, after sending the Status Response IU 915.
5. The control unit 910 may re-send the unsolicited FICON 85 STATUS IU 911 on the current path or on a different path in the same logical path group.
In the following example, a procedure for processing data in a ships passing condition is illustrated with reference to
1. The control unit 910 sends the FICON 85 STATUS IU 911 to the channel 905, the channel 905 sends the TCCB IU 912 to the control unit 910, recognizes the ships passing mode, stacks the status, and sends the FICON Stack IU 913 to the control unit 910. The control unit 910 receives the TCCB IU 912, recognizes the ships passing mode, and sends the FICON DACK IU 914 to the channel 905. The control unit 910 sends the RSP IU 915 to the channel 905 on Exchange 901. This phase is similar to the procedure performed in phases 1-7 of Example 1.
2. If the RSP IU 915 sent in response to the TCCB IU 912 is lost, the channel 905 does not receive the RSP IU 915. The channel 905 times out (i.e., the status response IU timer times out) waiting for the RSP IU 915. In response, the channel 905 opens the exchange 904 and sends the ELS REC IU 917 for the exchange 901 to the control unit and starts a (e.g., 1 second) request timer.
3. The control unit 910 sends a response, i.e., a REC response 918, to the channel 905 that closes the exchange 904, and that informs the channel 905 that the control unit 910 does not have the exchange 901. This only occurs if the control unit 910 did not ask for a confirm to the RSP IU 915 and closed the exchange 901 when it sent the status RSP IU 915 to the channel 905. If the control unit requests a confirm on the RSP IU 915 then the control unit leaves the exchange 901 open and transfers transfer sequence initiative to the channel 905.
In one exemplary embodiment, the control unit 910 may request a confirm to the RSP IU 915 if the command operation may be retried. For example, a read or a write to a direct access storage device (DASD) can be retried and the end result is the same as if the original operation was successful. In this case, the control unit 910 may have completed the command operation when the status response IU 915 is lost and the control unit did not ask for the status to be confirmed.
If the command operation cannot be retried, then the control unit 910 handles this by asking for a confirm to the status response IU 915. In this case, if the control unit 910 times out waiting for the confirm, then the control unit may resend the status to the channel 905 for that device and will not accept a new operation for that device until the status has been successfully sent to the channel 905.
4. The channel may then wait a selected duration (e.g., 100 ms), abort the exchange 901 via abort sequence 928, and store the channel (or subchannel) status to alert the software, for example, that the subchannel is primary, secondary and alert status pending with an interface control check (IFCC).
5. In an exemplary embodiment, the channel 905 may request the possible stacked status from the control unit 910, or otherwise request pending status, e.g., via a request-status IU.
In the following example, a procedure for processing data in a ships passing condition is illustrated with reference to
1. The control unit 910 sends the FICON 85 STATUS IU 911 to the channel 905, the channel 905 sends the TCCB IU 912 to the control unit 910, recognizes the ships passing mode, stacks the status, and sends the FICON Stack IU 913 to the control unit 910. The control unit 910 receives the TCCB IU 912, recognizes the ships passing mode, and sends the FICON DACK IU 914 to the channel 905. The control unit 910 sends the RSP IU 915 to the channel 905 on the exchange 901. This phase is similar to the procedure performed in phases 1-7 of Example 1.
2. If the RSP IU 915 is sent by the control unit 910, and confirmation is required, the channel 905 sends the Status Confirm IU 916 in exchange 901 in response to the RSP IU 915. If the control unit 910 does not receive the Status Confirm IU 916, then the control unit 910 times out and aborts exchange 901 via abort sequence 929.
3. The control unit 910 may then re-send the unsolicited FICON 85 STATUS IU 911 to the channel 905. FICON 85 STATUS IU 911 may be re-sent on exchange 904. In this example, the unsolicited FICON 85 STATUS IU 911 is sent to the channel 905 twice.
The naming and numbering conventions described in the above examples are exemplary and provided to illustrate the method described herein. The naming and number convention provided is arbitrarily chosen, and is provided for explanation only.
Furthermore, the protocols and specific messages described in the above examples are exemplary. Any suitable I/O protocols and associated messages may be processed as described herein.
One or more aspects of the present invention can be included in an article of manufacture (e.g., one or more computer program products) having, for instance, computer usable media. The media has therein, for instance, computer readable program code means or logic (e.g., instructions, code, commands, etc.) to provide and facilitate the capabilities of the present invention. The article of manufacture can be included as a part of a computer system or provided separately.
One example of an article of manufacture or a computer program product incorporating one or more aspects of the present invention is described with reference to
Technical effects of exemplary embodiments include the ability of I/O processing systems to resolve ships passing conditions among I/O components using disparate protocols. In addition, the control unit may determine independently of the channel whether to execute a command in a ships passing condition. The systems and methods described herein provide numerous advantages, in that they provide an efficient way to process data in a ships passing condition, and further provide for processing messages and data sent from disparate protocols.
For example, ships passing rules utilized in one protocol or mode may not work with other protocols or modes. For example, a protocol using CCWs (e.g., FICON), may not work with other protocols, such as protocols using TCWs (e.g., transport mode). The transport mode link protocol is not amiable to the FICON behavior because once a transport mode link operation is started by a channel (e.g., a transport mode command is sent on an outbound exchange to the control unit), there is no way for the channel to efficiently discontinue the transport mode link operation. The control unit cannot use the inbound FICON status exchange opened by the control unit to complete or terminate the transport mode link operation. The channel and control unit must stay in sync with each other while sorting out the two open exchanges, even if an IU is lost on an exchange. The systems and methods described herein allow the control unit to complete or terminate the operation, thus overcoming the disadvantages described above. In addition, using the protocols described herein, the channel and control unit need not stay in sync with each other while resolving the open exchanges involved in the ships passing condition.
As described above, exemplary embodiments can be embodied in the form of computer-implemented processes and apparatuses for practicing those processes. In some exemplary embodiments, the invention is embodied in computer program code executed by one or more network elements. Exemplary embodiments include the computer program product 1600 as depicted in
While the invention has been described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims. Moreover, the use of the terms first, second, etc. do not denote any order or importance, but rather the terms first, second, etc. are used to distinguish one element from another. Furthermore, the use of the terms a, an, etc. do not denote a limitation of quantity, but rather denote the presence of at least one of the referenced item.
The present application is a continuation of U.S. patent application Ser. No. 12/031,182 entitled “PROCESSING COMMUNICATION DATA IN A SHIPS PASSING CONDITION”, filed Feb. 14, 2008, the entirety of which is specifically incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3693161 | Price et al. | Sep 1972 | A |
| 3943283 | Caragliano et al. | Mar 1976 | A |
| 4004277 | Gavril | Jan 1977 | A |
| 4080649 | Calle et al. | Mar 1978 | A |
| 4207609 | Luiz et al. | Jun 1980 | A |
| 4374415 | Cormier et al. | Feb 1983 | A |
| 4380046 | Frosch et al. | Apr 1983 | A |
| 4414644 | Tayler | Nov 1983 | A |
| 4455605 | Cormier et al. | Jun 1984 | A |
| 4497022 | Cormier et al. | Jan 1985 | A |
| 4564903 | Guyette et al. | Jan 1986 | A |
| 4760518 | Potash et al. | Jul 1988 | A |
| 4779188 | Gum et al. | Oct 1988 | A |
| 4837677 | Burrus, Jr. et al. | Jun 1989 | A |
| 4843541 | Bean et al. | Jun 1989 | A |
| 4866609 | Calta et al. | Sep 1989 | A |
| 4870566 | Cooper et al. | Sep 1989 | A |
| 5016160 | Lambeth et al. | May 1991 | A |
| 5031091 | Wakatsuki et al. | Jul 1991 | A |
| 5040108 | Kanazawa | Aug 1991 | A |
| 5170472 | Cwiakala et al. | Dec 1992 | A |
| 5185736 | Tyrrell et al. | Feb 1993 | A |
| 5237325 | Klein et al. | Aug 1993 | A |
| 5265240 | Galbraith et al. | Nov 1993 | A |
| 5297262 | Cox et al. | Mar 1994 | A |
| 5301321 | Bell et al. | Apr 1994 | A |
| 5301323 | Maeurer et al. | Apr 1994 | A |
| 5317739 | Elko et al. | May 1994 | A |
| 5325492 | Bonevento et al. | Jun 1994 | A |
| 5386512 | Crisman et al. | Jan 1995 | A |
| 5388219 | Chan et al. | Feb 1995 | A |
| 5410727 | Jaffe et al. | Apr 1995 | A |
| 5414851 | Brice, Jr. et al. | May 1995 | A |
| 5434980 | Casper et al. | Jul 1995 | A |
| 5440729 | Kimura et al. | Aug 1995 | A |
| 5452455 | Brown et al. | Sep 1995 | A |
| 5461721 | Cormier et al. | Oct 1995 | A |
| 5463736 | Elko et al. | Oct 1995 | A |
| 5465359 | Allen et al. | Nov 1995 | A |
| 5500942 | Eickemeyer et al. | Mar 1996 | A |
| 5517670 | Allen et al. | May 1996 | A |
| 5526484 | Casper et al. | Jun 1996 | A |
| 5528755 | Beardsley et al. | Jun 1996 | A |
| 5539918 | Allen et al. | Jul 1996 | A |
| 5546533 | Koyama | Aug 1996 | A |
| 5548791 | Casper et al. | Aug 1996 | A |
| 5561809 | Elko et al. | Oct 1996 | A |
| 5564040 | Kubala | Oct 1996 | A |
| 5568648 | Coscarella et al. | Oct 1996 | A |
| 5584039 | Johnson et al. | Dec 1996 | A |
| 5600793 | Nord | Feb 1997 | A |
| 5600805 | Fredericks et al. | Feb 1997 | A |
| 5608898 | Turpin et al. | Mar 1997 | A |
| 5613163 | Marron et al. | Mar 1997 | A |
| 5640600 | Satoh et al. | Jun 1997 | A |
| 5640603 | Meritt et al. | Jun 1997 | A |
| 5644712 | Coscarella et al. | Jul 1997 | A |
| 5671441 | Glassen et al. | Sep 1997 | A |
| 5680580 | Beardsley et al. | Oct 1997 | A |
| 5758190 | Johnson et al. | May 1998 | A |
| 5768620 | Johnson et al. | Jun 1998 | A |
| 5787071 | Basso et al. | Jul 1998 | A |
| 5793983 | Albert et al. | Aug 1998 | A |
| 5805808 | Hansani et al. | Sep 1998 | A |
| 5812877 | Young | Sep 1998 | A |
| 5831985 | Sandorfi | Nov 1998 | A |
| 5845146 | Onodera | Dec 1998 | A |
| 5860022 | Kondou et al. | Jan 1999 | A |
| 5894583 | Johnson et al. | Apr 1999 | A |
| 5901327 | Ofek | May 1999 | A |
| 5907684 | Halma et al. | May 1999 | A |
| 5918028 | Silverthorn et al. | Jun 1999 | A |
| 5996026 | Onodera et al. | Nov 1999 | A |
| 6070070 | Ladue | May 2000 | A |
| 6125399 | Hamilton | Sep 2000 | A |
| 6125411 | Sato | Sep 2000 | A |
| 6128311 | Poulis et al. | Oct 2000 | A |
| 6195330 | Sawey et al. | Feb 2001 | B1 |
| 6202095 | Beardsley et al. | Mar 2001 | B1 |
| 6230218 | Casper | May 2001 | B1 |
| 6249787 | Schleimer et al. | Jun 2001 | B1 |
| 6263380 | Tsuboi et al. | Jul 2001 | B1 |
| 6338105 | Niizuma et al. | Jan 2002 | B1 |
| 6343335 | Dahman et al. | Jan 2002 | B1 |
| 6347334 | Fredericks et al. | Feb 2002 | B1 |
| 6351779 | Berg et al. | Feb 2002 | B1 |
| 6353612 | Zhu et al. | Mar 2002 | B1 |
| 6401223 | Depenning | Jun 2002 | B1 |
| 6460087 | Saito et al. | Oct 2002 | B1 |
| 6466590 | Park et al. | Oct 2002 | B1 |
| 6484217 | Fuente et al. | Nov 2002 | B1 |
| 6546435 | Yoshimura et al. | Apr 2003 | B1 |
| 6584511 | Marsh, III et al. | Jun 2003 | B1 |
| 6594785 | Gilbertson et al. | Jul 2003 | B1 |
| 6609161 | Young | Aug 2003 | B1 |
| 6609165 | Frazier | Aug 2003 | B1 |
| 6647016 | Isoda et al. | Nov 2003 | B1 |
| 6651125 | Maergner et al. | Nov 2003 | B2 |
| 6654954 | Hicks | Nov 2003 | B1 |
| 6658603 | Ward | Dec 2003 | B1 |
| 6687766 | Casper et al. | Feb 2004 | B1 |
| 6693880 | Gregg et al. | Feb 2004 | B2 |
| 6694390 | Bogin et al. | Feb 2004 | B1 |
| 6718419 | Delvaux | Apr 2004 | B1 |
| 6738647 | Link, II | May 2004 | B1 |
| 6751680 | Langerman et al. | Jun 2004 | B2 |
| 6751683 | Johnson et al. | Jun 2004 | B1 |
| 6769009 | Reisman | Jul 2004 | B1 |
| 6772207 | Dorn et al. | Aug 2004 | B1 |
| 6826661 | Umbehocker et al. | Nov 2004 | B2 |
| 6839773 | Vishlitzky et al. | Jan 2005 | B2 |
| 6862322 | Ewen et al. | Mar 2005 | B1 |
| 6898202 | Gallagher et al. | May 2005 | B2 |
| 6915378 | Roberti | Jul 2005 | B2 |
| 6922548 | Moore et al. | Jul 2005 | B1 |
| 6950888 | Rooney et al. | Sep 2005 | B1 |
| 6963940 | Glassen et al. | Nov 2005 | B1 |
| 7000036 | Carlson et al. | Feb 2006 | B2 |
| 7003700 | Elko et al. | Feb 2006 | B2 |
| 7020810 | Holman | Mar 2006 | B2 |
| 7035540 | Finan et al. | Apr 2006 | B2 |
| 7058735 | Spencer | Jun 2006 | B2 |
| 7085860 | Dugan et al. | Aug 2006 | B2 |
| 7100096 | Webb, Jr. et al. | Aug 2006 | B2 |
| 7111130 | Blake et al. | Sep 2006 | B2 |
| 7120728 | Krakirian et al. | Oct 2006 | B2 |
| 7124207 | Lee et al. | Oct 2006 | B1 |
| 7133988 | Fujibayashi | Nov 2006 | B2 |
| 7142520 | Haverinen et al. | Nov 2006 | B1 |
| 7149823 | Miller et al. | Dec 2006 | B2 |
| 7155569 | Johnson et al. | Dec 2006 | B2 |
| 7164425 | Kwak et al. | Jan 2007 | B2 |
| 7174274 | Carlson et al. | Feb 2007 | B2 |
| 7202801 | Chou | Apr 2007 | B2 |
| 7266296 | Ovadia et al. | Sep 2007 | B2 |
| 7277387 | Sanders et al. | Oct 2007 | B2 |
| 7292597 | Mills et al. | Nov 2007 | B2 |
| 7315911 | Davies et al. | Jan 2008 | B2 |
| 7373435 | Carlson et al. | May 2008 | B2 |
| 7382733 | Banerjee et al. | Jun 2008 | B2 |
| 7395284 | Sato et al. | Jul 2008 | B2 |
| 7398335 | Sonksen et al. | Jul 2008 | B2 |
| 7484021 | Rastogi et al. | Jan 2009 | B2 |
| 7500023 | Casper et al. | Mar 2009 | B2 |
| 7500030 | Hathorn et al. | Mar 2009 | B2 |
| 7502873 | Casper et al. | Mar 2009 | B2 |
| 7512133 | Dugan et al. | Mar 2009 | B2 |
| 7516248 | Carlson et al. | Apr 2009 | B2 |
| 7539777 | Aitken | May 2009 | B1 |
| 7543087 | Philbrick et al. | Jun 2009 | B2 |
| 7555554 | Manders et al. | Jun 2009 | B2 |
| 7558827 | Kawashima et al. | Jul 2009 | B2 |
| 7564791 | Jayakrishnan et al. | Jul 2009 | B2 |
| 7577772 | Sonksen et al. | Aug 2009 | B2 |
| 7577773 | Gandhi et al. | Aug 2009 | B1 |
| 7594057 | Gandhi et al. | Sep 2009 | B1 |
| 7599360 | Edsall et al. | Oct 2009 | B2 |
| 7600053 | Carlson et al. | Oct 2009 | B2 |
| 7630405 | Gao et al. | Dec 2009 | B1 |
| 7631128 | Sgrosso et al. | Dec 2009 | B1 |
| 7668984 | Gregg et al. | Feb 2010 | B2 |
| 7711871 | Haechten et al. | May 2010 | B1 |
| 7743197 | Chavan et al. | Jun 2010 | B2 |
| 7765336 | Butler et al. | Jul 2010 | B2 |
| 7826349 | Kaur et al. | Nov 2010 | B2 |
| 7840717 | Flanagan et al. | Nov 2010 | B2 |
| 7840718 | Ricci et al. | Nov 2010 | B2 |
| 7840719 | Casper et al. | Nov 2010 | B2 |
| 7856511 | Ricci et al. | Dec 2010 | B2 |
| 7941570 | Flanagan et al. | May 2011 | B2 |
| 8169938 | Duchscher et al. | May 2012 | B2 |
| 8478915 | Gainey, Jr. et al. | Jul 2013 | B2 |
| 8495253 | Flanagan et al. | Jul 2013 | B2 |
| 20010030943 | Gregg et al. | Oct 2001 | A1 |
| 20020032810 | Wagner | Mar 2002 | A1 |
| 20020062407 | Tateyama et al. | May 2002 | A1 |
| 20020099967 | Kawaguchi | Jul 2002 | A1 |
| 20020152338 | Elliott et al. | Oct 2002 | A1 |
| 20020178404 | Austen et al. | Nov 2002 | A1 |
| 20030002492 | Gallagher et al. | Jan 2003 | A1 |
| 20030056000 | Mullendore et al. | Mar 2003 | A1 |
| 20030084213 | Brice, Jr. et al. | May 2003 | A1 |
| 20030103504 | Dugan et al. | Jun 2003 | A1 |
| 20030158998 | Smith | Aug 2003 | A1 |
| 20030187627 | Hild et al. | Oct 2003 | A1 |
| 20030188053 | Tsai | Oct 2003 | A1 |
| 20030208581 | Behren et al. | Nov 2003 | A1 |
| 20040030822 | Rajan et al. | Feb 2004 | A1 |
| 20040054776 | Klotz et al. | Mar 2004 | A1 |
| 20040113772 | Hong Chou | Jun 2004 | A1 |
| 20040125960 | Fosgate et al. | Jul 2004 | A1 |
| 20040136241 | Rapp et al. | Jul 2004 | A1 |
| 20040151160 | Sanders et al. | Aug 2004 | A1 |
| 20040193968 | Dugan et al. | Sep 2004 | A1 |
| 20040210719 | Bushey et al. | Oct 2004 | A1 |
| 20040230706 | Carlson et al. | Nov 2004 | A1 |
| 20040260851 | Tu | Dec 2004 | A1 |
| 20050018673 | Dropps et al. | Jan 2005 | A1 |
| 20050102456 | Kang | May 2005 | A1 |
| 20050105456 | Cookson et al. | May 2005 | A1 |
| 20050108251 | Hunt | May 2005 | A1 |
| 20050175341 | Ovadia | Aug 2005 | A1 |
| 20050193029 | Rom et al. | Sep 2005 | A1 |
| 20050204069 | Carlson et al. | Sep 2005 | A1 |
| 20050216617 | Carlson et al. | Sep 2005 | A1 |
| 20050223291 | Zimmer et al. | Oct 2005 | A1 |
| 20050229033 | Tanaka et al. | Oct 2005 | A1 |
| 20050257118 | Shien | Nov 2005 | A1 |
| 20060036769 | Frey et al. | Feb 2006 | A1 |
| 20060050726 | Ahmed et al. | Mar 2006 | A1 |
| 20060075154 | Carlson et al. | Apr 2006 | A1 |
| 20060085595 | Slater | Apr 2006 | A1 |
| 20060159112 | Sundaram et al. | Jul 2006 | A1 |
| 20060224795 | Muto et al. | Oct 2006 | A1 |
| 20070005810 | Halleck et al. | Jan 2007 | A1 |
| 20070005838 | Chang et al. | Jan 2007 | A1 |
| 20070016554 | Dapp et al. | Jan 2007 | A1 |
| 20070061463 | Hiramatsu et al. | Mar 2007 | A1 |
| 20070072543 | Paila et al. | Mar 2007 | A1 |
| 20070079022 | Carlson et al. | Apr 2007 | A1 |
| 20070079051 | Tanaka et al. | Apr 2007 | A1 |
| 20070091497 | Mizuno et al. | Apr 2007 | A1 |
| 20070162631 | Balakrishnan et al. | Jul 2007 | A1 |
| 20070174544 | Yasuda et al. | Jul 2007 | A1 |
| 20070239944 | Rupanagunta et al. | Oct 2007 | A1 |
| 20070294697 | Theimer et al. | Dec 2007 | A1 |
| 20080040519 | Starr et al. | Feb 2008 | A1 |
| 20080043563 | Brice et al. | Feb 2008 | A1 |
| 20080059638 | Hathorn et al. | Mar 2008 | A1 |
| 20080103754 | Carlson et al. | May 2008 | A1 |
| 20080103755 | Carlson et al. | May 2008 | A1 |
| 20080109580 | Carlson et al. | May 2008 | A1 |
| 20080147889 | Casper et al. | Jun 2008 | A1 |
| 20080147890 | Casper et al. | Jun 2008 | A1 |
| 20080183877 | Carlson et al. | Jul 2008 | A1 |
| 20080235553 | Chintada et al. | Sep 2008 | A1 |
| 20080256264 | Muto et al. | Oct 2008 | A1 |
| 20080273518 | Pratt et al. | Nov 2008 | A1 |
| 20080307122 | Butler et al. | Dec 2008 | A1 |
| 20090049241 | Ohno et al. | Feb 2009 | A1 |
| 20090055585 | Fernandes et al. | Feb 2009 | A1 |
| 20090144586 | Casper et al. | Jun 2009 | A1 |
| 20090172203 | Casper et al. | Jul 2009 | A1 |
| 20090172301 | Ebersole et al. | Jul 2009 | A1 |
| 20090201537 | Araya | Aug 2009 | A1 |
| 20090210557 | Gainey, Jr. et al. | Aug 2009 | A1 |
| 20090210559 | Flanagan et al. | Aug 2009 | A1 |
| 20090210560 | Yudenfriend et al. | Aug 2009 | A1 |
| 20090210561 | Ricci et al. | Aug 2009 | A1 |
| 20090210562 | Huang et al. | Aug 2009 | A1 |
| 20090210563 | Flanagan et al. | Aug 2009 | A1 |
| 20090210564 | Ricci et al. | Aug 2009 | A1 |
| 20090210570 | Bendyk et al. | Aug 2009 | A1 |
| 20090210571 | Casper et al. | Aug 2009 | A1 |
| 20090210572 | Yudenfriend et al. | Aug 2009 | A1 |
| 20090210573 | Yudenfriend et al. | Aug 2009 | A1 |
| 20090210576 | Casper et al. | Aug 2009 | A1 |
| 20090210579 | Bendyk et al. | Aug 2009 | A1 |
| 20090210580 | Bendyk et al. | Aug 2009 | A1 |
| 20090210581 | Flanagan et al. | Aug 2009 | A1 |
| 20090210582 | Bendyk et al. | Aug 2009 | A1 |
| 20090210583 | Bendyk et al. | Aug 2009 | A1 |
| 20090210584 | Carlson et al. | Aug 2009 | A1 |
| 20090210585 | Ricci et al. | Aug 2009 | A1 |
| 20090210768 | Carlson et al. | Aug 2009 | A1 |
| 20090210769 | Casper et al. | Aug 2009 | A1 |
| 20090210884 | Ricci et al. | Aug 2009 | A1 |
| 20090307388 | Tchapda | Dec 2009 | A1 |
| 20100014526 | Chavan et al. | Jan 2010 | A1 |
| 20100030919 | Flanagan et al. | Feb 2010 | A1 |
| 20100030920 | Casper et al. | Feb 2010 | A1 |
| 20100064072 | Tang et al. | Mar 2010 | A1 |
| 20100299460 | Wang | Nov 2010 | A1 |
| 20110113159 | Casper et al. | May 2011 | A1 |
| 20110173640 | Kreuzenstein et al. | Jul 2011 | A1 |
| 20120110222 | Dang et al. | May 2012 | A1 |
| 20120311390 | Bubb et al. | Dec 2012 | A1 |
| 20130047042 | Bubb et al. | Feb 2013 | A1 |
| Number | Date | Country |
|---|---|---|
| 3931514 | Mar 1990 | DE |
| 1264096 | Feb 1972 | GB |
| 2291990 | Feb 1996 | GB |
| 61123970 | Jun 1986 | JP |
| 63236152 | Oct 1988 | JP |
| 2010140127 | Jun 2010 | JP |
| 0235367 | May 2002 | WO |
| 2006102664 | Sep 2006 | WO |
| Entry |
|---|
| Z/Series Input/Output Configuration Program user's Guide for IYP IOCP, SB10-7029-03c. International Business Machines Corporation, Jun. 2003, 372 pages. |
| Aboda, B.-et al.; Network Working Group; “Securing Block Storage Protocols Over IP”; ACM Digital Library; RFC3723; Apr. 2004, 66 pages. |
| Azimi, R.-et al.; “miNI: Reducing Network Interface Memory Requirements with Dynamic Handle Lookup”; ACM Digital Library; pp. 261-272; Jun. 2003. |
| Emulex Corporation; “Install the LP850 Host Adapter”; Google/Emulex Corporation, LightPulse LP850 Fibre Channel PCI Host Adapter Manuals; pp. 1-10, 1999. |
| Foong, A.-et al.; “Towards SSD-Ready Enterprise Platforms”; Google/Intel Corporation; 2008-2009, 7 pages. |
| Hewlett-Packard Company; HP A4800A PCI FWD SCSI Host Bus Adapter—Service & User Guide, Edition 6; Google/H-P; 2001, pp. 1-64. |
| Hewlett-Packard Company; “HP A5149 PCI Ultra2 SCSI Host Bus Adapter—Service and User Guide”, Edition 2; Google/H-P; 2001, pp. 1-66. |
| Jiang, J.-et al.; “The Role of FCoE in I/O Consolidation”; ACM Digital Library/International Conf on Advanced Infocomm Technology '08; Jul. 2008, pp. 1-6. |
| Josephson, WK.-et al.; “DFS: A File System for Virtualized Flash Storage”; ACM Digital Library; vol. 6, No. 3, Article 14, Sep. 2010, pp. 1-15. |
| LSI Corporation; “PCI Express to 6Gb/s SAS Host Bus Adapters”; Google; Chapter 1, Introduction/Overview; LSI User Guide; Oct. 2009, pp. 1-28. |
| LSI; “ScsiPortGetDeivceBase”; Google/LSI; Apr. 2003, pp. 1-3. |
| Magoutis, K.; “The Optimistic Direct Access File System: Design and Network Interface Support”; Division of Engineering & Applied Science, Harvard Univ.; Feb. 2002, pp. 1-7. |
| Miller, DJ.-et al.; “Motivating Future Interconnects: A Differential Measurement Analysis of PCI Latency”; ACM Digital Library; pp. 94-105; Oct. 2009. |
| Network Storage Systems; Google; Oct. 2007, pp. 1-7. |
| Petersen, MK.-et al.; “DIF/DIX Aware Linux SCSI HBA Interface”; Google; Oracle Linux Engineering; Jul. 2008, pp. 1-258. |
| Satran, J.-et al.; Network Working Group; “Internet Small Computer Systems Interface (iSCSI)”; ACM Digital Library; RFC3720; Apr. 2004, pp. 1-258. |
| Sun, Oracle; “Sun Storage 6 Gb SAS PCIe HBA, External—Installation Guide for HBA Models”; Google; Revision A; Nov. 2010, 80 pages. |
| U.S. Appl. No. 13/024,468, Non Final Office Action Mailed Jan. 26, 2012, 58 pages. |
| U.S. Appl. No. 13/351,073, Non Final Office Action Mailed Mar. 30, 2012, 8 pages. |
| U.S. Appl. No. 12/030,912, Final Office Action Mailed Feb. 27, 2012, 25 pgs. |
| U.S. Appl. No. 12/031,023, Non-Final Office Action Mailed Feb. 1, 2012, 37 pages. |
| URL, http://en.wikipedia.org/wiki/FICON, FICON, Wikipedia, USA, Wikimedia Foundation, Inc., Aug. 9, 2011, 3 pages. |
| U.S. Appl. No. 12/030,912 Non Final Office Action Mailed Aug. 18, 2011, 35 pages. |
| U.S. Appl. No. 12/030,981 Non Final Office Action Mailed Aug. 2, 201, 59 pages. |
| U.S. Appl. No. 12/031,042, Non-Final Office Action Mailed Sep. 30, 201, 20 pages. |
| U.S. Appl. No. 12/031,182 Final Office Action dated Oct. 20, 2011, 10 pages. |
| U.S. Appl. No. 12/031,182 Non-Final Office Action dated Mar. 16, 2012, 18 pages. |
| Vaghani, SB.; “Virtual Machine File System”; VMWare Inc./ACM Digital Library; pp. 57-69; 2008-2009. |
| “Fibre Channel Single Byte Command Code Sets—2 Mapping Protocol (FC-SB-3)” T11/Project 1357-D/Rev 1.6, INCITS Mar. 2003, 206 pgs., American National Standards Institute. |
| “Information Technology—Fibre Channel Protocol for SCSI, Third Version (FCP-3),” T10 Project 1560-D, Revision 4g, Sep. 13, 2005, 140 pages. |
| ANSI INCITS 433-2007, Information Technology Fibre Channel Link Services (FC-LS), Jul. 2007, 211 pages. |
| Behrs, Jr, “Adaptive Prediction Minimizes Data Overrun and Underrun”, IBM, Nov. 1994, pp. 1-3. http:// priorartdatabase.com/IPCOM/000114189. |
| 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. |
| Dauby, et al. “Contention Resolution Between Two Processors”; IBM Technical Disclosure Bulletin; vol. 26; No. 10A; Mar. 1984; 3 pages. |
| DeVeer, J.A.; “Control Frame Multiplexing on Serial I/O Channels”; IBM Technical Disclosure Bulletin; vol. 32; No. 10A; Mar. 1990; pp. 39-40. |
| Golasky, Richard; “Link-Level Error Recovery With Tape Backup”; Dell Power Solutions; Aug. 2005; pp. 88-91. |
| 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. |
| U.S. Pat. No. 7,373,435 Non-Final Office Action Sep. 13, 2007. |
| U.S. Pat. No. 7,373,435 Non-Final Office Action Jun. 11, 2007. |
| U.S. Pat. No. 7,600,053 Non-Final Office Action dated Mar. 17, 2009. |
| U.S. Appl. No. 12/031,023, Final Office Action Mailed Nov. 18, 2010. |
| U.S. Appl. No. 12/030,932, Final Office Action Mailed Jul. 23, 2010. |
| U.S. Appl. No. 12/030,932, Non-Final Office Action Mailed Dec. 16, 2010. |
| U.S. Appl. No. 12/030,951, Final Office Action Mailed Oct. 26, 2010. |
| U.S. Appl. No. 12/030,975 Non-Final Office Action dated Oct. 22, 2009. |
| U.S. Appl. No. 12/030,975. Final Office Action Mailed May 13, 2010. |
| U.S. Appl. No. 12/030,993, Final Office Action Mailed Dec. 10, 2010. |
| U.S. Appl. No. 12/031,021 Non-Final Office Action dated Jan. 8, 2010. |
| U.S. Appl. No. 12/031,201, Final Office Action Mailed Aug. 3, 2010. |
| U.S. Appl. No. 12/031,201, Non-Final Office Action Mailed Dec. 27, 2010. |
| U.S. Appl. No. 12/030,912 Non-Final Office Action dated Mar. 18, 2010. |
| U.S. Appl. No. 12/030,989 Non-Final Office Action dated Oct. 22, 2009. |
| U.S. Appl. No. 12/030,993 Non-Final Office Action dated Oct. 28, 2009. |
| U.S. Appl. No. 12/031,023 Non-Final Office Action dated Oct. 29, 2009. |
| U.S. Appl. No. 12/183,305, filed Jul. 31, 2008. |
| U.S. Appl. No. 12/183,315, filed Jul. 31, 2008. |
| U.S. Appl. No. 12/030,951 Non-Final Office Action dated Nov. 23, 2009. |
| U.S. Appl. No. 12/030,932 Non-Final Office Action dated Dec. 16, 2009. |
| U.S. Appl. No. 11/126,728 Non-Final Office Action Apr. 16, 2007. |
| U.S. Appl. No. 11/469,573 Non-Final Office Action dated Apr. 11, 2008. |
| U.S. Appl. No. 11/965,866 Non-Final Office Action dated Jun. 3, 2010. |
| U.S. Appl. No. 11/548,060 Non-Final Office Action dated Apr. 15, 2008. |
| U.S. Appl. No. 11/548,093 Non-Final Office Action dated Apr. 17, 2008. |
| U.S. Appl. No. 12/030,920 Non-Final Office Action dated Feb. 23, 2010. |
| U.S. Appl. No. 12/030,939 Non-Final Office Action dated Nov. 16, 2009. |
| U.S. Appl. No. 12/030,951 Non-Final Office Action dated May 20, 2010. |
| U.S. Appl. No. 12/030,961 Non-Final Office Action dated Dec. 17, 2009. |
| U.S. Appl. No. 12/030,985, Non Final Office Action Mailed May 5, 2010. |
| U.S. Appl. No. 12/031,038 Non-Final Office Action dated Nov. 16, 2009. |
| U.S. Appl. No. 12/031,038, Non-Final Office Action Mailed Apr. 15, 2010. |
| U.S. Appl. No. 12/031,182 Final Office Action Mailed Jul. 22, 2010. |
| U.S. Appl. No. 12/031,182 Non-Final Office Action dated Jan. 22, 2010. |
| Final Office Action for U.S. Appl. No. 12/030,912 mailed Oct. 6, 2010, 31 pages. |
| GB1206682.5 Combined Search and Examination Report under Sections 17 and 18(3). Mailed on Jul. 25, 2012. 14 pages. |
| Germian Office Action for Application No. 10 2012 209 014.2, Mailed on Apr. 9, 2013, 3 pages. |
| International Search Report and Written Opinion for PCT/EP2009/051447 dated Jul. 1, 2009, 9 pages. |
| International Search Report and Written Opinion for PCT/EP2009/051483 dated Jul. 27, 2009, 9 pages. |
| Iren, et al.; “The Transport Layer: Tutorial and Survey”; ACM Computing Surveys; vol. 31, No. 4; Dec. 1999; pp. 360-405. |
| Ishikawa, Hikaru, 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. |
| U.S. Appl. No. 12/181,662—Final Office Action dated Jan. 4, 2010, 10 pages. |
| U.S. Appl. No. 12/617,055, Non Final Office Action Mailed Jun. 23, 2011, 8 pages. |
| Written Opinion and International Search Report for PCT/EP2009/051463 dated Jul. 22, 2009, 9 pages. |
| U.S. Appl. No. 13/075,993 Non Final Office Action Mailed Jul. 19, 2012, 14 pages. |
| U.S. Appl. No. 12/030,912, Non Final Office Action Mailed Oct. 4, 2012, 25 pages. |
| U.S. Appl. No. 13/075,993, Final Office Action Mailed Feb. 13, 2012, 21 pages. |
| U.S. Appl. No. 13/150,539, Non-Final Office Action Mailed Mar. 2, 2012, 58 pages. |
| U.S. Appl. No. 13/150,583, Non-Final Office Action Mailed Feb. 3, 2012, 57 pages. |
| U.S. Appl. No. 13/173,772 Non Final Office Action Mailed Feb. 3, 2012, 61 pages. |
| U.S. Appl. No. 13/173,733, Non-Final Office Action Mailed Feb. 7, 2012, 55 pages. |
| U.S. Appl. No. 12/031,182, Non Final Office Action Mailed Dec. 23, 2010, 11 pages. |
| Written Opinion and International Search Report for PCT/EP2009/051459 dated Jun. 23, 2009, 8 pages. |
| “Protocol for Insochronous Traffic Over Fiber Channel Switching”; IBM Technical Disclosure Bulletin; vol. 37, No. 06B; Jun. 1994. pp. 377-380. |
| “z/Architecture-Principles of Operation,” IBM Publication No. SA22-7832-04, 5th Ed., Sep. 2005, pp. 1-1144. |
| IBM, “Method and Apparatus to Monitor PAV Utilization”, Feb. 2005, pp. 1-3. http://priorartdatabase.com/IPCOM/000082878. |
| 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. |
| 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. |
| 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. |
| 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. |
| International Search Report; International Application No. PCT/EP2009/059184; International Filing Date: Jul. 16, 2009; Date of mailing: Jan. 14, 2010; 9 pages. |
| Laudon et al.,“System Overview of the SGI Origin 200/2000 Product Line,” 1997, iEEE Publication pp. 150-156. |
| Moore et al., “Reconfiguration of Storage Elements to Improve Performance”, IBM, Dec. 1983, pp. 1-3. http://priorartdatabas.com/IPCOM/000047719. |
| Nordstrom.; “Sequence Reception Method for a Fibre Channel Protocol Chip”; IBM Technical Disclosure Bulletin; vol. 38, No. 12; Dec. 1995; pp. 267-269. |
| U.S. Pat. No. 7,000,036 Non-Final Office Action dated Jul. 15, 2005, 1 page. |
| U.S. Pat. No. 7,174,274 Non-Final Office Action dated Jun. 8, 2006, 1 page. |
| Peterson; “Information Techonology, Fibre Channel Protocol for SCSI, Fourth Version (FCP-3)”, Draft Proposed American National Standard, Jun. 2004; pp. 1-142. |
| Sachs, M.W.; “I/O Marker Changing”; IBM Technical Disclosure Bulletin; vol. 37, No. 02A; Feb. 1994; pp. 75-76. |
| SCSI Primary Commands—4 (SPC-4); Project T10/1731-D. Rev 11. INCITS Apr. 14, 2010, 785 pages (Part 1, pp. 1-390; Part 2, pp. 391-785). |
| Simmons et al.; “A Performance Comparison of Three Supercomputers: Fujitsu VP-2600, NEC SX-3, and CRAY Y-MP”; ACM, Conference on High Performance Networking and Computing, Jul. 1991 ACM/IEEE conference on Supercomputing, Albuquerque, NM; pp. 150-157. |
| 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. 1-575. |
| 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. |
| Srikrishnan et al.; “Sharing FCP Adapters Through Virtualization”; IBM J. Res. & Dev., vol. 51, No. 1/2; Jan./Mar. 2007; pp. 103-118. |
| Stone, et al.; “When the CRC and TCP Checksum Disagree”; SIGCOMM '00, Stockholm, Sweden; Jul. 2000; 10 pages. |
| 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. |
| U.S. Appl. No. 12/030,954 Non-Final Office Action dated Jan. 21, 2010, 20 pages. |
| U.S. Appl. No. 12/031,201 Non-Final Office Action dated Jan. 25, 2010, 14 pages. |
| U.S. Appl. No. 12/183,323, Non-Final Office Action Mailed Jan. 3, 2011, 18 pages. |
| U.S. Appl. No. 12/031,042, Final Office Action Mailed Oct. 25, 2010, 27 pages. |
| U.S. Appl. No. 12/183,323, filed Jul. 31, 2008, 54 pages. |
| U.S. Appl. No. 12/364,615, Non Final Office Action Mailed Oct. 7, 2010, 51 pages. |
| U.S. Appl. No. 12/030,954 Non Final Office Action mailed Jul. 12, 2010, 36 pages. |
| U.S. Appl. No. 12/030,961 Final Office Action mailed Jul. 12, 2010, 35 pages. |
| U.S. Appl. No. 12/030,989 Final Office Action dated May 24, 2010, 28 pages. |
| U.S. Appl. No. 12/030,993 Non Final Office Action mailed Jun. 28, 2010, 24 pages. |
| U.S. Appl. No. 12/031,023 Non Final Office Action mailed Jun. 11, 2010, 20 pages. |
| U.S. Appl. No. 12/031,042, Non-Final Office Action Mailed Apr. 5, 2010, 30 pages. |
| U.S. Appl. No. 12/183,305, Non-Final Office Action Mailed May 11, 2010, 34 pages. |
| U.S. Appl. No. 12/183,323 Non Final Office Action mailed Jul. 19, 2010, 42 pages. |
| Written Opinion and International Search Report for PCT/EP2009/051445 dated Jun. 25, 2009, 11 pages. |
| Written Opinion and International Search Report for PCT/EP2009/051446 dated Jun. 25, 2009, 8 pages. |
| Written Opinion and International Search Report for PCT/EP2009/051450 dated Jul. 7, 2009, 7 pages. |
| Written Opinion and International Search Report for PCT/EP2009/051461 dated Sep. 22, 2009, 7 pages. |
| Written Opinion and International Search Report for PCT/EP2009/051462 dated Jul. 1, 2009, 9 pages. |
| Z/Architecture, “Principles of Operation SA 22-7832-01 International Business Machines Corporation,” 2nd Edition, Oct. 2001, pp. 1-1024. |
| U.S. Appl. No. 14/304,383, filed Mar. 13, 2014; Non-final office action mailed Jun. 3, 2014; 15 pages. |
| U.S. Appl. No. 14/543,368, filed Nov. 17, 2014; Final office action mailed Jul. 30, 2015; 71 pages. |
| U.S. Appl. No. 14/483,700, filed Sep. 11, 2015; Non-final office action, mailed Aug. 27, 2015; 63 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20150254204 A1 | Sep 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12031182 | Feb 2008 | US |
| Child | 14717598 | US |
