![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The action coded is valid only when a value is specified in the RULE parameter. ACTION=T is strongly recommended. The rule specified by the RULE parameter is invoked by the login rule according to the value of this parameter:If ACTION=T, the login rule TRANSFERCALLs to the specified rule. This will cause the current transaction stream to end the new rule will run at the same transaction stream level.If ACTION=E, the login rule EXECUTEs the specified rule. This generates a second TIBCO Object Service Broker transaction stream.If ACTION=C, the login rule CALLs the specified rule. The specified rule run as at the same TIBCO Object Service Broker transaction stream level. The spelling to be used for abbreviated names of the days of the week when converting a date field to a string.
On the z/OS platform, the $SYSDATE macro is used to set date masks. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information about using the $SYSDATE macro. Specifies whether the TIMEOUTLIMIT session startup parameter takes precedence over the Execution Environment initialization parameter.
ALLOWSESSIONTIMEOUTLIMIT, ALLOWSESSTIMEOUT, NOALLOWSESSIONTIMEOUTLIMIT, NOALLOWSESSTIMEOUT Set ALLOWSESSIONTIMEOUTLIMIT according to site requirements. Using the ALLOWSESSIONTIMEOUTLIMIT parameter you can override the TIMEOUTLIMIT Execution Environment initialization parameter, on a session-by-session basis, through the use of the TIMEOUTLIMIT session startup parameter.Using the default of NOALLOWSESSIONTIMEOUTLIMIT causes the value of the TIMEOUTLIMIT session startup parameter to be ignored. The spelling to be used for abbreviated names of the months of the year when converting a date field to a string.
On the z/OS platform, the $SYSDATE macro is used to set date masks. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information about using the $SYSDATE macro.
BATCHCONSOLE—The osBatch output is sent to the display console, except for the copyright notice and the parameter list. After the first rule is completed, the return value and end message are also sent to the display console.NOBATCHCONSOLE—No output is sent to the display console, except for parameter syntax errors. It is set by the TIBCO Object Service Broker monitor process when it starts the Execution Environment process.
It is set to the value of the IPCKEY Execution Environment parameter by the TIBCO Object Service Broker monitor process when starting the Execution Environment.
This value determines the number of entries in the builtin name hash table. Each entry is 4 bytes long. Storage is virtual, non-fixed, above the 16 MB line, and allocated once at Execution Environment initialization. Specifies whether the first transaction of the session can update TDS tables and external databases.
If no persistent database updates are required in the first transaction, use BROWSE; otherwise, use NOBROWSE. BROWSE—The first transaction of the session runs in browse mode, disallowing updates to TDS and external databases. An exception is raised if a rule attempts to update data inappropriately.NOBROWSE—The first transaction of the session runs in update mode. Table type of TDS and external databases can be updated.Performance: Running in BROWSE mode does not request any locks. This reduces locking conflicts and message traffic between the Execution Environment and the Data Object Broker.
Each national character set name must have a one-page table for all 256 characters in the set. Each table entry includes an attribute list that describes the effects of converting type V syntax characters to type C.
•
• By entering a value in the @NLS1 table, you can use uppercasing rules other than ENGL on Open Systems. The name of the CICS container to be used by the Execution Environment to pass back error messages.
16-character container name according to the CICS specification This parameter enables the user to select any valid 16-character name. The name of the CICS container to be used for passing session parameters to the Execution Environment for session startup.
16-character container name according to the CICS specification This parameter enables the user to select any valid 16-character name.
A valid four-byte CICS transaction code associated with S6BCSSC2, the TIBCO Object Service Broker CICS client program. This enables the user to select any valid four-byte CICS transaction code to access TIBCO Object Service Broker. It is used when starting peer servers in the CICS Execution Environment. Specifies whether the CICS Execution Environment makes use of CICS pseudo-conversational processing whenever a DISPLAY statement or a DISPLAY & TRANSFERCALL statement is executed in a rule.
Set CICSPSEUDOCONVERSE=Y to use CICS pseudo-conversational processing. CICSPSEUDOCONVERSE=Y implements 3270 text display with the sequence:EXEC CICS SEND, EXEC CICS RETURN TRANSID, EXEC CICS RECEIVEStorage: running in pseudo-conversational mode releases CICS owned storage only. TIBCO Object Service Broker controlled storage is still retained. The amount of virtual storage above the 16 MB line to be made available to the CICS address space.
Set this parameter based on the needs of your CICS environment. This parameter increases only the site’s default upper limit of virtual storage that can be used above the 16 MB line. If this parameter is not coded or is set to 0K, this limit is determined by the REGION CICS parameter or the IEFUSI exit, if coded.This parameter overrides the CICS storage limit set by your systems programmer.
When you issue a VSAM close at the end of a TIBCO Object Service Broker transaction, a SYNCPOINT is done only if CICSVSAMSYNC=Y or if the session is an API session.You can change the setting during the session by calling $SETOPT('CICSVSAMSYNC',newvalue). Refer to TIBCO Object Service Broker Managing External Data for information on handling TIBCO Object Service Broker requests with respect to synchronization. The name of the SDK (C/C++)/SDK (Java) code page to be used for national language support. Set by the TIBCO Object Service Broker monitor process.
Open Systems: applies only to SDK (C/C++) and SDK (Java) sessions. The code page setting determines the code page of certain cliProc in and out parameters, as well as the external representation of MAP table fields with “*” external syntax and textual internal syntaxes.NOTE Setting the national character set does not set the decimal separator. Refer to TIBCO Object Service Broker for z/OS External Environments or TIBCO Object Service Broker for Open Systems External Environments for information on the SDK (C/C++) and the SDK (Java).
• The cliSetCodepage SDK (C/C++) function
• The STARTSS SDK (C/C++) operation
• The Session SDK (Java) constructor
• The start SDK (Java) methodThe SDK (C/C++)/SDK (Java) endian type. This sets the order of the bytes in a word: placing first the most significant or the least significant part of the number.This parameter can be used only as part of a parameter string passed to the STARTSS cliProc request (SDK (C/C++)) or to the Session or start methods (SDK (Java)).
Open Systems: applies only to SDK (C/C++) and SDK (Java) sessions. The endian type of the SDK (C/C++) or SDK (Java) platform. This parameter affects the external representation of MAP table fields with internal syntax B and “*” external syntax. Refer to TIBCO Object Service Broker for z/OS External Environments or TIBCO Object Service Broker for Open Systems External Environments for information on the SDK (C/C++) and the SDK (Java).
• The STARTSS SDK (C/C++) operation
• The Session SDK (Java) constructor
• The start SDK (Java) method
The client TCP/IP port number. The value is set by the parent TIBCO Object Service Broker monitor process.
The TCP/IP host name of the machine that runs the TIBCO Object Service Broker monitor process or the z/OS Execution Environment where the SDK (Java) client is to connect.
Use the host name of the machine that runs the TIBCO Object Service Broker monitor process (Open Systems) or the Execution Environment (z/OS). CLIHOST can be used only as part of a session parameter string passed to a STARTSS cliProc request. It identifies the host name where the SDK (C/C++) client is to establish a session. CLIHOST must be used in pair with the CLIPORT parameter to fully identify the target TIBCO Object Service Broker monitor process (Open Systems) or Execution Environment (z/OS). Use of CLIHOST and CLIPORT pair is optional; the CLINODE parameter can be used instead. The maximum length of an SDK (C/C++) or SDK (Java) message that can be sent or received between clients and servers. The length includes the message and control information.
z/OS: CICS Execution Environment, Native Execution Environment. A value of 0 MB means no limit. Use the specification of 0 MB with caution as it can cause storage constraint in the system. The node name of the TIBCO Object Service Broker monitor process or the z/OS Execution Environment where the SDK (C/C++) client is to connect.SDK (Java) does not support CLINODE.
For Open Systems, use the name specified for a node in the huron.dir file.For z/OS, use the value of the EENAME parameter, if it exists, or of the MDL parameter, from the HRNIN file. CLINODE can be used only as part of a session parameter string passed to a STARTSS cliProc request. It is used to identify the target TIBCO Object Service Broker monitor process (Open Systems) or Execution Environment (z/OS). Use of CLINODE is optional; the CLIHOST/CLIPORT pair can be used instead. The TCP/IP port number of the TIBCO Object Service Broker monitor process or the z/OS Execution Environment where the SDK (Java) client is to connect.
CLIPORT can be used only as part of a session parameter string passed to a STARTSS cliProc request. It is used in conjunction with CLIHOST to identify the target TIBCO Object Service Broker monitor process (Open Systems) or Execution Environment (z/OS). Use of the CLIHOST/CLIPORT pair is optional; the CLINODE parameter can be used instead. Specifies the CLI request processing elapsed time interval in centiseconds, after which the IMS TM Logger Exit is disabled and the Execution Environment shutdown.
0 to 232 -1 (100 = 1 second) Closes the TIBCO Object Service Broker monitor process that is listening on the host specified by the HOST parameter and listening on the port specified by the PORT parameter.
When CLOSE is specified with a TIBCO Object Service Broker monitor process, this process initiates a close sequence for the target TIBCO Object Service Broker monitor process and then exits immediately. As the target TIBCO Object Service Broker monitor process closes, its listening port is shutdown and it waits for any child Execution Environment processes to exit before exiting. Stops the specified Execution Environment process started by the TIBCO Object Service Broker monitor process that is running on the host specified by the HOST parameter and listening on the port specified by the PORT parameter.
The Execution Environment operating system process ID, or the EENAME:Execution Environment instance pair. When CLOSEEE is specified with a TIBCO Object Service Broker monitor process, this process initiates a stop sequence for the target instance of Execution Environment and then exits immediately. The target instance of the Execution Environment waits for all its sessions to stop. For additional information, refer to HOST, PORT, and STOPEE. See also TIBCO Object Service Broker for Open Systems Installing and Operating.
• Numeric values, such as 18000, are accepted; they are rounded to the next higher KB With COMMITSIZE=16K, an application that updates long rows where the length is 1 KB or more has to commit every 16 rows. Increasing COMMITSIZE to 32 KB allows the application to extend the number of row updates to 32, thereby maintaining a larger logical unit of work.For an application that updates rows with short row lengths and runs into a COMMITLIMIT exception, increasing COMMITSIZE allows a larger logical unit of work, that is, a larger number of updates.Extending COMMITSIZE for this application could require a corresponding increase in the WORKINGSET Data Object Broker parameter. This avoids the Data Object Broker “too many buffers required” error message that implies that the logical unit of work is updating too many data store pages.For some applications, extending COMMITSIZE allows fewer intermediate COMMITs. This lowers the number of sync messages from the Execution Environment to the Data Object Broker.
z/OS.
• S6BDRCB0—TIBCO Object Service Broker Batch Execution Environment Use the defaults, unless you have a requirement for multiple modules in a specific environment. This parameter is specified at Execution Environment initialization to select an alternative module to supply the configuration defaults. The TIBCO Object Service Broker SVC number (specified by the SVC parameter) is extracted from the default module of the respective environment, regardless of the setting of the parameter. The amount of time, in seconds, that the TIBCO Object Service Broker monitor process waits for a connection to be made before timing out.
A valid TIBCO Object Service Broker date format; length must be other than six (6). Refer to TIBCO Object Service Broker Shareable Tools for a listing of valid formats. On the TIBCO Object Service Broker z/OS platform, the $SYSDATE macro is used to set date masks. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information about using the $SYSDATE macro.
Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday On the TIBCO Object Service Broker z/OS platform, the $SYSDATE macro is used to set date masks. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information about using the $SYSDATE macro. Specifies whether the Execution Environment is to log DB2 server commands for the purpose of creating STATIC SQL handlers.
z/OS.
period (. or '.') and comma (','). That is, the period can appear with or without single quotation marks, while the comma must appear within single quotation marks. Specifies the character to be used as the decimal separator. The value can be queried by the $GETOPT tool.Note Setting the national character set does not set the decimal separator. The default value of the EENAME parameter.
The default value of the MONNAME parameter.
The default value of the SESSNAME parameter.
The default value of the ostty NAME parameter.
Abbreviated Name
• Move it from the %OS_ROOT%\log (Windows) or ${OS_ROOT}/log (Solaris) directory Only log files not marked as read-only are deleted. They are deleted when the current time minus the last change time of the log file is greater than the value specified for DELETELOG.Startup logs require special consideration: Startup log files are opened and appended to by all TIBCO Object Service Broker processes run during a day. When the date changes, a startup log is not used again. The startup log file is deleted only when the current time is greater than the value specified for DELETELOG after the end of the day when the startup log is created. The name of the Data Object Broker to which a session is to connect. Can also affect binding between sessions.
Abbreviated Name A valid upper case alphanumeric identifier of one to 16 characters in length. osee: For online sessions, it defaults to the OSMONDOB parameter value. For osBatch, it defaults to an empty string. The Data Object Broker name is expected to be set to the name of an accessible Data Object Broker whose connection information is listed in the file specified by the OSDIR parameter.The simplest way to set the DOB parameter is to set the osMon DOB parameter and let osee use it as the default. When you use the TIBCO Object Service Broker monitor process (osMon) parameter, osMon writes this name to the OSMONDOB parameter to serve as a default value for the Execution Environment (osee) initialization parameter.As an osee parameter, this is the name of the Data Object Broker to which all sessions in the osee connect.Binding between sessions is performed only if the osMon DOB parameter is not empty and the osee DOB parameter is either empty or is the same as the osMon DOB parameter. The file type used to process calls to the @READDSN and @WRITEDSN tools and the load/unload to external files tools.
Abbreviated Name LENGTH_PREFIXED_EBCDIC, LINE_SEPARATED_ASCII Use the file type of LENGTH_PREFIXED_EBCDIC if you are using the load/unload to external file tools. LENGTH_PREFIXED_EBCDIC—Native TIBCO Object Service Broker format. This data is stored in EBCDIC and big-endian format. The length of a record is determined by a length stored in the first two bytes of a record.LINE_SEPARATED_ASCII—ASCII line-oriented data where the end of a line is delimited by a new line character or the end of the file format. The path to the directory containing files accessed with the @OPENDSN tool, import and export tables, and load/unload to external files tools.
Refer to WORKINGDIR for more information.
If both quote character and field separator characters are defined, fields are delimited by the quote characters.If quote character is NONE and a field separator is defined, a backslash (\) is inserted in the output before any characters that are the same character as the field separator and that are not generated as field separators. The backslash does not appear before the actual separator.For example, if you set quote character to NONE, and field separator to COMMA, commas that your application inserts, that are not field separators, are preceded by a backslash in the output.
LENGTH_PREFIXED_EBCDIC, LENGTH_PREFIXED_EBCDIC_NATIVE_ENDIAN, LINE_SEPARATED_ASCII LENGTH_PREFIXED_EBCDIC—Native TIBCO Object Service Broker format. This data is stored in EBCDIC and big-endian format. The length of a record is determined by a length stored in the first two bytes of a record.LENGTH_PREFIXED_EBCDIC_NATIVE_ENDIAN—The native format of the platform.LINE_SEPARATED_ASCII—ASCII line-oriented data where the end of a line is delimited by a new line character or the end of the file format.
If both quote character and field separator characters are defined, fields are delimited by the quote characters.If quote character is NONE and a field separator is defined, a backslash (\) is inserted in the output before any characters that are the same character as the field separator, and that are not generated as field separators. The backslash does not appear before the actual separator.For example, if you set quote character to NONE, and field separator to COMMA, commas that your application inserts, that are not field separators, are preceded by a backslash in the output.
This parameter’s value can be used as a reference to the Execution Environment process that runs the session.
Abbreviated Name For batch Execution Environments: ee.name.mm.dd-hh.MM.ss.log,
− mm is the month
− dd is the day
− hh is the hour
− MM is the minutes
− ss is the seconds
• instance is the Execution Environment instance number
Abbreviated Name z/OS: Use a name that starts and ends with an alphabetic character (does not end in a numeric character). For Execution Environments supporting the SDK (C/C++) or the SDK (Java), specify the 8‑byte ID of the IP address of the TCP/IP socket.
• If not specified, the value for the MDL parameter is used. If specified, the value for EENAME is used instead of the value for the MDL parameter. Refer to MDL for more information about the MDL parameter.
• If you specify a value of the form AAAnnn, that is, one that ends in numeric characters, communications tries to open an identifier of AAA001, AAA002, and so on, until either it finds an available ID or the pool of names is exhausted.
• For a Native Execution Environment, EENAME should NOT end in numerics, to avoid pattern matching behavior.
• For the SDK (C/C++) and the SDK (Java) running under a Native Execution Environment, if the Native Execution Environment is to support VTAM terminals, the VTAM definitions should have the same applid. This parameter defines which osee process is to run the session. The monitor process tries to find an instance of osee with the specified name and number of running sessions below the value of the MAXSESSION parameter. If it finds such an instance, it selects that instance to run the new session. Otherwise, a new instance of osee with the specified name and with parameters corresponding to that name is created to run the new session. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information about specifying the application identifier model.
z/OS. Use the default to print the messages with suffix I that are destined for the console, unless you want the system to suppress them. Specifies the codepage (net_codepage) that TIBCO Enterprise Message Service uses to transmit TIBCO Enterprise Message Service messages.
z/OS. Refer to TIBCO Enterprise Message Service C and COBOL Reference for information on the tibems_SetCodePages() function and to TIBCO Object Service Broker National Language Support for the value of the host_codepage mentioned in TIBCO Enterprise Message Service C and COBOL Reference.The response to the CICS end message that is issued when a TIBCO Object Service Broker session ends.
Abbreviated Name Use the default. In conjunction with ERRMESSAGESCREEN=HOLD, you can set the RTIMOUT CICS transaction profile parameter to an appropriate value (for example, two minutes). This prevents CICS from entering a terminal READ state immediately, enabling the operator to read the end message and respond.NOTE If CICS does not receive input from the terminal before the time-out period specified by RTIMOUT expires, the transaction is terminated abnormally.RTIMOUT has no effect for MRO connections. In an MRO environment, you can use the terminal-level TYPETERM equivalent SIGNOFF setting. The time-out value can then be set in the RACF profile information. When a TIBCO Object Service Broker session ends with a SESSIONENDACTION, an error message is sent to the terminal. ERRMESSAGESCREEN specifies how you want to handle the error message screen that appears:
• HOLD—Waits for the terminal operator to read the message before terminating the TIBCO Object Service Broker transaction. The transaction is conversational while it waits for terminal input.
• NOHOLD—Displays the error message screen for two seconds and then terminates the task. Associated DocumentationThe CICS Resource Definition Guide IBM manual for information about the RTIMOUT CICS parameter.
Abbreviated Name One or more of the following, each separated by a single space: INFORMATION, LOG, WARNING, ERROR; or an empty string meaning that no message is to be written
Storage: This value is used to determine the number of entries in the rule name hash table. Each table entry is 4 bytes long and is allocated for each transaction stream level. The storage is non-fixed virtual above the 16 MB line.
This parameter is used to determine the size of the table containing local variable names and is allocated for each transaction stream level. Each local variable uses a 24‑byte table entry. The storage is non-fixed virtual above the 16 MB line.
z/OS. Use the default unless you are using large strings or are accessing CICS or IMS COMMAREAs; then set EXECLOCALSIZE to 128K. Storage: This is used to determine the size of the heap containing storage for TIBCO Object Service Broker local variables and is allocated for each transaction stream level. The storage is non-fixed virtual above the 16 MB line.
Use the default, unless performing a significant amount of nesting within FORALL statements. Allocates storage for the Executor Scope stack of each transaction stream level. Each entry corresponds to one nested FORALL statement. The size of each entry is 22 bytes plus the length of all parameters of the table. The storage is non-fixed virtual above the 16 MB line.
Use the default, unless you are using CICS or IMS COMMAREAs; then set EXECSTACKSIZE to 128K. Allocates storage for the interpreter runtime stack of each transaction stream level. The method of allocation of GDG (Generation Data Group) data sets accessed either as tables of type IMP and EXP or through the @OPENDSN, @READDSN, @WRITEDSN shareable tools.TIBCO Object Service Broker passes this information to the operating system for use during dynamic allocation.
z/OS.
• If FILEGDGSEARCH=STATIC, the requested level of the GDG is allocated based on the state of the GDG at the time of the first allocation under TIBCO Object Service Broker. This behavior was standard before the introduction of this parameter. This ensures that multiple accesses to the same level from the same TIBCO Object Service Broker session results in the same data set generation being accessed.
• If FILEGDGSEARCH=DYNAMIC, the requested level of the GDG is allocated by doing a catalog search. This is to ensure that level 0 always returns the most recent data set generation. If the same level is requested more than once in a TIBCO Object Service Broker session, the data set accessed could differ. The TIBCO Hawk microagent application name for a Hawk microagent embedded in the TIBCO Object Service Broker monitor process (osMon) or the TIBCO Object Service Broker batch client (osBatch). This name can be used by TIBCO Hawk Agents when applying a Hawk rulebase. For online Execution Environments, the value is set by the parent TIBCO Object Service Broker monitor process.
If the value is an empty string, the default application name used will be based upon the location of the Hawk microagent: Set as appropriate to avoid Hawk microagent application name collisions. Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information about the TIBCO Object Service Broker interface to TIBCO Hawk. The TIBCO Hawk Rendezvous daemon and TCP port parameters. For online Execution Environments, the value is set by the parent TIBCO Object Service Broker monitor process.
Setting this parameter enables the Hawk microagent within osMon or osBatch. Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information about the TIBCO Object Service Broker interface to TIBCO Hawk. Refer to product documentation for TIBCO Hawk and TIBCO Rendezvous for information about the Rendezvous daemon parameter. The TIBCO Hawk microagent display name for a Hawk microagent embedded in the TIBCO Object Service Broker monitor process (osMon) or the TIBCO Object Service Broker batch client (osBatch). This name is displayed when using a TIBCO Hawk console application, such as TIBCO Hawk Display. For online Execution Environments, the value is set by the parent TIBCO Object Service Broker monitor process.
If the value is an empty string, a default display name will be generated based upon the location of the Hawk microagent:When osMon is configured to only listen on a specific network interface, the following is used: Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information about the TIBCO Object Service Broker interface to TIBCO Hawk. The TIBCO Hawk Rendezvous network parameter. For online Execution Environments, the value is set by the parent TIBCO Object Service Broker monitor process.
Setting this parameter enables the Hawk microagent within osMon or osBatch. Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information about the TIBCO Object Service Broker interface to TIBCO Hawk. Refer to product documentation for TIBCO Hawk and TIBCO Rendezvous for information about the Rendezvous network parameter. The number of milliseconds to wait between TIBCO Hawk session creation attempts. For online Execution Environments, the value is set by the parent TIBCO Object Service Broker monitor process.
If the internal Hawk microagent is not able to establish a connection to TIBCO Hawk, then it will sleep for at most the specified number of microseconds before trying again. Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information about the TIBCO Object Service Broker interface to TIBCO Hawk. The TIBCO Hawk Rendezvous UDP service port. For online Execution Environments, the value is set by the parent TIBCO Object Service Broker monitor process.
Setting this parameter enables the Hawk microagent within osMon or osBatch. Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information about the TIBCO Object Service Broker interface to TIBCO Hawk. Refer to product documentation for TIBCO Hawk and TIBCO Rendezvous for information about the Rendezvous network parameter.
This parameter can be specified only from a command line. It is ignored for online execution. The name of the host machine where the TIBCO Object Service Broker monitor process listens for connections; also, the name of the destination machine for the STOP, CLOSE, RELOADPARAMS, STOPEE, CLOSEEE, STOPSESS, and STATUS TIBCO Object Service Broker monitor commands.
• If HOST is set to an empty string and the IP parameter is set to an empty string, the TIBCO Object Service Broker monitor process listens on all IP addresses associated with the machine where it is executing.
• If HOST is not set to an empty string or the IP parameter is not set to an empty string, the TIBCO Object Service Broker monitor process listens only to the specified IP address.
• If both HOST and IP are not set to empty strings, both parameters must specify the same IP address. Specifies whether to use emulated IBM S/370 floating-point operations for all arithmetic on floating point data.
Use IBMFLOAT to obtain identical results when running on Windows or Solaris as compared with z/OS or to obtain greater precision for the results. Use NOIBMFLOAT only if it is important to ensure that results obtained on TIBCO Object Service Broker Release 4.0 or later are identical to those obtained on Release 3.2.
Specifies whether terminals with sessions established under this IMS TMclient or Native Execution Environment have the extended data stream or extended attribute support.
z/OS: IMS TM client (MPR), Native Execution Environment. This parameter can be specified in the MPR, in the Native Execution Environment, or in both.
• If this parameter is not specified in the MPR, the Native Execution Environment setting is used.
• If specified both in the MPR and the Native Execution Environment, the MPR setting is used.
• If not specified in either the MPR or the Native Execution Environment, no extended attribute support is assumed for IMS TM terminals.
• The name of the transaction to invoke when resuming a TIBCO Object Service Broker IMS TM conversational transaction in the Message Processing Region (MPR).
The named conversational IMS transaction must be associated with the S6BDCKRN TIBCO Object Service Broker IMS continuation-client program.The named transaction is used by TIBCO Object Service Broker to implement the rules statements DISPLAY, UNTIL DISPLAY, and DISPLAY & TRANSFERCALL in an IMS TM conversational environment.To use one IMS TM system to connect to multiple TIBCO Object Service Broker environments, specify a transaction code name on the IMSSCREENTRAN parameter that is different from the default S6BDCKRN. To avoid an 806 abend when loading the module with the new name, relink the S6BDCKRN module with the new module name. The PSB name must match the transaction code to avoid a 0C4 abend. The name of the transaction to invoke when resuming a TIBCO Object Service Broker IMS TM non-conversational transaction in the Message Processing Region (MPR).
The named non-conversational IMS transaction must be associated with the S6BNCKRN TIBCO Object Service Broker IMS continuation-client program. The named transaction is used by TIBCO Object Service Broker to implement the rules statements DISPLAY, UNTIL DISPLAY, and DISPLAY & TRANSFERCALL in an IMS TM non-conversational environment. The instance number for an Execution Environment process. It is used in conjunction with the MAXSESSION and EENAME parameters.
The value for MAXSESSION determines when a new instance is created for an Execution Environment. Refer to MAXSESSION and EENAME for additional information. The name of the library that holds the rules for the installation promoted from the local libraries.
Abbreviated Name
• osMon and osBatch: SITE.
• TIBCO Object Service Broker UI, Object Integration Gateway, ostty, SDK (C/C++), and SDK (Java): The value is set by the parent TIBCO Object Service Broker monitor process.
• For TIBCO Object Service Broker UI, Object Integration Gateway, ostty, SDK (C/C++), and SDK (Java) sessions, this is a read-only parameter and should not be modified by a user. The estimated number of rules that can be executed during a session from the installation library, for the rules manager.
Use the default, or the actual number of rules in your system/installation library. This value determines the number of entries in the installation library rules name hash table. If the value is less than the number of rules that can be executed, the table grows dynamically. Over-allocating increases storage usage unnecessarily, while under-allocating could increase search time, as the dynamic nature of the table chains new entries to the original table.Each entry is 4 bytes long. Storage allocated is virtual, non-fixed, above the 16 MB line, and allocated once at Execution Environment initialization. The IP address of the host where the TIBCO Object Service Broker monitor process listens for connections.
• If IP is set to an empty string and the HOST parameter is set to an empty string, the TIBCO Object Service Broker monitor process listens on all IP addresses associated with the machine where it is executing.
• If IP is not set to an empty string or the HOST parameter is not set to an empty string, the TIBCO Object Service Broker monitor process listens only to the specified IP address.
• If both IP and HOST are not set to empty strings, both parameters must specify the same IP address.
This must be a unique value for each TIBCO Object Service Broker monitor process. Specifies whether to keep the Execution Environment log after the Execution Environment shuts down.
ALWAYS—Never deletes the log at Execution Environment shutdown.ANY_MSG—Deletes the log file only if no messages were logged (other than the parameter listings).WARNING_MSG—Deletes the log file only if no warning or error messages were logged.ERROR_MSG—Deletes the log file only if no error messages were logged.NEVER—Always deletes the log file at Execution Environment shutdown. Specifies whether to keep the monitor process log after the TIBCO Object Service Broker monitor process shuts down.
ANY_MSG—Deletes the log file only if no messages were logged (other than the parameter listings).WARNING_MSG—Deletes the log file only if no warning or error messages were logged.ERROR_MSG—Deletes the log file only if no error messages were logged. Specifies whether to keep the session log after the TIBCO Object Service Broker session shuts down.
ANY_MSG—Deletes the log file only if no messages were logged (other than the parameter listings).WARNING_MSG—Deletes the log file only if no warning or error messages were logged.ERROR_MSG—Deletes the log file only if no error messages were logged.
ALWAYS—Never deletes the log at ostty shutdown.ANY_MSG—Deletes the log file only if no messages were logged (other than the parameter listings).WARNING_MSG—Deletes the log file only if no warning or error messages were logged.ERROR_MSG—Deletes the log file only if no error messages were logged.NEVER—Always deletes the log file at ostty shutdown.
The library specified here is searched when SEARCH=L is specified.
One or more of the following, each separated by a single space: INFORMATION, LOG, WARNING, ERROR; or an empty string meaning that no message is to be written
To reduce fragmentation on the database disk, specify a location on a disk separate from the one used to store TIBCO Object Service Broker database files.
If your site defines an alternate rule to the default LOGONHURON rule, the alternate rule must be available in your search path. If it is in your site library, the SEARCH parameter must be set to I. If the rule is in the user’s local library, the SEARCH parameter must be set to L. The alternate rule must also have the same number of arguments as the LOGONHURON default rule. The maximum number of Execution Environments that the TIBCO Object Service Broker monitor process can simultaneously execute.
Another instance of the Execution Environment is started when the maximum number of sessions for an instance is reached.
Coordinate with Communications Support, to ensure acceptability by VTAM.
• The identifier must be available even when z/OS Cross Memory Services are being used.
• If EENAME is specified, the value for EENAME overrides the value for the MDL parameter. Refer to EENAME for more information about the EENAME parameter.
• If you specify a value of the form AAAnnn, that is, one that ends in numeric characters, communications tries to open an identifier of AAA001, AAA002, and so on, until either it finds an available ID or the pool of names is exhausted. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information about specifying the application identifier model.
mon.name.mm.dd-hh.MM.ss.log, where:
• From the TIBCO Object Service Broker monitor startup timestamp:
− mm is the month
− dd is the day
− hh is the hour
− MM is the minutes
− ss is the seconds
If this parameter is set to a non-empty string, ostty attempts to determine the address of the TIBCO Object Service Broker monitor process by using this name to look up the address of the process in the mon.prm file or, for Windows only, in the registry under the MON key.
The spelling to be used for names of the months of the year when converting a date field to a string.
January, February, March, April, May, June, July, August, September, October, November, December On the TIBCO Object Service Broker z/OS platform, the $SYSDATE macro is used to set date masks. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information about using the $SYSDATE macro.
Limits virtual storage available to the session’s message log. The LOGLIMIT exception is raised if the allocated message log is exceeded.z/OS storage: Non-fixed virtual storage, above the 16 MB line, managed by TIBCO Object Service Broker. The name of the group of ostty, Execution Environment, session, or TIBCO Object Service Broker monitor process parameter assignments to be used.Multiple groups of parameter assignments can be stored in the parameter sources. The NAME parameter identifies the start of a group of defaults within the parameter source. It is used to specify which group of defaults are to be used from the file or, for Windows only, in the registry under the appropriate key.
Used to index into the ostty, Execution Environment, session, or TIBCO Object Service Broker monitor parameter sources to set the remaining parameters. If present, this parameter specifies that SMF detail records cannot be created. This parameter overrides SMFDETAIL, if SMFDETAIL is specified at the session level. The parameter can be specified only at installation time when creating default Execution Environment option modules.
If specified as a configuration parameter, System Management Facility (SMF) records are not created even if requested at Execution Environment or session startup. Specifies whether the session (Windows or Solaris) or the Execution Environment (z/OS) is to run in online mode and that screen I/O can take place using rules statements DISPLAY, UNTIL DISPLAY, and DISPLAY & TRANSFERCALL.
Open Systems: ONLINE for ostty, otherwise OFFLINE. The value is passed to the Execution Environment by the parent TIBCO Object Service Broker monitor process. Open Systems: This is a read-only parameter and should not be modified by a user. The name of the file that contains the location directory for Data Object Broker and TIBCO Object Service Broker monitor processes.
The default Data Object Broker name for the osee, as set by the TIBCO Object Service Broker monitor process.
This non-user configurable Execution Environment parameter is set to the TIBCO Object Service Broker monitor listening TCP/IP port number.
TIBCO Object Service Broker monitor process sets this Execution Environment parameter to its listening port number.
This value is passed to the Execution Environment by the parent TIBCO Object Service Broker monitor process.
The name of the peer server within the Execution Environment to be started for servicing remote data access requests.You can also name the Gateway for Files server with this parameter. For details on configuring the Gateway for the Files component, see the chapter “Installing and Using TIBCO Service Gateway for Files” in the TIBCO Object Service Broker Managing External Data manual.
z/OS: distributed Execution Environments (CICS and Native Execution Environments). To enable the server sessions to connect to the DOB, define the z/OS Data Object Broker (DOB) Resource Manager with the S6BTLADM tool. Use the default value of DEFAULT0 unless you must distinguish between your peer servers. Setting one PEERSERVERID name, such as DEFAULT0, simplifies configuration and allows maximum sharing of peer-server sessions. Setting multiple PEERSERVERID names requires that you configure more settings to the z/OS Data Object Broker Resource Manager and the server name in the rule or table definition for the resource being accessed. The number of peer servers within an Execution Environment to be started up for a Data Object Broker using the same startup parameters with the same SERVERID.
z/OS: distributed Execution Environments (CICS and Native Execution Environments). Set up enough servers to accommodate the number of concurrent remote requests expected to be serviced by the associated Data Object Broker. Use this parameter instead of the obsolete REMOTESERVERNUM parameter. If not enough servers are available to serve concurrent remote requests, a request queue results in waiting time.
The default JES SYSOUT class for output generated using TIBCO Object Service Broker print facilities.
z/OS. A‑Z, 0-9 (a valid JES output class at your site) Specify a value that is valid for your JES and that provides the default printing characteristics required by TIBCO Object Service Broker output. When specified at session startup, the setting overrides the default established during Execution Environment initialization.
Use the default, unless more than 1 copy of a report is always required. When specified at session startup, the setting overrides the default established during Execution Environment initialization. The name of a file or existing data set to which a TIBCO Object Service Broker generated report is written.
Specify this parameter when you want output generated by TIBCO Object Service Broker to be written to a data set rather than JES spool. When specified at session startup, the setting overrides the default established during Execution Environment initialization. PRINTDATASET takes precedence over PRINTDEST if both are specified.You can specify PRINTDATASET for a specific online session in the MANAGE USERID screen.z/OS: You can set PRINTDATASET using the $SETOPT shareable tool.
• <node> is optional and specifies the JES node where the output prints.
• <char> is required when node is specified. Otherwise, it is optional.
• <printer> is the JES name of the printer where the output prints. Use a period (.) when specifying the JES printer name; for example, N2.P57.
• if you are using a Windows network printer, machinename indicates the computer on the network where the printer resides
• printername is the share name of the printer where you want to printFor example: \\sherbrook\printer1
• if you are using an IP printer, printername is the name or the IP address of the printer
• printqueuename is the name of the print queue associated with the selected printerFor example: /sherbrookprinter/ltrszqueue Specify this parameter when you want your output generated by TIBCO Object Service Broker to be printed at a destination other than your site’s default.
• If specified in the parameters used to generate the Execution Environment environment default options module, all output generated by the Execution Environment is routed to the same destination for printing by default.
• If specified in the session login command, the value specified during Execution Environment initialization is overridden for the user specifying it.PRINTDATASET takes precedence over PRINTDEST if both are specified.You can specify PRINTDEST for a specific online session in the MANAGE USERID screen.z/OS: You can set PRINTDEST using the $SETOPT shareable tool. Refer to PRINTDATASET for more information.
User Profile — The print output is directed to the values supplied in the print options fields in the TIBCO Object Service Broker User Profile. If this value is specified, the following parameters are also determined from the User Profile: PRINTCOPY. PRINTDATASET, PRINTDEST.Printer — The print output is directed to the printer named in PRINTDEST.File — The print output is directed to the file named in PRINTDATASET. The default option for printing or not printing the TIBCO Object Service Broker workbench information logs in a multi-user Execution Environment, that is, CICS or Native Execution Environment.PRINTERRORLOG is ignored in single-user environments like TSO and Batch, when the TIBCO Object Service Broker error log is always printed.
z/OS. Specify the desired option for your Execution Environment.Generally, it is preferable to not print the error log for a production system, support personnel preferring the error log to remain in the system. Developers, on the other hand, could prefer to see the error log printed. When specified at Execution Environment start-up, the setting overrides the default value specified in the configuration module.When specified at session start-up, the setting overrides the default established during Execution Environment initialization.When specified via the $SETOPT tool, the setting overrides the then current value in effect. The name of a Forms Control Buffer (FCB) to be used when printing output generated by TIBCO Object Service Broker.
z/OS. Use your site’s default as assigned by JES. If the TIBCO Object Service Broker report has special printing requirements such as a special pre-printed form, use the FCB for that form.
• If specified in the parameters used to generate the Execution Environment environment default options module, all output generated by the Execution Environment is printed to the same FCB.
• If specified in the session login command, the value specified during Execution Environment initialization is overridden for the user specifying it. The name of a form on which JES SYSOUT output generated by TIBCO Object Service Broker is to be printed.
z/OS. Use your site’s default as assigned by JES. If the report has special printing requirements such as a special pre-printed form, specify that particular form name.
• If specified in the parameters used to generate the Execution Environment environment default options module, all output generated by the Execution Environment is printed using the same form.
• If specified in the session login command, the value specified during Execution Environment initialization is overridden for the user specifying it.
PRINTPORTRAIT, PORTRAIT, NOPRINTPORTRAIT, NOPORTRAIT The default intermediary JES SYSOUT class for the SPOOLSTRIP job in a multi-user Execution Environment such as the Native Execution Environment or in a CICS region.
z/OS. A‑Z, 0-9 (a valid JES output class at your site) Specify a value that is valid for your JES and that provides the default Intermediary JES SYSOUT class required by the TIBCO Object Service Broker SPOOLSTRIP job.If running in JES2 in a multi-user environment, such as CICS or a native Execution Environment, do not specify a print class that is HELD. When a print request tries to use a HELD class, an IEFSSREQ error occurs and the print request fails.Use the JES2 command $DOUTCLASS to display the characteristics of the SYSOUT classes. This is shown by the values for the CLASS OUTDISP=(normal_disposition, abnormal_disposition).The following definition for SYSOUT=A is inappropriate for use in PRINTSPOOLCLASS=A as shown by the JES2 display of the class features:$DOUTCLASS(A)
$HASP842 OUTCLASS(A)
$HASP842 OUTCLASS(A) OUTPUT=PRINT,BLNKTRNC=YES,
$HASP842 OUTDISP=(HOLD,HOLD),TRKCELL=YES$DOUTCLASS(W)
$HASP842 OUTCLASS(W)
$HASP842 OUTCLASS(W) OUTPUT=PRINT,BLNKTRNC=YES,
$HASP842 OUTDISP=(WRITE,WRITE),TRKCELL=YES When specified, the setting overrides the default in the installation configuration module. The name of a universal character set (UCS) to be used to print the JES SYSOUT output generated by TIBCO Object Service Broker.
z/OS. Use your site’s default as assigned by JES. If the report has special printing requirements such as unique characters, specify that particular UCS name.
• If specified in the parameters used to generate the Execution Environment environment default options module, all output generated by the Execution Environment is printed using the same character set.
• If specified in the session login command, the value specified during Execution Environment initialization is overridden for the user specifying it. The name of an external writer (XWTR) to be used to print output generated by TIBCO Object Service Broker.
Use your site’s default. Specify this parameter only if the report has unique characteristics that require it to be printed by a special site supplied writer program.
• If PRINTXWTR is specified in the parameters used to generate the Execution Environment environment default options module, all output generated by the Execution Environment is printed using the same external writer. Normally standard printing services are used and this parameter is not specified.
• If PRINTXWTR is specified in the session login command, the value specified during Execution Environment initialization is overridden for the user specifying it.For Solaris, PRINTXWTR takes precedence over PRINTDEST if both are specified. TIBCO Object Service Broker for z/OS Installing and Operating or TIBCO Object Service Broker for Open Systems Installing and Operating for additional information about printing.
The value is set by the parent TIBCO Object Service Broker monitor process. Specifies whether the user’s profile information stored within TIBCO Object Service Broker is to be merged by the startup rule with Execution Environment parameters at session startup.
Use the default to take advantage of the user profile feature that sets the user’s session defaults at every login. If NOPROFILE, the user’s profile information that is stored within TIBCO Object Service Broker is not merged with session parameters.
The amount of storage to be allocated during Execution Environment initialization to bind table definitions and data.
z/OS. Specify a value large enough so that table data and definitions that are bound can reside in Execution Environment storage. Binding table definitions and data that are frequently accessed is part of a well-tuned system. The amount of storage defined for REGIONTABLESIZE is allocated from private, non-fixed, virtual storage above the 16 MB line.Specifying a value that is too small to hold all the bound table data and definitions accessed by rules causes the non-bound data to be continually refetched from the Data Object Broker each time it is referenced. This results in increased rules transaction times, Data Object Broker overhead to refetch data, and increased Execution Environment virtual storage usage, as each user has their own copy of the table definition and data.Specifying a large value provides the necessary storage for bound data and table definitions. References to this information are satisfied from the data and definitions in the Execution Environment and access to the Data Object Broker is not necessary. Transactions run faster and Data Object Broker overhead decreases.
z/OS. Use the default. Indicates that only the following components are to be traced: RTH, SFR, EXR, CQH, OCPThis parameter is used in conjunction with the REGIONTRACESIZE parameter. Each bit of the binary representation of the parameter value corresponds to a single Execution Environment component for which the trace is to be activated.Only the following components are currently defined for tracing: RTH, SFR, EXR, CQH, OCP, CSD, QMR, SRS, HAX, RCX, SNX, TMR, OAI, MSG, SMC, TAM, MEM, DYN, EDP, GAT, MOM.
• 0 — indicates that no components are to be traced
• 2147483647 — indicates that all components are to be tracedThe higher the number of components being traced, the more useful the trace; however, the CPU utilization increases as more components are traced.This information is useful to TIBCO Support in diagnosing TIBCO Object Service Broker system problems. Refer to REGIONTRACESIZE for more information.
z/OS. This parameter is used in conjunction with the REGIONTRACE parameter and must specify a non-zero value. By specifying a larger buffer you can get a greater amount of trace information recorded. This information is useful to the TIBCO Support in diagnosing TIBCO Object Service Broker system problems. Refer to REGIONTRACE for more information.
z/OS. REGIONTYPE=REMOTE must be coded in an IMS MPR. Specifying REMOTE causes TIBCO Object Service Broker to connect to a Native Execution Environment defined by the EENAME parameter to access full Execution Environment services, as well as Data Object Broker and external database server data.For other environments, this parameter must have a value of LOCAL, which is the default setting. Specifies whether the multi-user Execution Environment should accept the SHUTI (shutdown immediately) command without a prior SHUT command.When you specify REJECTSHUTI=N, the Execution Environment honors the SHUTI command and abnormally terminates all login sessions and shuts down the Execution Environment. This is not a good idea, as it can cause system abends. REJECTSHUTI=N is the default.When you specify REJECTSHUTI=Y, the Execution Environment rejects the SHUTI command that is not preceded by a SHUT command. It serves as a warning that SHUTI should be used only when it is absolutely required.
z/OS. Specify YES if you prefer a warning for SHUTI. Specify NO to retain the default behavior of no warning. When specified, the setting overrides the default in the installation configuration module.
RELOADPARAMS causes the configuration source parameters to be reloaded.When RELOADPARAMS is specified with a TIBCO Object Service Broker monitor process, this process sends a RELOADPARAMS request to the TIBCO Object Service Broker monitor process connected to the same PORT. Related parameters The name and arguments of the first application rule to be invoked after login rules processing completes. Does not apply to SDK (C/C++) or SDK (Java) sessions.
• rulename is a valid name of a rule located in one of the libraries specified by the SEARCH parameter.
• argumentn is the value of the nth argument.the first argument is the number 1; the second argument is the string 'X'; and the third argument is the string of length 2 whose value is '46’ z/OS: Seamless clients and non-seamless offline clients use the default rule name specified in the user profile.Open Systems: An empty string. For ostty clients, if a session parameter string does not contain a rule name, a start-up rule from the user profile is used, unless NOPROFILE is also specified. If the user profile contains an empty rule name, SESSMGR (workbench) is called.For SDK (C/C++) and SDK (Java): the RULE parameter has no effect. Use this parameter to specify a rule to run after TIBCO Object Service Broker session startup. If the RULE parameter is defaulted or overridden by a rule name specification, the named rule is run from the library, as determined by the SEARCH parameter, using the method specified in the ACTION parameter, in the transactional environment specified by the BROWSE and TEST parameters.If the RULE parameter is not specified for an ONLINE non-seamless client, the rule specified in the user profile is run before the menu specified in the profile appears. This parameter specifies a rule to be invoked after session startup. If the value of the parameter is not empty, the following takes place:
• A transaction with default flags is created. The default flags are defined by the BROWSE, NOBROWSE; TEST, NOTEST; and SEARCH session parameters.If the value of the parameter is empty and NOPROFILE is not present in the session parameter string, the following happens:
• A transaction with BROWSE, TEST, and SEARCH=S is created and the SESSMGR rule is called.
• If the startup rule field of the user profile is not empty, SESSMGR invokes this rule. The invocation method depends on the ACTION session parameter. The transaction flags for ACTION=E (execute) and ACTION=T (transfercall) are the session defaults (BROWSE/NOBROWSE, TEST/NOTEST, and SEARCH session parameters).
• After the rule runs, a menu specified in the user profile appears. Refer to TIBCO Object Service Broker Managing Security for more information on the startup rule field in the user profile, as well as to ACTION and to LOGONRULENAME.
Use S, which is the default, or I. Specify I or L only when one or more required rules reside in the site’s installation or local library. Specification L causes overhead in finding rules; the local library must be searched whenever a new rule name is encountered for the first time in a transaction. Significant performance benefits can be realized when frequently used rules are promoted to the installation library. If SEARCH=S is specified, TIBCO Object Service Broker searches for rules, external routines, or builtins in the following order:
2.
3. The external routines library that is contained in the ROUTINES tableIf SEARCH=I is specified, TIBCO Object Service Broker searches for rules, external routines, or builtins in the following order:
1.
3.
4. The external routines library that is contained in the ROUTINES tableIf SEARCH=L is specified, TIBCO Object Service Broker searches for rules, external routines, or builtins in the following order:
1.
4.
5. The external routines library that is contained in the ROUTINES table The size of the discretionary permission access control list area for access-securable TIBCO Object Service Broker objects: libraries, screens, tables, object sets, and reports.
z/OS. This parameter allocates an area for containing information that allows or disallows access to objects based on the user ID and current group set for the user. Each entry in this area occupies 35 bytes. If the area fills up, it is flushed and restarted, resulting in increased overhead.Storage: This requires non-fixed virtual storage above the 16 MB line; the larger a value that you specify, the more storage is required. Execute the SECSTATS rule. The area defined by this parameter is shown as OBJACL. The Storage Used field indicates how much of this area is currently in use. Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information on SECSTATS.
For a single-user Execution Environment, the minimum value provides more than enough space. For multiple users, start with the default value and tune from there. In a multiple session situation, the amount of space required is 18 bytes for each user logged in to TIBCO Object Service Broker. If the area fills up, it is flushed and restarted, resulting in increased overhead.Storage: This requires non-fixed virtual storage above the 16 MB line; the larger a value that you specify, the more storage is required. Execute the SECSTATS rule. The area defined by this parameter is shown as USERSEC.The Storage Used field indicates how much of this area is currently in use. The number of times the list has flushed should be zero; otherwise, it is indicates that space allocation is too small. Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information on SECSTATS. The accesses to non-dictionary (MetaStor) tables to be logged to the AUDITLOG. You can have different settings for Execution Environments on the same Data Object Broker.
• Use SECAUDITLOG=DISABLED for batch jobs and promotions.
•
• Use SECAUDITLOG=NORMAL for test and development systems.
• SECAUDITLOG=STRICT means all accesses are logged for objects with the log accessed flag set to Y; update accesses by level‑7 users are logged, regardless of the setting of the Log Accesses flag set in the Security Manager.
• SECAUDITLOG=NORMAL means all accesses are logged for all objects with the Log Accesses flag set to Y. When Log Accesses is set to N, table accesses are not logged.
• SECAUDITLOG=DISABLED means that nothing is recorded except for an initial entry indicating that SECAUDITLOG is disabled.
• With all the above settings per login and logout, for each TSO and batch user there is one entry per execution; for CICS and Native Execution Environments there is one entry per user per address space. Refer to TIBCO Object Service Broker Managing Security for more information about the audit log facility and TIBCO Object Service Broker for z/OS Installing and Operating about EECONFIG and the CNTL data set. The security class of the request defined by TIBCO Object Service Broker for archiving the Audit Log.
The size of the TIBCO Object Service Broker object security information area. This area holds entries that contain object name, owner, and security classification.
z/OS. Each entry in this area uses 42 bytes. If the area fills up, it is flushed and restarted, resulting in increased overhead.Storage: This requires non-fixed virtual storage above the 16 MB line; the larger a value that you specify, the more storage is required. Execute the SECSTATS rule. The area defined by this parameter is shown as OBJSEC. The Storage Used field indicates how much of this area is currently in use. Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information on SECSTATS. The size of the discretionary permission access control list area for parameterized tables. This area contains information to allow or disallow access to parameterized table instances based on the user’s user ID, group or ALL permission, when the table data is secured by individual parameter instances.
z/OS. Each entry in this area uses 102 bytes. If the area fills up, it is flushed and restarted, resulting in increased overhead.Storage: This requires non-fixed virtual storage above the 16 MB line; the larger a value that you specify, the more storage is required. Execute the SECSTATS rule. The area defined by this parameter is shown as TBLACL. The Storage Used field indicates how much of this area is currently in use.
The type of security used to verify user access to TIBCO Object Service Broker from an Execution Environment.
• INTERNAL or null implies that TIBCO Object Service Broker internal security is used for user ID login verification. This is typically done because the external security environment cannot be trusted.
• EXTERNAL implies that an external security product is controlling access to TIBCO Object Service Broker. SAF security packages such as IBM RACF, CA‑ACF2, and CA-Top Secret are supported on z/OS. Native security and the Generic Security Service (GSS) API are supported on Open Systems.
• MIXED causes the password to be verified against the TIBCO Object Service Broker password first. If this fails, it is then checked against the password in the external security system. This is useful where some user identifications are managed externally by the operating system security manager and others are defined only to TIBCO Object Service Broker. Refer to TIBCO Object Service Broker Managing Security for more information about the different types of security.
If an Userid profile is set with EXT Security Mixed-case Password: Y, the security for that user is set as if this parameter was set with EXTERNAL regardless of its actual setting.The size of the TIBCO Object Service Broker object security information area. This area holds entries that contain object name, owner, and security classification.
The size of the user basic security information area. This area holds one entry for each user logged in to the address space.
z/OS. Each entry in this area uses 33 bytes. If the area fills up, it is flushed and restarted, resulting in increased overhead.Storage: This requires non-fixed virtual storage above the 16 MB line; the larger a value that you specify, the more storage is required. Execute the SECSTATS rule. The area defined by this parameter is shown as USRSEC. The Storage Used field indicates how much of this area is currently in use. Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information on SECSTATS. The identifier for an external database server or Service Gateway for Files server. For details on configuring the Service Gateway for Files component, see the TIBCO Object Service Broker Managing External Data manual.This identifier directs remote TIBCO Object Service Broker table accesses to a particular group of servers. Some table definitions enable you to specify a server identifier for routing requests to the correct server. For example, you might need to do so for VSAM files that are controlled by a particular CICS/TS Execution Environment (EE) server.
The maximum number of times the TIBCO Object Service Broker monitor process is to attempt to restart a peer or rules-based server after a severe server failure.
z/OS: The maximum number of server sessions that are managed in this Execution Environment.Open Systems: A string containing the set of servers to be started by TIBCO Object Service Broker monitor. Syntax is: ‘number1 sessionname1 number2 sessionname2 numberN sessionnameN’
Open Systems: The validity of the values in the user string is not checked. Open Systems: SERVERS='10 NodeA 12 NodeB' Open Systems: An empty string z/OS: You must specify at least one when starting an external database server. If the SERVERBUSY exception is encountered frequently, consider increasing the value.Open Systems: Each session parameter group (sessionnameN) must contain a non-blank SERVERTYPE server parameter. The higher the value of SERVERS, the more concurrent accesses can be made to the external database.The higher the number in numberN, the more concurrent accesses can be made to the external database via server sessionnameN. Refer to the appropriate Service Gateway manual for additional information about this parameter.
Refer to the appropriate Service Gateway manual for further details about this parameter. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for further details about server types. The maximum amount of display and transfer (DISPLAY & TRANSFERCALL rules language statement) screen rows storage allowed for a user session.
z/OS. You can change the setting during the session by calling the $SETOPT tool. The action to be performed when a TIBCO Object Service Broker session terminates. The action performed uses the SESSIONENDVALUE as the object of the action.
In conjunction with the SESSIONENDVALUE parameter, this parameter can be used to implement automatic control switching between TIBCO Object Service Broker and non-TIBCO Object Service Broker applications.
• START requests a CICS transaction be automatically started after a TIBCO Object Service Broker session ends. The name of the transaction ID is specified with SESSIONENDVALUE or the $SETSESSIONEND tool.
• XCTL requests a program be executed automatically after a TIBCO Object Service Broker session ends. The name of the program to be invoked is specified by SESSIONENDVALUE or the $SETSESSIONEND tool.
• FORMAT requests that an IMS TM screen appear automatically after a TIBCO Object Service Broker transaction ends. The name of the screen to appear is specified by SESSIONENDVALUE or the $SETSESSIONEND tool.
• SWITCH requests than an immediate switch to a program be performed automatically after a TIBCO Object Service Broker session ends. The name of the program to be invoked is specified by SESSIONENDVALUE or the $SETSESSIONEND tool. Refer to TIBCO Object Service Broker Shareable Tools for more information on the $SETSESSIONEND tool. Yes (using the $SETSESSIONEND shareable tool).The CICS transaction ID or CICS program name or IMS TM screen name or IMS TM program name, depending on the action defined by the SESSIONENDACTION parameter.
A string of up to 8 characters in length, 4 characters for CICS transaction IDs In conjunction with the SESSIONENDACTION parameter, this parameter can be used to implement automatic control switching between TIBCO Object Service Broker and non-TIBCO Object Service Broker applications. Refer to TIBCO Object Service Broker Shareable Tools for more information on the $SETSESSIONEND tool. Yes (using the $SETSESSIONEND shareable tool).
z/OS. Performance: Data sets opened by one user could be inaccessible by another user; therefore, the higher the value specified, the more likely data set contention can occur among users.
This parameter’s value can be used as a reference to the instance number of the current session.
For batch sessions: batch.name.mm.dd-hh.MM.ss.log
− mm is the month
− dd is the day
− hh is the hour
− MM is the minutes
− ss is the seconds
• eeinstance is the Execution Environment instance number
• instance is the session instance number
The maximum amount of session memory for a user. On z/OS it also controls the maximum amount of storage available for EES tables.
This storage limit has no effect on the maximum transaction memory set by the TRANMEMMAX parameter.
• CLI for an SDK (C/C++), SDK (Java), and Object Integration Gateway sessions
This parameter enables a user to specify the NAME parameter for the session. When a NAME parameter is specified on the ostty command line, or any other TTY source, the specification always refers to the ostty NAME parameter not the NAME parameter for the session. The SESSNAME parameter is used to set the NAME parameter for the session.
This value is used by the osee as the virtual memory address where it maps the binding area. If present, this parameter specifies that System Management Facility (SMF) records for TIBCO Object Service Broker (subtype 72) be created for each user session.
z/OS. Use SMFDETAIL when you want SMF records to be produced at the TIBCO Object Service Broker transaction level for reporting or debugging purposes.
• If present as a session parameter and NOSMFDETAIL is not specified in the default option module, SMF detail records are created for the requesting user.
• If NOSMFDETAIL is specified, SMF detail records are not produced.For SMF detail data to be reported, SMF data collection in the Execution Environment must be turned on by specifying the SMFTYPE parameter, and the Execution Environment must be authorized.Performance: Running with SMF detail causes a significant overhead in the Execution Environment. Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information about generating SMF records. If present, this parameter specifies that TIBCO Object Service Broker Execution Environment performance information be collected and reported in TIBCO Object Service Broker System Management Facility (SMF) subtype-52, -62 and -72 records (if requested).
z/OS. Use SMFPERFORMANCE only when you require the additional information. For performance data to be reported, SMF data collection in the Execution Environment must be turned on by specifying the SMFTYPE parameter and the Execution Environment must be authorized.Performance: Running with SMFPERFORMANCE causes additional overhead in the Execution Environment. Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information about generating SMF records.
z/OS.
• When you want to collect SMF data for the Execution Environment (subtypes 50, 51, and 52) and the user sessions (subtype 60, 61, and 62), specify a number that is not currently being used by your site.
• If you are collecting SMF data for the Data Object Broker, specify the same number here. Performance: Generating SMF data from the Execution Environment involves minimal overhead. Refer to TIBCO Object Service Broker for z/OS Monitoring Performance for more information about generating SMF records. The amount of storage that can be used by an external sort product. This value is specified in the sort options via the MAINSIZE sort product parameter.
z/OS. Use the default, unless you want to allow the external sort product to use more virtual storage. External sorting is invoked when seven or more fields are sorted. Performance: More virtual storage enables the sort to perform better, although it can increase your paging rate.Storage: More non-fixed virtual storage above the 16 MB line is used. The amount of storage that can be used by the TIBCO Object Service Broker internal sort. Allocated storage is released when the sort ends, rather than at the transaction end.
z/OS. Performance: More virtual storage enables the sort to perform better.Storage: More non-fixed virtual storage above the 16 MB line is used. The maximum number of medium-sized internal sorts that can be active concurrently. Small sorts are not subject to this limit.
z/OS. Performance: Allowing more internal sort tasks improves throughput if there is a lot of sort activity.Storage: More non-fixed virtual storage above the 16 MB line is used.
Performance: Allowing more pages can improve transaction performance, if sufficient memory is available.z/OS storage: More non-fixed virtual storage above the 16 MB line is used.
z/OS.
z/OS. This value is being passed to the external sort routine via the MSGPRT sort product parameter. Control statements are printed according to installation defaults.
• ALL—Specifies that all messages, except diagnostic, are printed to the message data set
Windows: The value of the TMP environment variable if it is set, otherwise the value of the TEMP environment variable if it is set, otherwise the Windows directory.Solaris: Value of the TMPDIR environment variable if it is set and is valid, otherwise the value of the P_tmpdir manifest found in stdio.h (which is usually /var/tmp/) if it is valid, otherwise /tmp/.For Open Systems, Execution Environment start-up checks that the value represents a usable directory for temporary files.
z/OS. This value is passed to the external sort package via the DYNALLOC sort parameter. Specifies whether to enable the Execution Environment Extended Specified Task Abnormal Exit (ESTAE) routine for handling abnormal terminations.
z/OS. Enabling the STAE routine releases z/OS common system storage (SQA, CSA, and so on) acquired for Service Request Blocks (SRBs) should the Execution Environment abnormally terminate.The NOSTAE parameter disables the ESTAE routine. Disabling the STAE routine retains z/OS common system storage (SQA, CSA and so on) acquired for Service Request Blocks (SRBs) should the Execution Environment abnormally terminate.NOSTAE should be specified only when requested by the TIBCO Support for purposes of debugging. An IPL is then required to release the z/OS common system storage if the Execution Environment abnormally terminates.
z/OS. For Call Level Interface, SDK (C/C++), and SDK (Java) support, specify a minimum of 1.To improve the performance of the SDK (C/C++) or SDK (Java) sessions, use the TASKINITNUM Execution Environment parameter to increase the number of Session Initiator Tasks. The number of Session Initiator Tasks is independent of the number of concurrent SDK (C/C++) or SDK (Java) client sessions. Refer to TASKINITNUM. Each API in session occupies one standby session until the API releases the session. If no standby session is available when an API calls for one, the API is queued to a wait queue. Specifies whether the Object Service Broker SDK start-session request is to wait for an available standby session if all the standby sessions are busy.
• Specifying NO causes the Object Service Broker SDK start-session request to be rejected with an error return code of x’04’ (Start session failed) and a reason code of x’4C’ (All standby sessions are busy).
• Specifying YES causes the Object Service Broker SDK start-session request to go on a wait queue for a standby session. The wait time is controlled by the STANDBYWAITLIMIT parameter. For details, see the description of that parameter.Also, you can specify STANDBYWAIT as a parameter on the Object Service Broker SDK start-session request. In that case, the value specified in the request overrides that of STANDBYWAIT specified as a configuration or EE initialization parameter.
z/OS. Each installation must set the three parameters, STANDBYWAIT, STANDBYWAITLIMIT, and STANDBYWAITMSG, as appropriate, for the desired behavior. Specifies the wait-time limit for an available standby session if all standby sessions are busy. When that limit expires, the Object Service Broker SDK start- session request terminates with an error Return Code of x’04’ (Start session failed) and a Reason Code of x’4C’ (All standby sessions are busy).
z/OS. Each installation must set the three parameters, STANDBYWAIT, STANDBYWAITLIMIT, and STANDBYWAITMSG, as appropriate, for the desired behavior.
• Specifying YES causes a warning message to be logged for every TIBCO Object Service Broker SDK start-session request that encounters the busy condition for all standby sessions.
• Specifying NO causes no logging of such warning messages. Also, no other indications show that the SDK start-session request is awaiting an available standby session; the request appears to be hung.
Each installation must set the three parameters, STANDBYWAIT, STANDBYWAITLIMIT, and STANDBYWAITMSG, as appropriate, for the desired behavior.
z/OS. Use the default value. To capture better information on the performance of an application, consider increasing this for a development or new production system. Each entry is 160 bytes in length. You can display the information using the TIBCO Object Service Broker Performance Monitor utility. Controls the number of buffers allocated for a session. When needed, these buffers are used each in turn. Displays current status information for the TIBCO Object Service Broker monitor process that is running on the host specified by the HOST parameter and listening on the port specified by the PORT parameter.
If DETAIL is specified, the TIBCO Object Service Broker monitor process displays status information for the specified TIBCO Object Service Broker monitor process and exits immediately. The information is similar to the following:If SUMMARY is specified, the TIBCO Object Service Broker monitor process displays basic status information plus counts only for the specified TIBCO Object Service Broker monitor process and exits immediately. The information is similar to the following: Stops the TIBCO Object Service Broker monitor process that is running on the machine specified by the HOST parameter and listening on the port specified by the PORT parameter.
When STOP is specified with a TIBCO Object Service Broker monitor process, this process initiates a stop sequence for the target TIBCO Object Service Broker monitor process and then exits immediately. When the target TIBCO Object Service Broker monitor process is stopped, any child Execution Environment processes are terminated immediately. For a more orderly shutdown, use the CLOSE parameter.
When STOPALL is specified with a TIBCO Object Service Broker monitor process, this process initiates a stop sequence for all other TIBCO Object Service Broker monitor processes on the same system and then exits immediately. When a TIBCO Object Service Broker monitor process is stopped, all its child Execution Environment processes are terminated immediately. Stops the Execution Environment process specified. This process is identified by the Execution Environment operating system process ID, or the EENAME:Execution Environment instance pair.
The Execution Environment operating system process ID, or the EENAME:Execution Environment instance pair. When STOPEE is specified with a TIBCO Object Service Broker monitor process, this process initiates a stop sequence for the target instance of Execution Environment and then exits immediately. When the target instance of Execution Environment is stopped, all its sessions are terminated immediately. If a more orderly shutdown is required, use the CLOSEEE parameter. Stops the session identified either by Execution Environment and session instance numbers, or by Execution Environment operating system process ID and session operating system thread ID.
•
• You can find the values for the different parts of these formats in the session log for the session you want to stop. If STOPSESS is specified, the TIBCO Object Service Broker monitor process initiates a stop sequence for the target session and then exits immediately. For additional information, refer to HOST and PORT. Also refer to EEINSTANCE, INSTANCE, SESSIONINSTANCE, and THREADID. See also TIBCO Object Service Broker for Open Systems Installing and Operating. The type‑3 TIBCO Object Service Broker SVC number assigned to be used in establishing an authorized Execution Environment. The parameter SVC was previously named HURONSVC. Even though both names are supported, the name HURONSVC is deprecated and might be discontinued in the future.
z/OS. For CICS or IMS TM, you must use this parameter if you require an authorized Execution Environment. Authorized Execution Environments are required to obtain SMF records, use cross memory communications, and clear the TIBCO Object Service Broker audit log.Warning If the TIBCO Object Service Broker SVC is not going to be used to authorize the CICS Execution Environment, do not include this parameter in the EECONFIG jobstream input. SVC can be specified only in the default Execution Environment environment option modules. When the TIBCO Object Service Broker interface is activated in these environments, the appropriate parameter module is loaded, the SVC number is extracted, and the module deleted.To run TIBCO Object Service Broker authorized, your site must have default option modules. These modules are created during the installation process by uncommenting steps in member EECONFIG in CNTL. Specifies whether fields whose external definition specifies type "V" will be padded with blanks or NULL (0x00) characters.
• YES causes all external syntax V fields to be padded with EBCDIC blanks (X'40'). This is the same behavior as on TIBCO Object Service Broker for z/OS systems, but is different from the usual Open Systems behavior.
• NO causes external syntax V fields to be padded with bytes of zero (X'00'). This is the standard behavior for TIBCO Object Service Broker for Open Systems, but is different from the behavior on z/OS. The name of the rules library that contains the rules shipped with the TIBCO Object Service Broker product.
• All other session types: The value is set by the parent TIBCO Object Service Broker monitor process.
• For ostty, SDK (C/C++), and SDK (Java) sessions, this is a read-only parameter and should not be modified by a user. The SYSLIB parameter establishes the rules library to be searched for system rules that implement the TIBCO Object Service Broker shareable tools.
z/OS. When the Execution Environment needs a buffer for a table row, it tries to create one of size TAMBMIN. If this size is too small, the Execution Environment creates one of size TAMBMAX.
z/OS. When the Execution Environment needs a buffer for a table row, it tries to create one of size TAMBMIN. If this size is too small, the Execution Environment creates one of size TAMBMAX.
z/OS. Use the default, 8K, if the number of SESSION (SES) tables used is less than 64. If the maximum number of SESSION (SES) tables used in a Execution Environment is n, set TAMBSTS to n *128. Each entry in SES directory is 128 bytes. The maximum number of SES directory entries is 32. For the default value (TAMBSTS=8K), if the 65th SES table in the Execution Environment is referenced, the transaction is terminated and an error is issued.
z/OS. Specify a value equivalent to the maximum number of TCBs that can be active at one time on your processor.Increase the value if external routines and VSAM files are involved because TCB affinity is required for them.
z/OS. Use the default, or reduce to the maximum number of TCBs that can be active at one time on your processor.
Use the default, except when running in a Native Execution Environment. In this case, increase the number of session initiator tasks. If users log in to a Native Execution Environment through a VTAM session monitor without completing the entire login process before switching to another VTAM session, the session initiator task could go into a wait state until the login process completes. To remedy this situation, increase the number of session initiator tasks.
z/OS. Use the default, unless you want to decrease it to the number of TCBs that can be active concurrently on your processor.
z/OS.
z/OS. 0 and 1. Setting the value to 0 disables TIBCO Enterprise Message Service support for the Execution Environment. If you do not use TIBCO Enterprise Message Service, set the parameter value to 0, otherwise use the default.
z/OS. To improve the performance of the SDK (C/C++) or SDK (Java) sessions, set the TASKRCLINUM Execution Environment parameter to increase the number of remote CLI tasks. The number of those tasks is independent of the number of concurrent SDK (C/C++) or SDK (Java) client sessions. The number of System Management Facility (SMF) Writer Tasks to be started at Execution Environment initialization.
z/OS.
z/OS. Set according to resource availability. Some sort products utilize Virtual Storage below the 16 MB line, and this should be considered. Too many sort tasks could degrade the performance of the Execution Environment. Not having enough could create bottlenecks for TIBCO Object Service Broker sessions that perform sorting. The communications identifier (COMMID) of the Data Object Broker to which an Execution Environment or Message Switch is to connect.
z/OS. Must be specified; otherwise, the Execution Environment cannot communicate with a Data Object Broker. The SVC99 dynamic allocation default primary space quantity for the temporary input and output data sets used for large sorts. Space is allocated in cylinders of the device type selected by the TEMPUNIT parameter.
z/OS. Abbreviated Name The SVC99 dynamic allocation secondary space quantity for the temporary input and output data sets used for large sorts. Space is allocated in cylinders of the device type selected by the TEMPUNIT parameter.
z/OS.
Windows: The value of the TMP environment variable if it is set, otherwise the value of the TEMP environment variable if it is set, otherwise the Windows directory.Solaris: Value of the TMPDIR environment variable if it is set and is valid, otherwise the value of the P_tmpdir manifest found in stdio.h (which is usually /var/tmp/) if it is valid, otherwise /tmp/.For Open Systems, Execution Environment start-up checks that the value represents a usable directory for temporary files. The SVC 99 dynamic allocation unit and volume count for the temporary input and output data sets used for large sorts.
z/OS. One unit is more than adequate for general use. For specific applications requiring more than one unit, specify the number of units according to your space calculations. When set to a value greater than 1, this parameter allows the temporary data sets to span multiple volumes.
Do not specify, leaving the default value, unless TEST mode is specifically required. If TEST mode is on, changes to tables that are initiated by a rule are in effect only for the duration of the transaction. When the transaction ends or a COMMIT is issued, the updates are rolled back.This does not apply to external data tables; updates to external data are not rolled back.
This value can be used in conjunction with STOPSESS to stop a session.
z/OS. In a multiuser region, use the default unless a larger number of long running requests are active at any given time. An example of a long running request is a request waiting for data to be read from an TIBCO Enterprise Message Service queue.
All: all terminal-based sessions.
The Execution Environment parameters that use the value in the PORT parameter cannot use the value in the TN3270PORT parameter. These include CLOSE, CLOSEEE, RELOADPARAMS, NORELOADPARAMS, STATUS, STOP, STOPEE, and STOPSESS. The maximum amount of display and transfer (DISPLAY & TRANSFERCALL rules language statement) screen rows storage allowed for a transaction.
z/OS. You can change the setting during the session by calling the $SETOPT tool.
A transaction fails if it requests more memory than specified here.
tty.name.mm.dd-hh.MM.ss.log, where:
− mm is the month
− dd is the day
− hh is the hour
− MM is the minutes
− ss is the seconds
Must be the same as the UNICODEDIR Data Object Broker parameter. None, TIBCO Object Service Broker uses its default information for Unicode processing. The TIBCO Object Service Broker initialization code uses the files in this directory to configure Unicode processing.In the absence of any of the files in the directory, TIBCO Object Service Broker uses the default information for that portion of Unicode processing: translation, casing, or collation. Refer to TIBCO Object Service Broker for Open Systems Installing and Operating for more information about Unicode configuration.
• The external logon ID; for example, if under TSO, the TSO logon ID; in batch, the user ID submitting the job; in CICS or IMS TM, the sign-on ID.
• There is no default for the Native Execution Environment. Refer to TIBCO Object Service Broker for z/OS External Environments for more information about z/OS sessions invoked by other programs. A TIBCO Object Service Broker session does not start without a user ID. The character to be used as the left delimiter for enclosing substituted variables in @SCHEDULEMODEL.
If appropriate for your installation, use the default character (left brace). Otherwise, use a character or a string of up to three characters that is not used for other purposes. This parameter specifies the character string to be recognized by TIBCO Object Service Broker as the left delimiter for enclosing substituted variables in @SCHEDULEMODEL table instances.Instances of @SCHEDULEMODEL that are supplied with TIBCO Object Service Broker use the left brace as the left delimiter for substituted variables. If your VARLDELIMITER setting is other than the default, you must edit the @SCHEDULEMODEL instances to be consistent with this parameter’s setting. The character to be used as the right delimiter for enclosing substituted variables in @SCHEDULEMODEL.
If appropriate for your installation, use the default character (right brace). Otherwise, use a character or a string of up to three characters that is not used for other purposes. This parameter specifies the character string to be recognized by TIBCO Object Service Broker as the right delimiter for enclosing substituted variables in @SCHEDULEMODEL table instances.Instances of @SCHEDULEMODEL that are supplied with TIBCO Object Service Broker use the right brace as the right delimiter for substituted variables. If your VARRDELIMITER setting is other than the default, you must edit the @SCHEDULEMODEL instances to be consistent with this parameter’s setting.
The current century to be used for a date in a 2‑digit year date semantic type field.
If YYCENTURYRANGE is not 0, for example a valid value such as 1970, and the input year is greater than or equal to the year portion of the YYCENTURYRANGE value, the century portion of the YYCENTURYRANGE value is used. If the input year is smaller than the year portion of YYCENTURYRANGE, the century portion of YYCENTURYRANGE+1 is used. On the TIBCO Object Service Broker z/OS platform, the $SYSDATE macro is used to set the YYCENTURYRANGE. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information about using the $SYSDATE macro.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |