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


Chapter 2 Configuring the Accesses to Adabas Data : Startup Prerequisites

Startup Prerequisites
Before you can start the server, you must do either of the following:
If the Data Object Broker is on z/OS and Dynamic Resource Creation is not permitted (Data Object Broker Parameter DYNAMICRESOURCE = N), the Gateway must be identified to the Data Object Broker in a permanent resource. To do this, define Gateway resources to the Data Object Broker’s resource management repository file.
If the Data Object Broker is on z/OS and Dynamic Resource Creation is permitted (Data Object Broker Parameter DYNAMICRESOURCE = Y) and there is no matching permanent resource a dynamic resource entry matching, the Gateways requirements will be created when the Gateway connects to the Data Object Broker. If there is a permanent entry for the Gateway it must match the requirements for the Gateway. It is recommended that all permanent entries for File, ADA and DAT Gateways are deleted from the repository when dynamic resource creation is permitted.
If the Data Object Broker is on Windows or Solaris, set up National Language Support, if necessary. Refer to TIBCO Object Service Broker National Language Support for setup and configuration information.
Default Resource Settings (z/OS only)
The table below lists the base defaults you must specify in the Resource Detail (PF2) and the Resource Schedule (PF10) screens 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 ADA and a GROUP corresponding to the server ID of your Adabas server.
 
Resource Schedule
If the FSLEVEL startup parameter equals 1, the COMMIT LEVEL value on the Resource Detail screen must also be set to 1.
Refer to Supplying the Startup Parameters, for the description of the FSLEVEL parameter.
See Also
TIBCO Object Service Broker for z/OS Installing and Operating for more information on defining and managing TIBCO Object Service Broker resources using the Resource Management option, and for information about the Administration menu.
Customization of the Startup Batch JCL
Before starting the server, use the OSEMOD macro to customize the JCL for your installation. Sample batch JCL is shipped as member S6BSJCL in the JCLSAMP data set. Customize it as required.
By default, TIBCO Object Service Broker loads the Adabas interface module in the HRNEXTR DD statement. This can be changed to load from the standard load library search path STEPLIB, JOBLIB, LINKLIB, and LPA (Link Pack Area) using the @CONFIGURESERVER tool. If the Adabas load library is part of the STEPLIB, both the Adabas and TIBCO Object Service Broker load libraries should be authorized.
Refer to Communications Requirements for more information about the OSEMOD macro. Refer to Configuration Parameters for information about @CONFIGURESERVER.

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