Jump to Alchemy

Fujitsu PowerCOBOL

Choosing PowerCOBOL

  1. How quickly can I apply my COBOL knowledge to Windows programming?
  2. What is the difference between PowerCOBOL and NetCOBOL?
  3. How do I get started using PowerCOBOL?
  4. How long will it take me to use PowerCOBOL effectively?
  5. What languages do I need to know or learn to use PowerCOBOL?
  6. Can I create software that runs on Windows 98, Windows Me, Windows NT, Windows 2000, Windows XP and Windows 2003?
  7. What are the resource requirements for NetCOBOL and PowerCOBOL under Windows 98/Me/NT/2000/XP/2003?

Using PowerCOBOL

  1. How do I debug a mixed PowerCOBOL and NetCOBOL application?
  2. What packaging options are available for NetCOBOL and PowerCOBOL applications? Are there any guidelines for packaging in client/server environments?
  3. Does PowerCOBOL support the European date format?
  4. Can I import Version 3 projects into Version 10 of PowerCOBOL?
  5. Does PowerCOBOL Version 10 support Version 3 syntax?

Using PowerCOBOL with Databases

  1. Can I access SQL databases?
  2. Can I access Oracle and other databases with native SQL calls?
  3. Will other databases work with Fujitsu PowerCOBOL?
  4. Where can I get the ODBC Driver for my database?
  1. How quickly can I apply my COBOL knowledge to Windows programming?

    Answer: Immediately. PowerCOBOL can have you creating GUI's in minutes and you will find that NetCOBOL comes with all the tools to make you feel very comfortable in the Windows environment.

  2. What is the difference between PowerCOBOL and NetCOBOL?

    Answer: PowerCOBOL is a GUI Builder that allows COBOL programmers to create Windows applications. PowerCOBOL uses an event-driven programming model like Visual Basic but all the programming is done in COBOL.

    NetCOBOL is the compiler used to create batch and character mode (DISPLAY/ACCEPT and Screen Section) applications. It is possible to create mixed PowerCOBOL and NetCOBOL applications. With PowerCOBOL, you can create and use ActiveX controls.

  3. How do I get started using PowerCOBOL?

    Answer: PowerCOBOL Getting Started is a good place to start learning about PowerCOBOL. Make sure that you install the Softcopy Documentation - this is a separate step from installing the NetCOBOL product. You will then find all the manuals can be easily accessed from the NetCOBOL Documentation Viewer. First read the overview in Chapter 1, then take the guided tour in Chapter 2.

    After that you can move on to the PowerCOBOL User's Guide - Chapter 3, Developing Your First PowerCOBOL Application. Therafter you can check out the numerous sample programs that come with PowerCOBOL.

  4. How long will it take me to use PowerCOBOL effectively?

    Answer: If you are a proficient COBOL programmer with some familiarity with event-based programming, you can create your first interfaces within minutes, you will be creating useful interfaces within a few hours, and be highly productive within a few days.

  5. What languages do I need to know or learn to use PowerCOBOL?

    Answer: You only need to know COBOL to use PowerCOBOL. Properties and data are defined using COBOL data definitions, methods are invoked using COBOL syntax, and application events are coded in COBOL.

  6. Can I create software that runs on Windows 98, Windows Me, Windows NT, Windows 2000, Windows XP and Windows 2003?

    Answer: Past versions of PowerCOBOL have supported the creation of applications for these versions of Windows. However, the latest version is only being tested on the operating systems listed under Platforms Supported above. We therefore only recommend using PowerCOBOL to create applications for these platforms.

  7. What are the resource requirements for NetCOBOL and PowerCOBOL?

    Answer:NetCOBOL for Windows will operate on any computer with at least the minimum resources required by each of these operating systems and the following available hard disk space:

    610 MB to install NetCOBOL Enterprise Edition

  8. How do I debug a mixed PowerCOBOL and NetCOBOL application?

    Answer: The NetCOBOL Debugging Guide - Chapter 3 describes debugging mixed PowerCOBOL and NetCOBOL applications.

  9. What packaging options are available for NetCOBOL and PowerCOBOL applications? Are there any guidelines for packaging in client/server environments?

    Answer:Guidelines for packaging the NetCOBOL runtime support with your applications are provided in the NetCOBOL Runtime Installation Guide. Microsoft installation files are available for download along with tools that can help with the packaging – depending on which version of the Windows operating system you are targeting.

  10. Does PowerCOBOL support the European date format?

    Answer: Yes. A custom date format is provided in PowerCOBOL providing support for European date formats as well as others.

  11. Can I import Version 3 projects into Version 10 of PowerCOBOL?

    Answer: Yes. PowerCOBOL Version 10 has the ability to convert Version 3 projects into the Version 10 format.

  12. Does PowerCOBOL Version 10 support Version 3 syntax?

    Answer: Yes. For backward compatibility, Version 3 syntax is supported. However, you are encouraged to update your programs to the more object-oriented and component-based facilities in Version 10, on which future versions of PowerCOBOL will be based.

    For more information on the Controls, Properties and Methods available in PowerCOBOL, including syntax descriptions and examples of each method, see the PowerCOBOL Reference and the on-line help for PowerCOBOL.

  13. Can I access SQL databases?

    Answer: Yes, Fujitsu PowerCOBOL and NetCOBOL support databases like Microsoft SQL Server, Microsoft Access, Oracle, Sybase and Informix using ODBC, and also using native EXEC SQL syntax.

  14. Can I access Oracle and other databases with native SQL calls?

    Answer: Yes. PowerCOBOL has been tested with various versions of the Oracle Pro*COBOL precompilers.

  15. Will other databases work with Fujitsu PowerCOBOL?

    Answer: Any database that can be accessed via ODBC should work.

  16. Where can I get the ODBC Driver for my database?

    Answer: The first place to look is with the vendor who supplied the database.