Job Parameters

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.

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 user 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. Furthermore, any transaction data specified with the ET may appear anywhere in this sequence.

• 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 profile overrides are to be allowed for the job.

Each job defined in the Adabas Vista configuration file may have job profile overrides specified. These override parameters influence the target category for a given source profile, and thus the actual database and file number for the appropriate commands issued for the duration of this job.

Any job profile overrides specified for the job will be ignored if this parameter is set to NO. Note that only published overrides will be processed.

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 the database number to be used for ET data.

ET data requests are processed according to the value of this parameter:

• value 0: the request is issued with no modification by Adabas Vista. It is the user's responsibility to ensure that the database number specified for the request is valid.

• value not 0: Adabas Vista modifies the request by issuing it to the database number specified by this parameter.

Note:
In a Natural environment, the Natural parameter ETDB specifies the database where transaction data is to be stored (refer to the section Profile Parameters in the Natural Installation and Operations documentation). If this parameter is used dynamically, it is recommended that you set the Adabas Vista job parameter to zero to maintain the dynamic capability in an Adabas Vista environment.

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.

Indicates whether or not a Profile ID is to be validated against other translation rules and partition definitions that have been defined in the Adabas Vista configuration file.

Adabas Vista checks each command to determine if it conforms to a published translation rule or partition definition. This check consists of Profile ID, the source database number, and the source file number. If no matching translation rule or partition definition is found, this parameter is then evaluated according to the parameter value specified:

• NO: the command is allowed to continue without any change.

• YES: a further check against the configuration file is performed to see if the Profile ID has been defined to any published translation rule or partition definition. If so, the command is allowed to continue; if not, an error code is returned.

Indicates whether or not profile overrides for this job are to be selected based on the Profile ID.

Separate overrides may be specified for the same source database and file number, but with different Profile IDs. This parameter enables selection of the appropriate overrides based on the current Profile ID.

Possible values are:

• NO: only overrides with a blank Profile ID are considered for processing.

• YES: only overrides with a matching Profile ID will be processed. Other overrides, including those with a blank Profile ID (unless the current Profile ID is blank) are ignored.

Note:
This parameter is ignored unless the parameter Enable Profile Overrides is set to YES.

Indicates the size (in kilobytes) of memory to be allocated to the read-ahead pool.

The Adabas Vista read-ahead feature provides the benefits of multifetch processing for batch jobs in an Adabas Vista environment, thus reducing the amount of interprocess communication and command selection within the database.

The read-ahead pool is used only during read-ahead processing. This parameter defines the maximum amount of storage to be used. This pool is not extended.

Because all commands are dynamically analyzed to determine their suitability for read-ahead processing, it is not necessary to specify files or commands to be excluded from the process. For each suitable command, the read-ahead factor is dynamically modified for best performance.

Adabas Vista read-ahead is controlled at the job level by specifying the Adabas parameter ADARUN PREFETCH. No other Adabas prefetch parameter is necessary.

Indicates whether read-ahead processing is to be handled by Adabas Vista or by Adabas.

The read-ahead process itself is controlled by specifying the Adabas parameter ADARUN PREFETCH. If Adabas Vista read-ahead is to be used, no other Adabas prefetch parameter is required.

Possible values are:

• V: Adabas prefetch is disabled and all calls are satisfied using Adabas Vista read-ahead processing.

• A: Adabas prefetch is to be used.

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.