|
|
|
|
|
|
|
Designated segment number where you want the audit log data table moved. This segment must be defined in the DBDLIB and must be available online at all times; see DBDLIB.
|
|
|
|
|
Accounting information to be used in installation JOB cards. The parameter string is placed inside the JOB card accounting field, for example:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Member name in <HLQ>.FILECTL that contains the startup parameters for the batch server created during the installation process. Refer to Step 3: Prepare the Initial Batch Server.
|
|
|
|
|
Initial user ID for the TIBCO Object Service Broker batch server created during the installation process. The user ID specified must be defined before the batch server is used.
|
|
|
|
|
|
|
|
|
|
High-level qualifier for the name of the IBM library that contains token routines used for locating MSBs properly.To find this value, use ISPF 3.4 with a Dsname Level of **.*CSSLIB*.
|
|
|
|
|
Number of generation data group data sets to be kept for the Data Object Broker. Used on the SYSMDUMP DD card.
|
|
|
|
|
The TCP/IP port number in the HCS relay parameter file (member RELAYCFG in <HLQ>.OSB.FILEI) that defines a z/OS Data Object Broker peer connection to a Windows Data Object Broker using TCP/IP.
|
|
|
|
|
Name of the Native Execution Environment (NEE) to be used to run the session. This is the VTAM LU name or the communications ID used to log in to the Native Execution Environment. This value must be uppercase and at most 8 characters long. It also defines the node name of the z/OS NEE used for the TIBCO Object Service Broker UI connectivity in Windows.
|
|
|
|
|
The TCP/IP port number in the HCS relay parameter file (member RELAYCFG in <HLQ>.OSB.FILEI) that defines a z/OS Native Execution Environment for TIBCO Object Service Broker UI in Windows using TCP/IP.
|
|
|
|
|
|
|
|
|
|
High-level qualifier for data sets designated as distribution libraries, uploaded from TIBCO's download site.
|
|
|
|
|
High-level qualifier for non-VSAM data sets used by TIBCO Object Service Broker. The final data set name generated must be valid to z/OS.
|
|
|
|
|
High-level qualifier for VSAM data sets used by TIBCO Object Service Broker. The final data set name generated must be valid to z/OS.
|
|
|
|
|
The symbolic name of the TCP/IP host system where the Data Object Broker resides (member RELAYCFG in <HLQ>.OSB.FILEI).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Default jobname for installation JCL JOB cards. This value must be uppercase and at most 7 characters long.
|
|
|
|
|
The size of the journals in number of disk cylinders. For a minimal TIBCO Object Service Broker system accessing external database gateways, use a value of 25.
|
|
|
|
|
Number of journal spin accumulation generation data group data sets; for example, JOURNAL.SPINOUT.
Use this parameter in conjunction with $SPINLIM$ to control how often the journal spin generation data groups are merged by SPINMRG.
|
|
|
|
|
|
|
|
|
|
The high-level qualifier for the name of the WebSphere MQ library. To find this value, use ISPF 3.4 with a Dsname Level of **.SCSQLOAD.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Your site's defined SMS MANAGEMENTCLASS for non-VSAM data sets, as required.
|
|
|
|
|
Assigns a unique Data Object Broker name in a distributed data environment. The name can be from 1 to 16 characters. The name specified is for use in remote nodes to access data in the local node. A value must be specified.
|
|
|
|
|
Default NOTIFY value for the installation JCL JOB cards. For example, you can use your TSO ID or the value of the &SYSUID variable.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A conditional variable to indicate whether duplex redologs are to be implemented. To implement duplex redologs, specify Y.
|
|
|
|
|
The size of the redolog in number of disk cylinders. For a minimal system, use a value of 50.
|
|
|
|
|
Member name in <HLQ>.FILECTL that supplies IDCAMS statements for job S6A3ALOC in <HLQ>.OSB.FILEI to define the redolog data sets. If duplexing the redolog, specify DPLXREDO.
|
|
|
|
|
Second-level qualifier for segment 0 page data sets. Use a name that is meaningful and unique.
|
|
|
|
|
|
|
|
|
|
Second-level qualifier for segment 1 page data sets. Use a name that is meaningful and unique.
|
|
|
|
|
|
|
|
|
|
Second-level qualifier for page data sets on the segment specified by $ACLSEG$ (default: segment 99). Use a name that is meaningful and unique.
|
|
|
|
|
Size in cylinders for page data sets on the segment specified by $ACLSEG$ (default: segment 99). For a minimal system, use a value of at least 14.
|
|
|
|
|
Identifier to be used to run the server sessions. This value corresponds to the Resource Management Group value within a specific TYPE. Refer to Resource Detail Screen. This value must be uppercase and at most 8 characters long.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Number of journal spin generation data group data sets created before they are merged by SPINMRG into a single data set. Default must not be changed until SPIN verification is complete in post-installation. This variable is used in conjunction with $JSRGDG$.
|
|
|
|
|
Type‑3 TIBCO Object Service Broker SVC number assigned to be used in establishing an authorized Execution Environment. The number must be between 200 and 255.
|
|
|
|
|
SYSOUT class for installation jobs output. Default directs SYSOUT to the same class as the default message class ( $MSGCLS$) on the JOB card.
|
|
|
|
|
Communications identifier assigned to the Data Object Broker. It is required by the Execution Environments to establish communications with a Data Object Broker.
|
|
|
|
|
|
|
|
|
|
Your site's defined SMS MANAGEMENTCLASS for VSAM data sets, as required.
|
|
|
|
|
|
|
|
