[HECnet] DAP

[G.]

On Tue, 10 Dec 2019 18:34:18 -0500, Thomas DeBellis wrote:

> What is the difference in practice between functions 7 (SUBMIT) and 8 
> (EXECUTE)?

I've looked around a bit, see this:

| 796         .SBTTL  FAL$SUBMIT, FAL$CREATE
| 797
| 798 ;++
| 799 ; The following routines have separate entry points but share common code ...
| 800 ;
| 801 ; This routine performs the DAP SUBMIT file function which consists of creating
| 802 ; the command file, submitting it to the symbiont manager for execution, and
| 803 ; finally deleting the command file when the job is finished.
| 804 ;--
| 805
| 806 FAL$SUBMIT::                            ; Entry point
| 807         BISL2   #<<FAB$M_SCF>!-         ; Set submit-on-close and
| 808                   <FAB$M_DLT>!-         ;  delete-after-execution bits
| 809                 0>,FAB$L_FOP(R10)       ; Fall thru to FAL$CREATE ...
| 810
| 811 ;++
| 812 ; This routine performs the DAP CREATE file function.
| 813 ;--
| 814
| 815 FAL$CREATE::                            ; Entry point
| 816

And this:

| 974         .SBTTL  FAL$EXECUTE
| 975
| 976 ;++
| 977 ; This routine performs the DAP EXECUTE file function which consists of
| 978 ; submitting a command file to the symbiont manager for execution. The command
| 979 ; file must exist on the destination node and it is not deleted after execution.
| 980 ;
| 981 ; Note: The DAP specification allows partner to request that DAP Extended
| 982 ;       Attributes messages be returned, but it is unlikely that anyone will
| 983 ;       make a request for anything but a Name message.
| 984 ;--
| 985
| 986 FAL$EXECUTE::                           ; Entry point

Also, from the DAP V5.6 specification:

| 5.2.7  Command/Batch  Execution  Files - The  Data   Access   Protocol
| includes  commands for the transfer and submission of files to a batch
| processing facility or command interpreter.  The  "submit  as  command
| file"  request  in  the  Access  Message  requests  that the data that
| follows be stored in a temporary file and that this file be  submitted
| to a batch-type facility upon access completion (closing of the file).
| The file will be deleted following execution by  the  batch  facility.
| DAP  does  nothing with regard to any feedback from the batch facility
| and does not guarantee that the file actually executes  in  the  batch
| monitor.   The  file is transferred using sequential file storage, see
| section 5.2.2.
| 
| The "execute-as-command-file" requests that the specified file be only
| submitted  to  the  batch facility.  No data follows this command (the
| specified file having been  previously  established  on  the  accessed
| system).   The  file  is  not deleted following execution by the batch
| facility, so that the sequence "store, and execute command file"  will
| transfer  a  file,  submit  it and retain the file for later use.  The
| message sequence for "submit-as-command-file" is identical to "store",
| while the "execute command file" is identical to ERASE.

I suspect that the VMS SUBMIT/REMOTE command might result in a DAP execute
file function, wherease the PRINT/REMOTE command in a DAP submit:

|   94 ; NT$CLOSE - engages in a DAP dialogue with the remote FAL to close the
|   95 ;       specified file and to process selected FOP options and XABs.
|  ...   ...
|  137 ;       Optionally, a file may be deleted, executed, printed, submitted
|  138 ;       (executed then deleted), or spooled (printed then deleted) on close
|  139 ;       at the remote node. Note that there is a distinction between the DAP
|  140 ;       execute and submit functions.  Furthermore, the DCL SUBMIT/REMOTE
|  141 ;       command really maps into the DAP execute function (i.e., the file is
|  142 ;       not deleted after the batch job completes). Also, the file's protection
|  143 ;       and revision information may be optionally altered on close.

Also again: 

http://pdp-10.trailing-edge.com/BB-JR93L-BB_1990/01/10,7/nft/nip.mac.html

| ;Note: DAP refers to this function as "execute", and defines "submit" to
| ;	be a copy operation with execute on close. For the purposes of
| ;	user interface on TOPS-10, the terminology is "submit", even
| ;	though the code in the I/O library will use "execute".

Hope this helps, :)

G. (Gerardo)