Installing and configuring the IMS transaction isolation extension for the ADFz Common Components server

About this task

Note: Debug Profile Service with IMS Isolation support is available since z/OS® Debugger 16.0.0. This task is required only when your Eclipse IDE users cannot access IMS Isolation with Debug Profile Service to create IMS Isolation Debug Profiles. The IMS transaction isolation extension is only available in IBM® Developer for z/OS Enterprise Edition.
You must create a configuration file for the IMS transaction isolation extensions for the ADFz Common Components server, and then specify the location of the configuration file to the server. You can find step-by-step procedures to run the ADFz Common Components server in the IBM Application Delivery Foundation for z/OS Common Components Customization Guide and User Guide.

Procedure

To configure the IMS transaction isolation extension for the ADFz Common Components server, complete the following steps:

  1. Create a sequential MVS™ data set (FB, LRECL 80) that contains the following records:
    1. Replace the z/OS Debugger data set names, SEQAMOD, SEQAEXEC, and SEQATLIB with the installed z/OS Debugger data set names.
    2. Replace the ISPF data set name SISPLOAD with the installed ISPF data set name.
    3. Replace the IMS data set name SDFSRESL with the installed IMS data set name.
    Note: Do not change other statements.
    * IMS transaction isolation view
    CONFIG=II
    SPAWN_PROGRAM=EQAIIINT
    SPAWN_STEPLIB=EQAW.SEQAMOD:
    CEE.SCEERUN:
    ISP.SISPLOAD:
    IMS.SDFSRESL
    SPAWN_PARMS_SECTION
    SPAWN_DD=EQATIPSB=EQAW.SEQAMOD:               
    IMS.SDFSRESL:                                     
    CEE.SCEERUN                                             
    SPAWN_DD=SYSLIB=SYS1.MACLIB                                  
    SPAWN_DD=SYSPROC=EQAW.SEQAEXEC                         
    SPAWN_DD=JCLLIB=EQAW.SEQATLIB(EQAZPROC)   
  2. Modify the ADFz Common Components server started proc IPVSRV1.
    1. Add the configuration data set to the CONFIG DD statement concatenation.
    2. Set the region size parameter to 200M or 0M. For example, //RUN EXEC PGM=IPVSRV,REGION=200M.
    3. Stop and restart the ADFz Common Components server.
  3. Ensure the user ID (ownerID) that owns and starts the proc IPVSRV1 has the following capabilities:
    • An OMVS segment. You can use the following command to create the segment:
       altuser ownerID omvs(home(/u/ownerID) program(/bin/sh))
    • Read access to BPX.SERVER. You can use the following command to add permission:
      PE BPX.SERVER CL(FACILITY) ID(ownerID) ACC(READ)
  4. Inform your users of remote IMS Application with Isolation launch configuration of the following information:
    • They need to choose the same encoding scheme as the character encoding scheme of your host system when they add a host connection to IMS transaction isolation extension.