Once the SPECX command has been installed in the command tables, as described above, it can be invoked from DCL using the command:
$ specx
This command has two options:
Thus valid command lines could be:
$ specx
$ specx/dump=NRAO.DMP/nomap
$ specx/map=humpty_dumpty
etc.
SPECX has two initialization files. The first -- logical name SPECX_INIT -- defines defaults for many of the programs flags and variables, particularly those relating to hardware. The actual file normally resides in the directory with logical name sys_specx, and should be maintained/altered only by the site manager. SPECX_INIT is internally documented, so that any changes should be straightforward, but note that it is actually a FORTRAN namelist, and the format is rather fussy.
The second initialization file is actually a .SPX script, which is run when the program is started (analogous to your DCL LOGIN.COM). This command file has logical name SPINIT, which defaults to the file specx_local:init.spx This presently sets up a load of useful command symbols, mostly geared towards JCMT observing. You may however wish to modify this file for your own purposes. By far the best way is to generate your own .SPX file, assign it the USER logical name SPINIT, and to start it by invoking the default file. Thus your initialization file might also be called init.spx, and look like this:
! init.spx
! Command file to define user symbols etc
!
! First run default initialization file
@specx_local:init
!
! Then define/redefine my own commands
LASER := see-plot ln03
:
:
RETURN
Then before you start up SPECX, just assign the logical name SPINIT:
$ assign/user init.spx spinit