[Info-vax] An old program I found, a hack allowing for using recall /input from within a login script

[Hans Bachner]

Stephen Tyree schrieb am 21.10.2021 um 18:41:
> Folks,
> 
> I was looking through some old code of mine, and I found a program I had written that allowed you to leverage recall/input from a login script... by way of mucking with the program's process level using executive mode privileges. See for yourself:
> 
> https://pastebin.com/PTFseGkz
> 
> You would compile it with an mmk file such as:
> 
> !
> ! Flags for controlling compilation/linking
> !
> CXX = CXX
> CXXFLAGS = /model=ansi/reentrancy=multi/exceptions/standard=strict/switch="const_string_literals"-
>             /nopure_cname/ansi_alias/assume=(stdnew,trusted_short_alignment,nopointers_to_globals)-
>             /float=ieee/ieee_mode=fast/architecture=HOST/opt=(LEVEL=5,TUNE=HOST)-
>             /pointer_size=64=argv/rtti/warn=(disable=(dollarid))
> LINK = LINK
> LINKFLAGS = /sysexe/notraceback
> OBJECTS = RECALL_INPUT.OBJ
> 
> !
> ! One rule to rule them all
> !
> RECALL_INPUT.EXE : $(OBJECTS)
>          $(LINK)/EXECUTABLE=$(MMS$TARGET) $(LINKFLAGS) $(MMS$SOURCE_LIST)
> 
> ..CXX.OBJ
>          $(CXX) $(MMS$SOURCE) $(CXXFLAGS)
> 
> Then you need to install it with executive-mode privileges. BUT, if you did all of that, you could override the behavior of log*out to write out the recall buffer, change your login script to call this monstrosity of a program, and voila, your command history (well, about 50 commands worth at least) is saved across sessions.
> 
> It worked very well for me (and some others at my company), but I take no responsibility for its behavior on your systems :). Enjoy!
> 
> Thanks,
> Stephen Tyree

You did not explain what the program does - is it different from 
RECALL/OUTPUT=xxx and RECALL/INPUT=xxx ?

Hans.