VisualAge COBOL for Windows NT


Getting Started
Version 3.0.2

GC27-0811-02
VisualAge COBOL for Windows NT


Getting Started
Version 3.0.2

GC27-0811-02
 Note!
Before using this information and the product it supports, be sure to read the general information under “Appendix.
Notices” on page 81.

Third Edition (December 2000)

This edition applies to IBM VisualAge COBOL for Windows NT, Version 3.0.2 (program number 5639-I44), and to
all subsequent releases and modifications until otherwise indicated in new editions. Make sure you are using the
correct edition for the level of the product.
Order publications by phone or fax. IBM Software Manufacturing Solutions takes publication orders between 8:30
a.m. and 7:00 p.m. Eastern Standard Time (EST). The phone number is (800) 879-2755. The fax number is (800)
445-9269.
You can also order publications through your IBM representative or the IBM branch office serving your locality.
Publications are not stocked at the address below.
A form for reader’s comments appears at the back of this publication. If the form has been removed, address your
comments to:
IBM Corporation, Department HHX/H3
P.O Box 49023
San Jose, CA 95141-9023
USA
or Fax it to this U.S. number: 800-426-7773
or use the form on the Web at:
http://www.ibm.com/software/ad/rcf/
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any
way it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 1995, 2000. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
What’s new in this release . . . . . . . v Preparing to uninstall Version 2.2 and earlier
Version 3 . . . . . . . . . . . . . . . v versions . . . . . . . . . . . . . . 20
Uninstalling VisualAge COBOL. . . . . . . 21
Chapter 1. Product overview . . . . . . 1 Uninstalling the search system in Version 3.0 or
later . . . . . . . . . . . . . . . . 21
Working with OS/390 host applications . . . . . 1
Installing and configuring the MS Loopback
Access host data sets in COBOL MVS projects . . 2
Adapter on Windows NT. . . . . . . . . . 23
Edit host files with the COBOL editor . . . . . 2
Installing and configuring the MS Loopback
Compile on the workstation to check syntax . . . 2
Adapter on Windows 2000 . . . . . . . . . 24
Submit batch jobs to the host . . . . . . . . 2
Installing Version 3.0.2 if Version 3.0 is not already
Monitor the status of batch jobs on the host . . . 2
installed . . . . . . . . . . . . . . . 24
Execute TSO commands on the host . . . . . 2
Basic installation: installing on your local hard
Debug programs running on an OS/390 host . . 2
drive . . . . . . . . . . . . . . . 25
Building stored procedures . . . . . . . . 2
Network installation: installing on a network
Comparing workstation and host concepts . . . 3
server . . . . . . . . . . . . . . . 25
Working in a project environment . . . . . . . 4
Shared installation: installing on a client from a
Editing source code . . . . . . . . . . . . 4
network server . . . . . . . . . . . . 25
Creating GUI applications . . . . . . . . . . 5
Configuring components after installation . . . 26
Creating COBOL applications for the workstation . . 5
Configuring your browser for online help . . . . 26
Compiler and run-time environment . . . . . 5
Configuring Netscape . . . . . . . . . . 27
Object-oriented extensions . . . . . . . . . 6
Configuring MS Internet Explorer . . . . . . 27
DB2 coprocessor . . . . . . . . . . . . 6
Resetting environment variables . . . . . . . 27
Distributed data access . . . . . . . . . . 6
After uninstalling COBOL or C++ . . . . . . 28
Debugging workstation applications . . . . . . 6
Using your own macros for the editor . . . . 28
Developing CICS host applications from your
Using your own Interface Repository files . . . 29
workstation. . . . . . . . . . . . . . . 7
Installing by using a response file . . . . . . . 29
Accessing IMS databases . . . . . . . . . . 8
Setup parameters for silent installation . . . . 29
Analyzing program performance . . . . . . . 8
Setup log file for silent installation . . . . . 30

Chapter 2. Hardware and software

Chapter 4. Configuring your systems 33
requirements . . . . . . . . . . . . 11 Configuring and connecting your workstation for
Required hardware . . . . . . . . . . . . 11 remote ECD . . . . . . . . . . . . . . 34
Processor . . . . . . . . . . . . . . 11 Verifying your connection . . . . . . . . 37
Memory . . . . . . . . . . . . . . 11
Hard drive space . . . . . . . . . . . 11
Adapter card . . . . . . . . . . . . . 11
Chapter 5. Creating an MVS project . . 41
Required software . . . . . . . . . . . . 11
For remote edit-compile-debug . . . . . . . 12 Chapter 6. Creating your first
For local development . . . . . . . . . . 12 VisualAge COBOL application. . . . . 45
Software requirement notes . . . . . . . . 12 Creating a non-GUI project . . . . . . . . . 46
Optional software . . . . . . . . . . . . 13 The COBOL Projects folder . . . . . . . . 47
Stored procedure manager . . . . . . . . 13 The IBM VisualAge COBOL Project window . . 47
Data Assistant . . . . . . . . . . . . 13 Creating the application . . . . . . . . . . 48
Remote data access . . . . . . . . . . . 14 Building the application . . . . . . . . . . 49
LAN data access. . . . . . . . . . . . 14 Running the application . . . . . . . . . . 50
Local DB2 development . . . . . . . . . 15
Software requirement notes . . . . . . . . 15 Chapter 7. Creating a simple Visual
Local CICS development . . . . . . . . . 16
Builder application . . . . . . . . . 53
MQSeries for Windows NT . . . . . . . . 17
Creating a visual project . . . . . . . . . . 54
Oracle* * . . . . . . . . . . . . . . 17
Starting Visual Builder. . . . . . . . . . . 55
Sybase* * . . . . . . . . . . . . . . 17
The Composition Editor window . . . . . . 56
Changing the title of the to-do list frame window 57
Chapter 3. Installing on the workstation 19 Placing parts in the application window . . . . . 57
Installing Version 3.0.2 if Version 3.0 is already Placing a static text part in the window . . . . 58
installed . . . . . . . . . . . . . . . 19 Placing an entry field in the window . . . . . 58
Uninstalling VisualAge COBOL. . . . . . . . 20

© Copyright IBM Corp. 1995, 2000 iii

 Placing another static text in the window . . . 58 Creating a nonvisual part. . . . . . . . . . 71
Placing a list box in the window . . . . . . 59 Defining features . . . . . . . . . . . 71
Placing the push buttons in the window. . . . 59 Defining your system interface . . . . . . . . 72
Resizing and aligning the parts . . . . . . . . 59 Generating your code . . . . . . . . . . . 73
Dragging and dropping parts in the frame Generating the feature source . . . . . . . 73
window . . . . . . . . . . . . . . 60 Generating the part source . . . . . . . . 73
Resizing the frame window (optional) . . . . 60 Updating feature source . . . . . . . . . . 73
Matching the width of the list box to the width Connecting the parts . . . . . . . . . . . 75
of the entry field . . . . . . . . . . . 60 Adding the Date nonvisual part . . . . . . 75
Sizing and aligning the push buttons . . . . . 61 Connecting the nonvisual part to the main part 75
Aligning the static text so their left edges are Connecting the Date push button to the blank
even . . . . . . . . . . . . . . . . 61 static text field . . . . . . . . . . . . 75
Connecting the parts . . . . . . . . . . . 62 Generating the COBOL code for your application. . 76
Connecting the Add push button to the list box 63 Building the application . . . . . . . . . . 77
Connecting the Remove push button to the list Running the application . . . . . . . . . . 77
box . . . . . . . . . . . . . . . . 64 Exiting the Visual Builder . . . . . . . . . 77
Generating the COBOL code for your application. . 65
Building the application . . . . . . . . . . 65 Chapter 9. Product support . . . . . . 79
Running the application . . . . . . . . . . 66 Getting product support . . . . . . . . . . 79
Exiting the Composition Editor and Visual Builder 66 CompuServe . . . . . . . . . . . . . 79
Fixes . . . . . . . . . . . . . . . 79
Chapter 8. Expanding the simple Visual FAX . . . . . . . . . . . . . . . . 79
Builder application . . . . . . . . . 67 Phone . . . . . . . . . . . . . . . 79
Opening the TODOLIST part . . . . . . . . 68 Mail . . . . . . . . . . . . . . . . 80
Enabling the Add push button . . . . . . . . 68 Getting consulting services . . . . . . . . . 80
Making the Add push button unavailable . . . 68 Getting education and training . . . . . . . . 80
Making the Add push button available when text
is entered in the entry field . . . . . . . . 68 Appendix. Notices . . . . . . . . . . 81
Removing the entry field text . . . . . . . 69
Making the Add push button unavailable . . . 69 Index . . . . . . . . . . . . . . . 83
Adding and aligning new parts to display the date 70

iv Getting Started
What’s new in this release
This section lists the primary changes in Version 3 of IBM VisualAge COBOL for
Windows NT.

Version 3
v Enhanced OS/390 host connectivity for remote editing, compiling, and
debugging of COBOL source code that resides on an OS/390 host
v A new wizard for setting up COBOL projects and a new MVS connections
manager for configuring and managing connections to MVS systems
v A job monitor for submitting JCL to an OS/390 system and then monitoring job
status and job output.
v Job monitor support for JES2 and JES3
v A stored procedure manager for creating and managing DB2 Universal Database
for OS/390 stored procedure definitions associated with your MVS projects
v An HTML help system, making information easier to find
v Enhanced debugging capability with IBM Distributed Debugger for debugging
COBOL, C++, and compiled Java programs running on an OS/390 host system
or on your workstation
v File locking (as for ISPF) so that only one user can edit a file at the same time
v Support for Windows 2000
v Support for long file names

For more information about enhancements in VisualAge COBOL Version 3, refer to

the IBM COBOL Web site.

RELATED CONCEPTS
“Chapter 1. Product overview” on page 1

© Copyright IBM Corp. 1995, 2000 v

vi Getting Started
Chapter 1. Product overview
VisualAge COBOL is an integrated development environment for editing,
compiling, and debugging COBOL applications that reside on an OS/390 host. You
can also use VisualAge COBOL for developing applications that reside on a
workstation or a LAN.

With VisualAge COBOL, you develop host COBOL programs remotely from your
workstation without downloading files. Application parts (such as COBOL source
code, COBOL copy books, and host JCL) stay in partitioned data sets (PDSs) on the
host. You access and work with them through an MVS project on your
workstation, as if they resided on your workstation.

Communication between the workstation and the host for remote editing,
compiling, and debugging is accomplished through a TCP/IP connection. A wizard
helps you create MVS projects on your workstation, and a connection manager
helps you configure and manage your connection to the MVS system.

With remote ECD, you can develop or enhance many types of applications,
including CICS, batch, TSO, or IMS Database Manager and IMS Transaction
Manager (with or without BTS) applications. These applications can access many
forms of data, including DB2, VSAM, DL/I, and QSAM data.

RELATED CONCEPTS
“Working with OS/390 host applications”
“Working in a project environment” on page 4
“Editing source code” on page 4
“Creating GUI applications” on page 5
“Creating COBOL applications for the workstation” on page 5
Debugging applications“Debugging workstation applications” on page 6
“Developing CICS host applications from your workstation” on page 7
“Accessing IMS databases” on page 8
“Analyzing program performance” on page 8

Working with OS/390 host applications

The remote edit-compile-debug component (remote ECD) of VisualAge COBOL
provides a workstation environment for developing COBOL applications targeted
for the host. With remote ECD, you can do the following tasks.

© Copyright IBM Corp. 1995, 2000 1

 Access host data sets in COBOL MVS projects
After completing the required configuration, you can connect to PDS or PDSE data
sets and include members in your MVS project. You can then access your host files
as if they were workstation files.

Edit host files with the COBOL editor

You can edit remote files using the COBOL editor, which enables you to use the
language-sensitive editing on host COBOL programs.

Compile on the workstation to check syntax

From the workstation, you can run a syntax-check compile on your source files to
ensure they compile error-free before submitting them for compiling on the host.

Submit batch jobs to the host

You can submit jobs directly from your project without logging on to your host.

Monitor the status of batch jobs on the host

From your workstation, you can monitor the status of jobs submitted to the host,
and look at job output.

Execute TSO commands on the host

You can open a TSO command prompt window from your project and submit TSO
commands to the host.

Debug programs running on an OS/390 host

You can debug COBOL, C++, and compiled Java programs running on an OS/390
host system in the following environments: batch (JES), TSO, CICS, and IMS (BTS,
IMS TM, IMS DM). The debugging sessions are cooperative; that is, you work on
your workstation with the Distributed Debugger, while Debug Tool runs your
program on the host. The workstation and the host communicate with each other
through a TCP/IP connection. The COBOL code must be at the ANSI 85 level.

RELATED CONCEPTS
“Building stored procedures”
“Comparing workstation and host concepts” on page 3

Building stored procedures

The stored procedure manager integrates the management of the stored procedure
definition with your MVS project where you are developing your stored procedure
logic.

Using the stored procedure manager, you can do the following tasks:
v Associate a DB2 Universal Database for OS/390 stored procedure definition with
an MVS project.
v Create, view, modify and drop the stored procedure definition.
v Generate SQL to create, modify or drop the definition.
v Understand the impact that the definition has on the COBOL development and
run-time environments.

RELATED REFERENCES
DB2 UDB for OS/390 V5 Application Programming and SQL Guide (SC26-8958-02)

2 Getting Started
 HTML PDF
DB2 UDB for OS/390 V6 Application Programming and SQL Guide (SC26-9004-00)
HTML PDF

Comparing workstation and host concepts

If workstation concepts are new to you, but you are familiar with the host
environment, the following table might help you. It provides a comparison of
workstation and host concepts. In most cases, the terms are only roughly
equivalent.

Workstation concept Host concept

File: A unit of stored or processed Member: In OS/390 and MVS, a data set is
information such as text, data, and the major unit of data storage and retrieval.
programs. A member is a partition of a partitioned
data set.
Batch file (.BAT) and command file JCL: Stands for job control language, which
(.CMD): a file containing operating system is used to identify a job to an operating
commands organized for sequential system and to describe the job’s
processing. In workstation programs, requirements.
command files are much like JCL.
A CLIST is a list of TSO commands and
A command file can also function similarly statements designed to perform a specific
to a CLIST (in OS/390 or MVS) or an EXEC function for the user, and an EXEC is a
(in VM). user-written command file that contains
REXX commands and execution of control
statements, such as branches.
Dynamic link library (DLL) file: This file DLL files are much like preloaded
contains executable code and data that is subprograms in the link pack area on MVS
bound to a program at load or run time, and OS/390 or in a shared segment on VM.
rather than during linking. The code and For COBOL, DLL files are most like
data in a DLL can be shared by several dynamically called subprograms.
applications at the same time.
Environment variables: These are any SYS1.PARMLIB and a STEPLIB or
number of variables that describe the way PARMLIB statement in JCL perform
an operating system is going to run and the functions similar to workstation
devices it is going to recognize. For example, environment variables, in that they provide
in a COBOL project on the workstation, an global values or settings, and provide search
environment variable is an operating system information.
variable like PATH and DPATH, and other
environment variables that are defined such
as TMP.
Executable (.EXE) file: This is a file that Load module, statically linked program,
contains the executable code for a program. statically linked load module: All or part of
a computer program in a form suitable for
loading into main storage for execution. A
load module is usually the output of a
linkage editor.
Module definition (.DEF) file: Directives to Linkage editor input statements: Directives
the linkage editor on how to build the to the linkage editor, such as INCLUDE and
executable file. NAME, on how to build the load module.
Make: An action that invokes the make Any automated way of controlling
utility, a tool that automates the process of compiling and link-editing.
updating project files. This process includes
compiling and linking programs.

Chapter 1. Product overview 3

 Workstation concept Host concept
