CommonProblems

This article is an overview of common problems in porting an application
to VMS.

When you are porting a project, there are several issues that tend to show up.

Most Open Source projects need a config.h file that generated by a Configure script.
The article [GeneratingConfigh] is to address methods of creating this file on VMS.

Many programs being ported are in C or C++.
The VMS C Environment has many run time and compile time option settings that control the behavior of programs. Some of the run time settings need to be set before the main() routine in the program is executed.

The article [CompilerOptions] is to address the compile time settings used for porting.

The article [CRuntimeSettings] is to address the run-time settings, including how to set them prior to main() starting.

The article [CrtlIssues] is to document issues that have been found in the VMS environment that may need to be worked around, and [CrtlWrappers] is to document routines that are either wrappers for existing routines or new replacement routines.

The article [ProvidingHelp] is to address building VMS help and Unix man or info pages for your applications.

The article [VMSKitting] is to address making a distribution kits.

The article [VMSForking] is to address how to deal with fork() calls in an application to be ported.

The article [CommonPortingBugs] is address common bugs that get introduced into programs that are ported to VMS.

The article [VMStoPosixFilenames] is to address translating Unix filenames to or from VMS, especially on ODS-2 volumes that VAX is limited to..