Ever since command-level programming was introduced in CICS in 1975, an in-memory process called the communications area (COMMAREA) has been used to pass data from one application to another. From its inception, the size of the COMMAREA was held in a half-word data field— the EIBCALEN—which limited the size of the COMMAREA to 32KB. Although this was a problem, since most application...
Table of Contents
- 10 Years of Enterprise Linux on IBM System z
- An Implementation Fast Path for CICSPlex SM
- CICS and Web 2.0
- CICS as a Web Services Provider: A Design to Foil Attacks
- Cloud Perspectives: The Inclusive Cloud
- Compliance Options: Modeling Governance and Compliance
- DB2 for z/OS SQL Performance Choices
- DB2 Tips: Reorganize DB2 on z/OS Objects to Save Time and Money
- HiperDispatch: A Conceptual Overview
- Integrating Mainframe-Based Legacy Applications Using Mashups and Web 2.0
- IT Sense: Great Symphonies Require Maestros and Virtuosos
- Linux on System z: Here, Kitty, Kitty … Examining xCAT
- Mainframe Security: Operating System Protection
- Pete Clark on z/VSE: z/VSE, z/VM, and Linux Requirements Processing
- Storage & Data Management: Mainframe Storage Efficiencies Outpace Open Systems
- The Secrets of Better Batch
- Top-10 Features of DB2 10 for z/OS: A Preview
- Using the CICSPlex SM API and z/OS Named Tokens to Load Balance CTG/CICS Services
- z/Data Perspectives: The 10 Database Commandments
- z/OS Data De-De-De-De-duplication
- z/Vendor Watch: New “Green” Business Sustains Mainframe Growth
