.PAGE SIZE 58, 68
.RIGHT MARGIN 68
.TITLE Starting the All-In-1 to Message Router Batch Jobs
.SUBTITLE B.#Z.#Lederman
.CENTER
Starting the All-In-1 to Message Router Batch Jobs
.BLANK.CENTER
Automatically during System Startup
.BLANK 2.CENTER
Bart#Z.#Lederman
.BLANK.CENTER
ITT World Communication
.BLANK.CENTER
New York, NY 10004-2464
.PARAGRAPH
All-In-1 V2.1 uses the Message Router and Message Router VMS Mail
Gateway to exchange electronic mail between All-In-1 users and VMS
Mail users on the same system (node), or on different systems (nodes
in a network). In order for this to work, however, there must be two
batch jobs scheduled to run at regular intervals which exchange mail
between the Message Router and All-In-1. For example, with all of
the Message Router products installed and running, a SHOW#QUEUE/ALL
command should look something like this (you will see two sets of
queues here as I have a two node cluster):
.BLANK.NO JUSTIFY.NO FILL
$ show queue/all
Generic batch queue MB$BATCH
.BLANK
  Jobname     Username     Entry  Status
  -------     --------     -----  ------
  MB$MR       MRMANAGER    1765  Holding until 13-MAR-1987 09:17
  MB$MG       MRGATE       1769  Holding until 13-MAR-1987 09:22
  MB$NET      MRMANAGER    1770  Holding until 13-MAR-1987 09:27
.BLANK
Batch queue MB$BATCH_SYS30, on SYS30::
.BLANK
Batch queue MB$BATCH_SYS31, on SYS31::
.BLANK
Generic batch queue SYS$BATCH
.BLANK
Batch queue SYS30_BATCH, on SYS30::
.BLANK
Batch queue SYS31_BATCH, on SYS31::
.BLANK
  Jobname     Username     Entry  Status
  -------     --------     -----  ------
  MRTOVMS     MRGATE       1777  Holding until 13-MAR-1987 09:20
  OAMTISEND   ALLIN1       1782  Holding until 13-MAR-1987 09:23
  OAMTIMAIL   ALLIN1       1784  Holding until 13-MAR-1987 09:28
  MRTIDY      MRMANAGER    1717  Holding until 14-MAR-1987 03:00
.BLANK.JUSTIFY.FILL
The two jobs which exchange mail between All-In-1 and the Message
Router are OAMTISEND and OAMTIMAIL. The other jobs (MRTOVMS, MRTIDY,
etc.) are automatically started when your system is booted by the
Message Router or Message Manager startup command files (if you have
followed the installation instructions and added the command files
to your SYSTARTUP.COM file), but the two All-In-1 jobs are NOT
started: you have to manually start them using All-In-1. I find this
inconvenient: I would much rather have everything start
automatically when I boot my system. To solve this problem, I have
developed a batch procedure which can be invoked during system
startup to insure that everything is running.
.PARAGRAPH
To invoke this command procedure, you must submit a batch job AFTER
the queue manager has been started, and AFTER All-In-1 has been
started. Normally, in your SYS$MANAGER:SYSTARTUP.COM file you will
have the command to start the queue manager before you invoke the
All-In-1 startup command file: therefore, you can make a simple
change to SYS$MANAGER:A1V2START.COM shown here between the rows of
exclamation points:
.BLANK.NO JUSTIFY.NO FILL
$ ! Run ALLIN1 to install the forms and TXL libraries
$	set noon
$	ALLIN1/NOINIT
oa$fbt_remove_lib oa$lib:memres
oa$fbt_remove_lib oa$lib:oaform
oa$txl_remove
oa$fbt_install_lib oa$lib:memres
oa$fbt_install_lib oa$lib:oaform
oa$txl_install
$!
$ !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
$!
$! Make certain the mail queues have started.
$! Must be a batch job as it has to run in the
$! ALLIN1 account.
$!
$! B. Z. Lederman
$!
$ submit/noprint/user=ALLIN1 sys$manager:a1mailstart.bat
$!
$ !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
$!
$	set on
$!
.BLANK.JUSTIFY.FILL
The batch file A1MAILSTART.BAT looks like this:
.BLANK.NO JUSTIFY.NO FILL
$! This should startup the All-In-1 to Message Router
$! batch queues.
$!
$! B. Z. Lederman	12-Mar-1987
$!
$ ALLIN1/USER=MANAGER/NOINIT
COMMAND EMCONTROL SS
COMMAND EMCONTROL SF
$!
$ PURGE A1MAILSTART.LOG
$!
$ EXIT
.BLANK.JUSTIFY.FILL
The reason for making this a batch job is because you usually have
to be in the (All-In-1) MANAGER account, or another privileged
account, to invoke commands like starting and stopping mail. The
default profiles for All-In-1 require that you be in the (VMS)
ALLIN1 account in order to use the (All-In-1) MANAGER account, so by
submitting the batch job with the /USER=ALLIN1 qualifier, I insure
that the job will be done in the proper account. Also, my system
startup is a little faster because I don't have to wait for All-In-1
to do the work of starting the queues.
.PARAGRAPH
It was stated earlier that the All-In-1 batch jobs don't start
automatically. In practice, this depends upon what state the batch
queues are in when the system shuts down and re-boots. It is
possible for a batch job which was scheduled before the system shuts
down to still be scheduled when the system re-boots: but it is also
possible for batch jobs to be "lost", especially if you have to
re-initialize the queue manager. This procedure is intended to
insure that all of the necessary batch jobs are started when the
system is re-booted regardless of the state of the queue manager.