COBOL

The objective of this project is to write a Cobol program according to this specification : I have provided detailed information under Deliverables. 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request. 3) Complete ownership and distribution copyrights to all work purchased.

## Deliverables

1) Read a sequential input file of inventory information ordered by Part Number. 2) Read a sequential transaction file of inventory information also ordered by Part Number. 3) The Transaction file will have the same physical layout as the Input file, with an additional field for the Action code. 4) Using the "Balance Line algorithm" perform maintenance on the Input file by applying Insert, Update, or Delete transactions from the Transactionn file. 5) The Transaction file will contain Insert, Update, Delete records, as indicated by the contents of the final field in the file: 'I' for insert action, 'U' for Update action, and 'D' for Delete action. 6) The program will produce an Ouput file, with the same layout as the Input file. Records on the Output file will be Inserted (added) from the transaction file, or updated from the Transaction file. A transaction with a Delete action will prevent the corresponding record on the Input file from being written to the Output file. Also, records on the Input file without key values on the Transaction file will be written unchanged to the Output file: A) If a transaction is an Insert, write the record to the Output file in correct order by the Key field. B) If a transaction is an Update, move the Inv-Date from the transaction to the output record but ADD the YTD-Sales Amount from the transaction to the ouptut record. Simply MOVE the other fields from the Input record to the Output record. C) If a transaction is a Delete, do not write the correspnding Input record to the Output file - this casues the record to stay on the Input file but not be written to the Output file. D) If there is no matching Transaction record for a record on the Input file, write that record to the Output file. 7) Create a simple error report (using an output print file - no DISPLAY statements) to show any instances of the 4 errors that may occur: A) Attempt to Insert a record with an existing Key field value already on the Input file B) Attempt to Update a record that does not exist, i.e., without an existing Key field value C) Attempt to Delete a record that does not exist, i.e., without an existing Key field value D) A transaction record without a valid I.,U. or D Action code. 8) Place a heading line on the error report, called 'ACME File Maintenance Error Report', skip two lines, write column headings for 'Error Message' and 'Key Value'. Individual report lines wil consist of and error message and the associated value of the Key Field. 9) Follow all requirements regarding program comments, as published on the home page. Input File: (definition also to be used for Output File) Inventory-Information [url removed, login to view] Definition: INV-ID 3 characters. INV-DATE 8 characters (MMDDYYYY). INV-DESCRIPTION 12 characters. INV-YTD-SALES 5 numeric Transaction File: [url removed, login to view] Definition: TRAN-ID 3 characters. TRAN-DATE 8 characters (MMDDYYYY). TRAN-DESCRIPTION 12 characters. TRAN-YTD-SALES 5 numeric TRAN-ACTION-CODE 1 character I will provide the input and transaction file. I also have a example that my help. In fact the example could easily be just fixed to meet the above standards. I usually use NetExpress but this is not necessay.

## Platform

I use NetExpress on campus. I believe they have windows xp but it really doesn't matter

## Deadline information

I need done as soon as possible. It is not hard and I will provide some examples which will make it much easier.

Teknik MySQL PHP Perancangan Perangkat Lunak Pengujian Perangkat Lunak

ID Proyek: #2884454

Tentang proyek