1 – CHARACTER_SET
Format
SET CHARACTER_SET character-set
1.1 – Parameters
1.1.1 – character-set
Specifies the type of characters to be used during the current
CDO session. Valid Character Set Names lists the valid character
set names.
Table 1-6 Valid Character Set Names
Character Character
Set Type Set Description
MCS DEC_MCS A set of international alphanumeric
characters
Kanji+ASCII DEC_KANJI Japanese characters as defined by
the JIS X0208:1990 standard, Narrow
Katakana characters, as defined by
the JIS X0201:1976 standard, and ASCII
characters
1.2 – Description
Specifies the valid characters that you can use for an element
name, the initial value field property, and in comments. You
must set the character-set parameter to DEC_KANJI when you use
Japanese with Oracle CDD/Repository.
If you omit the SET CHARACTER SET command, Oracle CDD/Repository
references the equivalence name of the CDD$CHARACTER_SET logical
as the character set for the session. If this logical is not
assigned, the default character set is DEC_MCS.
RESTRICTION
DEC_KANJI is not available through the CDO editor.
Oracle CDD/Repository accepts a maximum field and record name
length of 31 octets (31 characters for ASCII/MCS characters; 15
characters for Kanji and Narrow Katakana).
Oracle CDD/Repository accepts the following characters as the
field and record name when the character-set parameter is DEC_
KANJI:
o Kanji (Japanese characters as defined by the JIS X0208:1990
standard)
o Katakana (Japanese phonetic alphabet, Narrow Katakana, as
defined by the JIS X0201:1976 standard)
o ASCII characters (A-Z, a-z, _, $)
1.3 – Examples
CDO> SET CHARACTER_SET DEC_KANJI
In this example, the character-set parameter is DEC_KANJI to
support Japanese characters during the CDO session.
2 – CONTEXT
Format
SET CONTEXT [ context-name ] [ AUDIT IS /*text*/ ]
2.1 – Parameters
2.1.1 – context-name
Specifies the context you are setting. If you omit this
parameter, CDO sets the current context to null.
2.1.2 – text
Adds information to the history list entry. Valid delimiters are
/* */ or double quotation marks (" ").
You can use Japanese to document comments in the AUDIT clause for
a field. To do this, use the SET CHARACTER_SET command, and set
the character_set of the session to DEC_KANJI.
2.2 – Description
The SET CONTEXT command defines a context as the current context
and implicitly controls all versioned elements that you define
while the context is set.
A context is a nonversioned element. Do not include a version
number in the context name.
If the top collection associated with the context is undefined,
the SET CONTEXT command takes the element named in the next
command as the top collection for the context. An error occurs
if the next command is not a DEFINE COLLECTION command.
The context set remains the current context until you issue
another SET CONTEXT command, you delete the context, or you end
the CDO session.
As an alternative to the SET CONTEXT command, you can define
the CDD$CONTEXT logical name. Once set, this context becomes the
current context each time you access the repository. For example:
$ DEFINE CDD$CONTEXT "cdd$disk:[smith.rep]test_context"
2.3 – Examples
CDO> DEFINE PARTITION FIRST_BASELEVEL.
CDO> DEFINE CONTEXT DEVELOPMENT_CONTEXT.
cont> BASE_PARTITION FIRST_BASELEVEL.
CDO> SET CONTEXT DEVELOPMENT_CONTEXT
CDO> DEFINE COLLECTION COMPILER_C. 1
CDO> RESERVE COLLECTION COMPILER_C
CDO> DEFINE COLLECTION FRONT_END.
CDO> DEFINE COLLECTION BACK_END.
CDO> REPLACE COLLECTION COMPILER_C.
CDO> SET CONTEXT 2
CDO> DEFINE RECORD ISSUES.
In this example, the SET CONTEXT command sets the current
context and implicitly defines a collection as the top
collection. Subsequent definitions will be implicitly
controlled.
1 The DEFINE COLLECTION command sets the top collection for
the current context. All definitions made within the current
context are attached to the top collection. FRONT_END and
BACK_END are attached to COMPILER_C.
2 The SET CONTEXT command sets the current context to a null
value. ISSUES is uncontrolled and unattached because it is
defined outside a context.
3 – DEFAULT
Format
SET DEFAULT path-name
3.1 – Parameters
3.1.1 – path-name
Specifies a default repository directory. You cannot use wildcard
characters in this parameter.
3.2 – Description
The SET DEFAULT command establishes the default repository
directory for the current CDO session.
You can use a logical name that translates to a search list
as the path name in the SET DEFAULT command. After setting the
default repository area, commands that directly affect elements,
such as CHANGE, DEFINE, or DELETE, only operate on the first
occurrence of the element in the search list. However, the
DIRECTORY command searches through all the repository areas
specified in the search list.
3.3 – Examples
CDO> SET DEFAULT DISK:1[SMITH.DATA]REVIEW
In this example, the SET DEFAULT command sets the default
directory to the REVIEW directory in the DISK1:[SMITH.DATA]
anchor repository.
4 – KEY
Format
SET KEY qualifier
4.1 – Qualifiers
4.1.1 /STATE=key-state
Specifies the key state to be set.
4.2 – Description
The SET KEY command sets the current key state. See the DEFINE
KEY command description for information on the key states.
4.3 – Examples
CDO> SET KEY/STATE=ONE
In this example, the SET KEY command sets the key state to ONE.
5 – OUTPUT
Format
SET OUTPUT [ file-spec ]
5.1 – Parameters
5.1.1 – file-spec
Specifies the file to which CDO sends the output from CDO
commands.
5.2 – Description
The SET OUTPUT command defines where CDO sends the output from
CDO during a session.
If you specify a file with the SET OUTPUT command, CDO sends
output to the default output location (SYS$OUTPUT) for your
current process and to the specified file.
If you specify SET OUTPUT without a file specification, CDO sends
output only to the default output location.
The SET OUTPUT command stays in effect until you change it with
another SET OUTPUT command.
5.3 – Examples
CDO> SET OUTPUT
In this example, the SET OUTPUT command captures the output
from a CDO session and sends it to the default output location
for your process.
6 – VERIFY
Format
{ VERIFY }
SET { NOVERIFY }
{ }
6.1 – Description
The SET VERIFY command causes CDO to display all commands in a
command procedure before executing them. The initial setting is
off (NOVERIFY).
To override this default, you can issue the SET VERIFY command
at the CDO prompt before you process the command procedure. SET
VERIFY then remains in effect until you issue a SET NOVERIFY
command.
Alternatively, you can insert the SET VERIFY command as the first
command within your command procedure. SET VERIFY then remains in
effect until the command procedure finishes executing.
6.2 – Examples
CDO> SET VERIFY
CDO> @ON.CDO
In this example, the SET VERIFY command causes CDO to display
all commands in the ON.CDO command procedure as they execute.