Show Bid Request
COBOL
Bid Request Id: 35377
|
|
|
|
Posted by: |
SimuGD (14 ratings)
(Software buyer rating 10 )
|
|
Non-action Ratio: |
Very Good - 0.00%
|
|
Posted: |
Nov 14, 2002
8:17:23 AM EDT
|
|
Bidding Closes: |
Nov 15, 2002
8:40:18 AM EDT
|
|
Viewed (by coders): |
113 times
|
|
Deadline: |
11/15/2002 10:40:18 AM
TIME EXPIRED
|
|
|
|
|
Description:
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 INPUT5.dat
Definition:
INV-ID 3 characters.
INV-DATE 8 characters (MMDDYYYY).
INV-DESCRIPTION 12 characters.
INV-YTD-SALES 5 numeric
Transaction File: TRANS5.dat
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
Must be 100% finished and received by buyer on:
Nov 15, 2002 10:40:18 AM EDT
Deadline legal notes: All times are expressed in the time zone of the site EDT (UT - 5). If the buyer omitted a time, then the deadline is 11:59:59 PM EDT on the indicated date.
Special Conditions / Other:
I need done as soon as possible. It is not hard and I will provide some examples which will make it much easier.
Remember that contacting the other party outside of the site (by email, phone, etc.) on all business projects < $500 (before the buyer's money is escrowed) is a violation of both the software buyer and seller agreements.
We monitor all site activity for such violations and can instantly expel transgressers on the spot, so we thank you in advance for your cooperation.
If you notice a violation please help out the site and report it. Thanks for your help.
|
|
|
Bidding/Comments:
|
All monetary amounts on the site are in United States dollars.
Rent a Coder is a closed auction, so coders can only see their own bids and comments. Buyers can view every posting made on their bid requests. |
See all rejected bids (and all comments)
| Name |
Bid Amount
|
Date |
Coder Rating |
|
|
This bid was accepted by the buyer!
|
$30 (USD)
|
Nov 14, 2002
3:04:14 PM EDT
|
9.93
(Excellent)
|
|
|
| Hi,
Thanks for the detailed program spec given. If it is Ok with you,I can do this work in Fujitsu Cobol 3.0 which is the cobol compiler I have.
I will use the std commands so that it will compile in all compilers with out difficulty.
I can finish in time provided you accept the bid and give the input and sample prgs if any at the earliest(by end of day today).
I have good exp in doing cobol assignments and will do good quality work with well written comment.
I put the bid amount as 30$ as the deadline is very close. The bid amount can be reduced
provided you give 3 to 4 days time after bid acceptance.
Thanks
PVA
|
|
|
|
|
|
|
