Adabas Console Messages †ADAN* & ADACM*‡ - Software AG ...
Adabas Console Messages †ADAN* & ADACM*‡ - Software AG ...
Adabas Console Messages †ADAN* & ADACM*‡ - Software AG ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Adabas</strong> <strong>Console</strong> <strong>Messages</strong> (ADAN* & ADACM*)<br />
ADAN62 FNR=fnr A= U= ID= CA= CU=<br />
24<br />
Explanation This message is displayed in response to the DNFV operator command.<br />
FNR supplies the file number<br />
A is set to either "Y", indicating that the file is being used by access-only users, or<br />
blank, indicating that it is not being used by access-only users.<br />
U is used in the same way as A, but indicates usage by update users.<br />
ID shows the ID of the database which has exclusive control over the file<br />
CA provides the count of how many access-only users are using the file.<br />
CU is the count of how many update users are using the file.<br />
ADAN65 TSP subsystem (nn) name has abended<br />
Explanation The triggers and stored procedures facility has been activated for the current session.<br />
However, subsystem number nn, batch Natural nucleus name, terminated abnormally<br />
and will not restart.<br />
Action Determine the cause of the abend and correct the problem.<br />
ADAN69 date time BASE AND LOB FILE ARE OUT-OF-SYNC<br />
BASE FNR=base-fnr, UPDATE STATUS=upd-status1<br />
LOB FNR=lob-fnr, UPDATE STATUS=upd-status2<br />
Explanation A LOB file group consisting of a file with LB fields (base file) and a file containing the<br />
associated LB field values (LOB file) has become inconsistent. An illogical sequence of<br />
utility operations has exported (saved, restructured, unloaded) the files from, and<br />
subsequently reimported (restored, stored, loaded, defined) them into the database in a<br />
way that the two files no longer reflect the same point in time during processing.<br />
The base and LOB file have gotten out-of-sync. It is possible that the base file contains<br />
references to LB field values that should be, but are not, stored in the LOB file. Also,<br />
the LOB file may contain LB field values that should be, but are not, referenced by<br />
records in the base file.<br />
Action Investigate the cause of the base and LOB file getting out-of-sync. Take corrective<br />
action, such as reloading or restoring both files, depending on the findings. If necessary,<br />
you can use the following function to just mark the two files as being back in sync:<br />
ADADBS MODFCB FILE=base-fnr,LOBFILE=lob-fnr<br />
Overview of <strong>Messages</strong>