Migration of OS/390 C/C++ applications to z/OS V2R2 XL C/C++
OS/390® C/C++
applications were created with one of the following products:
- IBM® OS/390 V1R1 C/C++ (reship of IBM C/C++ for MVS/ESA V3R2)
- IBM OS/390 V1R2 or V1R3 C/C++
- IBM OS/390 V2R4, V2R5, V2R6, V2R7, V2R8, V2R9, or V2R10 C/C++
- IBM z/OS® V1R1 C/C++ (reship of IBM OS/390 V2R10 C/C++)
Notes:
- The z/OS V1R1 compiler and library are equivalent to the OS/390 V2R10 compiler and library.
- The OS/390 V2R5 compiler is equivalent to the OS/390 V2R4 compiler.
- The OS/390 V1R1 compiler and library are equivalent to the final MVS/ESA compiler and library, and are described in Migration of pre-OS/390 C/C++ applications to z/OS V2R2 XL C/C++.
Generally, you can bind OS/390 programs successfully with z/OS V2R2 programs without changing source code, and without recompiling or relinking programs.
The following topics provide information relevant to migrating
a OS/390 application to z/OS V2R2 XL
C/C++:
- Source code compatibility issues with OS/390 programs
- Compile-time migration issues with OS/390 programs
- Bind-time migration issues with OS/390 C/C++ programs
- Runtime migration issues with OS/390 C/C++ applications
- Migration issues resulting from class library changes between OS/390 C/C++ applications and Standard C++ library
Notes:
-
If your application uses IBM CICS® information or statements, also see Migration issues with earlier C/C++ applications that run CICS statements.
-
If your application uses IBM DB2® information or statements, also see Migration issues with earlier C/C++ applications that use DB2.