US6622176B2 - Interface device and method - Google Patents

Interface device and method Download PDF

Info

Publication number
US6622176B2
US6622176B2 US08/732,319 US73231996A US6622176B2 US 6622176 B2 US6622176 B2 US 6622176B2 US 73231996 A US73231996 A US 73231996A US 6622176 B2 US6622176 B2 US 6622176B2
Authority
US
United States
Prior art keywords
message
device dependent
messages
client
message format
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 - Lifetime
Application number
US08/732,319
Other languages
English (en)
Other versions
US20020004853A1 (en
Inventor
Colin Jones
Mandeep Singh Dhaliwal
Peter Kennedy
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.)
British Telecommunications PLC
Original Assignee
British Telecommunications PLC
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 British Telecommunications PLC filed Critical British Telecommunications PLC
Assigned to BRITISH TELECOMMUNICATIONS PUBLIC LIMITED COMPANY reassignment BRITISH TELECOMMUNICATIONS PUBLIC LIMITED COMPANY ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: DHALIWAL, MANDEEP S., JONES, COLIN, KENNEDY, PETER
Publication of US20020004853A1 publication Critical patent/US20020004853A1/en
Application granted granted Critical
Publication of US6622176B2 publication Critical patent/US6622176B2/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22—Indexing; Data structures therefor; Storage structures
    • G06F16/2282—Tablespace storage structures; Management thereof
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering

