04330 - Changing ASP on Journaling

04330 - Changing ASP on Journaling

ABAP Short Reference   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Changing ASP on Journaling


One of the first things that we learn about SAP on the AS/400 is to create a
second ASP to hold the Journal Receivers so that we can restore the file changes
since the last backup in the event of a catastrophe. In theory we can recover
right up to the moment the system crashed. I would like to ask the group a
question. Has anyone actually successfully used this technique ?

I ask this because having spoken to a number of people managing SAP systems on
AS/400's they all say that in the event of a major failure (too often from
running the TP *ALL by accident from STMS) they ended up using the save from the
previous night and just having to re-key that days work. The major problem seems
to be the time taken to restore the journals and the lack of familiarity with
applying journals. People I have discussed this with say that it is quicker to
restore the previous nights backup and get the users back to work then spend the
time figuring out how to use APYJRNCHG.

I am not for a moment suggesting that we CHGJRN(QSQJRN) DLTRCV(*YES) on
production (though there might be an argument for this on development and QA if
you back up the machine every night). I am interested in real life experiences
of how people dealt with journals in a disaster.

If I were to really want to use the Journals to recover I would want to force a
commit before the backup to make life easier and set up some tests so that I
could have written documentation should there be a big problem. Having several
hundred users and managers waiting while I looked for a Redbook would not be fun

Matt Milne
> Was the journal receiver in asp 1 as well? It is possible to have the
> journal receiver library in asp 1 and the journal receivers in asp 2. As
> long as only the journal receivers are in asp 2 you are ok.

Not really!
You put the journal receivers in ASP2 not only for performance.
The main reason is DISASTER RECOVERY. If you should happen to lose
ASP1 (containing the database) you should have your last DB backup
on tape and all the JrnRcvs since then in ASP2 to reconstruct the database.
If you lose the ASP containing the library object you may not be able
to recover the JrnRcvs - at least not easily.
So it 's wise to move the R3SIDJrn lib into ASP2.

[Non-text portions of this message have been removed]

Durban Tours - Südafrika Safari

RFUMSV00 - Advance Return for Tax on Sales/Purchases   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 2840 Date: 20240620 Time: 024341     sap01-206 ( 3 ms )