CA1291576C - Concurrent multi-protocol i/o controller - Google Patents

Concurrent multi-protocol i/o controller

Info

Publication number
CA1291576C
CA1291576C CA000561203A CA561203A CA1291576C CA 1291576 C CA1291576 C CA 1291576C CA 000561203 A CA000561203 A CA 000561203A CA 561203 A CA561203 A CA 561203A CA 1291576 C CA1291576 C CA 1291576C
Authority
CA
Canada
Prior art keywords
control unit
channel
data
controller
control
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
CA000561203A
Other languages
French (fr)
Inventor
Suzanne L. Estrada
Robert R. Ploger, Iii
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
International Business Machines Corp
Original Assignee
International Business Machines Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by International Business Machines Corp filed Critical International Business Machines Corp
Application granted granted Critical
Publication of CA1291576C publication Critical patent/CA1291576C/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/10Program control for peripheral devices
    • G06F13/102Program control for peripheral devices where the programme performs an interfacing function, e.g. device driver
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Abstract

CONCURRENT MULTI-PROTOCOL I/O CONTROLLER
Abstract The improved I/O controller includes a data processing element for executing a sequence of stored program instructions to control the transfer of data between respective ones of a plurality of I/O devices and the host computer. The controller further includes a memory element for storing the program instructions and parameter tables associated with the transfer of data. A first sequence of stored program instructions defines a first communications protocol and a second sequence of stored program instructions defines a second communications protocol. A first control table is associated with a first I/O
device, for relating the first device to the first program instructions and a second control table is associated with a second I/O device, for relating the second I/O device to the second program instructions. The first table is invoked when first data is to be transferred between the first I/O device and a host computer, to call a first program instructions to impose the first communications protocol to govern the transfer of the first data. The second table is invoked when second data is to be transferred between a second, diverse I/O device and the host computer, to call the second program instructions to impose the second communications protocol to govern the transfer of the second data. In this manner, a plurality of communications protocols which are mutually incompatible, can be concurrently executed for communication between a host computer and a plurality of diverse I/O devices.

Description

Description CoNcuRRENT MULTI-PROTOCOL I/O CONTROLLER

8ackground of the Invention 1. Technical Field The invention broadly relates to data processing methods and apparatus and more particularly relates to improvements in I/O control between a communications network and the data processor.
2. Background Art Data communications networks which interconnect data processing nodes, are not only inherently complex, but have evolved into a variety of forms. Information flowing between I/O terminal devices and application programs residing on a remote host computer, require the coordination among the terminal design characteristics, the application requirements, the operating system in the main computer systems, and the characteristics of the communications link. General purpose communications controllers have been developed, containing a stored program front end that can attach to the I/O channel of a host data processor, to provide teleprocessing control functions. Another class of control functions, implemented with software and known as telecommunications access methods, are fundamentally of two types, direct control and queued. For example, the Basic Telecommunications Access Method (BTAM) provides for direct control over telecommunications operations while appropriately interfacing with the operating system of the host computer. The Virtual Telecommunications Access Method (VTAM) was later developed to match the technology advances of virtual memory machines and Synchronous Data Link ~30 Control (SDLC), along with having a compatibility with new programmable communications controllers and providing a facility for distributed processing. VTAM is described in the IBM publication "Virtual Telecommunications Access Method (VTAM) - Concepts and Planning," GC27-6998-3, June 1976.
Additional description can be found in the article by H. R.
Albrecht, et al., "The Virtual Telecommunications Access Method - A Systems Network Architecture Perspective," IBM*Systems Journal, Vol. 15, No. 1, pp. 53-80, 1976. The IBM 3274 control unit is described in the IBM puhlication "An Introduction to *Registered Trade Mark MA~-86-009 -2~ 7~

