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


Chapter 2 Operating Service Gateway for IDMS/DB : Other Operational Procedures

Other Operational Procedures
Adding the Gateway Tasks
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:
Using Distributed Data with TIBCO Service Gateway for IDMS/DB
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.
This illustration shows a sample TIBCO Object Service Broker IDMS/DB distributed-data scenario:
Displaying the Status of the Instances of TIBCO Service Gateway for IDMS/DB
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.

 
S6BADM33 HTSTSRV RESOURCE DETAIL FOR IDMS IDMSSRV 2000JAN02 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 Rules and Applications
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:
CHANGE_SERVERID(table_name,old_serverid,new_serverid)
Reporting Problems
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:
CA‑IDMS Release and Maintenance Level you are running
CA‑IDMS schema and subschema definition (section containing CA‑IDMS records selected in your IDM tables)
Bachman diagram for CA‑IDMS records accessed by your IDM tables
Also, have a listing available of all TIBCO Object Service Broker IDMS/DB control tables:
See Also
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 for z/OS Installing and Operating for more information on the RESOURCE MANAGEMENT option
TIBCO Object Service Broker Programming in Rules for more information on debugging rules and applications

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