Adabas Vista Client Runtime Controls

The service name used to link together the instances of the clustered application system.

For clustered applications such as job types CICS Cluster, IMS, or UTM, the service name is required to link all the instances of the same application system. If the job is running in a single operating system image (for example, UTM), the service name is still required.

Refer to the Adabas System Coordinator documentation for more information.

An optional hexadecimal value that Adabas Vista will set in the Command Time field of the Adabas Control Block for any command not passed to Adabas. The default is 00000000.

When this control is set to non-null it is used as the database number for all commands using ET data. This allows you to strictly control the place where ET data operations take place.

There are other Software AG products (such as Transaction Manager and Natural) that also provide controls for processing ET data commands. If these products are used (together) the precedence over which products control wins is 1) Adabas Transaction Manager 2) Adabas Vista 3) Natural.

When this control is set to null the database number in the command is trusted by Vista as the place for ET data (Adabas Transaction Manager may still take precedence if it is present); where the trusted database number is used it must either be a) active to be able to process the ET data or b) explicitly translated by an all-files Vista translation rule to a database that is active.

Controls the type of record hold processing to be used in a partitioned environment.

This parameter is applied when a distributed READ(L6) or FIND(S4) command is issued against a partitioned file.

Possible values are:

• 0: Normal processing.

• 1: The hold option is removed from the command and a L3 or S1 command is issued instead. If a record is to be modified, the corresponding ISN for the record is placed in hold status before it is modified.

• 2: The hold option is removed from the command and a L3 or S1 is issued instead. Record collating-sequence processing occurs immediately before returning a record to the user. After this processing, the record is placed in hold status.

• 3: The same as value '2' with an added integrity check during collating-sequence processing.

• 4: READ (L6) and FIND (S4) commands result in response code 249.

Controls whether or not a client can update more than one database in a single transaction.

Using Adabas Vista for file partitioning and translating increases the probability of a single transaction spanning multiple databases. In such circumstances, the Adabas Transaction Manager (ATM) should be used to ensure the integrity of the transaction.

If this parameter is set to YES, Adabas Vista processes ET commands serially. Any failure during this serial process jeopardizes the integrity of the transaction. It is therefore recommended that this parameter be set to YES only when the Adabas Transaction Manager is installed.

If Adabas Transaction Manager is not used, this parameter can be used to allow or disallow multiple database updates within the same transaction:

• If allowed, ET (or BT) commands are issued serially to the relevant databases. Under such conditions, the programmer should not assume any particular sequence of ETs.

• If disallowed, an Adabas Vista response code is generated whenever an attempt is made to modify a second database within one transaction.

Controls whether or not the WTO option is to be used during Adabas Vista error message processing.

The WTO option identifies the subcode of an Adabas Vista error for those programs that do not have ON ERROR processing to display the subcode. The subcode is needed to uniquely identify the reason for the error. See also section Error Handling.

If YES is specified for the WTO option, an error message written to the job log identifies the subcode associated with each Adabas Vista error. This error message has the prefix AVI-0018-10.

The Adabas response code to be used for identifying Adabas Vista processing errors.

A subcode in the Additions 2 field of the Adabas Control Block uniquely identifies the actual error. Possible values for this subcode are detailed in the section Messages. See also section Error Handling.

If you need to use a response code other than the default 249, refer to the Adabas Messages and Codes documentation for unused response codes.

Determines the approximate size of the Adabas System Coordinator user pool where

• type "a" represents batch, TSO, CMS, and TIAM jobs

• type "b" represents Com-plete, CICS, CICSplex, IMS, and UTM jobs

Refer to the Adabas System Coordinator documentation for more information.

type a: 2
type b: 1000

Indicates whether the P and M options on all transaction directives will be honored.

Possible values are:

• MINIMUM: P and M options on the first transaction directive will be honored – all other held records will be released.

• MAXIMUM: All records will be preserved on hold until subjected to any P and M options provided during the transaction directive sequence.