the IBM 3270 Information Display System," GA27~2739-11, July 1979. Additional description can be found in the IBM
publication "IBM 3270 Information Display System, 3274 Control Unit Planning, Setup and Customizing Guide," GA27-2827-10, June 1982. The Defense Data Network (DDN~ is described in the NTIS
publication AD-~166324 entitled "DDN (Defense Data Network) Protocol Handbook," Vol. 1, DoD Military Standard Protocols, December 1985 by E. ~. Feinler, et al., and its companion volumes 2 and 3. Additional information can be found in the NTIS publication AD-A137427 "Defense Data Network X.25 Host Interface Specification," December 1983. An overall telecommunications architecture plan known as Systems Network Architecture (SNA) significantly advanced the state of the art in teleprocessing software systems by providing a unified design for the functions and structure of data communications - products. SNA and SDLC are described in detail in the book by R. J. Cypser r "Communications Architecture for Distributed Systems," Addison Wesley Publishing Co., Reading, Massachusetts, 1978. SNA is also described in the publication nSNA Technical Overview," order No. GC30-3073, published by the IBM Corporation and available through IBM branch offices.
second major communications network architecture has evolved, known as the Defense Data Network (DDN) which consists of a packet-switched network providing data communications services between remote data processing hosts and terminals. DDN is described in the IBM publication "Virtual Telecommunications Access Method (VTAM) - Concepts and Planning," GC27-6998-3, June 1976. Additional description can be found in the ~rticle by El. R. Albrecht, et al., "The Virtual Telecommunications Access Method - A Systems Network Architecture Perspective,"
IBM Systems Journal, Vol. 15, No. 1, pp. 53-80, 1976. The IBM
3274 control unit is described in the IBM publication "An Introduction to the IBM 3270 Information Display System,"
GA27-2739-11, July 1979. Additional description can be found in the IBM publication "IBM 3270 Information Display System, 3274 Control Unit Planning, Setup and Customizing Guide,"
GA27-2827-10, June 1982. The Defense Data Network (DDN) is described in the NTIS publication AD-A166324 entitled l'DDN
(Defense Data Network) Protocol Handbook,'' ~lol~ 1, DoD Military 40` Standard Protocols, December 1985 by E. J. Feinler, et al.~ and its companion volumes 2 and 3. Additional information can be found in the NTIS publication AD-A137427 "Defense Data Network X.25 Host Interface Specification," December 1983. These two ~3~ ~ 57~

major data communications architectures have incompatible protocols which prevents communications between machines designed for either one ox the other type oE architecture.
Prior art I/O control units attached to an I/O channel of a S host computer using the SNA-type protocol, cannot communicate with the non-SNA-type protocols and methodologies. For example, a terminal user on an IBM 3270 terminal conventionally attaches to host applications over an IBM 3274 control unit, but IBM 3274 control units are not compatible with Defense Data Network communication protocols and cannot operate using them.
What is desired is a programmable I/O controller which can concurrently handle a plurality of communications protocols between a host computer and two or more diverse and mutually incompatible data communications architectures.

Objects of the Invention It is therefore an object of the invention to provide an improved I/O controllex.
It is another object of the invention to provide an improved I/O controller which concurrently handles a plurality of communications protocols.
It is yet a further object of the invention to provide an improved programmable I/O controller which concurrently handles a plurality of communications protocols between a host computer and a plurality of diverse I/O devices.

Summary of the Invention These and other objects, features and advantages of the invention are accomplished by the concurrent multi protocol I/O
controller disclosed herein. The improved I/O controller includes a data processing e]ement for executing a sequence of stored program instructions to control the transfer of data between respective ones of a plurality of I/O devices and the host computer. The controller further includes a memory element for storing the program instructions and parameter tables associated with the transfer of data. A first sequence of stored program instructions defines a first communications protocol and a second sequence of stored program instructions - flefines a second communications protocol. A first control table is associated with a first I/O device, for relating the first device to the first program instructions and a second control table is associated with a second I/O device, for relating the second I/O device to the second program _4 ~29~S76 instructions. The first ta~le is invoked when first data is to be transferred between the first I/O device and a host computer, to call a first program instructions to impose the first communicationS protocol to govern the transfer of the first data. The second table is invoked when second data is to be transferred between a second, diverse I/O device and the host computer, to call the second program instructions to impose the second communications protocol to govern the transfer of the second data. In this manner, a plurality of communications protocols which are mutually incompatible, can be concurrently executed for communication between a host computer and a plurality of diverse I/O devices.
..
8rief Description of the Drawings These and other objects, features and advantages of the invention will be more fully appreciated with reference to the accompanying figures.
Fig. 1 is a system block diagram of the overall structure of a host computer connected through its I/O channel to an I/O
controller.
Fig. 2 is a system block diagram of the interconnection of a host computer through its I/O channel to the programmable I/O
controller, in accordance with the invention.
Fig. 3 is a more detailed block diagram of the programmable I/O controller in accordance with the invention.
Fig. ~ is a detailed block diagram of the programmable I/O
controller in accordance with the invention, depicting the paths of connectivity.
Fig. 5 is a block diagram of the interconnection of the programmable I/O controller with a host computer, where the programmable I/O controller is programmed to represent two different control units concurrently, and the host computer is operating under two diffelent host access methods.
Fig. 6 is an implementation example of the invention.

..
Description of the Best Mode for Carrying Out the Invention Fig. 1 is an overall system block diagram of a prior art host data processor con~iguration where the host data processor ICPU) 20 communicates through its I/O channel 22 to one ~_- more I/O control units 24 and 26 which connect to a single type protocol data communications architecture network 28.
The goal of the invention, is to permit the concurrent appearance of more than one control unit type to the host over its channel, using a single physical computer 30 such as an IBM

MA9-86-009 ~2~

Series/l, connected to the network 32, as shown in Fig. 2.
The IBM Series/l is described for example in the IBM
publication "IBM Series/l System Summary, GA34-0035-5," dated 1979. The System/370 architecture is described in tlle IBM
publication "IBM System/370 Principles of Operation,"
GA22-7000, dated 1970. An additional description can be found in the article by R. P. Case, et al. entitled "Architecture of the IBM System/370," CommunicatiOnS of the ACM, 21, 73-96 (1978). Further, this should be done using only one physical connection to the host's channel 22, since only eight physical control units can be attached to a channel and every such connection can be regarded as consumption of a valuable resource in the customer's view, not to mention the additional cost. Specifically, we wish to emulate both IBM 3274 and IBM
37x5 control units; we should also allow, however, for additional control unit types not required at this time but which may become a requirement in the future (for example, the IBM 3088). The IBM 3274 control unit is described in the IBM
publication "Virtual Telecommunications Access Method (VTAM) -Concepts and Plannin~," GC27-6998-3, June 1976. Additional description can be found in the article by H. R. Albrecht, et al., "The Virtual Telecommunications Access Method - A Systems Network Architecture Perspective," IBM Systems Journal, Vol. 15, No. 1, pp. 53-80, 1976. The IBM 3274 control unit is described in the IBM publication "An Introduction to the IBM
3270 Information Display System," GA27-2739-ll, July 1979.
Additional description can be found in the IBM publication "IBM
3270 Information Display System, 3274 Control Unit Plannlng, Setup and Customizing Guide," GA27-2827-10, June 1982, The Defense Data Network (DDN) is described in the NTIS publication AD-A166324 entitled "DD~ (Defense Data Network) Protocol EIandbook," Vol. 1, DoD Military Standard Protocols, December ; 1985 by E. J. Feinler, et al., and its companion volumes 2 and 3. Additional information can be found in the NTIS publication AD-A137427 "Defense Data Network X.25 Host Interface Specification," December 1983.
The possibility of multi-control unit emulation is conditioned upon the fact that the IBM System/370 channel protocol in fact represents two distinct la~rs o~ protocol:
the common protocol and the control unit level protocol. The IBM Series/1 is described for example in the IBM publication "IBM Series/l System Summary, G~34-0035-5," dated 1979. The System/370 architecture is described in the IBM publication MA9-86-009 -6- ~29~5~

"IBM System/370 Principles oE Operation," GA22-7000, dated 1970. An additional description can be found in the article by R. P. Case, et al. entitled "Architecture of the IBM
System/370,'~ Communications of the ACM, 21, 73-96 (1978).
The common protocol includes signal sequences, generic meanings of commands and generic meanings of status representations. This protocol level is the same regardless of control unit type and is formally defined in IBM publication GA22-6974, "IBM System/360 and System/370 Channel to Control Unit Original Equipment Manufacturers' Information."
The second, or control unit level protocol, operates on top of the first protocol but is unlike the first in that the second protocol differs for every different type of control unit. The control unit level of protocol~defines exact meanings to channel commands codes, types, sizes and direction of data transfers, and specific meanings are attributed to status indications presented by the control unit. For example, Le command encoded as hexadecimal 05 means to accept the following host data as an initial program load to an IBM 3705 control unit. The same command to an IBM 3274 control unit is used to pass configuration information as part of bringing that control unit online to VTA~. For an IBM 3272 control unit, x'05' commands the control unit to clear the screen of the addressed display terminal and then display the data which will ~ollow The other key attribute allowing for emulating multiple control units on the physical channel is the inability of the ho.st's channel 22 to actually "see" a physical control unit instead, the channel perceives only devices attached through control units, in the form of a one byte device address. The control unit has no address as such. It simply manages its one or more devices, responding on behalf of that or those devices which it sees selected by the channel 22. Thus, there is no electrical or low level logical significance to the fact that more than one control unit, represented to the channel by more than one device address, can be in fact supported through a single physical connection to the channel interface.
The design to handle concurrent control unit emulation must accommodate both the common interface protocol as well as the disparate behavior of the various control units. To do this, function in the IBM Series/l computer 30 is partitioned along lines that represent the two levels of protocol, as shown in Fig. 3. The common level control handler 34 for the common MA9-86-009 _7_ ~2 ~ 5 76 protocol treats commands and status as generic, and operates the physical interface 36 to the channel 22. On its other side r the common level control 34 multiplexes I/O service from control unit level logic 38, represented by code and tables 40, 42 and 44 unique for each emulated control unit co-resident over the common handler 34.
A common interface i5 supplied between the low level handler 34 and the control unit level code 38 so that dependencies relating to specific and partlcular control unit characteristics reside only in the control unit level code 38.
Control unit code 38 representing different control units may appear at that common interface any time after the system is initialized. It announces its existence to the always resident common code 34 by performing an-open type function, identifying at that time over what address or addresses it wishes to communicate with the host 20, and establishing critical control block addresses to the common code 34 to allow for communication across the interface. Once this connectivity between control unit level code 3~ and addresses on the physical channel interface has been established, the common code 34 will serve as an intermediary, passing host commands, data and control unit status over that connection, as shown in Fig. 4. Because there are 256 possible addresses on the channel 22 interface, there may be that many connections operating concurrently between control unit level logic 38 and host-resident logic in host 20, all handled e~ually by the single instance of the common level handler code 34. Thus the invention allows for as many as 256 control units to be represented by the Series/1 computer 30 for each physical attachment to the host's channel 22, if each emulated control unit represents one address on the channel 22.
Provision is made for multiple use of a single instance of ~;' control unit level code 38. That is, an instance of 3274 control unit emulation code 40 can represent as many 3274 control units as need to be emulated on the physical channel interface. This reduces the storage consumption called for by control unit level code 38. The same is true for 37x5 emulation code 42 or any other control unit emulation code 44.
As stated above, the common logic 34 has the function to manage the physical connection to the channel interface, turning control unit level I/O requests into I/O requests understood by the interfacing hardware on the Series/1 computer 30. It further manages the connections established between the -8~ 576 control unit level l~gic 38, passing received channel comman~s to it and initiating responding I/O requests back to the channel 22 in response. The control unit logic 38 must be characterized to properly support the operations defined for the emulated control unit according to the rules established for that control unit. That is, if an instance of control unit level logic 40 represents an IsM 3274, receipt of the "05"
channel command to it will result in performing the configuration operations normally performed by a real 3274, including setting the number of buffers and their size for subsequent communications with host access methods resident in the host 20. If this same "05" command were received by control unit level logic 42 representing an IBM 3705, the data to be received from the host 20 under the command would be treated as a bootstrap load module for it.
The concurrent multi-protocol control unit function is implemented on the IBM Series/l computer 30 under the Event Driven Executive (EDX) operating system 46. EDS is further described in the IBM publications SC34-0645, "Series/1 Event Driven Executive" and SC34-1705, "EDX Communications and Terminal Application Guide." The common level logic 34 is referred to herein as the Basic Channel Access Method (sCAM) 34. It is coded in Series/1 assembler language and is made an integral part of the EDX I/O control system.
BCAM 34 provides an Application Program Interface (API) 48 to control unit level logic 38, in the form of new Event Driven Language (EDL) instructions. These instructions are "open,"
"close," "read," "write" and "I/O control." Control unit leve7 logic 38 uses these instructions to establish connectivity to the channel 22 and to request the transfer of data and status information to the host 20. A wait/post interface exists on that API 48 and is used to inform the control unit level code 38 of events occurring on the channel interface, including receipt of channel commands directed toward the "owning"
control unit logic 40, 42 or 44. Ownership of a path is determined at the time the control unit logic 38 performs the "open" instruction to BCAM 34. Subsequent to the "open," the issuing control unit logic 40, 42 or 44 has exclusive ownership of the path, including the specified device addrecs on the channel interface. Thus an event such as receipt of a channel command is directed by BCAM 34 to the single instance of control unit level logic 38 which owns the channel address over which the command has arrived, and no other instance of control unit level logic is aware of that event.

MA9-86-009 ~2~

Control unit level logic, such as 327~ emulation lo~ic ~0 or 3705 emulation logic 42, can in turn supply an API ~8 to an actual Series/l device, communication line, or another program within the Series/1. For the DDN implementation, connection i5 made to application programs which provide the protocol conversion and adaptation required for connectivity to the Defense Data Network. Those programs in turn connect to the actual network communications lines, thereby completing the link between the host's access method to the DDN network.
To establish an adaptive design, the implementation of the multi-protocol control unit in the Series/1 includes the means of configuring which control units are to be emulated and over which host channel addresses on each physical connection to the host. This is represented by a three-step process. First, the system programmer, when creating the EDX system for a particular machine, includes BCAM as a component of the operating system. Second, a table represented by a configuration dataset is created defining the physical connection(s) to the host channel(s) and how many paths (device addresses on those physical connections) are to be used.
Third, the system user defines the specific values to be used for the addresses to be "owned" by each type of control unit level logic. This can either be encoded in another table constructed by the system user or can be embedded within the user's application code itself. Although either method is acceptable, the former is suggested to preserve the highly adaptive nature of the implementation. If the latter method is used, each d~fferent installation requires a re-compilation of the user's code.
On the host side, the system programmer follows conventional procedures for defining control units and access methods. Since we are emulating actual control units in the Series/1, no unusual action must be taken by the host system programmer in defining that system. That configuration action requires only that the control units and access methods defined on the host match the configuration as established within the Series/1.
The flexibility and adaptability of the Series/1 in LepreSenting multiple control units concurrently brings with it a certain level of complexity that can be easily understood by the system programmer but may be confusing to an individual responsible for maintenance of the host system. This individual (a Customer Support Representative or CSR~ may have ~9-86-009 -10- ~ 576 difficulty correlatin~ the host system definition which establishes control units such as 3274 and 3705 and nowhere defines a Series/l, while his or her eyes see only a Series/l on the host's channel.
To ease the CSR's problem, we define yet another control unit to operate in the Series/1, referred to numerically as 4950. This emulated control unit has only one function, viz., to serve as the maintenance point within the Series/l against which the CSR executes control unit test programs.
This is to allow a common maintenance strategy for the CSR
irrespective of the number and types of "real" control units emulated by the channel-attached Series/l. That is! the CSR
can execute a certain diagnostic program from the host to Series/1 regardless of control units it is emulating, and that diagnostic program will run successfully if the hardware components of the host, channel and Series/1 are operating correctly.
The control unit called 4950 is made a permanent part of the EDX system in the Series/l and its is always available for these CSR tests. An address on the channel interface is declared (as part of system configuration) for the 4950 connection, and it is this address to which the CSR directs the diagnostic tests. That address is made unavailahle for any application oriented control unit paths that may be operating concurrently.
The 4950 uses the same BCAM API as the other control unit level components which use BCAM. It has its own special understanding of channel commands which of course matches the intended meanings of those commands as implemented in the CSR's diagnostic programs.
As part of the spirit of allowing the concurrent operation of different protocol control units, the CSR can exercise his or her diagnostic tests to the 4950 control unit while the "real" (i.e., 3274/3705) control unit applications continue to run within the same Series/1.
An additional complication arises when more than one communications access method is operating in the host computer, as is illustrated in Fig. 5. The programmable I/O controller 30, in accordance with the invention, can communicate through a common channel interface with two or more different host access methods, for example VTAM 25 and BTAM 25' operating on the host, while the controller represents two or more different control units concurrently communicating with two or more ~A9-86-009 ~ 5~

diverse and mutually incompatible communications network architectures, BT~M is IB~I's Basic Telecommunications Access Method/ a lower level acess method introduced in 1964 to provide more direct control of telecommunications devices.

Detailed Description of the Preferre~ Embodiment The programmable I/O controller 30 can be referred to as a channel attachment device which connects an IBM Series/1 computer to an IBM System/370 I/O channel. In the following example, control blocks are disclosed for providing device descriptions, channel control tables, and buffer control to carry out concurrent multi-protocol operations.

Introduction The programmable I/O controller channel attachment 30 is a two-card attachment which connects a Series/l to a System/370 I/O channel. The programmable I/O controller is capable of emulating a variety of System/370 device types by means of appropriate Series/1 software. The Series/l device driver for the programmable I/O controller will perform the functions required to control communications between the Series/l and the attachment across the I/O interface. The device driver software will also provide a high-level EDL interface to enable Control Unit Emulation Software to use the programmable IjO
controller channel attachment to communicate with the System/370 host. Emulation software for 3272, 3274, 3088 and DDN type control units is provided.

Device Driver Software Components .
The Series/l device driver for the programmable I/O
controller channel attachment is comprised of the following components:
- Configuration Utility - Device Initialization Routine - IO and Interrupt Handler - Clean-up Routine - EDL Application Interface The Configuration Utility is an application program which is invoked by the user to specify site specific information regarding the desired configuration and use of the programmable I/O controller devices on the Series/1 system. This configuration information is similar to that which would normally be provided in the $EDXDEFS dataset during system ~A9-86-009 -12- ~ 576 generation, This will allow changes to be made to the configuration of the programmable I/O controller devices for emulation of the various control unit types without requiring that an EDX sysgen be performed. A Series/1 IPL will be required following use of this utility to enable the Series/l device driver and emulati~n software to reflect the desired configurations.
The Device Initialization Routine is loaded at Series/1 IPL time to build various control blocks and initialize the programmable I/O controller devices. The Device Initialization Routine uses information provided via the Configuration Utility to perform these tasks.
The Application Interface provides a set of EDL
instructions which enable Series/1 programs to communicate with a host using the programmable I/O controller channel attachment. When a Series/l pxogram issues one of these instructions, the user's request is translated and passed to the I/O and Interrupt Handler for execution by the programmable I/O controller. A return code will be passed back to the issuing program indicating success or failure of the requested operation.
The Clean-up Routine is passed control when the EDX -operating system detects a PROGSTOP or performs a $C function.
The Clean-up Routine will determine whether a terminating task was operating any of the subchannels on any of the programmable I/O controller devices and attempt to terminate pending operations and close the subchannel(s) being used.
The I/O and Interrupt Handler, Clean-up Routine, and EDL
Application Interface components of the programmable I/O
controller device driver will be linked together and reside within the EDX supervisor.

Configuration Utility .. . .
The Configuration Utility prompts the user for site specific information concerning the desired configuration of the programmable I/O controller devices located in the Series/l. The input to the configuration utility is formatted and stored in a file for use by the programmable IiO controller Device Initialization Routine.
The user may enter the following information using the utility - For each programmable I/O channel attachment device:
- The Series/1 device address.
- The Device Name, a unique 1-8 character symbolic name which will be assigned to the device.

MA9-&6-009 -13~ S~ ~

- The EDX partition # where control blocks required for use by the progran~able I/O
controller software support will reside.
- Information concerning each of the control units to be configured on the device including:
- The unique 1-6 character symbolic name which will be assigned to the control unit.
- The type of control unit; supported control unit types are 3272, 3274, 3725, 3088 and DDN.
- The base subchannei address of the control unit in hex.
- The subchannel address range in decimal.
Each subchannel configured for a particular control unit will be assigned a symbolic name by appending a two-digit hex number (00-lF) to the name of the corresponding control unit.
The configured subchannels will be numbered in ascending order starting at the base address with '00'~.

EDL Application Interface The following extensions to the EDL language will be supplied to allow applications to access the programmable I/O
controller.
- CPBDEV
- CPBIOCB
- CPBOPEN
- CPBCLOSE
- CPBREAD
- CPBWRITE
- CPBIOCTL

CPBDEV
The CPBDEV statement is the programmable I/O controller .. . . .
device definition statement which is included in the $EDXDEFS
dataset during EDX system generation. One CPBDEV statement should be coded for each programmable I/O controller attachment in the Series/l system. Definitions of devices must be specified sequentially in the system definition dataset.
Syntax~
CPBDEV END=yes no Required: none Optional: END-Defaults: END=NO
Indexable: none MA9-86-009 -14- 1~9~5~6 Operand: Description END= This parameter must be coded YES on the last or only CPBDEV statement in your EDX
system definition dataset.

CPBIOCB
The CPBIOCB statement is used to allocate an I/O control block to be used for interactions with the programmable I/O
controller device over the named subchannel. A unique CPBIOCB
must be allocated for each opened subchannel.
Syntax:
label CPBIOCB
Required: label Optional: none Defaults: none Indexable: none Operand: Description label The name which will be assigned to the ; control block.

CPBOPEN
The CPBOPEN instruction is used to reserve a System/370 subchannel for use by the issuing task. Execution of this instruction enables the specified subchannel and causes it to become responsive to selections on the System/370 interface.
The issuing task should supply the Device Name, Subchannel Name, and Path Identifier information in the CPBlOCB before execution of the CPBOPEN instruction.

Syntax .

label CPBOPEN cpbiocb,ECBADR=,ERROR=,Pl=,P2=,P3=
~; . .
Required: cpbiocb,ECBADR=
Optional: label,ERROR=,Pl=,P2=,P3=
Defaults: none Indexable: cpbiocb,ECBADR=,ERROR=

erand Description label The name assigned to this instruction.
cpbiocb The address of the CPBIOCB associated with the subchannel to be opened for use.
ECBADR= The aadress of the ECB posted when an asynchronous event occurs on the subchannel.

-15- ~ 5~

ERROR= The label of the instruction which i~ to receive con~rol if an error occurs durin~
processing of the CPBOPEN.
P1= The label assigned to the cpbiocb parameter.
P2= The label assigned to the ECBADR=
parameter.
P3= The label assigned to the ERROR=
parameter.

CPBOPEN Return Codes (found at CPBIOCB+18):
Code Condition -1 Successful 1 Device specified is offline 2 Invalid device name specified lS 3 Invalid subchannel name specified Subchannel specified is already in use 2~0 System/370 reset occurred 2~1 Selective reset occurred The CPBCLOSE instruction is used to release a subchannel which was reserved for use with a CPBOPEN instruction.

Syntax: `
label CPBCLOSE cpbiocb,ERROR=,P1=,P2=

Required: cpbiocb Optional: label,ERROR=,P1=,P2=
Defaults: none Indexable: cpbiocb,ERROR=

Operand Description label l'he name assigned to this instruction.
cpbiocb The address of the CPBIOCB associated with the subchannel to be closed.
ERROR= The label of the instruction which is to receive control if an error occurs during processing of the CPBCLOSE.
P1= The label assign~d to the cpbiocb parameter.
P2= The label assigned to the ERROR= parameter.

M~9-86-009 129~57~

CPBCLOSE Return Codes (found at CPBIOCB~18):

Code Condition -1 Successful 4 Invalid I/O control bloek speeified o Subchannel specified is already closed CPBREAD
The CPBREAD instruction is used to pass data from the host to the Series/l. The issuing task must provide the address and key of the Buffer Control Block in ~he CPBIOCB before execution of the CPBREAD. The actual number of bytes transferred is stored in the B~TXTCNT field of the Buffer Control Block upon eompletion of the CPBREAD.

Syntax:
label CPBREAD epbioeb,ERROR=,Pl=,P2=

Required: epbioeb Optional: label,ERROR=,P1=,P2=
Defaults: none Indexable: epbioeb,ERROR=

Operand Description label The name assigned to this instruction.
epbioeb The address of the CPBIOCB assoeiated with the subehannel over whieh the operation is to oeeur.
ERROR= The label of the instruction which is to reeeive eontrol if an error oeeurs during proeessing of the CP~READ.
P1= The label assigned to the epbiocb parameter.
P2= The label assigned to the ECBADR=
parameter.

CPBREAD Return Codes (found at CPBIOCB+18):

Code Condition -1 Suecessful 4 Invalid I/O eontrol bloek specified 6 Subehannel specified is not open 240 System/370 reset oeeurred 241 Seleetive reset occurred 242 Halt I/O received MA9-86-009 -17- ~29~7~

CPBWRITE
The CPBWRITE instruction used is to pass data from the Series/l to the host. The issuing task must provide the address and key of the Buffer Control Block in the CPBIOCB
before execution of the CPBWRITE. The actual number of bytes transferred is stored in the B$TXTCNT fi~ld of the Buffer Control Block upon completion of the CPBWRITE.

Syntax:
label CPBWRITE cpbiocb,ERROR=,Pl=,P2=

Required: cpbiocb Optional: label,ERROR=,P1=,P2=
Defaults: none Indexable: cpbiocb,ERROR=

Operand Description label The name assigned to this instruction.
cpbiocb The address of the CPBIOCB associated with the subchannel over which the operation is to occur.
ERROR= The label of the instruction which is to receive con~rol if an error occurs during processing of the CPBWRITE.
P1- The label assigned to the cpbiocb parameter.
P2= The label assigned to the ECBADR=
parameter.

CPBWRITE Return Codes (found at CPBIOCB~18):

C _ Condition -1 Successful 4 Invalid I/O control block specified 6 Subchannel specified is not open 240 System/370 reset occurred 241 Selective reset occurred 242 Halt I/O received CPBIOCTL
The CPBIOCTL instruction is to present asynchronous status to the host. ~he issuing task must provide the Unit Status Byte to be passed, along with a Unit Sense Byte(s) where appropriate in the CPBIOCB before execution of the CPBIOCTL.

-18- ~ 7~

Synta~:
label CPBIOCTL cpbiocb,ERRO~=,P1=,P2=

Required: cpbiocb Optional: label,ERRO~=,Pl=,P2=
Defaults: none Inde~able: cpbiocb,ERROR=

operand Description label The name assigned to this instruction.
cpbiocb The address of the CPBIOCB associated with the subchannel to be opened for use.
ERROR= The label of the instruction which is to receive control if an erxor occurs during processing of the CPBIOCTL.
P1= The label assigned to the cpbiocb parameter.
P2= The label assigned to the ECBADR=
parameter.

CPBIOCTL Return Codes (found at CPBIOCB+18):

Code Condition -1 Successful Invalid I/O control block specified 6 Subchannel specified is not open 240 System/370 reset occurred 2~1 Selective reset occurred 2~2 Halt I/O received Post Codes A task which has opened a subchannel for use will receive a post to the ECB specified in the CPBOPEN upon the driver's receipt of an async event affectlng the owned subchannel. The Post Code will contain the Path Identifier specified in the CPBOPEN along with an indication of the event which has occurred.

Path ID Event A task opening multiple subchannels for use may specify a unique Path Identifier for each subchannel and the address of a common ECB in the CPBOPEN requests. This will enable the task ~9-86-00~

to wait for work on a common ECB and use the unique Path Identifier to distinguish over which of the owned subchannels the event has occurred. The Path Identifier may be any value in the range 1-255.

Contrcl Blocks:

Device Descriptor Block During system generation, a Device Descriptor Block (CPBDDB) will be created for each programmable I/O controller device specified in the $EDXDEFS system definition dataset.
This DDB has the following format:

A(Interrupt Handler) +2 Device ID - X'3102' lS +4 A(Next CPBDDB) +6 Device Name ~14 A(DDB Extension Control Block) ~16 Key(DDB Extension Control Block) The address of the first CPBDDB will be placed in the EDX
Communications Vector Table to enable programs outside the supervisor to loca-te the DDB. All device specific information will be maintained in a DDB Extension Control Block (CPBDEXB), one of which is allocated for each physical device by the programmable I/O controller device Initialization Routine. The Device Name is specified by the user via the Configuration Utility and installed in the DDB at ini-tialization time as well.

DDB Extension Control Block The DDB Extension Control Block (CPBDEXB) has the following format:

Device Address ~2 AlNext CPBDEXB DDB extension) MA9-86-009 ~ ~ 9 +4 Key(Next CPBDEXB DDB extension) +6 Flags +8 Device IDCB
+12 Device Control Block (DCB) +28 Controller Status Block (CSB) +44 Sync ECB for controller I/O
+50 Queue Control Block (QCB) +60 Number of Subchannels +62 Subchannel Control Table The Subchannel Control Table (SCCT) contains one Subchannel Control Entry (SCCE) for each of the subchannels configured for a particular programmable I/O controller device.

