Adabas Vista Parameters

The maximun number of commands permitted against a source file. Any command that exceeds this number will result in an error code. The default value 0 indicates no limit.

The number of a database which identifies an Adabas Vista file. This number is used in conjunction with a source file number.

Note:
In Natural systems, this is the database number defined in a DDM.

The file number for an Adabas Vista file. This number is used in conjunction with a source database number.

Note:
In Natural systems, this is the file number defined in a DDM.

A unique name identifying a particular Adabas Vista file without referring to the source database and file number. The name must be unique across all published partitioned file definitions. The name must also be unique across all published translation rules.

(optional)

Controls the type of access for each partition of a partitioned file.

The following values are permitted:

• FULL: read/write access is permitted

• READ: read-only access is permitted

• ONLY: partition is set to FULL and all other partitions to NONE

• NONE: no access is permitted

See section Partition Restriction for more information.

The maximum Adabas ISN permitted for a partition.

Adabas Vista enforces the specified maximum during read and store processing.

The initial maximum is determined by the Maximum Number of Partitions / Default Partition TOPISN, established when the partitioned file is first defined.

This parameter may be used to provide a lower value in order to maintain specific partition sizes that may have been derived from recovery and maintenance considerations.

Note:
The Adabas TOPISN value is a limit on the maximum ISN for a partition and not the maximum number of records.

Indicates the action to be taken whenever a partition becomes unavailable.

Possible values are:

• YES: the user cannot tolerate the partition's unavailability. Normal user operation is interrupted when access is attempted (with the corresponding Adabas response code).

• NO: the user can tolerate the partition's unavailability. Data in that partition is ignored until the partition becomes available again. The partitions that return one of the partition unavailable response codes (17, 48, 148) when accessed are logged and can subsequently be identified using the CRITREP function of the Adabas Vista API.

See section Partition Outage for more information.

Indicates whether or not ISN positioning is to be used when an Adabas Vista ISN is provided as an optional start ISN for L2/5 and L3/6 commands or as a minimum ISN value for Sx commands.

If an L1 command with Command Option 2 set to I is issued with a starting Adabas Vista ISN of zero and this parameter is set to YES, reading begins from the first partition.

The maximum number of partitions available for use by a partitioned file.

Only those partitions relevant to current processing requirements need to be defined. However, the future requirements of the partitioned file must also be considered when determining the value for this parameter.

Because of the structure of the Adabas Vista ISN, this parameter directly affects

• the amount of space reserved in the ISN field for the Partition ID; and

• the default Adabas TOPISN for each partition.

The default Adabas TOPISN imposed by this parameter is calculated and displayed in order to help determine the correct balance between the maximum number of partitions and the resulting Adabas TOPISN partition limit.

The Adabas name, length, and format of the field used to distribute the data into separate partitions.

The partitioning field of a partitioned file can be a standard Adabas field, a descriptor, a superdescriptor, a subdescriptor, or a dummy field.

It may not be

• a multiple value field;

• an item in a periodic group;

• of format F, G, or W;

• a superdescriptor with one or more parents of format W;

• of variable length (length of zero in the FDT); or

• a field with the long alphanumeric (LA) attribute.

The Adabas UQ attribute is supported only for fields defined as the partitioning field, and only if the appropriate Adabas field name is defined with the UQ option in the Adabas FDT for each partition.

The specified Adabas short name, length, and format must be identical to its field definition in the Adabas FDT with one exception: if the partitioning field is a superdescriptor with format A (that is, one of its parent fields is defined with format A), then a format of B may need to be specified to enable correct specification of the Partitioning Field High Value, if any component of the superdescriptor cannot be represented by character values. The field formats may be obtained from either the full or demo version of Adabas Online System, or by running the Adabas ADAREP utility.

Note:
An optional name for the partitioning field may be provided in the "display as" field to make the partitioning field easier to identify.

This parameter is mandatory for each partition. It is used to specify the highest value of the partitioning field that can exist in the partition. The value must be specified in accordance with the defined partitioning field's format and length.

If the partitioning field's format has been defined as

• alphanumeric (A), normal alphanumeric values may be specified.

• packed decimal (P) or unpacked decimal (U), the decimal value must be preceded, if applicable, by a '-' or optionally a '+' sign.

• binary (B), the value must be specified in hexadecimal format (that is, two digits for each byte). In the case of a superdescriptor with a U or P format parent, the sign F or D must be used to indicate a positive or negative value, respectively.

A database number to which Adabas commands issued against an Adabas Vista partitioned file may be directed.

A file number to which Adabas commands issued against an Adabas Vista partitioned file may be directed.

A number that uniquely identifies a partition within a partitioned file.

