Follow the steps below to prepare the mcidas and mcadde accounts.
The mcidas account should allow logins; the mcadde account should not allow logins. Both of these accounts should be in the same group and both should have the SAME home directory.
NB: Defining all of these enviornment variables is most easily accomplished by adding the following lines to your shell definition file:
|non-Conforming shells (e.g., .cshrc)
|Conforming shells (e.g., .profile, .bash_profile, or .kshrc)
# McINST_ROOT and VENDOR non-conforming shell defines # needed to build McIDAS setenv MCVER 2022 setenv MCHOME $HOME setenv McINST_ROOT $MCHOME setenv MCADMIN $McINST_ROOT/admin setenv VENDOR -gfortran # NOTE: uncomment the line that sets MySQL_ROOT if you want to # build with MySQL support: # - leave the value blank if MySQL is installed in a standard # location # - specify the value as the root directory of the MySQL # installation if MySQL is not installed in a standard # location # setenv MySQL_ROOT TRUE if ( -e $MCADMIN/mcidas_env.csh ) then source $MCADMIN/mcidas_env.csh endif
# McINST_ROOT and VENDOR conforming shell defines # needed to bulid McIDAS MCVER=2022 MCHOME=$HOME McINST_ROOT=$MCHOME MCADMIN=$McINST_ROOT/admin VENDOR=-gfortran export MCVER MCHOME McINST_ROOT MCADMIN VENDOR # NOTE: uncomment the next two lines that set MySQL_ROOT if you # want to build with MySQL support: # - leave the value blank if MySQL is installed in a standard # location # - specify the value as the root directory of the MySQL # installation if MySQL is not installed in a standard # location # MySQL_ROOT=TRUE # export MySQL_ROOT if [ -e $MCADMIN/mcidas_env.sh ]; then . $MCADMIN/mcidas_env.sh fi
The names of environment variables that are needed and their meaning is listed in the following table.
|the version of the McIDAS-X installation
|the HOME directory of the user mcidas
|the directory under which you wish to install Unidata McIDAS-X. This is usually the same as MCHOME)
|the fully qualified pathname of the location of admin scripts
|working directory for McIDAS-X sessions
|MCPATH - a colon-separated list of directories that
McIDAS routines will search when looking for data and
ancillary data files
|the directory in which McIDAS executables reside
|the directory in which the Tcl/Tk GUI executables and scripts reside
|the directory in which McIDAS-X/-XCD source code can be found
|a semi-colon separated list of fully qualified pathnames of ADDE client routing tables that will be read by McIDAS applications when determining the server from which data will be requested
|the ADDE client routing table that will be modified when the McIDAS DATALOC command is run
|set the EXPanded or ORIGinal stretch environment
|when set, makes McIDAS clients request that ADDE servers send them data in compressed format
|setting this environment variable to a non-blank value
tells the McIDAS-X/-XCD build process to include
MySQL support. If MySQL is installed in a standard
location, specify the flag as TRUE).
If MySQL is installed in a non-standard
install location, specify the flag as
directory is the root MySQL install
NB: if MySQL is not installed setting this environment variable will cause the build to fail.
|fully qualified pathname of the XCD decoder status file, DECOSTAT.DAT. This should be located in mcidas's working directory.
|add the MCGUI directory to the front of your PATH
All BATCH files and McBASI scripts in the $MCHOME/data directory that have the same name as ones in the Unidata McIDAS-X distribution will be automatically copied to a backup directory, $MCHOME/savedata, but these files can still be overwritten under certain circumstances. Saving the files you have modified before you begin will prevent loss of work later on.