Workstation desktop: A graphical way of No exact equivalent. The closest equivalent
accessing your tools and files. It fills the on the mainframe is menu-driven tools such
entire screen and holds the objects with as ISPF or OfficeVision.
which you can interact to perform
operations on the operating system.

Working in a project environment

With the VisualAge COBOL project environment, your tools and files are
integrated into a single development environment, where you can work with your
files directly rather than accessing them through individual tools. For example,
when you want to edit your source code, you select the icon representing the file
and invoke the edit action from the pop-up menu for the file. You can concentrate
on the file itself because you can rely on the project to provide context-sensitive
actions for your files.

With VisualAge COBOL, you organize your code by grouping related files into
projects. A COBOL project is the complete set of data and actions you need to
complete a programming task. An MVS project typically includes the COBOL
source programs you want to edit and compile, as well as related files like JCL and
BMS maps. A workstation project typically includes the files and other information
needed to build a single target, such as a dynamic link library (DLL) or executable
(EXE).

VisualAge COBOL provides preconfigured COBOL projects. When you create your
own COBOL projects, you get a complete set of actions, types, and environment
variable settings preconfigured for your particular project type. This means that
you get an environment with the tools and actions already set up for you.

RELATED CONCEPTS
“Editing source code”

RELATED TASKS
“Chapter 6. Creating your first VisualAge COBOL application” on page 45

Editing source code

The COBOL editor provides language-sensitive editing for your files. Different
COBOL constructs, such as comments, are shown in different colors. In addition,
context-sensitive help is available for most COBOL language elements. COBOL
keywords are highlighted and by pressing F1, you get help for a particular
language element.

Aside from standard editing functions, you can create GUI code, generate SQL
statements, and generate calls to invoke CICS transactions with the following
components of VisualAge COBOL.
Code Assistant
Generates code to access the data and attributes of your graphical user
interface parts. Code Assistant is available only if you have installed the
Visual Builder. Code Assistant works with files with CBV and CPV
extensions. The Visual Builder must be running to access Code Assistant.
Data Assistant
Simplifies the process of constructing embedded SQL statements. SQL

4 Getting Started
 statements generated by Data Assistant can be compiled and executed in
Windows and host COBOL programs. Data Assistant is available only for
non-GUI applications.

The COBOL editor displays certain tool bar icons and menu choices for the coding
assistants when you need them. The tool bar icons and menu choices for the Data
and Transaction Assistants come up only if you are editing a COBOL file (CBL), a
copy file (CPY), a DB2 file (SQB), or a CICS file (CCP).

RELATED CONCEPTS
“Creating GUI applications”

Creating GUI applications

The COBOL Visual Builder helps you create COBOL GUI applications.

The Visual Builder is based on a “construction from parts” paradigm. It consists of

the following:
Composition Editor
Use the Composition Editor to create the views for your application,
choose the parts that perform the logic you need, and make connections
between the parts.
System Interface Editor
Use the System Interface Editor to specify the names of files and resources
associated with the current part.
Part Interface Editor
Use the Part Interface Editor to define the features (attributes, actions, and
events) for your parts, along with a list of preferred features for the pop-up
connections menu. These features make up the part’s interface. You use
them when you make connections between collaborating parts. You can
also promote features of subparts from this editor.

RELATED CONCEPTS
“Creating COBOL applications for the workstation”

RELATED TASKS
“Chapter 7. Creating a simple Visual Builder application” on page 53

Creating COBOL applications for the workstation

VisualAge COBOL supports development of new COBOL applications targeted for
the workstation by providing the following function on the workstation.

Compiler and run-time environment

The VisualAge COBOL compiler and run-time environment supports the high
subset of ANSI 85 COBOL functions, just like the other IBM COBOL products.
Your applications can be compiled and run on supported platforms, whether they
are created on an OS/390 host, an AIX workstation, or a Windows workstation.

The IBM COBOL language is by in large the same across platforms, with minor
differences between IBM COBOL for OS/390 & VM and VisualAge COBOL.

Chapter 1. Product overview 5

 Object-oriented extensions
The object-oriented language extensions of VisualAge COBOL are a syntax
extension to COBOL that implements a complete object-oriented paradigm. These
object-oriented extensions allow you to define classes and subclasses, to instantiate
objects, and to have objects inherit characteristics from other objects.

VisualAge COBOL creates language-neutral objects that interoperate with objects

created in other object-oriented languages enabled for the IBM System Object
Model* (SOM*). This is provided through the Direct-to-SOM capability of
VisualAge COBOL.

DB2 coprocessor
The COBOL compiler on the workstation provides a DB2 coprocessor, which
eliminates the DB2 precompiling step, resulting in better optimization of EXEC
SQL statements. The DB2 support is fully integrated with the compiler. Your source
program containing embedded SQL statements is handled by the compiler without
your having to use a separate precompiler. When the compiler encounters SQL
statements and at significant points in the source program, the DB2 coprocessor
processes the SQL statements by taking appropriate actions and indicating to the
compiler what native COBOL statements to generate.

Distributed data access

VisualAge COBOL also provides a set of functions that enable your applications to
handle data across distributed environments. The services include:
v Access to remote VSAM record files using the file-processing capabilities of
COBOL
v Copy, sort, and merge functions for both record and byte files
v Access to local and remote DB2, CICS, and Oracle database using native, SQL
support
v Data managed by Btrieve** using the file-processing capabilities of COBOL
v Local sequential, relative, and indexed files using the STL (a VisualAge COBOL
access method) file system, which supports full ANSI 85 COBOL standard file
I/O language

These services complement their counterpart services on the host, enabling you to
create client/server and cooperative processing applications using the IBM COBOL
language. Your applications can also call the utilities directly using the application
programming interfaces (APIs) that come with the utilities.

RELATED CONCEPTS
Debugging applications“Debugging workstation applications”

Debugging workstation applications

The Distributed Debugger helps detect and diagnose errors in source code
developed with VisualAge COBOL. You can use the Distributed Debugger to
debug programs running on an OS/390 host through a TCP/IP connection (with
Debug Tool running your program on the host) as well as debug programs
running on your workstation. Using the Distributed Debugger, you can do the
following tasks:

6 Getting Started
 Step through or run a program
You can step through your program one line at a time, or you can run the
program until a breakpoint is encountered, the program is halted, or the
program ends.
You can also select the way the Distributed Debugger steps through a
program. If you are debugging a call, for example, you can halt the run
when the call is complete, at the first statement in the called program, or at
the return statement of the current program. The Distributed Debugger can
also step over any program for which debugging is not available, such as
library and system routines.
Set breakpoints
You can control how your program executes by setting breakpoints. A
breakpoint stops the execution of your program at a specific location or
when a specific event occurs.
View the program source code
You can view the source code of the program you are debugging. You can
view it as a source, disassembly (assembler instructions), or mixed (a
combination of source and disassembled code).
Monitor variables
You can display and change the variables during debugging.
Monitor the registers
You can view all the processor and coprocessor registers for a particular
thread.
Monitor the call stack
You can display all of the active programs, the stack frame size, and the
return address. When the state of the program changes, such as when you
execute the program or you update displayed data, the Distributed
Debugger changes the information displayed to reflect the current state.
Monitor storage
You can monitor variables in a storage window. For example, if you are
monitoring a pointer, as the pointer changes, the storage window changes
to show the new location referenced by the pointer.

RELATED CONCEPTS
“Developing CICS host applications from your workstation”

Developing CICS host applications from your workstation

Included with VisualAge COBOL is the VisualAge CICS Enterprise Application
Development offering, which enables complex transaction management
applications to be developed and tested using the function available in VisualAge
COBOL. VisualAge CICS Enterprise mirrors the enterprise environment for
transaction systems on a typical desktop computer. It provides the capability to use
the power of the workstation together with networks, which can be local area or
wide area, stand-alone or host-attached.

With VisualAge CICS Enterprise, you can:

v Communicate between application programs and local and remote workstations,
terminals, subsystems, printers, and other devices.
v Add more CICS resources while debugging and testing transactions.

Chapter 1. Product overview 7

 v Use the standard CICS distributed features all in one desktop computer, namely:
Distributed link, Transaction routing, Function shipping, and Distributed
Transaction Processing over MRO or ISC.
v Enable a non-CICS application to call a VisualAge CICS program synchronously
or asynchronously, using External Call Interface (ECI).
v Enable programs in one CICS system to have requests to address resources (such
as files or queues) in any other connected CICS system executed on that system.
v Use the performance analyzing function to provide information that will assist
in the resolution of application performance issues including a high-level
application trace and probe.
v Use IBM’s leading commercial messaging MQSeries (TM) software.

RELATED CONCEPTS
“Accessing IMS databases”

Accessing IMS databases

Remote DL/I provides access to IMS full-function databases and GSAM databases
from programs using DL/I calls running on a workstation. Remote DL/I provides
the support to develop and test mainframe COBOL programs on a workstation
that use DL/I calls in IMS batch applications that access IMS full-function
databases and GSAM databases.

With VisualAge COBOL’s Remote DL/I support, you can develop, compile and
test COBOL programs that run in an IMS batch environment and use CBLTDLI
calls on the workstation.

Note:
v Remote DL/I does not provide access to IMS message queues or IMS fastpath
databases.
v Remote DL/I runs using only S/390 data types as input and output. It does not
provide any data conversion function.

Remote DL/I uses APPC and an IMS batch environment to provide the remote
DL/I call support. When Remote DL/I is first initialized on the workstation, you
are prompted for your TSO user ID and password, which are used when the
remote job is started on MVS. APPC is used by Remote DL/I to start a job on
MVS, which brings up an IMS batch environment. When the IMS batch
environment is available, remote DL/I calls can be processed. The DL/I calls on
the workstation are sent to the IMS batch environment environment and executed.
The results of the DL/I call are then sent back to the program running on the
workstation.

RELATED CONCEPTS
“Analyzing program performance”

Analyzing program performance

The Performance Analyzer helps you understand your program’s flow and tune
your program’s performance.

It traces the execution of your application and allows you to analyze the call-return
path of your COBOL programs as well as the paragraphs within your programs.
The generated trace file contains trace analysis data that can be graphically

8 Getting Started
displayed in diagrams. Using these diagrams, you can improve the performance of
an application, examine occurrences that produce faults, and in general,
understand what happens when your application runs.

The Performance Analyzer does not replace static analyzers or debug tools, but it
can complement them by helping you understand aspects of the application that
would otherwise be difficult or impossible to see.

With the Performance Analyzer, you can do the following tasks:

Time and tune applications
The Performance Analyzer time stamps each trace event using a
high-resolution clock (about 838 nanoseconds per clock tick). As a result,
the trace file contains a detailed record of when each traced function was
called and when it returned.
The trace data also shows how long each function runs. This information
helps you find hot spots, the areas within an application where a
disproportionate amount of time was spent.
Locate program hangs and deadlocks
The Performance Analyzer provides a complete history of events leading
up to the point where a program stops. You can view the function call
stack from anywhere in the application.
Trace multithreaded interactions
When multithreaded applications are traced, you can look at the
sequencing of functions across threads in some of the diagrams. These
diagrams highlight problems within critical areas of the application.
Trace the complete application
Not only does the analyzer trace procedures in the EXE file, but it also
traces the entry points to system calls and application DLLs.

Chapter 1. Product overview 9

10 Getting Started
Chapter 2. Hardware and software requirements
This section provides the minimum hardware and software requirements for
VisualAge COBOL, the software requirements for optional components that you
choose to install, and the software requirements for the products that you want to
operate with VisualAge COBOL.

RELATED REFERENCES
“Required hardware”
“Required software”
“Optional software” on page 13

Required hardware
This section provides hardware requirements for VisualAge COBOL for Windows
NT, Version 3.0.2.

Processor
Pentium-based 100MHz processor (minimum) or higher (recommended)

Memory
128 MB or higher

Hard drive space

v Basic installation: 400 MB
v Network server installation: 690 MB
v Shared installation: 10 MB
v Swap space: 40 MB

All hard drive space estimates are for the full product. You can reduce the space
required by selectively installing components. InstallShield displays the amount of
hard drive space required for the components you select.

Adapter card
For host communications, LAN adapter card supported by Windows NT

RELATED REFERENCES
“Required software”
“Optional software” on page 13

Required software
This section provides the minimum software required for VisualAge COBOL for
Windows NT, Version 3.0.2.

© Copyright IBM Corp. 1995, 2000 11

 For remote edit-compile-debug
On the OS/390 host
v OS/390 Version 2 Release 5 or later, which includes the following required
software:
– TCP/IP
– IBM HTTP Server (formerly known as Domino Go Webserver for OS/390),
plus the appropriate PTF for APAR PQ29311
– For job monitor support, the PTF for JES APAR 0W41734
– For JES3 support, the PTF for APAR OW36022 and the PTF for APAR
OW45210
– OS/390 Language Environment. Apply the PTFs for the following APARs as
appropriate (“Language Environment note” on page 13): PQ088138, PQ05057,
and PQ07402 for OS/390 V2R5; PQ32787 (for DBCS in Debug Tool) for
OS/390 V2R7
v IBM COBOL for OS/390 & VM Version 2 Release 1 (5648-A25) Full Function
Offering, which includes the following required software (“COBOL note” on
page 13):
– Debug Tool, plus the PTFs for APARs PQ30470 and PQ31829, which
synchronize Debug Tool with IBM Distributed Debugger in VisualAge
COBOL. In addition, the PTFs for APARs PQ33668 and PQ37039 are
recommended; they bring the Debug Tool up to the current service level and
provide support for remote debug of COBOL OS/390 applications running
under UNIX System Services (USS).
– The PTFs for the following APARs as appropriate: PQ21350, PQ36963, and
PQ35436

On the workstation
v IBM VisualAge COBOL for Windows NT, Version 3.0.2 (5639-I44)
v One of the following:
– Microsoft Windows NT** Version 4.0 (Service Pack 4 or later is required)
– Microsoft Windows 2000** Professional
v Microsoft Loopback Adapter
v For the Information Center (online help):
– One of the following:
- Netscape Navigator for Windows 4.51 or later
- Microsoft Internet Explorer 5.0 or later
– For online books in PDF format, Adobe Acrobat Reader 4.0 or later
– For a shared installation, Microsoft Peer Web Services on the network server

For local development

One of the following:
v Microsoft Windows NT Version 4.0 (Service Pack 4 or later required)
v Microsoft Windows 2000 Professional
v Microsoft Windows 98** (for application execution only)
v Microsoft Windows 95** (for application execution only)

Software requirement notes

The following notes are referenced from the software requirements material.

12 Getting Started
 COBOL note
v Source code must be at the ANSI 85 level.

Language Environment note

v For debugging, applications must run under Language Environment. A steplib
can be used to make Language Environment available at run time.

RELATED REFERENCES
“Optional software”

Optional software
This section lists requirements for components of VisualAge COBOL that you
choose to install or use, such as the stored procedure manager. It also includes
requirements for specific products that operate with VisualAge COBOL, such as
MQSeries.
v “Stored procedure manager”
v “Data Assistant”
v “Remote data access” on page 14
v “LAN data access” on page 14
v “Local DB2 development” on page 15
v “Local CICS development” on page 16
v “MQSeries for Windows NT” on page 17
v Oracle“Oracle* *” on page 17
v Sybase“Sybase* *” on page 17

Stored procedure manager

On the OS/390 host
DB2 Universal Database for OS/390 Version 5 or Version 6

On the workstation
For accessing DB2 data on an OS/390 host:
v Run-time Client for DB2 Universal Database Version 6.1
– Available from the Web
– Included in DB2 server software
v One of the following:
– DB2 Connect Enterprise Edition (included with DB2 Universal Developer’s
Edition Version 6.1)
– DB2 Connect Personal Edition (included with DB2 Personal Developer’s
Edition Version 6.1)

