Run Time
You can closely preserve OPM-compatible run unit semantics in:
To preserve the OPM-compatible run unit semantics in an ILE COBOL application, the following conditions must be met:
If these conditions are not met, an implicit or explicit STOP RUN in an ILE activation group may not end the activation group. With the activation group still active, the various ILE COBOL programs will be in their last used state.
In order to mix OPM COBOL/400 programs with ILE COBOL programs and still preserve the OPM-compatible run unit semantics as closely as possible, the following conditions need to be met:
If the above conditions are not met, the OPM-compatible run unit semantics is not preserved for OPM/ILE mixed application. For example, if an ILE COBOL program is running in the *DFTACTGRP and it issues a STOP RUN, both the OPM COBOL/400 and ILE COBOL programs will be left in their last used state.
In ILE COBOL, the flow of control operations, CALL, CANCEL, EXIT PROGRAM, STOP RUN, and GOBACK, will cause the run unit to behave differently unless an OPM-compatible run unit is used.
In ILE COBOL, runtime error messages are prefixed with LNR. Also, some of the message numbers are not always the same as in OPM COBOL/400.
In ILE COBOL, when the run unit terminates abnormally, the message CEE9901 is returned to the caller. In OPM COBOL/400, the message LBE9001 is returned to the caller under the same circumstances.
Due to differences between ILE exception handling and OPM exception handling, you may receive more exceptions in an ILE COBOL statement compared to an OPM COBOL/400 statement.
In OPM COBOL/400, file status is set to 9A when a job is ended in a controlled manner.
In ILE COBOL, file status is set to 0A when a job is ended in a controlled manner.
In OPM COBOL/400, file status is set to 9M when the last record is written to a subfile.
In ILE COBOL, file status is set to 0M when the last record is written to a subfile.
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.