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


Chapter 1 Using Execution Environment Parameters : Format of the Parameters

Format of the Parameters
Syntax of Parameters
The platform that you are using determines the syntax of the parameters.
z/OS
The type of client that you are using, for example, CICS or batch, determines the actual syntax to use. In general, the syntax is:
{PARAMETER=VALUE} {KEYWORD}
for example:
RULE=LOGONHURON BROWSE
Open Systems
To set a parameter, use the syntax:
{PARAMETER=VALUE} {KEYWORD}
for example:
RULE=LOGONHURON BROWSE
See Also
TIBCO Object Service Broker for z/OS External Environments or TIBCO Object Service Broker for Open Systems External Environments for detailed information about the syntax for a specific client type.
Length of Parameter Lists
z/OS: TIBCO Object Service Broker limits the total list of parameters you specify when you start an Execution Environment to a length of 900 characters. The mechanism you use to run the Execution Environment can further reduce this limit.
Syntax of Environment Variables
Open Systems: To set a parameter using an environment variable, use a name in the following format:
OS_<type>_<parameter group name>_<parameter name>
where:
<type> is one of: EE, SESSION, MON, or TTY
<parameter group name > is the name of an Execution Environment, session, osMon, or ostty (specified by the NAME parameter and present, for example, in ee.prm, session.prm, or mon.prm as names of parameter groups)
<parameter name> is the name of the parameter that you want to set
For example, in Windows:
Set OS_EE_PROD_DOB=MYDOB
To set the environment variable for the INSTLIB parameter to MYLIB for a TIBCO Object Service Broker monitor process called PRODMON, use:
Set OS_MON_PRODMON_INSTLIB=MYLIB
Set OS_MON_MYOTHERMON_VERBOSE=TRUE
or, to set NOVERBOSE
Set OS_MON_MYOTHERMON_VERBOSE=FALSE
Parameter Files for z/OS
You can specify TIBCO Object Service Broker parameters using the HRNIN DD statement for all client styles, or a CLIST for TSO clients. The following section describes using an input file. For details about using a CLIST, refer to TIBCO Object Service Broker for z/OS External Environments.
Format of the Input File
The data set associated with HRNIN can be sequential, partitioned, or instream. The format of HRNIN must be as follows:
Example of Instream Parameter List Using HRNIN in JCL

 
/...
//HURON EXEC PGM=S6BBATCH,REGION=4M,
//PARM=(OFFLINE,’U=USERID,TDS=VTAMID’)           > USER AND VTAM IDS
//STEPLIB DD DSN=HUR01.HURON.LOAD,DISP=SHR       > SHOULD CUSTOMIZE
//HRNOUT DD SYSOUT=*
//HRNPRNT DD SYSOUT=*
//HRNIN DD *                                     > RULE AND PARAMETERS
RULE=HLIPREPROCESSOR(’COBOL’,’HURON’,’HURON AND COBOL SOURCE’,
’COBOL ONLY SOURCE’,’HLL.HLLLIST’,’ERRORSTOP’), MSGLOGMAX=4M,
CHARSET=CDNB /* HRNIN comment */
/*

 
Parameter Files for Open Systems
You can specify parameter values using parameter files. The parameter files are located in %OS_ROOT%\database on Windows and ${OS_ROOT}/database on Solaris. The files are indexed by a NAME parameter and only parameter assignments that follow the NAME parameter whose value corresponds to the current NAME parameter for the process to be used.
Format of the Parameter Specifications
NAME=value1
P1=pvalue1
P2=pvalue2
NAME=value2
P1=pvalue1
P2=pvalue2

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