A report field used to determine which data columns are to be printed on an across report. When a new value is encountered for an across-by field, a new data column is printed.
A report that displays its data across the report in a spreadsheet-like format. See
across-by field.
An identifier that determines which rules statements are executed when a given condition is satisfied.
A menu-based administrative tool used to monitor and control the TIBCO Object Service Broker operating environment. It is invoked by the S6BTLADM/hrntladm utility.
A TIBCO Object Service Broker supplied session menu used by system administrators to administer the TIBCO Object Service Broker database. To invoke the administrator workbench, @ADMIN must be specified in the security user ID profile as the session menu to be used at login.
An ordered collection of arguments specified within parentheses after the rule name. The argument separator is a comma.
A Security facility that logs security failures, security related events such as logins, logouts, changes of permissions, accesses to tables when logging of accesses is requested, and, if specified, all updates made by level‑7 users. Also known as the accesslog.
A formal notation for describing the syntax of a programming language. It is used by the documentation to describe the syntax of the rules language. Formerly known as Backus normal form.
The copying of definitions or data into the Execution Environment binding area when the definition or data is first accessed by a session. Definitions of screens, tables, or rules, and the data of tables can be bound. Binding improves performance by reusing information stored in the binding area thereby reducing message traffic.
The repeating table of a report, used to display the report data. Data from data tables is inserted into the body report table.
A user who has the Borrower flag in their user profile set to Y. A borrower can obtain rights to an object so that other users cannot modify the object. See also
rights.
The report fields used to determine where a report is to take a control break. A new break within a body report table begins when a changed value is encountered in the break field.
A repeating table, with title and body components, that groups together related information in a body report table. A new grouping is started when a new value is encountered in the break field defined to the break table. Break tables can also be defined at the beginning or end of the entire report.
A read-only method of viewing data that does not lock the data. When a user is operating in browse mode, other users have access to the same data.
The U+FEFF (ZERO WIDTH NO-BREAK SPACE) Unicode character when used at the beginning of text to indicate the byte order and Unicode transformation of the following text.
A set of client and server facilities that enable programs written in third generation languages to access TIBCO Object Service Broker. Also known as the CLI. See also
SDK (C/C++) and
SDK (Java).
A table that is used to count the number of occurrences of a particular value in a specified field or fields of another table. It has a table type of CLC.
A short name describing the category (that is, purpose) of a change request. The name is within a list from which users must make a selection.
A request made by developers to promote changes made to objects associated with an application. When the request is accepted, the objects of the change request can be promoted. Commonly abbreviated as CR.
As used by Promotions, the borrowing rights of child objects that are part of a compound object.
A security level assigned to each object when it is created. The object is assigned a classification level that matches the object creator’s security clearance level. To access an object, a user’s clearance level must be equal to or greater than the object’s classification level.
A security level assigned to each TIBCO Object Service Broker user ID. The Security Manager currently supports clearance levels 0, 1, and 7. Level‑0 is used only to suspend a user from logging in. Level‑1 clearance is assigned to users and developers. Level‑7 clearance is assigned to system administration personnel.
See Call Level Interface.
This term is used in the context of National Language Support (NLS). It refers to an ordered set of characters and/or symbols that have a numeric index encoding (code point value) associated with each character and symbol. The term is usually used with a modifier, for example, the U.S. English EBCDIC code page. It is sometimes referred to as a character set or charset.
A scrollable section at the bottom of a standard workbench that lists commands you previously entered.
See primary command field.
An action that takes place during transaction processing that causes changes made to the database to be irreversible. This action occurs as part of normal termination of a transaction, or can be explicitly initiated with the COMMIT statement.
Two or more fields whose values, when concatenated together, uniquely identify occurrences of a table.
An expression evaluated for its truth or logical value (Y or N). The evaluation is used to determine the flow of execution in a rule.
A change request that contains within it one or more change requests with a status of C (that is, promoted change requests).
A control is the lowest level of graphical object that a user can manipulate within a graphical application. A control must be within a container object.
Fields of a body report table that determine how data should appear on a report. There are four types of control fields: sort, break, summary, and across-by.
As used by Security, an access mode that gives a user the authority to update the security permissions to a given object. Users with control access to an object can add, modify, or delete permissions, but they cannot pass control access to anyone or take control access away from anyone. Only individual users can control objects. Security groups cannot be assigned control access.
A transaction that has interactions with a client process during the life of the transaction. The transaction retains control of all its resources while it waits for user input (that is, during a screen display). In TIBCO Object Service Broker text-based processing, conversational transactions use the DISPLAY statement.
The security group from which a user is currently operating. A user’s current group is specified in the user profile. When a user attempts to access an object, if the user’s user ID is not listed in the permissions for that object, the name of the user’s current group is the next item looked for in the permissions for the object.
The store of data associated with a specific node, also known as the Pagestore. Each database has its own Data Object Broker. See also
Pagestore.
See external database server.
The Data Object Broker manages updates to the MetaStor and Pagestore, performs Pagestore accesses and updates on behalf of transactions running in Execution Environments, controls requests to external data servers, and controls data integrity. In a distributed environment, it is identified by its node name. The Data Object Broker was formerly referred to as the Control Region.
The meaning of the data stored in the field. The data type, also referred to as the semantic data type, determines the conversions and allowed operations that can be done on the data, and implies some TIBCO Object Service Broker edits on values placed in these fields.
As used by Security, a default permissions list names members (users or security groups) and their default access rights to new objects created by a user or group. You can specify a default permissions list for a user ID, for a Security group, or for all users.
See Execution Environment.
A field whose value is not explicitly stored in the database. The value can be determined through a reference to another field, a rule call, or a report function. For example, the value in a field can be derived from the totalling of values in another field.
A set of characters that holds display space for numeric fields. Each character has a specific representation, and represents one digit of a numeric field.
A set of display conventions applied to numeric or date fields. For example, applying the display mask MM/DD/YY to the date 2000-01-01 causes it to appear as 01/01/00.
As used in Promotions, this refers to whether a TIBCO Object Service Broker object is designated for creation, replacement, or deletion in a target system.
The placement and access of data on separate TIBCO Object Service Broker systems (nodes). See
distributed environment.
An application environment where data used in an application can be stored on a TIBCO Object Service Broker system (node) separate from the node where it is being accessed. Communications must be previously established between the nodes.
The name of a Data Object Broker. It identifies a TIBCO Object Service Broker system and is equivalent to the TIBCO Object Service Broker node name. See
node name.
1) The TCP/IP network name that your network administrator defined and configured. 2) In SNA, the system services control point providing system services for its owned resources such as lines, terminals, and applications.
See Execution Environment.
As used by Security, an action taken to activate previously defined permissions for an object set.
1) The first rule executed at the start of a text-based application.2) As used by Promotions, the first rule that is to be executed for a set of rules. This set of rules is executed and then discarded as part of a promotion.
A rule that validates access or triggers additional processing when the data in a table is accessed. It is associated with the table definition. See
trigger rule and
validation rule.
A condition raised as a result of circumstances occurring during rules processing. An exception causes the flow of a program to change and can be handled by a program by the inclusion of an ON
exception statement. Exceptions can be system-defined or user-defined.
A defined sequence of actions to be executed in a rule if an exception is encountered during rules processing.
The TIBCO Object Service Broker transaction manager. It handles application programming tasks such as rules execution, screen and report I/O, and I/O to external data. It is dependent on the Data Object Broker for access to the MetaStor. Formerly referred to as the Dependent Region.
A table that is used to export data from TIBCO Object Service Broker to a sequential file or data set. It has a table type of EXP.
A combination of elements and arithmetic or concatenation operators that results in a single value when evaluated.
A local variable, field of a table, rules argument name, function call, constant, or indirect reference.
A self-contained program provided with TIBCO Object Service Broker that allows concurrent real-time access to external data from within TIBCO Object Service Broker. It is associated with and managed by a specified Data Object Broker.
As used by Promotions, an object that is copied from a source system and stored in a file pending promotion to a target system. Objects are extracted to prepare them for their promotion to multiple TIBCO Object Service Broker systems. After extraction, the objects are still in the source system.
A commit process used to ensure that updates made in a single transaction to multiple databases (owned by one or more TIBCO Object Service Broker systems, and optionally one external database server) are synchronized at commit time.
The section of the Screen Table Painter or Report Table Painter screen used to define data fields.
The display character used to pad a screen field for the purpose of the display, for example, a dot (.).
The left-most <nn> columns of a scrollable screen table that do not scroll horizontally.
The mapping of lowercase characters to uppercase characters, such as for purposes of case-insensitive string comparison.
See external database gateway.
A field defined by a system administrator to be used organization-wide when tables are defined. Global field definitions are accessed and incorporated into applications from within the various definer tools.
As used in Promotions, a set of rights that permits all the members of a group operating out of the same library to share the management of rights and change requests among themselves.
International Components for Unicode–a mature, widely used set of C/C++ and Java libraries for Unicode support. Refer to the
ICU web site.
An attribute specified in the Table Definer that determines whether the user provides a unique primary key value for each occurrence of a table (IDgen=N), or TIBCO Object Service Broker generates a value for the primary key field of each occurrence (IDgen=Y).
The section of the Screen Table Painter or Report Table Painter used to paint literal text and data fields. It visually represents a screen table or a report table.
A table that is used to import data from an external environment into TIBCO Object Service Broker. It has a table type of IMP.
A method used when writing rules that enables the identification of objects (tables, screens, rules, and fields) to be deferred until runtime. This allows table names and field references to be stored in tables and/or to be obtained from rules arguments.
A transaction involving an external DBMS or peer TIBCO Object Service Broker system that could not be completed. In-doubt transactions are kept in the contingency log until the update is confirmed by the other system(s), then written to the redolog.
A rules library that contains production rules developed by your installation. SITE is the default name of this library.
1) A member of a class of objects. For example, the EMPLOYEE table is an instance of a table object.
2) In a table with data parameters, all the data associated with a particular set of parameter values. For example, #RECEIPTS(79912, 06-03-1998) is an instance of the #RECEIPTS(employee#, batchdate) table.
A client facility that allows programs written in Java to access TIBCO Object Service Broker. The SDK (Java) client can be in a different address space than the server, which is the SDK (C/C++) server. See also
Call Level Interface and
SDK (C/C++).
1) As used in Promotions, the grouping method used to implement group promotion rights. 2) See
rule library.
A command used in the line command field denoted by an underscore (_) at the left or right of each line. These commands perform various functions on an object in the list, depending on which screen you are using.
A field that cannot be modified by a user, contains only text, and cannot have data inserted into it.
A variable declared within a rule. Its scope is the rule where it is declared and descendant rules in the same transaction.
The portion of a user’s environment that is sensitive to the cultural conventions of a particular language, country, or territory. The value defined for the locale establishes the language used for data manipulation and storage within a Data Object Broker.
A table used to map the contents of memory to fields. Before a MAP table is instantiated, its size and scope must be pre-allocated by a TIBCO Object Service Broker application request.
A list of options created through DEFINE_MENU that are presented on a screen. A menu can be part of an application, a login screen for users, or an individualized login screen.
A line at the bottom of TIBCO Object Service Broker screens. Messages generated by the system, and by user-written rules, can appear on this line.
A collection of messages generated by a transaction. There are two types of message logs: a system log and a user log containing output directed by a user-written rule.
An active store for all metadata: all definitions, characteristics, access paths, and storage locations of all objects in TIBCO Object Service Broker. Each Data Object Broker has its own MetaStor.
In z/OS environments, this refers to a VTAM- and TCP/IP-based Execution Environment. In non-z/OS environments, this is another name for the Execution Environment that provides online transaction processing. See
Execution Environment.
The name associated with a Data Object Broker. In a distributed environment it is used to identify a Data Object Broker to another Data Object Broker.
A field defined to a report or a screen in such a way that it does not display on the report or screen. It can be used to store data used by other fields and rules.
A development environment where users can save modifications they made to an object, even if the promotion rights of the object are held by someone else.
An instance of an entity recognized by TIBCO Object Service Broker, such as libraries, screens, reports, tables, and rules.
A tool that displays the contents of a table (usually a list of objects), and allows a customized set of commands to operate on the display.
A collection of TIBCO Object Service Broker objects grouped together using the Object Set Definer, which can be managed as a single entity. It can be treated as a single object for the purposes of defining security and in selection criteria for promotions. An object set can contain a TIBCO Object Service Broker object, including other object sets.
See TIBCO Object Service Broker Communications Support.
1) An entity that can be applied to one or more operands to yield a result. 2) The person responsible for monitoring system operations and communicating with the operating system.
A display console that is used by an operator to communicate with the system. It is used to monitor system operations and specify information about application programs and I/O operations.
The section of the Report Generator screen that displays valid options for each field on the screen in succession. You can select any of these options as values for a field. This section appears in the lower portion of most Report Generator screens.
As used in Security, each object in TIBCO Object Service Broker has a user ID assigned as its owner, initially the creator of the object. The owner can access and delete the object, manage permissions to the object, and transfer ownership. System administrators and the owner’s security administrator share ownership privileges with the owner.
A data set (on z/OS) or a file (on Windows or Solaris) that holds TIBCO Object Service Broker data. Page data sets and page files are grouped within individual segments and stored in the Pagestore.
A value that logically partitions data in a table. In a distributed data environment, it is also used to partition data by location (TIBCO Object Service Broker node).
A type of TIBCO Object Service Broker table that lists the different data parameter values for a given table. The table type is PRM.
peer TIBCO Object Service Broker
A Data Object Broker that communicates with one or more other Data Object Brokers in a distributed data environment.
A server used in a distributed data environment to connect peer TIBCO Object Service Broker systems.
As used in Security, the object type specifies access rights to an object. These access rights are specified by designating which subset of access modes are to be allowed on the object or type.
A command used in the primary command field of a screen. These commands perform various functions on the entire screen, depending on which screen you are using.
A field whose values uniquely identify occurrences of a table. See also
composite primary key.
A field whose values you want to print on a report. Normally used in conjunction with a break field.
A person responsible for administering the promotion of application code, and applying the changes submitted by developers.
A transaction started using the DISPLAY & TRANSFERCALL statement that allows the data displayed for a screen and the screen context to be maintained, but terminates the current transaction and starts up a new transaction. To the user, it appears to be a conversational transaction. Pseudo-conversational transactions are used to minimize resource usage.
A field that references another table to verify values that a user can insert, or in the case of user or automatic prompting, displays values from which a user can select.
A table whose primary key is used as verification for values that a user can insert or add to another table where the reference table is specified in the definition.
As used in Promotions, in the case of a disposition mismatch this allows the change request being promoted to take on the disposition of the target system.
A set of client and server facilities that enable programs written in third-generation languages to access TIBCO Object Service Broker. The server portion of the interface can be in a different address space than the client portion. See also
Call Level Interface and
SDK (Java).
A term sometimes used in Promotions to describe a consolidated change request.
A collection of attributes for a report that includes its name, component report tables, and the attributes of the report tables.
A table used to present report data. It is defined to a report and can be shared with other reports. The report table can be a title report table, a body report table, or a break table. It has a table type of RPT.
A stored list of all the tables defined in TIBCO Object Service Broker that contains pointers to where more information is stored about the data and the indexes for the tables. It is abbreviated as RTIX.
As used in Promotions, a development environment where only one person (user-restrictive), or one group (group-restrictive), has promotion rights to an object. In a user-restrictive environment, objects held by the user cannot be modified by other users. In a group-restrictive environment, objects held by the group cannot be modified by others outside of the group.
As used in Promotions, the permission provided by TIBCO Object Service Broker to a user or group to modify an object after the object is promoted. Only user IDs with borrower status can obtain rights to an object. The type of development environment determines the rights enforced. See also
restrictive environment.
During transaction processing, an action that causes changes to the database to be discarded. The database is returned to the state it was in at the previous committed action. This action occurs as part of abnormal termination of a transaction, or can be explicitly initiated with the ROLLBACK statement.
A program that is written in a programming language other than TIBCO Object Service Broker rules. It can be called from within a rule. It is also known as a builtin.
See resident table index.
An external database gateway written in the rules language, for example, the TIBCO Service Gateway for CA-Datacom. It operates from within a Native Execution Environment.
The TIBCO Object Service Broker programming language. A high-level language that consists of a set of data access, assignment, and control statements.
A TIBCO Object Service Broker library that contains rules. The three types of rules libraries are: local, installation, and system. The user session options determine the search order for the libraries.
A TIBCO Object Service Broker-defined screen built from screen tables. It appears in text mode.
A collection of attributes for a screen that includes its name and component screen tables.
A table used to display data on a screen. It is defined to a screen and can be shared with other screens. It has a table type of SCR.
See security administrator.
A structure for retrieving table occurrences based on the values in a secondary key field rather than the primary key. This can improve performance because only the secondary index structure is searched instead of the entire table.
A predefined field (or set of fields) that can be used to retrieve data through a secondary index. A secondary key is not used to order data.
As used in Security, a privileged user who shares ownership of objects with his or her subjects. Security administrators are usually allowed to create, update, and delete user IDs, depending upon the authorities specified in their SecAdmin profile. See
subject.
As used in Security, a set of users who, during a TIBCO Object Service Broker session, can operate out of any group in which they have membership. They can also choose not to operate out of a group. When users operate out of a security group, they are able to share objects and share access rights to those objects unless access is specifically overridden by the security permissions for their user ID.
An explicit grouping of page data sets/files within the Pagestore. A segment holds only TDS data. Segment 0 holds the MetaStor.
See external database server.
A unit of resources allocated to a user when the user connects to an Execution Environment and Data Object Broker, thereby enabling the user to run transactions in TIBCO Object Service Broker. The resources are released when the user exits from TIBCO Object Service Broker.
A TIBCO Object Service Broker program that enables a user to run one or more transactions. The transactions can be chosen from a TIBCO Object Service Broker developer workbench, administrator workbench, or a user-defined menu.
User specifiable options that determine the characteristics of a TIBCO Object Service Broker session. In most cases, default values apply if no user specification is made.
A memory-resident table whose data persists for the life of a TIBCO Object Service Broker session. It has a table type of SES.
A class library of actions or methods for use in application development. These are developed by and shipped with TIBCO Object Service Broker.
A number displayed in the system message log that identifies the rules statement where an error occurred. Statement numbers disregard action sequence numbers and refer to each statement in the rule.
As used by Security, a user under the responsibility of a given security administrator. Security administrators have ownership privileges to all objects owned by their subjects.
A table that is based on the data of another table (a source table). It can consist of selected fields of the source table, derived fields, or both. It has a table type of SUB.
The field used to determine how data is to be summarized. A new report line is printed for every change in value of a summary field.
A type of report where a print line is produced when a summary field changes its value. In a non-summary report, a print line is produced for every body table occurrence.
A Unicode representation of a single abstract character that consists of a sequence of two 16-bit code units.
1) As used by Security, a user with the highest security clearance (level 7). The system administrator has full access to all objects in the system, can grant or revoke access privileges, add, delete, or change users, and appoint security administrators and other system administrators. 2) An individual who maintains the TIBCO Object Service Broker system.
A rules library that contains system rules developed by and shipped with TIBCO Object Service Broker. COMMON is the default name of this library.
Interface through which a rule can access and update an occurrence in a table. Information is placed in the buffer with assignment, GET, or FORALL statements.
The description of a table including its type, parameters, if any, field names and attributes, and event rules, if any.
All table occurrences that are associated with a specific parameter value (for a table with a single parameter), or a specific set of parameter values (for a table with multiple parameters).
The notation used within rules to identify a specific field within a specific table when processing data. This is the reference notation used for all the types of TIBCO Object Service Broker fields and tables.
A type of table used to store data in the TIBCO Object Service Broker database. The MetaStor is stored as TDS data. TDS is the default table type.
A protocol that is a subset of the Telnet protocol, which provides a general bi-directional, eight-bit byte oriented means of communication. It is primarily used to connect terminal devices with terminal-oriented processes. The name Telnet 3270 protocol refers to the implementation of transferring 3270 display information using Telnet capabilities.
A table whose data is available for the life of a transaction. At the end of the transaction, the data is discarded. It has a table type of TEM.
A state that causes changes to tables that are initiated by a user-written rule to be in effect only for the duration of the transaction. When the transaction ends or a COMMIT is issued, the updates are discarded.
A component of TIBCO Object Service Broker that presents a single, consistent, and general purpose Application Program Interface (API) to higher-level TIBCO Object Service Broker components that require the use of varied communications facilities. Formerly called Huron Communications Support (HCS).
An Eclipse-based graphical interface for creating and modifying TIBCO Object Service Broker and Object Integration Gateway objects.
The table that comprises the top or bottom titles of a report. Title report tables bracket the body report table but are defined independently of it.
The first <nn> rows of a screen table that do not scroll vertically.
A unit of processing that acquires locks, allows database synchronization points within the processing unit with the COMMIT and ROLLBACK statements, and binds object definitions until the end of the processing unit. Resources are released when the transaction ends.
The depth at which a transaction is nested. The first nested transaction is at level two. Transactions executed by another transaction are nested one level deeper, that is, higher in number, than their parent.
An encoding scheme for Unicode. TIBCO Object Service Broker uses UTF-16BE (Big Endian) internally. In this encoding, characters occupy either 2 or 4 bytes. All characters in common usage occupy 2 bytes in this scheme. Other transformations are supported as external syntaxes.
A method of accessing tables so that data is locked to maintain data integrity when changes are made to the data.
A person or entity, such as another process, accessing TIBCO Object Service Broker through the Execution Environment or Display Client.
An event defined by the application developer to be triggered by a user action. A user-defined event can call a shareable tool or be redirected to a system-defined event. These events are used in graphical applications.
A standard menu that groups a number of TIBCO Object Service Broker tools and user applications, in any combination, so that a user has ready access to them. There are two standard workbenches supplied with TIBCO Object Service Broker: STANDARD and @ADMIN. Custom workbenches can be created using the DEFINE_MENU tool. A user’s security profile determines which workbench appears when the user logs in to TIBCO Object Service Broker.