Identification of load utility
First Claim
Patent Images
1. A computer implemented method for identifying a load utility, the method comprising:
- receiving a first information, wherein the first information comprises one or more records, the one or more records being associated with a load utility and defining a library of parameters, wherein the first information comprises transaction data, wherein transaction data comprises at least one of an account name, an account number, an account balance, a transaction amount, a transaction date, a payee, a signature, and/or a memo, wherein the library of parameters defines a first syntax, wherein the library of parameters comprise a Log table, a Work table, a Uniqueness Violation (UV) table, and/or an Error table;
counting the number of records in the first information;
comparing the counted number of records to a predetermined threshold value;
identifying a load utility to be used to load the records into a database based on the comparison between the counted number of records and the predetermined threshold value, wherein identifying further comprises (i) determining that the number of records is greater than the predetermined threshold, and loading the first information into a database using a multiload load utility (MLOAD);
(ii) determining that the number of records is less than the predetermined threshold, and loading the first information into the database using a Teradata load utility (TPUMP);
or (iii) determining that the number of records equals the predetermined threshold, and loading the first information into a data base using either the MLOAD or the TPUMP utility, whereby larger volumes of records are processed using the MLOAD load utility and smaller volumes of records are processed using the TPUMP utility, and whereby less computer resources are used to implement TPUMP than MLOAD thereby providing for conservation of computer resources;
loading the first information into the database using the MLOAD load utility or the TPUMP utility based on at least comparing the counted number of records to the predetermined threshold value;
converting the first syntax of the library of parameters to a second syntax, wherein the second syntax is associated with the identified load utility, wherein converting the first syntax comprises generating at least one script and computer code of the library of the parameters using the second syntax, wherein converting further comprises;
identifying one or more unassociated parameters, wherein the one or more unassociated parameters are not associated with the identified load utility;
automatically editing the one or more unassociated parameters to comply with the second syntax, wherein automatically editing further comprises automatically adding a statement and a parameter into the library of parameters associated with the identified load utility; and
updating the library of parameters based on at least automatically editing the one or more unassociated parameters;
validating the second syntax of the library of parameters, wherein validating the second syntax of the library of parameters comprises using a compiler; and
writing an output parameter to a memory location based on positive validation of the second syntax of the library of parameters.
1 Assignment
0 Petitions
Accused Products
Abstract
Embodiments of the invention are directed to systems, methods and computer program products for converting MLOAD and TPUMP operations. In some embodiments, a system is configured to: receive a first information, wherein the first information comprises at least one piece of data; count the number of pieces of data; compare the counted number of pieces of data to a predetermined threshold value; and identify a load utility based on the comparison between the counted number of pieces of data and the predetermined threshold value.
-
Citations
24 Claims
-
1. A computer implemented method for identifying a load utility, the method comprising:
-
receiving a first information, wherein the first information comprises one or more records, the one or more records being associated with a load utility and defining a library of parameters, wherein the first information comprises transaction data, wherein transaction data comprises at least one of an account name, an account number, an account balance, a transaction amount, a transaction date, a payee, a signature, and/or a memo, wherein the library of parameters defines a first syntax, wherein the library of parameters comprise a Log table, a Work table, a Uniqueness Violation (UV) table, and/or an Error table; counting the number of records in the first information; comparing the counted number of records to a predetermined threshold value; identifying a load utility to be used to load the records into a database based on the comparison between the counted number of records and the predetermined threshold value, wherein identifying further comprises (i) determining that the number of records is greater than the predetermined threshold, and loading the first information into a database using a multiload load utility (MLOAD);
(ii) determining that the number of records is less than the predetermined threshold, and loading the first information into the database using a Teradata load utility (TPUMP);
or (iii) determining that the number of records equals the predetermined threshold, and loading the first information into a data base using either the MLOAD or the TPUMP utility, whereby larger volumes of records are processed using the MLOAD load utility and smaller volumes of records are processed using the TPUMP utility, and whereby less computer resources are used to implement TPUMP than MLOAD thereby providing for conservation of computer resources;loading the first information into the database using the MLOAD load utility or the TPUMP utility based on at least comparing the counted number of records to the predetermined threshold value; converting the first syntax of the library of parameters to a second syntax, wherein the second syntax is associated with the identified load utility, wherein converting the first syntax comprises generating at least one script and computer code of the library of the parameters using the second syntax, wherein converting further comprises; identifying one or more unassociated parameters, wherein the one or more unassociated parameters are not associated with the identified load utility; automatically editing the one or more unassociated parameters to comply with the second syntax, wherein automatically editing further comprises automatically adding a statement and a parameter into the library of parameters associated with the identified load utility; and updating the library of parameters based on at least automatically editing the one or more unassociated parameters; validating the second syntax of the library of parameters, wherein validating the second syntax of the library of parameters comprises using a compiler; and writing an output parameter to a memory location based on positive validation of the second syntax of the library of parameters. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A computer program product for identifying a load utility, the computer program product comprising:
-
a non-transitory computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising; a computer readable program code configured to receive a first information, wherein the first information comprises one or more records, the one or more records being associated with a load utility and defining a library of parameters, wherein the first information comprises transaction data, wherein transaction data comprises at least one of an account name, an account number, an account balance, a transaction amount, a transaction date, a payee, a signature, and/or a memo, wherein the library of parameters defines a first syntax, wherein the library of parameters comprise a Log table, a Work table, a Uniqueness Violation (UV) table, and/or an Error table; a computer readable program code configured to count the number of records in the first information; a computer readable program code configured to compare the counted number of records to a predetermined threshold value; a computer readable program code configured to identify a load utility to be used to load the records into a database based on the comparison between the counted number of records and the predetermined threshold value, wherein identifying further comprises (i) determining that the number of records is greater than the predetermined threshold, and loading the first information into a database using a multiload load utility (MLOAD);
(ii) determining that the number of records is less than the predetermined threshold, and loading the first information into the database using a Teradata load utility (TPUMP);
or (iii) determining that the number of records equals the predetermined threshold, and loading the first information into a data base using either the MLOAD or the TPUMP utility, whereby larger volumes of records are processed using the MLOAD load utility and smaller volumes of records are processed using the TPUMP utility, and whereby less computer resources are used to implement TPUMP than MLOAD thereby providing for conservation of computer resources;a computer readable program code configured to load the first information into the database using the MLOAD load utility or the TPUMP utility based on at least comparing the counted number of records to the predetermined threshold value; a computer readable program code configured to convert the first syntax of the library of parameters to a second syntax, wherein the second syntax is associated with the identified load utility, wherein converting the first syntax comprises generating at least one script and computer code of the library of the parameters using the second syntax, wherein the computer program code for converting further comprises; a computer readable program code configured to identify one or more unassociated parameters, wherein the one or more unassociated parameters are not associated with the identified load utility; a computer readable program code configured to automatically edit the one or more unassociated parameters to comply with the second syntax, wherein automatically editing further comprises automatically adding a statement and a parameter into the library of parameters associated with the identified load utility; and a computer readable program code configured to update the library of parameters based on at least automatically editing the one or more unassociated parameters; a computer readable program code configured to validate the second syntax of the library of parameters, wherein validating the second syntax of the library of parameters comprises using a compiler; and a computer readable program code configured to write an output parameter to a memory location based on positive validation of the second syntax of the library of parameters. - View Dependent Claims (14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24)
-
Specification