IMS Dependent Regions workspace

The IMS Dependent Regions workspace displays status information for dependent regions, including the status of the region, transaction and PSB name if applicable, external subsystem system if applicable, region occupancy percentage, and locks held count.

For IMS V10 and later versions, the number of DL/I databases, DL/I message, DL/I system service, and external subsystem calls and transaction elapsed time for the currently running application (Unit of Recovery) are provided. In addition, the workspace provides OTMA information, if applicable, including the TMember name, TPipe name, commit mode, synchronization level, and TPipe status. This workspace consists of two views:
  • Dependent Region Counters bar chart
  • IMS Dependent Regions table view
The IMS Dependent Regions table view supports links to view the selected PSB, selected transaction, and DLI call statistics for the selected region. For the TMember name in a selected Dependent Region row, the IMS Dependent Regions table view supports a link to the IMS OTMA TMember Status workspace. For the TMember name and TPipe name in a selected Dependent Region row, the IMS Dependent Regions table view supports a link to the IMS OTMA TPipe Status workspace.

In addition, the IMS Dependent Regions table view supports a link to the IMS Dependent Region in Classic workspace, which displays all dependent regions in the Classic interface and a link to the IMS Dependent Region in Classic workspace, which displays the selected dependent region in the Classic interface. The event workspace for the IMS_DepReg_Occupancy_High situation supports a link to the IMS Dependent Region Locking Conflict in Classic workspace which displays lock conflicts for the selected region in the Classic interface and a link to the IMS Console in Classic workspace which displays OCMD or ICMD in the Classic interface configured to stop the current transaction in the selected region.

For OMEGAMON® for IMS and the Realtime Monitor (Classic), an external subsystem status indicates when an application that is running in a dependent region issues an external subsystem request to WebSphere® MQ, and Db2®. The external subsystem status reflects the processing that is occurring within the WebSphere MQ subsystem or Db2 subsystem. Therefore, if an application is waiting on an external subsystem such as WebSphere MQ or Db2, the region status indicates that an external subsystem request is issued. Furthermore, the external subsystem status identifies the process that the subsystem is running. In addition, the external subsystem ID is displayed when the application is processing an external subsystem request.

The dependent region displays include OTMA information. OTMA information includes the TMember name, TPipe name, commit mode, synchronization level, and TPipe status. The OMEGAMON for IMS Dependent Regions workspace provides OTMA information for an application, as applicable. Additionally, this workspace provides a link to the OTMA TMember Status workspace and a link to the OTMA TPipe workspace. The Realtime Monitor (Classic) displays OTMA information for a single region by including a minor command for the region major commands.