[HECnet] DAP

[Thomas DeBellis]

That's interesting, I wonder what context it executes under on the 
remote system?  Running on the console under Tops-10 used to be able to 
get you the ability to run INITIA and sign on as whomever you wanted, no 
password.  But that was a 5.00 series monitor; I don't know if they 
changed that.  On Tops-20, if you bounce the keys hard enough, you can 
wind up the in the mini-exec, which is not a good thing.

Changing your user id is one of the few things that's a cinch on Unix.  
You 'just' do a SETUID to the user in question and now for all intents 
and purposes, you are them.

No such luck on Tops-20 or as I recall, Tops-10.  On Tops-10, you have 
to run the LOGIN or INITIA program from SYS: so you get the JACCT bit 
set and then you can set your PPN.  On Tops-20, you can only execute the 
LOGIN% JSYS when you are not logged in.  Once you are logged in, you 
can't execute LOGIN% ever again, even if you have WHEEL or OPERATOR 
capabilities; this effectively broke my implementation of REIN for FTP.

You've got to start a complete new job context.  So to execute, I guess 
you'd have to grab a pseudo-terminal and fire up a job on it, perhaps 
via CRJOB%.  But now you're talking about what BATCON does, so what's 
the point?

I definitely couldn't whack the user context in FAL, it unfortunately 
has run with OPERATOR.  To do it right, I'd need to modify the monitor 
to give FAL its own (un-logged in) job slot and then have it do the 
LOGIN% based on what is passed to it.

I'd looked at the monitor code a few months ago; looks doable. Actually 
it looked easier than putting RENAME in.  I guess I'll look at that some 
more after I get the ANONYMOUS FAL up.

On 12/10/19 6:45 PM, Johnny Billquist wrote:
> On 2019-12-11 00:39, Johnny Billquist wrote:
>> On 2019-12-11 00:34, Thomas DeBellis wrote:
>> [...]
>>
>>> What is the difference in practice between functions 7 (SUBMIT) and 
>>> 8 (EXECUTE)?  In both cases, Tops-20 submits the file as a Batch job 
>>> to Galaxy, this being the only way to construct the proper user 
>>> context.
>>
>> In RSX, SUBMIT would be something placed in a batch queue, but 
>> EXECUTE would be something that was run directly, if I remember 
>> right. (I could be confused.) You do not need a user context in the 
>> same sense under RSX in order to run programs. Such program would be 
>> run under the console terminal.
>
> To quote the online help:
>
> .nft /id
> NFT -- Version V9.0
> Local NFARs V8   DAP V7.1 Buffer size=  2064. OS=RSX-11M+ FS=FCS-11 
> DC=Yes
> .nft /he
>
>  NFT is the Network File Transfer utility.  It can perform file
>  transfers and file operations over the network.
>
>  Information is available for the following operations:
>      APPEND (/AP) .............. File Append commands
>      COPY ...................... File Transfer commands
>      DELETE (/DE) .............. File Deletion commands
>      DEFAULTS (/DF) ............ Set/Examine Defaults commands
>      DIRECTORY (/AT,/BR,/LI,/FU) Directory list commands
>      EXECUTE (/EX) ............. File Execution commands
>      IDENTIFY (/ID) ............ Identify commands
>      PROTECTION (/PR)........... File Protection commands
>      RENAME (/RE) .............. File Rename command
>      SPOOL (/SP) ............... File Spooling commands
>      SUBMIT (/SB) .............. File Submission commands
>  And the following subjects:
>      DATA CHECKING (/DC) ....... Remote file transfer data checking
>      FILESPECS ................. File Specification syntax
>      NODE NAMES ................ Node and Access control syntax
>      MODES (/AS,/AX,/BK,/IM,/RC) File transfer Mode switches
>      QUOTES .................... Quoting foreign filespecs
>      SWITCHES .................. NFT switch summary
>      VERSION NUMBERS ........... Version number processing
>
> .nft help ex
>   To execute a file, or a several files which are located on a remote
>   node, the command format is:
>     NFT>filespec1[,filespec2,...,filespecN]/EX
>
>   Valid qualifiers are:
>         /LO
>
> .nft help sb
>   To submit a file, or several files to a remote system, the command
>   format is:
>         NFT>[outfilespec]=infilespec1[,...,infilespecn]/SB
>
>   Valid qualifiers are:
>         /AS, /AX, /BK, /DC, /IM, /NV, /RC, /LO
>
>
>
>   Johnny
>
>
>