SCLM translators

This chapter describes the translators provided with SCLM. The translators are used in language definitions that are included with SCLM. You can modify these language definitions for the specific needs of your site and environment. The supplied parsers might not recognize all syntax rules for a specific language, and you might have to modify statements to adhere to generic syntax.

FLMCSPDB DB2 Bind/Free translator
FLMDTLC DTL Processor Build translator
FLMLPCBL COBOL Parser
FLMLPFRT FORTRAN Parser
FLMLPGEN General Purpose Parser
FLMLRASM REXX Assembler Parser
FLMLRCBL REXX COBOL Parser
FLMLRCIS MVS C/C++ parser with include set support
FLMLRC2 C, C++, and Resource file parser for workstation source
FLMLRC37 REXX C370 Parser
FLMLRDTL REXX DTL Parser
FLMLRIPF Script and OS/2 IPF Source Parser
FLMLSS General Purpose Parser
FLMLTWST Workstation Build translator
FLMTBMAP Build Map Print - Build translator
FLMTCIDS, FLMTCVER, FLMTCLGT, FLMTCPC, FLMTCPP, FLMTCCPS CPS translators:
SCLM CSP programs are shipped for historical reasons to allow SCLM customers to use the CSP within SCLM. However, since CSP is no longer supported by IBM®, support for these SCLM CSP programs is not provided:
FLMTCIDS

Initialise dummy data sets

FLMTCVER

CSP verify translator

FLMTCLGT

CSP LIST(A) and generate translator

FLMTCPC

CSP Promote copy translator

FLMTCPP

CSP Promote purge translator

FLMTCCPS

CSP translator to copy from a PDS member into a sequential file
FLMTMJI Interface to JOVIAL Compiler
FLMTMMI Interface to DFSUNUB0 (phase 2 of MFSUTL and MFSTEST)
FLMTMSI Interface to SCRIPT/VS
FLMTPRE
FLMTPST
FLMTXFER Workstation Transfer - Build translator

There are five types of translators:

A parse translator gathers statistics and dependencies. Parse translators run during migration, when the member is saved in an edit session, or when the SAVE or PARSE service is called. A parse translator can also be used to define user data and change codes for the member.
A verify translator can be used to perform validation in addition to default SCLM validation. The verify translator can be used to check the change codes or user data defined for members. Another example could be verification of data that is related to an SCLM-controlled member but is not under SCLM control itself. Verify translators run during build and promote verification.
For builds, SCLM invokes a verify translator to verify inputs to build translators. For example, when an LEC architecture definition is being built, the source member is verified before compiling and the object member is verified before linking.

For promotes, SCLM invokes a verify translator to verify build inputs and outputs. For example, when an LEC architecture definition is being promoted, the source, object, and load members are verified before the promote copy phase.
A build translator can assemble, compile, link, or otherwise process a member so that the outputs have different formats than the inputs. For example, building a COBOL source program generates a listing and an object module.
A copy translator is invoked when Promote copies an SCLM-controlled member to the next group in the hierarchy. Copy translators are invoked before Promote copies the SCLM-controlled member. If the copy translators for a member fail, Promote does not attempt to copy the controlled member. Copy translators can be used to copy data that is related to an SCLM-controlled member but is not under SCLM control itself.
Purge translators can be used to purge data that is related to an SCLM-controlled member but is not under SCLM control itself. Purge translators are invoked whenever SCLM performs a delete operation on an SCLM-controlled member during build or promote.