Tony Summers wrote:

>Nice idea - what if an application issues the FILE equate command via
>the HPCOMMAND intrinsic ?
>
>(Example,  the user chooses their printer in their view screen, and the
>application issues the file equate just before the open output statement).
>

It would have been nice if we had some expanded UDC options:
Enforce Logon UDC All= yes/no <currently exists>
Enforce Logon UDC All except ldev 20=yes/no
Enforce COMMAND->HPCICOMMAND=yes/no

Since we don't, IMHO, these create MAJOR security issues for MPE/iX.

However, to address your specific question:
What if an application issues the FILE equate command via
the HPCOMMAND intrinsic? (I presume that you referred to COMMAND)

Several methods exist to deal with this issue depending on the number
of programs, CM or NM mode, and directory location. These range
from modifying the source, patching the command image in the object file,
'hooking' the program, and intercepting the call to the COMMAND or
FOPEN/HPFOPEN intrinsics.

Paul, also wrote of other 'additional situations', $stdlists from jobs can
easily be spsaved with simple logon udc logic. (below)

Cordially,

Mike Hornsby
Beechglen Development Inc.
513-922-0509



logonudc
option logon
if hpinteractive = false
    spoolf !hpspoolid;spsave;show
endif
***

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