2 DECnet
See HELP on the following topics:
SHOW NETWORK
SET HOST
SUBMIT/REMOTE
PRINT/REMOTE

SET HOST PHAST::    (PHAST:: is our node name)
lets you recursively log in to THIS computer.
 (note:  SET HOST/LOG  allows you to record your session).

We are currently connected to the High Energy MicroVAX II (UWAPA1::),
the Astronomy MicroVAX II (JANUS::), and the Particle Theory
MicroVAX II (UWAPA2::) via Ethernet (a 10 megabit per second DECnet link).

If you use DECnet, NETSERVER.LOG files will be created in your main
directory.  You may delete them to save disk space, but they are
automatically PURGEd when the system thinks there are too many.
3 MicroVAX
The Physics Computer Cost Center owns several MicroVAXen.
We are currently connected to the High Energy microVAX II (UWAPA1::)
and  the Astronomy MicroVAX II (JANUS::)
via Ethernet (a 10 megabit per second DECNET link).
There is limited disk space on the microVAX.  71 Megabytes total, of which
about half is VMS, etc.
RAM Memory is much more available.  6 Megabytes is currently installed
on UWAPA1:: and UWAPA2:: and 9 Megabytes on JANUS:: .
3 Programs_available
FORTRAN
ULIB:[TALARIS.TEX82]TEX82,QTEX,QPOST
WHAT,STAT,ATNODE
3 Expectations
We expect to implement one or more batch queues on the MicroVAX II's.
Only a limited number of people will be allowed to log in
interactively (people in the purchasing group as payment for the
donation of the microVAX to the Cost Center).  Others will have to
make do with submitting batch jobs.  Computing costs on the MicroVAXen
will be lower than on the big VAX due to reduced maintenance costs.
If you discover ways to make batch jobs more convenient,
please MAIL to MANAGER on any Cost Center system.
3 Examples
DECnet and microVAX commands

Current nodenames ('node::' in the following)
PHAST::		VAX 11/780 (the big VAX or the VAX)
UWAPA1::	High Energy MicroVAX II 
JANUS::         Astronomy   MicroVAX II 
UWAPA2::        Particle Theory Group MicroVAX II

Important network commands:  (See HELP about them)
SHOW NETWORK
SET HOST
SUBMIT/REMOTE
PRINT/REMOTE

NCP is manager's Network Control Program.

From the big VAX:
DIR  node::   displays filenames on the little VAX
              (default is your SYS$LOGIN directory there)
MAIL to an account on a little VAX, SEND   'To:'  node::username
EDIT/EDT  node::filename  will edit a file on the little VAX
	(do NOT use SET HOST to do this since EDIT/EDT is a network hog)
SET HOST node::  to connect to a little VAX and log in.
	Beware some operations may be very expensive (like screen editing).
        This command will be restricted to the purchasing group.
