Thanks Rich. At Tim’s suggestion I cracked it by giving the user account profile a quota on dskb: and that automatically included dskb: in the search list for the user account.
> On 9 Feb 2018, at 00:25, Rich Alderson <s...@alderson.users.panxi.com> wrote: > >> From: Quentin North <quen...@quentin.org.uk> >> Date: Wed, 7 Feb 2018 20:27:12 +0000 > > [ snip the REACT stuff which Tim Litt answered ] > >> When I login with a user that I have created I don't seem to get a default >> SSL and dsk: is not assigned to dskb. If I manually assign dskb: dsk: that >> seems to work in that I can direct, but it doesn't seem to just do that. > >> .login quentin >> Job 3 KS10 TTY1 >> %LGNSLE Search list is empty >> 20:05 7-Feb-118 Wednesday > >> .dir > >> %WLDSLE Search list empty >> .dir dsk: > >> %WLDSLE Search list empty dsk: > > Well, when you boot the OS, you can define a system search list prior to > issuing the GO command. Type a "?" at the "Startup option:" prompt to see > what > all you can do there. > > You can also define a system search list by logging in as a privileged user. > Since the OPERATOR ([1,2]) is automagically logged in by the startup, issue > the > PUSH command in OPR to get to a command prompt and issue the command > > .R SETSRC > *CS DSKB: > *^Z > > You will now have a system search list defined. This is permanent until > something clobbers it; it will ride out system crashes, etc. > > .HELP SETSRC will provide you with all the ugly information on this useful > command. > > Rich _______________________________________________ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
