The number of Gateways attached to the Gateway address space is specified in the Gateway startup JCL. You can use one of the following methods to add additional Gateways:
Distributed access between TIBCO Object Service Broker and CA‑IDMS is permitted subject to requirements of all distributed access. Refer to
TIBCO Object Service Broker Application Administion and
TIBCO Object Service Broker for z/OS Installing and Operating for more information on distributed access.
You can display the status of all instances of TIBCO Service Gateway for IDMS/DB in an address space using the RESOURCE MANAGEMENT option from the Administration menu. The following screen shows an example of the type of information displayed for resource type IDMS.
The Rule Debugger helps you identify and fix errors within your application. You can also make and test certain ad hoc changes to your rules. The debugger stops the rules execution at events specified from within the Debug screen.
For CA‑IDMS Release 12.0 and greater, you can determine the DML statements being sent to CA‑IDMS by your TIBCO Object Service Broker rules by adding a SYSLIST DD NAME for the output in the Gateway startup JCL, and adding the line DMLTRACE=ON to the SYSIDMS SYSIN member specified in the Gateway startup JCL. When you use this parameter, DML statements for all IDMS/DB table accesses are included in the trace. To view only DML statements created by your rules, you require a dedicated Gateway. You can do this by using the SERVERID parameter. To change the server ID of an IDM table definition to an alternate dedicated server ID, invoke the
CHANGE_SERVERID tool from the workbench as follows:
Refer to How to Contact TIBCO Support for information about reporting problems with Service Gateway for IDMS/DB to TIBCO Support. Have the following information available when reporting a problem: