S U P - V 1.0

		S U B S Y S T E M    U T I L I T Y

			P R O G R A M


	General:
	SUP is a program to create and maintain subsystemfiles,
	which are used by the DLLOAD-Facility. You can use SUP to
	copy files on normal devices to files in subsystems and vice
	versa.It is also possible to copy files from one subsystem
	to another. Further you may delete or rename subsystem
	files. One command creates a new subsystem and yet another
	copies the bootstrap information of a RT11 monitor to the
	bootstrap blocks of a subsystem. In this way you can create
	complete, bootable subsystems by using SUP exclusively.


	Files on normal devices will be denoted by MNSYS, while
	files on subsystems (SUBSYS) will be called SUBFIL. The SUP
	command syntax resembles normal RT11 Command Language.


	The general form of a SUP command is:

	COMMAND FILENAME/SUBFILENAME FILENAME/SUBFILENAME

	The filenames are of standard RT11 format:

			DEV:FILNAM.EXT

	The use of wildcards in filespecs is not allowed in SUP, but
	there are some defaults: MNSYS and SUBSYS filespecs default
	to SY: for the device and to .DSK for the extension, while
	SUBFIL-specs default to .DAT for the extension and may not
	have a DEV: specification.






	Commands of SUP:
	When SUP types a ? ,it waits for your command. Now you may
	type one of the following commands followed by a <RETURN>
	after the last filespec if any. Commands may be shortened to
	the first character.
	SUP commands may be used in indirect command files. But
	remember to include RUN SUP in your indirect command file
	before you use SUP commands and EXIT as the last SUP
	command.
	Note: Angle brackets [] enclose defaults and should not be
	      typed in your actual command.









1. HELP
	Function:Types these instructions

	Form:

	HELP

	Example: None













2. COPY
	Function:It is used to copy files from
	subsystemfiles to normal device files and vice
	versa, as well as to copy files from one subsystem
	to another. There are three forms of COPY:

	Form 1:

	COPY [SY:]SUBSYS[.DSK]/SUBFIL[.DAT] [SY:]MNSYS.DAT

	Form 2:

	COPY [SY:]MNSYS.DAT [SY:]SUBSYS[.DSK]/SUBFIL[.DAT]

	Form 3:

	COPY [SY:]SUBSY1[.DSK]/SUBFIL[.DAT] [SY:]SUBSY2[.DSK]/SUBFIL[.DAT]




	Examples:

	COPY DL0:SUBSY1.DSK/OUTPUT.DAT OUTPUT.DAT

	(Copies the file OUTPUT.DAT on SUBSY1.DSK to
	file OUTPUT.DAT on SY:)

	COPY INPUT.DAT SUBSY1/INPUT

	(Copies the file INPUT.DAT on SY: to INPUT.DAT on
	SY:SUBSY1.DSK)

	COPY SUBSY1/PIP.SAV SUBSY2/PIP.SAV

	(Copies the file PIP.SAV which resides on
	SY:SUBSY1.DSK to SY:SUBSY2.DSK while retaining the
	its original name)



3. INITIALIZE
	Function:It is used to create a subsystemfile and
	to initialize its directory.

	Form:
	INITIALIZE [SY:]MNSYS[.DSK]

	Example:
	INITIALIZE DL0:SUBSY3.DSK

	How many blocks (256-1024) [1024] ?_
	(Now you may specify how many blocks you want to
	allocate to the new subsystemfile. The default is
	1024 blocks.)

	How many directory segments (1-4) [1] ?_
	(Now you can specify how many directory segments
	you want. You should allocate 1 segment unless you
	expect a large number of small files. Default is 1
	segment.)



4. BOOT
	Function: Copies the bootstrap information from an
	RT11 Monitor to the appropriate blocks of a
	subsystemfile, so that this sub- systemfile may be
	booted.

	Form:
	BOOT [SY:]SUBSYS[.DSK]/SUBFIL.SYS V#/SUBFIL.SYS

	Note: V#/ is a necessary dummy filespec denoting
	the version number of the monitor to boot and may be
	either V4 or V3! The first subfile spec has to
	specify the monitor name, while the second has to be
	the system device name. For V3 boots the last
	subfilespec may be a dummy.

	Example:
	BOOT SUBSY0/RT11SJ.SYS V4/DD.SYS

	Copies the bootstrap of an RT11SJ monitor (version 4)
	with the systemdevice DD: to the appropriate
	blocks. 


5. DIRECTORY
	Function: Displays the directory of the specified
	subsystem on the console device in the usual
	RT11-format.

	Form:

	DIRECTORY [SY:]SUBSYS[.DSK][/FULL]

	Note: If the option /FULL is specified after the
	subsystem name, the unused areas of the subsystem
	will be displayed too.

	Example:

	DIR SUBSY3


6. RENAME
	Function: changes the name of a subsystemfile

	Form:

	RENAME [SY:]SUBSYS[.DSK]/SUBFIL[.DAT] A/SUBFIL[.DAT]

	Note: A/ in the second filespec is a necessary
	dummy parameter; - don't leave it out!

	Example:

	RENAME DY1:SUBSY1/OLDSPC.DAT A/NEWSPC.DAT

	(Searches DY1:SUBSY1.DSK for a file called
	OLDSPC.DAT and, if found, renames it to NEWSPC.DAT )


7. KILL
	Function: After querying the user for confirmation, the
	specified file is deleted from the subsystems directory.

	Form:

	KILL [SY:]SUBSYS[.DSK]/SUBFIL[.DAT]

	Example:

	KILL DK:SUB.DSK/OUTPUT.DAT

	Delete DK:SUB.DSK/OUTPUT.DAT - Are you sure?_

	(Now answer: Y<RET> if you really want to delete
	the file, or anything else if you have changed your
	mind )


8. EXIT
	Function: returns to the monitor.

	Form:

	EXIT

	Example: None








�����������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������