clients

AutoRouter Clients

The following table shows how AutoRouter provides local routing services to client applications. Clients use either VMS Mailbox or UNIX FIFO devices, and are invoked or enabled with the indicated options.
Type Mailbox/FIFO Names Invocation and Enabling Special Notes

AutoMan MBX_xxxxxxxx.PROMIS OPTION_AUTO = YES
AUTO_<func>_<eqpid> = <eqpid@node> AutoRouter will timeout the connection and terminate Automan after 10 minutes of idle time.
The first 4 characters of the 8-digit hex number xxxxxxxx are the last 4 characters of the process pid.

Standalone HS Objects and Instances VMS:
MBX_object
MBX_instance.object

UNIX:
$AUTOFIFO/object
$AUTOFIFO/instance.object Incoming CONNECT message where target=object

UNIX:
hs ñf $(AUTORUN)/object.hyp -e CONNECT -e DISCONNECT -e ABORT ñl $($AUTOLOG)object.log

VMS:
$ set proc/name=object
$ @aeq_ssp:hs
HS may execute an instantiate function to create a unique 8-digit hex instance name AutoRouter will timeout instance connections after 10 minutes of idle activity.
AutoRouter will not timeout object connections.
Dead FIFO's (no readers) are dropped after 10 minutes.

PROMIS
HS
Objects and
Instances VMS:
MBX_xxxxxxxx.object
MBX_object Incoming CONNECT message with target=object

VMS:
$ set proc/name=object
$ @aeq_ssp:mm
HS may execute an instantiate method to create unique 8-digit hex instance name AutoRouter will timeout instance connections after 10 minutes of idle activity.

VMS Servers MBX_PROT
MBX_ZORCH
MBX_PRIF @aeq_ssp:autostart name
Registers with AutoRouter using CONNECT message AutoRouter will never timeout object connections.

FASTechDMBX Action Schedules schedule.mbx
schedule_i.mbx Registers with AutoRouter using DISCONNECT/CONNECT sequence. AutoRouter will never timeout DMBX connections