Response Codes

The user was timed out for one of the following reasons:

• The user was notified of an Adabas response code 9 timeout against one source database and existing partitioned file definitions determine that the user is timed out of the current, different source database as well. The original Adabas response code 9 is returned in the first two bytes of the Additions 2 field.

• The user was timed out by Adabas Vista.

Review the Adabas timeout values and the Adabas Vista job parameter User Non-Activity Time Limit.

Unable to read the FDT of the partitioned file. None of the partitions were available/online and at least one of the partitions had the file parameter Critical set to YES. To access a partitioned file, at least one of the partitions must be available/online.

Ensure at least one of the file partitions is available/online.

Adabas Vista uses a default Adabas response code of 249 for all processing errors. This response code can be changed by using the Job Parameter function of Adabas Vista Online Services.

Refer to the section Subcodes for the explanation of the subcode. If the subcode is not mentioned, contact Software AG technical support.

The partitioned file concurrency limit has been reached.

Increase the partitioned file concurrency limit using the File Partitioning function of Adabas Vista Online Services.

The job parameter Enable Multiple Updates is set to NO. After updating one database, the user attempted to update a second database in the same transaction.

Review the job parameter Enable Multiple Updates in the Job Parameter function of Adabas Vista Online Services.

One of the following errors was detected in the Adabas search buffer while processing a partitioned file:

• the specified field is not in the Adabas FDT.

• an S or N operator is used incorrectly.

• a superdescriptor with a variable-length parent field is not allowed.

• coupled file syntax is not allowed.

• the value1 operator (EQ, GE, GT, etc.) is unknown.

• a connecting operator (D, O, R, etc.) is unknown.

• a command ID enclosed in parentheses is not allowed

• a memory request failed.

Review and correct the application program.

One of the following errors was detected in the Adabas format or record buffer while processing a update/store for a partitioned file:

• The partitioning field specified in the format buffer could not be located in the Adabas FDT (N1 and N2).

• An Adabas field specified in the format buffer could not be located in the Adabas FDT (N1, N2 and A1).

• The partitioning field value specified in the record buffer is inconsistent with the defined partitioning criteria for the file (N1 and N2).

• The partitioning field value specified in the record buffer is inconsistent with the partition criteria defined to the partition identified by the ISN in the Adabas control block (N2 only).

• The partitioning field value specified in the record buffer is null and the Store Control Option is set to 2 (N1 only).

• The partitioning field/value has not been specified and no target partition has been identified (N1 and N2).

Review application program and partitioning criteria.

The partitioning field value specified in the record buffer of the A1 command is inconsistent with the partition criteria defined to the partition identified by the ISN in the Adabas control block.

Such an update requires the relocation of the ISN to another partition, which is not allowed.

Review the application program. Use a delete and store as an alternative.

An ISN has been detected that is invalid for one of the following reasons:

• The partition identifier extracted from the Adabas Vista ISN is not consistent with any partition defined to the partitioned file.

• The Adabas ISN read from a partition is greater than the TOPISN value defined for the partition.

• An attempt to store a record has resulted in an Adabas ISN greater than the TOPISN value defined for the partition.

Review the application program and check TOPISN setting.

One of the following errors occurred while processing Distributed Lock Mode (DLM) against a partitioned file:

• Prefetch/multifetch options on a distributed access L6command are not allowed for DLM options 2 and 3.

• DLM option 4 is specified and a distributed accessS4 or L6 command was issued.

• DLM option 3 is specified and the distributed access data integrity check failed.

Review the application and use of the DLM option.

One of the following unsupported commands has been issued:

• an S5 command (partitioned files only)

• a C5 command

• a BT command with Command Option 2 set to F

• anL1 command with Command Option 1 or 2 set to F

Review application program.

An update command has been issued to a partitioned file; however, the target partition does not have the option ACCESS=FULL.

Review application program and partition ACCESS options.

An L1 (get next) command was issued but the supplied command ID is not currently active.

