D: Installation Checklist

Installation Checklist for X Windows

Binaries

• Your PATH must include the directory in which Ada-ASSURED shell commands were installed.

• The FLEXlm license manager must have access to the file that contains your site's license keys.

• The DISPLAY environment variable must be set to your local screen.

• If you are running Ada-ASSURED on a remote machine, the remote host must have permission to display on your local screen.

• Enter the command aa from a shell window. An Ada-ASSURED window labeled Ada-ASSURED:*untitled* should appear on your screen. If no such window appears, something is wrong:

  • If aa can not be found, you may need to add a directory to your PATH.

  • If an error message states that the license file can not be found, you may need to set the LM_LICENSE_FILE environment variable.

  • If an error message states that you are not authorized to use Ada-ASSURED, the license key was either entered incorrectly during installation, or the key was time-limited and is now stale.

  • If an error message states that the application cannot open your display, and you are running on a remote host, verify that your DISPLAY environment variable is set to your local screen, and that your local machine has granted the remote host permission to use your display.

  • If there are no error messages in your shell window, but Ada-ASSURED appears to be running, i.e., you have not returned to a shell prompt, but no Ada-ASSURED window has appeared, then the DISPLAY variable is probably not set to your local screen.

• X Resources specific to Ada-ASSURED must be accessible.

• If you start Ada-ASSURED, and a window appears, but it is labeled aa83:*untitled* or aa95:*untitled*, something is wrong:
  • None of the Ada-ASSURED specific resources are accessible. You have not loaded the X resources correctly.

• If you are seated at a color monitor, but the text in the Ada-ASSURED:*untitled* window is not multi-colored, something is wrong:

  • The mechanism used to choose the appropriate Ada-ASSURED resources, i.e., black-and-white or color, depends on which release of X you are using and how Ada-ASSURED was installed at your site. Consult the system administrator.

• Ada-ASSURED must have access to a file that defines the values of the style enforcement parameters.

• Select Set from the Options/Enforcement Parameters menu. If the enforcement parameters are all blank or zero, something is wrong. There are two cases depending on whether the X resource user0 is defined:

  • The X resource user0 is not defined. In this case, Ada-ASSURED looks in the directory ../files (relative to the directory that contains the Ada-ASSURED binary) for the file .aa_enforcement_params. Either the file could not be read, or it contains inappropriate information. Common reasons why this may have occurred include:

    • The file has the wrong permissions and you do not have read permission.

    • The file was moved to another location, but the X resource user0 was not defined.

  • The X resource user0 is defined. In this case, this resource directs Ada-ASSURED to a file containing enforcement parameter definitions. The file either could not be read, or contains inappropriate information. Common reasons why this may have occurred include:

    • The file has been moved to a different location, e.g., the entire Ada-ASSURED directory has been moved, but the user0 resource definition has not been updated.

    • Due to the way file systems are mounted at your site, the file is known by a different full path name when accessed from your workstation.

• A web browser must be installed and accessible.

• Select Tutorial from the Help menu. A web browser, e.g, Internet Explorer, Netscape, or Enhanced Mosaic, should be launched containing the first page of the Ada-ASSURED on-line tutorial introduction. If this does not occur, something is wrong:

Requirements:

• Ada-ASSURED must have access to the files that support PostScript printing.

• The print command X resource must be set properly.

• Invoke the command print from the File menu. Click OK. If a printed copy of the buffer does not appear at your printer, something is wrong:
  • If an error message states that the prolog for printing could not be found, the X resources are not correct. Either the value of the prologPathname resource is wrong or you are not loading the X resources correctly.

  • If an error message states that a font metric file could not be found, the X resources are not correct. Either the value of the fontMetricLocations resource is wrong or you are not loading the X resources correctly.

  • If you received a message about pages sent to the printer, but no output appears, check the printCommand X resource. This can be done using the print-setup command from the File menu.

Manual Pages

• Your MANPATH environment variable must include the directory in which the man pages for Ada-ASSURED were installed.

• From the command line of a shell window, enter the command

  man aa

  If a man entry for Ada-ASSURED does not appear, something is wrong:

  • You probably need to add a directory to your MANPATH.

Exit Ada-ASSURED by selecting exit from the File menu.