Moving to Language Environment

If you are starting with load modules consisting of programs that are compiled with the NORES option and link-edited with the OS/VS COBOL runtime library or the VS COBOL II runtime library, then you will need to use REPLACE linkage-editor control statements to replace the existing runtime library routines with the Language Environment® versions. If you start with object programs (non-linked), then you just need to link-edit with Language Environment.

Note: If your IGZEBST bootstrap routine from VS COBOL II has PN74000 installed, you do not need to REPLACE this IGZEBST with the Language Environment version of IGZEBST.

If the programs are compiled with the RES option, make the Language Environment library routines available at run time in place of the OS/VS COBOL or VS COBOL II library routines by using LNKLST, LPALST, JOBLIB, or STEPLIB.

Do not make more than one COBOL runtime library available to your applications at run time. For example, there should be one and only one COBOL runtime library, such as SCEERUN for Language Environment, in LNKLST. If you have more than one, you will either get hard-to-find errors or you will have an unused load library in your concatenation. In addition, if you have more than one runtime library in your concatenation, then you have an invalid configuration that is not supported by IBM®.

If you have not yet completed your runtime library migration, you must complete that migration before using this book. For details, see Chapter 3. Planning the move to Language Environment in the Enterprise COBOL 4.2 Compiler and Runtime Migration Guide.