|
|
|
|
|
|
|
| ☜ | OMI - Write ArgumentDraft MDC Standard | ☞ | ||||
A write request (see 5.4.28) shall contain 0 to 65 535 write arguments, whose sequence shall preserve the sequence of writearguments executed by the client process. Except as noted in the following paragraph, each writeargument executed by the client process shall correspond to exactly 1 write argument.
When the device supports the stream forms 1 or 2, then string-type write arguments need not correspond 1-to–1 with the writearguments of the client routine. In forms 1 and 2 the agent may concatenate the values of exprs from an unbroken sequence of "WRITE expr" commands. In form 2 it may also divide a value from 1 "WRITE expr" into separate write arguments.
NOTE – Client routines may set standard special variables $DEVICE, $KEY, $X, and $Y; and in some implementations, also non-standard variables beginning with $Z. Although not arguments of the WRITE command, these variables effect device control functions; thus the write request transmits them.
The following descriptions of write arguments’ effects on the device are for information only; they refer to the forms of writeargument defined in ANSI/MDC X11.1.
Each write argument shall comprise 1 or more fields. The first shall be a numeric type <SI>. Different types of arguments contain different numbers and kinds of additional fields.
|
|
|
|
|
|
|
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 16-Nov-2023, 16:56:53.
For comments, contact Ed de Moel (demoel@jacquardsystems.com)