Button for 1977 Button for 1984 Button for 1990 Button for 1995 Button for MDC Button for notes Button for examples
Left Hand Pointer

JOB

Annotations

Right Hand Pointer

jobactuallist

Introduced in the 1990 ANSI M[UMPS] language standard.

This metalanguage symbol represents an actual parameter list for a Job command (formal parameter list: at the label of the invoked subroutine or function; actual parameter list: in the call to that subroutine or function).

An actual parameter list starts with a parenthesis open, then follows a list of actual parameters, separated by commas, and ends with a parenthesis close.

The difference between an actual parameter list on a Job command and an actual parameter list on a subroutine-call or a function reference is that a parameter list on a Job command can only have "by value" parameters and no "by reference" parameters.

Removed in the 1995 ANSI M[UMPS] language standard.

jobargument

Introduced in the 1984 ANSI M[UMPS] language standard.

This metalanguage symbol represents an occurrence of an argument of the Job command. Examples of valid arguments for the Job command appear in an earlier section. The argument of the Job command is either a destination, optionally followed by a colon, followed by implementation-specific process parameters (either an expression or a list of expressions (separated by colons) enclosed in parentheses), optionally followed by a colon and a time-out specification, or an indirection operator (@) followed by an expression that evaluates to a list (separated by commas) of such arguments.

Modified in the 1990 ANSI M[UMPS] language standard.

There may be a parameter list between the destination and the optional implementation-specific process parameters. Parameters in this parameter list may only be passed by value.

Approved for addition in a future M[UMPS] language standard.

An argument of a Job command may optionally include a specification of the environment in which the process is intended to execute.

jobenv

Approved for inclusion in a future M[UMPS] language standard.

This metalanguage symbol represents a specification of an environment. This symbol is used to indicate the environment where a process is executing. The representation in this context consists of a vertical bar, the name of an environment and another vertical bar.

jobparameters

Introduced in the 1984 ANSI M[UMPS] language standard.

This metalanguage symbol represents any implementation-specific parameters to be passed to the process being created, optionally followed by a time-out specification. The implementation-specific parameters may be either a single expression, or a list of expressions (separated by colons), enclosed in parentheses.

Introduced in the 1995 ANSI M[UMPS] Windowing Application Programmer's Interface standard.

This metalanguage symbol represents a key sequence (one or more keystrokes). Such codes can by any sequence of characters, except for commas.

To be modified in a future M[UMPS] Windowing Application Programmer's Interface.

Key sequences may contain any characters, except for the comma. Any commas will be identified by the special value "COMMA" (see metalanguage symbol commacode). In addition, there may be special codes present in the specification of this key sequence that identify modifier-keys, function-keys or implementation-specific entities.

processparameters

Introduced in the 1984 ANSI M[UMPS] language standard.

This metalanguage symbol represents any implementation-specific parameters to be passed to the process being created. The implementation-specific parameters may be either a single expression, or a list of expressions (separated by colons), enclosed in parentheses.

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-2018 MUMPS Development Committee;
Copyright © Examples: 1995-2018 Ed de Moel;
Copyright © Annotations: 2003-2008 Jacquard Systems Research
Copyright © Annotations: 2008-2018 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 12-Sep-2014, 10:12:45 .

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