The Database Specifications screen is used to specify database options for a dialog, such as the:
Sample Screen
Database Specifications Dialog NAME1 Version 1 Subschema . . . . . . . . . . . . ________ Schema . . . . . . . . . . . . . ________ Version . . . . . . . . . . . . . ____ Access Module . . . . . . . . . . NAME1 SQL Compliance . . . . . . . . . _ 1. ANSI-standard SQL 2. FIPS Date Default Format . . . . . . . _ 1. ISO 2. USA 3. EUR 4. JIS Time Default Format . . . . . . . _ 1. ISO 2. USA 3. EUR 4. JIS Enter F1=Help F3=Exit F4=Prev F5=Next
Field Descriptions
Displays the name of the current dialog, as specified on the Main Menu screen. This field is protected.
Specifies the version number, in the range 1 through 9999, of the current dialog. This field is protected.
Specifies the 1- to 8-character name of the subschema associated with the current dialog.
The specified subschema must be defined in the data dictionary. If no subschema is specified, the dialog cannot perform database access.
Specifies the 1- to 8-character name of the schema with which the named subschema is associated.
If the named subschema is associated with more than one schema or version of a schema, a schema name must be specified. If the named subschema is associated with exactly one schema and version, Schema defaults to the name of that schema.
Specifies the version number, in the range 1 through 9999, of the named schema. If no version number is specified, version defaults to the version of the named schema that was most recently defined.
Specifies the 1- to 8-character name of the access module associated with the current dialog. The access module need not exist when the dialog is compiled, but it must exist at runtime if the dialog accesses a database with SQL DML (other than dynamic SQL). If the dialog will not require an access module to be loaded at runtime, clear this field.
The dialog process logic can override the specification on this screen at runtime by issuing a SET ACCESS MODULE statement.
If you do not change the value in this field, the default value assigned by CA ADS is the dialog name. If the dialog was copied from another dialog, the default value is:
About Access Modules
An access module is the executable form of the SQL statement that a program issues. When an access module is created, CA IDMS/DB automatically determines the most effective access to the data requested by the SQL statements. The CA IDMS access module compiler incorporates the access strategy in the access module, which is stored in the catalog component of the dictionary.
An access module is defined with a CREATE ACCESS MODULE statement in an SQL session, and it is associated with an SQL schema. It is built at runtime for the dialog if it is specified for the dialog on this screen and it has been created. Under CA IDMS internal security, ownership of the schema qualifying the access module affects authority to use the access module.
Note: For more information on creating and executing access modules, see:
Specifies the SQL standard you are enforcing. If you select neither ANSI-standard SQL nor FIPS, the default is CA IDMS extended SQL.
Note: For more information on SQL standards, see the CA IDMS SQL Reference Guide.
Specifies the external date representation format. The date format can be one of the following:
Specifies the external time representation format. The time format can be one of the following:
Note: For more information on date/time representations, see the CA IDMS SQL Reference Guide.
|
Copyright © 2014 CA.
All rights reserved.
|
|