The Partition ID is used together with the Adabas ISN to form an Adabas Vista ISN. This Adabas Vista ISN is returned to the application in place of the Adabas ISN.

The allocation of a Partition ID depends on the Partition ID Assignment of the partitioned file.

The actual maximum value of the Partition ID is determined by the Maximum Number of Partitions established when the partitioned file is first defined.

When such an Adabas Vista ISN is received from the application (for example, in the case of an update), Adabas Vista interprets the ISN and is able to redirect the update to the correct partition.

Refer to the section Adabas Vista ISN for more information.

Indicates whether Partition ID assignment is to be performed by Adabas Vista automatically or by the user manually.

User assignment, which requires that the user specify a Partition ID for each partition, may be useful when an application stores the Adabas Vista ISN as data and the likelihood exists that the structure of the partitioned file may change; for example, inserting new partitions or splitting current partitions.

Refer to the section Adabas Vista ISN for more information.

This parameter can be used to enable the Adabas Vista shared partition feature (also referred to as the multipart feature).

See also the section Partition Sharing.

This source file is an extreme file.

Extreme files can be adopted in one of three styles:

1. Extreme files for well-formed applications

   This is the simplest implementation style where your applications use classic references to current record (through *ISN in Natural for example) in all areas which allows Vista to always recognize the current partition for the current record without any special behaviors in the application.

   The parts of your applications that refer to records by ISN that are not known as the current record (if any) must be adjusted to use Vista APIs to identify the partition identity for the record.

   To select this style, specify source type E.

   For more information refer to Extreme files and well-formed application logic.

2. Extreme files by field

   Extreme files by field requires you to set aside a field in the FDT for transient use by Vista (no data is ever stored in this field inside Adabas) to identify the partition identity for the current record without any special behaviors in the application.

   The parts of your applications that refer to records by ISN that are not known as the current record (if any) must be adjusted to use Vista APIs to identify the partition identity for the record.

   To select this style, specify a source type other than S or E, and in the pop-up window mark "Extreme using special FDT field" and specify the corresponding Adabas short name where indicated.

   For more information refer to Field style extreme files.

3. Extreme files by ISN

   Extreme files by ISN requires all your application to use ACBX style Adabas commands when using the file. In addition, your applications must use the 8-byte ACBX-ISN (because Vista will use some of this to identity the partition). Any use of ACB style commands will be rejected, if Vista requires ACBX.

   To select this style, specify a source type other than S or E, and in the pop-up window mark "Restricted to ACBX-only style".

   For more information refer to ISN style extreme files.

Controls the placement of new records into a partitioned file.

When storing a record to a partitioned file, the value for the partitioning field is extracted from the Adabas record buffer and used to direct the new record to the correct partition: this is termed normal placement. For store operations that do not specify a partitioning field or provide a null value for it, Store Control Option may be used to direct the record to a partition.

The number of concurrent Adabas Command ID sequences that a user may have outstanding for each partition.

The number of the database to which an Adabas command that is subject to an Adabas Vista translation rule is to be re-directed.

The number of the file to which an Adabas command that is subject to an Adabas Vista translation rule is to be re-directed.

When resolving a source file into a translation target (by reference to the translation file pages defined in the client’s runtime controls), Adabas Vista will always select the first translation rule it finds with a mandatory attribute of Y.

When resolving a source file into a translation target (by reference to the file translation pages defined in the client’s runtime controls), and a translation rule exists in more than one page – none of which have the mandatory attribute set to Y - then Adabas Vista will select the translation rule with the highest priority setting.

To provide additional flexibility during translation processing, the active target category (mode) can be altered using Redirect.

Any such redirection is maintained for the remainder of the translation process.

You can explicitly prevent translation by leaving the target database and file and redirect category empty and marking the "None" attribute with any non-blank character. Note that this setting is a conscious action to prevent translation, unlike leaving a null entry. As such, notice will be taken of this setting during page merge and translation resolution processing.

This field is provided for use by the DBA.

(optional)

Specifies how Adabas Vista should react at runtime if the translation process for the active target category (mode) results in a “null” outcome. Options are:

• Allow calls for which no rules exist (default)

• Reject with response 249, subcode 106 at end of page-merge

• Use the rule from a nominated category

Specifies whether Adabas Vista at runtime should honour translation rules that change the active target category (mode). Options are:

• Allow a rule in a page to change (redirect) category (default)

• Reject with response 249, subcode 107

Specifies how Adabas Vista should react at runtime if the first-level null definition policy redirects to another target category (mode) which in turn results in a “null” outcome. Options are:

• Allow calls for which no rules exist (default)

• Reject with response 249, subcode 108 at end of page-merge