Bind-time migration issues with OS/390 C/C++ programs

This information helps application programmers understand and resolve the compatibility issues that might occur when they relink programs from an OS/390® C/C++ compiler to z/OS® V2R2 XL C/C++.

Executable program compatibility problems that require source changes are discussed in Source code compatibility issues with OS/390 programs.

Notes:
  1. An executable program is the output of the prelink/link or bind process. For more information, see "Prelinking and linking of z/OS XL C/C++ programs" in z/OS XL C/C++ User's Guide.
  2. The terms in this topic having to do with linking (bind, binding, link, link-edit) refer to the process of creating an executable program from object modules.
  3. The output of a prelinking, linking, or binding process depends on where the programs are stored:
    • When the programs are stored in a PDS, the output is a load module.
    • When the programs are stored in a PDSE or in UNIX System Services files, the output is a program object.
When you bind programs that were previously compiled with an OS/390 compiler and library, be aware of the following potential migration issues:
Parent topic: Migration of OS/390 C/C++ applications to z/OS V2R2 XL C/C++