Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dots(5) [ultrix man page]

DOTS(5) 							File Formats Manual							   DOTS(5)

Name
       DOTS - Data Object Transport Syntax (DOTS) files

Description
       Data  Object  Transport	Syntax	(DOTS)	is  DDIS/ASN.1 encoding for encapsulating the encoded interchange form of a number of related data
       objects.  Data objects must be related by having embedded references to other objects in the same  DOTS	encapsulation.	 Typically,  these
       embedded  references depend on the storage address (for example, filename) of the referenced object.  Therefore, when the referenced object
       is moved from one location to another, the storage address must be updated.

       The purpose of DOTS is to allow composite data objects to be moved from one location to another as a single object and to allow the  neces-
       sary storage reference to be updated as part of the process.

       The  primary  use for DOTS is moving multifile compound documents in which one DDIF or DTIF file may have reference data stored in a physi-
       cally separate file.  Mail is a major vehicle for moving DOTS objects.

       The commands and are used to pack and unpack DDIF and DTIF files.  The commands can also be used to copy a related  set	of  DDIF  or  DTIF
       files, or both, from one location to another.

See Also
       ctod(1), dtoc(1), DDIF(5), DTIF(5), DDIS(5), CDA(5)

																	   DOTS(5)

Check Out this Related Man Page

capsar(1)						      General Commands Manual							 capsar(1)

Name
       capsar - prepares documents not in ASCII format for transport in the mail system

Syntax
       capsar [-c] [-t] [-x[hTD]] [file]

Description
       The  utility  allows  ULTRIX mail to support documents containing non-ASCII data, such as DDIF.	Only the DDIF and DOTS data types are cur-
       rently supported.  DDIF is Digital's standard format for document interchange. DOTS is an encapsulation of the encoded interchange form	of
       a number of related data objects into a single composite object.  For more information, see and

       The utility prepares a DOTS file or a DDIF document for transport in the mail system by performing the following steps:

       1)    The DDIF document is converted to DOTS format.  As a DDIF document may contain more than one file, all files within the DDIF document
	     are incorporated into one DOTS file which can be sent as one mail message.

       2)    Each DOTS file is then compressed and encoded using only printing ASCII characters.   This is because ULTRIX mail software only  sup-
	     ports 7 bit mail.

       3)    The  routine  encapsulates  coded	documents by adding leading and trailing lines, each surrounded by a <CR>.  The lines should begin
	     with 2 or more dashes (-) and some text that indicates the nature of the encapsulated message. The following is  a  typical  encapsu-
	     lated mail message:
	     To: anybody@anynode
	     Cc:
	     Subject: Another DDIF document

	     -----------motd.ddif : DOTS.ctod.compress.uuencode message

	     begin 0 motd.ddif
	     M__]@*" ,(" !BO.#P$# 8$* &UO=&0N9&1I9H0$)%546     "A@"B !@8K
	     MS@ P$''T1$248M96YC;V1E9"!R979I<V%B;&4@9&]C=6UE;G2@@/__?X"@
	     M@( ! 8$! ((/1$1)1B1?4D5!1%]415A4HX#)% !$1$E&(%1E>'0@1G)O;G0@

	     end

	     -----------End of motd.ddif : DOTS.ctod.compress.uuencode message
	     The command can also extract different parts of a mail message, namely, the header information, the text part of the message, and the
	     DOTS file that was encapsulated as described above.

       Extracting the DOTS file is done by parsing the mail message and detecting the leading and trailing encapsulation boundaries.  Decoding and
       uncompressing the data results in the original DOTS file.

       The utility is built into Rand MH to provide DDIF mail support.	It can, however, be used with mail.

Options
       -c   Causes to create an encapsulated DOTS bodypart from file. The file must be a DOTS/DDIF type document.

       -t   Causes to write to the standard output the message type of file. Message type can be either text or DOTS.

       -xh  Extracts  the mail header lines from file.	The header line must be at the beginning of the file and separated from the remaining text
	    by a <CR> or <CRLF>.  Each header line is a string containing a header field name (for example, Subject), a colon  (:),  one  or  more
	    spaces,  and  a  field  value.  Each header line may have embedded continuation sequences it it (for example, LF followed by spaces or
	    tabs).

       -xT  Extracts all the text parts of the mail message in file to the standard output.

       -xD  Extracts any DOTS bodyparts in file. The DOTS document is sent to the standard output.  This is the reverse of the -c option above.

	    The file must be specified for the -c option.  If file is not specified with the -x or -t option then the standard input is used.

Examples
       The following are examples of how to use the command:

       Encapsulates a DDIF document
       capsar -c file.ddif | more

       Lists the header line from the mail message
       capsar -xh file.mail

       Extracts the encapsulated DOTS file from the file
       capsar -xD file > file.dots

	    or

       capsar -xD file | dtoc

       In order to mail a DDIF/DOTS document you can use one of the following:
       capsar -c file.ddif | mail -s "subject" address

       capsar -c file.ddif | mhmail -subject "subject" address

       Use the second command if you are using RAND mh.

       A DOTS file is extracted from dxmail first extracting the message into a file. The dxmail utility has an extract feature built in so  isn't
       needed.

See Also
       compress(1), ctod(1), dtoc(1), mail(1), mh(1mh), mhmail(1mh), uuencode(1), vdoc(1), prompter(1mh), DDIF(5), DOTS(5)

																	 capsar(1)
Man Page