Subchannel Control Entry Each Subchannel Control Entry (SCCE) contains the following information:

0 .
Subchannel Name -~8 Channel Command Subch Address +10 Path Identifier Flags +12 A(User's I/O Control Block) ~14 A(User's Async ECB) ~16 A(User's Task Control Block) +18 User's Instruction Space Key +20 Control Unit Type MA9-86-009 -21- ~9~5~

+2~
Sense Byte(s) +24 Attention Subdevice Status Block +32 Subdevice Status Block +40 Number OL DCBs +42 Device Control Block(s) I/O Control Block The I/O Control Block (CPBIOCB) has the following format:

Device Name +8 Subchannel Name +16 Flags +18 Synchronous ECB for I/O
+24 Path IdentiEier Unit Status -~26 Sense Byte(s) +28 A(Buffer C~ntrol Block) +30 Key(Buffer Control Block) The Device Name field will be replaced by the following upon successful completion of a CPBOPEN:
o Address of DDB Extension +2 Address of SCCE
+4 Key of DDB e~tension, SCCE

MA9-86-oo~
-22 ~ 7~

Buffer Control Block The Buffer Control sloc]c used i5 compatible to the buffer and message headers of the E~X Communications Facility (CF).
The format of the control block is as follows:

B$SIZE

B$COUNT

