This submission contains three items:


[.PRC.BACKUP]*.*

    A captive command procedure for doing system backups in a consistent
    manner.  The main features are: 

	The backup command procedure implements the backup schedule suggested
	in the Guide to VAX/VMS System Management and Daily Operations manual.
	The suggested schedule is as follows: 

	    Daily incremental backups are performed Monday through Saturday. 

	    Weekly incremental backups are performed on all Sundays except the
	    first Sunday of the month. 

	    Image backups are performed on the first Sunday of each month. 

	All defaults are determined by the command procedure including type of
	backup and disks to be backed up.  However, all defaults can be
	overridden. 

	The backup command procedure can type a file on the system console to
	relay special instructions for the backup procedure.  These special
	instructions could be to override either the type of backup to
	perform, the list of disks to be backed up, or the backup date for a
	Weekly backup. 

	The default list of disks to be backed up can be either all disks on
	the system, a restricted group of disks or an explicit list of disks. 

	The tape device to be used can be selected from any on the system,
	with preference given to certain types of tape drives or particular
	individual drives. 

	The recording density used can be specified explicitly or the command
	procedure can select the highest density that the allocated tape drive
	supports. 

	For Image backups, the backup command procedure will force users to
	logout, if necessary, to insure a complete backup of the disks. Before
	an image backup of the system disk the command procedure instructs the
	operator how to boot Stand-alone BACKUP, what command to use to backup
	the system disk, and how to re-boot VAX/VMS, before performing a
	system shutdown. 

	The BACKUP commands issued by the command procedure create a BACKUP
	journal file which can be used to locate files to be restored.  The
	command procedure also maintains a log of the backups that are
	performed. Log file entries record the type of backup performed, the
	date and time of the backup, the list of disks that were backed up,
	and the backup date for Weekly backups. 

    For complete information RUNOFF the file BACKUP.RND. 


[.PRC.KERMIT]*.*

    An copy of VMS Kermit (version '3.0.052') distribution with several bug
    fixes and updates.  See the file CHANGES.DIF for complete descriptions of
    the changes.  These changes include: 

	Restricting the "SET RECEIVE PACKET_LENGTH <number>" and "SET SEND
	PACKET_LENGTH <number>" commands to specifying a maximum value for
	<number> of 94 instead of 96. 

	Correcting the descriptions of the "SET RECEIVE PACKET_LENGTH
	<number>" and "SET SEND PACKET_LENGTH <number>" commands to indicate
	that the maximum value for <number> is 94 instead of 96, and to
	"quote" some characters that RUNOFF was interpreting as special flag
	characters. 

	Increasing the size of the buffers used for packets sent and received.
	While the buffers were large enough for the maximum size of a Kermit
	packet, they did not include space for a line terminator character. 

	Restoring the transmission terminal's parity settings and <CR> and
	<LF> fill counts. 


[.PRC]PARITY_FLAGS.DOC

    This file contains some documentation on the format of the Parity Flags
    field in the IOSB of the Terminal Driver's Set/Sense Mode/Characteristics
    I/O functions that is not contained in the I/O User's Reference Manual. 
    In the process of fixing a problem in VMS Kermit that cropped up under VMS
    V4 I found that the format of the Parity Flags field was not documented. 
    With the help of DEC's Customer Support Center and some microfiche reading
    I was able to determine the format of some of the information returned in
    the Parity Flags field. 


Jim Noble
Mail Stop 5S3
Planning Research Corporation
1500 Planning Research Drive
McLean, VA  22102

(703) 556-1394