Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Milestone 12: Enabling IMS support

If your site is not using—and does not plan to use—change's IMS support, you may skip this milestone and continue with Milestone-13-Enabling-Code-Debug-TSO-interface. This milestone contains tasks for enabling IMS support.

The roles involved are: Xchange Installer.

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.

Warning

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.

Task 12.1: Enable IMS message level support

To enable IMS Message Level Support, perform the following steps:

  1. Define the Xchange Message Level Support programs and their associated transactions to IMS.
    1. 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.
    2. 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 Regions (MPRs) in which they will be running.

    Important

    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 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.
  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.

    Important

    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, see the appropriate IBM IMS/ESA documentation.

  7. Use IDCAMS to create each IMS request data set. 

    All dependent regions that connect to a control region must share the same IMS request data set. That data set cannot be shared by dependent regions connected to any other control region. The JCL for creating and initializing an IMS request data set 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:

    1. In the step that executes DFSRRC00, concatenate the Xchange loadlib to the region’s steplib.

      Important

      If 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 Task 11.1: Apply the Db2 zap, you can use that same zapped CEEPLPKA module in this step. An alternative solution is to remove CEELRRIN from the pre-load list.

    2. Add the following DD statement, replacing customer.ims.file with the data set name you defined in step 7:

      //XGIMSREQ DD DSN=customer.ims.file,DISP=SHR

    3. 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 data set name you defined in step 7:

      //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, or XGPCCU15 for IMS 15.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 step 12. Otherwise, go to step 13.

  12. Review the JCL to perform the SMP/E install of the Xchange interface.

    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.

    We recommend 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.

    1. Before submitting the job, edit the appropriate member to make any necessary changes including jobcard, SMPE PROC, and ZONE names.
    2. 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.
    3. 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.
    4. Submit XGLNKPCC or XGLNKPC1 for IMS 8.1 and above to link module XGIMSTFR into DFSPCC20.
      This job should complete with RC0.
    5. Go to step 15.

  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 or
    • –XGPCC20F for IMS 15.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, XGPCC20E, or XGPCC20F 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:
    1. Use IEBUPDTE to create a temporary copy, SYSUT2, of IMS module DFSPCC20.
      SYSUT1 must point to the data set containing the current source code for DFSPCC20.
    2. Assemble the updated temporary copy of DFSPCC20 created in previous step.
    3. Link edit the new DFSPCC20 object module created in previous step.
      We recommend 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 Milestone-8-Configuring-Xchange-external-security.
    The user who submits the job that starts the MPP must have update access to the Xchange pseudo-data set name.

  16. Recycle the IMS system and execute the necessary /MODIFY PREPARE and /MODIFY COMMIT commands to activate your new control blocks.

    Important

    Sites with IMS can now use the Xchange demonstration programs listed in the table at IMS-message-level-support-test-programs.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*