IMS Installation Guide 8

8/10/2019 IMS Installation Guide 8

1/355


2/355


3/355

International Technical Support Organization

IMS Version 8 Implementation GuideA Technical Overview of the New Features

October 2002

SG24-6594-00


4/355

Copyright International Business Machines Corporation 2002. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM

Corp.

First Edition (October 2002)

This edition applies to IMS Version 8 (program number 5655-C56) or later for use with the OS/390 or z/OSOperating System.

Note: Before using this information and the product it supports, read the information in Notices onpage xi .

Note: This book is based on a pre-GA version of a product and may not apply when the product becomesgenerally available. We recommend that you consult the product documentation or follow-on versions ofthis redbook for more current information.


5/355

Copyright IBM Corp. 2002. All righ ts reserved.iii

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiThe team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiBecome a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

Part 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 Introduction to the enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 Availability and recoverability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2.1 Database Recovery Control (DBRC) enhancements . . . . . . . . . . . . . . . . . . . . . . . 4

1.2.2 Database Image Copy 2 enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2.3 HALDB enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2.4 Batch Resource Recovery Service (RRS) support . . . . . . . . . . . . . . . . . . . . . . . . . 71.2.5 Remote Site Recovery (RSR) enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2.6 Enhanced availability by using the Resource Manager (RM) . . . . . . . . . . . . . . . . . 71.2.7 Common Queue Server (CQS) enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2.8 APPC and OTMA enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2.9 APPC/IMS enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2.10 IMS Online Recovery Service (ORS) support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2.11 System Log Data Set (SLDS) dynamic backout processing . . . . . . . . . . . . . . . . . 9

1.3 Performance and capacity enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.3.1 Fast Path enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.3.2 Parallel database processing enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.3.3 IMS MSC FICON CTC support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3.4 Virtual storage constraint relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.4 Systems management enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.4.1 BPE enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.4.2 Common Service Layer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.4.3 Installation and configuration enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.4.4 Syntax Checker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.4.5 Transaction trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.5 Application enablement enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.5.1 Java enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Part 2. IMS Version 8 base enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 2. Packaging and installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.1 Product packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.1.1 Installation changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.1.2 Changes in target and distribution data sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.1.3 SMP/E processing changes in IMS Version 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.1.4 User exits in IMS Version 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.2 IVP changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.2.1 Execution steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.2.2 IMS Java IVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26


6/355

iv IMS Version 8 Implementation Guide

2.3 IMS system definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.3.1 Changed minimum and default values for RECLNG in MSGQUEUE macro . . . . 26

2.4 New and obsolete execution parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 3. Syntax Checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.2 Getting started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3 Using the Syntax Checker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.3.1 Changing releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.3.2 Display options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.3.3 Save options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 4. Database management enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.1 Database Image Copy 2 enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

4.1.1 Multiple DBDS and ADS copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.1.2 Group name support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.1.3 Single output data set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.1.4 Support for the DFSMSdss OPTIMIZE option . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.1.5 GENJCL support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4.2 Parallel database processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.2.1 DBRC authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.2.2 Full function database allocation, open and close processing . . . . . . . . . . . . . . . 554.2.3 Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

4.3 Fast Path DEDB enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.3.1 DEDB support greater than 240 areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.3.2 Nonrecoverable DEDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.3.3 Coupling Facility support for DEDB VSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.3.4 Unused IOVF count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

4.4 Batch RRS support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.4.1 Supported environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.4.2 Activation and requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

4.5 Coordinated IMS/DB2 disaster recovery support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624.5.1 XRC tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.5.2 Log synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.5.3 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.5.4 Messages and log records changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664.5.5 Coexistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 5. Database Recovery Control enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 695.1 Support of 16 MB RECON record size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

5.1.1 RECON record spanning segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.1.2 Usage of alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

5.2 DBRC PRILOG compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.3 DBRC command authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

5.3.1 Security support for DBRC commands and protected resources . . . . . . . . . . . . . 745.3.2 The resource name table DSPRNTBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745.3.3 How command authorization gets invoked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745.3.4 Supported environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.3.5 Usage of the DBRC command authorization exit (DSPDCAX0). . . . . . . . . . . . . . 765.3.6 DBRC command authorization examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5.4 Avoidance of certain DBRC abends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795.5 Automatic RECON loss notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805.6 IMS version coexistence for DBRC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80


7/355

Contentsv

Chapter 6. Transaction trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.1 Transaction trace (MVS component trace) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

6.1.1 How transaction trace works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846.1.2 How to use transaction trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866.1.3 Sample transaction trace output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 7. APPC base enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897.1 Dynamic LU 6.2 descriptor support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

7.1.1 Add a new LU 6.2 descriptor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907.1.2 Delete an LU 6.2 descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

7.2 CPU time limit for CPI-C driven transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927.3 Support for APPC outbound LU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 8. Application enablement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968.2 Java dependent regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

8.2.1 Persistent Reusable Java Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978.2.2 Benefits of a JVM environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978.2.3 Other IMS Java considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

8.2.4 DFSJMP and DFSJBP procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988.2.5 JVMOPMAS and JVMOPWKR members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998.2.6 ENVIRON= and DFSJVMAP members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018.2.7 IMS system definition considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028.2.8 PSBGEN considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038.2.9 /DISPLAY examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

8.3 Java standards enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048.3.1 Java result set types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048.3.2 Java result set concurrency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058.3.3 Batch updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068.3.4 New SQL keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

8.4 JDBC access enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

8.5 Java Tooling enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1088.6 XML and IMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Chapter 9. Java enhancements for IMS and WebSphere . . . . . . . . . . . . . . . . . . . . . . 1099.1 WebSphere 4.0.1 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109.2 J2EE architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109.3 DataSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119.4 Enterprise Archive (.ear) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1139.5 Deploying the ear file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

9.5.1 Configure the WebSphere server region for IMS access . . . . . . . . . . . . . . . . . . 1149.5.2 Obtain the WebSphere for z/OS System Administration tool . . . . . . . . . . . . . . . 1179.5.3 Install an IMS JDBC Resource Adapter into a WebSphere server region. . . . . . 1189.5.4 Configure and deploy an instance of the IMS JDBC Resource Adapter. . . . . . . 122

