Menu
▾
▴
tiny-cobol-users
|
From: vgkdinavahi <vgk...@in...> - 2003-09-25 09:22:50
|
we found a problem with tinycobol divide werb that if used divide syntax to get remainder of the below statement the value is as 01 instead of 11, any one can solve the problem? Example: divide 23 by 12 giving value remainder rem. if any value divided by 12 and its remainder is 11 tinycobol is showing the remainder is 1 please verify the same. Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for for Air Tickets on Air Sahara Flights at Prices Lower Than Before. Just log on to http://airsahara.indiatimes.com and Bid Now! |
|
From: daniel b. <db...@ho...> - 2004-02-20 19:58:17
|
buenas tardes estoy utilizando el tinycobol 6.1 para linux pero se me ha dificultado el cargarlo en el computador si ustedes fiuesen tan amables de decirmen los pasos que debo realixzar les agrdeceria muchisiiimo muchas gracias _________________________________________________________________ MSN Amor: busca tu ½ naranja http://latam.msn.com/amor/ |
|
From: Hudson R. <hud...@gm...> - 2004-03-05 03:40:34
|
Hi Daniel, En: I will translate your message, but if possible try to translate your me= ssages to english language, because it will be more acceptable. PtBR: Eu estou traduzindo sua mensagem, mas se poss=EDvel tente traduzir su= as mensagens para a lingua ingl=EAsa por que elas ser=E3o mais aceit=E1veis En: (I have more things to say after more below) PtBR: (Eu tenho mais coisas para dizer mais abaixo) > buenas tardes > > estoy utilizando el tinycobol 6.1 para linux pero se me ha dificultado > el cargarlo en el computador si ustedes fiuesen tan amables de > decirmen los pasos que debo realixzar les agrdeceria muchisiiimo > muchas gracias =3D=3D Translation =3D=3D Good Afternoon, I'm using the TinyCOBOL 0.61 to linux but I'm having some problems to insta= ll it in my PC. If yours can give me the basic steps I'm stay very happy, Thank you. =3D=3D End =3D=3D En: My answer to your question is: PtBR: Minha resposta para sua pergunta =E9: En: 1. Look at in our resources webpage at http://tinycobol.org/resources.h= tml. You will found a document in spanish called "Introduction to COBOL and= TinyCOBOL" translated by Juan J. Martinez. Read it and try to install TC. PtBR: 1. D=EA uma olhada na nossa p=E1gina de recursos em http://br.tinycobol.org/recursos.html. Voc=EA encontrar=E1 um documento em = espanhol chamado "Introdu=E7=E3o ao COBOL e ao TinyCOBOL" traduzido por Jua= n J. Martinez. Leia-o e tente instalar o TinyCOBOL. En: 2. I'm developing a TinyCOBOL FAQ and you can found it in http://hudson= .tinycobol.org/tmp/tc/faq.html PtBR: 2. Eu estou desenvolvendo um FAQ do TinyCOBOL e voc=EA pode encontr= =E1-lo em http://hudson.tinycobol.org/tmp/tc/faq.html En: 3. Read the TinyCOBOL User Manual that was been developed in http://www= .nanatree.com/tinycobol/index.html PtBR: 3. Leia o Manual do Usu=E1rio TinyCOBOL que est=E1 sendo desenvolvido= em http://www.nanatree.com/tinycobol/index.html=20 En: Hope this helps, PtBR: Espero que isto ajude, Hudson ------------------------------------------------------------------------ Hudson Reis http://hudson.tinycobol.org |
|
From: vgkdinavahi <vgk...@in...> - 2004-06-15 13:23:30
|
Hi, I wants to bring to your notice that in tinycobol the 78 level is not supporting presently which is supporting by Micro Focus cobol is any body can able to support the above level in tinycobol. We are having Micro Focus cobol def file which is containing the 78 level which is to be converted to tinycobol please help me. Thanking you, Venu Gopala Krishna. Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now! |
|
From: Hudson R. <hud...@gm...> - 2004-06-17 03:06:35
|
Hi Venu, > I wants to bring to your notice that in tinycobol the 78 level is > not supporting presently which is supporting by Micro Focus cobol is > any body can able to support the above level in tinycobol. The 78 level won't be added in TC because it's a MF extension and it doesn't part of the COBOL 85 standard. > We are having Micro Focus cobol def file which is containing the 78 > level which is to be converted to tinycobol please help me. How can I help you? Could you post in list a test program or the program that have the 78 level? Hope this helps, Hudson ------------------------------------------------------------------ Hudson Reis http://www.hreis.net |
|
From: Ravi K. <ra...@gr...> - 2004-07-13 16:25:05
|
Hello,<BR> <BR> I am a newbie as far as tiny cobol is concerned. Its really great to see that so much of effort is put in by highly talented individuals to make a cobol compiler freely available.<BR> <BR> Is tiny cobol multiuser? Also is there any utility like supersort/powersort in tinycobol?<BR> <BR> Thanks and Regards <BR> Ravi Katti <BR> |
|
From: Hudson R. <hud...@gm...> - 2004-07-14 02:57:46
|
Hi Ravi, > Hello, > > I am a newbie as far as tiny cobol is concerned. Its really great to > see that so much of effort is put in by highly talented individuals to > make a cobol compiler freely available. Man, we have a huge way to finish TC. > Is tiny cobol multiuser? Also is there any utility like > supersort/powersort in tinycobol? At this moment, TC is not multiuser. TC doesn't has the utilities supersort or powersort, but TC does support SORT files(verbs SORT, RELEASE, RETURNING, SD...), but only generating sequential files, not storing the data in the memory like the commercial COBOL compilers. Hope this helps. Hudson ------------------------------------------------------------------ Hudson Reis http://www.hreis.net |
|
From: RAFAEL r. <raf...@la...> - 2005-10-07 16:47:32
|
Hi, We aer need help to do an program inc tiny cobol for Windows to do invo= ice, with TCL-TK Thaks, a lot of. rafael reyes Chile TRADUCCION: Necesitamos ayuda para confeccionar un programa en tiny cobol con TCL-T= k para windows que emita e imprima una factura. Muchas gracias =A1S=E9 listo! Contrata el antivirus http://www.pandasoftware.es/tienda= /?idpers=3D109&track=3D13920 |
|
From: John R. C. <jo...@we...> - 2005-10-08 20:58:38
|
On Friday 07 October 2005 04:46 pm, RAFAEL reyes wrote: > Hi, > > We aer need help to do an program inc tiny cobol for Windows to do invoice, > with TCL-TK > > Thaks, a lot of. > > rafael reyes Chile > Do you have TinyCOBOL installed on your system? Do you have Tcl/Tk installed on your system? Do you have the Expect package installed on your system? Was the file where the invoice information is available created by TinyCOBOL? If so can you show us the file layout (FD)? Is there a customer file that is to be used when creating invoices.? It is possible to use both Tcl/Tk and COBOL in the same application but the connection between the two programs is not trivial. Perhaps someone who has mastery of Spanish could be of more help than I. Any volunteers? -- John Culleton Books with answers to marketing and publishing questions: http://wexfordpress.com/tex/shortlist.pdf Book coaches, consultants and packagers: http://wexfordpress.com/tex/packagers.pdf |
|
From: Marcello M. <mar...@fo...> - 2005-10-09 11:40:47
|
> > We aer need help to do an program inc tiny cobol for Windows to do > invoice, with TCL-TK > > Thaks, a lot of. > > rafael reyes Chile > I'm handling the same matter. The first thing I did was separating cobol screen handling from procedural sources. In this way the computing program does all i-o and other data handling. It just CALLs screen program to get user interface. Second thing I did was writing a cobol source which translates cobol screens sentences to tcl sources for USING-FROM-GIVING handling. Now, when a "procedural" source needs user input, it just writes data, to modify-confirm, to a line sequential file; does a system call to tcl interpreter which reads and eventually rewrites the file; finally, procedural cobol re-reads the file and handles data. Unfortunately, the calling program is unable to wait for tcl interpreter (system call) exit. So it just manages a wait-read-wait cycle for a second line sequantial file, handled by tcl, where an exit status is written. The solution appears to be a direct call to tcl's (not a system call) with a direct return-status, but. so far, I've not found the solution. Anyone has any idea? Marcello |
|
From: John R. C. <jo...@we...> - 2005-10-09 12:23:57
|
> > > > rafael reyes Chile > > I'm handling the same matter. > The first thing I did was separating cobol screen handling from procedural > sources. > In this way the computing program does all i-o and other data handling. It > just CALLs screen program to get user interface. > Second thing I did was writing a cobol source which translates cobol > screens sentences to tcl sources for USING-FROM-GIVING handling. > Now, when a "procedural" source needs user input, it just writes data, to > modify-confirm, to a line sequential file; does a system call to tcl > interpreter which reads and eventually rewrites the file; finally, > procedural cobol re-reads the file and handles data. > Unfortunately, the calling program is unable to wait for tcl interpreter > (system call) exit. So it just manages a wait-read-wait cycle for a second > line sequantial file, handled by tcl, where an exit status is written. > The solution appears to be a direct call to tcl's (not a system call) with > a direct return-status, but. so far, I've not found the solution. > Anyone has any idea? > Marcello I have ideas but thus far no success. First, the tcl/tk program wants to be in charge. We want the COBOL program to be in charge. Second, a good application will provide instant data checking. This means that either the Tcl program checks the data or else there is interaction between the two programs on a field by field basis. Some part of the solution may require the use of the Expect package. But wait, it gets worse. Interactive applications are essentially event driven. A person fills out a field and something happens. This may not occur in any predictable order. COBOL is driven by its internal flow of logic. Perhaps the solution is a kind of message handling process. Something happens in the Tcl/Tk program. A message is sent to the COBOL program, containing a field identifier and a string of data. The COBOL program accepts this message, and performs the necessary logic depending on the field identifier. Then it sends a message back to the Tcl/Tk program. The tcl logic is reduced to sending the identifier and the field. Essentially the two programs are co-routines, with heavy interaction. Creating tcl code on the fly is interesting but is not a solution the heavy interaction problem as I see it. Like it or not the windowed program has to be in charge and start up the COBOL program, not vice versa. Coding Tcl is tough enough.Coding it in the COBOL program just adds another layer of complexity. So my proposed solution requires: a: The Tcl program spawns the COBOL program. b: The Expect package is used. c: The action taken as each field is exited is a message to the COBOL program. The response is either a "OK" message that the user never sees or an "ERROR" message. That is my plan anyhow. I'll let you know how it works out. Too bad the COMMUNICATION SECTION was abolished. We never needed it before, and now we need it and don't have it. If I have any success I'll post. Don't hold your breath. And my solution will be Linux-only. Windows is just too difficult for me. John Culleton Books with answers to marketing and publishing questions: http://wexfordpress.com/tex/shortlist.pdf Book coaches, consultants and packagers: http://wexfordpress.com/tex/packagers.pdf |
|
From: Rildo J. C. P. <ril...@gl...> - 2005-10-10 01:37:14
|
Hi all, John R. Culleton wrote: >>>rafael reyes Chile >>> >>> >>I'm handling the same matter. >>The first thing I did was separating cobol screen handling from procedural >>sources. >>In this way the computing program does all i-o and other data handling. It >>just CALLs screen program to get user interface. >>Second thing I did was writing a cobol source which translates cobol >>screens sentences to tcl sources for USING-FROM-GIVING handling. >>Now, when a "procedural" source needs user input, it just writes data, to >>modify-confirm, to a line sequential file; does a system call to tcl >>interpreter which reads and eventually rewrites the file; finally, >>procedural cobol re-reads the file and handles data. >>Unfortunately, the calling program is unable to wait for tcl interpreter >>(system call) exit. So it just manages a wait-read-wait cycle for a second >>line sequantial file, handled by tcl, where an exit status is written. >>The solution appears to be a direct call to tcl's (not a system call) with >>a direct return-status, but. so far, I've not found the solution. >>Anyone has any idea? >>Marcello >> >> > >I have ideas but thus far no success. First, the tcl/tk program >wants to be in charge. We want the COBOL program to be in >charge. Second, a good application will provide instant data >checking. This means that either the Tcl program checks the >data or else there is interaction between the two programs on a >field by field basis. > > > I have written a very simple interface between TC (TinyCobol) and tcl/tk which does exactly that: the cobol program is in charge and have the control. I have also written a short tutorial (in portuguese only for now, sorry, but full of pictures) on how to do several kinds of interactions back and forth from/to tcl variables. You may find the sources of my "tctcl" interface from my local TC cvs (see below for directions) at the directory development/test.code/00_FernandoWuthstrack/tcl. You may also get the tutorial at http://pragana.net/cobol/TC-gui.pdf (ready to read/print) or http://pragana.net/cobol/TC-gui.odt for a OpenOffice.org source of the tutorial. With this interface, you are able to create your GUIs with any Tk gui-builder like Visual Tcl, SpecTcl, TclProE, or others. Please see some examples I've included. By the way, I'm the originator and used to lead this (TinyCobol) project, and I'm also a tcl fan, so if you want to ask anything more, I feel home with this combination (TC+tcl/tk). >Some part of the solution may require the use of the Expect >package. > >But wait, it gets worse. Interactive applications are >essentially event driven. A person fills out a field and >something happens. This may not occur in any predictable order. >COBOL is driven by its internal flow of logic. > >Perhaps the solution is a kind of message handling process. >Something happens in the Tcl/Tk program. A message is sent to >the COBOL program, containing a field identifier and a string of >data. The COBOL program accepts this message, and performs the >necessary logic depending on the field identifier. Then it sends >a message back to the Tcl/Tk program. The tcl logic is reduced >to sending the identifier and the field. Essentially the two >programs are co-routines, with heavy interaction. > >Creating tcl code on the fly is interesting but is not a >solution the heavy interaction problem as I see it. Like it or >not the windowed program has to be in charge and start up the >COBOL program, not vice versa. Coding Tcl is tough enough.Coding >it in the COBOL program just adds another layer of complexity. > >So my proposed solution requires: >a: The Tcl program spawns the COBOL program. >b: The Expect package is used. >c: The action taken as each field is exited is a message to the >COBOL program. The response is either a "OK" message that the >user never sees or an "ERROR" message. > >That is my plan anyhow. I'll let you know how it works out. Too >bad the COMMUNICATION SECTION was abolished. We never needed it >before, and now we need it and don't have it. > >If I have any success I'll post. Don't hold your breath. And my >solution will be Linux-only. Windows is just too difficult for >me. > > To grab my local cvs sources, you may use the following: CVSROOT=:pserver:ano...@pr...:/mnt/cvspublic cvs login (with an empty passord) cvs co development My development platform is Linux, but I expect most of this to work flawlessly under Windows too. If it doesn't, you may ask me for assistance. best regards, Rildo -- ------------------------------------------------------------------ Rildo Pragana FPGA/uControllers * Linux * tcl/tk R.Joaquim Nabuco,92/1102 Derby http://www.pragana.net Recife, PE - Brazil 52011-000 +55-81-3223-5694 / 8837-6122 |
|
From: John R. C. <jo...@we...> - 2005-10-10 12:24:53
|
On Monday 10 October 2005 01:37 am, Rildo J. C. Pragana wrote:
> Hi all,
>
>
> To grab my local cvs sources, you may use the following:
>
> CVSROOT=:pserver:ano...@pr...:/mnt/cvspublic
> cvs login
> (with an empty passord)
> cvs co development
>
> My development platform is Linux, but I expect most of this to work
> flawlessly under Windows too. If it doesn't, you may ask me for assistance.
>
> best regards,
> Rildo
Your effort is far more advanced than mine.
Perhaps the gentleman from Chile can puzzle his way through the
documentation in Portugese, since the languages are similar in
many ways.
I am taking a simpler route for now. Here are two tiny test
programs using tcl, expect and COBOL. They work in TC or
OpenCOBOL. They are at this point just proof of concept. The
tcl program is activated and is spawns the COBOL program. The
two exchange a few messages.
-----------------------------
000010 IDENTIFICATION DIVISION.
000020 PROGRAM-ID. TEMPLATE.
000030 AUTHOR. JOHN CULLETON.
000040 INSTALLATION. WEXFORDPRESS
000045 Eldersburg MD.
000050*REMARKS.
000060* THIS IS A TEMPLATE FOR OPEN COBOL AND HTCOBL.
000070 ENVIRONMENT DIVISION.
000080
000090 CONFIGURATION SECTION.
000100 SOURCE-COMPUTER.
000110 Linux.
000120 OBJECT-COMPUTER.
000230 Linux.
000140
000150 INPUT-OUTPUT SECTION.
000160 FILE-CONTROL.
000170 SELECT PRINTFILE ASSIGN TO "testit"
ORGANIZATION IS LINE SEQUENTIAL.
000180 DATA DIVISION.
000190
000200 FILE SECTION.
000210 FD PRINTFILE.
01 PRINTREC PIC X(80).
000220 WORKING-STORAGE SECTION.
000230 01 SPECREC PIC XXX.
000240 PROCEDURE DIVISION.
000250 001-MAIN-PROCEDURE.
OPEN OUTPUT PRINTFILE.
000260 DISPLAY "foo".
ACCEPT SPECREC.
MOVE SPECREC TO PRINTREC.
WRITE PRINTREC.
DISPLAY "OK".
ACCEPT SPECREC.
IF SPECREC EQUAL "end"
MOVE SPECREC TO PRINTREC
WRITE PRINTREC.
CLOSE PRINTFILE.
000270 STOP RUN.
-----------------------------
#!/usr/local/bin/expect -f
spawn cobprog
expect "foo"
send -- "bar\r"
expect "OK"
send -- "end\r"
--------------------------
--
John Culleton
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X