tiny-cobol-users

Re: [Tiny-cobol-users] Segmentation Fault - unable to trace

[David E. <de...@us...>]

ravi :

 > Could someone pls help me with the following?
 > I am able to compile the programs without any error.
 > But I get "segmentation fault" on executing the binary.
 > One is calling program and the other called program.
 > gdb is also of no use in this case. I am unable to
 > proceed any further. Pls help.
 > I have attached both the programs in one single file.

There is some sort of memory corruption problem in one of the literals 
or identifiers.

This is causing a segmentation fault when one of the identifiers gets 
initialized due to the VALUE clause.

Due to the large amount of literals and identifiers it is difficult to 
isolate the problem, as the memory location where the problem occurs may 
have only a casual relation to the problem.
And since the memory location is corrupt, it is difficult, if not 
impossible, to identify the problem statement.

Anyway I will try to isolate the problem.

BTW, if you which to look at the problem just compile the run-time with 
the GCC '-g' option, and set the '.gdbinit' file with a break-point at 
'b tcob_move'.
The run the tests program (gdb BPVITD3), and use the continue command.

[Tiny-cobol-users] Segmentation Fault - unable to trace

[<ra...@gr...>]

Could someone pls help me with the following?
I am able to compile the programs without any error. But I get "segmentation fault" on executing the binary. One is calling program and the other called program.
gdb is also of no use in this case. I am unable to proceed any further. Pls help.
I have attached both the programs in one single file.

TIA
Ravi

Re: [Tiny-cobol-users] test program

[Jim M. <ro...@vi...>]

David

Thanks.
I never fail to impress myself with my ability to make dumb mistakes.

Jim


David Essex wrote:

>
> > ...
> > * Error - unbalanced qoutation mark
> > MOVE "A" TO P-IND-B".
> > ...
>

Re: [Tiny-cobol-users] test program

[David E. <de...@us...>]

Jim Morcombe wrote:

 > I am trying to modify the test program test18.cob
 > from the test suite to play around with the START
 > command.
 > However, I have a bug and can't get it to compile.
 > Its probably some stupid thing I've done, but what is it?
 >
 > ...
 > FIND-FIRST-KEY.
 > ...
 > * Error - unbalanced qoutation mark
 > MOVE "A" TO P-IND-B".
 > ...
 > DISPLAY "We found a record with the START".
 > READ ARQ
 > * AT END - duplicate 'at end'
 >   AT END SET END-OF-FILE TO TRUE

Unbalanced quotation marks is a known problem with TC.

Will have to add better error traps, at a later date.

Re: [Tiny-cobol-users] Calling Programs

[David E. <de...@us...>]

Jim Morcombe wrote:

> I have a program that compiles when I have the following:
> CALL "SCN-ERROR" USING ERROR-LINES.
> 
> However, if I change it to be
> 
> 01  PROG       PIC X(10)       VALUE "SCN-ERROR".
> CALL PROG USING ERROR-LINES.
> 
> Then I get a Segmentation error during the compile.

The valid values in a program-id are implementation defined.

With TC, a '-' (dash) can't be used in a program-id, as both C and GNU 
assembler will not support it.

Unfortunately the CALL statement error trapping needs improvement, both 
at compile time and run-time.

[Tiny-cobol-users] test program

[Jim M. <ro...@vi...>]

I am trying to modify the test program test18.cob from the test suite to 
play around with the START command.
However, I have a bug and can't get it to compile.
Its probably some stupid thing I've done, but what is it?

[Tiny-cobol-users] Calling Programs

[Jim M. <ro...@vi...>]

I have a program that compiles when I have the following:
 CALL "SCN-ERROR" USING ERROR-LINES.

However, if I change it to be

01  PROG       PIC X(10)       VALUE "SCN-ERROR".
 CALL PROG USING ERROR-LINES.

Then I get a Segmentation error during the compile.

Re: [Tiny-cobol-users] Segmentation fault

[David E. <de...@us...>]

Jim Morcombe wrote:

 > I have attached a Cobol program that crashes the compiler with a
 > segmentation fault.
 > ...

Jim, trying to debug the TC compiler can be a real pain at times.

Trying isolate the problem with the code you enclosed will not work as 
it contains COPYBOOKS.

