At a first cut, I see a lot of file-paths without the leading slash – e.g.,
setenv IOAPI_MOD_DIR home/creator/ioapi/ioapi
(and, by the way, the I/O API “.mod” files will be in the same directory as the “.a” files).
Note also that you will probably have trouble with the package-manager netCDF and OpenMPI:
as the I/O API installation instructions https://www.cmascenter.org/ioapi/documentation/all_versions/html/AVAIL.html#warnstate,
In general, you are best off if you can build your whole modeling system (libnetcdf.a, libpvm3.a, libioapi.a, and your model(s) CMAQ, SMOKE, etc. with a common compiler set and common set of compile-flags. In particular, Linux-distribution-vendor supplied libnetcdf.a rarely works with CMAS-supported compiler sets.
That should get you at least a little further along…
Carlie J. Coats, Jr., Ph.D. email@example.com
Senior Software Engineer I/O API Author/Maintainer
Center for Environmental Modeling for Policy Development,
UNC Institute for the Environment www.ie.unc.edu
100 Europa Dr., Suite 490 Rm 4051 / Campus Box 1105 919.843.5951
Chapel Hill, NC 27599-1105 Fax 919.966.9920