Systems and methods for data brick creation and use
AssigneeIII Holdings 1, LLC
InventorsJoe M. Fenicle, Krishna K. Lingamneni, Ron Sexton, Martin D. Lantry, Arnold S. Santos
Life of this patent
Estimating the term…
Abstract
Data Brick is a state of the art solution to access the data through high speed data access mechanism that is exceptionally fast and is associated with low CPU consumption cost. The Data Brick stores relatively static reference data in the form of a programming language Load Module. The Load module contains the data can be launched into the application program memory and this data can be accessed very efficiently in a programming language program. Static application data that is accessed by multiple applications in a mainframe Batch environment is a prime candidate for the Data Brick.
Claims12
A system comprising:
- a processor;
- memory having instructions stored thereon that, in response to execution by the processor, cause the system to perform operations comprising:
- retrieving, by a program, static data stored in a dataset from a database;
- prior to invoking a linker, creating, by the program, a file having a layout that is the same as a layout of a COBOL object module, wherein the program is not a compiler, wherein the file created by the program includes 1) a header record indicating a name associated with the file, 2) a set of contiguous records that include the static data, and 3) a trailer record indicating record count information;
- invoking, by the program, the linker via a link edit command that produces a load module from the file;
- and
- providing the load module to an application that specifies a pointer associated with the load module, wherein the load module is provided such that the static data included in the file is accessible to the application.
A non-transitory computer readable medium having program instructions stored thereon, wherein the program instructions are executable by a computer system to cause the computer system perform operations comprising:
- reading static data from a database source;
- prior to invoking a linker, writing an output file via a program other than a COBOL compiler, wherein the output file has a layout that is the same as a layout of a COBOL object module created by the compiler, wherein the output file includes 1) a header record indicating a name associated with the output file, 2) a set of contiguous records that include the static data, and 3) a trailer record indicating record count information;
- and
- invoking the linker that accesses the written output file and inserts the static data into a linkage section of an application such that the static data is accessible to the application upon execution.
Dependencies are inferred from the claim text.