Configuring the IMS Transaction Isolation Service API for Debug Profile Service

IMS Transaction Isolation Service API is a RESTful API supported by Debug Profile Service.

Before you begin

• Ensure that z/OS® Explorer 3.2.0.13 or later and Debug Profile Service are installed and configured, and IMS Transaction Isolation Service API is installed. For more information, see Adding support for Debug Profile Service.
• IMS Transaction Isolation Service API has a dependency with IMS Transaction Isolation Facility, which must be enabled to operate the API. Both the IMS Transaction Isolation Service API and IMS Transaction Isolation Facility use the same in-memory IMS Transaction Isolation table to perform IMS Isolation functions. Ensure that the IMS Transaction Isolation Facility in enabled:
  • Scenario F: Enabling the Transaction Isolation Facility
  • Sample customization of the IMS Transaction Isolation Facility
  Notes:

  • The IMS Transaction Isolation Service API works by calling the EQANIPSB program to support IMS Isolation functions, and to interface with IMS subsystem. Both IMS Transaction Isolation Service API and EQANIPSB programs must be able to locate the same SEQAMOD driver in order to operate successfully.
    The installation provides a sample job called EQAW.SEQASAMP(EQAPROF) that sets SEQAMOD in the STEPLIB of the job. Alternatively, SEQAMOD can be added in the system linked-list. Both options enable IMS Transaction Isolation Service API to locate the current EQANIPSB program. However, SEQAMOD must also be set in the imso_dd_eqatipsb property defined in eqaprof.env. This enables EQANIPSB to locate the current programs that interface with IMS. A discrepancy between SEQAMODs can cause internal errors.
  • A private message processing region (MPR) may transition into a Terminated state if the in-memory IMS Transaction Isolation table expected the private region to be Started, but it discovered that it is Stopped. This can occur if the private MPR is stopped or stops unexpectedly by a process external from IMS Isolation, which causes the in-memory IMS Transaction Isolation table to be out-of-sync with the actual state of the private region. A stop request is required to re-sync the in-memory IMS Transaction Isolation table.
  • The debug profile EQAUOPTS dataset name given to an IMS Isolation Private Region comes from the parameter default_dsname defined in the eqaprof.env, the Debug Profile Service deployment configuration file (default location: /etc/debug/).

1. Ensure that the protected user ID (STCEQA) that starts Debug Profile Service (EQAPROF) has READ authority to BPX.DAEMON.HFSCTL:

   RDEFINE FACILITY BPX.DAEMON.HFSCTL UACC(NONE)
   PERMIT BPX.DAEMON.HFSCTL CLASS(FACILITY) ID(STCEQA) ACCESS(READ)
   SETROPTS RACLIST(FACILITY) REFRESH
   

2. Customize the following attributes in the Debug Profile Service configuration file eqaprof.env:
   • imsiso_dd_eqatipsb
   • imsiso_dd_syslib
   • imsiso_dd_sysproc
   • imsiso_dd_jcllib
3. Replace the z/OS Debugger data set names, SEQAMOD, SEQAEXEC, and SEQATLIB with the installed z/OS Debugger data set names, and replace IMS.SDFSRESL with the IMS RESLIB load library for your IMS subsystem.
4. Verify that the default_dsname property in the eqaprof.env configuration file uses the same dataset profile naming pattern as the DLAYDBGDSN property defined in the EQAOPTS load module.