Welcome
Developing
Developing EGL applications
Enterprise Generation Language (EGL) is a programming language that you can use to focus on business problems instead of software technologies. Within the Rational® development environment, you can use EGL wizards and other tools to write complex applications with minimal effort.
EGL Programmer's Guide
The EGL Programmer's Guide covers using EGL within the Eclipse Integrated Development Environment (IDE), as well as some of the common programming tasks that EGL developers perform.
Developing programs for iSeriesC
You can deploy EGL-generated COBOL programs targeted for the IBM® i environment.
Compatibility considerations for iSeriesC
There are a number of platform issues to consider in preparing programs to run in an iSeries® environment.
File I/O status in sysVar.errorCode for iSeriesC
If the V60ExceptionCompatibility program property is set to YES, the sysVar.errorCode system variable contains the status code for file I/O in the iSeriesC environment.

Overview
Getting started
Installing
Upgrading and migrating
EGL Code Accelerator for IBD
Developing
- Model driven development of EGL code
- Generating source code from UML models
  You can use transformations to create source code from a UML model. First you must create a transformation parameters file and then apply those parameters to a model.
- Generating the EGL Dependency Graph from EGL projects
- Generating Source Code from OpenAPI Documents
- Developing EGL applications
  Enterprise Generation Language (EGL) is a programming language that you can use to focus on business problems instead of software technologies. Within the Rational® development environment, you can use EGL wizards and other tools to write complex applications with minimal effort.
  - How to use this documentation
  - Additional information about EGL
    The most recent EGL documentation is in the IBM Business Developer documentation.
  - EGL Programmer's Guide
    The EGL Programmer's Guide covers using EGL within the Eclipse Integrated Development Environment (IDE), as well as some of the common programming tasks that EGL developers perform.
    - Introduction
      These topics explain the fundamentals of using EGL in the Eclipse IDE, as well as changes to the EGL language and IDE in this version.
    - Contents of an EGL application
      EGL applications contain projects, packages, folders, and files.
    - Properties
      Properties set specific options for parts. In general, you specify the properties when you create the part and then the properties are static. In certain circumstances, however, it is possible to change a property dynamically.
    - Annotating EGL Applications
      EGL developers can annotate their applications to indicate the version, authors as well as a general description.
    - Import and use statements
      Use the EGL import and use statements to expand the visibility of code elements.
    - Working with EGL code
    - Accessing data with EGL code
    - Transfer of control across programs
    - Developing segmented programs in EGL
      Different runtime environments have different considerations for developing segmented programs.
    - Developing EGL programs for the IMS™ environment
    - Developing EGL programs for the CICS® environment
      There are specific design and development considerations when creating EGL programs for CICS® for z/OS® and CICS for VSE.
    - Developing EGL programs for the VSE environment
      IBM Business Developer provides a Generation for VSE feature that you can use to generate EGL as COBOL source for the z/VSE® environment.
    - Developing programs for iSeriesC
      You can deploy EGL-generated COBOL programs targeted for the IBM® i environment.
      - Defining native database files for iSeriesC programs
        You must consider a number of issues when preparing your EGL programs and data for use with native database files in the iSeriesC target environment.
      - Considerations for iSeriesC database commitment control
        You can specify how an EGL program uses Commitment Control services in the iSeriesC target environment.
      - Recovery and database integrity considerations for iSeriesC
        EGL programs can use all the recovery and data integrity features that DB2® provides in the iSeriesC environment.
      - Compatibility considerations for iSeriesC
        There are a number of platform issues to consider in preparing programs to run in an iSeries® environment.
        iSeriesC file SHARE attribute
        The file SHARE attribute has an effect on the behavior of EGL programs in the iSeriesC environment.
        File I/O status in sysVar.errorCode for iSeriesC
        If the V60ExceptionCompatibility program property is set to YES, the sysVar.errorCode system variable contains the status code for file I/O in the iSeriesC environment.
        unique and duplicate I/O error enablement for iSeriesC
        If you use the unique or the duplicate file I/O error values in an EGL expression, you must enable detection of duplicate record keys for indexed files in the iSeriesC environment.
      - Considerations for EGL form definition and runtime behavior for iSeriesC
        There are specific considerations in the iSeriesC environment when you use Text UI forms.
      - Performance considerations for iSeriesC
        You can tune your EGL programs in the iSeriesC environment to improve performance.
      - Security considerations for iSeriesC
        The iSeriesC environment provides commands to control access to programs and administration activities.
    - Overview of EGL Logging for Java Application
    - Overview of EGL Rich UI
    - Services: a top-level overview
      The topics in this section describe service-oriented architecture (SOA) and related technologies, EGL support for SOA, and service-related procedures, with an emphasis on service access. For details about deployment, see “Introduction to EGL generation and deployment” and “Add web-service deployment entries in the EGL deployment descriptor.”
    - Generating source code from UML models
      You can use transformations to create source code from a UML model. First you must create a transformation parameters file and then apply those parameters to a model.
    - Building EGL Text User Interface applications
      A Text UI application presents a text-based user interface similar to that of a 5250 or 3270 terminal.
    - Creating reports with EGL
      EGL offers different ways to create reports, using external engines to generate the report contents.
    - Working with web transaction applications in EGL
    - Debugging EGL applications
    - EGL Unit Testing
    - z/OS Connect
  - EGL Generation Guide
    The EGL Generation Guide covers the process of converting EGL code to Java™ or COBOL source code, including the processes and the files involved. This section is intended for a developer who will generate or deploy EGL applications.
  - EGL Language Reference
    The EGL Language Reference covers the fundamental use of the language, including its concepts, syntax, and keywords. This volume is intended for a developer writing EGL applications with some experience in procedural programming.
  - Rational® COBOL Runtime Guide for zSeries®
    This manual provides information about customizing and administering the IBM® Rational® COBOL Runtime.
  - IBM Business Developer EGL Server Guide for IBM® i
    This manual provides information about customizing and administering EGL Server for IBM® i on the host.
  - Generation for VSE Feature Reference
    This reference manual provides z/VSE-specific information about developing and generating EGL programs in the VSE environment.
- Source code analysis with code review
  With code review, you can create configurations of coding rules for EGL source code. You can then run the configurations to check the source code for consistency with the rules.
- Responsive Design Support in IBD
  What is Responsive Design? Responsive design is an approach for creation of web pages that automatically scales its content and elements to match the screen size on which it is viewed. So, instead of designing multiple websites for different devices with variable screen sizes, we can design just one website that scales up or down automatically, to match the device it’s being viewed on.
- Containerizing an EGL RUI Application
Samples
Troubleshooting and support
EGL runtime error messages
Reference
Glossary
Using the help
Notices for IBM Business Developer documentation

File I/O status in sysVar.errorCode for iSeriesC

If the V60ExceptionCompatibility program property is set to YES, the sysVar.errorCode system variable contains the status code for file I/O in the iSeriesC environment.

For generated COBOL, use the sysCodes build descriptor option to control the codes that are returned for file I/O errors. The sysCodes build descriptor option does not affect the EGL I/O error values.

If you set the sysCodes build descriptor option to "YES", sysVar.errorCode contains system dependent access method return codes. This is the COBOL File Status Key. For information on the COBOL File Status Key values, see the i5/OS™ Information Center. For details on the format of sysVar.errorCode, see errorCode.
By contrast, if you set sysCodes build descriptor option to "NO", sysVar.errorCode contains return codes from the EGL runtime services I/O routine that detected the IBM® i file I/O error.

The following table shows the correspondence between status key values, EGL I/O error values, and sysVar.errorCode. There are many COBOL File Status Key values that might correspond to a single sysVar.errorCode.

Table 1. Correspondence between Status Key Values, I/O error values, and sysVar.errorCode
errorCode (sysCodes = "YES"), COBOL File Status Key values	EGL I/O error value	errorCode (sysCodes = "NO")
00,05,07	[no error]	000
02	duplicate, ioError	103
04 (Variable-length record)	[no error]	000
04	invalidFormat, ioError, hardIOError	220
10,14,46	endOfFile, ioError	102
22	unique, ioError	206
23 (START)	endOfFile, ioError	102
23	noRecordFound, ioError	205
24,34 (access method not relative or relative key not 0)	full, ioError, hardIOError	25A
35	fileNotFound, ioError, hardIOError	251
38	fileNotAvailable, ioError, hardIOError	218
39,95	invalidFormat, ioError	220
9D	deadlock, ioError, hardIOError	381

For all other COBOL File Status Key values, sysVar.errorCode is set based on the type of request as shown in the following table:


Type of request	EGL I/O error value	errorCode (sysCodes = "NO")
OPEN	ioError, hardIOError	500
CLOSE, UNLOCK	ioError, hardIOError	989
READ, START	ioError, hardIOError	987
WRITE	ioError, hardIOError	988