Identification of load utility

• US 9,646,065 B2
• Filed: 05/20/2016
• Issued: 05/09/2017
• Est. Priority Date: 06/13/2013
• Status: Active Grant

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Samantaray, Sushanta, Vanga, Naga Lakshmi, Mahankali, Nagaraju, Mohan, Dineshkumar
• Primary Examiner(s): PHILLIPS, III, ALBERT M
• Application Number:
  US15/160,304
• Publication Number:
  US 20160267124A1
• Time in Patent Office: 354 Days
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/24 Querying
• CPC Class Codes: G06F 16/2455 Query execution
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

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.

Claims

1. An apparatus for identifying a load utility, the apparatus comprising:

a memory;

at least one processor; and

a module stored in the memory, wherein said module comprising computer instruction code executable by the at least one processor, and structured to cause said at least one processor 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;

count the number of records in the first information;

compare the counted number of records to a predetermined threshold value;

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;

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;

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 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;

validate the second syntax of the library of parameters, wherein validating the second syntax of the library of parameters comprises using a compiler; and

write an output parameter to a memory location based on positive validation of the second syntax of the library of parameters.

2. The apparatus of claim 1, wherein if the number of records equals the predetermined threshold either loading the first information into a data base using the MLOAD utility for increased accuracy or loading the first information into a data base using the TPUMP utility for conservation of computing resources.

3. The apparatus of claim 1, wherein when said processor automatically edits the one or more unassociated parameters to comply with the second syntax, said processor deletes the unassociated parameters.

4. The apparatus of claim 1, wherein counting the number of records comprises storing the counted number of records in a database.

5. The apparatus of claim 1, wherein the counted number of records is a numerical value.

6. The apparatus of claim 1, wherein the counted number of records is used to determine the volume of the first information.

7. The apparatus of claim 1, wherein the predetermined threshold value is stored in a memory location.

8. The apparatus of claim 1, wherein the predetermined threshold value is a numerical value.

9. The apparatus of claim 1, wherein identifying the load utility further comprises loading the first information to a memory location using the identified load utility.

10. The apparatus of claim 1, wherein identifying the load utility occurs substantially simultaneously to receiving the first information.

11. The apparatus of claim 1, wherein the predetermined threshold value is configurable by a user.

12. The apparatus of claim 1, wherein comparing the counted number of records to the predetermined threshold value comprises subtracting the number of records from the threshold value to obtain a difference value.

13. The apparatus of claim 12, wherein the difference value is used to determine the load utility.

14. A system for identifying a load utility, the system comprising:

a memory;

at least one processor; and

a module stored in the memory, wherein said module comprising computer instruction code executable by the at least one processor, and structured to cause said at least one processor 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;

count the number of records in the first information;

compare the counted number of records to a predetermined threshold value;

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;

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;

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 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;

validate the second syntax of the library of parameters, wherein validating the second syntax of the library of parameters comprises using a compiler; and

write an output parameter to a memory location based on positive validation of the second syntax of the library of parameters.

15. The system of claim 14, wherein if the number of records equals the predetermined threshold either loading the first information into a data base using the MLOAD utility for increased accuracy or loading the first information into a data base using the TPUMP utility for conservation of computing resources.

16. The system of claim 14 wherein when said processor automatically edits the one or more unassociated parameters to comply with the second syntax, said processor deletes the unassociated parameters.

17. The system of claim 14, wherein counting the number of records comprises storing the counted number of records in a database.

18. The system of claim 14, wherein the counted number of records is a numerical value.

19. The system of claim 14, wherein the counted number of records is used to determine the volume of the first information.

20. The system of claim 14, wherein the predetermined threshold value is stored in a memory location.

21. The system of claim 14, wherein the predetermined threshold value is a numerical value.

22. The system of claim 14, wherein identifying the load utility further comprises loading the first information to a memory location using the identified load utility.

23. The system of claim 14, wherein identifying the load utility occurs substantially simultaneously to receiving the first information.

24. The system of claim 14, wherein the predetermined threshold value is configurable by a user.

25. The system of claim 14, wherein comparing the counted number of records to the predetermined threshold value comprises subtracting the number of records from the threshold value to obtain a difference value.

26. The system of claim 25, wherein the difference value is used to determine the load utility.