Data Assistant
For Data Assistant, the following are required on the Windows NT workstation
(“Packaging note” on page 16):
v SDK for DB2 Universal Database Version 5.2 or Version 6.1
– Available from the Web
– Included in DB2 server software
v One of the following:

Chapter 2. Hardware and software requirements 13

 – DB2 Connect Enterprise Edition (included with DB2 Universal Developer’s
Edition Version 5.2 or Version 6.1)
– DB2 Connect Personal Edition (included with DB2 Personal Developer’s
Edition Version Version 5.2 or Version 6.1)

Remote data access

On the OS/390 host
v For accessing IMS data on an OS/390 host, one of the following:
– IMS/ESA Database Manager Version 6 Release 1 (5655-158), plus the PTF for
APAR PQ07947 (for remote DL/I)
– IMS/ESA Database Manager Version 5 Release 1 (5695-176) plus the PTF for
APAR PQ07950 (for remote DL/I)
v For accessing DB2 data on an OS/390 host, DB2 Universal Database for OS/390
Version 5 or Version 6
v For accessing VSAM data on an OS/390 host, DFSMS/MVS (included with
OS/390) plus the following APARs: OW20884, OW23571, and OW26104 (which
apply to DFSMS/MVS Version 1.4.0 and below).

On the workstation
v For accessing DB2 data on an OS/390 host:
– Run-time Client for DB2 Universal Database Version 5.2 or Version 6.1
- Available from the Web
- Included in DB2 server software
– One of the following:
- DB2 Connect Enterprise Edition (included with DB2 Universal Developer’s
Edition Version 5.2 or Version 6.1)
- DB2 Connect Personal Edition (included with DB2 Personal Developer’s
Edition Version 5.2 or Version 6.1)
v For communications, one or more of the following, as appropriate:
– IBM eNetwork Personal Communications Version 4.2 for Windows (for IMS
and SdU, but not CICS)
– IBM eNetwork Communications Server Version 5.0 for Windows NT (for IMS
and SdU, but not CICS)
– Microsoft SNA Server Version 3.0 or later (for CICS and SdU, but not IMS)

LAN data access

On the server
v For accessing DB2 data on a LAN, one of the following: (DB2 server
requirements“Server requirements” on page 16)
– DB2 Universal Database Enterprise - Extended Edition Version 5.2 or Version
6.1
– DB2 Universal Database Enterprise Edition Version 5.2 or Version 6.1
– DB2 Universal Database Workgroup Edition Version 5.2 or Version 6.1
v For developing and testing CICS applications, one of the following:
– VisualAge CICS Enterprise Application Development Version 3.1, included
with VisualAge COBOL for Windows NT, Version 3.0.2 (includes support for
host data types)

14 Getting Started
 – TX Series Version 4.2 for Windows NT (which contains CICS Version 4.2 for
Windows NT) (no support for host data types)
– Transaction Server Version 4.0 for Windows NT (which includes CICS Version
4.0 for Windows NT) plus the PTF1 Refresh Level (no support for host data
types)

On the workstation
v For developing applications that access DB2 data on a LAN, the following:
(“DB2 note”)
– Run-time Client for DB2 Universal Database Version 5.2 or Version 6.1:
- Available from the Web
- Included in DB2 server software
– SDK for DB2 Universal Database corresponding to the Run-time Client level
(“Packaging note” on page 16)
– Workstation DB2 requirements for LAN scenario“Workstation DB2
requirements for LAN access” on page 16
v For developing applications that access CICS data on a LAN, one of the
following:
– VisualAge CICS Enterprise Application Development Version 3.1, which
includes host data type support and is provided with VisualAge COBOL for
Windows NT, Version 3.0.2 (recommended).
– TX Series Version 4.2 for Windows NT (which contains CICS Version 4.2 for
Windows NT) (no host data type support)
– Transaction Server Version 4.0 for Windows NT (which includes CICS Version
4.0 for Windows NT) plus the PTF1 Refresh Level (no host data type support)

Local DB2 development

One of the following (“Packaging note” on page 16):
v DB2 Universal Developer’s Edition Version 5.2 or Version 6.1
v DB2 Personal Developer’s Edition Version 5.2 or Version 6.1

For more information, refer to one of the following Web addresses:

v Web information
v DB2 library
v CompuServe: GO IBMDB2
v Anonymous FTP site: ftp.software.ibm.com/

Software requirement notes

The following notes are referenced from the software requirements material.

DB2 note
Before embarking, you are strongly urged to get more information from one or
more of the following Web addresses.
v Web information
v DB2 library
v Installing and Configuring DB2 Clients book (with requirements)
v CompuServe: GO IBMDB2
v Anonymous FTP site: ftp.software.ibm.com/

Chapter 2. Hardware and software requirements 15

 Packaging note
v DB2 Universal Developer’s Edition Version 6.1 is comprised of the SDK and the
developer licenses and media for the following:
– DB2 Universal Database Enterprise Edition
– DB2 Universal Database Workgroup Edition
– DB2 Universal Database Personal Edition
– DB2 Connect Enterprise Edition
– DB2 Connect Personal Edition
v DB2 Personal Developer’s Edition is comprised of the SDK plus the developer
licenses and media for the following:
– DB2 Universal Database Personal Edition
– DB2 Connect Personal Edition
v DB2 Universal Database Enterprise Edition and DB2 Universal Database
Enterprise - Extended Edition include the DB2 Connect Server Support
component. All references to DB2 Connect Enterprise Edition also apply to the
DB2 Connect Server Support component.

Server requirements
v For IPX/SPX, NetBIOS, or TCP/IP, the Windows NT base operating system
provides support.
v For APPC, Microsoft SNA Server Version 3.0 (or later)

Workstation DB2 requirements for LAN access

IPX/SPX, NetBIOS, TCP/IP, APPC, or Named Pipes
v For IPX/SPX, NetBIOS, or TCP/IP, the Windows NT base operating system
provides support.
v For APPC connectivity, one of the following:
– IBM eNetwork Communications Server Version 5.0 for Windows NT
– Microsoft SNA Server Version 3.0 (or later), on the LAN
You do not have to install Microsoft SNA Server on the same workstation as the
Run-time Client for DB2 Universal Database Version 6.1.

Client requirements with DB2 Universal Developer’s Edition or

DB2 Personal Developer’s Edition
v Products running on Windows NT support communications with MVS and
OS/390, databases using SNA (APPC), TCP/IP, and MPTN (APPC over TCP/IP)
protocols. These products can support all of these protocols at the same time.
v For direct connection to MVS and OS/390 databases via SNA (APPC), one of the
following communications products is required:
– IBM eNetwork Communications Server Version 5.0 (or later) for Windows NT
– IBM eNetwork Personal Communications Version 4.2 (or later) for Windows
NT
– Microsoft SNA Server Version 3.0 (or later)
v For direct connections to host databases via TCP/IP, the Windows NT base
operating system provides support.

Local CICS development

For developing and running production applications on Windows NT, one of the
following:

16 Getting Started
 v TX Series for Windows NT Version 4.2 (which contains CICS for Windows NT
Version 4.2)
v Transaction Server for Windows NT Version 4.0 (which includes CICS for
Windows NT Version 4.0) plus the PTF1 Refresh Level.

For developing and testing applications on Windows NT that are targeted for an
OS/390 host:
v VisualAge CICS Enterprise Application Development (provided with VisualAge
COBOL Version 3.0.2)

MQSeries for Windows NT

For developing applications with MQSeries for Windows NT, one of the following:
v MQSeries for Windows NT Version 5.1
v MQSeries Client for Windows NT (shipped with the above product)

Oracle* *
Oracle7 or Oracle 8

Sybase* *
Sybase System 10

Chapter 2. Hardware and software requirements 17

18 Getting Started
Chapter 3. Installing on the workstation
This document provides information you need to install VisualAge COBOL Version
3.0.2 on your workstation.

Before you start the installation, be sure you have done the following:
v You have read the readme.htm file for late-breaking information or other
information that supplements the VisualAge COBOL online help.
v Your workstation meets the hardware and software requirements for the
components of VisualAge COBOL that you choose to install, and for the
applications you want to operate with VisualAge COBOL. Also make sure that
your workstation has enough virtual memory. Your paging file should be 128
MB.
v You have uninstalled Version 2.2 or earlier versions of VisualAge COBOL before
you install Version 3.0.2. You do not have to uninstall Version 3.0 or Version
3.0.1.
v If the contents of the Windows NT CD are not already on your workstation, you
have a Windows NT CD for installing and configuring the MS Loopback
Adapter.
v If you have IBM AntiVirus installed on your workstation, you have V3.02 or
greater. Remove any earlier versions from your workstation before you install.
v If you plan to use IBM VisualAge C++ Version 3.5 for Windows, you have
installed it before you install IBM VisualAge COBOL.

After the installation, be sure to configure your browser so you can access
VisualAge COBOL online help.

RELATED TASKS
“Installing Version 3.0.2 if Version 3.0 is already installed”
“Uninstalling VisualAge COBOL” on page 20
Installing and configuring the MS Loopback Adaptor on Windows NT“Installing
and configuring the MS Loopback Adapter on Windows NT” on page 23
Installing and configuring the MS Loopback Adaptor on Windows 2000“Installing
and configuring the MS Loopback Adapter on Windows 2000” on page 24
Installing Version 3.0.2 if Version 3.0 is not already installed“Installing Version 3.0.2
if Version 3.0 is not already installed” on page 24
“Configuring your browser for online help” on page 26
“Resetting environment variables” on page 27
“Installing by using a response file” on page 29

Installing Version 3.0.2 if Version 3.0 is already installed

To install IBM VisualAge COBOL Version 3.0.2 on a workstation with Version 3.0
or Version 3.0.1 already installed, do the following steps:
1. Insert the IBM VisualAge COBOL 3.0.2 CD in the CD-ROM drive.
2. Select Start -> Run, and type x:\setup.exe, where x is the CD-ROM drive. The
IBM VisualAge COBOL Setup window opens.
3. Select Repair and click Next.
4. Follow the prompts to complete the installation. Your original installation
directory is retained.

© Copyright IBM Corp. 1995, 2000 19

 5. Shut down and restart your computer.
6. If you had any shortcuts, associations, or links to a previous installation of IBM
VisualAge COBOL on your workstation, you should verify or update them
now.
7. Configure your browser for online help.

This procedure is the same for all three types of installations: basic, network, and
shared. For example, if Version 3.0 was installed as a network installation on a
network server, following this procedure will automatically install Version 3.0.2 as
a network installation.

RELATED TASKS
“Configuring your browser for online help” on page 26
“Resetting environment variables” on page 27

Uninstalling VisualAge COBOL

You must uninstall Version 2.2 and earlier versions of VisualAge COBOL before
you install Version 3.0.2.

Preparing to uninstall Version 2.2 and earlier versions

If you are uninstalling Version 2.2 or earlier versions of VisualAge COBOL, do the
following preparatory steps as appropriate:
1. Shut down any running COBOL product applications.
2. Remove any files that you want to retain from the product directories (for
example, ibmcobw) and save them elsewhere on your workstation before
uninstalling.
The following are files created by IBM VisualAge COBOL components that you
might want to save:

Directory where
Component File name located Comments
Compiler IGYCDOPT.DLL ibmcobw\bin Defines the
installation default
values for the
compiler options
Data Assistant *.SM and *.CPY ibmcobw\da Mapping and copy
files that Data
Assistant generates
Tivoli *.AOF, *.CDF, and ibmcobw\files Application
*.GDF description files that
the Tivoli Developer
Kit created
COBOL project Project (*.iwp and ibmcobw directories If you put the project
environment *.iwo) files and source ibmcobw\mainproj files in a directory
directories Files if you outside ibmcobw
used Tools Setup to when you created a
modify any actions project, no action is
needed.

3. Shut down and restart your computer.

You are now ready to uninstall VisualAge COBOL.

20 Getting Started
Uninstalling VisualAge COBOL
Be sure that you have completed the preparatory steps above before uninstalling
Version 2.2 and earlier versions. Do the following steps to uninstall all versions of
VisualAge COBOL:
1. Click Start -> Settings -> Control Panel.
2. In the Control Panel window, click the Add/Remove Programs icon, and then
click the Install/Uninstall tab.
3. On the Install/Uninstall page, double-click IBM VisualAge COBOL
(double-click VisualAge COBOL in Version 2.2 and earlier).
4. Follow the prompts to proceed with the uninstall.
5. Shut down and restart your computer.
6. Check that the product directory (for example, c:\Ibmcobw) and all files in it
were deleted.

RELATED TASKS
Uninstalling the search system“Uninstalling the search system in Version 3.0 or
later”
“Resetting environment variables” on page 27

Uninstalling the search system in Version 3.0 or later

After you have uninstalled IBM VisualAge COBOL, you must restart the operating
system before you do another install. Without this restart, the operating system can
hold onto some search system DLLs, which then are not removed until the next
restart. If you install a search system before you restart, the newly installed search
system DLLs will be deleted on the next restart, rendering the search system
unusable.

If the search system does not get uninstalled when you uninstalled IBM VisualAge
COBOL, you will see that the x:\imnnq directory is still there. This directory might
persist because:
v Another product is using the search system, so it cannot be (and should not be)
removed.
v The search system uninstall did not perform as expected.

Determining which products are registered with the search

system
To determine which products are still registered with the search system, issue one
of the following commands:

imndomap -a (for SBCS)

imqdomap -a (for DBCS)

If this command returns no indexes, you can safely proceed to remove the search
system as described below.

If the list contains indexes that do not belong to VisualAge COBOL (that is, their
names begin with something other than IWZ), you cannot remove the search
system. Another product requires it.

If the list contains only VisualAge COBOL index file names (IWZ3EN*, IWZ3JA*),
VisualAge COBOL could not unregister the indexes, causing the uninstall of the
search system to fail. This problem occurs if VisualAge COBOL was incorrectly

Chapter 3. Installing on the workstation 21

 uninstalled (for example, the ibmcobw directory was deleted manually). In this
case, you must manually unregister the indexes before removing the search system.

Unregistering the indexes

To unregister the indexes, use the following procedure and commands:
1. Ensure that the search server is running:
imnss start server (for SBCS)
imqss -start dbcshelp (for DBCS)
2. Delete each of the index entries:
imndomap -d index_name (for SBCS)
imqdomap -d index_name (for DBCS)
You can remove all of the indexes at once by using one of these commands:
for /f %a in (’imnixlst’) do imndomap -d %a (for SBCS)
for /f %a in (’imqixlst’) do imqdomap -d %a (for DBCS)
3. Remove each of the index files:
nqdelet index_name (for SBCS)
tmdelet index_name (for DBCS)
You can remove all of the index files at once by using one of these commands:
for /f %a in (’imnixlst’) do imnixdel -d %a (for SBCS)
for /f %a in (’imqixlst’) do imqixdel -d %a (for DBCS)
4. Stop the search server:
imnss stop server (for SBCS)
imqss -stop dbcshelp (for DBCS)
5. Verify that there are no VisualAge COBOL indexes (IWZ3*) remaining:
imndomap -a (for SBCS)
imqdomap -a (for DBCS)
If there are, please contact IBM service.
6. Verify that no other indexes are active:
nqcounti search system directory (for SBCS)
tmcounti search system directory (for DBCS)
Here search system directory is something like x:\imnnq.
If this command returns data that indicates one or more indexes are still active, the
search system cannot be removed because other products are still registered. Do
not run the uninstall program or try to remove the search system manually.
If the search system returns “0 indices active,” you can try to remove the search
system.

Removing the search system

