Including symbolic feedback code files
Symbolic feedback codes are provided for Language Environment, C or C++, COBOL, Fortran, and PL/I conditions.
The symbolic feedback code files are stored in the SCEESAMP sample
library. To use symbolic feedback codes, you must include the symbolic
feedback code files in your source code. The symbolic feedback code
files have file names of the form xxxyyyCT,
where:
- xxx
- Indicates the facility ID of the conditions represented in the
file. For example, EDCyyyCT contains condition
tokens for C- or C++-specific
conditions (those with the facility ID of EDC).
xxx can be CEE (Language Environment), EDC (C or C++), FOR (Fortran), IBM® (PL/I), or IGZ (COBOL).
- yyy
- Indicates the facility ID of the language in which the declarations are coded. For example, EDCIBMCT contains PL/I declarations of C condition tokens. yyy can be BAL (assembler), EDC (C or C++), FOR (Fortran), IBM (PL/I), or IGZ (COBOL).
- CT
- Stands for “condition token.”
To use symbolic feedback codes, include the file in your source
code using the appropriate language construct, for example:
- In C or C++,
to include the file of C or C++ declarations
for IGZ (COBOL) condition tokens, specify:
#include <igzedcct>
- In COBOL, define SCEESAMP and use the COPY statement to include
the file, as shown below. Define SCEESAMP in your SYSLIB statement:
//SYSLIB DD DSNAME=CEE.SCEESAMP,DISP=SHR
Specify the following in your COBOL code to include the files containing Language Environment and COBOL condition tokens declared in COBOL:⋮ COPY CEEIGZCT. COPY IGZIGZCT. ⋮
- In Fortran,
to include the Fortran declarations
for FOR (Fortran)
and CEE (Language Environment)
condition tokens. specify the following.
INCLUDE (FORFORCT) INCLUDE (CEEFORCT)
- In PL/I,
to include the PL/I declarations
for IBM (PL/I) and
CEE (Language Environment)
condition tokens, specify:
%INCLUDE IBMIBMCT %INCLUDE CEEIBMCT