SUBMIT/REMOTE  UWAPA1::filename   submits batch job to SYS$BATCH
	on the microVAX.  (file must already be on the microVAX and
	no useful qualifiers are recognized, so if you have redefined
	SUBMIT to be SUBMIT/NOTIFY etc, you must SUBMIT/NONOTIFY/REMOTE.

From the little VAX:
DIR PHAST::  to see files on the big VAX
COPY PHAST::filename *
MAIL to an account on the big VAX, SEND   'To:'  PHAST::username
	SET FORWARD PHAST::username   will forward your mail to the big VAX
EDIT/EDT  PHAST::filename  will edit a file on the big VAX
	(do NOT use SET HOST) 
PRINT/REMOTE  PHAST::filename     prints on the big VAX's Printronix
	(file must already be on the big VAX, and no useful qualifiers are
	recognized)

Copying directory structures:
On the big VAX
BACKUP  [directory...]*.*  node::filename.BCK/SAVE_SET
creates a save-set on the microVAX containing the specified directory
and subdirectories as they exist on the big VAX.
On the microVAX
BACKUP  filename.BCK/SAVE_SET  [000000...]*.*
will restore the directories onto the microVAX.

3 Cautions
Do NOT do intensive input/output over the network.  It is usually
best to COPY files to the node which will be using them.

Commands involving network access may need CTRL-Y to abort instead of just
CTRL-C.  If you use CTRL-S and CTRL-Q when scrolling through a file
and you CTRL-C, several pages of the file may have been
buffered ahead and finish displaying before you see any response
to your CTRL-C.

When running SET HOST,  Quick double CTRL-Y's cause the local node
to ask if you want to disconnect.

Broadcast messages will appear on your screen if you SET HOST
	and either machine's account receives messages.
3 LOGIN.COM
Whenever you use network access, a process is created on the remote
computer which runs your LOGIN.COM .  In order to speed this startup,
you should use the following lines in your LOGIN.COM file.

$ SET NOON          ! first line (so errors won't crash LOGIN.COM)
$ GOTO 'F$MODE()'
$INTERACTIVE:
$OTHER:

your terminal-dependent setup commands go here

$BATCH:

your symbol definitions and everything else go here

$NETWORK:    ! last line of LOGIN.COM (network jobs skip everything)
3 MAIL
If your main account is on a MicroVAX, you might want to
use MAIL's internal command SET FORWARD to cause your MAIL to
accounts on lesser used nodes to be be forwarded to your main node

To send BITNET MAIL from non-PHAST:: nodes, use an address of the form
PHAST::JNET%"username@password"
This awkward form must be used since only PHAST:: is on BITNET .
To the receiver, the MAIL message will appear to come from
POSTMASTER@UWAPHAST, so be sure to include your UWAPHAST address
in the body of the message.
3 SET_PROMPT
The SET PROMPT command is useful in your LOGIN.COM
to help you keep aware of which computer you are on if you SET HOST.
E.g.  SET PROMPT="j$ "
will display
j$
instead of
$
to indicate you are on JANUS::

This has already been done system-wide.
3 SET_DEFAULT
You can
SET DEFAULT  node::
the overhead is worse than SET HOST and some operations may not work
(like SET PROTECTION).  Each file being accessed causes creation of a
network process to access the file on that node.  This is expensive.
3 Command_files
You can run command files located on remote nodes,
but all commands you might put in a command file are not guaranteed
to work and the command file runs in your local computer context.
$ @UWAPA1::DUA0:[directory]commandfile.COM
will run the specified command file even if you are on node PHAST:: .

Note: this can cause lots of remote DECnet file access processes
if the .COM file has not been written with care to take advantage
of the network and you have SET DEFAULT node:: .
3 Batch
YOU MUST HAVE AN ACCOUNT ON A MICROVAX TO SUBMIT JOBS THERE.
MAIL to MANAGER for accounts.  Creation of accounts may be made
automatic later.

The beginnings of batch job submission to the MicroVAX
are in DRC1:[DECNETWORK.BATCH]
The command
NETSUBMIT  file-spec/qualifiers
will copy the specified command file to your main directory on the remote
system and submit it.  If executable programs or data files
are referred to, your batch job must take care of them
by either COPYing them explicitly, or using the big VAX's node name
in their filenames.
See DRC1:[DECNETWORK.BATCH]NETBATEXAMP.COM for an example batch file.
More complex batch submission is used in DRC1:[TALARIS.TEX82]LTEX.COM
3 NETSUBMIT
Runs a batch job in SYS$LOGIN: directory of another DECNET node
using transparent decnet access.
Format:
	NETSUBMIT  file-spec/qualifiers

NOTE:  ALL SUBMIT QUALIFIERS ARE ACCEPTED including /QUEUE
but some may not work in an obvious or useful way.

The commandfile must be customized for the destination node,
copying necessary executables and data files and deleting them
when finished (even if errors abort the job).
See SYS$ULIB:[DECNETWORK.BATCH]NETBATEXAMP.COM for example.
4 Parameters
All qualifiers after the commandfile name
are passed to the SUBMIT command on the remote node

file-spec
	command file to submit to the remote node
4 Qualifiers
	qualifiers as specified in HELP SUBMIT

        Note: many will not work in obvious ways since they
	refer to the temporary file on the target node, e.g.
	/BACKUP,/DATE,.../NOTIFY

4 Example
	DEFINE  NET_NODE  JANUS::
	NETSUBMIT  G1FD/QUEUE=FAST$BATCH/NOLOG/PAR=(FILE1,FILE2)

submits G1FD.COM from current directory on current node
to JANUS:: queue FAST$BATCH
keeping no .LOG file on that node
with two filenames as parameters to the G1FD.COM command file
4 NET_NODE
Logical name specifying the node to run the batch job.
Remember the double colon.
e.g.
DEFINE  NET_NODE  PHAST::
3 NETPRINT
Prints on any print queue on a remote node with arbitrary qualifiers.
Format:
       NETPRINT  file-spec[,...]

All PRINT qualifiers are accepted, including /QUEUE
and including positional qualifiers.
But some will not work in obvious or useful ways.
Wildcards may not work reliably ?

Currently prints only on PHAST:: since all printers are there.

NOTE:  All PHAST:: system-wide print commands are defined also
on the MicroVAXen modified properly to print on PHAST::
e.g. NEC,LASER,QNEC,QLASER
4 Parameters
file-spec
  a file on the local node to print on the remote node
4 Qualifiers
Same as for PRINT .  A trick has been employed to allow qualifiers
to immediately follow the command, e.g. NETPRINT/QUE=LASER filename
even though the command is implemented by a command file.
 
  /NOTIFY will only work if you are logged into the target node.
  /DELETE will only delete the temporary file from the target node
          (Default)
  /NODELETE will keep the temporary copy on the target node.
  /CONFIRM will not work properly, since you can not respond to its
           prompt (may hang)
  /BACKUP,/DATE,... will not work since they will be used at the
	remote node on the temporary file newly copied there.
3 TALK
The DECNET_DIR:TALK command file allows limited interactive use
of the remote node via a network object CONVERSE.COM .
Format:
	@DECNET_DIR:TALK

DCL command lines that TALK prompts for are sent to the CONVERSE
object running on the remote node and executed as DCL commands
and results are sent back to the user's terminal.  Some DCL commands
will not work and/or may hang the terminal (especially those which
are capable of using DECNET themselves such as MAIL, PHONE, SEND).
See HELP NETWORKS DECNET ATNODE CONVERSE .
3 ATNODE
The ATNODE command will run certain commands at the remote system.
Format:
         ATNODE  UWAPA1::  command  [parameters]

      command         what it does

        HELP		displays this text
        BILL            BILL command to see how much you owe there
        CONVERSE        displays output from commands 'til EXIT
        ONELINE         displays output from one command
        SENDME          notify yourself
        SHOWDEV		SHOW DEVICE
        SHOWMEM		SHOW MEMORY
        SHOWQ		SHOW QUEUE/ALL
        SHOWNET		SHOW NETWORK
        SHOWUSERS       SHOW USERS
        SHOWSYS         SHOW SYSTEM
        WHAT            WHAT

You might want to put the line
$ ATNODE :== ATNODE node::
into your LOGIN.COM command procedure file on PHAST::
to allow you to reduce your typing to
        ATNODE  command

4 CONVERSE
Format:
         ATNODE  node::  CONVERSE  dcl_command

Opens a pseudo-interactive session with the remote computer.
Please do not use this extensively as it runs a priority 4
process on the remote computer which is likely to interfere
with its truely interactive users.
Some commands may not work due to DECnet complications.

Prompts for input line after completion of previous comand's
output.

Interactive programs will not work since it can only display
output from programs.
4 ONELINE
Format:
        ATNODE  node::  ONELINE  dcl_command

Executes one DCL command on the remote node and displays the output.
4 SENDME
Format:
        ATNODE  node::  SENDME  text

Use quotes to keep lower case.  Truncates at 132 characters of text.
Prompts for text if not given on command line.

Useful as a command in remote batch jobs to notify yourself
upon completion or about errors.
5 Example
$!      BATCH.COM
$!
$ SET NOON	! handle errors myself
$ message="Finished PROGRAM."
$ ON ERROR THEN  message="Error during BATCH."
$ COPY  PHAST::DATA.DAT  *
$ COPY  PHAST::PROGRAM.EXE  *
$ DEFINE/USER_MODE  FOR002  DATA.DAT
$ ON ERROR THEN  message="Error during PROGRAM."
$ RUN PROGRAM
$ ON ERROR THEN  message="Error during BATCH."
$ DELETE  DATA.DAT;0
$ DELETE  PROGRAM.EXE;0
$ ATNODE  PHAST::  SENDME  "''message'"
!
4 Your_own
You may also write your own command files to run on a remote node
and copy them to your SYS$LOGIN: directory there, then
ATNODE  node::  filename      (no .COM allowed)
will execute the command file  node::SYS$LOGIN:filename.COM
and output will come back to your terminal if you put
$ DEFINE  SYS$OUTPUT  SYS$NET
at the beginning and
$ DEASSIGN  SYS$OUTPUT
at the end.  This is what NETSUBMIT and NETPRINT do.
See DECNET_DIR:*.COM for examples.
Contact MANAGER if you come up with useful ones.
2 ARPANET
A United States Defense Department Advanced Research Projects
(DARPA) sponsored computer network.
We can send MAIL and FILES to ARPANET computers via BITNET
(see HELP NETWORKS SENDGATE), or via UUCP.