Review application program.

An A1 command was issued without the H option and the DLM option is set to 1. However, the ISN to be updated has not been previously read by a hold command.

Review application program and use of DLM option.

The file parameter Enable ISN Positioning is set to NO and one of the following commands was issued:

• L1 with Command Option 2 set to I

• L2/5 with starting ISN

• L3/6 with starting ISN

• Sx with the ISN Lower Limit field specified

Review application program and the file parameter Enable ISN Positioning.

A memory request failed.

Review the memory availability of the

• host TP system;

• host operating system; and

• global common memory pool (BS2000 only; specified in the Adabas System Coordinator group definition).

One of the following invalid values was used for a command ID value:

• X'00000000'

• X'40404040'

Do not use the above command ID values.

One of the following errors was detected during read-ahead processing:

• direction change occurred during an L3 sequential read with no accompanying value reposition; or

• a direction change occurred during anL9 sequential read.

Review the application program.

The Adabas Vista database process is not installed. It must be installed on all Adabas databases which contain Adabas Vista partitions. This subcode indicates that a database

• is not running with ADARUN VISTA=YES; or

• is not running Adabas version 7 or above.

Refer to the Adabas Vista installation procedures.

A command has been issued against a partitioned file which has the Shared Partition option set to YES for one or more of its partitions. However, the partitioning field defined does not exist in the Adabas FDT.

The partitioning field must be present in the Adabas FDT when using shared partitions.

One of the following errors occurred while processing the record, value, or search buffer:

• A P format field value was not in packed decimal format.

• A U format field value was not in unpacked decimal format.

• The attempted format conversion was not possible because of incompatible data formats or other compatibility problems.

• The field length was zero or not consistent with the field format.

Check field values for correct formats and lengths.

A non-zero response code was returned when accessing the Adabas Vista configuration file.

A message is issued to the console from the job that received the error. The message has the prefix AVI-0017-10 and displays the configuration file database/file number and the response code and subcode returned.

The job parameter Profile ID Validationis set to YES and a Profile ID has been provided for which there are no translation or partition rules defined.

Review the Profile ID and the defined rules.

In batch mode this error is accompanied by a message issued to the console from the job that received the error. The message has the prefix AVI-0016-10 and displays the Profile ID in question.

An invalid partitioned file definition has been found in the Adabas Vista configuration file.

Check the file definition using Adabas Vista Online Services.

An invalid translation file definition has been found in the Adabas Vista configuration file.

Check the file definition using Adabas Vista Online Services.

An error in the record buffer was detected during processing of an OP command.

One of the following errors occurred while processing an S8 command:

• An invalid command ID was specified in the Additions 1 field.

• Different file numbers were detected for ISN lists.

• An error occurred while processing a subsequent S8 call.

Review the application program.

One of the following errors occurred while processing an S2 command:

• An invalid sort sequence was specified.

• An invalid ISN was detected during processing.

• An error was detected during ISN processing.

Review the application program.

One of the following errors occurred while processing an S9 command:

• The command ID value specified was assigned to another command.

• An invalid sort sequence was specified.

• An invalid ISN buffer length was detected.

• The number of ISNs to be sorted as provided in ISN quantity is equal to 0.

• The command ID value specified in Additions 4 was not found.

• An invalid ISN was detected during processing.

• An error was detected during ISN processing.

Review the application program.

One of the following errors occurred whilst processing a direction change during an L9 command sequence:

• A second direction change for this sequence was attempted.

• A format override cannot be processed.

• A length override greater than specified in the FDT cannot be processed.

• A length override has been specified with complex search criteria.

Review the use of the L9 command and the Adabas Vista restrictions.

An S2 command to continue a sequence has been received. The sequence was not started by an S2 command.

Amend the command sequence to process either all S1 commands, or all S2commands, as appropriate.

One of the following errors occurred while initializing AVIKRN:

• The dynamic load failed.

• The version is not compatible.

Check the Adabas Vista installation procedures.