This leaves two options.

Try to isolate the bug yourself, which is not difficult but can be 
problematic.

Or, assuming that it is a viable option, send me the the complete source 
including the COPYBOOKS, and I will try to duplicate the problem on the 
CVS version.

If you would like to try to isolate the problem first, then just do the 
following.

1) Compile the TC compiler (RT not required) with the GCC '-g' option.
2) In the same directory as $PROG.cbl, create a '.gdbinit' file and
    add the following line.
    'r -c -g -C -D -F -P -I $COBCPY -I $IO $PROG.cbl'
3) initialize the environment variables.
    export COBCPY=...
4) Run GDB
    gdb htcobol

This should give you output some thing like the following.

[Tiny-cobol-users] Segmentation fault

[Jim M. <ro...@vi...>]

I have attached a Cobol program that crashes the compiler with a 
segmentation fault.

Here is the output
------------------------------------------

We are about to compile : jimtest

/home/jim/bin/int: line 52:  2524 Segmentation fault      htcobol -c -g 
-C -D -F -P -I $COBCPY -I $IO $PROG.cbl
Woops! The compiler returned error : 139
[jim@byrlin3 work]$

-------------------------------------------------

I'm sorry I couldn't give you a shorter example, but the error 
disappears every time I delete a few lines of code.

The error seems so flaky that I won't be surprised if you can't 
reproduce it.

Our programing standards state that we shouldn't use "SECTIONS" in the 
PROCEDURE DIVISION, so I have little experience with the effects of 
SECTIONS.

If I change the "MAINLINE SECTION" statement on line 212 to be just 
"MAINLINE" then the error goes away.

Alternatively,

If I move line 211 to line 213 the error also goes away.  That is, when 
I move the statement PERFORM GET-DATABASE-TYPE. to be after the 
"MAINLINE SECTION" the error goes away.

Alternatively,
if I comment out line 254 -   DISPLAY "SEARCH-ACCOUNT = " 
SEARCH-ACCOUNT. Then the error disappears.

Alternatively,
If I just delete apparently random lines of code, the error disappears.

Jim

Re: [Tiny-cobol-users] Called Programs

[Jim M. <ro...@vi...>]

David

My appologies.  I was compiling my "called program" with the wrong 
script and was still trying to compile it to an executable, not a shared 
library.  Naturally it complained.

In fact, it compiles nicely.

Jim

Re: [Tiny-cobol-users] does htcobol 0.62 work with gcc 3.3.5 ?

[Carlucio L. <car...@te...>]

On Tue, 12 Jul 2005 20:41:53 +0200
Alfred Cleve <alf...@t-...> wrote:

> Hello Carlucio,
> 
> > install version:
> > ii  bison          1.35-3
> > ii  flex           2.5.4a-24 
> 
> which version of gcc and which version of Debian is used at your system ?
> 

I have Debian Sarge,

for install bison and flex 
deb ftp://ftp.debian.org/debian woody main contrib non-free

carlucio@cpd1:~$ gcc -v
Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.5/specs
Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --enable-__cxa_atexit --with-system-zlib --enable-nls --without-included-gettext --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux
Thread model: posix
gcc version 3.3.5 (Debian 1:3.3.5-13)
carlucio@cpd1:~$ 

bye

Carlucio Lopes - Debian Gnu/Linux+Tinycobol+Tcl+Postgresql
compilador Cobol FREE  http://tinycobol.org site em Portugues
Por que COBOL? http://www.clubecobol.com.br/cc_porque_cobol.asp
Pirataria!!??.. entenda o que e'.-> www.carlinux.hpg.com.br
Goiania-Goias-Brasil   62-526-8006  62-9946-3523
icq - 267274130  msn - car...@ho...

Re: [Tiny-cobol-users] does htcobol 0.62 work with gcc 3.3.5 ?

[Alfred C. <alf...@t-...>]

Hello Carlucio,

> install version:
> ii  bison          1.35-3
> ii  flex           2.5.4a-24 

which version of gcc and which version of Debian is used at your system ?

bye,
Alfred

Re: [Tiny-cobol-users] Called Programs

[David E. <de...@us...>]

Jim Morcombe wrote:

