It works if you have no programming experience. Those programs need to be maintained. And this is the only book that shows you the techniques that were used to develop those programs. In summary, then, this is the right book for anyone who needs to use structured COBOL on a mainframe. You can read these chapters in sequence or in any order you prefer.
|Published (Last):||10 May 2014|
|PDF File Size:||18.85 Mb|
|ePub File Size:||8.16 Mb|
|Price:||Free* [*Free Regsitration Required]|
Book description Section 1: The essence of COBOL programming In chapters 1, 2, and 3, your students learn how to code and test simple programs that prepare reports. In chapters 4 and 5, they learn how to design, code, and test more complicated programs using the best structured programming techniques.
In chapter 6, they learn the mainframe skills that they will need for working with data. Section 2: Other COBOL essentials In this section, your students will learn how to work with intrinsic functions, dates, characters, tables, copy members, and subprograms.
You can assign these chapters in sequence or in any order you prefer. Because file processing not database processing is a major feature of many mainframe programs, these are essential skills for COBOL programmers. You also need to learn how to work productively in the IBM mainframe environment.
But here are four that are specific to this book: In chapters 4 and 5, your students learn the structured programming methods that are used in the best mainframe shops. They became an ad hoc standard in many mainframe shops by the mids. That means that it is best used in curricula that provide free access to an IBM mainframe. Then, your students can compile and test their exercises and projects on that mainframe.
Then, you can enhance the course by teaching mainframe programming skills as information-only no hands-on. A third alternative is to teach the entire course as information-only. This gets the students programming right away without all the added complexity of working with files.
Then, chapter 2 shows the students how to compile and test their programs. With this approach, the students are ready for report-preparation programs when they are introduced to them in chapter 3. So that chapter shows them how to develop a simple listing program with headings and a total line.
After just five chapters, these students can clearly see the differences between structured programming and object-oriented programming. And if you jump to section 3 after section 1, your students will start to understand why COBOL will still be around 15 years from now.
In contrast, a leading college textbook takes four chapters to show how to develop a report program that lists the records in a file…with no headings and no total lines! These components provide everything that other publishers provide in a way that delivers better results.
Beyond that, those programs are going to be maintained and enhanced for many years to come because no other platform has the power to support that level of transaction processing. In addition, most of the COBOL programs that were once running on other platforms have been replaced by new systems written in newer languages.
As a result, our book can be used to teach COBOL with any compiler that supports those standards and they all do. Are your structured methods used in industry? Paul had developed these methods as a training manager for Pacific Telephone. Then, after we published his book, he started a consulting career during which he taught his methods in COBOL shops throughout the country.
In particular, our book presents the structure chart as the graphic documentation for program design, and it presents top-down coding and testing as the preferred way to develop programs.
It also presents pseudocode as an occasional tool for planning the logic of critical paragraphs. Please note, however, that our focus is on the design principles, not the graphic methods. This focus is what distinguishes our structured methods from others. For instance, one best-selling college textbook presents report-preparation programs that are driven by the Not At End clauses of Read statements. This is contrary to any reasonable principles of structured design, and it leads to serious problems as the complexity of a program increases.
First, programmers can understand the logic of pseudocode or COBOL code more easily than the logic of flowcharts. Second, the more complicated the logic, the more this is true.
There are no book corrections that we know of at this time. Thank you! Murach college books and courseware since Contact Murach Books.
Search Results for "murach-s-mainframe-cobol"
Web development books
Murach’s Mainframe COBOL