4.2 Running SCHED

4.2.1 Running SCHED under UNIX or LINUX

To run SCHED on a UNIX machine such as a SUN or a PC under LINUX, prepare the keyin file without system level commands. Then type, for example,

sched < input.key

Alternatively, if plotting is wanted, for example, type:

sched  
<SCHED will write a number of instructive lines>  
* plot schedule=input.key /

where the SCHED executable file is assumed to be in the default directory or path and the SCHED input commands are in input.key in the default directory. The “<” pipes the information in input.key to SCHED. The “*” is the prompt from SCHED. Remember that, in UNIX, file names and commands are case sensitive. Also, there is a complication for users of the tc shell for versions after mid 1995: there is a built-in shell command “sched” that the shell takes instead of running SCHED. So to use SCHED, either alias “sched” to mean this program or else specify the full path name of the execute module. The files output by SCHED will appear in the default directory.

If your version of SCHED is linked with the PGPLOT libraries (has plotting capability), you will need to set the environment variables PGPLOT_DIR to the location of the PGPLOT libraries and PGPLOT_FONT to the location of the PGPLOT font files. If you use PGPLOT for other reasons (programming, DIFFMAP etc), then this is likely to be part of your standard setup.

4.2.2 Running SCHED on a VAX with VMS

Note that I am not aware of anyone using SCHED on VAXes any more.

To run SCHED on a VAX, make a VMS command file, called INPUT.COM for example, which begins with a VMS command that causes SCHED to be executed. For systems with a fully installed Caltech package, the command “$ SCHED” should work. Otherwise use a command of the form “$ RUN UMA3:[VPGM.CIT.VLB]SCHED”, where you will need to substitute the correct directory specification. The command file should end with “$ EXIT”, although this is not necessary. The SCHED command file is run by typing, for example,

@INPUT.COM

The files output by SCHED will appear in the default directory.

SCHED has not been tested under VMS since the plotting capabilities were added.

It has been a very long time since I was aware of anyone running SCHED on an MS-DOS machine, or a Windows machine for that matter.

To run SCHED on a PC (MS DOS), prepare the input file without system level commands. Then type, for example,

\CODE\SCHEDB < INPUT.KEY

where the SCHED.EXE executable file is assumed to be in the CODE directory (substitute whatever is correct for your system) and the SCHED input commands are in INPUT.KEY in the default directory. The “<” pipes the information in INPUT.KEY to the program (note the similarity to UNIX). The files output by SCHED will appear in the default directory.

It has been a long time since SCHED was ported to DOS. It has never been ported to Windows. It seriously outgrew DOS, but should work in Windows if someone were to take the effort to install it.