Ted writes:
> "The RUN command is parsed by the Compatibility Mode parser unless it is
> implied, in which case the Native Mode parser is used."

IIRC, The NM parser which was written when MPE/XL was developed is used for
most "new" commands and is the thing that supports constructs like
;SELEQ=[ACCESS=INUSE], etc.

Unfortunately the old CM parsers in the CM command executors allowed a
number of goofy things in syntax and there are cases where the NM parser
will just refuse to deal with this nonsense, so not all of the parsing code
uses the "new" parser, and there are still a number of commands which are
parsed by the same CM code that was used on MPE/V.

> I wasn't aware that there even were two parsers.

While I suspect that the NM parser is more or less a single entity, I think
that many of the CM command processing routines each parsed their own
parameters rather than having a separate shared "parser".  So a lot of the
problem is that different commands do things differently, and it's not
practical to invent a single parsing module that can be all things to all
programs.

> The gentleman who shared this with me reported that someone had told
> him that the native mode parser is faster.  Is this true?  If so, by
> how much?

Who cares?  It's not going to make a measurable difference in the load on
your machine.

G.