Easytrieve - 1.0

Description

If your Mainframe application contains Easytrieve Classic or Easytrieve Plus report generator source code and you want to view these object types and their links with other objects, then you should install this extension.

Download and installation instructions

The extension will be automatically downloaded and installed when any of the file types listed below are delivered in the source code. It can be managed through the Application → Extensions interface.

Supported file types

Technology support

The following languages are supported:

Transactions

Transaction support is derived from metamodel concepts used to build CAST Imaging Blueprint and structural transaction flows. Entry Points start transactions; Exit Points include both output/boundary concepts and Data Entities manipulated by transactions.

ISO 5055 Structural Rules

Quality support is based on ISO 5055 structural rules available for the selected extension version.

What results can you expect?

Objects

Type	Object Name	Comment
	Easytrieve Call to Program	Created when a call to a program is not resolved or an external program
	Easytrieve File	Equivalent to Cobol File Link in the Cobol Program
	Easytrieve Macro	Standard Macro declaration
	Easytrieve Procedure	Standard Procedure declaration
	Easytrieve Program	Standard Program declaration
	Easytrieve Report	Standard Report declaration
	Easytrieve SQL Query	An object is created when we encounter EXEC SQL statement
	Missing Schema	Parent of the missing tables and procedures, attached to the Easytrieve Project.
	Missing Table	A table or a view selected/updated/deleted/inserted in an Easytrieve Query missing from the DDL file.
	Missing Procedure	A procedure or a function called in an Easytrieve Query missing from the DDL file.

Links

non-exhaustive list of links between Easytrieve objects

Example of links between Easytrieve objects

The above result are produced based on following code snippets in file DEMOESY2.ezt:

• The Easytrieve Program is created based on the file presence itself.
• The Easytrieve Procedure is created based on the following PROC statement.
• The Easytrieve File is created based on the following FILE statement.
• Access Read and Access Write links are created based on the following POINT and GET statements inside the Easytrieve Procedure.
• Access Read link is created based on the following JOB statement inside the Easytrieve Program.

...
*
FILE M8124D  VS (2446)
  M-KEY                             2   22  A
  M-001-DELETE-CODE                 1    1  A
  M-005-BANK-NUMBER                 2    2  N
  M-010-OBLIGOR-NUMBER              4   10  N
  M-012-APPLICATION-CODE           14    1  N
  M-015-OBLIGATION-NUMBER          15    6  P 0
  M-025-RECORD-CODE                21    3  N
...
 GET-PROCESS-DATE. PROC
      MOVE ' ' TO KEY-M-KEY
      POINT M8124D   GE KEY-M-KEY, STATUS
      IF EOF M8124D , OR FILE-STATUS (M8124D) NOT ZERO
             DISPLAY ' UNSUCCESSFUL START FOR OBLIGATION FILE ' +
                        KEY-M-KEY
         STOP
      END-IF
      GET   M8124D
      IF EOF M8124D , OR FILE-STATUS (M8124D) NOT ZERO
         DISPLAY ' UNSUCCESSFUL READ FOR OBLIGATION INTEGRITY RECORD ' +
                   KEY-M-KEY
         STOP
      END-IF
      DATE-OUT   =     M-DATE
      MOVE MM-OUT    TO MM-IN
      MOVE DD-OUT    TO DD-IN
      MOVE YY-OUT    TO YY-IN
      MOVE DATE-IN   TO PROC-DATE
 END-PROC
...
JOB INPUT M8124D START(START-OBLIGAT-PROC) FINISH(LAST-REC-PROC)
...

The above result are produced based on following code snippets in file DEMOBD2A.ezt:

• The Easytrieve Program is created based on the file presence itself.
• The Easytrieve Procedure is created based on the following PROC statement.
• The Easytrieve SQL Query is created based on the following SQL key word.
• Call Link between the Program and the Procedure is created based on the following PERFORM statement inside the Easytrieve Program.
• Call Link between the Procedure and the SQL Query is created based on the following SQL statement inside the Easytrieve Procedure.

List of links between Mainframe, SQL standard objects and Easytrieve objects

Example of links between Easytrieve and JCL objects

Quality rules

• None on Easytrieve language
• Quality rules computed by com.castsoftware.sql  on Easytrieve SQL Query objects.