$ DBO/DUMP database-name/SUB-SCHEMAS=sub-schema-name/OUTPUT=filename
$ PRINT filename

Additional Reference

Refer to the Oracle CODASYL DBMS documentation set for more information.

Examples

1. This example references the default subschema in the PARTS database:

   DB DEFAULT_SUB-SCHEMA WITHIN PARTS.

2. This example references the NEW database that contains the PARTS schema and the PARTSS1 subschema:

   DB PARTSS1 WITHIN PARTS FOR "DB1:[COBOL88]NEW.ROO".

3. This example references the default subschema in the PARTS database through the stream STREAM1.

   DB DEFAULT_SUB-SCHEMA WITHIN PARTS THRU "STREAM1".

Function

The Keeplist Description entry names a keeplist.

keeplist-name

is a user-defined name.

integer

is a positive integer.

Syntax Rules

1. The LD entry can appear only in the Subschema Section following the DB entry or another LD entry.
2. The LIMIT clause is for documentation only. The compiler ignores this clause.

General Rules

1. Keeplist-name implicitly has the global attribute. Any program defining the name, and any program contained within that defining program, can reference keeplist-name.
2. A keeplist is a table containing an ordered list of database key values.
3. At program initiation, each existing keeplist is empty.
4. A KEEP or a FIND ALL statement adds a database key value to the end of keeplist-name. FIND ALL can add multiple database keys to a keeplist.
5. A FREE statement selectively removes a database key value from keeplist-name.
6. A keeplist with zero entries is called an empty keeplist. The order of the entries in the keeplist reflects their sequence of insertion. As entries are added, the cardinality increases. As entries are removed, the cardinality decreases.
7. A COBOL program can reference a keeplist entry by using a database key identifier.
8. The Database Control System (DBCS) creates and maintains all keeplists.
9. Each value in keeplist-name represents a database record in the database.
10. A keeplist can contain the same database key value more than once.
11. More than one keeplist can contain the same database key value at the same time.
12. No other run unit can update a record whose database key value is in a keeplist. Every entry in the keeplist causes the DBCS to perform a retrieval lock on the record it identifies. The record remains locked until the entry is freed, or until the program executes a COMMIT (without the RETAINING option) or ROLLBACK statement, or until the program terminates. If another run unit references a locked record, the DBCS forces the run unit to wait until the record is unlocked.

Additional Reference

• Section 4.4, on database key identifiers

Example

The following example defines three keeplists to navigate through the PARTSS1 subschema: KEEP-COMPONENT, K-EMPLOYEE, and KL-ID:

DB PARTSS1 WITHIN PARTS.
LD KEEP-COMPONENT.
LD K-EMPLOYEE.
LD KL-ID.

The Procedure Division of your COBOL database programs may contain declarative and nondeclarative procedures. These may include:

• Directive and imperative statements
• Conditional statements
• Database key identifiers
• Explicit and implicit scope terminators
• Section 4.6, on record selection expressions

There are four types of COBOL statements:

• Compiler-directing statements specify an action taken by the compiler during compilation.
• Imperative statements specify an unconditional action taken by the object program at run time.
• Conditional statements specify a conditional action taken by the object program at run time; the action depends upon a truth value that is generated by the program. (A truth value is either a yes or no answer to the question, "Is the condition true?")
• Delimited-scope statements specify their explicit scope terminator.

Table 4-1 shows the three types of COBOL statements (conditional, imperative, delimited-scope) that are considered particularly relevant to database programming.

( 1 ) Without the optional [NOT ] ON ERROR phrase
( 2 ) Without the optional [NOT ] AT END or [NOT ] ON ERROR phrase

Like statements, COBOL sentences also can be compiler-directing, imperative, or conditional. Sentence type depends upon the types of clauses the statement contains. Table 4-2 summarizes the contents of the three types of COBOL sentences. The remaining text in this section discusses each type of statement and sentence in greater detail.