B$ADDR
B$DATAQ

B$TXTCNT

B$TEXT

Description of the Fields B$SIZE The size, in bytes, of the entire buffer.
B$COUNT The count of the bytes of actual data in the buffer, beginning at B$ADDR.
B$ADDR The address of the first byte of the buffer to be treated as data.
B$DATA@ An address of some data within the buffer.
B$TXTCNT The ac-tual number of bytes transferred during the last CPBRE~D or CPBWRITE operation performed using this Buffer Control Block.
B.~TEXT Normally, the start of text. B$ADDR normally points here. The Buffer Control Block must be loca-ted in the same partition as the data it addresses, but need not be contiguous to the data.
.

Implementation Example In this example, a single Series/l computer 30, representing a single physical connection to a hosting System/370 computer 20 over one of its I/O channels 22, is made to appear as two different types of emulated control unit.
That is, any program in the host would see two individual and dissimilar control units and would be unable to recognize that these are in fact contained in a single machine using a single physical connection to the host's channel. The IBM Series/l is described for example in the IBM publication "IBM Series/l MA 9 - ~3 6 - O O 9 iL~ g~L~i7~

System Summary, GA34-0035-5," dated 1979. The System/370 architecture is described in the IBM publication "IBM
System/370 Principles of Operation," GA22-7000, dated 1970. An additional description can be found in the article by R. P.
Case, et al. entitled ~ArchitectUre of the IBM System/370,"
Communications of the ACM, 21, 73-96 1197~).
A control unit's identity is in part established by the types of channel commands it executes and how it executes them.
In addition, for any real case, it is further defined and known by the address or addresses it represents on the host's channel. Knowing both of these pieces of information, a program in the host can successfully cause I/O to be perfor~ed on the devices or over the communication lines that that control unit manages.
Establishment of a multi-protocol unit therefore requires that the physical machine respond over different addresses, representing the different control units, and that it further execute channel commands in different ways over those different addresses as the desired emulated control units would. This should be done in a way that no interference between the operation of the emulated control units be detectable by the controlling program(s) in the hosting system, despite the fact that all operations are in fact being performed by the common hardware represented by the single physical control unit (which, in this case, is an IBM Series/1).
The following conditions must be obtained for these criteria to be met:

