AMPAC 8 with Graphical User Interface Release Notes - IBM AIX ----------------------- Copyright (c) 1996-2005 Semichem, Inc. All Rights Reserved. All compilations were done using the AIX 5.2.0 OS. You may need this level of system software or later to run AMPAC. If you are running an older version of the system software, we suggest you update to ensure proper compatibility. AMPAC requires that the XLF Fortran runtime libraries be present. These should be available as a part of the AIX 5 OS, possibly as an optional component. They need to be installed to use AMPAC. The following shows the shared library dependencies of ampac.exe: % ldd ampac.exe ampac.exe needs: /usr/lib/libc.a(shr.o) /usr/lib/libxlf90.a(xlfsys.o) /usr/lib/libxlf90.a(io.o) /usr/lib/libxlf90.a(math.o) /unix /usr/lib/libcrypt.a(shr.o) /usr/lib/libxlf90_r.a(io.o) The following shows typical installation information for XL Fortran runtime libraries % lslpp -l | grep -i xlf | grep -i runtime xlfrte 8.1.1.6 COMMITTED XL Fortran Runtime Environment xlfrte.aix51 8.1.1.5 COMMITTED XL Fortran Runtime Environment xlfrte.msg.EN_US 8.1.1.1 COMMITTED XL Fortran Runtime Environment xlfrte.msg.En_US 8.1.1.1 COMMITTED XL Fortran Runtime Environment xlfrte.msg.en_US 8.1.1.1 COMMITTED XL Fortran Runtime Messages - System Information ------------------ To determine your OS level, use the following command: /usr/bin/uname -a Configuring Swap Space ---------------------- Efficient use of AMPAC requires sufficient swap space as discussed in README.txt. This can be configured through the "smit" utility that is provided with the operating system. Super-user privileges are required to affect changes. After launching "smit," select "System Storage Management (Physical & Logical Storage)" -> "Logical Volume Manager" -> "Paging Space" to bring up a menu of options. From here, paging space can be added or changed. =============== Troubleshooting =============== Missing Libraries ----------------- AMPAC (and AGUI) relies on libraries that must be loaded at run time. In the event that AMPAC is unable to find all of its required libraries, then it will print out an error message and exit. A diagnostic script, "check_env.csh", has been provided to identify and resolve the most common problems. Instructions on how to use this diagnostic can be found in README.txt. If that fails to resolve the problem, follow the procedure given here. 1) The user must switch to either a csh or tcsh shell. If the user is already running in csh or tcsh, then nothing needs to be done. For users running sh, ksh, or bash shells, issue the following command: /usr/bin/csh (or /usr/bin/tcsh) (If you are unsure of which shell you are using, issue the command "echo $0" to identify it.) AMPAC can run in any of the common shell environments, however, the scripts that run AMPAC are csh based and so this diagnostic procedure requires a csh environment. 2) Initialize AMPAC information. To do this: cd {main AMPAC directory} source init_ampac.csh If AMPAC_DIR has already been properly initialized, then this step may be skipped. 3) Manually initialize AMPAC's run time environment. This must been done first to insure that the proper environmental variables are being tested. source $(AMPAC_DIR)/bin/ld_env.csh Normally, this is done automatically by the scripts that run AMPAC. It is done this way, so that only the processes that are actually used to run AMPAC will have their environmental variables altered and so these changes disappear once the job is finished. This prevents AMPAC's changes to environmental variables from interfering with other processes. For this diagnostic procedure, we need set the same environment used by the AMPAC scripts. (Note, "ld_env.sh" also exists but is not used by AMPAC, even if AMPAC is being used from a sh-based shell. This script is provided only for completeness.) 4) Check the library dependencies. Use: cd $(AMPAC_DIR)/program ldd ampac.exe ("dump -H ampac.exe" will also produce useful information.) [???] The output from "ldd" lists each of the libraries required to run AMPAC. Note any libraries that have not been found by the system. If the required library has been found, the exact location of the library that will be loaded in at run time is given. Since more than one version of a given library may exist on the system, verify that the correct library is being used. 5) Verify that the missing library exists on your system. Use: find / -name "missing library" -print If the library is not found, then it must be installed before AMPAC can be used. Consult your system administrator or the system documentation. If the library is found, note the directory in which it is located. 6) Edit the script "$(AMPAC_DIR)/bin/ld_env.csh" and insert library directory into each of the link library search path variables. Run AMPAC to verify that the problem has been resolved. If there are additional missing libraries, go back to step 3. 7) If a shell was started for this diagnostic test (step 1), then exit it. This can be done by typing ctrl-D or "exit". AGUI reports missing Libraries ---------------------------- Symptom: The AGUI application fails to launch and reports that libraries are missing. The AGUI program requires OpenGL libraries. These libraries may not be installed on systems that do not have a 3D capable graphics card installed. In this case, we recommend that you contact your IBM Representative about purchasing a 3D graphics card. Also, you may install the missing libs and use AGUI in -Xmode. Once the OpenGL libraries are installed, verify that the appropriate packages have been properly installed. Here is an example of a typical OpenGL installation as reported by lslpp: lslpp -l | grep -i opengl OpenGL.OpenGL_X.adt.include 5.2.0.0 COMMITTED OpenGL Application Development OpenGL.OpenGL_X.adt.samples 5.2.0.0 COMMITTED OpenGL Application Development OpenGL.OpenGL_X.dev.pci.14101b02.PPC 5.2.0.30 COMMITTED OpenGL GXT6500P Device OpenGL.OpenGL_X.dev.pci.14101b02.PPC64 5.2.0.30 COMMITTED OpenGL GXT6500P Device OpenGL.OpenGL_X.dev.pci.14101c02.PPC 5.2.0.30 COMMITTED OpenGL GXT4500P Device OpenGL.OpenGL_X.dev.pci.14101c02.PPC64 5.2.0.30 COMMITTED OpenGL GXT4500P Device OpenGL.OpenGL_X.dev.pci.14103c00.PPC 5.2.0.0 COMMITTED OpenGL GXT250P/GXT255P Device OpenGL.OpenGL_X.dev.pci.14105400.PPC 5.2.0.0 COMMITTED OpenGL GXT500P/GXT550P Device OpenGL.OpenGL_X.dev.pci.14105400.PPC_mp 5.2.0.0 COMMITTED OpenGL MP GXT500P/GXT550P OpenGL.OpenGL_X.dev.pci.14105e00.PPC 5.2.0.0 COMMITTED OpenGL GXT800P Device OpenGL.OpenGL_X.dev.pci.14105e00.PPC_mp 5.2.0.0 COMMITTED OpenGL MP GXT800P Device OpenGL.OpenGL_X.dev.pci.14106e01.PPC 5.2.0.30 COMMITTED OpenGL GXT4000P Device OpenGL.OpenGL_X.dev.pci.14106e01.PPC64 5.2.0.30 COMMITTED OpenGL GXT4000P Device OpenGL.OpenGL_X.dev.pci.14107001.PPC 5.2.0.30 COMMITTED OpenGL GXT6000P Device OpenGL.OpenGL_X.dev.pci.14107001.PPC64 5.2.0.30 COMMITTED OpenGL GXT6000P Device OpenGL.OpenGL_X.dev.pci.14108e00.PPC 5.2.0.10 COMMITTED OpenGL GXT3000P Device OpenGL.OpenGL_X.dev.pci.1410b800.PPC 5.2.0.10 COMMITTED OpenGL GXT2000P Device OpenGL.OpenGL_X.dev.vfb 5.2.0.10 COMMITTED OpenGL Virtual Frame Buffer OpenGL.OpenGL_X.rte.base 5.2.0.30 COMMITTED OpenGL Base Runtime OpenGL.OpenGL_X.rte.base+ 5.2.0.30 COMMITTED OpenGL Enhanced Geometry OpenGL.OpenGL_X.rte.base_mp 5.2.0.0 COMMITTED OpenGL MP Base Runtime OpenGL.OpenGL_X.rte.pipe++ 5.2.0.0 COMMITTED Enhanced OpenGL Graphics OpenGL.OpenGL_X.rte.pipe64++ 5.2.0.0 COMMITTED Enhanced OpenGL Graphics OpenGL.OpenGL_X.rte.soft 5.2.0.30 COMMITTED OpenGL Soft Runtime OpenGL.OpenGL_X.tools.base 5.2.0.0 COMMITTED OpenGL Base Tools OpenGL.OpenGL_X.tools.debugger 5.2.0.10 COMMITTED OpenGL Debugger No hardware acceleration ------------------------ Symptom: I think I have a 3D graphics card, but the performance is not what I expect. Not all 3D cards manufactured by IBM are accelerated for OpenGL. You can determine which graphics card is installed using the lsdisp command. The output should be something like: lsdisp DEV_NAME SLOT BUS ADPT_NAME DESCRIPTION ======== ==== === ========= =========== mtn0 20-60 pci GXT3000P GXT3000P Graphics Adapter Default display = mtn0 In this example, the GXT3000P is an OpenGL accelerated card. If you are uncertain if your card supports hardware acceleration, contact your IBM representative using the name from the output of the lsdisp command on your machine. If your card is not hardware accelerated, you could see diminished performance. If the performance is unacceptably slow, contact your IBM representative about purchasing a 3D card that supports OpenGL acceleration.