Adabas Response Codes - Software AG Documentation

More documents

Recommendations

Info

Adabas Response Codes Response 149 Origin Open systems only Explanation A communication error was detected. The Additions 2 field contains the system service completion code which caused the error response. Action Check the Additions 2 field. Response 150 Origin Open systems only Explanation Too many database nuclei have been used in parallel. The Additions 2 field contains the maximum number of nuclei allowed in parallel. Action Do not use more database IDs in a single program than the value given in the Additions 2 field. Response 151 Origin Mainframe and open systems Explanation A command queue overflow occurred. 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. Action The DBA may increase the value of the NC parameter or the command may be issued when there is a lower level of command activity. Response 152 66 Origin Mainframe and open systems Overview of Messages Explanation The internal user buffer was not large enough to contain the user buffer areas. Action The DBA should increase the value of the LU parameter used by the Entire Net-Work nucleus.
Overview of Messages Response 153 Origin Mainframe and open systems Explanation A second Adabas call was issued while the first one was still being processed. Action Issue only one call at a time. Response 154 Origin Mainframe and open systems Explanation One of the following occurred: The Adabas call was cancelled by the user (open systems). The command was rejected because it resulted in a trigger being fired, but the queue is full at this time. (mainframe) Action On open systems, no action is required for this informational message. On mainframe systems, retry the command. Response 155 Origin Mainframe systems only Explanation A command resulted in a pre-command trigger being fired. The triggered procedure returned a nonzero command, so the command was not executed. Action Check the Additions 4 field for the error returned from the procedure. Response 156 Origin Mainframe systems only Explanation A command resulted in a post-command trigger being fired. The triggered procedure returned a nonzero command, indicating an unsuccessful execution of the procedure. Action Check the Additions 4 field for the error returned from the procedure. Adabas Response Codes 67
Page 1 and 2:
Adabas Response Codes Adabas Respon
Page 3 and 4:
Table of Contents Explanation The m
Page 5 and 6:
Overview of Messages Response 3 Ori
Page 7 and 8:
Overview of Messages Response 10 Or
Page 9 and 10:
Overview of Messages Response 18 Or
Page 11 and 12:
Overview of Messages Explanation Th
Page 13 and 14:
Table of Contents Response 25 Origi
Page 15 and 16: Table of Contents Response 29 Origi
Page 19 and 20: Table of Contents Explanation The m
Page 23 and 24: Overview of Messages Action The fol
Page 25 and 26: Overview of Messages Response 50 Or
Page 29 and 30: Table of Contents Action Increase t
Page 43 and 44: Table of Contents Action The method
Page 49 and 50: Overview of Messages Action For mai
Page 51 and 52: Table of Contents Explanation An er
Page 53 and 54: Table of Contents Explanation The s
Page 55 and 56: Overview of Messages Response 123 O
Page 57 and 58: Overview of Messages Response 131 R
Page 59 and 60: Table of Contents Explanation The e
Page 61 and 62: Table of Contents Response 143 Orig
Page 63 and 64: Table of Contents Origin Mainframe
Page 65: Overview of Messages Explanation Th
Page 75 and 76: Overview of Messages Explanation Ei
Page 93 and 94: Overview of Messages Response 248 R
Page 95 and 96: Table of Contents Explanation Mainf
Page 97 and 98: Overview of Messages Explanation On
Page 99 and 100: Overview of Messages Explanation On
Page 101 and 102: Overview of Messages Explanation A
show all

Adabas Response Codes - Software AG Documentation

Create successful ePaper yourself

Delete template?

Save as template?