> Yes, I have a LINKAGE SECTION with a number of variables.
>  ...
 > Linking glcosch.o...
 > /usr/lib/gcc-lib/i386-redhat-linux/3.2/../../../crt1.o: In function
 > `_start':
 > /usr/lib/gcc-lib/i386-redhat-linux/3.2/../../../crt1.o(.text+0x18):
 > undefined reference to `main'
 > collect2: ld returned 1 exit status

OK, I think I mis-read the error messege.

It is the link step that is trying to create an executable, but does not 
find a main entry point as declared in crt1.o.

So there must be some thing wrong with the GCC link step.

Looking at 'test.code/t33', the compile and link should look some thing 
like the following.

Example:
htcobol -c -P subrots.cob
gcc -shared -Wl,-soname,libsubrot2.so.1.0 -o libsubrot2.so.1.0 subrots.o
ln -s libsubrot2.so.1.0 libsubrot2.so
ln -s libsubrot2.so.1.0 libsubrot2.so.1

[Tiny-cobol-users] Called Programs

[Jim M. <ro...@vi...>]

David

Yes, I have a LINKAGE SECTION with a number of variables.

Jim

Here is my linkage section.

018600******************************************************************
018700*                       LINKAGE SECTION                          *
018800******************************************************************
020100 LINKAGE SECTION.
020300 77  PROG-NAME           PIC X(6).
020400 77  PROG-DESC           PIC X(40).
       77  SEARCH-COMPANY         PIC X(05).
       77  SEARCH-ACCOUNT         PIC X(20).
020600 77  ACCOUNT-DESC         PIC X(40).
020700 77  PF-KEY              PIC 99.
020800 77  ERROR-CODE          PIC 99.
020900
021000/
021100******************************************************************
021200*                     PROCEDURE DIVISION                         *
021300******************************************************************
021400 PROCEDURE DIVISION USING PROG-NAME,
021500                          PROG-DESC, SEARCH-COMPANY,SEARCH-ACCOUNT
                                ACCOUNT-DESC,
021600                          PF-KEY, ERROR-CODE.
    

Re: [Tiny-cobol-users] Bold and underline not working

[David E. <de...@us...>]

David Essex wrote:

 > Massimo Colani wrote:
 >
 >> Will this problem be solved in future releases or
 >> will it stay?
 >
 > I'm currently trying to resolve the problems.

I've uploaded some changes to SF CVS which hopefully has resolved the
bold and underline and the background color problems.

I don't think these changes have reloved all the problems with the
curses code, but it is the best that can be achived under the circumstances.

Note that no tests have been perfomed on Win32 using PDcurses.

Re: [Tiny-cobol-users] Called Programs

[David E. <de...@us...>]

BB wrote:

 > I want to compile and link a program as a
 > shared library, but am running into problems.
 >
 > As soon as I add the "LINKAGE SECTION" and
 > place "USING.." on the "PROCEDURE DIVISION" line
 > of my Cobol program, it crashes during the link stage.
 >
 > Here is how I compiled it...
 >
 > # First we compile the program $PROG to produce the .o file
 > htcobol -c -g -C -D -F -P -I $COBCPY $PROG.cbl
 > #    -c  Compile to a statically linked object module.
 > #    -g  Generate Compiler debugging output
 > #    -C  Make all Cobol calls dynamic
 > #    -D  Include Source Debugging Lines
 > #    -F  Input Source is in standard Fixed Column format
 > #    -P  Generate Output Listing file
 > #    -I  Define include (copybooks) search path(s).
 >
 > Here is how I linked it...
 >
 > # Next we create the Dynamically Loadable Shared Library "scn.so.0.0"
 > gcc -shared -Wl,-soname,lib$PROG.so.0.0 -o lib$PROG.so.0.0 $PROG.o
 >
 > Here is the output produced by "gcc".
 > ---------------------------------------
 > The program compiled successfully!
 > Linking glcosch.o...
 > /usr/lib/gcc-lib/i386-redhat-linux/3.2/../../../crt1.o: In function
 > `_start':
 > /usr/lib/gcc-lib/i386-redhat-linux/3.2/../../../crt1.o(.text+0x18):
 > undefined reference to `main'
 > collect2: ld returned 1 exit status
 > ----------------------------------------

