Are *._a,*._j,caesar.cfg enough for preservation for 7 years or it is safe to keep input print-out for Caesar-II model?

regards,
sam

These files (_a, _j, and caesar.cfg) are necessary for archiving a job. There may be other files you also need to save, depending on the job:

_7, dynamic input
.str, structural input
\caesar\system\umat1.bin, user material database
*.fil, user units files


Are they safe for 7 years? That depends on the media you use. I've seen floppy disks go bad, and I've read articles about low quality CDs not lasting more than a few years (although I haven't experienced this). Just be careful.

Yes, you have rightly pointed out that reliable media for archiving is needed. But, with so many version changes in software in 7 years, whether the portability of input data are maintained? Or, if needed the old version of software is brought out from archive in that case?

My question originated from the fact that without processing the files archivied using caesarII software, one can't justify the inputs used unless some textfile of input is also kept.

regards,
sam

All COADE products always, always can read the input from all previous versions. Input files are always upward compatible - this is one of the rules here.

However, you are correct in stating that "some" version of CAESAR II would be needed to process the archived files. Without a text listing of the input, you would need the software.

Thank You. CAESAR II Users like us feel reassured that CAESAR II remains always upward compatible.

But, some independent reviewer or client, if tally the old documented CAESAR II results with the same reproduced from preserved input rerun with latest CAESAR II version, a few mismatch are possible, which obviously can be defended.

regards,
sam

Ah yes - different results, always fun to resolve. Two big reasons for differing results are:

a) Piping code changes.
b) Running with a different configuration file.