![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The operating system of the Service Gateway for Files determines the communications prerequisites, as follows:Before a Service Gateway for Files running on z/OS can communicate with a remote Data Object Broker, the name and IP port number of the Data Object Broker must be added to the RELAYCFG member in the CNTL data set for Service Gateway for Files.TIBCO Object Service Broker for z/OS Installing and Operating for details about the RELAYCFG member.Use ISPF EDIT to modify the contents of the sample TCP/IP Relay configuration data set, identified by the S6BRELAY DD statement in your Service Gateway for Files JCL. You need only modify the last sample entry as follows:
node name="..." tcpip host="..." Replace with either the IP address or symbolic domain name of your remote Data Object Broker. A Resource Management entry is automatically created for the Service Gateway for Files when these conditions are satisfied:
• The Data Object Broker Parameter DYNAMICRESOURCE = Y
• There is no permanent resource in the Resource Management Facility that matches the requirements for the Service Gateway for FilesFor best results, delete all permanent entries for Service Gateway for Files from the repository when dynamic resource creation is enabled.If the Data Object Broker is on z/OS and Dynamic Resource Creation is not enabled (Data Object Broker Parameter DYNAMICRESOURCE = N) the Service Gateway for Files must be defined through the Resource Management facility available from the Administration menu. Resource Management is option 3 on the Administration menu. This option brings you to the Resource Type List, on which you must supply a TYPE of API and a GROUP corresponding to the server ID of your Service Gateway for Files. You must also have a schedule defined for the resource (a default schedule is provided with TIBCO Object Service Broker).On the Resource Type Menu, PF5 allows you to configure a new Service Gateway for Files. PF2 can be used to view the configuration of an existing Service Gateway for Files. Once you are viewing such a configuration, PF11 allows you to edit it.The configuration is substantially the same as for a Peer Server; the following values can be used. Other options can also be set on this menu.
API name name is the server ID you wish to use for Service Gateway for Files. This is the same name as in session.prm. INTERMEDIATE ROLLBACK Service Gateway for Files provides update support for table types (EXP and VSM) that are always updated immediately rather than via commit processing. As a consequence, it must operate at Commit Level 0.TIBCO Object Service Broker for z/OS Installing and Operating for details about the Resource Management facility.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |