Normally, link-editing an OS/VS COBOL NORES application with Language Environment has no effect. The application will provide the same results as before, and cannot access Language Environment services.
However, in some cases, after you link-edit an OS/VS COBOL NORES application with Language Environment, the application will exhibit RES behavior. Table 1 lists what can cause this change in behavior.
| Attribute | Comments |
|---|---|
| Contains a VS COBOL II program | Applications with a VS COBOL II program will exhibit RES behavior after being link-edited with Language Environment. |
| Contains an IBM COBOL or Enterprise COBOL program | Any applications with an Enterprise COBOL, COBOL for OS/390 & VM, COBOL for MVS & VM, or COBOL/370 program will exhibit RES behavior after being link-edited with Language Environment. For additional information, see Adding Enterprise COBOL programs to existing COBOL applications. |
| Contains the IGZCBSN bootstrap routine | IGZCBSN is the COBOL/370 bootstrap routine. |
| Contains the IGZCBSO bootstrap routine | IGZCBSO is the COBOL for MVS & VM, COBOL for OS/390 & VM, and Enterprise COBOL bootstrap routine. |
| Contains a program using an object module produced using the IGZBRDGE macro. | An object module produced by using the IGZBRDGE macro is normally used to convert static CALL statements to dynamic CALL statements. However, just the presence of an object module produced by using IGZBRDGE causes the behavior to change, regardless of how it is being used. |
| Note: For multiple
load module applications, if the first load module contains one of the above
attributes, it will behave as if it were RES.
|
|