9.6 Configure and deploy an Enterprise Archive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1259.7 IVP for WebSphere for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

9.7.1 Untar the IVP Enterprise Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1259.7.2 Configure an IMS JDBC Resource Adapter instance for the IVP EJB . . . . . . . . 1269.7.3 Import, deploy and export the IVP application . . . . . . . . . . . . . . . . . . . . . . . . . . 1269.7.4 Deploy and configure the Enterprise Archive (imsjavaIVP.ear) . . . . . . . . . . . . . 1279.7.5 Update the HTTP Server for access to the IVP Web application . . . . . . . . . . . . 130

9.8 Test the IVP application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1319.9 Error logging and tracing in WebSphere for z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

9.9.1 Sample trace outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133


8/355

vi IMS Version 8 Implementation Guide

Part 3. IMS Version 8 Parallel Sysplex enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Chapter 10. Coupling Facility structure management . . . . . . . . . . . . . . . . . . . . . . . . . 13710.1 System managed rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13810.2 Alter and autoalter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13910.3 System managed duplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

10.3.1 Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14010.3.2 Duplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14010.3.3 Enabling duplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14110.3.4 Disabling duplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

10.4 Which structures support which features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Chapter 11. Base Primitive Environment enhancements . . . . . . . . . . . . . . . . . . . . . . 14311.1 Base Primitive Environment (BPE) enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . 14411.2 New BPE address space initialization module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14411.3 User exits and statistics for BPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

11.3.1 BPE configuration parameters member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14511.3.2 BPE user exit list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

11.4 Displaying the BPE and CQS versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Chapter 12. Shared queues support for APPC and OTMA synchronous messages 14712.1 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14812.2 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14812.3 Migration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

12.3.1 Synchronous messages and program-to-program switches. . . . . . . . . . . . . . . 15012.3.2 Error conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15112.3.3 Other miscellaneous migration considerations . . . . . . . . . . . . . . . . . . . . . . . . . 15112.3.4 Support considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Part 4. Common Service Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Chapter 13. Common Service Layer (CSL) architecture . . . . . . . . . . . . . . . . . . . . . . . 15513.1 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

13.1.1 The IMSplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16013.1.2 Systems management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16113.1.3 Operations management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16113.1.4 Resource Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

