David shelby kirk <br/><br/>
Cobol/370 for power programmers / 

 - 1era edicion  
 - United Estates  John Wiley and sons  1994 
 - 384  Ilustraciones, tablas, graficos   25cm  
 - series  .
<br/><br/>EDITORIAL <br/>John Wiley and sons<br/>ISBN <br/>0-471-62367-9 
<br/><br/>Contents<br/><br/>List of Figures<br/><br/>Preface<br/><br/>Acknowledgments<br/><br/>1 Introduction to COBOL II and COBOL/370<br/><br/>1.1. What are COBOL II and COBOL/370?<br/><br/>1.1.1. Overview of COBOL history<br/><br/>1.1.2. Overview of COBOL II<br/><br/>1.1.3. Overview of COBOL/370 LE/370 and AD/CYCLE products<br/><br/>1.2. Major features of COBOL II and COBOL/370<br/><br/>1.2.1.<br/><br/>Newer IBM features supported<br/><br/>31-bit addressability<br/><br/>Reentrant code<br/><br/>Faster sorting<br/><br/>VSAM enhancements<br/><br/>Higher compiler limits<br/><br/>CALLable services<br/><br/>Intrinsic functions<br/><br/>1.2.2. ANSI 85 support<br/><br/>1.2.3. Standards control opportunities<br/><br/>1.2.4. SAA opportunity<br/><br/>1.2.5. Improved tuning and cost control Optimization<br/>Batched compiles<br/><br/>Environment management<br/><br/>1.3. Benefits to an application<br/><br/>1.4. Benefits to a programmer<br/><br/>Structured programming<br/><br/>Documentation<br/><br/>Debugging<br/><br/>CICS enhancements<br/><br/>1.5. Developing an approach to learning COBOL II or COBOL/370<br/><br/>Summary<br/><br/>2 Coding Differences between COBOL II, COBOL/370, and OS/VS COBOL<br/><br/>How to read the syntax charts<br/><br/>2.1. OS/VS COBOL features that were dropped<br/><br/>2.1.1. Report Writer<br/><br/>2.1.2. ISAM and BDAM<br/><br/>2.1.3. Communications feature<br/><br/>2.1.4. Segmentation feature<br/><br/>2.1.5. Macro-level CICS<br/><br/>2.1.6. EXAMINE and TRANSFORM<br/><br/>2.1.7. READY/RESET TRACE, EXHIBIT, and USE FOR DEBUGGING<br/><br/>CURRENT-DATE and TIME-OF-DAY 2.1.8.<br/><br/>2.1.9. NOTE and REMARKS<br/><br/>2.1.10. ON statement<br/><br/>2.1.11. WRITE AFTER POSITIONING statement<br/><br/>2.1.12. STATE and FLOW compile options<br/><br/>2.1.13. OPEN and CLOSE obsolete options<br/><br/>2.2. Modified COBOL components<br/><br/>2.2.1. IDENTIFICATION DIVISION PROGRAM-ID modifications<br/><br/>Recommendation for using IDENTIFICATION DIVISION<br/><br/>features<br/><br/>2.2.2. ENVIRONMENT DIVISION<br/><br/>Use of expanded FILE STATUS codes for VSAM Recommendation for using ENVIRONMENT DIVISION<br/><br/>features<br/><br/>2.2.3. DATA DIVISION<br/><br/>The FILLER entry<br/><br/>Modifications to the USAGE clause<br/><br/>Modifications to the VALUE clause<br/><br/> 
<br/><br/> So, Why a Second Edition?<br/><br/>When I wrote the first edition of this book, little did I know that a superset of COBOL II was in the works at IBM. I should have known better. IBM has been consistent in their efforts to periodically upgrade the programming environ-ment, and a superset of COBOL II should have been predictable. Fortunately for those of us who write the code, IBM's newest version of COBOL, SAA AD/Cycle COBOL/370 (referenced as COBOL/370 in this book), builds on the foundation of COBOL II. While COBOL II is certainly a major enhancement to the COBOL language and changed the perception that COBOL is a dead language, COBOL/370 ties many loose ends together from an environmental perspective. We'll see more on that later. As you read this book, you will find that COBOL/370 is actually several products, not just the compiler. I'll cover that shortly.<br/><br/>When I wrote the first edition, I felt strongly that COBOL programmers finally had a compiler worthy of professionals. In the two years since that book, I have had this consistently proved to me. Now, COBOL/370 carries forward what was begun with COBOL II, the flexibility to carry an application beyond the mainframe to other platforms. Programmers developing applications at pro-grammable workstations (PWS) now have a compiler that is accessible either from the mainframe or from the PWS.<br/><br/>If you're wondering why I didn't write a separate book for COBOL/370, the answer is that the two languages have more similarities than differences. IBM Announced COBOL/370 as a superset of COBOL II and I can't improve on those worda. In case you read the first edition, you will find that all of the programming features introduced for COBOL II are also in COBOL/370. Additionally, if your 
<br/><br/>
<br/><br/><label>ISBN: </label>0-471-62367-9 
<br/><br/><label>Subjects--Topical Terms: </label><br/>Ingeniería en tecnologias de la información y comunicaciones