If you have established that there are no active indexes registered to other
products, use the following procedure to remove the search system.
1. In the x:\imnnq directory, run the uninstall program uninstnq.exe.
2. Wait at least two minutes.
3. Restart the system. The uninstall program is a silent uninstall. If you do not
wait long enough or do not restart, you might compromise future reinstalls.

If the search system still does not uninstall, you can try removing it manually:
v Remove the registry entries that are under
\\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\NetQuestion. Remove this
entry including all its subtrees.
v Remove the search system directory and all its subdirectories (x:\imnnq).

22 Getting Started
 v Remove the environment variables IMNINST and IMNINSTSRV, and remove the
search system path from the PATH environment variable.

If you still cannot uninstall the search system, call VisualAge COBOL support.

Installing and configuring the MS Loopback Adapter on Windows NT

You must install and configure the MS Loopback Adapter to be able to connect to
an MVS system. You can install the MS Loopback Adapter after you install
VisualAge COBOL, but it must be installed before you start the MVS connections
manager for the first time.

To install the MS Loopback Adapter, follow these steps:

1. Right-click the Network Neighborhood icon on your Windows NT desktop.
Click Properties and select the Adapters tab.
2. On the Adapters page, click the Add button.
3. In the Select Network Adapter window, select MS Loopback Adapter from the
Network Adapter list. Click OK.
4. In the MS Loopback Adapter Card Setup window, click OK to accept the frame
type.
5. In the Windows NT Setup window, specify the location of the installation files
for the adapter. If the installation files are on your workstation, the directory
where they reside is indicated. If not, the directory where they reside on the
Windows NT CD-ROM is indicated, and you will need to insert the CD-ROM.
6. Click Continue. The MS Loopback Adapter will be added to the Network
Adapter list. Click Close.

To configure the MS Loopback Adapter, do these steps:

1. In the Microsoft TCP/IP Properties window, select the MS Loopback Adapter
from the Adapter list.
2. Click the button for specifying an IP address and enter the IP address,
192.168.2.1. Do not click the button to obtain an IP address from a DCHP
server.
3. Move the cursor to the Subnet Mask field. This field should contain
255.255.255.0. Leave the Default Gateway blank. Click OK.
4. Reboot your workstation.

To verify that the MS Loopback Adapter was installed and configured, do these
steps:
1. Right-click Network Neighborhood, then click Properties.
2. Click the Services tab. On the Services page of the Network window, click
NetBIOS Interface, then click Properties.
3. In the NetBIOS Configuration window, you will see that a Lana number with
the value NetBT->NDISLoop has been added.

In some cases, you can increase the speed of bringing up certain tasks by placing
the Loopback Adapter last in the protocol bindings. To do this:
1. Right-click Network Neighborhood, and then click Properties.
2. Click the Bindings tab. On the Bindings page in the Network window, select
all protocols in the box next to Show Bindings for.
3. Expand each protocol option by clicking the + sign.

Chapter 3. Installing on the workstation 23

 4. For each protocol where MS Loopback Adapter appears, click MS Loopback
Adapter and then click Move Down until each occurrence of MS Loopback
Adapter is last in the list of bindings for each protocol.

RELATED TASKS
Installing Version 3.0.2 if Version 3.0 is not already installed

Installing and configuring the MS Loopback Adapter on Windows 2000

To install the MS Loopback Adapter on Windows 2000, follow these steps:
1. Click Start -> Settings -> Control Panel.
2. In the Control Panel window, click Add/Remove Hardware.
3. Click Next at the welcome screen.
4. Click Add/Troubleshoot a device in the task list, then click Next.
5. Click Add a new device in the list of hardware devices, then click Next.
6. Click No, I want to select the hardware from a list when prompted to search
for the new hardware, then click Next.
7. Click Network adapters in the list of hardware types, then click Next.
8. Click Microsoft in the Manufacturers list and Microsoft Loopback Adapter in
the Network Adapter list, then click Next.
9. Click Next again to start the hardware installation, then click Finish after the
hardware is installed.

To configure the MS Loopback Adapter, do these steps:

1. In the Control Panel window, click Network and Dial-up Connections.
2. In the Network and Dial-up Connections window, right-click the appropriate
Local Area Connection for the Loopback Adapter and then click Properties.
3. In the Local Area Connection Properties window, select Internet Protocol
(TCP/IP). Clear all other boxes so that no other components in the list are
selected; if other components are selected, the connection to an MVS system
will not work. Click the Properties button.
4. In the Internet Protocol (TCP/IP) Properties window, click the button for
specifying an IP address and enter the IP address, 192.168.2.1. Do not click the
button to obtain an IP address from a DCHP server.
5. Move the cursor to the Subnet Mask field. This field should contain
255.255.255.0. Leave the Default Gateway blank. Click OK.
6. Reboot your workstation.

RELATED TASKS
Installing Version 3.0.2 if Version 3.0 is not already installed“Installing Version 3.0.2
if Version 3.0 is not already installed”

Installing Version 3.0.2 if Version 3.0 is not already installed

This section provides instructions for installing IBM VisualAge COBOL Version
3.0.2 if Version 3.0 or Version 3.0.1 is not already installed. You must have
administrator authority to complete the installation. Three types of installations of
IBM VisualAge COBOL Version 3.0.2 are possible:
v Basic installation“Basic installation: installing on your local hard drive” on
page 25 installs the IBM VisualAge COBOL base, plus the additional components
that you select, on your local hard drive.

24 Getting Started
 v Network installation“Network installation: installing on a network server”
installs the entire IBM VisualAge COBOL product on a network server, which
then lets you use IBM VisualAge COBOL in a LAN environment with a
minimum number of files on the local hard drives of your client workstations.
v Shared installation“Shared installation: installing on a client from a network
server” installs a minimum number of VisualAge COBOL files on a client
connected to a network server with VisualAge COBOL installed.

Basic installation: installing on your local hard drive

To install VisualAge COBOL on your local hard drive, do the following steps:
1. Insert the IBM VisualAge COBOL CD in the CD-ROM drive.
2. Select Start -> Run, and type x:\setup.exe, where x is the CD-ROM drive.
3. Select Basic installation and click Next.
4. Follow the prompts to complete the installation.
Important: The default installation directory for VisualAge COBOL Version 3.0.2 is
c:\Program Files\IBM\VACOBOL. However, you can install VisualAge COBOL in the
c:\ibmcobw directory, which was the default installation directory in previous
versions, or another directory of your choosing.
Important: The estimates for the amount of space required are too low for FAT file
systems (but correct for NTFS and HPFS formatted target drives). The cluster size
has not been rounded up. Allow approximately 400 megabytes for a basic
installation if you selected all of the components. If you selected only some of the
components, multiply by 1.7 the space that the installation program says is
required. This factor may be a little lower on a smaller disk where the FAT cluster
size is smaller.
5. Shut down and restart your computer.
6. If you had any shortcuts, associations, or links to a previous installation of IBM
VisualAge COBOL on your workstation, you should verify or update them
now.
7. Configure your browser for online help.

Network installation: installing on a network server

To install VisualAge COBOL on a network server, do the following steps:
1. Insert the IBM VisualAge COBOL CD in the CD-ROM drive.
2. Select Start -> Run, and type x:\setup.exe, where x is the CD-ROM drive.
3. Select Network installation and click Next.
4. Follow the prompts to complete the installation. (The notes labeled Important
above apply here as well.)
5. Shut down and restart your computer.
6. If you had any shortcuts, associations, or links to a previous installation of IBM
VisualAge COBOL on your workstation, you should verify or update them
now.
7. Configure your browser for online help.

Shared installation: installing on a client from a network

server
If you have installed VisualAge COBOL Version 3.0.2 on a network server and you
want to install VisualAge COBOL on a client from the network server, do the
following steps:
1. Connect to the network server where VisualAge COBOL is installed.

Chapter 3. Installing on the workstation 25

 2. Select Start -> Run, and type x:\Program Files\IBM\VACOBOL\setup.exe, where
x:\Program Files\IBM\VACOBOL is the drive and directory where VisualAge
COBOL is installed on the network server.
3. Select Shared installation and click Next.
4. Follow the prompts to complete the installation.
5. Shut down and restart your workstation.
6. If you had any shortcuts, associations, or links to a previous shared installation
of IBM VisualAge COBOL on your workstation, you should verify or update
them now.
7. Configure your browser for online help.

Important: When connecting to the network server from a client in a shared

installation, be sure to do the following to preserve your link:
v Do not use Network Neighborhood to establish a connection to the network
server.
v If you connect to the network server by using Map Network Drive, be sure to
click the Reconnect at Logon box.
v If you connect to the network server by using the net use command, be sure to
specify the persistent:yes option.

Configuring components after installation

The following components require configuration or setup after you install.
Instructions are provided in the Information Center.
v Your browser (for online help)
v Remote edit-compile-debug (remote ECD)
v Remote DL/I
v SMARTdata UTILITIES (SdU)

For more information on the product or to report problems, refer to the IBM
COBOL Web site.

RELATED TASKS
“Configuring your browser for online help”
“Resetting environment variables” on page 27
“Installing by using a response file” on page 29

Configuring your browser for online help

If your organization uses a proxy server for connecting to the Internet, the proxy
configuration for your browser must include the following exceptions for the
VisualAge COBOL help system to work: localhost:49213,127.0.0.1. These proxy
exceptions allow your browser to bypass the proxy and access the help system
directly. The installation program for VisualAge COBOL checks your browser’s
proxy configuration and will update it for you. However, in the following cases
you may need to manually update your browser’s proxy configuration:
v If you are using VisualAge COBOL from a user ID other than the one from
which COBOL was installed.
v If your browser’s proxy exception settings have been changed after installation
(for example, the IE setup wizard was run).
v If you declined to have your proxy settings updated during the installation.

26 Getting Started
 Configuring Netscape
To check that your browser configuration for Netscape 4.x is correct, do the
following steps:
1. In Netscape, click Edit -> Preferences.
2. In the Preferences window, click Advanced -> Proxies.
3. If the Direct connection to the Internet button is selected, no action is required.
If the Automatic proxy configuration button is selected, contact your system
administrator to ensure that 127.0.0.1 is included in your proxy exceptions.
If the Manual proxy configuration button is selected, do the following steps:
a. Click View (next to the Manual proxy configuration button).
b. In the Manual Proxy Configuration window, add
localhost:49213,127.0.0.1 to the list of proxy exceptions at the bottom.
c. Click OK on both the Manual Proxy Configuration window and the
Preferences window to have your changes take effect.

If you use VisualAge COBOL without a TCP/IP connection to a network, and you
use Netscape for viewing the online help, you must click the Direct connection to
the Internet button for the online help to work.

Configuring MS Internet Explorer

To check that your browser configuration for Internet Explorer 5.x is correct, do the
following steps:
1. In Internet Explorer, click Tools -> Internet Options.
2. In the Internet Options window, click the Connections tab.
3. Click the LAN settings button at the bottom of the Connections page.
4. If the Use a proxy server box is not checked, no action is required.

If the Use a proxy server box is checked, do the following steps:

a. Click Advanced (next to the Use a proxy server box).
b. In the Proxy Settings window, add localhost:49213;127.0.0.1 to the list of
proxy exceptions at the bottom.
c. Click OK on both the Proxy Settings window and the Local Area Network
(LAN) Settings window to have your changes take effect.

RELATED TASKS
“Resetting environment variables”
“Installing by using a response file” on page 29

Resetting environment variables

To reset environment variables, follow these steps:
1. Click Start -> Settings -> Control Panel.
2. In the Control Panel window, double-click the System icon, and then click the
Environment tab.
3. On the Environment page, set the variables to the appropriate values (as
discussed in the sections below). That is, for each variable, do as follows:
v Type the name of the variable (for example, SOMBASE) in the Variable box.
v Type the value of the variable (for example, c:\ibmcobw\SOM, where
c:\ibmcobw is the path where VisualAge COBOL was installed) in the Value
box.

Chapter 3. Installing on the workstation 27

 v Click the Set button.
4. Click OK after setting all the variables.

After uninstalling COBOL or C++

VisualAge COBOL Version 3.0 and VisualAge C++ Version 3.0 use the same names
for environment variables for SOM Toolkit and other components. If you have
VisualAge C++ already on your system when you install VisualAge COBOL,
VisualAge COBOL will reset these variables for COBOL usage.

If you install VisualAge C++ after VisualAge COBOL, uninstalling VisualAge C++
will not restore your COBOL values. You will need to reset the following
environment variables for IBM VisualAge COBOL, where c:\Program
Files\IBM\VACOBOL is the path where IBM VisualAge COBOL was installed:

Variable Value
IPF_PATH32 c:\Program Files\IBM\VACOBOL
SOMIR c:\Program Files\IBM\VACOBOL\SOM\ETC\SOM.IR;SOM.IR
SOMBASE c:\Program Files\IBM\VACOBOL\SOM
SC SC
SOMBINDINGS c:\Program Files\IBM\VACOBOL\SOM\BINDINGS
SOMDDIR c:\Program Files\IBM\VACOBOL\SOM\ETC\DSOM

If you uninstall IBM VisualAge COBOL, you may need to manually reset the SOM
variables for VisualAge C++ to their original settings, where c:\ibmcppw is the
path where IBM VisualAge C++ was installed:

Variable Value
IPF_PATH32 c:\ibmcppw
SC SC
SMBINDINGS c:\ibmcppw\BINDINGS
SOMBASE c:\ibmcppw
SOMDDIR c:\ibmcppw\SOM\ETC\DSOM

Using your own macros for the editor

Before you installed VisualAge COBOL, you may have had your own macros for
the language-sensitive editor, which the LPATH or LPATH2 environment variable
pointed to. If so, you need to append the contents of the LPATH or LPATH2
environment variable to the contents of the environment variable that VisualAge
COBOL created, COBLPATH4.

For example, suppose that before you installed VisualAge COBOL, LPATH or
LPATH2 contained d:\MYMACROS. During the installation of VisualAge COBOL,
the COBLPATH4 environment variable was set to e:\IBMCOBW\MACROS. To
make your macros available, you would update the COBLPATH4 environment
variable to be e:\IBMCOBW\MACROS;d:\MYMACROS.

28 Getting Started
 Using your own Interface Repository files
Similarly, before you installed VisualAge COBOL, you may have updated the
SOMIR environment variable to specify your own Interface Repository files. After
you install VisualAge COBOL, reset the SOMIR variable to point to your files.

Installing by using a response file

With a normal (nonsilent) installation, you provide the necessary input in the form
of responses to requests for information. With a silent installation, the response file
for InstallShield Silent contains the input and no messages are displayed. Instead, a
log file captures the installation information, including whether the installation
was successful.

A response file is a text file that contains information similar to what an end user
would enter as responses to requests for information when running a normal
installation. InstallShield Silent reads the necessary input from the response file at
run time. The format of a response file resembles that of an .ini file, but a response
file has the .iss extension.

You might want to use a response file when you have many workstations on
which to install the product and do not need to observe each install process.

To install VisualAge COBOL by using a response file, follow these steps:

1. Create a response file. You can have InstallShield create the response file for
you, or you can write the response file, perhaps using the response file
setup.iss, which is provided, as a template. To have InstallShield create the
response file for you, enter:
setup -r

As you do a normal installation, InstallShield records your installation choices

in setup.iss and then puts the file in the Windows folder (c:\WINNT or
c:\WINDOWS on most systems). If you have the system restarted at the end of
the installation when you record the response file, the silent installation will
also restart the system when it finishes. You may want to copy the response file
to a diskette or network drive to use it later.
2. Run the installation in silent mode using InstallShield Silent. Enter, for example:
d:\setup -s -f1a:\setup.iss -f2a:\vad3.log

The -s parameter requests a silent installation, the -f1 parameter gives the
location and name of the response file to use, and the -f2 parameter gives the
location and name of the log file to use.
3. Review the log file, especially the return values, to verify that the silent
installation succeeded.

