CICS programming guidelines | |
CICS program design | |
Traditional program design vs. modular program design | p. 4 |
Traditional program design | p. 4 |
Modular program design | p. 5 |
Pseudo-conversational programming | p. 6 |
A program development procedure | p. 8 |
Program specifications | p. 9 |
Event/response charts | p. 12 |
Structure charts | p. 14 |
A general procedure for designing the first two levels of a structure chart | p. 14 |
A general procedure for designing one leg of a structure chart | p. 15 |
Design variations for modular programs | p. 17 |
Design considerations for the presentation logic | p. 18 |
Design considerations for the business logic | p. 20 |
Structure listings | p. 22 |
CICS programming fundamentals | |
How programs execute under CICS | p. 24 |
CICS supports multitasking | p. 24 |
How CICS invokes an application program | p. 24 |
Program storage | p. 26 |
The Working-Storage Section | p. 26 |
The Linkage Section | p. 27 |
The Procedure Division: Coding basics | p. 30 |
How to code program modules | p. 30 |
How to code CICS commands | p. 30 |
How to handle exceptional conditions | p. 31 |
The Procedure Division: Controlling program processing | p. 32 |
Traditional design: How to code the top-level module of a program | p. 32 |
Modular design: How to code the top-level module of the business logic portion | p. 34 |
How to detect the use of AID keys | p. 36 |
How to invoke other programs | p. 38 |
The Procedure Division: User interface and I/O considerations | p. 40 |
How to modify attribute bytes | p. 40 |
How to control cursor positioning | p. 42 |
How to edit terminal input data | p. 43 |
How to update file records | p. 44 |
COBOL features you can't use in a command-level CICS program | p. 45 |
Coding conventions found in older programs | p. 46 |
JCL procedures for CICS program development | |
Preparing a CICS program for execution | p. 48 |
How to prepare a BMS mapset | p. 50 |
How to prepare a command-level COBOL program | p. 52 |
Translator and compiler options | p. 54 |
Testing and debugging | |
Installation-dependent considerations | p. 58 |
4 common types of testing | p. 58 |
CICS testing environments | p. 59 |
Developing a unit test plan | p. 60 |
A 3-step plan for unit testing | p. 60 |
A checklist for program testing | p. 61 |
Testing a program from the top down | p. 62 |
Additional considerations for modular programs | p. 64 |
CICS service transactions for testing and debugging | p. 65 |
CESN: The sign-on transaction | p. 65 |
CESF: The sign-off transaction | p. 65 |
CEMT: The master terminal transaction | p. 66 |
CECI: The command-level interpreter | p. 68 |
CEDF: The Execution Diagnostics Facility | p. 70 |
CICS abend codes | p. 72 |
Exceptional condition abends | p. 72 |
Program check abends (ASRA abend code) | p. 73 |
Other abend codes | p. 73 |
Transaction dump debugging | p. 74 |
How to determine the cause of an abend | p. 74 |
How to determine the instruction that caused the abend | p. 74 |
A model program using two different designs | |
The customer maintenance program: Traditional design | p. 76 |
The program overview | p. 77 |
The screen layouts | p. 78 |
The copy members | p. 79 |
The error-handling program (SYSERR) | p. 80 |
The event/response chart | p. 81 |
The structure chart | p. 82 |
The BMS mapset | p. 83 |
The symbolic map | p. 87 |
The customer maintenance program: CUSTMNT2 | p. 90 |
The customer maintenance program: Modular design | p. 101 |
The program overview | p. 102 |
The screen layouts | p. 103 |
The copy members | p. 104 |
The error-handling program (SYSERR) | p. 105 |
The event/response chart | p. 106 |
The structure chart for the presentation logic | p. 107 |
The structure chart for the business logic | p. 108 |
The BMS mapset for the presentation logic | p. 109 |
The symbolic map for the presentation logic | p. 113 |
The presentation logic program: CSTMNTP | p. 116 |
The business logic program: CSTMNTB | p. 125 |
3 more model programs | |
The menu program | p. 132 |
The program overview | p. 132 |
The screen layout | p. 133 |
The event/response chart | p. 134 |
The structure chart | p. 134 |
The BMS mapset | p. 135 |
The symbolic map | p. 137 |
The menu program: INVMENU | p. 138 |
The customer inquiry program | p. 141 |
The program overview | p. 141 |
The screen layout | p. 142 |
The event/response chart | p. 143 |
The structure chart | p. 144 |
The BMS mapset | p. 145 |
The symbolic map | p. 147 |
The customer inquiry program: CUSTINQ2 | p. 149 |
The order entry program | p. 156 |
The program overview | p. 156 |
The screen layout | p. 157 |
The event/response chart | p. 158 |
The structure chart | p. 159 |
The BMS mapset | p. 160 |
The programmer-generated symbolic map | p. 163 |
The order entry program: ORDRENT | p. 166 |
The GETINV subprogram | p. 178 |
The INTEDIT subprogram | p. 179 |
The NUMEDIT subprogram | p. 180 |
CICS command reference | |
CICS command preview | |
Syntax conventions | p. 186 |
Syntax notation | p. 186 |
Argument values | p. 186 |
Data types | p. 187 |
RESP and RESP2 options | p. 188 |
Commands by function | p. 189 |
CICS commands: An alphabetical list of the commands that are commonly used in CICS/COBOL programs, with command syntax, option explanations, exceptional conditions, notes and tips on usage, and coding examples | |
Basic Mapping support | |
BMS mapset definition for 3270 displays | |
Characteristics of 3270 displays | p. 470 |
Standard attributes | p. 470 |
The format and contents of an attribute byte | p. 472 |
Extended attributes | p. 474 |
Recommendations for formatting screen displays | p. 476 |
How to code a BMS mapset | p. 478 |
The commands and macros in a BMS mapset | p. 478 |
Assembler language syntax | p. 479 |
The DFHMSD macro instruction | p. 480 |
The DFHMDI macro instruction | p. 484 |
The DFHMDF macro instruction | p. 488 |
The symbolic map | p. 494 |
BMS-generated symbolic maps | p. 494 |
How to create your own symbolic map | p. 498 |
A complete BMS mapset | p. 500 |
Creating HTML documents from BMS mapsets | |
How to prepare an HTML template | p. 504 |
The conversion process | p. 504 |
JCL that invokes the DFHMAPT procedure | p. 504 |
The DFHMAPT procedure | p. 505 |
Generated HTML output | p. 506 |
Standard output | p. 506 |
Customized output | p. 507 |
How to create a customizing macro definition with DFHMDX | p. 508 |
The DFHMDX macro | p. 509 |
The DFHWBOUT macro | p. 512 |
CICS program development aids | |
AMS commands to define and manipulate VSAM files | |
How to code AMS commands | p. 516 |
Parameters, continuation lines, and abbreviations | p. 516 |
Parameter values and subparameter lists | p. 516 |
Parameter groups and parentheses | p. 517 |
Comments | p. 517 |
How to invoke AMS using JCL | p. 518 |
The DD statement for VSAM files | p. 518 |
Coding example | p. 518 |
The DEFINE CLUSTER command | p. 519 |
The DEFINE ALTERNATEINDEX command | p. 523 |
The DEFINE PATH command | p. 526 |
The BLDINDEX command | p. 527 |
The LISTCAT command | p. 529 |
The ALTER command | p. 531 |
The DELETE command | p. 532 |
The PRINT command | p. 533 |
The REPRO command | p. 535 |
CICS resource definition | |
Resource Definition Online (RDO) basics | p. 538 |
RDO transactions | p. 538 |
How to enter CEDA commands | p. 538 |
The CEDA DEFINE command | p. 540 |
How to define mapsets | p. 541 |
How to define programs | p. 542 |
How to define transactions | p. 543 |
How to define files | p. 544 |
CICS service transactions | |
The Master Terminal Transaction (CEMT) | p. 548 |
The terminal status transaction (CEOT) | p. 551 |
The temporary storage browse transaction (CEBR) | p. 552 |
The message switching transaction (CMSG) | p. 553 |
The page retrieval transaction (CSPG) | p. 556 |
Reference tables | |
Hex/binary equivalents | p. 558 |
EBCDIC code table | p. 559 |
Attribute bytes | p. 562 |
Execute Interface Block fields | p. 563 |
DFHAID field names for EIBAID values | p. 564 |
Table of Contents provided by Syndetics. All Rights Reserved. |
The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.
The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.