Adabas Transaction Manager Messages and Codes - Software AG ...
Adabas Transaction Manager Messages and Codes - Software AG ...
Adabas Transaction Manager Messages and Codes - 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> Response <strong>Codes</strong><br />
Response 49<br />
Origin<br />
■ Make the file available for all users (on open systems, if value 16 occurred in bytes 3 <strong>and</strong><br />
4).<br />
■ Restore or unlock the file (on open systems, if value 17 occurred in bytes 3 <strong>and</strong> 4).<br />
■ Rebuild the file's index (on open systems, if value 18 occurred in bytes 3 <strong>and</strong> 4).<br />
■ On open systems, if the value in bytes 3 <strong>and</strong> 4 of the Additions 2 field is 8, <strong>and</strong> the nucleus<br />
was started with the OPEN_REQUIRED option, you can reissue the OP comm<strong>and</strong><br />
immediately. This will cause the other user with the same user ID to be stopped, unless<br />
that user is currently active.<br />
■ On open systems, if a utility receives a response 48 because non-utility users are still active,<br />
you can lock the file with ADAOPR LOCK. This ADAOPR comm<strong>and</strong> stops all non-utility<br />
users from accessing the file <strong>and</strong> allows only utility users to access the file until it is unlocked<br />
again.<br />
On mainframe systems, if a utility receives a response 48 because non-utility users are still<br />
active, you can lock the file with ADADBS MODFCB FILEREADONLY. The<br />
FILEREADONLY comm<strong>and</strong> stops all non-utility users from accessing the file <strong>and</strong> allows<br />
only utility users to access the file until it is unlocked again.<br />
Mainframe <strong>and</strong> open systems<br />
Explanation The compressed record was too long. It exceeds the maximum permitted compressed record<br />
length for the file.<br />
80<br />
On open systems, the first two bytes of the Additions 2 field contain the length of the<br />
compressed record in binary format.<br />
On mainframe systems, the following subcodes may be indicated:<br />
Note: This response code always means that the compressed record is too long <strong>and</strong> there are<br />
duplicate meanings for subcodes but the subcode can help your <strong>Software</strong> <strong>AG</strong> technical support<br />
representative analyze where in the code we are giving the response. This can be useful for<br />
debugging purposes. Please always provide the subcode when communicating about this<br />
response code with your <strong>Software</strong> <strong>AG</strong> technical support representative.<br />
Subcode Meaning<br />
1<br />
2<br />
3<br />
4<br />
5<br />
6<br />
File(s) not available at open time. This is the default message displayed with this<br />
response code if another subcode is not provided.<br />
Multiple-value (MU) field.<br />
Periodic (PE) group field.<br />
MU field.<br />
PE group.<br />
PE group level.<br />
Remaining fields.<br />
<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong>
Change language