Attention: You must recompile and relink your Open PL/I applications to use them with this
Enterprise Developer release.
You can use either static or dynamic linking of Open PL/I applications. The Open PL/I run-time library is built as a static library (.lib). The ldpli link-step uses the static version of the Open PL/I run-time library by default. To link,
creating a non-shared executable, use
ldpli -dll [options…]
ldpli MODULE1.o [MODULE2.O [MODULEn.o]] [options…]
You also need to add to the command one of the options below:
- -mvs - for programs executed under the control of JCL.
Note: -mvs is deprecated and will be removed in a future release. Please use the
-systemmvs option instead.
- -ims - for programs executed under the control of IMS.
Note: -ims is deprecated and will be removed in a future release. Please use the
-systemmims option instead.
- -cics - for programs executed under the control of CICS.
- -db2 - for programs executed under the control of DB2.
Note: This option is required for the mfdb2 preprocessor, which is deprecated. Please use the EXEC preprocessor (invoked by
-sql db2).
To link an Open PL/I program, use either mfplx or ldpli.
To link an Open PL/I program, use ldpli, unless you want to create a Sharable Object, in which case you should use the ld command. For more information, see
Creating a Sharable Library.
- mfplx compiles and links in one step, automatically invoking ldpli if the -c option is not used. For the use of mfplx, see the section
mfplx Syntax
.
- ldpli references the components that were installed with this version of Open PL/I and is the recommended link command when using mfpli.
