Distributed access between TIBCO Object Service Broker and IMS 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.
Use the RESOURCE MANAGEMENT option from the Administration menu to display the status of the Gateway. The example below shows the type of information displayed for SERVER TYPE=IMS.
A typical use for IMSUSRXT is to alter the SSA used by the Gateway. For example, you can change the command code from
*D to
*L such that you can retrieve the last segment and read the database backwards.
You can use the TIBCO Object Service Broker Rule Debugger to identify and fix errors in your applications. You can also make and test certain ad hoc changes to your rules. The Debugger stops the running of the rule at events you specified in the Debug screen.
For the Gateway to determine the SSAs built and sent, include the TRACE parameter in the IMSSRV00 SYSIN file. This requires a dedicated Gateway since the SSAs for all IMS accesses are included in the trace. This can be accomplished using the SERVERID parameter. To change the server ID of an IMS table definition to an alternate dedicated server ID, execute the
CHANGE_SERVERID tool as follows:
In addition to the trace output, you can also use the DEBUG gateway parameter to echo all requests received by the Gateway to the JES job log for batch jobs or to the console for started tasks. For more information refer to
Supplying Gateway Startup Parameters.
If you are running an instance of the Gateway using the DL/I or DBB interface, you can use the DL/I Trace Facility to assist in debugging problems. To trace DL/I calls created by the Gateway, make the following modifications:
To view only the DL/I statements created by your rules, you require a dedicated Gateway. This can be accomplished using the SERVERID parameter. To change the server ID of an IMS table definition to an alternate dedicated server ID, execute the
CHANGE_SERVERID tool as follows:
In addition to the DL/I Trace Facility, you can also use the DEBUG gateway parameter to echo all requests received by the Gateway to the JES job log for batch jobs, or to the console for started tasks. For more information, refer to the DEBUG parameter in
Supplying Gateway Startup Parameters.
Refer to How to Contact TIBCO Support to report problems to TIBCO Support. Have the following information available:
TIBCO Object Service Broker Application Administion and
TIBCO Object Service Broker for z/OS Installing and Operating for more information on distributed access.
TIBCO Object Service Broker Programming in Rules for more information on debugging rules and applications.