RELATED REFERENCES
“Setup parameters for silent installation”
“Setup log file for silent installation” on page 30

Setup parameters for silent installation

You can pass setup parameters directly to the setup program (setup.exe) or put
them into a setup.ini file. If you use the parameters, observe these guidelines:
v Put a slash (/) or a dash (-) in front of each parameter.

Chapter 3. Installing on the workstation 29

 v Put a space between parameters but not inside a parameter. For example, the
following command is valid:
/s /f1a:\setup.iss

The following command is not valid:

/s/f1 a:\setup.iss
v When you use long path and file name expressions with parameters, enclose the
expressions in double quotation marks. These quotation marks tell the operating
system not to treat the spaces within the quotation marks as delimiters.
v You can use uppercase or lowercase letters for all of the parameters except -SMS.

The command-line parameters are:

Parameter Purpose Comments

-f1 To specify the location and name InstallShield Silent will read the
of the response file response file that you specify.
-f2 To change the location and name By default, setup.log is created and
of the log file that InstallShield stored in the same folder as setup.exe.
Silent creates
-m To cause InstallShield to generate a Do not include a path. The .mif file is
management information format always placed in the Windows folder. If
(.mif) file at the end of installation you do not specify a file name, the file
is called status.mif.
-r To cause the setup program to The response file is a record of the
generate a file (.iss) for silent installation input that you use as you
installation step through a normal installation. It is
stored in the Windows folder.
-s To have InstallShield Silent run a
silent installation
-SMS To prevent a network connection You can use this parameter when
and keep the setup program from installing from a Windows NT server
closing before the installation is over a network. SMS must be
complete uppercase.

RELATED TASKS
“Installing by using a response file” on page 29

RELATED REFERENCES
“Setup log file for silent installation”

Setup log file for silent installation

Setup.log is the default name for the log file that results from the silent installation.
Its default location is Disk1 in the same folder as setup.exe. You can specify a
different name and location for setup.log by using the -f1 and -f2 parameters with
the setup program..

Setup.log has three sections:

Section Name Identifies:

1 [InstallShield Silent] Version of InstallShield used in the silent
installation

File as a log file

30 Getting Started
Section Name Identifies:
2 [Application] Name and version of the installed
application

Company name
3 [ResponseResult] Result code indicating whether or not the
silent installation succeeded

InstallShield puts one of the following return values after the ResultCode keyname:

Value Meaning
0 Success
-1 General error
-2 The mode is not valid.
-3 The required data was not found in the setup.iss file.
-4 Not enough memory is available.
-5 The file does not exist.
-6 Cannot write to the response file.
-7 Cannot write to the log file.
-8 The path to the InstallShield Silent response file is not valid.
-9 The list type (string or number) is not valid.
-10 The data type is not valid.
-11 Unknown error during setup.
-12 The dialogs are out of order.
-51 Cannot create the specified folder.
-52 Cannot access the specified file or folder.
-53 The option selected is not valid.

RELATED TASKS
“Installing by using a response file” on page 29

RELATED REFERENCES
“Setup parameters for silent installation” on page 29

Chapter 3. Installing on the workstation 31

32 Getting Started
Chapter 4. Configuring your systems
Before you can start remote edit-compile-debug of host applications from your
workstation, you need to do these tasks:
v Make sure you have the appropriate software installed on the host and on your
workstation. Be sure that you have installed the MS Loopback Adapter (using
the Adapters page of the network properties on Windows NT).
v Have a system programmer or network administrator configure the
communication software (TCP/IP, IBM HTTP Server, foreign file system server,
and job monitor server) for your development environment. The remote
commands server is required only if you plan to issue TSO commands from the
workstation.
v Set up remote edit-compile-debug for the workstation by running the MVS
connections manager.

The remote edit-compile-debug component of VisualAge COBOL communicates

between the workstation and the host through the HTTP protocol. The IBM HTTP
Server (formerly Domino Go Webserver) runs under UNIX System Services
(formerly Open Edition) in OS/390. The server must be installed under the
hierarchical file system (HFS) of UNIX System Services and configured for the
remote capability of VisualAge COBOL. This server communicates with the foreign
file system server through the GoWebserver API (GWAPI).

The person installing and configuring the server is usually an OS/390 system
programmer familiar with OS/390 security features and with UNIX System

© Copyright IBM Corp. 1995, 2000 33

 Services. The person installing and configuring VisualAge COBOL on the
workstation (the COBOL administrator) need not be an OS/390 system
programmer but does need to coordinate with the OS/390 system programmer. For
the convenience of the system programmer, the instructions for installing and
configuring the parts that reside on OS/390 are in a program directory that comes
with the product.

RELATED CONCEPTS
Remote edit-compile-debug

RELATED TASKS
Installing and configuring the MS Loopback Adapter on WIndows NT“Installing
and configuring the MS Loopback Adapter on Windows NT” on page 23
Installing and configuring the MS Loopback Adapter on Windows 2000“Installing
and configuring the MS Loopback Adapter on Windows 2000” on page 24
“Configuring and connecting your workstation for remote ECD”

Configuring and connecting your workstation for remote ECD

Before configuring the connection to an MVS system, be sure of the following:
v You have installed the MS Loopback Adapter on your workstation. You will not
be able to connect to the MVS system unless you have installed this adapter.
v The system programmer has configured TCP/IP, IBM HTTP Server, foreign file
system server, job monitor server, and (if you plan to issue TSO commands from
the workstation) remote commands server.
v The system programmer has told you the port numbers for the IBM HTTP
Server (default 80) and job monitor server (default 6715) if these numbers were
changed during the configuring.
v You have your user ID and password for the MVS system where your source
code resides.

While you are configuring your workstation for remote ECD, you will select drive
letters that VisualAge COBOL will use to attach your host files. You can specify
more than one drive and more than one folder (directory) on a drive for a project.
For example, you might use one drive for your source files and another drive for
your test files. In a source folder, you might have different folders for your JCL
and your COBOL code.

To configure the connection to an MVS system, do the following steps:

1. Click Start -> Programs -> IBM VisualAge COBOL -> Tools - Remote Access
-> MVS Connections.
2. On the Host and User page, enter the TCP/IP name of your MVS system. After
you enter the system name and move to the next box, you will see that a
system short name, a nickname for your system, is provided for you. You can
either accept the default short name or specify your own. The short name can
be any combination of letters and numbers. Enter your user ID for the MVS
system.
If you want to define default data set properties for new data sets that you
create on MVS, click Data Set Properties and specify the information requested
in each field. Otherwise, click Next.

34 Getting Started
3. On the Data Transfer page, check whether the default code pages are correct.
Typically, you should not need to change the default local code page. The host
code page must match the code page used on your MVS system.
You can accept the drive selected or choose a drive letter to represent the
virtual directory on your Windows workstation that VA COBOL creates for
linking to the host. Click Next.

Chapter 4. Configuring your systems 35

 4. On the Ports page, check whether the port numbers of the IBM HTTP Server
(Web port) and job monitor server (job port) are correct. Normally, you would
not change the defaults. Click Finish.
5. In the Directory box in the Directory Properties window, enter the name
(probably the high-level qualifier) of the host directory path. A default directory
path, generated from the MVS user ID you specified earlier, is provided for
you. You can either accept this default directory path, or specify your own. Do
not use a PDS name for the path. For example, if you have a data set called
userid.MYSRC.COBOL, you can specify a path of either userid or
userid.MYSRC, but do not specify a path of userid.MYSRC.COBOL. Doing so
will result in unexpected behavior.
Select the type of data set (either text or binary) from the Transfer menu.
If you want to to define default data set properties for new data sets that you
create on MVS, click Data Set Properties. Otherwise, click Finish.

You have completed configuring one connection to your MVS system! In the MVS
Connections Manager window, the information for your MVS system connection

36 Getting Started
 should be displayed.

6. Check the information displayed and make sure you have entered everything
correctly. If you find a mistake, double-click the information you want to
change to open the Connection Properties window and make changes there.
You can add a directory to this drive by right-clicking on the drive and then
clicking Add Directory and filling in the information.
The mappings of local and host files in the lower right pane determine the file
extensions that PDS members will have on the workstation. To change these,
right-click an item and then click Properties. Or you can right-click a drive in
the top pane and then click Add Mapping.
When you have finished, click the Save changes icon at the far left of the tool
bar to save the configuration of your MVS connection.
7. You are now ready to establish a connection. Select the system connection that
you want to connect, and then click the Connect All icon. The status field
should change from Not Connected to Connected.

RELATED TASKS
Installing and configuring the MS Loopback Adapter“Installing and configuring
the MS Loopback Adapter on Windows NT” on page 23
Mapping MVS data sets
“Verifying your connection”
“Chapter 5. Creating an MVS project” on page 41

Verifying your connection

To verify that your communications configuration is working, do the following
steps:
1. In the MVS Connections Manager window, click the Connect all button on the
toolbar. If the MVS host is available, you will be prompted for a password.

Chapter 4. Configuring your systems 37

 2. Enter your password for the MVS host and the user ID that you specified in
the MVS connections manager. If the connection was successful, the Status
column in the MVS Connections Manager window changes to Connected.

If the connection was unsuccessful, you might see the following message:
The host mymvs.ibm.com is not responding.

Please check that the MVS system name is valid and the host is accessible to
TPC/IP.

This message means that your host TCP/IP name is not valid. Check that you have
entered the correct name.

You might see this message:

The following drives failed to connect: driveletter1, . . .

To find out why the drive failed to connect, you can check parts of the connection
as described below. If you find that something is wrong with the host connection
and you have narrowed the cause to a part on the host, contact your MVS system
programmer for help.

Checking the TCP/IP connection

1. In an MS DOS command window, enter this command to ping your MVS host
by name:
C:\>ping mymvs.ibm.com
2. Check the messages that you receive from the ping command for any errors. If
ping returns an error about an unknown host and the name is correct, your
TCP/IP configuration on the workstation is incorrect. If ping returns data from
the host, your TCP/IP connection is operating normally.

Checking the IBM HTTP Server connection

1. In the MS DOS window, enter:
C:\>net use f: \\ffssash\mvs1

Here f: is the drive letter that you specified in the Connections properties
setup, and mvs1 is the short name that you specified for your MVS host.
2. Check the messages that you receive from the net use command for any errors.
If the command fails, the problem could be that the MS Loopback Adapter is
not installed and configured correctly. Go through the installation and
configuration steps for the Loopback Adapter to make sure it is working
correctly. If the connection still does not work, the IBM HTTP Server might not
be started, or the foreign file system server might not be installed and running
on your host system.
3. If the connection to the host was successful, disconnect from the host by using
the Disconnect all button or by using the net use delete command:
C:\>net use f: /d

Checking whether the IBM HTTP Server has started

1. In a Web browser, enter the following Web address:
http://mvsipaddr:port/

Here mvsipaddr is the TCP/IP name of your MVS system, and port is the port
number of your Web server.
2. If prompted, fill in your TSO user ID and password.

38 Getting Started
3. If the server has started, you will see the Web page for the IBM HTTP Server.

Checking whether the foreign file system server is installed

1. In a Web browser, enter the following Web address:
http://mvsipaddr:port/FFSDS/

Here mvsipaddr is the TCP/IP name of your MVS system, and port is the port
number of your Web server. FFSDS must be uppercase.
2. If the server has been installed, you will see the Web page for the VisualAge
foreign file system server.

RELATED TASKS
Installing and configuring the MS Loopback Adapter“Installing and configuring
the MS Loopback Adapter on Windows NT” on page 23
“Configuring and connecting your workstation for remote ECD” on page 34

Chapter 4. Configuring your systems 39

40 Getting Started
Chapter 5. Creating an MVS project
Before creating an MVS project, be sure of the following:
v You have configured the connection to an MVS system, and you are connected
to that system.
v You know what drives you assigned to your MVS data sets when you
configured your connections.
v You know the names of the data sets that you will use in your MVS project.

To create an MVS project, do the following steps:

1. Click Start -> Programs -> IBM VisualAge COBOL -> IBM VisualAge
COBOL Projects.
2. In the COBOL Projects window, click the Create New Project tab.
3. Click MVS Project. Click Next. On the Create New Project page, you will enter
information to identify your project and where it will reside on the
workstation.
4. Enter an unqualified name for the project (such as myproject). After you enter
the project name and move to the next box, you will see that default names for
the target file and make file are provided for you. Either accept the default
names or specify your own. Click Next.

5. Enter Project Folder information. Click Add to specify a folder for your source
files, which already exist as data sets on MVS. Choose the drive and folder that

© Copyright IBM Corp. 1995, 2000 41

 you designated for the host files when you created the MVS connection. Filling
in the drive and folders for your project here lets the COBOL project
environment know about your project. To add more than one folder, press the
Ctrl key while you select the folders that you want to add.
Accept the default names for the working folder that will hold your generated
files and for the folder that will hold your project definition files. This
information is generated from the information that you specified when you
created your MVS connection. Click Next.

You are prompted to have the folder created. Click Yes.

6. Specify environment variables, or you can accept the default one. Click Finish.
A message confirms the creation of the project, and the IBM VisualAge COBOL
Project - myproject window opens. You have set up the project environment for
remote editing, compiling, and debugging!

42 Getting Started
RELATED TASKS
“Configuring and connecting your workstation for remote ECD” on page 34
Changing the source directories for your MVS project

Chapter 5. Creating an MVS project 43

44 Getting Started
Chapter 6. Creating your first VisualAge COBOL application
This section guides you through creating your first VisualAge COBOL application.
The steps you follow here teach you the basic principles that you use for further
applications.

Your first step in developing an application with VisualAge COBOL is to set up a

project. The VisualAge COBOL development paradigm centers around the concept
of a COBOL project, which is a container of your application files, such as COBOL
source files, copy files, listings, object code, and executable files. Projects are set up
to enable you to perform actions on those application files. The actions vary
depending on the type of file. For example, edit is an action appropriate for a
COBOL source file but not for an executable file.

With VisualAge COBOL, your can work with the following types of applications:
Non-GUI applications
Enables you to create applications using basic COBOL language features.
Visual Builder applications
Enables you to create applications with a graphical user interface (GUI).
Using a “construction from parts” paradigm, you create applications by
dropping parts onto a palette and then adding connections to define the
actions for those parts. For more complex applications, you then add user
code to complete the application.
Remote MVS applications
Using the remote edit-compile-debug component of VisualAge COBOL,
you can work with your host applications from the workstation, without
having to download the applications or data to the workstation.

The Hello Application you create in this chapter is a non-GUI application, which
contains a COBOL source file (a component) from which you build (compile and
link) the running COBOL program (a target). When you finish, you have an
application that displays a customized greeting.

A complete Hello Application is provided in the Guide to Samples. You can use
the Hello Application sample to get an idea of how your Hello Application will
run.

When you have finished coding your Hello Application, the application interface
will look like this:

© Copyright IBM Corp. 1995, 2000 45

 To create the Hello Application, complete the following steps:
1. Create a project.
2. Code the application.
3. Build the application.
4. Run the application.

RELATED CONCEPTS
“Creating a non-GUI project”
“Creating the application” on page 48
“Building the application” on page 49
“Running the application” on page 50

Creating a non-GUI project

VisualAge COBOL provides a project setup wizard in which you define the type of
project you want to create and provide other information needed to create the
project. Using the project setup wizard, you can create a new project, access
existing projects or define default settings that can apply to all projects you create.

To create a non-GUI project, do the following:

1. Click Start -> Programs -> IBM VisualAge COBOL -> IBM VisualAge
COBOL Projects.
2. In the COBOL Projects window, click the Create New Project tab.
3. Click Non-GUI Project. Click Next. On the Create New Project page, you will
enter information to identify your project and where it will reside on the
workstation.
4. Enter HELLOAPP for the project name. After you enter the project name and
move to the next box, you will see that default names for the target file and
make file are provided for you. Accept the defaults: HELLOAPP as the target
name, .EXE as the target type, and HELLOAPP.MAK as the make file name. Click
Next.
5. Enter Project Folder information. Leave clear the box for specifying the names
of folders for existing source files. The source files you create will be stored in
the same working folder as the generated files.

46 Getting Started
 Accept the default names for the working folder that will hold your generated
files and for the folder that will hold your project definition files. Click Next.
You are prompted to have the folder C:\IBMCOBW\Projects\HELLOAPP created.
Click Yes.
6. Specify environment variables, or you can accept the default one. Click Finish.
A message confirms the creation of the project. Click OK. The COBOL Projects
window opens, and a COBOL Projects folder is created on your desktop.

The COBOL Projects folder

The COBOL Projects folder contains two project files:
v HELLOAPP.IWP for holding general project information and settings
v HELLOAPP.IWO for holding the options settings for the actions that you can
invoke on files in your project

The .IWP and .IWO files must reside in the same folder, and they must have the
same file name. They do not need to reside in the same folder as the project source
files. You can open existing projects from the COBOL_Projects folder by
double-clicking the .IWP file for the project.

The IBM VisualAge COBOL Project window

The IBM VisualAge COBOL Project window includes the following items:
(1)System menu
Contains menu items for manipulating (minimizing, maximizing, or
closing) the window that contains your project.
(2)Project toolbar
Contains buttons for frequently used actions.
The left side of the project toolbar has buttons that let you clear, save, or
print the contents of the monitor window. It also has a button that opens
the Tasks help for COBOL projects.

Chapter 6. Creating your first VisualAge COBOL application 47

 The right-hand side of the project toolbar has buttons for launching
frequently used actions like build, debug, and run.
(3)Menu bar
Contains menu items to launch actions on projects and files, bring up the
settings notebook, set options, and link to the Information Center.
File contains actions to open or create another project, to close the project
view, and to exit the project. It also allows you to view or edit the Project
Settings notebook.
Edit allows you perform basic editing actions, such as copy and delete; it
also lets you select or deselect all the files in the project container.
View contains controls for opening different views of the project. It also
contains view options for the project toolbar and information area.
Actions lists all the actions available to the project. Actions on both
projects and files are also accessible from the pop-up menus.
Options includes a list of the actions for which you can change option
settings. When you select an action from this menu, the options dialog for
the action displays.
Help provides various entry points into the VisualAge COBOL online help
system.
(4)Filter
Enables you to select which files display in the project container. The list
box lists all the masks that are available to the project. To use more than
one filter, separate them with a semicolon.
(5)Container
Displays the project files and any subprojects.
(6)Project Monitor Command Window
Displays the progress of project builds.

Now that you have created your project, you can create the files you need for the
application.

RELATED TASKS
“Creating the application”

Creating the application

After you have created a new project, you have a set of actions available for the
files you create for your program. This section explains how to create COBOL
source files and enable the language-sensitive editing feature. If you are familiar
with these concepts, you can copy HELLOAPP.CBL from the
SAMPLES\HELLOAPP subdirectory where you installed VisualAge COBOL to the
directory where you stored your source files for this tutorial. Then skip this step
and continue with next step, “Building the application” on page 49.

To create the COBOL source file for the Hello Application project, do the following
steps:
1. In the IBM VisualAge COBOL Project - HELLOAPP window, click Actions ->
Edit a new file. The parsing editor opens with a default document titled
Editor - Untitled Document 1.
To enable the COBOL language-sensitive editing features:

48 Getting Started
 v Click Options -> Profiles -> Change profile.
v In the Change Profile window, click the arrow to display the list. Locate the
item cbl; you might have to scroll to find it. Click cbl to select it.
v Click OK. The COBOL language-sensitive editing features are enabled.
2. Enter the following source code:
Identification division.
Program-ID. Helloapp.

Data division.
Working-storage section.

01 Program-work-fields.
05 Input-name Pic x(30).
05 Output-name Pic x(37).

01 Program-flags.
05 Loop-flag Pic 9(01).
88 Loop-done Value 1.

Procedure division.

Initialize program-work-fields
Program-flags.

Perform until loop-done

Display “ ”
Display “Enter a name or Q to quit:”
Accept input-name
If function upper-case (input-name) = “Q”
Set loop-done to true
Else
Move spaces to output-name
Move “Hello, ” to output-name (1:7)
Move input-name to output-name (8:30)
Display output-name
End-if
End-perform.

Goback.
3. Click File -> Save to save the source code. Ensure that the Directory list shows
IBMCOBW/PROJECTS/HELLOAPP as the selected directory. Enter HELLOAPP.CBL in the
File Name field and click OK. Then click File -> Exit to close the COBOL
Editor.
4. Press F5 to refresh the IBM VisualAge COBOL Project - HELLOAPP window.
The HELLOAPP project now contains the source file HELLOAPP.CBL.

You are now ready to build the application.

RELATED TASKS
“Building the application”

Building the application

When you build your application, the target file that you specify is created. For
Hello Application, you have a single COBOL source object, which you build into a
running COBOL program.

From the toolbar, click , the Build Normal icon.

Chapter 6. Creating your first VisualAge COBOL application 49

 During the build, the target (an executable file titled HELLOAPP.EXE) is created from
the COBOL source file, and files generated as a result of the build appear in the
project container.

The progress of the build is displayed in the Project Monitor Command window.

If errors are detected during the build step, the monitor displays the return code
and compiler error messages. Scroll up to the message lines that include the drive,
path names, source file name (HELLOAPP.CBL), and the error message text.
Double-click a message line.

The COBOL editor opens, showing the line in the HELLOAPP.CBL source file where
the error occurred. Correct the error and save the file. Rebuild the file and check
the results in the monitor window.

Some linker error messages also contain drive, path, and file names. You can
double-click only compiler error messages to fix errors in the source program.

You are now ready to run the Hello Application.

RELATED TASKS
“Running the application”

Running the application

You can run your application from your Hello Application project. From the tool

bar, click , the Run icon.

A workstation window opens and runs your program, prompting you for a name.

50 Getting Started
Chapter 6. Creating your first VisualAge COBOL application 51
52 Getting Started
Chapter 7. Creating a simple Visual Builder application
This section introduces you to the Visual Builder where, from a Project
environment, you create a visual application using the Composition Editor, add
parts in a frame window, connect the parts, build the application, and run the
application. This section takes you through an example of how you use Visual
Builder to develop an application for creating and maintaining a simple to-do list.
Here is what the application will look like when it is finished.

A complete to-do list application is provided in Sample Projects (click Start ->
Programs -> IBM VisualAge COBOL -> Sample Projects). The TODOLIST sample
includes the date function, which you create when you expand your to-do list
application in “Adding and aligning new parts to display the date” on page 70.
The TODOLIST sample also includes additional connections, which are not
included in the to-do list application that you create in this section. You can use
the TODOLIST sample to get an idea of how your to-do list application will run.

Note: Visual Builder is not supported on Windows 95 or 98.

RELATED TASKS
“Creating a visual project” on page 54
“Starting Visual Builder” on page 55
“Placing parts in the application window” on page 57
Resizing and aligning parts“Resizing and aligning the parts” on page 59
“Connecting the parts” on page 62
“Generating the COBOL code for your application” on page 65
“Building the application” on page 65
“Running the application” on page 66
“Exiting the Composition Editor and Visual Builder” on page 66

© Copyright IBM Corp. 1995, 2000 53

Creating a visual project
For this tutorial, we will organize the files in a Visual Builder project. To create a
project, do the following steps:
1. Click Start -> Programs -> IBM VisualAge COBOL -> IBM VisualAge
COBOL Projects.
2. In the COBOL Projects window, click the Create New Project tab.
3. Click Visual Builder Project. Click Next. On the Create New Project page, you
will enter information to identify your project and where it will reside on the
workstation.
4. Enter TODOLIST for the project name. After you enter the project name and
move to the next box, you will see that default names for the target file and
make file are provided for you. Accept the defaults: TODOLIST as the target file
name, .EXE as the target type, and MAKEFILE.MAK as the make file name. Click
Next.
5. Enter Project Folder information. Leave clear the box for specifying the names
of folders for existing source files. The source files you create will be stored in
the same working folder as the generated files.
Accept the default names for the working folder that will hold your generated
files and for the folder that will hold your project definition files. Click Next.
You are prompted to have the folder C:\IBMCOBW\Projects\TODOLIST created.
Click Yes.
6. Specify help format. Click RTF as the type of help you will create for your
visual application. Click Next.
7. Specify environment variables, or you can accept the default one. Click Finish.
A message confirms the creation of the project. Click OK. The IBM VisualAge
COBOL Project - TODOLIST window opens, and a COBOL Projects folder is
created on your desktop.

54 Getting Started
 IBM VisualAge COBOL Project - TODOLIST window

RELATED TASKS
“Starting Visual Builder”

Starting Visual Builder

In the IBM VisualAge COBOL Project - TODOLIST window, you should see the
project you created: C:\IBMCOBW\Projects\TODOLIST. Your TODOLIST project
contains the following files:
v READ.ME - A file explaining the basics for creating a visual project.
v TODOLIST.VCB - The TODOLIST visual part.
v VBHELP.IWO/VBHELP.IWP - Subproject files, which contain two skeleton help
source files: VBHELP.RTF and VBHELP.HPJ. The wizard creates the HELPDIR
subdirectory under VISUAL\TODOLIST for the help source files.

To start the Visual Builder, double-click the icon for TODOLIST.VCB in the IBM
VisualAge COBOL Project - TODOLIST window. The Visual Builder window and
the Composition Editor window open.

Chapter 7. Creating a simple Visual Builder application 55

 The Composition Editor window

Note the following in the Composition Editor window:

(1)Toolbar
Enables you to invoke frequently used actions by clicking the icon.
(2)Parts palette
The left column of the parts palette contains the categories of parts (such
as buttons and list boxes). The right column contains the parts available for
the category selected.
Each category contains a collection of similar or related parts. You drop
parts on the free-form surface or on top of other parts, like a canvas (which
is a component of your visual part).
(3)Free-form surface
The area on which you place parts, such as a canvas or nonvisual parts.
(4)Visual part
A frame window with a canvas and two push buttons. As you create your
applications, you will add more parts (such as push buttons and static text)
to this canvas.
Close push button — When you run the application, clicking Close closes

56 Getting Started
 the window. It has no effect on the Composition Editor. The solid green
arrow pointing to the to-do list frame is the completed connection that
closes the to-do list application when a user clicks Close. You learn how to
connect parts later in this tutorial.
Help push button — When you run the application, clicking Help causes
a help window to open for the to-do list application.
The help file (VBHELP.HLP) is created from the supplied help source files
(VBHELP.RTF and VBHELP.HPJ) when you build the to-do list application.
The settings of the Help push button determine which help panel displays
based on a specific resource ID. For example, double-click the Help push
button to open the settings notebook. On the Control page, Help panel id
specifies 100 as the footnote ID for the Help push button. If you edit
VBHelp.hpj, you see that footnote 100 is included for the Main Window
Help panel.

The TODOLIST part also contains a subpart titled CHelpWindow2, which is outside
of the TODOLIST frame window on the free-form surface. This subpart represents
the actual help window and it is where you define the help libraries. (If you
double-click CHelpWindow2, the settings notebook opens. The default help library
is VBHELP.HLP.)

Before you place any parts in the frame window, first edit the title.

Changing the title of the to-do list frame window

The visual part that you just created is a CFrameWindow part, titled Window Title.
This will be the to-do list application title bar. Change the title of this window by
doing the following:
1. Position the cursor over the title bar.
2. Press the ALT key and click with the left mouse button.
3. Enter a new title (such as My To-Do List)
4. Click anywhere on the to-do list canvas.

You are now ready to place parts (such as push buttons and static text) in the
application window.

RELATED TASKS
“Placing parts in the application window”

Placing parts in the application window

To build the TODOLIST application, you need to add the following parts:
Static text
The labels for To-Do Item and To-Do List.
Entry field
Where you will type your to-do items when you run the application.
List box
Where the to-do items is listed (your to-do list), when you run the
application.
Push buttons
To add or remove items from the to-do list.

Chapter 7. Creating a simple Visual Builder application 57

 To select parts to place in the application window, you:
v Select the parts category from the left-hand column of the parts palette.
v Select the part from the right-hand column of the parts palette.
v Move the mouse pointer to the free-form surface and click the spot where you
want the part.
You do not need to drag the part from the parts palette to the free-form surface.
You just point and click.

Placing a static text part in the window

The to-do list application needs two static text fields. Follow these steps to place
the first static text part in the to-do list application window:

1. Click (Data entry category icon) on the left-hand side of the parts
palette.

2. Click (COBOL Text StaticText icon) on the right-hand side of the

parts palette. When you move the mouse pointer over the free-form surface,
you see that it has changed to crosshairs. This means the mouse pointer is
loaded with the COBOL Text StaticText part.
3. Place the crosshairs in the upper-left corner of the client area of the to-do list
application window and click the left mouse button. A static text part is placed
in the window.
4. Change the name of the static text part to: To-Do Item:
Use the same method for changing text that you learned when you changed the
title of the to-do list frame window.

Placing an entry field in the window

The to-do list application needs an entry field so the user can type in new to-do
items.

1. Click (COBOL Text Entry Field icon) on the right-hand side of the
parts palette. (This icon is also in the Data entry category set of icons.)
2. Place the crosshairs beneath the first static text, indented a few spaces to the
right, and click the left mouse button. The entry field is placed beneath the
static text.

Placing another static text in the window

Follow these steps to position and modify the second static text:
1. Place the second static text in the to-do list frame window under the entry
field, but aligned with the first static text. Use the same method for placing the
static text that you learned when you placed the first static text in the to-do list
frame window.
2. Change the name of the static text to: To-Do List: Use the same method for
changing text that you learned when you changed the title of the to-do list
application frame window.

58 Getting Started
 Placing a list box in the window
Because the to-do list will consist of a list of text strings, you want to store that list
in a COBOL ListBox. To place a list box in the to-do list frame window:

1. Click (Lists category icon) on the left-hand side of the parts palette.

2. Click (COBOL ListBox icon) on the right-hand side of the parts

palette.
3. Place the crosshairs below the second static text, aligned with the entry field,
and click the left mouse button. The list box is placed beneath the second static
text.

Placing the push buttons in the window

The to-do list application needs two additional push buttons, one for adding items
to the list and one for removing items from the list. To place two push buttons in
the frame window:

1. Click (Buttons category icon) on the left-hand side of the parts

palette.

2. Click (COBOL PushButton icon) on the right-hand side of the parts

palette.
3. Place the crosshairs above the Help push button, and click the left mouse
button. (Leave a bit of space; we will move the Close push button above the
Help push button in the next section.) The first push button is placed in the
window.
4. Change the name of the new push button to Remove. Also, to help identify
subparts after you begin connecting parts, rename the subpart to removepb.
Double-click the Remove push button to display the settings notebook. On the
General page, change the subpart name to removepb and change the label to
Remove. Click OK.
5. Click the COBOL PushButton icon again.
6. Place the crosshairs above the Remove push button. Click the left mouse
button. The second push button is placed in the window.
7. Change the name of the push button to Add and the subpart name to addpb.

Note: If you place the push buttons slightly out of alignment with the existing push
buttons, that’s OK. We’ll align and size the push buttons in the next step.

RELATED TASKS
Resizing and aligning parts“Resizing and aligning the parts”

Resizing and aligning the parts

Now that you have placed all of the parts you need in the To-Do List window, you
can resize and align them. When you have finished, your frame window should
look like this:

Chapter 7. Creating a simple Visual Builder application 59

 Dragging and dropping parts in the frame window
Before you align the parts, you might want to drag and drop some of them to put
them closer to each other. For example, we want to move the Close push button
above the Help push button to align it vertically with the other push buttons.
Follow these steps to drag and drop the parts in the application window:

Note: The following instructions are written for dragging and dropping multiple parts
simultaneously. If you want to drag and drop just one part at a time, select the
part and continue with Step 3.

1. Select the first part you want to drag.

2. While holding down the Shift key, select a second part. The selection handles
on the first part become outlined, and black selection handles appear on the
four corners of the second part. This means both parts are selected, but the
second part is the anchor part. Therefore, any sizing actions performed using
the tool bar cause the first part to match the anchor part for the sizing action
selected.
3. Move the mouse pointer over one of the parts that you selected to drag.
4. Press and hold the left mouse button, and move the mouse cursor. Visual
Builder displays an outline of the parts that you are dragging.
5. Move the outline to the place where you want to drop the parts, and release
the mouse button. The parts are moved to their new location.

Resizing the frame window (optional)

At this point, the parts in the frame window might be closer to the left window
border than to the right window border (depending on where you have placed the
parts). Follow these steps to resize the frame window:
1. Select the application window by clicking the left mouse button on the title bar.
2. Move the mouse pointer over the selection handle on the lower-right corner of
the frame window.
3. Press and hold the left mouse button.
4. Resize the frame window by dragging the mouse pointer toward the left until
the right border of the frame window is approximately the same distance from
the entry field and list box as the left border is.

To size the frame window in only one direction, either horizontally or vertically,
hold down the Ctrl key while dragging the mouse pointer.

Matching the width of the list box to the width of the entry
field
Follow these steps to match the width of the list box to the width of the entry
field:
1. Using the multiple selection technique you learned in Dragging and dropping
parts in the frame window, select the list box and then the entry field, making the
entry field the anchor part. (The last part you select becomes the anchor part.)

60 Getting Started
 2. Click (Match Width tool icon) on the toolbar. The width of the list box
changes to match that of the entry field.

Sizing and aligning the push buttons

After you change the text for each push button, the push buttons have different
widths and heights, and are not aligned.

If you have not already done so, move the Close push button above the Help push
button.

Using the techniques you learned in the preceding steps, select all four push
buttons, using the Remove push button as the anchor part.

v Match the width of the push buttons by clicking (Match Width tool
icon).
While all four push buttons are still selected, match their height and align them
in the frame window.

v To match the height of the push buttons, click (Match Height tool
icon).

v To align the push buttons, click (Align Left tool icon).

v To space the push buttons evenly in the frame window, click

(Distribute Vertically tool icon).

Aligning the static text so their left edges are even

The two static text parts need to be aligned evenly. Follow these steps to align
them:
1. Select both static text parts (making either one the anchor part). Use the
multiple part selection technique you learned previously.

2. Click (Align Left tool icon) on the toolbar. The first static text part is
aligned with the second static text part.

Your To-Do List window should now look like the one shown below.

Chapter 7. Creating a simple Visual Builder application 61

 RELATED TASKS
Connecting the parts

Connecting the parts

The next step in developing your to-do list application is to code the logic behind
the parts. The COBOL program behind your to-do list application follows the
event-driven programming model.

An event-driven program runs segments of logic in response to events. It has entry

and exit points that correspond to many events that can happen with respect to the
program. When you run an event-driven program, all logic in your application
waits for certain events to happen, such as when a user clicks the Add push
button. Once a selected event occurs, only the logic for that event is performed;
then the application waits for the next event. (With procedural programming, the
program has one entry point of entry and exit. The program follows each step in
the program logic sequentially until it reaches the end of the logic.)

The Visual Builder helps you code the event logic. Each part you place on your
to-do list canvas has a connections menu, from which you select the event to
which your logic will respond.

When connecting parts, you follow these basic steps:

1. Select the part and right-click to display the connections menu.
2. Select the event that triggers an action on that part.
3. Select the part affected when that event occurs.
4. Select the action to occur.

For the to-do list, you need to connect the push buttons to the list box and entry
field. You add connections that will move the text that a user types in the To-Do
Item entry field to the end of the To-Do List list box when the user clicks the Add
push button. You will also add connections to remove one item from the To-Do
List list box when the user clicks the Remove push button.

62 Getting Started
Connecting the Add push button to the list box
The connection between the Add push button and the list box provides the
information your application needs to add items to the list box.
1. With the mouse pointer over the Add push button, click the right mouse
button. A pop-up menu displays.
2. Click Connect -> press. This action means you want something to happen
whenever a user clicks this push button. The mouse pointer changes to look
like a spider, indicating that it is ready for you to select another part.
3. Move the mouse pointer to the list box and click the right mouse button.
4. Click addItemEnd. This action means you want new items to be added to the
end of the to-do list whenever a user clicks the Add push button. Here is what
the connection looks like:

The line connecting the Add push button to the list box is dark green. It points
from the push button to the list box, showing that the event that occurs when the
user clicks the push button causes the list box to perform an action.
The dashed line means the connection is incomplete. The connection is supposed
to add something to the list box when the Add push button is clicked, but you
have not yet supplied what needs to be added. You will do that in the next step.
5. Move the mouse pointer to the dashed connection line between the Add push
button and the list box. Right-click.
6. Click Connect -> Item.
7. Move the mouse pointer over the entry field, and right-click.
8. Click contents. This action contents means you want to move the text that a
user types in the entry field to the Item parameter of addItemEnd. This text
string is added to the end of the to-do list whenever addItemEnd is called,
which occurs whenever the Add push button is clicked. Here is what the
completed connection looks like:

Chapter 7. Creating a simple Visual Builder application 63

 The completed connections indicate that the entry field contains the data to be
added to the end of the list box when the user clicks the Add push button.
The line connecting the entry field to the connection between the Add push
button and the list box is violet. This is the parameter connection. The open
circle end indicates that the contents attribute of the entry field is the source
for the parameter to the addItemEnd action.
The solid circle touches the connection line between the Add push button and
list box. The Item parameter of the addItemEnd action is the target of the
connection. When the Item parameter needs a value, which occurs when a user
clicks the Add button, the connection invokes the get member function of the
contents attribute of the entry field. The value of that attribute (the text in the
entry field) is returned and moved to the Item parameter, and the addItemEnd
action puts the text string in the list box.
Notice that both of the connection lines are solid. This means the connection
between the Add push button and the list box now has the information it
needs to perform its function, so the connection is complete.

Connecting the Remove push button to the list box

The connection between the Remove push button and the list box programs your
application to remove items from the list box.
1. Right-click the Remove push button.
2. Click Connect -> Press.
3. Right click the list box.
4. Click removeOne. This action means you want your application to remove one
item in the to-do list whenever a user clicks the Remove push button. Once
again, the connection is incomplete.
5. Move the mouse pointer to the connection between the Remove push button
and the list box, and right-click.
6. Click Connect -> itemIndex.
7. Right click the list box.
8. Click firstSelected. This action means you want to move the index of the first
selected item in the list box to the ItemIndex parameter of the removeOne action.

64 Getting Started
 The removeOne action uses this index to determine which item to remove
whenever the Remove push button is clicked.
Making this connection completes your application. It should now look like
this:

Now that you have made all of the connections, the next step is to generate your
COBOL source code.

RELATED TASKS
“Generating the COBOL code for your application”

Generating the COBOL code for your application

Before you can build your application, you must first generate source code and
build files.
1. To generate the COBOL source code for your visual part, select File -> Save
and generate -> Part Source.
Important: Visual Builder generates several files in the working directory
(VISUAL\TODOLIST). Do not edit or move these files; they are used by Visual
Builder and your project.
2. To generate the build file, select File -> Save and generate -> Build files.
You have now generated the COBOL code for your application. The next step is
to build the application.

RELATED TASKS
“Building the application”

Building the application

Building your application consists of compiling and linking it. You will build the
application from your Visual Builder project that you created in the first step:
1. In your project, press F5 to refresh it.

2. From the toolbar, click , the Build Normal icon.

Chapter 7. Creating a simple Visual Builder application 65

 Subprojects are built first, in this case VBHELP, which generates its make files
in the HELPDIR subdirectory under VISUAL\TODOLIST. Then, the main project
(TODOLIST) is built. The build action generates an executable, binary resource,
several object files, and some additional temporary files.
3. Close the Editor Project Monitor window by selecting File -> Close.

Now you can run your application.

RELATED TASKS
“Running the application”

Running the application

To run your application from your Visual Builder project, from the toolbar, click

, the Run icon.

When your application is running, experiment with it to make sure it works as

designed. You will notice that when you type text in the To-Do Item field and
click Add, the text is added to the To-Do Listlist. However, the text remains in the
entry field. You will learn how to clear the entry field, and enable and disable the
Add push button in Expanding the simple Visual Builder application.

When you run the application, the list box might blend into the white background
of the To-Do List canvas. To see the list box, you can change the color of the
background in the Composition Editor:
1. Double-click the To-Do List canvas.
2. Click the Color notebook page.
3. Click Color values arrow.
4. Select a color.
5. Click OK.

After making this change, you need to regenerate the part source, build, and run
your application.

RELATED TASKS
“Exiting the Composition Editor and Visual Builder”

Exiting the Composition Editor and Visual Builder

You have created a simple Visual Builder application!

If you want to expand the to-do list application, continue to the next tutorial. Do
not close the Visual Builder or Composition Editor.

If you want to continue at another time, exit the Visual Builder. To exit, click File
-> Exit.

66 Getting Started
Chapter 8. Expanding the simple Visual Builder application
This section explains how to expand the to-do list application, which you created
in the previous section, to include user-supplied code contained in a nonvisual
part. You will create a nonvisual part contained in the TODOLIST part. You will
use the Part Interface Editor and System Interface Editor to generate feature code
(skeleton COBOL code) in which you will add code (using Code Assistant) that
will generate the current date in the to-do list application.

You will also add connections that will make the Add push button available (or
unavailable), based on the content in the To-Do Item entry field. Here is what the
application looks like when it is finished.

RELATED TASKS
“Opening the TODOLIST part” on page 68
“Enabling the Add push button” on page 68
“Adding and aligning new parts to display the date” on page 70
“Creating a nonvisual part” on page 71
“Defining features” on page 71
“Defining your system interface” on page 72
“Generating your code” on page 73
Updating the feature source“Updating feature source” on page 73
“Connecting the parts” on page 75
“Generating the COBOL code for your application” on page 76
“Building the application” on page 77
Running the application
Exiting Visual Builder“Exiting the Visual Builder” on page 77

© Copyright IBM Corp. 1995, 2000 67

Opening the TODOLIST part
If you are continuing with the to-do list application from “Chapter 7. Creating a
simple Visual Builder application” on page 53, skip this step. If not, open the
TODOLIST part:
1. Double-click the COBOL_Projects folder on your desktop. The TODOLIST -
Icon View window opens. This is your TODOLIST project.
2. Double-click the icon forTODOLIST.VCB in the project view. The Visual Builder
and the Composition Editor with your TODOLIST part open.

Now you are ready to continue with the to-do list application.

RELATED TASKS
“Enabling the Add push button”

Enabling the Add push button

To fine tune the to-do list application, you will probably want to make the Add
push button unavailable, depending on whether text is entered in the To-Do Item
entry field. You can clear the entry field of the To-Do Item after the user clicks the
Add push button. You need to do the following:
1. Make the Add push button unavailable (because, initially, the text entry field is
blank).
2. Make the Add push button available after text is entered into the entry field.
3. Clear the entry field after the Add push button is clicked.
4. Make the Add push button unavailable after the Add push button is clicked.

Notice that steps 3 and 4 are driven by the same event (clicking the Add push
button). When you have multiple actions occurring as a result of a single event,
you must code the connections in the same sequence as the actions occur.

Making the Add push button unavailable

To disable the Add push button, you need to do the following:
1. Double-click the Add push button.
2. Click the Control notebook tab.
3. On the Control notebook page, select the enable check box to remove the check
mark. (The push button is available (checked) by default.)
4. Click OK.

Making the Add push button available when text is entered in

the entry field
To enable the Add push button after you enter an item in the To-Do Item entry
field, you need to add a connection between the entry field and the Add push
button. Do the following:
1. Right-click the entry field.
2. Click Connect -> All Features.
3. In the Event column, click change.
4. Click OK
5. Left-click the Add push button.

68 Getting Started
 6. Click enable. This action means that when something is changed in the entry
field (for example, typing text), the Add push button is available.

Removing the entry field text

After you enter a to-do item in the entry field and click the Add push button, you
should clear the text from the entry field. Do the following:
1. Right-click the Add push button.
2. Click Connect -> press.
3. Left-click the entry field.
4. Click Contents. A dashed line shows the connection between the Add push
button and the entry field.
5. Double-click the dashed connection line. The Event-to-Action Connection -
Setting dialog opens.
6. Click the Set parameters button. The Constant Parameter Value Settings dialog
opens, containing an entry for the Contents parameter.
7. Click in the Value column next to the Contents parameter and then enter a
blank space. (This will “empty” the entry field when the Add push button is
clicked.)
8. Click OK to close the Constant Parameter Value Settings dialog.
9. Click OK to close Event-to-Action dialog.

Making the Add push button unavailable

Again you need to disable the Add push button, after adding the to-do item to the
to-do list. Do the following:
1. Right-click the Add push button.
2. Click Connect -> press.
3. Left-click the Add push button.
4. Click Disable.

Now the Add push button will not be available after the user clicks on it.

The connections so far look like this:

Chapter 8. Expanding the simple Visual Builder application 69

 RELATED TASKS
“Adding and aligning new parts to display the date”

Adding and aligning new parts to display the date

To display the current date, you will need to add the following parts in the frame
window:
v A push button, labeled Date
v Static text for the Date label.
v Static text where the application will display the date

In the TODOLIST part, add the following in the frame window:

1. Add a static text field to the top of the window and change the text to Date.
2. Add another static text field to the right of the Date field. Double-click the field
to display the settings notebook. On the General page, remove CStaticText4
from the Text field and change the Limit field value to 16. (The application will
display the date into this blank static text field.)
Click OK. Selection handles show the location of the blank static text field.
(You might want to move the blank static text field closer to the Date static
text.)
3. Align the two text fields using the Align Top icon.
4. Align the Date static text field with the To-Do Item static text field.
5. Add a push button above the Add push button and change the text to Date.
You probably need to move the existing push buttons to make room for the
Date push button.
6. Click all five buttons, using Remove as the anchor part. Using the toolbar
icons, match their height and width, align them, and then distribute them
vertically in the frame window.

When you have finished, your frame window should look like this:

70 Getting Started
 You have added and aligned the new parts. Before you can connect them, you
need to create a nonvisual part that will define an action to get the date.

RELATED TASKS
“Creating a nonvisual part”

Creating a nonvisual part

You need to add data processing to your application. To perform data processing,
you should use a nonvisual part, in which you will add code to generate the
system date. After creating a nonvisual part and updating code generated by the
Visual Builder, you will connect the nonvisual part to the main TODOLIST visual
part.

To create a nonvisual part, do the following steps:

1. From the main Visual Builder window (Visual Builder - TODOLIST), click Part
-> New.
2. In the Part - New window, enter theDate as the class name.
3. Click the Part type arrow, and select Nonvisual part.
4. Click Open. The Part Interface Editor opens for the nonvisual part theDate.

The Part Interface Editor is the default editor when you work with a nonvisual
part.

RELATED TASKS
“Defining features”

Defining features
To define a feature (an attribute, action, or event) for your part, you use the Part
Interface Editor. For additional details on the Part Interface Editor, see the Visual
Builder User’s Guide.

