Document ID:        475.1
Subject:            PORTABILITY OF PRECOMPILER CODE IN V6 & V7
Last Modified:      27 January   1997
Author:             RGOVINDA


Some general guidelines for porting the code are given in the V6 to V7
Migration Guide (Page 7-6) outlining the procedure and appropriate
switches to use in precompiling etc.  Pro* 1.5 libraries should be used
for ORACLE V7.0, and Pro* 1.6 or Pro*C 2.0 libraries should be used for ORACLE
V7.1.

Oracle corporation recommends that you use the latest  available version
of the precompiler.  However, if your migration process will take time, it
is possible to use code generated by an earliar version of the precompiler
with libraries from a later RDBMS to ease the migration process.

For example, Pro* 1.3 code can be linked with libraries from any version 6
or 7 RDBMS.  Note however that this approach will not give you bug fixes
which were fixed in a later precompiler version and as a rule, bug fixes are
not back ported to a superceded version.

Programs precompiled by any PRO* 1.3 versions are compatible with Pro* 1.4
libraries as well as libraries from any higher versions.  So, when a user
migrates to Oracle7, the only required step is to relink.   Appropriate linking
instructions as specified in the Installation and User's Guide for your
Operating System should be used.

CAUTION:
1. For Pro*COBOL, with the changes made for the byte swap issue in both
   Pro*COBOL and in the RDBMS, the combination 1.3 Pro*COBOL and 6.0.36
   RDBMS is NOT recommended.

2. The new versions of SQLLIB make use of new internal and extern functions
   and variables SQLXXX.  Hence, the user is advised to refrain from using
   tokens starting with 'SQL' as user- defined variable names.

If, a user runs into problems while migrating their 3GL applications from
V6 to V7, inspite of following the above, it should be reported to the
Language Support Group.