AMBCOMP Program

Restriction: This topic applies only when the AppMaster Builder AddPack has been installed, and applies only to Windows platforms.

To initiate Distributed Generation Server from the mainframe, you execute the AMBCOMP program from the JCL that is running your APS job. You can replace all of the standard APS generation steps with a single AMBCOMP step. The AMBCOMP program processes a set of SYSIN cards that specify the following:

AMB generation parameters
Cataloged PDS names containing input source files needed by the AMB generators
Cataloged PDS and member names of input CNTL files neede by the AMB generators
Cataloged PDS name where generated components and the AMB generation logfile are sent upon completion of the generation process

The AMBCOMP program passes this information to the Distributed Generation Server as an XML document. The Distributed Generation Server writes the document to an XML file in the apsftwrk subdirectory of the user area specified on the Distributed Generation Server workstation.

Note: If you start Distributed Generation Server with the Error Reporting Level set to Debug and Keep User Area Files checked, DGS keeps the XML file; it is not deleted and can be useful when tracking problems.

The DGS then parses this XML file and creates two files in the jobqueue subdirectory of the user area specified on the Distributed Generation Server workstation:

The first file has an extension of .lst and contains generation parameters and locations of input and output files
The second file has an extension of .sub and drives the AMB generators

Note: If you start Distributed Generation Server with the Error Reporting Level set to Debug and Keep Submission Files checked, DGS keeps these files; they are not deleted and can be useful when tracking problems.

After the AMB generation process completes, APSCOMP writes the AMB generation log file to the jobqueue subdirectory. This file does not have a file extension. It contains messages and return codes from each of the AMB generators.

After all of the appropriate AMB generators have finished, DGS uploads a number of files to mainframe-cataloged PDSs. These files include all generated components (e.g., COBOL programs, screen symbols, BMS, MFS, etc.) and the AMB generation log file.

Jobs steps following the AMBCOMP step, (e.g., DB2 translator, CICS translator, COBOL compiler, etc.) might execute, depending on the value of this return code.