Hi all,

...
> >:print abort4dg
> >showme
> >:abort4dg
> >Command only allowed in break. (CIERR 1686)
> >:xeq abort4dg
> >USER: #S142,MANAGER.SYS,PUB      (NOT IN BREAK)
...

I think several have covered this subject, but let me
add that for MPE V compatibility reasons the MPE/iX CI
uses the same command name parsing rules as the old MPE
V CI. There are numerous examples looking at customer's
JCL where they have commands like:
   :run$oldpass    <<no space>>
   :abortio6       <<no space>>  etc.

So, the XEQ command was created to let you run scripts and
program files that have the same name (up to the first non-
alpha character) as a built-in CI command.

The CI name parsing rules are even trickier when it
needs to determine the command name for implied run and
for scripts once POSIX/HFS names were allowed.  For
example, is the name "a/b arg1" an MPE script named "A"
with a lockword of "B", or file "b" in the directory "a"?
This is described in a Communicator at:
http://jazz.external.hp.com/papers/Communicator/5.0/exp3/ci_enhancements.htm
l
(probably wrapped)

 Jeff Vance, vCSY

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *