Method and apparatus for remote object code inclusion

Details Method and apparatus for remote object code inclusion Method and apparatus for remote object code inclusion

1998-01-20

2001-02-06

Chaki, Kakali (Department: 2762)

Data processing: software development, installation, and managem

Software program development tool

Translation of code

C717S152000, C709S241000

Reexamination Certificate

active

06185733

ABSTRACT:

CROSS-REFERENCE TO RELATED APPLICATION
This application is related to the commonly owned, concurrently filed application of the same inventors, Ser. No. 09/009,293, entitled “METHOD AND APPARATUS FOR REMOTE SOURCE CODE INCLUSION”, incorporated herein by reference.
BACKGROUND OF THE INVENTION
1. Field of the Invention
This invention is related to computer linkage editor programs and particularly to object module library search processing.
2. Description of the Related Art
Computer linkage editors are well known in the art. Basically, a computer linkage editor is a computer program for creating load modules from one or more object modules by resolving cross references among the modules and, if necessary, adjusting addresses. See, for example, the IBM publication
VSE/Central Functions, Linkage Editor, Diagnostic Reference,
IBM publication number LY33-9169, incorporated herein by reference, and a related IBM publication
System Control Statements,
IBM publication number SC33-6613, incorporated herein by reference.
An input stream to a linkage editor may contain one or more control statements known as include statements. Each include statement directs the linkage editor preprocessor to replace the statement with the contents of a specified object module. Normally, object modules referenced by include statements are contained in the input stream or reside in libraries contained in specified subdirectories. An include statement may explicitly specify the library containing an object module by specifying a drive and path location. Otherwise, object module libraries are specified by control statements that are known as library definition statements. A library definition statement is a control statement for specifying which program library or libraries to search for object modules specified in include statements. Library definition statements function in a manner similar to PATH statements in DOS and its derivatives to specify a search path for locating files (in this case, include files).
Conventionally, when linking object modules to form a load module, the library or libraries containing the object modules to be included must be resident on either a local drive or a connected network drive. Here a “connected network” means a local area network (LAN) or other network in which LAN server or other disk drives can be accessed as if they were locally connected to each client system on the LAN. In an OS/2®, Windows®, or DOS environment, the LAN server disk drives would be referred to by a drive letter such as W: or Z:. In a UNIX®-based system, access to remote files is accomplished via a network file system (NFS) and is limited to disk drives attached to systems comprising the LAN. In both the above cases, a linkage editor accesses the accessible disks as if they were locally attached.
As a result of this local access requirement for object module libraries, two sets of expenses are incurred. First, software producers pay media and distribution costs for the (sometimes rather substantial) amounts of data written on disks or CD-ROMs that are used for product distribution. Second, users have to allocate substantial amounts of space on their personal computers to store the object libraries distributed with compilers, linkage editors and product application program interfaces (APIs).
With the introduction of thin clients (cost-reduced computers having small amounts of memory and disk space that rely on a network to store most of their data), the ability to include remotely resident object modules becomes imperative.
Another reason for the present invention is related to the practice of team software development. During development of software, programmers within a development team are conventionally given access to the same local area network (LAN) so that they can easily share their data. This practice is based on the paradigm ascribing most or all of the programmers in a team to a single company developing code.
With the widespread acceptance of Internet and the emergence of virtual enterprises, this static-team paradigm is being replaced with a dynamic, widely dispersed team of programmers, cooperating on a development project across vast distances, time zones, continents, etc., making it impossible to place all of the software developers on a single LAN. It is often necessary for a team of programmers to be able to access the same set of object libraries, but which, because of the distances involved, cannot be made available on any single LAN as a single instance.
A number of products (e.g., IBM TeamConnection) exist for software version management and group development; however, they either provide programmers with access to shared data within a LAN, or replicate data among LANs or single nodes. Some way to access source libraries via a direct Internet access is what is required.
SUMMARY OF THE INVENTION
Existing linkage editors do not automatically access a non-connected network destination (for example, an arbitrary Internet location outside of a local area network) that contains object libraries, therefore, to allow the specification of either a Transmission Control Protocol/Internet Protocol (TCP/IP) address or name (to be resolved via a name server or local TCP/IP name resolution file), or a World Wide Web (WWW) Uniform Resource Locator (URL) of a non-connected system that contains the libraries required to properly create the load module under construction.
When the linkage editor encounters such a remote address specification, it calls a program which attempts to make the remote connection. If the remote connection is made, the object library specified is accessed an appropriate protocol. These remote addresses are specified to the linkage editor via a linker option, just as it is done for local include paths currently.
The present invention provides for a library definition file that contains a user ID/password, along with any other required parameters that may need to be specified, so that in the case of a protocol that has more complex access requirements, for example, the File Transfer Protocol (FTP), the linkage editor will know how to login and get the object modules it needs to include.
The present invention provides in a library definition file any information that may be necessary in case the remote library charges a fee for supplying remote object modules, such as an account number to be charged.
Then, the retrieved object module is used for linking the object code to create the load module.


REFERENCES:
patent: 4567574 (1986-01-01), Saade et al.
patent: 5023907 (1991-06-01), Johnson et al.
patent: 5185860 (1993-02-01), Wu
patent: 5204897 (1993-04-01), Wyman
patent: 5247678 (1993-09-01), Littleton
patent: 5303376 (1994-04-01), Taki
patent: 5313635 (1994-05-01), Ishizuka et al.
patent: 5339435 (1994-08-01), Lubkin et al.
patent: 5371852 (1994-12-01), Attanasio et al.
patent: 5381547 (1995-01-01), Flug et al.
patent: 5386369 (1995-01-01), Christiano
patent: 5394546 (1995-02-01), Hanatsuka
patent: 5418957 (1995-05-01), Narayan
patent: 5437029 (1995-07-01), Sinha
patent: 5499340 (1996-03-01), Barritz
patent: 5517635 (1996-05-01), Cross et al.
patent: 5613120 (1997-03-01), Palay et al.
patent: 5692196 (1997-11-01), Unni et al.
patent: 5706502 (1998-01-01), Foley et al.
patent: 5708811 (1998-01-01), Arendt et al.
patent: 5732219 (1998-03-01), Blumer et al.
patent: 5761499 (1998-06-01), Sonderegger
patent: 5778231 (1998-07-01), van Hoff et al.
patent: 5867707 (1999-02-01), Nishida et al.
patent: 5923882 (1999-07-01), Ho et al.
IBM C Set ++ for AIX Reference Summary—Version 3 Release 1 SX09-1300-01—Second Edition (Aug. 1995).
IBM VSE/Enterprise Systems Architecture—VSE/Central Functions Linkage Editor Diagnosis Reference, Version 6 Release 1—First Edition (Apr. 1995) LY33-9169-00.
IBM/VSE Enterprise Systems Architecture—System Control Statements—Version 2, Release 1—First Edition (Apr. 1995)—SC33-6613-00.
IBM TDB—vol. 29, No. 8, Jan. 1997—“Execution-Time Loading . . . Stubs” M.R. Beghtel et al—p. 3521.
IBM TDB—vol. 33, No. 6B, Nov. 1990—Tracing The Exported Entry P

Affiliated with

Also associated with

Rating

Method and apparatus for remote object code inclusion does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Method and apparatus for remote object code inclusion, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method and apparatus for remote object code inclusion will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-2566517