13.2 Common Service Layer (CSL) architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16213.3 Structured Call Interface (SCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16313.4 Operations Manager (OM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

13.4.1 Today . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16413.4.2 OM infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16513.4.3 OM clients and their roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16813.4.4 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

13.4.5 User exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17013.5 Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

13.5.1 Resource management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17213.5.2 Resource management infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17213.5.3 RM clients and their roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17313.5.4 Resource structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17413.5.5 Common Queue Server (CQS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17413.5.6 Resource Manager (RM) address space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17513.5.7 RM characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176


9/355

Contentsvii

Chapter 14. Sysplex terminal management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17714.1 Sysplex terminal management objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17814.2 Sysplex terminal management environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17914.3 IMSplex resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17914.4 STM terms and concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

14.4.1 Resource type consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

14.4.2 Resource name uniqueness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18514.4.3 Resource status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18614.4.4 Significant status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18814.4.5 Status recovery mode (SRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18914.4.6 Status recoverability (RCVYxxxx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

14.5 Enabling sysplex terminal management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19014.5.1 Setting SRM and RCVYxxxx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19114.5.2 Overriding SRM and RCVYxxxx defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

14.6 Ownership and affinities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19214.6.1 Resource ownership and RM affinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19214.6.2 VTAM generic resources affinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19314.6.3 Setting VGR affinity management responsibility . . . . . . . . . . . . . . . . . . . . . . . . 19314.6.4 VGR affinities and IMS Version 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

14.7 Resources and the resource structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19514.7.1 Resource structure components and characteristics . . . . . . . . . . . . . . . . . . . . 19514.7.2 Resource entries in the resource structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

14.8 STM in action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20114.8.1 Before the first IMS joins the IMSplex. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20214.8.2 Start IMSplex address spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20214.8.3 Log on from a static NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20214.8.4 Logon from an ETO NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20214.8.5 Signon from an ETO NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20314.8.6 Commands that change significant status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20314.8.7 Work which changes end-user significant status . . . . . . . . . . . . . . . . . . . . . . . 20314.8.8 Commands which change end-user status. . . . . . . . . . . . . . . . . . . . . . . . . . . . 20314.8.9 Session termination with significant status (not IMS failure) . . . . . . . . . . . . . . . 20414.8.10 Logon from NODE which already exists in resource structure . . . . . . . . . . . . 20414.8.11 IMS failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20414.8.12 IMS emergency restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20514.8.13 Recovering significant status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20614.8.14 Recovering conversations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20614.8.15 Recovering Fast Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20814.8.16 Recovering STSN sequence numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20814.8.17 Summary of STM in action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

14.9 Resource structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20914.9.1 Defining the resource structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20914.9.2 Managing the resource structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21014.9.3 Structure failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21014.9.4 Loss of connectivity to a structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21114.9.5 SCI, RM, CQS, or structure failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

14.10 Miscellaneous other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21114.10.1 IMS exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21114.10.2 Global callable services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21214.10.3 Extended Recovery Facility (XRF) considerations . . . . . . . . . . . . . . . . . . . . . 21314.10.4 Rapid Network Reconnect (RNR) considerations . . . . . . . . . . . . . . . . . . . . . . 213

14.11 Summary of sysplex terminal management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214


10/355

viii IMS Version 8 Implementation Guide

Chapter 15. Global online change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21515.1 Online change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

15.1.1 Review of local online change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21615.1.2 Overview of global online change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

15.2 Setting up the global online change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21915.2.1 Preparation for global online change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

15.2.2 Overview of execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22015.2.3 OLCSTAT data set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22115.2.4 DFSUOLC0 functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22115.2.5 DFSUOLC procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22115.2.6 Initializing OLCSTAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22215.2.7 OLC copy utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

15.3 Global online change processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22315.3.1 Prepare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22315.3.2 Commit phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22515.3.3 Commit phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22615.3.4 Commit phase 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

15.4 Terminate command usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22915.5 Status display commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

15.5.1 QUERY MEMBER TYPE(IMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22915.5.2 QUERY OLC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23015.5.3 /DISPLAY MODIFY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

15.6 Adding and deleting IMS subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23115.7 Inactive subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23215.8 Resource consistency checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23215.9 Migration and fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23315.10 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Chapter 16. Single point of control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23516.1 Introduction to SPOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

16.1.1 Command behaviors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

16.2 TSO SPOC application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23816.2.1 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23916.2.2 Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24216.2.3 IMSplex and classic command displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24316.2.4 Defining groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24616.2.5 Defining command shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24616.2.6 Saving and printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24816.2.7 Sorting and searching results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24916.2.8 Command status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25316.2.9 Leaving the SPOC application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Chapter 17. User written interface to Operations Manager . . . . . . . . . . . . . . . . . . . . . 255

17.1 Introduction to Operations Manager user interface . . . . . . . . . . . . . . . . . . . . . . . . . . 25617.2 REXX SPOC example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25717.2.1 The REXX SPOC environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25817.2.2 Sample REXX API program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Chapter 18. Automatic RECON loss notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26518.1 The benefits of automatic RECON loss notification . . . . . . . . . . . . . . . . . . . . . . . . . 26618.2 Getting started with automatic RECON loss notification . . . . . . . . . . . . . . . . . . . . . . 267

18.2.1 Two choices to enable ARLN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26718.2.2 How to migrate and fallback from automatic RECON loss notification . . . . . . . 268

18.3 DSPSCIX0 details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269


11/355

Contentsix

18.4 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Chapter 19. Language Environment (LE) dynamic run time options . . . . . . . . . . . . . 27919.1 LE overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28019.2 Defining LE run time options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28019.3 Dynamic run time option support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28119.4 DFSCGxxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28219.5 New commands and enhanced DL/I INQY call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

19.5.1 Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28219.5.2 Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28319.5.3 Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28319.5.4 DFSBXITA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28419.5.5 DL/I INQY LERUNOPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28419.5.6 Migration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28519.5.7 Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28619.5.8 LE option recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Chapter 20. Common Service Layer configuration and operation . . . . . . . . . . . . . . . 28920.1 Setting up a CSL environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

20.1.1 Basic rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29020.1.2 Base primitive environment (BPE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29120.1.3 Update the CFRM couple data set (CDS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29220.1.4 Set up the Structured Call Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29320.1.5 Set up the Operations Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29420.1.6 CQS procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29520.1.7 Set up the Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29620.1.8 Set up IMS PROCLIB members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29620.1.9 Set up TSO logon procedure for SPOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

20.2 CSL operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29820.2.1 The CSL execution environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29820.2.2 Starting IMSplex address spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

20.2.3 Shutting down IMSplex address spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30020.3 IMS commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

20.3.1 IMSplex commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30120.3.2 Classic commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30120.3.3 CSL operations summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Part 5. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Appendix A. Hardware and software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 307A.1 Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

A.1.1 Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308A.1.2 System console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308A.1.3 Tape units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308A.1.4 Direct access devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308A.1.5 Multiple systems coupling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308A.1.6 Terminals supported by IMS Version 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308A.1.7 Sysplex data sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309A.1.8 Shared message queues and shared EMH queues . . . . . . . . . . . . . . . . . . . . . . 309A.1.9 DEDB shared VSO enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309A.1.10 Remote Site Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

A.2 Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310A.2.1 Data sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311A.2.2 DBRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311


12/355

x IMS Version 8 Implementation Guide

A.2.3 IMS Java. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311A.2.4 Small programming enhancements (SPEs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311A.2.5 Sysplex data sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312A.2.6 Transaction trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

A.3 IBM IMS Tools for IMS Version 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

Appendix B. Resource structure sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315The resource structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Resource types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Resource number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317Data element number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318Resource table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318Adjusting the size of the Resource Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Appendix C. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Other resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325Referenced Web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

IBM Redbooks collections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329


13/355

Copyright IBM Corp. 2002. All righ ts reserved.xi

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consultyour local IBM representative for information on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state or imply that only that IBM product,program, or service may be used. Any functionally equivalent product, program, or service that does notinfringe any IBM intellectual property right may be used instead. However, it is the user's responsibility toevaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. Thefurnishing of this document does not give you any license to these patents. You can send license inquiries, inwriting, to:IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law : INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically madeto the information herein; these changes will be incorporated in new editions of the publication. IBM may makeimprovements and/or changes in the product(s) and/or the program(s) described in this publication at any timewithout notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurringany obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirm theaccuracy of performance, compatibility or any other claims related to non-IBM products. Questions on thecapabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate themas completely as possible, the examples include the names of individuals, companies, brands, and products.All of these names are fictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrates programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing application

programs conforming to the application programming interface for the operating platform for which the sampleprograms are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, anddistribute these sample programs in any form without payment to IBM for the purposes of developing, using,marketing, or distributing application programs conforming to IBM's application programming interfaces.


14/355

xii IMS Version 8 Implementation Guide

TrademarksThe following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both:

AIXATC/MVSCICSCUADATABASE 2DB2DFSDFSMSdssES/9000ESCONFICON

IBMIMSIMS/ESALanguage EnvironmentMQSeriesMVSNetViewNetViewOS/390Parallel SysplexRACFRedbooks

Redbooks(logo) RMFS/390SequentSPSystem/370VM/ESAVSE/ESAVTAMWebSpherez/OSzSeries

The following terms are trademarks of International Business Machines Corporation and Lotus DevelopmentCorporation in the United States, other countries, or both:

Lotus Word Pro

The following terms are trademarks of other companies:

ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the UnitedStates, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems,Inc. in the United States, other countries, or both.

C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure ElectronicTransaction LLC.

Other company, product, and service names may be trademarks or service marks of others.


15/355

Copyright IBM Corp. 2002. All righ ts reserved.xiii

Preface

In this IBM Redbook, we describe the new features and functions in IMS Version 8. We

document the tasks necessary to exploit the features, and identify migration, coexistence, andfallback considerations. We also identify specific hardware and software requirements thatare needed to exploit certain enhancements.

First we provide an overview, where we have grouped the various enhancements and theirdiscussion into the categories availability and recoverability, performance and capacity,systems management, and application enablement. Then we have more detailed chapters fordescribing the individual enhancements.

The base enhancements part of the book describes the base product enhancements thatapply to all users migrating to IMS Version 8. The Parallel Sysplex enhancements part of thebook describes enhancements in IMS Version 8 that apply to both existing users of IMSVersion 6 or IMS Version 7 in a Parallel Sysplex environment and users that are considering

sysplex functionality.The Common Service Layer part documents the Common Service Layer (CSL), new in IMSVersion 8, which is the next step in IMS Parallel Sysplex evolution. The CSL enables IMSsystems to operate in unison in an OS/390 Parallel Sysplex. The CSL components providethe infrastructure for an IMSplex.

The team that wrote this redbook This redbook was produced by a team of specialists from around the world working at theInternational Technical Support Organization, San Jose Center.

Jouko Jntti is a Project Leader specializing in IMS with the IBM International TechnicalSupport Organization, San Jose Center. He holds a bachelor s degree in BusinessInformation Technology from Helsinki Business Polytechnic, Finland. Before joining the ITSOin September 2001, Jouko worked as an Advisory IT Specialist at IBM Global Services,Finland. Jouko has been working on several e-business projects with customers as aspecialist in IMS, WebSphere, and UNIX on the OS/390 platform. He has also beenresponsible for the local IMS support for Finnish IMS customers. Prior to joining IBM in 1997,he worked as a systems programmer and transaction management specialist in a largeFinnish bank for 13 years, and was responsible for the bank's IMS systems.

Henry Kiesslich is an IT Specialist in IMS with IBM Global Services Germany where he is amember of the IMS Technical Support team. He has 12 years of experience in the IT fields.He holds a bachelor degree in Information Technology. His areas of expertise include CICS,

IMS and OS/390. Before he joined IBM in 1999 he was working as a systems programmer fora computer and systems center of a large steel mill and later for a large German bank for 5years, responsible for IMS systems and IMS related projects.

Roddy Munro is a Project Manager for the IMS Version 8 QPP for EMEA in the ProductIntroduction Centre (PIC) in the UK. He has 22 years of experience in the IMS field and hasworked at IBM for 28 years. His areas of expertise include IMS, CICS, DB2, and MQSeries.He holds a bachelor s degree in Geology, and joined IBM initially as an IMS applicationprogrammer. Subsequently he has worked as a systems programmer, a technical planner forCICS with IMS and DB2, and as a CICS developer. Prior to joining the PIC he was the DB/DC


16/355

xiv IMS Version 8 Implementation Guide

systems programming group leader at the Hursley lab, providing test systems to thedevelopment projects on-site.

John Schlatweiler is a Systems Manager with SBC Services, Inc. in St. Louis Missouriwhere he is a member of the IMS Support Group's IMS Development Team. He has 17 yearsof experience in the IT fields. His areas of expertise include CICS, DB2, IMS, and OS/390.John has worked as an applications developer, application architect, technical leader,database administrator, and systems programmer. Prior to joining SBC, John wasresponsible for database and transaction processing systems in a large banking environment.

Bill Stillwell is a Senior Consulting I/T Specialist and has been providing technical supportand consulting services to IMS customers as a member of the Dallas Systems Center for 20years. During that time, he developed expertise in application and database design, IMSperformance, Fast Path, data sharing, shared queues, planning for IMS Parallel Sysplexexploitation and migration, DBRC, and database control (DBCTL). He also develops andteaches IBM Education and Training courses, and is a regular speaker at the annual IMSTechnical Conferences in the United States and Europe.

Thanks to the following people for their contributions to this project:

Yvonne LyonDeanna PolmInternational Technical Support Organization, San Jose Center

Rich ConwayBob HaimowitzInternational Technical Support Organization, Poughkeepsie Center

Barbara KleinJim BahlsThomas BridgesKyle CharletRichard CooperVince HenleyRose LevinBob LoveTom MorrisonBruce NaylorKhiet NguyenDavid OrmsbyBovorit PibulsonggramKaren RansonPatrick SchroeckRichard SchneiderSandy StoobDon TerryJudy TsePedro VeraJack WiedlinIBM Silicon Valley Laboratory

Alonia Lonnie ColemanIBM Dallas Systems Center, USA

Alan CooperIBM EMEA Technical Sales, UK


17/355

Prefacexv

Alison CoughtrieIBM EMEA Product Introduction Centre, UK

Become a published author

Join us for a two- to six-week residency program! Help write an IBM Redbook dealing withspecific products or solutions, while getting hands-on experience with leading-edgetechnologies. You'll team with IBM technical professionals, Business Partners and/orcustomers.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus,you'll develop a network of contacts in IBM development labs, and increase your productivityand marketability.

Find out more about the residency program, browse the residency index, and apply online at:

ibm.com/redbooks/residencies.html

Comments welcomeYour comments are important to us!

We want our Redbooks to be as helpful as possible. Send us your comments about this orother Redbooks in one of the following ways:

Use the online Contact us review redbook form found at:

ibm.com/redbooks

Send your comments in an Internet note to:

[email protected]

Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. QXXE Building 80-E2650 Harry RoadSan Jose, California 95120-6099
http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/http://www.ibm.com/redbooks/http://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/contacts.htmlhttp://www.ibm.com/redbooks/http://www.ibm.com/redbooks/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.html


18/355

xvi IMS Version 8 Implementation Guide


19/355

Copyright IBM Corp. 2002. All righ ts reserved.1

Part 1 Introduction

In this part of the book we provide an introduction to the enhancements included in IMSVersion 8. This part consists of an overview chapter that provides a summary the newfeatures and enhancements in preparation for a more detailed review of each major item inthe other parts of the book.

Part 1


20/355

2 IMS Version 8 Implementation Guide


21/355

Copyright IBM Corp. 2002. All righ ts reserved.3

Chapter 1. Overview

In this chapter we provide an overview of the general structure for the materials to bepresented in this IBM Redbook. We introduce the enhancements made to InformationManagement System (IMS) Version 8 at the highlight level. All the major enhancements arethen fully discussed in their own chapters later in this book. The following items are onlydescribed in this overview chapter:

IBM IMS Online Recovery Service (ORS) product supportSystem log data set (SLDS) dynamic backout processingVirtual storage constraint relief (VSCR)

In the overview chapter, we have grouped the various enhancements and their discussioninto the categories of availability and recoverability, performance and capacity, systems

management, and application enablement.

1


22/355


1.1 Introduction to the enhancementsIn general terms, IMS development is driven primarily by user requirements within the contextof maintaining compatibility with existing IMS applications and data and ensuring absoluteintegrity of those applications and data. Additionally, IMS development is directed toward theearly exploitation of new facilities in the OS/390 and z/OS environments and supporting

hardware to continue to reduce the overall cost of computing.

Since the first IMS system, which was an inventory tracking system for the Apollo spaceprogram in the late 1960s, IMS has successfully provided features that have made it one ofthe leading transaction and database management systems.

Still, after more than 30 years, the strengths that have been in place from the beginning aresecond to none. Additionally, IMS has been able to evolve through the decades to takeadvantage of changes in technology. In addition to the fact that most corporate data ismanaged by IMS today, it has also been a foundation for a new generation of Web-based,high volume workload applications.

IMS Version 8 introduces significant enhancements in availability and recovery, performance

and capacity, application enablement and systems management for IMS systems.

1.2 Availability and recoverabilityA major long term goal of IMS developers is the achievement of continuous availability of IMSapplications and data. This aim includes improvements in the reliability, serviceability, andmaintainability of IMS itself. It also includes the removal of requirements for planned outagesfor system, application, and database maintenance, as well as the prevention, bypassing, orelimination of unplanned outages.

1.2.1 Database Recovery Control (DBRC) enhancementsThese are the major Database Recovery Control (DBRC) changes for IMS Version 8:

16 megabyte maximum recovery control (RECON) data set record sizePrilog compression enhancementDBRC command authorization supportAutomatic RECON loss notificationElimination of several DBRC and IMS abendNew DBRC batch commands for HALDBIncreased maximum values for DBRC groups

16 MB RECON record sizePrior to IMS Version 8, the record size for RECON data sets was limited by the type of DASD

the RECONs were defined on and was limited to a maximum of approximately 800 kilobytes.As of IMS Version 8, the maximum RECON record size is 16 MB. This eliminates the need forthe unwanted shutdown of IMS systems when some of the RECON records (usually thePRILOG record) were growing over the maximum record size.

PRILOG compressionThe efficiency of PRILOG record compression has been improved. Compression will now beattempted more frequently than was the case prior to IMS Version 8. Compression will beattempted whenever an online log data set (OLDS) archive job is run. For Remote SiteRecovery (RSR), this is when the tracking log data set is opened.


23/355

Chapter 1. Overview5

DBRC command authorization supportPrior to IMS Version 8, any user who was authorized to access the RECON data set had theauthority to enter any DBRC command. As of IMS Version 8, you can use RACF (or anequivalent product), a user-written exit, or both to control who is authorized to issue DBRCcommands. When a DBRC command is issued from the DBRC batch utility (DSPURX00),DBRC verifies that the user is authorized to issue the command.

Automatic RECON loss notificationWhen an I/O error occurs on a RECON data set and a spare data set is available, theinstance of DBRC that noticed the error copies the good RECON to the spare, activates thespare, and deallocates the original RECON data set. Prior to IMS Version 8, the other DBRCinstances sharing the same RECON data sets are not aware of the reconfiguration of theRECONs until their next access to the RECONs. They would continue to hold allocation to theoriginal (discarded) RECON. The original RECON could not be deleted and redefined until allDBRC instances deallocated it. This potentially could take a long time. As of IMS Version 8,the first DBRC now automatically notifies the other DBRCs about the reconfiguration and thediscarded RECON gets deallocated. The bad RECON data set can then be deleted andredefined as the spare.

This enhancement requires the usage of the Structured Call Interface (SCI) and thus it isdescribed in detail in the Common Service Layer (CSL) part of the book. For more informationon automatic RECON loss notification (ARLN) feature, refer to Chapter 18, AutomaticRECON loss notification on page 265.

Elimination of DBRC and IMS abendsThere are three areas that caused abends in previous releases and no longer do so underIMS Version 8:

Authorization processing DBRC will no longer abend if the SUBSYS record becomeslarger than the RECON physical record size. With the support ofRECON records up to 16 megabytes in size, the SUBSYS recordis written as multiple RECON record segments.

Database I/O error DBRC will no longer abend if recording an extended error queueelement (EEQE) causes the database data set record to exceedthe RECON physical record size.

Deallocation processing DBRC will not abend during deallocation processing if theALLOC record is not found or if the ALLOC record already has adeallocation time. Instead of the abend, error messages areissued, a dump is taken, and the status for the database area isset to prohibit further authorization status.

New DBRC batch commands for HALDBThe exiting DBRC batch commands DELETE.DB, CHANGE.DB and INIT.DB are modified

and the new commands DELETE.PART and CHANGE.PART are provided for HALDBs tosupport the deletion and change of a HALDB or one of its partitions. The INIT.DB commandalso allows a HIKEY value to be used even tough the database is defined with a partitionselection exit. This enhancement is available also for IMS Version 7 users as an APARPQ52858.

Increased maximum values for DBRC groupsThe maximum number of members allowed in change accumulation (CA) groups and DBDSgroups have been increased from 2000 to 32767.


24/355


For details on DBRC enhancements applicable to all operating environments, see Chapter 5,Database Recovery Control enhancements on page 69 . For more information on AutomaticRECON loss notification (ARLN), refer to Chapter 18, Automatic RECON loss notification onpage 265.

1.2.2 Database Image Copy 2 enhancementsThe Database Image Copy 2 (DFSUDMT0) utility has been enhanced to:

Image copy multiple database data sets (DBDSs) during a single execution of the utility.Accept the specification of database group names.Allow the user to specify the DFSMSdss option OPTIMIZE for better performance.Allow the user to specify a new option, SAMEDS, for creating multiple image copies in thesame output data set.Issue an image copy complete notification by group or database name.

For more information on Database Image Copy 2 enhancements, see 4.1, Database ImageCopy 2 enhancements on page 48.

1.2.3 HALDB enhancementsSeveral enhancements have been made for the usability of High Available Large Database(HALDB) feature. The enhancements listed here are also available for IMS Version 7 userthrough the service process. These enhancements include:

Enhanced and new DBRC batch commands for changing and deleting HALDBs andpartitions (See 1.2.1, Database Recovery Control (DBRC) enhancements on page 4 ).The ability to restrict the DL/I calls to a single partitionThe ability to bypass the creating of secondary index during the load processing

Restricting DL/I calls to a single partitionPrior this enhancement, all DL/I calls made against a database PCB were allowed to access

any partition in a multiple partition HALDB. This enhancement allows the user to indicate aparticular partition to which the DL/I calls are to be restricted in batch or a BMP. This can alsobe done for a secondary index which has multiple partitions, when that index is either beingaccessed as a database, or used with DL/I calls via PROCSEQ.

This is accomplished via a new HALDB control statement inputted through a new DD cardwith a ddname of DFSHALDB. This new DD card needs to be provided in the JCL for the IMSbatch job or Batch Message Processing dependent region. The syntax of the new controlstatement is:

HALDB PCB=(nnn,pppppppp)

In this statement: nnn = the nth DBPCB (required) and pppppppp = partition name (required).This enhancement is available also for IMS Version 7 users as an APAR PQ57313.

Bypassing the creation of secondary index during the load processingPrior this enhancement, for secondary indexes that are defined for a HALDB, the indexentries are always created during the initial load of the data base. This enhancement providesthe flexibility to bypass the creating of the secondary index during the load processing, andthen build it once the load has completed, thereby reducing the elapsed time that is requiredfor the load. A new parameter of BLDSNDX=YES or BLDSNDX=NO is added to theOPTIONS statement in the DFSVSAMP member for this. If BLDSNDX=YES is coded, or theparameter is omitted, then secondary index entries will be built during initial load. IfBLDSNDX=NO is coded then secondary index entries will not be built during initial load. Thisenhancement is available also for IMS Version 7 users as an APAR PQ55840.


25/355


1.2.4 Batch Resource Recovery Service (RRS) supportIMS batch programs can now use the operating system s Resource Recovery Service (RRS)to enable 2-phase commit processing. This support includes IMS DB, DB2 and MQSeriesresource managers.

For more information on the enhancements to batch Remote Recovery Service support, see4.4, Batch RRS support on page 61 .

1.2.5 Remote Site Recovery (RSR) enhancementThe IMS Remote Site Recovery (RSR) function has been enhanced to support coordinateddisaster recovery for IMS and DB2.

For more information on Remote Site Recovery enhancements, see 4.5, CoordinatedIMS/DB2 disaster recovery support on page 62 .

1.2.6 Enhanced availability by using the Resource Manager (RM)

For IMS Version 8, IMS Transaction Manager (TM) has been enhanced to use the newResource Manager (RM) to maintain IMS resource information in a sysplex environment. Byhaving the resource information available to other IMSs in the sysplex, the following isachievable:

Resume work for VTAM terminals and users if their local IMS failsEliminate VTAM generic resources terminal affinitiesProvide resource type consistencyProvide name uniquenessProvide global callable services for NODE, LTERM, and user resources

For more information on Resource Manager as part of the CSL architecture, see Chapter 13,Common Service Layer (CSL) architecture on page 155 .

For more detailed information on resource structures and Resource Manager seeChapter 14, Sysplex terminal management on page 177

For Resource Manager and CSL configuration information see Chapter 20, Common ServiceLayer configuration and operation on page 289.

1.2.7 Common Queue Server (CQS) enhancementsCQS has been enhanced to support the Resource Manager access to the new (optional)resource structure. Resource manager (RM) is a new address space introduced in IMSVersion 8 and uses the CQS to access a new Coupling Facility list structure called a resourcestructure to maintain global resource information for IMSplex resources.

The CQS is also exploiting the enhancements made available to Coupling Facility liststructures in the recent releases of OS/390 and z/OS. These enhancements include:

System managed rebuild of the structuresStructure alter and autoalterSystem managed duplexing of the structuresStructure full monitoring capability

In addition to the functional enhancements for IMS Version 8, the Common Queue Server(CQS) information is now in a separate book from that of BPE information. For IMS Version 8,you will find all the information pertaining to CQS in the IMS Version 8: Common QueueServer Guide and Reference, SC27-1292.


26/355


For more information on Coupling Facility structure processing see Chapter 10, CouplingFacility structure management on page 137 .

For more information on CQS as part of the CSL architecture, see Chapter 13, CommonService Layer (CSL) architecture on page 155 . For more detailed information on resourcestructures and Resource Manager see Chapter 14, Sysplex terminal management onpage 177

1.2.8 APPC and OTMA enhancementsPrior to IMS Version 8, implicit synchronous APPC and OTMA messages could only beprocessed by the front-end IMS in a shared queue environment. In IMS Version 8, all implicitAPPC and OTMA transactions are eligible for sysplex-wide processing.

For more information on APPC and OTMA enhancements, see Chapter 12, Shared queuessupport for APPC and OTMA synchronous messages on page 147 .

1.2.9 APPC/IMS enhancements

IMS Version 8 included several enhancements for the management of APPC/IMS resources:A new parameter (CPUTIME) has been added to the TP_Profile data set (which ismaintained by the operating system) to specify the number of CPU seconds that a CPI-Cprogram is allowed to run before being terminated. This limits the time that resources areheld due to a possible error in the program causing it to loop endlessly.

LU 6.2 descriptors can now be added or deleted dynamically using the /START and /DELETE commands.

The /CHANGE command has been enhanced to allow you to change the outbound LUusing the new OUTBND keyword.

New OUTBND= parameter has been added to IMS PROCLIB member DFSDCxxx.

For more information on the APPC/IMS enhancements, see Chapter 7, APPC baseenhancements on page 89 .

1.2.10 IMS Online Recovery Service (ORS) supportIMS Online Recovery Service (ORS) is a separately priced product which provides adatabase recovery process in an IMS online system. IMS dynamically allocates all of therequired data sets to perform the recovery. ORS utilizes IMS commands as opposed toDBRC commands and generated batch recovery job streams. The IMS online system uses adependent address space to restore the image copy and change accumulation files onto thedatabase(s). Once these have been processed, IMS ORS reads log data sets and passes arecovery stream to the IMS control region address space to update the databases.

ORS support has been enhanced in IMS Version 8, and the enhancements made available toIMS Version 7 through the service process. IMS ORS will accept image copy data setscreated by all releases of the IMS Database Image Copy 2 utility. ORS is now able to:

Process IC2 SAMEDS image copiesUtilize compressed image copies produced by IBM IMS Image Copy Extensions productUse virtual tape cachingSend messages to IMS MTO (requires IMS Version 8)

To learn more about Online Recovery Service, please see the IBM Redbook A DBA s View ofIMS Online Recovery Service , SG24-6112.


27/355


1.2.11 System Log Data Set (SLDS) dynamic backout processingWith IMS Version 8, the online system has the ability to read the system log data set (SLDS)for backout processing in the event required backout records are no longer available on theonline log data set (OLDS). Previous releases of IMS could only read the SLDS duringemergency restart. This enhancement is also being made available to IMS Version 7 throughthe service process.

If dynamic backout required a record that was only available on a SLDS, a backout failureoccurred and the user was required to run the batch backout utility. This was often the resultof the abend of a BMP which had run a very long time without taking a checkpoint. Recordsneeded for its backout were written to OLDS which were subsequently archived and reused.

With this enhancement, if a log record is needed for a dynamic backout and the log record isno longer available on an OLDS, IMS will dynamically allocate the required SLDSs. TheSLDSs are allocated in reverse time sequence. The most recent SLDS containing records nolonger available on an OLDS will be allocated first. IMS reads and saves the log records fromthis SLDS in a data space. If this SLDS does not contain all of the required records, additionalSLDSs are allocated, read, and saved. This continues until all required records have beenread.

This enhancement also applies to shared queues. If the message queue structure and itsoverflow structure becomes full, committed output messages are logged but not written to thestructures. These messages were created before the structures became full, but notcommitted until after the structure full condition occurred. If space in the structures isavailable at a later system checkpoint, these messages are written to the structures. It isnecessary to access log records to complete this. If the log records are no longer availablefrom the OLDS, IMS Version 8 will dynamically allocate the required SLDSs to acquire theneeded records.

Commands /START SLDSREAD and /STOP SLDSREAD have been added to enable anddisable the SLDS read function. When disabled, IMS acts as it did in prior releases.Disablement during use of the function will cause failure of the current read request andrejection of subsequent requests. Any outstanding mount request is aborted by abnormaltermination of the subtask that is used to open the SLDS and all dataspace storage isreleased. Externally, this results in DFS982I for backouts, for instance. /STOP isasynchronous, producing the 'command in progress' response.

The SLDS read function is disabled until restart completes and enabled thereafter until a /STOP command disables it again.

The output from the /DISPLAY OLDS command has been modified to indicate the state of theSLDS read function. The output will contain the string 'SLDSREAD ON' if the function isenabled or 'SLDSREAD OFF' otherwise. The new string will occur on the line after the WADSDDNAME list. Example 1-1 shows the DISPLAY command output with the SLDSREAD ON string.

Example 1-1 /DISPLAY OLDS -command output showing

SLDSREAD ON

DFS000I WADS = *DFSWADS0 DFSWADS1DFS000I SLDSREAD ON

Example 1-2 shows the messages that are issued when SLDS is required for backout.

Example 1-2 /DISPLAY OLDS -command output showing SLDS required for backout

DFS000I WADS = *DFSWADS0 DFSWADS1DFS000I SLDS REQUIRED FOR BACKOUT - RGN 00001, SLDSREAD ON


28/355


The interface to DBRC has been enhanced, allowing SLDS read to allocate the exact SLDSrequested on the first read request. Subsequent log allocations (within the same set ofrequests) will still need to be contiguous with previously allocated logs. This eliminates muchdataspace use when reads are for very old log data, which may happen if SLDS read isturned off until a time of less contention for storage. Turning SLDS read on later and issuing

/START DB to redrive backout will not cause IMS to read unnecessary log data between pointof failure and the current OLDS.

The DBRC enhancement added field SLDLBKID to the PRISLD record in the RECON dataset. SLDLBKID is not maintained by RSR, so the SLDS read function will not operatesuccessfully on log data migrated from a remote site by RSR. After a remote takeover,deferred or restartable backouts may require the Batch Backout utility.

1.3 Performance and capacity enhancementsAs usual with the new release of IMS, IMS Version 8 includes improvements also in the areaof performance. These improvements are provided for lowering the cost of processing a givenworkload, by internal improvements in IMS, and by exploitation of new system facilities.

Frequently this aspect of performance is measured in terms of cost to perform a givenfunction which may include both direct processing costs and indirect costs such as thetime and manpower needed to perform system, application and database maintenance.Additionally, IMS Version 8 continues to remove constraints and limitations on the capacitiesof an IMS system.

1.3.1 Fast Path enhancementsFast Path has been enhanced for IMS Version 8 as follows:

Shared VSO databases are also able to exploit the following Coupling Facility features:

System managed rebuild of a VSO structure. Automatic altering of a VSO structure size. System managed duplexing of VSO structures.

DEDBs can now have up to 2048 areas.

DEDBs can now be defined as nonrecoverable in DBRC.

IOVFI parameter in DFSPBxxx sets update interval for unused IOVF count.

For details on Fast Path enhancements applicable to all operating environments, see 4.3,Fast Path DEDB enhancements on page 56 .

For more information on Fast Path enhancements specific to Parallel Sysplex operations, seeChapter 10, Coupling Facility structure management on page 137 .

1.3.2 Parallel database processing enhancementIMS Database Manager now performs the tasks of database authorization, allocation, andopen and close processing in parallel using multiple OS/390 threads. For systems with alarge number of databases, this enhancement can reduce the amount of time required toreopen the databases during restart processing and return the system to a steady state.

For more information on parallel database processing enhancements, see 4.2, Paralleldatabase processing on page 54 .


29/355


1.3.3 IMS MSC FICON CTC supportThe multiple systems coupling (MSC) feature of IMS provides a reliable, high bandwidthhost-to-host communications between IMS systems. One choice for the physical host-to-hostconnection is to define the MSC to utilize the channel-to-channel (CTC) hardware support.

On z/Series 900 processors, CTC bandwidth can be enhanced by implementing the S/390Fiber Connection (FICON) channel support for CTCs. This FICON support could besignificantly faster than the Enterprise System Connection (ESCON) support for large blocksof data transferred. It is estimated that one FICON CHPID can do the work of a number ofESCON CHPIDs. This increased bandwidth is the result of faster data transfer rates, I/Orates, and CCW and data pipelining. The distance between hosts can also be increased.

The IMS MSC FICON CTC support increases the volume of IMS messages that can be sentbetween IMS systems when using the IMS MSC facility. This enhancement is activated bychanging the IMS online procedure so that the DD cards specifying the CTC address for thelink specify the CTC FICON address. No changes are needed to the IMS system definition toconvert existing CTC links to FICON. z/OS Version 1 Release 2 is needed for IMS MSCFICON CTC support. This capability is also enabled for IMS Version 7 by APAR PQ51769.

1.3.4 Virtual storage constraint reliefIn order to relieve common system area (CSA) and private (PVT) virtual storage constraints,IMS Version 8 is using less private and common storage below the 16 MB line. The systemProgram Specification Tables (PSTs) and other IMS modules and control blocks have beenmoved to private and common storage above the 16 MB line.

Reducing CSA utilization and providing virtual storage constraint relief (VSCR) freesadditional storage below the 16MB line for user applications and vendor program productsthat run in the same system as IMS. Additionally, CSA VSCR enables single-system growthand the capability to add additional IMS systems to the operating system environment.

VSCR has been provided in the following areas:

Checkpoint Processor (DFSRCP00) load module has been moved above the 16MB line.

Restart Processor (DFSRCP00) load module has been moved above the 16MB line.

Fast Database Recovery (FDBR) modules were moved from CSA to private storage, orfrom extended CSA to extended private storage. The CSA/ECSA storage relief is receivedfor each FDBR product on the system.

LPST pools (PSTs for IMS internal use in private storage) have been moved above the16MB line.

QSAV areas were moved from CSA to Extended CSA (ECSA).

Asynchronous Work Elements (AWEs) were moved from CSA to ECSA.

A portion of each log buffer prefix located in CSA was moved to ECSA. The followingformula can be used to calculate the total number of bytes of log buffer prefixes movedfrom CSA to ECSA:

The number of log buffers (BUFFNO= specification on the OLDSDEF statement ofDFSVSMxx member) times 176 (BUFFNO * 176).

If using dual logging, this result is the number of log buffers multiplied by 352.

Table 1-1 summarizes the estimated virtual storage constraint relief provided in IMS Version8.


30/355


Table 1-1 Estimated virtual storage constraint relief provided by IMS Version 8

1.4 Systems management enhancementsAs IMS systems are joined together into sharing groups (sharing databases, networkresources, or message queues) in a sysplex environment, system management becomesmore complex. Prior to IMS Version 8, the IMSs that were in sharing groups had to bemanaged individually. IMS Version 8 builds upon the idea of an IMS sysplex (known hereafteras an IMSplex) to help reduce the complexity of managing multiple IMSs in a sysplexenvironment.

An IMSplex can be defined as one or more IMS address spaces (control, manager, or server)that work together as a unit. Typically (but not always), these address spaces:

Share either databases or network resources or message queues (or any combination)Run in a S/390 sysplex environmentInclude an IMS Common Service Layer (CSL - new for IMS Version 8)

Note: The QSAV and AWE storage pools can expand during high volume processing.Thus, the CSA saving shown in the following table is a minimum value of 8K (for QSAV)and 12K (for AWE) per IMS subsystem. During high volume processing, these pools couldbe significantly expanded, resulting in exhausting CSA and causing problems. By movingthese areas above the line the CSA problems may be avoided, thereby helping preventoperating system crashes. So while the base system with no activity saves 8K and 12K,the actual savings in the previously described situation, would be more.

Item Moved fromCSA toPrivate

Moved from CSA toECSA

Moved fromECSA toEprivate

Moved fromPrivate toEprivate

Checkpoint processor 54 KB

Restart processor 286 KB

FDBR modules 378 KB 420 KB

LPSTs (per IMS) 12 KBQSAV areas (per IMS) 8 KB

System PSTs for a DB/DCFP generated system- or -System PSTs for a DB/DCsystem without FP

92 KB- or -28 KB

AWEs 12 KB

Part of each IMS logbuffer prefix

176 bytes per logbuffer, 352 bytes if duallogging

Total 378 KB 112 KB (with FP) or48 KB (without FP)+172 * BUFFNO (singlelogging) or352 * BUFFNO (duallogging)

420 KB 352 KB


31/355


The address spaces that can participate in the IMSplex are:

Control region address spaces (CTL and DBRC)

CSL address spaces (Operations Manager (OM), Resource Manager (RM), StructuredCall Interface (SCI))

IMS server address spaces (CQS)

Batch and utility regions using DBRCAutomated operator programs and SPOCs

Address spaces that serves as an interface between IMS and a protocol that is not directlysupported by IMS (for example, TCP/IP)

Examples of IMSplexes are:

A set of IMS control regions at the Version 6, 7 or 8 level without a CSL that are sharingdata or sharing message queues

A set of IMS control regions at the Version 8 level with a CSL that are sharing data orsharing message queues

A single IMS control region at the Version 8 level with a CSL. This still qualifies as anIMSplex because it is a set of IMS address spaces (IMS control, CQS, SCI, OM, RM)working together.

To support IMSplexes, a number of IMS functions have been enhanced and a number of newfunctions have been added.

The Base Primitive Environment (BPE) has been enhanced.

The Common Queue Server (CQS) has been enhanced.

A new component, the Common Service Layer (CSL), is introduced consisting of thefollowing three new address spaces:

Operations Manager (OM) Resource Manager (RM) Structured Call Interface (SCI)Optional Resource Structure.

A TSO-based single point of control (SPOC) application program and a REXX API isshipped with IMS Version 8.

The IMS terminal management function of IMS TM has been enhanced.

A new coordinated

Date post:	02-Jun-2018
Category:	Documents
Upload:	subramaniam-kumar
View:	230 times
Download:	0 times

IMS Installation Guide 8

Documents