Copyright © Cloud Software Group, Inc. All Rights Reserved

Specifying the Startup Parameters

You can specify parameters on the EXEC statement of the startup JCL, in a data set, or both.

Available Parameters

The available parameters are as follows:

 

IDPREFIX	Required. The server appends three decimal digits to this prefix and uses the result, which uniquely identifies each instance of the server, to log in to TIBCO Object Service Broker. An IDPREFIX can have up to, or will be truncated down to, five characters.
SERVERID	Required. This parameter identifies a pool of server instances with common characteristics. If you run multiple address spaces to start up servers with the same SERVERID, ensure that the FSLEVEL and TRXDB parameters are assigned the same values in each of these jobs. A SERVERID can have up to eight characters and you must specify one when you are defining a DAT table. The SERVERID specified in a DAT table definition allocates a suitable server instance to your transaction when accessing the CA Datacom data with this table definition. The SERVERID parameter can be overridden at runtime. Refer to Dynamically Changing the Parameters for more information.
SERVERS	Required. The number of server instances to be attached to the server address space at startup. This number can be from one to a value less than or equal to the value set in the Maximum Connection Count field in your network configuration. The default value is 1.
SERVERTYPE	Required. The type of server to be initialized. For CA Datacom the value is DAT and it must be specified.
TDS	Required. The Communications Identifier of the Data Object Broker for the server to attach to.
FSLEVEL (FSL)	This parameter specifies the level of Fail Safe processing. The default value is 0. The valid values are as follows: 1 – Activate Fail Safe processing. The server informs the Data Object Broker that it can support Fail Safe level‑1 processing. If the server is to attach to a z/OS Data Object Broker, the Data Object Broker’s connection attribute setting “commit level” must be set to 1. If not, the server connection is rejected. Refer to Implementing Fail Safe Processing for more information. You must specify the TRXDB parameter. 0 – Deactivate Fail Safe processing. The server informs the Data Object Broker that it does not support Fail Safe level‑1 processing. If the server is to attach to a z/OS Data Object Broker, the Data Object Broker’s connection attribute setting “commit level” must be set to 0. If not, the server connection is rejected. Refer to Implementing Fail Safe Processing for more information.
POOLSIZE	This parameter sets the amount of space (in kilobytes) to hold DAT table definitions in the server. This parameter can be 4 KB through16384 KB. The default value is 256 KB. An estimate of the number of DAT tables that can be accessed in a single transaction is POOLSIZE divided by CTABLESIZE. Refer to Estimating the CTABLESIZE Parameter for more information.
SECLEVEL	The valid values are 0 (default) and 1. If SECLEVEL=0 or 1, the server passes to CA Datacom the caller’s TIBCO Object Service Broker user ID in positions 4 through 11 of the User Information Block (UIB). If SECLEVEL=1, the server “impersonates” a CA Datacom client, as follows: 1. The TIBCO Object Service Broker caller passes to the server the credentials (user ID and password) of the CA Datacom client. 2. The server verifies those credentials with the operating system, which either rejects them or creates an ACEE (system control block representing a user). 3. The server associates the ACEE with its own task control block and invokes CA Datacom to process the caller’s request. 4. CA Datacom checks the ACEE-represented client’s rights with respect to the resources required for the current request. If any of the above actions fails, the server raises the SECURITYFAIL exception.
SCOPE	The valid values are SESSION (default) and TRANSACTION. If SCOPE=TRANSACTION, all the URTs opened by a server instance during a user’s transaction are closed at transaction end. Otherwise, all those open URTs stay open until explicitly closed by MODIFY … SERVERCOMMAND (see Closing and Opening of URTs) or until the end of the session. If CA Datacom MUF’s number of tasks is limited, consider specifying SCOPE=TRANSACTION to release a task as quickly as possible. However, if you repeatedly execute the same transaction in the server, specifying SCOPE=SESSION might result in optimal performance.
TRXDB	This parameter is required only if FSLEVEL=1. Specify the database number of the CA‑Datacom transaction database used to log Fail Safe records. The default value is 888.

Estimating the CTABLESIZE Parameter

When you select CA Datacom fields as TIBCO Object Service Broker DAT fields, the number of fields that you can access using a DAT table definition depends on the CTABLESIZE Data Object Broker parameter. To estimate the number of bytes required to support a specified number of fields, execute the following shareable tool:

ESTIMATETBLDFN(num_fields)

You must supply one argument, which is the maximum number of fields accessed by a DAT table in your system. The tool returns an estimate of the maximum CTABLESIZE required (for each TIBCO Object Service Broker table type) to support this number of fields.

Result of Executing ESTIMATETBLDFN for 50 fields.

---

 

----------------------------- INFORMATION LOG --------------------------------

COMMAND ===> SCROLL ===> P

DATE: Nov 28,2006 REPORT ON ESTIMATE CTABLESIZE

FOR "50" FIELDS

 

Table Type CTablesize(K)

---------- -------------

 

ADA 5

DAT 7

DB2 5

IDM 6

IMS 6

MAP 4

SLK 4

TDS 3

 

 

PFKEYS: 2=NEXT LOG 3=EXIT 5=REPEAT FIND 12=EXIT 13=PRINT 9=RECALL

---

 

See Also

•	TIBCO Object Service Broker Parameters for information about parameters.

•	TIBCO Object Service Broker for z/OS Installing and Operating for more information about network connections.

Copyright © Cloud Software Group, Inc. All Rights Reserved