On Aug 25,  8:59am, Keven Miller wrote:
> Subject: Re: CONSOLE REPLYS
> We created a system wide [REPLY] udc for things like this.
...
> One drawback is that if you issue a REPLY with no space between the
> keyword and the pin, it's not trapped  (REPLY103,Y). Something to do
> with numerics allowed in udc command names, which are parsed before regular
> MPE commands.

This is correct.  In retaining MPE V compatability, the MPE/iX CI follows
the same rules in extracting the command name.  Namely:
  - parse out the name using only alphanumerics (must start with alpha)
  - see if it is a UDC
    if yes the 1st byte past the end of the name begins the 1st arg.
  - if not a UDC parse out the name using only alpha chars.
  - see if it is a built-in CI command.
    if yes the first byte past the end of the name begins the 1st arg.
  (added to the MPE XL CI)
  - if not parse out the name using MPE and POSIX filename rules.
  - see if the name matches any file using HPPATH elements.
    if yes the first byte past the name begins the 1st arg.

Example command line:

:abcd23.ef_g

If a UDC named ABCD23 exists it will be invoked and passed ".ef_g" as the arg
ElseIf a built-in command named ABCD exists it will be passed "23.ef_g" as
       the first arg
ElseIf an MPE named file matches ABCD23.EF[.acct] it will be invoked and passed
       "_g" as the first arg
ElseIf a POSIX-named file matches abcd23.ef_g is will be passed no arg.


HTH,
Jeff Vance, CSY

--