Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 Operational Requirements for Adabas Access : Understanding Other Operational Procedures

Understanding Other Operational Procedures
This section describes other operational procedures: distribution access, status display, debugging, and problem reporting.
Distributed Access
Distributed access between TIBCO Object Service Broker and Adabas is permitted and is subject to the requirements of all distributed access. Refer to TIBCO Object Service Broker Application Administration and TIBCO Object Service Broker for z/OS Installing and Operating for more information on distributed access.
Refer to Connection to a Windows or Solaris Data Object Broker for information about connecting to a Data Object Broker on Open Systems.
Status Display
Use the RESOURCE MANAGEMENT option from the Administration menu to display the status of the instances of the server. The sample screen below shows an example of the type of information displayed for resource type ADA.

 
S6BADM33 HTSTSRV RESOURCE DETAIL FOR ADA ADASRV 2007JAN02 16:40:52
INTERMEDIATE ROLLBK N EARLY RELEASE Y LAST USER REUSE N COMMIT LEVEL 0
RETRY INTERVAL 0 TP NAME USER ID PREFIX FAILURES 0
NODE MMMSYSTEMA01 INDOUBTS N DELETE

CONNECTIONS IN-USE TRX MESSAGE
CUR MAX LMT CUR MAX COUNT COUNT
ONLINE 0 0 0 0 0 0 0
COMMON 0 0 25 0 0 0 0

SCHEDULE NAME IMSIMSDRASV
APPLICABLE DAYS EXCEPTION START ONLINE CONNECTIONS
MON TUE WED THR FRI SAT SUN DATE TIME ONLY MAX
Y Y Y Y Y Y 00:00 N 25






ENTER-PATHS PF2-TYPE PF4-GROUP PF5-PEER PF9-START PF10-SCHEDULES PF11-UPDATE
THERE ARE NO ACTIVE PATHS TO BE DISPLAYED, REQUEST IGNORED

 
Debugging
Use the TIBCO Object Service Broker Rule Debugger to identify and fix errors in your TIBCO Object Service Broker application. You can also make and test changes to your rules. The Debugger stops the rule execution at events that you specified from within the Debug screen.
Use the @CONFIGURESERVER tool to trace all Adabas calls that are made to the Adabas nucleus and the control blocks.
Set the TRACE and DUMP configuration parameters to Y, and the LOGMEDIA and DEBUGLEVEL configuration parameters as required to capture the log information necessary for diagnosing the problem. Setting TRACE and DUMP to Y logs all accesses and dumps the Adabas control blocks before and after the call to ADALNK. Setting the DEBUGLEVEL value to 1, 2, or 3 enables the logging of this data, and determines at what point the Adabas control blocks are dumped:
The LOGMEDIA configuration parameter determines where the output from the trace goes:
The default print destination for your TIBCO Object Service Broker user ID. Set the desired print file with the UP user profile option on the workbench.
The @SERVERLOG table. The table is parameterized by the server type (ADA for Adabas), the server ID specified by the SERVERID startup parameter, and the thread ID used by the transaction, specified by the IDPREFIX startup parameter.
For more information on the @CONFIGURESERVER tool, refer to Configuration Parameters.
For more information on the TRACE, DUMP, DEBUGLEVEL, and LOGMEDIA parameters, refer to Available Configuration Parameters.
For more information on the SERVERID and IDPREFIX parameters, refer to Supplying the Startup Parameters.
See Also
TIBCO Object Service Broker for z/OS Installing and Operating for more information on the RESOURCE MANAGEMENT option of the Administration menu.
TIBCO Object Service Broker Programming in Rules for more information on using the Rule Debugger.
TIBCO Object Service Broker Parameters for more information about parameters.
Problem Reporting
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
Copyright © TIBCO Software Inc. All Rights Reserved