SYLLABUS HANDOUT
for
CPT 250 8A
Introduction to CICS
Instructor
Quarter
Days Time  Place
METHODS OF CONTACTING INSTRUCTOR:
Date class begins:
IMPORTANT DATES:
Date class ends:
Last date to drop class:
WELCOME TO METROPOLITAN COMMUNITY COLLEGE!
STUDENT SERVICES
IMPORTANT DATES
REFUND POLICY
Eligibility for a refund is automatically calculated by the date of the withdrawal. Amount of refund is based on
number of sessions that met as of the withdrawal date to the total number of scheduled sessions for the course.
For additional information call: (402) 457-2405 or 1-800-228-9553
IMPORTANT DATES:
Date class begins:
Date class ends:
Last date to drop class:
SECTION I: THE CLASS AND THE INSTRUCTOR
COURSE SECTION AND TITLE:
CPT 250 **CIntroduction to CICS
INSTRUCTOR=S NAME:
LOCATION OF CLASS:
1
LOCATION OF LABS:
METHODS OF CONTACTING INSTRUCTOR: e-mail:
web site (under construction):
*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.
SECTION II: THE COURSE
COURSE DESCRIPTION:
This course provides an introduction to developing programs using IBM=s Customer Information Control System
(CICS) for the Micro Focus CICS Option environment, with references to the mainframe environment. The student
will learn how CICS interfaces with the operating system, how to use the CICS development and operational
environments, how to create on-line display screen maps, and how to create COBOL programs that use the CICS
command-level interface.
COURSE PREREQUISITES: CPT 222CCOBOL II or instructor permission
COURSE OBJECTIVES:
Upon completion of this course, the student will be able to do the following:
1.
2.
3.
4.
5.
Describe interactive programming, CICS and its major components, and the typical mainframe
and Micro Focus environments.
Define important terms and concepts in CICS programming.
Demonstrate the design of CICS programs, using standard techniques.
Demonstrate screen setup using Basic Mapping Support.
Successfully implement CICS applications for file inquiry, file update, file browsing, and menu.
REQUIRED/SUPPLEMENTAL MATERIALS:
Textbook:
CICS/ESA Primer
Edition:
First
Author:
James G. Janossy & Steve Samuels
Publisher:
John Wiley and Sons.
SECTION III, PART A: 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.
1Students will find computer resources for this class at Computer and Office Technology (COT) Computer Labs on
the South Omaha Campus only.
Metropolitan Community College
Page 3
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.
This course requires students to work an average of 4.5 hours per week in hands-on, lab activity. Students are
responsible for completing all lab work outside of the classroom. The software required for this course is not
readily available to students. Metro provides the necessary software in this classroom and in the South Omaha
Campus computer lab.
This course will be somewhat experimental in the sense that questions may arise that can be answered only by
testing on the system and determining what works. There may also be some adjustments in assignments and
tests should circumstances so dictate. Part of the learning process will be the students= participation in the
experimental method.
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 will also be taken into consideration.
SELECTED TESTING/ASSESSMENT METHODS:
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, data element usage, and input/output requirements; adequacy of
program testing procedures; and adequacy of program documentation. Of course, the program should also run
correctly.
Typical point assignments for these various aspects of programming for a 60 point program is as follows:
2 program overview
2 screen layout(s) (i.e., Amap(s)@)
2 file and record layout(s) (as needed)
2 processing summary
2 hierarchy diagram/structure chart
4 flowchart or pseudocode
5 coding style, etc.
5 methodology
10 correct compile
15 correct run
--------60 total
Usage of comments in program and Amaps@:
2 general description in Identification Division
2 misc. input/output requirements
2 data element usage, especially Working-Storage
5 program logic (Procedure Division)
Full points are awarded for the inclusion of the specified item(s), with points being deducted for
notable problems.
Exams consist mostly of fill-in-the-blank questions and short programming segments.
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 may then receive a grade of 0.
Assignments may not be accepted after the test has been given. Also, see AAttendance@ below.
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:
Metropolitan Community College
Page 4
Letter Grade
Percentage Range
Point Range
A
90%
100%
540
600
B
80%
89.9%
480
539
C
70%
79.9%
420
479
D
60%
69.9%
360
419
F
0%
59.9%
0
359
MAINTENANCE OF STUDENT RECORDS:
All work is graded and returned as soon as possible, almost always by the following class. 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.
SECTION III, PART B: 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.
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 which 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 become 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, 4575231. Failure to officially withdraw will result in either an instructor withdrawal (IW) or failing (F) grade. The last
date to withdraw is .
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.
COLLEGE POLICIES:
All students are expected to abide by College policies. These policies exist so that all students may pursue their
educational goals in a fair and non-threatening environment. Academic and non-academic standards exist for all
students. Academic standards involve acts of cheating or plagiarizing. Non-academic standards include, but are
Metropolitan Community College
Page 5
not limited to, any acts of harassment, disruption of College functions, possession, use or sale of controlled
substances or firearms, and inappropriate use of College equipment or property. The College imposes specific
disciplinary actions in response to incidents of both academic and non-academic misconduct. These actions may
include: admonition, failing grade, failure of course, disciplinary probation, suspension or dismissal. (A copy of the
current disciplinary procedure is available in each campus Student Services center and from your Associate
Dean.)
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.
INFORMATION SOURCES:
Refer to both the College catalog and student handbook as sources of general College information such as
parking, children on campus, identification cards, etc.
PROGRAM IDENTIFICATION: Associate Dean of Computers & Visual Arts:
Tom Pensabene
Location: FOC 8 207
Phone: 457-2502 (Candi Otterpohl)
Email: tpensabene@metropo.mccneb.edu
The Associate Dean of Curriculum Delivery is the person you should contact if you have any questions or
problems concerning the instructor that cannot be resolved by the instructor to the student's satisfaction.
SECTION IV: PROJECTED SCHEDULE OF ASSIGNMENTS:
Wk
1
Date
Topics
Chapters
Interactive Programming
Introduction to CICS
Mainframe Environment & 3270 Terminals
Guidelines for CICS Programming
The AMicro Focus CICS Option@
Environment
--Introduction
JS 1
JS 2
JS 3
Handout I
Handout II (UG 1-1
thru 1-5, 2-1 thru 217, 3-6 thru 3-10, 6-
Metropolitan Community College
Assignments
Page 6
Points
Wk
Date
Topics
Chapters
1 thru 6-4, 11-1 thru
11-8, 20-1 thru 20-6
UG 3-2 thru 3-5)
Assignments
Points
--Running the AIVP@
2
The AMicro Focus CICS Option@
Environment
--Setting up a region on floppy
Handout III (steps +
UG 5-1 thru 5-2, 118 thru 12-6)
--Creating CICS table entries
Handout IV (UG 206 thru 20-7, 6-9 thru
6-15, 7-1 thru 7-12)
(AUGR: 8-1 thru 820, 8-26 thru 8-32,
8-35 thru 8-44)
Coding Screens Using BMS
3
Choose col. A or
col. B
JS 4
Handout V (steps +
UG 20-8 thru 20-11)
(AUGR: 23-1 thru
23-51)
col. A
4.17
Physical and Symbolic Maps
JS 5
HOE
(5.13)
A.-D.
Introduction to CICS Programming
JS 6
Handouts VI (steps
+ UG 20-12 thru 2017, 9-1 thru 9-11,
27-1 thru 27-15),
VI.A., VI.B. (AUGR:
20-17 thru 26, 21-9
thru 21-10, 5-3 thru
5-7, 5-12 thru 5-13)
col. B
60
(AMFCS@)
HOE
(6.13)
A.-D.
(ACAC@)
Introducing Pseudoconversational Logic
JS 7
HOE
(7.10)
D.
HOE
(7.10)
A.-C.
Structured Pseudoconversational Logic
JS 8
HOE
(8.11)
C.-D.
HOE
(8.11)
A.-B.
Using Machine-Generated Symbolic Maps
JS 12
HOE (12.10) A.-B.
XC
Review
4
Test
5
Additional Thoughts on User Interface
Handout VII (L: 14,
64, 83-88, 179-180,
182-183)
Programming Your Function Keys
JS 9
HOE (9.12) A. or
B.
Using COPY and CALL in CICS Programs
JS 10
HOE (10.21) A.-C.
Programming On-Line Help
JS 11
HOE (11.10) A.-C.;
D. extra credit
Indexed File Inquiry
JS 13
HOE (13.13) any
one of A.-E.
6
Metropolitan Community College
100
Page 7
XC
60
Wk
7
Date
Topics
Indexed File Update
Review
Chapters
JS 14
Assignments
HOE (14.17) any
one of A.-E., plus
F. & G.
Points
60
8
Test
100
9
Indexed File Browsing
JS 15
Handout VIII (SS:
661-675)
HOE (15.20) any
one of A.-E.
60
10
XCTL & LINK Commands
Menus
JS 16
HOE (16.20) A.-C.
60
11
Test
100
600
JS: Janossy & Samuels, CICS/ESA Primer
L: Doug Lowe, CICS for the COBOL Programmer, Part 1
SS: Stern & Stern, Structured COBOL, 7th ed.
UG: Micro Focus CICS Option Transaction System User Guide
AUGR: Additional User Guide Readings & Resources (see .pdf file on lab server “F:” drive)
HOE: Hands-On Exercise(s) in JS
MFCS: My First CICS Screen
CAC: CICS Average Calculator
XC: Extra Credit
Metropolitan Community College
Page 8