gdt development tutorial

GDT Development Tutorial

GDT Development TutorialDoug Evans and Detlef Lexut

GDT 2008 International User ConferenceAugust 10 – 13 Lake Las Vegas, Nevada

GDT Development Tutorial

Creating a Net Express Project to run GDT Batch programs and GDT TDS programs Build a Net Express project Setting up Project Properties Loading the Source Pool Preparing programs for Debug Build and Animation Animating the program Preparing programs for Generic Release Build

Using Decision Tables to generate COBOL Source GDTETAB Utility

Using GDT Utility to Generate Report Definition COBOL Source GDTLGEN Utility GDTPGEN Utility



Build a Net Express projectBatch / TDS

From the DOS command prompt, set yourself to the folder where your batch programs are located. For TPR’s, you need to be located where

the TPR programs are located (c:\infosol\prod\source\online) Set your environment ( In this case run GDTENV.BAT). If you do not want

to use FILESHARE, you can also do a SET SRVRNAME= to the folder where your files are located.



Build a Net Express project Batch / TDS

Now type in RUN MFNETX to start the NetExpress IDE. You will now have the necessary environment settings to load your project.




When the IDE is up, we will first createa new project. From the FILE drop

down menu, select NEW.




Now we will select Project to create a newProject.




Now you enter the name of the project (MyBatch) and the location of the project (C:\INFOSOL\PROD\SOURCE\BATCH). Press the Create button. Example for

TPR’s (MyTpr) with location C:\INFOSOL\PROD\SOURCE\ONLINE.



Setting up Project Properties Batch / TDS

Now we need to setup the Project Properties. Fromthe Project drop down menu, select Properties.




First, set the Project Directory. You may use the Browse to select the directory or justmanually type it in. (C:\INFOSOL\PROD\SOURCE\BATCH).

or (C:\INFOSOL\PROD\SOURCE\ONLINE).Next we need to add a couple of directives in the Project Directives Window. They are:

USE(COBOL.DIR) NOCOBOLDIR CONFIRM.Now you need to press the IDE button (Integrated Development Environment settings).




Since we already have set our environment variables before opening

the IDE, all we need to do is Import these settings.

Press the Import button.




Just press the Import button again. It is shown that theCurrent environment will be brought in. (This is the

Environment from the GDTENV.BAT done at the DOSCommand prompt).




This shows all local and system environment variablesthat are going to be set.




You need to select all of the variables and press the OKButton.




Press OK again to set the IDE environment variables. Thisscreen can also be used to add new variables or change the

existing ones.




After pressing the APPLICATION button on the main windowyou are then given a screen to import the APPLICATION environment

as well. Press the Import button.




Again, press the Import button. The current environmentfrom GDTENV.BAT setting will be imported.




As done with the IDE variables, you need to select all of theApplication Variables and press the OK button.




Press ok once all have been selected.




Now select the Program Execution Tab.




You can now set Error Handling features.Have a view to the remaining tabs for additional application

environment settings that can be done.




Now you can press OK as the Project Properties settings are now complete.



Types of Build Setting Batch / TDS

Now we need to setup the Types of Build settings for this project. From the Project dropdown menu select Types of Build…




Select Debug and press the Change button.




Add USE(COBOL.DIR) to the Build Directives.



Loading the Source Pool Batch / TDS

Now right click in your source window. You will be given the option to Add file to source pool.

Select this option.



Loading the Source PoolBatch / TDS

Now you can select the program(s) that you want to be part of this project.We will select the address program for this example.



Loading the Source PoolBatch / TDS

As the program is selected, Net Express will do a dependency check to make sure all copybooks, called programs etc. are found for the program(s) you have selected.



Preparing programs for Debug Build and AnimationBatch / TDS

Now we need to prepare the program for the Debug Build. Select and drag the program over to the build window.

A window will pop up and allow for you to select the preferred compiled type for the program.

We will be selecting intermediate code for debugging.




Now you will see the .int and .cbl in the build Window.




Next we need to set up the Build Settings for address.int. Right click on Address.int or any other program you may have and

select Build Settings.



Preparing programs for Debug Build and Animation

A couple minor modifications are needed. Make sure .\ is placed just before the File name on disk.

This states that the .int file will be placed in the current project directory.




Right click on the Address.cbl member and select the Compile Tab. Again, we need to place a .\ before the %BASENAME.int.

Press Close Button to save your Build Settings.




Now we are ready to compile the program(s). One method is selecting theRebuild All option from the Project menu or you can individually select each

program in your project and press the red check to compile each.




In the Build Window, you will see the information concerning your Build (Compile).