I think the problem is with TC version 0.62, which tries to auto detect 
if program is a main or sub-program, is generating a main entry point.

Check that your sub-program has a 'LINKAGE SECTION' and at least one 
variable defined.

Example:
LINKAGE SECTION.
01 VAR  PIC X(10).
PROCEDURE DIVISION USING VAR.

To aviod these headaches, you could download the current CVS version 
which has command line options to better deal with entry points and 
sub-programs.

Re: [Tiny-cobol-users] STRING problem (DELIMITED BY SPACES)

[Jim M. <ro...@vi...>]

My 2 cents worth...

David is 100% correct.

In the string statement, the delimitter is defined by the "next"=20
DELIMITED BY" statement that is encountered.  This is the normal usage=20
of STRING...

STRING VAR1 VAR2 VAR3 DELIMITED BY SPACES
                VAR2 VAR3 VAR4 DELIMITED BY SIZE
                 VAR5 VAR6 DELIMITED BY SPACES
                 VAR 7 VAR8 DELIMITED BY "#"
                                INTO WHATEVER.

Jim Morcombe



David Essex wrote:

> Sorry the first messege got truncated.
>
> Carlos Gomes wrote:
>
> > String verb that has strage output has no
> > DELIMITED in first token (by default DELIMITED
> > BY SIZE). DELIMITED BY SPACES is used only
> > in WTEXT1 token (with a value of "12345     ").
> > It seems that using DELIMITED BY SPACES
> > only in one token does the compiler to use
> > this option in every token of the command.
> >
> > STRING
> > "INSERT INTO TEST " , <<<--- No DELIMITED (Default BY SIZE)
> > ",",
> > W9,
> > ",",
> > WTEXT1 DELIMITED BY SPACES,
> > ");"
> > INTO WRESULT.
> >
> > Result:
> > INSERT,999,12345);
> >
> > Using DELIMITED BY SIZE in first token gives the correct result.
> >
> > STRING
> > "INSERT INTO TEST " DELIMITED BY SIZE,
> > ",",
> > W9,
> > ",",
> > WTEXT1 DELIMITED BY SPACES,
> > ");"
> > INTO WRESULT.
> >
> > Result:
> > INSERT INTO TEST ,999,12345);
> >
> > It looks like default DELIMITED BY SIZE doesn=B4t
> > be use by TC in this case.
>
> I do not agree.
>
> If you look at the syntax below, the 'DELIMITED' phrase of the 'STRING'
> statement can have more than one argument (ie. {identifier-1 |
> literal-1}...).
> Thus the "INSERT INTO TEST " literal is part of the 'DELIMITED BY
> SPACES' phrase.
>
> The COBOL 89 draft standard (not in COBOL 85) states that if (and only
> if) the last token before the INTO phrase, does not have a 'DELIMITED'
> clause, then that token(s) defaults to a 'DELIMITED BY SIZE'
>
> Thus in the above examples the '");" INTO WRESULT' is equivalent to
> '");" DELIMITED BY SIZE INTO WRESULT'.
>
> I've also compiled and run the sample program provided, using an old
> commercial COBOL compiler. It's output is identical to TC.
>
> So unless some one can produce proof to the contrary, using a commercia=
l
> grade COBOL compiler, I think we can put this matter to rest.
>
>
> The COBOL 89 draft standard:
>
> 14.10.39  STRING statement
> ...
> 14.10.39.1 General format
> ...
> Syntax:
> STRING {
> {identifier-1 | literal-1}...
> DELIMITED [BY]
> {identifier-2 | literal-2 | SIZE }
> }...
> INTO identifier-3
> ...
>
> 4.10.39.2 Syntax rules
> ...
> 8) The DELIMITED phrase may be omitted only immediately preceding the=20
> INTO phrase. If it is omitted, DELIMITED BY SIZE is implied.
> ...
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar=20
> happening
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dua=
l
> core and dual graphics technology at this free one hour event hosted=20
> by HP, AMD, and NVIDIA.  To register visit=20
> http://www.hp.com/go/dualwebinar
> _______________________________________________
> Tin...@li...
> https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users
>
>

Re: [Tiny-cobol-users] does htcobol 0.62 work with gcc 3.3.5 ?

[Carlucio L. <car...@te...>]

