Adabas Transaction Manager Messages and Codes - Software AG ...

More documents

Recommendations

Info

Adabas Response Codes Action Response 147 Origin Explanation Action 132 ■ the buffer header was invalid (both offsets are set) ■ at least one ISN buffer offset was not divisible by 4 ■ the start offset was outside the multicall buffer range ■ the record buffer was not large enough to contain all subcommand control blocks. The value in the Additions 2 field identifies the buffer: the first 2 bytes contain the buffer number in binary format, the last two bytes contain the buffer name, as shown in the following table: Correct the buffer length and try again. Mainframe and open systems Bytes 1-2 Bytes 3-4 1 FB (format buffer) 2 RB (record buffer) 3 SB (search buffer) 4 VB (value buffer) 5 IB (ISN buffer) The exact meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems. Mainframe Systems The ISN was invalid. The ISN transformation resulted in a negative ISN or an ISN greater than the maximum ISN permitted for the file. Open Systems A user buffer is not accessible by the Adabas interface routine. The method of resolving the error varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems. Mainframe Systems Open Systems Check whether the control block, format buffer, value buffer, record buffer and ISN buffer have valid addresses and lengths. Check whether the control block, ISN buffer and record buffer are write-protected. Adabas Transaction Manager Messages and Codes
Response 148 Origin Mainframe and open systems Explanation The Adabas nucleus was either not active or not accessible (a call could not be sent to the Adabas nucleus when the command was issued). In an ACB, refer to the hexadecimal subcode that appears in the low-order (rightmost) two bytes of the Additions 2 field; in an ACBX, refer to the binary subcode that appears in the Error Subcode (ACBXERRC) field. Note: If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (in the ACB) or the ACBXERRC field (in the ACBX) may contain the ID of the Entire Net-Work node that issued this response code. The following are the decimal equivalents of the subcodes and their meanings: Subcode Occurrence Location 0 1 2 3 4 5 8 open systems mainframe systems mainframe systems mainframe and open systems mainframe systems mainframe systems mainframe systems Description Adabas Transaction Manager Messages and Codes No active database server was found, either local or remote. Exclusive database control requirement conflicts with read-only nucleus status. A nonprivileged call was made to the nucleus while it was in utility-only (UTI) mode. The nucleus is performing shutdown processing (an ADAEND operation) and will not accept new users or new transactions. Either a new user is attempting to begin operation or an existing user in ET status is trying to continue operation. A utility with exclusive database control is running. A single-user nucleus could not start operation due to an error that could not be corrected. A user is performing a logical ADALNK call. The IDT for the call has not been allocated. Action Adabas Response Codes Start the nucleus and reissue the command. Remove the READONLY=YES parameter setting for the nucleus and restart it. Remove the UTIONLY=YES parameter setting for the nucleus and restart it. Wait for the nucleus to shut down, restart it, and reissue the command. Either stop the utility or wait for its processing to complete (this is preferred) and try again. Verify that single-user mode has been set up correctly and restart the nucleus. On BS2000 systems, check the setting of the parameter accessed by the link name DDLNKPAR or DDCARD, or in the macro B2CONFIG of the module SSFB2C. Also check the IDTNAME parameter of the database to be accessed. 133
Page 1 and 2:
Adabas Transaction Manager Adabas T
Page 3:
Table of Contents 1 Adabas Transact
Page 7 and 8:
2 Message Format and Severity Codes
Page 9 and 10:
3 ATM* - Adabas Transaction Manager
Page 11 and 12:
ATM015_10 RRMS LOGNAME INCONSISTENC
Page 13 and 14:
ATM028_10 DB RESTART. MAX TARGETS E
Page 15 and 16:
ATM039_04 TRANSACTION RESTART NOT P
Page 17 and 18:
ATM050_20 ‘SIGN-OFF’ FAILED, RE
Page 19 and 20:
ATM061_10 MIXED TRANSACTION STATUS
Page 21 and 22:
ATM073_10 DB ACTIVITY NOT QUIESCED.
Page 23 and 24:
ATM085_10 TRANSACTION DETAILS TRANS
Page 25 and 26:
ATM103_08 TM END PENDING, INCOMPLET
Page 27 and 28:
ATM124_04 the details to your Softw
Page 29 and 30:
ATM132_10 RMI RESYNC ERROR. SYS/CD/
Page 31 and 32:
ATM141_04 DTP DISABLED FOR THIS JOB
Page 33 and 34:
ATM172_10 TM tmid DID NOT COMPLETE
Page 35 and 36:
4 Adabas Transaction Manager Error
Page 37 and 38:
error 076 Explanation Transaction (
Page 39 and 40:
error 156 Explanation Client is alr
Page 41 and 42:
error 236 Explanation A CICS/RMI sy
Page 43 and 44:
error 316 Explanation Invalid dynam
Page 45 and 46:
error 396 Explanation Attempt to ch
Page 47 and 48:
error 480 Explanation A request fro
Page 49:
error 540 Explanation The “F” c
Page 52 and 53:
Adabas Response Codes Response 1 Or
Page 54 and 55:
Adabas Response Codes Response 3 Or
Page 56 and 57:
Adabas Response Codes 52 Subcode Me
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Adabas Response Codes Action 58 ■
Page 64 and 65:
Adabas Response Codes 60 Subcode 6
Page 66 and 67:
Adabas Response Codes Response 19 O
Page 68 and 69:
Page 70 and 71:
Adabas Response Codes Action Respon
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87: Adabas Response Codes Response 50 O
Page 88 and 89: Adabas Response Codes Action Respon
Page 92 and 93: Adabas Response Codes Action 88 ■
Page 96 and 97: Adabas Response Codes Action 92 Ope
Page 110 and 111: Adabas Response Codes 106 Subcode M
Page 114 and 115: Adabas Response Codes 110 Subcode 1
Page 116 and 117: Adabas Response Codes Response 102
Page 132 and 133: Adabas Response Codes Action 128 Su
Page 138 and 139: Adabas Response Codes 134 Subcode O
Page 140 and 141: Adabas Response Codes 136 Subcode O
Page 186 and 187:
Adabas Response Codes Response 250
Page 188 and 189:
Page 190 and 191:
Adabas Response Codes Response 254
Page 192 and 193:
188
Page 194 and 195:
User Abend Codes Code Module 27 28
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
200
Page 206:
202
show all

Adabas Transaction Manager Messages and Codes - Software AG ...

Create successful ePaper yourself

Delete template?

Save as template?