| Mapping a source file from a source system to a target system -> Monitor Keywords |
|
|
 
Mapping a source file from a source system to a target systemRelated Patent Categories: Data Processing: Database And File Management Or Data Structures, Database Or File Accessing, Query Processing (i.e., Searching), Pattern Matching AccessMapping a source file from a source system to a target system description/claimsThe Patent Description & Claims data below is from USPTO Patent Application 20070124302, Mapping a source file from a source system to a target system. Brief Patent Description - Full Patent Description - Patent Application Claims
RELATED APPLICATION [0001] This application is a continuation-in-part of U.S. patent application Ser. No. 11/311,423 entitled "Application Conversion of Source Data," filed Dec. 20, 2005, which is incorporated herein by reference in its entirety. BACKGROUND [0002] Embodiments of the invention relate generally to the migration of data and, more particularly, to a method and apparatus for migrating data from a source system to a target system. [0003] One problem encountered when migrating a source application from a source platform to a target platform is the compatibility of the source application with the target platform. Often, the source application is ported to the target system with minimal modifications because modifying portions of the source application for complete compatibility with the target system can be complicated and/or prohibitively expensive. Incompatibilities, such as differences in operating systems/functions, file storage directory structures, and so forth can cause the source application of the source platform to fail in processing source data on the target platform. For example, a source application that has been migrated to a target platform may fail at the time of execution on the target platform because an operating system of the target platform may not be configured with the same functionality as a source operating system of a source platform. Thus there is a need for a method and apparatus that can be used to mitigate problems associated with migration of a source application to a target platform. SUMMARY OF THE INVENTION [0004] A method includes defining a file attribute indicator based on an attribute associated with a source file and based on a mapping policy. The source file has a source filename and the source file is migrated to a target system from a source system. The target filename is based on the source filename and the file attribute indicator. The target filename is used by a target application of the target system to process the source file. The target application is the source application configured for use on the target system. BRIEF DESCRIPTION OF THE DRAWINGS [0005] The present invention is described with reference to the accompanying drawings. In the drawings, identical or like reference numbers indicate identical or functionally similar elements. [0006] FIG. 1 is a schematic diagram of an embodiment of the invention. [0007] FIG. 2 is a flowchart illustrating an embodiment of the invention. [0008] FIG. 3 is a figure illustrating the processing of source data on a target system according to the flowchart in FIG. 2. [0009] FIG. 4 is a flowchart illustrating an embodiment of the invention. [0010] FIG. 5 is a flowchart illustrating an embodiment of the invention [0011] FIG. 6 is a schematic diagram that illustrates a copy module that is configured to define a target filename associated with a source file/data that is migrated from a source system to a target system, according to an embodiment of the invention. [0012] FIG. 7 is a table that illustrates an example of indicators of file attributes included in UNIX filenames based on a mapping policy and based on MVS filenames, according to an embodiment of the invention. [0013] FIG. 8 is a flowchart that illustrates processing related to a source file migrated from a source system to a target system, according to an embodiment of the invention. [0014] FIG. 9 is a flowchart that illustrates processing related to a source file when the source file is requested at a target system, according to an embodiment of the invention. [0015] FIG. 10 is a flowchart that illustrates a method related to source file compression, according to an embodiment of the invention. DETAILED DESCRIPTION [0016] The diagram in FIG. 1 illustrates a personal computer application 160 receiving, processing, and manipulating mainframe data 130 from a mainframe computer 100. Manipulating includes functions such as reading data, performing mathematical operations, writing data, and executing programs. The mainframe data 130 contains character data portions and numeric data portions that are encoded, based on data type, in a mainframe encoding for use by the mainframe application 110. The personal computer application 160 is a version of the mainframe application 110 configured for use on a personal computer 150. Although the applications 110 and 160 are the same application, since the mainframe data 130 is encoded in a mainframe encoding, the mainframe data 130 cannot be directly manipulated by the personal computer application 160 using compiler libraries that are configured to manipulate data that is encoded for the personal computer application 160. [0017] The file format information, however, used by the personal computer application 160 is the same as the file format information used by the mainframe application 110 to process the mainframe data 130. Even if the mainframe data 130 contains records with variable lengths and different mixtures of data types such as numeric data and character data that are not in fixed positions, the file format information specifies the locations of records and contains field layout information that describe the lengths and locations of data types within each record. Simply put, the file format information specifies the portions of the mainframe data 130 that are character data and the portions of the mainframe data 130 that are numeric data. The personal computer application 160 can use the common file format information to parse the character and numeric portions of the mainframe data 130. Before manipulating the mainframe data 130, the personal computer application 160 parses the mainframe data 130 using the file format information and converts the parsed data using a modified compiler library 170 that is modified to convert the mainframe data 130 into an encoding that can be manipulated by the personal computer application 160. The personal computer application 160 itself is not modified, but the compiler libraries called by the personal computer application 160 are modified. The compiler and application could be coded in any programming language, such as COBOL and C++, used for manipulating a variety of datasets in encodings such as EBCDIC, ASCII, binary, and packed decimal. [0018] Assume, for example, that the portion of the mainframe data 130 that is a character data type is encoded in an EBCDIC encoding and that the personal computer application 160 manipulates character data that is encoded in an ASCII encoding. Also, assume that the personal computer application 160 can manipulate binary data and that the numeric data in the mainframe data 130 is encoded in a binary encoding. When the personal computer application 160 uses the numeric data, which is encoded in a binary encoding, the personal computer application 160 can manipulate the data normally. However, when using the portions of the mainframe data 130 that are character data, the compiler library used by the personal computer application 160 for manipulating character data can be modified so that the character data, when retrieved using file format information, can be converted from the EBCDIC characters into ASCII characters. The personal computer application 160 is not modified, only the selected compiler library used by the personal computer application 160 for manipulating character data is modified to convert the mainframe data 130 into an encoding usable by the personal computer application 160. [0019] In alternative embodiments, data can be converted from any type of source system using source data encoded in a source encoding to any type of target system using a target application to convert the source data into a target encoding that calls modified target libraries. For example, the source system and target system can both be mainframe computers that are configured to read data encoded in different encodings. Continue reading about Mapping a source file from a source system to a target system... Full patent description for Mapping a source file from a source system to a target system Brief Patent Description - Full Patent Description - Patent Application Claims Click on the above for other options relating to this Mapping a source file from a source system to a target system patent application. ###  How KEYWORD MONITOR works... a FREE service from FreshPatents1. Sign up (takes 30 seconds). 2. Fill in the keywords to be monitored. 3. Each week you receive an email with patent applications related to your keywords. Start now! - Receive info on patent apps like Mapping a source file from a source system to a target system or other areas of interest. ### Previous Patent Application: Visually-represented results to search queries in rich media content Next Patent Application: Methods and systems for improving text segmentation Industry Class: Data processing: database and file management or data structures ### FreshPatents.com Support Thank you for viewing the Mapping a source file from a source system to a target system patent info. IP-related news and info Results in 0.11094 seconds Other interesting Feshpatents.com categories: Qualcomm , Schering-Plough , Schlumberger , Seagate , Siemens , Texas Instruments , 174 |
 * Protect your Inventions * US Patent Office filing 
PATENT INFO |
|
