![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Distributed access between TIBCO Object Service Broker and CA Datacom is permitted subject to requirements of all distributed access. This illustration shows a sample TIBCO Object Service Broker CA Datacom distributed-data scenario:Use the RESOURCE MANAGEMENT option from the Administration menu (S6BTLADM utility) (z/OS only) to display the status of your server. The sample screen below shows an example of the type of information displayed for resource type DAT.
Using the TIBCO Object Service Broker Rule Debugger you can 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 that you specify in the Debug screen.To turn on the CBS Trace in CA Datacom, include the X option in the DEBUGPARMS field in the @SERVERDEBUG(DAT) table. SERVERID is the primary key value for this table. This records runtime information in the CA Datacom PXX.To view only trace information associated with your rules, you require a dedicated server. This can be accomplished using the SERVERID parameter. To change the server ID of a DAT table definition to an alternate dedicated server ID, execute the CHANGE_SERVERID tool as follows:You can view the information included in the PXX Trace using the standard CA Datacom PXX reporting utility.
• Refer to TIBCO Object Service Broker Parameters for information about parameters.
• TIBCO Object Service Broker Application Administration and TIBCO Object Service Broker for z/OS Installing and Operating for more information on distributed access, and on the RESOURCE MANAGEMENT option of the Administration menu.
• TIBCO Object Service Broker Programming in Rules for more information on the Rule Debugger.To show CA Datacom errors as they are returned from CA Datacom or problems processing the requests in the server, add one or more of the following values in the field DEBUGPARMS in the @SERVERDEBUG(DAT) table. SERVERID is the primary key value for this table.
Prints resource usage statistics at the end of the transaction (for example, CPU time or table access calls). Logs every CA Datacom return code in the trace. Use this value only for support activities. Dumps CA Datacom specific work areas such as area, work area, request qualification area, element list, and user information when an unexpected CA Datacom return code is encountered. You should always specify this value. Contact your CA Datacom database administrator for interpretation. Logs non-CA Datacom errors when the server cannot convert data. You should always specify this value. Causes the server to close all its tables at each synchronization point, while the server continues to run. Use of this option can cause significant server wait time as CA Datacom opens and closes the files. If the files are still in use by other users, the wait time is minimal. Records trace information to SYSOUT. If not specified, the trace information is recorded in the @DATTRACE TIBCO Object Service Broker table. Turns on CBS trace in CA Datacom. Reports can then be produced analyzing CA Datacom access path usage. The first three characters of the User Information Block are set to $$$. This causes additional recording of CBS runtime information in the CA Datacom PXX.Refer to How to Contact TIBCO Support for information about reporting problems with the server to TIBCO Support.Have the following information available when reporting server related problems to TIBCO Support:
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |