GDDM function can be invoked by application programs that use standard
OS/370 call interfaces. These include application programs written using
the programming languages and compilers shown in Table 7.
|
|
|
Table 7. Programming languages and compilers |
Language |
Compiler / Interpreter |
Notes |
Assembler |
H Assembler or High Level Assembler |
|
APL2 |
|
1, 2, 3 |
BASIC |
IBM BASIC |
1, 2, 4 |
COBOL |
DOS/VSE OS/VS VS COBOL II |
|
C |
C/C++ Compiler |
|
C/370 |
C/370 Compiler |
1 |
FORTRAN |
VS FORTRAN |
1, 5 |
PL/I |
DOS Optimizing Compiler OS Optimizing Compiler Checkout Compiler |
|
REXX |
TSO/E 2.1.0 |
1, 6 |
Notes:
1. GDDM Interactive Map Definition (GDDM-IMD) does not generate
application data structures in FORTRAN, IBM BASIC, APL2, C/370, or
REXX. However, application data structures generated by GDDM-IMD can
be converted for use in C/370 and REXX applications. Also, mapping
techniques can be used in FORTRAN and IBM BASIC applications for which
programmers create their own data structures.
2. High-performance alphanumerics is not supported in BASIC and APL2
applications.
3. The GDDM auxiliary processor (AP126) gives full-screen control and
allows access by APL programs to the functional capabilities of GDDM
Base and GDDM-PGF.
4. IBM BASIC/VM and IBM BASIC/MVS each provide a CALL statement that can
be used to call GDDM.
5. GDDM application programs written in FORTRAN cannot run under the CICS
and IMS subsystems.
6. GDDM-REXX is supported in the VM and MVS environments. There is no
support for GDDM-REXX in the VSE environment. In the MVS environment,
TSO/E 2.1.0 is required. The GDDM-REXX component of GDDM 3.2 must be
both licensed and enabled.
|