 
[352,4]README.1ST - Anaheim - Fall 1984 - Files submitted by:
 
			SRD Working Group
			Bob Turkelson
			NASA/Goddard Space Flight Center
			Mail Code 614
			Greenbelt, MD  20771
			301-344-9832
			FTS 344-9832
 
 
This UIC contains the files for building SRD V6.5.
 
The first two items below were described in an article in the
October 1984 issue of the Multi-Tasker.

The modifications made by the SRD Working Group since V6.4 are:
 
  o  Corrected a bug so that the diagnostic message for a corrupted date
	in a file header is not repeated for files with proper dates.

  o  Changed the date decoding routine so that it skips over the first
	byte of the date field if it is a blank.  When VMS BACKUP/IMAGE
	restores a Structure 1 disk, a file date with a single digit day
	of month is stored in the file header with a blank preceding the
	digit, rather than a zero character as is done in RSX.  (For
	example, " 4OCT84" rather than "04OCT84".)  Recently we learned
	that the RMS utilities DSP and BCK get file date errors when
	accessing such files.

  o  Added information to the /ID message telling which operating system
	and support features were specified when the SRD task was
	generated.

  o  Added support for named directories on P/OS and Micro/RSX.  Used
	decimal format for file version numbers in P/OS.  If named
	directories are not supported on a system, ignore any that exist
	in the MFD.  Note that this code has not yet been tested on
	these operating systems.  We will try to publish a report in the
	Multi-Tasker.  Thanks to Bob Denny, Richard Kirkman, and
	B. Z. Lederman for sending us their modifications for these
	systems.

  o  Added the /AP switch to append the listing to an existing file.
	If the named file does not exist, a new file will be created
	in most cases.  See the documentation for details.

  o  Changed the .PSECT attribute in the SRDXX1, SRDXX2, and SRDXX3 dummy
	routines so that SRD will work on RSX-11M V3.2.

  o  Modified the help and documentation files.


The *.C65 files are correction files which have already been applied to
the V6.4 source files.  They are provided here for reference purposes
only.  The *.MAC files are those for V6.5.

SRD.TSK is a task built with the default switches shown in SRDDEF.HLP;1.
It was built for RSX-11M V4.0/V4.1 with dynamic checkpoint allocation.

SRDMOD.DOC describes the past changes to this version of SRD.

SRDREF. is the text for a two-page SRD Reference Guide showing the
available switches.  Please send us any ideas you have for improving
its organization and content.  We will be updating it for each new
version.

 
Procedure:	@SRD		!  Asks configuration questions and
				!    builds SRD

		Copy SRD.HLP and SRDDEF.HLP to [1,2] and refer to SRD.HLP
		in [1,2]MCR.HLP.
		HELP SRD NEW will show users a list of the new switches.

 
Note that under RSX-11M V4.0 or later and RSX-11M-PLUS V2.0 or later,
the command string interpreter allows wildcards (* and %) anywhere in the
file name or type.  This eliminates the need for the /SE: switch in most
circumstances.  For example, SRD *AB%D*.%D* is valid.

Specify /-SR whenever you are looking for certain files and do not care in
what order they are listed.  You will save the time required for sorting
the directories.

The /CM switch should be used with /NV (or /SV) unless V is specified in
the second switch value and all versions are wanted.

The value specified in the /GT:n switch is a four-byte integer value on
RSX-11M V4.0/V4.1 and RSX-11M-PLUS V2.0/V2.1.  It is considered a two-byte
integer on V3.2.  Its use on V3.2 has not been tested.

The additions to the selection/listing overlay segment and the root
segment total about 140. words (when built without FCSRES).  This reduces
the largest directory section that can be handled at one time by one
block (out of about 110 blocks).  Each block contains up to 32 file
entries.

The SRD Working Group plans to make additional modifications for future
SIG tapes.  Command and help file improvements are planned as well as
program changes.  We recently expanded our wish-list, and a number of
changes are currently being implemented for the next version.
 
We would appreciate hearing from those who have made changes or plan to make
changes to this version, so we can continue to improve this useful utility.
Many thanks to those who have written.
 
[352,4]README.1ST - END