On Mon, 11 Jul 2005 01:51:17 +0200
Alfred Cleve <alf...@t-...> wrote:

> Hi,
> 
> i tried to compile the stable version of htcobol 0.62 within the actual 
> debian-sarge. The used gcc is
> 
> gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
> Copyright © 2003 Free Software Foundation, Inc.
> 
> the result of make gives a result like that:
> alfred@tux:/usr/local/src/tinycobol-0.62/compiler$ make
> gcc -I/usr/include -I/usr/local/include -I../lib -I../ -c scan.c
> scan.c:1060: error: Syntaxfehler before "YY_PROTO"
> scan.l:120: error: Syntaxfehler before "switch"
> scan.l:123: error: redefinition of `yy_start'
> scan.c:272: error: `yy_start' previously defined here
> scan.l:123: Warnung: data definition has no type or storage class
> scan.l:124: error: Syntaxfehler before "break"
> 
> Is anybody out there, who can give me a hint ?

install version:
carlucio@cpd1:~$ dpkg -l |grep bison
ii  bison          1.35-3         A parser generator that is compatible with Y

ii  flex           2.5.4a-24      A fast lexical analyzer generator.

bye

Carlucio Lopes - Debian Gnu/Linux+Tinycobol+Tcl+Postgresql
compilador Cobol FREE  http://tinycobol.org site em Portugues
Por que COBOL? http://www.clubecobol.com.br/cc_porque_cobol.asp
Pirataria!!??.. entenda o que e'.-> www.carlinux.hpg.com.br
Goiania-Goias-Brasil   62-526-8006  62-9946-3523
icq - 267274130  msn - car...@ho...

Aw: Re: [Tiny-cobol-users] Can i call DB2 database from tinyCOBOL

[<he...@ne...>]

Hi Nikil,

I compiled DB2 cobol programs with TC under windows, only.
So I can't tell you, if it's working under Linux, too.
You have to try for your own... :-)
Maybe it's some kind easier, because you needn't deal with the Microsoft Vi=
sual C library problems.

The free application development client packages for DB2 on all supported p=
lattforms can be downloaded at:
  http://www-306.ibm.com/software/data/db2/udb/support/downloadv8.html

I used the Microfocus cobol examples in subdirectory
  SQLLIB\samples\cobol_mf.

For a sample precompile procedure see=20
  embprep.bat
in the same directory.

Good luck.

Best regards
Stefan
----- Original Nachricht ----
Von:     nikil chakravarthy <nik...@ya...>
An:      Stefan Heublein <he...@ne...>
Datum:   11.07.2005 07:18
Betreff: Re: [Tiny-cobol-users] Can i call DB2 database from tinyCOBOL

