US 9,052,837 B2Grant
Processing communication data in a ships passing condition
Issue Date:2015-06-09
•20 Claims
•17 Drawing Sheets
Abstract
Articles of manufacture, apparatuses, and methods for processing communications between a control unit and a channel subsystem in an input/output processing system are disclosed. Embodiments of the invention 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 message in a first mode from the control unit to the channel subsystem; receiving a command in a second mode 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.
Metadata
Assignee
- International Business Machines Corporation
Inventors
- Catherine C. Huang
- Daniel F. Casper
- John R. Flanagan
- Roger G. Hathorn
- Matthew J. Kalos
- Louis W. Rcci
Application Information
Application Number:US 12/031,182
Filing Date:2008-02-14
Priority Date:2008-02-14
Art Unit:2184
Classifications
IPC:
G06F3/00G06F3/06
Patent Drawings (17 sheets)
Description
BACKGROUND OF THE INVENTION
[0001] 1. Field of the Invention
[0002] This invention relates, in general, to input/output processing, and in particular, to processing data associated with or generated by input/output processing.
[0003] 2. Description of Background
[0004] 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.
[0005] 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.
[0006] 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.
[0007] 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.
[0008] 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.
[0009] 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.
[0010] 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.
[0011] 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.
[0012] 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.
[0013] 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.
[0014] 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.
BRIEF SUMMARY OF THE INVENTION
[0015] Embodiments of the invention 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 message in a first mode from the control unit to the channel subsystem; receiving a command in a second mode 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.
[0016] 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.
[0017] 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.
[0018] 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.
[0019] 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.
[0020] 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.
[0021] 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.
BRIEF DESCRIPTION OF THE DRAWINGS
[0022] 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:
[0023] FIG. 1 depicts an exemplary embodiment of a processing environment incorporating and using one or more aspects of the present invention;
[0024] FIG. 2A depicts one example of a prior art channel command word;
[0025] FIG. 2B depicts one example of a prior art channel command word channel program;
[0026] FIG. 3 depicts an exemplary embodiment of a prior art link protocol used in communicating between the channel and control unit to execute the channel command word channel program of FIG. 2B ;
[0027] FIG. 4 depicts an exemplary embodiment of a transport control word channel program, in accordance with an aspect of the present invention;
[0028] FIG. 5 depicts an exemplary embodiment of a link protocol used to communicate between a channel and control unit to execute the transport control word channel program of FIG. 4 , in accordance with an aspect of the present invention;
[0029] FIG. 6 depicts an exemplary embodiment of a prior art link protocol used to communicate between a channel and control unit in order to execute four read commands of a channel command word channel program;
[0030] FIG. 7 depicts an exemplary embodiment of a link protocol used to communicate between a channel and control unit to process the four read commands of a transport control word channel program, in accordance with an aspect of the present invention;
[0031] FIG. 8 depicts an exemplary embodiment of a control unit and a channel, in accordance with an aspect of the present invention;
[0032] FIG. 9 depicts a first exemplary embodiment of a link protocol used to communicate between a channel and control unit to process messages between a channel and a control unit in a ships passing condition;
[0033] FIG. 10 depicts a second exemplary embodiment of a link protocol used to communicate between a channel and control unit to process messages between a channel and a control unit in a ships passing condition;
[0034] FIG. 11 depicts a third exemplary embodiment of a link protocol used to communicate between a channel and control unit to process messages between a channel and a control unit in a ships passing condition;
[0035] FIG. 12 depicts a fourth exemplary embodiment of a link protocol used to communicate between a channel and control unit to process messages between a channel and a control unit in a ships passing condition;
[0036] FIG. 13 depicts a fifth exemplary embodiment of a link protocol used to communicate between a channel and control unit to process messages between a channel and a control unit in a ships passing condition;
[0037] FIG. 14 depicts a sixth exemplary embodiment of a link protocol used to communicate between a channel and control unit to process messages between a channel and a control unit in a ships passing condition;
[0038] FIG. 15 depicts a seventh exemplary embodiment of a link protocol used to communicate between a channel and control unit to process messages between a channel and a control unit in a ships passing condition; and
[0039] FIG. 16 depicts an exemplary embodiment of an article of manufacture incorporating one or more aspects of the present invention.
[0040] The detailed description explains the preferred embodiments of the invention, together with advantages and features, by way of example with reference to the drawings.
DETAILED DESCRIPTION OF THE INVENTION
[0041] 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.
[0042] 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.
[0043] 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.
[0044] 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.
[0045] One example of an I/O processing system incorporating and using one or more aspects of the present invention is described with reference to FIG. 1 . I/O processing system 100 includes a host system 101, which further includes for instance, a main memory 102, one or more central processing units (CPUs) 104, a storage control element 106, and a channel subsystem 108. The host system 101 may be a large scale computing system, such as a mainframe or server. The I/O processing system 100 also includes one or more control units 110 and one or more I/O devices 112, each of which is described below.
[0046] 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.
[0047] 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.
[0048] 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.
[0049] 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.
[0050] Each channel path 122 includes a channel 124 (channels 124 are located within the channel subsystem 108, in one example, as shown in FIG. 1 ), one or more control units 110 and one or more connections 120. In another example, it is also possible to have one or more dynamic switches (not depicted) as part of the channel path 122. A dynamic switch is coupled to a channel 124 and a control unit 110 and provides the capability of physically interconnecting any two links that are attached to the switch. In another example, it is also possible to have multiple systems, and therefore multiple channel subsystems (not depicted) attached to control unit 110.
[0051] 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.
[0052] 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.
[0053] 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.
[0054] 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.
[0055] 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 FIG. 2A . A CCW 200 includes, for instance, a command code 202 specifying the command to be executed (e.g., read, read backward, control, sense and write); a plurality of flags 204 used to control the I/O operation; for commands that specify the transfer of data, a count field 206 that specifies the number of bytes in the storage area designated by the CCW to be transferred; and a data address 208 that points to a location in main memory that includes data, when direct addressing is employed, or to a list (e.g., contiguous list) of modified indirect data address words (MIDAWs) to be processed, when modified indirect data addressing is employed. Modified indirect addressing is further described in U.S. application Ser. No. 11/464,613, entitled “Flexibly Controlling The Transfer Of Data Between Input/Output Devices And Memory,” Brice et al., filed Aug. 15, 2006, which is hereby incorporated herein by reference in its entirety.
[0056] 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 FIG. 2B . A CCW channel program 210 includes, for instance, a define extent CCW 212 that has a pointer 214 to a location in memory of define extent data 216 to be used with the define extent command. In this example, a transfer in channel (TIC) 218 follows the define extent command that refers the channel program to another area in memory (e.g., an application area) that includes one or more other CCWs, such as a locate record 217 that has a pointer 219 to locate record data 220, and one or more read CCWs 221. Each read CCW 220 has a pointer 222 to a data area 224. The data area includes an address to directly access the data or a list of data address words (e.g., MIDAWs or IDAWs) to indirectly access the data. Further, CCW channel program 210 includes a predetermined area in the channel subsystem defined by the device address called the subchannel for status 226 resulting from execution of the CCW channel program.
[0057] The processing of a CCW channel program is described with reference to FIG. 3 , as well as with reference to FIG. 2B . In particular, FIG. 3 shows an example of the various exchanges and sequences that occur between a channel and a control unit when a CCW channel program is executing. The link protocol used for the communications is FICON (Fibre Connectivity), in this example. Information regarding FICON is described in “Fibre Channel Single Byte Command Code Sets-3 Mapping Protocol (FC-SB-3), T11/Project 1357-D/Rev. 1.6, INCITS (March 2003), which is hereby incorporated herein by reference in its entirety.
[0058] Referring to FIG. 3 , a channel 300 opens an exchange with a control unit 302 and sends a define extent command and data associated therewith 304 to control unit 302. The command is fetched from define extent CCW 212 (FIG. 2B ) and the data is obtained from define extent data area 216. The channel 300 uses TIC 218 to locate the locate record CCW and the read CCW. It fetches the locate record command 305 (FIG. 3 ) from the locate record CCW 217 (FIG. 2B ) and obtains the data from locate record data 220. The read command 306 (FIG. 3 ) is fetched from read CCW 221 (FIG. 2B ). Each is sent to the control unit 302.
[0059] 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.
[0060] 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.
[0061] 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 FIG. 1 , uses a TCW to identify the location of the TCCB, as well as locations for accessing and storing status and data associated with executing the channel program. The TCW is interpreted by the channel and is not sent or seen by the control unit.
[0062] One example of a channel program to read 4 k of data, as in FIG. 2B , but includes a TCCB, instead of separate individual CCWs, is described with reference to FIG. 4 . As shown, a channel program 400, referred to herein as a TCW channel program, includes a TCW 402 specifying a location in memory of a TCCB 404, as well as a location in memory of a data area 406 or a TIDAL 410 (i.e., a list of transfer mode indirect data address words (TIDAWs), similar to MIDAWs) that points to data area 406, and a status area 408. TCWs, TCCBs, and status are described in further detail below.
[0063] The processing of a TCW channel program is described with reference to FIG. 5 . The link protocol used for these communications is, for instance, Fibre Channel Protocol (FCP). In particular, three phases of the FCP link protocol are used, allowing host bus adapters to be used that support FCP to perform data transfers controlled by CCWs. FCP and its phases are described further in “Information Technology—Fibre Channel Protocol for SCSI, Third Version (FCP-3),” T10 Project 1560-D, Revision 4, Sep. 13, 2005, which is hereby incorporated herein by reference in its entirety.
[0064] 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.
[0065] Referring to FIG. 5 , a channel 500 opens an exchange with a control unit 502 and sends TCCB 504 to the control unit 502. In one example, the TCCB 504 and sequence initiative are transferred to the control unit 502 in a FCP command, referred to as FCP_CMND information unit (IU) or a transport command IU. The control unit 502 executes the multiple commands of the TCCB 504 (e.g., define extent command, locate record command, read command as device control words (DCWs)) and forwards data 506 to the channel 500 via, for instance, a FCP_Data IU. It also provides status and closes the exchange 508. As one example, final status is sent in a FCP status frame that has a bit active in, for instance, byte 10 or 11 of the payload of a FCP_RSP IU, also referred to as a transport response IU. The FCP_RSP_IU payload may be 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.
[0066] In a further example, to write 4 k of customer data, the channel 500 uses the FCP link protocol phases, as follows:
[0067] 1. Transfer a TCCB in the FCP_CMND IU.
[0068] 2. Transfer the IU of data, and sequence initiative to the control unit 502.
[0069] 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.
[0070] By executing the TCW channel program of FIG. 4 , there is only one exchange opened and closed (see also FIG. 5 ), instead of two exchanges for the CCW channel program of FIG. 2B (see also FIG. 3 ). Further, for the TCW channel program, there are three communication sequences (see FIGS. 4-5 ), as compared to seven sequences for the CCW channel program (see FIGS. 2B-3 ).
[0071] 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 FIG. 6 with the communications of the TCW channel program of FIG. 7 . In the CCW channel program of FIG. 6 , each of the commands (e.g., define extent command 600, locate record command 601, read command 602, read command 604, read command 606, locate record command 607 and read command 608) are sent in separate sequences from channel 610 to control unit 612. Further, each 4 k block of data (e.g., data 614-620) is sent in separate sequences from the control unit 612 to the channel 610. This CCW channel program requires two exchanges to be opened and closed (e.g., open exchanges 622, 624 and close exchanges 626, 628), and fourteen communications sequences. This is compared to the three sequences and one exchange for the TCW channel program of FIG. 7 , which accomplishes the same task as the CCW channel program of FIG. 6 .
[0072] As depicted in FIG. 7 , a channel 700 opens an exchange with a control unit 702 and sends a TCCB 704 to the control unit 702. The TCCB 704 includes the define extent command, the two locate record commands, and the four read commands in DCWs, as described above. In response to receiving the TCCB 704, the control unit 702 executes the commands and sends, in a single sequence, the 16 k of data 706 to the channel 700. Additionally, the control unit 702 provides status to the channel 700 and closes the exchange 708. Thus, the TCW channel program requires much less communications to transfer the same amount of data as the CCW channel program of FIG. 6 .
[0073] Turning now to FIG. 8 , one embodiment of the control unit 110 and the channel 124 of FIG. 1 that support TCW channel program execution is depicted in greater detail. The control unit 110 includes CU control logic 802 to parse and process command messages containing a TCCB, such as the TCCB 704 of FIG. 7 , received from the channel 124 via the connection 120. The CU control logic 802 can extract DCWs and control data from the TCCB received at the control unit 110 to control a device, for instance, I/O device 112 via connection 126. The CU control logic 802 sends device commands and data to the I/O device 112, as well as receives status information and other feedback from the I/O device 112.
[0074] 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.
[0075] 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.
[0076] 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”.
[0077] In an exemplary embodiment, the TCW channel program is implemented using a protocol to execute Transport Control Words, for example, the transport mode protocol.
[0078] 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.
[0079] 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.
[0080] 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.
[0081] 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.
[0082] 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.
[0083] 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.
[0084] 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.
[0085] 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”.
[0086] 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.
[0087] 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.
[0088] Exemplary embodiments of the processing of messages and/or programs in a ships passing situation are described with reference to FIGS. 9-15 . The link protocol used for these communications is, for instance, Fibre Channel Protocol (FCP).
[0089] 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.
[0090] 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.
[0091] 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”.
[0092] Examples of embodiments of the method described herein are further described below, with reference to FIGS. 9-15 . The exemplary embodiment described with reference to FIG. 9 describes a procedure for processing data in a ships passing condition. The exemplary embodiments described with reference to FIGS. 10-15 describe alternative embodiments of the procedure where various messages have been lost. The loss of a message is represented as a broken line portion shown in relation to a respective exchange.
EXAMPLE 1
Ships Passing Condition
[0093] In the following example, a procedure for processing data in a ships passing condition is illustrated with reference to FIG. 9 . The procedure for opening exchanges and exchanging various methods includes one or more of the following phases:
[0094] 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.
[0095] 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.
[0096] 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.
[0097] 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”).
[0098] 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.
[0099] 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.
[0100] 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.
[0101] 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.
[0102] 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.
[0103] 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.
[0104] 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.
EXAMPLE 2
The TCCB IU 912 is Lost
[0105] In the following example, a procedure for processing data in a ships passing condition is illustrated with reference to FIG. 10 . In this example, the TCCB IU 912 is lost, i.e., is not received by the control unit 910. The procedure includes one or more of the following phases:
[0106] 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.
[0107] 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.
[0108] 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.
[0109] 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.
[0110] 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.
[0111] 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).
[0112] 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.
EXAMPLE 3
The FICON 85 STATUS IU 911 is Lost
[0113] In the following example, a procedure for processing data in a ships passing condition is illustrated with reference to FIG. 11 . In this example, the FICON 85 STATUS IU 911 is lost, i.e., is not received by the channel 905. The procedure includes one or more of the following phases:
[0114] 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.
[0115] 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.
[0116] 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).
[0117] 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.
EXAMPLE 4
The FICON Stack IU 913 is Lost
[0118] In the following example, a procedure for processing data in a ships passing condition is illustrated with reference to FIG. 12 . In this example, the FICON Stack IU 913 is lost, i.e., is not received by the control unit 910. The procedure includes one or more of the following phases:
[0119] 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.
[0120] 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.
[0121] 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).
[0122] 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.
EXAMPLE 5
The FICON DACK IU 914 is Lost
[0123] In the following example, a procedure for processing data in a ships passing condition is illustrated with reference to FIG. 13 . In this example, the FICON DACK IU 914 is lost, i.e., is not received by the channel 905. The procedure includes one or more of the following phases:
[0124] 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.
[0125] 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.
[0126] 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.
[0127] 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.
[0128] 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.
EXAMPLE 6
The RSP IU 915 is Lost
[0129] In the following example, a procedure for processing data in a ships passing condition is illustrated with reference to FIG. 14 . In this example, the RSP IU 915 is lost, i.e., is not received by the channel 905. The procedure includes one or more of the following phases:
[0130] 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.
[0131] 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.
[0132] 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.
[0133] 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.
[0134] 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.
[0135] 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).
[0136] 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.
EXAMPLE 7
The Confirm IU 916 is Lost
[0137] In the following example, a procedure for processing data in a ships passing condition is illustrated with reference to FIG. 14 . In this example, the Confirm IU 916 is lost, i.e., is not received by the channel 905. The procedure includes one or more of the following phases:
[0138] 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.
[0139] 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.
[0140] 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.
[0141] 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.
[0142] 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.
[0143] 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.
[0144] 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 FIG. 16 . A computer program product 1600 includes, for instance, one or more computer usable media 1602 to store computer readable program code means or logic 1604 thereon to provide and facilitate one or more aspects of the present invention. The medium can be an electronic, magnetic, optical, electromagnetic, infrared or semiconducter system (or apparatus or device) or a propagation medium. Example of a computer readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Examples of optical disks include compact disk-read only memory (CD-ROM), compact disk-read/write (CD-R/W) and DVD.
[0145] 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.
[0146] 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.
[0147] 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 FIG. 16 on the computer usable medium 1602 with computer program code logic 1604 containing instructions embodied in tangible media as an article of manufacture. Exemplary articles of manufacture for computer usable medium 1602 may include floppy diskettes, CD-ROMs, hard drives, universal serial bus (USB) flash drives, or any other computer-readable storage medium, wherein, when the computer program code logic 1604 is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. Exemplary embodiments include computer program code logic 1604, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code logic 1604 is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. When implemented on a general-purpose microprocessor, the computer program code logic 1604 segments configure the microprocessor to create specific logic circuits.
[0148] 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.
Claims
What is claimed is:
1. A computer program product for processing communications between a control unit and a channel subsystem in an input/output (I/O) processing system, comprising a tangible storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method comprising:
sending a message in a command mode from the control unit to the channel subsystem of a host computer system, the control unit configured to control an I/O device and receive information from the host computer system and the control unit via a channel path, the command mode using a first protocol that supports Channel Command Word (CCW) channel programs configured to support at least one CCW that specifies a command for performing an I/O operation;
receiving, by the control unit, a command in a transport mode from the channel subsystem at the control unit, the transport mode using a second protocol that supports Transport Control Word (TCW) channel programs configured to support at least one transport command control block (TCCB), the TCCB configured to hold a plurality of commands for performing an I/O operation;
determining, by the control unit, whether the command is responsive to the message;
determining, by the control unit, that a ships passing condition has occurred between the channel subsystem and the control unit based on the command being not responsive to the message and the command being sent on the same logical path as the message; and
based on determining that the ships passing condition has occurred, determining by the control unit whether to perform one of i) executing the command and ii) terminating the command.
2. The computer program product of claim 1, further comprising at least one of i) receiving the command on a first exchange, ii) sending the message on a second exchange, and iii) awaiting a response message from the channel subsystem on a third exchange.
3. The computer program product of claim 2, wherein determining is responsive to the response message received from the channel subsystem.
4. The computer program product claim 2, further comprising:
setting a time period for receipt of the response message, and
responsive to expiration of the time period without receiving the response message, aborting the first exchange and the second exchange.
5. The computer program product of claim 1, further comprising sending a response message in response to the command, the response message comprising at least one of an indication of execution of the command and a device status.
6. The computer program product of claim 1, wherein:
sending the message comprises opening a first exchange and sending a status message in a command mode on the first exchange and setting a time period for receipt of a response message from the channel subsystem in response to the status message;
receiving the command comprises receiving the command in a transport mode on a second exchange; and
determining whether to perform comprises:
awaiting a response message from the channel subsystem in the command mode on a third exchange; and
responsive to the response message, determining whether to perform one
of i) executing the command and ii) terminating the command, and sending a response message in the transport mode on the second exchange in response to the command, the response message comprising at least one of: an indication of execution of the command, and a device status.
7. An apparatus for processing communications in an input/output (I/O) processing system, comprising:
a control unit capable of commanding and determining status of an I/O device, the control unit configured to communicate with a channel subsystem of a host computer system via a channel path, the control unit configured to perform:
sending a message in a command mode to the channel subsystem, the command mode using a first protocol that supports Channel Command Word (CCW) channel programs configured to support at least one CCW that specifies a command for performing an I/O operation;
receiving a command in a transport mode from the channel subsystem, the transport mode using a second protocol that supports Transport Control Word (TCW) channel programs configured to support at least one transport command control block (TCCB), the TCCB configured to hold a plurality of commands for performing an I/O operation;
determining whether the command is responsive to the message;
determining that a ships passing condition has occurred between the channel subsystem and the control unit based on the command being not responsive to the message and the command being sent on the same logical path as the message; and
based on determining that the ships passing condition has occurred, determining whether to perform one of i) executing the command and ii) terminating the command.
8. The apparatus of claim 7, further comprising at least one of i) receiving the command on a first exchange, ii) sending the message on a second exchange, and iii) awaiting a response message from the channel subsystem on a third exchange.
9. The apparatus of claim 8, wherein determining is responsive to the response message received from the channel subsystem.
10. The apparatus claim 8, further comprising:
setting a time period for receipt of the response message, and
responsive to expiration of the time period without receiving the response message, aborting the first exchange and the second exchange.
11. The apparatus of claim 7, wherein:
sending the message comprises opening a first exchange and sending a status message in a command mode on the first exchange and setting a time period for receipt of a response message from the channel subsystem in response to the status message;
receiving the command comprises receiving the command in a transport mode on a second exchange; and
determining whether to perform comprises:
awaiting a response message from the channel subsystem in the command mode on a third exchange; and
responsive to the response message, determining whether to perform one
of i) executing the command and ii) terminating the command, and sending a response message in the transport mode on the second exchange in response to the command, the response message comprising at least one of: an indication of execution of the command, and a device status.
12. A method of processing communications between a control unit and a channel subsystem in an input/output (I/O) processing system, the method comprising:
sending a message in a command mode from the control unit to the channel subsystem of a host computer system, the control unit configured to control an I/O device and receive information from the host computer system and the control unit via a channel path, the command mode using a first protocol that supports Channel Command Word (CCW) channel programs configured to support at least one CCW that specifies a command for performing an I/O operation;
receiving, by the control unit, a command in a transport mode from the channel subsystem at the control unit, the transport mode using a second protocol that supports Transport Control Word (TCW) channel programs configured to support at least one transport command control block (TCCB), the TCCB configured to hold a plurality of commands for performing an I/O operation;
determining, by the control unit, whether the command is responsive to the message;
determining, by the control unit, that a ships passing condition has occurred between the channel subsystem and the control unit based on the command being not responsive to the message and the command being sent on the same logical path as the message; and
based on determining that the ships passing condition has occurred, determining by the control unit whether to perform one of i) executing the command and ii) terminating the command.
13. The method of claim 12, further comprising at least one of i) receiving the command on a first exchange, ii) sending the message on a second exchange, and iii) awaiting a response message from the channel subsystem on a third exchange.
14. The method of claim 12, wherein:
sending the message comprises opening a first exchange and sending a status message in a command mode on the first exchange and setting a time period for receipt of a response message from the channel subsystem in response to the status message;
receiving the command comprises receiving the command in a transport mode on a second exchange; and
determining whether to perform comprises:
awaiting a response message from the channel subsystem in the command mode on a third exchange; and
responsive to the response message, determining whether to perform one
of i) executing the command and ii) terminating the command, and sending a response message in the transport mode on the second exchange in response to the command, the response message comprising at least one of: an indication of execution of the command, and a device status.
15. The computer program product of claim 1, wherein the message is unsolicited, and the method further comprises:
receiving a stack status message in response to the message, the stack status message indicating to the control unit that the message is not accepted.
16. The computer program product of claim 1, wherein the determining comprises detecting the ships passing mode, the ships passing mode comprising the message and the command indicating an identical device address field value and an identical logical path value.
17. The apparatus of claim 7, wherein the message is unsolicited, and the method further comprises:
receiving a stack status message in response to the message, the stack status message indicating to the control unit that the message is not accepted.
18. The apparatus of claim 7, wherein the determining comprises detecting the ships passing mode, the ships passing mode comprising the message and the command indicating an identical device address field value and an identical logical path value.
19. The method of claim 12, wherein the message is unsolicited, and the method further comprises:
receiving a stack status message in response to the message, the stack status message indicating to the control unit that the message is not accepted.
20. The method of claim 12, wherein the determining comprises detecting the ships passing mode, the ships passing mode comprising the message and the command indicating an identical device address field value and an identical logical path value.
Patent Citations (198)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3943283(A) | 1976-03-01 | Caragliano et al. | Applicant |
| US4004277(A) | 1977-01-01 | Gavril | Applicant |
| US4380046(A) | 1983-04-01 | Frosch et al. | Applicant |
| US4414644(A) | 1983-11-01 | Tayler | Applicant |
| US4760518(A) | 1988-07-01 | Potash et al. | Applicant |
| US4779188(A) | 1988-10-01 | Gum et al. | Applicant |
| US4837677(A) | 1989-06-01 | Burrus, Jr. et al. | Applicant |
| US4866609(A) | 1989-09-01 | Calta et al. | Applicant |
| US4870566(A) | 1989-09-01 | Cooper et al. | Applicant |
| US5016160(A) | 1991-05-01 | Lambeth et al. | Applicant |
| US5031091(A) | 1991-07-01 | Wakatsuki et al. | Applicant |
| US5040108(A) | 1991-08-01 | Kanazawa | Applicant |
| US5325492(A) | 1994-06-01 | Bonevento et al. | Applicant |
| US5386512(A) | 1995-01-01 | Crisman et al. | Applicant |
| US5410727(A) | 1995-04-01 | Jaffe et al. | Applicant |
| US5440729(A) | 1995-08-01 | Kimura et al. | Applicant |
| US5461721(A) | 1995-10-01 | Cormier et al. | Applicant |
| US5463736(A) | 1995-10-01 | Elko et al. | Applicant |
| US5465359(A) | 1995-11-01 | Allen et al. | Applicant |
| US5500942(A) | 1996-03-01 | Eickemeyer et al. | Applicant |
| US5517670(A) | 1996-05-01 | Allen et al. | Applicant |
| US5526484(A) | 1996-06-01 | Casper et al. | Applicant |
| US5528755(A) | 1996-06-01 | Beardsley et al. | Applicant |
| US5539918(A) | 1996-07-01 | Allen et al. | Applicant |
| US5561809(A) | 1996-10-01 | Elko et al. | Examiner |
| US5584039(A) | 1996-12-01 | Johnson et al. | Applicant |
| US5600793(A) | 1997-02-01 | Nord | Applicant |
| US5608898(A) | 1997-03-01 | Turpin et al. | Applicant |
| US5613163(A) | 1997-03-01 | Marron et al. | Applicant |
| US5758190(A) | 1998-05-01 | Johnson et al. | Applicant |
| US5768620(A) | 1998-06-01 | Johnson et al. | Applicant |
| US5787071(A) | 1998-07-01 | Basso et al. | Applicant |
| US5831985(A) | 1998-11-01 | Sandorfi | Applicant |
| US5894583(A) | 1999-04-01 | Johnson et al. | Applicant |
| US5901327(A) | 1999-05-01 | Ofek | Applicant |
| US5918028(A) | 1999-06-01 | Silverthorn et al. | Applicant |
| US6125399(A) | 2000-09-01 | Hamilton | Applicant |
| US6202095(B1) | 2001-03-01 | Beardsley et al. | Applicant |
| US6230218(B1) | 2001-05-01 | Casper et al. | Examiner |
| US6338105(B1) | 2002-01-01 | Niizuma et al. | Applicant |
| US6343335(B1) | 2002-01-01 | Dahman et al. | Applicant |
| US6347334(B1) | 2002-02-01 | Fredericks et al. | Applicant |
| US6353612(B1) | 2002-03-01 | Zhu et al. | Applicant |
| US6401223(B1) | 2002-06-01 | DePenning | Applicant |
| US6466590(B1) | 2002-10-01 | Park et al. | Applicant |
| US6484217(B1) | 2002-11-01 | Fuente et al. | Applicant |
| US6546435(B1) | 2003-04-01 | Yoshimura et al. | Applicant |
| US6584511(B1) | 2003-06-01 | Marsh, III et al. | Applicant |
| US6594785(B1) | 2003-07-01 | Gilbertson et al. | Applicant |
| US6609161(B1) | 2003-08-01 | Young | Applicant |
| US6609165(B1) | 2003-08-01 | Frazier | Applicant |
| US6647016(B1) | 2003-11-01 | Isoda et al. | Applicant |
| US6651125(B2) | 2003-11-01 | Maergner et al. | Applicant |
| US6654954(B1) | 2003-11-01 | Hicks | Applicant |
| US6658603(B1) | 2003-12-01 | Ward | Applicant |
| US6687766(B1) | 2004-02-01 | Casper et al. | Applicant |
| US6693880(B2) | 2004-02-01 | Gregg et al. | Applicant |
| US6694390(B1) | 2004-02-01 | Bogin et al. | Applicant |
| US6751680(B2) | 2004-06-01 | Langerman et al. | Applicant |
| US6772207(B1) | 2004-08-01 | Dorn et al. | Applicant |
| US6826661(B2) | 2004-11-01 | Umbehocker et al. | Applicant |
| US6839773(B2) | 2005-01-01 | Vishlitzky et al. | Applicant |
| US6862322(B1) | 2005-03-01 | Ewen et al. | Applicant |
| US6877043(B2) | 2005-04-01 | Mallory et al. | Applicant |
| US6882634(B2) | 2005-04-01 | Bagchi et al. | Applicant |
| US6910149(B2) | 2005-06-01 | Perloff et al. | Applicant |
| US6915378(B2) | 2005-07-01 | Roberti | Applicant |
| US6922548(B1) | 2005-07-01 | Moore et al. | Examiner |
| US6963940(B1) | 2005-11-01 | Glassen et al. | Applicant |
| US7000036(B2) | 2006-02-01 | Carlson et al. | Applicant |
| US7003700(B2) | 2006-02-01 | Elko et al. | Applicant |
| US7020810(B2) | 2006-03-01 | Holman | Applicant |
| US7035540(B2) | 2006-04-01 | Finan et al. | Applicant |
| US7046665(B1) | 2006-05-01 | Walrand et al. | Applicant |
| US7058735(B2) | 2006-06-01 | Spencer | Applicant |
| US7100096(B2) | 2006-08-01 | Webb, Jr. et al. | Applicant |
| US7111130(B2) | 2006-09-01 | Blake et al. | Applicant |
| US7120728(B2) | 2006-10-01 | Krakirian et al. | Applicant |
| US7124207(B1) | 2006-10-01 | Lee et al. | Applicant |
| US7133988(B2) | 2006-11-01 | Fujibayashi | Applicant |
| US7142520(B1) | 2006-11-01 | Haverinen et al. | Applicant |
| US7149823(B2) | 2006-12-01 | Miller et al. | Applicant |
| US7155569(B2) | 2006-12-01 | Johnson et al. | Applicant |
| US7164425(B2) | 2007-01-01 | Kwak et al. | Applicant |
| US7202801(B2) | 2007-04-01 | Chou | Applicant |
| US7266296(B2) | 2007-09-01 | Ovadia et al. | Applicant |
| US7277387(B2) | 2007-10-01 | Sanders et al. | Applicant |
| US7292597(B2) | 2007-11-01 | Mills et al. | Applicant |
| US7315911(B2) | 2008-01-01 | Davies et al. | Applicant |
| US7395284(B2) | 2008-07-01 | Sato et al. | Applicant |
| US7398335(B2) | 2008-07-01 | Sonksen et al. | Applicant |
| US7484021(B2) | 2009-01-01 | Rastogi et al. | Applicant |
| US7500030(B2) | 2009-03-01 | Hathorn et al. | Applicant |
| US7539777(B1) | 2009-05-01 | Aitken | Applicant |
| US7543087(B2) | 2009-06-01 | Philbrick et al. | Applicant |
| US7555554(B2) | 2009-06-01 | Manders et al. | Applicant |
| US7558827(B2) | 2009-07-01 | Kawashima et al. | Applicant |
| US7564791(B2) | 2009-07-01 | Jayakrishnan et al. | Applicant |
| US7577772(B2) | 2009-08-01 | Sonksen et al. | Applicant |
| US7577773(B1) | 2009-08-01 | Gandhi et al. | Applicant |
| US7594057(B1) | 2009-09-01 | Gandhi et al. | Applicant |
| US7599360(B2) | 2009-10-01 | Edsall et al. | Applicant |
| US7743197(B2) | 2010-06-01 | Chavan et al. | Applicant |
| US7765336(B2) | 2010-07-01 | Butler et al. | Applicant |
| US7826349(B2) | 2010-11-01 | Kaur et al. | Applicant |
| US7840717(B2) | 2010-11-01 | Flanagan et al. | Applicant |
| US7840718(B2) | 2010-11-01 | Ricci et al. | Applicant |
| US7840719(B2) | 2010-11-01 | Casper et al. | Applicant |
| US7856511(B2) | 2010-12-01 | Ricci et al. | Applicant |
| US7941570(B2) | 2011-05-01 | Flanagan et al. | Applicant |
| US8495253(B2) | 2013-07-01 | Flanagan et al. | Applicant |
| US2001/0030943(A1) | 2001-10-01 | Gregg et al. | Applicant |
| US2002/0062407(A1) | 2002-05-01 | Tateyama et al. | Applicant |
| US2002/0099967(A1) | 2002-07-01 | Kawaguchi | Applicant |
| US2002/0178404(A1) | 2002-11-01 | Austen et al. | Applicant |
| US2003/0002492(A1) | 2003-01-01 | Gallagher et al. | Applicant |
| US2003/0056000(A1) | 2003-03-01 | Mullendore et al. | Applicant |
| US2003/0084213(A1) | 2003-05-01 | Brice, Jr. et al. | Applicant |
| US2003/0158998(A1) | 2003-08-01 | Smith | Applicant |
| US2003/0188053(A1) | 2003-10-01 | Tsai | Applicant |
| US2003/0208581(A1) | 2003-11-01 | Behren et al. | Applicant |
| US2004/0030822(A1) | 2004-02-01 | Rajan et al. | Applicant |
| US2004/0054776(A1) | 2004-03-01 | Klotz et al. | Applicant |
| US2004/0113772(A1) | 2004-06-01 | Hong Chou | Applicant |
| US2004/0136241(A1) | 2004-07-01 | Rapp et al. | Applicant |
| US2004/0151160(A1) | 2004-08-01 | Sanders et al. | Applicant |
| US2004/0193968(A1) | 2004-09-01 | Dugan et al. | Applicant |
| US2004/0210719(A1) | 2004-10-01 | Bushey et al. | Applicant |
| US2004/0260851(A1) | 2004-12-01 | Tu | Applicant |
| US2005/0018673(A1) | 2005-01-01 | Dropps et al. | Applicant |
| US2005/0102456(A1) | 2005-05-01 | Kang | Applicant |
| US2005/0105456(A1) | 2005-05-01 | Cookson et al. | Applicant |
| US2005/0108251(A1) | 2005-05-01 | Hunt | Applicant |
| US2005/0175341(A1) | 2005-08-01 | Ovadia | Applicant |
| US2005/0193029(A1) | 2005-09-01 | Rom et al. | Applicant |
| US2005/0204069(A1) | 2005-09-01 | Carlson et al. | Applicant |
| US2005/0223291(A1) | 2005-10-01 | Zimmer et al. | Applicant |
| US2005/0229033(A1) | 2005-10-01 | Tanaka et al. | Applicant |
| US2005/0257118(A1) | 2005-11-01 | Shien | Applicant |
| US2006/0036769(A1) | 2006-02-01 | Frey et al. | Applicant |
| US2006/0050726(A1) | 2006-03-01 | Ahmed et al. | Applicant |
| US2006/0085595(A1) | 2006-04-01 | Slater | Applicant |
| US2006/0159112(A1) | 2006-07-01 | Sundaram et al. | Applicant |
| US2006/0224795(A1) | 2006-10-01 | Muto et al. | Applicant |
| US2007/0005838(A1) | 2007-01-01 | Chang et al. | Applicant |
| US2007/0016554(A1) | 2007-01-01 | Dapp et al. | Applicant |
| US2007/0061463(A1) | 2007-03-01 | Hiramatsu et al. | Examiner |
| US2007/0072543(A1) | 2007-03-01 | Paila et al. | Applicant |
| US2007/0079051(A1) | 2007-04-01 | Tanaka et al. | Applicant |
| US2007/0091497(A1) | 2007-04-01 | Mizuno et al. | Applicant |
| US2007/0162631(A1) | 2007-07-01 | Balakrishnan et al. | Applicant |
| US2007/0239944(A1) | 2007-10-01 | Rupanagunta et al. | Applicant |
| US2007/0294697(A1) | 2007-12-01 | Theimer et al. | Applicant |
| US2008/0040519(A1) | 2008-02-01 | Starr et al. | Applicant |
| US2008/0059638(A1) | 2008-03-01 | Hathorn et al. | Examiner |
| US2008/0147889(A1) | 2008-06-01 | Casper et al. | Examiner |
| US2008/0147890(A1) | 2008-06-01 | Casper et al. | Applicant |
| US2008/0183877(A1) | 2008-07-01 | Carlson et al. | Applicant |
| US2008/0235553(A1) | 2008-09-01 | Chintada | Applicant |
| US2008/0273518(A1) | 2008-11-01 | Pratt | Applicant |
| US2008/0307122(A1) | 2008-12-01 | Butler et al. | Applicant |
| US2009/0049241(A1) | 2009-02-01 | Ohno et al. | Applicant |
| US2009/0055585(A1) | 2009-02-01 | Fernandes et al. | Applicant |
| US2009/0144586(A1) | 2009-06-01 | Casper et al. | Applicant |
| US2009/0172203(A1) | 2009-07-01 | Casper et al. | Applicant |
| US2009/0210557(A1) | 2009-08-01 | Gainey, Jr. et al. | Applicant |
| US2009/0210559(A1) | 2009-08-01 | Flanagan et al. | Applicant |
| US2009/0210560(A1) | 2009-08-01 | Yudenfriend et al. | Applicant |
| US2009/0210561(A1) | 2009-08-01 | Ricci et al. | Applicant |
| US2009/0210563(A1) | 2009-08-01 | Flanagan et al. | Applicant |
| US2009/0210564(A1) | 2009-08-01 | Ricci et al. | Applicant |
| US2009/0210570(A1) | 2009-08-01 | Bendyk et al. | Applicant |
| US2009/0210571(A1) | 2009-08-01 | Casper et al. | Applicant |
| US2009/0210572(A1) | 2009-08-01 | Yudenfriend et al. | Applicant |
| US2009/0210573(A1) | 2009-08-01 | Yudenfriend et al. | Applicant |
| US2009/0210576(A1) | 2009-08-01 | Casper et al. | Applicant |
| US2009/0210579(A1) | 2009-08-01 | Bendyk et al. | Applicant |
| US2009/0210580(A1) | 2009-08-01 | Bendyk et al. | Applicant |
| US2009/0210581(A1) | 2009-08-01 | Flanagan et al. | Applicant |
| US2009/0210582(A1) | 2009-08-01 | Bendyk et al. | Applicant |
| US2009/0210583(A1) | 2009-08-01 | Bendyk et al. | Applicant |
| US2009/0210584(A1) | 2009-08-01 | Carlson et al. | Applicant |
| US2009/0210585(A1) | 2009-08-01 | Ricci et al. | Applicant |
| US2009/0210768(A1) | 2009-08-01 | Carlson et al. | Applicant |
| US2009/0210769(A1) | 2009-08-01 | Casper et al. | Applicant |
| US2009/0210884(A1) | 2009-08-01 | Ricci et al. | Applicant |
| US2009/0307388(A1) | 2009-12-01 | Tchapda | Applicant |
| US2010/0014526(A1) | 2010-01-01 | Chavan et al. | Applicant |
| US2010/0030919(A1) | 2010-02-01 | Flanagan et al. | Applicant |
| US2010/0030920(A1) | 2010-02-01 | Casper et al. | Applicant |
| US2010/0064072(A1) | 2010-03-01 | Tang et al. | Applicant |
| US2010/0299460(A1) | 2010-11-01 | Wang | Applicant |
| DE3931514 | 1990-03-01 | Applicant | |
| GB1264096 | 1972-02-01 | Applicant | |
| GB2291990 | 1996-02-01 | Applicant | |
| JP63236152 | 1988-10-01 | Applicant | |
| JP2010-140127(A) | 2010-06-01 | Applicant | |
| WO2006102664(A2) | 2006-09-01 | Applicant |
Non-Patent Literature (138)
- Written Opinion and International Search Report for PCT/EP2009/051445 dated Jun. 25, 2009.Applicant
- Written Opinion and International Search Report for PCT/EP2009/051446 dated Jun. 25, 2009.Applicant
- Written Opinion and International Search Report for PCT/EP2009/051462 dated Jul. 1, 2009.Applicant
- Written Opinion and International Search Report for PCT/EP2009/051450 dated Jul. 7, 2009.Applicant
- Written Opinion and International Search Report for PCT/EP2009/051459 dated Jun. 23, 2009.Applicant
- Written Opinion and International Search Report for PCT/EP2009/051463 dated Jul. 22, 2009.Applicant
- Brice, et al.; U.S. Appl. No. 11/464,613; “Flexibility Controlling The Transfer Of Data Between Input/Output Devices And Memory”; filed Aug. 15, 2006; Specification having 23 pages and Drawings having 4 sheets.Applicant
- Casper, et al.; U.S. Appl. No. 11/548,060; “Facilitating Input/Output Processing By Using Transport Control Words To Reduce Input/Output Communications”; filed Oct. 16, 2006; Specification having 32 pages and Drawings having 12 sheets.Applicant
- Casper, et al.; U.S. Appl. No. 11/548,093; “Facilitating Access To Status And Measurement Data Associated With Input/Output Processing”; filed Oct. 16, 2006; Specification having 33 pages and Drawings having 12 sheets.Applicant
- Dauby, et al. “Contention Resolution Between Two Processors”; IBM Technical Disclosure Bulletin; vol. 26; No. 10A; Mar. 1984; 3 pages.Applicant
- DeVeer, J.A.; “Control Frame Multiplexing On Serial I/O Channels”; IBM Technical Disclosure Bulletin; vol. 32; No. 10A; Mar. 1990; pp. 39-40.Applicant
- Golasky, Richard; “Link-Level Error Recovery With Tape Backup”; Dell Power Solutions; Aug. 2005; pp. 88-91.Applicant
- “IBM® z/Architecture Principles of Operation”, Publication No. SA22-7832-05, 6th Edition, Apr. 2007. 1,215 pages separated into 4 electronic attachments.Applicant
- Peterson, David; “Information Technology, Fibre Channel Protocol for SCSI, Fourth Version (FCP-3)”, Draft Proposed American National Standard, Jun. 2004; pp. 1-142.Applicant
- 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.Applicant
- 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.Applicant
- U.S. Appl. No. 12/030,912 Non-Final Office Action dated Mar. 18, 2010.Applicant
- U.S. Appl. No. 12/030,920 Non-Final Office Action dated Feb. 23, 2010.Applicant
- U.S. Appl. No. 12/030,954 Non-Final Office Action dated Jan. 21, 2010.Applicant
- Written Opinion and International Search Report for PCT/EP2009/051461 dated Sep. 22, 2009.Applicant
- U.S. Appl. No. 12/031,201 Non-Final Office Action dated Jan. 25, 2010.Applicant
- International Search Report; International Application No. PCT/EP2009/059184; International Filing Date: Jul. 16, 2009; Date of mailing: Jan. 14, 2010; 9 pages.Applicant
- U.S. Appl. No. 12/030,967 Restriction Requirement Mailed Dec. 29, 2009.Applicant
- ANSI INCITS 433-2007, Information Technology Fibre Channel Link Services (FC-LS), Jul. 2007.Applicant
- Fibre Channel Single Byte Command Code Sets-2 Mapping Protocol (FC-SB-3), T11/Project 1357-D/Rev 1.6, INCITS Mar. 2003.Applicant
- U.S. Appl. No. 12/030,951 Non-Final Office Action dated May 20, 2010.Applicant
- U.S. Appl. No. 12/031,038, Non-Final Office Action Mailed Apr. 15, 2010.Applicant
- U.S. Appl. No. 12/030,975. Final Office Action Mailed May 13, 2010.Applicant
- U.S. Appl. No. 12/030,967, Notice of Allowance mailed Apr. 23, 2010.Applicant
- U.S. Appl. No. 12/030,985, Non Final Office Action Mailed May 5, 2010.Applicant
- U.S. Appl. No. 12/031,042, Non-Final Office Action Mailed Apr. 5, 2010.Applicant
- U.S. Appl. No. 12/031,021, Notice of Allowance Mailed Apr. 30, 2010.Applicant
- U.S. Appl. No. 12/183,305, Non-Final Office Action Mailed May 11, 2010.Applicant
- U.S. Appl. No. 12/183,315 Notice of Allowance dated Jun. 15, 2010.Applicant
- U.S. Appl. No. 12/030,989 Final Office Action dated May 24, 2010.Applicant
- SCSI Primary Commands-4 (SPC-4); Project T10/1731-D. Rev 11. INCITS Apr. 14, 2010.Applicant
- “Information Technology—Fibre Channel Protocol for SCSI, Third Version (FCP-3),” T10 Project 1560-D, Revision 4g, Sep. 13, 2005.Applicant
- U.S. Appl. No. 12/031,038 Non-Final Office Action dated Nov. 16, 2009.Applicant
- U.S. Appl. No. 12/030,975 Non-Final Office Action dated Oct. 22, 2009.Applicant
- U.S. Appl. No. 12/030,932 Non-Final Office Action dated Dec. 16, 2009.Applicant
- U.S. Appl. No. 12/031,023 Non-Final Office Action dated Oct. 29, 2009.Applicant
- U.S. Appl. No. 12/030,951 Non-Final Office Action dated Nov. 23, 2009.Applicant
- U.S. Appl. No. 12/030,961 Non-Final Office Action dated Dec. 17, 2009.Applicant
- U.S. Appl. No. 12/030,939 Non-Final Office Action dated Nov. 16, 2009.Applicant
- U.S. Appl. No. 12/030,989 Non-Final Office Action dated Oct. 22, 2009.Applicant
- U.S. Appl. No. 12/030,993 Non-Final Office Action dated Oct. 28, 2009.Applicant
- U.S. Appl. No. 12/031,021 Non-Final Office Action dated Jan. 8, 2010.Applicant
- U.S. Appl. No. 12/181,662—Non-Final Office Action dated Jun. 18, 2009.Applicant
- U.S. Appl. No. 12/181,662—Final Office Action dated Jan. 4, 2010.Applicant
- Iren, et al.; “The Transport Layer: Tutorial and Survey”; ACM Computing Surveys; vol. 31, No. 4; Dec. 1999; pp. 360-405.Applicant
- International Search Report and Written Opinion for PCT/EP2009/051447 dated Jul. 1, 2009.Applicant
- International Search Report and Written Opinion for PCT/EP2009/051483 dated Jul. 27, 2009.Applicant
- Nordstrom.; “Sequence Reception Method for a Fibre Channel Protocol Chip”; IBM Technical Disclosure Bulletin; vol. 38, No. 12; Dec. 1995; pp. 267-269.Applicant
- U.S. Appl. No. 11/548,060 Non-Final Office Action dated Apr. 15, 2008.Applicant
- U.S. Appl. No. 11/548,093 Non-Final Office Action dated Apr. 17, 2008.Applicant
- “Protocol for Insochronous Traffic Over Fiber Channel Switching”; IBM Technical Disclosure Bulletin; vol. 37, No. 06B; Jun. 1994. pp. 377-380.Applicant
- Sachs, M.W.; “I/O Marker Changing”; IBM Technical Disclosure Bulletin; vol. 37, No. 02A; Feb. 1994; pp. 75-76.Applicant
- 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, Proceedings of the 1991 ACM/IEEE conference on Supercomputing, Albuquerque, New Mexico; Jul. 1991; pp. 150-157.Applicant
- Srikrishnan et al.; “Sharing FCP Adapters Through Virtualization”; IBM J. Res. & Dev., vol. 51, No. 1/2; Jan./ Mar. 2007; pp. 103-118.Applicant
- Stone, et al.; “When The CRC and TCP Checksum Disagree”; SIGCOMM '00, Stockholm, Sweden; Jul. 2000; 10 pages.Applicant
- U.S. Appl. No. 12/183,315, filed Jul. 31, 2008.Applicant
- U.S. Appl. No. 12/183,323, filed Jul. 31, 2008.Applicant
- U.S. Appl. No. 12/183,305, filed Jul. 31, 2008.Applicant
- “z/Architecture—Principles of Operation,” IBM Publication No. SA22-7832-04, 5th Ed., Sep. 2005.Applicant
- Behrs, JR, “Adaptive Prediction Minimizes Data Overrun and Underrun”, IBM, Nov. 1994, pp. 1-3. http://priorartdatabase.com/IPCOM/000114189.Applicant
- U.S. Appl. No. 12/031,038, Notice of Allowance Mailed Oct. 6, 2010.Applicant
- Final Office Action for U.S. Appl. No. 12/030,912 mailed Oct. 6, 2010.Applicant
- U.S. Appl. No. 12/030,920 Notice of Allowance Mailed Aug. 23, 2010.Applicant
- U.S. Appl. No. 12/030,975, Notice of Allowance Mailed Oct. 19, 2010.Applicant
- U.S. Appl. No. 12/030,932, Final Office Action Mailed Jul. 23, 2010.Applicant
- U.S. Appl. No. 12/030,951, Final Office Action Mailed Oct. 26, 2010.Applicant
- U.S. Appl. No. 12/030,961 Notice of Allowance Mailed Nov. 5, 2010.Applicant
- U.S. Appl. No. 12/030,967 Notice of Allowance Mailed Oct. 7, 2010.Applicant
- U.S. Appl. No. 12/031,201, Final Office Action Mailed Aug. 3, 2010.Applicant
- U.S. Appl. No. 12/031,042, Final Office Action Mailed Oct. 25, 2010.Applicant
- U.S. Appl. No. 12/181,662, Notice of Allowance Mailed Aug. 4, 2010.Applicant
- U.S. Appl. No. 12/364,615, Non Final Office Action Mailed Oct. 7, 2010.Applicant
- U.S. Appl. No. 12/183,305, Notice of Allowance Mailed Nov. 1, 2010.Applicant
- IBM, “Method and Apparatus to Monitor PAV Utilization”, Feb. 2005, pp. 1-3. http://priorartdatabase.com/IPCOM/000082878.Applicant
- Moore et al., Reconfiguration of Storage Elements to Improve Performance, IBM, Dec. 1983, pp. 1-3. http://priorartdatabas.com/IPCOM/000047719.Applicant
- 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.Applicant
- U.S. Appl. No. 12/030,920, Notice of Allowance Mailed Dec. 28, 2010.Applicant
- U.S. Appl. No. 12/030,954, Notice of Allowance mailed Dec. 28, 2010.Applicant
- U.S. Appl. No. 12/030,932, Non-Final Office Action Mailed Dec. 16, 2010.Applicant
- U.S. Appl. No. 12/031,023, Final Office Action Mailed Nov. 18, 2010.Applicant
- U.S. Appl. No. 12/031,201, Non-Final Office Action Mailed Dec. 27, 2011.Applicant
- U.S. Appl. No. 12/030,985, Notice of Allowance mailed Nov. 24, 2010.Applicant
- U.S. Appl. No. 12/030,993, Final Office Action Mailed Dec. 10, 2010.Applicant
- U.S. Appl. No. 12/183,315, Notice of Allowance Mailed Dec. 13, 2010.Applicant
- U.S. Appl. No. 12/183,323, Non-Final Office Action Mailed Jan. 3, 2011.Applicant
- 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.Applicant
- 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.Applicant
- Aboda, B.-et al.; Network Working Group; “Securing Block Storage Protocols Over IP”; ACM Digital Library; RFC3723; Apr. 2004.Applicant
- Azimi, R.-et al.; “miNI: Reducing Network Interface Memory Requirements with Dynamic Handle Lookup”; ACM Digital Library; pp. 261-272; Jun. 2003.Applicant
- Emulex Corporation; “Install the LP850 Host Adapter”; Google/Emulex Corporation, LightPulse LP850 Fibre Channel PCI Host Adapter Manuals; pp. 1-10, 1999.Applicant
- Foong, A.-et al.; “Towards SSD-Ready Enterprise Platforms”; Google/Intel Corporation; 2008-2009.Applicant
- Hewlett-Packard Company; HP A4800A PCI FWD SCSI Host Bus Adapter—Service & User Guide, Edition 6; Google/H-P; 2001.Applicant
- Hewlett-Packard Company; “HP A5149 PCI Ultra2 SCSI Host Bus Adapter—Service and User Guide”, Edition 2; Google/H-P; 2001.Applicant
- U.S. Appl. No. 12/030,951, Notice of Allowance Mailed Apr. 4, 2011.Applicant
- U.S. Appl. No. 12/364,615, Notice of Allowance Mailed Mar. 10, 2011.Applicant
- Jiang, J.-et al.; “The Role of FCoE in I/O Consolidation”; ACM Digital Library/International Conf on Advanced Infocomm Technology '08; Jul. 2008.Applicant
- Josephson, WK.-et al.; “DFS: A File System for Virtualized Flash Storage”; ACM Digital Library; vol. 6, No. 3, Article 14, Sep. 2010.Applicant
- LSI Corporation; “PCI Express to 6Gb/s SAS Host Bus Adapters”; Google; Chapter 1, Introduction/Overview; LSI User Guide; Oct. 2009.Applicant
- LSI; “ScsiPortGetDeivceBase”; Google/LSI; Apr. 2003.Applicant
- Magoutis, K.; “The Optimistic Direct Access File System: Design and Network Interface Support”; Division Of Engineering & Applied Science, Harvard Univ.; Feb. 2002.Applicant
- Miller, DJ.-et al.; “Motivating Future Interconnects: A Differential Measurement Analysis of PCI Latency”; ACM Digital Library; pp. 94-105; Oct. 2009.Applicant
- Network Storage Systems; Google; Oct. 2007.Applicant
- Sun, Oracle; “Sun Storage 6 Gb SAS PCIe HBA, External—Installation Guide for HBA Models”; Google; Revision A; Nov. 2010.Applicant
- Petersen, MK.-et al.; “DIF/DIX Aware Linux SCSI HBA Interface”; Google; Oracle Linux Engineering; Jul. 2008.Applicant
- Satran, J.-et al.; Network Working Group; “Internet Small Computer Systems Interface (iSCSI)”; ACM Digital Library; RFC3720; Apr. 2004.Applicant
- Vaghani, SB.; “Virtual Machine File System”; VMWare Inc./ACM Digital Library; pp. 57-69; 2008-2009.Applicant
- URL, http://en.wikipedia.org/wiki/FICON, FICON, Wikipedia, USA, Wikimedia Foundation, Inc., Aug. 9, 2011.Applicant
- U.S. Appl. No. 13/024,468, Non Final Office Action Mailed Jan. 26, 2012.Applicant
- U.S. Appl. No. 12/030,912 Non Final Office Action Mailed Aug. 18, 2011.Applicant
- U.S. Appl. No. 12/031,182 Final Office Action dated Jun. 10, 2011.Applicant
- U.S. Appl. No. 12/030,925, Notice of Allowance Mailed Feb. 14, 2008.Applicant
- U.S. Appl. No. 13/075,993, Final Office Action Mailed Feb. 13, 2012.Applicant
- U.S. Appl. No. 13/075,993 Non Final Office Action Mailed Aug. 31, 2011.Applicant
- U.S. Appl. No. 12/030,932, Notice of Allowance mailed Nov. 1, 2011.Applicant
- U.S. Appl. No. 12/030,981 Non Final Office Action Mailed Aug. 2, 2011.Applicant
- U.S. Appl. No. 12/030,981, Notice of Allowance mailed Jan. 27, 2012.Applicant
- U.S. Appl. No. 12/031,023, Non-Final Office Action Mailed Feb. 1, 2012.Applicant
- U.S. Appl. No. 12/030,938, Notice of Allowance Mailed Aug. 8, 2011.Applicant
- U.S. Appl. No. 12/031,201 Final Office Action dated Jun. 13, 2011.Applicant
- U.S. Appl. No. 12/030,989, Notice of Allowance Mailed Aug. 5, 2011.Applicant
- U.S. Appl. No. 12/030,993 Notice of Allowance Mailed Dec. 22, 2011.Applicant
- U.S. Appl. No. 12/031,042, Non-Final Office Action Mailed Sep. 30, 2011.Applicant
- U.S. Appl. No. 12/946,514, Non-Final Office Action Mailed Jun. 23, 2011.Applicant
- U.S. Appl. No. 12/183,323, Notice of Allowance Mailed Jun. 23, 2011.Applicant
- U.S. Appl. No. 13/150,583, Non-Final Office Action Mailed Feb. 3, 2012.Applicant
- U.S. Appl. No. 13/173,733, Non-Final Office Action Mailed Feb. 7, 2012.Applicant
- U.S. Appl. No. 13/173,772 Non Final Office Action Mailed Feb. 3, 2012.Applicant
- U.S. Appl. No. 12/030,912, Final Office Action Mailed Feb. 27, 2012.Applicant
- U.S. Appl. No. 13/351,073, Non Final Office Action Mailed Mar. 30, 2012.Applicant
- U.S. Appl. No. 12/031,042, Notice of Allowance Mailed Feb. 29, 2012.Applicant
- U.S. Appl. No. 12/031,023, Notice of Allowance Mailed Jul. 5, 2012.Applicant
- U.S. Appl. No. 13/351,073 Notice of Allowance Mailed Apr. 15, 2013.Applicant
- U.S. Appl. No. 13/833,378, Notice of Allowance Mailed Dec. 6, 2013.Applicant