Notes on Customizing SYSGEN
	
	SYSGEN will allow the user considerable latitude in customizing
the UFD's and disks upon which sources exist and the UFD's and disks
upon which tasks and maps are output.  Why is this useful.  For one thing
we build non privileged tasks to TK:[1,53] and privileged tasks to 
TK:[1,54].  It will, however, allow one to have a variety of customized
privileged sources on [n,24] and build systems to [n,54].  Why you wonder
would you wish to do that?  Well if you have a variety of systems which
you are supporting on one large disk system, and some of the systems
are mapped, some unmapped, some use DCL and the queue manager, some don't,
some use the Full duplex driver, and some don't, it may be convenient
to seperate the sources and to build unique systems to UFD's other than
[1,54] and [1,50].

	This document sole purpose is to document some of the internal
sysgen symbols which I have come across.  Their definition and use is as
of BL30-BL31, but I don't think they have changed.  I have played with some
of these with success in the PRE2, PRE3 and CUSTOMIZE.CMD files.

	Symbol		If True
	
	$11M		RSX11M system, false otherwise
	$11MPL		RSX11M-Plus system, false otherwise
	$IAS		IAS system, false otherwise
	$MAP		Mapped system (always true for M-PLUS)
	$MAPM		Mapped system (true for mapped 11M, false for
			unmapped M, true for any M-plus, false for IAS)

	$FRLTK		FCSRES or SYSRES exists (M and IAS respectively)
	$FSLTK		FCSFSL exists (M=Plus)
	$FCSTK		FCS modules included in task image (no FCSRES)
	$EXRTK		Extended routines in task image - FCSRES and
			FCSFSL contain all of FCS plus $EDTMSG and 
			CSI$ while SYSRES (IAS) contains only a subset of
			FCS.  The additional routines in FCSRES and FCSFSL
			not found in SYSRES are called extended routines.
			False for 11M FCSRES and M-Plus FCSFSL
			True for IAS

	$ANFCS		FCS is ANSI
	$UTYP1		Set by XXXBLD.BLD file to tell SYSGEN3 whether 
			the $TYP1 string was used.  $TYP1 is used if
			FCSRES, FCSFSL, or ANSI versions of a task exist.
			If no FCSRES a TKB build command file might get
			created as FOOBLD.CMD.  However, the FCSRES version
			might be FOORESBLD.CMD and $UTYP1 would get set to
			tell SYSGEN3 that the $TYP1 string (RES) had gotten
			used.

	$RSLIB		Resident library name (FCSRES for M, but can
			be selected.  See CUSTOMIZE.CMD).
	$TYP1		Identifier in the middle of the command and ODL file
			names indicating the flavor of the task they will
			produce (RES, FSL, ANS).  
	$TYP2		Command line suffix for some task and map names.
			Not to my knowlege used by M, but can be set so
			SYSGEN3 will produce tasks such as PIPRES.TSK, etc
			so one can distinguish between tasks built with
			FCSRES, FCSPLS, of ANSILB and those built with 
			SYSLIB.
	
	$LIBOP		The TKB resident library option command line.
	$MUSW		"/MU" for multi-user M-Plus task.
	$MMSW		"/MM" for mapped 11M/M+.  "/-MM" for unmapped
			11M, null for IAS
	$DFLIB		Default system library for cmd and ODL files.
			Normally SYSLIB or ANSLIB.
	$TK		device and UFD for .TSK and .STB files
	$CL		device and UFD where .CMD and .ODL files are created.
	$OD		Device and UFD which the TKB command line uses for
			specifying the location of the ODL files.
	$MP		The device and UFD for the .MAP files
	$LI		device and UFD for the .OLB's other  than [1,1]SYSLIB
			of LB:[1,1]ANSLIB

	$DBF		Delete taskbuild command and ODL files after 
			taskbuilding.
	$BLD		Build the task.
	$EDF		Pause to edit task build command file

	$ANSLB		all tasks can use ANSLIB
	$ANSBB		Only task needing big buffering can link to ANSLIB