Generation output

This topic outlines the output generated by EGL, including the control files that affect preparation or external deployment.

For Rich UI, two outputs are generated for each handler or library: a JavaScript™ file, and a deploy file that lists all of the parts referenced by the part being generated. The EGL deployer uses the deploy files to determine what JavaScript™ files are to be included in the HTML file. For further details, see "Overview of Rich UI deployment."

The following table lists the main parts and whether the parts are associated with COBOL generation or Java™ generation.

Table 1. Java™ and COBOL generation output for main parts
Main part	Generation type	Description
DataTable	generated as COBOL	In zSeries® platforms, creates a COBOL program that contains the data table contents; in iSeries® platforms, creates a binary file which contains the data table contents.
	generated as Java™	Creates a Java™ class that contains the data table contents.
EGL deployment descriptor	generated as COBOL	A table shown later gives the detail.
	generated as Java™	A table shown later gives the detail.
Library	generated as COBOL	Creates a COBOL program and provides functions and values for use by other generated COBOL programs.
	generated as Java™	Creates a Java™ class and provides functions and values for use by other generated Java™ programs.
Program	generated as COBOL	Creates a COBOL program that can be run in the target runtime environment (z/OS® batch, z/OS® CICS®, or iSeries®).
	generated as Java™	Creates a Java™ program that can be run outside of J2EE or in the context of a J2EE client application, web application or EJB container.
	generated as Java™ wrapper	Creates Java™ source code that can be used in a non-EGL Java™ program to invoke an EGL-generated program.
Report Handler	generated as Java™	Creates a Java™ class that can make areport.
Record with the stereotype ConsoleForm	generated as Java™	Creates a Java™ class that contains the ConsoleForm.
Service	generated as COBOL	Creates a COBOL program that acts as a service.
	generated as Java™	Creates a Java™ class that acts as a service.

In addition to your Java™ or COBOL output, additional files are created during the generation process. The next table lists these other files and their file names.

The file names of these other files depend on the alias property, if any, that is specified in the part. If the alias property is not specified, the name of the part is used but it is truncated, if necessary, to the maximum number of characters allowed in the runtime environment. Other characteristics of the alias variable in the file name are determined by the kind of output:

If you are generating a COBOL program and related output, all letters of alias are uppercase.
If you are generating a Java™ program, the case of each letter in alias is taken without change from the source code.
If you are generating a Java™ wrapper, the rules for naming the wrapper and EJB session bean are as follows:
- The first letter in alias is uppercase.
- Every subsequent letter is lower case, with this exception: any underscore or hyphen is eliminated, and the subsequent letter is uppercase.

Table 2. Additional files created during Java™ or COBOL generation
File type	Generation type	Description
Bind control file	COBOL for z/OS® when the program uses SQL	This file contains the bind command that is used in preparing an SQL program for z/OS®. The file name is alias.bnd.
Build plan	COBOL, and for Java™ when the destDirectory build descriptor option is set	This file lists the code-preparation steps that will occur in the target runtime environment. The file name is alias_BuildPlan_timestamp.xml.
CICS® table files	COBOL for CICS®	This file specifies the CICS® program and transaction definitions that are needed for a generated COBOL program, form group, data table, or library. The file name is alias.ppt for PPT entries or RDO PROGRAM, or alias.pct for PCT entries or RDO TRANSACTION.
Data definition specification (DDS) files	COBOL for iSeries® when the genDDSFile build descriptor is set to YES	This file contains the data description specification (DDS) files based on the record declarations used for input or output in the program. The file name is alias.dds.
Deployment file	Java™	This file contains a list of build descriptors with which the part was generated. The file name is partName.deploy, even if the part has an alias.
J2EE environment file	Java™, when the genProperties build descriptor option is set to GLOBAL or PROGRAM	This file provides entries for insertion into the J2EE deployment descriptor. The file name is alias-env.txt.
Linkage properties file	Java™	This file guides how calls are made from generated Java™ code, but only if decisions are final at runtime rather than generation time. The file name is linkageOptionsPart.properties, where linkageOptionsPart is the name of the linkage options part specified in the build descriptor.
Link edit file	COBOL for z/OS®	There are two possible files: An initial link edit file generated by EGL. The file name is alias.led. A link edit file that provides a re-link of the program. This file is created only if there is a link edit part for the program being generated. The file name is alias.lkg.
Program properties file	Java™, when the genProperties build descriptor option is set to GLOBAL or PROGRAM	This file contains Java™ runtime properties in a format that is accessible only when you are running or debugging a Java™ program outside of J2EE. The file name is alias.properties, or rununit.properties on a VGWebTransaction if genProperties is set to GLOBAL.
Results file	COBOL, and for Java™ when the destDirectory build descriptor option is set	This file gives status information on the code-preparation steps that occurred on the target platform. The file name is alias_Results_timestamp.xml.
Sample runtime CL	COBOL for iSeries®	This file contains sample Control Logic (CL) used to run an iSeries® program. The file name is alias.clr.
Sample runtime JCL	COBOL for z/OS® batch when the genRunFile build descriptor option is set to YES	This file contains sample JCL used to run a z/OS® batch program. The file name is alias.jcx.
Enterprise JavaBean (EJB) session bean	Java™ wrapper	This file runs in an EJB container. The file name is aliasEJBHome.java for the home interface, aliasEJB.java for the remote bean interface, and aliasEJBBean.java for the bean implementation.

The following table shows the files that are created when you generate the EGL deployment descriptor for Java™ or COBOL. Generating the deployment descriptor has no effect for Rich UI because in that case, the file is used only during deployment.

Table 3. Generation output for EGL deployment descriptors
Purpose of file entry	Target runtime environment	Output files
Web service deployment	z/OS® CICS® COBOL	A COBOL web service wrapper program used by CICS® to start an EGL web service A WSDL file that is used to describe the web service A CICS® web service binding file used by CICS® to convert SOAP messages to and from COBOL data A CICS® web service log file used to log events when creating the web service binding file
	iSeries® COBOL	A Java™ web service wrapper generated to a designated web project. This wrapper provides access to the COBOL service through a layer of Java™ code. A WSDL file that is used to describe the web service A collection of Java™ classes used to communicate between the service wrapper and the service.
	Java™ (all environments); for SOAP services	A Java™ web service wrapper generated to a designated web project A WSDL file that is used to describe the web service A collection of Java™ classes used to communicate between the service wrapper and the service.
	Java™ (all environments); for EGL REST-RPC services	An XML file that defines the EGL REST-RPC endpoints. The file name is projectName-uri.xml, where projectName is the name of the project.
Service binding	z/OS® CICS® COBOL	A COBOL web service proxy program used by EGL COBOL clients to call web services. A CICS® web service binding file that is used by CICS® to convert SOAP messages to and from COBOL data. The file name is eglddName-bind.xml, where eglddName is the name of the EGL deployment descriptor. A CICS® web service log file that is used to log events when creating the web service binding file
	iSeries® COBOL	An XML file that defines the service bindings. The file name is eglddName-bind.xml, where eglddName is the name of the EGL deployment descriptor. A proxy to access the EGL Java™ runtime code by way of the Java™ Native Interface (JNI).
	Java™ Standard Edition; or Apache Tomcat	An XML file that defines the service bindings. The file name is eglddName-bind.xml, where eglddName is the name of the EGL deployment descriptor.
	A fully JEE-compliant application server such as WebSphere® Application Server	An XML file that defines the service bindings. The file name is eglddName-bind.xml, where eglddName is the name of the EGL deployment descriptor. A proxy to interact with the application server A collection of Java™ classes used to communicate between the proxy and the application server.