The following table lists the most important variables from the mc Namespace for Windows and Mac64 bit:
NOTE that some variables are only available from certain Runtypes on (e.g. configdb_opensuccessful is not available before MarvelClient opened/tried to open the Config database), on certain operating systems, and/or from specific MarvelClient releases on.
NOTE: On Linux and Mac32 bit, various references may not be available
The most important variables from the mc Namespace | ||
|---|---|---|
| actions_path |  | Full filepath of actions.xml. |
| addin_directory, addin_filename, addin_path | Details on the filename of the MarvelClient binary (dll/so/dylib) and where it was loaded from. | |
| addon_computer_assettag, addon_computer_identifyingnumber, addon_computer_model, addon_computer_name, addon_computer_partnumber, addon_computer_serialnumber, addon_computer_version | Windows only | Machine details populated by the optional HW & SW inventory agent. |
| addon_isadmin, addon_whoami_admin, addon_whoami_admin_domain, addon_whoami_admin_elevated, addon_whoami_dialup_session, addon_whoami_interactive_session, addon_whoami_kernel6_check, addon_whoami_network_session, addon_whoami_remote_session, addon_whoami_uac_disabled, addon_whoami_uac_enabled, addon_whoami_uac_silent_admin_prompt | Windows only | Details for the logged on operating system user populated by the optional HW & SW inventory agent. Note that some of the details listed are only available on Windows Vista or 7 and up (e.g. UAC details). |
| bg_runcount | | How often has MarvelClient already run in the background. (the default background interval is 60 minutes) |
| build_type | Information as to whether the MarvelClient binary is a DLL or EXE file. | |
| configdb_changedonopen | Release >= 3 | "1" if the replica id of the opened Config database is different from the replica id last stored in actions.xml; if MarvelClient detects a change of replica id, it resets the entire actions.xml |
| configdb_current_location, configdb_current_path, configdb_current_replicaid, configdb_current_server | | Details for the Config database as last opened. configdb_current_replicaid is only available for MarvelClient releases >= 3. |
| configdb_fb_* | | If so set, holds details for fallback Config databases, e.g. configdb_fb_lastreachable_location orconfigdb_fb_notresolvable_location |
| configdb_location, configdb_location_placeholder | | ini:MC_DB in unresolved (placeholder) and resolved format. (unresolved format defaults to %notes_homeserver%!!panagenda\panagenda.nsf) |
| configdb_opensuccessful | Release >= 3 | Could MarvelClient successfully open the Config database? |
| configdb_path, configdb_replicaid, configdb_server | | see mc_configdb_current_* |
| configdb_timeoutencountered, configdb_usedfallback | Release >= 3 | Did opening the Config database run into a timeout? Did opening the Config database use a fallback option? |
| db_dbopentimeout db_checktimedout | Optional timeout settings for opening server-side databases (defaults to no timeout being set) | |
| desktop_wib_found | Is desktop/workspace stored in bookmarks? NOTE: Whether a desktop stored in bookmarks is in fact used from there (aka IBM Roaming) is determined by ini:WORKSPACE_INI_BOOKMARKS | |
| dlm_disabled, dlm_initialdelay | Details for whether the Smart File Download action is disabled (defaults to false) and what the initial delay is in minutes (defaults to 5). | |
| duration_* | Information as to how long certain moments from client start to client shutdown took (in milliseconds). | |
| ecm_plugin_* | Details for the MarvelClient Eclipse plugin | |
| ecm_tl_timeout_synack, ecm_tl_timeout_wait | Timeout settings for the MarvelClient Eclipse plugin. (synack defaults to 4,000 milliseconds, wait to 120,000) | |
| last_fs_roaming_failed | Did the last executed (MarvelClient) Roaming action fail? | |
| last_fs_roaming_no_instance_found | Could the last executed (MarvelClient) Roaming action connect to the roaming source, but did not find any more recent backup there? | |
| last_fs_roaming_target_empty | Could the last executed (MarvelClient) Roaming action connect to the roaming source, but did not find any backups there? | |
| localstore_path | Filepath of mc_localstore.nsf (relative to Notes data directory) | |
| log_path | Absolute filepath of log.xml. | |
| pbar_shutdown_enabled pbar_textshow | Windows only | Optional settings for displaying a progress bar during client shutdown. (enabled defaults to 0, textshow to 1) |
| run_section | | Current "moment" (in most cases currently executed Runtype) from client start to shutdown |
| skinning_directory | Windows only | Optional - Directory for Skinning the IBM Notes Workspace/Desktop. NOTE: You do NOT need mc_skinning.dll - The mc.dll has all the skinning capabilities built in, too. |
| temp_directory | | mc:temp_directory defaults to mc:working_directory\temp |
| time_* | DateTime of when certain moments from client start to shutdown started/ended in UTC format YYYYMMDDTHHMMSSZ | |
| version_* | | Version details for the MarvelClient binary (dll/so/dylib) |
| working_directory, working_directory_placeholder | | ini:MC_WorkingDirectory in unresolved (placeholder) and resolved |
The full list of available Variable names from within each Namespace can be derived from a representative config.xml (in each client’s Working Directory or in the Analyze database if so collected).
Note that the config.xml file is recreated upon every client start – after closing an IBM Notes Client, any therein stored variables are NOT read back ever.
NOTE that namespaces and variables are NOT write-protected. You must not change important system variables (e.g. notes:client_directory, mc:working_directory or similar).