Vis - Which directories and files require write access to install and run Visualizer?

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    BMC Capacity Management for Mainframes


    BMC Capacity Management for Mainframes


    Which directories and files require write access to install and run Visualizer?

    LP: BMC Capacity Management for Mainframes





    Legacy ID:KA414743


    The Visualizer install creates (if it doesn't already exist) this directory and copies the program files into it:

    On 64bit Windows...
    C:\Program Files (x86)\BMC Software\Visualizer

    On 32bit Windows...
    C:\Program Files\BMC Software\Visualizer

    Also Visualizer will require write access.
    Other than projects and templates (presumed in user's documents) and temporary files (user's temp), Visualizer must write C:\Windows\visual.ini, which keeps configuration information about the product, such as options settings, from session to session.

    IF users also use Automator, then three more c:\Windows directory files are written:

    Also, Automator user requires sufficient authority for COM and ODBC DSN creation.

    I mention Automator because I suggested he consider "CDB-mode" Visualizer graphics, which requires that Visualizer have access to the Automator catalog (autoodbc.dat above). This presumes a "pseudo-CDB" install, which puts down a few CDB components in the Visualizer product directory. Additionally, this mode creates a cached version of data dictionaries for each platform in use in a directory it creates:
    <Visualizer product>\DataDictionary\Cache.

    The Vis install adds the following registry entries:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\visual32.exe


    To install Visualizer a user with Administrative right must be used and to run Visualizer a user with Power User rights must be used.

    Related Products:  
    1. BMC Capacity Management for Mainframes


    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles