Table 1 lists the possible combinations of
calls involving COBOL programs and assembler programs and indicates whether
the calls are supported or not supported when running under Language Environment under
non-CICS. For the calls that are not supported, this table also lists
the symptom (message or abend code) that is returned in most cases. In some
cases, depending on the application environment, the symptom might not occur.
You could receive a different failure, or the application might appear to
run successfully.
Note: The term, IBM COBOL refers to COBOL/370, COBOL for MVS & VM and COBOL for OS/390 & VM.
Table 1. Language Environment's support for calls
between COBOL programs and assembler (Asm) programs on non-CICS| Calls from |
|
Issued to |
| Program issuing |
Call type |
Enterprise COBOL |
IBM COBOL |
VS COBOL II |
OS/VS COBOL |
LanEnv1 Asm
main |
LanEnv1 Asm
subrtn |
Non-LanEnv Asm |
Enterprise COBOL
IBM COBOL
VS COBOL II
OS/VS COBOL
|
Static
|
Yes
Yes
Yes
Yes
|
Yes
Yes
Yes
Yes
|
Yes
Yes
Yes
Yes
|
Yes
Yes
Yes
Yes
|
No2
No2
No2
No2
|
Yes
Yes
Yes3
Yes3
|
Yes
Yes
Yes
Yes
|
Enterprise COBOL
IBM COBOL
VS COBOL II
OS/VS COBOL
|
Dynamic
|
Yes
Yes
Yes
Yes
|
Yes
Yes
Yes
Yes
|
Yes
Yes
Yes
Yes
|
Yes
Yes
Yes
Yes
|
No2
No2
No2
No2
|
Yes
Yes
Yes
Yes
|
Yes
Yes
Yes
Yes
|
Asm (LanEnv)
Asm (non-LanEnv)
|
VCON
|
Yes
Yes
|
Yes
Yes
|
Yes
Yes
|
Yes
Yes
|
No2
Yes4
|
Yes
No5
|
Yes
Yes
|
Asm (LanEnv)
Asm (non-LanEnv)
|
LOAD
BALR
|
Yes
Yes
|
Yes
Yes
|
Yes
Yes
|
Yes
Yes
|
No2
Yes4
|
Yes
No5
|
Yes
Yes
|
Asm (LanEnv)
Asm (non-LanEnv)
|
LINK
|
Yes
Yes
|
Yes
Yes
|
Yes
Yes
|
Yes6
Yes6
|
Yes
Yes
|
No5
No5
|
Yes
Yes
|
Note: The
failure symptoms described in these notes are as they would appear when the
Language Environment TRAP(ON)
and ABTERMENC(ABEND) runtime options are in effect.
- CEEENTRY macro with MAIN=YES creates a Language Environment assembler
main. If you specify MAIN=NO on the CEEENTRY macro, a Language Environment
assembler subroutine is created. The default is MAIN=YES.
- Invoking a Language Environment assembler main program from an established
Language Environment enclave is not recommended (unless through the use of
SVC LINK). For this reason, the table entries associated with this footnote
are marked No. A nested enclave is not created and, therefore, the program
runs as a subprogram in the invoking enclave. If you follow this recommendation,
you might avoid the need for reprogramming in the future.
- You must specify NAB=NO and MAIN=NO on the CEEENTRY macro. Otherwise,
you will receive failure symptom 0C1, 0C4, or 0C5 abend.
- If the non-Language Environment assembler caller is running within an
established Language Environment enclave, see note 2.
- Failure symptom of 0C1, 0C4, or 0C5 abend.
- Except when OS/VS COBOL programs exist in another established Language
Environment enclave. For detail, see Failure symptom of: message IGZ0005S.