☜	OMI - Finish Output Draft MDC Standard					☞

5.4.29 Finish output

(Operation type 48) requests the server to finish writing all accepted write arguments to the device, that is, to empty its buffers and accept acknowledgment from the device. The server shall not close a file nor terminate output to a device, but shall remain ready to execute subsequent transactions for the device.

The server shall not wait for output to finish, but shall respond immediately, indicating the status and progress of output.

The fields of the finish 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.

Figure 52 – Finish output request

The response shall consist of a header only. If the error class indicates success, then the error type shall equal 0 if output has finished, and shall equal 1 if not. All other values are reserved.

When output is pending (error class equals 0 and error type equals 1), the implementer may choose to show progress in the error modifier, for example by changing its value from 1 response to another if output has occurred between the responses.

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:07.

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