Figure 2-1 | Hierarchical Database Model | 11 |
Figure 3-1 | Example of a Simple Application That Accesses an IMS Database Through DL/I | 19 |
Figure 3-2 | Example of an EJB That Accesses an IMS Database Through the JDBC Interface | 21 |
Figure 3-3 | Accessing IMS DB from Other Programs | 23 |
Figure 3-4 | Accessing IMS TM from Other Programs | 25 |
Figure 4-1 | Structure of a Sample IMS DB/DC Environment | 30 |
Figure 4-2 | Structure of a Sample IMS DBCTL Environment | 32 |
Figure 4-3 | Structure of a Sample IMS DCCTL Environment | 34 |
Figure 4-4 | Structure of an IMS DB Batch Environment | 35 |
Figure 4-5 | JMP or JBP Application That Uses the IMS Java Function | 40 |
Figure 4-6 | Client Systems, CQS, and a Coupling Facility | 41 |
Figure 7-1 | Example of a Hierarchical Dealership Database | 68 |
Figure 7-2 | Relational Representation of the Dealership Database | 69 |
Figure 7-3 | Hierarchical Data Structure | 71 |
Figure 7-4 | Segment Types and Their Relationships | 72 |
Figure 7-5 | Two Logically Related Physical Databases: Part and Order | 74 |
Figure 7-6 | Two Logical Databases After Relating the Part and Order Databases | 76 |
Figure 7-7 | Segments Used for Secondary Indexes | 78 |
Figure 7-8 | A Physical Database and Its Secondary Index Database | 81 |
Figure 8-1 | Elements of the Physical Storage of Data | 84 |
Figure 8-2 | Layout of a Typical Segment | 85 |
Figure 8-3 | Database Segments and Pointers | 86 |
Figure 8-4 | Physical Layout of Records in an HDAM Database Data Set | 90 |
Figure 8-5 | HDAM Database Free Space Management | 92 |
Figure 8-6 | HIDAM Database in Physical Storage | 95 |
Figure 8-7 | Logical View of an HDAM Database and a PHDAM Database | 98 |
Figure 8-8 | A Logical View of a HIDAM and a PHIDAM | 100 |
Figure 8-9 | Overall Structure of a Fast Path DEDB | 103 |
Figure 10-1 | Database Unload Processing | 132 |
Figure 10-2 | Simple Database Reload Processing | 134 |
Figure 10-3 | Database Reload Processing with Secondary Indexes | 136 |
Figure 10-4 | Database Reload Processing with Logical Relationships | 138 |
Figure 10-5 | Database Reload Processing with Secondary Indexes and Logical Relationships | 140 |
Figure 10-6 | Offline Reorganization of a HALDB database | 143 |
Figure 10-7 | The Relationship between Input Data Sets and Output Data Sets during the Online Reorganization of a HALDB Partition | 147 |
Figure 10-8 | The Normal Processing Steps of HALDB Online Reorganization | 150 |
Figure 11-1 | IMS Database Recovery Process | 152 |
Figure 11-2 | Overview of the Recovery Utilities | 155 |
Figure 11-3 | Inputs to and Outputs from the Database Image Copy Utility | 156 |
Figure 11-4 | Inputs to and Outputs from the Database Image Copy 2 Utility | 158 |
Figure 11-5 | Inputs to and Outputs from the Online Database Image Copy Utility | 159 |
Figure 11-6 | Inputs to and Outputs from the Database Change Accumulation Utility | 160 |
Figure 11-7 | Inputs to and Outputs from the Database Recovery Utility | 162 |
Figure 11-8 | Inputs to and Outputs from the Batch Backout Utility | 164 |
Figure 12-1 | Transmission, Message, and Segment Relationships | 172 |
Figure 12-2 | Format of a Message Segment | 172 |
Figure 12-3 | The IMS Control Region, Its Control, and Data (Message) Flow | 174 |
Figure 12-4 | Components of a Network | 176 |
Figure 12-5 | System Overview using IMS Connect | 187 |
Figure 12-6 | Sample Traditional Master Terminal Screen | 192 |
Figure 12-7 | Sample JCL for the Secondary Master Spool | 193 |
Figure 13-1 | Input Message Processing | 196 |
Figure 13-2 | Overview of the Message Queuing Process | 199 |
Figure 13-3 | Basic Shared-Queues Environment | 202 |
Figure 13-4 | Components of a Shared-Queues Environment | 204 |
Figure 13-5 | Message Scheduling Based on Information in the PSB | 207 |
Figure 13-6 | Sample APPLCTN Macro Transaction Definition in IMS Stage 1 Input | 207 |
Figure 13-7 | Example of MPR PROC Statement | 209 |
Figure 13-8 | Example of /ASSIGN CLASS Command | 209 |
Figure 13-9 | Example of /DISPLAY ACTIVE Command | 210 |
Figure 14-1 | Structure of an IMS Application Program | 219 |
Figure 14-2 | Application PCB Structure | 224 |
Figure 14-3 | Example of a DB PCB Mask in COBOL | 225 |
Figure 14-4 | Examples of Concatenated Keys | 227 |
Figure 14-5 | Example of an Online Application PCB Mask | 227 |
Figure 14-6 | Example of a COBOL Application Program Testing Status Codes | 229 |
Figure 14-7 | Sample TP PCB | 231 |
Figure 14-8 | Example of a Simple DB PCB | 232 |
Figure 14-9 | IMS Control Block Generation and Usage | 234 |
Figure 15-1 | Sample Call Format | 247 |
Figure 15-2 | Basic Get Unique Call | 248 |
Figure 15-3 | Unqualified Get Next Call | 249 |
Figure 15-4 | Qualified Get Next Call | 250 |
Figure 15-5 | Qualified Get Next Call with Qualified SSA | 251 |
Figure 15-6 | Sample Combination of a Get Hold Unique Call and a Replace Call | 252 |
Figure 15-7 | Sample Combination of a Get Hold Unique Call and a Delete Call | 253 |
Figure 15-8 | Basic Insert Call | 254 |
Figure 15-9 | Example of an SSA with D and P Command Codes | 255 |
Figure 15-10 | Sample Path Retrieve Call | 256 |
Figure 15-11 | Example of a Hyphen (-) Command Code | 258 |
Figure 15-12 | Example of a COBOL Batch Program | 261 |
Figure 15-13 | Example of a PL/I Batch Program | 263 |
Figure 15-14 | Example of a PSB with a Secondary Index Defined | 267 |
Figure 15-15 | Example of a Get Unique Call Using a Secondary Index | 268 |
Figure 15-16 | Loading a HIDAM Database That Has Logical Relationships | 272 |
Figure 15-17 | Loading a Database That Has Secondary Indexes | 273 |
Figure 15-18 | Loading a Database That Has Logical Relationships and Secondary Indexes | 274 |
Figure 16-1 | General MPP Structure and Flow | 282 |
Figure 17-1 | Message Formatting Using MFS | 299 |
Figure 17-2 | MFS Utilities and Their Output | 301 |
Figure 17-3 | Overview of the MFS Online Environment | 302 |
Figure 17-4 | Overview of the MFS Test Environment | 303 |
Figure 17-5 | MFS Input Formatting | 306 |
Figure 18-1 | DLIModel Utility Inputs and Outputs | 313 |
Figure 18-2 | JMP Application Example | 314 |
Figure 18-3 | JBP Application Example | 316 |
Figure 18-4 | WebSphere Application Server for z/OS EJB Using the IMS Java Function | 318 |
Figure 18-5 | The IMS Java Function and WebSphere Application Server Components | 319 |
Figure 18-6 | DB2 UDB for z/OS Stored Procedure Using IMS Java | 320 |
Figure 18-7 | CICS Application Using IMS Java | 321 |
Figure 18-8 | Overview of XML Storage in IMS | 322 |
Figure 18-9 | Creating XML Using the retrieveXML UDF and the getClob Method | 322 |
Figure 18-10 | How XML Is Decomposed and Stored in IMS Segments | 324 |
Figure 18-11 | Intact Storage of XML with a Secondary Index | 326 |
Figure 19-1 | Overview of the Preprocessor Stage of the System Definition Process | 330 |
Figure 19-2 | Overview of Stage 1 and Stage 2 of the System Definition Process | 331 |
Figure 19-3 | Static Resources: Node and Static Terminals | 340 |
Figure 19-4 | ETO Dynamic Resources: User and Dynamic Terminals | 341 |
Figure 19-5 | Summary of ETO Implementation | 345 |
Figure 22-1 | Inputs and Outputs of the Log Archive Utility | 370 |
Figure 23-1 | Logs Produced for Recovery and Restart | 382 |
Figure 23-2 | How DBRC Works with the Database Recovery Utility | 386 |
Figure 23-3 | DBRC's Role in Utility Execution | 390 |
Figure 23-4 | Example of a RECON Data Set Definition | 399 |
Figure 23-5 | Example JCL for Allocating RECON Data Sets Dynamically | 400 |
Figure 24-1 | Sample Program Isolation Trace Report | 417 |
Figure 27-1 | Example of Sysplex Data Sharing with Four IMSs | 470 |
Figure 27-2 | Moving a Dependent Region Between IMSs | 471 |
Figure 27-3 | Example of a Dependent Region Running with a Different Control Region | 472 |
Figure 27-4 | Sample FDBR Configuration | 473 |
Figure 27-5 | Example of VTAM USERVAR Exit Routing IMS Logons | 476 |
Figure 27-6 | VTAM Generic Resources Distributing IMS Logons in a Sysplex | 477 |
Figure 27-7 | TN3270 Client Connecting to IMS | 479 |
Figure 27-8 | IND Connecting to Multiple IMSs through IMS Connect | 480 |
Figure 27-9 | Web Connections to IMS Using the Sysplex Distributor and IMS Connect | 481 |
Figure 27-10 | VTAM Sessions of Three IMSs Connected Using MSC | 482 |
Figure 27-11 | A Single IMS with a Single Message Queue | 484 |
Figure 27-12 | Two IMSs Accessing One Message Queue on a Coupling Facility | 484 |
Figure 27-13 | SNPS Example Scenario: Logon Is Not Terminated When Its IMS Fails | 486 |
Figure 27-14 | MNPS Example Scenario: Logon Is Not Terminated When Its IMS Fails | 487 |
Figure 27-15 | ARM Restarting an Abended IMS | 489 |
Figure 27-16 | ARM Restarting IMS, CICS, and DB2 after a z/OS Failure | 490 |
Figure 27-17 | Three IMSs on Three z/OSs Sharing One IRLM Lock Structure on a Coupling Facility | 491 |
Figure 27-18 | IRLM Structure on Failed Coupling Facility Is Rebuilt on Another Coupling Facility | 492 |
Figure 27-19 | IRLM Structure Rebuilt on Another Coupling Facility After a Connectivity Failure | 492 |
Figure 27-20 | Shared VSO Structure Duplexed on Two Coupling Facilities | 493 |
Figure 27-21 | System-Managed Duplicate Shared VSO Structure Is Used After a Coupling Facility Failure | 494 |
Figure 28-1 | Sample IMSplex Configuration with a CSL | 497 |
Figure 28-2 | Minimum CSL Configuration for an IMSplex | 499 |
