COMMAND completely ignores HPPATH since it does not check to see if the
passed in command image references a script or program file. So, if
parm-1 is not a known, built-in command the COMMAND intrinsic will
return error 975.
On the other hand, HPCICOMMAND will continue to look for a script or
program file before returning error 975.
Unless parm-1 is a qualified filename, HPCICOMMAND uses HPPATH in its
attempt to resolve the command name.

Here's a simple way to compare COMMAND vs. HPCICOMMAND. EDITOR calls the
COMMAND intrinsic when its command line begins with a colon, and VOLUTIL
calls HPCICOMMAND.  Try feeding these utilities a UDC command, a script
name, a program file name, the RUN and XEQ commands, etc.

Jeff Vance, vCSY


> -----Original Message-----
> That was a good idea also, but it did not work. It did change 
> the HPPATH var in the session, but the "COMMAND" ( and "HPCICOMMAND")
intrinsics
> ignored the HPPATH variable.
> 
> Thanks,
> 
> Gordon

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