Definitions

  • the present invention relates to an interface device for, and to a method for interfacing between a plurality of application programs of a data management system, each application program requiring a device dependent message to run a transaction, and a client device capable of requesting a transaction to be run.
  • a large computer system for example a system for accessing a database, typically includes software in the form of a number of application programs, which reside on a central mainframe computer, and many client devices, or terminals, which are remote from the mainframe and which are employed by users of the computer system to request information from the database.
  • the application programs perform a number of functions, for example they may specify the dialogue with the client device, access the database (typically via a database management system) and apply certain business rules, e.g. specifying that a customer appointment can only be made once a customer order has been taken, that only certain products are available, etc.
  • the application programs on large computer systems may comprise millions of lines of software code, and thus represent a significant investment.
  • the application programs are generally designed to be modular, and are often reused for example with different databases.
  • dumb terminals Many application programs written in the 1980s were designed to be accessed by so called “dumb” terminals, and thus were designed to receive, and to output, a device dependent datastream.
  • a dumb terminal requires that the information sent to it includes hardware controls which are specific to the particular device employed as the dumb terminal, and which specify the manner in which any information sent to the dumb terminal is to be displayed.
  • PC personal computers
  • many users of large computer systems utilise a PC as the client device to gain access to the mainframe computer.
  • This can be achieved by running software on the PC which emulates a dumb terminal.
  • users of PCs, or any other intelligent client device wish to use the intelligence of their terminals to access, and manipulate the data stored by the mainframe computer in a more flexible manner than is possible with a dumb terminal.
  • Screen scraping also known as “face lifting”.
  • Screen scraping techniques employ a dumb terminal emulator, but rather than requiring interaction with the user, a further program is run on the PC which automatically drives the dialogue with the mainframe computer, via the dumb terminal emulator, without requiring interaction with the user.
  • the data can be combined and displayed in any format chosen by the user, rather than being restricted to the screen format dictated by the mainframe computer.
  • PC users are thus able to specify a more modern, user friendly screen interface.
  • the screen scraping software on the PC can be programd to acquire data from a number of formatted dumb terminal screens output by the mainframe computer, and to display this data on a single screen.
  • the computer system comprises the customer database for a telephone operator
  • the telephone number of a customer input to the screen scraping program on the PC could be used to acquire a profile of the customer i.e. his address, the telephone equipment he has installed, the date of his last bill, etc.
  • the PC user can decide on new functionality that he requires from the large computer system, and achieve this functionality, by programming screen scraping software local to the PC, far more rapidly than the new functionality could be achieved by reprogramming the large application programs resident on the mainframe computer.
  • Such screen scraping software can be purchased, for example from Attachmate Corporation (Attachmate Sales UK Ltd, Attachmate House, 102 Markham Mews, Broad Street, Wokingham, Berkshire, RG111AH) who sell screen scraping software products called “Extra!” and “Extra! for Windows”.
  • a further problem is created due to the ease with which many transactions may be requested via screen scraping software by the PC client of the mainframe application programs. Since these transactions are run serially by the PC client, the response time at the PC is adversely affected, and the network traffic between the PC and the mainframe is increased substantially. Furthermore, use of screen scraping by a significant number of PC clients may cause degradation in the performance of the mainframe computer, which was designed and tuned to deal with the work rates of a user interacting with a dumb terminal client.
  • an interface device for interfacing between a plurality of application programs of a data management system, each application program requiring a device dependent message to run a transaction, and a client device capable of requesting a transaction to be run, the interface device comprising:
  • first input means for receiving a device independent message containing a keyword from the client device
  • first output means for sending a device dependent message to an application program
  • memory means for storing keywords, data identifying the transaction(s) to which each of the keywords relates, and the device dependent messages required to run each of the transactions, and
  • processing means for extracting the keyword(s) from a message received by the first input means, accessing the memory means to determine the device dependent message(s) associated with the keyword(s), sending said device dependent message(s) via the first output means to the application program(s), extracting data from a message received by the second input means, and sending said data within a device independent message to the client device via the second output means.
  • embodiments of the present invention by providing an interface device which facilitates the translation of a device independent message from the client device, to a device dependent message as expected by the application program, and vice versa, allow the client device to be isolated from the precise requirements of the applications program.
  • a PC client making a request of a data management system comprising an interface device according to the present invention thus does not need to know, for example the screen co-ordinates required by the particular application program to run a particular transaction.
  • the PC client simply needs to identify the relevant transaction, and data required, via the keyword sent in a device independent message to the interface device.
  • the interface device will then relate the keyword sent to the device dependent message required to run a particular transaction via the application program. If the application program is altered so that it requires a different device dependent message, or so that it outputs the results of a transaction in a different format, only the appropriate device dependent message stored within the memory means of the interface device need be altered.
  • the PC client can continue to access the same application program in the same manner via the same keyword, so that as improvements are made to application programs no changes are required to the many PC clients.
  • a single keyword may be associated with more than one device dependent message within the memory means of the interface device.
  • This allows a single request from a client device to cause the interface device to run a number of transactions, and to return information from a plurality of formatted screens output by the application program(s) to the client device via a device independent message.
  • multiple serial communications between the client device and the application program(s) have been replaced by a single communication. The response times experienced by a user at the client device are thus greatly improved, and the network traffic between the client device and the central computing resource is greatly reduced.
  • a data management system comprising a central computing resource having an interface device according to the present invention also comprises a dialogue manager for receiving requests for transactions from client devices, which dialogue manager is able to distinguish between device independent messages, and device dependent messages, and to pass device independent messages to the interface device.
  • a dialogue manager for receiving requests for transactions from client devices, which dialogue manager is able to distinguish between device independent messages, and device dependent messages, and to pass device independent messages to the interface device.
  • This allows the data management system to support both dumb terminals communicating with the central computing resource via device dependent datastreams, and intelligent client devices communicating with the central computing resource via device independent messages.
  • a method for interfacing between a plurality of application programs of a data management system, each application program requiring a device dependent message to run a transaction, and a client device comprising the steps of:
  • FIG. 1 is a schematic diagram of a data management system according to the present invention
  • FIG. 2 is a schematic diagram showing in greater detail the middleware components of the data management system of FIG. 1;
  • FIG. 3 is a schematic diagram of the screen-related static tables employed in a data management system according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of an embodiment of the present invention showing the relationship between the components of the data management system.
  • FIG. 5 is a schematic diagram showing an example of multiple transactions run on a data management system according to an embodiment of the present invention, and according to a prior art technique.
  • the embodiment of the present invention to be described comprises a large data management system which includes an interface device, according to the present invention, which in the present embodiment is termed MMBI (middleware message based interface).
  • the data management system comprises hardware and software.
  • the hardware components are IBM 3090 series mainframes. Standard IBM software is utilised for the operating system (MVS), and the teleprocessing monitor (CICS), and the database management system is IDMS, sold by Computer Associates of Computer Associates House, 183-187 Bath Road, Slough, Berkshire, SL1 4AA.
  • the IBM hardware and software components can be purchased from IBM UK Ltd, PO BOX 41, North Harbour, Portsmouth, PO63AU.
  • the system furthermore comprises a number of software modules collectively known as middleware.
  • Middleware is a term known in the software field to describe a layer of software which is positioned between application programs, which are written for the specific requirements of the operator of the computer system, and the proprietary software purchased by the operator of the computer system.
  • a key role of middleware is to insulate the application programs from the demands of the teleprocessing monitor, i.e. IBM's CICS.
  • CICS is a complex piece-of software produced by IBM which is regularly updated.
  • middleware the application programers need know very little about CICS, since they can rely on the middleware programers to deal with the complexities of interfacing with CICS, and to incorporate any changes necessary due to new versions of CICS.
  • Middleware also allows many routine functions such as sign-on, menu, validation and abends to be handled centrally rather than being reproduced in each of the application programs.
  • FIGS. 1 and 2 show schematic diagrams of the software of the data management system.
  • All input from terminals 1 is passed, via MVS 2 , to CICS 3 which in turn passes it to middleware 4 .
  • Middleware 4 performs certain functions on the data, such as access control and validation, before passing it on to the appropriate application program 5 .
  • Data is returned to the terminal back via middleware 4 , CICS 3 and MVS 2 .
  • middleware tables 13 hold reference data that describes the configuration of the on-line system. While the system is running these tables are held within the machine's memory which belongs to MVS (the MVS private storage area associated with the CICS address space). The data for the tables 13 is held in a middleware database. This data is then used to build linear datasets (LDS) which are loaded into memory when the system is started. The data is entered and maintained in the middleware database by middleware ancillary software 7 .
  • LDS linear datasets
  • Middleware is made up of a number of different components which are shown in FIG. 2 .
  • Each of the middleware components 6 accesses one or more of the middleware tables 13 .
  • the system can be reconfigured by adding and changing certain elements in the tables. Any changes made to the tables do not immediately become effective.
  • the tables are loaded into the machine's memory during system start-up and thus changes do not become effective until the tables are reloaded, i.e. when the LDSs are next rebuilt and refreshed or the CICS system is restarted.
  • Dialogue manager 8 is the main middleware component. Each time a terminal sends data, dialogue manager 8 is executed. Dialogue manager 8 controls the processing of the input, calling the various middleware components and application programs 5 as necessary. After the application program 5 has finished processing the data, dialogue manager 8 takes control of processing any output messages.
  • Access control 9 is the main middleware security feature. Before the on-line system can be used the user must ‘sign on’. Once a user has ‘signed on’ access control determines whether the user can access a particular transaction or application according to:
  • the terminal group their terminal is in (note that access control based on terminal group can be configured off).
  • Middleware developed systems are menu driven. When a user ‘signs on’, the primary menu is displayed. This menu is built by menu management 10 and it only shows the applications that the user is allowed to use. If the user selects a particular application, menu management 10 builds an application menu showing only the transactions, belonging to the selected application, that the user can access.
  • ‘Routing’ is a process 11 used in transaction switching. Its function is to examine screen input data (telephone number, account number, or address data), and identify the system where the transaction should run with that data. In order to do this it uses routing tables to ‘look up’ the incoming data and associate it with a system. There are five routing tables:
  • Validation 12 is a large part of the processing of any terminal input.
  • the middleware tables 13 there is a set of tables that specify the basic validation that is to be performed on every field on every screen.
  • validation 12 validates each field on the screen according to the rules specified in the tables 13 .
  • the types of validation that are performed are for format, ranges and specific values. There are no validation checks against the application database or field interdependency checks. These are the responsibility of the application programs 5 .
  • the current screen is redisplayed to the user with an appropriate error message.
  • the data is not passed to the application program 5 .
  • MMBI 14 allows an intelligent front-end system (e.g. PC client) to invoke back-end system functions via self-defining type/length/value (TLV) messages.
  • front-end system e.g. PC client
  • back-end system functions via self-defining type/length/value (TLV) messages.
  • TLV type/length/value
  • the MMBI server 14 logically acts as an agent between the front-end client and dialogue manager 8 (which runs standard screen-based business transaction). It allows one or more transactions to be executed under the control of an object script language.
  • the MMBI 14 introduces new middleware systems tables 13 , themselves supported by new linear datasets.
  • Any middleware or business function can be executed using a self-defining datastream message rather than the classic CICS screen presentation.
  • the message for both input and output, is in a type, length and value (TLV) format.
  • the MMBI server 14 processes the message, controls transaction execution (via requests to dialogue manager) and finally returns the resulting output in a self defining format.
  • Every error message output on a user's screen is allocated a unique id.
  • the text associated with each message is stored in one of the middleware tables 13 .
  • middleware e.g. validation, or an application program wishes to display a message to the user they only supply the unique id to dialogue manager.
  • the message is displayed, by dialogue manager 8 , using the text in the middleware table.
  • an operator interface 15 is thus provided. With this interface 15 the user can monitor all messages produced by the system and monitor and control items such as:
  • Message service 16 is used to pass data between systems that need to communicate whilst performing transaction switching. There are two sides to message services:
  • LMS Local message service
  • RMS Remote message services
  • the report printing subsystem 18 allows an application to generate a report into the middleware database from which the printing function within middleware controls the actual printing of the report.
  • the subsystem runs in CICS, but in the background. It is started when the CICS system is brought up and it is controlled through the operator interface 15 rather than dialogue manager 8 .
  • the background scheduler 20 facilitates these functions. It controls the functions as they execute in CICS background.
  • the scheduler 20 is controlled by the operator interface 15 .
  • a transaction running from a terminal submits data to the background scheduler 20 for processing. It is left up to each application to determine whether or not the dat has been processed.
  • the batch job submission part of middleware 21 allows an application program 5 to submit a job to JES (Job Entry subsystem) the user can then monitor the jobs progress through the system.
  • JES Job Entry subsystem
  • a typical use of this facility is for an application transaction to submit a batch job to create a report into the report printing subsystem 18 .
  • the report can be browsed online using the report printing subsystem 18 .
  • the reference data that is loaded into the middleware tables 13 is held in the middleware database.
  • the ancillary software transactions are used to create and maintain this data.
  • This reference data describes the components of the on-line system and certain control information.
  • the data for the tables is held in the middleware database. To reduce the overhead of accessing the data it is loaded into the machine's memory.
  • the tables are loaded as part of the CICS STARTUP process, or during an inflight tables reload.
  • the data is loaded from linear datasets (LDS) into the MVS private storage area.
  • LDS linear datasets
  • DBCT Database Control Table
  • the address of each table loaded is stored in the CICS CWA (Common Work Area).
  • the static tables cannot are modified.
  • the details in the dynamic tables can be, and are, modified by the system but no new elements can be added.
  • the SIGNON_MESSAGE and BROADCAST tables are loaded with empty records which are updated during the CICS run.
  • One of the middleware functions is to perform basic validation on all application screens. To do this middleware needs to know the details of every application screen, i.e. field locations, sizes and validation rules.
  • the screen details are generated into the middleware database when a screen is created as part of the application development.
  • the load module for a screen is sent out to a site, the screen details are also sent.
  • the details are loaded into the site's database as part of the configuration management system.
  • the screen details are loaded into four tables as shown in FIG. 3 .
  • Map Headers 22 Contains the name of every screen in the system. It is used to find the field details for each screen.
  • Map Fields 23 Contains the definitions of each field on every screen. It defines the start position, length and validation type of each field. If the validation type is a range check it also contains the lower and upper limits of the range.
  • Validation Values Ids When a field is to be validated against a specific value or list of values the value or list is assigned an ID. Any particular ID can be reference by more than one field. This table contains all valid IDs. Validation Values For each valid ID in the validation type table this table contains the specific value or list of values.
  • New Maps/Program Tables The new maps/programs table is used by the tables load manager during the inflight reload to determine which new maps have been introduced since the last system startup. This list of maps and their associated programs is used to drive an automatic CICS new copy which is synchronised with the introduction of the new versions of a map mask and any validation table information.
  • the validation types tables is not used during normal processing. Its purposes is to provide a link to the validation details table when the tables are loaded. After the table load the table is not used.
  • the client To gain access to the MMBI the client only needs normal terminal access to the middleware system.
  • MMBI objects can be executed.
  • An object allows the client to pre-define a group of one or more transactions to be run in sequence.
  • the definition is written using a MMBI script language.
  • the definitions of all objects are loaded into the object table at startup and accessed from there whenever one is executed.
  • the language can define:
  • a sequence of transactions (with or without parameters) to be run (EXEC command).
  • the response message to the client only contains the data specified by the EXTRACT commands. For example an object running 10 transactions may only return 5 data values out of the possible hundreds available from the transactions.
  • middleware When receiving or sending a message in MMBI mode middleware needs to know the details of all the application screens currently supported by the MMBI facility. These details include the field's standard name, location and size. For one screen the details are collective known as a mapview.
  • the mapview are generated into the middleware database when one of the MMBI supported screens is created or modified as part of the application development.
  • the load module for a screen is sent out to a site, the screen details are also sent.
  • the screen details are loaded into two tables, with a relationship similar to that of the map headers and map fields tables of FIG. 3 .
  • Mapview Headers Contains the name of every MMBI supported screen. It is used to find the mapview field details for each screen.
  • Mapview Field Table Contains the definitions of each field on all the MMBI supported screens. It defines the start position, length and standard name (actually the numeric identify of the name in the standard name dictionary) of each field.
  • the standard name dictionary table is used to verify all MMBI messages.
  • the object table is used to execute supported objects when requested by the client. It is actually two tables, the header and detail tables.
  • Standard name dictionary Contains all the standard names which are supported by MMBI. Each entry contains a unique numeric subscript used in both the mapview table and the object table to identify the name.
  • Object header table Contains all the objects which are supported by MMBI. Each entry contains one or more events to be handled by the object. Each event points into the details table, defining the object language statement(s) to be executed for that event.
  • Object detail table Contains all the statements needed to service all the events of all the objects in the header table.
  • the MMBI server 14 is invoked when a request for function or data is made via the message-based interface to middleware.
  • TLV type/length/value
  • the key rule of the syntax for both input and output is that apart from the first five characters (MMBI and one blank) the entire message is in TLV format, separated by delimiters.
  • control-TLV is a series of control word values that request and report on actions and control the flow of data e.g. “RUN- TRNSN; 3; DCA;” data-TLV is a series of TLV items that define the data. These can be key data needed to run a MW processor the data returned by a process. END; 1; *; denotes the end of the message, both client and server knows there is no more data to process after this point.
  • the server's 14 invocation and operation will now be described, with reference to FIG. 4 .
  • the client process requests a switch from normal screen operation to MMBI mode.
  • All the context data for the client is available to transactions running in MMBI mode.
  • the server 14 is invoked and it prepares the initial message acknowledging that the switch is complete.
  • the middleware system is now operating in MMBI mode for that user (client).
  • dialogue manager 8 invokes the server 14 and passes the data it has received over to the server 14 .
  • the server 14 decodes the message and operates thus:—
  • the client has requested one of the MMBI supported functions (e.g. run process, function keys, overflow data etc.).
  • MMBI supported functions e.g. run process, function keys, overflow data etc.
  • the data items sent in the message are converted into a standard screen. To do this the server uses two of the MMBI tables.
  • map This contains all the maps (screens) of all the transactions supported by the server. For each map the numeric identities for all of its standard names are listed (collectively called a ‘mapview’).
  • a virtual screen (as expected by the application program) is built using the relationship between the message elements and the positional information contained in the mapview and standard name dictionary.
  • the server accesses the third table, the object table, which contains all the supported objects. For each object the transaction to be executed, data to be extracted and logic control within the object are listed.
  • the virtual screen is passed to-20 dialogue manager 8 along with the transaction details, function key data etc.
  • Dialogue manager 8 then executes the underlying application code just as if it had been requested by a normal screen user.
  • the output data is converted into the TLV format and returned to the client.
  • the client wants to be switched from MMBI mode to normal screen operation.
  • All the context data for the client is available to screen-mode processing.
  • the server will either request dialogue manager 8 to send the primary menu or initiate a transaction and allow dialogue manager 8 to handle the screen output.
  • FIG. 5 is illustrative of how an MMBI object, containing multiple transactions, would run a set of transactions by employing a single request from a PC client 1 , and a single response from the MMBI server 14 . Also shown in FIG. 5 is the manner in which a dumb terminal 25 would invoke the same set of transactions. It can be seen that for each transaction required a pair of device dependent messages must be exchanged between the dumb terminal 25 and the dialogue manager 8 .
  • the object CRSS01 contains the transactions DCS (Display Customer Summary), DCA (Display Customer Account), DCRD (Display Customer Rental Details), DMU (Display Metered Usage) and DIX (Display Invoice).
  • DCS Display Customer Summary
  • DCA Display Customer Account
  • DCRD Display Customer Rental Details
  • DMU Display Metered Usage
  • DIX Dislay Invoice
  • the MMBI server returns:
  • the CRSS01 object results in a return of only a subset of the data contained in its constituent transaction.
  • an interface device for use in interfacing between a PC client and a mainframe computer system, it will be appreciated that it is equally suitable for interfacing between a mainframe client, or a client comprising for example a UNIX server (with LAN based PCs), to a mainframe computer system.
  • the communications link between the client and the mainframe may be serial, for example IBM 3270, or parallel, for example

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Software Systems (AREA)
  • Computing Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Computer And Data Communications (AREA)
  • Communication Control (AREA)
  • Electrical Discharge Machining, Electrochemical Machining, And Combined Machining (AREA)
  • Maintenance And Management Of Digital Transmission (AREA)
  • Debugging And Monitoring (AREA)
  • Digital Computer Display Output (AREA)
