Text |
Address of program starting asynchronous task is missing. |
Explanation |
A master file definition specified that an asynchronous task is to be started after an update to the master file has been committed by means of an Adabas ET command. The address of the program used to start such a task has not been specified correctly in the ETP 3GL interface initialization call. |
Action |
Specify the correct address of a program used to start an asynchronous task in the ETP 3GL interface initialization call. |
Text |
Updating the distribution key of a master file is not allowed. |
Explanation |
If a distribution key is defined for a master file, it may be contained in any view used to update the master file, but the distribution key field itself may not be updated. |
Action |
Use a sequence of DELETE and STORE statements instead of UPDATE in the application programs to update the distribution key field. |
Text |
Using more than one log file in a transaction not allowed. |
Explanation |
The "Verify transaction consistency during logging" field is set to "Y" (yes) and two or more master files that were updated in the same transaction have different log files assigned. Action: Either set the "Verify transaction consistency ..." field to "N" using the MODIFY SYSPROF function or modify your master file definitions so that all master files that are updated in a single transaction have the same log file assigned. |
Text |
Concurrent updates to more than one database are not allowed. |
Explanation |
It is not allowed to update master files that are contained in different databases in the same transaction. Transaction consistency cannot be guaranteed for such operations. |
Action |
Change the application programs so that a transaction contains only updates to a single database. |
Text |
Length of format buffer or record buffer exceeds allowed maximum. |
Explanation |
Format and record buffer for an update call logged by ETP may not exceed a maximum value. |
Action |
Split your Natural views or the format and record buffers supplied by a 3GL program into smaller portions and issue multiple Adabas calls. |
Text |
Administration file is not defined. |
Explanation |
To use ETP, an administration file has to be assigned to logical file number 200 for Natural applications. For 3GL applications, the administration file has to be specified as a parameter for an initialization call to the ETP 3GL interface. ACTION: For a Natural application, use the Natural LFILE parameter or the NTLFILE macro to specify the ETP administration file. |
Action |
or the NTLFILE macro to specify the ETP administration file. For a 3GL application, specify the administration file correctly in the ETP 3GL interface initialization call. |
Text |
GETMAIN failed for ETPSIZE. |
Explanation |
For an NTDB macro or for the Natural DB parameter, the ETP option is specified for at least one database. Entire Transaction Propagator (ETP) is not be able to run, because the required storage could not be obtained. |
Action |
Restart Natural in a larger environment: Increase your region size or increase the size of your Natural thread when running in a thread environment. |
Text |
Error during start of asynchronous task after ET. |
Explanation |
After an Adabas ET command, ETP tried to start an asynchronous task because the definition of a master file that was updated in the completed transaction requested so. The program that was executed ended with an error. |
Action |
Check the task name specified in the ETP system profile. Verify that a transaction with that name is in a library that is accessible from the current TP monitor session. |
Text |
The ETP identification record is invalid or missing. |
Explanation |
When invoked for the first time, the ETP maintenance utility writes an identification record into the administration file, which is never deleted by ETP. If the error occurred during logging of transactions, the ETP identification record has been deleted, but other information in the administration file still exists. If the error occurred when you invoked the ETP maintenance utility, you attempted to access an ETP administration file with an old version of the ETP maintenance utility after it had been accessed with a newer version. ACTION: If the error occurred during logging of transactions, invoke the ETP maintenance utility and verify that all information contained in the administration file is still correct. |
Action |
information contained in the administration file is still correct. If the error occurred when you invoked the ETP maintenance utility, use only the newer version of the maintenance utility to access the administration file. |
Text |
Invalid ISNQ value for S1 cmd on obtaining replicate ISN. |
Explanation |
The file definition requested that the criterion used to replicate records is the distribution key defined for the replicate"s master file. The distribution key must be a unique descriptor. To replicate the record, the ISN of the record in the replicate file is retrieved. For N1 calls (STORE), no record with that key may be present. For A1/E1 (UPDATE/DELETE), exactly one record with that key must be present. As the record"s ISN was retrieved, ETP encountered an invalid ISNQ value, meaning that for an N1 a record with the key already existed or for an A1/E1 command either no or more than one record with that key exists in the replicate file. The reason for this error is usually that an application program modified the replicate file (which is not allowed) or Adabas utilities were used to modify the replicate file. |
Action |
utilities were used to modify the replicate file. Re-initialize the replicate file from the master file as described in the manual and, if necessary, correct your application programs. |
Text |
Overflow of master file table. |
Explanation |
The limit of 512 master files for a specific database was exceeded. |
Action |
Contact your Entire Transaction Propagator administrator. |
Text |
Overflow of log file table. |
Explanation |
The limit of 512 log files for a specific database was exceeded. |
Action |
Contact your Entire Transaction Propagator administrator. |
Text |
Outline editor requires delimiter class D defined in map. |
Explanation |
The definition of delimiter class D in a map (see map settings) is a prerequisite for using the outline editor. |
Action |
Run migration program or define delimiter class D in the map. |