Compile Errors regarding relative key rrn and file seloi4.cob
I got a compile error that said relative key rrn must be unsigned.
FIX:
copybooks/wsfnctn.cob line 10:
03 Rrn binary-long unsigned.
added unsigned. compiled fine.
I got a compile error copybook seloi5.cob not found
common/xl150.cob
FIX:
lines 110 and 152
change
COPY "fdoi5.cob" in "../purchase".
to
COPY "fdoi4.cob" in "../purchase".
Also change all instances of
open-item-file-5
to
open-item-file-4
and
open-item-record-5
to
open-item-record-4
Other compile errors:
irs010.cbl:277: warning: OCCURS screen items is not implemented [-Wpending]
irs020.cbl:240: warning: OCCURS screen items is not implemented [-Wpending]
irs030.cbl:291: warning: OCCURS screen items is not implemented [-Wpending]
and
sl930.cbl: in section 'zz080-Setup-Company-Details':
sl930.cbl:948: warning: inline PERFORM without imperative statement used [-Wdialect]
sl930.cbl:950: warning: inline PERFORM without imperative statement used [-Wdialect]
sl930.cbl:952: warning: inline PERFORM without imperative statement used [-Wdialect]
sl930.cbl:954: warning: inline PERFORM without imperative statement used [-Wdialect]
sl930.cbl:956: warning: inline PERFORM without imperative statement used [-Wdialect]
sl930.cbl:958: warning: inline PERFORM without imperative statement used [-Wdialect]
sl930.cbl:960: warning: inline PERFORM without imperative statement used [-Wdialect]
sl950.cbl: in section 'zz080-Setup-Company-Details':
sl950.cbl:785: warning: inline PERFORM without imperative statement used [-Wdialect]
sl950.cbl:787: warning: inline PERFORM without imperative statement used [-Wdialect]
sl950.cbl:789: warning: inline PERFORM without imperative statement used [-Wdialect]
sl950.cbl:791: warning: inline PERFORM without imperative statement used [-Wdialect]
sl950.cbl:793: warning: inline PERFORM without imperative statement used [-Wdialect]
sl950.cbl:795: warning: inline PERFORM without imperative statement used [-Wdialect]
sl950.cbl:797: warning: inline PERFORM without imperative statement used [-Wdialect]
sales done
st060.cbl: in section 'ba000-Import-Stock':
st060.cbl: in paragraph 'ba020-Process-Regular':
st060.cbl:341: warning: inline PERFORM without imperative statement used [-Wdialect]
st060.cbl: in paragraph 'ba030-Process-Comma':
st060.cbl:395: warning: inline PERFORM without imperative statement used [-Wdialect]
st060.cbl: in section 'zz027-Clean-Number':
st060.cbl:564: warning: inline PERFORM without imperative statement used [-Wdialect]
st060.cbl: in section 'zz030-Format-Amount':
st060.cbl:588: warning: inline PERFORM without imperative statement used [-Wdialect]
st060.cbl:610: warning: inline PERFORM without imperative statement used [-Wdialect]
stock done
I believe those inline performs are fine, it does not appear that you are doing anything except looking for the first not space in the variable...
As to the OCCURS SCREEN ITEMS, it may be that i am doing something wrong with libcob. I am using version 3.2-dev.0 of cobc. but i cannot tell if it is using libcob at all? when I ./configure then make then sudo make install i do not get a directory in /usr/include/libcob i did try copying over there.. and still same results. could not figure out how i was supposed to do a configure/make etc with libcob. but irs does compile and run when i change directories and run ./irs
Thanks kindly...and yes i am preparing to return to programming from trucking.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
These messages refer to files using copybooks ???04 & 05 but these are NOT used looking at the current source code for v3.02.
Here is my quick compile for v3.02 using GnuCobol v3.2 as shown etc and using the ACAS script comp-all-no-rdbms.sh when running from the ACAS directory but first o/p from cobc -v (minus the cr stuff) then list of content from ACAS folder :
cobc -V
cobc (GnuCOBOL) 3.2-dev.0
Built Mar 27 2022 15:25:50
Packaged Mar 27 2022 14:24:51 UTC
C version "10.3.0"
ls -la --group-directories-first with folder not in the available archive remove (used for testing) :
Ok thanks. I was able to get it all to compile but you are correct I was using the older ACAS v3.01.
I just downloaded the ACAS-nightly.rar just now after reading your message here. Is that the v3.02 beta?
To compile I used the comp-all.sh from the v3.01..
Is there a file in the downloads that tells me which version? I am looking now to see if I can verify which ACAS files I need to download. The COBC I downloaded was from the one you linked here on sourceforge because I could not find COBC v3.2-dev.0 on the GnuCOBOL sourceforge.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The comp-all.sh script is to build a version that support both Cobol ISAM files and the mysql RDB to store data in tables, which of course needs the mysql (or mariadb), system and that if the C headers and other development sources installed.
To build just for using the Cobol ISAM files etc, use the supplied script comp-all-no-rdbms.sh
This will change directory, for each sub system as well as the common folder and call the build scripts in each.
This is really designed so that companies / businesses that will have a number of staff using the ACAS system at the same time but more importantly entering data at the same time such as Invoice production do not have any issues including performance.
On paper using the right ISAM library will also work BUT in my testing, admittedly some time back, the locking element within Cobol did not work.
When using RDB via mysql, it works as standard, at least using the default RDB engine.
Here, record locking issues do not arise.
If wanting to compile the system to only use the Cobol ISAM system and libraries, use the script I used to build the ACAS system, and this 'should' be documented in the Build manual.
The one on my system should be the same, but I do not do any kind of a daily check.
The latest version for v3.2 gnu cobol can be found at :
Scroll down until you get to GnuCOBOL 3.2 (stable): but further down if you are after Windows distributions and NO I have not tried building, testing or using on Windows.
Only *nix such as Linux and OSX including using a Raspberry Pi 3B+ and Pi 4 both using a hard disk and SSD respectively.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes I compiled as below without mysql. Once I understand the ACAS and GnuCOBOL better, from live work, then I will dig into the mysql. And as I mentioned in another post, when I understand what you are doing with that see what can be done to integrate PostgreSQL, and SQLite...SQLite does not give record locking... and using WAL all the processes have to actually be on the same system..which is fine if TELNET or SSH is used perhaps. But for single user applications.. SQLite and built in GnuCOBOL data handling should be fine.
However yes I agree record locking is frankly imperative.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes I compiled as below without mysql. Once I understand the ACAS and
GnuCOBOL better, from live work, then I will dig into the mysql. And
as I mentioned in another post, when I understand what you are doing
with that see what can be done to integrate PostgreSQL, and
SQLite...SQLite does not give record locking... and using WAL all the
processes have to actually be on the same system..which is fine if
TELNET or SSH is used perhaps. But for single user applications..
SQLite and built in GnuCOBOL data handling should be fine.
However yes I agree record locking is frankly imperative.
Agree. For sqlite it is not suitable as many users can be running on
their own PC's and that is outside the sqlite model as near as I can see.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
SQLite would work for a small business where one employee at a time was using the software or using different parts of the software on different machines.. i think it can do many reads at once but has to lock on rights.. and i would have to understand the write ahead log which they seem to indicate you kinda could lock records..
but they say plainly it is not meant to do what mysql and postgres et al are meant to do.
I used to use a program called MagicPC by Aker.. written in pascal.. not a programming language.. even tho they called it the visual database programming language..it used betrieve..and you basically laid out your fields in a visual designer.. your screens and expressions and i was able to create accounting software in it.. now i have been muddling around w ith it again.. so i could use it as a kind of guide to whether i could create a similar program in GnuCOBOL.. sqlite would work in those cases i think. (source code is not available for MagicPC)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok thanks. I was able to get it all to compile but you are correct I
was using the older ACAS v3.01.
I just downloaded the ACAS-nightly.rar just now after reading your
message here. Is that the v3.02 beta?
To compile I used the comp-all.sh from the v3.01..
Is there a file in the downloads that tells me which version? I am
looking now to see if I can verify which ACAS files I need to
download. The COBC I downloaded was from the one you linked here on
sourceforge because I could not find COBC v3.2-dev.0 on the GnuCOBOL
It should all be in the Building... manual along with any README type
files in the archive at the top level directory.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just looked in the ACAS-Manuals directory and wow you really went to town with creating thorough manuals, including a bookkeeping manual Accounting for everyone. I have been wanting a refresher in bookeeping and accounting (I took accounting in high school) and for others I am working with and this is going to be good.
In any case i am looking at ACAS - Building the ACAS System.pdf and I presume that is the place I go to for building the system that you mean.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just looked in the ACAS-Manuals directory and wow you really went to
town with creating thorough manuals, including a bookkeeping manual
Accounting for everyone. I have been wanting a refresher in bookeeping
and accounting (I took accounting in high school) and for others I am
working with and this is going to be good.
In any case i am looking at ACAS - Building the ACAS System.pdf and I
presume that is the place I go to for building the system that you mean.
Yes the that's goto manual for Building as all if not most of the other
content from the other manuals have been transferred there - if only to
cut down on my typing :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your assistance. I am going to read through all the manuals you have created. Then start to work with this as much as I can to contribute.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is my list of files. I am not trying to use mysql so i dont know if the builds for those create the directories:
JCs-mysql-preprocessor/
rdbms/
but I do not have those. I do not think it matters if I am not using mysql. I will eventually install mysql again in a virtual machine to test but for now I am testing against normal COBOL data files.
Here is the LS:
ls --group-directories-first -1
ACAS-Manuals
common
copybooks
etc
general
home
irs
mysql
purchase
sales
stock
acasbkup-Post-EOY.sh
acasbkup-Pre-EOY.sh
acasbkup.sh
'ACAS list of files and tables.txt'
comp-all-no-rdbms.sh
comp-all.sh
dykegrove.sh
Dykegrove.sh
install-ACAS-preinstalled.sh
install-ACAS.sh
mariadb-connector-c-3.0.3-linux-x86_64.tar.gz
mysql-connector-c-6.1.11-src.tar.gz
presql2-latest.zip
README.nightly
README.SVN
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, stick to the KISS (Keep It Simple, stupid!) principles at least, at the beginning.
Looks right but if you can build the system and then run the install script (install-ACAS.sh you are ready to run but follow the instructions with the Building.. manual in order to create the needed folders to use when running the system as well any needed environment variables created via export or set up in your .bash_profile or .bashrc (can be other file names) in your root directory, i.e., at say /home/your-user-name.
Compiled.. worked.. installed.. worked.. program ran.. via ACAS worked..
I presume I had to be in ~/ACAS but was not sure.
So i presume whenever you run the ACAS binary it looks for the data in
the directory you are in.
Downloaded the knightly data into ~/ACAS and that worked.
I presume ACAS-Practice means practice as in experimenting.
Not sure what Dykegrove is.. but in your scripts referencing it rather
than ~/something it is /home/vince/something...
such as dykegrove.sh
I'm assuming that is a test data.
But it all worked and compiled with 3.02 ACAS without any errors at
all whatsoever. so YAY!
Dykegrove - yes test data including around 1,000 record for Sales and for
Purchase Ledgers (US terms Receivables & Payables) and a few records for Stock Control.
Stock really needs a lot more, and I was going to go to a supermarket
with a bar-code scanner and read a stack of cans where I can download
the details for each one - easier said than done for my local supermarkets.
Fine on paper, poor in practice.
Last edit: Vincent (Bryan) Coen 2023-03-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Compile Errors regarding relative key rrn and file seloi4.cob
I got a compile error that said relative key rrn must be unsigned.
FIX:
copybooks/wsfnctn.cob line 10:
03 Rrn binary-long unsigned.
added unsigned. compiled fine.
I got a compile error copybook seloi5.cob not found
common/xl150.cob
FIX:
lines 110 and 152
change
COPY "fdoi5.cob" in "../purchase".
to
COPY "fdoi4.cob" in "../purchase".
Also change all instances of
open-item-file-5
to
open-item-file-4
and
open-item-record-5
to
open-item-record-4
Other compile errors:
irs010.cbl:277: warning: OCCURS screen items is not implemented [-Wpending]
irs020.cbl:240: warning: OCCURS screen items is not implemented [-Wpending]
irs030.cbl:291: warning: OCCURS screen items is not implemented [-Wpending]
and
sl930.cbl: in section 'zz080-Setup-Company-Details':
sl930.cbl:948: warning: inline PERFORM without imperative statement used [-Wdialect]
sl930.cbl:950: warning: inline PERFORM without imperative statement used [-Wdialect]
sl930.cbl:952: warning: inline PERFORM without imperative statement used [-Wdialect]
sl930.cbl:954: warning: inline PERFORM without imperative statement used [-Wdialect]
sl930.cbl:956: warning: inline PERFORM without imperative statement used [-Wdialect]
sl930.cbl:958: warning: inline PERFORM without imperative statement used [-Wdialect]
sl930.cbl:960: warning: inline PERFORM without imperative statement used [-Wdialect]
sl950.cbl: in section 'zz080-Setup-Company-Details':
sl950.cbl:785: warning: inline PERFORM without imperative statement used [-Wdialect]
sl950.cbl:787: warning: inline PERFORM without imperative statement used [-Wdialect]
sl950.cbl:789: warning: inline PERFORM without imperative statement used [-Wdialect]
sl950.cbl:791: warning: inline PERFORM without imperative statement used [-Wdialect]
sl950.cbl:793: warning: inline PERFORM without imperative statement used [-Wdialect]
sl950.cbl:795: warning: inline PERFORM without imperative statement used [-Wdialect]
sl950.cbl:797: warning: inline PERFORM without imperative statement used [-Wdialect]
sales done
st060.cbl: in section 'ba000-Import-Stock':
st060.cbl: in paragraph 'ba020-Process-Regular':
st060.cbl:341: warning: inline PERFORM without imperative statement used [-Wdialect]
st060.cbl: in paragraph 'ba030-Process-Comma':
st060.cbl:395: warning: inline PERFORM without imperative statement used [-Wdialect]
st060.cbl: in section 'zz027-Clean-Number':
st060.cbl:564: warning: inline PERFORM without imperative statement used [-Wdialect]
st060.cbl: in section 'zz030-Format-Amount':
st060.cbl:588: warning: inline PERFORM without imperative statement used [-Wdialect]
st060.cbl:610: warning: inline PERFORM without imperative statement used [-Wdialect]
stock done
I believe those inline performs are fine, it does not appear that you are doing anything except looking for the first not space in the variable...
As to the OCCURS SCREEN ITEMS, it may be that i am doing something wrong with libcob. I am using version 3.2-dev.0 of cobc. but i cannot tell if it is using libcob at all? when I ./configure then make then sudo make install i do not get a directory in /usr/include/libcob i did try copying over there.. and still same results. could not figure out how i was supposed to do a configure/make etc with libcob. but irs does compile and run when i change directories and run ./irs
Thanks kindly...and yes i am preparing to return to programming from trucking.
These messages refer to files using copybooks ???04 & 05 but these are NOT used looking at the current source code for v3.02.
Here is my quick compile for v3.02 using GnuCobol v3.2 as shown etc and using the ACAS script comp-all-no-rdbms.sh when running from the ACAS directory but first o/p from cobc -v (minus the cr stuff) then list of content from ACAS folder :
cobc -V
cobc (GnuCOBOL) 3.2-dev.0
Built Mar 27 2022 15:25:50
Packaged Mar 27 2022 14:24:51 UTC
C version "10.3.0"
ls -la --group-directories-first with folder not in the available archive remove (used for testing) :
ACAS-Manuals/
common/
copybooks/
general/
irs/
JCs-mysql-preprocessor/
mysql/
purchase/
rdbms/
sales/
stock/
Where am I :
pwd
/home/vince/cobolsrc/ACAS
O/p from comp-all-no-rdbms.sh : As compiling ACAS for using Cobol ISAM files only :
Compiled dummy-rdbmsMT entry points
'dummy-rdbmsMT.cbl' -> '../stock/dummy-rdbmsMT.cbl'
'dummy-rdbmsMT.cbl~' -> '../stock/dummy-rdbmsMT.cbl~'
'dummy-rdbmsMT.so' -> '../stock/dummy-rdbmsMT.so'
'dummy-rdbmsMT.cbl' -> '../sales/dummy-rdbmsMT.cbl'
'dummy-rdbmsMT.cbl~' -> '../sales/dummy-rdbmsMT.cbl~'
'dummy-rdbmsMT.so' -> '../sales/dummy-rdbmsMT.so'
'dummy-rdbmsMT.cbl' -> '../purchase/dummy-rdbmsMT.cbl'
'dummy-rdbmsMT.cbl~' -> '../purchase/dummy-rdbmsMT.cbl~'
'dummy-rdbmsMT.so' -> '../purchase/dummy-rdbmsMT.so'
'dummy-rdbmsMT.cbl' -> '../irs/dummy-rdbmsMT.cbl'
'dummy-rdbmsMT.cbl~' -> '../irs/dummy-rdbmsMT.cbl~'
'dummy-rdbmsMT.so' -> '../irs/dummy-rdbmsMT.so'
'dummy-rdbmsMT.cbl' -> '../general/dummy-rdbmsMT.cbl'
'dummy-rdbmsMT.cbl~' -> '../general/dummy-rdbmsMT.cbl~'
'dummy-rdbmsMT.so' -> '../general/dummy-rdbmsMT.so'
Copied dummy-rdbmsMT.so to irs, general, purchase, sales, stock dirs.
Compiled maps01.cbl
Compiled maps04.cbl
Compiled maps09.cbl
compiled maps
Compiled acas000.cbl
Compiled acas005.cbl
Compiled acas006.cbl
Compiled acas007.cbl
Compiled acas008.cbl
Compiled acas010.cbl
Compiled acas011.cbl
Compiled acas012.cbl
Compiled acas013.cbl
Compiled acas014.cbl
Compiled acas015.cbl
Compiled acas016.cbl
Compiled acas017.cbl
Compiled acas019.cbl
Compiled acas022.cbl
Compiled acas023.cbl
Compiled acas026.cbl
Compiled acas029.cbl
Compiled acas032.cbl
Compiled acasirsub1.cbl
Compiled acasirsub3.cbl
Compiled acasirsub4.cbl
Compiled acasirsub5.cbl
Compiled acas*
Compiled fhlogger
compiled xl150 & sys002
Compiled ACAS.cbl
Compiled acasconvert1.cbl - IRS Default file layout changes
Compiled for No RDBMS
Common modules done
Compiled gl000.cbl
Compiled gl020.cbl
Compiled gl030.3.02.14..cbl
Compiled gl030.cbl
Compiled gl050.cbl
Compiled gl051.cbl
Compiled gl060.cbl
Compiled gl070.cbl
Compiled gl071.cbl
Compiled gl072.cbl
Compiled gl080.cbl
Compiled gl090a.cbl
Compiled gl090b.cbl
Compiled gl090.cbl
Compiled gl100.cbl
Compiled gl105.cbl
Compiled gl120.cbl
Compiled general
Compiled for No RDBMS
General Ledger done
Compiled irs000.cbl
Compiled irs010.cbl
Compiled irs020.cbl
Compiled irs030.cbl
Compiled irs040.cbl
Compiled irs050.cbl
Compiled irs055.cbl
Compiled irs060.cbl
Compiled irs065.cbl
Compiled irs070.cbl
Compiled irs080.cbl
Compiled irs085.cbl
Compiled irs090.cbl
Compiled IRS
Compiled for No RDBMS
IRS done
Compiled pl000.cbl
Compiled pl010.cbl
Compiled pl015.cbl
Compiled pl020.cbl
Compiled pl025.cbl
Compiled pl030.cbl
Compiled pl040.cbl
Compiled pl050.cbl
Compiled pl055.cbl
Compiled pl060.cbl
Compiled pl070.cbl
Compiled pl080.cbl
Compiled pl085.cbl
Compiled pl090.cbl
Compiled pl095.cbl
Compiled pl100.cbl
Compiled pl115.cbl
Compiled pl120.cbl
Compiled pl130.cbl
Compiled pl140.cbl
Compiled pl160.cbl
Compiled pl165.cbl
Compiled pl170.cbl
Compiled pl180.cbl
Compiled pl190.cbl
Compiled pl900.cbl
Compiled pl910.cbl
Compiled pl920.cbl
Compiled pl930.cbl
Compiled pl940.cbl
Compiled pl950.cbl
Compiled pl960.cbl
Compiled purchase
Compiled for No RDBMS
Purchase Ledger done
compiled sl000.cbl
compiled sl010.cbl
compiled sl020.cbl
compiled sl050.cbl
compiled sl055.cbl
compiled sl060.cbl
compiled sl070.cbl
compiled sl080.cbl
compiled sl085.cbl
compiled sl090.cbl
compiled sl095.cbl
compiled sl100.cbl
compiled sl110.cbl
compiled sl115.cbl
compiled sl120.cbl
compiled sl130.cbl
compiled sl140.cbl
compiled sl160.cbl
compiled sl165.cbl
compiled sl170.cbl
compiled sl180.cbl
compiled sl190.cbl
compiled sl200.cbl
compiled sl900.cbl
compiled sl910.cbl
compiled sl920.cbl
compiled sl930.cbl
compiled sl940.cbl
compiled sl950.cbl
compiled sl960.cbl
Compiled for No RDBMS
Sales Ledger done
Compiled for No RDBMS
Stock Control done
Compiled for No RDBMS
We Are all done but check for any error or warning messages
What version are you using for ACAS, i.e., v3.02 or the older one v3.01?
Did you follow the instructions for building ACAS ?
The above was done for v3.02 beta.
Ok thanks. I was able to get it all to compile but you are correct I was using the older ACAS v3.01.
I just downloaded the ACAS-nightly.rar just now after reading your message here. Is that the v3.02 beta?
To compile I used the comp-all.sh from the v3.01..
Is there a file in the downloads that tells me which version? I am looking now to see if I can verify which ACAS files I need to download. The COBC I downloaded was from the one you linked here on sourceforge because I could not find COBC v3.2-dev.0 on the GnuCOBOL sourceforge.
Yes.
The comp-all.sh script is to build a version that support both Cobol ISAM files and the mysql RDB to store data in tables, which of course needs the mysql (or mariadb), system and that if the C headers and other development sources installed.
To build just for using the Cobol ISAM files etc, use the supplied script comp-all-no-rdbms.sh
This will change directory, for each sub system as well as the common folder and call the build scripts in each.
This is really designed so that companies / businesses that will have a number of staff using the ACAS system at the same time but more importantly entering data at the same time such as Invoice production do not have any issues including performance.
On paper using the right ISAM library will also work BUT in my testing, admittedly some time back, the locking element within Cobol did not work.
When using RDB via mysql, it works as standard, at least using the default RDB engine.
Here, record locking issues do not arise.
If wanting to compile the system to only use the Cobol ISAM system and libraries, use the script I used to build the ACAS system, and this 'should' be documented in the Build manual.
The one on my system should be the same, but I do not do any kind of a daily check.
The latest version for v3.2 gnu cobol can be found at :
https://sourceforge.net/projects/gnucobol/files/gnucobol/nightly_snapshots/
Scroll down until you get to GnuCOBOL 3.2 (stable): but further down if you are after Windows distributions and NO I have not tried building, testing or using on Windows.
Only *nix such as Linux and OSX including using a Raspberry Pi 3B+ and Pi 4 both using a hard disk and SSD respectively.
Yes I compiled as below without mysql. Once I understand the ACAS and GnuCOBOL better, from live work, then I will dig into the mysql. And as I mentioned in another post, when I understand what you are doing with that see what can be done to integrate PostgreSQL, and SQLite...SQLite does not give record locking... and using WAL all the processes have to actually be on the same system..which is fine if TELNET or SSH is used perhaps. But for single user applications.. SQLite and built in GnuCOBOL data handling should be fine.
However yes I agree record locking is frankly imperative.
On 30/09/2022 18:53, Aoirthoir An Broc wrote:
Agree. For sqlite it is not suitable as many users can be running on
their own PC's and that is outside the sqlite model as near as I can see.
SQLite would work for a small business where one employee at a time was using the software or using different parts of the software on different machines.. i think it can do many reads at once but has to lock on rights.. and i would have to understand the write ahead log which they seem to indicate you kinda could lock records..
but they say plainly it is not meant to do what mysql and postgres et al are meant to do.
I used to use a program called MagicPC by Aker.. written in pascal.. not a programming language.. even tho they called it the visual database programming language..it used betrieve..and you basically laid out your fields in a visual designer.. your screens and expressions and i was able to create accounting software in it.. now i have been muddling around w ith it again.. so i could use it as a kind of guide to whether i could create a similar program in GnuCOBOL.. sqlite would work in those cases i think. (source code is not available for MagicPC)
On 30/09/2022 17:33, Aoirthoir An Broc wrote:
It should all be in the Building... manual along with any README type
files in the archive at the top level directory.
I just looked in the ACAS-Manuals directory and wow you really went to town with creating thorough manuals, including a bookkeeping manual Accounting for everyone. I have been wanting a refresher in bookeeping and accounting (I took accounting in high school) and for others I am working with and this is going to be good.
In any case i am looking at ACAS - Building the ACAS System.pdf and I presume that is the place I go to for building the system that you mean.
Yep, created for that purpose.
On 30/09/2022 17:38, Aoirthoir An Broc wrote:
Yes the that's goto manual for Building as all if not most of the other
content from the other manuals have been transferred there - if only to
cut down on my typing :)
Alright after untarring ACAS-nightly.rar this was my action and the results compiled without error right from the start...
./comp-all-no-rdbms.sh
Compiled dummy-rdbmsMT entry points
'dummy-rdbmsMT.cbl' -> '../stock/dummy-rdbmsMT.cbl'
'dummy-rdbmsMT.so' -> '../stock/dummy-rdbmsMT.so'
'dummy-rdbmsMT.cbl' -> '../sales/dummy-rdbmsMT.cbl'
'dummy-rdbmsMT.so' -> '../sales/dummy-rdbmsMT.so'
'dummy-rdbmsMT.cbl' -> '../purchase/dummy-rdbmsMT.cbl'
'dummy-rdbmsMT.so' -> '../purchase/dummy-rdbmsMT.so'
'dummy-rdbmsMT.cbl' -> '../irs/dummy-rdbmsMT.cbl'
'dummy-rdbmsMT.so' -> '../irs/dummy-rdbmsMT.so'
'dummy-rdbmsMT.cbl' -> '../general/dummy-rdbmsMT.cbl'
'dummy-rdbmsMT.so' -> '../general/dummy-rdbmsMT.so'
Copied dummy-rdbmsMT.so to irs, general, purchase, sales, stock dirs.
Compiled maps01.cbl
Compiled maps04.cbl
Compiled maps09.cbl
compiled maps
Compiled acas000.cbl
Compiled acas005.cbl
Compiled acas006.cbl
Compiled acas007.cbl
Compiled acas008.cbl
Compiled acas010.cbl
Compiled acas011.cbl
Compiled acas012.cbl
Compiled acas013.cbl
Compiled acas014.cbl
Compiled acas015.cbl
Compiled acas016.cbl
Compiled acas017.cbl
Compiled acas019.cbl
Compiled acas022.cbl
Compiled acas023.cbl
Compiled acas026.cbl
Compiled acas029.cbl
Compiled acas032.cbl
Compiled acasirsub1.cbl
Compiled acasirsub3.cbl
Compiled acasirsub4.cbl
Compiled acasirsub5.cbl
Compiled acas*
Compiled fhlogger
compiled xl150 & sys002
Compiled ACAS.cbl
Compiled acasconvert1.cbl - IRS Default file layout changes
Compiled for No RDBMS
Common modules done
Compiled gl000.cbl
Compiled gl020.cbl
Compiled gl030.3.02.14..cbl
Compiled gl030.cbl
Compiled gl050.cbl
Compiled gl051.cbl
Compiled gl060.cbl
Compiled gl070.cbl
Compiled gl071.cbl
Compiled gl072.cbl
Compiled gl080.cbl
Compiled gl090a.cbl
Compiled gl090b.cbl
Compiled gl090.cbl
Compiled gl100.cbl
Compiled gl105.cbl
Compiled gl120.cbl
Compiled general
Compiled for No RDBMS
General Ledger done
Compiled irs000.cbl
Compiled irs010.cbl
Compiled irs020.cbl
Compiled irs030.cbl
Compiled irs040.cbl
Compiled irs050.cbl
Compiled irs055.cbl
Compiled irs060.cbl
Compiled irs065.cbl
Compiled irs070.cbl
Compiled irs080.cbl
Compiled irs085.cbl
Compiled irs090.cbl
Compiled IRS
Compiled for No RDBMS
IRS done
Compiled pl000.cbl
Compiled pl010.cbl
Compiled pl015.cbl
Compiled pl020.cbl
Compiled pl025.cbl
Compiled pl030.cbl
Compiled pl040.cbl
Compiled pl050.cbl
Compiled pl055.cbl
Compiled pl060.cbl
Compiled pl070.cbl
Compiled pl080.cbl
Compiled pl085.cbl
Compiled pl090.cbl
Compiled pl095.cbl
Compiled pl100.cbl
Compiled pl115.cbl
Compiled pl120.cbl
Compiled pl130.cbl
Compiled pl140.cbl
Compiled pl160.cbl
Compiled pl165.cbl
Compiled pl170.cbl
Compiled pl180.cbl
Compiled pl190.cbl
Compiled pl900.cbl
Compiled pl910.cbl
Compiled pl920.cbl
Compiled pl930.cbl
Compiled pl940.cbl
Compiled pl950.cbl
Compiled pl960.cbl
Compiled purchase
Compiled for No RDBMS
Purchase Ledger done
compiled sl000.cbl
compiled sl010.cbl
compiled sl020.cbl
compiled sl050.cbl
compiled sl055.cbl
compiled sl060.cbl
compiled sl070.cbl
compiled sl080.cbl
compiled sl085.cbl
compiled sl090.cbl
compiled sl095.cbl
compiled sl100.cbl
compiled sl110.cbl
compiled sl115.cbl
compiled sl120.cbl
compiled sl130.cbl
compiled sl140.cbl
compiled sl160.cbl
compiled sl165.cbl
compiled sl170.cbl
compiled sl180.cbl
compiled sl190.cbl
compiled sl200.cbl
compiled sl900.cbl
compiled sl910.cbl
compiled sl920.cbl
compiled sl930.cbl
compiled sl940.cbl
compiled sl950.cbl
compiled sl960.cbl
Compiled for No RDBMS
Sales Ledger done
Compiled for No RDBMS
Stock Control done
Compiled for No RDBMS
We Are all done but check for any error or warning messages
Thank you for your assistance. I am going to read through all the manuals you have created. Then start to work with this as much as I can to contribute.
This is my list of files. I am not trying to use mysql so i dont know if the builds for those create the directories:
JCs-mysql-preprocessor/
rdbms/
but I do not have those. I do not think it matters if I am not using mysql. I will eventually install mysql again in a virtual machine to test but for now I am testing against normal COBOL data files.
Here is the LS:
ls --group-directories-first -1
ACAS-Manuals
common
copybooks
etc
general
home
irs
mysql
purchase
sales
stock
acasbkup-Post-EOY.sh
acasbkup-Pre-EOY.sh
acasbkup.sh
'ACAS list of files and tables.txt'
comp-all-no-rdbms.sh
comp-all.sh
dykegrove.sh
Dykegrove.sh
install-ACAS-preinstalled.sh
install-ACAS.sh
mariadb-connector-c-3.0.3-linux-x86_64.tar.gz
mysql-connector-c-6.1.11-src.tar.gz
presql2-latest.zip
README.nightly
README.SVN
Yes, stick to the KISS (Keep It Simple, stupid!) principles at least, at the beginning.
Looks right but if you can build the system and then run the install script (install-ACAS.sh you are ready to run but follow the instructions with the Building.. manual in order to create the needed folders to use when running the system as well any needed environment variables created via export or set up in your .bash_profile or .bashrc (can be other file names) in your root directory, i.e., at say /home/your-user-name.
I use for compiling the system :
export COBCPY=~/cobolsrc/ACAS/copybooks
export COB_SCREEN_ESC=YES
export COB_SCREEN_EXCEPTIONS=YES
export COB_LIBRARY_PATH=~/bin
For running ACAS :
export ACAS_LEDGERS=~/ACAS
export ACAS_BIN=~/bin
export TMPDIR=~/tmp
Compiled.. worked.. installed.. worked.. program ran.. via ACAS worked..
I presume I had to be in ~/ACAS but was not sure.
So i presume whenever you run the ACAS binary it looks for the data in the directory you are in.
Downloaded the knightly data into ~/ACAS and that worked.
I presume ACAS-Practice means practice as in experimenting.
Not sure what Dykegrove is.. but in your scripts referencing it rather than ~/something it is /home/vince/something...
such as dykegrove.sh
I'm assuming that is a test data.
But it all worked and compiled with 3.02 ACAS without any errors at all whatsoever. so YAY!
On 30/09/2022 19:08, Aoirthoir An Broc wrote:
Dykegrove - yes test data including around 1,000 record for Sales and for
Purchase Ledgers (US terms Receivables & Payables) and a few records for Stock Control.
Stock really needs a lot more, and I was going to go to a supermarket
with a bar-code scanner and read a stack of cans where I can download
the details for each one - easier said than done for my local supermarkets.
Fine on paper, poor in practice.
Last edit: Vincent (Bryan) Coen 2023-03-03