Preface

Fujitsu PowerCOBOL is a Graphical User Interface (GUI) design and implementation tool for COBOL programmers. It provides all the graphical controls commonly used in applications today and gives the COBOL programmer the ability to respond to events and manipulate the controls using COBOL.

In addition to PowerCOBOL's GUI capabilities all the power of Fujitsu's standard COBOL compiler are available to the PowerCOBOL user.

This Getting Started manual aims to take you through the most significant parts of the product's functionality as quickly as possible, thus making the most effective use of your time.

Audience

COBOL programmers ready to start creating GUI applications.

Product reviewers who are assessing Power COBOL's suitability for an organization or who are writing an article on PowerCOBOL.

You do not need to know COBOL to work through this manual, but you will need to know COBOL to make serious use of PowerCOBOL.

How This Manual is Organized

This manual contains the following information:

Chapter 1	Introduction
Chapter 2	A Quick Tour
Appendix A	Tips
Appendix B	Support

Related Manuals

NetCOBOL Getting Started
NetCOBOL User's Guide
NetCOBOL Language Reference
NetCOBOL Debugging Guide
PowerCOBOL User's Guide
PowerCOBOL Reference
PowerBSORT User's Guide
PowerFORM Getting Started

Trademarks

Microsoft, Windows, Windows Server and ActiveX are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Fujitsu, NetCOBOL and Fujitsu PowerCOBOL are trademarks or registered trademarks of Fujitsu Limited.

Product Names

The following product names are abbreviated in this manual as follows:

Product Name	Abbreviation
Microsoft(R) Windows Server(R) 2012 R2 Datacenter Microsoft(R) Windows Server(R) 2012 R2 Standard Microsoft(R) Windows Server(R) 2012 R2 Essentials Microsoft(R) Windows Server(R) 2012 R2 Foundation	Windows Server 2012 R2
Microsoft(R) Windows Server(R) 2012 Datacenter Microsoft(R) Windows Server(R) 2012 Standard Microsoft(R) Windows Server(R) 2012 Essentials Microsoft(R) Windows Server(R) 2012 Foundation	Windows Server 2012
Microsoft(R) Windows Server(R) 2008 R2 Foundation Microsoft(R) Windows Server(R) 2008 R2 Standard Microsoft(R) Windows Server(R) 2008 R2 Enterprise Microsoft(R) Windows Server(R) 2008 R2 Datacenter	Windows Server 2008 R2
Windows(R) 8.1 Windows(R) 8.1 Pro Windows(R) 8.1 Enterprise	Windows 8.1
Windows(R) 8 Windows(R) 8 Pro Windows(R) 8 Enterprise	Windows 8
Windows(R) 7 Home Premium Windows(R) 7 Professional Windows(R) 7 Enterprise Windows(R) 7 Ultimate	Windows 7
Windows Server 2012 R2 Windows Server 2012 Windows Server 2008 R2 Windows 8.1 Windows 8 Windows 7	Windows

Conventions Used in This Manual

Example of convention	Description
setup, setup	Characters you enter appear in bold.
Program-name	Underlined text indicates a placeholder for information you supply.
ENTER	Small capital letters are used for the name of keys and key sequences such as ENTER and CTRL+R. A plus sign (+) indicates a combination of keys.
...	Ellipses indicate the item immediately preceding can be specified repeatedly.
Edit, Literal	Names of menus and options appear with the initial letter capitalized.
[def]	Indicates that the enclosed item may be omitted.
{ABC\|DEF}	Indicates that one of the enclosed items delimited by \| is to be selected.
CHECK WITH PASCAL LINKAGE ALL PARAGRAPH-ID COBOL ALL	Commands, statements, clauses, and options you enter or select appear in uppercase. Program section names, and some proper names also appear in uppercase. Underlined text indicates the default.
DATA DIVISION. WORKING-STORAGE SECTION. * Get the #INCLUDE file to the data control #INCLUDE "NUMDATA.COB". PROCEDURE DIVISION.	This font is used for examples of program code.
The form acts as an application creation window.	Italics are occasionally used for emphasis.
"PowerCOBOL User's Guide" See Chapter 6, "Creating an Executable Program."	References to other publications or chapters within publications are in quotation marks.

Export Regulation

Exportation/release of this document may require necessary procedures in accordance with the regulations of your resident country and/or US export control laws.

August 2015