GET 433 Course Syllabus Spring 2017

Transcription

1 Instructor: Doug Taber Telephone: Office: Hinds Hall 239 Location: Hinds 013 Day: Tues / Thurs Time: 8 AM to 9:20 AM Office Hours: TBA Course Overview GET 433 Enterprise Systems This course focuses on the structure and specification of enterprise applications and on the lower-level, aspects of application development, specifically the close coupling between implementation environments and the hardware and software infrastructure of modern mainframe systems. Prerequisites None Course Objectives At the completion of this course students will be able to: Describe enterprise technology concepts Evaluate the use of enterprise technologies in business environments Evaluate the use multi-tier architectures for large scale systems Utilize programming techniques to address business needs for technological solutions Describe key architectural concepts used in enterprise systems including transaction processing and messaging Describe key enterprise data structure concepts including various file access and management systems, including but not limited to relational databases Use large enterprise computing systems to build enterprise objects Resources Text Optional: Murach (2004), Mainframe COBOL, Mike Murach and Associates, ISBN-13: Ebbers, M., O Brien, W., Ogden, B., Introduction to the New Mainframe: zos Basics, (2 nd ed), International Business Machines Corp. 2009, SG do not buy this book you can access it online: Readings There are a variety of articles that complement the textbook located in the Blackboard Assignments for this course, URL: 1

2 Grading Policy Final grades will be based on the number of points earned throughout the semester according to the table below. Grade Points A A B B B Grade Points C C C D F 270 Class Attendance and Participation (140 points) Attendance is important and will be taken at the beginning of each class. The 140 points will be split over 14 class sessions. Class exercises will be collected and counted toward the 140 points. Assignments (160 points) Labs (160 points) There will be six (8) labs that will reinforce the concepts and principles covered in our classroom lectures, readings and discussions. Exams (150 points) Exams (100 points) There will be two (2) exams. These exams will be based on class lectures, readings, labs and other course related activities. Final Exam (50 points) There will be a final exam that will consist of a variety of questions and problems. It will be comprehensive and cover all of the topics presented during the semester. When you come to the exam bring with you all of the resources you will need to be successful since this will be an open book, open notes, open lab exam. Assignment Policy Assignments Due Dates - All reading (and video viewing) and discussion posting assignments are due on date indicated in Blackboard. All non-reading assignments (labs, models etc.) are due as indicated in Blackboard. Late assignments will be accepted; but may be assessed a reduction in points. Use the point system judiciously so that you can compensate for missed assignment due dates. Assignment Format - You are responsible for getting assignments from/to the instructor for missed classes. All assignments are to be prepared using word processing software. Space and one half, 12 font is the accepted format. 2

3 University Policies Add/drop Process and Course Withdrawal Policy It is the responsibility of the students to be fully informed of the college catalog policies regarding course add, drop and withdrawal policies. For more information about the Syracuse University Add/drop Process and Course Withdrawal Policy, please see the following web site: Academic Integrity Policy Syracuse University s academic integrity policy reflects the high value that we, as a university community, place on honesty in academic work. The policy defines our expectations for academic honesty and holds students accountable for the integrity of all work they submit. Students should understand that it is their responsibility to learn about course-specific expectations, as well as about university-wide academic integrity expectations. The university policy governs appropriate citation and use of sources, the integrity of work submitted in exams and assignments, and the veracity of signatures on attendance sheets and other verification of participation in class activities. The policy also prohibits students from submitting the same written work in more than one class without receiving written authorization in advance from both instructors. The presumptive penalty for a first instance of academic dishonesty by an undergraduate student is course failure, accompanied by a transcript notation indicating that the failure resulted from a violation of academic integrity policy. The presumptive penalty for a first instance of academic dishonesty by a graduate student is suspension or expulsion. SU students are required to read an online summary of the university s academic integrity expectations and provide an electronic signature agreeing to abide by them twice a year during pre-term check-in on MySlice. For more information and the complete policy, see Disability-Related Accommodations If you believe that you need accommodations for a disability, please contact the Office of Disability Services (ODS), located in Room 309 of 804 University Avenue, or call (315) , TDD: (315) for an appointment to discuss your needs and the process for requesting accommodations. ODS is responsible for coordinating disability-related accommodations and will issue students with documented Disabilities Accommodation Authorization Letters, as appropriate. Since accommodations may require early planning and generally are not provided retroactively, please contact ODS as soon as possible. Syracuse University values diversity and inclusion; we are committed to a climate of mutual respect and full participation. My goal is to create learning environments that are useable, equitable, inclusive and welcoming. If there are aspects of the instruction or design of this course that result in barriers to your inclusion or accurate assessment or achievement, I invite any student to meet with me to discuss additional strategies beyond accommodations that may be helpful to your success. Religious Observances Notification and Policy SU religious observances notification and policy, found at recognizes the diversity of faiths represented among the campus community and protects the rights of students, faculty, and staff to observe religious holidays according to their tradition. Under the policy, students are provided an opportunity to make up any examination, study, or work requirements that may be missed due to a religious observance provided they notify their instructors before the end of the second week of classes for regular session classes and by the submission deadline for flexibly formatted classes. 3

