Why does @INFORMATION (ABOUT) FILES ... say "restricted JFN"?

[FEINBERG at CMU-20C]

Howdy!
	I beg to differ with you, JONL.  Here is a excerpt from 
QIO.MID.750:

;HERE TO ALLOCATE A FRESH JFN AND OPEN THE FILE
OPEN3D:	PUSH FXP,TT		;SAVE THE TTSAR
	MOVEI T,F.DEV(TT)
	HRLI T,-L.F6BT
	PUSH FXP,(T)		;COPY THE GIVEN DEVICE NAMES ONTO THE STACK
	AOBJN T,.-1
	PUSHJ P,6BTTLS		;CONVERT TO A NAMESTRING IN PNBUF
	POP FXP,TT		;GET TTSAR
	MOVE T,(FXP)		;RESTORE MODE BITS IN T
	MOVSI 1,(GJ%ACC+GJ%SHT)	.SEE .GJDEF
	TRNE T,1		
	 TLNE T,FBT.AP
	  TLOA 1,(GJ%OLD)	;FOR INPUT OR APPEND, WE WANT AN EXISTING FILE
	   TLO 1,(GJ%FOU+GJ%NEW) ;FOR OUTPUT, A NON-EXISTENT FILE
	MOVE 2,PNBP
	GTJFN			;GET A JFN

The line MOVSI 1,(GJ%ACC+GJ%SHT) sets the Restricted Access bit.
There are apparently many GJ%ACCs throughout QIO.MID.  If there is a
good reason for them to be there, that is one thing.  Denying that
they are there is a different story.  I would proposed eliminating
GJ%ACC from all GTJFN calls. This would make debugging easier.