Response Codes

Adabas Vista has determined that no data is available to satisfy this command due to one of the following reasons:

• A partitioned file end-of-file or end-of-list condition was detected.

• None of the partitions were available/online and all of them have the file parameter Critical set to NO.

None.

All transaction activity by the client has been backed out for one of the following reasons:

• The client is using multiple (different) ETIDs which have collided against a particular database

Review the client’s use of ETIDs with respect to the current translation rules and/or partitioned files.

While attempting to satisfy a partitioned file command the unavailability of an FDT has been detected – this is invalid for one of the following reasons:

• None of the partitions were available/online and at least one of them has the file parameter Critical set to YES.

• None of the partitions were available/online and all of them have the file parameter Critical set to NO and the command can not be satisfied with a “no data” response such as RSP003.

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

The record buffer provided for an L9 command with ‘I ‘ option against a partitioned file is not large enough to hold the full list of ISNs.

Increase the size of the record buffer.

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.

This partitioned file has been defined with an unsupported Partitioning Field. The Partitioning Field may not be:

• A multiple value field

• An item in a periodic group

• A field with format F, G, or W

• A variable length field

• A field with the long alphanumeric (LA) attribute

• A SUPDE or SUPFN of format Alphanumeric with at least one parent of format W

Review the partitioning criteria.

One of the following errors was detected while processing a partitioned file:

• A distributed access can not be successfully processed due to the client encoding being incompatible with Vista’s record collating process.

• A command can not be successfully processed due to the client encoding being incompatible with the defined partition criteria.

Review the use of client encodings.

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.

• collation descriptors are not supported.

Review and correct the application program.

Runtime controls have been changed dynamically without the client previously resetting all Adabas context to null. In this situation Vista is forced to discard all Adabas context and alert the application with this response.

Avoid this response by ensuring the client has no Adabas context prior to the runtime controls being changed.

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.

The client runtime control for CL convergence is set to reject when your Vista rules used during runtime result in activity for multiple source databases converging into a single target database. With this setting the CL command cannot be processed by Vista because it would result in the loss of cursor/transaction activity in the target database for source database(s) beyond the one indicated in this CL command which would result in unpredictable results and errors if those other source databases are used further.

Review the application program and the convergent translation/partitioning rules or alter the CL convergence runtime control setting.

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 (any transaction will have been backed out)

• an L1 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 existing Command ID has been reused after the client’s translation context has been modified but this now references a different file, which is an illegal situation and is therefore rejected.

Review programming practices for changing client contexts.

Partitioned files can not be subjected to a change in client context

Review programming practices for changing client contexts.

A session-related memory allocation failed during an inter-system dynamic transaction routing operation, the client session is unable to continue. This sub-code may not indicate an error on this current Adabas command, but it indicates that an internal error has prevented the Vista session continuing successfully.

Increase the shared memory available.

A file-related memory allocation failed during an inter-system dynamic transaction routing operation, the client session is unable to continue using the file. This sub-code may not indicate an error on this current Adabas command, but it indicates that an internal error has prevented the Vista session continuing successfully with one of the files currently being used so Vista is alerting you immediately.

Increase the shared memory available.

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

Review application program.

An error has occurred during the processing of a distributed L3/L9 command against a partitioned file.

Contact your Software AG technical support representative and use the COR Debug Event Monitor controls specifying Response 249 and this subcode to provide diagnostic information.

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 number of segmented buffers used by this ACBX call against a Partitioned File is greater than the maximum allowed.

Reduce the number of segmented buffers.

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.

Support for the use of this API has been withdrawn.

Please refer to the currently supported APIs or, alternatively, contact your Software AG technical support representative to discuss your requirements.

An ET Data related command has been issued, but the runtime control Database Number for ET Data is not set to a specific database number and Vista has been unable to establish a target database to satisfy the command.

Review the runtime control Database Number for ET Data to specifically identify the database number to be used.

A sequence direction change has been detected during an L3 or L9 command against a Partitioned File whose Command ID sequence has been previously subjected to multifetch.

Review the program logic.

An error has occurred during the processing of an L1 ‘get next’ command against a partitioned file.

Contact your Software AG technical support representative and use the COR Debug Event Monitor controls specifying Response 249 and this subcode to provide diagnostic information.

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.

An error has occurred during the parsing of the Format Buffer during the processing of an Ax or Nx command against a partitioned file.

Contact your Software AG technical support representative and use the COR Debug Event Monitor controls specifying Response 249 and this subcode to provide diagnostic information.

The configuration for the first-level null definition policy for this target category (mode) is set to reject “null” as the outcome of translation processing.

Review the null definition policy for the target category (mode) used if you do not wish to receive this error.

Translation processing has been configured to disallow redirection to a different target category (mode).

Remove the redirection rule(s) or review the category adjustment policy for the target category (mode) in use.

The configuration for the first-level null definition policy redirects to another target category (mode) which in turn has resulted in a “null” outcome. The second-level null definition policy is set to reject such an outcome.

Review the translation rules in use to avoid a null result or alter the null definition policies.

Translation processing has detected a recursive redirection.

Review the translation rules in use.

An error has occurred during the processing of the current command.

Contact your Software AG technical support representative and use the COR Debug Event Monitor controls specifying Response 249 and this subcode to provide diagnostic information.

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.

Contact your Software AG technical support representative and use the COR Debug Event Monitor controls specifying Response 249 and this subcode to provide diagnostic information.

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.

One of the following has occurred:

• Runtime configuration on behalf of this client was unsuccessful and Adabas Vista has been defined as “critical” using the Critical Product Support feature of the Adabas System Coordinator.

• The Adabas Vista configuration file was not available during an attempt to satisfy an Adabas Vista API request.

Check the availability of the configuration file.

If the client runtime control Error Reporting WTO option is set to YES, this error may be accompanied by an AVI-0017-10 console message.

The client previously issued a command to a source file for which Vista was unable to determine the existence of any translation rules due to the configuration file not being available at the time. Subsequently, Vista has detected the availability of the configuration file and has determined the existence of a transation rule for this source file. This subcode is returned the next time the client attempts to access the source file.

Review the availability of the configuration file.

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 rule has been found in the Adabas Vista configuration file.

Check the rule 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.

The command limit defined for this source file has been exceeded.

Review the command limit.

A requested file refresh of a partitioned file has failed due to an unexpected Adabas response code. The partitioned file is in a partially refreshed state.

Review the Adabas response code.

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.

The session is not compliant with correct distributed transaction processing. Please refer to section Transaction Directives for a more detailed explanation of this subcode.

Adhere to correct distributed transaction processing.