Ansicht
Dokumentation

05226 - Backup of Journalreceivers

05226 - Backup of Journalreceivers

PERFORM Short Reference   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Backup of Journalreceivers

Hi Franz,

We use the SAVDLTRCV and SAVDLTRCVE utilities to automate part of the
process. SAVDLTRCV starts a "listener" job (so if you submit it, don't
submit it to a single threaded job queue or it will block it forever (we use
QSYSNOMAX after blocking QBATCH for half a day - oops) which monitors a
message queue for the journal and saves the disconnected receiver either to
save file (which is what we do) or tape and then deletes the receiver. If it
is unable to delete the receiver (pending commits, etc.), it waits for a
couple of minutes and retries (and retries).

We save our "save file library" (R3<SID>SAVF), each night and manually
delete the save files which have been saved to tape in the morning. Bear in
mind, if you use the save file option, the save files are almost the same
size as the journal receivers so you don't really save any space - you just
move it from ASP2 to ASP1. (We started this process in the first place after
2 ASP2 overflows.)

Rick

-----Original Message-----
From: Gueldenpfennig, Volker [mailto:volker.gueldenpfennigZs...]
Sent: Wednesday, February 27, 2002 9:37 AM
To: 'franz.lehnardtZe...'
Cc: Sap400 (E-mail)
Subject: RE: Backup of Journalreceivers


Hi Franz,

I would recommend the following:
V4R5:
CHGJRN JRN(R3SIDDATA/QSQJRN) RCVSIZOPT(*MAXOPT1)

V5R1:
CHGJRN JRN(R3SIDDATA/QSQJRN) RCVSIZOPT(*MAXOPT2)

Then the journal receivers can grow up to 1 GB, because I guess, that the
problem is, that the system is not able to change the receiver before it
reached 2GB which is normally the maximum.

Regards

Volker

> -----Original Message-----
> From: Lehnardt, Franz [mailto:franz.lehnardtZe...]
> Sent: Mittwoch, 27. Februar 2002 15:08
> To: 'SAP on System i (E-Mail)'
> Subject: Backup of Journalreceivers
>
>
> Hi all
>
> another poll to the group:
>
> I wonder, how you out there do manage the backup/archive of
> your JRNRCVs?
> How much traffic do you have on your journal?
> How often and in which way do you backup your receivers?
>
> The background of my questions:
>
> Once we used BRMS function "Archive" to handle the daily
> backup of our R/3
> JRNRCVs. But it happened sometimes that our PRD system came
> to a complete
> hold because of the Archive job locked the entire PRD journal, so the
> current RCV couldn't get changed when it reached its
> threshold. Msg CPI70E5
> "Journal or Journalreceiver not available" was issued.
>
> An additional reason for that conflict was the fact, that the
> rate of RCV
> changes on our system is at some times of day very high (less
> than 5 min.),
> so when the Backup Job runs for about 10-15 minutes, the
> current receiver is
> guaranteed to crash against the wall...
>
> Finally we set a manual procedure which is still in use today:
>
> WRKJRNA to check, what JRNRCVs are in status ONLINE
> SBMJOB with command SAVOBJBRM where the known receiver
> numbers are entered.
> This way we make sure, that all the receivers which will be
> attached during
> the backup will not get locked
> Last step: Delete all saved receivers also manually.
>
> But this manual input is risky (the human IT-component...)
> and sure enough -
> this week we had another PRD stop, because of accidentially
> saving the wrong
> receiver-number. Now we think of an alternative, fully or
> partly automatted.
>
> Any insight will help, thanks a lot in advance.
>
> Franz Lehnardt
> AS/400 & R/3 Basis Administration
> EGG IT Services GmbH
> Eschborn, Germany
> Tel. ++49 (0) 6196 477-360
> Fax ++49 (0) 6196 477-776
>
>

Durban Tours - Südafrika Safari

General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 4811 Date: 20240305 Time: 074609     sap01-206 ( 3 ms )