RE: OS/400 journaling of Mapics data

["Shaw, Dave" <dshaw@xxxxxxxxxxxx>]

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Konrad,

Sounds like you're talking about hot switchover with zero loss - that's
tough to do in ANY application, but probably not impossible.  Just
journaling the database is trivial; replicating it so that you can go on on
a second machine just as you would if you had an unexpected system
termination is fairly easily achievable.  There's a lot of details to take
care of, but no rocket science.

Dave Shaw
MAPICS-L Moderator
Rauch Industries, Inc.
Gastonia, NC

-----Original Message-----
From: Konrad Underkofler [mailto:kdunderk@hoshizaki.com]
Sent: Thursday, September 26, 2002 9:14 AM
To: 'mapics-l@midrange.com'
Subject: RE: OS/400 journaling of Mapics data


Mike,

I am not sure given the MAPICS architecture that this is possible.
To journal all MAPICS files would be difficult, not to mention expensive
in horsepower and disk space. As the applications were added over the years
some used temporary files, some used multiple members, some made extensive
use of QTEMP to storage in process data.

Plus the nitely backup cleans up and resets several internal files and
counters
used by checkpoint restart.

In the worst case scenario, a non-restartable job killed by a system failure
would still not be fixed by the hot backup becuase the job image in QTEMP,
JOBACT and QBATCH would not be the same on the new machine even if all files
were in sync.

Regards

Konrad