6. Considerations for OpenVMS : Application Rebuilding : Building Member_Aligned Against Ingres 2.6 or 2006
 
Share this page                  
Building Member_Aligned Against Ingres 2.6 or 2006
Note:  This section applies only to migrating from releases prior to Ingres II 2.0/0011 (axm.vms/00).
With the move to a member_aligned version of Ingres, some applications must be rebuilt. You must rebuild applications that connect directly to an installation located on the same node, or through Ingres Net on the client node.
Building Vision and Application-By-Forms applications member_aligned is the default behavior, with no further changes being required from the developer.
C
/MEMBER_ALIGNED
Pascal
/ALIGN=ALPHA_AXP
COBOL
/ALIGNMENT=PADDING
Fortran
/ALIGNMENT=ALL
If an application cannot be built using Alpha member alignment, it is possible to rebuild it with the Ingres components naturally aligned. The steps needed for C and COBOL applications are described in the following sections.
These changes require modification to the Ingres supplied files only and not the application code. Even by performing the steps listed here, you still must recompile all parts of the application that interface with Ingres or that use any structures declared in the Ingres header files.
By default, user applications are built using the same compiler options used to build the Ingres libraries and applications. If these options are not used, proceed carefully.
The introduction of the member_aligned version of Ingres occurred when alignment-related memory issues were encountered in Ingres II 2.0/9808 (axp.vms/00). If any applications are built using un-aligned structures with the communicating interface to Ingres, data corruption is likely to occur.