1. The hosting channel uses separate paths (subchannels) in executing channel programs directed to the several addresses -the Series/1 represents.

. The hardware attachment tying the Series/1 to the channel be capable oE concurrent operations over the several addresses the Series/1 represents.

3. That hardware attachment does not attempt to interpret the meaning or ultimate effects of commands directed to the Series/1 from t11e hosting channel.

4. The controlling program(s) in the Series/1 are structured such that the mechanics of operation of the standard channel interface are divorced from the unique behavior expected of the emulated control units.

The example configuration is shown in Fig. 6. In the host CPU, two different access methods are operating the two emulated control units. VTA~I 25 is controlling an emulated 3274A unit 40, a terminal control unit that channel attaches as a Physical Unit type 2 (PU2). DNAM 25'' is controlling a Defense Data Network ccntrol unit 44. The channel 22 is using three unshared subchannels, two for DNAM operations and one for the 3274A. Corresponding to this, the Series/l uses three addresses in answering to 370 channel commands, two for the emulated DNAM control unit 44 and one for the emulated 3274A
unit 40. A common device handler (BCAM) 34 operates the single channel attachment. It represents the access point for two control unit emulation programs, one emulating the DNAM control unit and the other the 3274A. The IBM 3274 control unit is described in the IBM publication "Virtual Telecommunications Access Method (VTAM) - Concepts and Planning," GC27-6998-3, June 1976. Additional description can be found in the article by H. R. Albrecht, et al., "The Virtual Telecommunications Access Method - A Systems Network Architecture Perspective,"
IBM Systems Journal, Vol. 15, No. 1, pp. 53-80, 1976. The IBM
3274 control unlt is described in the IBM publication "An Introduction to the IBM 3270 Information Display System,"
GA27-2739-11, July 1979. Additional description can be found in the IBM publication i'IBM 3270 Information Display System, 3274 Control Unit Planning, Setup and Customizing Guide,"
GA27-2827-10, June 1982. The DeEense Data Network (DDN) is described in the NTIS publication AD-A166324 entitled "DDN
(Defense Data Network) Protocol Handbook," Vol. 1, DoD Military Standard Protocols, December 1985 by E. J. Feinler, et al., and its companion volumes 2 and 3. Additional information can be found in the NTIS publication AD-A137427 "Defense Data Network X.25 Host Interface Specification," December 1983.
In turn, the control unit program representing the DNAM
control unit sends and receives data from a Series/1 attachment connecting to the De~ense Data Network while the control unit program representing the 3274A sends and receives data from another Series/1 attachment serving as a primary station on an SNA SDLC line to a remotely attached real 3274. Systems Network Architecture (SNA) and Synchronous Data Link Control (SDLC) are described in the book by R. J. Cypser, "Communications Architecture for Distribu-ted Systems," Addison Wesley Publishing Company, 1978.

MA9-86-oog ~9~

