Ansicht
Dokumentation
05227 - Backup of Journalreceivers
CL_GUI_FRONTEND_SERVICES - Frontend Services General Material DataThis documentation is copyright by SAP AG.
Backup of Journalreceivers
Thru a CL program at set key times of the day(so can achieve point in time recovery 12noon; 4pm; 8pm)
a. Display the journal to spool - WRKJRNA to *print
b. Copy the spool file to a physical file - CPYSPLF to *PF
c. Read thru the *PF to find a record containing a receiver name - RCVF
d. If found a receiver name record save it to tape - SAVOBJ
e. If receiver had been saved on a previous run delete it this time since it is
now on 2 different tape media (if status *SAVED going into this job) - DLTJRNRCV
f. read next record (step c.) above
Doreen Anderson
Ball Horticultural Company
dandersoZb...
(630) 231-3600 x3214
-----Original Message-----
From: Lehnardt, Franz [mailto:franz.lehnardtZe...]
Sent: Wednesday, February 27, 2002 8:08 AM
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
[Non-text portions of this message have been removed]
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
Durban Tours - Südafrika Safari
rdisp/max_wprun_time - Maximum work process run time TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 3772 Date: 20240425 Time: 073419 sap01-206 ( 2 ms )