US08/732,319 1994-04-21 1995-04-19 Interface device and method Expired - Lifetime US6622176B2 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
EP94302863 1994-04-21
EP94302863 1994-04-21
EP94302863.9 1994-04-21
PCT/GB1995/000881 WO1995029440A1 (fr) 1994-04-21 1995-04-19 Dispositif et procede concernant une interface

Publications (2)

Publication Number Publication Date
US20020004853A1 US20020004853A1 (en) 2002-01-10
US6622176B2 true US6622176B2 (en) 2003-09-16

Family

ID=8217660

Family Applications (1)

Application Number Title Priority Date Filing Date
US08/732,319 Expired - Lifetime US6622176B2 (en) 1994-04-21 1995-04-19 Interface device and method

Country Status (8)

Country Link
US (1) US6622176B2 (fr)
EP (1) EP0756725B1 (fr)
JP (1) JPH09512358A (fr)
KR (1) KR970702523A (fr)
AU (1) AU679637B2 (fr)
CA (1) CA2187925C (fr)
DE (1) DE69511080T2 (fr)
WO (1) WO1995029440A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020087302A1 (en) * 2000-11-10 2002-07-04 Miyuki Tomaru Processing system, processing method and recording medium
US20030191735A1 (en) * 2002-04-04 2003-10-09 First Data Corporation Method and system for maintaining enhanced file availability
US20040044856A1 (en) * 2002-08-30 2004-03-04 Veritas Software Corporation Methods and systems for storage architectures
US20070016792A1 (en) * 2005-07-14 2007-01-18 International Business Machines Corporation Middleware sign-on
US20090089742A1 (en) * 2007-09-28 2009-04-02 Verizon Data Services Inc. Generic xml screen scraping
US7596611B1 (en) 2002-04-01 2009-09-29 Veritas Operating Corporation Method and apparatus for maintaining information for use in the configuration of a client
US9697337B2 (en) 2011-04-12 2017-07-04 Applied Science, Inc. Systems and methods for managing blood donations
US11426498B2 (en) 2014-05-30 2022-08-30 Applied Science, Inc. Systems and methods for managing blood donations

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5999728A (en) * 1996-07-30 1999-12-07 Sun Microsystems, Inc. Method and apparatus for enhancing the portability of an object oriented interface among multiple platforms
US6041332A (en) * 1997-12-31 2000-03-21 Alcatel Usa Sourcing, L.P. Product-independent performance monitoring tool kit
EP1044409B1 (fr) * 1998-01-02 2002-06-05 Acos International Limited Procede de deroulement de programme et procede pour l'extension d'un systeme de composantes de programme
US6614430B1 (en) * 1998-09-08 2003-09-02 Proficiency Ltd. System and method for the exchange of CAD data
US6807549B2 (en) * 1999-06-03 2004-10-19 B.I.S. Advanced Software Systems Ltd. General purpose interpreter and database for accessing enterprise servers over an internet protocol network
AU7643800A (en) * 1999-08-30 2001-03-26 Datango Ag Method and device for simulating user input data
IL154743A0 (en) 2000-09-06 2003-10-31 Proficiency Ltd Boundary representation per feature methods and systems
US6828963B1 (en) 2000-09-06 2004-12-07 Proficiency Ltd. Pattern matching for data exchange between computer aided design systems
US7099803B1 (en) 2000-09-06 2006-08-29 Proficiency Solutions Ltd. Data exchange between computer aided design systems
EP1324193A1 (fr) * 2001-06-14 2003-07-02 Abb Research Ltd. Système et procédé pour la modélisation cohérente
US7058898B2 (en) * 2002-03-22 2006-06-06 Sun Microsystems, Inc. Abstract user interface manager with prioritization
US7502745B1 (en) * 2004-07-21 2009-03-10 The Mathworks, Inc. Interfaces to a job manager in distributed computing environments
US8726278B1 (en) 2004-07-21 2014-05-13 The Mathworks, Inc. Methods and system for registering callbacks and distributing tasks to technical computing works
US20050144249A1 (en) * 2003-12-31 2005-06-30 Us Edirect, Inc. Method to populate a database
US7908313B2 (en) * 2004-07-21 2011-03-15 The Mathworks, Inc. Instrument-based distributed computing systems
US7571447B2 (en) * 2005-06-20 2009-08-04 International Business Machines Corporation Loose coupling of web services
US8880889B1 (en) * 2007-03-02 2014-11-04 Citigroup Global Markets, Inc. Systems and methods for remote authorization of financial transactions using public key infrastructure (PKI)
US7831630B2 (en) * 2007-07-18 2010-11-09 Accenture Global Services Limited Automation tool for providing access to an electronic database for business intelligence

