000 04534 a2200265 4500
008 250318s########|||||||||||||||||||||||#d
020 _a0-471-62367-9
040 _aGAMADERO2
_bspa
_cGAMADERO2
100 _aDavid shelby kirk
245 _aCobol/370 for power programmers /
250 _a1era edicion
260 _bJohn Wiley and sons
_aUnited Estates
_c1994
300 _a384
_bIlustraciones, tablas, graficos
_c25cm
490 0 _aseries
504 _aEDITORIAL John Wiley and sons ISBN 0-471-62367-9
505 _aContents List of Figures Preface Acknowledgments 1 Introduction to COBOL II and COBOL/370 1.1. What are COBOL II and COBOL/370? 1.1.1. Overview of COBOL history 1.1.2. Overview of COBOL II 1.1.3. Overview of COBOL/370 LE/370 and AD/CYCLE products 1.2. Major features of COBOL II and COBOL/370 1.2.1. Newer IBM features supported 31-bit addressability Reentrant code Faster sorting VSAM enhancements Higher compiler limits CALLable services Intrinsic functions 1.2.2. ANSI 85 support 1.2.3. Standards control opportunities 1.2.4. SAA opportunity 1.2.5. Improved tuning and cost control Optimization Batched compiles Environment management 1.3. Benefits to an application 1.4. Benefits to a programmer Structured programming Documentation Debugging CICS enhancements 1.5. Developing an approach to learning COBOL II or COBOL/370 Summary 2 Coding Differences between COBOL II, COBOL/370, and OS/VS COBOL How to read the syntax charts 2.1. OS/VS COBOL features that were dropped 2.1.1. Report Writer 2.1.2. ISAM and BDAM 2.1.3. Communications feature 2.1.4. Segmentation feature 2.1.5. Macro-level CICS 2.1.6. EXAMINE and TRANSFORM 2.1.7. READY/RESET TRACE, EXHIBIT, and USE FOR DEBUGGING CURRENT-DATE and TIME-OF-DAY 2.1.8. 2.1.9. NOTE and REMARKS 2.1.10. ON statement 2.1.11. WRITE AFTER POSITIONING statement 2.1.12. STATE and FLOW compile options 2.1.13. OPEN and CLOSE obsolete options 2.2. Modified COBOL components 2.2.1. IDENTIFICATION DIVISION PROGRAM-ID modifications Recommendation for using IDENTIFICATION DIVISION features 2.2.2. ENVIRONMENT DIVISION Use of expanded FILE STATUS codes for VSAM Recommendation for using ENVIRONMENT DIVISION features 2.2.3. DATA DIVISION The FILLER entry Modifications to the USAGE clause Modifications to the VALUE clause
520 _aSo, Why a Second Edition? 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. 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. 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
526 _aIngeniería en Tecnologías de la Información y Comunicación
650 0 _aIngeniería en tecnologias de la información y comunicaciones
_9585
942 _cLIB
_2ddc
_e1ERA EDICION
945 _a1
_badmin
_c1261
_dJenny Viridiana Quiroz Linares
999 _c2028
_d2028