The ENVI_DOIT procedure is the interface for all of the ENVI Classic processing routines (those that end with _DOIT). Each _DOIT is a string argument to ENVI_DOIT with specific keywords that follow.
ENVI_DOIT, 'Routine_Name' [, /NO_CATCH] [, /INVISIBLE] [, /NO_REALIZE]
Routine_Name is a string variable specifying the processing routine to execute. ENVI Classic commonly refers to processing routines as “DOIT.” Many of the internal ENVI Classic processing routines are available to you in batch mode. The value of Routine_Name should be any valid _DOIT routine in ENVI Classic. Keywords specific to each of these routines are described in this Help.
Set this keyword to disable the ENVI Classic catch mechanism, which provides a generalized method for handling exceptions and errors. By disabling the ENVI Classic catch mechanism, you have the option to add your own. If you do not use a catch mechanism and an error occurs, ENVI Classic stops program execution, prints an error message, and reverts control to the command line. The ENVI Classic session (interactive or batch) must be continued manually from the command line. See the IDL procedure CATCH for instructions on adding your own catch mechanism. Use NO_CATCH only with the procedure ENVI_DOIT.
Set this keyword to prevent the result of the _DOIT processing routine (usually the output of the R_FID keyword) from being automatically opened and listed in the Available Bands List at the end of the Routine_Name process. In cases when an opened file is automatically displayed, setting the INVISIBLE keyword will also suppress the automatic display of the output result. Some processing routines (such as ENVI_STATS_DOIT) produce dialogs, but they do not produce output files. The INVISIBLE keyword only applies to cases when an output file is created. Otherwise, this keyword is ignored.
Set this keyword to prevent the Available Bands List from displaying if a new output file is created at the end of the Routine_Name process. If the Available Bands List is already realized, this keyword has no effect. Some processing routines (such as ENVI_STATS_DOIT) produce dialogs, but they do not produce output files. The NO_REALIZE keyword only applies to cases resulting in an output file. Otherwise, this keyword is ignored.