☜	OMI - Database Errors Draft MDC Standard					☞

4.10.1 Database errors

Implementers may choose to handle errors arising from database operations in the same way whether the database is local or remote. OMI responses indicate errors like undefined global variable, unauthorized operation, reference to an undefined environment, or maximum length exceeded. OMI does not support the M[UMPS] naked reference because that would require the server to retain information about past transactions. Agents shall detect naked reference errors.

OMI does not specify the timing of responses to database update requests. Servers that defer disk writing may be implemented to notify their own system manager of a failure to write, and not to delay their OMI response until the disk operation completes.

Copyright © Standard Documents; 1977-2024 MUMPS Development Committee;
Copyright © Examples: 1995-2024 Ed de Moel;
Copyright © Annotations: 2003-2008 Jacquard Systems Research
Copyright © Annotations: 2008-2024 Ed de Moel.

Some specifications are "approved for inclusion in a future standard". Note that the MUMPS Development Committee cannot guarantee that such future standards will indeed be published.

This page most recently updated on 07-Mar-2004, 10:17:06.

For comments, contact Ed de Moel (demoel@jacquardsystems.com)