[273,41]	Command file modules to assist installing packages.

These in*.cmd files run on RSX-11M/M+ and help me make install
command files for other kludges i submit to DECUS etc.
What do you think? Are they worth using?

The 'reason for existence' of these files is that unlike simple commands e.g.

	MAC foo=bar

these commands will (a) complain in english(?) about any problems
		    (b) pause so you can fix the problem
		    (c) re-try the failed command and keep on trucking.
By using these macro-commands, you can build quite robust command files
that cope with many flavours of RSX (assuming a wizard is available to
pick up command files that fall over).
Features (frobs) of these command files include
-	automatic clean-up of intermediate files if desired
-	automatic back-out of the install process if desired (not perfect)
-	a list of what the install file needs, and what it will do

The table sumarises the commands as I use them.

p0	p1	p2	p3	p4			does

inc	prg	wot				xcc prg -a
incl	prg	wot	lib.olb	wot		@inc prg wot
						@inl prg wot lib.olb wot
inh	foo	wot				pip [1,1]=foo.h
ini	tsknam	$tsk	wot			ins $tsk/task=tsknam
ink	proc	wot				pip '<libuic>'=proc.cmd
inl	prg	wot	lib.olb	wot		lbr lib.olb/in=prg
inm	prg	wot				mac prg=prg
inml	prg	wot	lib.olb	wot		@inm prg wot
						@inl prg wot lib.olb wot
inmp	prg	wot	pre1	...		mac prg=pre1,...,prg
inmpl	prg	wot	lib.olb	wot	pre...	@inmp prg wot pre...
						@inl prg wot lib.olb wot
inn	lib	wot				lbr lib/cr
int	tsk	wot				pip lb:'<libuic>'/nv=tsk
inx	fil	wot				ensure file exists

#1	cleanup instructions
#2	backout instructions
#3	requirements documentation

inn.cmd expects lbr to be installed, checking this nests at. too deeply
use ini.cmd to check lbr before @inn
