The following are informal notes on running Decus C on the PRO-350
under the native toolkit.

1.	The compiler image should be patched to redefine the
	#include <file.h> library to [ZZDECUSC] by adding the
	following to the link command file when you build
	the CC compiler.

	GBLPAT=CC000:SYSINC:41114:55472:55132:42504:52503:41523:00135

	Copy the compiler and assembler to the PRO hard disk
	into APPL$DIR:.  Copy the .h files (from the command
	directory on the Decus C distribution kit) to [ZZDECUSC].
	Then, copy the object libraries (C.OLB and CX.OLB) to
	[001005] on the PRO hard disk.

2.	Task images should be linked on the PRO using the native
	toolkit linker.  Alternatively, you should copy the
	native toolkit system library to your host development
	system and use it as the default library.  If this isn't
	done, Decus C programs can't open files on the PRO.
	
	For example, on a Vax/VMS system, you might copy the
	native toolkit system library [001005]SYSLIB.OLB to
	your default login directory.  Then, you would link
	PRO applications using a PRO task builder command line
	of the form:

	MCR PROTKB task/CP=objects,C:CX/LB,C:C/LB,SYS$LOGIN:SYSLIB/DL

	(Don't forget to make the task image checkpointable.  The
	/DL switch defines a default library.

3.	The following notes may help you to build an installable image.
	They are rudamentary, and may not be complete.  Clearly,
	all features of P/OS aren't available.

	Installable applications need a P/OS installation file.
	For a standard Decus-C program, this would look something like:

	NAME "DECUS/C Application For The PRO"	! Default Menu Entry...
	FILE decusapp.tsk/delete	! Application image file
	FILE decusdat.dat/delete	! Data files...  See below
	INSTALL decusapp.tsk/task	! Install the task file
	RUN decusa			! Run the application.

	To make an installable application diskette, you create a
	directory with some name, say [DECUSCAPP] and you put an
	install file with the same name, in this case DECUSCAPP.INS,
	in that directory.  The P/OS install utility will look in that
	directory for any files that it is told to copy in FILE commands
	that do not have directory specs.  The "/delete" qualifier on
	the FILE commands tell CTAB to delete the file if the application
	is removed by the P/OS application remove facility.  When the
	application is installed, a unique directory name is generated
	and all files copied from the application directory on the floppy
	are copied there.  When the application is run, the logical
	APPL$DIR is defined as that directory.  If you want to access
	the data file without translating APPL$DIR (and since we've not
	implemented the getenv() call for P/OS yet, I expect you do) you
	can use a file command of the form

	    FILE [datadir]decusdat.dat/delete"

	The P/OS facility (install facility) will look on the floppy in
	[DATADIR] for the file and copy it to that directory on the
	winchester (creating it if necessary).  The INSTALL command
	installs the task image.  If you have built against a library
	or have other tasks that you want to install, you must include
	INSTALL commands for them.  The libraries get the qualifier
	/LIBRARY and the task images, /TASK.  If you want a library or
	task to stay around after the application has terminated, 
	use the /NOREMOVE qualifier on the INSTALL command as well.
	You are allowed only one RUN command per install file.  This
	takes the installed task name.  This is either the first six
	characters of the task image file name or the name given at
	task-build time.  The RUN command is the last in the .INS file.

