EMS FastStart Manual

Installing and Configuring EMS FastStart
EMS FastStart Manual133701
3-2
Post-installation Files
Post-installation Files
After the installation is complete, the following files will be in the EMS FastStart
installation subvolume (ISV) and in your working subvolume:
EMS FastStart Configuration
EMS FastStart lets you adapt the code generation process to your environment by using
a configuration file called CCF (Compiler Configuration File). The CCF should be
modified by your system manager if your installation has different configurations than
the default values specified in the CCF (for example, your COBOL85 compiler is not on
$SYSTEM.SYSTEM). The default CCF is shown in Example 3-1
.
CCF Compiler Configuration File, used to modify the run time
environment of EMS FastStart.
CEGNDECS C Library Header for EGEN Procedure (Needed by C programs).
EGENDECS EGEN TAL Procedures Declaration File.
EMSFS TACL macro file used to attach the segment file.
EMSFSC20 EMS FastStart Segment File for release C20.
EXTRADDL DDL Schema Source File used for user-defined variable data field
types.
SATMACF ATM Example, ACF source code.
SATMC ATM Example, C Source code.
SATMCOB ATM Example, COBOL85 source code.
SATMDDL ATM Example, DDL event definitions
SATMDOC ATM Example, Programming and Compilation Notes.
SATMTAL ATM Example, TAL source code.
SATMTMPL ATM Example, EMF source template.
SOFTDOC Programmer notes supplied in the release tape.
Note. Be aware that EMS FastStart may not work properly if you use a batch product to invoke
the TAL, COBOL85, and DDL compilers at your installation. EMS FastStart uses the
completion codes returned by these compilers to determine if the compilation was successful.
Since some batch products do not return completion codes, EMS FastStart can wait
indefinitely. To correct this problem, specify the exact location of the Tandem compilers in the
CCF.