Environment Debugging

A faulty or incomplete environment definition can cause problems with running jobs. Example: A job succeeds when executed directly from the command line but fails when executed by the taskers.

The utility taskerdebug can be used to debug the environments used by the taskerdebug. This utility prints all environment variables, aliases and equivalences into the file that is given as its first argument. In the following example, the environment named BASE is debugged, and base.out is the output file:

% ves BASE 
% vov taskerdebug base.out

The command can now be retraced on selected taskers and check the file base.out for clues about the problem with the environment. If necessary, use the resource mechanism to direct the job to the desired tasker.

Note: The taskerdebug command is implemented as a csh script on UNIX, and a .bat script for Windows. The command machinfo can also be used, which is implemented in Tcl. Implemented in Tcl allows using this command in either UNIX or Windows. This may be preferred, as the machinfo output provides more information than the command taskerdebug on Windows.

Environment Checking

To verify if an environment is good, use vovenvcheck, which checks that all variables set in the start.* file are properly unset in the end.* file. Example:

% vovenvcheck env_name