Button for 1977 Button for 1984 Button for 1990 Button for 1995 Button for MDC Button for notes Button for examples
☜

OMI - About Output

Draft MDC Standard

☞

5.4.30 Abort output

(Operation type 49) requests the server to terminate output to the device immediately without waiting for buffers to empty nor for acknowledgment from the device. An indeterminate amount of data may be lost.

The server shall not close a file nor relinquish a device, but shall remain ready to execute subsequent transactions for the device. Subsequent close device, close client’s devices, and close all devices transactions directed to the device shall succeed if otherwise acceptable and if no other intervening transactions for the device have occurred. That is, the output pending error shall not apply in this condition.

The fields of the abort output request and their sequence shall be:

  1. Environment: <LS> the server’s environment for the device.
  2. Device name: <LS> the server’s name for the device from the open device response.
  3. Client identifier: <SS> $Job (see ANSI/MDC X11.1) of the client process making the request, an ASCII string of decimal digits.
<LS> <LS> <SS>
<LI> Environment <LI> Device Name <SI> Client ID

Figure 53 – Abort output request

The response shall consist of a header only.

Button for 1977 Button for 1984 Button for 1990 Button for 1995 Button for MDC Button for notes Button for examples

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 14-Nov-2023, 21:50:16.

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