z/OS ISPF Software Configuration and Library Manager Guide and Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Define the language definitions

z/OS ISPF Software Configuration and Library Manager Guide and Reference
SC19-3625-00

Language Definitions define the languages and translators that a project uses. SCLM functions invoke translators (such as compilers, parsers, and linkage editors) based on a member's language. The language definition defines the translators used by each language. Each language can have multiple translators defined for it. The translators can be IBM® program products, independent program products, or user-written translators.

IBM provides examples of language definitions for many commonly used languages such as COBOL and PL/I.

Table 1. Language Definitions Supplied with SCLM
Compilers and Linkage Editors Language Definitions
Architecture definition FLM@ARCD (noncompiler)
BookMaster® FLM@BOOK (noncompiler)
CICS® map groups FLM@BMS
CLIST FLM@CLST (noncompiler)
COBOL OS/VS FLM@COBL
COBOL OS with CICS preprocessing FLM@CCOB
COBOL OS with DB2® preprocessing FLM@2COB
COBOL OS with DB2 and CICS preprocessing FLM@ECOB
COBOL II FLM@COB2
COBOL II with CICS preprocessing FLM@CICS
COBOL II with DB2 preprocessing FLM@2CO2
COBOL II with DB2 and CICS preprocessing FLM@ECO2
COBOL II with member expansion and CICS preprocessing FLM@ICO2
Enterprise COBOL FLM@COBE
COBOL with integral CICS preprocessing FLM@CCBE
Enterprise COBOL with integral DB2 preprocessing FLM@2CBE
Enterprise COBOL with integral DB2 and CICS preprocessing FLM@2CCE
COBOL FLM@RCBL (COBOL parser written in REXX)
 
C/C++ for MVS™ FLM@RCIS (C/C++ parser written in REXX)
C/370™ FLM@C370, FLM@RC37 (C/370 parser written in REXX)
C/370 with CICS preprocessing FLM@CC
C/370 with DB2 preprocessing FLM@2C
C/370 with DB2 and CICS preprocessing FLM@EC
C/370 with member expansion and CICS preprocessing FLM@IC
C/370 with pre-link FLM@CPLK
C/370 pre-link with link-edit FLM@CLNK
DB2 See Table 1
Enterprise COBOL compiler with integral DB2 preprocessing and Fault Analyzer side file generation. FLM@2CBF
DB2 and PL/I enterprise compiler and NCAL linkedit to a sub-module library with Fault Analyzer side file generation. FLM@2PLF
FORTRAN IV FLM@FORT
FORTRAN IV with DB2 preprocessing FLM@2FRT
JOVIAL FLM@JOV FLM@JOVC
Object language definition to migrate object modules into SCLM as outputs (non-editable) FLM@COPY
Object/Load dummy language definition to migrate object and load into SCLM as inputs (editable) FLM@OBJ
Pascal FLM@PSCL
PL/I Checkout Compiler FLM@PLIC
PL/I Optimizer with DB2 preprocessing FLM@2PLO
PL/I Optimizing Compiler FLM@PLIO
PL/I Optimizer with CICS preprocessing FLM@CPLO
PL/I Optimizer with DB2 and CICS preprocessing FLM@EPLO
PL/I Optimizer with member expansion and CICS preprocessing FLM@IPLO
Enterprise PL/I FLM@PLIE
Enterprise PL/I with integral CICS preprocessing FLM@CPLE
Enterprise PL/I with integral DB2 preprocessing FLM@2PLE
REXX FLM@REXX (noncompiler) FLM@REXC (compiler)
Language Parsers written in REXX FLM@RASM (Assembler), FLM@RCBL (COBOL), FLM@RC37 (C/370), FLM@RCIS (C/C++ for MVS)
SCRIPT 3 FLM@SCRP (noncompiler)
S/370 Assembler F FLM@ASM
S/370 Assembler with DB2 preprocessing FLM@2ASM
S/370 Assembler with CICS preprocessing FLM@ASMC
S/370 Assembler with DB2 and CICS preprocessing FLM@EASM
S/370 Assembler with member and CICS preprocessing FLM@IASM
S/370 Assembler H FLM@ASMH
High Level Assembler for MVS FLM@HLAS, FLM@RASM (Assembler parser written in REXX)
S/370 Linkage Editor FLM@L370
TEXT FLM@TEXT (noncompiler)

All the example language definitions are located in the data set ISP.SISPMACS.

The ISPF Sample and Macro libraries contain a number of other files to support SCLM workstation builds. See ISPF Sample and Macro libraries.

This step describes how to define language definitions to the project definition. When this step is complete, all the languages your project will use will be defined.

To define the language definitions:

  1. Determine what languages are used in your project.
  2. Copy the appropriate example language definitions to the project.PROJDEFS.SOURCE data set allocated in Step 4: Allocate the PROJDEFS data sets.
  3. Modify the language definitions.

    If you do not find an example language definition that meets your project requirements, you can write a new language definition. For instructions on defining a new language to SCLM, see Defining a new language to SCLM.

See SCLM macros for details on the use of each SCLM macro.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014