CA2367061A1 - Generating optimized computer data field conversion routines - Google Patents
Generating optimized computer data field conversion routines Download PDFInfo
- Publication number
- CA2367061A1 CA2367061A1 CA002367061A CA2367061A CA2367061A1 CA 2367061 A1 CA2367061 A1 CA 2367061A1 CA 002367061 A CA002367061 A CA 002367061A CA 2367061 A CA2367061 A CA 2367061A CA 2367061 A1 CA2367061 A1 CA 2367061A1
- Authority
- CA
- Canada
- Prior art keywords
- input
- application program
- attributes
- output
- conversion
- 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.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/151—Transformation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/14—Tree-structured documents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/186—Templates
Abstract
A system (20) converts data from input field types to output field types. Th e system (20) receives a plurality of input attributes and output attributes from an application program (10), dynamically generates a plurality of data field conversion routines (30) for each set of input attributes and output attributes, and stores the plurality of data field conversion routines (30) in memory that is accessible to the application program (10).
Description
GENERATING OPTTMIZED COMPUTER DATA FIELD CONVERSION ROUTTNES
FIELD OF THE INVENTION
The present invention is directed to computer data. More particularly, the present invention is directed to the conversion of one type of computer data field to another type.
BACKGROUND OF THE INVENTION
In many instances during computer processing of information, computer data must be converted from one data field type to another. For example, whenever data is passed from one program to another, the data typically goes though several conversions during the process, such as converting from text digits to a binary number.
The typical technique for converting data includes using a generic data conversion routine. When an entire record of data must be converted, the conversion routine must determine what the characteristics or attributes are for each of the data fields in the record.
This may require the conversion routine to execute the same decision tree for each field for each record even though each field has known characteristics that do not change on a row by row basis. Therefore, many computer cycles are wasted by asking questions such as "Is this field of type character, integer, etc.?" over and over for each data field.
Based on the foregoing, there is a need for a system that provides efficient conversion of data fields.
_1_ SUMMARY OF THE INVENTION
One embodiment of the present invention is a system for converting data from input field types to output field types. The system receives a plurality of input attributes and output attributes from an application program, dynamically generates a plurality of data field conversion routines for each set of input attributes and output attributes, and stores the plurality of data field conversion routines in memory that is accessible to the application program.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 is a block diagram that illustrates an overview of the functionality of an optimized conversion generator system in accordance with one embodiment of the present invention.
Fig. 2 is a flowchart of the steps performed by the system in accordance with one embodiment of the present invention to generate optimized conversion routines.
Fig. 3 is a flowchart of the steps executed by the application when using the routines to convert input fields to output fields.
Fig. 4 is a flowchart of the code generating steps executed the conversion generator system to generate code when called by the application.
Figs. Sa and Sb illustrate a general example of dynamic code building that is used in one embodiment of the present invention.
Figs. 6a - 6h illustrate a specific example of a dynamic code generation routine that performs CHARACTER to CHARACTER conversions.
FIELD OF THE INVENTION
The present invention is directed to computer data. More particularly, the present invention is directed to the conversion of one type of computer data field to another type.
BACKGROUND OF THE INVENTION
In many instances during computer processing of information, computer data must be converted from one data field type to another. For example, whenever data is passed from one program to another, the data typically goes though several conversions during the process, such as converting from text digits to a binary number.
The typical technique for converting data includes using a generic data conversion routine. When an entire record of data must be converted, the conversion routine must determine what the characteristics or attributes are for each of the data fields in the record.
This may require the conversion routine to execute the same decision tree for each field for each record even though each field has known characteristics that do not change on a row by row basis. Therefore, many computer cycles are wasted by asking questions such as "Is this field of type character, integer, etc.?" over and over for each data field.
Based on the foregoing, there is a need for a system that provides efficient conversion of data fields.
_1_ SUMMARY OF THE INVENTION
One embodiment of the present invention is a system for converting data from input field types to output field types. The system receives a plurality of input attributes and output attributes from an application program, dynamically generates a plurality of data field conversion routines for each set of input attributes and output attributes, and stores the plurality of data field conversion routines in memory that is accessible to the application program.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 is a block diagram that illustrates an overview of the functionality of an optimized conversion generator system in accordance with one embodiment of the present invention.
Fig. 2 is a flowchart of the steps performed by the system in accordance with one embodiment of the present invention to generate optimized conversion routines.
Fig. 3 is a flowchart of the steps executed by the application when using the routines to convert input fields to output fields.
Fig. 4 is a flowchart of the code generating steps executed the conversion generator system to generate code when called by the application.
Figs. Sa and Sb illustrate a general example of dynamic code building that is used in one embodiment of the present invention.
Figs. 6a - 6h illustrate a specific example of a dynamic code generation routine that performs CHARACTER to CHARACTER conversions.
DETAILED DESCRIPTION
One embodiment of the present invention is a system that generates optimized data field to data field conversion routines for each type of conversion required by an application program. Fig. 1 is a block diagram that illustrates an overview of the functionality of an S optimized conversion generator system 20 in accordance with one embodiment of the present invention. System 20 can be implemented in software and executed on a general purpose computer that includes a central processing unit, and memory. In one embodiment, system 20 is implemented with IBM/360 machine instructions.
An application program 10 requires one or more types of field conversions to be executed. For each type of conversion, application 10 provides to system 20 the input (or "source") and output (or "destination") field attributes. For each set of input and output field attributes, system 20 dynamically generates an optimized conversion routine 30 that performs the conversion. The optimized routines 30 are placed in storage that is available to application 10.
The routines 30 in one embodiment are generated as stand-alone routines that are capable of being serially reusable and are called by application 10 using, for example, an application program interface ("API") when a conversion is required. In another embodiment, the routines 30 are generated as code chunks that are inserted inline with application 10 and are directly accessed when a conversion is required.
One benefit of the present invention is that by building optimized conversion routines specifically tailored to the input and output field attributes, every execution of the routine saves numerous instructions that would normally be needed to identify field attributes each time the conversion is executed.
_3_ Fig. 2 is a flowchart of the steps performed by system 20 in accordance with one embodiment of the present invention to generate optimized conversion routines 30. The steps are executed by system 20 after application 10 determines at step 100 what attributes the input fields and output fields have.
At step 102, system 20 sets up the default process options of the generated conversion routines 30. The options may include whether the generated conversion routines 30 will be callable functions (i.e., able to be called by application 10), or copied inline into application 10. Step 102 builds a template interface block 104 which is an interface between application and conversion generator system 20. Step 102 also generates an initiation call 106 that 10 obtains the necessary storage and checks for errors.
At step 108, a loop is initiated. The loop continues until all fields that must be converted are exhausted.
Within the loop, at step 110 each set of input and output field attributes is received from application 10. The attributes are received through an API, and step 110 also builds a common field con~~ersion interface block 116 based on the attributes.
At step 112, the code generator of system 20 is called, using the common interface block 116. Step 112 generates code 118.
At step 114. a function pointer that points to the generated field conversion routine 30 is saved.
Fig. 3 is a flowchart of the steps executed by application 10 when using routines 30 to convert input fields to output fields.
During step 122, the application is processing. At step 124, the application obtains source or input data to convert. Typically, step 124 involves reading one or more records.
_4_ At step 126, a loop is initiated for each record read. At step 128, in one embodiment the appropriate conversion routine 30 for the conversion is called.
When all the data field and records are converted, at step 132 the code generator system 20 is called for termination. This results in freeing up memory at step 134.
At step 136, application 10 continues to process. Finally, at step 138 application 10 is completed.
Fig. 4 is a flowchart of the code generating steps executed by conversion generator system 20 to generate code when called by application 10.
At step 200, system 20 initializes by, for example, establishing the required storage, checking for invalid options, and specifying how the code should be generated.
At step 202, system 20 validates specific field conversion options such as verifying that the input and output lengths are correct. Step 202 also determines how big the code will be when generated. This can be used by application 10 if the generated code will be stored inline.
At step 204, system 20 builds the conversion routine using field conversion interface block 116.
At step 206, the storage obtained at step 200 is released.
Steps 202 and 204 go through the same internal process. Therefore, at step 208 the input field type is determined. Examples of input field types include character input 210 or special time format input 212. However, any input field type is supported by the present invention.
_5_ Similarly, at step 214 the output field type is determined. Examples of output field types also include character input 213 or special time format input 215, but any output field type is supported by the present invention.
At step 216, if step 202 was executed, the size of the generated code is determined.
At step 218, if step 204 was executed, the field conversion routines 30 are generated.
As disclosed, system 20 in accordance with one embodiment of the present invention dynamically generates optimized conversion routines 30 for each set of input and output field attributes. Routines 30 are then utilized by application 10 to process conversions. Input and output fields are categorized into archetypal data types by system 20, each with definable attributes and conversion behaviors. For example:
~ Character data types will be a fixed length field with a maximum length attribute and a CCS>D (or character set code page) attribute.
~ Date data types will be a fixed length field with a maximum length attribute and a format attribute (ISO, EUR, etc) which determines location and type of separators used in date.
Some previously described or additional features included in one embodiment of optimized conversion generator system 20 include:
~ Optionally obtain and free storage for API control blocks and/or generated code.
~ API control blocks can be chained and templated by API management functions.
~ API control blocks can be built through use of a macro interface.
~ Conversion routines can utilize registers to address the input and output field locations directly. The registers can be chosen by application 10 through API
parameters.
~ The source field address register may optionally be incremented to the end of the input field after conversion based on API parameters.
~ The target field address register may optionally be incremented to the end of the formatted field after conversion based on API parameters.
~ An additional register may be incremented by the length of the converted field based on API parameters.
~ Standard Linkage may be generated for conversion routines based on API
parameters.
~ Conversion Error exits may be specified to handle enumerated conversion error conditions based on API parameters.
~ Character Code Set translation conversion code can be generated based on API
parameters (i.e., ASCII character fields can be translated to EBCDIC character fields).
~ Conversion routines can be generated to utilize the latest instructions supported by the level of the operating system for which the code is being generated.
In one embodiment, system 20 dynamically generates code by building code chunks in storage accessible by calling application 10 based on various settings in the API control block. Generating the code involves the following steps, as discussed in conjunction with the flowcharts:
1. Obtain storage for the code.
2. Identify code templates needed.
One embodiment of the present invention is a system that generates optimized data field to data field conversion routines for each type of conversion required by an application program. Fig. 1 is a block diagram that illustrates an overview of the functionality of an S optimized conversion generator system 20 in accordance with one embodiment of the present invention. System 20 can be implemented in software and executed on a general purpose computer that includes a central processing unit, and memory. In one embodiment, system 20 is implemented with IBM/360 machine instructions.
An application program 10 requires one or more types of field conversions to be executed. For each type of conversion, application 10 provides to system 20 the input (or "source") and output (or "destination") field attributes. For each set of input and output field attributes, system 20 dynamically generates an optimized conversion routine 30 that performs the conversion. The optimized routines 30 are placed in storage that is available to application 10.
The routines 30 in one embodiment are generated as stand-alone routines that are capable of being serially reusable and are called by application 10 using, for example, an application program interface ("API") when a conversion is required. In another embodiment, the routines 30 are generated as code chunks that are inserted inline with application 10 and are directly accessed when a conversion is required.
One benefit of the present invention is that by building optimized conversion routines specifically tailored to the input and output field attributes, every execution of the routine saves numerous instructions that would normally be needed to identify field attributes each time the conversion is executed.
_3_ Fig. 2 is a flowchart of the steps performed by system 20 in accordance with one embodiment of the present invention to generate optimized conversion routines 30. The steps are executed by system 20 after application 10 determines at step 100 what attributes the input fields and output fields have.
At step 102, system 20 sets up the default process options of the generated conversion routines 30. The options may include whether the generated conversion routines 30 will be callable functions (i.e., able to be called by application 10), or copied inline into application 10. Step 102 builds a template interface block 104 which is an interface between application and conversion generator system 20. Step 102 also generates an initiation call 106 that 10 obtains the necessary storage and checks for errors.
At step 108, a loop is initiated. The loop continues until all fields that must be converted are exhausted.
Within the loop, at step 110 each set of input and output field attributes is received from application 10. The attributes are received through an API, and step 110 also builds a common field con~~ersion interface block 116 based on the attributes.
At step 112, the code generator of system 20 is called, using the common interface block 116. Step 112 generates code 118.
At step 114. a function pointer that points to the generated field conversion routine 30 is saved.
Fig. 3 is a flowchart of the steps executed by application 10 when using routines 30 to convert input fields to output fields.
During step 122, the application is processing. At step 124, the application obtains source or input data to convert. Typically, step 124 involves reading one or more records.
_4_ At step 126, a loop is initiated for each record read. At step 128, in one embodiment the appropriate conversion routine 30 for the conversion is called.
When all the data field and records are converted, at step 132 the code generator system 20 is called for termination. This results in freeing up memory at step 134.
At step 136, application 10 continues to process. Finally, at step 138 application 10 is completed.
Fig. 4 is a flowchart of the code generating steps executed by conversion generator system 20 to generate code when called by application 10.
At step 200, system 20 initializes by, for example, establishing the required storage, checking for invalid options, and specifying how the code should be generated.
At step 202, system 20 validates specific field conversion options such as verifying that the input and output lengths are correct. Step 202 also determines how big the code will be when generated. This can be used by application 10 if the generated code will be stored inline.
At step 204, system 20 builds the conversion routine using field conversion interface block 116.
At step 206, the storage obtained at step 200 is released.
Steps 202 and 204 go through the same internal process. Therefore, at step 208 the input field type is determined. Examples of input field types include character input 210 or special time format input 212. However, any input field type is supported by the present invention.
_5_ Similarly, at step 214 the output field type is determined. Examples of output field types also include character input 213 or special time format input 215, but any output field type is supported by the present invention.
At step 216, if step 202 was executed, the size of the generated code is determined.
At step 218, if step 204 was executed, the field conversion routines 30 are generated.
As disclosed, system 20 in accordance with one embodiment of the present invention dynamically generates optimized conversion routines 30 for each set of input and output field attributes. Routines 30 are then utilized by application 10 to process conversions. Input and output fields are categorized into archetypal data types by system 20, each with definable attributes and conversion behaviors. For example:
~ Character data types will be a fixed length field with a maximum length attribute and a CCS>D (or character set code page) attribute.
~ Date data types will be a fixed length field with a maximum length attribute and a format attribute (ISO, EUR, etc) which determines location and type of separators used in date.
Some previously described or additional features included in one embodiment of optimized conversion generator system 20 include:
~ Optionally obtain and free storage for API control blocks and/or generated code.
~ API control blocks can be chained and templated by API management functions.
~ API control blocks can be built through use of a macro interface.
~ Conversion routines can utilize registers to address the input and output field locations directly. The registers can be chosen by application 10 through API
parameters.
~ The source field address register may optionally be incremented to the end of the input field after conversion based on API parameters.
~ The target field address register may optionally be incremented to the end of the formatted field after conversion based on API parameters.
~ An additional register may be incremented by the length of the converted field based on API parameters.
~ Standard Linkage may be generated for conversion routines based on API
parameters.
~ Conversion Error exits may be specified to handle enumerated conversion error conditions based on API parameters.
~ Character Code Set translation conversion code can be generated based on API
parameters (i.e., ASCII character fields can be translated to EBCDIC character fields).
~ Conversion routines can be generated to utilize the latest instructions supported by the level of the operating system for which the code is being generated.
In one embodiment, system 20 dynamically generates code by building code chunks in storage accessible by calling application 10 based on various settings in the API control block. Generating the code involves the following steps, as discussed in conjunction with the flowcharts:
1. Obtain storage for the code.
2. Identify code templates needed.
3. Move code templates.
4. Modify code templates.
5. Return executable code to calling application.
Further, in one embodiment system 20 can optionally, based on the API
specification, generate program debugging instrumentation for the dynamically generated code.
This instrumentation can include an optional dynamically allocated output file containing, for each field conversion: a report of the API options used for each dynamically generated routine that can be used to insure correctness of field attributes and general processing options; and a disassembled listing of the dynamically generated routine provided by an internal disassembler within system 20 that can be used to identify conversion code inaccuracies and areas of further optimization, and to help resolve generated code failures.
Figs. Sa and Sb illustrate a general example of dynamic code building that is used in one embodiment of the present invention.
Figs. 6a - 6h illustrate a specific example of a dynamic code generation routine that performs CHARACTER to CHARACTER conversions.
Several embodiments of the present invention are specifically illustrated and/or described herein. However, it will be appreciated that modifications and variations of the present invention are covered by the above teachings and within the purview of the appended claims without departing from the spirit and intended scope of the invention.
_g_
Further, in one embodiment system 20 can optionally, based on the API
specification, generate program debugging instrumentation for the dynamically generated code.
This instrumentation can include an optional dynamically allocated output file containing, for each field conversion: a report of the API options used for each dynamically generated routine that can be used to insure correctness of field attributes and general processing options; and a disassembled listing of the dynamically generated routine provided by an internal disassembler within system 20 that can be used to identify conversion code inaccuracies and areas of further optimization, and to help resolve generated code failures.
Figs. Sa and Sb illustrate a general example of dynamic code building that is used in one embodiment of the present invention.
Figs. 6a - 6h illustrate a specific example of a dynamic code generation routine that performs CHARACTER to CHARACTER conversions.
Several embodiments of the present invention are specifically illustrated and/or described herein. However, it will be appreciated that modifications and variations of the present invention are covered by the above teachings and within the purview of the appended claims without departing from the spirit and intended scope of the invention.
_g_
Claims (20)
1. A method of converting a plurality of input field types to a plurality of output field types by an application program, said method comprising:
(a) receiving a first attribute of a first input field type and a second attribute of a first output field type;
(b) generating a first optimized conversion routine based on said first attribute and said second attribute; and (c) executing said first optimized conversion routine from said application program to convert said first input field type to said first output field type.
(a) receiving a first attribute of a first input field type and a second attribute of a first output field type;
(b) generating a first optimized conversion routine based on said first attribute and said second attribute; and (c) executing said first optimized conversion routine from said application program to convert said first input field type to said first output field type.
2. The method of claim 1, wherein step (c) comprises calling said first optimized conversion routine from said application.
3. The method of claim 1, wherein step (c) comprises storing said first optimized conversion routine inline with said application.
4. The method of claim 1, wherein step (b) is performed dynamically while said application program is executing.
5. The method of claim 1, further comprising:
(d) -receiving a third attribute of a second input field type and a fourth attribute of a second output field type;
(e) generating a second optimized conversion routine based on said third attribute and said fourth attribute; and (f) executing said second optimized conversion routine from said application program to convert said second input field type to said second output field type.
(d) -receiving a third attribute of a second input field type and a fourth attribute of a second output field type;
(e) generating a second optimized conversion routine based on said third attribute and said fourth attribute; and (f) executing said second optimized conversion routine from said application program to convert said second input field type to said second output field type.
6. The method of claim 1, wherein said first and second attribute is character type.
7. The method of claim 1, farther comprising generating program debugging instrumentation for said first optimized conversion routine.
8. A method of converting data from input field types to output field types, said method comprising:
(a) receiving a plurality of input attributes and output attributes from an application program;
(b) dynamically generating a plurality of data field conversion routines for each set of input attributes and output attributes; and (c) storing said plurality of data field conversion routines in memory accessible to said application program.
(a) receiving a plurality of input attributes and output attributes from an application program;
(b) dynamically generating a plurality of data field conversion routines for each set of input attributes and output attributes; and (c) storing said plurality of data field conversion routines in memory accessible to said application program.
9. The method of claim 8, wherein said data field conversion routines are callable by said application program.
10. The method of claim 8, wherein said data field conversion routines are stored inline said application program.
11. The method of claim 8, wherein step (b) is performed dynamically while said application program is executing.
12. The method of claim 8, wherein said input and output attributes are character type.
13. The method of claim 8, wherein said input and output attributes are date type.
14. The method of claim 8, further comprising generating program debugging instrumentation for said plurality of data field conversion routines.
15. A system for dynamically generating computer data field conversion routines, said system comprising:
a processor; and a memory device coupled to said processor;
wherein said system is adapted to receive a plurality of input attributes and output attributes from an application program; and wherein said memory device stores instructions that, when executed by said processor, cause said processor to:
dynamically generate a plurality of data field conversion routines for each set of input attributes and output attributes; and store said plurality of data field conversion routines in a second memory device accessible to said application program.
a processor; and a memory device coupled to said processor;
wherein said system is adapted to receive a plurality of input attributes and output attributes from an application program; and wherein said memory device stores instructions that, when executed by said processor, cause said processor to:
dynamically generate a plurality of data field conversion routines for each set of input attributes and output attributes; and store said plurality of data field conversion routines in a second memory device accessible to said application program.
16. The system of claim 15, wherein said data field conversion routines are callable by said application program.
17. The system of claim 15, wherein said data field conversion routines are stored inline said application program.
18. The system of claim 15, wherein said plurality of data field conversion routines are generated while said application program is executing.
19. The system of claim 15, wherein said input attributes are character type and said output attributes are date type.
20. The system of claim 15, wherein said processor further generates program debugging instrumentation for said plurality of data field conversion routines.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US27314999A | 1999-03-19 | 1999-03-19 | |
| US09/273,149 | 1999-03-19 | ||
| PCT/US2000/007288 WO2000057268A1 (en) | 1999-03-19 | 2000-03-17 | Generating optimized computer data field conversion routines |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2367061A1 true CA2367061A1 (en) | 2000-09-28 |
Family
ID=23042736
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002367061A Abandoned CA2367061A1 (en) | 1999-03-19 | 2000-03-17 | Generating optimized computer data field conversion routines |
Country Status (11)
| Country | Link |
|---|---|
| US (1) | US8108828B2 (en) |
| EP (1) | EP1183596B1 (en) |
| JP (1) | JP2002540500A (en) |
| KR (1) | KR20020021083A (en) |
| CN (1) | CN1252586C (en) |
| AU (1) | AU776882B2 (en) |
| BR (1) | BR0009162A (en) |
| CA (1) | CA2367061A1 (en) |
| IL (2) | IL145365A0 (en) |
| WO (1) | WO2000057268A1 (en) |
| ZA (1) | ZA200107669B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120233200A1 (en) * | 2011-03-11 | 2012-09-13 | Farahnaz Faegh | Database data localization |
| CN105718429B (en) * | 2014-12-04 | 2019-11-19 | 中兴通讯股份有限公司 | The method and device of inspection report generation |
| US10528328B2 (en) | 2015-12-08 | 2020-01-07 | Microsoft Technology Licensing, Llc | Learning from input patterns in Programing-By-Example |
Family Cites Families (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4751740A (en) * | 1984-12-10 | 1988-06-14 | Wang Laboratories, Inc. | Apparatus, method, and structure for translating a document having one structure into a document having another structure |
| US5410675A (en) * | 1989-08-21 | 1995-04-25 | Lisa M. Shreve | Method of conforming input data to an output data structure and engine for accomplishing same |
| US5299304A (en) * | 1991-04-16 | 1994-03-29 | International Business Machines Corporation | Method and apparatus for identifying multiple stage document format transformations |
| US5513323A (en) * | 1991-06-14 | 1996-04-30 | International Business Machines Corporation | Method and apparatus for multistage document format transformation in a data processing system |
| JPH05108641A (en) * | 1991-10-17 | 1993-04-30 | Fuji Xerox Co Ltd | Document style design supporting device |
| US5491628A (en) * | 1993-12-10 | 1996-02-13 | Xerox Corporation | Method and apparatus for document transformation based on attribute grammars and attribute couplings |
| US5649214A (en) * | 1994-09-20 | 1997-07-15 | Unisys Corporation | Method and apparatus for continued use of data encoded under a first coded character set while data is gradually transliterated to a second coded character set |
| US5629846A (en) * | 1994-09-28 | 1997-05-13 | General Electric Company | Method and system for document translation and extraction |
| US5708828A (en) * | 1995-05-25 | 1998-01-13 | Reliant Data Systems | System for converting data from input data environment using first format to output data environment using second format by executing the associations between their fields |
| DE19535306A1 (en) * | 1995-09-22 | 1997-03-27 | Siemens Ag | Process for converting different data formats |
| US5907709A (en) * | 1996-02-08 | 1999-05-25 | Inprise Corporation | Development system with methods for detecting invalid use and management of resources and memory at runtime |
| US5784635A (en) * | 1996-12-31 | 1998-07-21 | Integration Concepts, Inc. | System and method for the rationalization of physician data |
| US6549918B1 (en) * | 1998-09-21 | 2003-04-15 | Microsoft Corporation | Dynamic information format conversion |
| US6502236B1 (en) * | 1999-03-16 | 2002-12-31 | Fujitsu Network Communications, Inc. | Method and apparatus for automatic generation of programs for processing data units of multiple formats |
| US6772413B2 (en) * | 1999-12-21 | 2004-08-03 | Datapower Technology, Inc. | Method and apparatus of data exchange using runtime code generator and translator |
-
2000
- 2000-03-17 JP JP2000607077A patent/JP2002540500A/en active Pending
- 2000-03-17 AU AU38999/00A patent/AU776882B2/en not_active Ceased
- 2000-03-17 BR BR0009162-6A patent/BR0009162A/en not_active IP Right Cessation
- 2000-03-17 CA CA002367061A patent/CA2367061A1/en not_active Abandoned
- 2000-03-17 WO PCT/US2000/007288 patent/WO2000057268A1/en not_active Application Discontinuation
- 2000-03-17 IL IL14536500A patent/IL145365A0/en active IP Right Grant
- 2000-03-17 EP EP00918135.5A patent/EP1183596B1/en not_active Expired - Lifetime
- 2000-03-17 KR KR1020017011893A patent/KR20020021083A/en not_active Application Discontinuation
- 2000-03-17 CN CNB008052026A patent/CN1252586C/en not_active Expired - Fee Related
-
2001
- 2001-09-10 IL IL145365A patent/IL145365A/en unknown
- 2001-09-18 ZA ZA200107669A patent/ZA200107669B/en unknown
-
2008
- 2008-04-16 US US12/104,076 patent/US8108828B2/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| EP1183596B1 (en) | 2017-04-26 |
| WO2000057268A1 (en) | 2000-09-28 |
| CN1359486A (en) | 2002-07-17 |
| JP2002540500A (en) | 2002-11-26 |
| CN1252586C (en) | 2006-04-19 |
| IL145365A (en) | 2006-12-31 |
| IL145365A0 (en) | 2002-06-30 |
| WO2000057268A9 (en) | 2002-06-20 |
| US20080216099A1 (en) | 2008-09-04 |
| EP1183596A4 (en) | 2003-02-05 |
| ZA200107669B (en) | 2003-02-20 |
| US8108828B2 (en) | 2012-01-31 |
| EP1183596A1 (en) | 2002-03-06 |
| KR20020021083A (en) | 2002-03-18 |
| BR0009162A (en) | 2003-03-05 |
| AU776882B2 (en) | 2004-09-23 |
| AU3899900A (en) | 2000-10-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110096338B (en) | Intelligent contract execution method, device, equipment and medium | |
| CN108108162B (en) | Application programming interface generation method and device | |
| US8458681B1 (en) | Method and system for optimizing the object code of a program | |
| US8924944B2 (en) | Implementation of distributed methods that support generic functions | |
| US20090037459A1 (en) | Annotation data handlers for data stream processing | |
| KR20040097909A (en) | Reflection-based processing of input parameters for commands | |
| US20110314459A1 (en) | Compiler with user-defined type inference rules | |
| CN110673856B (en) | Data processing method and device and machine-readable storage medium | |
| US11922168B2 (en) | Stack traces using shadow stack | |
| CN111400387A (en) | Conversion method and device for import and export data, terminal equipment and storage medium | |
| CN111124551A (en) | Data serialization and deserialization method and device and computer equipment | |
| US8108828B2 (en) | System for generating optimized computer data field conversion routines | |
| US7406681B1 (en) | Automatic conversion of source code from 32-bit to 64-bit | |
| US6708310B1 (en) | Method and system for implementing user-defined codeset conversions in a computer system | |
| CN111475150A (en) | Cross-language binding method, device, equipment and storage medium | |
| JP5377522B2 (en) | Efficiently correlate nominally incompatible types | |
| CN115310127A (en) | Data desensitization method and device | |
| US7555708B2 (en) | Mechanism for converting text output into objects | |
| CN113688056A (en) | Breakpoint debugging control method and related equipment | |
| CN112380142A (en) | Interface document management method and device and test equipment | |
| US7330870B1 (en) | Streaming computer system and method with multi-version protocol compatibility | |
| CN111399842A (en) | Code compiling method and device | |
| CN117873607A (en) | Processing method and device for target operation corresponding to custom function | |
| CN117667725A (en) | Database script generation method, device and equipment and readable storage medium | |
| CN114090007A (en) | Multi-language text generation method, terminal and storage medium suitable for development language |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| FZDE | Discontinued |