I didn't release any new version after. so that is latest
Is the source up to date?
even in 2022 the mostly used tool for debugging is "DISPLAY" :-) Any weeks ago i improved a new modul and wanted to debug it with TPD. Didn't work because the screen got scrumbled and the managing of multiple dimensions and qualified fields doesn't exist. I've looked into the source and long time didn't understand the reason. Now i understand the reason why and i have an idea to solve it. I realized, that the scrumbled screen is a behaviour of xfce-terminal. On a pure console (reached with ctrl+alt+f1)...
Improvements are always good as this software still stands as "Beta" and has mostly one person working on it, you may want to have a look at debugging with different options. At least for GnuCOBOL you can also use GDB + cbl-gdb (biggest cons: handling of OCCURS DEPENDING ON and of level-88 variables, for some: only works with GCC) or using the debugger from Gix IDE (which is said to be available as separate project with a defined client interface soon - its biggest cons are "no terminal interface...
anybody here who works on improving the TPD ? As far as i see there are many open points to do -managing of qualified fields with in/of -managing multiple dimensions of tables/arrays -debugger output on other terminal than the debugee -and further steps points If nobody does, i'd improve the basically file ARK-FIELD bye, Alfred
Maybe a typo by changing a few lines. It seems strange. I'll take a look these days.
Hi Federico, I downloaded the latest tp-debugger and tried to use it on windows 11. The debugger is not working as shown on the screenshot attached, version TP-COBOL-DEBUGGER release 2.2.5 Package 23-02-2020 doesn't work but version TP-COBOL-DEBUGGER release 2.2.4 Package 22-02-2020 works fine. I don't know what was changed but it broke the debugger.
I' m sorry you wasn't able to run the code. Having a source of your code could be useful to investigate why it doesn't recognize the sectios. however not only windows code but pure 100% cobol code so anything where who knows the language can read what is performs
Yes could you please provide a cobol sample here ? It seems to be a wrong sequential format that tp-cobol-debugger doesn't recognize. Did you test it without data evaluating ? e.g. invoke the animator with -d command line option to turn off this feature.
It is written in COBOL and GnuCOBOL reads both dos- und unix-style EOL in with LINE SEQUENTIAL files which are used here - so that is likely not the problem. If you can provide a minimal sample including the commands you've executed and the results you see then someone could recheck and possibly help you. Note: If you don't need a very COBOL debugger you could also debug via a GDB frontend in VSCodium for GnuCOBOL (two extensions avaialable). There's also a gdb extension that works on the command...
Hi I am unable to animate any cobol program I have.. error : Missing WORKING-STORAGE for data evaluating.. 100% my programs have a WORKING-STORAGE and can be compiled under gnucobol 3 or even 4 . (platform Debian Testing) is this a "windows" only program eg . looking for ^M on the lines ? thx eddy
adjust statement list
Ok, It was completely stupid thing. I had GnuCobol configures with flag --without-db. I installed vbisam and now its works normally. Thank you. Miha
Yes. I think so too
Yes. I think so tooInviato dal mio dispositivo Huawei-------- Messaggio originale --------Oggetto: [tp-cobol-debugg:discussion] Debugger Support for GnuCobol 3.0Da: Miha Pečnik pecnikmiha@users.sourceforge.netA: "[tp-cobol-debugg:discussion] " general@discussion.tp-cobol-debugg.p.re.sourceforge.netCC: Hi, Yes I compiled all modules with cobc without parameters. There is no file named temp. Compiler creates directory named temp, but cant create .dat file. I also changed compiler that tries to create...
Hi, Yes I compiled all modules with cobc without parameters. There is no file named temp. Compiler creates directory named temp, but cant create .dat file. I also changed compiler that tries to create .dat file in other directory, but result is the same. I think there's something wrong with my environment. Will post what was wrong, if somebody else will experience the same problem. Thank you, Miha
Somehow the answer from Federico got into a new topic, adding it back here where it belongs "manually: The animator create the temp directory where it writes the temporary files... unable...strange is there already a single file that use the name temp ? also let's try to create yourself the ./temp and check for issues About the compilation all modules except animator.cbl must be compiled with cobc animate.cbl without any parameteres (animatre..animload animdata .ecc.). the animator must be an executable...
You have to move "continue" between perform and end-perform since.the latest.compiler required that statement. I suppose that solve the trouble
Thank you. Compiling the Animator Testing the Animator TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017 Federico Priolo TP ONE SRL Animator.inf file used is: animator.inf invoked argument(S) for the animator: compile main executable (.exe).. Unable to create:./temp/322073.dat libcob: warning: implicit CLOSE of ARK-OUT ('test.ani') libcob: warning: implicit CLOSE of ARK-IN ('test.cbl') lcompall.sh: line 38: ./test: No such file or directory cat: telco.txt: No such file or...
You have to move "continue" between perform and end-perform since.the latest.compiler required that statement. I suppose that solve the troubleInviato dal mio dispositivo Huawei-------- Messaggio originale --------Oggetto: [tp-cobol-debugg:discussion] Debugger Support for GnuCobol 3.0Da: Miha Pečnik pecnikmiha@users.sourceforge.netA: "[tp-cobol-debugg:discussion] " general@discussion.tp-cobol-debugg.p.re.sourceforge.netCC: Hello. I'm also having problems with running animator. Im using GnuCobol 3.2...
Hello. I'm also having problems with running animator. Im using GnuCobol 3.2 on CentOS 6. When I start lcompall.sh I get : Compiling the Animator animator.cbl: in section 'ELABORA': animator.cbl: in paragraph 'TRATTA': animator.cbl:845: warning: inline PERFORM without imperative statement used animator.cbl: in section 'APERTURE': animator.cbl:1120: warning: inline PERFORM without imperative statement used analyzer.cbl: in section 'INIZIO': analyzer.cbl: in paragraph 'TRATTA-IN': analyzer.cbl:654:...
Federico, I think it would be very useful to change animator.inf to remove the COBC option (only use it as a fallback if COBC_FLAGS is not set) and to have two variables. Then in the animator: check if COBC_FLAGS is set (=new animator.inf), if yes then string "cobc " cobc_flags " " cobc_flags_compile where you currently use COBC and "cobc -E " cobc_flags where you currently use cobc -E. In the case of this topic they would be defined as follows: # common flags that are always passed to the compiler...
TEST.CBL is the same from the tp-cobol-debugger package ? If not starting could be for the cyle perform.. but could you please do a test with -d (WITHOUT DATA analysys) ?
I have to do the same test with the -ext fix you did. Tell me actually did solved with work around by compiling the .ani file ?
Hi, you meen in the animator.inf? We do: cat /opt/gd/animator.inf | grep ^COBC COBC= -ext lib -D 'C-OBS-COMPILER=2' -K SQLADR -K SQLADRVC -K SQLBEX -K OBSCONNECT -K INIT_ERRNO -I/destination/to/src -save-temps -g -debug -Wall Hans
Usage: animator cobolsource [options] cobolsource:source.cbl/cpy/src (when missing ".cbl" is added by default....) Options: -h This support panel -d Turn off data analisys -c Do not compile the generated .ani source -k/-K keep the generated cobol .ani source -f Use constants names for temporary files -F Force to free format -S Use stop run to evaluate exit -x Build an executable program -A Perform only structure control flow graph -v Turn on verbose -o add native option invoking the compiler (eg:...
Hi, vsoft03_gnubf2> animator ST409.cob -x -v -o 'ext lib' TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017 Federico Priolo TP ONE SRL Animator.inf file used is: /opt/gd/animator.inf invoked argument(S) for the animator: compile main executable (.exe).. show verbose process during make add invoking the compiler (eg: -o'-Wall') the startup variable is:start--x.inf the control variable is:cycle--x.inf Processing open file.. Deleting flat file for data table.../obs/gnubf2/tmp/591734.var...
The compile works within the animator: vsoft03_gnubf2> animator -x -v ST409.cob -extlib TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017 Federico Priolo TP ONE SRL Animator.inf file used is: /opt/gd/animator.inf invoked argument(S) for the animator: compile main executable (.exe).. show verbose process during make Unrecognisez option in command line: 'e' vsoft03_gnubf2> animator -x -v ST409.cob TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017 Federico...
You should use -ext <extension> add file extension for resolving COPY invoking the compiler.
Hi, about Benedicts problem: echo $COBCPY /destination/to/src/subdir:/destination/to/src /destination/to/src/subdir> animator -x ST409.cob TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017 Federico Priolo TP ONE SRL Animator.inf file used is: /opt/gd/animator.inf invoked argument(S) for the animator: compile main executable (.exe).. ST409.cob:43: error: CECONFI: No such file or directory ST409.cob:52: error: CWALLGEM: No such file or directory ST409.cob:53: error: CWINTME:...
Yes that is what i meant... justo to give you an example on my windows pc I used to include my copy... SET COB_COPY_DIR=C:\OPENCOBOL\COPY;F:\STIPEURO\CBL;F:\STIPEURO\CPY
Yes that is what i meant... justo to give you an example on my windows pc I used to include my copy... SET COB_COPY_DIR=C:\OPENCOBOL\COPY;F:\STIPEURO\CBL;F:\STIPEURO\CPY
Hi, one more information. When I start after the "animator -x test.cbl" the programm "test", then the debuggerscreen appears: vsoft03_gnubf2> ./test TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 000302 01 WS-Output. 000303 05 Header-1 Pic X(70) Value 000304 " Time Rate | Price Btax Dtax | 000305- " Output". 000306 05 Header-2 Pic X(70) Value "-------------+----------------------------------------+- "------------". < 000309 05 Detail-Line. 000310 10 Pic X(01) Value Space. 000311 10 Time-Out Pic...
Hi, yes, test.cbl is from the cobol-tp-debugger package. vsoft03_gnubf2> animator -x -d test.cbl TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017 Federico Priolo TP ONE SRL Animator.inf file used is: /opt/gd/animator.inf invoked argument(S) for the animator: compile main executable (.exe).. do not use the data analysis.... vsoft03_gnubf2> there is no difference. The Debugger-Screen does not appear. The last lines - if I use the verbose-flag - is: Done...just compiling the...
TEST.CBL is the same from the tp-cobol-debugger package ? If not starting could be for the cyle perform.. but could you please do a test with -d (WITHOUT DATA analysys) ? Federico Priolo Amministratore unico TP ONE SRL VIA PARADISO 6 02034 MONTOPOLI DI SABINA Cell.: 348-6063530 federico.priolo@tp-one.it P. Iva 01126870573 Cap. Soc 20.000,00 Int. vers. Reg. delle Imprese di Rieti REA: RI70185 email: tpone@legamail.it MESSAGGIO ORIGINALE Hi, the problem is not solved. The fix removes the errormessages...
Hi, the problem is not solved. The fix removes the errormessages from "cobc -E" ("No such file or directory"). But the main problem is, that the debugger will not start the debugging-screen. animator -x -k test.cbl ... Building.. cobc -x test.ani -ext lib -D 'C-OBS-COMPILER=2' -K SQLADR -K SQLADRVC -K SQLBEX -K OBSCONNECT -K INIT_ERRNO -I/obs/gnubf2/src -save-temps -g -debug -Wall manual compiling of the .ani-file brings no errors: vsoft03_gnubf2> cobc -x test.ani -ext lib -D 'C-OBS-COMPILER=2' -K...
I have to do the same test with the -ext fixed you did. Tell me actually did solved with work around by compiling the .ani file ? Federico Priolo Amministratore unico TP ONE SRL VIA PARADISO 6 02034 MONTOPOLI DI SABINA Cell.: 348-6063530 federico.priolo@tp-one.it P. Iva 01126870573 Cap. Soc 20.000,00 Int. vers. Reg. delle Imprese di Rieti REA: RI70185 email: tpone@legamail.it MESSAGGIO ORIGINALE and one more information: debuging the test.cbl does not work, too: vsoft03_gnubf2> animator -x test.cbl...
and one more information: debuging the test.cbl does not work, too: vsoft03_gnubf2> animator -x -v test.cbl TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017 Federico Priolo TP ONE SRL Animator.inf file used is: /opt/gd/animator.inf invoked argument(S) for the animator: compile main executable (.exe).. show verbose process during make the startup variable is:start--x.inf the control variable is:cycle--x.inf Processing open file.. Deleting flat file for data table.../obs/gnubf2/tmp/443706.var...
and one more information: debuging the test.cbl does not work, too: vsoft03_gnubf2> animator -x test.cbl TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017 Federico Priolo TP ONE SRL Animator.inf file used is: /opt/gd/animator.inf invoked argument(S) for the animator: compile main executable (.exe).. using previous compiler syntax for data analysis.(-000000001) vsoft03_gnubf2> animator -x -v test.cbl TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017...
Hi, a little bit more informations: first: animator ST409.cob -x -v -o 'ext lib' does not pass the options to the "cobc -E" statement. If I will run the "cobc -E" standalone, I will get the same errors: vsoft03_gnubf2> cobc ST409.cob -E > /obs/gnubf2/tmp/035580.var ST409.cob:52: error: CWALLGEM: No such file or directory ST409.cob:53: error: CWINTME: No such file or directory ST409.cob:54: error: CVRELEASE: No such file or directory Then I add tempory the "-ext"-option in animator.cbl: 012800 STRING...
Hi, a little bit more informations: first: animator ST409.cob -x -v -o 'ext lib' does not pass the options to the "cobc -E" statement. If I will run the "cobc -E" standalone, I will get the same errors: vsoft03_gnubf2> cobc ST409.cob -E > /obs/gnubf2/tmp/035580.var ST409.cob:52: error: CWALLGEM: No such file or directory ST409.cob:53: error: CWINTME: No such file or directory ST409.cob:54: error: CVRELEASE: No such file or directory Then I add tempory the "-ext"-option in animator.cbl: 012800 STRING...
Hi, a little bit more informations: first: animator ST409.cob -x -v -o 'ext lib' does not pass the options to the "cobc -E" statement. If I will run the "cobc -E" standalone, I will get the same errors: vsoft03_gnubf2> cobc ST409.cob -E > /obs/gnubf2/tmp/035580.var ST409.cob:52: error: CWALLGEM: No such file or directory ST409.cob:53: error: CWINTME: No such file or directory ST409.cob:54: error: CVRELEASE: No such file or directory Then I add tempory the "-ext"-option in animator.cbl: 012800 STRING...
Hi, vsoft03_gnubf2> animator ST409.cob -x -v -o 'ext lib' TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017 Federico Priolo TP ONE SRL Animator.inf file used is: /opt/gd/animator.inf invoked argument(S) for the animator: compile main executable (.exe).. show verbose process during make add invoking the compiler (eg: -o'-Wall') the startup variable is:start--x.inf the control variable is:cycle--x.inf Processing open file.. Deleting flat file for data table.../obs/gnubf2/tmp/591734.var...
Hi, vsoft03_gnubf2> animator ST409.cob -x -v -o 'ext lib' TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017 Federico Priolo TP ONE SRL Animator.inf file used is: /opt/gd/animator.inf invoked argument(S) for the animator: compile main executable (.exe).. show verbose process during make add invoking the compiler (eg: -o'-Wall') the startup variable is:start--x.inf the control variable is:cycle--x.inf Processing open file.. Deleting flat file for data table.../obs/gnubf2/tmp/591734.var...
Usage: animator cobolsource [options] cobolsource:source.cbl/cpy/src (when missing ".cbl" is added by default....) Options: -h This support panel -d Turn off data analisys -c Do not compile the generated .ani source -k/-K keep the generated cobol .ani source -f Use constants names for temporary files -F Force to free format -S Use stop run to evaluate exit -x Build an executable program -A Perform only structure control flow graph -v Turn on verbose -o add native option invoking the compiler (eg:...
The compile works within the animator: vsoft03_gnubf2> animator -x -v ST409.cob -extlib TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017 Federico Priolo TP ONE SRL Animator.inf file used is: /opt/gd/animator.inf invoked argument(S) for the animator: compile main executable (.exe).. show verbose process during make Unrecognisez option in command line: 'e' vsoft03_gnubf2> animator -x -v ST409.cob TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017 Federico...
Hi, you meen in the animator.inf? We do: cat /opt/gd/animator.inf | grep ^COBC COBC= -ext lib -D 'C-OBS-COMPILER=2' -K SQLADR -K SQLADRVC -K SQLBEX -K OBSCONNECT -K INIT_ERRNO -I/destination/to/src -save-temps -g -debug -Wall Hans
You should use -ext <extension> add file extension for resolving COPY invoking the compiler.</extension>
Hi, about Benedicts problem: echo $COBCPY /destination/to/src/subdir:/destination/to/src /destination/to/src/subdir> animator -x ST409.cob TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017 Federico Priolo TP ONE SRL Animator.inf file used is: /opt/gd/animator.inf invoked argument(S) for the animator: compile main executable (.exe).. ST409.cob:43: error: CECONFI: No such file or directory ST409.cob:52: error: CWALLGEM: No such file or directory ST409.cob:53: error: CWINTME:...
Hi benedict.the.animator.do not use.any other variables so adding.the cpy.it.recognizes animwork.cpy and runs.correctly....how.kind.of grammar did you use to attach the other folders? Maybe Simon.or Brian could give you useful advices. I also suggest to open a thread on gnucobol . Federico
Yes that is what i meant... justo to give you an example on my windows pc I used to include my copy... SET COB_COPY_DIR=C:\OPENCOBOL\COPY;F:\STIPEURO\CBL;F:\STIPEURO\CPY Federico MESSAGGIO ORIGINALE Hi federico, thanks for the fast reply! I don't exactly understand what you mean by: how.kind.of grammar did you use to attach the other folders? I exported the debuggers installation directory /opt/gd which contains the procanim.cpy and workanim.cpy with: export COBCPY="$COBCPY:/opt/gd" and the errors...
Hi federico, thanks for the fast reply! I don't exactly understand what you mean by: how.kind.of grammar did you use to attach the other folders? I exported the debuggers installation directory /opt/gd which contains the procanim.cpy and workanim.cpy with: export COBCPY="$COBCPY:/opt/gd" and the errors regarding those copies where solved. (If you were asking that) But I'll open up a thread on gnucobol regarding this topic, thanks for the hint! Kind Regards
Hi benedict.the.animator.do not use.any other variables so adding.the cpy.it.recognizes animwork.cpy and runs.correctly....how.kind.of grammar did you use to attach the other folders? Maybe Simon.or Brian could give you useful advices. I also suggest to open a thread on gnucobol . FedericoatorInviato dal mio dispositivo Huawei-------- Messaggio originale --------Oggetto: [tp-cobol-debugg:discussion] Debugger Support for GnuCobol 3.0Da: Benedict Rice breis111@users.sourceforge.netA: "[tp-cobol-debugg:discussion]...
Hello again, unfortunately we're facing the next problem when it comes to compiling our Cobolprograms with the animator. I think i'm missing some kind of variable that tells the Debugger where to find our cobol libraries while compiling: #/path/to/source> animator -x ST409.cob TP-COBOL-DEBUGGER release 2.2.3 Package 12-08-2017 Copyright (C) 2010-2017 Federico Priolo TP ONE SRL Animator.inf file used is: /opt/gd/animator.inf invoked argument(S) for the animator: compile main executable (.exe).. **ST409.cob:43:...
A wonderful idea ! A better debugger even more integrated into the compiler is absolutely important ! I also suggest to add the use of some of the TUI-TOOLS that I have created and released (drop-down menus, listboxes, etc.) to make the look more pleasant and professional and mainly to make the debugger better usable.
... and you can find a diagram on how the animator works in the final pages of documentation file at: https://sourceforge.net/projects/tp-cobol-debugg/files/documentation/GC-USING-TP-DEBUGGER-MANUAL-V04-20170114.pdf/download
... and you can find a diagram on how the animator works in the final pages of documentation file at: https://sourceforge.net/projects/tp-cobol-debugg/files/documentation/GC-USING-TP-DEBUGGER-MANUAL-V04-20170114.pdf/download
I think that simply I will change the animator configuration name with some like as "AnimatorConfigurationFile".... depending on running operating system Please use a simple solution that would work everywhere, in this case: ANIM_CONFIG_FILE is both readable and portable. it's time to refresh the project... Yay. Note: there is a new feature in 3.1 (not out yet, so only CI builds available) which would allow a free "go to line NNN" command (from within the same program). As this is absolutely unportable...
I think that simply I will change the animator configuration name with some like as "AnimatorConfigurationFile".... depending on running operating system ...it's time to refresh the project... :-)
I think that simply I will change the animator configuration name with some like as "AnimatorConfigurationFile".... depending on running operating system ...it's time to refresh the project... :-) MESSAGGIO ORIGINALE Yes, the period in the environment variable is sub-optimal. @priolof do you see any option to change this to an underscore (or use both, with the period as fall-back value)? @breis11: COB_ENV_MANGLE should likely work around the issue (but has a global scope). Debugger Support for GnuCobol...
Yes, the period in the environment variable is sub-optimal. @priolof do you see any option to change this to an underscore (or use both, with the period as fall-back value)? @breis11: COB_ENV_MANGLE should likely work around the issue (but has a global scope).
Yes It runs fine under 3.0 Federico Priolo
Thanks for the feedback Simon I am get used with Fujitsu where my licensed version uses 256 as limit. So I can increase it. I will add this as fix. Thanks again.
thanks for the feedback Simon I am get used with Fujitsu where my licensed version uses 256 as limit. So I can increase it. I will add this as fix. Thanks again. Inviato dal mio dispositivo Huawei-------- Messaggio originale --------Oggetto: [tp-cobol-debugg:discussion] Re: Debugger Support for GnuCobol 3.0Da: Simon Sobisch sf-mensch@users.sourceforge.netA: "[tp-cobol-debugg:discussion] " general@discussion.tp-cobol-debugg.p.re.sourceforge.netCC: Federico, can you please recheck? All paths should...
Federico, can you please recheck? All paths should take at least 256 bytes (up to 2048 bytes)!
Hello again, problem is solved. Both errors we're caused because the installation path /opt/gnucoboldebugger/was too long.. Debugger is working now. Thanks again and Kind Regards
Hello, first of all, thank you very much for the fast reply! Installation seems to work know, but the animator.inf is only available if the animator binary is executed in the same directory. Exporting the animator.inf does not work as the dot in the variable is not permitted in bash (we're running on RHEL 7.3) By replacing the dot with an underscore the variable seems not to be found by the animator. (found this solution in another article) (ANIMATOR_INF=/opt/gnucoboldebugger/animator.inf) Error...
Yes It runs fine under 3.0 Federico Priolo < MESSAGGIO ORIGINALE Hello dear folks, as i cannot find any information regarding this topic, i'd like to ask if the current version of the debugger generally works with GnuCobol Compiler 3.0? Currently we are not able to get the Debugger functional.. Thank you very much for any hints or information! Kind Regards Debugger Support for GnuCobol 3.0 Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/tp-cobol-debugg/discussion/general/...
Hello dear folks, as i cannot find any information regarding this topic, i'd like to ask if the current version of the debugger generally works with GnuCobol Compiler 3.0? Currently we are not able to get the Debugger functional.. Thank you very much for any hints or information! Kind Regards
federico - I hope things work out for you - I've seen the support you've given to other people including myself and appreciate it - I hope he understands. David.
David, thanks you for the reply you gave to Paul, I am so sorry for him I got some personaly troubles and really wasn't able to help him... generally I give any support... Btw, I hope your explanation will help him to solve .. in any case I want to say that the .ani source is not only a cobol source but it is really "the" cobol source for the animator. So for investigate about trouble one can simple to take a look inside it.. Federico
I downloaded the bbc.i file & modded it to create original source as best I could - then ran it thru my version of the animator - I've attached a screen copy of it in operation as well as a data trace that my version can also produce. I haven't released it as such as there are still things I want to play with.
I downloaded the bbc.i file & modded it to create original source as best I could - then ran it thru my version of the animator - I've attached a screen copy of it in operation as well as a data trace that my version can also produce.
I downloaded the bbc.i file & modded it to create original source as best I could - then ran it thru my version of the animator - I've attached a screen copy of it in operation as well as a data trace that my version can also produce.
Paul, You seem to be unusually hard on federico. He has requested a particular file from you that you haven't supplied. Let me explain just how the Animator works. It processes your input cobol source file analysing for datanames & verbs. It then creates 2 files - xxxxx.ani - your original source file with additional code lines. The second file is is xxxx.cpy which is merely a .cpy module to do the actual processing of the additional code in .ani. It would appear that there is some failing in the...
Paul, You seem to be unusually hard on federico. He has requested a particular file from you that you haven't supplied. Let me explain just how the Animator works. It processes your input cobol source file analysing for datanames & verbs. It then creates 2 files - xxxxx.ani - your original source file with additional code lines. The second file is is xxxx.cpy which is merely a .cpy module to do the actual processing of the additional code in .ani. It would appear that there is some failing in the...
Federico It appears that you are unable or unwilling to provide any support regarding my attempt to use TP-Debugger so I will not pursue these attempts any further.
Unfortunately i wasnt able during last weeks to give you a more appropriate suppport in order at your request..maybe these days i Will be more availableInviato dal mio dispositivo Huawei-------- Messaggio originale --------Oggetto: [tp-cobol-debugg:discussion] TP-Debugger ErrorsDa: Paul Richards paoloricardo@users.sourceforge.netA: "[tp-cobol-debugg:discussion] " installing@discussion.tp-cobol-debugg.p.re.sourceforge.netCC: FedericoAre you able to assist me in correcting theerrors I received?---TP-Debugger...
no you have to run the animator with -k parameter this allows the animator to leave the .ani file. inside you can find the core of the animator It Simply add COBOL statements to arrange the process.Inviato dal mio dispositivo Huawei-------- Messaggio originale --------Oggetto: [tp-cobol-debugg:discussion] TP-Debugger ErrorsDa: Paul Richards paoloricardo@users.sourceforge.netA: "[tp-cobol-debugg:discussion] " installing@discussion.tp-cobol-debugg.p.re.sourceforge.netCC: FedericoAre these the files...
Federico Are you able to assist me in correcting theerrors I received?
i didnt check for them yetInviato dal mio dispositivo Huawei-------- Messaggio originale --------Oggetto: [tp-cobol-debugg:discussion] TP-Debugger ErrorsDa: Paul Richards paoloricardo@users.sourceforge.netA: "[tp-cobol-debugg:discussion] " installing@discussion.tp-cobol-debugg.p.re.sourceforge.netCC: FedericoHave you an explanation as to why I am getting these errors?---TP-Debugger Errors---Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/tp-cobol-debugg/discussion/installing/To...
Federico Have you an explanation as to why I am getting these errors?
This seems to be a correct version of BBCB.i
Federico Are these the files you require?
may you attach the ani file ?Inviato dal mio dispositivo Huawei-------- Messaggio originale --------Oggetto: [tp-cobol-debugg:discussion] TP-Debugger ErrorsDa: Paul Richards paoloricardo@users.sourceforge.netA: "[tp-cobol-debugg:discussion] " installing@discussion.tp-cobol-debugg.p.re.sourceforge.netCC: I am trying to debug/animate a program and I am getting errors I do not understand.The relevant code in my program is as follows:95 procedure division.96 97 *** main loop 98 99 01-function-select.100...
I am trying to debug/animate a program and I am getting errors I do not understand. The relevant code in my program is as follows: 95 procedure division. 96 97 *** main loop 98 99 01-function-select. 100 set environment "COB_SCREEN_ESC" to "Y" 101 set environmenT "COB_SCREEN_EXCEPTIONS" to "Y" 102 open i-o beeb-file 103 display beeb-scrn 104 perform 02-amend-database 105 until cob-crt-status = cob-scr-esc 106 107 stop run. The whole program compiles without errors using GnuCOBOL 3.0rc-1 and using...
no others update were releasedFedericoInviato dal mio dispositivo Huawei-------- Messaggio originale --------Oggetto: [tp-cobol-debugg:discussion] Any update ?Da: Eugenio Di Lorenzo dilodilo@users.sourceforge.netA: "[tp-cobol-debugg:discussion] " installing@discussion.tp-cobol-debugg.p.re.sourceforge.netCC: Hi Federico, It's been a year since the last release.Do you have any improvements or updates to be released?---Any update ?---Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/tp-cobol-debugg/discussion/installing/To...
Hi Federico, It's been a year since the last release. Do you have any improvements or updates to be released?
The test sample given along works fine. Looks like, there are issue with Dot. :)
it seems to be correct. did you test also other COBOL samples?
Hi, Could you please help me on generating flowgraph for the cobol program? At first, I compiled all the cobol programs including analyzer.cbl Then, I compiled my program with the command "cobc -x ./PROGRAMS/SEQRPT2.cbl" Then, I gave this command "animator ./PROGRAMS/SEQRPT2.cbl -A -x" I got the message as below: Making CFG..C:\"Program Files (x86)"\"Graphviz2.38"\bin\dot.exe -Tgif -o"TEST gif" -Kdot ./temp/172709.flw Error: ./temp/172709.flw: syntax error in line 5 near '->' 'test.gif' is not recognized...