> Hi Stefan Heublein,
>=20
> Once again thanks for information. I am trying to use
> redhat 8.0 along with DB2 7.2 installed on windows
> machine. With respect to my configuration can you tell
> me how i can proceed with compiling and running cobol
> programs which are accessing DB2 data.
> Can u tell me where can i download DB2 IBM application
> development client package and Sample IBM COBOL
> programs. Looking forward for response.
>=20
> Thanks & Regards,
> Nikil
>=20
> --- Stefan Heublein <he...@ne...> wrote:
>=20
> > Hi,
> >=20
> > it's possible to compile and run the IBM supplied
> > DB2 COBOL samples using TC
> > on Windows.
> >=20
> > First of all, you must compile the COBOL source
> > which contains embedded SQL
> > with the DB2 precompiler supplied by IBM (included
> > in the free application
> > development client package). The precompiler is
> > capable of generating
> > Microfocus COBOL compatible code. This leads to
> > plain COBOL source (without
> > embedded SQL), which has to be modified for
> > compiling with TC:
> >=20
> > - TC doesn't support literals as program identifiers
> > - TC requires the STDCALL keyword for DB2 api calls
> > (Microfocus COBOL:
> > SPECIAL-NAMES. CALL-CONVENTION 74 IS DB2API. CALL
> > DB2API "<api function>")
> > - I ran into problems with the precompiler generated
> > "by content" parameter
> > passing to the DB2 api. Converting "by content" to
> > "by reference" solved the
> > problem. Later I found another solution for this
> > problem. When aligning and
> > enlarging the passed structure to word boundary (4
> > bytes), the "by content"
> > parameter passing can remain unchanged...
> >=20
> > Last, but not least, you have to link the TC
> > compiled module to the DB2 api
> > libs. These libs are intended for use with
> > Microsoft's Visual C and have to
> > be converted to Mingw usable libs before (see Mingw
> > faqs).
> >=20
> > Good luck!
> >=20
> > I succeeded to compile and run a COBOL program
> > containing embedded (static)
> > SQL and accessing DB2 for z/OS (using DB2 Connect).
> >=20
> > Best regards
> > Stefan
> > -----Urspr=FCngliche Nachricht-----
> > Von: tin...@li...
> >
> [mailto:tin...@li...]Im
> > Auftrag von
> > --__--__--
> >=20
> > Message: 1
> > Date: Tue, 5 Jul 2005 21:59:35 -0700 (PDT)
> > From: nikil chakravarthy <nik...@ya...>
> > To: tiny-cobol-users
> > <tin...@li...>
> > Subject: [Tiny-cobol-users] Can i call DB2 database
> > from tinyCOBOL
> >=20
> > Hi All,
> >=20
> > I am newbie for tinyCOBOL development. I am
> > struggling
> > with finding information about tinyCOBOL with DB2
> > database access. Can somebody let me know whether it
> > is possible to connect to DB2 from tinyCOBOL and
> > send
> > me some URL's and resources. Your help is very much
> > appreciated. Looking forward for positive response.
> >=20
> > Thanks & Regards,
> > Nikil
> >=20
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam
> > protection around
> > http://mail.yahoo.com
> >=20
> >=20
> > --__--__--
> >=20
> > Message: 2
> > Date: Wed, 06 Jul 2005 02:35:56 -0400
> > From: David Essex <de...@us...>
> > Reply-To: tiny-cobol-users
> > <tin...@li...>
> > To: tiny-cobol-users
> > <tin...@li...>
> > Subject: Re: [Tiny-cobol-users] Can i call DB2
> > database from tinyCOBOL
> >=20
> > nikil chakravarthy wrote:
> >=20
> >  > I am newbie for tinyCOBOL development. I am
> > struggling
> >  > with finding information about tinyCOBOL with DB2
> >  > database access. Can somebody let me know whether
> > it
> >  > is possible to connect to DB2 from tinyCOBOL and
> > send
> >  > me some URL's and resources. Your help is very
> > much
> >  > appreciated. Looking forward for positive
> > response.
> >=20
> > TC does not have an SQL pre-processor, thus you can
> > only access any SQL
> > database using the native API, and not using
> > embedded SQL.
> >=20
> > If DB2 includes an SQL pre-processor for COBOL, and
> > I think it does, the
> > following may (or may not) work.
> > Pass the embedded SQL COBOL program thru the DB2 SQL
> > pre-processor for
> > COBOL. And then using TC, compile it's output adding
> > the appropriate DB2
> > library(s) in the link step.

Machen Sie aus 14 Cent spielend bis zu 100 Euro!
Die neue Gaming-Area von Arcor - =FCber 50 Onlinespiele im Angebot.
http://www.arcor.de/rd/emf-gaming-1

[Tiny-cobol-users] Called Programs

[BB <be...@by...>]

I want to compile and link a program as a shared library, but am running 
into problems.

As soon as I add the "LINKAGE SECTION" and place "USING.." on the 
"PROCEDURE DIVISION" line of my Cobol program, it crashes during the 
link stage.

Here is how I compiled it...

# First we compile the program $PROG to produce the .o file
htcobol -c -g -C -D -F -P -I $COBCPY $PROG.cbl
#    -c  Compile to a statically linked object module.
#    -g  Generate Compiler debugging output
#    -C  Make all Cobol calls dynamic
#    -D  Include Source Debugging Lines
#    -F  Input Source is in standard Fixed Column format
#    -P  Generate Output Listing file
#    -I  Define include (copybooks) search path(s).

Here is how I linked it...

# Next we create the Dynamically Loadable Shared Library "scn.so.0.0"
gcc -shared -Wl,-soname,lib$PROG.so.0.0 -o lib$PROG.so.0.0 $PROG.o


