The responses and subcodes that may be generated by Adabas Vista during command processing are described below. Subcodes are returned in big-endian byte order in the right-most two bytes of the ADDITIONS 2 field in the Adabas Control Block.
Adabas responses and subcodes not mentioned here are automatically returned to the user unchanged. Information regarding these can be found in the Adabas documentation.
| Response 17 | Subcode 0x00F9 |
| Explanation |
An error occurred whilst accessing a file. The program tried to access a file that was not listed in the file
list of an |
| Action |
Review the program logic. |
| Response 21 | Subcode 0x00F9 |
| Explanation |
An invalid command ID value was detected:
|
| Action |
Review the program logic. |
| Response 23 | Subcode 0x00F9 |
| Explanation |
An invalid ISN was detected. The starting ISN specified for an |
| Action |
Review the program logic. |
| Response 25 | Subcode 0x00F9 |
| Explanation |
An invalid ISN was detected. The ISN specified in the ISN Lower Limit field for an
|
| Action |
Review the program logic |
| Response 101 | Subcode 0x0000 – 0xFFFF |
| Explanation |
Adabas System Coordinator processing error. |
| Action |
Refer to the Messages and Codes section of the Adabas System Coordinator documentation. |
| Response 113 | Subcode 0x00F9 |
| Explanation |
An invalid ISN was detected. The ISN specified for an |
| Action |
Review the program logic |
| Response 249 | Subcode 0x0000 – 0xFFFF |
| Explanation |
An error occured during command execution. |
| Action |
Refer to the appropriate Subcodes section. |
| Response 249 | Subcode 0x0001 |
| Explanation |
An inconsistency in an internal data structure was detected. This may indicate a code fault within Adabas Vista. |
| Action |
Contact your Software AG support representative. |
| Response 249 | Subcode 0x0002 |
| Explanation |
An inconsistency in an internal data structure was detected. This may indicate a logic error within Adabas Vista. |
| Action |
Contact your Software AG support representative. |
| Response 249 | Subcode 0x0003 |
| Explanation |
The |
| Action |
Review the program logic. |
| Response 249 | Subcode 0x0004 |
| Explanation |
The F option for an |
| Action |
Review the program logic. |
| Response 249 | Subcode 0x0005 |
| Explanation |
The F option for a |
| Action |
Review the program logic. |
| Response 249 | Subcode 0x0006 |
| Explanation |
The ISN buffer for a |
| Action |
Review the program logic |
| Response 249 | Subcode 0x0007 |
| Explanation |
The maximum number of active command ID values has been reached. |
| Action |
Review the program logic |
| Response 249 | Subcode 0x0008 |
| Explanation |
The command ID value specified for
|
| Action |
Review the program logic |
| Response 249 | Subcode 0x0009 |
| Explanation |
Adabas Vista is not compatible with the installed version of Natural, Adabas or Net-Work. |
| Action |
Contact your Software AG support representative. |
| Response 249 | Subcode 0x000A |
| Explanation |
The definitions for partitioned file do not exist. |
| Action |
Review the partition definitions in SYSAVI. |
| Response 249 | Subcode 0x000B |
| Explanation |
The parititioning field does not exist in the FDT. |
| Action |
Review the partition definitions in SYSAVI. |
| Response 249 | Subcode 0x000C |
| Explanation |
The field type in the partition definition does not match the field type in the FDT. |
| Action |
Review the partition definitions in SYSAVI. |
| Response 249 | Subcode 0x000D |
| Explanation |
The type for the parititioning field is not suitable. |
| Action |
Review the partition definitions in SYSAVI. |
| Response 249 | Subcode 0x000E |
| Explanation |
The format buffer specified for an |
| Action |
Review the program logic. |
| Response 249 | Subcode 0x000F |
| Explanation |
The value of the partitioning field in the record buffer specified for
an |
| Action |
Review the program logic. |
| Response 249 | Subcode 0x0010 |
| Explanation |
The value of the partitioning field in the record buffer specified for
an |
| Action |
Review the partition definitions in SYSAVI. |
| Response 249 | Subcode 0x0011 |
| Explanation |
The value of the partitioning field in the record buffer specified for
an |
| Action |
Review the program logic. |
| Response 249 | Subcode 0x0012 |
| Explanation |
The ISN and the value of the partitioning field in the record buffer
specified for an |
| Action |
Review the program logic. |
| Response 249 | Subcode 0x0013 |
| Explanation |
The license is not valid for this operating system. |
| Action |
Contact your Software AG support representative. |
| Response 249 | Subcode 0x0014 |
| Explanation |
The license has expired. |
| Action |
Contact your Software AG support representative. |
| Response 249 | Subcode 0x0015 |
| Explanation |
The license file could not be found. |
| Action |
Contact your Software AG support representative. |
| Response 249 | Subcode 0x0016 |
| Explanation |
The license key is invalid. |
| Action |
Contact your Software AG support representative. |
| Response 249 | Subcode 0x0017 |
| Explanation |
The license is for a different version of the product. |
| Action |
Contact your Software AG support representative. |
| Response 249 | Subcode 0x0018 |
| Explanation |
The license is not for this product. |
| Action |
Contact your Software AG support representative. |
| Response 249 | Subcode 0x0019 |
| Explanation |
The ISN of a record read from a partition or the ISN of a record
stored using an |
| Action |
Check the settings for the Adabas file to ensure that the ISN values cannot exceed the highest value defined for the partition in SYSAVI. |
| Response 249 | Subcode 0x1000 – 0x10FF |
| Explanation |
The subcodes in this range are returned as a result of Adabas errors encountered when either accessing the configuration file or reading the FDT of a partitioned file. The low-order byte of the subcode contains the Adabas response code. |
| Action |
Refer to the Messages and Codes section of the Adabas documentation for an explanation of the Adabas response code. |
| Response 249 | Subcode 0x2000 – 0x20FF |
| Explanation |
The subcodes in this range are returned as a result of unexpected errors returned by the SAGOVO library. The low-order byte of the subcode contains the identifier for the SAGOVO function that caused the error. |
| Action |
Contact your Software AG support representative. |
| Response 249 | Subcode 0x3000 – 0x30FF |
| Explanation |
The subcodes in this range are returned as a result of unexpected errors in the SAGSMP library. The low-order byte of the subcode contains the identifier for the SAGSMP function that caused the error. |
| Action |
Contact your Software AG support representative. |
| Response 249 | Subcode 0x4000 – 0x40FF |
| Explanation |
The subcodes in this range are returned as a result of unexpected errors in the SAGLST library. The low-order byte of the subcode contains the identifier for the SAGLST function that caused the error. |
| Action |
Contact your Software AG support representative. |
| Response 249 | Subcode 0x5000 – 0x50FF |
| Explanation |
The subcodes in this range are returned as a result of unexpected errors in the SAGRGS library. The low-order byte of the subcode contains the identifier for the SAGRGS function that caused the error. |
| Action |
Contact your Software AG support representative. |
| Response 249 | Subcode 0x6000 – 0x60FF |
| Explanation |
The subcodes in this range are returned as a result of unexpected errors in the SAGLIC library. The low-order byte of the subcode contains the identifier for the SAGLIC function that caused the error. |
| Action |
Contact your Software AG support representative. |
| Response 249 | Subcode 0x7000 – 0x70FF |
| Explanation |
The subcodes in this range are returned as a result of unexpected system errors. The low-order byte of the subcode contains system error code. |
| Action |
Contact your Software AG support representative. |