Citations (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4709328A (en) * 1985-06-17 1987-11-24 International Business Machines Corporation Composite data-processing system using multiple standalone processing systems
US4774661A (en) * 1985-11-19 1988-09-27 American Telephone And Telegraph Company, At&T Information Systems Database management system with active data dictionary
US4791558A (en) * 1987-02-13 1988-12-13 International Business Machines Corporation System and method for generating an object module in a first format and then converting the first format into a format which is loadable into a selected computer
EP0394614A2 (fr) * 1989-04-28 1990-10-31 International Business Machines Corporation Interface utilisateur avancée
US5036484A (en) * 1988-11-23 1991-07-30 International Business Machines Corporation Personal computer/host emulation system for handling host data with personal computer application programs at personal computers
US5058000A (en) * 1987-06-30 1991-10-15 Prime Computer, Inc. System for accessing remote heterogeneous database including formatting retrieved data into applications program format
US5179660A (en) * 1989-05-15 1993-01-12 International Business Machines Incorporated System for reducing communications overhead in distributed database transactions by serializing in order related requests into single transmission message and receiving transmission response
US5187787A (en) * 1989-07-27 1993-02-16 Teknekron Software Systems, Inc. Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes
US5212792A (en) * 1989-06-01 1993-05-18 Hewlett-Packard Company Method and apparatus for controlling execution of tools in a computer-aided software engineering system
US5235701A (en) * 1990-08-28 1993-08-10 Teknekron Communications Systems, Inc. Method of generating and accessing a database independent of its structure and syntax
US5261079A (en) * 1990-12-18 1993-11-09 International Business Machines Corporation Interface for keyboard emulation provided by an operating system
US5339434A (en) * 1992-12-07 1994-08-16 Trw Inc. Heterogeneous data translation system
US5361344A (en) * 1993-01-29 1994-11-01 Unisys Corporation Method of operating, via a block mode terminal, UNIX programs for a character mode terminal
US5406557A (en) * 1993-02-01 1995-04-11 National Semiconductor Corporation Interenterprise electronic mail hub
US5414762A (en) * 1994-01-18 1995-05-09 Q.Sys International, Inc. Telephony controller with functionality command converter
US5423022A (en) * 1988-10-03 1995-06-06 General Signal Corporation Method for adapting a relational database management system so that it can address foreign information
US5437024A (en) * 1992-07-06 1995-07-25 French; Donald H. Selective computer-generated information distribution system by computer peripheral emulation and use
US5572711A (en) * 1993-09-28 1996-11-05 Bull Hn Information Systems Inc. Mechanism for linking together the files of emulated and host system for access by emulated system users
US5594792A (en) * 1994-01-28 1997-01-14 American Telecorp Methods and apparatus for modeling and emulating devices in a network of telecommunication systems
US5627997A (en) * 1994-06-07 1997-05-06 Microsoft Corporation Method and system for converting computer mail messages using an extensible set of conversion routines
US5634053A (en) * 1995-08-29 1997-05-27 Hughes Aircraft Company Federated information management (FIM) system and method for providing data site filtering and translation for heterogeneous databases
US5758125A (en) * 1995-12-28 1998-05-26 Newframe Corporation Ltd. Method of sharing data in a heterogeneous computer system
US5761494A (en) * 1996-10-11 1998-06-02 The Sabre Group, Inc. Structured query language to IMS transaction mapper
US5761656A (en) * 1995-06-26 1998-06-02 Netdynamics, Inc. Interaction between databases and graphical user interfaces
US5914713A (en) * 1996-09-23 1999-06-22 Fmr Corp. Accessing data fields from a non-terminal client
US6052685A (en) * 1997-08-13 2000-04-18 Mosaix, Inc. Integration of legacy database management systems with ODBC-compliant application programs

Patent Citations (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4709328A (en) * 1985-06-17 1987-11-24 International Business Machines Corporation Composite data-processing system using multiple standalone processing systems
US4774661A (en) * 1985-11-19 1988-09-27 American Telephone And Telegraph Company, At&T Information Systems Database management system with active data dictionary
US4791558A (en) * 1987-02-13 1988-12-13 International Business Machines Corporation System and method for generating an object module in a first format and then converting the first format into a format which is loadable into a selected computer
US5058000A (en) * 1987-06-30 1991-10-15 Prime Computer, Inc. System for accessing remote heterogeneous database including formatting retrieved data into applications program format
US5423022A (en) * 1988-10-03 1995-06-06 General Signal Corporation Method for adapting a relational database management system so that it can address foreign information
US5036484A (en) * 1988-11-23 1991-07-30 International Business Machines Corporation Personal computer/host emulation system for handling host data with personal computer application programs at personal computers
EP0394614A2 (fr) * 1989-04-28 1990-10-31 International Business Machines Corporation Interface utilisateur avancée
US5179660A (en) * 1989-05-15 1993-01-12 International Business Machines Incorporated System for reducing communications overhead in distributed database transactions by serializing in order related requests into single transmission message and receiving transmission response
US5212792A (en) * 1989-06-01 1993-05-18 Hewlett-Packard Company Method and apparatus for controlling execution of tools in a computer-aided software engineering system
US5187787A (en) * 1989-07-27 1993-02-16 Teknekron Software Systems, Inc. Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes
US5187787B1 (en) * 1989-07-27 1996-05-07 Teknekron Software Systems Inc Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes
US5235701A (en) * 1990-08-28 1993-08-10 Teknekron Communications Systems, Inc. Method of generating and accessing a database independent of its structure and syntax
US5261079A (en) * 1990-12-18 1993-11-09 International Business Machines Corporation Interface for keyboard emulation provided by an operating system
US5437024A (en) * 1992-07-06 1995-07-25 French; Donald H. Selective computer-generated information distribution system by computer peripheral emulation and use
US5339434A (en) * 1992-12-07 1994-08-16 Trw Inc. Heterogeneous data translation system
US5361344A (en) * 1993-01-29 1994-11-01 Unisys Corporation Method of operating, via a block mode terminal, UNIX programs for a character mode terminal
US5406557A (en) * 1993-02-01 1995-04-11 National Semiconductor Corporation Interenterprise electronic mail hub
US5572711A (en) * 1993-09-28 1996-11-05 Bull Hn Information Systems Inc. Mechanism for linking together the files of emulated and host system for access by emulated system users
US5414762A (en) * 1994-01-18 1995-05-09 Q.Sys International, Inc. Telephony controller with functionality command converter
US5594792A (en) * 1994-01-28 1997-01-14 American Telecorp Methods and apparatus for modeling and emulating devices in a network of telecommunication systems
US5627997A (en) * 1994-06-07 1997-05-06 Microsoft Corporation Method and system for converting computer mail messages using an extensible set of conversion routines
US5761656A (en) * 1995-06-26 1998-06-02 Netdynamics, Inc. Interaction between databases and graphical user interfaces
US5634053A (en) * 1995-08-29 1997-05-27 Hughes Aircraft Company Federated information management (FIM) system and method for providing data site filtering and translation for heterogeneous databases
US5758125A (en) * 1995-12-28 1998-05-26 Newframe Corporation Ltd. Method of sharing data in a heterogeneous computer system
US5914713A (en) * 1996-09-23 1999-06-22 Fmr Corp. Accessing data fields from a non-terminal client
US5761494A (en) * 1996-10-11 1998-06-02 The Sabre Group, Inc. Structured query language to IMS transaction mapper
US6052685A (en) * 1997-08-13 2000-04-18 Mosaix, Inc. Integration of legacy database management systems with ODBC-compliant application programs

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CCL: A Portable and Tunable Collective Communication Library for Scalable Parallel Computers, IEEE, Apr., 1994, pp. 835-844.* *
IBM TDB, "Method to Provide Mainframe Applicaiton with Interactive Scrolling on a Workstation", vol. 32, No. 4A, pp. 277-282, Sep. 1989.* *
IBM TDB, "System for Accessing a Mainframe from a Workstation User Interface", vol. 32, No. 4A, pp. 290-292, Sep. 1989.* *
IBM Technical Disclosure Bulletin, vol. 33, No. 2, Jul. 1990, New York US, pp. 99-100, "Device-Independent Support in Communication Environments".

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020087302A1 (en) * 2000-11-10 2002-07-04 Miyuki Tomaru Processing system, processing method and recording medium
US7596611B1 (en) 2002-04-01 2009-09-29 Veritas Operating Corporation Method and apparatus for maintaining information for use in the configuration of a client
US20030191735A1 (en) * 2002-04-04 2003-10-09 First Data Corporation Method and system for maintaining enhanced file availability
US7203670B2 (en) * 2002-04-04 2007-04-10 First Data Corporation Method and system for maintaining enhanced file availability
US20040044856A1 (en) * 2002-08-30 2004-03-04 Veritas Software Corporation Methods and systems for storage architectures
US6826661B2 (en) * 2002-08-30 2004-11-30 Veritas Operating Corporation Methods and systems for storage architectures
US20070016792A1 (en) * 2005-07-14 2007-01-18 International Business Machines Corporation Middleware sign-on
US7720829B2 (en) 2005-07-14 2010-05-18 International Business Machines Corporation Middleware sign-on
US20090089742A1 (en) * 2007-09-28 2009-04-02 Verizon Data Services Inc. Generic xml screen scraping
US8484626B2 (en) * 2007-09-28 2013-07-09 Verizon Patent And Licensing Inc. Generic XML screen scraping
US9697337B2 (en) 2011-04-12 2017-07-04 Applied Science, Inc. Systems and methods for managing blood donations
US11426498B2 (en) 2014-05-30 2022-08-30 Applied Science, Inc. Systems and methods for managing blood donations

Also Published As

Publication number Publication date
JPH09512358A (ja) 1997-12-09
WO1995029440A1 (fr) 1995-11-02
EP0756725A1 (fr) 1997-02-05
EP0756725B1 (fr) 1999-07-28
CA2187925A1 (fr) 1995-11-02
CA2187925C (fr) 2000-04-25
DE69511080T2 (de) 2000-02-03
AU679637B2 (en) 1997-07-03
US20020004853A1 (en) 2002-01-10
AU2261795A (en) 1995-11-16
DE69511080D1 (de) 1999-09-02
KR970702523A (ko) 1997-05-13

Similar Documents

Publication Publication Date Title
US6622176B2 (en) Interface device and method
US7912935B2 (en) Development and deployment of mobile and desktop applications within a flexible markup-based distributed architecture
US6990466B1 (en) Method and system for integrating core banking business processes
US6430556B1 (en) System and method for providing a query object development environment
US5442779A (en) System and method for enabling an interpreted programming language to be executed in a database management system environment
US6041344A (en) Apparatus and method for passing statements to foreign databases by using a virtual package
US5390314A (en) Method and apparatus for developing scripts that access mainframe resources that can be executed on various computer systems having different interface languages without modification
US6625590B1 (en) Command line interface for reducing user input in a network management device
US6507833B1 (en) Method and apparatus for dynamically rendering components at run time
CA2172221A1 (fr) Methode et appareil pour gerer les relations entre les objets d'un environnement a objets repartis
EP0839358B1 (fr) Emulateur pour base de donnees relationnelles sql
CN113626016A (zh) 一种基于Vue+Element UI+Koa2的前后端分离的可重用组件
JPH09171473A (ja) エラーを管理するための方法およびデータ処理システム
US20230195792A1 (en) Database management methods and associated apparatus
US7603675B2 (en) Object in, object out technique
US20050262037A1 (en) Method and apparatus for controlling result dataset generation in a javascript environment
US12613754B2 (en) Database management methods and associated apparatus
GB2294134A (en) Accessing computer databases
US8185542B1 (en) Stored procedure interface
US20050262139A1 (en) Method and apparatus for dataset manipulation in a javascript environment
US20050262156A1 (en) Method and apparatus for informational comparison of multiple datasets in a javascript environment
US6032176A (en) Data-independent type computer system: processing machine, data machine and man-machine interface therein
Singleton et al. Data access within the Information Warehouse framework
Voss APPC/MVS distributed application support
Guide Adaptive Server® Enterprise

Legal Events

Date Code Title Description
AS Assignment

Owner name: BRITISH TELECOMMUNICATIONS PUBLIC LIMITED COMPANY,

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JONES, COLIN;KENNEDY, PETER;DHALIWAL, MANDEEP S.;REEL/FRAME:008675/0525

Effective date: 19961011

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FPAY Fee payment

Year of fee payment: 8

FPAY Fee payment

Year of fee payment: 12