Here is the output produced by "gcc".
---------------------------------------
The program compiled successfully!
Linking glcosch.o...
/usr/lib/gcc-lib/i386-redhat-linux/3.2/../../../crt1.o: In function 
`_start':
/usr/lib/gcc-lib/i386-redhat-linux/3.2/../../../crt1.o(.text+0x18): 
undefined reference to `main'
collect2: ld returned 1 exit status
----------------------------------------


Jim Morcombe
(Still using Ben's computer, and wishing the 24 hour warranty on his own 
PC really meant something less than a week!  Why did he ever trade in 
his trusty old Windows 98 PC?  What was wrong with his Windows 95 PC? 
At least his old ancient Linux box and even more ancient ancient SCO 
boxes still work faithfully.)

Re: [Tiny-cobol-users] does htcobol 0.62 work with gcc 3.3.5 ?

[David E. <de...@us...>]

Alfred Cleve wrote:

> i tried to compile the stable version of htcobol 0.62 within the actual 
> debian-sarge. The used gcc is
> 
> gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
> 
> the result of make gives a result like that:
> alfred@tux:/usr/local/src/tinycobol-0.62/compiler$ make
> gcc -I/usr/include -I/usr/local/include -I../lib -I../ -c scan.c
> scan.c:1060: error: Syntaxfehler before "YY_PROTO"
> scan.l:120: error: Syntaxfehler before "switch"
> scan.l:123: error: redefinition of `yy_start'
> scan.c:272: error: `yy_start' previously defined here
> scan.l:123: Warnung: data definition has no type or storage class
> scan.l:124: error: Syntaxfehler before "break"
> 
> Is anybody out there, who can give me a hint ?


I think this a problem with GCC 3.3.x relating to the following 'define'.

$grep -n YY_PROTO *.l
scan.l:59:#define YY_DECL int yylex2 YY_PROTO((void))
scan.l:741:int yylex YY_PROTO((void))

I seams to work fine with versions prior to GCC 3.3 .

No idea why this is a problem, nor how to fix it.

Maybe some thing to do with the C99 standard again.

Re: [Tiny-cobol-users] Re: Re: Can i call DB2 database from tinyCOBOL

[nikil c. <nik...@ya...>]

Hi ALL,

Once again thanks for information. I am trying to use
redhat 8.0 along with DB2 7.2 installed on windows
machine. With respect to my configuration can you tell
me how i can proceed with compiling and running cobol
programs which are accessing DB2 data.
Can u tell me where can i download DB2 IBM application
development client package and Sample IBM COBOL
programs. Looking forward for response.

Thanks & Regards,
Nikil

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: [Tiny-cobol-users] STRING problem (DELIMITED BY SPACES)

[David E. <de...@us...>]

Sorry the first messege got truncated.

Carlos Gomes wrote:

 > String verb that has strage output has no
 > DELIMITED in first token (by default DELIMITED
 > BY SIZE). DELIMITED BY SPACES is used only
 > in WTEXT1 token (with a value of "12345     ").
 > It seems that using DELIMITED BY SPACES
 > only in one token does the compiler to use
 > this option in every token of the command.
 >
 > STRING
 > "INSERT INTO TEST " , <<<--- No DELIMITED (Default BY SIZE)
 > ",",
 > W9,
 > ",",
 > WTEXT1 DELIMITED BY SPACES,
 > ");"
 > INTO WRESULT.
 >
 > Result:
 > INSERT,999,12345);
 >
 > Using DELIMITED BY SIZE in first token gives the correct result.
 >
 > STRING
 > "INSERT INTO TEST " DELIMITED BY SIZE,
 > ",",
 > W9,
 > ",",
 > WTEXT1 DELIMITED BY SPACES,
 > ");"
 > INTO WRESULT.
 >
 > Result:
 > INSERT INTO TEST ,999,12345);
 >
 > It looks like default DELIMITED BY SIZE doesn´t
 > be use by TC in this case.

I do not agree.

If you look at the syntax below, the 'DELIMITED' phrase of the 'STRING'
statement can have more than one argument (ie. {identifier-1 |
literal-1}...).
Thus the "INSERT INTO TEST " literal is part of the 'DELIMITED BY
SPACES' phrase.