Chapter 8. Expanding the simple Visual Builder application 71

 Attribute Page
On the Attribute page of the Part Interface Editor, you will define a data
item that has a set and get method. Do the following:
1. Enter Today in the Attribute Name field.
2. Click the Attribute type arrow. Scroll down and click VarLengthString,
which is the data type that the static text field uses and where you will
connect the date data.
3. Click Defaults. The Visual Builder displays the default set and get
methods, which are the full method definition used in the generated
feature code. The default Event identification is also displayed.
4. Click Add to add Today as an attribute of the nonvisual part theDate.
Visual Builder creates the getToday and setToday methods.
Action Page
On the Action page you will define a method that determines the date
from the system, formats it, and sets the value of the attribute Today Do
the following:
1. Enter setDate in the Action name field.
2. Click Defaults.
3. Click Add.
Preferred Page
The Preferred page allows you to specify which items are displayed on the
menu when the user makes connections.
1. Under Actions, select setDate and click Add. The setDate action is
added to the Preferred Features list.
2. Under Attributes, select Today and click Add. The Today attribute is
added to the Preferred Features list.

Now you need to define the files that will contain the code for this action (and
other features) and will be included when you build the to-do-list application.

RELATED TASKS
“Defining your system interface”

Defining your system interface

Feature source is code that Visual Builder generates based on specifications in the
Part Interface Editor and System Interface Editor. The first step in generating
feature source is to define the file names for the feature code using the System
Interface Editor.

To open the System Interface Editor, click (System Interface Editor

icon) at the lower-right corner of the Part Interface Editor.

To define user files, do the following:

1. Click the Generation Options notebook tab.
2. Select User declaration file. Visual Builder enters theDate.cpv.
3. Select User code file. Visual Builder enters theDate.cbv

The Part file specification contains the path location of the theDate part.

72 Getting Started
 RELATED TASKS
“Generating your code”

Generating your code

Now you need to generate the code for your nonvisual part. You need to generate
both the feature source, which you will update with your own code, and the part
source.

Generating the feature source

To generate the feature source, from the System Interface Editor:
1. Click File -> Save and generate -> Feature source. The theDate - Generate
feature source code window opens.
2. Click Generate All. An information message opens saying the feature code
generation is complete. Click OK.
Visual Builder generates the following files:
v theDate.cbv - COBOL feature code source file
v theDate.cpv - COBOL copy file

Any subsequent generations produce feature code that is appended to the

selected features. Thus, when generating feature code for other methods you
define, use Generate selected to avoid appending duplicate feature code to
existing files.
3. Close the System Interface Editor for the theDate part.

Generating the part source

To generate part source, click File -> Save and generate -> Part source.

RELATED TASKS
“Updating feature source”

Updating feature source

When you generated the feature source in the previous step, Visual Builder created
a skeleton COBOL file for the theDate part based on the information you included
in the Part Interface Editor and System Interface Editor. To generate the system
date, you need to add some code to the LOCAL-STORAGE SECTION and PROCEDURE
DIVISION of the setDate method in the theDate.cbv file. You can use the Code
Assistant tool to edit the file.
1. From the main Visual Builder window (Visual Builder - TODOLIST), select
theDate in the Nonvisual Parts list.
2. Click Part -> Code Assistant. The Code Assistant window opens.
3. Expand the setDate method in the left-hand pane of the Code Assistant
window. The setDate method displays in the code panel of the window.
4. Expand the DATA DIVISION, and add the following code to the LOCAL-STORAGE
SECTION of the setDate method:
01 tempdate PIC X(8).
01 sep PIC X VALUE “-”.
01 temp2 PIC X(10).
01 Tempday.
03 Tempday-Length PIC 9(9) COMP-5.

Chapter 8. Expanding the simple Visual Builder application 73

 03 Tempday-String.
05 Tempday-Chars PIC X
OCCURS 1 TO 255 TIMES
DEPENDING ON Tempday-Length.

After you enter your code, the setDate method will look like this.

5. Scroll down a bit and add the following code to the PROCEDURE DIVISION of the
setDate method:
Move function current-date(1:8) to tempdate.
String tempdate(5:2) sep tempdate(7:2) sep tempdate(1:4)
delimited by spaces into temp2.
Move 10 To Tempday-Length.
Move Temp2 To Tempday-String.
Invoke self “setToday” using Tempday.
6. Save the file and close the Code Assistant window. Now you are ready to use
the part.

Optionally, you can copy thedate.cbv and thedate.cpv from the

SAMPLES\TODOLIST directory where you installed VisualAge COBOL to the
VISUAL\TODOLIST directory you created for this tutorial.

RELATED TASKS
“Connecting the parts” on page 75

74 Getting Started
Connecting the parts
In the Composition Editor for the TODOLIST visual part, you need to add the
nonvisual part to the TODOLIST free-form surface and connect the Date push
button to the blank static text field.

Adding the Date nonvisual part

To add the nonvisual part to the TODOLIST:
1. From the TODOLIST Composition Editor, click Options -> Add part.
2. In the Add Part window, click the Part Class arrow., and select theDate.
3. Click OK.
4. Click anywhere on the free-form surface. The nonvisual object theDate2 is
added to the main TODOLIST visual part. Now, when the TODOLIST part is
instantiated, it creates the instance theDate2 of the theDate part.

Connecting the nonvisual part to the main part

You now need to connect the nonvisual part to the main TODOLIST part.
1. Right-click the title bar (To-Do List Application) of the TODOLIST part.
2. Click Connect->Visible.
3. Right-click the nonvisual object theDate2. A pop-up menu shows the methods
you added to the Preferred Features list in the Part Interface Editor.
4. Click the setDate method. A solid line connects the main TODOLIST part with
the theDate2 nonvisual object.

Selecting the setDate method indicates that when the to-do-list application is run,
the current date is calculated using the setDate method and stored in the attribute,
Today.

Connecting the Date push button to the blank static text field
1. Connect the press event of the Date button to the label action of the blank
static text field.
2. Connect the contents parameter of that connection to the Today attribute of the
theDate part.

Selecting the Today attribute means that you want to pass the system date, as
returned by the getToday method to the contents parameter of the label action.
The date is displayed in the static text field whenever the getToday action is called,
which occurs whenever the Date push button is clicked.

The completed connection looks like this. (Your connection lines might be slightly
different.)

Chapter 8. Expanding the simple Visual Builder application 75

 The connection between the Date push button and blank static text field is green.
The connection between the theDate2 object and this green line is violet. The
hollow circle leads to the theDate object, showing that a feature of the theDate
nonvisual part (the attribute Today) is the source of the connection. The solid circle
leads to the connection line, indicating that the contents parameter is the target of
the connection. (You can verify this by clicking the connections. The features
connected appear in the information area of the Composition Editor.)

When you click the Date push button, the application calls the getToday method in
the nonvisual part and passes the string, returned as a parameter, to set the label
of the static text field. When the contents parameter needs a value, it invokes the
getToday method of theDate2, which returns Today. The value is passed as a
parameter to the label action of the static text field. The label action then displays
the current date in the static text field.

Now that you have made the connections, you need to generate the COBOL code.

RELATED TASKS
“Generating the COBOL code for your application”

Generating the COBOL code for your application

To get your application ready to build, do these steps:
1. Generate the COBOL source code for your visual part by clicking File -> Save
and generate -> Part source.
2. Generate the make file by clicking File -> Save and generate -> Build files.

RELATED TASKS
“Building the application” on page 77

76 Getting Started
Building the application

From the toolbar, click , the Build Normal icon.

You have now built your application. The next step is to run your application.

Typos or syntax errors in the feature source will cause compilation errors.

RELATED CONCEPTS
Running the application

Running the application

From the toolbar, click , the Run icon.

When your application is running, experiment with it to make sure it works as

designed.

Remember to use the Add button to add to-do items to your to-do list. Because the
initial focus is on the Close button, if you press the Enter key, the to-do list
application will close.

RELATED TASKS
Exiting Visual Builder“Exiting the Visual Builder”

Exiting the Visual Builder

To exit the Visual Builder, close the following windows (if they are still open):
v Visual Builder (Visual Builder - TODOLIST)
v TODOLIST project (TODOLIST - Icon view)

Chapter 8. Expanding the simple Visual Builder application 77

78 Getting Started
Chapter 9. Product support
IBM provides product support, consulting services, and education for using
VisualAge COBOL and other IBM COBOL family products.

RELATED TASKS
“Getting product support”
“Getting consulting services” on page 80
“Getting education and training” on page 80

Getting product support

There are several ways for you to get product support for VisualAge COBOL:
CompuServe, mail, fixes, the Internet, FAX, and phone support.

CompuServe
If you have access to CompuServe, you can enter your comments about COBOL.
At the ! command prompt enter, GO IBMLANG. Place your messages or comments
regarding COBOL in “Section 11, COBOL Language”. Note that if you want a
guaranteed response to a problem, call 1-800-237-5511.

If you want to e-mail a Defect Report Form through CompuServe, you can find the
form in the Library area. To submit, send it to the Personal Systems Support
Family at [email protected].

For CompuServe membership information, call 1-800-848-8199 and request

Representative 239.

Fixes
You can access fixes from the following sources.
v Call 1-800-237-5511 to request packaged fixes in the form of a CD-ROM.
v Download the fixes from the FTP site at:
ftp://ftp.software.ibm.com/ps/products/cobol/fixes
v Access fixes from your respective bulletin board services (BBS).
v Go to the IBM COBOL Web site and click the Support button.

FAX
You can also fax the Defect Report Form to IBM at 1-800-426-8602. To receive a
copy of this form, call 1-800-992-4777, Monday through Friday, 8:00 a.m. to 5:00
p.m., your time zone.

Phone
Phone support provides assistance for a variety of incidents, such as installation
problems and defect reporting. There may be a fee associated with voice support.
You may pay for the call on a per incident basis; elect to use bulletin board
services (BBS), CompuServe, or the Internet; or purchase an annual contract for
phone support. However, if IBM determines that the defect is in the IBM code, you
are not charged for the incident.

© Copyright IBM Corp. 1995, 2000 79

 To report a problem, call 1-800-237-5511 or 1-800-992-4777. These phone numbers
are available Monday through Friday, 8:00 a.m. to 5:00 p.m., your time zone.

Mail
Mail your comments to:
IBM Corporation
Personal Systems Support Family
Internal Zip 2901
11400 Burnett Road
Austin, Texas 78758

For support in other countries, contact your local IBM-authorized sales

representative.

RELATED TASKS
“Getting consulting services”
“Getting education and training”

Getting consulting services

IBM provides service offerings for VisualAge COBOL and the rest of the IBM
COBOL family of products. For more information about consulting services in the
United States, call 1-800-IBM-3333, ext. STAR703. To arrange for an IBM
representative to discuss your specific COBOL services requirements, call
1-800-IBM-4YOU. For consulting services in other countries, contact your local
IBM-authorized sales representative.

If you have access to the Internet, you can go to the IBM COBOL Web site and
click the Support button.

RELATED TASKS
“Getting education and training”

Getting education and training

IBM provides education and training for VisualAge COBOL and the rest of the
IBM COBOL family of products. You can request information or enroll in courses
in one of the following ways:
v For more information about the course offerings in the United States and
Canada, call 1-800-IBM-8322. For education and training in other countries, call
001-520-574-4500. These phone numbers are available Monday through Friday,
8:00 a.m. to 8:00 p.m., Eastern Standard Time (EST).
v If you have access to the Internet, you can go to the IBM COBOL Web site and
click the Support button.

80 Getting Started
Appendix. Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this publication to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.

If you are viewing this information softcopy, the photographs and color
illustrations may not appear.

© Copyright IBM Corp. 1995, 2000 81

82 Getting Started
Index
A I product overview 1
product support 79
Add push button 63 IMS project
databases 8 building a target 49
B installation
planning for 11
correcting syntax errors 50
creating 45
basic install installing
VisualAge COBOL 24 visual, creating 54
Loopback Adapter on Windows project environment
Btrieve 6 2000 24
buttons 56 overview 4
Loopback Adapter on Windows Projects file, creating 46
NT 23 push buttons 56
C on a network server 24
canvas, in visual builder 56 on the workstation 24
CICS transactions 4 resetting environment variables 27
using a response file 29
R
Code Assistant remote
description 4 VisualAge COBOL 24
DL/I 8
using 73 installing on the workstation 19
remote ECD
composition editor 56 overview 1
changing window title 57
creating L Remove push botton 64
requirements
GUI applications 5 Loopback Adapter adapter card 11
non-GUI project 46 installing on Windows 2000 24 hard disk space 11
nonvisual parts 71 installing on Windows NT 23 hardware 11
source files 48 memory 11
processor 11
M software 11
D memory requirements 11 running
Data Assistant GUI applications 77
description 4 non-GUI applications 50
DB2 coprocessor 6 N
distributed data access 6 network install
debugger VisualAge COBOL 24 S
description 6 non-GUI applications sample application
disk space requirements 11 running 50 building 45
Distributed Debugger 6 Notices 81 source code 49
shared install
E O
VisualAge COBOL 24
silent installation
editing
object-oriented extensions 6 setup log file 30
creating a new file 48
operating system requirements 12 setup parameters 29
description 4
software
environment variables
optional 13
resetting 27
event-driven program 62
P required 11
part source SOM 6
generating 73 SQL statements 4
F parts stored procedure manager
feature source adding a list box 59 overview 2
generating 73 adding a push button 59 support
updating 73 adding a static text part 58 consulting services 80
free-form surface, in visual builder 56 adding an entry field 58 education and training 80
adding and aligning 70 ways of getting 79
G aligning 59
connecting 62
syntax errors, correcting 50
system interface
generating code 65 defining 72
nonvisual, adding and connecting 75
GUI applications System Interface Editor 72
nonvisual, creating 71
creating 5
placing 57
running 77
selecting 58
TODOLIST, opening 68 T
parts palette 56 title bar, changing text in 57
H Performance Analyzer to-do list application
hardware requirements 11 overview 8 creating 53

© Copyright IBM Corp. 1995, 2000 83

to-do list application (continued)
expanding 67
trace
execution of an application 9
multithreaded interactions 9

U
uninstalling 20

V
visual builder
aligning parts 59
building applications 65
composition editor 56
parts 56
resizing parts 59
running an application 66
running applications 77
starting 55
visual builder projects
creating 54

84 Getting Started
Readers’ Comments — We’d Like to Hear from You
VisualAge COBOL for Windows NT
Getting Started
Version 3.0.2

Publication No. GC27-0811-02

Overall, how satisfied are you with the information in this book?

Very Satisfied Satisfied Neutral Dissatisfied Very

Dissatisfied
Overall satisfaction h h h h h

How satisfied are you that the information in this book is:

Very Satisfied Satisfied Neutral Dissatisfied Very

Dissatisfied
Accurate h h h h h
Complete h h h h h
Easy to find h h h h h
Easy to understand h h h h h
Well organized h h h h h
Applicable to your tasks h h h h h

Please tell us how we can improve this book:

Thank you for your responses. May we contact you? h Yes h No

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you.

Name Address

Company or Organization

Phone No.
 ___________________________________________________________________________________________________
Readers’ Comments — We’d Like to Hear from You Cut or Fold
GC27-0811-02
 Along Line

_ _ _ _ _ _ _Fold
_ _ _and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______

NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES

BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBM Corporation
Department HHX/H3
P.O. Box 49023
San Jose, CA
United States of America
95161-9023

_________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape

Cut or Fold
GC27-0811-02 Along Line



Part Number: CT65QNA

Printed in the United States of America

on recycled paper containing 10%
recovered post-consumer fiber.

(1P) P/N: CT65QNA

GC27-0811-02