Identifies a database name table defined to the dictionary. You must specify the database name table if you have not established a current database name table as described in 7.3.3, "Entity Currency" earlier in this chapter.
Specifies a unique database name in the database name table. Db-name is a 1- to 8-character value that follows the conventions described in 7.3, "Naming Conventions". It cannot be the reserved keyword '*DEFAULT'.
Specifies that the database name is intended for use by application programs.
Specifies that the database name is intended for administrative purposes only.
Specifying MIXED PAGE GROUP BINDS ALLOWED on a DBNAME statement allows a rununit accessing the DBNAME to bind to areas with a mixture of page group and radix values. If not explicitly specified, a rununit binding to a DBNAME whose segments have different page groups will fail if the subschema being used includes areas with different page groups. The default is NOT ALLOWED.
Note: This option applies only to non-SQL-defined databases. Mixedpage group access is always ALLOWED for SQL-defined databases.
Specifies whether or not a check will be made at bind rununit time to ensure that no chain sets included in the subschema cross page group boundaries. If VERIFY OFF is specified, it is your responsibility to ensure that this condition is met. The default for VERIFY is OFF.
Notes:
Specifies that the subschema name passed with the BIND RUN-UNIT statement does not have to be present in the database name definition. OPTIONAL is the default.
Specifies that the subschema name passed with the BIND RUN-UNIT statement must be present in the database name definition. If the subschema name is not present, the bind is rejected.
Associates a segment with the database name. ADD is the default. You have to add at least one segment to a database name definition.
Disassociates a segment from the database name.
Identifies a segment to be added to or dropped from the database name definition.
Adds or updates a subschema mapping associated with the database name. This clause either maps the subschema name passed in a BIND RUN-UNIT statement to the name of a corresponding subschema that CA IDMS/DB will use to access the database or it specifies that the subschema mappings associated with the DBTABLE statement are to be used in determining the database name to be accessed.
Note: New subschema mappings are added at the end of all existing mappings associated with the database name.
Specifies the name of a subschema passed in a BIND RUN-UNIT statement. You can use wildcards to specify the subschema name as described below under "Usage".
Specifies the name of a subschema to which CA IDMS/DB maps the subschema named in the BIND RUN-UNIT statement. You can use wildcards to specify the subschema name as described below under "Usage".
Selects an alternate database name using the subschema name passed on the BIND RUN-UNIT statement and the subschema mapping rules associated with the DBTABLE statement.
Remove a subschema mapping from the database name definition. Ssc-name-1 must be the same as that specified in a subschema mapping associated with the database name.
Removes all subschema mappings from the database name definition. This can be useful when the subschema mappings must be reordered. You can drop all mappings and then re-add them in a different order.
Displays or punches details about the database name.
Displays or punches:
Displays or punches all information about the database name. ALL is the default action for a DISPLAY or PUNCH verb.
Displays or punches the name of the database name.
|
Copyright © 2014 CA.
All rights reserved.
|
|