CPT 212 8A: Assembler Language II
W · 6:00pm-9:35pm
SYLLABUS
METROPOLITAN COMMUNITY COLLEGE
SECTION I: THE CLASS AND THE INSTRUCTOR
COURSE SECTION AND TITLE:
CPT 212 8A: Assembler Language II
ACADEMIC YEAR/QUARTER:
Spring, 2002-2003
INSTRUCTOR’S NAME:
Alan R. Reinarz
LOCATION OF CLASS:
SOC 145
LOCATION OF LABS:
SOC 127
METHODS OF CONTACTING INTRUCTOR:
areinarz@metropo.mccneb.edu
http://cot.mccneb.edu/areinarz
METRO OFFICES
HOURS*
LOCATION
PHONE
FAX
M/W/Th: 4:00p-5:00p
T/Th: 1:00p-2:00p
SOC 300
738-4089
738-4553
T: 3:30p-4:30p
EVC 156
289-1364
289-1405
*Stated office hours may need to be changed due to special circumstances or events. If the student wishes to meet with the instructor at a time other
than scheduled office hours, the student should make an appointment with the instructor.
Home phone:
(402) 556-3071
IMPORTANT DATES:
DATE CLASS BEGINS:
DATE CLASS ENDS:
LAST DATE TO DROP CLASS:
DATES CLASS DOES NOT MEET:
3/12/2003
5/21/2003
4/30/2003
SECTION II: THE COURSE
COURSE DESCRIPTION:
This course presents advanced programming and logic using IBM Mainframe Assembler Language. Topics covered include
binary arithmetic, table processing, subprograms, and macros.
COURSE PREREQUISITES: CPT 211 – Assembler I
COURSE OBJECTIVES: Upon completion of this course, the student will be able to:
1. Demonstrate the use of binary arithmetic.
2. Code instructions that perform logical operations and manipulate bit data.
3. Perform data validation routines.
4. Define, load, search and sort tables.
5. Code a program and subprogram that pass parameters.
6. Debug an assembler program using a storage dump.
7. Define and invoke macros in assembler programs.
REQUIRED/SUPPLEMENTAL MATERIALS:
Textbook:
MVS Assembler Language
Edition: 1987
Author: Kevin McQuillen & Anne Prince
Publisher:
Murach
Textbook:
Assembler Language Programming for IBM & IBM-Compatible Computers
Edition: 2nd (1986); Authors: Stern, Sager, Stern; Publisher: John Wiley and Sons.
Two 3.5 " diskettes.
Students may wish to purchase the current Reference Summary from IBM. This reference is not currently available from the
Metro bookstores. It may be obtained from IBM on-line at
http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi and search on “z/Architecture” or publication no. SA22-7871-00. An early version of the Reference Summary is available as a class handout. A Reference Summary
may be used during closed-book exams.
Another useful IBM manual is Principles of Operation, which contains the most complete description of the IBM mainframe
hardware and every individual machine language instruction. Latest versions may be found at the above URL, again searching
under “z/Architecture” or publication no. SA22-7832-00. Some editions are available for a free download.
SECTION III: STUDENT RESPONSIBILITIES
METHODS OF LEARNING:
The student will have specific assignments to read and master. These assignments are indicated in the course schedule and/or outlined
by the instructor. The student should have read the material prior to class meeting date.
This course requires students to work an average of 1.5 hours per week in hands-on, lab activity. Students are responsible for completing all lab work outside of the classroom. While you may choose to do this lab work someplace other than the College, Metro provides
computer labs for students who do not have the required resources or facilities available to them. The software for this course will be
available at the South Omaha Campus only. A downloadable MS-DOS version of the software used in this class has been located on
the Web, but its functionality has not been fully determined (http://www.simtel.net/pub/pd/45216.html). We also anticipate exploring
an on-line IBM z-series mainframe server provided through IBM’s University Program. This service will be available to any PC having web access and a standard web browser.
ATTENDANCE STATEMENT:
The course will be covered partially by assigned portions of the text and may be presented in a sequence different from the text. Material will also be covered that is not in the text. Attendance is necessary to understand the course material. Each student is expected to
recognize the importance of class attendance and promptness. CHRONIC TARDINESS AND ABSENCES MAY RESULT IN A
REDUCTION IN THE FINAL GRADE BY 10%.
Excessive absences or unsatisfactory progress will subject the student to administrative withdrawal from the course. If a student
should miss a class for any reason, he/she is expected to cover the material he/she missed on his/her own. All work must be made up
to the satisfaction of the instructor.
RETAINING COPIES OF SUBMITTED WORK:
On very rare occasion, the instructor has been unable to find any record of work that a student claims to have submitted. There may be
several reasons this has occurred, including loss or theft of the work before it gets to the instructor, or oversight on the part of the student or instructor. The student should understand that grades are based upon achievement of learning objectives and successful completion of assignments. If work is missing, for whatever reason, it becomes impossible for the instructor to evaluate it and assign a
grade. It is highly recommended that students keep backup copies of all work submitted toward the unlikely event that it might need to
be resubmitted.
STUDENT WITHDRAWAL:
If you cannot attend and complete this course, you should officially withdraw by calling Central Registration, 457-5231. Failure to
officially withdraw will result in either an instructor withdraw (IW) or failing (F) grade. The last date to withdraw is identified on the
first page of this syllabus handout.
Metropolitan Community College
2 of 5
Revised: 7/11/16
ACADEMIC HONESTY STATEMENT:
The College imposes specific actions in response to incidents of student dishonesty (cheating, plagiarism, etc.) that may include receiving a failing grade on a test, failure in the course, suspension from the College, or dismissal from the College. The disciplinary procedures are available in the Counseling/Advising Centers.
Please note: ANY sharing or transfer of assigned work or test contents or answers between a student and any other person or
party; in part or in whole; whether by disk exchange, E-mail, manual transcription, codevelopment of an assignment, or any
other means; unless authorized by the instructor in advance in accordance with the guidelines in the following paragraph; will
be considered academic misconduct and be sanctioned with disciplinary action in accordance with the above paragraph. Both
originating and receiving parties will be liable to such sanction.
Sharing of class notes and handouts is authorized. Obtaining assistance from others (including tutors or lab techs) for specific programming issues or debugging is authorized. However, no further collaboration is authorized for any standard assignment. Students
wishing to collaborate further must contact the instructor for special assignments. Such special assignments must clearly identify in
advance which portions are the responsibility of each individual student wishing to collaborate. The learning objectives, level of difficulty, and typical work involved for each portion must be comparable to that for a single student working alone on the corresponding
standard assignment. Each portion will be graded individually. Each portion must clearly represent the competency of the individual
responsible for it, and only that individual. The instructor reserves the right to refuse any request for special assignments.
Indications of unauthorized collaboration and/or intent to defraud include, but are not restricted to, assignments, submitted by students
(not necessarily from the same section) individually under each of their respective names; but which are essentially identical; are essentially identical except for mechanical changes such as differing variable or module names; are essentially identical except for differing
comments; or exhibit essentially identical idiosyncratic features such as errors in syntax, style, logic, output formatting, or spelling.
The same criteria apply to submissions, by one or more students, where those submissions bear indications of copying from any other
unauthorized source. Authorized sources are the student textbook for the class, lecture notes, class handouts, and compiler/interpreter
documentation and help materials.
In summary, if you want a grade attached to your name and only your name (the only way I know MCC records grades), the work you
submit must be your work and only your work.
TECHNOLOGY RESOURCES:
As you pursue your educational objectives, you may be required to use computer information technology resources at Metropolitan
Community College. Use of these resources is a privilege and carries with it a responsibility to respect the rights and privacy of others,
the integrity of facilities, and to follow Student Conduct Guidelines and College Policies.
EDUCATIONAL SERVICES PROGRAM AREA IDENTIFICATION:
Program Area
Computer Technology and Visual Arts
Academic Dean Thos C. Pensabene
Academic Dean’s office phone
457-2660
The Office of the Academic Dean should be contacted with any questions or problems that your instructor is not able to resolve to your
satisfaction.
SECTION IV: INSTRUCTOR RESPONSIBILITIES
METHODS OF INSTRUCTION:
In each lecture during this course, the instructor will cover material the student needs to learn and accomplish. In addition, written
handouts will be provided from time to time. These will be used to supplement the text material and expand the course.
Instruction will consist mainly of lecture material presented by the instructor. In some classes, group discussion and demonstration will
be utilized. In all meetings, discussion opportunities will be provided and the student is encouraged to ask questions and clarify information as the instructor is lecturing and/or presenting material.
METHODS OF ASSESSING STUDENT PROGRESS:
Student progress is assessed through the completion of assigned projects and tests. A summary of programming assignments and tests
may be found at the end of the syllabus under the heading PROJECTED SCHEDULE OF ASSIGNMENTS. Attendance and class participation may also be taken into consideration.
Metropolitan Community College
3 of 5
Revised: 7/11/16
The majority of programming assignments require the student to take a basic set of program requirements and, based on knowledge
gained from reading and class, develop a program using the typical program development process. Work will be evaluated on the adequacy of program planning; correctness of coding generated; usage of comments to describe and clarify program logic, identifier/symbol usage, and input/output requirements; adequacy of program testing procedures; and adequacy of program documentation. Of
course, the program should also run correctly. Full points are awarded for the inclusion of the specified item(s), with points being deducted for notable problems. Typical point assignments for these various aspects of programming for a 60 point program is as follows:
Planning & external documentation:
3 input layout(s)
3 printer/output layout(s)
2 hierarchy diagram
6 flowchart or pseudocode
Usage of comments in program:
2 general description
2 misc. input/output requirements
2 identifier/symbol usage
5 program logic
5 coding style, etc.
5 methodology
10 correct assembly
15 correct run
--------60 total
Exams consist mostly of fill-in-the-blank questions and short programming segments.
CRITERIA FOR DETERMINING FINAL COURSE GRADE:
A percentage grade will be obtained by dividing the total points a student earns by the total possible points for the course. The points
for each assignment and test may be found in the PROJECTED SCHEDULE OF ASSIGNMENTS found at the end of the syllabus.
The percentage grade will then determine the letter grade for the course, according to the following table:
Letter Grade
Percentage Range
Point Range
A
90%
100%
477
530
B
80%
89.9%
424
476
C
70%
79.9%
371
423
D
60%
69.9%
318
370
F
0%
59.9%
0
317
MAKE-UP TEST PROCEDURES:
Students MUST be present on the day of an announced test. If the instructor is informed BEFORE THE TEST concerning a valid
absence, other arrangements MAY be made. There will be no retakes of tests. Test dates are not firm and are therefore subject to
change.
LATE ASSIGNMENTS:
Assignments turned in late may lose 10% per class day for up to a week and will then receive a grade of 0. Instructor reserves the right
not to accept assignments after the test has been given. Also, see “Attendance” above.
MAINTENANCE OF STUDENT RECORDS:
Test will be returned after grading for review in class and then recollected and retained for record keeping purposes. All other work is
graded and returned as soon as possible, usually by the following week. All grades are kept by the instructor in a grade book and on
computer, which students may see at any time by asking the instructor.
Metropolitan Community College
4 of 5
Revised: 7/11/16
SECTION V: PROJECTED SCHEDULE OF ASSIGNMENTS:
Week Date
Topic
1
3/12/03 Data Storage
Binary Arithmetic
2
3/19
Binary Arithmetic continued
ORG and DSECT
3
3/26
Logical Operations
Data Validation
Program 1 due
4
4/2
Test
Sorting Tables
5
4/9
Table Processing
Program 2 due
6
4/16
Searching
Binary Search
7
4/23
Test
8
4/30
Subprograms
Program 3 due
9
5/7
Dumps and Debugging
10
5/14
Macros
11
5/21
Test
Program 4 due
Metropolitan Community College
5 of 5
McQ & P
Chapter
4, p. 70-75
7
7
10
Stern
Chapter
2
11,12
20
Assignment
Program 1 – Binary arithmetic
Program 2 – Data validation, CSECT, DSECT, Get
Locate
Points
60
60
90
9
16
Program 3 – Onedimensional tables
60
9
8
18
11
Appendix. D Program 4 – Twodimensional tables, Sort
100
60
19
100
Revised: 7/11/16