Xpediter/xchange Installation And User Guide

Transcript

Xpediter/Xchange Installation and User Guide Release 17.02 ii Xpediter/Xchange Installation and User Guide Please direct questions about Xpediter/Xchange or comments on this document to: Compuware Customer Support https://go.compuware.com/ This document and the product referenced in it are subject to the following legends: Copyright 1995 - 2017 Compuware Corporation. All rights reserved. Unpublished rights reserved under the Copyright Laws of the United States. U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Compuware Corporation license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. Compuware Corporation. This product contains confidential information and trade secrets of Compuware Corporation. Use, disclosure, or reproduction is prohibited without the prior express written permission of Compuware Corporation. Access is limited to authorized users. Use of this product is subject to the terms and conditions of the user’s License Agreement with Compuware Corporation. Xchange, Xpediter, and FrontLine are trademarks or registered trademarks of Compuware Corporation. CICS, CICS TS, DB2, IBM, IMS, MVS, MVS/ESA, OS/390, RACF, VTAM, and z/OS are trademarks or registered trademarks of International Business Machines Corporation. Adobe® Reader® is a trademark of Adobe Systems Incorporated in the United States and/or other countries. All other company and product names are trademarks or registered trademarks of their respective owners. Doc. APR2017 March 31, 2017 iii Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Who Should Read this Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Manual Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Notation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Accessibility Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Selecting Font and Font Size in the Emulator. . . . . . . . . . . . . . . . . . . . . . . . x Changing Color and Contrast. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Special Considerations When Using a Screen Reader. . . . . . . . . . . . . . . . . . x Exceptions and Work-Arounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Known Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Work-Arounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Compuware FrontLine Customer Support Website . . . . . . . . . . . . . . . . . . . xi Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Corporate Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Information for Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Chapter 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 What is Xpediter/Xchange?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1 System Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Installation of Enterprise Common Components . . . . . . . . . . . . . . . . . . . . . . . 1-3 License Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3 Compuware Mainframe Services Controller (CMSC) . . . . . . . . . . . . . . . . . . . . 1-4 Installation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Product Delivery Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Receive From Network (RFN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Extended Play (EP) Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 SMP/E Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 SMP/E Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Xpediter/Xchange Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5 Libraries Created During SMP/E Installation . . . . . . . . . . . . . . . . . . . . . . . 1-5 Preinstallation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Ensure Specific MVS System Commands Run . . . . . . . . . . . . . . . . . . . . . . 1-6 Collect Site-specific System Information . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Determine DASD Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Review Upgrade Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Designate an APF Authorized Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Update the MVS Program Properties Table . . . . . . . . . . . . . . . . . . . . . . . . .1-9 PARMLIB Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 PARMLIB Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 General Guidelines for PARMLIB Members . . . . . . . . . . . . . . . . . . . . . . . 1-10 General Guidelines for PARMLIB Dataset . . . . . . . . . . . . . . . . . . . . . 1-11 PARMLIB Product Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12 Step 1. Copy Sample PARMLIB Members . . . . . . . . . . . . . . . . . . . . . . . . . 1-12 iv Xpediter/Xchange Installation and User Guide Step 2. Update the CMSC with PARMLIB Information . . . . . . . . . . . . . . 1-12 Chapter 2. Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Chapter 3. Configuring Xchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Configure Xpediter/Xchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 How NUM Options Affect Xchange Use. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Step 1. Specify Xchange Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Optional Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Step 2. Perform CMSC REFRESH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12 Step 3. Assemble and Link the RACROUTE Module . . . . . . . . . . . . . . . . 3-12 Step 4. Update TSO CLISTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12 Step 5. Allocate the Journal Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13 Step 6. Allocate the Save/Restore Dataset . . . . . . . . . . . . . . . . . . . . . . . . 3-14 Step 7. Enable CICS Transaction Support . . . . . . . . . . . . . . . . . . . . . . . . 3-15 Step 8. Enable CICS Region Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18 Using STCKSYNC Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18 PLT Initialization for CICS TS 4.1 and Above . . . . . . . . . . . . . . . . . 3-18 Enable Midnight Rollover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18 Enable Language Environment (LE) . . . . . . . . . . . . . . . . . . . . . . . . 3-19 Step 9. Enable DB2 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19 Applying the DB2 Zap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20 Enable Language Environment (LE) for DB2 Support . . . . . . . . . . . 3-20 Step 10. Enable IMS Message Level Support . . . . . . . . . . . . . . . . . . . . . . 3-21 Step 11. Enable Enterprise PL/I DATE or DATETIME Built-in Function Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24 Enterprise PL/I DATE Built-in Function Support . . . . . . . . . . . . . . . 3-24 Enterprise PL/I DATETIME Built-in Function Support . . . . . . . . . . 3-24 Step 12. Enable C time() Function Support . . . . . . . . . . . . . . . . . . . . . . . 3-25 Step 13. Enable Natural Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25 Step 14. Configure Xchange External Security . . . . . . . . . . . . . . . . . . . . . 3-26 Defining Security Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26 Step 15. Update the Xpediter/TSO LIBDEF . . . . . . . . . . . . . . . . . . . . . . . 3-30 Step 16. Assemble a Journal Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30 Step 17. Assemble or Compile and Link Edit Test Programs . . . . . . . . . . 3-31 CICS Transaction Support Test Programs. . . . . . . . . . . . . . . . . . . . . 3-31 IMS Message Level Support Test Programs. . . . . . . . . . . . . . . . . . . . 3-32 Chapter 4. Starting and Terminating Xchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting Xchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting Xchange as a Batch Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting Xchange as a Started Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Xchange SVC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminating Xchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminating Xchange From the Operator Console . . . . . . . . . . . . . . . . . . Terminating Xchange From the Batch Facility. . . . . . . . . . . . . . . . . . . . . . 4-1 4-1 4-1 4-3 4-3 4-4 4-4 4-5 Chapter 5. Using Xchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Xchange Criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CICS Transaction Support Criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DB2 Distributed Data Facility (DDF) Support Criteria . . . . . . . . . . . . . . . Using the ISPF Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invoking the ISPF Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subsystem Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying Requests in ISPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 5-1 5-1 5-2 5-2 5-3 5-3 5-3 5-4 5-5 v Status Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 PF Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Primary Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10 Creating an Xchange Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12 Using the ISPF Interface with Date/Time Offset . . . . . . . . . . . . . . . . . . . . 5-13 Constants Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Advancing Xchange Requests Using the ISPF Interface . . . . . . . . . . . . . . . 5-15 Line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16 Example of Advancing the Requested Date and Time or Offset of Existing Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16 Using Jobclass Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19 Primary Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20 Line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20 Status Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21 Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21 PF Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22 Additional Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22 Using Jobclass Support with Date/Time Offset . . . . . . . . . . . . . . . . . . . . . 5-22 Constants Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23 Using DB2 Distributed Data Facility (DDF) Support. . . . . . . . . . . . . . . . . 5-24 DB2 DDF Request Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-25 Using the Batch Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27 Implementing the Input Dataset Feature of the Batch Facility . . . . . . . .5-30 JCL and Dataset Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-30 Coding the Parameter List for the XGPARMDS Dataset . . . . . . . . . . 5-30 Example Batch Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31 Automatically Deleting Xchange Batch Requests (Optional) . . . . . . . . . . 5-32 Using IMS Message Level Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-32 Xchange IMS Transaction IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-32 Specifying Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33 Primary Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33 Line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35 Status Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36 Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36 PF Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38 Comparison of Request Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38 Using IMS Message Level Support with Date/Time Offset . . . . . . . . . . . . 5-38 Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39 Advancing Xchange Requests Using IMS Message Level Support . . . . . . . 5-40 Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40 Example Advancing IMS Message Level Support Requests . . . . . . . . 5-41 Using the Extended Batch Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43 Modify and Run JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43 Sequential File Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43 Extended Batch Facility Sample Reports . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45 Using CICS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-51 CICS Region Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51 Using Language Environment (LE) with Xchange CICS Region Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51 Enabling Region Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51 CICS Transaction Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52 Using CICS Transaction Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52 Using CICS Transaction Support with Date/Time Offset . . . . . . . . . 5-60 Advancing Xchange Requests Using CICS Transaction Support . . . . 5-62 vi Xpediter/Xchange Installation and User Guide Using CICS Transaction Support with Input from a PDS or PDSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Xpediter/TSO Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Simulated Date Time Settings Screen . . . . . . . . . . . . . . . . . . . Entering Xchange Requests on the Xpediter/TSO COMMAND Line. . . . Xchange Date/Time Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Xchange Date/Time Offset Requests . . . . . . . . . . . . . . . . . . . . . . . . . Using Standard STCK and STCKF and Enhanced STCK, STCKE, and STCKF Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard STCK and STCKF Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced STCK Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced STCKE Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced STCKF Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66 5-67 5-68 5-68 5-68 5-68 5-69 5-69 5-70 5-71 5-73 Chapter 6. Using the Xchange Journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Closing or Swapping the Journal Dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Closing or Swapping From the Operator Console. . . . . . . . . . . . . . . . . . . Closing or Swapping From the Batch Facility . . . . . . . . . . . . . . . . . . . . . . Online Journal Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing Activity Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simulation Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CICS Transaction Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity Report JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Journal Extract. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Note to REXX Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Journal Dump Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 6-1 6-1 6-2 6-2 6-3 6-4 6-5 6-5 6-5 6-6 6-6 6-7 6-7 6-9 6-9 Chapter 7. Using the Xchange Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XGFNDMOD Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running XGFNDMOD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XGFNDMOD Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XGSUBRST Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running XGSUBRST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 7-1 7-1 7-2 7-2 7-3 Appendix A. Xchange Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 Owner Field Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 IMS Message Level Support Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 XGIM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 MVS Console Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7 Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-22 CICS Abend Codes and Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-27 Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-27 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-28 Xchange Parsing Exit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-30 Appendix B. Using Xchange Internal Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating the Trace Dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Execution Procedure and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capturing Diagnostic Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 B-1 B-1 B-2 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1 vii Introduction Intro Although installation is now documented in the Compuware Installer Compuware Product SMP/E Installation Guide, this manual is the single source of detailed information about configuring and using Xpediter/Xchange. It contains reference and task-oriented information, syntax diagrams, and step-by-step procedures. We have tried to make this manual as comprehensive as possible. CAUTION: Rolling back the date on a software product may be a violation of your licensing agreement. You should review the terms of your license agreement and/or contact the software licensor before attempting to roll back any dates. Xpediter/Xchange is not intended to be used in any manner which will violate your license agreement with another software licensor. Who Should Read this Manual This manual is written for individuals and groups responsible for the following tasks: • Installing and configuring Xchange and its components • Starting the product • Using the product to simulate date/time scenarios. Manual Organization This manual consists of the following chapters and appendixes: Chapter 1, “Overview”: Provides an overview of Xchange functions, interfaces, and capabilities. Chapter 2, “Checklist”: Convenient hyperlinked list of primary configuration steps. Chapter 3, “Configuring Xchange”: Provides step-by-step instructions for installing Xchange, including detailed explanations of each step. Chapter 4, “Starting and Terminating Xchange”: Explains how to execute Xchange using two methods: batch and started task. It also describes how to shut down Xchange. Chapter 5, “Using Xchange”: Describes Xchange’s ISPF, batch, and Xpediter/TSO interfaces, as well as use with Assembler STCK, STCKE, and STCKF instructions. IMS Message Level Support and CICS region and transaction support are also explained. The Xchange Extended Batch Facility is also described. Chapter 6, “Using the Xchange Journal”: Discusses the Xchange journal dataset. It describes how to change the types of records written to the journal and how to view or extract the contents of the journal. Chapter 7, “Using the Xchange Utilities”: Explains how to use the Xchange XGFNDMOD and XGSUBRST utilities. Appendix A, “Xchange Messages”: Presents messages you may encounter as well as recommended actions to take. viii Xpediter/Xchange Installation and User Guide Appendix B, “Using Xchange Internal Diagnostics”: Explains how to set up and utilize Xchange’s built-in diagnostic capabilities. Notation Rules Syntax diagrams define primary command syntax. A parameter is either a keyword or a variable. All KEYWORDs are shown in uppercase characters and must be spelled exactly as shown. You cannot substitute another value. If any part of a KEYWORD is shown in lowercase characters, that part is optional. Variables are user-specified values and are printed in lowercase italics. For example, dataset-name indicates you are to substitute a value. The syntax for commands is described in diagrams that help you visualize parameter use. The following example shows a command and a parameter: Read the diagrams from left to right and from top to bottom. These symbols help you follow the path of the syntax: indicates the beginning of a statement. indicates the statement is continued on the next line. indicates the statement is continued from the previous line. indicates the end of a statement. Required parameters appear on the horizontal line (the main path). Optional parameters appear below the main path. Default parameters appear above the main path and are optional. The command executes the same regardless of whether the default parameter is included. Vertically stacked parameters are mutually exclusive. If you must choose a parameter, one item of the stack appears on the main path. If the parameters are optional, the entire stack appears below the main path. If a parameter in a stack is the default, it appears above the main path. Introduction ix If the same parameters are used with several commands, their syntax may be documented in a separate diagram. In the command syntax, these common parameters are indicated with separators before and after the parameter name. An arrow returning to the left indicates a repeatable item. If the arrow contains a comma, separate the repeated items with a comma. Related Publications An RFN order e-mail also includes a copy of the Compuware Installer Compuware Product SMP/E Installation Guide, which should be used to perform the installation of Xpediter/Xchange. Preparation for installation and post-installation configuration should be done according to this Guide. The Xpediter/Xchange Installation and User Guide is the only manual in the Xpediter/Xchange document set. There are, however, other sources of information that may interest you. Online Documentation The Xpediter/Xchange product installation package does not include the product documentation. Access the Xpediter/Xchange documentation from the Compuware FrontLine customer support website at https://go.compuware.com in the following electronic formats: • • • • Release Notes in HTML format Product manuals in PDF format Adobe PDF index file (PDX file) Product manuals in HTML format. The product documentation is available for viewing or downloading: • View PDF files with the free Adobe Reader, available at http://www.adobe.com. • View HTML files with any standard web browser. Accessibility Information Compuware is committed to making its products and services easier for everyone to use. This section provides information about the features that make Xpediter/Xchange more accessible for people with disabilities. This section also applies to Xchange’s features and components, such as System Flow reporting. Xpediter/Xchange is a mainframe application designed to run on IBM's OS/390 or z/OS operating systems, utilizing IBM’s ISPF on IBM 327x-type terminals. This platform offers few if any accessibility features in the mainframe environment referenced above. Due to this fact, Compuware Corporation has focused its attention in regard to the accessibility of its mainframe products in the area of emulated 3270 sessions on personal computers (PCs) with Windows 98 or higher operating systems. Xpediter/Xchange supports and/or does not disrupt, with few exceptions, Windows accessibility features and Windowsbased Assistive Technology (AT) devices and software such as Braille devices, screen readers, and magnifiers. x Xpediter/Xchange Installation and User Guide Note: Xpediter/Xchange is a mainframe system development tool intended for use by mainframe systems software developers/programmers. Much of the input and output used and produced by Xchange, such as program execution statistics, are not easily understood by the general public, nor are they intended to be. Unfortunately, as in the case of Xchange reports, data/information in these formats by its very nature can be confusing to screen readers, and therefore to those who use them as well. Effective use of this application requires the specialized knowledge of a mainframe systems software developer/programmer. Selecting Font and Font Size in the Emulator This option is particularly useful for people with low vision. By default, dialog boxes and tool windows in the emulator window should use the same font as the Icon font used by the operating system. The color settings for dialogs and tool windows should also match the defaults used by the operating system. Text can also be manipulated within the emulator window to meet individual needs via the selection of font and/or font size settings. Changing Color and Contrast Xpediter/Xchange inherits color and contrast settings from the emulator or ISPF. Selecting color/contrast settings in the emulator or ISPF to provide appropriate highlighting can assist people with low vision. For more information, see the emulator or ISPF documentation or help. Special Considerations When Using a Screen Reader Xchange’s accessibility was evaluated using Freedom Scientific JAWS for Windows version 10.0 screen reader and Attachmate EXTRA! Personal Client Version 6.5 in addition to Windows accessibility features. When using a screen reader such as JAWS, select the following emulator settings for enhanced compatibility: • A plain font (such as Lucida, Courier New, Times Roman, etc.) • A font size of 10 points or smaller (especially if JAWS is used) • A blinking cursor with the fastest blink rate possible (especially if JAWS is used). Enhanced accessibility can be gained by customizing your screen reader for your emulator. This can be done using frames and custom script files for your emulator when using JAWS. Different emulator/screen reader combinations can present differing compatibility issues. Consult your screen reader’s documentation, help, or technical support for more information. Exceptions and Work-Arounds Known Exceptions During Xchange’s accessibility evaluation, some exceptions were found in which some accessibility features or assistive technology were not fully supported. These exceptions are currently under investigation by Compuware Corporation and include: • Function key (PF key) information at the bottom of a screen is not read by the screen reader on some screens. This is believed to be caused by an external interface. See “Work-Arounds” below. • Some system error and warning messages are not read by the screen reader when issued. This is believed to be caused by an external interface. See “Work-Arounds” below. Introduction xi • Some system error and warning messages are not accompanied by audio alerts when issued, however they are read by the screen reader. This is believed to be caused by an external interface. Currently, no solution is available. • Some pop-up screens and/or drop-down menus do not capture exclusive focus and are not read correctly by the screen reader. This is believed to be caused by an external interface. Currently, no solution is available. • System error and warning messages do not the capture visual focus of a screen magnifier. This is believed to be caused by an external interface. Currently, no solution is available. • Some entry and display fields lack individual labels, and when entry fields are accessed via the Tab key, the entire individual line is read. Work-Arounds • When the screen reader fails to read the PF key information upon entry to a new screen, cursor down using the arrow keys to the line(s) with the PF key information. Allow the screen reader to read each line as it is cursored to, or press the Page Up key for the screen reader to reread the entire screen. • When the screen reader fails to read an error or warning message (an audio alert will occur if enabled on your system), cursor up the screen to the line containing the error message (usually on the top/title line). Allow the screen reader to read the line and its error message individually. Customer Support Compuware provides a variety of support resources to make it easy for you to find the information you need. Compuware FrontLine Customer Support Website You can access online information for Compuware products via our FrontLine customer support website at https://go.compuware.com. Compuware FrontLine provides access to critical information about your Compuware products. You can review frequently asked questions, read or download documentation, access product fixes, or e-mail your questions or comments. The first time you access Compuware FrontLine, you are required to register and obtain a password. Registration is free. Contacting Customer Support Phone • USA and Canada: 1-800-538-7822 or 1-313-227-5444. • All other countries: Contact your local Compuware office. Contact information is available at https://go.compuware.com. Web You can report issues via the Quick Link Create & View Support Cases on the Compuware FrontLine home page. Note: Please report all high-priority issues by telephone. xii Xpediter/Xchange Installation and User Guide Mail Compuware Customer Support Compuware Corporation One Campus Martius Detroit, MI 48226-5099 Corporate Website To access Compuware’s site on the Web, go to http://www.compuware.com. The Compuware site provides a variety of product and support information. Information for Customer Support If problems arise, please check your manual for assistance. Additional information is available on Compuware’s FrontLine website at http://go.compuware.com. If problems persist, before calling Compuware’s 24-hour Customer Support Hotline, please obtain the following information: 1. Identify the release number of Xchange and the operating system being used. 2. If an abend occurs, note the displacement and the module in which it occurs. If possible, obtain a copy of the system dump. 3. Note the sequence of issued transactions or commands that resulted in the problem, and the data type involved. 4. Xchange produces a comprehensive journal that includes, among other data, diagnostic information about the internal processing of Xchange itself. Be prepared to transmit a copy of the journal that was active at the time of the problem. 1-1 Chapter 1. Overview Chap 1 With all the date and time dependencies in modern applications — even after the year 2000 has come and gone — many in the data processing community still face a distinct challenge. Even programs with a four digit year in their date format (MM/DD/YYYY) require time-dependent testing to verify functions such as month-end and leap year processing. Inadequate and untested code can lead to invalid results for comparison, subtraction, division, and sorting routines. Because so many application programs have required so many modifications over the past few years, an incredible amount of testing needs to be done. But how do you simulate a specific date and time for some programs without affecting all the rest? Compuware’s Xpediter/Xchange serves as the perfect tool to automate application date and time testing. What is Xpediter/Xchange? Xpediter/Xchange is a sophisticated tool for moving your time-sensitive applications into the year 2000 and beyond. By using Xchange, you’ll be prepared to address the potentially costly impact that improper date and time manipulations can have on your applications. Xchange automates date and time testing in your applications. You can build an inventory of all applications that make system date and time requests, and then test those applications using different dates and times. You can simulate century date changes, month-end and leap year processing, and a variety of other exception conditions on a job-by-job, program-by-program, or application group basis. Use Xchange to test different dates for any program without dedicating a separate system or affecting other jobs that are running simultaneously. You can set the values for the date and time you want to simulate. Then, Xchange will substitute, or exchange, this value each time the programs you specify request the system date and time with a TIME macro, EXEC CICS ASKTIME, STCK, STCKE, or STCKF instruction, or DB2 call. You can tell by looking at the results of your application whether it handled the date change in an appropriate manner. If not, just make the necessary changes and test again using Xchange. System Environment Xpediter/Xchange Release 17.02 supports the following environments: • • • • • z/OS Release 1.4 and above ISPF/PDF Release 3.5 and above CICS/TS 3.1 and above IMS Release 10.1 and above DB2 Release 8.1 and above. Xchange supports any language that uses a TIME macro, EXEC CICS ASKTIME, EIB date and time, or a DB2 call to retrieve date and time requests. Some of these languages are: • COBOL and Enterprise COBOL • COBOL II 1-2 Xpediter/Xchange Installation and User Guide • • • • COBOL/370 PL/I and Enterprise PL/I C/370, C/C++ MVS (excluding native language services), and z/OS XL C Assembler (including STCK, STCKE, and STCKF instructions when replaced with Xchange macro). Features In addition to the new release features described in the Xpediter/Xchange Release Notes, Xchange continues to include the following features: • Save and Restore of Xchange Requests. All your date and time simulation requests are now saved at user-specified intervals and automatically restored whenever Xchange is restarted. • Jobclass Requests and Exclusions. Now you can exchange dates and times for all jobs running under a specified jobclass. A new Xchange parameter allows you to designate the jobclasses under which date and time exchanges are to be allowed. • UserID and Asynchronous Task CICS Requests. Xchange requests can now be set by CICS userID, and a single request can be used to specify both userID and asynchronous tasks. • ISPF Interface. Xchange’s ISPF interface lets you enter time simulation requests for jobs, steps, procedure steps, and programs. The interface consists of a screen that allows you specify individual entries or use a wildcard feature to specify multiple jobs, steps, procedure steps, and program names. • Batch Facility. By inserting an Xchange batch step in your JCL, you can modify system date and time requests in batch for your application. • Xpediter/TSO Interface. Users of Xpediter/TSO can dynamically request Xchange to set a simulated date and time for programs they are testing. Xchange is simply invoked from the COMMAND line of the Xpediter/TSO Source screen, allowing thorough and immediate testing of the program’s date and time logic. • Xchange Journal. Xchange’s journal provides a comprehensive record of system date and time requests that have been exchanged. You can access the journal online or print an activity report. • Security. Xchange works within the confines of your existing external security system to ensure that unauthorized access is not granted to any programs. Before an Xchange request is activated, external security validates the authorization of the request originator. • CICS Transaction Support. Xchange uses its CICS transaction feature to exchange the date and time for individual programs, terminals, and transactions within a CICS region. • Language Environment Support. Xchange fully supports LE’s common execution environment for the following IBM high-level language (HLL) products: – – – – – – – Enterprise COBOL COBOL/370 COBOL for MVS & VM PL/I for MVS & VM Enterprise PL/I C/370, C/C++ MVS (excluding native language services), and z/OS XL C Language Environment-conforming Assembler • DB2 Support. Dates and times returned by DB2 calls are exchanged. Xchange intercepts every DB2 date or time request but changes the date or time only when a match is found with one of your Xchange requests. Overview 1-3 • IMS Message Level Support. Xchange uses its IMS Message Level feature to exchange the date and time for individual programs within an IMS message region. • Support for LINKAGE=SYS. In addition to the LINKAGE=SVC parameter, Xchange also supports the TIME macro parameter LINKAGE=SYS. • STCK Support. Xchange supports the Store Clock (STCK) operation code used by many Assembler programs to store the current value of the CPU time-of-day clock. This support is augmented by Enhanced STCK Support beginning with Release 3.1. • STCKE Support. Xchange supports the Store Clock Extended (STCKE) operation code used by newer Assembler programs to store the current value of the extended CPU time-of-day clock. This support is augmented by Enhanced STCKE Support. • STCKF Support. Xchange supports the Store Clock Fast (STCKF) operation code used by some Assembler programs to store the current value of the CPU time-of-day clock. This support is augmented by Enhanced STCKF Support. • Journal Exit. When a journal record is written for a date or time exchange, Xchange can invoke a journal exit that determines the program ID to be reported. Installation of Enterprise Common Components Installation of Enterprise Common Components (ECC) libraries is a required part of the Xpediter/Xchange installation process. The most current release of ECC is provided in SMP/E installation format on separate media. A copy of the most current version of the Enterprise Common Components Installation and Customization Guide is included on the ECC media. If you do not have your copy and are a registered user of Compuware Go support website (http://go.compuware.com), you can download a copy from there. Follow the instructions in the Enterprise Common Components Installation and Customization Guide and perform all the procedures applicable to Xpediter/Xchange to install Enterprise Common Components. License Management System Compuware provides the License Management System (LMS) to help manage access to Compuware’s products at your site. The LMS includes several components that together allow you to establish, maintain, diagnose, and upgrade access to the Compuware products licensed by your enterprise. Install LMS from the Enterprise Common Components (ECC) installation media. Separately, via e-mail you receive License Certificate(s) for the Compuware product(s) you are licensed for. IMPORTANT: Xpediter/Xchange operation requires these steps: 1. Ensure that the Compuware License Management System has been installed from the ECC installation media. Refer to the Compuware Enterprise Common Components Installation and Customization Guide for installation procedures. This step is only necessary for a first-time install of LMS or when upgrading the License Management System itself. 2. Import the License Certificate into your License File. 3. Establish and update the Runtime License Management System by running the program LMSINIT. Refer to the “License Certificate Import Checklist” section in the Compuware License Management User/Reference Guide for detailed instructions. 1-4 Xpediter/Xchange Installation and User Guide Compuware Mainframe Services Controller (CMSC) Compuware provides the Compuware Mainframe Services Controller (CMSC) facility to centralize common parameter library services. This facility will replace the options specified in previous releases in the Configuration Module and the parameters specified at Xchange startup. Xpediter/Xchange operation requires the installation of the CMSC from the Enterprise Common Components (ECC) installation media. Refer to the Enterprise Common Components Installation and Customization Guide for detailed instructions. Installation Considerations Product Delivery Options Compuware has made the following product delivery options available: • Receive From Network (RFN) • Extended Play (EP) media on DVD or electronic FTP download. Receive From Network (RFN) The Receive From Network (RFN) process enables you to receive the product directly to your z/OS environment and install it using System Modification Program Extended (SMP/E). After completing your product order from Compuware’s online ordering system, you receive an e-mail message containing sample JCL to FTP the Compuware Installer which has been customized to include installation information of your current order. Your order e-mail also includes a copy of the Compuware Installer Mainframe Products SMP/E Installation Guide (CompuwareInstaller.pdf). The e-mail may also contain links for downloading any PC-based products that may have been ordered at the same time. Note: For the RFN process, always use the customized Compuware Installer dialog PDS that you receive with your current order. The Compuware Installer is used to generate the JCL for SMP/E processing of your Compuware mainframe products, including the Receive From Network step which FTPs the binary data from the Compuware FTP site directly to your z/OS Environment. Extended Play (EP) Media Xpediter/Xchange can also be delivered as part of an installation media (DVD) or electronic FTP download. Information on the Product Media Label When Xchange is delivered as part of the Xpediter installation media, some of the label information applies to installation capability, as noted below: This DVD contains: List of the included Xpediter products identifying each product’s name and release number. Security: Minimum level of Compuware’s License Management System required. Created on: The Xpediter installation media label shows when it was made. Compare this creation date with any maintenance posted on the Compuware Go customer support website at http://go.compuware.com. Overview 1-5 If additional maintenance has become available since the date on the installation DVD, either download the maintenance from the Compuware Go customer support website, or call Xpediter/Xchange Customer Support to request a new installation media with the current maintenance. SMP/E Installation Follow the procedures as described in the Compuware Installer Mainframe Products SMP/E Installation Guide. After the successful SMP/E installation, continue with the product configuration as described in Chapter 3, “Configuring Xchange”. SMP/E Maintenance Compuware recommends that you periodically obtain and apply maintenance to keep your product version current. All maintenance for Xpediter/Xchange and each of its releases is provided on the Compuware Go (FrontLine) customer support website at http://go.compuware.com. Locate the Fixes and Downloads section for the Xpediter/Xchange product and select the release for which you wish to apply maintenance. Follow the instructions on the website for acquiring the maintenance. Optionally you may acquire maintenance by getting a current copy of the Xpediter EP media and using it to generate the JCL for applying maintenance via SMP/E. To install the Xpediter/Xchange maintenance to an existing installation, perform the steps described in Chapter 3, “Apply Maintenance with SMP/E” of the Compuware Installer Mainframe Products SMP/E Installation Guide. Xpediter/Xchange Packaging Compuware has registered the following element prefixes with IBM for the Xpediter/Xchange components: • LXG for Xpediter/Xchange • KCW as a generic Compuware prefix The FMID for Xpediter/Xchange is MLXGnnn, where nnn is the release number code, for example MLXG170. Libraries Created During SMP/E Installation Table 1-1 lists the libraries created during the Xpediter/Xchange installation using SMP/E, where nnn is the release number code, for example CPWR.MLXG170.DZONE.CSI. Table 1-1. Libraries Created During Installation with SMP/E ddname Library Type and Content Dataset Name as Distributed SMPCSI Compuware Global CSI CPWR.GLOBAL.CSI SMPLOG Compuware SMP/E System File CPWR.GLOBAL.SMPLOG SMPPTS Compuware SMP/E System File CPWR.GLOBAL.SMPPTS MXGnnnD Base Distribution Zone CPWR.MLXGnnn.DZONE.CSI MXGnnnT Base Target Zone CPWR.MLXGnnn.TZONE.CSI SMPTLIB Base SMP/E System File CPWR.MLXGnnn.F1 SMP##### Base SMP/E System File CPWR.MLXGnnn.F2 SMP##### Base SMP/E System File CPWR.MLXGnnn.F3 1-6 Xpediter/Xchange Installation and User Guide Table 1-1. Libraries Created During Installation with SMP/E ddname Library Type and Content Dataset Name as Distributed SMPMTS Base SMP/E System File CPWR.MLXGnnn.SMPMTS SMPSCDS Base SMP/E System File CPWR.MLXGnnn.SMPSCDS SMPSTS Base SMP/E System File CPWR.MLXGnnn.SMPSTS ALXGCLIB Base Distribution Clist Library CPWR.MLXGnnn.ALXGCLIB ALXGCNTL Base Distribution CNTL Library CPWR.MLXGnnn.ALXGCNTL ALXGDATA Base Distribution Data Library CPWR.MLXGnnn.ALXGDATA ALXGLOAD Base Distribution Load Library CPWR.MLXGnnn.ALXGLOAD ALXGMSG Base Distribution Message Library CPWR.MLXGnnn.ALXGMSG ALXGPNL Base Distribution Panel Library CPWR.MLXGnnn.ALXGPNL ALXGSAMP Base Distribution Sample Library CPWR.MLXGnnn.ALXGSAMP SLXGAUTH Base Target Authorized Loadlib CPWR.MLXGnnn.SLXGAUTH SLXGCLIB CPWR.MLXGnnn.SLXGCLIB Base Target Clist Library SLXGCNTL Base Target CNTL Library CPWR.MLXGnnn.SLXGCNTL SLXGDATA CPWR.MLXGnnn.SLXGDATA Base Target Data Library SLXGLOAD Base Target Loadlib CPWR.MLXGnnn.SLXGLOAD SLXGMSG Base Target Message Library CPWR.MLXGnnn.SLXGMSG SLXGPNL Base Target Panel Library CPWR.MLXGnnn.SLXGPNL SLXGSAMP Base Target Sample Library CPWR.MLXGnnn.SLXGSAMP Preinstallation Considerations This section includes important information that must be considered before beginning the Xchange installation procedure. Specifically, you must: • • • • • • Ensure Specific MVS System Commands Run Collect Site-specific System Information Determine DASD Space Requirements Review Upgrade Considerations Designate an APF Authorized Library Update the MVS Program Properties Table. Each of these preinstallation considerations are described below. Ensure Specific MVS System Commands Run For the Xchange subsystem to properly detect job starts and completions, your site must run with the MVS system commands MONITOR JOBNAMES and MONITOR SESS. Consult your site’s MVS system programmer. Collect Site-specific System Information Collect the following information before you begin to install any component of Xchange: • Generic names assigned to temporary units and DASDs (for example, DISK, SYSDA, VIO, or 3390). • Unique four-character name you choose to assign to the Xchange subsystem. This value must be unique within the entire MVS complex. The subsystem ID used for a Overview 1-7 previous Xchange installation can be reused by performing one of the two options mentioned in “Review Upgrade Considerations” on page 1-8. The default is CWXG. • Job cards to submit batch jobs. • VSAM dataset requirements for special high-level qualifiers or separate volumes. • External security high-level name qualifier. • Values to specify for the NUM variables (see “How NUM Options Affect Xchange Use” on page 3-1). • Xchange requires an Authorized Program Facility (APF) library. Determine DASD Space Requirements Table 1-2 lists the estimated DASD space needed for Xpediter/Xchange target libraries. Table 1-2. DASD Space Requirements Dataset Name 3390 DASD Cylinders CPWR.GLOBAL.CSI 6 CPWR.MLXGnnn.ALXGCLIB 1 CPWR.MLXGnnn.ALXGCNTL 2 CPWR.MLXGnnn.ALXGDATA 4 CPWR.MLXGnnn.ALXGLOAD 15 CPWR.MLXGnnn.ALXGMSG 1 CPWR.MLXGnnn.ALXGPNL 3 CPWR.MLXGnnn.ALXGSAMP 4 CPWR.MLXGnnn.DZONE.CSI 3 CPWR.MLXGnnn.SLXGAUTH 5 CPWR.MLXGnnn.SLXGCLIB 2 CPWR.MLXGnnn.SLXGCNTL 3 CPWR.MLXGnnn.SLXGDATA 4 CPWR.MLXGnnn.SLXGLOAD 9 CPWR.MLXGnnn.SLXGMSG 2 CPWR.MLXGnnn.SLXGPNL 3 CPWR.MLXGnnn.SLXGSAMP 4 CPWR.MLXGnnn.SMPMTS 1 CPWR.MLXGnnn.SMPSCDS 1 CPWR.MLXGnnn.SMPSTS 1 CPWR.MLXGnnn.TZONE.CSI 3 CPWR.SMPLOG 2 CPWR.SMPPTS 2 Note: Compuware recommends that space allocations for Xchange’s SMP/E datasets not be reduced. The supplied allocations provide enough space to receive and apply the FMIDs without forcing SMP/E to perform numerous in-flight compresses. If too many compresses are attempted, SMP/E may abort the current operation. This could leave the installation environment in an unknown, and possibly undesirable, condition. 1-8 Xpediter/Xchange Installation and User Guide Review Upgrade Considerations This section lists various considerations related to upgrading from a previous release of Xpediter/Xchange. • Compuware mainframe products, including Xpediter/Xchange, now use parameter libraries (PARMLIBs) in conjunction with the Compuware Mainframe Services Controller (CMSC) to configure each product as well as common components. For more information, see “Compuware Mainframe Services Controller (CMSC)” on page 1-4 and “PARMLIB Overview” on page 1-9. • If you use the same MVS subsystem name for this release of Xchange as you used for the prior release and you have not IPLed your MVS image since you last started your prior release of Xchange, two options are available to you: – Run the XGSUBRST utility as documented in Chapter 6. This is the preferred method of upgrade as it eliminate the need for the MVS IPL. See Chapter 7, “Using the Xchange Utilities” for more details. – IPL your MVS image. If you use different subsystem names for the new release and the older one, you will be able to run both releases at the same time. • If you plan to run both your currently installed release and the latest release of Xchange, then in “Step 1. Specify Xchange Parameters” on page 3-2, keep in mind that: – The values for NUMAMB, NUMATB, PREVDATE, and other variables in your previous release can be used as initial values for this release. – If you want to run both your currently installed release and the latest release at the same time, the new release must have a different value specified for SUBSYS. – If your security requirements are the same as with the previous release, you can use the same value for SECPFX. If you will not be running two releases at the same time, you can reuse your Xchange journal datasets by specifying the same values on the LOGxxxx parameters. • If you will be running a previous release and the most current release of Xchange at the same time, do the following: – In “Step 4. Update TSO CLISTs” on page 3-12, provide separate TSO CLISTs for each Xchange release. – In “Step 14. Configure Xchange External Security” on page 3-26, create new security rules if a new value was used for the SECPFX parameter. – In “Step 15. Update the Xpediter/TSO LIBDEF” on page 3-30, provide separate Xpediter/TSO CLISTs for each Xchange release. • If any changes were made to the source code in your previous release’s RACROUTE module, then in “Step 3. Assemble and Link the RACROUTE Module” on page 3-12 make the same changes to your new RACROUTE module. • If your site requires IMS Message Level Support, you must perform “Step 10. Enable IMS Message Level Support” on page 3-21, substep 6 for XGTM (DATA member XGTMTM) and XGTS (DATA member XGTMTS). • If your site requires CICS transaction support, you must use Resource Definition Online (RDO) to update your site’s CICS tables with CEDA transactions as described in “Step 7. Enable CICS Transaction Support” on page 3-15. Designate an APF Authorized Library The Xchange address space must be executed from an Authorized Program Facility (APF) load library because it replaces the TIME services vectors and creates a new subsystem. All Overview 1-9 Xchange modules must be link-edited into this library, with the exception of those used for the ISPF, CICS, and batch interfaces, which do not need to run in an authorized state. Prior to MVS/ESA release 4.3, the SYS1.PARMLIB member IEAAPFxx identified authorized libraries in a static list that could be updated only at IPL and could contain up to 253 entries. Since MVS/ESA release 4.3, the SYS1.PARMLIB member PROGxx can be used to identify authorized libraries in a static or dynamic list. When PROGxx uses a dynamic list, an unlimited number of authorized libraries can be specified, and the list can be updated without an IPL. To use PROGxx: 1. Remove the APF=xx parameters from the IEASYSxx and IEASYS00 members of SYS1.PARMLIB. 2. Activate the PROGxx member with the SET PROG=xx operator command. 3. Define the Xchange APF authorized library, CPWR.MLXGnnn.SLXGAUTH, to MVS by adding the DSN and volume to IEAAPFxx or PROGxx (depending on MVS release) in SYS1.PARMLIB. For more information about using PROGxx, consult your site’s MVS system programmer. Update the MVS Program Properties Table Make the following updates to the MVS Program Properties Table (PPT), SCHEDxx in SYS1.PARMLIB: • Change the KEY parameter value to 4. This will allow Xchange to build its control blocks in CSA storage Key 4. • Compuware recommends that you set the PRIV/NOPRIV parameter to PRIV and do not explicitly define Xchange in the WLM classification rules. The PRIV setting will allow Xchange to run in the SYSSTC service class. If Xchange is not allowed to execute at a high priority level, date/time exchanges may not occur. PPT PGMNAME(XGMMAIN) CANCEL KEY(4) NOSYST PRIV NOSWAP DSI PASS AFF(NONE) NOPREF Once the PPT Entry is made to the SCHEDxx member of SYS1.PARMLIB, use the MVS command SET SCH=XX to activate the new program properties table. XX represents the suffix appended to the SCHEDxx member in the SYS1.PARMLIB. PARMLIB Overview This section provides the information and procedures to configure and customize Compuware mainframe products once the SMP/E installation of your products has completed. (See the Compuware Installer Mainframe Products SMP/E Installation Guide for more information on installation of your Compuware mainframe products.) PARMLIB Members Compuware mainframe products use parameter libraries, or PARMLIBs, to configure each product and common components. Table 1-4 lists the Release 17.02 PARMLIB Members 1-10 Xpediter/Xchange Installation and User Guide for all Compuware mainframe products and common components. Your product requires a PARMLIB where its members are provided such that you can modify them to fit your site’s requirements. Compuware recommends using one common dataset, but can be concatenation of dataset names to store your site’s PARMLIB (if applicable) members in a common library. A copy of your product’s parameter file(s) must reside in the //CWPARM DD concatenation of the Compuware Mainframe Services Controller (CMSC). Note: See the Enterprise Common Components Installation and Customization Guide for release 16.05 for further information on CMSC. The Compuware Mainframe Services Controller (CMSC) address space is a centralized facility providing the common parameter library services. It provides two basic functions in relation to parameters: storage and retrieval. The following is a guideline for some of the usage and features of the CMSC: • Users will modify a human readable PARMLIB member and issue a modify command to the CMSC to store this new set of parameters into a common memory object. • This common memory object is accessible even if the CMSC is inactive. • When the CMSC is initialized, all PARMLIB members are loaded into a common memory object. • The default suffix is 00, but this can be changed in the CMSCnnnn PARMLIB member. General Guidelines for PARMLIB Members Parameters used by your Compuware mainframe product or component are read from the common PARMLIB dataset. Edit the sample parameters to your site’s requirements. Table 1-3. General Guidelines PARM Name Values Samples Data columns 1 to 71 N/A Symbol separator Underscore Continuation Check first for any character in Column 72 otherwise, check for “,” is the last non-blank Comments Follow keyword=value and at least one space. "A_LONG_SYMBOL" 1. any non-blank 2. “,” SUBSYS=ACM1 ACME SSID 1 “ACME SSID 1” is a comment If the PARMLIB member includes multiple groups of parameters, for example for the definition of multiple DB2 Subsystem, then only one occurrence of each of the parameters within each group is allowed. System Symbolics The CMSC resolves system symbolics as product parameters which are saved into storage, potentially allowing a single parameter member to be used across multiple LPARs. These symbols are defined by your installation in IEASYMxx. Issue the following display command to display the current symbols: /DISPLAY SYMBOLS PARMLIB Member Naming Convention PPPPnnnn PPPP is the product prefix (see Table 1-3). nnnn is the 1 to 4-character PARMLIB suffix, for example 00. Overview 1-11 The PARMLIB member name for each product or product component must start with the product prefix, for example FACM for File-AID Common Components. The 1- to 4character suffixes can be used to replace the default name (FACM00). If the parameter for a given product is omitted, the default suffix will be 00. Changing the Default PARMLIB Member In the CMSC startup parameters, specify the product parameter, followed by the equal sign, and the 1- to 4-character suffix (for example: FACM=01, which points to PARMLIB member FACM01). If you changed your PARMLIB member name from the default FACM00 to FACM0005, for example, update your CMSC PARMLIB member to point to the new PARMLIB member, FACM=0005. General Guidelines for PARMLIB Dataset • • • • • The The The The The dataset can be blocked. dataset must be defined as Fixed Block. dataset can have multiple extents. dataset must be on a single volume. CMCS must have READ access. Table 1-4. Compuware Product PARMLIB Member Parameters Product PARMLIB Member Parameters Product AABD Abend-AID BDCAS AADC Abend-AID DCAS AAFA Abend-AID Fault Analytics AATD Abend-AID TDCAS AAVW Abend-AID Viewer CMSC Compuware Mainframe Service Controller FACM File-AID Common Component FADA File-AID/Data Solutions FADE File-AID DB2 Environment Information FAMV File-AID/MVS FAFR File-AID/RDX FAFD File-AID for DB2 FAIE File-AID IMS Environment Information FAIX File-AID for IMS HCI Host Communications Interface HSCM Hiperstation LMCL License Management Client (LMSINIT) LMSV License Management Server (LMZINIT) STR Strobe XCOV Xpediter/Code Coverage XVGB Xpediter/Code Coverage CICS components XDGB Xpediter/CICS Global components XDDB Xpediter/CICS DBPA components XTSO Xpediter/TSO XCHG Xpediter/Xchange 1-12 Xpediter/Xchange Installation and User Guide PARMLIB Product Configuration Step 1. Copy Sample PARMLIB Members 1. Copy the provided sample PARMLIB members from your installation sample library to your site’s common PARMLIB dataset(s) for Compuware. Note: Starting with Release 17.02, all Compuware mainframe products require the Compuware Mainframe Services Controller (CMSC) of Enterprise Common Components (Enterprise Common Components) Release 16.05 with all current maintenance applied. Step 2. Update the CMSC with PARMLIB Information 1. Make your product’s PARMLIB members available in the //CWPARM concatenation of the Compuware Mainframe Services Controller (CMSC). (See the Enterprise Common Components Installation and Customization Guide for release 16.05 for further information on CMSC.) 2. After making changes to your PARMLIB members, use the z/OS MODIFY command to update the CMSC with the changes you made to the PARMLIB member. Note: Users issuing MODIFY commands must have MODIFY authority to the CMSC. The verb MODIFY may be abbreviated as the letter F. Refreshing all PARMLIB Members: F cmscname,PARMLIB REFRESH Refreshing a Single Parameter Member: F cmscname,PARMLIB REFRESH member_name For example, if you updated the parameters in member FACM00: F cmscname,PARMLIB REFRESH FACM00 2-1 Chapter 2. Checklist Chap 2 This chapter provides a checklist to configure and customize Xpediter/Xchange once the SMP/E installation has completed (refer to the Compuware Installer Mainframe Products SMP/E Installation Guide). Ensure Enterprise Common Components (ECC) has been installed and configured. ECC includes License Management System (LMS), Host Communications Interface (HCI), Base Services, Compuware Mainframe Services Controller (CMSC), and Compuware Shared Services (CSS). Each step in the checklist provides a convenient link to the full step in Chapter 3, “Configuring Xchange”. ❏ “Step 1. Specify Xchange Parameters” ❏ “Step 2. Perform CMSC REFRESH” ❏ “Step 3. Assemble and Link the RACROUTE Module” ❏ “Step 4. Update TSO CLISTs” ❏ “Step 5. Allocate the Journal Datasets” ❏ “Step 6. Allocate the Save/Restore Dataset” ❏ “Step 7. Enable CICS Transaction Support” ❏ “Step 8. Enable CICS Region Support” ❏ “Step 9. Enable DB2 Support” ❏ “Step 10. Enable IMS Message Level Support” ❏ “Step 11. Enable Enterprise PL/I DATE or DATETIME Built-in Function Support” ❏ “Step 12. Enable C time() Function Support” ❏ “Step 13. Enable Natural Support” ❏ “Step 14. Configure Xchange External Security” ❏ “Step 15. Update the Xpediter/TSO LIBDEF” ❏ “Step 16. Assemble a Journal Exit” ❏ “Step 17. Assemble or Compile and Link Edit Test Programs”. 2-2 Xpediter/Xchange Installation and User Guide 3-1 Chapter 3. Configuring Xchange Chap 3 This chapter is intended for those responsible for configuring Xpediter/Xchange. The configuration process consists of the following primary steps: • • • • • • • • • • • • • • • • • • “How NUM Options Affect Xchange Use” “Step 1. Specify Xchange Parameters” “Step 2. Perform CMSC REFRESH” “Step 3. Assemble and Link the RACROUTE Module” “Step 4. Update TSO CLISTs” “Step 5. Allocate the Journal Datasets” “Step 6. Allocate the Save/Restore Dataset” “Step 7. Enable CICS Transaction Support” “Step 8. Enable CICS Region Support” “Step 9. Enable DB2 Support” “Step 10. Enable IMS Message Level Support” “Step 11. Enable Enterprise PL/I DATE or DATETIME Built-in Function Support” “Step 12. Enable C time() Function Support” “Step 13. Enable Natural Support” “Step 14. Configure Xchange External Security” “Step 15. Update the Xpediter/TSO LIBDEF” “Step 16. Assemble a Journal Exit” “Step 17. Assemble or Compile and Link Edit Test Programs”. This chapter presents each of these steps in detail. Configure Xpediter/Xchange This section details the steps necessary to configure Xpediter/Xchange and its associated modules. If you have already installed the base product and are only applying maintenance PTFs, you may not need to perform the steps in this section. Read the HOLDDATA supplied with the maintenance PTFs to determine whether any of the following steps need to be performed. How NUM Options Affect Xchange Use Before you specify the options in the Xchange CMSC PARMLIB member, you need to know how the NUM variables (NUMAMB, NUMATB, NUMJRE, NUMORE, NUMURE, and NUMXRE) affect Xchange use. Discuss the intended use of Xchange with your site’s users to determine the optimal values for the NUM variables and LOGxxxx parameters. Table 3-1 shows each NUM variable, its initialized (default) value, and the size in bytes of each occurrence of the specified variable. The total storage required in the Extended Common Storage Area (ECSA) for each NUM variable can be determined by multiplying initialized value by the size in bytes of that variable. Table 3-1. NUM Space Requirements NUM Variable Initialized Value Size in Bytes NUMAMB 128 326 NUMATB 256 448 NUMJRE 128 16 3-2 Xpediter/Xchange Installation and User Guide Table 3-1. NUM Space Requirements NUM Variable Initialized Value Size in Bytes NUMORE 16 432 NUMURE 32 256 NUMXRE 64 344 If you expect to make a single subsystem available to a large number of users, Compuware recommends increasing the NUMAMB (number of jobs) value and the NUMATB (number of steps) value. Without the increases, some users might be unable to work with Xchange. Each time you add 1 to NUMAMB increases the ECSA size by 326 bytes, and each time you add 1 to NUMATB increases the ECSA by 448 bytes. Because most jobs have multiple steps, you should normally increase NUMATB by 2 for every 1 that you increase NUMAMB. Therefore, increasing NUMAMB by 1 would require increasing the module by over 1K: 326 bytes for NUMAMB plus 896 bytes (448 x 2) for NUMATB. If you change the default values for NUMAMB and NUMATB, a good starting number to use equals the maximum number of jobs that will be exchanged at any one time for NUMAMB. For NUMATB, use the NUMAMB value multiplied by your average number of steps per job. Your site may choose to use multiple subsystems if, for example, you need to establish more restrictive security in production than you have in your test environment. If you will be using multiple subsystems, you should reduce the NUM variable values for each subsystem in order to reduce the overall resource consumption for Xchange. The other NUM parameters consume less resources than NUMAMB and NUMATB. NUMXRE, at 16 bytes, is unlikely to require considerable resources due to its small size. When determining an appropriate NUMURE value, remember that it is directly affected by the Xchange workload, as identified by the number of requests entered via the ISPF interface in conjunction with the number of Xchange requests running on the system. In addition, setting the correct priority level for the Xchange address space can significantly enhance the throughput of the Xchange system by enabling rapid processing and resetting of the URE control blocks so they can be reused immediately. If Xchange has no opportunity to process the URE control blocks, they can accumulate until the NUMURE value is reached and exchanges no longer occur. See “Update the MVS Program Properties Table” on page 1-9 for information about setting the priority level. After Xchange has been given the proper priority level, you can make minor adjustments to the NUMURE value to meet your maximum workload needs. NUMORE and NUMJRE represent queued units of work, which should be reset so quickly that their values need not be very high. As with NUMURE, resetting of the associated control blocks to enable immediate reuse is directly affected by the priority level of the Xchange address space. Step 1. Specify Xchange Parameters The default parameters that need to be specified in the Xchange CMSC PARMLIB member reside in member XCHG00 in the CPWR.MLXGnnn.SLXGDATA library. The Xchange CMSC PARMLIB member name must be prefixed with XCHG and suffixed with either the CMSC default suffix or 1 to 4 characters of your choice. If suffixed with anything other than the default, make sure the suffix matches the SUFFIX= value on the PARM of the EXEC JCL statement in the Xchange startup JCL. All parameters in the Xchange CMSC PARMLIB member must be in the format keyword=value where keyword begins in column 1 and at least one blank follows value, without any blanks in between. Configuring Xchange 3-3 After adding the default parameters and modifying those parameters based on your organizational needs, save the Xchange CMSC PARMLIB member. Don’t forget to enter the CMSC REFRESH command (see “Step 2. Perform CMSC REFRESH” on page 3-12). The CMSC REFRESH command must be issued every time changes are made to the Xchange CMSC PARMLIB member. In addition, the Xchange subsystem must be recycled for the changes to take effect. All Xchange parameter keywords, values, and defaults are defined below. PARSELIB (Optional) The load library, specified without quotes, where the Xchange parsing exit, LXGPARSE, resides. The parsing exit reads the Xchange CMSC PARMLIB member, validates parameters present and—if validation is successful—generates a common memory object for later retrieval. The default is CPWR.MLXGnnn.SLXGLOAD, replacing CPWR.MLXGnnn with the values used at your site. Notes: – PARSELIB, if specified, should be the first parameter. – If PARSELIB is not specified, this library must be included in the concatenation for LINKLIST. SUBSYS A four-character value that defines the subsystem ID for the Xchange program using this configuration. This value must be unique within the entire MVS complex. The subsystem ID used for a previous Xchange installation cannot be reused without performing an IPL. Compuware recommends consulting an MVS system programmer to choose a name that does not duplicate any existing MVS subsystem names. The default is CWXG. Notes: – Xchange dynamically creates this subsystem in the SSCVT. Do not add the subsystem to IEFSSNxx. No modification of SYS1.PARMLIB is required for installation, except to authorize the AUTHLIB load library. – The first Xchange subsystem started creates another subsystem named XGPC that is shared by any subsequent Xchange subsystems. The name XGPC is reserved for this Xchange subsystem and should not be used for any other subsystem. AUTHUSR Whether Xchange will perform date substitution for programs running authorized. The default is NO. BYPSPLC Whether Xchange will set the automatic QC process off to allow the MPR to process messages that are queued. This will allow the Xchange IMS interface to process the messages queued, instead of processing only one for every program load. YES indicates that the automatic QC process will be set to off, and NO indicates it will not. The default is NO. Note: When this parameter is set to YES, all messages queued will be processed using the IOPCB and MVS date set by the first message processed by the program, even if there are other requests that would affect some of the queued messages. CICSGNRC Controls the logical location of a generic CICS transaction support request. A generic request consists of an asterisk in the UserID, Terminal, TransID, and Program fields. Valid values for the CICSGNRC parameter are YES and NO. The default is NO and does not change the logical location. When the value is YES, it enables CICS transaction support to logically place a generic request as the last request matched against, regardless of the generic request’s location in the transaction list on the 3-4 Xpediter/Xchange Installation and User Guide Simulated Date Time Settings screen. When CICSGNRC support is enabled, message XG3061 is issued in the job log of the Xchange address space. CICSMAXR Controls the number of CICS complete (C) messages that can be created by CICS regions. Valid values for CICSMAXR are in the range 000001 to 999999, but cannot be larger than the value specified for CICSMAXS. The default is 5000. In addition to limiting the number of messages a region can create, this parameter can be used to prevent one CICS region from consuming all the CICS messages available from the pool designated by the CICSMAXS parameter. For example, specifying CICSMAXR=5000 will limit regions to 5000 CICS complete messages even though CICSMAXS may be set to a higher number. If a CICS region reaches the CICSMAXR limit, message creation is suppressed until existing messages are deleted manually, via autoinstall delete (if available), or with the XGTD transaction. Once a message is suppressed for a CICS request, no additional messages will be created for that request until it is either reset or deleted and added again. Message suppression is indicated on the CICS Simulated Date/Time Settings screen with a status of T. If the number of messages is reduced to below the CICSMAXR limit and a request with a status of T is reset or deleted and added, normal message processing will resume until the limit is reached again. Xchange includes a utility called XGFNDMOD that you can use to display the CICSMAXR value and the current number of CICS completed messages for the Xchange subsystem. The JCL to run XGFNDMOD is provided in CPWR.MLXGnnn.SLXGCNTL(XGFNDMOD). It can also be invoked under TSO/E using the XGFNDIT CLIST provided in CPWR.MLXGnnn.SLXGCLIB. XGFNDMOD lists the current number of completed messages as GCACMAX#, the CICSMAXS value as GCACMAXS, the CICSMAXR value as GCACMAXR, and the greatest number of completed messages that have existed since Xchange initialization as GCACMAXH. CICSMAXS Controls the number of CICS complete (C) messages that can be created by an Xchange subsystem. Valid values for CICSMAXS are in the range 000001 to 999999. The default is 10000. Each CICS complete message is created in ECSA and is 84 bytes long. This parameter lets you limit the amount of ECSA that will be used. For example, specifying CICSMAXS=25000 will limit the Xchange subsystem to 25,000 CICS complete messages. If the Xchange subsystem reaches this limit, message creation is suppressed until existing messages are deleted manually, via autoinstall delete (if available), or with the XGTD transaction. Once a message is suppressed for a CICS request, no additional messages will be created for that request until it is either reset or deleted and added again. Message suppression is indicated on the CICS Simulated Date/Time Settings screen with a status of T. If the number of messages is reduced to below the CICSMAXS limit and a request with a status of T is reset or deleted and added, normal message processing will resume until the limit is reached again. Xchange includes a utility called XGFNDMOD that you can use to display the CICSMAXS value and the current number of CICS completed messages for the Xchange subsystem. The JCL to run XGFNDMOD is provided in CPWR.MLXGnnn.SLXGCNTL(XGFNDMOD). It can also be invoked under TSO/E using the XGFNDIT CLIST provided in CPWR.MLXGnnn.SLXGCLIB. XGFNDMOD lists the current number of completed messages as GCACMAX#, the CICSMAXS value as GCACMAXS, the CICSMAXR value as GCACMAXR, and the greatest number of completed messages that have existed since Xchange initialization as GCACMAXH. CLASS The execution class parameter for single-character classes. It is used to prevent accidental exchange of a user’s jobs. A job is not eligible for date/time simulation unless the class under which it runs has been designated during Xchange startup Configuring Xchange 3-5 processing. For example, if most of your site’s production workload runs under a particular class, you could prevent Xchange from affecting those jobs by specifically excluding that class with the CLASS parameter. For more information, see “Using Jobclass Support” on page 5-19. Valid values for the CLASS parameter are: – (ALL) – (ALL,Xchange) – (ONLY,exceptions) If you specify (ALL), every default class (A to Z and 0 to 9) is eligible for date/time exchange. A setting of (ALL,ABC) will allow exchanges for all default classes except classes A, B, and C. If CLASS=(ONLY,ABC), no classes are eligible for exchange except classes A, B, and C. If an Xchange request is set for a job that runs under a class not defined with the CLASS parameter, the date and time will not be exchanged and an ERR=CAUT (class not authorized) error message will be displayed in the Owner field of the request. This class protection is active even if external security has been disabled by setting SECUSE=NO. Note: The CLASS and CLASS8 parameters are mutually exclusive. CLASS8 The execution class parameter for multiple-character classes. It is used to prevent accidental exchange of a user’s jobs. A job is not eligible for date/time simulation unless the class under which it runs has been designated during Xchange startup processing. For example, if most of your site’s production workload runs under a particular class, you could prevent Xchange from affecting those jobs by specifically excluding that class with the CLASS8 parameter. For more information, see “Using Jobclass Support” on page 5-19. The only valid value for the CLASS8 parameter is (ONLY,exceptions). Multiple CLASS8=(ONLY,...) lines are allowed. For example, if you specify (ONLY,A,C2,CLASS008), no classes are eligible for exchange except classes A, C2, and CLASS008. If an Xchange request is set for a job that runs under a class not defined with the CLASS parameter, the date and time will not be exchanged and an ERR=CAUT (class not authorized) error message will be displayed in the Owner field of the request. This class protection is active even if external security has been disabled by setting SECUSE=NO. Note: The CLASS and CLASS8 parameters are mutually exclusive. DDF Enables date and time exchanges when a DB2 SQL CURRENT DATE, CURRENT TIME, or CURRENT TIMESTAMP is requested via the Distributed Data Facility (DDF). Valid values for the DDF parameter are YES and NO. The default is NO. When DDF support is enabled, message XG3057 is issued in the job log of the Xchange address space. DELRQST Whether Xchange will delete status for all jobs when the request is H and delete the status and the request for XGCBATCH and S requests. YES indicates the status/request will be deleted, and NO indicates it will not. The default is NO. DISPIMS Controls whether IMS Message Level Support pattern job requests are displayed on the ISPF Simulated Date Time Settings screen. Valid values are YES and NO. Specifying DISPIMS=YES—or omitting the keyword—will cause Xchange to display IMS requests on the ISPF Simulated Date Time Settings screen. Specifying DISPIMS=NO will cause Xchange to suppress display of IMS requests on the ISPF 3-6 Xpediter/Xchange Installation and User Guide Simulated Date Time Settings screen. DISPIMS=NO also causes Xchange to issue a message during initialization stating that the requests have been suppressed. The default is YES. DMPUNIT A one- to eight-character name of a valid MVS UNITNAME. Xchange uses this name when dynamically allocating a dump dataset. The default is SYSDA. DMPVOL (Optional) The six-character serial number of the volume that will contain any dump datasets dynamically defined by Xchange. This name is optional. If it is omitted, a nonspecific allocation request is made. If you specify a name for this volume, the volume must be correctly represented by the DMPUNIT parameter. DMPPFX A one- to twelve-character prefix used on all dump datasets that Xchange dynamically allocates. The default is CWXGDUMP. Notes: – The prefix you specify must conform to the rules for coding a dataset name. Do not end the prefix with a period (.). The period will be added when the dataset is created. If more than eight characters are used, a period (.) must be inserted to create two levels of the dataset qualifier. The 12-character maximum includes the period. – You must ensure that your external security system gives all userIDs authority to create new dump datasets that are named using the prefix you specify. DMPMCLAS (Optional) A one- to eight-character Management Class that is used to allocate any dump datasets dynamically allocated by Xchange. This name is optional. If omitted, a nonSMS dataset will be dynamically allocated by Xchange. DMPSCLAS (Optional) A one- to eight- character Storage Class that is used to allocate any dump datasets dynamically allocated by Xchange. This name is optional. If omitted, a non-SMS dataset will be dynamically allocated by Xchange. DMPDCLAS (Optional) A one- to eight- character Data Class that is used to allocate any dump datasets dynamically allocated by Xchange. This name is optional. If omitted, a non-SMS dataset will be dynamically allocated by Xchange. ECHJOBE Whether Xchange will put out an XGX404I message for every IEF404I message or an XGXSP395 message for every $HASP395 message (if USEHASP=YES) Xchange sees. This parameter is intended to assist in diagnosing the following error: User sets request, executes job, date/time exchanges, but request remains Active/Executing on ISPF panel. YES indicates Ended message will be echoed, and NO indicates it will not. The default is NO. JWTIM The number of hours and minutes between reactivations of the Xchange address space, represented as a four-digit number, hhmm, where hh is a number between 00 and 23 and mm is a number between 00 and 59. For example, the number 2010 would indicate 20 hours and 10 minutes between reactivations. You must ensure the interval between reactivations is less than the interval specified to JES for the Job Wait Time interval. The default is 0015, or every 15 minutes. Each time the Xchange address space is reactivated, Xchange writes a record to the Xchange journal that contains the amount of subsystem and TIME services activity during the previous interval. The journal record assists in tracking overhead and Configuring Xchange 3-7 system shutdown problems. In addition, the journal file is checkpointed to allow other address spaces access to the most recent records. When the reactivation interval is large, you need to wait a longer time before you can access recent journal records. When this interval is small, you incur increased overhead in the Xchange address space. NODDFAC Whether Xchange will eliminate the DDF entries on the ISPF panel that have an A status. DDF entries on the ISPF panel display requests with a Q status. Whenever a DDF request is exchanged, the actual correlation ID and resource name are displayed and have an A status. YES indicates the elimination of DDF entries on the ISPF panel that have an A status, and NO indicates no such elimination of DDF entries will occur. The default is NO. NUMAMB The maximum number of control blocks associated with jobs, active and completed, that can exist in the Xchange request queue at any given time. NUMAMB control blocks remain in use until you delete the associated request table entries and return them to the pool of free NUMxxx control blocks. The number must be between 10 and 100000. The default is 128. NUMATB The maximum number of steps (application program TCBs), active and completed, that can exist in the Xchange request queue at any given time. NUMATB control blocks remain in use until you delete the associated request table entries and return them to the pool of free NUMxxx control blocks. The number must be between 10 and 100000. The default is 256. NUMJRE The maximum number of queued units of work used to write messages to the Xchange journal dataset. JREs are internal control blocks that are created by Xchange throughout the exchange process. They are reset quickly and therefore should not require a large value. The number must be between 10 and 100000. The default is 128. NUMORE The maximum number of queued units of work used to display messages to the operator. OREs are internal control blocks that are created by Xchange throughout the exchange process. They are reset quickly and therefore should not require a large value. The number must be between 10 and 100000. The default is 16. NUMURE The maximum number of queued units of work. UREs are internal control blocks that are created by Xchange throughout the exchange process. They are reset quickly and therefore should not require a large value. The number must be between 10 and 100000. The default is 32. NUMXRE The maximum number of change request patterns that can be supported by this Xchange subsystem or supported for all users of this subsystem. The number must be between 10 and 100000. The default is 64. PREVDATE Whether previous dates are allowed (that is, whether a date can be exchanged for a date previous to the current date). The default is NO. REPLY Whether an outstanding reply message will display on the operator console. The default is NO. 3-8 Xpediter/Xchange Installation and User Guide Note: The console operator can always enter Xchange commands with the MVS MODIFY and STOP commands. RESTREQ The restore requests parameter used to control the Xchange save and restore process during startup and normal processing of the Xchange address space. Valid values are WARM, COLD, and OFF. Specifying WARM will cause Xchange to restore requests saved from its previous run. All requests are restored unless Xchange configuration changes, such as a reduction in XREs, prevent the restore. Jobclass and CICS H requests are restored with the same first-use running date/time as when they were saved. The default is WARM. Specifying COLD will cause Xchange to bypass restore processing during startup and delete any requests in the save/restore file. This option can be used to bypass restore processing if the file becomes damaged or to delete all current Xchange requests. Requests created after Xchange is started with RESTREQ=COLD are still saved, however, and can be used at the next Xchange startup if the value of RESTREQ is subsequently changed to WARM. Setting this RESTREQ to OFF will cause Xchange to bypass all save and restore processing. If your site uses the OFF setting, the XGSAV001 DD statement can be deleted from the XGSTART JCL or Xchange startup process. SECDFLT Whether Xchange allows access to jobs when a given entity name has not been defined to external security. ALLOW permits access to jobs, and DENY prohibits access to jobs. The default is DENY. For information on external security see “Step 14. Configure Xchange External Security” on page 3-26. SAVINTV A save interval parameter used to control the save request processing time interval for the Xchange address space. The format is SAVINTV=hhmm where hh is hours and mm minutes. The valid range for hh is 00 to 23, and the valid range for mm is 00 to 59. SAVINTV can be set to any valid value between one minute (0001) and one day (2359). You can also specify 0000 to cause a save process to be performed every time an Xchange request is added or deleted. This option prevents the loss of any requests if Xchange ends abnormally or an IPL is performed. If a large numbers of requests are added and deleted, however, the 0000 setting causes significantly more I/O processing. The default value is 0015 which causes Xchange requests to be saved every 15 minutes. SAVMSG A save messages parameter used control whether or not messages are written to the JES job log when Xchange request save processing is started and ended. The ON setting is intended only for verification and diagnostic use. The OFF setting causes Xchange to bypass message generation during save request processing. The default is OFF. SECPFX A one- to eight-character name that the external security module uses as a prefix when creating entity names to pass to the security system. The default is CWXG. For information on external security see “Step 14. Configure Xchange External Security” on page 3-26. SECUSE Whether external security will be used. YES indicates external security will be used, and NO indicates that it will not. The default is YES. For information on external security see “Step 14. Configure Xchange External Security” on page 3-26. Configuring Xchange 3-9 USEHASP Whether Xchange will use messages HASP373/HASP395 in lieu of messages IEF403I/IEF404I for job start/end detection. YES will use HASP messages, and NO will use IEF messages. NO is the default. Note: When this parameter is set to YES, a site will be able to run with MONITOR JOBNAMES and MONITOR SESS off and still allow Xchange to function properly. This logic will only work at sites using JES2. JES3 does not generate HASP messages. XGJEXIT1 Whether Xchange calls a journal exit to determine the program ID that is reported when a journal record is written for TIME services activity. YES indicates that Xchange calls the XGJEXIT1 journal exit as described in “Step 16. Assemble a Journal Exit” on page 3-30. NO indicates that no exit is called. The default is YES. XPGMDIR Whether Xchange will exchange programs that issue SVC11 that have been brought into storage via “directed load”. YES indicates the exchange will occur, and NO indicates it will not. The default is NO. Optional Parameters Each group of parameters described below is optional. If specified, each parameter group must appear at the end of the CMSC PARMLIB member and be specified in the order listed below. LOGxxxx Parameters Note: If you choose to have a journal or journal datasets, the LOGTYPE=INITIAL and LOGTYPE=FINAL parameters are required. Use the LOGxxxx parameters to define each journal dataset used by the Xchange subsystem. There is no limit to the number of journal datasets that a single Xchange subsystem can use. You can define as few or as many as you like, but you must specify one LOGDDN, LOGDSN, and LOGCOPY parameter for each journal dataset. The LOGTYPE=INITIAL must immediately precede all journal datasets defined, and LOGTYPE=FINAL must immediately follow the last one. Each journal dataset must have been defined by IDCAMS, and there cannot be JCL statements in the Xchange job referring to these datasets. Xchange dynamically allocates each dataset and, in turn, de-allocates each dataset when it is filled. This process allows automatic or manual unloading of data from inactive journal datasets. The JCL statements used to create your journal datasets resides in the installation CPWR.MLXGnnn.SLXGCNTL file member ALLOCLOG. Make a note of the journal file names you use in this macro so you can enter them accurately in the ALLOCLOG JCL deck in “Step 5. Allocate the Journal Datasets” on page 3-13. If you intend to view or extract records from the journal, specify at least two journal files. This permits automatic swapping from a filled journal file to the next journal file. When each journal file is swapped out, the next file is reset when it is swapped in, and data in it is lost. Therefore, more journal files give you more flexibility in monitoring Xchange transactions, but they require space allocated for the files themselves. Note: Discuss the intended usage of Xchange with your site’s users to determine optimal values for the LOGxxxx parameters. 3-10 Xpediter/Xchange Installation and User Guide LOGTYPE Bookend for the following parameters beginning with “LOG”. LOGTYPE=INITIAL must immediately precede the first of these parameters, and LOGTYPE=FINAL must immediately follow the last of these parameters. LOGDDN The one- to eight-character name of the data definition (DD) statement that Xchange uses when referencing this journal dataset. LOGDSN The 1- to 44-character dataset (DS) name for this journal dataset. LOGCOPY Whether the journal dataset is the backup journal file. Each time a journal file is filled, all date records are copied from that file to the backup journal file and appended to the existing entries in that backup file. YES indicates that the journal file is the backup file. NO indicates that it is not. Only one LOGCOPY parameter can contain the YES value. The default is NO. Note: The parameters prefixed with “LOG” above must be in the order listed for each journal dataset. For example, if using multiple journal datasets, the parameters would be listed in the following order: LOGTYPE=INITIAL LOGDDN=JOURNAL1 LOGDSN=CUSTOMER.JOURNAL1 LOGCOPY=NO LOGDDN=JOURNAL2 LOGDSN=CUSTOMER.JOURNAL2 LOGCOPY=NO etc. LOGTYPE=FINAL XCLPxxxx Parameters Note: If you choose to exclude a program or programs from date/time exchanges, the XCLPTYPE=INITIAL and XCLPTYPE=FINAL parameters are required. Use the XCLPxxxx parameters to identify programs to be excluded from date and time substitution. Excluding a program does not prevent a user from specifying it in a request. When a match for the specified program is encountered, Xchange returns the actual date and time rather than substituting a value. These parameters must be placed after the LOGxxxx parameters and before any XCLJxxxx parameters that you may have included. There is no limit to the number of programs you can exclude with the XCLPxxxx parameters. XCLPTYPE Bookend for the following parameter, XCLPROG. XCLPTYPE=INITIAL must immediately precede this parameter, and XCLPTYPE=FINAL must immediately follow the last one. XCLPROG The one- to eight-character name of the program to be excluded from Xchange’s date and time substitution process. You can specify an asterisk (*) as a wildcard character. For example, ADSIR* excludes all programs that begin with ADSIR (ADSIR100, ADSIR200, and so on). Notes: – Do not exclude DFS* for IMS programs or DSN* for DB2 programs. Xchange already has logic to exclude these programs when an SVC 11 is issued. Configuring Xchange 3-11 – There is no default Xchange exclude logic for DB2 SQL CURRENT DATE, CURRENT TIME, or TIMESTAMP special register requests. Use this parameter, replacing the program name with the plan name, to exclude specific plans from having their DB2 SQL special register requests exchanged. For DB2, the plan name is used instead of the program name. – To exclude CICS programs and/or transactions from date and time substitution, follow the instructions in "“Program and Transaction Exclusion” on page 3-17. XCLJxxxx Parameters Note: If you choose to specify Jobnames to exclude from date/time exchanges, the XCLJTYPE=INITIAL and XCLJTYPE=FINAL parameters are required. Use the XCLJxxxx parameters to identify Jobnames to be excluded from date and time substitution. Excluding a Jobname does not prevent a user from specifying it in a request. When a match for the specified Jobname is encountered, Xchange returns the actual date and time rather than substituting a value. This macro must be placed after the LOGxxxx parameters, and any XCLPxxxx parameters you may have included and before any XCLUxxxx parameters you may have included. There is no limit to the number of Jobnames you can exclude with the XCLJxxxx parameters. Note: The XCLJxxxx parameters cannot be used to exclude a CICS or IMS region. XCLJTYPE Bookend for the following parameter, XCLJOB. XCLJTYPE=INITIAL must immediately precede this parameter, and XCLJTYPE=FINAL must immediately follow the last one. XCLJOB The one- to eight-character Jobname to be excluded from Xchange’s date and time substitution process. The name may be enclosed in quotes. You can specify an asterisk (*) as a wildcard character. For example, JACME* excludes all Jobnames that begin with JACME (JACME101, JACME102, and so on). XCLUxxxx Parameters Note: If you choose to specify IMS userIDs to exclude from date/time exchanges, the XCLUTYPE=INITIAL and XCLUTYPE=FINAL parameters are required. Use the XCLUxxxx parameters to identify IMS userIDs to be excluded from date and time substitution. Excluding an IMS userID does not prevent a user from specifying it in a request. When a match for the specified IMS userID is encountered, Xchange returns the actual date and time rather than substituting a value. These parameters must be placed after the LOGxxxx parameters and after any XCLPxxxx or XCLJxxxx parameters that you may have included and before any TERMxxxx parameters you may have included. There is no limit to the number of IMS userIDs you can exclude with the XGGXCLU macro. XCLUTYPE Bookend for the following parameter, XCLUSER. XCLUTYPE=INITIAL must immediately precede this parameter, and XCLUTYPE=FINAL must immediately follow the last one. XCLUSER The one- to eight-character IMS userID to be excluded from Xchange’s date and time substitution process. The name may be enclosed in quotes. You can specify an asterisk (*) as a wildcard character. For example, ACMEU* excludes all IMS userIDs that begin with ACMEU (ACMEU8RC, ACME2DT, and so on). 3-12 Xpediter/Xchange Installation and User Guide TERMxxxx Parameters Note: If you choose to specify which terminals will be eligible for date/time exchanges, the TERMTYPE=INITIAL and TERMTYPE=FINAL parameters are required. Use the TERMxxxx parameter with CICS transaction support to define which terminals are eligible to be specified on the Simulated Date Time Settings screen. If no TERM values are specified, only the current terminal ID and the reserved terminal name ASYN will be accepted on the Simulated Date Time Settings screen. By specifying values for the TERM parameter, you can enable the entry of additional terminal IDs or groups of terminal IDs. These parameters must be placed after the LOGxxxx parameters and after any XCLPxxxx, XCLJxxxx, or XCLUxxxx parameters that you may have included. There is no limit to the number of terminals you may specify. TERMTYPE Bookend for the following parameter, TERM. TERMTYPE=INITIAL must immediately precede this parameter and TERMTYPE=FINAL must immediately follow the last one. TERM A terminal ID or group of terminal IDs that Xchange will accept on the Request Setup and Status screen. An asterisk (*) may be used as a wildcard character. For example, T* would enable all terminals with IDs starting with T to be entered in Xchange requests. Step 2. Perform CMSC REFRESH After saving the Xchange CMSC PARMLIB member, issue the CMSC REFRESH command. See the section entitled “CMSC Commands” in the ECC Installation and Customization Guide for detailed instructions on issuing this command. The Xchange parsing exit, LXGPARSE, will then read the Xchange CMSC PARMLIB member, validate parameters present, and if validation is successful, generate a common memory object for later retrieval. Step 3. Assemble and Link the RACROUTE Module The RACROUTE module found in install CPWR.MLXGnnn.SLXGDATA file member USRRACRT is designed to work with any SAF-compliant external security package. This module may be modified, if required. JCL to assemble and link the RACROUTE module (USRRACRT) is included in the CPWR.MLXGnnn.SLXGCNTL PDS as member ASMRACRT. Make any necessary edits and run the job. Step 4. Update TSO CLISTs This step has two parts, one required and one optional. 1. Edit the XCHANGE, XGLOG, XGFNDIT, and HELPPTFS CLISTs in CPWR.MLXGnnn.SLXGCLIB, replacing CPWR with the high-level qualifier chosen for your site. These four CLISTs dynamically LIBDEF the required datasets to allow Xchange to: – – – – – Be added to current ISPF panels Be invoked via the TSO COMMAND line Be invoked via the TSO EXEC facility Display certain parameter settings Display which PTFs have been applied 2. Optional: The Xchange SYSPROC and ISPF libraries can also be made accessible to Xchange users via their TSO logon CLIST. If you created new libraries for Xchange, Configuring Xchange 3-13 allocate those new libraries before ISPF initiation by adding the following allocations to the logon CLISTs: ALLOC ALLOC ALLOC ALLOC F(SYSPROC) F(ISPMLIB) F(ISPPLIB) F(ISPLLIB) DA(’CPWR.MLXGnnn.SLXGCLIB’) SHR DA(’CPWR.MLXGnnn.SLXGMSG’) SHR DA(’CPWR.MLXGnnn.SLXGPNL’) SHR DA(’CPWR.MLXGnnn.SLXGLOAD’) SHR Step 5. Allocate the Journal Datasets 1. Use IDCAMS to create each journal dataset. You do not need to pre-initialize the datasets. They simply need to be created. Figure 3-1 provides a sample of an IDCAMS job for creating journal datasets. This JCL is included in the CPWR.MLXGnnn.SLXGCNTL PDS as member ALLOCLOG. 2. Edit ALLOCLOG following the instructions given near the top of the file, then submit the job. 3-14 Xpediter/Xchange Installation and User Guide Figure 3-1. Sample IDCAMS job for Allocating a Journal Dataset (ALLOCLOG) //* --> PLACE JOB CARD HERE //* //********************************************************************* //* INSTALLER: * //* * //* TO USE THIS JCL, YOU NEED TO * //* * //* - USE ISPF 'CHANGE ALL' TO REPLACE 'CUSTOMER.JOURNALN' (WHERE * //* N=A DIGIT CORRESPONDING TO THOSE IN YOUR JOURNAL DSNS) WITH * //* THE JOURNAL FILE DSNS YOU WISH TO USE WITH XPEDITER * //* XCHANGE. NOTE: THESE MUST BE THE SAME NAMES AS THOSE YOU * //* USED WHEN YOU EDITED THE XCHANGE PARMLIB MEMBER IN YOUR * //* SITE'S COMMON PARMLIB DATASET FOR COMPUWARE. IF YOU ARE * //* NOT CERTAIN OF THOSE NAMES, REFER TO THE XCHANGE PARMLIB * //* MEMBER IN YOUR SITE'S PARMLIB DATASET FOR COMPUWARE. * //* * //* - USE ISPF 'CHANGE ALL' TO REPLACE 'VOLSER' WITH THE VOLUME * //* SERIAL NUMBER OF A DASD UNIT ON WHICH YOU CAN CREATE VSAM * //* FILES. * //* * //* - INSERT A VALID JOB CARD AND SUBMIT THE JOB. * //********************************************************************* //* //DELETE EXEC PGM=IDCAMS,REGION=3M //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE customer.journal1 CLUSTER DELETE customer.journal2 CLUSTER DELETE customer.journal3 CLUSTER /* //DEFINE EXEC PGM=IDCAMS,REGION=3M //SYSPRINT DD SYSOUT=* //SYSIN DD * DEFINE CLUSTER (NAME(customer.journal1) - TRK(90) VOL(volser) - CISZ(16384) SPANNED - RECSZ(60 32600) NONINDEXED - REUSE SHR(2 3) RECOVERY) DEFINE CLUSTER (NAME(customer.journal2) - TRK(90) VOL(volser) - CISZ(16384) SPANNED - RECSZ(60 32600) NONINDEXED - REUSE SHR(2 3) RECOVERY) DEFINE CLUSTER (NAME(customer.journal3) - TRK(90) VOL(volser) - CISZ(16384) SPANNED - RECSZ(60 32600) NONINDEXED - REUSE SHR(2 3) RECOVERY) /* Step 6. Allocate the Save/Restore Dataset Xchange can save all date/time simulation requests to a save/restore dataset at userspecified intervals, then automatically restore them when Xchange is restarted. The save/restore dataset is created with IDCAMS using the sample JCL shown in Figure 32. This JCL is provided in member CPWR.MLXGnnn.SLXGCNTL(ALLOCSAV). Edit the ALLOCSAV member following the instructions given near the top of the file, then submit the job. Note: If your site does not want to use Xchange’s save and restore capabilities: Configuring Xchange 3-15 • Do not submit the JCL shown in this step. • Specify OFF for the RESTREQ Xchange parameter. See “Step 1. Specify Xchange Parameters” on page 3-2 for more information. Figure 3-2. SAVE/RESTORE Dataset Allocation JCL //* ==> INSERT JOB CARD HERE //* //********************************************************************* //* INSTALLER: * //* * //* TO USE THIS JCL, YOU NEED TO * //* * //* - USE ISPF ’CHANGE ALL’ TO REPLACE ’customer.saverest.file’ * //* WITH THE FILE DSN YOU WISH TO USE WITH XPEDITER/XCHANGE. * //* * //* NOTE: THIS MUST BE THE SAME NAME AS THE NAME SUPPLIED IN * //* THE XCHANGE START JCL FOR THE DD XGSAV001. * //* * //* - USE ISPF ’CHANGE ALL’ TO REPLACE ’volser’ WITH THE VOLUME * //* SERIAL NUMBER OF A DASD UNIT ON WHICH YOU CAN CREATE VSAM * //* FILES. * //* * //* - INSERT A VALID JOB CARD AND SUBMIT THE JOB. * //* * //********************************************************************* //* //* //DELETE EXEC PGM=IDCAMS,REGION=3M //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE customer.saverest.file CLUSTER /* //DEFINE EXEC PGM=IDCAMS,REGION=3M //SYSPRINT DD SYSOUT=* //SYSIN DD * DEFINE CLUSTER (NAME(customer.saverest.file) - CYL(1) VOL(volser) - CISZ(32768) - NONINDEXED - REUSE - RECOVERY - RECSZ(100 32758) - SHR(2 3)) Step 7. Enable CICS Transaction Support Note: If your site does not require CICS transaction support, you may skip this step. You can exchange the date and time for individual programs, terminals, user IDs, and transactions within a CICS region using Xchange’s CICS transaction support feature. CAUTION: Do not use Xchange’s CICS region support and CICS transaction support at the same time. This combination can cause unpredictable results. 1. Add the load library CPWR.MLXGnnn.SLXGLOAD containing Xpediter/Xchange to the DFHRPL concatenation in your site’s CICS startup JCL. 2. Use Resource Definition Online (RDO) to update your site’s CICS tables with CEDA transactions, either one at a time or using the RDO batch utility. For CICS TS 3.1 and above, use member XGCRDOTE in the CPWR.MLXGnnn.SLXGDATA library as your 3-16 Xpediter/Xchange Installation and User Guide RDO batch utility input dataset. Make any necessary changes, then either submit your RDO batch utility JCL to batch the required CEDA transactions, or run the transactions individually. Language Environment/CICS Dependency Information Xpediter/Xchange supports Language Environment (LE). Ensure that your site is current on z/OS, CICS, and LE maintenance before attempting to use Language Environment with Xchange. Automatic Request Deletion Normally, an Xpediter/Xchange user will delete their requests before leaving CICS. But if a terminal is disconnected, signed off, or logged off while an Xchange session is still active, the ID of that terminal will remain assigned to the abandoned (but still active) requests. Because another terminal logging on could be assigned the same ID, it is possible for a user to be assigned active Xchange requests they don’t know about. The first user may have left the session with requests set and no sure way of re-accessing the same session to delete them. To prevent this from happening, Xchange can be set up to automatically delete requests when the terminal is signed off, logged off, and/or disconnected. This is done by modifying the exit DFHZATDX or whatever terminal autoinstall exit is being used. Then when a terminal is logged off, the modified exit will delete any Xchange requests owned by that terminal. Enable automatic request deletion as follows: 1. Locate the exit DFHZATDX (or the VTAM terminal autoinstall exit used at your site) for modification. If your site uses a different autoinstall exit, its name can be found in the SIT parameter AIEXIT. 2. Add the following line of code to DFHZATDX in the “Delete Processing Section” after the IBM “Put Delete Code Here” comment: EXEC CICS START INTERVAL (0) TRANSID (’XGTM’) FROM (DELETE_TERM_ID) Note: Consider adding “NOHANDLE”—or other appropriate condition handling— for exception conditions such as TRANSIDERR. 3. If your site uses MRO, additional lines of code are required for each application owning region (AOR) where Xchange is installed. The lines should be added directly after the line shown above. Select the lines appropriate for your site from the following: EXEC CICS START INTERVAL (0) TRANSID(’XGTn’) FROM(DELETE_TERM_ID) NOHANDLE * where XGTn is the terminal owning region (TOR) transaction ID for XGTM in the AOR, or EXEC CICS START INTERVAL (0) * TRANSID(’XGTM’) SYSID(’aor-id’) FROM(DELETE_TERM_ID) NOHANDLE where aor-id is the SYSID of the AOR. Note: A continuation character must be included in position 72 of the first line, as shown. 4. Reassemble and link edit DFHZATDX. Configuring Xchange 3-17 Program and Transaction Exclusion Xchange is designed to exclude certain default programs and transactions from date and time exchanges. You can specify additional programs or transactions by editing program XGTEXCL found in the CPWR.MLXGnnn.SLXGDATA PDS. Excluding a program or transaction does not prevent a user from specifying it in a request. When a match for the specified program or transaction is encountered, Xchange returns the actual date and time rather than substituting a value. Note: Program XGTEXCL is for CICS transaction support only. 1. Add an XGTXCLP entry for each program to be excluded and an XGTXCLT entry for each transaction to be excluded. The XGTXCLP entry is required whenever either entry is added and must always precede the XGTXCLT entry. An asterisk wildcard character can be used to create generic program or transaction entries as shown in this example: XGTXCLP ’PROG*’ XGTXCLT ’TRN*’ 2. When no programs but one or more transactions are to be excluded, be sure to include the XGTXCLP entry as shown here: XGTXCLP XGTXCLT ’TRN*’ 3. When no transactions but one or more programs are to be excluded, be sure to include the XGTXCLT entry as shown here: XGTXCLP 'PROG*' XGTXCLT 4. After adding the desired entries, perform the following: a. b. c. d. e. Assemble XGTEXCL Relink XGTMAIN and XGTSEQI Newcopy XGTMAIN and XGTSEQI STOP Xchange CICS interface - STOP primary command on XGTS line Enter XGTS/XGTM to restart CICS Xchange interface Sample JCL for assembling XGTEXCL and relinking XGTMAIN and XGTSEQI is provided in CPWR.MLXGnnn.SLXGCNTL PDS member ASMXCL. Note: If changes are later made to XGTXCLT, step 4 above must be performed again. PLT Initialization You may use PLT initialization to enable Xchange CICS transaction support and set Xchange CICS transaction support requests as follows: 1. To enable Xchange PLT initialization, add: DFHPLT TYPE=ENTRY,PROGRAM=XGTSEQI to your PLTPI table, placing it after the DFHDELIM entry. 2. Define a PDS or PDSE for DD XGSEQINP to hold Xchange CICS transaction support requests with the following attributes: – Record format: FB – Record length: 80. Sample JCL to define a PDS or PDSE is provided in CPWR.MLXGnnn.SLXGCNTL PDS member DEFSEQI. 3-18 Xpediter/Xchange Installation and User Guide 3. Create records in the input dataset as described in “Using CICS Transaction Support with Input from a PDS or PDSE” on page 5-66. 4. Add the input DD name to your site’s CICS startup JCL as described in “Using CICS Transaction Support with Input from a PDS or PDSE” on page 5-66. PLT Shutdown You may use the CICS PLT shutdown to free up the storage used for Xchange requests and messages. If program XGTMAIN is included in your PLT shutdown table, all Xchange requests and messages will be deleted, and their storage freed, when the CICS region is brought down. To enable Xchange PLT shutdown, add DFHPLT TYPE=ENTRY,PROGRAM=XGTMAIN to your PLTSD table, placing it before the DFHDELIM entry. Step 8. Enable CICS Region Support Note: If your site does not require CICS region support, you may skip this step. CAUTION: Do not use Xchange’s CICS region support and CICS transaction support at the same time. This combination can cause unpredictable results. When using CICS region support, transaction and/or program exclusion lists do not apply. Using STCKSYNC Support STCKSYNC support is required with CICS region support. The activation of STCKSYNC support is done during the startup of Xchange. By enabling the Xchange SVC, you also enable STCKSYNC support. See “Enabling Xchange SVC” on page 4-3 and “Enabling Region Support” on page 5-51 for additional information. PLT Initialization for CICS TS 4.1 and Above Due to the way in which the CICS ABSTIME value is returned starting in CTS 4.1, Xchange must be started in the PLT. Enable Xchange PLT initialization as follows: 1. Add the following to your PLTPI table, placing it after the DFHDELIM entry: DFHPLT TYPE=ENTRY,PROGRAM=XGTREGN 2. Use Resource Definition Online (RDO) to update your site’s CICS tables with CEDA transactions in member XGCRDOR of dataset CPWR.MLXGnnn.SLXGDATA, either one at a time or using the RDO batch utility. 3. Copy load modules XGTREGN and XGTABSTM from dataset CPWR.MLXGnnn.SLXGLOAD to a load library in the DFHRPL of your site’s CICS startup JCL. Enable Midnight Rollover Xchange’s CICS region support requires additional midnight rollover processing. To enable this support, perform the following steps: 1. Add the following line to your PLTPI table after the DFHDELIM entry: Configuring Xchange 3-19 DFHPLT TYPE=ENTRY,PROGRAM=XGTAJP3 Note: If you completed “Step 7. Enable CICS Transaction Support” on page 3-15, you may skip steps 2 and 3 below. 2. Add the load library CPWR.MLXGnnn.SLXGLOAD containing Xchange to the DFHRPL concatenation in your site’s CICS startup JCL. 3. Use Resource Definition Online (RDO) to update your site’s CICS tables with CEDA transactions, either one at a time or using the RDO batch utility. For CICS TS 3.1 and above, use member XGCRDOTE in the CPWR.MLXGnnn.SLXGDATA library as your RDO batch utility input dataset. Make any necessary changes, then either submit your RDO batch utility JCL to batch the required CEDA transactions, or run the transactions individually. Enable Language Environment (LE) Note: If your site does not require date/time exchanges for LE programs under Xchange CICS region support, you may skip this section. A zap to LE module CEEPLPKA is required if you want to exchange LE in CICS at the region level. The zap is necessary because LE gets initialized in a way that circumvents the normal dynamic hooking of LE by Xchange. To enable this support, perform the following steps: 1. Compuware recommends that a copy of load module CEEPLPKA be placed in its own library and this zap be applied to that copy. 2. Run the job contained in dataset CPWR.MLXGnnn.SLXGCNTL member XGZLE370. Follow the directions contained in the comments of the job. 3. Place the library with the zapped version of CEEPLPKA in the DFHRPL DD of the CICS region that is to be exchanged. This library must be concatenated before the normal LE SCEERUN library. Only use this zapped copy of CEEPLPKA when Xchange is required in a CICS region. Notes: – Whenever maintenance is applied to LE, make a new copy of CEEPLPKA and reapply this zap to that new copy. – If region level CICS exchanges are required and this zap has been applied, Xchange CICS transaction level support should not be used. Mixing region level and transaction level support concurrently in a CICS environment may cause the date/time value in the EIB to differ from the date and time requested. – If you will also be performing the procedure in “Enable Language Environment (LE) for DB2 Support” on page 3-20, you can use the same zapped CEEPLPKA module from this step to exchange DB2 stored procedures. Step 9. Enable DB2 Support Note: If your site does not require DB2 support, you may skip this step. Xchange DB2 support provides date/time simulation for SQL time functions while preserving the integrity and availability of DB2. With DB2 support enabled, Xchange will intercept DB2 special registers CURRENT DATE, CURRENT TIME, and CURRENT TIMESTAMP and return whatever values were specified on the Simulated Date Time Settings screen. Date, time, and timestamp columns defined as NOT NULL WITH DEFAULT will also be exchanged. Xchange DB2 support is enabled by applying a USERMOD zap to the CSECT named DSNXVCTS in the IBM module DSNXGRDS. This CSECT is used solely for SQL date 3-20 Xpediter/Xchange Installation and User Guide functions, so other DB2 dates are unaffected. The zapped module must be accessible to the DB2 database’s (DBM) address space — for example, in the STEPLIB. Cycling the address space may be necessary. Xchange DB2 Distributed Data Facility (DDF) support requires the same USERMOD zap. The zapped module must be accessible to the DB2 DIST address space — for example, in the STEPLIB. Cycling the address space may be necessary. Xchange DB2 Stored Procedure support requires the same USERMOD zap. The zapped module must be accessible to the Workload Manager (WLM) address space — for example, in the STEPLIB. Cycling the address space may be necessary. If Xchange fails during processing, its full recovery support prevents DB2 and the user application from abending and allows DB2 to perform its normal recovery and cleanup. DB2 returns a date of all asterisks to the caller and an SQL-187 return code just as it would if Xchange had not been involved. Applying the DB2 Zap Compuware recommends that SMP/E be used to apply the Xchange DB2 zap. There are two advantages to using SMP/E: • If DB2 maintenance is later applied, you will be alerted to any regressions. • The zap can be easily removed with the SMP/E RESTORE function. 1. Select the sample jobstream in CPWR.MLXGnnn.SLXGCNTL that corresponds to your site’s DB2 release from the list in Table 3-2. Table 3-2. DB2 Release Xchange DB2 Zap Members Sample Jobstream Non-SMP SMP/E 6.1 XGDB2A61 XGDB2S61 7.1 XGDB2A71 XGDB2S71 8.1 XGDB2A81 XGDB2S81 9.1 XGDB2A91 XGDB2S91 10.1 XGDB2AA1 XGDB2SA1 11.1 XGDB2AB1 XGDB2SB1 12.1 XGDB2AC1 XGDB2SC1 Both jobstreams for each DB2 release point to a common zap member, XGZPDBxx, found in the CPWR.MLXGnnn.SLXGDATA PDS. The xx corresponds to the final two digits of the jobstream. 2. Before applying the zap by running the appropriate job, either comment out or uncomment the EXPAND statement on the first line of XGZPDBxx as follows: • For SMP/E, replace the asterisk (*) in position 1 with a blank. • For non-SMP, make sure an asterisk is in position 1. 3. Apply the zap. Enable Language Environment (LE) for DB2 Support Note: If your site does not require date/time exchanges for LE programs under Xchange’s DB2 stored procedure support, you may skip this section. A zap to LE module CEEPLPKA is required if you want to exchange date/time calls from within DB2 stored procedures. The zap is necessary because LE gets initialized in a way that circumvents the normal dynamic hooking of LE by Xchange. Configuring Xchange 3-21 Make sure the previous portions of this step have been followed to enable the exchange of DB2 SQL date/time calls. Note: If you already executed CPWR.MLXGnnn.SLXGCNTL member XGZLE370 to create a zapped version of CEEPLPKA in “Enable Language Environment (LE)” on page 3-19, you can use the same zapped module to exchange DB2 stored procedures. To enable LE for DB2 support, perform the following steps: 1. Compuware recommends that a copy of load module CEEPLPKA be placed in its own STEPLIB/JOBLIB and this zap be applied to that copy. 2. Run the job contained in dataset CPWR.MLXGnnn.SLXGCNTL member XGZLE370. Follow the directions contained in the comments of that job. This STEPLIB/JOBLIB must be concatenated before the normal LE SCEERUN library in both the DB2 WLM JCL and the JCL invoking the DB2 application. Only use this zapped copy of CEEPLPKA when Xchange is required from within the execution of the DB2 stored procedure. 3. Whenever maintenance is applied to LE, make a new copy of CEEPLPKA and reapply this zap to that new copy. Step 10. Enable IMS Message Level Support Note: If your site does not require IMS Message Level Support, you may skip this step. With Xchange’s IMS Message Level Support, you can exchange the date and time for IMS Message Processing Programs (MPPs), including Wait For Input (WFI) transactions, Interactive Fast Path (IFP) programs, and Batch Message Processing (BMP) regions. CAUTION: Do not use the ISPF Interface to set a region level pattern request for the same message processing region being used for IMS Message Level Support. This combination can cause unpredictable results. To enable IMS Message Level Support, perform the following steps: 1. Define the Xchange Message Level Support programs and their associated transactions to IMS. a. Edit the definitions found in CPWR.MLXGnnn.SLXGDATA member XGIMSST1, substituting the desired message class codes for each occurrence of xx, then add those definitions to the appropriate section of your site’s IMS STAGE 1 SYSGEN input stream. b. Perform an IMS CTLBLKS gen. 2. Ensure that the message class codes associated with the Xchange transactions XGTM, XGTS, XGTMI02, XGTSI02, XGTMI03, and XGTSI03 are available in the Message Processing Region(s) (MPRs) in which they will be running. Note: The XGTM, XGTS, XGTMI02, XGTSI02, XGTMI03, and XGTSI03 transactions do not need to be defined in every MPR in which transactions will have their date and time exchanged. They only need to be defined in the MPR(s) where Xchange requests will be entered. Transactions to be exchanged can be run in any connected region. 3. Perform PSBGENs for the Xchange programs XGTMI01, XGTMI02, XGTMI03, XGTSI01, XGTSI02, and XGTSI03 using your site’s standard PSBGEN utility JCL. Use CPWR.MLXGnnn.SLXGDATA members XGTMI01, XGTMI02, XGTMI03, XGTSI01, XGTSI02, and XGTSI03 as input to the PSBGEN utility. 3-22 Xpediter/Xchange Installation and User Guide 4. Generate the appropriate ACB control blocks for programs XGTMI01, XGTMI02, XGTMI03, XGTSI01, XGTSI02, and XGTSI03 using your site’s standard ACBGEN utility. 5. Generate Message Format Services (MFS) control blocks for XGTM, XGTMC, XGTMV, XGTS, XGTSC, XGTSV, XGEMA, and XGHPA running your site’s MFS utility with CPWR.MLXGnnn.SLXGDATA members XGTMTM, XGTMTC, XGTMTV, XGTMTS, XGTSTC, XGTSTV, XGTMEMA, and XGTMHPA as input. Note: In the furnished MFS source, the DEV macro specifies TYPE=(3270,2). Some sites may require a different TYPE, such as TYPE=3270-A02. If necessary, change the TYPE operand of the DEV macro to a value appropriate for your site. 6. Run the IMS online change utility to load the control blocks you have generated into the inactive IMS system libraries. These control blocks are ACBLIB, MODBLKS, and FMTLIB members. If you want to use IMS security to restrict access to the Xchange administrative user transaction XGTS, refer to the appropriate IBM IMS/ESA documentation. 7. Use IDCAMS to create each IMS request dataset. All dependent regions that connect to a control region must share the same IMS request dataset. That dataset cannot be shared by dependent regions connected to any other control region. The JCL for creating and initializing an IMS request dataset is included in the CPWR.MLXGnnn.SLXGCNTL member ALLOCIMS. 8. Edit ALLOCIMS following the instructions given near the top of the file, then submit the job. 9. Modify the JCL of each dependent region in which Xchange date and time simulations are to be performed as follows: a. In the step that executes DFSRRC00, concatenate the Xchange loadlib to the region’s steplib. Note: If Xpediter/Xchange will be working with LE date/time calls in an MPR that specifies a pre-load of CEELRRIN, you must have the Xchange zap to CEEPLPKA in the STEPLIB concatenation before the SCEERUN library. If you created a zapped CEEPLPKA module in “Enable Language Environment (LE)” on page 3-19, you can use that same zapped CEEPLPKA module in this step. An alternative solution is to remove CEELRRIN from the pre-load list. b. Add the following DD statement, replacing customer.ims.file with the dataset name you defined in step 7 above: //XGIMSREQ DD DSN=customer.ims.file,DISP=SHR c. Add the following step at the end of the region’s JCL, replacing CPWR with the high-level qualifier chosen for your site and again replacing customer.ims.file with the dataset name you defined in step 7 above: //CLEANUP EXEC PGM=XGCLNREQ,COND=EVEN //STEPLIB DD DSN=CPWR.MLXGnnn.SLXGLOAD,DISP=SHR //XGIMSREQ DD DSN=customer.ims.file,DISP=SHR 10. Edit CPWR.MLXGnnn.SLXGDATA member XGPCCUPD for IMS 10.1 and below, XGPCCUP1 for IMS 11.1 through IMS 13.1, or XGPCCU14 for IMS 14.1 and above, changing the first character on the first line from a dollar sign ($) to a period (.). 11. If you want to use SMP/E to install the Xchange interface with the IMS module, go to substep 12. Otherwise, go to substep 13. 12. Review the JCL to perform the SMP/E install of the Xchange interface. Configuring Xchange 3-23 JCL to perform an SMP/E install of the Xchange interface with the IMS module DFSPCC20 is provided in CPWR.MLXGnnn.SLXGCNTL member XGIMSSxx, where xx represents the IMS release used at your site. (If using IMS release 10.1 or above, the member name is XGIMSxxx.) If necessary, this USERMOD may be removed from DFSPCC20 with the SMP/E RESTORE function. Compuware recommends that the RESLIB DD/DDDEF for this step point to a library other than your normal IMS RESLIB. The selected library should then be included ahead of your normal IMS RESLIB in the IMS STEPLIB concatenation of all dependent regions in which date and time exchanges are to be performed. a. Before submitting the job, edit the appropriate member to make any necessary changes including jobcard, SMPE PROC, and ZONE names. b. Submit the job. The job should complete with an SMP/E RC4. The assembly will complete with RC4, and the LINK will complete with RC8. SMP/E messages GIM31902I, GIM38201W, and GIM67301W can be ignored. c. Edit member XGLNKPCC or XGLNKPC1 for IMS 8.1 and above, making any necessary JCL changes. The SYSLIB DD statement should point to the same RESLIB used in the XGIMSSxx/XGIMSxxx job. d. Submit XGLNKPCC or XGLNKPC1 for IMS 8.1 and above to link module XGIMSTFR into DFSPCC20. This job should complete with RC0. e. Go to substep 15 on page 3-23. 13. Find CPWR.MLXGnnn.SLXGCNTL member: – – – – XGPCC20U for IMS releases prior to 8.1 or XGPCC20X for IMS 8.1 through IMS 10.1 or XGPCC20B for IMS 11.1 through IMS 13.1 or XGPCC20E for IMS 14.1 and above. It contains JCL to install the Xchange interface with IMS module DFSPCC20. 14. Before submitting the job, edit the XGPCC20U, XGPCC20X, XGPCC20B, or XGPCC20E member selected in the previous step, changing the DSNs to conform to your site’s standards and making the changes required in the following three job steps: a. Use IEBUPDTE to create a temporary copy, SYSUT2, of IMS module DFSPCC20. SYSUT1 must point to the dataset containing the current source code for DFSPCC20. b. Assemble the updated temporary copy of DFSPCC20 created in step a. c. Link edit the new DFSPCC20 object module created in step b. Compuware recommends that the SYSLMOD DD statement for this step point to a library other than your normal IMS RESLIB. The selected library should then be included ahead of your normal IMS RESLIB in the IMS STEPLIB concatenation of all dependent regions in which date and time exchanges are to be performed. 15. Ensure your site’s MPP jobnames are defined as jobs to Xchange external security as described in “Step 14. Configure Xchange External Security”. The user who submits the job that starts the MPP must have update access to the Xchange pseudo-dataset name. 16. Recycle the IMS system and execute the necessary /MODIFY PREPARE and /MODIFY COMMIT commands to activate your new control blocks. 3-24 Xpediter/Xchange Installation and User Guide Step 11. Enable Enterprise PL/I DATE or DATETIME Built-in Function Support Xchange supports both the DATE and DATETIME built-in functions of Enterprise PL/I. Enterprise PL/I DATE Built-in Function Support Notes: • If your site does not require date/time exchanges for the Enterprise PL/I DATE builtin function, you may skip this section and review “Enterprise PL/I DATETIME Builtin Function Support” on page 3-24. • If your site is using Language Environment 1.9 or above with the Enterprise PL/I DATE built-in function, you may skip this section and review “Enterprise PL/I DATETIME Built-in Function Support” on page 3-24. A zap to LE module CEEEV003 is required if you want to exchange the Enterprise PL/I DATE built-in function while running with Language Environment 1.8 or below. To enable this support, perform the following steps: 1. Compuware recommends that a copy of the load module CEEEV003 be placed in its own library and this zap be applied to that copy. CEEEV003 can be found in the LE SCEERUN library. 2. This zap works in conjunction with Xchange’s Enhanced STCK Support. See “Enabling Xchange SVC” on page 4-3. 3. Run the job contained in dataset CPWR.MLXGnnn.SLXGCNTL member XGZENTPL. Follow the directions contained in the comments of the job. Editing of the CPWR.MLXGnnn.SLXGDATA member XGZAPPLI is required in order to supply the user SVC number to be used by the Enhanced STCK Support. 4. Concatenate the library with the zapped version of CEEEV003 before the normal LE SCEERUN library. Only use this zapped copy of CEEEV003 when Xchange is required to support the PL/I DATE built-in function. Note: Whenever maintenance is applied to LE, make a copy of CEEEV003 and reapply this zap to that new copy. Enterprise PL/I DATETIME Built-in Function Support Notes: • If your site does not require date/time exchanges for the Enterprise PL/I DATETIME built-in function, you may skip this step. • If your site is using the Enterprise PL/I DATETIME built-in function without any date/time patterns, you may skip this step. An example without a date/time pattern is DATETIME(). An example with a date/time pattern is DATETIME(YYYYMMDD). A zap to LE module CEEEV003 is required if you want to exchange the Enterprise PL/I DATETIME built-in function while using date/time patterns. To enable this support, perform the following steps: 1. Compuware recommends that a copy of the load module CEEEV003 be placed in its own library and this zap be applied to that copy. CEEEV003 can be found in the LE SCEERUN library. 2. This zap works in conjunction with Xchange’s Enhanced STCK Support. See “Enabling Xchange SVC” on page 4-3. 3. Run the job contained in dataset CPWR.MLXGnnn.SLXGCNTL member XGZENTPL. Follow the directions contained in the comments of the job. Editing of the CPWR.MLXGnnn.SLXGDATA member XGZAPPLI is required in order to supply the user SVC number to be used by the Enhanced STCK Support. Configuring Xchange 3-25 4. Concatenate the library with the zapped version of CEEEV003 before the normal LE SCEERUN library. Only use this zapped copy of CEEEV003 when Xchange is required to support the PL/I DATETIME built-in function. Note: Whenever maintenance is applied to LE, make a copy of CEEEV003 and reapply this zap to that new copy. Step 12. Enable C time() Function Support Note: If your site does not require date/time exchanges for the C time() function, you may skip this step. A zap to LE module CEEEV003 is required if you want to exchange the C time() function. If you have already performed these steps for the PL/I DATE or DATETIME Built-in function support, then skip to step 4. Otherwise, to enable this support, perform the following steps: 1. Compuware recommends that a copy of the load module CEEEV003 be placed in its own library and this zap be applied to that copy. CEEEV003 can be found in the LE SCEERUN library. 2. This zap works in conjunction with Xchange’s Enhanced STCK Support. See “Enabling Xchange SVC” on page 4-3. 3. Run the job contained in dataset CPWR.MLXGnnn.SLXGCNTL member XGZENTPL. Follow the directions contained in the comments of the job. Editing of the CPWR.MLXGnnn.SLXGDATA member XGZAPPLI is required in order to supply the user SVC number to be used by the Enhanced STCK Support. 4. Concatenate the library with the zapped version of CEEEV003 before the normal LE SCEERUN library. Only use this zapped copy of CEEEV003 when Xchange is required to support the C time() function. Note: Whenever maintenance is applied to LE, make a copy of CEEEV003 and reapply this zap to that new copy. Step 13. Enable Natural Support Note: Natural is an application development and deployment environment from Software AG. If your site does not require Natural support, you may skip this step. To provide support for Natural date/time requests, Xpediter/Xchange supplies its own version of the Natural CMCOTIME exit. The Xchange version of the CMCOTIME exit must be linked into the Natural nucleus and enabled as follows: 1. The Xpediter/Xchange version of the CMCOTIME exit is named XGCOTIME and is located in the CPWR.MLXGnnn.SLXGLOAD library. As shown in Figure 3-3, an INCLUDE card pointing to the Xchange load library and the XGCOTIME member is required for the re-linking of the Natural nucleus. 2. Set the Natural TD parameter to TD=0. 3-26 Xpediter/Xchange Installation and User Guide Figure 3-3. Xchange Link Edit Cards to Re-Link the Natural Nucleus // JCL required // to re-link the // Natural nucleus //XGLIB DD DISP=SHR,DSN=CPWR.MLXGnnn.SLXGLOAD //SYSIN DD * INCLUDE XGLIB(XGCOTIME) (REST OF THE LINK EDIT CARDS TO RE-LINK THE NATURAL NUCLEUS) Step 14. Configure Xchange External Security If you are using an external security package (such as RACF, CA-ACF2®, or CA-TOP SECRET ®) at your installation, you will need to configure Xchange with the package. Xchange makes external security calls to protect jobs, steps, and programs from unauthorized execution using date and time modification. External security is invoked by Xchange when the job designated in a pattern job request executes an SVC11 or other TIME services call — not when the request is created. You can define a default action that is taken whenever a job selected by Xchange is not covered by a security access rule. You can specify that all such jobs are allowed either to run or to fail. When you create the Xchange CMSC PARMLIB member, the following security options are available: • SECUSE=NO does not activate external security checking. If you specify this parameter, the SECDFLT parameter is ignored. • SECUSE=YES activates external security checking. The following choices are then available for the SECDFLT parameter: – SECDFLT=ALLOW sets the security default to allow jobs that are not covered by a security rule to have their dates and times changed by Xchange. – SECDFLT=DENY sets the security default to fail date and time change requests that are not covered by a security rule. Sites using CA-TOP SECRET should check their facility definitions and ensure that the RES/NORES option is set to RES. If this option is set to NORES, DB2 and IMS date and time simulations will not occur properly. Sites using ACF2 must set up SAFDEF records similar to the following: SAFDEF.XCHANGE FUNCRET(0) FUNCRSN(0) ID(XCHANGE) MODE(GLOBAL) PROGRAM(-) RACROUTE(REQUEST=AUTH CLASS=DATASET) RB(-) RETCODE(4) If your site uses the ACF2 Command List Table, define the following TSO commands: • XGIPGM01 • XGIZAPL • XGIZAPA Consult your ACF2 administrator. Defining Security Rules The SECPFX parameter is used to define a one- to eight-character prefix for security pseudo-dataset names (see “SECPFX” on page 3-8). The default of CWXG can be changed Configuring Xchange 3-27 to suit site requirements. Whatever prefix is chosen should be unique in that it does not duplicate any existing dataset name prefix within the installation’s system. Note: If RACF is the security access method you are using, this prefix must be defined as a group or user ID to RACF. A pseudo-dataset name is built for each Xchange request. Its format is prefix.jobname.stepname.procstep.pgmname The values for jobname, stepname, procstep, and pgmname are taken from the Xchange request specified for the step and from the system at the time the job makes an SVC11 or other TIME services call. Notes: • If a job is being run as a started task and has no procstep, the pseudo-dataset name would have the format prefix.jobname.stepname.pgmname • To prevent a TSO userID from being exchanged, deny update access to the pseudodataset name prefix.userID.**. User ID Access The user ID of a pattern job request’s owner must have update access to the pseudodataset name generated by Xchange. Otherwise they will be prevented by external security from using Xchange to make a date and time change. The following scenario provides a basic overview of how Xchange would work with a typical site’s external security package: 1. An Xchange user creates a pattern job request. 2. A job step included in the request makes an SVC11 or other TIME services call. 3. Xchange builds a pseudo-dataset name as described above. 4. Xchange invokes the external security package to verify that the request owner’s user ID has authority for update access to the pseudo-dataset name. 5. If the request owner’s user ID is authorized for update access to the pseudo-dataset name, Xchange makes the date and time change. Otherwise, the date and time for the step are not exchanged. The pseudo-dataset name must be defined as CLASS=DATASET and, as such, must not duplicate any real dataset names defined to the security system. Duplication is avoided by using the SECPFX parameter to specify a unique pseudo-dataset name prefix. The user ID under which the target job runs plays no part in the Xchange security checking. For that reason, it does not matter who submits the target job. It can be submitted by any production or testing mechanism, including a job scheduling package. If the Xchange batch facility is used to make the request, the user who submits the job will always be the same one who made the request. That user must have update access to the Xchange pseudo-dataset name. Defining Security Rules for Jobclass Support If Xchange is configured to use external security (SECUSE=YES, SECDFLT=DENY), you must define additional profiles/rules to your security system in order to be able to use the line commands on the Simulated Date Time Settings screen in jobclass format. As explained above, the SECPFX parameter is used to define a one- to eight-character prefix for security pseudo-dataset names (see “SECPFX” on page 3-8). The default of 3-28 Xpediter/Xchange Installation and User Guide CWXG can be changed to suit site requirements. Whatever prefix is chosen should be unique in that it does not duplicate any existing dataset name prefix within the installation’s system. Note: If RACF is the security access method you are using, this prefix must be defined as a group or user ID to RACF. A pseudo-dataset name is built for each Xchange jobclass request. Its format is: prefix.JOBCLASS.#x or prefix.JOBCLASS.#class1.#class2 The x in #x represents a valid 1- to 7-character job class. Valid default job classes are A to Z and 0 to 9. The class1 in #class1 represents the first 7 characters of an 8-character job class, and class2 in #class2 represents the last character of an 8-character job class. Your Xchange administrator — or whoever will be responsible for enabling, disabling, and resetting jobclass Xchange requests — must have update access to the pseudo-dataset name generated by Xchange. If they do not, a NAUT (not authorized) error message will be displayed in the Imsg field of the Simulated Date Time Settings screen in jobclass format when a line command is entered for the corresponding jobclass. For example, with SECPFX=CWXG the following profiles/rules could be defined to your external security package: CWXG.JOBCLASS.** All jobclasses would be eligible for Xchange jobclass requests. CWXG.JOBCLASS.#A Jobclass A would be eligible for Xchange jobclass requests. CWXG.JOBCLASS.#P Jobclass P would be eligible for Xchange jobclass requests. CWXG.JOBCLASS.#0 Jobclass 0 would be eligible for Xchange jobclass requests. Once a JOBCLASS is activated with the H line command, any user can submit jobs in that jobclass for date and time exchange. There are no other security checks made by Xchange for jobs being exchanged under jobclass support. Defining Security Rules for DB2 Distributed Data Facility (DDF) Support If Xchange is configured to use external security (SECUSE=YES, SECDFLT=DENY), and the DDF parameter is set to YES, you must define additional profiles/rules to your security system in order to exchange entries that are added by the DDF format of the Simulated Date Time Settings screen. As explained above, the SECPFX parameter is used to define a one- to eight-character prefix for security pseudo-dataset names. (For more information, see “SECPFX” on page 3-8). The default of CWXG can be changed to meet site requirements. Whatever prefix is chosen should be unique in that it does not duplicate any existing dataset name prefix in the installation’s system. Note: If RACF is the security access method you are using, this prefix must be defined as a group or user ID to RACF. A pseudo-dataset name is built for each Xchange DDF request. Xchange will use a pseudodataset name constructed according to one of the following two rules in which ccbresnm is the abbreviation for the resource name field value and db2ssid is the abbreviation for the DB2 SSID field value. • If the correlation ID is comprised of a valid jobname identifier followed by spaces, the pseudo-dataset name format is: prefix.jobname.#.ccbresnm.db2ssid • Otherwise, the correlation ID’s contents is translated and split as follows: Configuring Xchange – – – – 3-29 Numbers, uppercase letters, #, $, and @ remain unchanged Lowercase letters are translated to uppercase All remaining characters are translated to a # The resultant twelve-byte field is split into two six-byte fields, ccbcor1 and ccbcor2. The pseudo-dataset name format is: prefix.#ccbcor1.#ccbcor2.ccbresnm.db2ssid Example 1 Assume the SECPFX parameter is set to CWXG. The correlation ID and resource name of the job making the DB2 SQL DDF request are TSOUSR1A and XGBCHDB2, respectively. Assume the Xchange DDF request is being restricted to DB2 Subsystem D14G. Because TSOUSR1A satisfies the rules for being a valid jobname, the first rule above is used to generate the following pseudo-dataset name: CWXG.TSOUSR1A.#.XGBCHDB2.D14G Example 2 Again assume the SECPFX parameter is set to CWXG. The correlation ID and resource name of the job making the DB2 SQL DDF request are javaw.exe and DISTSERV, respectively. Because javaw.exe does not satisfy the rules for being a valid jobname, the second rule above is used to generate the following pseudo-dataset name: CWXG.#JAVAW#.#EXE###.DISTSERV In this example, javaw.exe becomes JAVAW#EXE### because the period and spaces become #s, and the lowercase letters are uppercased. It is then split into two six-byte fields, JAVAW# and EXE###. Resource Rules Generic resource rules apply to the Xchange security pseudo-dataset names. For complete protection, an installation could specify SECDFLT=DENY, define each dataset resource, and allow only specific user IDs to have update access to those resources. Another alternative would be to define a security rule for a “catch all” pseudo-dataset name that would apply if no other more restrictive pseudo-dataset name rule could be applied. This pseudo-dataset name would be specified as CWXG.**, where CWXG is the value of the SECPFX parameter. The security rule for this pseudo-dataset name would be defined with universal access (UACC) equal to NONE, and no user IDs or groups would have update access to it. More restrictive security rules could be defined. For example, assume that an installation has a set of jobs for payroll processing, and job names for these jobs are PAYPROD (for production runs) and PAYTEST (for test runs). Xchange protects the installation’s PAYPROD jobs so that these jobs never have their dates and times modified, while allowing certain user IDs or groups the ability to modify the dates and times of PAYTEST jobs. The installation would define CWXG.PAYPROD.** as UACC=NONE with no user IDs or groups having update access. CWXG.PAYTEST.** would be defined as UACC=NONE with selected user IDs and groups having the required update access. PROCSTEP and STEP names can also be reflected in the security pseudo-dataset name. For example, assume a production job named ACCTPROD has a step named UPDATE that executes a PROC. This PROC has a step named NAMAST. The pseudo-dataset name security rule to protect the step would be CWXG.ACCTPROD.UPDATE.NAMAST.**. Program names are specified last on the security rule’s pseudo-dataset name. To protect a program named UPDTPGM, specify a pseudo-dataset name of CWXG.**.UPDTPGM. 3-30 Xpediter/Xchange Installation and User Guide With these security rules, complete protection of the installation’s jobs can exist, while still allowing authorized users to run jobs with dates and times modified. Designating Administrators Only Xchange administrators can perform the following functions: • • • • • Delete pattern requests and jobs created by a different user ID Input operator commands from the batch facility Reset pattern requests on the ISPF interface created by a different user ID Delete all completed entries on the ISPF interface for jobs not active Force active pattern requests and their executing requests on the ISPF interface to become inactive/queued and completed. Xchange administrators have user IDs with update access to the model dataset entity name XGADMIN. XGADMIN has been prefixed by the SECPFX parameter. For example, if SECPFX is specified as CWXG, and an installation wants user IDs USER1 and USER2 to be Xchange administrators, the installation would define a dataset model named CWXG.XGADMIN and would give update access to USER1 and USER2. To give administrator functions to all user IDs, the installation would define a dataset model named CWXG.XGADMIN and would give it universal access equal to UPDATE. To prohibit administrator functions from all user IDs, the installation would define a dataset model named CWXG.XGADMIN with universal access equal to NONE. Note: If external security is not activated (SECUSE=NO), all user IDs are considered Xchange administrators. Step 15. Update the Xpediter/TSO LIBDEF Note: If your site does not use Xpediter/TSO, you may skip this step. This step configures Xpediter/Xchange to allow users to invoke it from within an Xpediter/TSO session by typing XCHANGE on the COMMAND line and pressing Enter. Syntax and options for using the XCHANGE command are discussed in “Using the Xpediter/TSO Interface” on page 5-67. If you did not allocate the Xchange logon CLISTs in the second part of “Step 4. Update TSO CLISTs” on page 3-12, you must also add allocation LIBDEF statements for the datasets listed in Table 3-3 to your Xpediter/TSO startup CLIST: Table 3-3. Xpediter/TSO CLIST Allocations Allocation Dataset ISPPLIB CPWR.MLXGnnn.SLXGPNL ISPMLIB CPWR.MLXGnnn.SLXGMSG ISPLLIB CPWR.MLXGnnn.SLXGLOAD Step 16. Assemble a Journal Exit Note: You may skip this step if you want to use the supplied exit or if you specified NO for the XGJEXIT1 parameter in “Step 1. Specify Xchange Parameters” on page 3-2. When a journal record is to be written for an SVC11, an exit can be invoked to determine the program ID to be reported. Source code for this journal exit is provided in member XGJEXIT1 of the CPWR.MLXGnnn.SLXGDATA PDS. The supplied exit moves up the save area chain until a program is found that does not begin with the characters ILB (OS COBOL), IGZ (COBOL II), CEE (LE), or IBM (PL/I). This results in more meaningful entries in the journal dataset. Configuring Xchange 3-31 If you specify YES for the XGJEXIT1 parameter (see “Step 1. Specify Xchange Parameters” on page 3-2), Xchange will use the XGJEXIT1 journal exit. If you specify NO (YES is the default), the journal exit will not be invoked and the journal will list library routines instead of the programs that actually made the system date and time requests. If the supplied exit does not meet your needs, you can make modifications to the source in XGJEXIT1. CAUTION: Use care in modifying the Xchange journal exit. Improper coding could cause system outage. After any necessary modifications have been made, assemble and link your journal exit from the source in member XGJEXIT1. The modified journal exit will become effective the next time the Xchange subsystem is started. Step 17. Assemble or Compile and Link Edit Test Programs Note: If your site does not require programs for demonstrating Xchange, you may skip this step. The CPWR.MLXGnnn.SLXGSAMP files comprise programs in various programming languages that you can use to validate Xchange functionality. The PDS member names suggest the languages used, and the comment box in each file briefly describes the file. Compile and link the members listed in Table 3-4 to create a system that can be used to demonstrate Xchange batch functionality: Table 3-4. Test Programs Member Name Description CWXGCOB The driver program. CWXGDATE and CWXGSUBC Called subprograms. CWXGDATA Data used in the system. CWXGJCLC JCL to run the system. XGBASM An Assembler program. XGBASMLE A High-Level Assembler program for LE. XGBCOBLE A COBOL program for LE. XGBPLI A PLI program. XGBPLILE A PLI program for LE. XGBCHDB2 A program with DB2 calls. Note: If your site has Xpediter/TSO or Xpediter/CICS and you want to use them with the test programs listed in this step, compile the programs with the appropriate Compuware Shared Services language processor(s). For more details, see the Compuware Shared Services Installation and Customization Guide. CICS Transaction Support Test Programs Note: If your site does not require CICS transaction support, you may skip the rest of this step. Compile and link the programs listed in Table 3-5 for use in demonstrating Xchange CICS transaction support. 3-32 Xpediter/Xchange Installation and User Guide The resource definitions for the following programs or transactions were already added in “Step 7. Enable CICS Transaction Support” on page 3-15. Table 3-5. CICS Transaction Support Test Programs Program Name or Description Transaction Name XGDEMCBL A COBOL program with a transaction ID of XGCB. XGDEMASM The main Assembler program that links to XGLINKTD or transfers control to XGXCTLTD. The transaction ID for XGDEMASM is XGAS. XGLINKTD An Assembler program that links to XGLINK02. XGLINK02 An Assembler program. XGXCTLTD An Assembler program. XGCCOBLE A COBOL program for LE. The transaction ID for XGCCOBLE is XGCL. XGCPLI A PLI program with a transaction ID of XGPL. XGCPLILE A PLI program for LE. The transaction ID is XGPE. XGCDB2 A program with DB2 calls. XGCD is the transaction ID. IMS Message Level Support Test Programs Note: If your site does not require IMS Message Level Support, you may skip the rest of this step. The test programs listed in Table 3-6 are provided for use in demonstrating Xchange IMS Message Level Support. Table 3-6. IMS Message Level Support Test Programs Program Name and Language Application Transaction Name XGIASM Assembler XGICOB COBOL (non-LE) XGIPLI PL/I XGICOBLE COBOL (LE) To set up these test programs, perform the following steps: 1. Define the Xchange IMS test programs and their associated transactions to IMS. a. Edit the definitions found in CPWR.MLXGnnn.SLXGDATA member XGIDEFT, substituting the desired message class codes for each occurrence of xx, then add those definitions to the appropriate section of your site’s IMS STAGE 1 SYSGEN input stream. b. Perform an IMS CTLBLKS gen. 2. Perform PSBGENs for the Xchange IMS test programs using your site’s standard PSBGEN utility JCL. Use CPWR.MLXGnnn.SLXGDATA member XGIDEFP as input to the PSBGEN utility. 3. Generate the appropriate ACB control blocks for the Xchange IMS test programs using your site’s standard ACBGEN utility. 4. Run the IMS online change utility to load the control blocks you have generated into the inactive IMS system libraries. These control blocks are ACBLIB and MODBLKS. 5. Assemble and compile the IMS test programs using your site’s standard JCL. Configuring Xchange 3-33 6. Use CPWR.MLXGnnn.SLXGDATA member XGIMFS as the MFS source to your site’s standard JCL for running an MFSGEN. Run this job and verify that the MFS output is correctly created. 7. Recycle the IMS system and/or execute the necessary /MODIFY PREPARE and /MODIFY COMMIT commands to activate your new control blocks. 3-34 Xpediter/Xchange Installation and User Guide 4-1 Chapter 4. Starting and Terminating Xchange Chap 4 This chapter describes how to start and terminate Xpediter/Xchange. It also explains how to enable Xchange Enhanced STCK, STCKE, and STCKF Support. Xchange consists of three separate entities: • Subsystem (long-running address space) • ISPF interface • Replacements for the IBM-supplied TIME services The subsystem must be active whenever any Xchange processing occurs. Any number of Xchange subsystems can be active in a single MVS complex at the same time, but each must have a unique subsystem name. Compuware recommends, however, that only one subsystem be active at a time. You can start the Xchange subsystem either by submitting it as a normal batch job, or by initiating it from the operator console as a started task. Compuware recommends running Xchange as a started task or a high priority batch job in order to avoid any negative impact from higher priority systems or jobs. Terminate Xchange with the SHUTDOWN command, as described in “Terminating Xchange” on page 4-4. Compuware recommends you not use the MVS CANCEL command to terminate Xchange. Note: After you start Xchange, you then need to invoke it, as described in Chapter 5, “Using Xchange”. Starting Xchange This section provides instructions for starting Xchange as a batch job or as a started task. Note: For the Xchange subsystem to properly detect job starts and completions, your site must run with the MVS system commands MONITOR JOBNAMES and MONITOR SESS. Consult your site’s MVS system programmer. Starting Xchange as a Batch Job Starting Xchange as a batch job provides a convenient way to test new releases of the product. Be sure to include the TIME=1440 parameter shown to prevent the job from exceeding the CPU time limit (MVS abend S322). Figure 4-1 details sample JCL to initiate Xchange as a submitted job. This JCL is contained in XGSTART in CPWR.MLXGnnn.SLXGCNTL. For more information on the optional PARM fields used to install and activate STCKSYNC, STCKE, and Enhanced STCK, STCKE, and STCKF Support, see “Enabling Xchange SVC” on page 4-3. 4-2 Xpediter/Xchange Installation and User Guide Figure 4-1. Sample Batch Execution JCL (XGSTART) //* ==> INSERT JOB CARD HERE //* //********************************************************************* //* XPEDITER XCHANGE USER: * //* * //* YOU CAN USE THIS JCL TO ACTIVATE YOUR XCHANGE SUBSYSTEM. * //* * //* ADD A VALID JOB CARD. * //* * //* OPTIONALLY, CODE THE PARM='SVCNUM=???,RUNTYPE=INSTALL' * //* (WHERE ??? IS THE XCHANGE SVC NUMBER.) THE PARM IS REQUIRED TO * //* INSTALL / ACTIVATE THE XCHANGE SVC (NECESSARY FOR STCKSYNC * //* AND ENHANCED STORE CLOCK SUPPORT). - SEE 'ENABLING XCHANGE * //* SVC' FOR FURTHER INFORMATION ON THE PARM FIELDS. * //* * //* OPTIONALLY, CODE THE PARM='SVCENM=???,RUNETYP=INSTALL' * //* (WHERE ??? IS THE XCHANGE SVC NUMBER.) THE PARM IS REQUIRED TO * //* INSTALL / ACTIVATE THE XCHANGE SVC (NECESSARY FOR ENHANCED * //* STORE CLOCK EXTENDED SUPPORT). THESE PARM FIELDS CAN BE * //* INCLUDED ON THE PARM WITH THE PARM FIELDS FOR STCKSYNC * //* SUPPORT. - SEE 'ENABLING XCHANGE SVC FOR FURTHER INFORMATION * //* ON THE PARM FIELDS. * //* * //* OPTIONALLY, CODE 'SUFFIX=????' ON ONE OF THE PARMS PROVIDED TO * //* OVERRIDE THE DEFAULT XCHANGE COMPUWARE MAINFRAME SERVICES * //* CONTROLLER (CMSC) PARM MEMBER, WHERE ???? SPECIFIES A * //* 4-CHARACTER SUFFIX OF THE XCHANGE CMSC PARMLIB MEMBER INCLUDING * //* TRAILING SPACES IF NECESSARY. * //* * //* OPTIONALLY, UNCOMMENT THE "//*CWSC???? DD DUMMY" STATEMENT IF * //* YOU WISH TO OVERRIDE THE DEFAULT CMSC IN WHICH XCHANGE WILL * //* RETRIEVE PARAMETERS, WHERE ???? SPECIFIES THE 4-CHARACTER CMSC * //* IDENTIFIER FOR THE CMSC ADDRESS SPACE IN WHICH XCHANGE WILL * //* RETRIEVE PARAMETERS. * //* * //* USE ISPF 'CHANGE ALL' TO REPLACE CPWR TO THE HIGH-LEVEL DSN * //* NODE OF YOUR APF AUTHORIZED XCHANGE LOAD LIBRARY. * //* * //* USE ISPF 'CHANGE ALL' TO REPLACE 'CUSTOMER.SAVEREST.FILE' WITH * //* THE FILE DSN YOU WISH TO USE WITH XPEDITER/XCHANGE. THIS * //* DATASET WAS CREATED USING 'ALLOCSAV' JCL. * //* * //* SUBMIT THE JOB. * //********************************************************************* //* //XCHANGE EXEC PGM=XGMMAIN, //* PARM='SUFFIX=????', //* PARM='SVCNUM=???,RUNTYPE=INSTALL', //* PARM='SVCNUM=???,RUNTYPE=INSTALL,SUFFIX=????', //* PARM='SVCENM=???,RUNETYP=INSTALL', //* PARM='SVCENM=???,RUNETYP=INSTALL,SUFFIX=????', //* PARM='SVCNUM=???,RUNTYPE=INSTALL,SVCENM=???,RUNETYP=INSTALL', //* PARM='SVCNUM=???,RUNTYPE=INSTALL,SVCENM=???,RUNETYP=INSTALL,S+ //* UFFIX=????', // TIME=1440 //* //STEPLIB DD DSN=CPWR.MLXGnnn.SLXGAUTH,DISP=SHR //* //XGSAV001 DD DSN=CUSTOMER.SAVEREST.FILE,DISP=SHR //* //*CWSC???? DD DUMMY // Starting and Terminating Xchange 4-3 In the example shown in Figure 4-1 on page 4-2, you must provide the following information: • Your APF authorized library in place of CPWR.MLXGnnn.SLXGAUTH. For more information, see “Designate an APF Authorized Library” on page 1-8. • Your save/restore dataset in place of CUSTOMER.SAVEREST.FILE. For more information, see “Step 6. Allocate the Save/Restore Dataset” on page 3-14. Starting Xchange as a Started Task Starting Xchange as a started task automatically executes the product at IPL and uses no initiators. Also, started tasks are not constrained by batch performance values. To execute Xchange from the operator console as a started task, place the procedure shown in Figure 4-2 in the appropriate procedure library (PROCLIB). Be sure to include the TIME=1440 parameter shown to prevent the job from exceeding the CPU time limit (MVS abend S322). For more information on the optional PARM fields used to install and activate STCKSYNC, STCKE, and Enhanced STCK, STCKE, and STCKF Support, see “Enabling Xchange SVC” on page 4-3. Figure 4-2. Sample Command Procedure to Initiate Xchange //XCHANGE PROC //IEFPROC EXEC PGM=XGMMAIN,TIME=1440,PARM='SVCNUM=???,RUNTYPE=INSTALL' //STEPLIB DD DSN=CPWR.MLXGnnn.SLXGAUTH,DISP=SHR //XGSAV001 DD DSN=customer.saverest.file,DISP=SHR In the example shown in Figure 4-2, you must provide the following information: • Your APF authorized library in place of CPWR.MLXGnnn.SLXGAUTH. For more information, see “Designate an APF Authorized Library” on page 1-8. • Your save/restore dataset in place of customer.saverest.file. For more information, see “Step 6. Allocate the Save/Restore Dataset” on page 3-14. Enabling Xchange SVC Xchange provides support for Enhanced STCK Support for date/time simulation of Assembler STCK operation code and STCKSYNC macro support. STCK and STCKSYNC support are implemented with one SVC. The SVC is installed as part of the Xchange startup JCL. 1. Consult your site’s system programmer for an available SVC number between 200 and 255. Ensure the SVC number chosen will not be used by any other product. 2. Edit the JCL shown in Figure 4-2 on page 4-3, replacing the ??? values on the field SVCNUM with the SVC number. 3. Specify INSTALL or REFRESH for RUNTYPE. Use INSTALL unless specifically told to use REFRESH by Xchange Customer Support. When INSTALL is used, a check is done to see if the SVC is installed. If it is not installed, Xchange will dynamically install the specified SVC. The SVC will remain installed until the next system IPL. Between IPLs, using INSTALL during the startup of Xchange ensures that the SVC is installed. 4-4 Xpediter/Xchange Installation and User Guide 4. When you are ready to start Xchange, submit the revised JCL. Xchange provides support for Enhanced STCKE Support for date/time simulation of Assembler STCKE operation code and STCKE macro support. The SVC is installed as part of the Xchange startup JCL. 1. Consult your site’s system programmer for an available SVC number between 200 and 255. Ensure the SVC number chosen will not be used by any other product. 2. Edit the JCL shown in Figure 4-2 on page 4-3, replacing the ??? values on the SVCENM field with the SVC number. 3. Specify INSTALL or REFRESH for RUNETYP. Use INSTALL unless specifically told to use REFRESH by Xchange Customer Support. When INSTALL is used, a check is done to see if the SVC is installed. If it is not installed, Xchange will dynamically install the specified SVC. The SVC will remain installed until the next system IPL. Between IPLs, using INSTALL during the startup of Xchange ensures that the SVC is installed. 4. When you are ready to start Xchange, submit the revised JCL. Note: If Xchange is started without installing the SVC, any zapped modules using Enhanced STCK or STCKE Support will fail with an Sfxx abend, where xx is the hex representation of the SVC number used in the zap. For information on how to use Enhanced STCK or STCKE Support, see “Enhanced STCK Support” on page 5-70. Terminating Xchange Xchange can be terminated from the operator console. An Xchange administrator can also terminate Xchange from the batch facility. For information on designating Xchange administrators, see “Designating Administrators” on page 3-30. Compuware recommends you not use the MVS CANCEL command to terminate Xchange. If Xchange save/restore processing is enabled, a final checkpoint save of the Xchange requests dataset will be done as part of shutdown. This ensures that all Xchange requests are retained, even though the normal save interval may not have elapsed. This checkpoint save does not take place, however, if Xchange is terminated with an MVS CANCEL or if Xchange abends. Note: If CICS transaction support is active, an authorized user must enter the STOP primary command on the Simulated Date Time Settings screen for CICS before terminating Xchange. See “Primary Commands” on page 5-55. Terminating Xchange From the Operator Console If the REPLY parameter of the Xchange CMSC PARMLIB member is set to YES as described in “Step 1. Specify Xchange Parameters” on page 3-2, Xchange will leave the following Write-To-Operator with Reply (WTOR) message outstanding on the master console: nn XG9999 ssid ENTER XCHANGE COMMAND where nn is the message sequence number required for the SHUTDOWN operator command and ssid is the subsystem ID. You can terminate Xchange by terminating the Xchange address space with the SHUTDOWN operator command. Type the SHUTDOWN command on the master console in the following format: Starting and Terminating Xchange 4-5 R nn,SHUTDOWN xxxxxx In this command line, nn is the message sequence number from the outstanding WTOR message described above and xxxxxx is either NORMAL (the default) or IMMED. The NORMAL parameter terminates Xchange when all queued and active jobs have ended or have been deleted from the Simulated Date Time Setting screen (see “Specifying Requests in ISPF” on page 5-4 for more information). Xchange does not terminate until these conditions are met. The IMMED parameter immediately terminates Xchange. Active jobs continue to run. After Xchange terminates, any dates and times that are requested revert to the current system values. You can also specify SHUTDOWN with an MVS MODIFY or STOP command. Specify SHUTDOWN as a MODIFY (F) command in the format as follows: F jobname,SHUTDOWN xxxxxx Specify SHUTDOWN as an MVS STOP (P) command in the format P jobname. In these MVS examples, jobname is the name of the Xchange batch job or started task and xxxxxx is either NORMAL (the default) or IMMED. Terminating Xchange From the Batch Facility If you are an Xchange administrator, you can terminate Xchange by using a batch job to input the SHUTDOWN command as a parameter. The SHUTDOWN command is processed as if it were entered by the console operator. Invoke the batch facility with the JCL shown in Figure 4-3. Figure 4-3. JCL to Terminate Xchange //STEPNAME EXEC PGM=XGBOPCMD,PARM=’request’ //SYSPRINT DD SYSOUT=* //STEPLIB DD DSN=CPWR.MLXGnnn.SLXGLOAD,DISP=SHR // You must provide information for the request variable, according to the following syntax: SUBSYS=ssid,OPCMD=SHUTDOWN xxxxxx where ssid is a four-character subsystem ID and xxxxxx is either NORMAL or IMMED. 4-6 Xpediter/Xchange Installation and User Guide 5-1 Chapter 5. Using Xchange Chap 5 This chapter explains how to work with Xpediter/Xchange. Using Xchange, you can set the values for the date and time you want to simulate. Then Xchange will substitute, or exchange, this value each time the programs you specified request the system date and time with a TIME macro, EXEC CICS ASKTIME, STCK, STCKE, or STCKF instruction, or DB2 call. You can tell by looking at the results of your application whether it handled the date change in an appropriate manner. If not, just make the necessary changes and test again using Xchange. There are six different ways of using Xchange’s ability to simulate “non-current” system dates and times: • • • • • • ISPF Interface Jobclass Support Batch Utility Xpediter/TSO Interface IMS Message Level Support With CICS. Xchange can also be used with programs that use the Assembler STCK, STCKE, or STCKF instruction. The seven sections in this chapter cover each of these topics. For information on starting and stopping Xchange, see Chapter 4, “Starting and Terminating Xchange”. CAUTION: Rolling back the date on a software product may be a violation of your licensing agreement. You should review the terms of your license agreement and contact the software licensor before attempting to roll back any dates. Xchange is not intended to be used in any manner that will violate your license agreement with another software licensor. Xchange Criteria The Xchange system applies certain rules or criteria to programs that have been selected for date and time modification. If these criteria are not met, Xchange does not modify the dates and times, but instead passes the time request to the appropriate IBM module for processing. Xchange always allows the target job to run and reports in the journal when it modifies dates and times. General Criteria Except under CICS transaction support and DB2 Distributed Data Facility (DDF) support, the following criteria apply: • The JOB name, STEP name, and PROCSTEP name must have been specified, either explicitly or implicitly, by one of the following methods: – A pattern job request on the Simulated Date Time Settings screen – The request parameter of an Xchange batch step added to the affected job – An XCHANGE command from within an Xpediter/TSO session • When a program requests date and time information, the following checks are made: 5-2 Xpediter/Xchange Installation and User Guide – The program name must have been specified, either explicitly or implicitly, as described above. – External security is checked (once per step). – The program must be executing in problem state, using protect keys 8 through 15. – The request for date and time must come from a load module that has been the target of a LOAD, LINK, XCTL, or ATTACH macro, or via the PGM parameter on the EXEC statement that initiated the job step. These last criteria are applied on a request-by-request basis. As such, any date and time request that does not meet these criteria will be passed to the appropriate IBM module, which will return the actual date and time to the requesting program. It is possible that undesirable results will occur if different load modules within a job step are supplied different dates and times. CICS Transaction Support Criteria For CICS transaction support, the following criteria apply: • The terminal, trans ID, user ID, and program name must have been specified, either explicitly or implicitly, on the Simulated Date Time Settings screen. • When a program requests date and time information, the following checks are made: – The request must come from a load module that has been the target of a CICS LINK or CICS XCTL. – The request must specify a terminal defined on the TERM parameter in the Xchange CMSC PARMLIB member. These last criteria are applied on a request-by-request basis. As such, any date and time request that does not meet these criteria will be passed to the appropriate IBM module, which will return the actual date and time to the requesting program. It is possible that undesirable results will occur if different CSECTs within a transaction are supplied different dates and times. DB2 Distributed Data Facility (DDF) Support Criteria For DB2 DDF support, the following criteria apply: • The correlation ID and resource name must have been specified, either explicitly or implicitly, on the Simulated Date Time Settings screen. • The Xchange DDF request must be entered on the LPAR that contains the DB2 subsystem which will execute the DB2 SQL CURRENT DATE, CURRENT TIME, or CURRENT TIMESTAMP special register request. • When a program makes a DB2 SQL CURRENT DATE, CURRENT TIME, or CURRENT TIMESTAMP special register request using the DB2 DDF, the request is checked and must match the correlation ID, the resource name, and the DB2 subsystem ID if specified. These criteria are applied on a request-by-request basis. As such, any DB2 DDF SQL CURRENT DATE, CURRENT TIME, or CURRENT TIMESTAMP special register request that does not meet these criteria will be passed to the appropriate IBM module, which will return the actual CURRENT DATE, CURRENT TIME, or CURRENT TIMESTAMP value to the requesting program. Using Xchange 5-3 Using the ISPF Interface Xchange’s ISPF interface consists of a Simulated Date Time Settings screen that you use to make requests. The interface follows ISPF rules for navigation. An Xchange I000 message is placed in the JES2 job log the first time during program execution that Xchange simulates a date or time for a job step. The same message is sent to your terminal, but might not be seen unless you update your TSO profile. To enable viewing of I000 messages, type TSO PROFILE WTPMSG on the TSO COMMAND line and press Enter. Invoking the ISPF Interface To invoke Xchange from ISPF, the Xchange subsystem must be active and all productrelated ISPF libraries must be allocated during the logon process. The following Xchange product libraries are required to invoke Xchange from ISPF: • • • • Command List (CLIST) library Panel library Message library Program load library. The method you use to invoke Xchange from ISPF depends on the installation process and how you have set up the access method. You can invoke Xchange in a number of different ways, including: • • • • An option on an ISPF Option Menu screen (CMD(XCHANGE)) A TSO command on a command line A command from the TSO Command Processor screen (%XCHANGE) By entering the TSO EXEC 'CPWR.MLXGnnn.SLXGCLIB(XCHANGE)' command, replacing CPWR with the high-level qualifier chosen for your site and nnn with the release number identifier. You can also invoke the ISPF interface directly from an Xpediter/TSO session. This process is discussed in “Using the Xpediter/TSO Interface” on page 5-67. Subsystem Identification If your site has multiple active Xchange subsystems, the first time you invoke Xchange, the Subsystem Identification screen (Figure 5-1) appears. The ID you enter in the SUBSYSTEM ID field must match the ID of the authorized active subsystem. If you are unsure of the correct subsystem ID, consult your site’s Xchange administrator. Figure 5-1. Subsystem Identification Screen for the ISPF Interface           Xpediter/Xchange --------- Subsystem Identification -------------------------- COMMAND ===> SUBSYSTEM ID ===> Subsystem Id must consist of 4 unique alphanumeric characters Copyright (c) 2003, 2016 by Compuware Corporation. All rights reserved. Compuware Xpediter/Xchange release 17.02.00 5-4 Xpediter/Xchange Installation and User Guide Type the subsystem ID and press Enter. The Simulated Date Time Settings screen (Figure 5-3 on page 5-6) will be displayed. To use a different subsystem in subsequent Xchange sessions, invoke the Xchange CLIST with a subsystem ID parameter. Use the syntax XCHANGE SSID(ssid) where ssid is the ID of the desired subsystem. Specifying Requests in ISPF The Simulated Date Time Settings screen lets you specify requests for simulated system date and time scenarios for your applications. Figure 5-2 shows the format of the Simulated Date Time Settings screen. Figure 5-2. Simulated Date Time Settings Screen for the ISPF Interface Xpediter/Xchange ------ Simulated Date Time Settings ------- Row 1 to 14 of 14 COMMAND ===> SCROLL ===> PAGE System ID: AC12 Type Legal on the command line for Copyright/Trade Secret Notice Information Line Commands: S - Set H - Set and Hold R - Reset D - Delete A - Set Active Status Codes: Q - Queued P - Pending A - Active E - Executing * - Error C - Completed N - Not Active Filter: ******** ******** ******** ******** **** ** ** ** ** ** C/S Owner Jobname Stepname Procstep Program YYYY/MM/DD HH:MM:SS Jobno _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ ******************************* BOTTOM OF DATA ******************************** Each line is an entry where you can type information defining which portions of your application or applications are to be tested using Xchange. Each individual entry that you create is called a pattern job request. All the entries together constitute the request table. When you press Enter, the commands you put in the C portion of the C/S field are executed for each corresponding pattern job request. There are three aspects of Xchange operation that are especially important to understand: • Creating a pattern job request does not automatically run the specified job. • The date and time for a job specified in a pattern job request are exchanged no matter which user runs the job. The user ID in the OWNER field only indicates who created the Xchange request — not who initiated the job. The exception is requests created using the Xchange batch facility, which are displayed with the user ID of whoever ran the batch job. • If external security is used to verify the authority of a request’s owner, it is invoked by Xchange when the designated job executes an SVC11 or other TIME services call — not when the pattern job request is created. An online help facility and tutorial are available by pressing PF1 or typing HELP on the COMMAND line and pressing Enter. When you enter the HELP command, a list of contents is displayed, allowing you to navigate through the help facility. For contextsensitive field-level help, press PF1 when your cursor is in a field on the screen. The remainder of this section discusses four aspects of using the Simulated Date Time Settings screen: Using Xchange • • • • 5-5 line commands status codes fields PF keys. Line Commands Type line commands under the C portion of the C/S field (see “Fields” on page 5-6). The following line commands are available on the Simulated Date Time Settings screen: S Sets a pattern job request by adding it to the request table. The request is inactive once the job completes, but remains in the request table until you delete it with the D (Delete) line command. H Sets and holds a pattern job request by adding it to the request table. Unlike the S (Set) line command, this command allows the request to remain active once the job completes. The pattern job request and all related jobs remain until you delete them using the D (Delete) line command CAUTION: If you use the H line command to create a request on your own TSO userID, then log off TSO, you will be unable to delete that request when you log back on. To remove such a request, you must log off TSO and have the Xchange administrator delete it for you. R Resets a pattern job request. This command deletes an existing pattern job request and its related jobs, then adds the pattern job request back into the request table. The R command allows you to modify the values in the YYYY/MM/DD and/or HH:MM:SS fields of an existing pattern job request. No other fields can be modified using the R command. A request or job owned by a different user ID can only be reset by an Xchange administrator. For information on designating Xchange administrators, see “Designating Administrators” on page 3-30. D Deletes an existing pattern job request and its related jobs (if applicable). A request or job owned by a different user ID can only be deleted by an Xchange administrator. For information on designating Xchange administrators, see “Designating Administrators” on page 3-30. A Adds a pattern job request that defines a job that is already running (active). The active job request is added to the request table and becomes inactive only after a selected job completes and is removed from the active queue. The request remains in the request table until it is deleted. When you use this line command, the wildcard feature is prohibited for the Jobname field. F Entered on a pattern job request that is in A (Active) status. The command forces the status to C (Completed) for all executing requests associated with the A (Active) job pattern request. Job pattern requests that were initiated with the S (Set) line command will become N (Not Active) and job pattern requests initiated with the H (Set and Hold) line command will become Q (Queued). Also, the command forces the job that was being exchanged by the A (Active) job pattern request to stop exchanging its date and time. This line command may not be used on DDF requests and job pattern requests set with the A (Set Active) line command. This line command is only valid for users with Xchange administrator authority. For information on designating Xchange administrators, see “Designating Administrators” on page 3-30. Note: For details on how to exchange the date and time for CICS regions and individual CICS transactions, see “Using CICS Support” on page 5-51. 5-6 Xpediter/Xchange Installation and User Guide Status Codes Status codes appear under the S portion of the C/S field (see “Fields” on page 5-6). Any of the following status codes can appear: Q The pattern job request is queued. P The pattern job request is pending. A The pattern job request has an active job. E The pattern job request is executing. C The pattern job request has completed. The first completed (C) request entry with a particular job number indicates only that a jobstep was executed that matched the corresponding request. Each additional completed entry (if any) with the same job number is the result of one or more actual date/time exchanges. See Figure 5-3. N The pattern job request is not active. * The pattern job request contains an error. Figure 5-3. Completed Pattern Job Requests Xpediter/Xchange ------ Simulated Date Time Settings ------- Row 1 to 14 of 14 COMMAND ===> SCROLL ===> PAGE System ID: AC12 Type Legal on the command line for Copyright/Trade Secret Notice Information Line Commands: S - Set H - Set and Hold R - Reset D - Delete A - Set Active Status Codes: Q - Queued P - Pending A - Active E - Executing * - Error C - Completed N - Not Active Filter: ******** ******** ******** ******** **** ** ** ** ** ** C/S Owner Jobname Stepname Procstep Program YYYY/MM/DD HH:MM:SS Jobno _ Q YOURUID TSTJOB01 *_______ PROC01__ PRGM001_ 2004 02 29 __ __ __ _ C YOURUID TSTJOB01 *_______ PROC01__ PRGM001_ 2004 02 29 __ __ __ 12345 _ C YOURUID TSTJOB01 STEP001_ PROC01__ PRGM001_ 2004 02 29 __ __ __ 12345 _ C YOURUID TSTJOB01 STEP002_ PROC01__ PRGM001_ 2004 02 29 __ __ __ 12345 _ C YOURUID TSTJOB01 STEP003_ PROC01__ PRGM001_ 2004 02 29 __ __ __ 12345 _ Q YOURUID PAYRO*__ *_______ *_______ PAYRPT01 2000 01 01 __ __ __ _ C YOURUID PAYRO* *_______ *_______ PAYRPT01 2000 01 01 __ __ __ 12350 _ C YOURUID PAYROLLT PAYSTEP1 PAYPROC1 PAYRPT01 2000 01 01 __ __ __ 12350 _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ ******************************* BOTTOM OF DATA ******************************** Fields The Owner and Jobno fields and the S portion of the C/S field are display-only. You can type data into all other fields. The Filter row contains a series of mask fields, each corresponding to the column directly below it. Filter Jobname The mask for the Jobname field. The initial value is all asterisks, which directs Xchange to display all job requests for which the rest of the request entry fields match their corresponding masks. This mask is saved upon exit and restored upon entry. An asterisk represents a single wildcard character in the position of the jobname where it is placed. For example, masks TST***** and ***JOB** would each result in the display of all job requests associated with jobname TSTJOB01 — assuming the rest of the request entry fields match their masks. However the masks TST* , *JOB01 , and *JOB* , would each result in the display of no job requests for jobname Using Xchange 5-7 TSTJOB01, even if the rest of the request entry fields match their masks. Any character is valid in this field. Filter Stepname The mask for the Stepname field. The initial value is all asterisks, which directs Xchange to display all job requests for which the rest of the request entry fields match their corresponding masks. This mask is saved upon exit and restored upon entry. An asterisk represents a single wildcard character in the position of the stepname where it is placed. For example, masks STEP****, ****01 , and ****01** would each result in the display of all job requests associated with stepname STEP01 — assuming the rest of the request entry fields match their masks. However the masks STEP* , *01, and *01* would each result in the display of no job requests for stepname STEP01, even if the rest of the request entry fields match their masks. Any character is valid in this field. Filter Procstep The mask for the Procstep field. The initial value is all asterisks, which directs Xchange to display all job requests for which the rest of the request entry fields match their corresponding masks. This mask is saved upon exit and restored upon entry. An asterisk represents a single wildcard character in the position of the procstep where it is placed. For example, masks PROC****, ****01 , and ****01** would each result in the display of all job requests for procstep PROC01 — assuming the rest of the request entry fields match their masks. However the masks PROC* , *01, and *01* would each result in the display of no job requests for procstep PROC01 , even if the rest of the request entry fields match their masks. Any character is valid in this field. Filter Program The mask for the Program field. The initial value is all asterisks, which directs Xchange to display all job requests for which the rest of the request entry fields match their corresponding masks. This mask is saved upon exit and restored upon entry. An asterisk represents a single wildcard character in the position of the program where it is placed. For example, masks PRGM**** and ****0001 would each result in the display of all job requests for program PRGM0001 — assuming the rest of the request entry fields match their masks. However the masks PRGM* and *0001 would each result in the display of no job requests for program PRGM0001, even if the rest of the request entry fields match their masks. Any character is valid in this field. Filter YYYY/MM/DD, HH:MM:SS The mask for the YYYY/MM/DD and HH:MM:SS fields. The initial values are all asterisks, which directs Xchange to display all job requests for which the rest of the request entry fields match their masks. These masks are saved upon exit and restored upon entry. An asterisk represents a single wildcard character in the position of the date or time where it is placed. For example, masks 20** and **25 would each result in the display of all job requests for year 2025 — assuming the rest of the request entry fields match their masks. A mask of all blanks is valid. A combination of blanks and asterisks, or numeric data and asterisks, is also valid. If you enter all numeric data, validation rules are equivalent to that of the request entry date and time fields. C/S The command and status display for each entry. You can enter line commands under the C portion of the field. For a listing and description of the line commands, see “Line Commands” on page 5-5. Status codes are displayed under the S portion of the field. For a listing and description of the status codes, see “Status Codes” on page 5-6. 5-8 Xpediter/Xchange Installation and User Guide Owner The ID of the user who entered the pattern job request. This is a display-only field. The Owner user ID is also used in external security checking. See “Step 14. Configure Xchange External Security” on page 3-26. Xchange may also display ERR= followed by a four-letter message code in the Owner field to indicate a problem with the pattern job request. For more information on message codes, see “Owner Field Messages” on page A-1. Jobname The name of the MVS job or jobs for which to simulate the system date and time. You can specify a single job request or a number of job requests. To specify a single job request, you must enter a job name that exactly matches the name of the job being executed. To specify multiple job requests with a single entry, you may supply leading asterisk(s), embedded asterisk(s) or trailing asterisk(s) anywhere within the job name. A leading asterisk and an embedded asterisk represent a single character. A trailing asterisk represents one or more characters. An error message is displayed if: – – – – You do not enter a job name. There is no default for the Jobname field. You specify a job name that is the same as a previous job pattern request. You specify more than one request for a job name. You enter only a single asterisk and nothing else for the job name. You must enter other characters. Error messages and abend codes are documented in Appendix A, “Xchange Messages”. Note: For DB2 stored procedures, enter the jobname of the WLM address space that will be executing the stored procedure. All stored procedures that run in the WLM address space while it is “active” will have their time requests exchanged. CAUTION: If you create a pattern job request with your TSO user ID in the Jobname field and nothing specified in the Stepname, Procstep, or Program fields, that request will cause exchanges for every TIME service request issued by every program associated with your user ID. Stepname The name of a specific step or steps within a job request. To specify a single step, enter the exact step name in this field. To specify multiple steps with a single entry, you may supply leading asterisk(s), embedded asterisk(s), or trailing asterisk(s) anywhere within the step name. A leading asterisk and an embedded asterisk represent a single character. A trailing asterisk represents one or more characters. Specifying only an asterisk in this field requests all steps in a job request. The Stepname field defaults to an asterisk. Procstep The name of a procedure step or steps within a job request. To specify a single procedure step, enter the exact procedure step name in this field. To specify multiple procedure steps with a single entry, you may supply leading asterisk(s), embedded asterisk(s), or trailing asterisk(s) anywhere within the procedure step name. A leading asterisk and an embedded asterisk represent a single character. A trailing asterisk represents one or more characters. Specifying only an asterisk in this field requests all procedure steps in a job request. The Procstep field defaults to an asterisk. Program The name of the program specified on the EXEC PGM= JCL statement. To specify a single program, enter the exact program name in this field. Individual subprograms cannot be independently exchanged, but any subprograms called by the program Using Xchange 5-9 specified will also be exchanged. To specify multiple programs with a single entry, you may supply leading asterisk(s), embedded asterisk(s), or trailing asterisk(s) anywhere within the program name. A leading asterisk and an embedded asterisk represent a single character. A trailing asterisk represents one or more characters. Specifying only an asterisk in this field requests all programs in a job request. The Program field defaults to an asterisk. This field also displays a program name that was specified, either explicitly or implicitly, with the request parameter of an Xchange batch step or with the XCHANGE command from within an Xpediter/TSO session. YYYY/MM/DD The year, month, and day that you want Xchange to simulate. If the PREVDATE parameter is set to NO (see “Step 1. Specify Xchange Parameters” on page 3-2), dates prior to today’s date are not allowed. The following entries are valid: YYYY 1900 to 2041 MM 01 to 12 DD 01 to 28 (Feb.) 01 to 29 (Feb. during a leap year) 01 to 30 (Apr., June, Sept., and Nov.) 01 to 31 (Jan., Mar., May, July, Aug., Oct., and Dec.) If you enter a value for the day (DD), the month and year are required. If you enter a value for the month (MM), the year is required. You can enter just the year. This field defaults to the current year, month, and day. If you leave the DD field blank, an error will occur if the current day of the month is invalid for the month you specified — for example, if you entered February on July 31. HH:MM:SS The hour, minute, and second that you want Xchange to simulate for the specified date. The following entries are valid: HH 00 to 23 MM 00 to 59 SS 00 to 59 If you enter a value for seconds (SS), the hour and minutes are required. If you enter a value for minutes (MM), the hour is required. You can enter just the hour. This field defaults to the current hour, minute, and second for any values not specified. Jobno The low-order 5 position of the job number of the request. This is a display-only field. The first completed (C) request entry with a particular job number indicates only that a jobstep was executed that matched the corresponding request. Each additional completed entry (if any) with the same job number is the result of one or more actual date/time exchanges. See Figure 5-3 on page 5-6. PF Keys Xchange supports the standard default ISPF keys. Important keys to remember are PF1 (Help), PF3 (End), PF7 (Scroll Up), and PF8 (Scroll Down). The following PF keys are not active for this product: PF5 (RFIND), PF6 (RCHANGE), PF10 (Shift Left), and PF11 (Shift Right). 5-10 Xpediter/Xchange Installation and User Guide Primary Commands Type primary commands in the COMMAND field at the top of the Xchange screen. In addition to the standard ISPF primary commands, the following primary commands are available on the Simulated Date Time Settings screen: ADVANCE Use the ADVANCE command to display the Advance Request Settings screen. The command can be abbreviated as ADV. For more information, see “Advancing Xchange Requests Using the ISPF Interface” on page 5-15. DDF Use the DDF command to display the Simulated Date Time Settings screen in DDF format. For more information, see “Using DB2 Distributed Data Facility (DDF) Support” on page 5-24. DELDDF Use the DELDDF command to delete all active entries for all queued DDF requests. Only an Xchange administrator can perform this command. For information on designating Xchange administrators, see “Designating Administrators” on page 3-30. DELETE Use the DELETE command to delete all completed entries for jobs not active. The command can be abbreviated as DEL. Only an Xchange administrator can perform this command. For information on designating Xchange administrators, see “Designating Administrators” on page 3-30. JOBCLASS Use the JOBCLASS command to display the Simulated Date Time Settings in jobclass format. The command can be abbreviated as JOBC. For more information, see “Using Jobclass Support” on page 5-19. JOBOFF Using Xchange 5-11 Use the JOBOFF command to display the Simulated Date Time Settings in jobclass format with date/time offset fields. The command can be abbreviated as JOBO. For more information, see “Using Jobclass Support” on page 5-19 and “Using Jobclass Support with Date/Time Offset” on page 5-22. JOURNAL Use the JOURNAL command to view the active Xchange journal dataset name. The command can be abbreviated as JRNL. LOCATE Use the LOCATE command to position the display of requests starting with jobname xxxxxxxx. The command can be abbreviated as LOC. LEGAL Use the LEGAL command to display the Xpediter/Xchange copyright and trade secrets notice. OFFSET Use the OFFSET command to display the Simulated Date Time Settings screen in offset format. The command can be abbreviated as OFF. For more information, see “Using the ISPF Interface with Date/Time Offset” on page 5-13. PREFIX The PREFIX command is used to specify, by user ID, which pattern job requests display on the Simulated Date Time Settings screen. To view the pattern job requests for every user ID in the Xchange subsystem, type PREFIX * on the COMMAND line of the Simulated Date Time Settings screen and press Enter. If you enter the PREFIX primary command with nothing following it on the COMMAND line, a list of the pattern job requests set using your user ID is displayed. You can also display the pattern job requests set by a particular user by entering the PREFIX command followed by that user’s ID. This setting is retained across test sessions until it is specifically changed. 5-12 Xpediter/Xchange Installation and User Guide Note: You cannot delete or reset jobs that were added, set, or held by a user ID other than your own. RELEASE The RELEASE command displays the release number of Xpediter/Xchange you are using. If you type RELEASE in the COMMAND field and press Enter, Xchange will display the release number just below the SCROLL field. Enter the RELEASE command again to toggle the release number off. SSID The SSID command displays the subsystem ID for the subsystem you are using. If you type SSID in the COMMAND field and press Enter, Xchange will display the subsystem ID just below the SCROLL field. Enter the SSID command again to toggle the subsystem ID off. Creating an Xchange Inventory You can use Xchange and its journaling capability to generate an “inventory” of all the jobs with a particular job pattern, such as SALES* or ACCT*, that make TIME service requests. This inventory is created without actually changing any dates or times. It shows you the program name and offset of every TIME service request in every job you have run. Specify a pattern job request with your desired job pattern in the Jobname field and asterisks in the Stepname, Procstep, and Program fields. Be sure not to enter any values in the YYYY/MM/DD and HH:MM:SS fields. Leaving those fields blank will cause them to default to the current date and time. Then when any job is run that matches the pattern job request and, if security is activated, passes the security check for the generated dataset name, its date and time requests will be given the unchanged current date and time by Xchange. A sample inventory pattern job request is shown as the first entry in Figure 5-4. The completed entries below the request show the jobs that have been exchanged. Because every satisfied request is recorded in the Xchange journal, running your jobs will automatically create a detailed list showing the program and offset for every TIME service request issued. For more information on journaling, see Chapter 6, “Using the Xchange Journal”. Using Xchange 5-13 Figure 5-4. Inventory Pattern Job Request Xpediter/Xchange ------ Simulated Date Time Settings ------- Row 1 to 14 of 14 COMMAND ===> SCROLL ===> PAGE System ID: AC12 Type Legal on the command line for Copyright/Trade Secret Notice Information Line Commands: S - Set H - Set and Hold R - Reset D - Delete A - Set Active Status Codes: Q - Queued P - Pending A - Active E - Executing * - Error C - Completed N - Not Active Filter: ******** ******** ******** ******** **** ** ** ** ** ** C/S Owner Jobname Stepname Procstep Program YYYY/MM/DD HH:MM:SS Jobno _ Q YOURUID PAY*___ *_______ *_______ *_______ ____ __ __ __ __ __ _ C YOURUID PAY*___ *_______ *_______ *_______ ____ __ __ __ __ __ 18823 _ C YOURUID PAY*___ XGTEST01 *_______ XGCOBII_ ____ __ __ __ __ __ 18823 _ C YOURUID PAY*___ XGTEST02 *_______ XGCOBII_ ____ __ __ __ __ __ 18823 _ C YOURUID PAY*___ XGTEST03 *_______ XGCOBII_ ____ __ __ __ __ __ 18823 _ C YOURUID PAY*___ XGTEST04 *_______ XGCOBII_ ____ __ __ __ __ __ 18823 _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ ******************************* BOTTOM OF DATA ******************************** Using the ISPF Interface with Date/Time Offset In addition to standard Xchange requests used to specify a particular date and/or time, you can create pattern job requests based on a fixed offset from the current date and time. To create Xchange date/time offset requests, first enter the OFFSET primary command on the Simulated Date Time Settings screen as described in “Primary Commands” on page 5-10. The screen is redisplayed in date/time offset format as shown in Figure 5-5 on page 5-13. Create Xchange requests as you would using the standard ISPF interface, but use the Constants fields to specify how far in the future or past you want Xchange to simulate. Figure 5-5. Simulated Date Time Settings Screen for the ISPF Interface in Offset Format  Xpediter/Xchange ------ Simulated Date Time Settings ------- Row 1 to 14 of 14 COMMAND ===> SCROLL ===> PAGE System ID: AC12 Line Commands: S - Set H - Set and Hold R - Reset D - Delete A - Set Active Status Codes: Q - Queued P - Pending A - Active N - Not Active * - Error - Constants - Filter: ******** ******** ******** ******** **** ** ** * C/S Owner Jobname Stepname Procstep Program Days Hrs Mins Ind _ Q PPRJET0 PPRJET0O *_______ *_______ *_______ 1111 06 30 + _ ________ ________ ________ ________ ____ __ __ _ _ ________ ________ ________ ________ ____ __ __ _ _ ________ ________ ________ ________ ____ __ __ _ _ ________ ________ ________ ________ ____ __ __ _ _ ________ ________ ________ ________ ____ __ __ _ _ ________ ________ ________ ________ ____ __ __ _ _ ________ ________ ________ ________ ____ __ __ _ _ ________ ________ ________ ________ ____ __ __ _ _ ________ ________ ________ ________ ____ __ __ _ _ ________ ________ ________ ________ ____ __ __ _ _ ________ ________ ________ ________ ____ __ __ _ _ ________ ________ ________ ________ ____ __ __ _ _ ________ ________ ________ ________ ____ __ __ _ ******************************* BOTTOM OF DATA ******************************** After entering a date/time offset request, you can press PF3 to return to the standard ISPF Simulated Date Time Settings screen (Figure 5-6). Queued offset requests are displayed without a specific date and time. Completed offset request messages are displayed with 5-14 Xpediter/Xchange Installation and User Guide their simulated date/time calculated at execution from the Constants field values entered on the offset format screen. Note: The offset format screen remains unchanged and displays only requests, not messages. Figure 5-6. Simulated Date Time Settings Screen Showing Date/Time Offset Requests Xpediter/Xchange ------ Simulated Date Time Settings ------- Row 1 to 14 of 14 COMMAND ===> SCROLL ===> PAGE System ID: AC12 Type Legal on the command line for Copyright/Trade Secret Notice Information Line Commands: S - Set H - Set and Hold R - Reset D - Delete A - Set Active Status Codes: Q - Queued P - Pending A - Active E - Executing * - Error C - Completed N - Not Active Filter: ******** ******** ******** ******** **** ** ** ** ** ** C/S Owner Jobname Stepname Procstep Program YYYY/MM/DD HH:MM:SS Jobno _ Q PPRJET0 PPRJET0O *_______ *_______ *  _ C PPRJET0 PPRJET0O *_______ *_______ * 2011 03 26 12 47 40 75433 _ C PPRJET0 PPRJET0O GO______ ________ COBMAINA 2011 03 26 12 47 40 75433 _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ ******************************* BOTTOM OF DATA ******************************** Constants Fields Use the Constants fields to specify how far into the future or past you want Xchange to simulate the date and time for a request. For example, if you type 364 in the Days field, 23 in the Hrs field, 59 in the Mins field, and + in the Ind field of a pattern job request, Xchange will substitute a date and time nearly one year into the future for the specified job. The Owner field and the S portion of the C/S field are display-only. You can type data into all other fields. The Filter row contains a series of mask fields, each corresponding to the column directly below it. Note: Only those fields unique to Xchange’s date/time offset format are described in this section. For descriptions of other fields, see “Fields” on page 5-6. Filter Days, Hrs, Mins The masks for the Days, Hrs, and Mins fields. The initial values are all asterisks, which directs Xchange to display all job requests for which the rest of the request entry fields match their corresponding masks. These masks are saved upon exit and restored upon entry. An asterisk represents a single wildcard character in the position of the day or time where it is placed. For example, masks 20** and **25 would each result in the display of all job requests for 2025 days — assuming the rest of the request entry fields match their masks. The Filter Days mask must contain either numeric data, asterisks, or both. A mask of all blanks is valid for the Filter Hrs and Filter Mins fields. A combination of blanks and asterisks, or numeric data and asterisks, is also valid. If you enter all numeric data, validation rules are equivalent to that of the request entry Days, Hrs, and Mins fields. Using Xchange 5-15 Filter Ind The mask for the Ind field. An asterisk, + (plus), or - (minus) is valid. A minus is valid only if the PREVDATE parameter is set to YES (see “Step 1. Specify Xchange Parameters” on page 3-2). Days The number of days into the future or past that you want Xchange to simulate. Valid entries are from 0 to 9999. The default is 0. Hrs The number of hours into the future or past that you want Xchange to simulate. Valid entries are from 0 to 23. The default is 0. Mins The number of minutes into the future or past that you want Xchange to simulate. Valid entries are from 0 to 59. The default is 0. Ind Used to indicate the direction, future or past, that you want Xchange to simulate. Valid entries are + (plus) for an offset into the future and - (minus) for an offset into the past. The default is +. If the PREVDATE parameter is set to NO (see “Step 1. Specify Xchange Parameters” on page 3-2), date/time offsets into the past are not allowed. Advancing Xchange Requests Using the ISPF Interface In addition to requests that simulate date and time substitution, you can create pattern job requests to advance the date and time or the offset of existing Xchange requests. To create Xchange Advance requests, first enter the ADVANCE primary command on the Simulated Date Time Settings screen as described in “Primary Commands” on page 5-10. The Advance Request Settings screen (Figure 5-7) is displayed. Create Xchange Advance requests as you would using the standard or offset ISPF interface, but use the Advance fields to specify how many days, hours, and minutes to advance Xchange Date/Time and Offset requests forward or backward. Figure 5-7. Advance Request Settings Screen for the ISPF Interface  Xpediter/Xchange -------- Advance Request Settings --------- Row 1 to 14 of 14 COMMAND ===> SCROLL ===> CSR System ID: AC12 Line Commands: H - Set and Hold R - Reset D - Delete V - Advance Status Codes: Q - Queued * - Error Filter: C/S Owner _ _ ******** Jobname ________ ________ ******** Stepname ________ ________ ******** Procstep ________ ________ ******** Program ________ ________ -- Advance -- **** ** ** Days Hrs Mins ____ __ __ ____ __ __ * Ind _ _ Line Commands Type line commands under the C portion of the C/S field (see “Fields” on page 5-16). The following line commands are available on the Advance Request Settings screen: H Sets and holds a pattern job request by adding it to the request table. Requests remain staged until you delete them using the D (Delete) line command. 5-16 Xpediter/Xchange Installation and User Guide R Resets a pattern job request. This command deletes an existing pattern job request, then adds the pattern job request back into the request table. The R command allows you to modify the values in the Advance Days, Hours, Minutes, and Indicator fields of an existing pattern job request. No other fields can be modified using the R command. A request owned by a different user ID can only be reset by an Xchange administrator. For information on designating Xchange administrators, see “Designating Administrators” on page 3-30. D Deletes an existing pattern job request. A request owned by a different user ID can only be deleted by an Xchange administrator. For information on designating Xchange administrators, see “Designating Administrators” on page 3-30. V Advances the requested date and time or offset of all queued Date/Time and Offset requests that match the staged Advance request by the number of days, hours, and minutes specified in the Advance fields forward or backward as specified by the Indicator field. This command deletes all matching Date/Time and Offset pattern job requests along with their completed entries, then adds the pattern job requests back into the request table. No fields other than the Line Command need to be entered to advance a staged request. A request owned by a different user ID can only be advanced by an Xchange administrator. For information on designating Xchange administrators, see “Designating Administrators” on page 3-30. Fields Note: Fields not discussed in this section function in the same way as they do for the standard ISPF and offset screens. Jobname The name of the MVS job or jobs for which to advance the requested system date and time, or offset. Advance Days The number of days you want Xchange to advance the requested date and time or offset of existing requests. Valid entries are from 0 to 9999. The default is 0. Advance Hours The number of hours you want Xchange to advance the requested date and time or offset of existing requests. Valid entries are from 0 to 23. The default is 0. Advance Minutes The number of minutes you want Xchange to advance the requested date and time or offset of existing requests. Valid entries are from 0 to 59. The default is 0. Advance Indicator This field is used to specify whether to advance the requested date and time, or offset, of existing requests forward or backward. Valid entries are + (plus) to advance forward and - (minus) to advance backward. The default is + (forward). If the PREVDATE parameter is set to NO (see “Step 1. Specify Xchange Parameters” on page 3-2), advancing the requested date and time, or offset, of an existing request prior to the current date is not allowed. Example of Advancing the Requested Date and Time or Offset of Existing Requests In this example, two pattern job requests were queued, corresponding jobs were successfully executed, and Xchange substituted the date and time, or offset, as requested (Figure 5-8). Queued offset requests, like the fourth one below, are displayed without a specific date and time. Using Xchange 5-17 Figure 5-8. Advancing Pattern Job Requests – First Screen Xpediter/Xchange ------ Simulated Date Time Settings ------- Row 1 to 14 of 28 COMMAND ===> SCROLL ===> CSR System ID: AC12 Type Legal on the command line for Copyright/Trade Secret Notice Information Line Commands: S - Set H - Set and Hold R - Reset D - Delete A - Set Active Status Codes: Q - Queued P - Pending A - Active E - Executing * - Error C - Completed N - Not Active Filter: ******** ******** ******** ******** **** ** ** ** ** ** C/S Owner Jobname Stepname Procstep Program YYYY/MM/DD HH:MM:SS Jobno _ Q PPRJET0 PPRJET0D * * * 2022 02 02 02 02 02 _ C PPRJET0 PPRJET0D * * * 2022 02 02 02 02 02 44406 _ C PPRJET0 PPRJET0D GO XGBASM 2022 02 02 02 02 02 44406 _ Q PPRJET0 PPRJET0O * * * _ C PPRJET0 PPRJET0O * * * 2019 09 29 01 15 55 44407 _ C PPRJET0 PPRJET0O GO XGBASM 2019 09 29 01 15 55 44407 _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ Note: The OFFSET primary command can be used to display the Simulated Date Time Settings screen in offset format (Figure 5-9), allowing you to view the offsets for the fourth request above. Figure 5-9. Advancing Pattern Job Requests – Second Screen  Xpediter/Xchange ------ Simulated Date Time Settings ------- Row 1 to 14 of 14 COMMAND ===> SCROLL ===> CSR System ID: AC12 Line Commands: S - Set H - Set and Hold R - Reset D - Delete A - Set Active Status Codes: Q - Queued P - Pending A - Active N - Not Active * - Error Filter: C/S Owner _ Q PPRJET0 _ _ ******** Jobname PPRJET0O ________ ________ ******** Stepname * ________ ________ ******** Procstep * ________ ________ ******** Program * ________ ________ - Constants - **** ** ** Days Hrs Mins 1111 11 11 ____ __ __ ____ __ __ * Ind + _ _ The ADVANCE primary command can be entered on the Simulated Date Time Settings screen shown in Figure 5-8 to display the Advance Request Settings screen shown in Figure 5-10. An Advance request is entered on the Advance Request Settings screen using the Set and Hold (H) line command, specifying that Xchange should advance the requested date and time or offset of any request whose pattern job request matches that set below by 90 days, 4 hours, and 30 minutes forward at such time when the Advance is requested. For now, the Advance request is staged. 5-18 Xpediter/Xchange Installation and User Guide Figure 5-10. Advance Request Settings Screen Xpediter/Xchange -------- Advance Request Settings --------COMMAND ===>  Line Commands: H - Set and Hold R - Reset Status Codes: Q - Queued * - Error Filter: C/S Owner _ Q PPRJET0 _ _ ******** Jobname PPRJET0* ________ ________ ******** Stepname * ________ ________ ******** Procstep * ________ ________ Process Complete SCROLL ===> CSR System ID: AC12 V - Advance D - Delete ******** Program * ________ ________ -- Advance -- **** ** ** Days Hrs Mins 0090 04 30 ____ __ __ ____ __ __ * Ind + _ _ The Advance line command V is entered beside this request. Figure 5-11. Advance Request Settings Screen with V Line Command Xpediter/Xchange -------- Advance Request Settings --------COMMAND ===>  Line Commands: H - Set and Hold R - Reset Status Codes: Q - Queued * - Error Filter: C/S Owner V Q PPRJET0 _ _ ******** Jobname PPRJET0* ________ ________ ******** Stepname * ________ ________ ******** Procstep * ________ ________ D - Delete ******** Program * ________ ________ Process Complete SCROLL ===> CSR System ID: AC12 V - Advance -- Advance -- **** ** ** Days Hrs Mins 0090 04 30 ____ __ __ ____ __ __ * Ind + _ _ Once completed, the requested date and time or offset of any request whose pattern job request matches is advanced by 90 days, 4 hours, and 30 minutes forward as shown in Figure 5-12 and Figure 5-13. Figure 5-12. Simulated Date Time Settings Screen with Advance Request Xpediter/Xchange ------ Simulated Date Time Settings ------- Row 1 to 14 of 14 COMMAND ===> SCROLL ===> CSR System ID: AC12 Type Legal on the command line for Copyright/Trade Secret Notice Information Line Commands: S - Set H - Set and Hold R - Reset D - Delete A - Set Active Status Codes: Q - Queued P - Pending A - Active E - Executing * - Error C - Completed N - Not Active Filter: ******** ******** ******** ******** **** ** ** ** ** ** C/S Owner Jobname Stepname Procstep Program YYYY/MM/DD HH:MM:SS Jobno _ Q PPRJET0 PPRJET0D * * * 2022 05 03 06 32 02 _ Q PPRJET0 PPRJET0O * * * _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ Using Xchange 5-19 Figure 5-13. Simulated Date Time Settings Screen with Advance Request Showing Constants  Xpediter/Xchange ------ Simulated Date Time Settings ------- Row 1 to 14 of 14 COMMAND ===> SCROLL ===> CSR System ID: AC12 Line Commands: S - Set H - Set and Hold R - Reset D - Delete A - Set Active Status Codes: Q - Queued P - Pending A - Active N - Not Active * - Error Filter: C/S Owner _ Q PPRJET0 _ _ ******** Jobname PPRJET0O ________ ________ ******** Stepname * ________ ________ ******** Procstep * ________ ________ ******** Program * ________ ________ - Constants - **** ** ** Days Hrs Mins 1201 15 41 ____ __ __ ____ __ __ * Ind + _ _ Using Jobclass Support Beginning with Release 3.1, Xchange features improved flexibility to allow users to set Xchange requests based on execution jobclass. A running time clock for all programs run under that jobclass will be started at the moment the request is first used and will run parallel to real time. The request, including its displacement from the real time and date, is retained until you delete it with the D (Delete) line command or reset it with the R (Reset) line command. If an individual Xchange request is entered on the Simulated Date Time Settings screen for a job that happens to run in a class for which there is an active jobclass request, the date/time fields from the individual request will be used instead of the jobclass screen’s date/time fields because specific individual requests always take precedence over jobclass requests. In order for a class to be eligible for jobclass processing, it must have been defined with the Xchange parameter CLASS. For more information, see “Step 1. Specify Xchange Parameters” on page 3-2. When the JOBCLASS primary command is entered on the command line of the Xchange Date Time Settings screen, the screen is displayed in jobclass format as shown in Figure 5-14. All the classes that were designated with the CLASS parameter are displayed. Note: Jobclass support is also provided in date/time offset format. Enter the JOBOFF primary command on the Simulated Date Time Settings screen to redisplay the screen in jobclass format with date/time offset capability. For more information, see “JOBOFF” on page 5-10 and “Using Jobclass Support with Date/Time Offset” on page 5-22. 5-20 Xpediter/Xchange Installation and User Guide Figure 5-14. Simulated Date Time Settings Screen for Jobclass Support  Xpediter/Xchange ------ Simulated Date Time Settings -------- Process Complete COMMAND ===> SCROLL ===> CSR System ID: AC12 Line Commands: H - Set and Hold R - Reset D - Delete Status Codes: Q - Queued A - Active E - Executing * - Error -- Requested Time --- Current Simulated Time-- Filter: C/S Imsg _ Q _ _ _ _ _ _ _ _ _ _ _ _ _ _ Jobclass X A B C D E F G H I J K L M N **** ** ** YYYY/MM/DD 2010 10 10 ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ** ** ** HH:MM:SS 05 00 00 __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ YYYY/MM/DD ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ HH:MM:SS __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ Primary Commands Enter primary commands in the COMMAND field at the top of the Simulated Date Time Settings screen. Only the standard ISPF primary commands are supported when in jobclass format. The END command returns to the standard Simulated Date Time Settings screen. The RETURN command returns you to ISPF. Line Commands The line commands described below can be entered if the user has the necessary authority. See “Step 14. Configure Xchange External Security” on page 3-26 for more information on authority for jobclass line commands. Three line commands are available for each of the jobclasses displayed on the Simulated Date Time Settings screen in jobclass format. If your site is using Xchange external security (SECUSE=YES,SECDFLT=DENY), the TSO userID of the person entering the line command must have update access to the JOBCLASS pseudo-dataset name as described in “Step 14. Configure Xchange External Security” on page 3-26. If that update access is not established, a NAUT (not authorized) error will be displayed under the Imsg column. If Xchange external security is not used (SECUSE=NO), any user can enter line commands on the Simulated Date Time Settings screen in jobclass format. H Sets and holds a pattern jobclass request. This command activates jobclass processing for the class indicated on the line on which it is entered. D Deletes an existing pattern jobclass request and its related jobs (if applicable). R Resets an existing pattern jobclass request. This command deletes the existing pattern jobclass request and its related jobs, then adds the jobclass pattern back to the request table. The R command allows you to modify the values in the Requested Time YYYY/MM/DD and HH:MM:SS fields of the jobclass request. No other fields can be modified with the R command. Using Xchange 5-21 Status Codes Status codes are displayed in the S portion of the C/S field next to each Xchange jobclass request. Any of the following status codes can be displayed: A The jobclass request has an active job. E The jobclass request is executing. P The jobclass request is pending. Because pending is a momentary status, this code is normally not seen. Q The jobclass request is queued. * The jobclass request contains an error. Fields Line commands can be entered next to each jobclass request in the C portion of the C/S field, and the desired date and/or time can be entered in the Requested Time fields. The S portion of the C/S field and the Imsg, Jobclass, and Current Simulated Time fields are display-only. The Filter row contains a series of mask fields, each corresponding to the column directly below it. Filter Requested Time YYYY/MM/DD, HH:MM:SS The mask for the Requested Time YYYY/MM/DD and HH:MM:SS fields. The initial values are all asterisks, which directs Xchange to display all jobclass requests for which the rest of the request entry fields match their corresponding masks. These masks are saved upon exit and restored upon entry. An asterisk represents a single wildcard character in the position of the date or time where it is placed. For example, masks 20** and **25 would each result in the display of all jobclass requests for year 2025 — assuming the rest of the request entry fields match their masks. A mask of all blanks is valid. A combination of blanks and asterisks, or numeric data and asterisks, is also valid. If you enter all numeric data, validation rules are equivalent to that of the request entry date and time fields. C/S The command and status fields for each jobclass request. You can enter line commands in the C portion of the field. Status codes are displayed in the S portion of the field. Imsg The informational message area for each entry. When an asterisk (*) is displayed in the S portion of the C/S field, an informational error message will be displayed in the Imsg field. Jobclass The jobclass of each entry is displayed in this field. All jobclasses displayed have been defined with the Xchange parameter CLASS. Requested Time YYYY/MM/DD The year, month, and day that you want Xchange to simulate for jobs running in this jobclass. If the PREVDATE parameter is set to NO (Xchange CMSC PARMLIB member), dates prior to the current date are not allowed. The following entries are valid: YYYY 1900 to 2041 MM 01 to 12 5-22 Xpediter/Xchange Installation and User Guide DD 01 to 28 (Feb.) 01 to 29 (Feb. during a leap year) 01 to 30 (Apr., June, Sept., and Nov.) 01 to 31 (Jan., Mar., May, July, Aug., Oct., and Dec.) If you enter a value for the day (DD), the month and year are required. If you enter a value for the month (MM), the year is required. You can just enter the year. This field defaults to the current year, month and day. If you leave the DD field blank, an error will occur if the current day of the month is invalid for the month you specified — for example, if you entered February on July 31. Requested Time HH:MM:SS The hour, minute and second that you want Xchange to simulate for jobs running in this jobclass. The following entries are valid: HH 00 to 23 MM 00 to 59 SS 00 to 59 If you enter a value for seconds (SS), the hour and minutes are required. If you enter a value for minutes (MM), the hour is required. You can just enter the hour. This field defaults to the current hour, minute, and second for any values not specified. Current Simulated Time YYYY/MM/DD and HH:MM:SS These fields contain the date and time of the first time request issued by the first job running in this jobclass. These fields will remain blank until this occurs. Once these fields are populated, they will not change until the jobclass request is either deleted (D) or reset (R). This date/time field is used as the baseline from which Xchange creates a “delta” used to simulate a running time for all jobs executing in this jobclass. PF Keys Xchange supports the standard default ISPF keys. Additional Considerations The following limitations and special concerns apply to Xchange jobclass support: • Jobclass support is limited to batch jobs. Started Tasks (STCs) and TSO Users (TSUs) are unaffected by jobclass requests. • Specific, non-jobclass requests which cover jobs running in the same class as an active jobclass request override that jobclass request. The date/time of the nonjobclass request is used for the exchange. • Batch CICS/IMS regions that run in a class that happens to be covered by an active jobclass request will be exchanged at the region level. • A batch job will not be exchanged if the class under which it runs is not defined to Xchange with the parameter CLASS. Such jobs are displayed on the Simulated Date Time Settings screen with a JAUT error message. Using Jobclass Support with Date/Time Offset In addition to standard Xchange jobclass requests used to specify a particular date and/or time, you can create jobclass requests based on a fixed offset from the current date and time when the job is initiated. Using Xchange 5-23 To create Xchange jobclass date/time offset requests, first enter the JOBOFF primary command on the Simulated Date Time Settings screen as described in “Primary Commands” on page 5-10. The screen is redisplayed in jobclass date/time offset format as shown in Figure 5-15 on page 5-23. Create Xchange requests as you would using the standard jobclass format, but use the Constants fields to specify how far in the future or past you want Xchange to simulate. Other fields, status codes, and commands are the same as those described in “Using Jobclass Support” on page 5-19. Figure 5-15. Simulated Date Time Settings Screen for Jobclass Support in Offset Format  Xpediter/Xchange ------ Simulated Date Time Settings ------- Row 1 to 14 of 36 COMMAND ===> SCROLL ===> CSR System ID: AC12 Line Commands: H - Set and Hold R - Reset D - Delete Status Codes: Q - Queued A - Active E - Executing * - Error - Constants -- Current Simulated Time-- Filter: C/S Imsg _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ . . . . **** ** ** * Jobclass Days Hrs Mins Ind A ____ __ __ _ B ____ __ __ _ C ____ __ __ _ D ____ __ __ _ E ____ __ __ _ F ____ __ __ _ G ____ __ __ _ H ____ __ __ _ I ____ __ __ _ J ____ __ __ _ K ____ __ __ _ L ____ __ __ _ M ____ __ __ _ N ____ __ __ _ . . . . . . . . . . . . YYYY/MM/DD ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ ____ __ __ . . . . . HH:MM:SS __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ . . . . . . Constants Fields Use the Constants fields to specify how far into the future or past you want Xchange to simulate the date and time for a request. For example, if you type 364 in the Days field, 23 in the Hrs field, 59 in the Mins field, and + in the Ind field of a pattern job request, Xchange will substitute a date and time nearly one year into the future for the specified jobclass. The Imsg field and the S portion of the C/S field are display-only. You can type data into all other fields. The Filter row contains a series of mask fields, each corresponding to the column directly below it. Note: Only those fields unique to Xchange’s date/time jobclass offset format are described in this section. For descriptions of other fields, see “Fields” on page 5-21. Filter Days, Hrs, Mins The masks for the Days, Hrs, and Mins fields. The initial values are all asterisks, which directs Xchange to display all jobclass requests for which the rest of the constant by jobclass request entry fields match their corresponding masks. These masks are saved upon exit and restored upon entry. An asterisk represents a single wildcard character in the position of the day or time where it is placed. For example, masks 20** and **25 would each result in the display of all jobclass requests for 2025 days — assuming the rest of the constant by jobclass request entry fields match their masks. The Filter Days mask must contain either numeric data, asterisks, or both. A mask of all blanks is valid for the Filter Hrs and Filter Mins fields. A combination of blanks and asterisks, or numeric data and asterisks, is also valid. If you enter all numeric data, validation rules are equivalent to that of the request entry Days, Hrs, and Mins fields. 5-24 Xpediter/Xchange Installation and User Guide Filter Ind The mask for the Ind field. An asterisk, + (plus), or - (minus) is valid. A minus is valid only if the PREVDATE parameter is set to YES (see “Step 1. Specify Xchange Parameters” on page 3-2). Days The number of days into the future or past that you want Xchange to simulate. Valid entries are from 0 to 9999. The default is 0. Hrs The number of hours into the future or past that you want Xchange to simulate. Valid entries are from 0 to 23. The default is 0. Mins The number of minutes into the future or past that you want Xchange to simulate. Valid entries are from 0 to 59. The default is 0. Ind Used to indicate the direction, future or past, that you want Xchange to simulate. Valid entries are + (plus) for an offset into the future and - (minus) for an offset into the past. The default is +. If the PREVDATE parameter is set to NO (see “Step 1. Specify Xchange Parameters” on page 3-2), date/time offsets into the past are not allowed. Using DB2 Distributed Data Facility (DDF) Support To create Xchange DDF requests, first enter the DDF primary command on the Simulated Date Time Settings screen as described in “Primary Commands” on page 5-10. A screen is displayed in date/time offset format as shown in Figure 5-16 on page 5-24. Create Xchange requests as you would using the ISPF interface with Date/Time offset, but use the DB2 request fields to specify the criteria that will be used at execution time to see whether a DB2 Date/Time request is eligible for exchange. Figure 5-16. Simulated Date Time Settings Screen for DDF Support Xpediter/Xchange ------ Simulated Date Time Settings ------COMMAND ===> Process Complete SCROLL ===> CSR System ID: AC12 Line Commands: H - Set and Hold R - Reset D - Delete Status Codes: Q - Queued P - Pending * - Error - Constants - **** ************ ******** ******** **** ** ** * DB2 Correlation Resource C/S Owner SSID ID Name UserId Days Hrs Mins Ind _ Q PPRJET0 D14E PPRJET0O____ XGBCHDB2 PPRJET0 0030 __ __ + _ ____ ____________ ________ ________ ____ __ __ _ _ ____ ____________ ________ ________ ____ __ __ _ _ ____ ____________ ________ ________ ____ __ __ _ _ ____ ____________ ________ ________ ____ __ __ _ _ ____ ____________ ________ ________ ____ __ __ _ _ ____ ____________ ________ ________ ____ __ __ _ _ ____ ____________ ________ ________ ____ __ __ _ _ ____ ____________ ________ ________ ____ __ __ _ _ ____ ____________ ________ ________ ____ __ __ _ _ ____ ____________ ________ ________ ____ __ __ _ _ ____ ____________ ________ ________ ____ __ __ _ _ ____ ____________ ________ ________ ____ __ __ _ _ ____ ____________ ________ ________ ____ __ __ _ ******************************* BOTTOM OF DATA ******************************** Filter: After entering a DDF request, you can press PF3 to return to the standard ISPF Simulated Date Time Settings screen (Figure 5-2 on page 5-4). Queued DDF requests are displayed without a specific date and time. Completed DDF request messages are displayed with Using Xchange 5-25 their simulated date/time calculated at execution from the Constants field values entered on the DDF screen. The Correlation ID field appears in the Jobname field and the first 4 bytes of the Stepname field if necessary. The Resource Name appears in the Procstep field. =DDF appears in the first four positions of the Program field and the DB2 subsystem ID, if specified, appears in the last four positions to uniquely identify these requests. Unlike other Set and Hold requests that become queued and completed, a DDF request remains queued and active until it is deleted or Xchange is cycled. Note: The DDF screen remains unchanged and displays only requests, not messages. Figure 5-17. Simulated Date Time Settings Screen Showing a DDF Request Xpediter/Xchange ------ Simulated Date Time Settings ------- Row 1 to 14 of 14 COMMAND ===> SCROLL ===> CSR System ID: AC12 Type Legal on the command line for Copyright/Trade Secret Notice Information Line Commands: S - Set H - Set and Hold R - Reset D - Delete A - Set Active Status Codes: Q - Queued P - Pending A - Active E - Executing * - Error C - Completed N - Not Active Filter: ******** ******** ******** ******** **** ** ** ** ** ** C/S Owner Jobname Stepname Procstep Program YYYY/MM/DD HH:MM:SS Jobno _ Q PPRJET0 PPRJET0X ________ XGBCHDB2 =DDFD14E ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ _ ________ ________ ________ ________ ____ __ __ __ __ __ ******************************* BOTTOM OF DATA ******************************** DB2 DDF Request Fields Use the DB2 request fields to specify the criteria that will be used at execution time to see whether a DB2 Date/Time request is eligible for exchange. The Owner field and the S portion of the C/S field are display-only. You can type data into all other fields. The Filter row contains a series of mask fields, each corresponding to the column directly below it. Note: Only those fields unique to Xchange’s DDF support are described in this section. For descriptions of other fields, see “Fields” on page 5-6. Filter DB2 SSID The initial value is all asterisks, which directs Xchange to display all DDF requests for which the rest of the request entry fields match their corresponding masks. This mask is saved upon exit and restored upon entry. An asterisk represents a single wildcard character in the position of the DB2 SSID where it is placed. For example, masks D*** and **0* would each result in the display of all DDF requests associated with DB2 SSID D801 assuming the rest of the request entry fields match their masks. However the masks D* , *01 , and *01*, would each result in the display of no DDF requests for DB2 SSID D801, even if the rest of the request entry fields match their masks. Any character is valid in this field. Filter Correlation ID The mask for the Correlation ID field. The initial value is all asterisks, which directs Xchange to display all DDF requests for which the rest of the request entry fields match their corresponding masks. This mask is saved upon exit and restored upon entry. 5-26 Xpediter/Xchange Installation and User Guide An asterisk represents a single wildcard character in the position of the correlation ID where it is placed. For example, masks TST********* and ***JOB****** would each result in the display of all DDF requests associated with correlation ID TSTJOB01 — assuming the rest of the request entry fields match their masks. However the masks , *JOB01 , and *JOB* would each result in the display of no DDF TST* requests for correlation ID TSTJOB01, even if the rest of the request entry fields match their masks. Any character is valid in this field. Filter Resource Name The mask for the Resource Name field. The initial value is all asterisks, which directs Xchange to display all DDF requests for which the rest of the request entry fields match their corresponding masks. This mask is saved upon exit and restored upon entry. An asterisk represents a single wildcard character in the position of the resource name where it is placed. For example, masks PRGM**** and ****0001 would each result in the display of all DDF requests for resource name PRGM0001 — assuming the rest of the request entry fields match their masks. However the masks PRGM* and *0001 would each result in the display of no DDF requests for resource name PRGM0001, even if the rest of the request entry fields match their masks. Any character is valid in this field. Filter UserId The mask for the UserId field. The initial value is all asterisks, which directs Xchange to display all DDF requests for which the rest of the request entry fields match their corresponding masks. This mask is saved upon exit and restored upon entry. An asterisk represents a single wildcard character in the position of the user ID where it is placed. For example, masks ID****** and **10**** would each result in the display of all DDF requests for user ID ID10T — assuming the rest of the request and *10* would each entry fields match their masks. However the masks ID* result in the display of no DDF requests for user ID ID10T , even if the rest of the request entry fields match their masks. Any character is valid in this field. DB2 SSID The DB2 SSID identifies the DB2 subsystem to which the request is restricted. All characters are translated to uppercase for evaluation. Correlation ID The Correlation ID is a DB2 field that identifies the thread executed by DB2. For batch jobs, this is generally the Jobname. For other environments, please refer to the appropriate IBM DB2 Administration Guide. All characters are translated to uppercase for evaluation. Resource Name The Resource Name is a DB2 field that identifies the resource plan. For batch jobs, this is generally the 8-byte Plan Name used in the DB2 Bind process. For other environments, please refer to the appropriate IBM DB2 Administration Guide. All characters are translated to uppercase for evaluation. UserId The UserId is optional. If this field is left blank, the userID of the requester is used. If input to this field is an asterisk wildcard character, Resource Name must be DISTSERV and the requester must be defined as an Xchange Administrator or an error message will be displayed. A trailing asterisk is permitted, but an embedded asterisk is not. This field is not validated to ensure it is a valid user ID. In addition to the selection criteria in use today, if the User Id of the DB2 DDF job or service matches that of the request and it meets existing security criteria, a Date/Time substitution will occur. Using Xchange 5-27 Using the Batch Facility Xchange’s batch facility lets you insert steps in your batch jobs that will exchange the date and time for selected steps or the entire job. By including Xchange steps directly in your jobs, you can easily manage and maintain a large number and variety of date/time exchanges. An Xchange I000 message is placed in the JES2 job log the first time during program execution that Xchange simulates a date or time for a job step. The same message is sent to your terminal, but might not be seen unless you update your TSO profile. To enable viewing of I000 messages, type TSO PROFILE WTPMSG on the TSO COMMAND line and press Enter. If only one Xchange batch step is included in your job: • The Xchange step must come before the job step(s) it specifies. • A fully qualified stepname can be entered for the STEP parameter. If you include multiple Xchange batch steps in your job: • Each Xchange step must come before the job step(s) it specifies. • Fully qualified stepnames should not be used. • Only the last Xchange step executed will have an entry or entries on the Simulated Date Time Settings screen. You can use the batch facility by simply inserting the following Xchange batch steps as required in the application job that you want to affect. Figure 5-18. Xchange Batch Steps //* //STEPNAME EXEC PGM=XGCBATCH,PARM=’request’ //STEPLIB DD DSN=CPWR.MLXGnnn.SLXGLOAD,DISP=SHR //SYSPRINT DD SYSOUT=* //* Replace CPWR with the high-level qualifier chosen for your site. You must also provide information for the PARM='request' variable according to the syntax shown in either Figure 5-19 for fixed date and time or Figure 5-20 for date/time offset. Note: Do not mix fixed date and time keywords (DATE, TIME, and TOD) with date/time offset keywords (DAYS, HRS, MINS, and IND) in a single request. 5-28 Xpediter/Xchange Installation and User Guide Figure 5-19. Batch Facility Request Parameter Syntax for Fixed Date and Time Figure 5-20. Batch Facility Request Parameter Syntax for Date/Time Offset DATE The year, month, and day that you want Xchange to simulate. If the PREVDATE parameter is set to NO (see “Step 1. Specify Xchange Parameters” on page 3-2), dates prior to today’s date are not allowed. The following entries are valid: YYYY 1900 to 2041 MM 01 to 12 Using Xchange DD 5-29 01 to 28 (Feb.) 01 to 29 (Feb. during a leap year) 01 to 30 (Apr., June, Sept., and Nov.) 01 to 31 (Jan., Mar., May, July, Aug., Oct., and Dec.) This parameter defaults to the current year, month, and day. TIME or TOD The hour, minute, and second that you want Xchange to simulate for the specified date. The following entries are valid: HH 00 to 23 MM 00 to 59 SS 00 to 59 This parameter defaults to the current hour, minute, and second. SUBSYS The subsystem ID specified in the Xchange CMSC PARMLIB member. This name was specified by the product installer and is discussed in “Step 1. Specify Xchange Parameters” on page 3-2. This parameter defaults to CWXG. STEP The name of a specific step or set of steps within a job request. To specify a single step, enter the exact step name in this field. More than one step can be specified by substituting an asterisk (*) wildcard character anywhere in the step name. Specifying only an asterisk for this parameter requests all steps in the job. An asterisk is the default. PROC The name of a procedure step or steps within a job request. You can specify a single procedure step by entering the exact procedure name, or multiple procedure steps by replacing any part of the procedure step with an asterisk (*). You can request all procedure steps within a step by specifying only an asterisk for this parameter. An asterisk is the default. DAYS The number of days in the future or past for date/time offset processing of a job request. Valid entries for dddd are 0 to 9999. The default is 0. HRS The number of hours in the future or past for date/time offset processing of a job request. Valid entries for hh are 0 to 23. The default is 0. MINS The number of minutes in the future or past for date/time offset processing of a job request. Valid entries for mm are 0 to 59. The default is 0. IND The direction, future or past, for date/time offset processing of a job request. Valid entries for IND are + for future and - for past. The default is +. GHD Global Hold Date/Time option. Setting this option to YES eliminates the running clock between date/time requests. The default is NO. For an example of Global Hold Date/Time, assume a batch program does the following: 5-30 Xpediter/Xchange Installation and User Guide 1. Gets the date and time 2. Waits two seconds 3. Gets the date and time. When the XGCBATCH PARM is PARM='DATE=1999/12/31,TIME=23:59:59,GHD=N' the result is the following: 1. Gets the date and time of 1999/12/31 and 23:59:59 2. Waits two seconds 3. Gets the date and time of 2000/01/01 and 00:00:01. However, when the XGCBATCH PARM is PARM='DATE=1999/12/31,TIME=23:59:59,GHD=Y' the result is the following: 1. Gets the date and time of 1999/12/31 and 23:59:59 2. Waits two seconds 3. Gets the same date and time of 1999/12/31 and 23:59:59. Implementing the Input Dataset Feature of the Batch Facility Xpediter/Xchange provides the ability to retrieve parameter data from an input dataset. JCL and Dataset Requirements • Add a DD card for DDname, XGPARMDS. • You may put the parameters instream or create a dataset to contain the parameters. • If you create a dataset, the DCB information is: – RECFM=FB – LRECL=80 – BLKSIZE=multiple of 80. Note: The DSORG value may be sequential or partitioned. The file is opened sequential. Therefore, if the dataset is partitioned, the member name must be included with the dataset name. Coding the Parameter List for the XGPARMDS Dataset The syntax for the parameters is shown in Figure 5-19 on page 5-28 for fixed date and time and in Figure 5-20 on page 5-28 for date/time offset. Observe the following when coding a parameter list: • An asterisk (*) in column 1 makes the line a comment. • A parameter/value pair cannot be split across lines. • More than one parameter/value pair may be on a line. • A comma must be used to separate parameter/value pairs. • To continue a parameter list across lines, end the parameter/value pair with a comma followed by a blank. • To end a parameter list, end the last parameter/value pair with a blank, no comma. Member XGPARMDS in the XG.PROD.MLXGnnn.SLXGSAMP dataset contains an example and coding criteria. Using Xchange 5-31 Example Batch Scenario Figure 5-21 shows an example of an Xchange batch step a user might insert in an application: Figure 5-21. Example Batch Steps //* //STEPNAME // //STEPLIB //SYSPRINT //* EXEC PGM=XGCBATCH, PARM=’DATE=1999/12/31,TIME=23:59:59,SUBSYS=XCG1,STEP=STEP01’ DD DSN=CPWR.MLXGnnn.SLXGLOAD,DISP=SHR DD SYSOUT=* When the job containing this step runs, the system date and time are simulated as one second before midnight, December 31, 1999 for step STEP01. Figure 5-22 shows an example of an Xchange batch step a user might insert in an application to simulate a fixed date/time offset of 1234 days, 12 hours, and 15 minutes into the future: Figure 5-22. Example Batch Steps for Date/Time Offset //* //STEPNAME // //STEPLIB //SYSPRINT //* EXEC PGM=XGCBATCH, PARM=’DAYS=1234,HRS=12,MINS=15,IND=+,SUBSYS=XCG1,STEP=STEP01’ DD DSN=CPWR.MLXGnnn.SLXGLOAD,DISP=SHR DD SYSOUT=* Figure 5-23 shows an example of an Xchange batch step that uses dataset XGPARMDS to provide exchange parameters. Figure 5-24 on page 5-31 shows a sample parameter dataset. Note: The PARM values on the EXEC card are ignored because the XGPARMDS DD overrides them. Figure 5-23. Example Batch Steps with Dataset Parameter Input //* //STEPNAME // //STEPLIB //SYSPRINT //XGPARMDS //* EXEC PGM=XGCBATCH, PARM='DATE=1999/12/31,TIME=23:59:59,SUBSYS=XCG1,STEP=STEP01' DD DSN=ACME.LOAD,DISP=SHR DD SYSOUT=* DD DSN=MY.DATETIME.INPUT.FILE,DISP=SHR Figure 5-24. Example Parameter List In a Dataset with a Comment 000001 000002 000003 000004 * PARAMETER LIST IN A DATASET DAYS=9999,MINS=59, HRS=23, SUBSYS=CWXG 5-32 Xpediter/Xchange Installation and User Guide Automatically Deleting Xchange Batch Requests (Optional) You can set up automatic request deletion to free Xchange resources on a job-by-job basis. This optional step can reduce NUMAMB, NUMATB, and NUMXRE resource depletion. If you want to automatically delete an Xchange request set in your batch job, simply add the following step to the job. Figure 5-25. Automatic Request Deletion Batch Step //* //CLEANUP EXEC PGM=XGCLNREQ,COND=EVEN,PARM=’SUBSYS=ssid’ //STEPLIB DD DSN=CPWR.MLXGnnn.SLXGLOAD,DISP=SHR //* Replace CPWR with the high-level qualifier chosen for your site. You must also provide the subsystem ID in place of ssid. Use the subsystem ID specified in the Xchange CMSC PARMLIB member and in the XGCBATCH step previously added to the job. This name was specified by the product installer and is discussed on page 2-6. The default subsystem ID is CWXG. Note: Be sure the XGCBATCH step and this CLEANUP step both refer to the same subsystem ID. Using IMS Message Level Support Xpediter/Xchange’s IMS Message Level Support accomplishes date and time simulation by replacing the values in a message’s IOPCB. The values in the Local Date/Current Date, Local Time/Current Time, and Internal Time Stamp fields are replaced with values based on a user-specified Xchange request. Instead of changing the time and date for an entire IMS control region, Xchange intercepts a message and replaces the IOPCB date and time with the Xchange userrequested values, so that any of the program’s date and time accesses to the IOPCB will return an exchanged value. All Time Services employed by IMS applications — including SVC11, DB2, STCK, STCKE, STCKF the ACCEPT verb, MOVE CURRENT-DATE, and IOPCB — are supported by Xpediter/Xchange. Xchange’s IMS Message Level Support performs date/time simulations in the respective message regions. The IMS user specifies Xchange requests, including both IOPCB and MVS Time Services, on the IMS Simulated Date Time Settings screen shown in Figure 5-26 on page 5-33. Only the message processing regions designated by the user are affected by Xchange. Exchanges are logged in the Xchange journal. CAUTION: Do not use the ISPF Interface to set a region level pattern request for the same message processing region being used for IMS Message Level Support. This combination can cause unpredictable results. Xchange IMS Transaction IDs Xchange can be initiated with either of two separate IMS transactions: • To invoke standard Xchange IMS Message Level Support, type XGTM, plus the usual trailing space, on a blank IMS screen and press Enter. • To invoke Xchange as an administrative user, type XGTS, plus the usual trailing space, on a blank IMS screen and press Enter. Using Xchange 5-33 Administrative users can view and delete Xchange requests for all users or LTERMs in the IMS region. An administrative user can also completely inactivate all Xchange requests by entering the INACTIVATE primary command and activate them by entering the ACTIVATE primary command. Access to the XGTS transaction can be restricted to selected users with your site’s existing security package. Figure 5-26. IMS Simulated Date Time Settings Screen Xpediter/Xchange -- IMS Simulated Date Time Settings -ROW ____ TO ____ Command ===> _______________ Xchange Subsystem ID XG34 UP Active===> YES Line Commands: H - Set and Hold R - Reset P - Permanent D - Delete J - Jobname A - Activate I - Inactivate Status Codes: Request Type or * - Error  -------IOPCB------- ------MVS/HLL------ C A S Owner Req ID Program YYYY/MM/DD HH:MM:SS YYYY/MM/DD HH:MM:SS _ _ _ ________ ________ ________ ____ __ __ __ __ __ =___ __ __ __ __ __ _ _ _ ________ ________ ________ ____ __ __ __ __ __ =___ __ __ __ __ __ _ _ _ ________ ________ ________ ____ __ __ __ __ __ =___ __ __ __ __ __ _ _ _ ________ ________ ________ ____ __ __ __ __ __ =___ __ __ __ __ __ _ _ _ ________ ________ ________ ____ __ __ __ __ __ =___ __ __ __ __ __ _ _ _ ________ ________ ________ ____ __ __ __ __ __ =___ __ __ __ __ __ _ _ _ ________ ________ ________ ____ __ __ __ __ __ =___ __ __ __ __ __ _ _ _ ________ ________ ________ ____ __ __ __ __ __ =___ __ __ __ __ __ _ _ _ ________ ________ ________ ____ __ __ __ __ __ =___ __ __ __ __ __ _ _ _ ________ ________ ________ ____ __ __ __ __ __ =___ __ __ __ __ __ _ _ _ ________ ________ ________ ____ __ __ __ __ __ =___ __ __ __ __ __ _ _ _ ________ ________ ________ ____ __ __ __ __ __ =___ __ __ __ __ __   PF1 HELP PF2 COPYRIGHT/TRADE SECRET NOTICE CLEAR EXIT PF7 BWD PF8 FWD Specifying Requests The IMS Simulated Date Time Settings screen (Figure 5-26) lets you specify requests for simulated system date and time scenarios for your IMS applications. Each line is an entry where you can type information defining which portions of your IMS application or applications are to be tested using Xchange. Each individual entry that you create is called a request. All the entries together constitute the request table, which is stored in the Xchange request file. When you press Enter, any line commands you put in the C field are executed for each corresponding request. The remainder of this section discusses five aspects of using the IMS Simulated Date Time Settings screen: • • • • • primary commands line commands status codes fields PF keys Primary Commands Under Xchange IMS Message Level Support, only the administrative user can enter most of the primary commands. Type primary commands in the COMMAND field at the top of the Xchange screen. The following primary commands are available to the administrative user on the IMS Simulated Date Time Settings screen, and the OFFSET command is available to all users: ACTIVATE 5-34 Xpediter/Xchange Installation and User Guide The ACTIVATE command globally enables Xchange date/time simulation for every active request. Using the ACTIVATE command does not change the activation status of individual requests as displayed in the A field. ADVANCE Use the ADVANCE command to display the Advance Request Settings screen for IMS message level support. For more information, see “Advancing Xchange Requests Using IMS Message Level Support” on page 5-40. INACTIVATE The INACTIVATE command globally disables Xchange date/time simulation for every active request. Using the INACTIVATE command does not change the activation status of individual requests as displayed in the A field. OFFSET Use the OFFSET command to display the IMS Simulated Date Time Settings screen in offset format. This command is available to all users. For more information, see “Using IMS Message Level Support with Date/Time Offset” on page 5-38. PREFIX The PREFIX command allows an administrative user — one who invoked Xchange IMS Message Level Support with the XGTS transaction — to view the requests associated with other user IDs or logical terminals (LTERMs). Type PREFIX userID in the COMMAND field and press Enter to display all Xchange requests for the specified user ID. An asterisk (*) can be used as a wildcard character. Enter PREFIX * to view all requests in the Xchange request file. Enter PREFIX abc*, where abc is a partial user ID or LTERM, to view all the requests of users or terminals that start with that string. Enter PREFIX ? to display the current prefix status. RELEASE The RELEASE command displays the release number of Xpediter/Xchange IMS Message Level Support you are using. If you type RELEASE in the COMMAND field and press Enter, Xchange will display the release number at the bottom of the IMS Simulated Date Time Settings screen. Using Xchange 5-35 Line Commands A line command must be entered to create, modify, or delete an Xchange request. Type line commands in the C field (see “Fields” on page 5-36) and press Enter to execute them. The following line commands are available on the IMS Simulated Date Time Settings screen: H Sets and holds a request for the program specified in the Program field by adding it to the request table. A running time clock for the program will be started at the moment the request is first used and will run parallel to real time. This allows you to test the way your program will behave when an event such as the first second of the year 2000 occurs during processing. The request, including its displacement from the real time and date, is retained until you delete it with the D (Delete) line command or reset it with the R (Reset) line command. H requests are intended for use with programs that run in MPRs. P Sets and holds a permanent-time request for the program specified in the Program field by adding it to the request table. This command is similar to the H line command, except that the time specified is used as the starting point for a running clock on a program by program basis. Each time the request is used by each instance of a program, Xchange provides the request’s specified time and starts its running clock. This differs from H requests which start a running clock the first time the request is used and maintain the request’s time on that single running clock. P requests are intended for use with programs that run in MPRs. J Sets and holds a permanent-time request for the job specified in the Req ID field by adding it to the request table. A running time clock for the job will be started at the moment the request is first used and will run parallel to real time. Each time the request is used by each instance of a job, Xchange provides the request’s specified time and starts its running clock. Only an administrative user can use an asterisk (*) wildcard character as part of the program name specified in the Program field. J requests are intended for use with programs that run in BMPs, IFPs, and WFIs. A Activates the corresponding request so that Xchange date/time simulation will occur. The A field of activated requests displays a Y (yes). You can also overtype the A field with a Y or an N to activate or inactivate a request. The activated status of all requests can be globally overridden by an administrative user with the INACTIVATE command. I Inactivates the corresponding request so that Xchange date/time simulation will not occur. The A field of inactivated requests displays an N (no). You can also overtype the A field with a Y or an N to activate or inactivate a request. R Resets a request after new values have been entered under the IOPCB or MVS/HLL headings in the YYYY/MM/DD and/or HH:MM:SS fields. This allows you to change the date and time for the request without having to re-enter the other fields. None of the other fields can be modified with the R command. D Deletes an existing request. Only administrative users can delete requests associated with user IDs or LTERMs other than their own. The following line command is available on the IMS Advance Request Settings screen: V Advances the requested IOPCB and MVS/HLL date and time or offset of all IMS message level support requests that match the Advance request by the time interval specified in the Advance IOPCB and Advance MVS/HLL fields forward or backward. This command deletes all matching IMS message level support requests, then adds the requests back. A request owned by a different user ID can only be advanced by an Xchange administrator. For information on designating Xchange administrators, see “Designating Administrators” on page 3-30. 5-36 Xpediter/Xchange Installation and User Guide Status Codes Status codes are displayed in the S field next to each Xchange request (see “Fields” on page 5-36). Any of the following status codes can be displayed: H The request was set and held with the H line command. P The request is permanent and was set with the P line command. J The request was set for the jobname in the Req ID field with the J line command. * The request contains an error. Fields Command The field for entry of Xchange primary commands. For a listing and description of primary commands, see “Primary Commands” on page 5-33. Xchange Subsystem ID Displays the MVS ID of the Xchange subsystem and indicates whether the subsystem is up. Active Displays YES or NO to indicate whether active Xchange requests are enabled for date/time simulation. YES is displayed after an ACTIVATE command is entered, and NO is displayed after an INACTIVATE command is entered. C The field for entry of line commands for each Xchange request. For a listing and description of valid line commands, see “Line Commands” on page 5-35. A Displays the activation status of each Xchange request. The letter Y (yes) indicates that the request is active and, if YES is displayed in the ACTIVE field, date/time simulation will occur when the specified program or job is executed. The letter N (no) indicates that the request is inactive. The activated status of all requests can be globally overridden by an administrative user with the INACTIVATE command. S Displays the status of each Xchange request. The letters H, P, or J indicate the request type based on the line command that was used to create it. An asterisk (*) indicates that the request contains an error. Owner Displays the user ID of the person who created the request, if logged onto IMS by user ID, or the LTERM on which the request was created. A user who accessed Xchange with the XGTM transaction can only view requests for which they are the owner. An administrative user can enter the PREFIX primary command to view the requests of any or all Xchange users. See “Primary Commands” on page 5-33. Req ID Displays the user ID, LTERM, or jobname that identifies the request. This field is also used to enter the jobname of requests set with the J line command. For requests set with the H or P line commands, this field defaults to the current user ID or LTERM. An administrative user can also enter the user ID or LTERM of any Xchange user. Program The field for entering the name of the program for which date/time simulation is to be performed. In requests created with the H or P line commands, an asterisk Using Xchange 5-37 wildcard character can be used to specify multiple programs. For example, entering ABC* in the Program field will create a request for all programs whose names begin with ABC that are run under the user ID or LTERM in the Req ID field. If no program name — or a single asterisk — is entered in the Program field, the request will affect every program of the user ID or LTERM in the Req ID field. For requests created with the J line command, only an administrative user can include an asterisk in the Program field. YYYY/MM/DD The year, month, and day that you want Xchange to simulate. The same fields are provided under two headings, IOPCB and MVS/HLL. The date values under the IOPCB heading are substituted for the IOPCB values of the specified program or job. Those under the MVS/HLL heading are used to exchange other MVS and high-level language TIME services calls. The MVS/HLL fields default to the corresponding values entered in the IOPCB fields, as indicated by the equal sign (=) in the first position of the YYYY column. The following entries are valid: YYYY 1900 to 2041 MM 01 to 12 DD 01 to 28 (Feb.) 01 to 29 (Feb. during a leap year) 01 to 30 (Apr., June, Sept., and Nov.) 01 to 31 (Jan., Mar., May, July, Aug., Oct., and Dec.) If you enter a value for the day (DD), the month and year are required. If you enter a value for the month (MM), the year is required. You can enter just the year. This field defaults to the current year, month, and day. Note: If you leave the DD field blank, an error will occur if the current day of the month is invalid for the month you specified — for example, if you entered February on July 31. HH:MM:SS The hour, minute, and second that you want Xchange to simulate for the specified date. The same fields are provided under two headings, IOPCB and MVS/HLL. The time values under the IOPCB heading are substituted for the IOPCB values of the specified program or job. Those under the MVS/HLL heading are used to exchange other MVS and high-level language TIME services calls. The MVS/HLL fields default to the corresponding values entered in the IOPCB fields, as indicated by the equal sign (=) in the first position of the YYYY column. The following entries are valid: HH 00 to 23 MM 00 to 59 SS 00 to 59 If you enter a value for seconds (SS), the hour and minutes are required. If you enter a value for minutes (MM), the hour is required. You can enter just the hour in this field. If only hours or hours and minutes values are entered, the remaining fields will default to the time at which the request is created. If no values are entered, this field displays all zeros and defaults to the running current hour, minute, and second at the time of task execution. message area The line below the request entry fields is used to display Xchange and IMS messages. 5-38 Xpediter/Xchange Installation and User Guide PF Keys IMS Message Level Support recognizes the following function keys which are also displayed at the bottom of the IMS Simulated Date Time Settings screen: • • • • • PF1 (Help) PF2 (Copyright/Trade Secret Notice) PF7 (Scroll Up) PF8 (Scroll Down) Clear (Exit Xchange). Comparison of Request Types Table 5-1 presents a comparison of the three different types of IMS Message Level Support Xchange requests set with the P, H, and J line commands. The table summarizes the values displayed or entered in each request field and notes any differences associated with use of the administrative user XGTS transaction. Table 5-1. Request Field IMS Request Types Request Line Command (C Field) P H J Owner Displays User ID or LTERM of request Displays User ID or LTERM of request Displays User ID or LTERM of request owner. owner. owner. Req ID Leave blank. Defaults to UserID or LTERM. (Administrative user only can enter user ID or LTERM.) Program Name of program to be exchanged. Name of program to be exchanged. Name of program to be exchanged. May not include an asterisk. (Only May end with an asterisk. Default is May end with an asterisk. Default is administrative users can include an asterisk. asterisk. asterisk.) IOPCB Date and time to be exchanged for IOPCB date and time. Date and time to be exchanged for IOPCB date and time. Date and time to be exchanged for IOPCB date and time. Date and time to be exchanged for MVS/HLL MVS/HLL date and time. See note below. Date and time to be exchanged for MVS/HLL date and time. See note below. Date and time to be exchanged for MVS/HLL date and time. See note below. Leave blank. Defaults to UserID or LTERM. (Administrative user only can enter user ID or LTERM.) Enter jobname of BMP, IFP, or MPP to be exchanged. Note: The date/time of an Xchange request set on the ISPF Simulated Date Time Settings screen overrides the MVS/HLL date/time set on the IMS Simulated Date Time Settings screen. This ensures that multiple-step jobs which include BMPs, MPPs, or IFPs are given a consistent date and time. Using IMS Message Level Support with Date/Time Offset In addition to standard Xchange IMS requests used to specify a particular date and/or time, you can create IMS requests based on a fixed offset from the current date and time when the IMS transaction is started. To create Xchange IMS date/time offset requests, first enter the OFFSET primary command on the IMS Simulated Date Time Settings screen as described in “Primary Commands” on page 5-33. The screen is redisplayed in IMS date/time offset format as shown in Figure 527. Create Xchange requests as you would using the standard IMS format, but use the IOPCB and MVS/HLL fields to specify how far in the future or past you want Xchange to simulate. Other fields, status codes, and commands are the same as those described in “Using IMS Message Level Support” on page 5-32. Using Xchange 5-39 Figure 5-27. IMS Simulated Date Time Settings Screen in Offset Format  Xpediter/Xchange -- IMS Simulated Date Time Settings -ROW 0001 TO 0001 Command===> Xchange Subsystem ID XG40 UP Active===> YES Line Commands: H - Set and Hold P - Permanent R - Reset D - Delete J - Jobname A - Activate I - Inactivate Status Codes: Request Type or * - Error C A S N H Owner ACMJET0 Req ID ACMJET0 Program XGICOBLE -------IOPCB------Days Hrs Mins Ind 0100 00 00 +    PF1 HELP PF2 COPYRIGHT/TRADE SECRET NOTICE ------MVS/HLL------ Days Hrs Mins Ind 0100 00 00 + = = = = = = = = = = = CLEAR EXIT PF7 BWD PF8 FWD Fields Use the IOPCB and MVS/HLL fields to specify how far into the future or past you want Xchange to simulate the date and time for a request. For example, if you type 364 in the IOPCB Days field, 23 in the Hrs field, 59 in the Mins field, and + in the Ind field of an IMS request, Xchange will substitute a date and time nearly one year into the future for the specified program or job. The same constants fields are provided under two headings, IOPCB and MVS/HLL. The date/time offset values under the IOPCB heading are substituted for the IOPCB values of the specified program or job. Those under the MVS/HLL heading are used to exchange other MVS and high-level language TIME services calls. The MVS/HLL fields default to the corresponding values entered in the IOPCB fields, as indicated by the equal sign (=) in the first position of the MVS/HLL Days column. The descriptions below apply to both the IOPCB and MVS/HLL constants fields. The S portion of the C/A/S field is display-only. You can type data into all other fields. Note: Only those fields unique to Xchange’s IMS date/time offset format are described in this section. For descriptions of other fields, see “Fields” on page 5-36. Days The number of days into the future or past that you want Xchange to simulate. Valid entries are from 0 to 9999. The default is 0. Hrs The number of hours into the future or past that you want Xchange to simulate. Valid entries are from 0 to 23. The default is 0. Mins The number of minutes into the future or past that you want Xchange to simulate. Valid entries are from 0 to 59. The default is 0. Ind Used to indicate the direction, future or past, that you want Xchange to simulate. Valid entries are + (plus) for an offset into the future and - (minus) for an offset into the past. The default is +. If the PREVDATE parameter is set to NO (see “Step 1. Specify Xchange Parameters” on page 3-2), date/time offsets into the past are not 5-40 Xpediter/Xchange Installation and User Guide allowed. Advancing Xchange Requests Using IMS Message Level Support In addition to requests that simulate date and time substitution, you can create requests that will advance the date and time of any IMS message level support request they match. To create Xchange Advance requests, first enter the ADVANCE primary command on the Simulated Date Time Settings screen for IMS message level support as described in “Primary Commands” on page 5-33. The Advance Request Settings screen is displayed as shown in Figure 5-28. Create Xchange Advance requests as you would any other IMS message level support request, but use the three request identifier fields—A (Activation), Req ID, and Program—as masks to match those IMS message level support requests you want to advance, and use the Advance IOPCB and Advance MVS/HLL offset fields to specify how many days, hours, and minutes you want Xchange to advance those requests forward or backward. Figure 5-28. Advance Request Settings Screen for IMS Message Level Support   XPEDITER/Xchange Command===> Line Commands: Status Codes: C A S Owner -- Advance Request Settings -ROW 0001 TO 0001 Xchange Subsystem ID XG7C UP Active===> YES H - Set and Hold Request Type or Req ID Program R - Reset * - Error ---Advance IOPCB--Days Hrs Mins Ind    PF1 HELP D - Delete PF2 COPYRIGHT/TRADE SECRET NOTICE V - Advance --Advance MVS/HLL-- Days Hrs Mins Ind =  =  =  =  =  =  =  =  =  =  =  =  CLEAR EXIT PF7 BWD PF8 FWD Fields Use the Advance IOPCB and Advance MVS/HLL fields to specify the time interval you want Xchange to age IMS message level requests forward or backward. For example, if you type 1 in the Advance IOPCB Days field, 12 in the Hrs field, and + in the Ind field, Xchange will age all matching IMS message level requests forward 1 day and 12 hours. Days This field is used to enter the number of days by which to age matching requests. The default is 0000. Any numeric value is valid. Hrs This field is used to enter the number of hours by which to age matching requests. The default is 00. Valid entries are from 00 to 23. Mins This field is used to enter the number of minutes by which to age matching requests. The default is 00. Valid entries are from 00 to 59. Using Xchange 5-41 Ind This field is used to specify whether to advance matching requests forward or backward. Valid entries are + (plus) to advance forward and - (minus) to advance backward. The default is + (forward). If the PREVDATE parameter is set to NO (see “Step 1. Specify Xchange Parameters” on page 3-2), advancing the requested date and time, or offset, of an existing request prior to the current date is not allowed. Example Advancing IMS Message Level Support Requests In this example, two IMS message level support requests are in held status, as shown in Figure 5-29. Queued offset requests, like the one for XGICOB, are displayed without a specific date and time. Figure 5-29. IMS Message Level Support Requests Held  XPEDITER/Xchange -- IMS Simulated Date Time Settings -ROW 0001 TO 0002 Command===> Xchange Subsystem ID XG7C UP Active===> YES Line Commands: H - Set and Hold P - Permanent R - Reset D - Delete J - Jobname A - Activate I - Inactivate Status Codes: Request Type or * - Error C A S N H Y H Owner ACMJET0 ACMJET0 Req ID ACMJET0 ACMJET0 Program XGICOB XGICOBLE -------IOPCB------YYYY/MM/DD HH:MM:SS 2001 01 01 01 01 01 ------MVS/HLL------ YYYY/MM/DD HH:MM:SS  2002 02 02 02 02 02  Note: The OFFSET primary command can be used to display the Simulated Date Time Settings screen in offset format (Figure 5-30), allowing you to view the offsets for the request related to program XGICOB. Figure 5-30. IMS Message Level Support Request Showing Offsets  XPEDITER/Xchange -- IMS Simulated Date Time Settings -ROW 0001 TO 0001 Xchange Subsystem ID XG7C UP Active===> YES Command===> Line Commands: H - Set and Hold P - Permanent R - Reset D - Delete J - Jobname A - Activate I - Inactivate Status Codes: Request Type or * - Error C A S N H Owner ACMJET0 Req ID ACMJET0 Program XGICOB -------IOPCB------Days Hrs Mins Ind 1111 11 11 + ------MVS/HLL------ Days Hrs Mins Ind 2222 22 22 + =  = The ADVANCE primary command can be entered on the IMS Simulated Date Time Settings screen shown in Figure 5-29 to display the Advance Request Settings screen shown in Figure 5-31. An Advance request is entered on the Advance Request Settings screen using the Set and Hold (H) line command, specifying that Xchange should advance the requested date and time or offset of any IMS message level support request whose request identifier fields—A (Activation), Req ID, and Program—match that set below. The IOPCB requested dates and times or offsets will be advanced by 2 days, 2 hours, and 2 minutes forward and the MVS/HLL requested dates and times or offsets will be advanced by 1 day, 1 hour, and 1 minute backward at such time when the Advance is requested. For now, the Advance request is held. 5-42 Xpediter/Xchange Installation and User Guide Figure 5-31. Advance Request Settings Screen   XPEDITER/Xchange Command===> -- Advance Request Settings -ROW 0001 TO 0001 Xchange Subsystem ID XG7C UP Active===> YES Line Commands: Status Codes: H - Set and Hold Request Type or C A S * H Req ID ACMJET0 Owner ACMJET0 Program XGICOB* R - Reset * - Error D - Delete ---Advance IOPCB--Days Hrs Mins Ind 0002 02 02 + V - Advance --Advance MVS/HLL-- Days Hrs Mins Ind 0001 01 01 - =  = The Advance line command V is entered beside this request. An asterisk (*) in the A (Activation) field indicates that both Y and N (activated and not activated) matching requests will be advanced. Figure 5-32. Advance Request Settings Screen with V Line Command   XPEDITER/Xchange Command===> -- Advance Request Settings -ROW 0001 TO 0001 Xchange Subsystem ID XG7C UP Active===> YES Line Commands: Status Codes: H - Set and Hold Request Type or C A S V * H Req ID ACMJET0 Owner ACMJET0 Program XGICOB* R - Reset * - Error D - Delete ---Advance IOPCB--Days Hrs Mins Ind 0002 02 02 + V - Advance --Advance MVS/HLL-- Days Hrs Mins Ind 0001 01 01 - = = Once completed, the IOPCB requested date and time or offset of any IMS message level support request whose request identifier fields match the Advance request masks is advanced by 2 days, 2 hours, and 2 minutes forward, as shown in Figure 5-33. Likewise, the MVS/HLL requested date and time or offset of any matching IMS message level support request is advanced by 1 day, 1 hour, and 1 minute backward, as shown in Figure 5-34. Figure 5-33. Simulated Date Time Settings Screen with Advance Request  XPEDITER/Xchange -- IMS Simulated Date Time Settings -ROW 0001 TO 0002 Command===> Xchange Subsystem ID XG7C UP Active===> YES Line Commands: H - Set and Hold P - Permanent R - Reset D - Delete J - Jobname A - Activate I - Inactivate Status Codes: Request Type or * - Error C A S N H Y H Owner ACMJET0 ACMJET0 Req ID ACMJET0 ACMJET0 Program XGICOB XGICOBLE -------IOPCB------YYYY/MM/DD HH:MM:SS 2001 01 03 03 03 01 ------MVS/HLL------ YYYY/MM/DD HH:MM:SS  2002 02 01 01 01 02  Using Xchange 5-43 Figure 5-34. Simulated Date Time Settings Screen with Advance Request Showing Offsets  XPEDITER/Xchange -- IMS Simulated Date Time Settings -ROW 0001 TO 0002 Command===> Xchange Subsystem ID XG7C UP Active===> YES Line Commands: H - Set and Hold P - Permanent R - Reset D - Delete J - Jobname A - Activate I - Inactivate Status Codes: Request Type or * - Error C A S N H Owner ACMJET0 Req ID ACMJET0 Program XGICOB -------IOPCB------Days Hrs Mins Ind 1113 13 13 + ------MVS/HLL------ Days Hrs Mins Ind 2221 21 21 - =  = Using the Extended Batch Facility Xchange’s Extended Batch Facility lets you add, delete, and list batch, CICS, and IMS requests from outside of the ISPF, batch, CICS, and IMS interfaces. In addition, it allows you to advance the date and time of an existing batch, CICS, and IMS request any number of valid days, hours, and minutes in the future or past. Xchange requests stored in an 80-byte sequential file are input to a stand-alone job. This job either adds, deletes, lists, and/or advances the request to or from the specified active Xchange subsystem. It also produces a total of up to six reports (Batch Date/Time, Batch Offset, CICS Date/Time, CICS Offset, IMS Date/Time, and IMS Offset), echoing the request and any reason why it may not have been processed successfully, as well as the total number of records processed. In this way, Xchange requests can now be attached to and actioned as part of an automated test suite. No CICS regions need to be active at the time the stand-alone job is run for any CICS request specified. No IMS regions need to be active at the time the stand-alone job is run for any IMS request specified. Modify and Run JCL Sample JCL to define a PDS or PDSE to hold Xchange requests is provided in CPWR.MLXGnnn.SLXGCNTL PDS member DEFXSEQ. Modify and run the sample JCL and create Xchange requests in the PDS or PDSE member as directed by the template shown in Figure 5-35 and Figure 5-36. Sample JCL to run the Extended Batch Facility can be found in dataset CPWR.MLXGnnn.SLXGCNTL PDS member XGSEQJCL. The SORT step is optional and sorts the requests by Xchange subsystem identifier followed by fields that identify the request. Modify and run the sample JCL to add, delete, list, or advance Xchange requests to or from the specified active Xchange subsystem. Sequential File Template The template for the sequential file containing the fixed layout of Xchange requests is shown in Figure 5-35 on page 5-44 and Figure 5-36 on page 5-45. 5-44 Xpediter/Xchange Installation and User Guide Figure 5-35. Sequential File Template — Part 1 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * TEMPLATE FOR THE EXTENDED BATCH FACILITY INPUT FILE ASTERISK IN COLUMN 1 IS A COMMENT KEY --- T = TYPE OF REQUEST: REQUIRED - (B)ATCH, (C)ICS, OR (I)MS O = OFFSET REQUEST: OPTIONAL - (N)DEFAULT OR Y (REQUIRED FOR ADVANCE) FOR DELETE REQUESTS, USED ONLY FOR REPORTING PURPOSES SSID = XCHANGE SUBSYSTEM IDENTIFIER: REQUIRED C = COMMAND: REQUIRED BATCH: (S)ET, (H)OLD, (D)ELETE, (A)DD ACTIVE, (L)IST, AD(V)ANCE CICS: (H)OLD, (P)ERMANENT, (D)ELETE, (L)IST, AD(V)ANCE IMS: (H)OLD, (P)ERMANENT, (A)CTIVATE, (I)NACTIVATE, (D)ELETE, (L)IST, AD(V)ANCE DELETE REQUESTS CANNOT BE WILDCARDED TO DELETE MORE THAN 1 REQUEST. THE DATE/TIME IDENTIFICATION FIELDS, THE ASYNCHRONOUS FIELD (CICS), AND THE ACTIVE FIELD (IMS) ARE NOT REQUIRED. FOR IMS ACTIVATE AND INACTIVATE REQUESTS, THE DATE/TIME IDENTIFICATION FIELDS AND THE ACTIVE FIELD ARE NOT REQUIRED. THE REQUEST IDENTIFICATION FIELDS ARE OPTIONAL FOR THE (L)IST AND AD(V)ANCE COMMANDS. THE REQUEST IDENTIFICATION FIELDS MAY CONTAIN AN ASTERISK IN THE LAST CHARACTER TO WILDCARD A REQUEST. THE DATE/TIME IDENTIFICATION FIELDS ARE IGNORED FOR THE (L)IST COMMAND. THE DAYS, HOURS, AND/OR MINUTES, AND INDICATOR SHOULD BE SPECIFIED FOR THE AD(V)ANCE COMMAND. EVEN THOUGH SPECIFIED AS AN OFFSET REQUEST, IT ADVANCES ALL REQUESTS THAT MATCH THE SPECIFIED CRITERIA. REQUEST IDENTIFICATION FIELDS ----------------------------- JOBNAME: REQUIRED; NOT VALID FOR CICS AND IMS REQUESTS APPLID = APPLID OF THE CICS REGION: REQUIRED; NOT VALID FOR BATCH AND IMS REQUESTS STEPNAME: OPTIONAL; DEFAULT(*); NOT VALID FOR CICS AND IMS REQUESTS USERID = OPTIONAL: DEFAULT(*); USERID FOR WHICH TO SIMULATE THE DATE AND TIME CHANGE; NOT VALID FOR BATCH REQUESTS PROCSTEP: OPTIONAL; DEFAULT(*); NOT VALID FOR CICS AND IMS REQUESTS TERM = OPTIONAL: DEFAULT(*); NAME OF THE CICS TERMINAL FOR WHICH TO SIMULATE THE DATE AND TIME CHANGE; NOT VALID FOR BATCH AND IMS REQUESTS TRAN = OPTIONAL: DEFAULT(*); CICS TRANSACTION NAME; NOT VALID FOR BATCH AND IMS REQUESTS PROGRAM: OPTIONAL; DEFAULT(*) A = ASYNCHRONOUS (CICS): OPTIONAL - (Y)DEFAULT OR N; NOT VALID FOR BATCH AND IMS REQUESTS A = ACTIVE (IMS): OPTIONAL - Y OR (N)DEFAULT; FOR (L)IST AND AD(V)ANCE COMMANDS, THE DEFAULT IS ASTERISK(*); NOT VALID FOR BATCH AND CICS REQUESTS Using Xchange 5-45 Figure 5-36. Sequential File Template — Part 2 * DATE/TIME IDENTIFICATION FIELDS * ------------------------------- * G = GLOBAL HOLD DATA OPTION: OPTIONAL - Y OR (N)DEFAULT; * NOT VALID FOR CICS REQUESTS * * YYYY/MM/DD HH:MM:SS = DATE AND TIME OF THE REQUEST: OPTIONAL - * DEFAULT IS CURRENT DATE AND TIME; * NOT VALID FOR OFFSET REQUESTS * * DDDD HH MM I = DAYS, HOURS, MINUTES, AND INDICATOR FROM CURRENT DATE * AND TIME FOR OFFSET REQUESTS; * DAYS, HOURS, MINUTES, AND INDICATOR FROM REQUESTED * DATE AND TIME FOR ADVANCE REQUESTS: * * REFER TO THE XPEDITER/XCHANGE INSTALLATION AND USER'S GUIDE FOR MORE * DETAILED INFORMATION ABOUT THESE FIELDS * * 1 2 3 4 5 6 7 *234567890123456789012345678901234567890123456789012345678901234567890 * *BATCH DATE/TIME REQUESTS * *T O SSID C JOBNAME STEPNAME PROCSTEP PROGRAM G YYYY/MM/DD HH:MM:SS *- - ---- - -------- -------- -------- -------- - ---- -- -- -- -- -- * *BATCH OFFSET AND ADVANCE REQUESTS * *T O SSID C JOBNAME STEPNAME PROCSTEP PROGRAM G DDDD HH MM I *- - ---- - -------- -------- -------- -------- - ---- -- -- - * *CICS DATE/TIME REQUESTS * *T O SSID C APPLID USERID TERM TRAN PROGRAM A YYYY/MM/DD HH:MM:SS *- - ---- - -------- -------- ---- ---- -------- - ---- -- -- -- -- -- * *CICS OFFSET AND ADVANCE REQUESTS * *T O SSID C APPLID USERID TERM TRAN PROGRAM A DDDD HH MM I *- - ---- - -------- -------- ---- ---- -------- - ---- -- -- - * *IMS DATE/TIME REQUESTS * IOPCB MVS/HLL *T O SSID C USERID PROGRAM A YYYY/MM/DD HH:MM:SS YYYY/MM/DD HH:MM:SS *- - ---- - -------- -------- - ---- -- -- -- -- -- ---- -- -- -- -- -- * *IMS OFFSET AND ADVANCE REQUESTS * IOPCB MVS/HLL *T O SSID C USERID PROGRAM A DDDD HH MM I DDDD HH MM I *- - ---- - -------- -------- - ---- -- -- ---- -- -- - Extended Batch Facility Sample Reports Sample reports produced from the Extended Batch Facility are shown in the following figures.  Figure 5-37. Sample Extended Batch Facility Reports — D, H, P, S, I, and A Commands (Part 1, Batch and CICS)  JAN 27 2016 06:46:48 COMPUWARE CORPORATION XPEDITER/XCHANGE XGSETREQ INPUT REPORT BATCH DATE/TIME REQUESTS   PAGE 00001 SSID CMD JOBNAME STEPNAME ---- --- -------- -------XG50 S JOBA* STEP1 XG50 H JOBB* STEP1 XG50 H JOBB145 STEP1 XG50 D PPRRZC0A * PROCSTEP -------* * * * PROGRAM -------PGMA PGMB PGMC * GHD --N Y Y YYYY/MM/DD ---------2025 05 05 2026 06 06 2026 06 06 2022 02 02 HH:MM:SS -------05 05 05 06 06 06 06 06 06 02 02 02 ERROR MESSAGE ----------------------------------------------- JOB NAME IS AMBIGUOUS Using Xchange 5-46 TOTAL NUMBER OF REQUESTS PROCESSED = 000004  JAN 27 2016 COMPUWARE CORPORATION PAGE 00001 06:46:48 XPEDITER/XCHANGE XGSETREQ INPUT REPORT  BATCH OFFSET REQUESTS  SSID CMD JOBNAME STEPNAME PROCSTEP PROGRAM GHD DDDD HH MM IND ERROR MESSAGE ---- --- -------- -------- -------- -------- --- ---- -- -- ------------------------------------------------- XG50 S JOBC* STEP1 * PGMC N 1111 01 01 + XG50 H JOBD* STEP1 * PGMD Y 2222 02 02 - XG50 H JOBD145 STEP1 * PGME Y 3333 03 03 JOB NAME IS AMBIGUOUS XG50 D PPRRZC0B * * * 1111 01 01  TOTAL NUMBER OF REQUESTS PROCESSED = 000004  JAN 27 2016 COMPUWARE CORPORATION PAGE 00001 06:46:48 XPEDITER/XCHANGE XGSETREQ INPUT REPORT  CICS DATE/TIME REQUESTS  SSID CMD APPLID USERID TERM TRAN PROGRAM ASYNC YYYY/MM/DD HH:MM:SS ERROR MESSAGE ---- --- -------- -------- ---- ---- -------- ----- ---------- ------------------------------------------------------ XG50 H H40AC319 PPRRZC0 * XGCB * Y 2022 02 02 02 02 02 XG50 P H40AC319 PPRRZC0 * XGCL * Y 2023 03 03 03 03 03 XG50 H H40AC319 PPRRZC0 * XGCB * Y 2022 02 02 02 02 02 DUPLICATE CICS REQUEST XG50 D H40AC319 PPRRZC0 * XGAS * Y 2022 02 02 02 02 02  TOTAL NUMBER OF REQUESTS PROCESSED = 000004  JAN 27 2016 COMPUWARE CORPORATION PAGE 00001 06:46:48 XPEDITER/XCHANGE XGSETREQ INPUT REPORT  CICS OFFSET REQUESTS  SSID CMD APPLID USERID TERM TRAN PROGRAM ASYNC DDDD HH MM IND ERROR MESSAGE ---- --- -------- -------- ---- ---- -------- ----- ---- -- -- ------------------------------------------------- XG50 H H40AC319 PPRRZC0 * XGPL * Y 1111 01 01 XG50 P H40AC319 PPRRZC0 * XGPE * Y 2222 02 02 - XG50 H H40AC319 PPRRZC0 * XGPL * Y 1111 01 01 DUPLICATE CICS REQUEST XG50 D H40AC319 PPRRZC0 * XGCD * Y 1111 01 01  TOTAL NUMBER OF REQUESTS PROCESSED = 000004 Figure 5-38. Sample Extended Batch Facility Reports — D, H, P, S, I, and A Commands (Part 2, IMS)  JUL 26 2016 13:16:44 COMPUWARE CORPORATION XPEDITER/XCHANGE XGSETREQ INPUT REPORT IMS DATE/TIME REQUESTS      SSID CMD ACT USERID ---- --- --- -------XG7C H Y PPRRZC0 XG7C P Y PPRRZC0 XG7C D PPRRZC0 XG7C I PPRRZC0 PROGRAM -------XGICOB XGICOBLE XGITESTA XGITESTC IOPCB YYYY/MM/DD ---------2021 01 01 2022 02 02 HH:MM:SS -------01 01 01 02 02 02 MVS/HLL YYYY/MM/DD ---------2021 01 01 2022 02 02 HH:MM:SS -------01 01 01 02 02 02 ERROR MESSAGE ----------------------------------------------- TOTAL NUMBER OF REQUESTS PROCESSED = 000004 JUL 26 2016 13:16:44 COMPUWARE CORPORATION XPEDITER/XCHANGE XGSETREQ INPUT REPORT PAGE 00001 IMS OFFSET REQUESTS   PAGE 00001 SSID CMD ACT USERID ---- --- --- -------XG7C H PPRRZC0 XG7C P PPRRZC0 XG7C D PPRRZC0 XG7C A PPRRZC0 PROGRAM -------XGIASM XGIPLI XGITESTB XGITESTD IOPCB DDDD HH MM IND ---- -- -- --2000 3000 MVS/HLL DDDD HH MM IND ---- -- -- --2000 3000 ERROR MESSAGE ----------------------------------------------- TOTAL NUMBER OF REQUESTS PROCESSED = 000004 Using Xchange 5-47 Figure 5-39. Sample Extended Batch Facility Reports — L Commands (Part 1, Batch and CICS)  JAN 27 2016 06:46:48 COMPUWARE CORPORATION XPEDITER/XCHANGE XGSETREQ INPUT REPORT BATCH DATE/TIME REQUESTS      SSID CMD JOBNAME STEPNAME PROCSTEP ---- --- -------- -------- -------XG50 L JOBA* STEP1 * JOBB* STEP1 *  TOTAL NUMBER OF REQUESTS PROCESSED = PROGRAM -------PGMA PGMB GHD --N Y  JAN 27 2016 06:46:48 ERROR MESSAGE ----------------------------------------------- PAGE 00001 BATCH OFFSET REQUESTS SSID CMD JOBNAME STEPNAME PROCSTEP ---- --- -------- -------- -------XG50 L JOBC* STEP1 * JOBD* STEP1 *  TOTAL NUMBER OF REQUESTS PROCESSED = PROGRAM -------PGMC PGMD GHD --N Y DDDD ---1111 2222 HH -01 02 MM IND -- --01 + 02 - ERROR MESSAGE ----------------------------------------------- 000001 JAN 27 2016 06:46:48 COMPUWARE CORPORATION XPEDITER/XCHANGE XGSETREQ INPUT REPORT PAGE 00001 CICS DATE/TIME REQUESTS SSID CMD APPLID USERID TERM TRAN ---- --- -------- -------- ---- ---XG50 L H40AC319 PPRRZC0 * XGCB H40AC319 PPRRZC0 * XGCL  TOTAL NUMBER OF REQUESTS PROCESSED = PROGRAM ASYNC YYYY/MM/DD HH:MM:SS -------- ----- ---------- -------* Y 2022 02 02 02 02 02 * Y 2023 03 03 03 03 03 ERROR MESSAGE ----------------------------------------------- 000001 JAN 27 2016 06:46:48 COMPUWARE CORPORATION XPEDITER/XCHANGE XGSETREQ INPUT REPORT PAGE 00001 CICS OFFSET REQUESTS  SSID CMD APPLID USERID TERM TRAN ---- --- -------- -------- ---- ---XG50 L H40AC319 PPRRZC0 * XGPL H40AC319 PPRRZC0 * XGPE  TOTAL NUMBER OF REQUESTS PROCESSED = PROGRAM ASYNC DDDD HH MM IND -------- ----- ---- -- -- --* Y 1111 01 01 * Y 2222 02 02 - ERROR MESSAGE ----------------------------------------------- Using Xchange  HH:MM:SS -------05 05 05 06 06 06 COMPUWARE CORPORATION XPEDITER/XCHANGE XGSETREQ INPUT REPORT     YYYY/MM/DD ---------2025 05 05 2026 06 06 000001     PAGE 00001 000001 5-48 Figure 5-40. Sample Extended Batch Facility Reports — L Commands (Part 2, IMS)  JUL 26 2016 07:22:55 COMPUWARE CORPORATION XPEDITER/XCHANGE XGSETREQ INPUT REPORT IMS DATE/TIME REQUESTS      SSID CMD ACT USERID ---- --- --- -------XG7C L Y PPRRZC0 Y PPRRZC0 PROGRAM -------XGICOB XGICOBLE IOPCB YYYY/MM/DD ---------2021 03 02 2022 04 03 HH:MM:SS -------01 01 01 02 02 02 MVS/HLL YYYY/MM/DD ---------2021 03 02 2022 04 03 HH:MM:SS -------01 01 01 02 02 02 ERROR MESSAGE ------------------------------------------------ TOTAL NUMBER OF REQUESTS PROCESSED = 000001 JUL 26 2016 07:22:55 COMPUWARE CORPORATION XPEDITER/XCHANGE XGSETREQ INPUT REPORT PAGE 00001 IMS OFFSET REQUESTS   PAGE 00001 SSID CMD ACT USERID ---- --- --- -------XG7C L N PPRRZC0 N PPRRZC0 PROGRAM -------XGIASM XGIPLI IOPCB DDDD HH ---- -2090 00 3090 00 MM IND -- --00 + 00 + MVS/HLL DDDD HH ---- -2090 00 3090 00 MM IND -- --00 + 00 + ERROR MESSAGE ------------------------------------------------ TOTAL NUMBER OF REQUESTS PROCESSED = 000001 Using Xchange 5-49 Figure 5-41. Sample Extended Batch Facility Reports — V Commands (Batch, CICS, and IMS) MAY 31 2016 06:11:55  COMPUWARE CORPORATION XPEDITER/XCHANGE XGSETREQ INPUT REPORT PAGE 00001 BATCH OFFSET REQUESTS  SSID CMD JOBNAME STEPNAME PROCSTEP PROGRAM GHD DDDD HH MM IND ERROR MESSAGE ---- --- -------- -------- -------- -------- --- ---- -- -- -------------------------------------------------- XG7C V 0030 +  TOTAL NUMBER OF REQUESTS PROCESSED = 000001    MAY 31 2016 COMPUWARE CORPORATION 06:11:55 XPEDITER/XCHANGE XGSETREQ INPUT REPORT PAGE 00001  CICS OFFSET REQUESTS  SSID CMD JOBNAME STEPNAME PROCSTEP PROGRAM GHD DDDD HH MM IND ERROR MESSAGE ---- --- -------- -------- -------- -------- --- ---- -- -- -------------------------------------------------- XG7C V 0030 -  TOTAL NUMBER OF REQUESTS PROCESSED = 000001    JUL 26 2016 COMPUWARE CORPORATION PAGE 00001 07:19:15 XPEDITER/XCHANGE XGSETREQ INPUT REPORT  IMS OFFSET REQUESTS  IOPCB MVS/HLL SSID CMD ACT USERID PROGRAM DDDD HH MM IND DDDD HH MM IND ERROR MESSAGE ---- --- --- -------- -------- ---- -- -- ------ -- -- -------------------------------------------------- XG7C V N 0030 0030  TOTAL NUMBER OF REQUESTS PROCESSED = 000001 Using Xchange 5-50 Using Xchange 5-51 Using CICS Support Xchange can be used with CICS in two ways: • CICS region support • CICS transaction support. CICS region support and CICS transaction support are available for all current CICS releases. The Assembler TIME macro with LINKAGE=SYSTEM parameter can only be exchanged using CICS region support. CAUTION: Do not use Xchange’s CICS region support and CICS transaction support at the same time. This combination can cause unpredictable results. CICS Region Support Xchange’s CICS region support allows you to exchange the date and time for all transactions and programs running in a CICS region. Either at initialization or in response to a CEMT PERFORM RESET command, CICS issues an SVC11 that can be intercepted and changed by Xchange. CICS then stores the exchanged date and time in an internal CICS control block and maintains the field itself. All subsequent application time requests are given the modified date and time. Xchange also handles any program that issues a time request within the CICS region, including those programs for which STCK, STCKE, and STCKF support has been enabled, as described in “Using Standard STCK and STCKF and Enhanced STCK, STCKE, and STCKF Support” on page 5-69. Xchange’s CICS region support requires additional midnight rollover processing. This processing must be enabled during Xchange installation by performing “Enable Midnight Rollover” on page 3-18. If you are unsure whether that step was performed, midnight rollover processing can also be activated by submitting transaction XGAJ after CICS initialization. Using Language Environment (LE) with Xchange CICS Region Support A zap to LE module CEEPLPKA is required if you want to exchange LE in CICS at the region level. The zap is necessary because LE gets initialized in a way that circumvents the normal dynamic hooking of LE by Xchange. If you plan to use Xchange CICS region support with LE programs, make sure you have followed the instructions in “Enable Language Environment (LE)” on page 3-19. Note: If region level CICS exchanges are required and this zap has been applied, Xchange CICS transaction level support should not be used. Mixing region level and transaction level support concurrently in a CICS environment may cause the date/time value in the EIB to differ from the date and time requested. Enabling Region Support Xchange’s region support can enabled in either of two ways: • Using the ISPF interface • Using a CICS program. Using the ISPF Interface CICS region support is enabled by setting up a request on the Simulated Date Time Settings screen as described in “Using the ISPF Interface” on page 5-3. You can do either of the following: 5-52 Xpediter/Xchange Installation and User Guide • If the region is not yet running, use the S or H line command to set a request with the jobname of the region and the desired date and time. In addition, using the Xchange batch facility step before the CICS region step in the CICS region JCL will initiate CICS region support. See “Using the Batch Facility” on page 5-27 for more information. Note: CICS Region Support initiated by one of the above methods requires STCKSYNC support. • If the region is already active, perform the following steps: a. Use the A line command to set a request with the jobname of the region and the desired date and time. b. To specify a different date/time, use the D line command to delete the request, then repeat the first step. c. When Xchange testing is completed use the D line command to delete the request. Using a CICS Program The interface to Xchange region support can also be initiated using a CICS program instead of an Xchange request. The CICS region must already be active. Use an EXEC CICS LINK from a user-written CICS program to invoke the interface in CICS program XGTADDA. To specify date and time, XGTADDA is passed a 20-byte COMMAREA by the user-written program. A sample program illustrating the invocation is provided in CPWR.MLXGnnn.SLXGSAMP member XGAADDA. The transaction associated with this sample program is XGAA. Each time the user-written CICS program invokes XGTADDA, Xchange deletes any active request for the CICS region, then adds a new request. If the date and time passed in the COMMAREA is spaces, the current date and time are used. To use this type of CICS region support, the load module XGTADDA, located in CPWR.MLXGnnn.SLXGLOAD, must be included in the DFHRPL concatenation of the CICS region’s startup JCL. In addition, the CICS definitions in XGCRDOAA, located in CPWR.MLXGnnn.SLXGDATA, must be defined in the CICS region. Note: CICS region support initiated by XGTADDA requires STCKSYNC support. CICS Transaction Support CICS transaction support lets you exchange the date and time for individual terminals, programs, or transactions within a CICS region without affecting the execution of other terminals, programs, or transactions. The CICS transaction feature supports the exchange of the EIBDATE and EIBTIME fields. These fields are set up on transaction start to reflect the modified date and time that you have requested, and the exchanged values are supplied when the program issues an EXEC CICS ASKTIME request. Note: No I000 messages are generated under CICS transaction support. Using CICS Transaction Support Xchange Transaction IDs Xchange can be initiated with one of three separate CICS transactions: • To invoke standard Xchange CICS transaction support, type XGTM on a blank CICS screen and press Enter. • To invoke Xchange as an authorized user, type XGTS on a blank CICS screen and press Enter. Using Xchange 5-53 • To invoke Xchange using input from a PDS or PDSE instead of entering it on the Simulated Date Time Settings screen, type XGTN on a blank CICS screen and press Enter. See “Using Xchange CICS Transaction Support with Input from a PDS or PDSE” for more information. Authorized users can view and delete Xchange requests for all terminals in the CICS region. Also, an authorized user can completely shut down Xchange in the entire region by entering the STOP primary command. This can be useful when used with the NEWCOPY function of CICS to load a new copy of an Xchange module to which maintenance has been applied. The new version of the module will be loaded without cycling your CICS system. Access to the XGTS, XGTM, and XGTN transactions can be restricted to selected users with your site’s existing security package. Deleting Requests A third Xchange transaction, XGTD, deletes all requests owned by the current terminal ID. To run the transaction, type XGTD on a blank CICS screen and press Enter. This will delete all requests for the terminal without first having to display them. Another method of deleting the Xchange requests owned by your terminal is to enter XGTM on a blank CICS screen, then type END in the COMMAND field and press Enter. The authorized user can delete every request in a CICS region by entering XGTS on a blank CICS screen, then typing END ALL in the COMMAND field and pressing Enter. Specifying the Subsystem The first time you invoke Xchange CICS transaction support, one of the following occurs: • If no subsystem is running, the Subsystem Identification screen is displayed with the message shown in Figure 5-42. After you have started a subsystem, you must either type the subsystem ID on this screen, or reinvoke the Xchange transaction. • If more than one subsystem is running, the Subsystem Identification screen (Figure 5-43) is displayed with a list of running subsystems. You must select the subsystem you want to use. The subsystem selected will be used for all requests in this CICS region. • If only one subsystem is running, Xchange will immediately display the Simulated Date Time Settings screen shown in Figure 5-44 on page 5-55. After a subsystem has been specified (if necessary), each time Xchange is invoked, the Simulated Date Time Settings screen will immediately be displayed. 5-54 Xpediter/Xchange Installation and User Guide Figure 5-42. Subsystem Identification Screen with No Active Subsystem                   Xpediter/Xchange --------- Subsystem Identification --------------------------- COMMAND ===> No Xchange subsystem active - enter name when started ____ Copyright (C) 2003, 2007 by Compuware Corporation. All rights reserved Compuware Xpediter/Xchange Release 4.0.0 Figure 5-43. Subsystem Identification Screen with Choice of Active Subsystems                  Xpediter/Xchange --------- Subsystem Identification --------------------------- COMMAND ===> Choose subsystem to be used - enter "S" to make selection XG40 XG4A Copyright (C) 2003, 2007 by Compuware Corporation. All rights reserved Compuware Xpediter/Xchange Release 4.0.0 Specifying Requests The Simulated Date Time Settings screen (Figure 5-44) lets you specify requests for simulated system date and time scenarios for your applications. Using Xchange 5-55 Figure 5-44. Simulated Date Time Settings Screen for CICS Transaction Support   Xpediter/Xchange ------ Simulated Date Time Settings ------ Row 1 to 0 of 0 COMMAND ===> Scroll ===> PAGE Line Commands: H - Set and Hold P - Permanent R - Reset D - Delete Status Codes: H - Held P - Permanent C - Completed * - Error T - Threshold C/S Owner UserID Async Terminal TransID Program YYYY/MM/DD HH:MM:SS TASK NO _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ ============================================================================== PF1 Help PF2 COPYRIGHT/TRADE SECRET NOTICE PF3 END PF7 BWD PF8 FWD Each line is an entry where you can type information defining which portions of your application or applications are to be tested using Xchange. Each individual entry that you create is called a request. All the entries together constitute the request table. When you press Enter, the commands you put in the C portion of the C/S field are executed for each corresponding request. The remainder of this section discusses five aspects of using the Simulated Date Time Settings screen: • • • • • primary commands line commands status codes fields PF keys Primary Commands Type primary commands in the COMMAND field at the top of the Xchange screen. The following primary commands are available on the Simulated Date Time Settings screen: ADVANCE Use the ADVANCE command to display the Advance Request Settings screen. The command can be abbreviated as ADV. For more information, see “Advancing Xchange Requests Using CICS Transaction Support” on page 5-62. END The END command deletes all requests associated with the current terminal ID. If the ALL parameter is specified, all requests that have been displayed using the PREFIX 5-56 Xpediter/Xchange Installation and User Guide command will be deleted. This allows an authorized user to selectively delete all the requests associated with a particular terminal or with all terminals in the CICS region. LIST The LIST command without any parameters is used to display all Xchange requests that apply to the current terminal ID and user ID. Such requests may have been created by the Xchange authorized user using wildcards for term ID or user ID. Type LIST ALL and press Enter to also display messages. The requests and messages are not modifiable by a standard Xchange user unless they were created by that user. Type LIST OFF and press Enter to suppress the display of those requests. Type LIST ? and press Enter to display the current request viewing status of LIST ALL, LIST OFF associated with a particular terminal or with all terminals in the CICS region. MAX The MAX command is actually a scrolling parameter used with the PF7 and PF8 keys to move quickly to the top or bottom of the entries on the Simulated Date Time Settings screen. The command can be abbreviated as M. MSG Each time a request is completed, a message entry with a status of C is added to the request table. The MSG command can be used to suppress the display of these messages. This can reduce the need for scrolling and make it easier to view more requests on a single screen. Suppress message display by typing MSG OFF in the COMMAND field and pressing Enter. To redisplay the suppressed messages, type MSG ON — or simply MSG — in the COMMAND field and press Enter. Type MSG ? to display the status of the message display function. ON is the default. OFFSET Use the OFFSET command to display the Simulated Date Time Settings screen for CICS transaction support in offset format. The command can be abbreviated as OFF. For more information, see “Using CICS Transaction Support with Date/Time Offset” on page 5-60. Using Xchange 5-57 PREFIX The PREFIX command is used to revise the display of the Xchange requests. A request is displayed if any of the following are true: • The current prefix value matches the request’s originating terminal ID (owner field). • The current userID matches the CICS default userID and the current prefix value matches the request’s terminal ID (terminal field). • The current userID does not match the CICS default userID but does match the request’s userID. All users may issue the PREFIX and PREFIX ? commands. Only authorized users may issue the PREFIX termid and PREFIX * commands. PREFIX Sets the prefix value to the current terminal ID. PREFIX ? Displays the requests using the current prefix value. PREFIX termID Sets the prefix value to the specified value. A trailing asterisk (*) may be used as a wildcard. If a wildcard is entered, it is used only for the match to the originating terminal ID (owner field) as in the first selection rule above. PREFIX * Sets the prefix value to an asterisk (*). This will display all requests set from all terminals in the region. RELEASE The RELEASE command displays the release number of Xpediter/Xchange you are using. If you type RELEASE in the COMMAND field and press Enter, Xchange will display the release number just above the SCROLL field. Press Enter again to toggle the release number off. STOP The STOP command is used to terminate Xchange transaction support in the current CICS region. Because the STOP command halts Xchange for every terminal in the region, it can only be used by an authorized user and should not be used just to end an Xchange session on a single terminal. To end the Xchange session on your terminal, simply clear the screen. 5-58 Xpediter/Xchange Installation and User Guide Line Commands Type line commands in the C portion of the C/S field (see “Fields” on page 5-58). The following line commands are available on the Simulated Date Time Settings screen: H Sets and holds a request by adding it to the request table. A running time clock for the transaction/program will be started at the moment the request is first used and will run parallel to real time. This allows you to test the way your program or transaction will behave when an event such as the first second of the year 2000 occurs during processing. If the request is set for a specific program, the time and date will be exchanged only for that program — not for the entire transaction. The request, including its displacement from the real time and date, is retained until you delete it with the D (Delete) line command. D Deletes an existing request and its related transactions/programs (if applicable). Only authorized users can delete requests associated with terminal IDs other than their own. R Resets a request after new values have been entered in the YYYY/MM/DD and/or HH:MM:SS fields. This allows you to change the date and time for the request without having to retype every field. None of the other fields can be modified with the R command. P Sets and holds a permanent-time request by adding it to the request table. This command is similar to the H line command, except that the time specified is used as the starting point for a running clock on a transaction by transaction basis. The first time the request is used by each instance of a transaction, Xchange provides the request’s specified time and starts its running clock. This differs from H requests which start a running clock the first time the request is used and maintain the request’s time on that single running clock. V Advances the requested date and time or offset of all CICS transaction support Date/Time and Offset requests that match the Advance request by the time interval specified in the Advance offset forward or backward. This command deletes all matching CICS transaction support Date/Time and Offset requests along with their completed entries, then adds the requests back. Only the Line Command field is recognized when advancing a request. A request owned by a different user ID can only be advanced by an Xchange administrator. For information on designating Xchange administrators, see “Designating Administrators” on page 3-30. Status Codes Status codes appear under the S portion of the C/S field (see “Fields” on page 5-58). Any of the following status codes can appear: H The request is held. P The request is permanent. C The request has completed. * The request contains an error. T Threshold has been reached. A CICS complete message has been suppressed for the request based on the threshold value specified for the CICSMAXR or CICSMAXS parameter. For more information, see “Step 1. Specify Xchange Parameters” on page 3-2. Fields The Owner and Task No. fields and the S portion of the C/S field are display-only. You can type data into all of the other fields. Completed exchanges are displayed below their corresponding requests. Beginning with Xchange 3.1, you can specify userID and, depending on your release of CICS, asynchronous (non-terminal) transactions for date/time simulation on the same Using Xchange 5-59 Xchange request. Table 5-2 explains the use and behavior of the UserID, Async, and Terminal fields for a normal user, a normal user not logged onto the region, and an authorized user. Table 5-2. UserID, Terminal, and Async Fields by User Type Screen Field Defaults User Type Behavior When Setting Requests UserID Normal Logged on * userID Normal * (not logged on) Authorized Terminal Current termID Logged on * userID Async YES Terminal can be specified. UserID cannot be changed. NO Only current termID and NONE allowed in Terminal field. YES UserID and Terminal can be specified. NONE or * forces Async YES. Async cannot be changed. C/S The command and status display for each entry. You can enter line commands under the C portion of the field. For a listing and description of the line commands, see “Line Commands” on page 5-58. Status codes are displayed under the S portion of the field. For a listing and description of the status codes, see “Status Codes” on page 5-58. Owner The terminal ID of the user who defined the request or a four-character message code. This is a display-only field. For more information on the message codes, see “Owner Field Messages” on page A-1. UserID The userID the request will affect. The default for this field varies by the type of user. See Table 5-2 on page 5-59. Async Indicates whether asynchronous transactions that meet the request criteria are to be exchanged. Terminal The name of the CICS terminal ID for which to simulate the system date and time. Specify NONE to exchange only asynchronous transactions. With an asterisk in the Terminal field, all terminals and asynchronous tasks in the CICS region are eligible for the specified exchange. The default for this field varies by the type of user. See Table 5-2 on page 5-59. TransID The name of a specific or generic transaction ID for which to exchange dates. To specify a single ID, enter the exact ID in this field. You can use a wildcard feature by substituting an asterisk (*) anywhere in the transaction ID. Specifying only an asterisk in this field requests all transaction IDs in a request. The TransID field defaults to asterisks. Program The name of a specific or generic program for which to exchange dates. You can specify a single program by entering the exact program name in this field. To specify multiple programs, substitute an asterisk (*) anywhere in the program name. If you enter only an asterisk in this field, all programs are requested. The Program field defaults to an asterisk. 5-60 Xpediter/Xchange Installation and User Guide YYYY/MM/DD The year, month, and day that you want Xchange to simulate. The following entries are valid: YYYY 1900 to 2041 MM 01 to 12 DD 01 to 28 (Feb.) 01 to 29 (Feb. during a leap year) 01 to 30 (Apr., June, Sept., and Nov.) 01 to 31 (Jan., Mar., May, July, Aug., Oct., and Dec.) If you enter a value for the day (DD), the month and year are required. If you enter a value for the month (MM), the year is required. You can enter just the year. This field defaults to the current year, month, and day. If you leave the DD field blank, an error will occur if the current day of the month is invalid for the month you specified — for example, if you entered February on July 31. HH:MM:SS The hour, minute, and second that you want Xchange to simulate for the specified date. The following entries are valid: HH 00 to 23 MM 00 to 59 SS 00 to 59 If you enter a value for seconds (SS), the hour and minutes are required. If you enter a value for minutes (MM), the hour is required. You can enter just the hour in this field. If only hours or hours and minutes values are entered, the remaining fields will default to zeros. If no values are entered, this field displays all zeros and defaults to the running current hour, minute, and second at the time of task execution. Task No. The task number of the request. This is a display-only field. PF Keys The CICS transaction support feature recognizes the following function keys: • • • • • PF2 (Copyright/Trade Secret Notice) PF3 (End) PF7 (Scroll Up) PF8 (Scroll Down) Clear (Exit Transaction) Using CICS Transaction Support with Date/Time Offset In addition to standard Xchange CICS requests used to specify a particular date and/or time, you can create pattern job requests based on a fixed offset from the current date and time. To create Xchange date/time offset requests, first enter the OFFSET primary command on the Simulated Date Time Settings screen for CICS transaction support as described in “Primary Commands” on page 5-55. The screen is redisplayed in date/time offset format as shown in Figure 5-45. Create Xchange requests as you would using the standard CICS interface, but use the Constants fields to specify how far in the future or past you want Xchange to simulate. Using Xchange 5-61 Figure 5-45. CICS Simulated Date Time Settings Screen in Offset Format  Xpediter/Xchange ------ Simulated Date Time Settings ------ PREFIX SET TO * COMMAND ===> Scroll ===> PAGE Line Commands: H - Set and Hold P - Permanent R - Reset D - Delete Status Codes: H - Held P - Permanent * - Error - Constants - C/S Owner UserID Async Terminal TransID Program Days Hrs Mins Ind H 1333 * NO 1333 XGCD * 9999 23 59 - _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ =============================================================================== PF1 Help PF2 COPYRIGHT/TRADE SECRET NOTICE PF3 END PF7 BWD PF8 FWD After entering a date/time offset request, you can press PF3 to return to the standard CICS Simulated Date Time Settings screen (Figure 5-46 on page 5-61). Queued offset requests are displayed without a specific date and time. Completed offset request messages are displayed with their simulated date/time calculated at execution from the Constants field values entered on the offset format screen. Note: The offset format screen remains unchanged and displays only requests, not messages. Figure 5-46. CICS Simulated Date Time Settings Screen Showing Date/Time Offset Requests   XPEDITER/Xchange ------ Simulated Date Time Settings ------- Row 1 to 3 of 3 COMMAND ===> Scroll ===> PAGE Line Commands: H - Set and Hold P - Permanent R - Reset D - Delete Status Codes: H - Held P - Permanent C - Completed * - Error T - Threshold C/S Owner UserID Async Terminal TransID Program YYYY/MM/DD HH:MM:SS TASK NO _ H 1333 ACMJET0_ NO_ 1333 XGCD XGCDPAY1 1981 02 18 12 42 57 _ H 1333 ACMJET0_ NO_ 1333 XGCD XGCDPAY2 1981 02 18 12 43 05 _ H 1333 *_______ NO_ 1333 XGCD *_______ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ ============================================================================== PF1 Help PF2 COPYRIGHT/TRADE SECRET NOTICE PF3 END PF7 BWD PF8 FWD Constants Fields Use the Constants fields to specify how far into the future or past you want Xchange to simulate the date and time for a request. For example, if you type 364 in the Days field, 23 in the Hrs field, 59 in the Mins field, and + in the Ind field of a pattern job request, 5-62 Xpediter/Xchange Installation and User Guide Xchange will substitute a date and time nearly one year into the future for the specified job. The Owner field and the S portion of the C/S field are display-only. You can type data into all other fields. Note: Only those fields unique to Xchange’s date/time offset format are described in this section. For descriptions of other fields, see “Fields” on page 5-58. Days The number of days into the future or past that you want Xchange to simulate. Valid entries are from 0 to 9999. The default is 0. Hrs The number of hours into the future or past that you want Xchange to simulate. Valid entries are from 0 to 23. The default is 0. Mins The number of minutes into the future or past that you want Xchange to simulate. Valid entries are from 0 to 59. The default is 0. Ind Used to indicate the direction, future or past, that you want Xchange to simulate. Valid entries are + (plus) for an offset into the future and - (minus) for an offset into the past. The default is +. If the PREVDATE parameter is set to NO (see “Step 1. Specify Xchange Parameters” on page 3-2), date/time offsets into the past are not allowed. Advancing Xchange Requests Using CICS Transaction Support In addition to requests that simulate date and time substitution, you can create requests that will advance the date and time of any CICS transaction support request they match. To create Xchange Advance requests, first enter the ADVANCE primary command on the Simulated Date Time Settings screen for CICS transaction support as described in “Primary Commands” on page 5-55. The Advance Request Settings screen is displayed as shown in Figure 5-47 on page 5-63. Create Advance requests as you would any other CICS transaction support request, but use the request identifier fields—UserID, Async, Terminal, TransID, and Program—as masks to match those CICS transaction support requests you want to advance, and use the Advance offset fields to specify how many days, hours, and minutes you want Xchange to advance those requests forward or backward. Using Xchange 5-63 Figure 5-47. Advance Request Settings Screen for CICS Transaction Support  XPEDITER/Xchange ---------- Advance Request Settings --------- Row 1 to 0 of 0 COMMAND ===> Scroll ===> PAGE Line Commands: H - Set and Hold R - Reset Status Codes: H - Held * - Error D - Delete V - Advance -- Advance -- C/S Owner UserID Async Terminal TransID Program Days Hrs Mins Ind _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ =============================================================================== PF1 Help PF2 COPYRIGHT/TRADE SECRET NOTICE PF3 END PF7 BWD PF8 FWD Fields Use the Advance offset fields to specify the time interval you want Xchange to age requests forward or backward. Days This field is used to enter the number of days by which to age matching requests. The default is 0000. Any numeric value is valid. Hours This field is used to enter the number of hours by which to age matching requests. The default is 00. Valid values range from 00 to 23. Minutes This field is used to enter the number of minutes by which to age matching requests. The default is 00. Valid values range from 00 to 59. Ind This field is used to specify whether to advance the requested date and time, or offset, of existing requests forward or backward. Valid entries are + (plus) to advance forward and - (minus) to advance backward. The default is + (forward). If the PREVDATE parameter is set to NO (see “Step 1. Specify Xchange Parameters” on page 3-2), advancing the requested date and time, or offset, of an existing request prior to the current date is not allowed. Example Advancing CICS Transaction Support Requests In this example, two CICS transaction support requests are in held status, as shown in Figure 5-48. Queued offset requests, like the one for XGDEMCBL, are displayed without a specific date and time. 5-64 Xpediter/Xchange Installation and User Guide Figure 5-48. CICS Transaction Support Requests Held   XPEDITER/Xchange ------ Simulated Date Time Settings --------- Row 1 to 2 of 2 COMMAND ===> Scroll ===> PAGE Line Commands: H - Set and Hold P - Permanent R - Reset D - Delete Status Codes: H - Held P - Permanent C - Completed * - Error T - Threshold C/S Owner UserID Async Terminal TransID Program YYYY/MM/DD HH:MM:SS TASK NO H 1873 PPRJET0 YES * XGAS XGDEMASM 2022 02 02 02 02 02 C 1873 PPRJET0 1873 XGAS XGDEMASM 2022 02 02 02 02 02 195 C 1873 1873 XGAS 2022 02 02 02 02 02 195 C 1873 PPRJET0 1873 XGAS XGDEMASM 2022 02 02 02 02 06 196 C 1873 1873 XGAS 2022 02 02 02 02 06 196 C 1873 1873 XGAS 2022 02 02 02 02 06 196 H 1873 PPRJET0 YES * XGCB XGDEMCBL C 1873 PPRJET0 1873 XGCB XGDEMCBL 2019 10 31 01 02 39 197 C 1873 1873 XGCB 2019 10 31 01 02 39 197 C 1873 PPRJET0 1873 XGCB XGDEMCBL 2019 10 31 01 02 52 198 C 1873 1873 XGCB 2019 10 31 01 02 52 198 _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ =============================================================================== PF1 Help PF2 COPYRIGHT/TRADE SECRET NOTICE PF3 END PF7 BWD PF8 FWD Note: The OFFSET primary command can be used to display the Simulated Date Time Settings screen in offset format (Figure 5-49), allowing you to view the offsets for the request related to program XGDEMCBL. Figure 5-49. CICS Transaction Support Request Held Showing Offsets  XPEDITER/Xchange ------ Simulated Date Time Settings --------- Row 1 to 1 of 1 COMMAND ===> Scroll ===> PAGE Line Commands: H - Set and Hold P - Permanent R - Reset D - Delete Status Codes: H - Held P - Permanent * - Error - Constants - C/S Owner UserID Async Terminal TransID Program Days Hrs Mins Ind H 1873 PPRJET0 YES * XGCB XGDEMCBL 1111 11 11 + _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ =============================================================================== PF1 Help PF2 COPYRIGHT/TRADE SECRET NOTICE PF3 END PF7 BWD PF8 FWD The ADVANCE primary command can be entered on the Simulated Date Time Settings screen shown in Figure 5-48 to display the Advance Request Settings screen shown in Figure 5-50. An Advance request is entered on the Advance Request Settings screen using the Set and Hold (H) line command specifying that Xchange should advance the requested date and time or offset of any CICS transaction support request whose request identifier fields— UserID, Async, Terminal, TransID, and Program—match that set below. The requested dates and times or offsets will be advanced by 30 days, 4 hours, and 30 minutes forward at such time when the Advance is requested. For now, the Advance request is held. Using Xchange 5-65 Figure 5-50. Advance Request Settings Screen  XPEDITER/Xchange ---------- Advance Request Settings --------- Row 1 to 1 of 1 COMMAND ===> Scroll ===> PAGE Line Commands: H - Set and Hold R - Reset Status Codes: H - Held * - Error D - Delete V - Advance -- Advance -- C/S Owner UserID Async Terminal TransID Program Days Hrs Mins Ind H 1873 PPRJET0 YES * XG* XG* 0030 04 30 + _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ =============================================================================== PF1 Help PF2 COPYRIGHT/TRADE SECRET NOTICE PF3 END PF7 BWD PF8 FWD The Advance line command V is entered beside this request. Figure 5-51. Advance Request Settings Screen with V Line Command  XPEDITER/Xchange ---------- Advance Request Settings --------- Row 1 to 1 of 1 COMMAND ===> Scroll ===> PAGE Line Commands: H - Set and Hold R - Reset Status Codes: H - Held * - Error D - Delete V - Advance -- Advance -- C/S Owner UserID Async Terminal TransID Program Days Hrs Mins Ind V H 1873 PPRJET0 YES * XG* XG* 0030 04 30 + _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ =============================================================================== PF1 Help PF2 COPYRIGHT/TRADE SECRET NOTICE PF3 END PF7 BWD PF8 FWD Once completed, the requested date and time or offset of any CICS transaction support request whose request identifier fields match the Advance request masks is advanced by 30 days, 4 hours, and 30 minutes forward as shown in Figure 5-52 and Figure 5-53. 5-66 Xpediter/Xchange Installation and User Guide Figure 5-52. Simulated Date Time Settings Screen with Advance Request   XPEDITER/Xchange ------ Simulated Date Time Settings --------- Row 1 to 2 of 2 COMMAND ===> Scroll ===> PAGE Line Commands: H - Set and Hold P - Permanent R - Reset D - Delete Status Codes: H - Held P - Permanent C - Completed * - Error T - Threshold C/S Owner UserID Async Terminal TransID Program YYYY/MM/DD HH:MM:SS TASK NO H 1873 PPRJET0 YES * XGAS XGDEMASM 2022 03 04 06 32 02 H 1873 PPRJET0 YES * XGCB XGDEMCBL _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ _ ________ ___ ____ ____ ________ ____ __ __ __ __ __ =============================================================================== PF1 Help PF2 COPYRIGHT/TRADE SECRET NOTICE PF3 END PF7 BWD PF8 FWD Figure 5-53. Simulated Date Time Settings Screen with Advance Request Showing Constants  XPEDITER/Xchange ------ Simulated Date Time Settings --------- Row 1 to 1 of 1 COMMAND ===> Scroll ===> PAGE Line Commands: H - Set and Hold P - Permanent R - Reset D - Delete Status Codes: H - Held P - Permanent * - Error - Constants - C/S Owner UserID Async Terminal TransID Program Days Hrs Mins Ind H 1873 PPRJET0 YES * XGCB XGDEMCBL 1141 15 41 + _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ _ ________ ___ ____ ____ ________ ____ __ __ _ =============================================================================== PF1 Help PF2 COPYRIGHT/TRADE SECRET NOTICE PF3 END PF7 BWD PF8 FWD Using CICS Transaction Support with Input from a PDS or PDSE You can use a PDS or PDSE to provide input for Xchange’s CICS transaction support as described in this section. Specifying the Subsystem Define a PDS or PDSE for DD XGSEQINP to hold Xchange CICS transaction support requests as described in the “Step 7. Enable CICS Transaction Support” subsection entitled “PLT Initialization” on page 3-17. Columns 1-4 of the first record must contain the Xchange subsystem ID. Using Xchange 5-67 Specifying Requests Transaction support requests must follow the Xchange subsystem ID record and contain the following information: Table 5-3. Record Format for CICS Transaction Support Request Datasets Columns Field 1 Command 3-10 UserID 12-14 Async 16-19 Terminal 21-24 TransID 26-33 Program 35-42 YYYYMMDD 44-49 HHMMSS See “Fields” on page 5-58 for a description of these fields. All fields except Command are case-sensitive. Add the following DD name to your site’s CICS startup JCL: //XGSEQINP DD DSN=CPWR.XCHANGE.XGSEQINP(DEFXGTN),DISP=SHR The SYSOUT (Class=*) from dynamically allocated DD XGSEQRPT contains the Xpediter/Xchange Sequential Input Report. A sample report is shown in Figure 5-54. Figure 5-54. Sample Sequential Input Report MAR 26 2009 Compuware Corporation 10:32:50 PAGE 1 Xpediter/Xchange Sequential Input Report SUBSYSTEM XG4G C USERID ASY TERM TRAN PROGRAM H * XGAS P * 19800125 121212 XGCCOBLE 20110101 010101 P * P * YYYYMMDD HHMMSS XGCCOBLE 20220202 020202 NO XGPE 20330303 030303 R * XGPE 20370707 070707 D * XGPE Total number of records processed = Duplicate CICS request 7 Using the Xpediter/TSO Interface Xpediter/TSO can be used to immediately test the date and time requests you set up in Xchange. To invoke Xchange during an Xpediter/TSO session, either use the Simulated Date Time Settings screen or enter an Xchange request directly on the Xpediter/TSO command line. Date/time offset requests can also be entered directly on the Xpediter/TSO command line. Note: Direct entry of Xchange requests is only supported for Xpediter/TSO Release 5.3 and above. 5-68 Xpediter/Xchange Installation and User Guide Using the Simulated Date Time Settings Screen To invoke Xchange and access the Simulated Date Time Settings screen from within an Xpediter/TSO session, type XCH or XCHANGE on the command line and press Enter. The Simulated Date Time Settings screen shown in Figure 5-2 on page 5-4 is displayed. Be sure to enter your TSO user ID in the Jobname field when testing from the Standard screen (2.1) with Xpediter/TSO. You must also use the A line command to activate it. Otherwise, the request will not be activated until you log off from TSO and log back on again. For information on using the screen, see “Specifying Requests in ISPF” on page 5-4. When you are finished, press PF3 to return to your Xpediter/TSO session. If using the Xpediter/TSO batch connect facility, set Xchange requests on the jobname of the batch job. Entering Xchange Requests on the Xpediter/TSO COMMAND Line You can also dynamically activate Xchange for the program you are testing under Xpediter/TSO. The following two sections explain how to create standard date/time requests and date/time offset requests. CAUTION: When you finish your Xpediter/TSO testing, remember to access the Simulated Date Time Settings screen and delete your active TSO user ID request. Otherwise, the request remains active until you log off from TSO, and (depending on how generic your request is) exchanges could continue for date/time requests made by other applications on behalf of your TSO user ID. Xchange Date/Time Requests To do this, enter XCHANGE ssss yyyy/mm/dd hh:mm:ss on the Xpediter/TSO command line, specifying parameter values as described below. This command format is only valid on the Xpediter/TSO Source screen during Standard (2.1) testing. Notes: • You can abbreviate the XCHANGE command to the first three letters, XCH. • Do not use the XCHANGE command with the format XCHANGE ssss yyyy/mm/dd hh:mm:ss if using Xpediter/TSO batch connect. The ssss parameter identifies the Xchange subsystem to be updated and initially defaults to CWXG. After the Xchange ISPF interface is used, this parameter defaults to the last subsystem specified to the ISPF interface. The yyyy/mm/dd parameter identifies the Xchange date and defaults to the current date. If only a value for yyyy (year) is entered, mm/dd defaults to the current month and day. Even if a year is the only value entered, you must still follow it with a slash (yyyy/). If a value for mm is entered, yyyy is required, but dd defaults to the current day. The hh:mm:ss parameter identifies the Xchange time and defaults to the current time. As with the yyyy/mm/dd parameter, if you only enter a value for hh, mm and ss default to the current minutes and seconds. Even if an hour is the only value entered, you must still follow it with a colon (hh:). CAUTION: Be sure to delete your active TSO user ID request when you finish testing. Xchange Date/Time Offset Requests You can also dynamically activate Xchange in date/time offset format for the program you are testing under Xpediter/TSO. To do this, enter XCHANGE ssss dddd#hh#mmi on the Using Xchange 5-69 Xpediter/TSO command line, specifying parameter values as described below. This command format is only valid on the Xpediter/TSO Source screen during Standard (2.1) testing. Notes: • You can abbreviate the XCHANGE command to the first three letters, XCH. • Do not use the XCHANGE command with the format XCHANGE ssss dddd#hh#mmi if using Xpediter/TSO batch connect. The ssss parameter identifies the Xchange subsystem to be updated and initially defaults to CWXG. After the Xchange ISPF interface is used, this parameter defaults to the last subsystem specified to the ISPF interface. The dddd#hh#mmi parameter identifies the Xchange date/time offset value. Specify the desired number of days (dddd), hours (hh), and minutes (mm) into the future or past, separating the values with a # character. For the i portion of the parameter, specify + for an offset into the future or - for an offset into the past. The default is +. CAUTION: Be sure to delete your active TSO user ID request when you finish testing. Using Standard STCK and STCKF and Enhanced STCK, STCKE, and STCKF Support You can change the date and time returned by your program’s Assembler store clock (STCK), store clock extended (STCKE), and store clock fast (STCKF) instructions under Xchange CICS region support as well as the ISPF and batch interfaces. There are a number of methods of enabling Xchange STCK. STCKE, and STCKF support: • • • • standard STCK support introduced in Release 3.0, Enhanced STCK Support introduced with Release 3.1, standard STCKF support Enhanced STCKE and STCKF support. Unless you have previously set up your programs to use standard STCK or STCKF support, Compuware recommends using the version described in either “Enhanced STCK Support” on page 5-70, “Enhanced STCKF Support” on page 5-73, or “Enhanced STCKE Support” on page 5-71. Standard STCK and STCKF Support This Xchange function is enabled on a program-by-program basis by replacing STCK and STCKF instructions with a STCK or STCKF instream macro that leverages Xchange’s SVC 11 support. To enable standard STCK or STCKF Support, perform the following steps: 1. Edit your program’s JCL to add a SYSIN DD statement pointing to the STCK or STCKF macro in the Xchange SLXGDATA library. An example of modified JCL for ISPF and batch programs is shown in Figure 5-55. Replace CPWR with the high-level qualifier chosen for your site. 5-70 Xpediter/Xchange Installation and User Guide Figure 5-55. Example JCL Changes for ISPF and Batch //HLASM EXEC PGM=ASMA90, etc. //STEPLIB DD DISP=SHR,DSN=SYS2.HLASSEM.R2.SASMMOD1 //* THIS PLACES XCHANGE'S INSTREAM STCK MACRO //* IN FRONT OF YOUR PROGRAM SOURCE //SYSIN DD DISP=SHR,DSN=CPWR.MLXGnnn.SLXGDATA(STCK) // DD DISP=SHR,DSN=CPWR.MLXGnnn.SLXGDATA(STCKF) // DD DISP=SHR,DSN=PROGRAM.TEST.SOURCE(&MEM) Figure 5-56 shows an example of modified JCL for a CICS program. Replace CPWR with the high-level qualifier chosen for your site. Figure 5-56. Example JCL Changes for CICS //TRN EXEC PGM=DFHEAP1$,PARM='SP' //STEPLIB DD DSN=&INDEX..LOADLIB,DISP=SHR //SYSPRINT DD SYSOUT=* //* THIS PLACES XCHANGE'S INSTREAM STCK MACRO //* IN FRONT OF YOUR PROGRAM SOURCE //SYSIN DD DISP=SHR,DSN=CPWR.MLXGnnn.SLXGDATA(STCK) // DD DISP=SHR,DSN=CPWR.MLXGnnn.SLXGDATA(STCKF) // DD DISP=SHR,DSN=PROGRAM.TEST.SOURCE(&MEM) 2. Reassemble your program. Note: Before running a program that uses the Xchange STCK or STCKF instream macro, make sure the Xchange subsystem has been started at least once since the last IPL. With this support enabled, the STCK and STCKF operation codes in your program will return whatever date and time you specify with Xchange. Enhanced STCK Support The Xchange Enhanced STCK Support is performed via an Xchange user SVC. See “Enabling Xchange SVC” on page 4-3 for information on SVC installation. The user SVC instruction is “zapped” into each module that contains a STCK instruction on which you want to perform date/time simulation. Use the following steps to find and replace STCK instructions in modules. 1. Unless you already know the specific modules that must be zapped, use a search tool to scan the load library containing modules that might have STCK instructions. Use the search string X'B205'. Note: File-AID and ISPF 3.14 can be used to perform this function. 2. Edit and submit the following JCL to produce a DUMPT of the module to be zapped. Replace YOUR.LOAD.LIBRARY with the name of the load library containing the module. Replace XXXXXXXX with the name of the module. Using Xchange 5-71 Figure 5-57. STCK Support DUMPT JCL //* INSERT JOBCARD HERE //ZAP EXEC PGM=AMASPZAP //SYSPRINT DD SYSOUT=* //SYSLIB DD DISP=SHR,DSN=YOUR.LOAD.LIBRARY //SYSIN DD * DUMPT XXXXXXXX ALL 3. Browse the DUMPT output and search for X'B205's. Because the X'B205's are in a readable format, using a FIND 'B205' ALL command will locate the instructions. 4. Determine the CSECT name and OFFSET for each X'B205'. 5. Ensure each X'B205' is part of a valid IBM instruction — not storage constants. 6. Copy the member(s) to another dataset. Note: This zap should not be applied to any production datasets. 7. Edit and submit the JCL shown in Figure 5-58 to zap the module. Replace YOUR.LOAD.LIBRARY with the name of the load library containing the module. Replace mmmmmmmm with the module name to be zapped. Replace cccccccc with the CSECT name from the DUMPT report. Each X'B205' that is to be replaced will need a set of VER and REP cards in which you have replaced oooo with the offset found in the DUMPT report. Replace xx with the hex representation of the Xchange user SVC number. For example, user SVC 201 = 0AC9. Figure 5-58. STCK Support Zap JCL //* INSERT JOBCARD HERE //**************************************************** //*** APPLY ZAP TO COPIED LOAD MODULE *** //**************************************************** //ZAP EXEC PGM=AMASPZAP,PARM=IGNIDRFULL //SYSPRINT DD SYSOUT=* //SYSLIB DD DISP=SHR,DSN=YOUR.LOAD.LIBRARY //SYSIN DD * NAME mmmmmmmm cccccccc VER oooo B205 REP oooo 0Axx Your application program has now been properly zapped and is ready for Xchange testing with Enhanced STCK Support. Enhanced STCKE Support The Xchange Enhanced STCKE Support is performed via an Xchange user SVC. See “Enabling Xchange SVC” on page 4-3 for information on SVC installation. The user SVC instruction can be “zapped” into each module that contains a STCKE instruction on which you want to perform date/time simulation. Use the following steps to find and replace STCKE instructions in modules. 1. Unless you already know the specific modules that must be zapped, use a search tool to scan the load library containing modules that might have STCKE instructions. Use the search string X'B278'. Note: File-AID and ISPF 3.14 can be used to perform this function. 5-72 Xpediter/Xchange Installation and User Guide 2. Edit and submit the JCL in Figure 5-57 on page 5-71 to produce a DUMPT of the module to be zapped. Replace YOUR.LOAD.LIBRARY with the name of the load library containing the module. Replace XXXXXXXX with the name of the module. 3. Browse the DUMPT output and search for X'B278's. Because the X'B278's are in a readable format, using a FIND 'B278' ALL command will locate the instructions. 4. Determine the CSECT name and OFFSET for each X'B278'. 5. Ensure each X'B278' is part of a valid IBM instruction — not storage constants. 6. Copy the member(s) to another dataset. Note: This zap should not be applied to any production datasets. 7. Edit and submit the JCL shown in Figure 5-59 to zap the module. Replace YOUR.LOAD.LIBRARY with the name of the load library containing the module. Replace mmmmmmmm with the module name to be zapped. Replace cccccccc with the CSECT name from the DUMPT report. Each X'B278' that is to be replaced will need a set of VER and REP cards in which you have replaced oooo with the offset found in the DUMPT report. Replace xx with the hex representation of the Xchange user SVC number. For example, user SVC 201 = 0AC9. Figure 5-59. STCKE Support JCL //* INSERT JOBCARD HERE //**************************************************** //*** APPLY ZAP TO COPIED LOAD MODULE *** //**************************************************** //ZAP EXEC PGM=AMASPZAP,PARM=IGNIDRFULL //SYSPRINT DD SYSOUT=* //SYSLIB DD DISP=SHR,DSN=YOUR.LOAD.LIBRARY //SYSIN DD * NAME mmmmmmmm cccccccc VER oooo B278 REP oooo 0Axx 8. Alternatively, for those application programs for which source exists, edit your program’s JCL to add a SYSIN DD statement pointing to the STCKE macro in the Xchange SLXGDATA library. An example of modified JCL for ISPF and batch programs is shown in Figure 5-60. Replace CPWR with the high-level qualifier chosen for your site. Figure 5-60. Example JCL Changes for ISPF and Batch //HLASM EXEC PGM=ASMA90, etc. //STEPLIB DD DISP=SHR,DSN=SYS2.HLASSEM.R2.SASMMOD1 //* THIS PLACES XCHANGE'S INSTREAM STCKE MACRO //* IN FRONT OF YOUR PROGRAM SOURCE //SYSIN DD DISP=SHR,DSN=CPWR.MLXGnnn.SLXGDATA(STCKE) // DD DISP=SHR,DSN=PROGRAM.TEST.SOURCE(&MEM) Figure 5-61 shows an example of modified JCL for a CICS program. Replace CPWR with the high-level qualifier chosen for your site. Using Xchange 5-73 Figure 5-61. Example JCL Changes for CICS //TRN EXEC PGM=DFHEAP1$,PARM='SP' //STEPLIB DD DSN=&INDEX..LOADLIB,DISP=SHR //SYSPRINT DD SYSOUT=* //* THIS PLACES XCHANGE'S INSTREAM STCKE MACRO //* IN FRONT OF YOUR PROGRAM SOURCE //SYSIN DD DISP=SHR,DSN=CPWR.MLXGnnn.SLXGDATA(STCKE) // DD DISP=SHR,DSN=PROGRAM.TEST.SOURCE(&MEM) 9. Reassemble your program. Your application program has now been properly modified and is ready for Xchange testing with Enhanced STCKE Support. Enhanced STCKF Support The Xchange Enhanced STCKF Support is performed via an Xchange user SVC. See “Enabling Xchange SVC” on page 4-3 for information on SVC installation. The user SVC instruction is “zapped” into each module that contains a STCKF instruction on which you want to perform date/time simulation. Use the following steps to find and replace STCKF instructions in modules. 1. Unless you already know the specific modules that must be zapped, use a search tool to scan the load library containing modules that might have STCKF instructions. Use the search string x'B27C'. Note: File-AID and ISPF 3.14 can be used to perform this function. 2. Edit and submit the following JCL to produce a DUMPT of the module to be zapped. Replace YOUR.LOAD.LIBRARY with the name of the load library containing the module. Replace XXXXXXXX with the name of the module. Figure 5-62. STCKF Support DUMPT JCL //* INSERT JOBCARD HERE //ZAP EXEC PGM=AMASPZAP //SYSPRINT DD SYSOUT=* //SYSLIB DD DISP=SHR,DSN=YOUR.LOAD.LIBRARY //SYSIN DD * DUMPT XXXXXXXX ALL 3. Browse the DUMPT output and search for x'B27C's. Because the x'B27C's are in a readable format, using a FIND 'B27C' ALL command will locate the instructions. 4. Determine the CSECT name and OFFSET for each x'B27C'. 5. Ensure each x'B27C' is part of a valid IBM instruction — not storage constants. 6. Copy the member(s) to another dataset. Note: This zap should not be applied to any production datasets. 7. Edit and submit the JCL shown in “STCKF Support Zap JCL” on page 5-74 to zap the module. Replace YOUR.LOAD.LIBRARY with the name of the load library containing the module. Replace mmmmmmmm with the module name to be zapped. Replace cccccccc with the CSECT name from the DUMPT report. Each x'B27C' that is to be replaced will need a set of VER and REP cards in which you have replaced oooo 5-74 Xpediter/Xchange Installation and User Guide with the offset found in the DUMPT report. Replace xx with the hex representation of the Xchange user SVC number. For example, user SVC 201 = 0AC9. Figure 5-63. STCKF Support Zap JCL //* INSERT JOBCARD HERE //**************************************************** //*** APPLY ZAP TO COPIED LOAD MODULE *** //**************************************************** //ZAP EXEC PGM=AMASPZAP,PARM=IGNIDRFULL //SYSPRINT DD SYSOUT=* //SYSLIB DD DISP=SHR,DSN=YOUR.LOAD.LIBRARY //SYSIN DD * NAME mmmmmmmm cccccccc VER oooo B27C REP oooo 0Axx Your application program has now been properly zapped and is ready for Xchange testing with Enhanced STCKF Support. 6-1 Chapter 6. Using the Xchange Journal Chap 6 Each time Xchange substitutes a simulated date or time for a request from your application or program, it creates an entry in the Xchange journal dataset. This dataset provides documentation of all time and date simulations for the jobs, steps, procedure steps, transactions, and programs that were specified for Xchange. Note: Some Xchange journal entries may be in GMT format. Xchange returns date and time in GMT format for DB2, LE, and Xchange’s STCK, STCKE, and STCKF facilities. There are several ways to look at the contents of the journal dataset: • • • • Online Journal Facility Activity Report Journal Extract Journal Dump Report. Before discussing each of these options for viewing the journal, this chapter describes how to close or swap the journal dataset. Closing or Swapping the Journal Dataset To close the Xchange journal dataset, you must do one of the following: • Shut down the Xchange subsystem • Close or swap the journal dataset Shut down the Xchange subsystem using the SHUTDOWN command as described in “Terminating Xchange” on page 4-4. Close or swap the journal from the operator console. If you are an Xchange administrator, you can also close or swap the journal from the batch facility. For information on designating Xchange administrators, see “Designating Administrators” on page 3-30. Every time an Xchange journal dataset is closed, the following message is displayed in the Xchange log: XG0012 ssss LOG xxxxxxxx CLOSED Automated recognition software could be instructed to recognize this message and submit job UNLDLOG located in library CPWR.MLXGnnn.SLXGCNTL to capture the dataset to a pre-defined GDG. To review this data at a later date, submit job RELDLOG located in library CPWR.MLXGnnn.SLXGCNTL to restore a GDG to a test journal file. The contents of this file can be viewed using several methods. For information on each method, see the sections later in this chapter, beginning with “Online Journal Facility” on page 6-2. Closing or Swapping From the Operator Console To close or swap the journal dataset from the operator console, type the CLOSE or SWAPLOG command on the console in the following format R nn,command 6-2 Xpediter/Xchange Installation and User Guide Replace nn with the message sequence number and replace command with CLOSE or SWAPLOG. To open the next journal dataset, replace command with OPEN. The CLOSE command closes and deallocates the current journal dataset but does not open the next journal dataset. No records are written until you enter the OPEN command. You can abbreviate the CLOSE command as C, CL, CLO, or CLOS. The OPEN command allocates and opens the next journal dataset. It is valid only following the successful completion of the CLOSE command. You can abbreviate the OPEN command as O, OP, or OPE. The SWAPLOG command closes and deallocates the current journal dataset and allocates and opens the next journal dataset. You can abbreviate the SWAPLOG command as SW, SWA, SWAP, SWAPL, or SWAPLO. You can also specify commands with the MVS MODIFY (F) command in the following format: F jobname,command where jobname is the name of the Xchange job, and command is CLOSE, OPEN, or SWAPLOG. Closing or Swapping From the Batch Facility If you are an Xchange administrator, you can enter the CLOSE, OPEN, and SWAPLOG commands from the batch facility, and they will be processed as if they were entered by the console operator. Invoke the batch facility with the JCL shown in Figure 6-1. Figure 6-1. Closing or Swapping JCL //STEPNAME EXEC PGM=XGBOPCMD,PARM=’request’ //STEPLIB DD DSN=CPWR.MLXGnnn.SLXGLOAD,DISP=SHR //SYSPRINT DD SYSOUT=* // Replace CPWR with the high-level qualifier chosen for your site. You must also provide information for the request variable, according to the syntax SUBSYS=ssid,OPCMD=command where ssid is a four-character subsystem ID and command is CLOSE, OPEN, or SWAPLOG. Online Journal Facility The Xchange online journal facility displays the satisfied date and time requests. When you request the online Xchange journal, date and time records are extracted from the journal dataset, added to a temporary table, and displayed on your screen. Notes: • If the referenced journal is open for the Xchange subsystem, records recently written by Xchange will not appear until Xchange checkpoints the journal file. For more information, see the JWTIM parameter in “Step 1. Specify Xchange Parameters” on page 3-2. • IMS IOPCB information is included with CICS activity. 1. To display the online journal, type the command TSO XGLOG in the TSO COMMAND field. The Online Log Facility screen is displayed, as shown in Figure 6-2. Using the Xchange Journal 6-3 Figure 6-2. Online Journal Initial Information *********************************************************** *** XPEDITER XCHANGE ONLINE LOG FACILITY *** *********************************************************** *** ENTER XCHANGE JOURNAL DATASET NAME *** *********************************************************** *** DATASET NAME ===> 2. Type the journal dataset name and press Enter. The online log facility inquires whether or not you want to display CICS activity, as shown in Figure 6-3. Figure 6-3. Online Journal CICS Activity Inquiry *********************************************************** *** XPEDITER XCHANGE ONLINE LOG FACILITY *** *********************************************************** *** ENTER XCHANGE JOURNAL DATASET NAME *** *********************************************************** *** DATASET NAME ===> xg.xg20.journal1 *** *** *** ENTER ’Y’ TO DISPLAY CICS ACTIVITY ANYKEY FOR BATCH *** *** --------------------------------------------------- *** *** CICS ACTIVITY? ===> 3. Enter Y to display CICS activity, or press any other key to display non-CICS activity. The online journal will then be displayed, as shown in either Figure 6-4 for non-CICS activity, or Figure 6-5 on page 6-4 for CICS activity. The screen fields are explained below each respective screen. Figure 6-4. Xchange Online Journal of Non-CICS Activity Xpediter/Xchange ------- Simulated Date Time Activity Log ----ROW 1 TO 10 OF 10 COMMAND ===> SCROLL ===> PAGE  USERID JOB STEPNAME PROCSTEP PROGRAM YYYY/MM/DD HH:MM:SS OFFSET  XYZ123A XYZJOB1A STP01 TRACBL2 1999 12 31 23 59 59 00001718 XYZ123A XYZJOB1A STP02 TRACBL2 1999 12 31 23 59 59 00001718 XYZ123A XYZJOB1A STP02 TRACBL2 1999 12 31 23 59 59 00001718 XYZ123A XYZJOB1A STP03 TRACBL2 1999 12 31 23 59 59 00001718 XYZ123A XYZJOB1Z ATSOPROC CUSTOMER 2000 02 29 12 00 00 00000A27 XYZ123A XYZJOB1Z ATSOPROC CUSTOMER 2000 02 29 12 00 00 00000A27 XYZ123A XYZJOB1H STP05 PURORDER 2040 01 01 00 00 01 00002C1B XYZ123A XYZJOB1H STP05 PURORDER 2040 01 01 00 00 01 00002C1B XYZ123A XYZJOB1H STP16 PURORDER 2040 01 01 00 00 01 00002C1B XYZ123A XYZJOB1H STP17 PURORDER 2040 01 01 00 00 01 00002C1B ******************************* BOTTOM OF DATA ******************************** Fields USERID The ID of the user who made the request. JOB The MVS job for which the system date and time has been simulated. STEPNAME The name of a specific step within the job request. 6-4 Xpediter/Xchange Installation and User Guide PROCSTEP The name of a procedure step within the job request. PROGRAM The name of the program as specified on the EXEC PGM= JCL statement. YYYY/MM/DD The simulated date in year, month, and day format. HH:MM:SS The simulated time in hour, minute, and second format. OFFSET The number of bytes, in hex, from the start of the PROGRAM name to the TIME services request. You can use the OFFSET figure with a link-edit map to locate the CSECT that begins immediately before the OFFSET. Subtract the address of the beginning of the CSECT from the OFFSET to determine the relative offset. The relative offset is the number of bytes, in hex, from the beginning of the CSECT to the time request. Figure 6-5. Xchange CICS Transaction Activity Log  Xpediter/Xchange --------- CICS Transaction Activity Log -- Row 1 to 19 of 191 COMMAND ===> SCROLL ===> PAGE CICS JOB ACMEC011 ACMEC011 ACMEC011 ACMEC011 ACMEC011 ACMEC011 ACMEC011 ACMEC015 ACMEC015 ACMEC015 ACMEC015 ACMEC015 ACMEC011 ACMEC011 ACMEC011 ACMEC011 ACMEC022 ACMEC022 DB ORIGIN SYSID TERM A012 A012 A012 A012 A012 A012 A012 A032 A032 A032 A032 A032 A012 A012 A012 A012 DB09 A053 DB09 A053 EXEC TERM A012 A012 A012 A012 A012 A012 A012 A032 A032 A032 A032 A032 A012 A012 A012 A012 A053 A053 USERID ACMJET0 ACMJET0 ACMJET0 ACMJET0 ACMJET0 ACMJET0 ACMJET0 ACMWEC0 ACMWEC0 ACMWEC0 ACMWEC0 ACMWEC0 ACMJET0 ACMJET0 ACMJET0 ACMJET0 ACMPHB0 ACMPHB0 TRAN CODE PAY1 PAY1 PAY1 PAY1 PAY1 PAY1 PAY1 ACT4 ACT4 ACT4 ACT4 ACT4 PAY2 PAY2 PAY2 PAY2 ORDR ORDR TASK  ID PROGRAM 27 PAYROL01 27 PAYROL02 27 PAYSUB01 27 PAYSUB02 27 PAYSUB03 27 PAYSUB04 27 PAYROL03 30 ACCTPYAA 30 ACCTPYAB 30 ACCTPYAC 30 ACCTPYAD 30 ACCTPYAE 33 GETHOURS 33 GETPAYRT 33 PAYCALC1 33 PAYCALC2 37 ORDERIN1 37 ORDERIN2 YYYY/MM/DD 2000 01 01 2000 01 01 2000 01 01 2000 01 01 2000 01 01 2000 01 01 2000 01 01 1999 12 31 1999 12 31 1999 12 31 2000 01 01 2000 01 01 2000 01 01 2000 01 01 2000 01 01 2000 01 01 2022 06 22 2022 06 22 HH:MM:SS 00 00 01 00 00 01 00 00 01 00 00 02 00 00 02 00 00 03 00 00 03 23 59 59 23 59 59 23 59 59 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 13 31 02 13 31 02 Fields CICS JOB The CICS job for which the system date and time has been simulated. DB SYSID The ID of the DB2 subsystem involved in the exchanged transaction. ORIGIN TERM The terminal ID of the user who made the request. EXEC TERM The terminal ID of the user who ran the transaction affected by the request. USERID The ID of the user who initiated the transaction. Using the Xchange Journal 6-5 TRANCODE The transaction ID as specified in the TransID field of the request. TASK ID The CICS task number associated with the request. PROGRAM The name of the program as specified in the Program field of the request. YYYY/MM/DD The simulated date in year, month, and day format. HH:MM:SS The simulated time in hour, minute, and second format. Printing Activity Reports In addition to the online journal, you can also view journal contents by printing the Xpediter/Xchange Simulation Activity Report (Figure 6-6) or CICS Transaction Activity report (Figure 6-7 on page 6-6). The reports consist of printed records for each instance for which the date and time have been exchanged. The records are presented in the sequential order in which the requests took place. Note: The Xchange CICS Transaction Activity Report also includes IMS IOPCB records. Simulation Activity Report The Xpediter/Xchange Simulation Activity Report has the following format: Figure 6-6. Xpediter/Xchange Simulation Activity Report MAR 3 1997 13:17:08  RECORD 1 2 3 4 5 6 7 8 COMPUWARE CORPORATION XPEDITER/XCHANGE SIMULATION ACTIVITY REPORT JOB DFHTST0T DFHTST0D RTMNTPEB XYZ00413 JBR05055 JBR05055 JBR05055 RTMNTPEB STEPNAME STEP1 ABC APL05 STEP4 XYZ01 XYZ02 XYZ02 APL05 PROCSTEP TSTPROC ABRPROC ABRPROC ABRPROC PROGRAM TESTPGM1 PURCHORD ACCTRECV HMNRESRC TESTPGM3 TESTPGM3 TESTPGM3 ACCTINVT MODNAME TESTPGM1 PURCHORD ACCTRECV HMNRESRC TESTPGM3 TESTPGM3 TESTPGM3 ACCTINVT YYYY 2000 1999 2025 1999 2001 2001 2001 2025 DATE MM DD 01 05 12 31 09 01 12 31 02 14 02 14 02 14 09 01 HH 13 23 01 23 00 00 00 01 TIME MN SS 27 36 59 55 00 00 59 55 00 00 00 10 00 32 00 00 OFFSET 00016CDA 00030AF0 0002F912 00027BC4 000318D8 000A36FE 00036A12 00092FCC JOB# JOB06688 JOB06688 JOB00311 JOB00682 JOB04321 JOB04321 JOB04321 JOB00311 Fields RECORD The record number of the request. JOB The MVS job for which the system date and time has been simulated. STEPNAME The name of a specific step within the job request. PROCSTEP The name of a procedure step within the job request. USERID DFHTST0 DFHTST0 CWX0291 CWXABC1 JBR0505 JBR0505 JBR0505 CWX0291 6-6 Xpediter/Xchange Installation and User Guide PROGRAM The name of the program as specified on the EXEC PGM= JCL statement. MODNAME The program that issued the request. If this program is different from the program in the PROGRAM field, it is a program called by the program in the PROGRAM field. DATE The simulated date in year, month, and day format. TIME The simulated time in hour, minute, and second format. OFFSET The number of bytes, in hex, from the start of the MODNAME name to the TIME services request. You can use the OFFSET figure with a link-edit map to locate the CSECT that begins immediately before the OFFSET. Subtract the address of the beginning of the CSECT from the OFFSET to determine the relative offset. The relative offset is the number of bytes, in hex, from the beginning of the CSECT to the time request. JOB# The number of the MVS job. USERID The ID of the user who made the request. CICS Transaction Activity Report The Xpediter/Xchange CICS Transaction Activity report has the following format: Figure 6-7. Xpediter/Xchange CICS Transaction Activity Report JUL 01 1998 15:35:23 RECORD 1856 1857 1858 1859 1860 1861 1862 1863 CICS JOB TERMINAL USERID ACMEC011 A012 ACMJET0 ACMEC011 A012 ACMJET0 ACMEC011 A012 ACMJET0 ACMEC011 A012 ACMJET0 ACMEC011 A012 ACMJET0 ACMEC011 A012 ACMJET0 ACMEC011 A012 ACMJET0 ACMEC015 A032 ACMWEC0 COMPUWARE CORPORATION XPEDITER/XCHANGE CICS TRANSACTION ACTIVITY DATE TIME TRANSACTION TASK PROGRAM YYYY MM DD HH MM SS PAY1 27 PAYROL01 2000 01 01 00 00 01 PAY1 27 PAYROL02 2000 01 01 00 00 01 PAY1 27 PAYSUB01 2000 01 01 00 00 01 PAY1 27 PAYSUB02 2000 01 01 00 00 02 PAY1 27 PAYSUB03 2000 01 01 00 00 02 PAY1 27 PAYSUB04 2000 01 01 00 00 03 PAY1 27 PAYROL03 2000 01 01 00 00 03 ACT4 30 ACCTPYAA 1999 12 31 23 59 59 Fields RECORD The record number of the request. CICS JOB The CICS job for which the system date and time has been simulated. TERMINAL The terminal ID of the user who ran the transaction affected by the request. USERID The ID of the user who ran the transaction affected by the request. Using the Xchange Journal 6-7 TRANSACTION The transaction ID as specified in the TransID field of the request. TASK The CICS task number associated with the request. PROGRAM The name of the program as specified in the Program field of the request. YYYY/MM/DD The simulated date in year, month, and day format. HH:MM:SS The simulated time in hour, minute, and second format. Activity Report JCL You can produce the Xpediter/Xchange Simulation Activity Report, the CICS Transaction Activity report, or both using the JCL shown in Figure 6-8. Figure 6-8. Simulation Activity Report JCL //*------------------------------------------------------------------ //* ==> INSERT JOB CARD HERE //*------------------------------------------------------------------ //* //*PRINT EXEC PGM=XGIPLG01,PARM=’BATCH’ <=== Prints batch records //*PRINT EXEC PGM=XGIPLG01,PARM=’CICS’ <=== Prints CICS records //*PRINT EXEC PGM=XGIPLG01,PARM=’ALL’ <=== Prints both batch and CICS //STEPLIB DD DSN=CPWR.MLXGnnn.SLXGLOAD,DISP=SHR //LOGPRINT DD SYSOUT=* //LOGIN DD DSN=&jrnldsn,DISP=SHR //* This JCL is contained in the member PRTJRNL in CPWR.MLXGnnn.SLXGCNTL. Replace CPWR with the high-level qualifier chosen for your site. Replace &jrnldsn with your site’s journal dataset name. Journal Extract Program XGIPXTRT allows you to obtain an extract of the Xchange journal dataset. The extract is written to a file with 82-byte records in the format shown in Table 6-1 for nonDDF records and the format shown in Table 6-2 on page 6-8 for DDF records. Table 6-1. Journal Extract Record Layout for Non-DDF Records Name Length Format Record 4 Packed Job Name 8 Character Procedure Step 8 Character Step Name 8 Character Program 8 Character Modname 8 Character 6-8 Xpediter/Xchange Installation and User Guide Table 6-1. Journal Extract Record Layout for Non-DDF Records Name Length Format Year 4 Character Month 2 Character Day 2 Character Hour 2 Character Minute 2 Character Second 2 Character Offset 8 Character Job Number 8 Character User ID 8 Character Table 6-2. Journal Extract Record Layout for DDF Records Name Length Format Record 4 Packed Correlation ID 12 Character Unused 4 Character Resource Name 8 Character “=DDF” Literal 4 Character DB2 SSID 4 Character Modname 8 Character Year 4 Character Month 2 Character Day 2 Character Hour 2 Character Minute 2 Character Second 2 Character Offset 8 Character Job Number 8 Character User ID 8 Character You can produce the extract using the JCL shown in Figure 6-9. Using the Xchange Journal 6-9 Figure 6-9. Extract Record Format JCL //*------------------------------------------------------------------ //* ==> INSERT JOB CARD HERE //*------------------------------------------------------------------ //* //DELETE EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE &xtrctdsn NONVSAM //EXTRACT EXEC PGM=XGIPXTRT //STEPLIB DD DSN=CPWR.MLXGnnn.SLXGLOAD,DISP=SHR //LOGIN DD DSN=&jrnldsn,DISP=SHR //LOGXTRT DD DSN=&xtrctdsn,DISP=(NEW,CATLG), // UNIT=SYSDA,SPACE=(TRK,(5,5)), // DCB=(RECFM=FB,LRECL=82,BLKSIZE=4100) //* This JCL is contained in CPWR.MLXGnnn.SLXGCNTL member LOGXTRT. Replace CPWR with the high-level qualifier chosen for your site. Replace &jrnldsn with your site’s journal dataset name. Replace &xtrctdsn with your site’s journal extract dataset name. Note to REXX Users You can use REXX EXEC in member XGPRT in CPWR.MLXGnnn.SLXGCLIB. Replace CPWR with the high-level qualifier chosen for your site. The output from XGPRT is similar to the Xpediter/Xchange Simulation Activity Report from program XGIPLG01, but it allows you to sort and eliminate duplicate records prior to printing. For example, you can sort on the Program field with the Offset field as a secondary sort key. Then use an editor to delete duplicate records. Note: The XGPRT EXEC requires a parameter that specifies the name of the Xchange input extract file. Journal Dump Report To produce a dump of the journal dataset contents, use XGBJRPRT (see Figure 6-10). Figure 6-10. Journal Dump Report JCL //*------------------------------------------------------------------ //* ==> INSERT JOB CARD HERE //*------------------------------------------------------------------ //* //PRINT EXEC PGM=XGBJRPRT //STEPLIB DD DSN=CPWR.MLXGnnn.SLXGLOAD,DISP=SHR //LOGIN DD DSN=&jrnldsn,DISP=SHR //LOGPRINT DD SYSOUT=* //* The XGBJRPRT JCL is contained in DMPJRNL in CPWR.MLXGnnn.SLXGCNTL. Replace CPWR with the high-level qualifier chosen for your site. Replace &jrnldsn with your site’s journal dataset name. 6-10 Xpediter/Xchange Installation and User Guide 7-1 Chapter 7. Using the Xchange Utilities Chap 7 This chapter explains how to use the Xpediter/Xchange utilities. XGFNDMOD Utility XGFNDMOD displays all of the following Xchange-related information: • • • • • parameters, counts, and high-water marks for NUMAMB, NUMATB, and NUMXRE values for CICSMAXR and CICSMAXS current number of CICS completed messages (CICSMAX#) user exclusions security options These values are displayed for all Xchange subsystems. XGFNDMOD also displays the addresses of Xchange programs. This information can be used by Xchange Customer Support for trace and slip dump data. Running XGFNDMOD The JCL to run XGFNDMOD (shown in Figure 7-1) is provided in CPWR.MLXGnnn.SLXGCNTL(XGFNDMOD). It can also be invoked under TSO/E using the XGFNDIT CLIST provided in CPWR.MLXGnnn.SLXGCLIB. Note: Replace CPWR with the high-level qualifier chosen for your site. Figure 7-1. XGFNDMOD JCL //* --> PLACE JOB CARD HERE //* //********************************************************************* //* INSTALLER: //* //* TO USE THIS JCL, YOU NEED TO //** //*-- Replace CPWR with the high-level qualifier chosen for your site. //** //*-SUPPLY VALUES FOR THESE VARIABLES:* //** //* CHANGE THE SUBSYS= KEYWORD TO THE SSID YOU HAVE CHOSEN FOR XCHANGE* //* CHANGE THE MOD= KEYWORD TO THE NAME OF THE MODULE YOU WISH TO * //* FIND. MOD=ALL WILL FIND ALL XCHANGE MODULES * //* * //* - INSERT A VALID JOB CARD AND SUBMIT THE JOB. * //********************************************************************* //* //XGFNDMOD EXEC PGM=XGFNDMOD,PARM=’SUBSYS=CWXG,MOD=ALL’ //STEPLIB DD DSN=CPWR.MLXGnnn.SLXGLOAD,DISP=SHR //PRTFILE DD SYSOUT=* // * * * * 7-2 Xpediter/Xchange Installation and User Guide XGFNDMOD Report XGFNDMOD lists the current number of completed messages as GCACMAX#, the CICSMAXS value as GCACMAXS, the CICSMAXR value as GCACMAXR, and the greatest number of completed messages that have existed since Xchange initialization as GCACMAXH. A typical report is shown in Figure 7-2. Figure 7-2. Sample XGFNDMOD Report    XGFNDMOD - LAST MODIFIED ON 02/06/08 14.37 GCA GCA GCA GCA 0A5E8000 0A5E7000 0A32B000 09150000 80E7C7F3 80E7C731 80E7C7F3 80E7C731 MXG1 MXG2 XG35 XG31 MODULE S-ADDR E-ADDR LENGTH XGMINIT 0C023F30 0C026000 000020D0 XGMTERM 00000000 00000000 00000000 XGJINIT 0C03D3A0 0C03DDC8 00000A28 XGJTERM 00000000 00000000 00000000 XGOINIT 0C039208 0C039440 00000238 . . .  . . . XGMCFPGM 000162A8 000166E0 00000438 XGSSSYS 035EBC28 035ED000 000013D8 XGXPCRT# 0A6BC500 0A6BCD00 00000800 XGXSTUB8 0A253130 0A253388 00000258 XGXSVC08 00AEBF68 00AECDE0 00000E78  POOL DEFINED CURR-USE MAX-USED AMB 128 10 12 ATB 256 15 20 URE 32 0 2 XRE 64 10 12 ORE 16 0 2 JRE 128 0 2  GCACMAX# 190 GCACMAXR 5000 GCACMAXS 10000 GCACMAXH 380  NO USER EXCLUSIONS ARE FOUND  USER JOB EXCLUSION ENTRIES ENTQA*  NO IMS USERID EXCLUSIONS WERE FOUND  SECURITY OPTIONS - GCASTAT7 = 50 SECUSE=YES SECDFLT=DENY PREVDATE=YES  DDF OPTION DDF=NO XGSUBRST Utility This utility changes the first byte of the Xchange SSID specified to x'FF'. This will, in essence, rename that SSID so that it may be reused when bringing up a new release of Xchange without the need for an IPL. For example, if CWXG were specified as the SSID, this utility would change that SSID to x'FFE6E7C7'. Using the Xchange Utilities Running XGSUBRST The JCL to run XGSUBRST (shown in Figure 7-3) is provided in CPWR.MLXGnnn.SLXGCNTL(XGSUBRST). Note: Replace CPWR with the high-level qualifier chosen for your site. Figure 7-3. XGSUBRST JCL /* //********************************************************************* //* INSTALLER: //* //* TO USE THIS JCL, YOU NEED TO //** //*-- REPLACE CPWR WITH THE HIGH-LEVEL QUALIFIER CHOSEN FOR YOUR SITE //* //** //*-SUPPLY VALUES FOR THESE VARIABLES:* //** //* CHANGE THE XXXX TO THE XCHANGE SSID YOU WOULD LIKE TO RENAME * //* * //* - INSERT A VALID JOB CARD AND SUBMIT THE JOB. * //* //XGSUBRST EXEC PGM=XGSUBRST,PARM=XXXX //STEPLIB DD DSN=CPWR.MLXGnnn.SLXGAUTH,DISP=SHR // 7-3 7-4 Xpediter/Xchange Installation and User Guide A-1 Appendix A. Xchange Messages Appendix A. App A This appendix describes the messages that are generated by Xpediter/Xchange. Messages are separated into the following sections: • • • • • • “Owner Field Messages” “IMS Message Level Support Messages” “XGIM Messages” “MVS Console Messages” “Abend Codes” “Xchange Parsing Exit Messages”. Owner Field Messages Xchange displays four-character message codes in the Owner field of the Simulated Date Time Settings screen. For any of these message codes, type a different job, transaction, or program name — or doublecheck the spelling of the job, transaction, or program name and re-enter it. ACTJ Explanation: The specified pattern has active jobs. AMBG Explanation: exists. The specified job name is ambiguous. An equivalent Xchange request already CAUT Explanation: The job was not exchanged because the execution class in which it was run is not included in the Xchange CLASS parameter. INVL Explanation: The specified job is invalid. JACT Explanation: The specified job is currently active. JNFD Explanation: The specified job cannot be found to be deleted. NAUT Explanation: You are not authorized to perform this function. External security has denied update access to the pseudo-dataset name associated with the request. This message is not displayed until the job executes. NFND Explanation: Xchange cannot find the job to be displayed. PNFD Explanation: Xchange cannot find the pattern that you specified to be deleted. A-2 Xpediter/Xchange Installation and User Guide UADD Explanation: Xchange is unable to add the specified pattern. UNAB Explanation: Xchange is unable to process this request. The JOB name specified in this request duplicates or could duplicate a job name already active in this subsystem. IMS Message Level Support Messages The following messages related to Xchange’s IMS Message Level Support are directed to the MVS console. XGI0100E REQUEST FILE SUBSYSTEM IS NOT COMPATIBLE Explanation: Xchange subsystem name in the request file is incompatible with the Xchange IMS Message Level Support release. System Action: Processing terminates. Operator Response: Check the load library containing Xchange for the proper release. Resubmit the job. XGI0101I XCHANGE IMS INTERFACE IS STARTED Explanation: System Action: Xchange IMS Message Level Support has received control. Processing continues. Operator Response: None. XGI0102I XCHANGE IMS INTERFACE ADDRESS xxxxxxxx/xxxxxxxx Explanation: Severity: Xchange IMS Message Level Support is located in storage at this address range. Processing continues. Operator Response: None. XGI0103I LE/370 LIBR ROUTINE RETENTION ACTIVE Explanation: System Action: Xchange has detected the presence of OBM’s LPR in this IMS dependent region. Xchange will not be able to provide support for LE time calls. User Response: If Xchange of LE time calls is necessary, LRR must be deactivated from this dependent region. XGIM Messages Xchange XGIM messages are displayed below the Command field for requests made through the ISPF, CICS, or batch interface. XGIM010A Invalid Command Explanation: You have entered an invalid line command in the Command field. Valid line commands are A (Set Active), D (Delete), H (Set and Hold), R (Reset), and S (Set). XGIM010B Jobname Required Explanation: You have specified an invalid job name in the JOBNAME field. The job name is required and must contain more than a single asterisk (*). XGIM010C Procstep Required Explanation: You have specified an invalid procedure name in the PROCSTEP field. The procedure step name is required. Xchange Messages XGIM010D A-3 Stepname Required Explanation: You have specified an invalid step name in the STEPNAME field. The step name is required. XGIM010E Program Required Explanation: You have specified an invalid program name in the PROGRAM field. The program name is required. XGIM010F YYYY/MM Missing Explanation: You have not specified the year and month in the YYYY/MM/DD field. If you enter a value for the day (DD), you must enter the month and year. XGIM010G YYYY Missing Explanation: You have not specified the year in the YYYY/MM/DD field. If you enter a value for the month (MM), you must enter the year. XGIM010H YYYY Must Be 1900 To 2041 Explanation: 2041. XGIM010I MM Must Be 01 To 12 Explanation: XGIM010J You have specified a second in the SS field that is not in the range 00 to 59. Invalid Delete Explanation: XGIM010R You have specified a minute in the MM field that is not in the range 00 to 59. SS Must Be 00 To 59 Explanation: XGIM010Q You have specified an hour in the HH field that is not in the range 00 to 23. MM Must Be 00 To 59 Explanation: XGIM010P You have specified a day in the DD field that is not in the range 01 to 28. HH Must Be 00 To 23 Explanation: XGIM010O You have specified a day in the DD field that is not in the range 01 to 29. DD Must Be 01 To 28 Explanation: XGIM010N You have specified a day in the DD field that is not in the range 01 to 30. DD Must Be 01 to 29 Explanation: XGIM010M You have specified a day in the DD field that is not in the range 01 to 31. DD Must Be 01 To 30 Explanation: XGIM010L You have specified a month in the MM field that is not in the range 01 to 12. DD Must Be 01 To 31 Explanation: XGIM010K You have specified a year in the YYYY field that is not in the range 1900 to You have attempted to delete an active or new request. Invalid Command Explanation: You have entered an invalid line command. Valid line commands are A, H, or S. XGIM010S HH:MM Missing Explanation: You specified a value for seconds (SS) in the HH:MM:SS field, but you did not specify the minutes and hours. XGIM010T HH Missing Explanation: You specified a value for minutes (MM) in the HH:MM:SS field, but you did not specify the hours. A-4 Xpediter/Xchange Installation and User Guide XGIM010U Date In Past Explanation: today’s date. XGIM010V Constant Missing Explanation: XGIM010W Constant(s) must contain valid numeric characters. Indicator Invalid Explanation: XGIM020A Days, Hours, or Minutes is required. Constant Must Be Numeric Explanation: XGIM010X Your system is configured to prohibit dates being exchanged to a date prior to Enter a valid indicator, + or -, or leave blank. Subsys Not Available Explanation: You have entered a subsystem name that is not available for Xchange. Check the release and/or spelling of the subsystem name. XGIM020B Process Complete Explanation: XGIM020C Display Panel Error Explanation: be found. XGIM020D The specified panel, message, screen field, or message location field could not Translation Error Explanation: XGIM020E Request processing completed normally. A translation or truncation error has occurred in storing defined variables. Severe Error Explanation: ISPF has encountered a severe error. Contact the Xchange Customer Support staff. See “Customer Support” on page xi. XGIM020F Invalid ISPF RC Explanation: An invalid ISPF return code has been encountered. Contact the Xchange Customer Support staff. See “Customer Support” on page xi. XGIM020G Msg Table Error Explanation: The return code from the Xchange subsystem is greater than 20. Contact the Xchange Customer Support staff. See “Customer Support” on page xi. XGIM020H Program Error Explanation: An invalid program return code has been returned. Contact the Xchange Customer Support staff. See “Customer Support” on page xi. XGIM020I Command Error Explanation: XGIM020J Invalid Prefix Parm Explanation: XGIM020K Multiple parameters were entered for the PREFIX value. Invalid Command Explanation: XGIM020M The PREFIX parameter exceeds eight bytes. Multiple Prefix Parms Explanation: XGIM020L The specified command could not be found in the active command tables. The parameter is invalid for the specified command. Prefix Reset Explanation: The Xchange display prefix has been reset to your TSO user ID. Xchange Messages XGIM020N Prefix Altered Explanation: XGIM020O The default Xchange subsystem is unavailable. Activate the Xchange subsystem. Subsys Not Compatible Explanation: XGIM020Y You have entered an invalid Xchange command. Default Subsys Unavailable Explanation: XGIM020Q The Xchange display prefix has been successfully altered. Invalid Command Explanation: XGIM020P A-5 Subsystem entered is not compatible with this release of Xchange. Invalid Advance command Explanation: You have entered an invalid line command in the Command field on the Advance Request Settings screen. Valid line commands are D (Delete), H (Set and Hold), R (Reset), and V (Advance). XGIM030A Invalid Subsys ID Explanation: XGIM030B Invalid Subsys ID Explanation: XGIM030D The subsystem ID must be alphanumeric. The subsystem ID must be four characters long. RESET Invalid Explanation: RESET must be used on the respective request's entry panel. For example, if the request is a DDF request, then the DDF panel would allow the RESET. XGIM030J FORCE Invalid Explanation: XGIM030K FORCE Invalid Explanation: XGIM030L FORCE may not be used on a DDF or Set Active (A) request. Userid Not Authorized Explanation: XGIM030M FORCE must be used on an ACTIVE line. The user is not authorized for the FORCE command. Invalid Advance command Explanation: You have entered an invalid line command in the Command field on a blank line on the Advance Request Settings screen. H (Set and Hold) is the only valid line command that can be specified on a blank line. XGIM040A No Parameter Field Explanation: You have not specified the appropriate input parameters in the inserted Xchange batch steps. XGIM040B Incomplete Keyword Parameter Explanation: You did not enter the appropriate data following the specified Xchange batch step keyword. XGIM040C Missing Keyword Explanation: XGIM040D Unrecognized Keyword Explanation: XGIM040E Xchange expected a keyword in a batch step and did not find one. Xchange does not recognize the keyword specified in the batch step. Unable to Open Log Explanation: Xchange is unable to open the journal dataset. A-6 Xpediter/Xchange Installation and User Guide XGIM040F Get Storage Error Explanation: XGIM040G VSAM Read Error Explanation: XGIM040H GETMAIN is unable to allocate storage. VSAM has encountered an I/O read error for the journal dataset. Invalid Parameters Explanation: You have entered invalid date parameters, time parameters, or both. Specify the parameters correctly. XGIM040I Ambiguous Request Explanation: You have entered an Add active request with parameters that could apply to several active jobs or transactions. Re-specify the request to include only one active job or transaction. XGIM040J Unable To Add Request Explanation: You have entered a request that cannot be accepted because the Xchange subsystem is terminating or the request queue (XRE) is full. Reenter the request at a later time. XGIM040K UserID Not Authorized Explanation: The userID of the person running the XGBOPCMD job does not have Xchange administrator authority. XGIM040L Invalid OFFSET Parameters Explanation: You have entered an invalid value for one or more of the OFFSET parameters. Specify the parameter values correctly. XGIM040M DDNAME DD OPEN ERROR Explanation: An error occurred during the opening of the DDNAME DD dataset. Verify that the dataset DCB parameters are correct. XGIM040N XGPARMDS DD INPUT DATA > 100 BYTES Explanation: The input data that was read from the XGPARMDS DD dataset was longer than 100 bytes. XGIM040O DDNAME DD DATASET IS EMPTY Explanation: XGIM040P The DDNAME DD dataset did not have any data in it. XGPARMDS DD PARAMETER ENDED WITH A COMMA, NO CONTINUATION FOUND Explanation: The last parameter in the XGPARMDS DD dataset ended with a comma. This indicates that there are more parameters, but none were found. XGIM040Q RECORD NNNNN HAS INVALID REQUEST TYPE - SPECIFY B OR C Explanation: Record NNNNN of the XGINPREQ DD dataset specified an invalid request type. Only B for Batch or C for CICS is valid. XGIM040R RECORD NNNNN HAS INVALID OFFSET INDICATOR - SPECIFY Y OR N Explanation: Record NNNNN of the XGINPREQ DD dataset specified an invalid offset indicator. Only Y for Offset Request or N for Date/Time Request is valid. XGIM040S DDNAME DD DATASET WAS NOT FOUND Explanation: An essential dataset needed to run the Extended Batch Facility was not specified in the JCL. XGIM040T XGIMSREQ DD LRECL GREATER THAN 32758 Explanation: An error occurred during verification of the logical record length of the XGIMSREQ DD dataset. Verify that this dataset is the one that was allocated and initialized for IMS Message Level Support during Xchange installation. Xchange Messages XGIM040U A-7 XGIMSREQ DD LRECL LESS THAN 4086 Explanation: An error occurred during verification of the logical record length of the XGIMSREQ DD dataset. Verify that this dataset is the one that was allocated and initialized for IMS Message Level Support during Xchange installation. XGIM040V XGIMSREQ DD READ ERROR Explanation: An error occurred while reading a record from the XGIMSREQ DD dataset. Verify that this dataset is the one that was allocated and initialized for IMS Message Level Support during Xchange installation. XGIM040W XGIMSREQ DD INITIALIZATION ERROR Explanation: An error occurred during verification of data in the XGIMSREQ DD dataset. Verify that this dataset is the one that was allocated and initialized for IMS Message Level Support during Xchange installation. XGIM040X RECORD NNNNN HAS REQUEST TYPE I BUT XGIMSREQ DD WAS NOT FOUND Explanation: An IMS request was specified in the XGINPREQ DD dataset, but the XGIMSREQ DD dataset was not allocated. Specify the XGIMSREQ DD dataset in the JCL and rerun the job. MVS Console Messages Most messages directed to the MVS console include the four-character subsystem ID (shown here as ssss) identifying the subsystem from which the message was generated. XCHANGE DI00 A DDF REQUEST WAS FULFILLED FOR xxxxxxxxxxxx / yyyyyyyy Explanation: Informational. An Xchange DDF request was exchanged with the correlation ID specified by xxxxxxxxxxxx and the resource name specified by yyyyyyyy. This message is displayed in the JES log of the DB2 DIST address space and the system log. System Action: None. Operator Response: None. XCHANGE DN00 A DDF REQUEST WAS DISALLOWED FOR xxxxxxxxxxxx / yyyyyyyy Explanation: Informational. An Xchange DDF request was not exchanged with the correlation ID specified by xxxxxxxxxxxx and the resource name specified by yyyyyyyy. This message is displayed in the JES log of the DB2 DIST address space and the system log. System Action: None. Operator Response: None. XCHANGE I000 XCHANGE THIS STEP HAS HAD ITS EXECUTION DATES AND/OR TIMES INSPECTED BY Explanation: Informational. An Xchange request was eligible for the job’s date/time to be altered and the request was fulfilled. System Action: None. Operator Response: None. XCHANGE N000 SECURITY THIS STEPS EXECUTION DATES AND/OR TIME WERE BYPASSED DUE TO Explanation: Informational. An Xchange request was eligible for the job’s date/time to be altered, but security prevented the request from being fulfilled. System Action: None. Operator Response: Check the pseudo-dataset rules with your security administrator. The Xchange request owner ID must have update access to the pseudodataset rule. A-8 Xpediter/Xchange Installation and User Guide XG0007 ssss UNABLE TO ATTACH LOG TASK. R15=nn Explanation: The attempt to attach the journal processing task failed during Xchange startup. System Action: Xchange abends with a U0101 abend. Operator Response: Make sure the STEPLIB or JOBLIB DD statements point to the correct libraries. If they do, contact the Xchange Customer Support staff. XG0008 ssss LOG TASK INITIALIZATION ERROR nn Explanation: The attempt to initialize the journal processing task failed during Xchange startup. In the text of the message, nn can have the following values: 04 R15 return code from OPEN VSAM ACB 08 Insufficient storage available for control block for ESTAI request 1304 Unable to load the LOG initialization program 2001 Unable to extract VSAM control block length 2003 Unable to allocate storage for a VSAM ACB 2004 Unable to generate a VSAM ACB 2005 Unable to allocate storage for a VSAM RPL 2006 Unable to generate a VSAM RPL 2007 Unable to allocate storage for an OPEN/CLOSE work area 2012 Unable to establish ESTAE environment System Action: Xchange abends with a U0101 abend. Operator Response: Make sure the value specified for the REGION parameter of the Xchange EXEC statement is 3M or higher and that the STEPLIB or JOBLIB DD statements specify the correct libraries. If Xchange still abends, contact the Xchange Customer Support staff. XG0009 ssss LOG xxxxxxxx BEING OPENED Explanation: System Action: The DD statement specified by xxxxxxxx is in the process of being opened. Processing continues. Operator Response: None. XG0010 ssss LOG xxxxxxxx OPENED Explanation: System Action: The DD statement specified by xxxxxxxx is open. Processing continues. Operator Response: None. XG0011 ssss LOG xxxxxxxx BEING CLOSED Explanation: System Action: The DD statement specified by xxxxxxxx is in the process of being closed. Processing continues. Operator Response: None. XG0012 ssss LOG xxxxxxxx CLOSED Explanation: System Action: The DD statement specified by xxxxxxxx is closed. Processing continues. Operator Response: None. Xchange Messages XG0013 ssss A-9 LOG xxxxxxxx BEING ALLOCATED Explanation: System Action: The DD statement specified by xxxxxxxx is in the process of being allocated. Processing continues. Operator Response: None. XG0014 ssss LOG xxxxxxxx ALLOCATED ON VOLSER yyyyyy Explanation: The DD statement specified by xxxxxxxx is allocated on the DASD volume represented by yyyyyy in the message. System Action: Processing continues. Operator Response: None. XG0015 ssss LOG xxxxxxxx BEING DEALLOCATED Explanation: System Action: The DD statement specified by xxxxxxxx is in the process of being deallocated. Processing continues. Operator Response: None. XG0016 ssss LOG xxxxxxxx DEALLOCATED Explanation: System Action: The DD statement specified by xxxxxxxx is deallocated. Processing continues. Operator Response: None. XG0017 ssss LOG xxxxxxxx ALLOCATION ERROR Explanation: Xchange encountered a dynamic allocation error while attempting to allocate the journal dataset specified by xxxxxxxx. System Action: Message XG0024 displays, and Xchange uses the next journal dataset. Operator Response: None. XG0018 ssss LOG xxxxxxxx VSAM ACB CANNOT BE MODIFIED Explanation: The DD statement specified by xxxxxxxx could not be modified for input for the journal dataset autocopy. System Action: The autocopy is bypassed and processing continues. Operator Response: None. XG0019 ssss LOG xxxxxxxx VSAM OPEN ACB ERROR Explanation: Xchange encountered an OPEN ACB error while opening the journal dataset specified by xxxxxxxx. System Action: Message XG0025 displays, and Xchange uses the next journal dataset. Operator Response: None. XG0020 ssss LOG xxxxxxxx LOG DEALLOCATION ERROR Explanation: Xchange encountered a dynamic allocation error while attempting to deallocate the journal dataset specified by xxxxxxxx. System Action: Message XG0024 displays, and Xchange uses the next journal dataset. Operator Response: None. XG0021 ssss LOG xxxxxxxx HAS BEEN FILLED Explanation: The DD statement specified by xxxxxxxx has been completely filled with journal data. System Action: and used. The journal dataset is closed and deallocated. The next journal is allocated Operator Response: None. A-10 Xpediter/Xchange Installation and User Guide XG0022 ssss NO LOGS ARE AVAILABLE FOR USE Explanation: System Action: Xchange has marked all journal datasets as being unusable. Processing continues without any further logging. Operator Response: Make sure that the journal dataset names that Xchange is attempting to use are not in use by another job on the system. Also, ensure that these names have been successfully defined by an IDCAMS DEFINE CLUSTER job. If this is not the cause of the problem, contact the Xchange Customer Support staff. XG0023 ssss LOG xxxxxxxx VSAM CLOSE ACB ERROR Explanation: Xchange encountered a dynamic allocation error while attempting to close the journal dataset identified by xxxxxxxx. System Action: Processing continues with the next journal dataset. Operator Response: None. XG0024 ssss RBERROR=nn. RBINFO=nn Explanation: The text of the message indicates the exact error and information codes that resulted from an unsuccessful dynamic allocation or deallocation. System Action: None. Operator Response: None. XG0025 ssss R15=nn. ACBERROR=nn Explanation: The text of the message indicates the exact value returned in register 15 and the value in the ACB error field that resulted from an unsuccessful OPEN or CLOSE ACB function. System Action: Processing continues. Operator Response: None. XG0026 ssss LOG xxxxxxxx VSAM WRITE ERROR Explanation: Xchange encountered a non-zero return code from a VSAM write operation. System Action: The current journal dataset is closed and deallocated. The next dataset is allocated and opened. Operator Response: None. XG0027 ssss LOG xxxxxxxx PUT ERROR=yyyyyyyy Explanation: The DD statement specified by xxxxxxxx had a write error identified by yyyyyyyy that prevented output of a record. System Action: The write is bypassed and processing continues. Operator Response: None. XG0028 ssss LOG xxxxxxxx CANNOT BE COPIED FOR BACKUP Explanation: The DD statement specified by xxxxxxxx had an I/O error that prevented it from being read. System Action: The autocopy is bypassed and processing continues. Operator Response: None. XG0029 ssss LOG xxxxxxxx ALLOCATION ERROR=yyyyyyyy Explanation: The DD statement specified by xxxxxxxx for autolog had an allocation error identified by yyyyyyyy. System Action: The autocopy is bypassed and processing continues. Operator Response: None. Xchange Messages XG0030 ssss A-11 LOG xxxxxxxx SUCCESSFULLY COPIED TO BACKUP Explanation: The DD statement specified by xxxxxxxx was copied to the backup journal dataset successfully. System Action: Processing continues. Operator Response: None. XG0031 ssss LOG xxxxxxxx yyy ERROR=zzzzzzzz Explanation: The DD statement specified by xxxxxxxx had an I/O error identified by zzzzzzzz. The I/O operation type (GET or PUT) is identified by yyy. System Action: The remainder of the autocopy is bypassed and processing continues. Operator Response: None. XG0032 ssss AUTOLOG BACKUP FILE OPEN ERROR Explanation: System Action: The Autolog backup file could not be opened successfully. The autocopy is bypassed and processing continues. Operator Response: None. XG0033 ssss BACKUP COUNTS: xxxxxxxx=IN yyyyyyyy=OUT Explanation: The autolog copy successfully read a record count identified by xxxxxxxx and wrote a record count identified by yyyyyyyy. System Action: Processing continues. Operator Response: None. XG0034 ssss TRACE OPERAND ACCEPTED. TRACING CHANGED Explanation: System Action: The TRACE operator command changed the tracing parameters. Processing continues. Operator Response: None. XG0035 ssss TRACE OPERAND MUST BE ON, OFF, OR HEX DIGITS Explanation: The TRACE operator command contained an operand that did not contain valid hex digits or the keywords ON or OFF. Valid hex digits are 0-9 or A-F. Up to 16 hex digits can be entered. System Action: Processing continues. Operator Response: Reenter the TRACE command with a valid operand. XG0036 ssss AMBIGUOUS COMMAND, RETRY Explanation: The operator entered a command abbreviation that is ambiguous with multiple valid commands. System Action: Processing continues. Operator Response: Reenter the operator command with enough characters to specify a unique command. XG0037 ssss INVALID COMMAND. RETRY Explanation: System Action: An operator has entered an invalid reply to the Xchange WTOR. Processing continues. Operator Response: Reply again to the WTOR. XG0038 ssss xxxxxxxx COMMAND ACCEPTED Explanation: Xchange has accepted the command entered by the operator and is in the process of completing. System Action: Processing continues. A-12 Xpediter/Xchange Installation and User Guide Operator Response: None. XG0042 ssss LOG IS NOT OPEN Explanation: In response to an operator entered CLOSE command, Xchange indicates that the current journal dataset is not open. System Action: Processing continues. Operator Response: Reply again to the WTOR. XG0043 ssss LOG IS ALREADY OPEN Explanation: In response to an operator entered OPEN command, Xchange indicates that the current journal dataset is already open. System Action: Processing continues. Operator Response: Reply again to the WTOR. XG0044 ssss SVC 8 FRONT-END ABENDED, PLEASE CONTACT COMPUWARE Explanation: System Action: LE or STCK macro prerequisite failed. Xchange processing suspended. Operator Response: Restart Xchange subsystem. If problem recurs, contact the Xchange Customer Support staff. XG0045 ssss SVC 8 FRONT-END ESTAE FAILED, PLEASE CONTACT COMPUWARE Explanation: System Action: LE or STCK macro prerequisite failed. Xchange processing suspended. Operator Response: Restart Xchange subsystem. If problem recurs, contact the Xchange Customer Support staff. XG0046 ssss SVC 8 FRONT-END GETMAIN FAILED, PLEASE CONTACT COMPUWARE Explanation: System Action: LE or STCK macro prerequisite failed. Xchange processing suspended. Operator Response: Restart Xchange subsystem. If problem recurs, contact the Xchange Customer Support staff. XG0050 ssss DIAGNOSTIC TRACE ACTIVE Explanation: An MVS MODIFY command (F) was entered to Xchange specifying DTRACE ON (F XGJOBNAM,DTRACE ON). System Action: Xchange will begin passing trace records to GTF for subsequent recording into the trace dataset. Operator Response: None. XG0051 ssss DIAGNOSTIC TRACE INACTIVE Explanation: An MVS MODIFY command (F) was entered to Xchange specifying DTRACE OFF (F XGJOBNAM,DTRACE OFF). System Action: Xchange will stop passing trace records to GTF for subsequent recording into the trace dataset. Operator Response: None. XG0052 ssss DTRACE OPERAND MUST BE ON OR OFF Explanation: An MVS MODIFY command (F) was entered to Xchange specifying DTRACE, but the operand following DTRACE was invalid. ON and OFF are the only valid values for this operand. System Action: None. Operator Response: Re-enter the MODIFY command with the correct operand for DTRACE. Xchange Messages XG0100 A-13 NO MORE ATB(S) AVAILABLE Explanation: System Action: The Xchange ATB pool is at capacity, and no more entries can be added. The job’s date/time requests will not be exchanged. Operator Response: Either delete some requests or recycle the Xchange subsystem. The Xchange CMSC PARMLIB parameter NUMATB may also require adjustment. XG0101 NO MORE XRE(S) AVAILABLE Explanation: System Action: The Xchange XRE pool is at capacity, and no more entries can be added. The job will not be added to the Xchange request queue. Operator Response: Either delete some requests or recycle the Xchange subsystem. The Xchange CMSC PARMLIB parameter NUMXRE may also require adjustment. XG0102 NO MORE AMB(S) AVAILABLE Explanation: System Action: The Xchange AMB pool is at capacity, and no more entries can be added. The job’s date/time requests will not be exchanged. Operator Response: Either delete some requests or recycle the Xchange subsystem. The Xchange CMSC PARMLIB parameter NUMAMB may also require adjustment. XG0103 ERROR DURING SVC TABLE UPDATE Explanation: XGSTKINS encountered a non-zero return code while attempting to install/refresh XGSTKSVC via SVCUPDTE. System Action: Processing continues without STCK/STCKSYNC support. Operator Response: Contact the Xchange Customer Support staff. XG0104 PARM LENGTH MUST BE 11, 26, 38, 53, OR 65 CHARACTERS Explanation: XGSTKINS detected an error in the length of the parameter passed on the EXEC statement. The parameter must be 11 characters long in the format PARM='SUFFIX=ssss', 26 characters long in the format PARM='SVCNUM=xxx,RUNTYPE=zzzzzzz' or PARM='SVCENM= xxx,RUNETYP=zzzzzzz', 38 characters long in the format PARM='SVCNUM=xxx,RUNTYPE=zzzzzzz,SUFFIX=ssss' or PARM='SVCENM=xxx,RUNETYP=zzzzzzz,SUFFIX=ssss', 53 characters long in the format PARM='SVCNUM=xxx,RUNTYPE=zzzzzzz,SVCENM=xxx,RUNETYP=zzzzzzz', or 65 characters long in the format PARM='SVCNUM=xxx,RUNTYPE=zzzzzzz,SVCENM=xxx,RUNETYP=zzzzzzz,SUFFIX=ssss'. System Action: Processing continues without STCK/STCKSYNC and STCKE support. Operator Response: Correct the parameter, then resubmit the XGSTKINS job. XG0105 GETMAIN FAILED FOR SP241 STORAGE Explanation: System Action: XGSTKINS detected an error while trying to acquire storage in SP241. Processing continues without STCK/STCKSYNC support. Operator Response: Contact the Xchange Customer Support staff. XG0106 SVC NUMBER MUST BE WITHIN 200-255 RANGE Explanation: XGSTKINS detected an error on the xxx specification of the SVCNUM=xxx keyword. xxx must indicate a user SVC number in the range of 200 to 255. System Action: Processing continues without STCK/STCKSYNC support. Operator Response: Correct the parameter, then resubmit the XGSTKINS job. XG0107 (XGSTKSVC|XGSTESVC) HAS NEVER BEEN INSTALLED AS SVCxxx - USE (RUNTYPE|RUNETYP)=INSTALL Explanation: XGSTKINS tried to REFRESH SVCxxx as requested, but detected that (XGSTKSVC|XGSTESVC) was never installed as that SVC number. System Action: Processing continues without STCK/STCKSYNC and/or STCKE support. A-14 Xpediter/Xchange Installation and User Guide Operator Response: Change the parameter to specify (RUNTYPE|RUNETYP)=INSTALL, then resubmit the XGSTKINS job. XG0108 SVCxxx TO BE REFRESHED IS NOT (XGSTKSVC|XGSTESVC) Explanation: XGSTKINS determined that SVCxxx is already in use and is not the (XGSTKSVC|XGSTESVC) SVC. System Action: Processing continues without STCK/STCKSYNC and/or STCKE support. Operator Response: Change the parameter to specify the same SVCxxx used to install (XGSTKSVC|XGSTESVC), then resubmit the XGSTKINS job. XG0109 (SVCNUM|SVCENM)= KEYWORD NOT SPECIFIED Explanation: XGSTKINS determined that the (SVCNUM|SVCENM)=xxx keyword is missing from the parameter statement. System Action: Processing continues without STCK/STCKSYNC and/or STCKE support. Operator Response: Add the (SVCNUM|SVCENM)=xxx keyword to the parameter, then resubmit the XGSTKINS job. XG0110 (RUNTYPE|RUNETYP)= KEYWORD NOT SPECIFIED Explanation: XGSTKINS determined that (RUNTYPE|RUNETYP)=zzzzzzz keyword is missing from the parameter statement. System Action: Processing continues without STCK/STCKSYNC and/or STCKE support. Operator Response: Add the (RUNTYPE|RUNETYP)=zzzzzzz keyword to the parameter, then resubmit the XGSTKINS job. zzzzzzz must be REFRESH or INSTALL. XG0111 RUNTYPE= AND RUNETYP= MUST BE INSTALL OR REFRESH Explanation: XGSTKINS determined that in the RUNTYPE=zzzzzzz and/or RUNETYP=zzzzzzz keyword, zzzzzzz is not INSTALL or REFRESH. System Action: Processing continues without STCK/STCKSYNC and/or STCKE support. Operator Response: Change the zzzzzzz in the RUNTYPE= and/or RUNETYP= keyword to INSTALL or REFRESH, then resubmit the XGSTKINS job. XG0112 SVCxxx IS ALREADY IN USE AND IS NOT (XGSTKSVC|XGSTESVC) Explanation: The SVC number supplied is not “open”, and the module that is located there is not (XGSTKSVC|XGSTESVC). System Action: Processing continues without STCK/STCKSYNC and/or STCKE support. Operator Response: Get an available user SVC number in the range of 200 to 255. Bring down the Xchange subsystem and resubmit the job with the new available SVC number. XG0113 SVC NUMBER MUST BE 3 DIGITS WITHIN 200-255 Explanation: XGSTKINS determined that the SVC number specified in the SVCNUM=xxx and/or SVCENM=xxx keyword is not a 3-digit number in the range of 200 to 255. System Action: Processing continues without STCK/STCKSYNC and/or STCKE support. Operator Response: Specify a 3-digit user SVC number in the range of 200 to 255, then resubmit the XGSTKINS job. XG0114 REQUIRED PARM IS MISSING Explanation: XGSTKINS determined that no parameter was specified on the EXEC statement. System Action: Processing continues without STCK/STCKSYNC and STCKE support. Operator Response: Specify the required parameter, then resubmit the XGSTKINS job. Xchange Messages XG0115 A-15 (XGSTKSVC|XGSTESVC) HAS BEEN zzzzzzzzz AS SVCxxx Explanation: XGSTKINS has completed successfully, and (XGSTKSVC|XGSTESVC) (SVCxxx) is now available for use. xxx is the SVC number requested, and zzzzzzzzz is either INSTALLED or REFRESHED. System Action: XGSTKINS will complete normally. Operator Response: None. XG0116 (XGSTKSVC|XGSTESVC) SVCxxx IS NOT VALID Explanation: System Action: The value for (SVCNUM|SVCENM)= has a non-numeric digit. Processing continues without STCK/STCKSYNC and/or STCKE support. Operator Response: Change the incorrect value and resubmit the job. XG0117 (XGSTKSVC|XGSTESVC) WAS ALREADY INSTALLED AS SVCxxx Explanation: The (RUNTYPE|RUNETYP)=INSTALL option was used to start the Xchange address space. The SVC had been installed with an earlier start-up of Xchange. System Action: None. Operator Response: None. XG0119 THE NUMBER OF URE(S) IS AT OR EXCEEDS xxx% OF CAPACITY Explanation: The Xchange URE pool is at or exceeds xxx% of capacity. When xxx reaches 100%, no more entries can be added. System Action: When xxx reaches 100%, the job’s date/time requests will not be exchanged. Operator Response: The Xchange CMSC PARMLIB parameter NUMURE may require adjustment. See “How NUM Options Affect Xchange Use” on page 3-1. XG0120 OPEN ERROR ON XGIMSREQ FILE Explanation: System Action: The file associated with the XGIMSREQ DD failed to open. Processing terminates. Operator Response: Verify that the file associated with the XGIMSREQ DD is the one that was allocated and initialized for IMS Message Level Support during Xchange installation. XG0121 READ ERROR ON XGIMSREQ FILE Explanation: System Action: The file associated with the XGIMSREQ DD had a read error. Processing terminates. Operator Response: Verify that the file associated with the XGIMSREQ DD is the one that was allocated and initialized for IMS Message Level Support during Xchange installation. XG0122 XGIMSREQ FILE NOT INITIALIZED Explanation: System Action: The file associated with the XGIMSREQ DD was not initialized. Processing terminates. Operator Response: Verify that the file associated with the XGIMSREQ DD is the one that was allocated and initialized for IMS Message Level Support during Xchange installation. XG0123 INVALID PARM, DEFAULT SSID (CWXG) USED Explanation: System Action: The XGCLNREQ PARM value “SUBSYS=ssid” is in error. The program continues and uses the default ssid of CWXG. Operator Response: Verify that the “SUBSYS=” is spelled correctly. Also, verify that the ssid does not exceed 4 characters in length. See “Automatically Deleting Xchange Batch Requests (Optional)” on page 5-32. A-16 Xpediter/Xchange Installation and User Guide XG0200 Xchange xxxxxxxx xxxxxxxx processing has begun Explanation: System Action: Informational. Xchange has begun processing specified by xxxxxxxx xxxxxxxx. None. Operator Response: None. XG0201 Xchange xxxxxxxx xxxxxxxx processing has ended Explanation: xxxxxxxx. System Action: Informational. Xchange has completed processing specified by xxxxxxxx None. Operator Response: None. XG0202 Xchange xxxxxxxx xxxxxxxx turned on from PLT Explanation: Informational. Xchange support specified by xxxxxxxx xxxxxxxx was enabled during CICS initialization. If not specified, transaction support is assumed. System Action: None. Operator Response: None. XG0203 Unsupported CICS release - Xchange terminated Explanation: System Action: Xchange cannot determine the release of CICS being started. Xchange terminates. Operator Response: Start the CICS region with a supported release of CICS. XG0204 Xchange could not find the required transaction XXXX Explanation: System Action: Xchange could not start transaction XXXX. Xchange terminates. Operator Response: Ensure that a transaction definition exists for the transaction and its initial program as shown in the documented member of dataset CPWR.MLXGnnn.SLXGDATA. XG0205 Xchange unable to enable CICS exit programs Explanation: System Action: Xchange cannot enable CICS exit programs. Xchange terminates. Operator Response: Contact the Xchange Customer Support staff. XG0206 Xchange subsystem not active Explanation: Xchange subsystem, specified on the first record of dataset pointed to by DD XGSEQINP, is currently not active. System Action: Xchange terminates. Operator Response: Ensure dataset pointed to be DD XGSEQINP is defined properly. Start the Xchange subsystem specified on the first record of the input dataset. XG0207 Xchange unable to open dddddddd DD Explanation: System Action: Open of dddddddd DD was unsuccessful. Xchange terminates. Operator Response: Verify that the dataset the DD points to is correct. Check the console log for additional system messages that may indicate the cause of the error. XG0208 Xchange error reading XGSEQINP DD Explanation: System Action: Reading a record from file XGSEQINP was unsuccessful. Xchange terminates. Xchange Messages A-17 Operator Response: Ensure that file XGSEQINP is defined as described in the “Step 7. Enable CICS Transaction Support” subsection entitled “PLT Initialization” on page 3-17. XG0209 DD XGSEQINP missing from JCL Explanation: System Action: XGSEQINP DD could not be found in the CICS startup JCL. Xchange terminates. Operator Response: XG0210 Verify that the DD was properly added to the CICS startup JCL. Error getting JFCB via TIOT/SWAREQ for DD XGSEQINP Explanation: System Action: An internal error. Xchange terminates. Operator Response: Contact the Xchange Customer Support staff. XG0211 DD XGSEQINP is "DD DUMMY" Explanation: System Action: XGSEQINP DD was assigned as DD DUMMY. Xchange terminates. Operator Response: Correct the CICS startup JCL to point to a valid input dataset. XG0212 DD XGSEQINP requires DSORG=PS Explanation: System Action: XGSEQINP DD was not defined as sequential. Xchange terminates. Operator Response: The dataset must be a sequential dataset: either a SYSIN dataset, sequential dataset, or a member in a PDS or PDSE. Correct your CICS startup JCL. XG0213 Dynamic allocation of DD XGSEQRPT failed Explanation: System Action: XGSEQRPT DD could not be dynamically allocated. Xchange terminates. Operator Response: Ensure that no DD exists in the CICS startup JCL for DD XGSEQRPT. Also ensure that no errors occurred during a previous Xchange initialization in this CICS region. XG0214 Deallocation of DD XGSEQRPT failed Explanation: System Action: XGSEQRPT DD could not be deallocated. Xchange terminates. Operator Response: Ensure that no DD exists in the CICS startup JCL for DD XGSEQRPT. Also ensure that no errors occurred during a previous Xchange initialization in this CICS region. XG0215 Xchange SUBSYSTEM has been altered - Xchange terminated Explanation: Another user or program has altered the Xchange environment. Xchange subsystem may have been cycled with CICS up. System Action: Xchange terminates. Operator Response: Try XGTS, STOP command, then XGTM. If the problem persists, contact the Xchange Customer Support staff. XG0216 DD XGSEQINP is empty Explanation: System Action: XGSEQINP DD is empty. Xchange terminates. Operator Response: Verify that records exist in the input file. A-18 Xpediter/Xchange Installation and User Guide XG0217 Xchange cannot initialize CICS region support Explanation: System Action: Xchange detected CICS transaction support was active. Xchange terminates. Operator Response: Do not use CICS transaction support and CICS region support at the same time. XG3014 EXEC PARM STATEMENT NOT ALLOWED Explanation: System Action: The EXEC contains a PARM= statement. This is not allowed. Processing terminates. Operator Response: Remove PARM= statement from EXEC. Resubmit job. XG3015 DDNAME XGSAV001 IS MISSING Explanation: not OFF. System Action: The Xchange start JCL does not contain the ddname XGSAV001 and SAVREQ is Processing terminates. Operator Response: Add the ddname or specify SAVREQ=OFF. Resubmit the job. XG3016 XCHANGE RESTORE PROCESSING COLD STARTED Explanation: Xchange save/restore processing is being cold started. Previously entered requests are not restored. System Action: Processing continues. Operator Response: None. XG3017 XCHANGE RESTORE PROCESSING WARM STARTED Explanation: Xchange save/restore processing is being warm started. Previously entered requests are restored. System Action: Processing continues. Operator Response: None. XG3018 XCHANGE SAVE/RESTORE PROCESSING DISABLED Explanation: Xchange save/restore processing has detected that the RESTREQ=OFF parameter has been specified. System Action: Xchange will not perform save/restore processing of user requests but will continue processing. Operator Response: None. XG3021 GETMAIN ERROR, INCREASE REGION SIZE Explanation: System Action: Xchange cannot allocate local storage. Processing terminates. Operator Response: Increase the region size and resubmit the job. XG3022 GENCB ACB ERROR Explanation: System Action: Xchange cannot allocate local storage for an ACB. Processing terminates. Operator Response: Increase the region size and resubmit the job. XG3023 GENCB RPL ERROR Explanation: System Action: Xchange cannot allocate local storage for an RPL. Processing terminates. Operator Response: Increase the region size and resubmit the job. Xchange Messages XG3024 A-19 SHOWCB ERROR Explanation: System Action: Xchange cannot perform a SHOWCB. Processing terminates. Operator Response: Contact the Xchange Customer Support staff. XG3025 NON-REUSABLE ESDS DATASET ALLOCATED Explanation: RBA. System Action: The save request dataset was built without REUSE. Xchange cannot reset the Processing terminates. Operator Response: Recreate the SAVE/RESTORE file with the provided JCL. Resubmit the job. XG3026 PUT ERROR Explanation: System Action: The save dataset is full. Processing continues. Additional requests cannot be processed. Operator Response: The dataset should be recreated with a larger allocation. Resubmit the job. XG3027 MODCB ERROR Explanation: System Action: Xchange cannot perform a MODCB. Processing terminates. Operator Response: Contact the Xchange Customer Support staff. XG3030 REQUEST NOT ADDED, INTERNAL ERROR Explanation: System Action: Xchange cannot add the request. Processing terminates. Operator Response: Contact the Xchange Customer Support staff. XG3031 REQUEST NOT ADDED, UNABLE TO ADD Explanation: System Action: Xchange cannot add the request. Processing terminates. Operator Response: Contact the Xchange Customer Support staff. XG3032 REQUEST NOT ADDED, AMBIGUOUS REQUEST Explanation: System Action: Xchange cannot add the request. This request already exists. Processing terminates. Operator Response: Contact the Xchange Customer Support staff. XG3033 REQUEST NOT ADDED, ADD REQUEST ERROR Explanation: System Action: Xchange cannot add the request. Processing terminates. Operator Response: Contact the Xchange Customer Support staff. XG3034 REQUEST NOT ADDED, INVALID DATE/TIME Explanation: System Action: Xchange cannot add the request. The date and/or time is not valid. Processing terminates. Operator Response: Contact the Xchange Customer Support staff. XG3035 XCHANGE BLDR PROCESSING ERROR Explanation: Xchange could not build a save request list. A-20 Xpediter/Xchange Installation and User Guide System Action: Processing continues. Additional requests cannot be processed. Operator Response: Contact the Xchange Customer Support staff. XG3037 XCHANGE RESTORE PROCESSING STARTED Explanation: System Action: Xchange restore processing has started. Processing continues. Operator Response: None. XG3038 XCHANGE RESTORE PROCESSING SUCCESSFUL Explanation: System Action: Xchange restore processing was successful. Processing continues. Operator Response: None. XG3039 XCHANGE SAVE PROCESSING STARTED Explanation: System Action: Xchange save processing has started. Processing continues. Operator Response: None. XG3040 XCHANGE SAVE PROCESSING SUCCESSFUL Explanation: System Action: Xchange save processing was successful. Processing continues. Operator Response: None. XG3041 XCHANGE COLD START PROCESSING STARTED Explanation: System Action: Xchange restore processing is being cold started. Processing continues. Operator Response: None. XG3042 XCHANGE COLD START PROCESSING ENDED Explanation: System Action: Xchange restore processing was cold started. Processing continues. Operator Response: None. XG3043 SVC emulation NOT INITIALIZED Explanation: System Action: No parm on the EXEC card. Processing continues without STCK/STCKSYNC support. Operator Response: If STCK/STCKSYNC supported is desired, refer to the Xpediter/Xchange Installation and User’s Guide. XG3044 XGSTKINS DID NOT INITIALIZE STCK/STCKSYNC Explanation: XGSTKINS was unable to initialize the STCK SVC. Also, the STCKSYNC support will not be available. Operator Response: Look for another message with the details explaining the reason for the failure. XG3045 IEATSTCK hook failed, STCKSYNC not processed Explanation: IEATSTCK could not be hooked. Operator Response: Contact the Xchange Customer Support staff. XG3046 XGSTKINS not loaded no STCK emulation Explanation: Informational. Caused by previous error. Xchange Messages XG3047 A-21 XGMSYNC not loaded no STCKSYNC support Explanation: hierarchy. XGMSYNC not found. XGMSYNC must be available in the library search Operator Response: Correct the problem and rerun XGMMAIN with PARM='SVCNUM=nnn,RUNTYPE=REFRESH'. XG3048 XGMSYNC Could not remove STCKSYNC support Explanation: Unable to remove STCKSYNC support. Operator Response: Contact the Xchange Customer Support staff. XG3049 XGMSYNC was not available to remove Explanation: XG3050 XGSTKINS STCK Emulation available Explanation: XG3051 Informational. xxxxxxxx is the address of the Xchange GCA. STCKSYNC Emulation already installed Explanation: subsystem. XG3056 The hooks in IEATSTCK have been removed. GCA pointer = xxxxxxxx Explanation: XG3055 SVCNUM= was not specified. No STCKSYNC support available. XGMSYNC STCKSYNC EMULATION REMOVED Explanation: XG3054 Informational. No STCK/STCKSYNC support requested Explanation: XG3053 Informational. XGMSYNC STCKSYNC Emulation available Explanation: XG3052 Informational. Informational. STCKSYNC support was already installed by another Xchange STCKSYNC Emulation was not removed Explanation: Informational. STCKSYNC support was not removed because it was not installed by this Xchange subsystem. XG3057 DB2 DDF support is enabled Explanation: XG3059 Display of IMS transaction support entries in ISPF is suppressed Explanation: XG3061 Informational. CICS generic request checking is active Explanation: XG3062 DB2 DDF support has been installed and is available. Generic CICS transaction support is enabled. STORAGE OBTAIN Failure - RC = XXXXXX Explanation: MACRO. System Action: RC is the decimal equivalent of the Return Code returned from the STORAGE Processing terminates. Operator Response: Increase region size. Resubmit job. XG3063 MSC$PMRQ GET Failure - RC = XXXXXX Explanation: Unexpected error returned from the CMSC MSC$PMRQ MACRO where RC is the decimal equivalent of the Return Code returned. System Action: Processing terminates. A-22 Xpediter/Xchange Installation and User Guide Operator Response: Verify that the CMSC has been installed. Refer to the Enterprise Common Components Installation and Customization Guide for detailed instructions. Resubmit job. XG3064 CMSC parm member not found Explanation: System Action: The CMSC parameter member requested was not found. Processing terminates. Operator Response: Verify that the Xchange CMSC Common PARMLIB member is present, prefixed with “XCHG” and suffixed with either the default “00” or the suffix present on the PARM of the EXEC JCL statement, and a CMSC REFRESH command was successfully performed. See the section entitled “CSMC Commands” in the ECC Installation and Customization Guide for detailed instructions on issuing this command. If the CMSC refresh was successful, message LXG00001 can be located in the JESLOG of the CMSC address space after a CMSC REFRESH command has been performed. Resubmit job. XG3065 CMSC environment is invalid Explanation: System Action: The CMSC environment requested is invalid. Processing terminates. Operator Response: If using the default CMSC environment, verify that the default CMSC address space is up and functioning properly. If DD “//CMSC????” is present, where ???? specifies the 4-character CMSC identifier specified on the CMSC PARM= EXEC JCL statement of the CMSC started task or batch job, verify that ???? represents a valid CMSC environment and the CMSC address space is up and functioning properly. Resubmit job. XG8000 XCHANGE SUBSYSTEM ssss INITIALIZATION HAS COMPLETED Explanation: Xchange has completed its initialization routines and is ready to exchange the date and time. XG9000 ssss SUBSYSTEM xxxx HAS ENDED Explanation: Xchange has successfully removed itself from the operating system at Xchange shutdown. All storage allocated in common subpools has been freed, and all date and time requests have reverted back to the current date and time. System Action: Xchange termination continues. Operator Response: None. XG9999 ssss ENTER XCHANGE COMMAND Explanation: This message is displayed as a write to operator with reply. Xchange is ready to accept operator commands. This message is displayed each time a command is entered. System Action: Processing continues. Operator Response: Reply to the message number accompanying this message to enter commands to Xchange Abend Codes This section lists all abend codes issued by the Xchange address space. Reason codes associated with particular abend codes are found in general register 15 at entry to abend and/or in the MVS error message describing the abend. Reason codes are provided here in decimal. When they appear in register 15, they are in hexadecimal. ABEND U0101 Module: XGMINIT at Xchange start up Problem Determination: 400, 401, and 402 (x’190’, x’191’, and x’192’) Xchange Messages A-23 Explanation: Xchange did not find a required load module in the STEPLIB or JOBLIB datasets. Operator Response: Make sure the following conditions have been satisfied: – The JCL or PROC used to start Xchange contains the correct load libraries in the STEPLIB or JOBLIB concatenation. – The module name is correct in the PARM operand of the EXEC statement used to execute Xchange. – The RACROUTE module, XGVRACRT, exists in the correct load libraries. Problem Determination: Explanation: queue. 403 (x’193’) There was insufficient main storage for the operator request element (ORE) Operator Response: Ensure that the NUMORE parameter in the Xchange CMSC PARMLIB member (see page 3-2) does not contain an unreasonably large value. If not, increase the value for the REGION parameter of the EXEC statement used to execute Xchange. Problem Determination: Explanation: 404 (x’194’) There is insufficient main storage for the journal request element (JRE) queue. Operator Response: Ensure that the NUMJRE parameter in the Xchange CMSC PARMLIB member (see page 3-2) does not contain an unreasonably large value. If not, increase the value for the REGION parameter of the EXEC statement used to execute Xchange. Problem Determination: Explanation: 405 (x’195’) There is insufficient main storage for the user request element (URE) queue. Operator Response: Ensure that the NUMURE parameter in the Xchange CMSC PARMLIB member (see page 3-2) does not contain an unreasonably large value. If not, increase the value for the REGION parameter of the EXEC statement used to execute Xchange. Problem Determination: 406 (x’196’) Explanation: An Xchange address space using the same subsystem ID is already executing on this MVS system. Operator Response: Only one Xchange address space can use a subsystem ID at a time. Make sure that the correct Xchange is being executed. Execute Xchange with a different configuration member name or terminate Xchange using the current subsystem ID. Problem Determination: 407 (x’197’) Explanation: There is insufficient main storage for the Xchange request element (XRE) queue. Operator Response: Ensure that the NUMXRE parameter in the Xchange CMSC PARMLIB member (see page 3-2) does not contain an unreasonably large value. If not, increase the value for the REGION parameter of the EXEC statement used to execute Xchange. Problem Determination: Explanation: 408 (x’198’) There is insufficient main storage for the Active Memory Block (AMB) pool. Operator Response: Ensure that the NUMAMB parameter in the Xchange CMSC PARMLIB member (see page 3-2) does not contain an unreasonably large value. If not, increase the value for the REGION parameter of the EXEC statement used to execute Xchange. Problem Determination: Explanation: 409 (x’199’) There is insufficient main storage for the Active Task Block (ATB) pool. Operator Response: Ensure that the NUMATB parameter in the Xchange CMSC PARMLIB member (see page 3-2) does not contain an unreasonably large value. If A-24 Xpediter/Xchange Installation and User Guide not, increase the value for the REGION parameter of the EXEC statement used to execute Xchange. Problem Determination: Explanation: 410 and 411 (x’19A’ and x’19B’) Xchange cannot initialize the User Interface Task. Operator Response: Contact the Xchange Customer Support staff. Problem Determination: 412 (x'19C') Explanation: The system is unable to establish the main task ESTAE environment — a nonzero return code resulted from an ESTAE macro. Operator Response: Contact the Xchange Customer Support staff. Problem Determination: 413 (x'19D') Explanation: Xchange was unable to exchange itself with the IBM-supplied supervisor calls (SVCs), program call (PC) routines, or the branch-entered TIME processes. Operator Response: Contact the Xchange Customer Support staff. Problem Determination: 414 and 415 (x’19E’ and x’19F’) Explanation: Xchange cannot initialize the subsystem. When the main task abends, the associated subtasks may abend also. Operator Response: Check whether subsystem is mistakenly running in SYS1.PARMLIB or reusing an old subsystem name following an upgrade. Contact the Xchange Customer Support staff. Problem Determination: 5000 and 5001 Explanation: Xchange cannot schedule its startup SRB in the master scheduler address space to establish the PC routine. Operator Response: Contact the Xchange Customer Support staff. Note: After the Operator Response for your specific problem above has been investigated without success, continue with the Explanation below. Explanation: There may be a problem somewhere within Common PARMLIB. Operator Response: Make sure the following conditions have been satisfied: – Verify that the CMSC has been installed and is functioning properly. Refer to the Enterprise Common Components Installation and Customization Guide for detailed instructions. – Verify that the Xchange CMSC Common PARMLIB member is present, is prefixed with XCHG , and is suffixed with either the default 00 or the suffix present on the PARM of the EXEC JCL statement in the Xchange startup JCL. Also verify that a CMSC REFRESH command was successfully performed. See the section entitled “CMSC Commands” in the Enterprise Common Components Installation and Customization Guide for detailed instructions on issuing this command. If the CMSC refresh was successful, message LXG00001 can be located in the JESLOG of the CMSC address space. – If using the default CMSC environment, verify that the default CMSC address space is up and functioning properly. – If using a secondary CMSC environment, the CMSC identifier is specified on the PARM= EXEC JCL statement in the secondary CMSC address space. Verify that DD //CWSC???? is present in the Xchange startup JCL (where ???? is the CMSC identifier), that ???? represents a valid CMSC environment, and that the secondary CMSC address space is up and functioning properly. ABEND U0130 Module: XGIMSPGM Explanation: End-of-File detected on XGIMSREQ file. Xchange Messages A-25 Operator Response: Restart IMS dependent region and then contact the Xchange Customer Support staff. ABEND U0140 Module: XGIMSPGM Explanation: The Xchange internal request header could not be found for this IMS dependent region. Operator Response: Restart IMS dependent region and then contact the Xchange Customer Support staff. ABEND U0150 Module: XGIMSPGM Explanation: The Xchange address has been recycled in the middle of processing an IMS transaction being exchanged. Operator Response: Restart IMS dependent region and then contact the Xchange Customer Support staff. ABEND U0200 Module: XGMINIT at Xchange start up Problem Determination: Explanation: (GCA). 100 There is insufficient main storage to obtain a global communications area Operator Response: Increase the value for the REGION parameter of the EXEC statement used to execute Xchange. Problem Determination: 101 Explanation: The PARM parameter on the EXEC statement is not valid. The value may be longer than eight characters or missing altogether. It is also possible that there was insufficient main storage for the “above the 16m line” work area queues. Operator Response: Increase the value for the REGION parameter of the EXEC statement used to execute Xchange. Also, make sure the PARM parameter is correctly specified. Problem Determination: Explanation: area queues. 102 There is insufficient virtual storage to obtain the “below the 16m line” work Operator Response: Increase the value for the REGION parameter of the EXEC statement used to execute Xchange. Problem Determination: Explanation: 103 The XGMINIT initialization module could not be loaded. Operator Response: correct datasets. Ensure that the STEPLIB or JOBLIB concatenation specified the ABEND U0202 Module: XGTMAIN Explanation: Compuware security failed during initialization. Operator Response: Contact the Xchange Customer Support staff. ABEND U0203 Module: XGMMAIN Explanation: The Xchange SVC11 recovery routine has detected more than three abends within a 15 minute interval. These abends are happening for jobs targeted for Xchange. The Xchange address space will be terminated. A-26 Xpediter/Xchange Installation and User Guide Operator Response: Restart and then contact the Xchange Customer Support staff. ABEND U0300 Module: XGJMAIN Explanation: The operator communication task cannot be initialized. Operator Response: Contact the Xchange Customer Support staff. ABEND U0400 Module: XGMHEDW Explanation: A call to LICENSE MANAGEMENT CHECKOUT presented a nonzero return code. The Xchange address space will be terminated. Operator Response: Contact the Compuware License Management Customer Support staff. There is a license issue that needs to be resolved. ABEND U0406 Module: XGMHEDW Explanation: A storage obtain error or nonzero return code from LMRETMSG processing. The Xchange address space will be terminated. Operator Response: Contact the Xchange Customer Support staff. ABEND U0502 Module: XGJMAIN Explanation: A FREEMAIN of a journal dataset buffer has not been successful. Because journal buffers are relatively large, the journal task abends in this condition so MVS does not allocate unnecessary virtual storage. Operator Response: Contact the Xchange Customer Support staff. ABEND U0503 Module: XGJMAIN Explanation: An invalid journal dataset buffer has been encountered. Because journal buffers are relatively large, the journal task abends in this condition so MVS does not allocate unnecessary virtual storage. Operator Response: Contact the Xchange Customer Support staff. ABEND U3000 Module: XGJMAIN at Xchange start up Explanation: Xchange was not able to attach the operator task or an insufficient number of operator request elements (OREs) were available. Operator Response: Increase the value of the NUMORE parameter in the Xchange CMSC PARMLIB member (see page 3-2). Re-execute Xchange. ABEND U3001 Module: XGJMAIN at Xchange start up Explanation: The operator task was unable to complete initialization. Operator Response: Contact the Xchange Customer Support staff. ABEND U3002 Module: XGJMAIN at Xchange start up Explanation: The operator subtask has abended and restarted three times. It has abended again. Xchange terminates with this abend code. Operator Response: Contact the Xchange Customer Support staff. Xchange Messages A-27 ABEND U4000 Module: XGSTKINS Problem Determination: 001 See message XG0103 002 See message XG0104 003 See message XG0105 004 See message XG0106 005 See message XG0107 006 See message XG0108 007 See message XG0109 008 See message XG0110 009 See message XG0111 00A See message XG0112 00B See message XG0113 00C See message XG0114 Explanation: XGSTKINS encountered an error. There will be an XG0xxx message in the joblog prior to the abend. Operator Response: See appropriate XG0xxx message associated with each reason code for course of action. CICS Abend Codes and Messages Abend Codes XGNA Module: XGTMAIN Explanation: XGTMAIN is not authorized to issue EXEC CICS INQUIRE calls. Operator Response: Contact the Xchange Customer Support staff. XGIE Module: XGTMAIN Explanation: Invalid exit request. Operator Response: Contact the Xchange Customer Support staff. XGIV Module: XGTMAIN Explanation: An installation error has been detected. Operator Response: Review the install procedure in the Xpediter/Xchange Installation and User’s Guide. If the problem continues, contact the Xchange Customer Support staff. XGNS Module: XGTMAIN A-28 Xpediter/Xchange Installation and User Guide Explanation: No storage available. Operator Response: Contact the Xchange Customer Support staff. XGSY Module: XGTEIOUT Explanation: Xchange ended during exit XGTEIOUT processing. Operator Response: Resubmit the XGTM transaction. Messages XGT001 Module: XGTMAIN Explanation: No Xchange subsystem active. Operator Response: Start the subsystem and retry the XGTM transaction. XGT002 Module: XGTMAIN Explanation: More than one Xchange subsystem active. Operator Response: Either run XGTM and select a subsystem, or ensure that only one subsystem is running and restart CICS. XGT003 Module: XGTMAIN Explanation: Xchange CICS transaction support cannot be started. Operator Response: See explanation for previously displayed message. XGT004 Module: XGTMAIN Explanation: Xchange 03.00.00 CICS transaction support terminated. Operator Response: None. XPCTFTCH has been disabled. See explanation for previously displayed message, if any. XGT005 Module: XGTMAIN, XGTSEQI Explanation: Unsupported CICS release - Xchange terminated. Operator Response: Contact the Xchange Customer Support staff. XGT006 Module: XGTMAIN, XGTSEQI Explanation: Xchange SUBSYSTEM has been altered - Xchange terminated. Operator Response: Another user or program has altered the Xchange environment. Xchange subsystem may have been cycled with CICS up. Try XGTS, STOP command, then XGTM. If the problem persists, contact the Xchange Customer Support staff. XGT007 Module: XGTMAIN Explanation: Xchange SUBSYSTEM error - Xchange terminated. Operator Response: Subsystem active but not responding. Restart the subsystem and retry the XGTM transaction. If the problem persists, contact the Xchange Customer Support staff. Xchange Messages A-29 XGT008 Module: XGTMAIN Explanation: Xchange performed PLT shutdown processing. Operator Response: None. XGT009 Module: XGTMAIN Explanation: Xchange could not find the required program and/or map. Operator Response: Update the RDO definitions. See “Step 7. Enable CICS Transaction Support” on page 3-15. XGT010 Module: XGTSEQI Explanation: Xchange subsystem not active. Operator Response: Ensure dataset pointed to by DD XGSEQINP is defined properly. Start the Xchange subsystem specified on the first record of the input dataset. XGT011 Module: XGTSEQI Explanation: Xchange unable to enable CICS exit programs. Operator Response: Contact the Xchange Customer Support staff. XGT012 Module: XGTSEQI Explanation: Xchange sequential input processing has ended. Operator Response: None. XGT013 Module: XGTSEQI Explanation: DD XGSEQINP requires DSORG=PS. Operator Response: The dataset must be a sequential dataset: either a SYSIN dataset, sequential dataset, or a member in a PDS or PDSE. Correct your CICS startup JCL. XGT014 Module: XGTSEQI Explanation: DD XGSEQINP is "DD DUMMY". Operator Response: Correct the CICS startup JCL to point to a valid input dataset. XGT015 Module: XGTSEQI Explanation: Error getting JFCB via TIOT/SWAREQ for DD XGSEQINP. Operator Response: Contact the Xchange Customer Support staff. XGT016 Module: XGTSEQI Explanation: DD XGSEQINP missing from JCL. Operator Response: Verify that the DD was properly added to the CICS startup JCL. A-30 Xpediter/Xchange Installation and User Guide XGT017 Module: XGTSEQI Explanation: Xchange unable to open dddddddd DD. Operator Response: Verify that the dataset the DD points to is correct. Check the console log for additional system messages that may indicate the cause of the error. XGT018 Module: XGTSEQI Explanation: Dynamic allocation of DD XGSEQRPT failed. Operator Response: Ensure that no DD exists in the CICS startup JCL for DD XGSEQRPT. Also ensure that no errors occurred during a previous Xchange initialization in this CICS region. XGT019 Module: XGTSEQI Explanation: Deallocation of DD XGSEQRPT failed. Operator Response: Ensure that no DD exists in the CICS startup JCL for DD XGSEQRPT. Also ensure that no errors occurred during a previous Xchange initialization in this CICS region. XGT020 Module: XGTSEQI Explanation: Xchange error reading XGSEQINP DD. Operator Response: Ensure that file XGSEQINP is defined as described in the “Step 7. Enable CICS Transaction Support” subsection entitled “PLT Initialization” on page 3-17. XGT021 Module: XGTSEQI Explanation: DD XGSEQINP is empty. Operator Response: Verify that records exist in the input file. XGT022 Module: XGTREGN Explanation: XGTR must be started during PLTPI processing. Operator Response: See “Step 8. Enable CICS Region Support” on page 3-18. Xchange Parsing Exit Messages These messages are initiated from the Xchange Parsing Exit, LXGPARSE, and can be located in the JESLOG of the CMSC address space after a CMSC REFRESH command has been performed. LXG00001 XCHANGE PARSER RETURNED SUCCESSFULLY. Explanation: Informational. The Xchange Parsing Exit successfully validated all parameters present and generated a common memory object. System Action: None. Operator Response: None. Xchange Messages LXG00002 A-31 XCHANGE PARSER VALIDATION REQUIRED. Explanation: was required. The Request Code returned from the CMSC did not indicate that validation System Action: The Xchange Parsing Exit terminates without processing any parameters and does not generate a common memory object. Operator Response: Contact the Xchange Customer Support staff. LXG00003 XCHANGE PARSER FIXED FORMAT REQUIRED. Explanation: records. The Record Format Code returned from the CMSC did not indicate fixed System Action: The Xchange Parsing Exit terminates without processing any parameters and does not generate a common memory object. Operator Response: Verify that your CMSC PARMLIB was allocated with a Record Format of Fixed Block. Make corrections. Perform CMSC REFRESH command. LXG00004 XCHANGE PARSER RETURNED NO PARAMETERS. Explanation: No Xchange parameters were found in the CMSC PARMLIB. System Action: Informational. The Xchange Parsing Exit generated a common memory object containing default values. Operator Response: Verify that you intentionally wanted to use the default values. If not, create an Xchange CMSC PARMLIB member whose name is prefixed with XCHG and suffixed with the SUFFIX= value on the PARM of the EXEC JCL statement of the Xchange Startup JCL if present or 00 (default) if the SUFFIX= has been omitted. Verify that Xchange parameters are present in the Xchange CMSC PARMLIB member. Perform the CMSC REFRESH command. LXG00005 CICSMAXR PARM GREATER THAN CICSMAXS. Explanation: CICSMAXR exceeds CICSMAXS. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check CICSMAXR parameter. Make corrections. Perform CMSC REFRESH command. LXG00006 keyword=value DOES NOT CONTAIN A VALID KEYWORD. Explanation: There is no known Xchange parameter with the specified keyword. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check keyword and format of parameter. Make corrections. Perform CMSC REFRESH command. LXG00007 keyword=value IS INVALID. FIRST CHAR MUST BE ALPHA OR "$", "@", OR "#". Explanation: The first character of value must be alphabetic, “$”, “@”, or “#”. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check value. Make corrections. Perform CMSC REFRESH command. LXG00008 "#". keyword=value IS INVALID. AFTER FIRST CHAR MUST BE ALPHANUM OR "$", "@", OR Explanation: “@”, or “#”. The second and subsequent characters of value must be alphanumeric, or “$”, System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. A-32 Xpediter/Xchange Installation and User Guide Operator Response: Check value. Make corrections. Perform CMSC REFRESH command. LXG00009 keyword=value IS INVALID. CANNOT HAVE MULTIPLE keyword PARMS. Explanation: keyword was present in more than one parameter. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check Xchange CMSC PARMLIB member for multiple keywords. Make corrections. Perform CMSC REFRESH command. LXG00010 keyword=value IS INVALID. MAXIMUM NUMBER OF keyword PARMS EXCEEDED. Explanation: keyword was present in more parameters than allowed. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check Xchange CMSC PARMLIB member for multiple keywords. Make corrections. Perform CMSC REFRESH command. LXG00011 keyword=value IS INVALID. MUST BE list. Explanation: value specified was not one of those listed. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check value. Make corrections. Perform CMSC REFRESH command. LXG00012 keyword=value IS INVALID. MUST BE FROM n TO n. Explanation: value specified was not in the range listed. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check value. Make corrections. Perform CMSC REFRESH command. LXG00013 keyword=value IS INVALID. MUST BE n BYTES. Explanation: value specified was not the number of bytes listed. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check value. Make corrections. Perform CMSC REFRESH command. LXG00014 keyword=value IS INVALID. MUST BE n NUMERIC BYTES. Explanation: value specified was not the number of numeric bytes listed. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check value. Make corrections. Perform CMSC REFRESH command. LXG00015 keyword=value IS INVALID. MUST BE NUMERIC. Explanation: value specified was not numeric. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check value. Make corrections. Perform CMSC REFRESH command. LXG00016 keyword=value IS INVALID. MUST BE 1 TO n BYTES. Explanation: value specified was not in the range of the number of bytes listed. Xchange Messages A-33 System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check value. Make corrections. Perform CMSC REFRESH command. LXG00017 keyword=value IS INVALID. ONLY 1 LOG FILE CAN BE SELECTED AS BACKUP. Explanation: More than one LOGCOPY=YES parameter was detected. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check Xchange CMSC PARMLIB member for multiple LOGCOPY=YES parameters. Make corrections. Perform CMSC REFRESH command. LXG00018 keyword=value LAST CHARACTER IS INVALID. Explanation: The last character of the value specified is invalid. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check value. Make corrections. Perform CMSC REFRESH command. LXG00019 keyword=value MUST BE HHMM FORMAT. time interval IS INVALID. Explanation: The time interval portion of the value specified is invalid. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check value. Make corrections. Perform CMSC REFRESH command. LXG00020 keyword=value OPERAND IS REQUIRED WHEN SECUSE=YES. Explanation: detected. value was not specified and is required since parameter SECUSE=YES was System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check parameter. Make corrections. Perform CMSC REFRESH command. LXG00021 keyword=value OPERAND IS REQUIRED. Explanation: value was not specified and is required. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check parameter. Make corrections. Perform CMSC REFRESH command. LXG00022 keyword=value PARM CONFLICTS WITH keyword PARM. Explanation: keyword. keyword in this parameter conflicts with another parameter with the listed System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check parameters. Make corrections. Perform CMSC REFRESH command. LXG00023 keyword=value PARM CONTAINS INVALID SYNTAX. Explanation: value contains invalid syntax. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. A-34 Xpediter/Xchange Installation and User Guide Operator Response: Check value. Make corrections. Perform CMSC REFRESH command. LXG00024 keyword=value PARM DUPLICATE, MISSING, OR NOT IN CORRECT ORDER. Explanation: Either the parameter specified is a duplicate, a parameter has been detected as missing, or a parameter is out of sequence. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check parameters. Make corrections. Perform CMSC REFRESH command. LXG00025 keyword=value PARM EXCEEDS MAXIMUM LENGTH. Explanation: value exceeds the maximum length allowed. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check value. Make corrections. Perform CMSC REFRESH command. LXG00026 MISSING keyword PARAMETER Explanation: keyword has been detected as missing. System Action: The Xchange Parsing Exit terminates and does not generate a common memory object. Operator Response: Check parameters for keyword. Make corrections. Perform CMSC REFRESH command. B-1 Appendix B. Using Xchange Internal Diagnostics Appendix A. App B Beginning with Release 3.2, Xchange incorporates built-in trace diagnostics to aid in resolving customer problems. These diagnostics, when activated, require that the MVS Generalized Trace Facility (GTF) be running in order to capture the trace records. These trace records are saved in a dataset which may then be sent to the Xchange Customer Support staff for analysis. This appendix explains the steps required to prepare to use the trace diagnostics capability as well as how to actually invoke the facility to record a trace of an Xchange job experiencing problems. Allocating the Trace Dataset The dataset to be used by the GTF member GTFXG must be allocated prior to using Xchange’s internal diagnostics. Sample JCL to allocate the dataset is shown in Figure B-1. Figure B-1. JCL to Allocate GTF Dataset //ALLOC //DD1 // // // // // // // EXEC PGM=IEFBR14 DD DSN=CWXG.GTF.TRACE, DISP=(NEW,CATLG), SPACE=(CYL,(50,0,0)), RECFM=VB, LRECL=27994, BLKSIZE=27998, DSORG=PS Execution Procedure and Parameters Figure B-2 shows a sample procedure for invoking GTF. This PROC may be placed in SYS1.PROCLIB or some other proclib defined to the JES subsystem. Figure B-2. Sample PROC for Invoking GTF //GTF PROC MEMBER=GTFXG //* LIB: SYS1.PROCLIB(GTF) //* GDE: CBIPO MVS INSTALLATION //* DOC: THIS PROCEDURE EXECUTES THE GTF TRACE PROGRAM. //* //IEFPROC EXEC PGM=AHLGTF,PARM=’MODE=EXT,DEBUG=NO,TIME=YES’, // REGION=2280K,DPRTY=(15,15) //IEFRDER DD DSNAME=CWXG.GTF.TRACE,DISP=OLD //SYSLIB DD DSNAME=SYS1.PARMLIB(&MEMBER),DISP=SHR B-2 Xpediter/Xchange Installation and User Guide Store the sample parameters shown in Figure B-3 in SYS1.PARMLIB under member GTFXG. Before capturing diagnostic trace data as described in the next section, replace xxxxxxxx with the jobname of the task experiencing an Xchange problem. Figure B-3. Sample GTF Parameters TRACE=USRP,JOBNAMEP USR=(100,101,102,103,104,105) JOBNAME=xxxxxxxx END Capturing Diagnostic Trace Data Use the following steps to capture Xchange internal diagnostics trace data. 1. Enter the MVS console command S GTF.XG01,MEMBER=GTFXG to start GTF. 2. To invoke Xchange’s diagnostics trace capture, enter the MVS console command F jjjjjjjj,DTRACE ON where jjjjjjjj is the jobname of the Xchange address space. 3. Run the job experiencing the Xchange problem. 4. To terminate the capture, enter the MVS console command F jjjjjjjj,DTRACE OFF where jjjjjjjj is the jobname of the Xchange address space. 5. Enter the MVS console command P XG01 to stop GTF. The trace information is captured to dataset CWXG.GTF.TRACE. This dataset should then be sent to the Xchange Customer Support staff to aid in problem resolution. G-1 Glossary disaster recovery support facility. A facility that lets you activate Xchange at a disaster recovery site without first contacting Compuware. absolute address. An address that can reference the specified memory location without further modification. DMPDCLAS parameter. The Xchange CMSC PARMLIB member option that lets you specify the optional Data Class of any dump dataset that is dynamically allocated by Xchange. administrator. In Xchange, the user ID that has the authority to input operator commands from the batch facility and to delete pattern requests and jobs created by a different user ID. ALLOCLOG member. The member of the SLXGCNTL PDS that contains JCL for creating an Xchange journal dataset. ASMRACRT. The member of the SLXGCNTL PDS that contains JCL for assembling and linking the RACROUTE module. Authorized Program Facility (APF) load library. The library from which the Xchange address space is executed. batch. Processing in which jobs are grouped (batched). The jobs are executed sequentially, and each job must be processed to completion before the following job can begin execution. batch facility. In Xchange, a facility that lets you simulate a date and time by adding a step to a job. case sensitivity. Whether a group of letters is uppercase or lowercase has relevance. For example, “XPEDITER” is different from “XPEDiter” which is different from “xpediter.” DMPMCLAS parameter. The Xchange CMSC PARMLIB member option that lets you specify the optional Management Class of any dump dataset that is dynamically allocated by Xchange. DMPPFX parameter. The Xchange CMSC PARMLIB member option that lets you specify your own prefix used on all dump datasets. DMPSCLAS parameter. The Xchange CMSC  PARMLIB member option that lets you specify the optional Storage Class of any dump dataset that is dynamically allocated by Xchange. DMPUNIT parameter. The Xchange CMSC PARMLIB member option that lets you specify your own MVS UNITNAME. DMPVOL parameter. The Xchange CMSC PARMLIB member option that lets you specify the optional serial number of the volume that contains any dump datasets. external security package. A package (such as RACF) that makes external security calls to protect jobs, steps, and programs from unauthorized execution. extract. See Journal extract. CICS/VS. Customer Information Control System for Virtual Storage. CICS/VS operates on a host system, such as a System/370 system or a 30xx or a 43xx processor. Help facility. Online support that can be invoked for clarification or aid in relation to a problem. ISPMLIB file. The Xchange file for ISPF messages. CICS transaction support. The Xchange feature that exchanges the date and time for individual programs or transactions within a CICS region. close. In Xchange, the process of closing and deallocating the current journal dataset but not opening the next journal dataset. No logging takes place until the OPEN command is entered. Contrast with Swap. code block. In a COBOL program, a sequential group of statements. A code block has one entry point and one exit point. ISPPLIB file. The Xchange file for ISPF panel definitions. JCLUTILI JCL. Sample JCL for installing the Xchange customer information file. job stream. A specific series of job control procedure statements to execute programs in a predetermined sequence. journal. A dataset or report created from the dataset that contains all date and time simulations for the jobs, steps, procedure steps, and programs that you specified for Xchange. You can record all G-2 Xpediter/Xchange Installation and User Guide Xchange system activity or only the satisfied date and time request activity. journal exit. When a journal record is written for an SVC11, Xchange invokes a user exit to determine the program ID that is reported. This exit can be your own or the exit provided by Xchange (see XGJEXIT1 user exit). journal extract. A printout of the records within the Xchange journal dataset. MODIFY command. An MVS command that can be used to shut down Xchange. NUMAMB parameter. The Xchange CMSC PARMLIB member option that specifies the maximum number of jobs that can be run by the Xchange subsystem or by all users of the subsystem. NUMATB parameter. The Xchange CMSC PARMLIB member option that specifies the maximum number of steps that can be run by the Xchange subsystem or by all users of the subsystem. NUMJRE parameter. The Xchange CMSC PARMLIB member option that specifies the maximum number of queued requests to write messages to the Xchange journal dataset supported by the Xchange subsystem or supported for all users of the subsystem. NUMORE parameter. The Xchange CMSC PARMLIB member option that specifies the maximum number of queued requests to display messages to the operator that can be supported by the Xchange subsystem or supported for all users of the subsystem. NUMURE parameter. The Xchange CMSC PARMLIB member option that specifies the maximum number of queued requests from the ISPF interface to the Xchange subsystem or to all users of the subsystem. NUMXRE parameter. The Xchange CMSC PARMLIB member option that specifies the maximum number of change request patterns that can be supported by the Xchange subsystem or supported for all users of the subsystem. online help. See Help facility. PREFIX command. A command that lets you view the user IDs of every user that has set a pattern request in the Xchange subsystem. PREVDATE parameter. The Xchange CMSC  PARMLIB member option that specifies whether previous dates are allowed (that is, whether a date can be exchanged for a date previous to the current date). PROCSTEP. An individual step within a series of job control statements that execute a predetermined sequence of programs. RACF. Resource Access Control Facility, an external security package. RACROUTE module. The RACF security module. For other types of external security, it may need to be modified. REPLY parameter. The Xchange CMSC PARMLIB member option that indicates whether an outstanding reply message will display on the operator console. SECDFLT parameter. The Xchange CMSC PARMLIB member option that either allows or denies access to jobs when a given entity name has not been defined to external security. SECPFX parameter. The Xchange CMSC PARMLIB member option that the external security module uses as a prefix when creating entity names to pass to the security system. SECUSE parameter. The Xchange CMSC PARMLIB member option that indicates whether to use external security. SHUTDOWN command. An operator command to terminate Xchange processing. shut down. The process of terminating (stopping) Xchange. You can terminate Xchange normally (after all queued and active jobs have ended or have been deleted) or immediately. Simulation Activity Report. A report that shows the contents of the Xchange journal dataset. The records are listed in sequential order by request. softcopy. An online version of a Compuware manual that can be read or printed from any licensed version of IBM BookManager READ. software mall. An electronic shopping service available through the IBM Information Network (INN). In the software mall, you can find the current release for Xchange. STOP command. An MVS command that can be used to shut down Xchange. SUBSYS parameter. The Xchange CMSC PARMLIB member option that defines the subsystem ID for an Xchange configuration. subsystem ID. Each copy of Xchange running on an MVS system is defined as a subsystem and given a four-character subsystem ID. G-3 SVCUPDTE macro. A macro that replaces an SVC. SVC11. A date and time request. swap. The process of closing and deallocating the current journal dataset and allocating and opening the next journal dataset. Contrast with Close. switched major node. A node whose minor nodes are physical and logical units attached by a switched synchronous data link control (SDLC) and token-ring links. TRACE command. An operator command that lets you specify which trace records Xchange will route to the journal dataset for a specific run. USRRACRT module. The member of the SLXGDATA PDS that contains the RACROUTE module. VSAM. Virtual storage access method. working storage section. A section of a COBOL program used to define the data items that are used in a program. XCHANGE command. The command you type to invoke Xchange if you have specified this command in the Xpediter/TSO command table during Xchange installation. You can type XCHANGE or XCH. XGBJRPRT program. The Xchange program that provides a dump of the journal dataset contents. XGIPLG01 program. The Xchange program that prints the Simulation Activity Report. XGIPXTRT program. The Xchange program that writes an extract of the Xchange journal dataset to a file. XGJEXIT1 user exit. When a journal record is written for an SVC11, Xchange invokes a user exit to determine the program ID that is reported. The exit provided by Xchange is XGJEXIT1. XGPRT program. A REXX program that you can use to print the output from the XGIPXTRT Xchange extract program. XPCTUPDT CLIST. The CLIST that is used to install the XCHANGE command in the Xpediter/TSO command table. Xpediter. A symbolic debugging and testing tool that is used by programmers to simplify the tasks of diagnosing and fixing programming errors by giving the programmer control over the execution of the program interactively at the source level. G-4 Xpediter/Xchange Installation and User Guide I-1 Index A A field, IMS, 5-36 abend codes, A-22 absolute address, G-1 ACF2, 3-26 Acrobat PDF online documentation, ix ACTIVATE primary command, IMS, 5-33 Active field, IMS, 5-36 activity report JCL, 6-7 ACTJ, A-1 additional considerations, jobclass support, 5-22 address space executing from APF load library, 1-8 administrator, G-1 designating, 3-30 ADVANCE command, 5-10, 5-55 Advance Indicator field, Advance Request Settings screen, ISPF interface, 5-16 ADVANCE primary command, IMS, 5-34 Advance Request Setting for IMS message level support screen fields, 5-40 Advance Request Settings screen, CICS transaction support Ind value, setting, 5-63 Advance Request Settings screen, IMS message level support Days offset, setting, 5-40 Hrs offset, setting, 5-40 Ind value, setting, 5-41 Mins offset, setting, 5-40 Advance Request Settings screen, ISPF interface Advance Indicator value, setting, 5-16 allocating journal datasets, 3-13 allocating save/restore dataset, 3-14 ALLOCLOG member, 3-13, G-1 ALLOCSAV member, 3-15 AMBG, A-1 APF See Authorized Program Facility load library ASKTIME call, 5-52 ASMRACRT, G-1 ASMRACRT member, 3-12 Assembler support, 1-1 assembling test programs, 3-31 asterisk (*) status code, ISPF interface, 5-6 Async field, Simulated Date Time Settings screen, 5-59 audience for manual, vii Authorized Program Facility (APF) load library, G-1 AUTHUSR parameter, 3-3 automatic request deletion, 3-16 automatically deleting Xchange batch requests, 5-32 B batch, G-1 batch facility, G-1 date, setting, 5-28 example scenario, 5-31 Global Hold Date/Time option, 5-29 offset, days, 5-29 offset, hours, 5-29 offset, indicator for future or past, 5-29 offset, minutes, 5-29 procedures, naming, 5-29 steps, naming, 5-29 subsystem ID, 5-29, 5-32 syntax, 5-27 terminating Xchange from, 4-5 time, setting, 5-29 batch requests, deleting automatically, 5-32 BYPSPLC parameter, 3-3 C C field, IMS, 5-36 C/S field, 5-59 C/S field, jobclass support, 5-21 C/S field, Simulated Date Time Settings screen, 5-7 case sensitivity, G-1 CAUT, A-1 CEE, 3-30 CEEPLPKA, 3-19–3-20, 5-51 CICS abend codes, A-27 CICS interface Days offset, setting, 5-62 Hrs offset, setting, 5-62 Ind value, setting, 5-62 Mins offset, setting, 5-62 CICS interface in offset format screen fields, 5-61 CICS messages, A-28 CICS region support, 3-18–3-19 CICS startup JCL, 3-15 CICS Transaction Activity report, journal, 6-6 CICS transaction IDs, 5-52 CICS transaction support, 3-15, 5-52, G-1 date, setting, 5-60 deleting requests, 5-53 jobs, naming, 5-59 line commands, 5-58 PF keys, 5-60 primary commands, 5-55 programs, naming, 5-59 screen fields, 5-58 Simulated Date Time Settings screen, 5-54 specifying the subsystem, 5-53 status codes, 5-58 time, setting, 5-60 transaction ID, naming, 5-59 transaction IDs, 5-52 CICS transaction support, offset format, 5-60 CICS/VS, G-1 CICSGNRC parameter, 3-3 CICSMAXR parameter, 3-4 CICSMAXS parameter, 3-4 CLASS parameter, 3-4 CLASS8 parameter, 3-5 I-2 Xpediter/Xchange Installation and User Guide CLISTs, updating TSO, 3-12 close, G-1 CLOSE operator command, 6-2 closing the journal, 6-1 CMSC PARMLIB, 1-4, 1-9 CNTL file, G-1 COBOL support, 1-1 code block, G-1 Command field, IMS, 5-36 command, Simulated Date Time Settings screen, 5-7, 5-59 commands line, 5-5, 5-15 operator, 4-4, 6-2 Common Storage Area, 3-1 compiling test programs, 3-31 Compuware FrontLine customer support website, xi Compuware Installer, 1-4 Compuware Shared Services, 1-3 installation, 1-3 minimum release requirement, 1-3 configuring external security, 3-26 console messages, MVS, A-7 Correlation ID field, 5-26 creating an inventory, 5-12 CSA See Common Storage Area customer support, xi CWXG, 3-29 CWXGCOB, 3-31 CWXGDATA, 3-31 CWXGDATE, 3-31 CWXGJCLC, 3-31 D D line command, CICS, 5-58 date and time offset, CICS transaction support, 5-56 date and time offset, IMS, 5-34 date and time offset, ISPF, 5-11 date, product DVD, 1-4 Days field, Advance Request Settings screen, IMS message level support, 5-40 Days field, Simulated Date Time Settings screen, CICS offset format, 5-62 Days field, Simulated Date Time Settings screen, jobclass offset format, 5-24, 5-39 Days field, Simulated Date Time Settings screen, offset format, 5-15 DB2 request fields, 5-25 DB2 SSID field, 5-26 DB2 support, 3-19–3-20 DDF command, 5-10 DDF parameter, 3-5 DDF support defining security rules, 3-28 exchange criteria, 5-2 DELDDF command, 5-10 DELETE command, 5-10 deleting completed entries, 5-10 deleting request automatically, 3-16 deleting requests under CICS, 5-53 deleting requests, CICS, 5-58 deleting Xchange batch requests, automatically, 5-32 DELRQST parameter, 3-5 DFHRPL concatenation, 3-15 DFHZATDX, 3-16 disabling all requests, IMS, 5-34 disaster recovery support facility, G-1 DISPIMS parameter, 3-5 displaying legal notice, 5-11 displaying pattern owners, 5-11 displaying release number, 5-12, 5-34, 5-57 displaying request owners, 5-57 displaying requests, CICS, 5-56 displaying requests, IMS, 5-34 displaying subsystem ID, 5-12 Distributed Data Facility (DDF) See DDF support DMPDCLAS parameter, 3-6, G-1 DMPJRNL, 6-9 DMPMCLAS parameter, 3-6, G-1 DMPPFX parameter, 3-6, G-1 DMPSCLAS parameter, 3-6, G-1 DMPUNIT parameter, 3-6, G-1 DMPVOL parameter, 3-6, G-1 dump Xchange journal, 6-9 E ECHJOBE parameter, 3-6 ECSA See Extended Common Storage Area EIBDATE, 5-52 EIBTIME, 5-52 enabling all requests, IMS, 5-33 END primary command, CICS, 5-55 environment, system, 1-1 error job requests, 5-6 errors, A-1 examples batch facility, 5-31 exclusions transactions, 3-17 executing Xchange batch job, 4-1 started task, 4-3 exit for journal, 3-30 Extended Batch Facility, 5-43 Extended Common Storage Area, 3-1 external security package, G-1 external security, configuring, 3-26 extract, G-1 extract record format, 6-7 F fields, Advance Request Settings screen, 5-16 fields, Advance Request Settings screen, IMS message level support, 5-40 fields, CICS Transaction Activity Report, 6-6 fields, IMS Simulated Date Time Settings screen, 5-36 A, 5-36 Active, 5-36 C, 5-36 Command, 5-36 IOPCB and MVS/HLL, 5-37 message area, 5-37 Owner, 5-36 I-3 Program, 5-36 Req ID, 5-36 S, 5-36 Xchange Subsystem ID, 5-36 fields, IMS Simulated Date Time Settings screen, offset format, 5-39 fields, jobclass support, 5-21 C/S, 5-21 Imsg, 5-21 Jobclass, 5-21 fields, online journal, 6-3–6-4 fields, Simulated Date Time Settings screen, 5-6, 5-58 fields, Simulated Date Time Settings screen, CICS offset format, 5-61 fields, Simulated Date Time Settings screen, jobclass offset format, 5-23 fields, Simulated Date Time Settings screen, offset format, 5-14 fields, Simulation Activity Report, 6-5 Filter Correlation ID field, 5-25 Filter Days, Hrs, Mins field, Simulated Date Time Settings screen, 5-14, 5-21, 5-23 Filter DB2 SSID field, 5-25 Filter Ind field, Simulated Date Time Settings screen, 515, 5-24 Filter Jobname field, Simulated Date Time Settings screen, 5-6 Filter Procstep field, Simulated Date Time Settings screen, 5-7 Filter Program field, Simulated Date Time Settings screen, 5-7 Filter Resource Name field, 5-26 Filter row fields, 5-6, 5-14, 5-21, 5-23, 5-25 Filter Stepname field, Simulated Date Time Settings screen, 5-7 Filter UserId field, 5-26 Filter YYYY/MM/DD HH:MM:SS field, Simulated Date Time Settings screen, 5-7 FMID, 1-5 FrontLine, xi H H line command, CICS, 5-58 Help facility, G-1 help, online, 5-4 HELPPTFS, 3-12 HH:MM:SS field, jobclass support, 5-22 HH:MM:SS field, Simulated Date Time Settings screen, 5-9, 5-37, 5-60 holding requests, CICS, 5-58 how NUM options affect Xchange usage, 3-1 Hrs field, Advance Request Settings screen, IMS message level support, 5-40 Hrs field, Simulated Date Time Settings screen, CICS offset format, 5-62 Hrs field, Simulated Date Time Settings screen, jobclass offset format, 5-24, 5-39 Hrs field, Simulated Date Time Settings screen, offset format, 5-15 HTML documentation, ix I IBM, 3-30 IEASYS, 1-9 IGZ, 3-30 ILB, 3-30 IMS in offset format screen fields, 5-39 IMS Message Level Offset Support, 5-38 IMS Message Level Support, 5-32 comparison of request types, 5-38 date, setting, 5-37 IMS Simulated Date Time Settings screen, 5-33 line commands, 5-35 PF keys, 5-38 primary commands, 5-33 screen fields, 5-36 status codes, 5-36 IMS message level support, 3-21 IMS Message Level Support messages, A-2 IMS transaction IDs, 5-32 Imsg field, jobclass support, 5-21 INACTIVATE primary command, IMS, 5-34 Ind field, Advance Request Settings screen, CICS transaction support, 5-63 Ind field, Advance Request Settings screen, IMS message level support, 5-41 Ind field, Simulated Date Time Settings screen, CICS offset format, 5-62 Ind field, Simulated Date Time Settings screen, jobclass offset format, 5-24, 5-39 Ind field, Simulated Date Time Settings screen, offset format, 5-15 installation overview, 1-1 internal diagnostics, B-1 allocating trace dataset, B-1 capturing diagnostic trace data, B-2 proc and parms, B-1 introduction, vii audience, vii customer support, xi notation rules, viii related publications, ix using this manual, vii inventory, creating, 5-12 INVL, A-1 IOPCB and MVS/HLL fields, IMS, 5-37 ISPF interface, 5-3 date, setting, 5-9 Days offset, setting, 5-15 Hrs offset, setting, 5-15 Ind value, setting, 5-15 inventory, 5-12 invoking, 5-3 invoking from TSO, 5-3 jobs, naming, 5-8 line commands, 5-5, 5-15 Mins offset, setting, 5-15 PF keys, 5-9 primary commands, 5-10 procedures, naming, 5-8 programs, naming, 5-8 screen fields, 5-6, 5-16 Simulated Date Time Settings screen, 5-4 status codes, 5-6 steps, naming, 5-8 I-4 Xpediter/Xchange Installation and User Guide subsystem identification, 5-3 time, setting, 5-9 ISPF interface in offset format screen fields, 5-14 ISPMLIB, 3-12 ISPMLIB file, G-1 ISPPLIB, 3-12 ISPPLIB file, G-1 J JACT, A-1 JCL examples allocating save/restore dataset, 3-15 allocating Xchange journal, 3-13 batch execution, 4-1 CICS transaction activity report, 6-7 simulation activity report, 6-7 JCLUTILI JCL, G-1 JNFD, A-1 job stream, G-1 JOBCLASS command, 5-10 Jobclass field, jobclass support, 5-21 jobclass in offset format screen fields, 5-23 jobclass offset format Days offset, setting, 5-24, 5-39 Hrs offset, setting, 5-24, 5-39 Ind value, setting, 5-24, 5-39 Mins offset, setting, 5-24, 5-39 jobclass support, 5-19 screen fields, 5-21 status codes, 5-21 jobclass support with offset, 5-22 Jobname field, Simulated Date Time Settings screen, 58 Jobno field, Simulated Date Time Settings screen, 5-9 JOBOFF command, 5-10 jobs, deleting a different user ID, 3-30 journal, G-1 JOURNAL command, 5-11 journal exit, 3-30, G-2 journal extract, G-2 journal record, program ID, 3-30 journal, Xchange, 6-1 assembling datasets, 3-13 closing, 6-1 dump of, 6-9 extract record layout, 6-7 online, 6-2 opening, 6-1 operator commands, 6-1 printed, 6-5 simulation activity report, 6-5 swapping, 6-1 transaction activity report, 6-6 JWTIM parameter, 3-6 L label, installation DVD, 1-4 language support, 1-1 LE with Xchange CICS region support, 3-19, 5-51 LE with Xchange DB2 support, 3-20 LE/CICS Dependencies Cross Product Dependencies, 3-16 LEGAL command, 5-11 legal notice, displaying, 5-11 LIBDEF, updating, 3-30 libraries created during SMP/E installation, 1-5 libraries, authorizing, 1-8 license management product DVD, 1-4 limits for dates set, 5-9, 5-21, 5-37, 5-60 line commands, Advance Request Settings screen, 5-15 line commands, CICS, 5-58 line commands, IMS, 5-35 line commands, jobclass, 5-20 line commands, Simulated Date Time Settings screen, 5-5 LINKAGE=SVC, 1-1 LINKAGE=SYS, 1-1 linking test programs, 3-31 LIST primary command, CICS, 5-56 LMINPARM sample dataset, 1-10 load library, 3-15 LOCATE command, 5-11 locating, 5-11 LOGCOPY parameter, 3-9–3-10 LOGDDN parameter, 3-9–3-10 LOGDSN parameter, 3-9–3-10 LOGTYPE parameter, 3-9–3-10 M MAX primary command, CICS, 5-56 maximum year set, 5-9, 5-21, 5-37, 5-60 message area, IMS, 5-37 Message Level Offset Support, 5-38 Message Level Support, 5-32 message level support, 3-21 messages, A-1 abend codes, A-22 IMS Message Level Support, A-2 in Owner field, A-1 MVS console, A-7 Owner field messages, A-1 XGIM, A-2 messages, CICS, 5-56 midnight rollover, 3-18 Mins field, Advance Request Settings screen, IMS message level support, 5-40 Mins field, Simulated Date Time Settings screen, CICS offset format, 5-62 Mins field, Simulated Date Time Settings screen, jobclass offset format, 5-24, 5-39 Mins field, Simulated Date Time Settings screen, offset format, 5-15 MODIFY command, G-2 MSG primary command, CICS, 5-56 multiple subsystems, 5-3 MVS console messages, A-7 MVS system commands, 1-6 N Natural support, 3-25 I-5 NAUT, A-1 NFND, A-1 NODDFAC parameter, 3-7 notation rules, viii NUM options, 3-1 NUMAMB parameter, 3-1, 3-7, G-2 NUMATB parameter, 3-1, 3-7, G-2 NUMJRE parameter, 3-1, 3-7, G-2 NUMORE parameter, 3-1, 3-7, G-2 NUMURE parameter, 3-1, 3-7, G-2 NUMXRE parameter, 3-1, 3-7, G-2 O OFFSET command, CICS transaction support, 5-56 OFFSET command, IMS, 5-34 OFFSET command, ISPF, 5-11 online help, 5-4, G-2 online journal facility, 6-2 OPEN operator command, 6-1 opening the journal, 6-1 operator commands, 4-4, 6-2 operator commands, specifying, 3-30 overview, 1-1 environment, 1-1 language support, 1-1 Owner field messages, A-1 Owner field, IMS, 5-36 Owner field, Simulated Date Time Settings screen, 5-8, 5-59 P P line command, CICS, 5-58 parameters, specifying, 3-2 PARMLIB, 1-4, 1-9 PARSELIB parameter, 3-3 pattern job requests, 5-4 pattern owners, displaying, 5-11 pattern requests, deleting a different user ID, 3-30 PDF documentation, ix permanent-time requests, CICS, 5-58 PF keys, CICS transaction support, 5-60 PF keys, IMS, 5-38 PF keys, jobclass support, 5-22 PF keys, Simulated Date Time Settings screen, 5-9 PL/I support, 1-1 PLT initialization, 3-17 PLT shutdown, 3-18 PNFD, A-1 PREFIX command, 5-11, 5-57, G-2 PREFIX primary command, IMS, 5-34 preinstallation considerations, 1-6 PREVDATE parameter, 3-7, G-2 primary commands, CICS, 5-55 primary commands, IMS, 5-33 primary commands, ISPF, 5-10 primary commands, jobclass, 5-20 printed journal report, 6-5 problem reporting, xi PROCSTEP, G-2 Procstep field, Simulated Date Time Settings screen, 58 product DVD creation date, 1-4 label, 1-4 security, 1-4 product media, 1-5 contents of, 1-5 product overview, 1-1 Program field, IMS, 5-36 Program field, Simulated Date Time Settings screen, 58, 5-59 program ID for journal record, 3-30 program ID search, 3-30 publications, Xchange, ix R R line command, CICS, 5-58 RACF, 3-26, G-2 RACROUTE module, 3-12, G-2 RDO, 3-15 related publications, ix RELEASE primary command, 5-12 CICS, 5-57 RELEASE primary command, IMS, 5-34 RELEASE primary command, ISPF, 5-12 REPLY parameter, 3-7, G-2 report, printed, 6-5 Req ID field, IMS, 5-36 request owners, displaying, 5-57 requests, 5-11, 5-55 requests, deleting a different user ID, 3-30 requests, offset, setting by jobclass, 5-10 requests, setting by jobclass, 5-10 resetting requests, CICS, 5-58 Resource Definition Online, 3-15 Resource Name field, 5-26 RESTREQ parameter, 3-8 REXX XGPRT, 6-9 running time requests, CICS, 5-58 S S field, IMS, 5-36 SAMPLIB files, 3-31 save area chain, 3-30 save/restore dataset, 3-14 SAVINTV parameter, 3-8 SAVMSG parameter, 3-8 scenarios batch facility, 5-31 screen, Simulated Date Time Settings, 5-4 searching for program ID, 3-30 SECDFLT parameter, 3-8, 3-26, G-2 SECPFX, 3-30 SECPFX parameter, 3-8, G-2 security configuring external, 3-26 product DVD, 1-4 SECUSE parameter, 3-8, 3-26, G-2 setting and holding requests, CICS, 5-58 setting offset requests by jobclass, 5-10 setting requests by jobclass, 5-10 Shared Services See Compuware Shared Services shut down, G-2 I-6 Xpediter/Xchange Installation and User Guide SHUTDOWN command, G-2 SHUTDOWN operator command, 4-4 Simulated Date Time Settings Screen invoking from Xpediter/TSO, 5-68 Simulated Date Time Settings screen, CICS, 5-54 Simulated Date Time Settings screen, IMS, 5-33 Simulated Date Time Settings screen, ISPF, 5-4 Simulation Activity Report, G-2 Simulation Activity Report, journal, 6-5 SMP/E for DB2 zap, 3-20 installation and maintenance, 1-5 libraries created during installation, 1-5 overview of, 1-5 softcopy, G-2 software mall, G-2 SSID primary command, ISPF, 5-12 SSVT See Subsystem Vector Table starting and terminating Xchange, 4-1 starting Xchange, 4-1 batch job, 4-1 started task, 4-3 status codes, IMS Simulated Date Time Settings screen, 5-36 status codes, jobclass support, 5-21 status codes, Simulated Date Time Settings screen, 5-6, 5-58 status, Simulated Date Time Settings screen, 5-7, 5-59 STCK, using Xchange with, 5-69 Enhanced STCK Support, 5-70 standard support, 5-69 STCKSYNC support, 3-18 Stepname field, Simulated Date Time Settings screen, 5-8 STOP command, 5-57 stopping Xchange, 4-4 SUBSYS parameter, 3-3, G-2 subsystem ID, G-2 displaying, 5-12 Subsystem Vector Table, 1-8 subsystems, multiple, 5-3 subsystems, specifying, 5-53 support, technical, xi SVC11, G-3 SVCUPDTE macro, 1-8, G-3 swap, G-3 SWAPLOG operator command, 6-2 swapping, 6-2 switched major node, G-3 syntax conventions, viii diagrams, viii SYSPROC, 3-12 system commands, MVS, 1-6 system environment, 1-1 system information, 1-6 T Task No. field, Simulated Date Time Settings screen, 560 TERM parameter, 3-12 Terminal field, Simulated Date Time Settings screen, 559 terminating Xchange, 5-57 from batch facility, 4-5 with operator command, 4-4 terminating Xchange, CICS, 5-55 TERMTYPE parameter, 3-12 test programs, 3-31 TIME macro, 1-1 TOP SECRET, 3-26 TRACE command, G-3 trace function, B-1 allocating trace dataset, B-1 capturing diagnostic trace data, B-2 proc and parms, B-1 transaction exclusions, 3-17 transaction IDs, 5-52 transaction offset support, CICS, 5-60 transaction support, CICS, 3-15, 5-52 transaction XGAJ, 5-51 TransID field, Simulated Date Time Settings screen, 559 TSO CLISTs, updating, 3-12 U UACC, 3-29 UADD, A-2 UNAB, A-2 updating TSO CLISTs, 3-12 upgrade considerations, 1-8 USEHASP parameter, 3-9 user access, specifying, 3-29 user ID access, specifying, 3-29 UserId field, 5-26 UserID field, Simulated Date Time Settings screen, 559 using Xchange, 5-1 batch facility, 5-27 CICS region support, 5-51 CICS transaction offfset support, 5-60 CICS transaction support, 5-52 IMS Message Level Offset Support, 5-38 IMS Message Level Support, 5-32 ISPF interface, 5-3 jobclass support, 5-19 jobclass support with offset, 5-22 STCK, using with, 5-69 with CICS, 5-51 with DDF, 5-24 Xpediter/TSO interface, 5-67 USRRACRT module, 3-12, G-3 V viewing journal dataset name, 5-11 VSAM, G-3 W Working Storage Section, G-3 I-7 X Xchange assembling datasets, 3-13 batch facility, 5-27 CICS interface, 5-51 CICS region support, 5-51 midnight rollover, 3-18 with LE, 3-19, 5-51 CICS transaction offset support, 5-60 CICS transaction support, 5-52 DB2 support with LE, 3-20 external security, configuring, 3-26 IMS Message Level Offset Support, 5-38 IMS Message Level Support, 5-32 invoking, 5-3 ISPF interface, 5-3 jobclass support, 5-19 jobclass support with offset, 5-22 journal, 6-1, 6-5 messages, A-1 operator commands, 4-4, 6-2 overview, 1-1 parameters, specifying, 3-2 Simulated Date Time Settings screen, ISPF, 5-4 starting, 4-1 starting and terminating, 4-1 STCK, using with, 5-69 terminating, 4-4 using with DDF, 5-24 Xpediter/TSO interface, 5-67 XCHANGE command, G-3 XCHANGE command, from Xpediter/TSO, 5-68 Xchange date/time offset requests entering directly from Xpediter/TSO, 5-68 Xchange requests entering directly from Xpediter/TSO, 5-68 Xchange Subsystem ID field, IMS, 5-36 XCLJOB parameter, 3-11 XCLJTYPE parameter, 3-11 XCLPROG parameter, 3-10 XCLPTYPE parameter, 3-10 XCLUSER parameter, 3-11 XCLUTYPE parameter, 3-11 XGADMIN, 3-30 XGAJ transaction, 5-51 XGBASM, 3-31 XGBASMLE, 3-31 XGBCHDB2, 3-31 XGBCOBLE, 3-31 XGBJRPRT program, 6-9, G-3 XGBPLI, 3-31 XGBPLILE, 3-31 XGCCOBLE, 3-31 XGCDB2, 3-31 XGCPLI, 3-31 XGCPLILE, 3-31 XGDEMASM, 3-31 XGDEMCBL, 3-31 XGFNDIT, 3-12 XGFNDMOD utility, 7-1 report, 7-2 running, 7-1 XGIM messages, A-2 XGIPLG01 program, 6-9, G-3 XGIPXTRT program, 6-7, G-3 XGJEXIT1 parameter, 3-9 XGJEXIT1 user exit, G-3 XGLINK02, 3-31 XGLINKTD, 3-31 XGPRT program, 6-9, G-3 XGTD, 5-53 XGTM, 5-52 XGTMAIN, 3-17–3-18, 5-52 XGTS, 5-52 XGXCTLTD, 3-31 XPCTUPDT CLIST, G-3 Xpediter, G-3 Xpediter/TSO interface, 5-67 Xpediter/Xchange CICS Transaction Activity report, 6-6 Xpediter/Xchange Simulation Activity Report, 6-5 XPGMDIR parameter, 3-9 Y year specified, limit for, 5-9, 5-21, 5-37, 5-60 YYYY/MM/DD field, IMS, 5-37 YYYY/MM/DD field, jobclass support, 5-21 YYYY/MM/DD field, Simulated Date Time Settings screen, 5-9, 5-60 I-8 Xpediter/Xchange Installation and User Guide