Activity for Vincent (Bryan) Coen
-
Vincent (Bryan) Coen posted a comment on discussion GnuCOBOL
For accept for a field use AUTO Enter is not needed for a fixed sized field or similar. If the data is preloaded then also add UPDATE but without it all data is fresly created with any existing over written. Also see AUTO-SKIP in Prog guide or ref, sections 6.9.3 through 6.9.5
-
'The' best way to process accepting numbers etc, is to use Chuck's routine ACCEPT_NUMERIC which is a C routine that you call having preset some variables along with the target address field.
-
nightly - well as of today anyway
-
Update v2.03.15 has been uploaded to the file area. This fixes bugs where cobxref processes verb CALL where there is a reserved word pre routine name such as STATIC or STDCALL where these reserved words would be used instead of the routine. I have tried to update the SVN system but keep getting a message that the first file being commited is out of date and it is not. I cannot see a way of fixing this issue. That said the current version is present in the GnuCobol contrib area - that works.
-
2.03.15 bug fix
-
Please confirm that this bug report can now be closed.
-
In my .bashrc file I have (among others) : export COBCPY=~/cobolsrc/ACAS/copybooks export COB_SCREEN_ESC=YES export COB_SCREEN_EXCEPTIONS=YES export COB_LIBRARY_PATH=~/bin export PATH= etc, etc export TMPDIR=~/tmp export DB_HOME=. Note that the export commands do NOT have any quotes but in any event what is var apphome set to prior to these SET commands AND have you verified that they are set correctly such as by doing a set | less and checking. I have not seen anything using COB-ALLOW and COB_AUTO...
-
Not being an expert on the usage of the mouse but you have not specified the copy lib for the statuses for screen/mouse so include in WS : 01 All-My-Constants pic 9(4). copy "screenio.cpy". This copy book sits by default in the gnucobol compiler sources in folder copy. Now look in that copybook under "*> Exception keys for mouse handling" where you will find the codes available such as : 78 COB-SCR-MOUSE-MOVE VALUE 2040. 78 COB-SCR-LEFT-PRESSED VALUE 2041. 78 COB-SCR-LEFT-RELEASED VALUE 2042. 78...
-
Answers : 1. BDB will create a secondary index for each alternate index field so yes filename.dat and filename.dat.1 is correct. 2. This error shows that you have a diference of BDB versions between creating the file and the db_dump program. BDB does use a btree database as example for db-18.1.32 produces (before the data o/p : db_dump invoice.dat VERSION=3 format=bytevalue type=btree db_pagesize=4096 HEADER=END [ then the data ] DATA=END If, you deside to update version of DBD do NOT go beyond 18.1.32....
-
Now I could be wrong but it looks like the path is wrong as you have : C:\IBZANIM\LOADLIB>SET COB_FILE_PATH COB_FILE_PATH=.\;IBZANIM\LOADLIB;\WINZOS\ZOSICF; So 2 copies of "COB_FILE_PATH" Possibly SET is wrong any way but I would have used : C:\IBZANIM\LOADLIB>COB_FILE_PATH=\IBZANIM\LOADLIB;\WINZOS\ZOSICF Note the omission of some of the colons etc and that the path starts at the top level. Here I assume root (top level folder also has C:\WINZOS
-
Minor typo's fixed in sect. 6,7 & 8
-
Just some typos and a suggested addition for UNSTRING.
-
All fixed , thanks.
-
Attempt 1 failed I suspect because ws-t2-sort-day and ws-t2-sort-disp are not present - and possibly the compiler created those fields but should have produced a warning but in any event are outside the table . Attempt 2, is correct in that all fields are defined so yes that one should work.
-
On 09/08/2024 21:37, Ralph Linkletter wrote: This is a GnuCOBOL program BUT it needs CBL_ routines written by Chuck H. CBL_CHECK_FILE_EXISTS CBL_CHECK_FILE_EXIST exists already and has for some time. CBL_SPLIT_FILENAME Not really needed as there is Cobol verbs that do similar. i.e., UNSTRING - see PG or PR for usage if needed.
-
Do you have a copy of the program that created this file ? Do you have the record layout ? If you do the simplest and primary way is to create a sequential file using the ISAM file the ina very small PD do : Open Input ISAM-FILE Output Seq-file. perform until exit read ISAM-FILE at end exit perform write Seq-Record from ISAM-Record exit perform cycle end-perform close ISAM-File SEQ-File. goback. Then copy the seq file to GC and read it in what ever way you need. The normal method is above for migrating...
-
Do you have a copy of the program that created this file ? Do you have the record layout ? If you do the simplest and primary way is to create a sequential file using the ISAM file the ina very small PD do : Open Input ISAM-FILE Output Seq-file. perform until exit read ISAM-FILE at end exit perform write Seq-Record from ISAM-Record exit perform cycle end-perform close ISAM-File SEQ-File. goback. Then copy the seq file to GC and read it in what ever way you need. The normal method is above for migrating...
-
intrinsic functions: missing checks for argument type used
-
Let me know when available & working with the docs for all and I will put in the manuals PG & PR. On 23/07/2024 20:27, Simon Sobisch wrote: labels: --> fileio, mf-cobol, acucobol Group: unclassified --> GC 4.x Comment: This is related to configurable io status [feature-requests:#348] https://sourceforge.net/p/gnucobol/feature-requests/348/ which is loosely planned for GC 4.0
-
I have never programmed for Android but - have you checked the privledges for the folder you are trying to create a file in ? Another is to try and touch a non existant file in same folder i.e., touch fred Then check it created an empty file. In this I am clutching at straws a bit as I did not think Andriod uses owner settings for folders / files etc but could be wrong as I seem to recall Android is based on a Linux kernel but again could be wrong. Regarding path - yes you can specify a full path...
-
Using open i-o on a file that does not exist yet may well NOT create a new file. As a standard for all my code I use this code block : open i-o file-1 if file-1-fs not = zeros close file-1 open output file-1 if file-1-fs not = zeros *> JIC display "error opening file-1 - status " file-1-fs goback end-if close file-1 open i-o file-1.
-
For PG-Errors-07 --- The example should be if condition else ... end-if similar as the last tests - done. Typo tp -> to done. Spelling honoured - is correct, I am British not American :) Comma example changed as not correct anyway as an example so corrected and created 2nd example showing usage of zzz,zzz,zz9. Floating symbols corrected as you suggest. Latest version of the manuals PG and PR updated and on site. Thanks for all.
-
various fixes see updates section
-
Sorry I only try and keep the manual up to date, compiler thats down to Simon and others.
-
Early this year I took on a migration of an OE (Order Entry) system written for Tandy Cobol that was RM Cobol v1.3 or .4 . It was to run under Xenix on a TRS80 series PC with ram from 640K and this left around 500k for applications. This was written by one US company that then passed it to another who in turn gave Tandy marketing rights. The various Tandy archives do NOT have this version of OE and there is no documentation for OE or any other Cobol based accounting system that I have found anywhere....
-
Please try using v3.2 final and see if you get same results. On 03/07/2024 16:44, julian sefton wrote: cobc (GnuCOBOL) 3.2-dev.0 Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later https://gnu.org/licenses/gpl.html This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Keisuke Nishida, Roger While, Ron Norman, Simon Sobisch, Edward Hart Built Sep 26 2022...
-
The clause integer-1 TO is optional and "integer-2" is mandatory with TIMES optional as a table does NOT require both and is in fact pointless as all tables use the max size always. So if any thing only TIMES needs to be in square braces which it is. I would therefore say that therefore 'TO integer-2' and 'TIMES' are optional.
-
Explain why - in detail please.
-
Example 1 (DISPLAY2.COB) uses a numeric field so you can only input digits 0 - 9. So trying to input comma should NOT be accepted. The use of inputting a period should also be rejected but the numeric input processing is flacky in not having code that rejects invalid data correctly. My experience of input numbers is that one method with a second optional but still under test, can be used namely: Use a PIC X(size required such as 12 for your example) Then use NUMVAL to move to a numeric picture such...
-
As these have NOT been made avilable tot he code base I cannot do anything with them let alone seeing the formal specifications of each.
-
OE - Order Entry status -- This product is included for Cobol programmers to play with but it will NOT be included within ACAS. I have stoppped any work on it and that is not likely to change unless some one gives me a good reason to change my mind.
-
Nightly builds as available at applewood.linkpc.net/files/acas/nightlybuilds This, is the only location to get up to date builds and not via the sourceforge files area as I do NOT keep this up to date daily or any where near it. Remember these night builds are taken direct from the development sources and will contain code that may well not have been compiled let alone tested. When these builds get to a workable point in time, a copy of the current nightly build is put on to the sourceforge files...
-
Status report as of this date : As previously stated BO coding for Stock control is complete subject to full system testing. Sales Ledger coding is still in progress regarding the Invoicing Program sl910 and this involves the following functions : At start of program it checks if BO file and records exist then checks if any records has new stock added via a flag set in Stock control Stock Additions (st020) along with the quantity now added. If the above is not the case it continues as previously...
-
The whole Back Order system as well as recurring charges for sales ledger and with some coding for Purchase has been completed. I am very dubious as to using it in Purchase ledger though, so will not be added. Also included in the nightly build as in cvs as of today is recurring processing for which new program sl800, sl810, sl820 and sl830 are complete and also included. THIS STILL HAS TO BE TESTED. I have as of today not conducted any testing on these but will do so over the next few days if only...
-
With the additions of Back Order processing now included in acas via sales ledger invoicing and stock control the usefullness of OE is reduced to the point of being not needed. The only function now in OE that is not in acas is Salesman and sales commisions. As OE has no link to a payroll system nor General / Nominal ledgers, I consider it as not worth the effort in migrating OE into ACAS. However I have left the system in the nightlly builds for those that want to have a look see etc. I have created...
-
Issues with install script
-
B-SHIFT-xx
-
These and many other fixes
-
pg, pr, qr updates
-
On 24/06/2024 01:31, Charles B Appleton wrote: I did try using several variations including '$SET SOURCEFORMAT"FREE", and '>>SOURCE FORMAT IS FREE'. It does not work. I also checked the RM/COBOL documentation, including the most recent from MF, for any reference to SOURCE or FORMAT. I did not find any. I can only conclude that RM/COBOL does not support any source format other than fixed. Yep, like I said not many support other than fixed - GnuCobol is the only one I know but there but be at least...
-
Start pgm2 as a thread. That could well work. On 24/06/2024 18:19, Alain Reymond wrote: The 2 modified programs work under Linux: pgm1 starts pgm2, pgm2 displays the clock. When pgm1 stops, it kills pgm2 because the pid of pgm2 has been saved. But, control of the data displayed on the console display remains in pgm2. pgm1 accepts data but does not display anything. Only the clock runs! I do not know how to make 2 programs share the same console for display. Attachments:
-
Yep, like I said not many support other than fixed - GnuCobol is the only one I know but there but be at least one other some where :)
-
I would suspect that it is too old for that but simple way to tell is to try it. In any event there is not many that does - GnuCobol being the only one I have found that is free to obtain. It also supports VARIABLE and a lot more but the others are based on fixed and variable and are some what very obscure forms.
-
mbsebbs-1.0.8.8 released
-
Building 1.0.8.8 under Linux
-
Multiple application mostly now made open source including a account suite that includes sales, invoicing with back orders, purchase, general, stock. Flight logging for pilots and others, various Cobol tools. All migrated over or originally written for GnuCobol multi platform.
-
Compile using 16 subscripts never finishes
-
On 13/06/2024 08:15, Eugenio Di Lorenzo wrote: Since these are two rather particular clauses, it could be useful to add the two small example programs to the PG: a program for the use of CONTROL and a program for the use of COLOR (see the two sources in the previous posts ) These are present as previously requested.
-
Enable LTO, PGO and PLO for GnuCobol
-
Re-mapped to GC v3.X and not Prog guide.
-
screenio adjustments: attributes + runtime-adjustable via CONTROL/COLOR
-
Done - see bug report for same thing el al.
-
document binary operators
-
COMPUTE verb: boolean-expression is missing
-
Done but bug 468 is closed and has nothing to do with binary ops.
-
7.8.9 COMPUTE - added boolean & Shift text
-
Noted. That adds another dimension to the issue :)
-
See the Programming Guide or Reference at 10.1.1 cobc - The GnuCOBOL Compiler but according to it : -j [<args>]</args>, --job[=<args>]</args> run program after build, passing <args></args> So you compile program then run it although that said it runs slightly slower than executing it after the compile, at least on my system for some reason ! Yes the display after a while just comes out as a complete stream - So yes you might want to consider restructuring your displays etc. or using a text file as...
-
Try running it as : cobc -x -j FSX.CBL works here but a bit quicker is : cobc -x FSX.CBL ./FSX16 and doing time ./FSX16 gives time as : real 0m1.154s user 0m0.201s sys 0m0.201s but I run an old AMD FX8350 8 core under Mageia v9 Linux. On 10/06/2024 20:45, Vince Esparza wrote: [bugs:#973] https://sourceforge.net/p/gnucobol/bugs/973/ Compile using 16 subscripts never finishes Status: open Group: unclassified Created: Mon Jun 10, 2024 07:45 PM UTC by Vince Esparza Last Updated: Mon Jun 10, 2024 07:45...
-
-
CBL_GC_GET_SCR_SIZE
-
Error with get/set scr pos etc (all 4 of them
-
I have also changed same for : CBL_GC_SET_SCR_SIZE CBL_GET_CSR_POS CBL_SET_CSR_POS. On 05/06/2024 04:27, Chuck H. wrote: The programmers guide is incorrect, the format should be |01NO-OF-LINESUSAGEBINARY-CHARUNSIGNED. 01NO-OF-COLUMNSUSAGEBINARY-CHARUNSIGNED. | the value of binary 236 in a signed field is Negative 20 when corrected it displays as it should Attachments: myscreensize2_hPv1kgEpL6.png https://sourceforge.net/p/gnucobol/discussion/help/thread/319f6cb1fd/dda6/attachment/myscreensize2_hPv1kgEpL6.png...
-
Fixed. On 05/06/2024 04:27, Chuck H. wrote: The programmers guide is incorrect, the format should be |01NO-OF-LINESUSAGEBINARY-CHARUNSIGNED. 01NO-OF-COLUMNSUSAGEBINARY-CHARUNSIGNED. | the value of binary 236 in a signed field is Negative 20 when corrected it displays as it should
-
fixes 4 inline PERFORM, ACCEPT info etc
-
bug in CALL-CONVENTION and CALL STDCALL literal
-
Done.
-
Noted, sorry what exactly needs changing ?
-
User-defined names limit
-
done
-
On 28/05/2024 20:39, Alain REYMOND wrote: OK, found : DB_HOME has to be set to the directory where the files are positioned. Not very intuitive, but it works. Regards Sorry, had forgotten that one :(
-
No you are missing it, closing the file in prog 1 allows it to be read correctly by prog2. This of course does depend on the ISAM lib you are using but I have found from many years of experience to close a file when process is complete and if needed to open it again at the correct point. I do not trust any file or record locking as that also varies between ISAM libraries.
-
Using v3.2 final on a Mageia v9 X64 system AND changing your source in read fdmyfile next end-read display fdmyfile-key >4 close fdmyfile > New line call "subtestio" I get : [vince@applewood tmp]$ cobc -x test1.cbl [vince@applewood tmp]$ ./test1 00000001 00000002 00000003 00000004 myfile-status in subtestio - open file : 00 myfile-status in subtestio - write in file : 00 myfile-status in subtestio - close file : 00 00000001 00000002 00000003 00000004 00000005 00000006 00000007 00000010 Correct ?...
-
Thanks. On 18/05/2024 19:33, Eugenio Di Lorenzo wrote: Hi, you can filter only open tickets directly in the list from Tickets->Bugs-> Programming Guide. See screenshot Attachments: filter.png https://sourceforge.net/p/gnucobol/bugs/_discuss/thread/79dadeb97f/2e2d/7a5d/attachment/filter.png (89.8 kB; image/png)
-
5.2.1 SELECT H.b IBM not MF
-
.6 ACCEPT
-
Nested Elements Mishandled Despite 'with attributes' Specification
-
XML GENERATE
-
Done
-
ACCEPT from screen-info BUG
-
Done
-
On this use of ACCEPT, the data returned is from internal system values provided hopefully, by the terminal program similar in nature to accepting from environment variables. In both case as there is NO intervention from user and keyboard there is similarly no way to enter a Escape key. Yes ? So why test for escape key here. Now using ACCEPT for any other purpose and then testing for CRT STATUS is fine and many of use use it. So really the question is just what is the use of ESCAPE KEY based on your...
-
inline PERFORM bug
-
I must beg to differ, the END-PERFORM is NOT mandatory if, the perform is terminated by a period, as that then ends the scope of the PERFORM statement. .
-
Correct - nothing to do with the secondary ACCEPT. It is totally related to Windoz and the implementation. On 23/05/2024 19:05, Eugenio Di Lorenzo wrote: The presence or absence of ACCEPT OMITTED has nothing to do with it. I believe a bug ticket should be opened for CBL_GET_SCR_SIZE. CBL_GET_SCR_SIZE https://sourceforge.net/p/gnucobol/discussion/help/thread/319f6cb1fd/?limit=50#cfbf Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/gnucobol/discussion/help/ To...
-
XML Generate #2
-
XML Generate
-
The program works under Linux in both cases with and without the accept omitted but I did modify the display line64,65 & 66 lines to : in WS : 01 wlines-1 pic 999. 01 wlines-2 pic 999. 01 wlines-3 pic 999. at end block of 1st displays : subtract 1 from no-of-lines giving wlines-1. subtract 2 from no-of-lines giving wlines-2. subtract 3 from no-of-lines giving wlines-3. display "line64" at line wlines-1 col 001 end-display. display "line65" at line wlines-2 col 001 end-display. display "line66" at...
-
According to the manual there are only FOUR points, where point three is sub divided into five elements. Point four discusses the Escape key although you are correct it is a bit woolly (and lacking) in detail however it is not incorrect. The current manual was derived from the v2 (written in word or LibreOffice format as far as I know) by Gary. I am not convinced that the logic for ESCAPE KEY is valid at all as it is hard to understand how an escape key or any other can terminate that ACCEPT verb...
-
I use one of these calls on more than one program but do NOT use STATIC i.e., CA300-Save-Screen. move z"flg-temp.scr" to wScreenName. call "scr_dump" using wScreenName returning wInt. *> CA301-Restore-Screen. call "scr_restore" using wScreenName returning wInt. call "CBL_DELETE_FILE" using "flg-temp.scr". Used to save a copy of current screen then restore it after completing another process that display to screen, etc. No Idea if STATIC might be the cause but possibly worth a try. On 22/05/2024 22:34,...
-
Did you run this under Linux ? Vince On 22/05/2024 21:55, Boris Eng wrote: I am sorry for the delay although I accepted to be assigned to this bug. I recommend to put the command line you use to compile for bug reports. I tried to execute your code but did not exactly obtain the same behaviour as you: both programs exit with |attempt to reference unallocated memory (signal SIGSEGV)| after typing ENTER two times. After a first glance, it looks like it is an error related to memory and more precisely...
-
OK, save me having something to do but have enough with ACAS any way. Have to find extra things to do to occupy myself at the young age of 77. On 22/05/2024 18:26, John Ritter wrote: This is proprietary source code that I paid for and is licensed. It wouldn’t be appropriate to distribute it. From: discussion@gnucobol.p.re.sourceforge.net discussion@gnucobol.p.re.sourceforge.net On Behalf Of Vincent (Bryan) Coen Sent: Wednesday, May 22, 2024 8:10 AM To: [gnucobol:discussion] cobol@discussion.gnucobol.p.re.sourceforge.net...
-
Just tried overleaf but is does not like the manual sources. To build any of the manual source files texi2pdf is used but I have no idea what that calls so looks like overleaf is not compatible. On 18/05/2024 19:28, Eugenio Di Lorenzo wrote: Hi Vincent, as for the conversion of the manual, I generally agree with you. By now, however, the manual has already been converted into LATEX, I imagine with a lot of work, and since LATEX is an extremely powerful and flexible system (for those who know it)...
-
The is loads of special symbols included such as tab and I cannot find them to remove them. Possibly reason why latex is failing to build - there again may be not :( Latex does not seem to like non standard text. V. On 22/05/2024 09:12, Eugenio Di Lorenzo wrote: Here it is. Attachments: XML-GENERATE-V3.txt https://sourceforge.net/p/gnucobol/bugs/_discuss/thread/79dadeb97f/2568/f8e5/ccda/attachment/XML-GENERATE-V3.txt (28.3 kB; text/plain)
-
In text you have more than one instance of 'hex' but with no values, so is that correct ? Vince On 22/05/2024 09:12, Eugenio Di Lorenzo wrote: Here it is. Attachments: XML-GENERATE-V3.txt https://sourceforge.net/p/gnucobol/bugs/_discuss/thread/79dadeb97f/2568/f8e5/ccda/attachment/XML-GENERATE-V3.txt (28.3 kB; text/plain)
-
On 22/05/2024 15:44, Alain REYMOND wrote: Yes of course. But a compilation error or at least a warning should be raised. No error is reported, so you think the generated executable is correct although its behaviour does not match the program specification concerning the duplicates in the split key. Anyway, it is good to know what happens! If you use FIXED format but without any text in cc 72 - 80 I would recommend the first line of code in source contains : source variable starting cc8. I migrated...
-
Change fields No-Of-Lines and No-Of-ColUMNS to PIC 999 value zero. Then try again. Just in case bin-char is being truncated and there is no reason for using binary any way and removes the need for the intermediate move.
-
Any chance of the Cobol source code? Vince On 22/05/2024 02:19, John Ritter wrote: Unfortunately I don’t have any of the documentation. This goes back to the early 80’s, so no PDF files. From: discussion@gnucobol.p.re.sourceforge.net discussion@gnucobol.p.re.sourceforge.net On Behalf Of Vincent (Bryan) Coen Sent: Monday, May 13, 2024 8:29 AM To: [gnucobol:discussion] cobol@discussion.gnucobol.p.re.sourceforge.net Subject: [gnucobol:discussion] Re: tandy rmcobol Do you have access to the manuals for...
-
clear out rubbish folders
-
Please supply it as a text file as that is what is used for the texi files. I have tried to copy/paste from v2 but the build fails so could be an embedded data stream that it is not happy with. and I cannot find it :( On 21/05/2024 18:13, Eugenio Di Lorenzo wrote: Hi Vincent, I think the text I attach to this post (version 03 with some adjustments) is 99% correct. I think you could put it in the Programmers guide. If any FIX is needed we will apply it later. At least in this way the manual contains...
1 >