The following topics are covered:
This version of Predict supports further enhancements added to Adabas Version 8.3 on Mainframes.
For a detailed description of new features, refer to the following sections:
With Adabas Version 8.3 on Mainframes it is possible to store the security system user ID (SECUID) in system fields in an Adabas file. This functionality can be documented in Predict also with the new system field value SC.
Refer to DBMS Extensions in the section Field of the Predefined Object Types in Predict documentation.
This version of Predict supports DB2 Version 11.
For a detailed description of new features, refere to the following sections:
The DB2 archive table name can now be provided when documenting a DB2 table in Predict. This archive table is then automatically generated and connected to the base DB2 table.
If you want to use an archive table with an index of its own then this archive table must be documented separately in Predict. Indexes can then be defined manually where required. However, if an archive table is documented separately in Predict, it is also necessary to generate it separately.
Refer to DB2 Table/View in the section Generate for DB2 of the Predict and Other Systems documentation for special considerations concerning the generation of temporal tables.
Refer to DB2 Table, File Type D in the section File of the Predefined Object Types in Predict documentation for further information on the documentation of archive tables in Predict.
It is now possible to define indexes that exclude NULL
keys.
NULL key columns add to the size of an index and can
reduce the performance of index scans. If you exclude NULL key
columns from an index, index entries are only created for key columns that are
not null.
Refer to DBMS Extensions in the section Field of the Predefined Object Types in Predict documentation.
For fields of DB2 tables (field types A, AL and AV) you can now specify
an as-generated-expression-clause. This
is documented in Predict using the corresponding option in the
Base
Extensions of such fields. The value provided in
Generated
expression is the expression that is evaluated by DB2 when
generating the value of the field.
You can now specify the COMPRESS and LOGGED
option for DB2
tables.
For history tables you can now specify an additional setting
("E" - History add extra row) to document the usage
of a history table with the ON DELETE ADD EXTRA ROW option in
Predict.
Refer to DB2 Table, File Type D in the section File of the Predefined Object Types in Predict documentation for further information.
You can now specify the PCTFREE FOR UPDATE setting via the
Definition
of Using/Free Clause of DB2 tablespaces in Predict.
There is a new option "Document as table" to incorporate views or materialized-query tables in Predict as files of type D.
This incorporation option can be used if you are not interested in the derivation of a view from the underlying base table or if the used query involves the usage of compiled SQL scalar or table functions.
This incorporation option is also available in batch mode.
Arrays can be used as parameters or return values of functions. When generating such a function, the appropriate type definitions will also be generated. See also Documenting Other DB2 Objects.
Inplace Conversion will allow you to skip versions when converting to a newer version of Predict.
For example, you will be able to execute an inplace conversion from Predict Version 4.6 to Predict Version 8.n (where n > 2) directly without converting to Predict Version 8.2 first.