4 Attendance Policy Regular class attendance is obligatory. An instructor may recommend that a student be dropped from a course for poor achievement due to excessive absence. A student who is dropped after the deadline for dropping courses may be assigned a grade of F. Students who have two unexcused absences during the semester may be dropped from the course at the discretion of the instructor. The instructor or the department offering the course will notify the Registrar of this action. However, students should not assume that they have been dropped from a class just because the first two classes were missed. It is ultimately the responsibility of the student to drop a course that they are not planning to attend by the deadline published in the university calendar. Blackboard Policy The uses a Web-based teaching and learning environment called Blackboard. Most IST campus courses use Blackboard as a supplement to classroom activities and all distance learning courses are conducted in Blackboard. Access to Blackboard is available at the following URL: Your professor will let you know the date the course will be available. Syllabus Change Policy This syllabus can be changed with sufficient notice from your instructor. 4

5 Course Outline -by- Date 1 1/17 Topic, Objectives, Assignments & Deliverables Introduction to the New Mainframe - Introduction to Enterprise Environments Log on to the IBM Mainframe and set up files to be used Describe the characteristics of the Enterprise Technology environment and the need to COBOL. Describe the components of a computer system Explain the various multi-tier system architectures Compile, Link and Execute a COBOL Program Create JCL needed for the execution of a COBOL program Describe the coding rules and styles for COBOL List debugging techniques for COBOL programs Define fields in WORKING-STORAGE, variables and literals. Make use of the VALUE clause 5

6 2 1/24 Anatomy of a COBOL Program Discuss the use of data division and working-storage section of the COBOL program Make use of structured programming design Explain the use of working storage levels Use the appropriate PIC Clauses needed for fields Describe the use of alphanumeric and numeric data Describe the initialization of data fields. Describe the use of the MOVE, COMPUTE, IF and PERFORM statements List the techniques used to structure the logic for a COBOL program Describe the techniques for changing and maintaining production programs Describe the flow of a program Describe the procedures and needed COBOL features for printing a report Logic usage with 88 levels Use fields, sub-fields and arrays, subscripts and indexes Use COBOL table searches, sequential and binary Make use of string and unstring commands, TALLYING and REPLACE 3 1/31 COBOL File Handling Sequential and VSAM Make use of standard structuring features for programs Explain the needed COBOL program features for sequential and VSAM file handling. Write the needed JCL to use input and output sequential and VSAM files. Execute and debug programs using sequential and VSAM files. Describe the features needed for input and output files List the needed COBOL features for handling VSAM files, input and update. Write the needed JCL to use input and output sequential and VSAM files. Use VSAM files in sequential, random and dynamic mode Use COBOL to read, write and rewrite VSAM files 6

7 4 2/7 COBOL File Handling Sequential and VSAM (cont.) Make use of IDCAMS to allocate, load and print sequential and VSAM Files Create COBOL programs to utilize VSAM files for input and update Test by desk checking of programs Test and debug COBOL programs using sequential and VSAM files Make use of the appropriate condition codes when using files for input and output using COBOL with VSAM Design, code and test appropriate error handling routines for COBOL / VSAM 5 2/14 COBOL File Handling Relational Databases (DB2) Create COBOL programs to utilize DB2 databases. Test and debug COBOL utilize DB2 databases Make use of the appropriate bind operations and condition codes when using DB2 databases Create and execute the JCL needed to use programs and DB2 databases using COBOL with embedded DB2 commands 7

8 6 2/21 COBOL File Handling Relational Databases (DB2) (cont.) Make us of DB2 information to create extracts and reports Test and debug COBOL utilizing DB2 databases Make use of the appropriate condition codes when using DB2 databases Create and execute the JCL needed to use programs and DB2 databases with extract and report output Design, code and test appropriate error handling routines for DB2 7 2/28 COBOL and CICS Maps and Mapsets Design and Create Maps in a PDS using ISPF and BMS with Assembler macros from user specifications List the differences between conversational and pseudo-conversational design styles Develop CICS program designs for basic CICS programs Assemble the created maps and load to a zos program library Test the created maps as a prototype Use COBOL WORKING-STORAGE needed to load and unload data from CICS Maps Make use of the execute interface block for CICS programs 8 3/7 COBOL and CICS Menu Programs Design and Create CICS Programs to support a menu. Design, compile and test the needed Maps for a CICS Menu. using COBOL with embedded CICS commands Design, code and test appropriate error handling routines for CICS menu programs 8

9 9 3/21 COBOL and CICS Inquiry Programs Design and Create CICS Programs to inquire against VSAM files, including a BMS map for this program. Design, compile and test the needed Maps for a CICS Inquiry program. using inquiry COBOL / CICS programs 10 3/28 COBOL and CICS Inquiry Programs (cont.) Design and Create CICS Programs to inquire and browse VSAM files. Create, compile and test the programs and maps needed for an inquiry program. using inquiry COBOL / CICS programs Design, code and test appropriate error handling routines for CICS inquiry 11 4/4 COBOL and CICS Browse Programs (cont.) Describe the logic needed to execute a browse program forward and backward browse. Design and create maps that can be used for a browse program. 9

10 12 4/11 COBOL and CICS Browse Programs (cont.) Write, compile, execute, test and debug a browse program, along with the needed maps. using inquiry COBOL / CICS programs Design, code and test appropriate error handling routines for CICS browse programs 13 4/18 COBOL and CICS An Add and Update Program (cont) Design and Create CICS Programs to add or update a VSAM file, including a BMS map. Assemble the created maps and test Compile the created COBOL programs and test Create the appropriate user documentation needed to use CICS add / update programs Design, code and test appropriate error handling routines for add / update programs 10

11 14 4/25 COBOL and CICS An Add and Update Program (cont) Utilize pseudocode to develop the logic needed for an add or update CICS program using inquiry COBOL / CICS programs 15 Final Exam 5/2 11