☜	Routine Transfer Format Draft MDC Standard					☞

1 Routine Transfer Format

The routine loader routine shall have a form that will load the routines from the transfer medium and will save it in internal format. The save routine creating the transfer medium shall produce the following routine transfer format:

Header-line–1 eol
Header-line–2 eol
routinehead
routine-line eol
.
.
.
eol
routinehead
routine-line eol
.
.
.
eol
[***RTN END***] eol

In the above structure, routine-line is a string in a format as returned by $Text. The two header lines shall be free text and may contain any message the sender wishes to convey to the receiver.

Note: Each routine is separated by a blank line (an eol) from the following one. Optionally, either two successive blank lines or the string "***RTN END***" denotes the end of the file. Eol is defined to be a logical end-of-line record as mutually defined by the sending and receiving environments.

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 13-Sep-2014, 22:10:24.

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