You can enter an initial set of items when you invoke CUPLOT.
$ CUPLOT SH 55806 DE NB-BP-SL ; GO
You can put a sequence of CUPLOT commands in a file and process the entire file by typing ``@FILE.EXT''. Input files can be created using an editor. If you omit the extension, the default is ``.COM''. For example, BP.COM could contain:
DE NB-BP-SL ;XT TBON-.5 TBOF+.5 !adjust view window to beam pulse
GO
\
CUPLOT and invoke these commands for several shots:
$ CUPLOT
Command[ ]? SH 55806 @BP
Command[ ]? SH 55805 @BP
You can set parameters on the command line to be used inside CUPLOT. A parameter is an arbitrary name that is at least 4 characters long preceded by a slash. It is defined by ``/param=value''; it is invoked by ``/param''.
$ CUPLOT /SHOT1=55806Parameters are most useful in DCL command files that invoke CUPLOT. Procedure parameters (P1, P2, etc.) can only be used in DCL command lines, not in lines that provide program input. The following example shows invalid and valid contents for a command file that invokes CUPLOT to plot data identified by two DCL passed parameters.Command[ ]? SH /SHOT1 !sets shot number to 55806
Wrong:$ CUPLOT
SH 'P1 !cant use P1 here
DE 'P2 ; !ditto for P2
GO
Right:
$ CUPLOT /SHOT1='P1 /NAME='P2
SH /SHOT
DE /NAME ;
GO
Typing ``>FILE.EXT'' causes your responses to be recorded in ``FILE.EXT'' until you close the file with ``>''. You can create a file to be used as an input file by saving your responses using the ``>FILE'' feature.
When you are running interactively and invoke a command file, the default is for CUPLOT not to output on your terminal what it reads from the file. If you would like to see what is being processed, you can turn on ``echo'' mode by typing ``/E''; to turn off echo mode type ``/NOE''.