Now we are ready to set up your Animating Settings in coordinationwith the GDT software. From the Animate drop down menu select Settings…



Preparing programs for Debug Build and AnimationBatch Program

Important entries:Start Animating at: c:\infosol\

gdtpc\gdtbatch.lbr\gdtbatch.gnt

Local working Directory: c:\infosol\prod\source\batch - where your compiled program(s) are located.

Command line parameters: c:\infosol\prod\jcl\address.jcl - the directory and name and values of the jcl you need to run. If values

are needed, type them in as if your are running

GDTBATCH via the command line.



Preparing programs for Debug Build and AnimationTPR Program

Important entries:Start Animating at: c:\infosol\

gdtpc\gdtmon7.lbr\gdtmon7.gnt (For V3 users)

Start Animating at: c:\infosol\gdtpc\gdtmon7.lbr\

gdtmon7.gnt –TDS6 (For V4 users)

Local working Directory: c:\infosol\prod\source\online -

where your compiled program(s) are located.

Command line parameters: LOGON tpr name (IPASS in this

case) . Can place a ? in this entry which will bring up the GDTMON7

entry screen.



Animating the programBatch / TDS

Now you are ready to Start Animating. Select Start Animating… fromthe Animate dropdown menu.



Animating the programBatch



Animating the programTPR

FatClient Session is started, prompting you for user and password.




Logon TPR is activated.




TPR you have loaded into your project for debugging, is activated and ready foryou to animate.




You may now Run through the program without further animating. You will then see in the application output window

that the menu is displayed from the program IMENU.




Here is the Application output window. If you have TRACE and STEPMSG set in your GDTBATCH.PAR,

then you will see the input, output counters as when you run GDTBATCH via the command prompt.




You may now Run through the program without further animating.



Preparing programs for Generic Release Build Batch / TDS

Now you can set up your program for a Release Build (.GNT). Select Generic Release Build in the Type of Build Window.




Select and drag the Address.cbl program over to the build window. You now select Generated Code for the compiled type.




Now right click on Address.cbl and select Build Settings.




Again, place .\ before the %BASENAME.GNT to place the .GNT member in the current project folder.



Preparing programs for Generic Release Build

After right clicking on ADDRESS.CBL in the build window and selecting COMPILE, it now produces a .GNT for the ADDRESS program.

TPR Compiled!



Decision Tables

GDTETAB PROJ2.TXT PROJ2.CPY DAT



Decision Tables



GDTETAB Utility

GDTETAB converts symbolic decision tables to COBOL-sections, which may be executed by "PERFORM".

Rules are a key ingredient to the Decision Table.

There are 5 control commands known to GDTETAB : NAM, PRE, BED, AKT and

AFT



GDTETAB Utility5 Control Commands

NAM <name> specifies the name of the decision table. GDTETAB generates

a <name> SECTION. If the command is missing, <name> becomes STANDARD;

PRE <activity to be preprocessed) specifies a statement that will be executed before the

evaluation of the table; BED <conditon>

COBOL-condition (without IF) AKT <activity>

COBOL-statement to be executed pattern of Xs that denotes, what conditions have to be true if

the activity is to be performed; AFT <activity to be postprocessed>

specifies a statement that will be executed after the evaluation of the table.



GDTLGEN UtilityGenerate Report Definition

GdtLGen processes symbolic commands to create COBOL-Records for print output.

GdtLGen is the first choice if the print form design is specified on a paper form with exact columns. For other cases you my prefer GdtPGen.




The input file to the GDTLGEN utility.GDTLGEN RPT1.TXT RPT1.OUT DAT




The Generated Output File from the GDTLGEN Utility




3 commands are available : NAM, VAR and LIT.

NAM (generates a level-01 item) VAR (generates an elementary-item) LIT (generates a FILLER with corresponding

literal-value)



GDTPGEN Generate Report Definition

GdtPGen is the first choice if you design the print forms yourself.

For other cases you my prefer GdtLGen. Like GDTLGEN, GDTPGEN creates COBOL source that

describes a print form. Contrary to GDTLGEN the input format is like the

image form definition of a screen forms generator. Two outputs are created :

an output file with WORKING-STORAGE statements an output file with various MOVE statements, if %F-lines with

FROM were specified .




In input you may use line types as follow : (1) : normal lines that do not start with a % and are

no space lines. They build the print form image. (2) : a line starting with '%F' defines a field. (3) : a line starting with '%R' defines a record. (4) : any other line starting with '%' is treated as a

comment line.




Input file to GDTPGEN Utility




The WORKING-STORAGE statements




The Procedural Statements

gdt development tutorial

Documents