Home > Archive > Cobol > July 2006 > using Fujitsu Cobol version 3.0 from the command line
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
using Fujitsu Cobol version 3.0 from the command line
|
|
| epc8@juno.com 2006-07-10, 9:55 pm |
| For the benefit of any students lurking here, I have written up some
observations about using Fujitsu Cobol ver 3.0 which is available at
http://www.netcobol.com/student/ (registration required).
Some people have reported problems installing this version on Win XP or
Win 2000. I was able to install it without any difficulty on Windows
XP-SP2.
I did not like the "Programming Staff" IDE environment much partly
because I like to work with command line tools. You can compile and you
can link from the command line, even while working in fullscreen. All
that is required is to add the directory containg the .EXE and .LIB
files to the PATH and include that path in the LIB environment
variable.
Running the executable file, however, is best done from a console
window that has not been switched to full screen. The application opens
up a new console window instead of using the existing window. I prefer
running my editor in fullscreen (dos) partly for speed so this is a bit
of a pain.
Unless you set an environment variable or an entry in a config file,
running a program brings up a separate dialog window for run tine
configuration options. setting @EnvSetWindow=UNUSE turns this off.
Likewise, on exit, a message box pops up asking if you want to close
the new console window. To turn this off, say if you have done a final
ACCEPT into a dummy variable, then set @WinCloseMsg=OFF
Here are some representative .BAT files for setup, compile and link.
path=c:\fsc\pcobol32;%path%
set lib=c:\fsc\pcobol32
set @EnvSetWindow=UNUSE
Before compile and link set prog=your_program_name (no extension).
Note that -M indicates the main program. FSC 3.0 requires one program
to be designated as the main program (like C).
cobol32 -M %prog%.cob
link %prog%.obj f3bicimp.lib libc.lib kernel32.lib user32.lib
/out:%prog%.exe (all on one line, of course)
-- elliot
| |
| Robert Jones 2006-07-11, 6:55 pm |
| Thanks, I have just got a new computer, so have gone from 98SE to XP,
so am grateful to hear about any gotchas, etc
Robert
| |
| epc8@juno.com 2006-07-11, 6:55 pm |
| Robert Jones wrote:
> Thanks, I have just got a new computer, so have gone from 98SE to XP,
> so am grateful to hear about any gotchas, etc
>
> Robert
The URL in my original post has a reference to solutions to problems on
2000/XP. AFAIK the problem is with installing the software, not running
it once installed. I believe that setting one of the compatibility
modes for the setup program does solve the problems that arise.
Also it may be that later versions of FJ Cobol / Power Cobol do not
work on 2000/XP. Perhaps FJ wants its customers to upgrade to NetCOBOL
on these platforms.
-- elliot
| |
| HeyBub 2006-07-11, 6:55 pm |
| epc8@juno.com wrote:
>
> Also it may be that later versions of FJ Cobol / Power Cobol do not
> work on 2000/XP. Perhaps FJ wants its customers to upgrade to NetCOBOL
> on these platforms.
Terrible confusion.
PowerCobol works on XP
NetCOBOL *IS* PowerCobol. COBOL for NET is different. (I think).
| |
| Richard 2006-07-11, 6:55 pm |
|
HeyBub wrote:
>
> NetCOBOL *IS* PowerCobol.
No. Wrong. NetCobol is the normal Cobol. For example NetCOBOL for
Linux is not PowerCOBOL, nor does it include it. It happens that
NetCOBOL for Windows does, or used to, include PowerCOBOL.
> COBOL for NET is different. (I think).
No. Wrong. Fujitsu's product is "NetCOBOL for .NET" and there is no
PowerCOBOL in it.
|
|
|
|
|