DBEC/DBEX: Monitoring and Controlling Remote System Resources with Enhanced Commands

In an MRO environment, requests to display information in read-only mode for MUFs and URTs in a remote CICS system can be issued as follows:

With the DBEC transaction ID
With the DBEX transaction ID
With their substitute IDs

Issuing Requests with DBEC/DBEX

You can issue requests with either transaction ID for the following purposes:

Display the status of MUFs and their processing options and statistics.
Display the status of URTs and their processing options.
Display processing options for database tables defined within the URTs.

In an MRO environment, requests to perform an action on a remote CICS system defined in the CICS Connection table can be issued with the DBEC transaction. The PERFORM commands can be issued from the console to control remote resources. You can issue requests with this transaction to accomplish any of the following tasks:

Initiate or terminate CA Datacom CICS Services for a remote CICS system.
Connect and disconnect MUFs in any attached system.
Open and close URTs in any attached system.
Set or reset when to open specifications for any URTs in any attached system.
Move a new copy of a specified URT into a specified remote system.
Override processing options established by the following DBCSID parameters in any remote MUF definition:
- USERS= (Maximum threads for task processing)
Reset statistics in any remote MUF definition.
Override processing options established by the following DBURSTR parameters in any remote URT definition:
- CBSIO= (Maximum I/O for set processing—CBS commands)
- PRTY= (Request priority)
- TIMEMIN= or TIMESEC= (Maximum wait time for held record)
- TXNUNDO= (Transaction backout)
Override processing options established by the following DBURTBL parameters in any remote URT definition:
- AUTODXC= (Automatic dropping of exclusive control with subsequent read for update commands)
- BYPOPEN= (Bypass opening table)
- SYNONYM= (Table name is duplicated in this or another URT)
- UPDATE= (Table is updatable)

The following considerations are relevant to the available functions used in monitoring and controlling resources in remote MRO regions.

Using SYSID(aaaa) to reference a single remote CICS system requires that the referenced system has installed the CA Datacom CICS Services DBRC transaction required for communication.
Using SYSID(*) to reference all attached CICS systems (as defined in the CICS connections table) requires that all of the attached CICS AOR regions have the DBRC transaction installed so that communication can take place.
Note: The DBRC transaction is defined in the CA Datacom CICS Services CSD definitions.

In both previous cases, if a referenced AOR region does not have the CA Datacom CICS Services DBRC transaction installed, the DBEC/DBEX transaction issued from the TOR region receives the message "DBRC NOT DEFINED IN AOR". The transaction abends with an AZI6 abend code from CICS.

To use DBEC INQ,SYSID(*) in an MRO environment, define the following resources:

For CICS AOR regions without CA Datacom CICS Services
1. Define the DBRC transaction.
2. Define the DCCERPR program.
For CICS AOR regions with CA Datacom CICS Services installed, the necessary definitions for needed transactions and programs should be in place by having installed CA Datacom CICS Services CSD definitions. Specifically they are as follows:
- Define the DBRC transaction.
- Define the DCCERPR and DCCETPR programs.

The following topics provide detailed information about monitoring and controlling remote system resources in an MRO environment using a DBEC or DBEX transaction ID: