A specific implementation exists for each supported database: For mainframe DB2, both a dynamic interface and a static interface are supported. SQL statements are dynamically prepared during the compilation of your CA Easytrieve program and an access module or package is created. At runtime, SQL statements are executed from the access module or package. An access plan, from which SQL statements are executed, is created at compile time. Exceptions may exist for specific databases that maintain cursor positioning across commits or syncpoints.
|Published (Last):||21 February 2010|
|PDF File Size:||1.72 Mb|
|ePub File Size:||4.15 Mb|
|Price:||Free* [*Free Regsitration Required]|
The environment and library definition sections are optional, but at least one activity section is required. This section lets you override standard CA Easytrieve options and select a mode of operation. The environment section is not required for most of the examples in this section. Library Definition Section The library definition section describes the data the program processes, data files and their associated fields, and any working storage requirements of the program.
The library definition section is usually required; it is optional when the program does not perform any file input or output. JOB Reads information from files, examine and manipulate data, write information to files, and initiate printed reports.
Creates sequenced or ordered files. Data can be displayed to a terminal operator and received back into the program. Files can be read and updated. You can code one or more procedures PROCs at the end of each activity. Procedures are separate modules of program code that you use to perform specific tasks. The following table shows some CA Easytrieve keywords and other items in the sections where they are usually located.
The table gives the general order of CA Easytrieve statements in a program.
IBM MAINFRAME & MVS FORUM
Easytrieve Guide for Mainframe Programmers (4 of 20)
Structure of Easytrieve programs