The COBOL 89 draft standard (not in COBOL 85) states that if (and only
if) the last token before the INTO phrase, does not have a 'DELIMITED'
clause, then that token(s) defaults to a 'DELIMITED BY SIZE'

Thus in the above examples the '");" INTO WRESULT' is equivalent to
'");" DELIMITED BY SIZE INTO WRESULT'.

I've also compiled and run the sample program provided, using an old
commercial COBOL compiler. It's output is identical to TC.

So unless some one can produce proof to the contrary, using a commercial
grade COBOL compiler, I think we can put this matter to rest.


The COBOL 89 draft standard:

14.10.39  STRING statement
...
14.10.39.1 General format
...
Syntax:
STRING {
{identifier-1 | literal-1}...
DELIMITED [BY]
{identifier-2 | literal-2 | SIZE }
}...
INTO identifier-3
...

4.10.39.2 Syntax rules
...
8) The DELIMITED phrase may be omitted only immediately preceding the 
INTO phrase. If it is omitted, DELIMITED BY SIZE is implied.
...

Re: [Tiny-cobol-users] STRING problem (DELIMITED BY SPACES)

[David E. <de...@us...>]

Carlos Gomes wrote:

 > String verb that has strage output has no
 > DELIMITED in first token (by default DELIMITED
 > BY SIZE). DELIMITED BY SPACES is used only
 > in WTEXT1 token (with a value of "12345     ").
 > It seems that using DELIMITED BY SPACES
 > only in one token does the compiler to use
 > this option in every token of the command.
 >
 > STRING
 > "INSERT INTO TEST " , <<<--- No DELIMITED (Default BY SIZE)
 > ",",
 > W9,
 > ",",
 > WTEXT1 DELIMITED BY SPACES,
 > ");"
 > INTO WRESULT.
 >
 > Result:
 > INSERT,999,12345);
 >
 > Using DELIMITED BY SIZE in first token gives the correct result.
 >
 > STRING
 > "INSERT INTO TEST " DELIMITED BY SIZE,
 > ",",
 > W9,
 > ",",
 > WTEXT1 DELIMITED BY SPACES,
 > ");"
 > INTO WRESULT.
 >
 > Result:
 > INSERT INTO TEST ,999,12345);
 >
 > It looks like default DELIMITED BY SIZE doesn´t
 > be use by TC in this case.

I do not agree.

If you look at the syntax below, the 'DELIMITED' phrase of the 'STRING' 
statement can have more than one argument (ie. {identifier-1 | 
literal-1}...).
Thus the "INSERT INTO TEST " literal is part of the 'DELIMITED BY 
SPACES' phrase.

The COBOL 89 draft standard (not in COBOL 85) states that if (and only 
if) the last token before the INTO phrase, does not have a 'DELIMITED' 
clause, then that token(s) defaults to a 'DELIMITED BY SIZE'

Thus in the above examples the '");" INTO WRESULT' is equivalent to 
'");" DELIMITED BY SIZE INTO WRESULT'.

I've also compiled and run the sample program provided, using an old 
commercial COBOL compiler. It's output is identical to TC.

So unless some one can produce proof to the contrary, using a commercial 
grade COBOL compiler, I think we can put this matter to rest.


The COBOL 89 draft standard:

14.10.39  STRING statement
...
14.10.39.1 General format
...

[Tiny-cobol-users] does htcobol 0.62 work with gcc 3.3.5 ?

[Alfred C. <alf...@t-...>]

Hi,

i tried to compile the stable version of htcobol 0.62 within the actual=20
debian-sarge. The used gcc is

gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
Copyright =A9 2003 Free Software Foundation, Inc.

the result of make gives a result like that:
alfred@tux:/usr/local/src/tinycobol-0.62/compiler$ make
gcc -I/usr/include -I/usr/local/include -I../lib -I../ -c scan.c
scan.c:1060: error: Syntaxfehler before "YY_PROTO"
scan.l:120: error: Syntaxfehler before "switch"
scan.l:123: error: redefinition of `yy_start'
scan.c:272: error: `yy_start' previously defined here
scan.l:123: Warnung: data definition has no type or storage class
scan.l:124: error: Syntaxfehler before "break"

Is anybody out there, who can give me a hint ?

Thanks,
Alfred