![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Task C: Add Control InformationUse the Core screen to add or delete additional control information in your definition. To access this screen, press PF4 from the Table Definition screen.
USR40 N N 0
The user unit with which the table is associated is entered here by default. The Unit marks the table as belonging to a particular application or to a logical unit. This value can be changed. The default unit for your user ID is specified in your TIBCO Object Service Broker user profile.A valid entry is a character string up to eight characters long. Valid units can be provided by your system administrator. Whether the table definition is bound (Y) or not bound (N). For more information, refer to Binding DAT Table Definitions and TIBCO Object Service Broker Application Administration. Use this section of the Core screen to define a location parameter for the DAT table. A location parameter is required only if you want to access Datacom data through a peer server associated with a different Data Object Broker (remote node). If you do not require a location parameter, position your cursor in this section and press PF16 to delete the parameter.If you always access the CA Datacom table remotely, the node from which you request the access can have either a minimal or a full definition.The name of the remote node where the full definition is located must be supplied through the use of the Default field, Src field, or Src and Sourcename field. Data parameters are defined on the full definition, not a minimal definition.A minimal definition with a location parameter means you always access data at a remote node. The table type specified in a minimal definition does not have to match the table type of the full definition on the remote node.A full definition with a location parameter indicates you can access data at either the local node or a remote node.The table type specified in a full definition must match the data on the local node. For example, a full definition of type TDS used to access TDS data on the local node can also be used to access a DAT table with the same name on a remote node.TIBCO Object Service Broker Managing Data for more information on location parameters, event rules and minimal table definitions.Using the event rule feature, you can provide additional controls over access to a table. To provide these controls you define event rules based on defined accesses. These accesses can be one of the following, for each rule:
The event rules are always called when the table is accessed in the access type specified. All the rules that apply to a specific access are executed in the order in which they are entered in the event rule section. They cannot access tables on a remote node. You can define two types of event rules, as follows:
Verify the value of an occurrence when the table is being modified, such as checking the validity of a field value Cause additional processing to take place when a table is accessed. For example, a trigger rule can be used to create an audit trail or update other tables.The event rule information is entered in the scrollable event rule section. To define event rules, position your cursor in this section and press PF4. Complete the following fields:
Type in a line number, starting at 1 for the first line, with one event rule per line. The line numbers must be numbered consecutively.
• V — Validation rule. No database updates are allowed during the validation process. The rule must be a function that returns Y (yes), the validation was successful, N (no), the validation was not successful, or a message explaining why it was not successful.
• T — Trigger rule. No restrictions on coding other than that it must not be a function, it cannot change the contents of the triggering row, and it cannot use the TRANSFERCALL statement. Nested triggers are possible. The type of access (or manipulation) to be performed on the data, causing the event to be executed. See the table below for the valid entries.
TIBCO Object Service Broker Managing Data for more information on event rules.Although ordering of fields is possible, it is more efficient to use the ORDERED clause on a retrieval statement. However, to add ordering to your definition, use the scrollable ordering information section.
Restrictions: You will not be able to issue a GET on a table if you specify ordering in the table definition or on a GET statement.
Type in a line number, starting at 1 for the first line, with one field per line. Lines must be numbered consecutively.
Specify if the field is to be ordered in ascending or descending order. Rows are normally returned in primary key order. Valid entries:
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |