PMDF System Manager's Guide
Previous Contents Index

26.1.1 Setting Up the Channel

Two or more channels are needed for PMDF for OpenVMS to communicate using CETS UUCP. A single common channel is used for all incoming messages, no matter from what system they originated. An additional channel is needed for each system connected via UUCP. The incoming message channel is slave-only and should never have any messages queued to it. The outgoing message channels are master-only.

26.1.1.1 Adding the Channel to the Configuration File

The entry for the incoming message channel should look like this (do not use a different channel name): 


vn_gateway uucp slave 
vn-gateway
The official channel host name (the second line of the channel definition) is arbitrary, but is usually specified as vn-gateway, e.g., 


vn_gateway uucp slave 
vn-gateway

Entries for outgoing UUCP message channels will vary depending on the name of the system to which the channel connects. For example, suppose the remote system's official name is YMIR.CLAREMONT.EDU and its UUCP name is simply ymir. A channel definition for this system might be: 


vn_ymir uucp master 
ymir-uucp 
ymir.claremont.edu ymir

In this case the name of the remote host to which the channel connects is derived from the channel name. When a second channel connecting to the same remote host is needed, it can be defined as follows: 


vn_second uucp master daemon ymir 
ymir-second 
ymir.claremont.edu ymir

In this case the daemon channel keyword has been used to explicitly specify the name of the remote system to which the channel connects.

If the official name and UUCP name are the same, ymir, the entry can be simplified: 


vn_ymir uucp master 
ymir

Rewrite rules should be set up to point at the proper outgoing channel using the channel's official host name.

26.1.1.2 Setting Up the Master Program

Once the CETS UUCP channels have been added to the configuration file, the UUCP master program should be ready to use. No additional log, script or option files are needed; all such information is part of CETS UUCP.

26.1.1.3 Setting Up the Slave Program

The uucp_slave program is used as the rmail image. The file that is named UUCP_BIN:uuxqt_dcl.com must be edited to add an rmail command that invokes uucp_slave. As of CETS UUCP V1.1, the change consisted of removing all the code between the labels DO_RMAIL: and FAILED_RMAIL: and replacing it with the following: 


$       on warning then goto failed_rmail 
$       pmdf_privilege_save = f$setprv("BYPASS, CMKRNL") 
$       rmail = "$PMDF_EXE:uucp_slave.exe" 
$       define/user SYS$INPUT 'infile' 
$       rmail "''addressee'" 
$       delete 'infile';0 
$       delete 'xfile' 
$       pmdf_privilege_save = f$setprv(pmdf_privilege_save) 
$       goto read_loop
As of CETS UUCP V2.0, you would have to change 


$       rmail = "$PMDF_ROOT:[EXE]uucp_slave.exe"
To 


$       rmail = "$PMDF_EXE:uucp_slave.exe"
and also add the following line to your UUCP_CFG:control. file. 


UUCP_UUXQT_DCL_RMAIL_PMDF  "YES"
Future releases of CETS UUCP will probably include PMDF support, so this edit will no longer be required.

Note
The account under which remote UUCP connections log in to your system must be capable of reading and writing files in the PMDF queue and PMDF log directories, (i.e., in the directories PMDF_QUEUE: and PMDF_LOG: on OpenVMS) for proper operation. Protections or privileges should be set to allow this access.

Previous Next Contents Index