Control Unit Protocols VTAMt~274~:
The path between VTA~ and a 3274A for passing data and control information is over one subchannel in the channel and one device address in the control unit. Addressing information in the data allows the control unit in turn _o select and control terminals 50 attached to it on line 32. This allows the control of, for example, 32 terminals over a single address on the channel. Data from the terminal to VTAM and data from VTAM to the terminal all must flow over the single device address on the ehannel. This implies a duplex flow on that address, with contention for direetion of flow resolved via mutual agreement between the control unit and VTAM.
(Contention exists beeause data eannot flow both ways under eontrol of a single ehannel eommand, and only one ehannel eommand ean be in execution on a subchannel at any one time.~
To send data from VTAM to the eontrol unit, VTAM starts a ehannel program in the subchannel comprised of a Write Start eommand (which earries no data) ehained to one or more Write eommands (eaeh of whieh eauses a bloek of data ealled a PIU, Path Information Unit) to be sent to the eontrol unit. The eontrol unit, having buffering to eontain these PIUs, aeeepts them and then proeesses them individually. Eaeh PIU is directed to a speeifie terminal, and several terminals may be the reeipient of these several PIUs passed under the common single channel program that VTAM built. If the control unit eannot accept PIUs, a meehanism exists that allows it to tell V1'AM (via control unit status presented when the ehannel eommand is exeeuted) of this. Later, when the eonstraining eondition has cleared, the eontrol unit can signal VTAM that outbound flow ean resume.
Data inbound to VTAM ean be retrieved from the eontrol unit through the execution of another ehannel program which is eomprised of a Read Start eommand ehained to several Read data eommands. Since a control unit cannot initiate a ehannel eommand, it must signal VTAM that read service is required.
Once having signaled this faet, the eontrol unit retains the inbound data until VTAM responds by exeeuting the Read channel progr~m.

DNAM/DDN Control Unit Protocol The DDN control unit operates substantially differently than the 3274A. Instead of one, two subchannels and two device MA9-8G-009 -26- ~9~7~

addresses are used. One is used for outbound data only, and the other is used for inbound data and control.
To send data, DNA~I builds a write channel program which is comprised solely of write commands. The channel program is directed to the device address representing the outbound flow path. One internet datagram is passed under each write command in the channel program. The control unit, being able to accept a datagram, buffers it and then queues it on an X.25 virtual circuit outbound to the network 32'. If unable to accept the data, the control unit signals DNAM, again using control unit status, that it is momentarily unable to accept data from DNAM, and it will later provide an asynchronous indication that the congestion condition has cleared. This is similar to 3274A
outbound data operations, except that there is no contention to be resolved on the device relating to data direction.
Data inbound to DNAM is presented by the control unit to a read channel program built by DNAM. One or more read commands may be present in the read channel program, and one internet datagram is passed against each read command. The read channel program is executed on the inbound subchannel. Since only read type commands exist on this subchannel, there is no contention for direction of data flow, and DNAM may leave a read program permanently in place on the subchannel. This then is a polled type of operation, rather than an attention (request for read) type of operation that must be usecl with the 3274A control unit.

Operation In the Series/l, the control unit emulation program representing the 3274 executes an Open primitive which declares its readiness to operate on the channel. At that time, the device address over which it is to operate is also declared.
BCAM intercepts this request and allocates a control block (a Subchannel Control Entry or SCCE) which it uses to administer the path between the control unit program and the device address it is acquiring~ The SCCE contains information required by BCAM to identify what operations are in progress on that path and where critical addresses are located in the control unit program when indications are to be given relating to events on the specified device address on the channel.
Thus, for example, if VTAM now executes a channel program directed to the acquired device address, BCA~ will signal the owning program that this event has happened. The control unit MA9-86-009 -27- ~ S~ ~

program will in turn perform operations required to support the command directed to it, including developing information relating to where in Series/l storage data is to be moved to or fromr and how much is to be moved. It then executes a BCAM
command which causes the actual data movement to be accomplished. Once the transfer is done, the control unit program is signaled, and it may proceed with whatever additional processing is required to forward the received data (if a channel write operation) or free buffers (if a channel read operation).
This entire process operates independently of any other control unit programs which may be using BCAM's and the channel's services.
In this example, the DNAM~emulating control unit program can independently Open to BCAM. If it attempts to specify a device address on the channel that is already claimed by another program, the request is denied by BCAM. Only one control unit emulation program can claim a device address at any one time. For DNAM, two addresses must be claimed, one for output and one for input. This is done with two Opens to those respective subchannels/device addresses. BCAM, as before, allocates and fills in the SCCE for each address; it is not cognizant of the fact that only one control unit is being represented over both thèse paths, in keeping with the strategy mentioned above of keeping its function independent of specific control unit characteristics.
The DNAM control unit code is signaled by BCAM oE
occurrences on the channel directed to the addresses claimed in its Opens. Its behavior will differ from 327~'s, however, in that no logic is necessary for contention resolution. In fact, the only similarities between the two different control units lies in the necessity that data be both sent and received.
Although a specific embodiment of the invention has been disclosed, it will be understood by those having skill in the art that changes can be made to the disclosed embodiment without departing from the spirit and the scope of the invention.

Claims

The embodiments of the invention in which an exclusive property or privilege is claimed are defined as follows:
1. In a data processing system including a host processor having a channel for communicating commands through a first type I/O control unit to a first terminal or a second terminal having first and second device addresses, respectively, and for communicating commands through a second type I/O control unit to a communications link having a third device address, a multiprotocol I/O
communication controller unit coupled between said channel and said terminals and said communications link, said communication controller unit comprising:
a common level control logic means coupled to said channel, for receiving from said channel a device address value and an associated common command value representing a command;
a control unit level control logic means coupled to said common level control logic means and also coupled to said first terminal, to said second terminal and to said communications link, including a first emulated I/O
controller for controlling said first and said second terminals and including a second emulated I/O controller for controlling said communications link, said common level control logic means including a device address translation table for directing said associated common command value to said first emulated I/O
controller in response to said device address value being either said first or said second device address and for directing said associated common command value to said second emulated I/O controller in response to said device address value being said third device address;

said first emulated I/O controller including a first command translation table for convening said associated common command value to a first type terminal control command, said control unit level control logic means outputting said first type teriminal control command to either said first or said second terminal in response to said device address value being either said first or said second device address, respectively;
said second emulated I/O controller including a second command translation table for converting said associated common command value to a second type communications link control command, said control unit level control logic means outputting said second type communications link control command to said communications link in response to said device address value being said third device address.
CA000561203A 1987-04-29 1988-03-11 Concurrent multi-protocol i/o controller Expired - Fee Related CA1291576C (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US043,798 1987-04-29
US07/043,798 US4855905A (en) 1987-04-29 1987-04-29 Multiprotocol I/O communications controller unit including emulated I/O controllers and tables translation of common commands and device addresses

Publications (1)

Publication Number Publication Date
CA1291576C true CA1291576C (en) 1991-10-29

Family

ID=21928950

Family Applications (1)

Application Number Title Priority Date Filing Date
CA000561203A Expired - Fee Related CA1291576C (en) 1987-04-29 1988-03-11 Concurrent multi-protocol i/o controller

Country Status (5)

Country Link
US (1) US4855905A (en)
EP (1) EP0288713B1 (en)
JP (1) JPS63275243A (en)
CA (1) CA1291576C (en)
DE (1) DE3889766T2 (en)

Families Citing this family (107)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4975869A (en) * 1987-08-06 1990-12-04 International Business Machines Corporation Fast emulator using slow processor
US5021949A (en) * 1988-02-29 1991-06-04 International Business Machines Corporation Method and apparatus for linking an SNA host to a remote SNA host over a packet switched communications network
JPH0235524A (en) * 1988-03-14 1990-02-06 Advanced Micro Devicds Inc Bus convertible programmable sequencer
US4991089A (en) * 1988-09-30 1991-02-05 Ibm Corp. Method for establishing current terminal addresses for system users processing distributed application programs in an SNA LU 6.2 network environment
US4991133A (en) * 1988-10-07 1991-02-05 International Business Machines Corp. Specialized communications processor for layered protocols
US5073852A (en) * 1988-12-16 1991-12-17 Cayman Systems, Inc. Network protocol translator including method and apparatus for reducing interprocess communication and data exchange overhead
US7537167B1 (en) 1993-08-31 2009-05-26 Broadcom Corporation Modular, portable data processing terminal for use in a radio frequency communication network
US5226160A (en) * 1989-07-18 1993-07-06 Visage Method of and system for interactive video-audio-computer open architecture operation
EP0419064A3 (en) * 1989-09-22 1992-08-05 International Business Machines Corporation Computer system having apparatus for providing pointing device independent support in an operating environment
JPH0687569B2 (en) * 1989-09-28 1994-11-02 アメリカン テレフォン アンド テレグラフ カムパニー Terminal adapter and data transmission method
JPH03123244A (en) * 1989-10-06 1991-05-27 Matsushita Electric Ind Co Ltd Communication equipment
US5165022A (en) * 1989-10-23 1992-11-17 International Business Machines Corporation Channel and control unit having a first I/O program protocol for communication with a main processor and a second universal I/O program protocol for communication with a plurality of I/O adapters
US5063523A (en) * 1989-11-16 1991-11-05 Racal Data Communications Inc. Network management system with event rule handling
US7383038B2 (en) * 1990-01-18 2008-06-03 Broadcom Corporation Modular, portable data processing terminal for use in a radio frequency communication network
JPH03229352A (en) * 1990-02-05 1991-10-11 Hitachi Ltd Program changing method
CA2076366C (en) * 1990-03-02 1998-05-26 Michel J. Remion Telecommunication interface apparatus and method
US5379404A (en) * 1990-03-16 1995-01-03 Motorola, Inc. Plug code for automatically recognizing and configuring both non-microprocessor and microprocessor based radio frequency communication devices
CA2047459A1 (en) * 1990-07-20 1992-01-21 Randy J. Longsdorf Apparatus for communicating between systems having different communications standards
US5432795A (en) * 1991-03-07 1995-07-11 Digital Equipment Corporation System for reporting errors of a translated program and using a boundry instruction bitmap to determine the corresponding instruction address in a source program
US5265239A (en) * 1991-04-08 1993-11-23 Ardolino Anthony A Method for remotely accessing service programs of a local processing system supporting multiple protocol stacks and multiple device drivers
JP2930257B2 (en) * 1991-04-22 1999-08-03 株式会社東芝 Portable electronic devices
US5289580A (en) * 1991-05-10 1994-02-22 Unisys Corporation Programmable multiple I/O interface controller
DE4117510A1 (en) * 1991-05-29 1992-12-03 Standard Elektrik Lorenz Ag APPLICATION PROGRAM INTERFACE
US5572675A (en) * 1991-05-29 1996-11-05 Alcatel N.V. Application program interface
JPH05189574A (en) * 1991-07-23 1993-07-30 Internatl Business Mach Corp <Ibm> Method and apparatus for supporting plurality of commands in rendering constituent element
US5386525A (en) * 1991-10-29 1995-01-31 Pacific Bell System for providing application programs with direct addressability into a shared dataspace
US5361336A (en) * 1991-11-21 1994-11-01 Hewlett-Packard Company Method for controlling an instrument through a common instrument programming interface
US5826017A (en) * 1992-02-10 1998-10-20 Lucent Technologies Apparatus and method for communicating data between elements of a distributed system using a general protocol
GB2264374A (en) * 1992-02-24 1993-08-25 Systems Limited Kk Programmable protocol converter.
JP2868141B2 (en) * 1992-03-16 1999-03-10 株式会社日立製作所 Disk array device
US5508821A (en) * 1992-04-09 1996-04-16 Matsushita Electric Industrial Co., Ltd. Image scanner and image forming apparatus with an interface for connection with an external computer
CA2094097C (en) * 1992-04-30 2000-05-30 Ray Balogh Multi-equipment routing method and master station for layered protocol communication network system
WO1993023811A2 (en) * 1992-05-13 1993-11-25 Southwestern Bell Technology Resources, Inc. Open architecture interface storage controller
US5376928A (en) * 1992-09-18 1994-12-27 Thomson Consumer Electronics, Inc. Exchanging data and clock lines on multiple format data buses
JP2541767B2 (en) * 1992-11-12 1996-10-09 インターナショナル・ビジネス・マシーンズ・コーポレイション Smart bus control unit
US5696899A (en) * 1992-11-18 1997-12-09 Canon Kabushiki Kaisha Method and apparatus for adaptively determining the format of data packets carried on a local area network
JP2505974B2 (en) * 1992-12-08 1996-06-12 インターナショナル・ビジネス・マシーンズ・コーポレイション A method for integrating multiple application programs into an integrated graphical user interface processing environment.
US5517635A (en) * 1992-12-17 1996-05-14 International Business Machines Corporation System for designing an application program to be independent of I/O devices by utilizing application name, system name, and predetermined hardware specific parameters of data objects
WO1994015294A1 (en) * 1992-12-23 1994-07-07 Surefind Corporation Interactive computer system with multi-protocol capability
FR2700034B1 (en) * 1992-12-24 1995-03-24 Silicon Ingenierie Communication card intended to allow a serial link between a computer and an external communication system.
US5619650A (en) * 1992-12-31 1997-04-08 International Business Machines Corporation Network processor for transforming a message transported from an I/O channel to a network by adding a message identifier and then converting the message
US5392033A (en) * 1993-01-05 1995-02-21 International Business Machines Corporation Priority generator for providing controllable guaranteed fairness in accessing a shared bus
JP3421378B2 (en) * 1993-03-23 2003-06-30 株式会社東芝 Transmission control method
JP3568970B2 (en) * 1993-04-12 2004-09-22 株式会社東芝 IC card issuing device
US5631935A (en) * 1993-05-06 1997-05-20 Run-Rad Unlimited Networking, Ltd. Method and apparatus for governing information transfer using an efficient transport protocol
US5640517A (en) * 1993-06-22 1997-06-17 Dell Usa, L.P. Method and apparatus for masters to command a slave whether to transfer data in a sequential or non-sequential burst order
JPH0765540A (en) * 1993-08-27 1995-03-10 Olympus Optical Co Ltd Apparatus for controlling data of optical card
US7853254B2 (en) * 1993-08-31 2010-12-14 Broadcom Corp. Modular, portable data processing terminal for use in a radio frequency communication network
JP3670303B2 (en) * 1993-09-01 2005-07-13 富士通株式会社 Data conversion method and data conversion apparatus
US5530897A (en) * 1993-10-01 1996-06-25 International Business Machines Corporation System for dynamic association of a variable number of device addresses with input/output devices to allow increased concurrent requests for access to the input/output devices
US5717855A (en) * 1994-02-28 1998-02-10 International Business Machines Corporation Segmented communications adapter with packet transfer interface
WO1995024683A1 (en) * 1994-03-10 1995-09-14 Apple Computer, Inc. A virtual memory system that is portable between different cpu types
US5717614A (en) * 1994-05-04 1998-02-10 National Instruments Corporation System and method for handling events in an instrumentation system
US5847955A (en) * 1994-05-04 1998-12-08 National Instruments Corporation System and method for controlling an instrumentation system
US6769009B1 (en) * 1994-05-31 2004-07-27 Richard R. Reisman Method and system for selecting a personalized set of information channels
US5694546A (en) 1994-05-31 1997-12-02 Reisman; Richard R. System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest list
GB9414331D0 (en) * 1994-07-15 1994-09-07 Thomson Consumer Electronics Combined I*C and IM bus architecture
FR2723224B1 (en) * 1994-07-28 1996-09-06 Sgs Thomson Microelectronics MEMORY OR CHIP CARD READER SYSTEM
US5845072A (en) * 1994-11-10 1998-12-01 International Business Machines Corporation Method and apparatus for parallel and pipelining transference of data between integrated circuits using a common macro interface
US5657446A (en) * 1994-11-14 1997-08-12 Mitel Corporation Local area communications server
JP3522882B2 (en) * 1995-03-22 2004-04-26 株式会社東芝 Protocol switching method
US5781758A (en) * 1995-03-23 1998-07-14 Apple Computer, Inc. Software emulation system with reduced memory requirements
US5717903A (en) * 1995-05-15 1998-02-10 Compaq Computer Corporation Method and appartus for emulating a peripheral device to allow device driver development before availability of the peripheral device
JPH08315090A (en) * 1995-05-23 1996-11-29 Toshiba Corp Ic card reader/writer and method for transmitting data
US5710908A (en) * 1995-06-27 1998-01-20 Canon Kabushiki Kaisha Adaptive network protocol independent interface
US5915008A (en) * 1995-10-04 1999-06-22 Bell Atlantic Network Services, Inc. System and method for changing advanced intelligent network services from customer premises equipment
US6067527A (en) * 1995-10-12 2000-05-23 Gilbarco, Inc. Point of sale system, method of operation thereof and programming for control thereof
US5732283A (en) * 1995-10-24 1998-03-24 International Business Machines Corporation System and method of providing universal support for multiple pointing devices
US6405254B1 (en) * 1996-01-03 2002-06-11 Sterling Commerce, Inc. System and method for protocol conversion using facilities and utilities
US5966545A (en) * 1996-01-25 1999-10-12 Apple Computer, Inc. System for interfacing network applications with different versions of a network protocol by providing base class at session level and invoking subclass from base class at session level
US7167924B1 (en) 1996-06-10 2007-01-23 Diebold, Incorporated Financial transaction processing system and method
US6039245A (en) 1996-06-10 2000-03-21 Diebold, Incorporated Financial transaction processing system and method
US5857080A (en) 1996-09-10 1999-01-05 Lsi Logic Corporation Apparatus and method for address translation in bus bridge devices
US6064660A (en) * 1996-12-12 2000-05-16 Optimay Corporation GSM transceiver with portable protocol stack
US5956723A (en) * 1997-03-21 1999-09-21 Lsi Logic Corporation Maintaining identifier information in a memory using unique identifiers as a linked list
HUP0004141A2 (en) * 1997-03-21 2001-05-28 Canal+ Societe Anonyme Method and apparatus for providing communication chanel between a program and a component of a computer system, between an application and a component of a receiver/decoder, as well as method for transmitting data between an application and a component
US5958016A (en) * 1997-07-13 1999-09-28 Bell Atlantic Network Services, Inc. Internet-web link for access to intelligent network service control
US6477143B1 (en) 1998-01-25 2002-11-05 Dror Ginossar Method and apparatus for packet network congestion avoidance and control
US6131148A (en) 1998-01-26 2000-10-10 International Business Machines Corporation Snapshot copy of a secondary volume of a PPRC pair
US6968405B1 (en) * 1998-07-24 2005-11-22 Aristocrat Leisure Industries Pty Limited Input/Output Interface and device abstraction
US6256322B1 (en) 1998-10-02 2001-07-03 Canon Kabushiki Kaisha Bundling multiple network management packets
US6351691B1 (en) * 1998-10-15 2002-02-26 Micro Motion, Inc. I/O signaling circuit
US6453277B1 (en) * 1999-01-28 2002-09-17 Computer Associates Think, Inc. Virtual I/O emulator in a mainframe environment
FR2800952B1 (en) * 1999-11-09 2001-12-07 Bull Sa ARCHITECTURE OF AN ENCRYPTION CIRCUIT IMPLEMENTING DIFFERENT TYPES OF ENCRYPTION ALGORITHMS SIMULTANEOUSLY WITHOUT LOSS OF PERFORMANCE
GB2366019B (en) * 2000-01-24 2004-07-14 Hewlett Packard Co System and method for locally storing remote device data formats
US6978233B1 (en) * 2000-03-03 2005-12-20 Unisys Corporation Method for emulating multi-processor environment
US6785759B1 (en) * 2000-05-10 2004-08-31 International Business Machines Corporation System and method for sharing I/O address translation caching across multiple host bridges
US7054361B1 (en) 2000-05-31 2006-05-30 Thomson Licensing Method and apparatus for enhancing an infrared signal protocol
US6629166B1 (en) * 2000-06-29 2003-09-30 Intel Corporation Methods and systems for efficient connection of I/O devices to a channel-based switched fabric
AU2001284667A1 (en) * 2000-07-25 2002-02-05 Dutec, Inc. System, device and method for comprehensive input/output interface between process or machine transducers and controlling device or system
FI110900B (en) * 2001-07-11 2003-04-15 Nokia Corp Protocol-based end-users
US20030014579A1 (en) * 2001-07-11 2003-01-16 Motorola, Inc Communication controller and method of transforming information
GB0204035D0 (en) * 2002-02-21 2002-04-03 Adder Tech Ltd Interfacing devices
US7386609B2 (en) * 2003-02-20 2008-06-10 International Business Machines Corporation Method, system, and program for managing devices in a network
US6904476B2 (en) 2003-04-04 2005-06-07 Rosemount Inc. Transmitter with dual protocol interface
US7032108B2 (en) 2003-05-02 2006-04-18 Egenera, Inc. System and method for virtualizing basic input/output system (BIOS) including BIOS run time services
EP1623337A4 (en) * 2003-05-02 2008-12-31 Egenera Inc System and method for virtualizing basic input/output system (bios) including bios run time services
US7228265B2 (en) * 2003-05-02 2007-06-05 Egenera, Inc. System and method for emulating serial port communication
JP4136857B2 (en) * 2003-09-11 2008-08-20 キヤノン株式会社 Device search method and program
JP4834294B2 (en) * 2004-01-07 2011-12-14 日立オートモティブシステムズ株式会社 Data communication apparatus and controller using the same
US7587421B2 (en) * 2004-01-30 2009-09-08 International Business Machines Corporation Method, system, and article of manufacture for generating device specific requests
US20060106911A1 (en) * 2004-10-29 2006-05-18 Chapple James S Concurrent PCI express with sDVO
US7843961B2 (en) * 2005-07-25 2010-11-30 International Business Machines Corporation Hardware device emulation
US20090132747A1 (en) * 2007-11-19 2009-05-21 International Business Machines Corporation Structure for universal peripheral processor system for soc environments on an integrated circuit
US8046519B2 (en) * 2008-10-20 2011-10-25 Daniel Measurement And Control, Inc. Coupling a specialty system, such as a metering system, to multiple control systems
US9430429B2 (en) * 2012-05-07 2016-08-30 Bristol, Inc. Methods and apparatus to identify a communication protocol being used in a process control system
CN102722535B (en) * 2012-05-21 2016-04-13 周明 A kind of method avoiding the access conflict of modbus real-time data base

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3721961A (en) * 1971-08-11 1973-03-20 Ibm Data processing subsystems
US4084235A (en) * 1975-04-14 1978-04-11 Honeywell Information Systems Inc. Emulation apparatus
US4086658A (en) * 1976-10-04 1978-04-25 International Business Machines Corporation Input/output and diagnostic arrangements for programmable machine controllers having multiprogramming capabilities
US4261033A (en) * 1977-01-19 1981-04-07 Honeywell Information Systems Inc. Communications processor employing line-dedicated memory tables for supervising data transfers
US4156796A (en) * 1977-11-29 1979-05-29 International Business Machines Corporation Programmable data processing communications multiplexer
JPS559213A (en) * 1978-06-30 1980-01-23 Fujitsu Ltd Communication control unit
US4453211A (en) * 1981-04-28 1984-06-05 Formation, Inc. System bus for an emulated multichannel system
US4394726A (en) * 1981-04-29 1983-07-19 The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration Distributed multiport memory architecture
US4467445A (en) * 1981-06-16 1984-08-21 International Business Machines Corporation Communication adapter circuit
JPS5848551A (en) * 1981-09-18 1983-03-22 Nippon Telegr & Teleph Corp <Ntt> Data communication controller
US4443850A (en) * 1981-12-01 1984-04-17 Burroughs Corporation Interface circuit for subsystem controller
JPS5981732A (en) * 1982-10-30 1984-05-11 Sharp Corp Data processor
US4491915A (en) * 1982-11-30 1985-01-01 Rca Corporation Multiprocessor-memory data transfer network
US4731734A (en) * 1983-10-17 1988-03-15 Data General Corporation Digital computer system incorporating object-based addressing and access control and tables defining derivation of addresses of data from operands in instructions
US4593380A (en) * 1984-06-04 1986-06-03 General Electric Co. Dual function input/output for a programmable controller
US4701841A (en) * 1984-07-25 1987-10-20 Digital Equipment Corporation System for altering data transmission modes
US4648029A (en) * 1984-08-27 1987-03-03 International Business Machines Corporation Multiplexed interrupt/DMA request arbitration apparatus and method
US4604683A (en) * 1984-12-10 1986-08-05 Advanced Computer Communications Communication controller using multiported random access memory

Also Published As

Publication number Publication date
EP0288713A3 (en) 1989-12-13
US4855905A (en) 1989-08-08
DE3889766D1 (en) 1994-07-07
EP0288713A2 (en) 1988-11-02
DE3889766T2 (en) 1994-12-01
JPS63275243A (en) 1988-11-11
JPH0534860B2 (en) 1993-05-25
EP0288713B1 (en) 1994-06-01

Similar Documents

Publication Publication Date Title
CA1291576C (en) Concurrent multi-protocol i/o controller
KR960003413B1 (en) Data processing system
US5337412A (en) Method and apparatus for substituting real and virtual devices independent from an data processing system application program
US5551053A (en) System and Method for assigning addresses to I/O devices in a control network and for verifying the assigned address of the devices
US4701848A (en) System for effectively paralleling computer terminal devices
CA1294711C (en) Communication interface protocol
US4787026A (en) Method to manage coprocessor in a virtual memory virtual machine data processing system
US5414851A (en) Method and means for sharing I/O resources by a plurality of operating systems
CA1302586C (en) Apparatus and method for interconnecting an application of a transparent services access facility to a remote source
EP0366581A2 (en) Method to provide concurrent execution of distributed application programs by a host computer and an intelligent work station on an sna network
US5410709A (en) Mechanism for rerouting and dispatching interrupts in a hybrid system environment
JPH0527898B2 (en)
US6567837B1 (en) Object oriented processor arrays
JPH05274234A (en) General-purpose connection device for connecting computer bus to specific link of network
US5758159A (en) Structured software for a telecommunication system, including a communication service object which uses relationship data to route a message from an originator object to a recipient object
WO1998021862A1 (en) Multi-layered interface for interconnecting application programs to system bus lines for electronic devices
CN107168909A (en) Interconnecting device, telecommunication system, data transmission method and device
US5210747A (en) Communications controller for use with a computer and a plurality of isdn terminals
JPH0691535B2 (en) Controller for controlling many types of LAN
JP2758257B2 (en) Computer system
US5995741A (en) Simulation tool for a networking code
CN101228773B (en) Hardware device simulation
JPH04155566A (en) Down-load system
KR100344201B1 (en) Tcp/ip connection device of banking system
Schoeffler Organization of software for multicomputer process control systems

Legal Events

Date Code Title Description
MKLA Lapsed