Generation output and associated files

There are many types of generatable parts in the EGL language. In addition to the COBOL or Java™ output resulting from generation, there are other files that result from generation process. Most of these associated files are control files that affect the preparation or deployment of the generated code.

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

Table 1. Generation output for generatable parts
Generatable 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 Creates a service binding program used by service clients to locate and call services. See the table below for more detail.
  generated as Java Creates a service binding XML file used by service clients to locate and call services. See the table below for more detail.
JSF Handler generated as Java Creates output that controls a user's runtime interaction with a Web page.
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 a Jasper report.
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 following 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 generatable part. If the alias property is not specified, the name of the generatable 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:
Table 2. Additional files created during generation
File type Generation type Description
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.
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.
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.
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.
Services in EGL act a bit differently from other generatable parts. When you generate the EGL deployment descriptor, which contains binding information for your EGL services, EGL generates the service parts and also creates other files needed to deploy your services. The following table shows the files created, sorted according to whether you are generating COBOL or Java and also according to your target runtime environment.
Table 3. Generation output for EGL deployment descriptors
Deployment descriptor part Target runtime environment Resulting files
Web service entry z/OS CICS COBOL Generation produces the following:
  • 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 Generation produces the following:
  • 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 in Web service data conversion
  Java (all environments) Generation produces the following:
  • 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 in Web service data conversion
Web service client proxy z/OS CICS COBOL Generation produces the following:
  • A COBOL Web service proxy program used by EGL COBOL clients to call Web services
  • A WSDL file that is used to describe the remote Web service
  • A CICS Web service binding file that is used by CICS to convert SOAP messages to and from COBOL data
  • A CICS Web service log file that is used to log events when creating the Web service binding file
  iSeries COBOL A COBOL Web service proxy program used by EGL COBOL clients to call Web services.

Feedback