Environment Variables
The use of environment variables is entirely optional. They are provided so that the software can be configured to suit particular needs (e.g., to use a networked database file). Environment variables can be added or modified from the System Control Panel as follows:
Click the Advanced systems settings link.
Click Environment Variables button.
If software was installed “for you”, add the definition to the User variables list, otherwise as an Administrator, add the definition to the System variables list.
You do not need to reboot the system, however it is good practice to log out and then back in again when adding or changing environment variables.
The following environment variables have meaning to Icam Productivity Tools.
icam_lib is a dynamically set variable that defines the installation directory.
icam_bin is a dynamically set variable that defines the computer system type.
icam_appdata and icam_appdata_270 define the application data directory.
icam_dbf defines the database file in which post-processors, control emulators and Virtual machine models are stored.
icam_sec defines the Icam license server connection key file.
icam_cl defines the default directory for Icam Post GENER CL files.
icam_tap defines the default directory for Icam Post GENER tape and DNC files.
icam_lis defines the default directory for QUEST listing files.
icam_lst defines the default directory for Icam Post GENER listing files.
icam_lce defines the default directory for Control Emulator CERUN listing files.
The icam_lib environment variable is dynamically set when the software starts running. It points to the Icam Productivity Tools installation directory where the software is running from. This dynamic setting means that DEF file symbols and macros can use the icam_lib environment variable to refer to the installation directory. It also means that any setting of icam_lib before running the software will be ignored.
The icam_bin environment variable is also dynamically set when the software starts running. It defines the system type of the computer running the software. The system type will match one of the Icam Productivity Tools installation “bin” subdirectory names. DEF file symbols and macros can use the icam_bin environment variable to refer to the system type. Any setting of icam_bin before running the software will be ignored.
The icam_appdata and/or icam_appdata_270 environment variables can optionally be set to define the application data directory. If icam_appdata_270 is defined, it will temporarily override any value of icam_appdata. This enables different application data directories to be defined for different versions of Icam Productivity Tools. If neither environment variable is defined, icam_appdata will be dynamically set by searching for the ICAM.DEF file as defined in “Configuration Storage and Application Data”. DEF file symbols and macros can reliably use the icam_appdata environment variable to refer to the application data directory, since icam_appdata will be dynamically set if missing.
The remaining environment variables are not dynamically set.
The icam_dbf environment variable defines the database file that is used to store post-processors, control emulators and Virtual machine models. When GENER or CERUN is run from the Windows command prompt, the default database is named campost.dbf and resides below the application data directory in a subdirectory named work. When run in an interactive mode (i.e., via the “launch” panel), the default database is remembered from the last time GENER or CERUN was run interactively, unless icam_dbf is set. To use icam_dbf, set the environment variable to the full path and filename of the database.
The icam_sec variable defines the Icam license server connection file for the client computer. Icam products will look to the icam_sec environment variable, if defined, for the full path and filename of the license server connection file. If the variable is not defined or if the file does not exist, then they will look for a license server connection file named icam.key in the application data directory, and if still not found then in the directory pointed to by the icam_lib dynamic variable (i.e., the Icam Productivity Tools installation directory).
The icam_cl variable defines the default directory where Icam Post GENER input CL files are normally found. By default, when GENER is run in an interactive mode, the default input directory is one used when GENER was last run. When running in a batch mode, the default input directory is the current working directory. To use icam_cl, set the environment variable to the directory name where your CAM system normally outputs its CL files. The icam_cl setting is ignored if a path is specified with the CL name on the GENER command line.
The icam_tap and icam_lst variables simplify the management of Icam Post GENER output files. By default, when GENER is run in an interactive mode, all output files are created in the same directory as the input CL file. When GENER is run in a batch mode, all output files are created in the current working directory. The icam_tap variable defines the default directory where GENER will write all tape files. The icam_lst variable defines the default directory where GENER will write the listing, log and back-plotting files. The icam_tap and icam_lst settings will be ignored if directory paths are used for tape, listing, log or back-plot file specifications on the GENER command line.
The icam_lce variable simplifies the management of Control Emulator CERUN output files. By default, when CERUN is run in an interactive mode, all output files are created in the same directory as the input MCD file. When CERUN is run in a batch mode, all output files are created in the current working directory. The icam_lce variable defines the default directory where CERUN will write the listing and log files. It will be ignored if directory paths are used for listing or log file specifications on the CERUN command line.
The icam_lis variable defines the directory where QUEST listing
files should be written. These are created when a post-processor, control emulator or Virtual machine model is
generated, or on demand via the File»