For more information on extended hold processing, see Extended Hold in section Transaction Directives.

Determines the initial size of all fixed pools managed by the Adabas System Coordinator.

Refer to the Adabas System Coordinator documentation for more information.

Indicates whether or not global format IDs are to be used.

This parameter enables a user-supplied global format ID to be propagated appropriately when issued against a partitioned file.

Note:
Adabas Vista supports Natural global format IDs.

Note:
If this parameter is set to YES for a 3GL language, the programmer must ensure that the uniqueness of the supplied global format ID is maintained in the last 5 bytes of the 8-byte Additions 5 field of the Adabas Control Block. This allows Adabas Vista to use the first 3 bytes internally.

Natural: YES
3GL: NO

Determines type of session management to be used for clustered application sessions

For clustered applications (job types CICS Cluster, IMS, UTM) where dynamic user movement is possible, you can choose to manage only terminal tasks. This is more efficient and is possible when non-terminal tasks do not move between regions in a clustered application.

Refer to the Adabas System Coordinator documentation for more information.

When Vista processes an OP command from the application layer it may be that the database number in the OP command does not exist (and never will). However, Vista has no way of knowing this, so may get a RSP148 (response code 148) to the command. Vista can allow that response to be fed back to the application layer but it may trigger unwanted error processing for some applications. This parameter controls whether Vista exposes the RSP148 to the application layer or resets it to RSP000. If reset, the following OP control block fields can be set for return (default values are shown here):

• ISN Quantity………… 07040400 (Version/Release/SM)

• Additions-4………….. 740000 (Version /Release/dbid)

This runtime control may also be referenced when processing commands which are candidates for suppression such as RC and RI commands.

The mode is used to differentiate between translation rule destinations (target database and file numbers for commands) for user groups. A default mode must be identified if the job uses Vista translation.

The default value for a given configuration file is the first category defined in the Site Policies for Target Categories screen. See Adabas Vista Online Services, Maintain Site Policies for Target Categories, for more information.

Pages contain translation rules and influence the translation capabilities of Adabas Vista enabled jobs.

Pages can be differentiated between those that are implicitly referenced by Adabas Vista and those that are explicitly referenced by Adabas Vista.

The only implicitly referenced page is the *site page. You do not need to define this page to any job. Once this page is established, Adabas Vista will always reference it first.

Explicitly referenced pages are those that you define to the job and are referenced in the order they are defined. If a *site page exists then this page will be referenced before any of the defined pages.

The runtime translation rules for a session are merged from the *site page (if used by the site) and the other pages defined for the job. Where a duplicate rule is found conflict resolution is based upon the individual rule's settings for mandatory and priority in conjunction with the policy set for the site's conflict resolution.

See Adabas Vista Online Services, File Translation, for more information.

Identifies the Adabas System Coordinator group that is to manage the job.

For clustered applications (job types CICS Cluster, IMS, UTM), this name is required to link all the instances of the job in the cluster. If the job is running in a single image (for example, UTM), the name is still required.

Refer to the Adabas System Coordinator documentation for more information.

Indicates whether or not user command tracing is to be used.

The number of commands for which trace entries are to be used.

Note:
Information from these trace entries can be displayed by using the CLOG function of the Adabas Vista API. A sample use of this API can be found in the program AVICLOG in the INPL dataset.

Caution:
Do not modify this program as it may be required for support purposes.

Indicates whether or not Adabas Vista is to be enabled for a job.

Adabas Vista checks each command which may include checking against the configuration file to determine if the command should be translated, or whether it accesses a partitioned file. If it is known that a particular job makes no access to files that need to be under Adabas Vista control, this parameter can be used to disable Adabas Vista processing in order to enhance throughput.

Caution:
If Adabas Vista processing is disabled, there will be no recognition of commands that need to be targeted elsewhere. Therefore, care should be taken when using this parameter.