Only available with Object Description.

Information stored in Predict objects can be used to generate external objects, and documentation objects can be incorporated from external objects. External objects generated from documentation objects and documentation objects incorporated from external objects are connected. Predict provides functions to administrate external objects connected to documentation objects. These functions are described in this section.

See the section Handling of External and Documentation Objects in this documentation for a more detailed description of how external and Predict objects are handled.

This document covers the following topics:

• Overview of Options

• Administrating External Databases

• Administrating External Dataspaces

• Administrating External Files

• Administrating External Programs

• Administrating External Storagespaces

---

Overview of Options

The following topics are covered below:

• Overview of Administration Functions

• General Rules

Overview of Administration Functions

Administration functions are used to perform the following tasks.

• Disconnect implementation - Disconnect command
  Disconnects external objects from their corresponding Predict objects. The implementation pointer from the documentation object to the external object is deleted, but the objects themselves remain intact.

• Display implementation - Report command
  Displays external objects.

  The following information is displayed:

  • Generated code.

• Purge implementation - Delete command
  Purges external objects. Any dependent objects are physically deleted. It is sometimes necessary to delete an external object before the connected Predict object can be deleted.

• Refresh file - Refresh External command
  Deletes all records stored in Adabas files, DB2 tables/views or Oracle tables/views.

General Rules

• External objects to be processed are identified by the Predict documentation object to which they are connected.

• If the Predict object was incorporated or connected with an Incorporation function, no generation protocol is stored in Predict.

Administrating External Databases

Functions

Disconnect implementation - Disconnect command

Disconnects implemented databases connected to the Predict database object by deleting the implementation pointer of the documentation object.

Display implementation - Report command

For DB2 databases: displays the generation log. For Adabas and IMS databases: only the implementation pointer is displayed.

Purge implementation - Delete command

For DB2 databases: Deletes the database and all dependent tablespaces, tables and views. The database ID must be entered again to confirm deletion. If a table holds the last reference to a distinct type, the distinct type is also deleted.

The function is not available for Adabas and IMS databases.

Administrating External Dataspaces

Functions

Disconnect implementation - Disconnect command

Disconnects tablespaces and Predict dataspaces by deleting the implementation pointer of the Predict dataspace object.

Display implementation - Report command

Displays the generation log.

Purge implementation - Delete command

Deletes the tablespace and all dependent tables and views. The dataspace ID must be entered again to confirm deletion. If a table holds the last reference to a distinct type, the distinct type is also deleted.

If dependent tables and views exist, they are listed. The deletion of these dependent objects has to be confirmed.

Administrating External Files

Functions

Disconnect implementation - Disconnect command

Disconnects implemented external object(s) from the Predict file object by deleting the implementation pointer of the file object.

Display implementation - Report command

Displays generated code.

Purge implementation - Delete command

Deletes generated code. If a DB2 table holds the last reference to a distinct type, the distinct type is also deleted.

Special rules apply when deleting Adabas files or DDMs:

Adabas files

The following rules apply:

• If the file to be deleted is in use, the Adabas option Stop user using file is used.

• If Predict/AOS Security is active, access rights are required to delete an Adabas file or to stop users using the file. See Protecting Adabas Databases and Files in the section Protecting External Objects in Predict with Natural Security in the Predict Security documentation.

DDMs

• For DDMs defined in Natural Security, access rights to maintain the security definition of the file in Natural Security are required. See Protecting DDMs in the section Protecting External Objects in Predict with Natural Security in the Predict Security documentation.

Refresh file - Refresh External command

Deletes all records stored in Adabas files, DB2 tables or Oracle tables. Data structure remains intact. Refresh operation must be confirmed.

Special rules apply when refreshing Adabas files:

• If the file to be refreshed is in use, the Adabas option Stop user using file can be used.

Administrating External Programs

Functions

Disconnect implementation - Disconnect command

Disconnects implemented external object(s) from the Predict program. The implementation pointer from the documentation object to the external object(s) is deleted, but the objects themselves remain intact.

Display implementation - Report command

Displays generated code.

Purge implementation - Delete command

Deletes the procedure/function in DB2.

Administrating External Storagespaces

Functions

Disconnect implementation - Disconnect command

Disconnects implemented external object(s) from the Predict storagespace by deleting the implementation pointer of the documentation object.

Display implementation - Report command

Displays generated code.

Purge implementation - Delete command

Deletes generated code.

A storagespace which is used by any tablespace or index space cannot be deleted. In this case, a list of all the tablespaces, tables and views used by the storagespace is displayed.