From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 10-AUG-1989 18:12
To:	MRGATE::"ARISIA::EVERHART"
Subj:	VMS_SHARE (7.1-004) 8/8

Message-Id:  <8908102136.AA01839@crdgw1.ge.com>
Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Thu, 10 AUG 89 11:48:37 PDT
Received: from NSFnet-Relay.AC.UK by KL.SRI.COM with TCP; Thu, 10 Aug 89 11:35:19 PDT
Received: from oak.cc.kcl.ac.uk by NSFnet-Relay.AC.UK   via Janet with NIFTP
           id aa09581; 10 Aug 89 18:21 BST
Date: 		Thu, 10 AUG 89 18:18:33 GMT
From: UDAA055%oak.cc.kcl.ac.uk@NSFnet-Relay.AC.UK
To: info-vax <@NSFnet-Relay.AC.UK:info-vax@kl.sri.com>
Subject:        VMS_SHARE (7.1-004) 8/8
Sender: "JANET UDAA055@UK.AC.KCL.CC.OAK" <UDAA055%oak.cc.kcl.ac.uk@NSFnet-Relay.AC.UK>
Mailer:         Janet_Mailshr V3.4 (23-May-1989)

-+-+-+-+-+-+-+-+ START OF PART 8 -+-+-+-+-+-+-+-+
Xof their file name.
X
X
X5.3 Exclusion by type
X
XIf the logical name  SHARE_EXCLUDE_TYPES is defined with a comma-separated l
Vist
Xof non-wildcarded file types, then any file which has a similar file type
Xspecification will be excluded from the share file.`032
X
XFor example,
X
X   $ define share_exclude_types ".EXE,.DIR,.OBJ"
X
XAny files with these file types will be excluded. Files with a type of .DIR`
V032
Xare always excluded regardless.
X
XIf the logical name is not defined, then files are not excluded on the basis
V`032
Xof their file type, except that .DIR files are always excluded.
X
X
X
X5.4 Logging
X
XInformational messages are normally sent to SYS$OUTPUT by default. The logic
Val`032
Xname SHARE_LOG can be defined with a TRUE or FALSE value to determine whethe
Vr`032
Xsuch messages are produced.  If undefined, a TRUE value is assumed.
X
XFor example:
X
X   $ define SHARE_LOG FALSE
X
Xwill turn off informational messages.
X
XNot all messages can be turned off. In particular, error messages are always
V`032
Xproduced on SYS$ERROR.
X
X
X
X5.5 Setting the size of a part
X
XEach part of the share file is limited to a maximum size of 30 blocks by`032
Xdefault. VMS_SHARE will split at a point just below this in general (never`0
V32
Xabove) to guarantee that no share file part is more than 30 blocks long.
X
XThe default of 30 blocks can be changed by defining the logical name`032
XSHARE_PART_SIZE to whatever size is required. The only restriction is that i
Vt`032
Xmust be a minimum of 6 blocks. Values below 6 are treated as 6.
X
XWhen determining the best part size to use, remember that passage through`03
V2
Xmail systems generally add a lot of headers to the message, increasing its`0
V32
Xsize by several blocks. Allow for this when choosing the maximum part size.`
V032
X
XFor example:
X
X   $ define SHARE_PART_SIZE 200
X
Xchanges the maximum part size to 200 blocks.
X
X
X5.6 Inclusion of user's real name
X
XIf the logical name SHARE_REAL_NAME is defined, then its value is included`0
V32
Xfollowing the username at the head of the created share file. The normal`032
Xtranslation of this logical name should be the user's real name.
X
XFor example:
X
X   $ define SHARE_REAL_NAME "Fred Smith"
X
X
X5.7 Location of temporary files
X
XVMS_SHARE creates temporary files in the SYS$SCRATCH directory with a unique
V`032
Xname based on the process identification number.  If the logical name`032
XSHARE_TEMP is defined, this redefines the name/location of the temporary fil
Ve.
X
XFor example:
X
X  $ define SHARE_TEMP SYS$SCRATCH:DUMMY.TMP
X
Xredefines the temporary file name.
X
X
X5.8 Verification
X
XIf the user has read access to the procedure, then verification of its actio
Vns`032
Xmay be turned on by defining the logical name SHARE_VERIFY to have a TRUE`03
V2
Xvalue. If the logical name is undefined or has a FALSE value then no`032
Xverification takes place.
X
XFor example:
X
X   $ define SHARE_VERIFY TRUE
X
Xturns on verification IF the user has read access.  In general, only the`032
Xsystem manager has read access to the procedure and so this option is`032
Xrestricted.
X
X
X`012
X6.`009HOW TO UNPACK A SHARE FILE
X
X6.1 Command file
X
XA share file is designed to be run as a command procedure which will recreat
Ve`032
Xthe original source files. So in theory, it is simply necessary to extract t
Vhe`032
Xreceived mail message into a file, remove the mail headers, and then run it
V as`032
Xa command procedure.
X
XFor a single part share file, the following sequence of commands is necessar
Vy:
X
X     $ SET DEFAULT <scratch directory>
X     $ MAIL
X     MAIL>   READ <share file message part 1>
X     MAIL>   EXTRACT/NOHEADER file
X     MAIL>   EXIT
X     $
X     $ @file
X
X
X
X6.2 Dealing with multiple part share files
X
XThe recipient of a multi-part package sent in this form will receive a numbe
Vr
Xof separate mail messages - one per part - but not necessarily in the correc
Vt
Xnumeric order. These individual messages must be extracted into a file and
Xcombined into one file. The exact sequence of events is similar to above but
V`032
Xslightly complicated by the need to extract them in the right order and appe
Vnd`032
Xthem into a single file:
X
X     $ SET DEFAULT <scratch directory>
X     $ MAIL
X     MAIL>   READ <share file message part 1>
X     MAIL>   EXTRACT/NOHEADER        file
X     MAIL>   READ <share file message part 2>
X     MAIL>   EXTRACT/NOHEADER/APPEND file
X     MAIL>        ... repeat last two steps for each part in sequence
X     MAIL>   EXIT
X     $
X     $ @file
X
XStrictly speaking, it is not necessary to remove the mail headers from each`
V032
Xpart except the first, as the share file format is designed to skip these`03
V2
Xautomatically.
X
XIt is important to note that ALL parts must be extracted, and in the right
Xorder, before trying to unpack. It is not possible to unpack each part
Xindividually.`032
X
X
X
X
X7.`009REFERENCES
X
XThe following references provide further information on VMS_SHARE and are`03
V2
Xprovided with each release of the software.
X
X`0911`093`009VMS_SHARE Technical Information supplement
X`0912`093`009VMS_SHARE Release notes
X`0913`093`009On-line HELP
$ CALL UNPACK VMS_SHARE.USER_GUIDE;7 574604463
$ v=f$verify(v)
$ EXIT

