ARCHIVING FILES

Check out what the master of jBase thinks about:

Jim Idle
Hi,
The limitation is that the offsets and so on in the file format are
limited to signed 32 bit integers. However, internally, these numbers
can appear to get bigger than that, but will end up going negative, or
wrapping and so on and the C runtime assumes you know what you are
doing. I know programmers who use these quirks as 'optimizations' in
fact - they shouldn't, but they do.

So, when a file gets to a point where the 2GB limit is reached, you can
end up writing a record that pushes the file over 2GB, but not
discovering this until you try to read it, at which point the pointers
will be wrong and be rejected. In turn, this is because most file
systems these days do not limit a file to a 2GB limit, so the write the
extends the file beyond 2GB will not be rejected (though a write to an
incorrect offset that tries to be >2GB will throw an error).

Other jBASE file types are not limited to the 2GB, 32 bit interface to
the file system and you might wish to use these. However, in general
your system will probably be more efficient if you archive data or
partition it and so on, so that you do not get files of 2GB (though
there are of course times when this is desirable).

Jim

So try using partitioning, see e.g. t24all.com/forum/43-jbase-utilities/2576...e-creation.html#2576

What have you set up in F.ARCHIVE - STATEMENT?
Do you use ARC.STATEMENT ?
Have you checked the COMOs and F.ARCHIVE for any messages (also 'positve') ?
Do you have records in F.ARC.STATEMENT.PROCESSED ?

We developed our own arc-service as we needed selection for e.g. only NOSTRO accounts so I'm not total aware of the ARC.STATEMENT logic.

What I miss is the .ARC.PATHNAME as I think to remember that the default might not work correctly (files created in ./0 directory ?) [but that shouldn't stop the archiving itself]

329888 records doesn't look much data, do you have entries older than 1 year ?
Do you use STMT.ENTRY.DETAILS ? I think they must be archived before STATEMENT (NOT SURE ;-)

There are two files that should be updated during archiving

ARC.RECORDS.SEL
ARC.RECORDS.SELECT

When the process is finished F.ARCHIVE should show details as well.

From CONTROL.LIST display in COMO ?

jpb wrote: wrote:

We developed our own arc-service as we needed ...

That's why I don't need another way, can show in COMO whatever we want.