Global: ^DIC(4.2

domain whose domain name consists of its name less the 1st dot piece.  For example:  A.DOMAIN.COM is administered by DOMAIN.COM.

The domain name may be from 1 to 64 characters.

Each dot piece may be up to 20 characters, and must begin with an alpha or numeric, and be composed of only alpha, numeric, or "-" characters.

^TMP("XMY0",$J,)="".  If the address is too long, it can cause an invalid subscript error.

1)= S ^DIC(4.2,"B",$E(X,1,30),DA)=""

2)= K ^DIC(4.2,"B",$E(X,1,30),DA)

S = Send.  MailMan should start a TaskMan task to transmit the message as soon as the message is received.

C = Close.  MailMan will not allow users to address mail to this domain.

Q or "" (the null string) = Queue.  MailMan will not deliver until a task is explicitly created to deliver the mail.

P = Poll.  A TaskMan task will poll all domains with this flag.

N = NO-forward.  MailMan will not allow messages to be forwarded to this domain.

T = Talkman enabled.  The presence of this flag allows Talkman to be used at your site.  It is also necessary to put a 'T' command into the script so that TalkMan will be invoked properly.

1)= I X["P" S ^DIC(4.2,"AC","P",DA)=""

2)= K ^DIC(4.2,"AC","P",DA)

This cross reference keeps track of domains that have the polling flag on.

This field, if defined, names a security key which must be held by the sender.  If the sender does not have this key, then he may not address this domain.

This field is used for security.  If filled in any messaging services that contact you will need to know the value of this field, or their requests will be ignored.  Messaging services = other MailMan domains.

READ AUTHORITY:   ^

Domain.

security, to insure that the sending domain establishes the link.

is defined to be San Francisco.

The relay domain overides any other path determination processes, such as scripts and parent domains.

text field is interpreted by the MailMan script processor.

There are commands to be used:

Open

Device

Wait

Xecute

Call

These commands are described in other documentation.

However, this field is also looked at by the name server to determine implicit routing.  The implication to the system, if this field is not defined is that the local system does not know how to deliver mail to this

domain.  (There are no directions in the form of a Transmission Script to tell MailMan what to do.)  Since, this system doesn't know how to deliver the message, it is assumed that the parent of this system does know.

Therefore, if a domain has no data at all in the Transmission Script field, MailMan routes messages sent to it to the local domain's parent.  This often occurs with subdomains.    No protection exists to prevent infinite

loops of transmissions that can occur when the parent has no entry for the subdomain and therefore implicitely assumes that it should route the message to the subdomain's creator.  Other problems that do not cause systems

to be misued have can still occur, also.

NETWORK NOTES should be used to document idiosyncracies which occur when communicating with the domain in question.

Other names by which this domain is known.

This is the domain's station.

This is a three character routing indicator for the VADATS network's MCTS terminal system.

This field is used to route messages when they arrive at the central data collection point at the domain FOC-AUSTIN.VA.GOV.

1)= S ^DIC(4.2,"AD",$E(X,1,30),DA)=""

2)= K ^DIC(4.2,"AD",$E(X,1,30),DA)

This field contains a logical or physical address of a remote domain so that a connection can occur.

This field contains the IP address of this host so that it can be used as the to address for files that will be sent to this domain.

.

1)= S ^DIC(4.2,"D",$E(X,1,30),DA)=""

2)= K ^DIC(4.2,"D",$E(X,1,30),DA)

3)= If this cross reference is deleted, netmail may not be transmitted.

1)= S ^DIC(4.2,"ATCP",$E(X,1,30),DA)=""

2)= K ^DIC(4.2,"ATCP",$E(X,1,30),DA)

This cross reference is used by XMRTCP to poll domains that have messages to be sent out.  TaskMan does not run on the node that has the TCP/IP device sometimes.

There are really two pieces of data in this field separated by a ";".  Piece number 1 is the username.  Piece number 2 is the password.

This field contains the directory into which a file should be put by a domain sending it files to attach to multimedia messages.

If this domain belongs to a poll list, then it will be activated when a background poller is activated to send mail to this list.

4.3 is used.  If there's no device named in that field, then there is no device.  If this domain has a physical link such as a miniengine port, a direct line to another cpu, a modem, etc., this port should be named in this

field to direct network mail to the proper output device.  There must be an entry in the DEVICE file for this cpu port.  The name field of the DEVICE file can be a literal (such as MINIENGINE-OUT or CPU B LINK) but the $I

field must match with the correct cpu $I.  If the link is physically located on a cpu other than the one the network mail is being sent from, the local DEVICE file MUST reflect that in the OTHER CPU field of the device

file if the transmission is to take place immediately.  If it is not identified properly, the message will go into a queue to be processed the next time a network message is sent from or recieved on the processor with the

physical link.  NOTE:  The DEVICE files on all cpu's must have matching device names to correctly route the message to the proper cpu for sending.

9.2 = S Y(4.2,20,1)=$S($D(^DIC(4.2,D0,0)):^(0),1:"") S X=$P(Y(4.2,20,1),U,1),Y(4.2,20,2)=X S X=".",Y(4.2,20,3)=X,Y(4.2,20,4)=X S X=$P(Y(4.2,20,1),U,1)

The most right "." piece of a domain name ($P(domain-name,".",$L(domain-name,"."))

9.2 = S Y(4.2,21,1)=$S($D(^DIC(4.2,D0,0)):^(0),1:"") S X=$P(Y(4.2,21,1),U,1),Y(4.2,21,2)=X S X=".",Y(4.2,21,3)=X,Y(4.2,21,4)=X S X=$P(Y(4.2,21,1),U,1)

$P(domain-name,".",$L(domain-name,".")-1)

9.2 = S Y(4.2,22,1)=$S($D(^DIC(4.2,D0,0)):^(0),1:"") S X=$P(Y(4.2,22,1),U,1),Y(4.2,22,2)=X S X=".",Y(4.2,22,3)=X,Y(4.2,22,4)=X S X=$P(Y(4.2,22,1),U,1)

$P(domain-name,".",$L(domain-name,".")-2)

9.2 = S Y(4.2,23,1)=$S($D(^DIC(4.2,D0,0)):^(0),1:"") S X=$P(Y(4.2,23,1),U,1),Y(4.2,23,2)=X S X=".",Y(4.2,23,3)=X,Y(4.2,23,4)=X S X=$P(Y(4.2,23,1),U,1)

9.3 = X ^DD(4.2,23,9.2) S Y(4.2,23,5)=X,X=".",Y(4.2,23,6)=X,X=$L(Y(4.2,23,5),X),Y(4.2,23,6)=X,Y(4.2,23,7)=X S X=9

$P(domain-name,".",$L(domain-name,".")-3)

If the value is null or zero, no request will be made.  If the value is a positive integer, a request will be made at the same time as other domains with the same number in this field are made.  A task must be set up and

scheduled for each number assigned using the XMDIR-REQUEST-ALL option, which is then run every 90 days (or according to what you change the reschedule value to).

1)= S ^DIC(4.2,"AE",$E(X,1,30),DA)=""

2)= K ^DIC(4.2,"AE",$E(X,1,30),DA)