 	[VAX000]SUBMIT.TXT     M SUGGESTIONS REGARDING THE SUBMISSION OF SOFTWARE FOR THE VAX SYSTEMS SIG TAPE   N These suggestions are not to be considered as requirements for the acceptance J of software for the tape.  They are intended to help make the structure of( the submissions somewhat more consitent.  J 1.  If your submission is large or naturally fits into several directories submit it as a directory tree.  J 3.  There should be ONE AAAREADME.TXT with each submission.  The followingE information should be included for each program or group of programs:   ; 	a.  A brief description of the program or group of related  	programs.    < 	b.  The names of previous submissions which this submission
 	replaces.  = 	c.  The name of the person primarily responsible for putting  	the submission together.   ? 	If you use RUNOFF to generate this file don't hide the source  I under another name, use AAAREADME.RNO.  TEMPLATE.RNO contains the primary 5 runoff commands needed to generate this type of file.   I 4.  There should be sufficient documentation for each program or group of H programs.  The file containing or pointing to this documentation should I have a .DOC extension.  If your documentation is somewhere else, say, as  J comments in the program, a .DOC file is still useful to tell people where K to find the it.  This is good place to put the name of the author, whether  J or not he is interested in bug/improvement reports, and, if he is willing . to take telephone inquiries, his phone number.  C 5.  The intent of the above paragraphs is to provide two levels of  H documentation - one very brief which is available in each submission as H AAAREADME.TXT or collectively in [VAX000]AAAREADME.yyy and another with K more detail in files with a .DOC extension.  The first idea is enforced on  H most of the recent tapes with AAAREADME.TXT's added by the librarian as J necessary.  The second part is more a request than a requirement but some 5 file renaming has been done to fit into this pattern.   # 6.  Making and submitting the tape.   = 	a.  If you are submitting a single directory use either COPY < 	or BACKUP.  BACKUP is preferred.  For multiple directories @ 	use BACKUP.  If you must use some other format, please CLEARLY = 	indicate the format on the tape label and, if possible, the  0 	commands necessary to copy the tape on a VAX.    A 	b.  Do not be too restrictive with file protection.  BACKUP can  @ 	make things difficult. Also please try to make your tapes using> 	the /INTERCHANGE switch of BACKUP (at least on the first copy= 	of what you submit) so that ACLs will be stripped. These can ' 	produce all kinds of weird collisions.   8 	c.  Use a density of 1600 bpi and be aware that 1600 is> 	not always the default.  Use the /DENS=1600 qualifier in your6 	BACKUP command to insure that the density is correct.  A 	d.  Take or send the tape to the next symposia and submit it at  A 	the DECUS Library booth on Monday or Tuesday or send it, with a   	signed release form to:   		Glenn Everhart 		25 Sleigh Ride Rd  		Glen Mills, PA 19342 		(215 358 3866)  6 		(Tapes mailed can be accepted at 800, 1600, or 6250.9 		 Tapes turned in at a symposium should be 1600.  RX01,  5 		 RX02, or RX50 may be submitted also, but the media 3 		 may have to be taken away from the symposium, so 6 		 return of same may be more difficult to arrange. We7 		 will contrive to read almost anything a VAX or PDP11 8 		 can write, but only 1600 or 6250 BPI tape can be read" 		 at the symposium and returned.)  @ 	e.  Pick up your tape at the Library booth later in the week.  ) 	They are usually available on Wednesday.   ? 	f.  Submissions at symposia should be in by mid afternoon (4PM : 		or so) on Tuesday if at all possible; the merger process8 		sometimes is started early and adding late submissions 		is difficult.   1 		Late submissions may have to be taken away from 2 		the symposium and returning media will be harder 		to arrange. 