> While it does not matter to me, (I'm 'stuck' at 6.0 and thus 
> I will not be receiving the enhancement) I'd like to re-state 
> the suggestion presented earlier on this thread, of perhaps 
> invoking functions through a 'CALL' function.  Perhaps the 
> 'CALL' function could be made available just for those cases 
> where full file name qualification is required?
> 

I am also on 6.0 for the duration, it is by choice and not because I am
stuck, so it will not benefit me either but I would not find it very
difficult to work with unqualified functions.

Could you not use a method like:

Logon UDC:

SETVAR FUNCTIONLOC, "FUNCTION.SYS"
SETVAR FUNCTIONPATH, "!FUNCTIONLOC"
SETVAR HPPATH, "!!FUNCTIONPATH" + "," + "!HPPATH"

Then any time your command file or job wants to use an alternate
location you simply issue a new setvar:

SETVAR FUNCTIONPATH, "TEST.DEV"

And then when you want to return to the default function locations:

SETVAR FUNCTIONPATH, "!FUNCTIONLOC"

Can anyone see a hole in this approach?



Comment's are my own, not my employer's... Etc.

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