This program is a sequential update of a student master file. Your program must read the master file and the transactions file and create a new master file. You must also create both a transaction register of all good transactions (the ones that were acted upon and affected the file) and an exception/error report of all bad transactions. Both reports should include data and a message explaining what happened.

The master file is called SEQMST99.DAT and is located on the Web site. The layout of the master file is:

1 - 8	Identification Number
9 - 10	Title Code
11 - 32	Name (last/first m)
33 - 54	Street Address
55 - 72	City
73 - 74	State
75 - 79	ZIP
80 - 85	Total amount due
86 - 91	Total amount paid
92-93	Major
94	Number of Courses
95-99	Course 1
100 - 104	Course 2
105 - 109	Course 3
110 - 114	Course 4
115-119	Course 5
120 - 124	Course 6
125 - 129	Course 7

The transaction file is called TRANS99.DAT and is located on the Web site. The records are 131 characters long. There are six different transaction records: one for an add, one for a delete and four types of records for changes. These are shown in the descriptions/layouts below.

ADD: Add transactions have the same layout as the master file except that they have a space in character position 130 and the Record Action Code of A in character position 131. In processing the add transaction, you are simply using the information on the transaction to set-up a new master record of 129 characters. A successful ADD is listed on the transaction register. An unsuccessful add appears on the error report.

DELETE: Delete transactions have only the identification number in character positions 1 - 8 and the Record Action Code of D in character position 131. In processing the delete transaction, you simply by-pass the writing of a new master. A successful DELETE is reported on the transaction register. An unsuccessful delete appears on the error report.

CHANGE: There are four types of change transactions as shown below. A successful CHANGE is reported on the transaction register. An unsuccessful change appears on the error report. Changes should allow the fields on the master (with the exception of the identification number field which cannot be changed) to have data added to them, to have data changed in them, to have data deleted in them and to remain as they are. The deletion of a field will be handled by placing a hyphen in the last character of the field.

• Type 1: Type 1 allows you to change the name and address information. This transaction is distinguished by a 1 in character position 130 and the Record Action Code of C in character position 131. The first 79 characters of this record have the same format as the master file. Characters 80-129 are blank. The identification number field on the master cannot be changed. For all other fields, this transaction should be able to add data to an empty field, change information in a field and delete information from a field as well as leave a field with no alterations.
• Type2: Type 2 allows you to change financial information. The transaction is distinguished by a 2 in character position 130 and the Record Action Code of C in character position 131. The first 20 characters contain data and characters 21 - 129 are blank. The transaction should be able to change either of the amounts, add to a blank amount field and delete an amount field. The identification number cannot be changed. The layout is:

1 - 8	Identification Number
9 - 14	Total amount due
15 - 20	Total amount paid
21 -129	Blank
130	Change Type set to 2
131	Record Action Code set to C

• Type 3: Type 3 allows you to change the major, number of courses and ALL of the courses. When there is a change in course information, this transaction is used if all courses are changing, the Type 3 transaction is used if the changes are being made to certain courses individually. This transaction is distinguished by a 3 in character position 130 and the Record Action Code of C in character position 131. This transaction should be able to add data to an empty field, change information in a field and delete information from a field as well as leave a field with no alterations. This means in can effect the major, the number of courses and all of the courses (not individual courses). Essentially you should think of course changes from type 2 as simply overlaying the seven course list on the master with the seven course list on the transaction. The layout is:

1 - 8	Identification Number
9 - 10	Major
11	Number of Courses
12 - 16	Course 1
17 - 21	Course 2
22 - 26	Course 3
27 - 31	Course 4
32 - 36	Course 5
37 - 41	Course 6
42 - 46	Course 7
47 - 129	Blank
130	Change Type set to 3
131	Record Action Code set to C

• Type 4: Type 4 allows you to add, change or delete an individual course. If the student is adding, changing or deleting more than one course, a different type 3 change must be used for each transaction. This transaction is distinguished by a 4 in character position 130 and the Record Action Code of C in character position 131. The layout is:

1 - 8	Identification Number
9	Course Action Code 1 = Add a Course 2 = Change a Course 3 = Delete a Course
10 - 14	Old Course
15 - 19	New Course
20 -129	Blank
130	Change Type set to 4
131	Record Action Code set to C

• To add a course, the Course Action Code will be a 1 and the new course being added will be in the New Course field. You add a course into the next available slot in your course list. If the person is already taking the course, the transaction is an error so no change should be made and the transaction should be reported on the error report. If the person is already taking 7 courses, a new course cannot be added and the transaction should be reported on the error report. If a course is successfully added, the Number of Courses field must also be updated. Successful changes that involve adding a course are reported on the transaction register.
• To change a course, the Course Action Code will be a 2. The old course being changed (removed) from the record will be in the Old Course field. The new course being substituted will be in the New Course field. If you can't find a match to the Old Course in the course list on the master record, you have an error condition that should be reported on the error report. If the New Course matches a course in the course list on the master record, you have an error condition that should be reported on the error report. If everything is okay, make the change by placing the New Course where the Old Course currently appears in the course list on the master record. The successful change should be reported on the transaction register.
• To delete a course, the Course Action Code will be a 3 and the course being deleted will be in the Old Course field. If you can't find a match in the course list on the master record, you have an error condition that should be reported on the error report. If you find a match to the Old Course field in the course list on the master record, delete the course from the master record in the work area and push the other courses over in the master record course list or move the last course listed into the deleted course field so that you do not leave a blank embedded field in the master record course list. When a course is deleted the Number of Courses field must also be altered to reflect the change. The successful change involving deleting a course should be reported on the transaction register.

Transaction Register: Listing of all good transactions that were successfully processed and the action taken. At the end of this report, there should be a page of control totals. This needs to show the number of master records read, the number of new master records written, the number of transactions read, the number of successful adds, changes, and deletes, and the number of unsuccessful adds, changes, and deletes. To balance the results, the number of transactions in all categories should be equal to the number of transactions read and the number of master records read plus good adds, minus good deletes should equal the number of new master records. A message should be written telling whether the processing is in balance or out of balance.

Error/Exception Report: This is a listing of all errors. The report should identify the record and that data that was in error and include a message about the problem. Because you are producing two printed reports, you should write this report to disk and when the program is complete, open the file as input and create the report on paper.