Setting Defaults › Integrated Data Dictionary Options

Integrated Data Dictionary Options

Table 15 presents the options available through IDD and the statements that control the options.

Table 15. CA OLQ Options Set With the IDD ADD/MODIFY/DELETE USER Statement

Special considerations for the options available through IDD are presented below.

Note: For complete syntax and syntax rules, see the CA IDMS IDD DDDL Reference Guide.

OLQ:

You can allow users to distribute authority in IDD with the IDD USER statement. USER statement clauses are used to control access to CA OLQ qfiles and subschema views and to assign CA OLQ command authorities and processing and reporting options when the default processing options for the session include SECURITY FOR OLQ IS ON.

If OLQ is specified, the keyword UPDATE must be specified in the FOR clause of the ADD USER statement.

Access to ASF tables:

You can create, replace, modify, and delete ASF tables.

You use the IDD DDDL source statement USER to set the access switch to OLQ:

OLQ ACCESS IS OLQ

OLQ is the default.

The OLQ setting also allows you to use the SELECT statement with the following entities:

• ASF tables
• Logical records
• Database records
• Sequential files (batch only)

Access to SQL tables:

You can create, replace, modify, and delete tables which are associated with an SQL schema.

You use the IDD DDDL source statement USER to set the access switch to IDMS:

OLQ ACCESS IS IDMS

Note: For information on the USER statement, see the CA IDMS IDD DDDL Reference Guide.

Subschema access:

You can specify whether the user does or doesn't have access to a particular subschema. CA OLQ uses the DC/UCF signon ID and password of the user to determine which subschemas are available. Subschema security is enforced on a dictionary-by-dictionary basis.

Signon profile qfiles and users:

You can associate a signon qfile with a subschema. The signon qfile executes when a user signs on to the subschema.

You use the IDD DDDL source statement entity USER to associate a signon profile with a specific user. The specific clause of the ADD USER statement is:

SIGNON PROFILE IS module-name
LANGUAGE IS OLQ

Module-name refers to the name of the saved qfile.

Access to qfiles:

You can allow users to access only certain qfiles by naming the qfiles in the user's ADD USER statement, using the clause:

INCLUDE/EXCLUDE ACCESS TO QFILE qfile-name

Executing qfiles:

Use IDD to specify whether or not specific users are allowed to execute qfiles in general. The IDD statement that applies to this option is the following clause of the ADD USER statement:

QFILE IS ALLOWED/NOT ALLOWED/ONLY

With the ONLY option of the above clause, you can specify that the named user can access CA OLQ only through qfile execution. If you want the user to access CA OLQ only through qfiles, we recommend that you also specify MENU MODE IS DISALLOWED to keep the user from retrieving through menu mode.

Menu mode:

This security option assigns or denies access to the CA OLQ menu mode facility as follows:

• ALLOWED (default) authorizes the CA OLQ user to access CA OLQ in command mode and menu mode.
• NOT ALLOWED authorizes the CA OLQ user to access CA OLQ in command mode only.
• ONLY authorizes the CA OLQ user to access CA OLQ in menu mode only.

The IDD statement that applies to this option is:

MENU MODE IS ALLOWED/NOT ALLOWED/ONLY

Saving qfiles:

You can specify whether or not you want the user to be able to save qfiles after creating them with the following clause of the ADD USER statement:

QFILE SAVE IS ALLOWED/NOT ALLOWED

Retrieving multiple records:

This security option specifies whether the user can retrieve multiple record occurrences with a single CA OLQ command. To use the SELECT (IDMS access mode) statement, the user must be assigned authority to retrieve multiple record occurrences.

The IDD statement that applies to this option is:

MRR IS ALLOWED/NOT ALLOWED

Interrupt count:

Each user in CA OLQ has the ability to set an INTERRUPT COUNT during a CA OLQ session. The interrupt count is the number of records that can be retrieved before the system interrupts processing. As the DBA, you can specify whether the user is allowed to select the NO INTERRUPT option with the IDD option:

MANDATORY/OPTIONAL INTERRUPT

If you set MANDATORY INTERRUPT, the user cannot choose the NO INTERRUPT option in CA OLQ. If you set OPTIONAL INTERRUPT, the user can choose the NO INTERRUPT option in CA OLQ. When the NO INTERRUPT option is in effect, the default interrupt count set during system generation is used to perform commit checkpoints.

Sorts:

When you specify:

SORT IS NOT ALLOWED

keep in mind that you are prohibiting sorting in OLQ SELECT commands.

Setting CA OLQ default options:

The CA OLQ default options allow you to tailor the CA OLQ environment. These options come into effect at user signon regardless of the security status. The CA OLQ default options include:

• HEADER/NO HEADER specifies whether CA OLQ report files contain a header line. This option has no effect on single-record-occurrence retrieval displays.
• ECHO/NO ECHO specifies whether a user-entered command will be repeated by CA OLQ on the output device.
• ALL/NONE specifies whether the default internal field list for all records retrieved during the user's CA OLQ session will contain all or none of the fields. Menu mode always defaults to none; no fields are preselected.
• FILLER/NO FILLER specifies whether filler field values are displayed.
• INTERRUPT/NO INTERRUPT specifies whether the processing interrupt feature for multiple record retrievals is enabled or disabled.

  Note: The MANDATORY INTERRUPT specification takes precedence over NO INTERRUPT.

  If INTERRUPT is specified, CA OLQ breaks processing after the specified number of records has been retrieved. If NO INTERRUPT is specified (as long as OPTIONAL INTERRUPT has been specified), the interrupt count is used for commit checkpoints.

• WHOLE/PARTIAL specifies the content of displayed path retrieval report lines. WHOLE displays only those lines containing a retrieved occurrence for every record type in a path definition. PARTIAL displays all lines, whether or not they contain data for every path record type. SELECT (OLQ access mode), and therefore menu mode, doesn't build partial lines.
• FULL/SPARSE specifies the format of displayed path retrieval report lines. FULL displays data associated with a record type once for each retrieved occurrence. SPARSE, used with a SELECT command, displays only the first of a repeating data value; SPARSE, used with a path command, displays only the first of a repeating record type.
• OLQ HEADER/NO OLQ HEADER specifies whether CA OLQ is to use predefined headers as columns headers in the report. This option has no effect on single-record-occurrence retrieval displays.
• COMMENTS/NO COMMENTS specifies whether comments accompany the output from HELP RECORDS, HELP SUBSCHEMAS, and HELP QFILE requests.
• CODETABLE/NO CODETABLE specifies whether CA OLQ accesses a code table to encode and decode data.
• PATHSTATUS/NO PATHSTATUS specifies the conditions under which CA OLQ will retrieve a logical record. NO PATHSTATUS requests CA OLQ to retrieve a logical record only when the path status of LR-FOUND is returned. PATHSTATUS requests CA OLQ to retrieve a logical record when any DBA-defined path status is returned.
• EXTERNAL PICTURE/NO EXTERNAL PICTURE specifies whether CA OLQ will use external pictures for displaying data.
• VERBOSE/TERSE controls the amount of information displayed following record and field-level breaks.