Ansicht
Dokumentation
09718 - Entry not journaled to journal QSQJRN
CPI1466 during Backup Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
Entry not journaled to journal QSQJRN
Marina,You have two problems here. Firstly, while you have specified a storage
threshold on the journal receiver size, you appear to not have anything
monitoring the message queue for threshold exceeded messages and
automatically changing them. I'm not quite sure where is comes from, but we
have a small batch job called SAVDLTRCV that runs in QBATCH and simply
monitors the message queue assigned to the journal. When the threshold
exceeded message is sent to this message queue, this job automatically does
a CHGJRN, then saves and deletes the journal receiver.
The second problem is the size of your journal receiver. I assume you are on
a release earlier than V5R1, or if a later version you haven't changed the
maximum number of entries allowed in a journal receiver, but there are
limits on the maximum size of a journal receiver. I recall that the maximum
is around 2Gb.
Hope this helps,
Andrew Tilbrook
Computer Services Manager
Dairy Farmers
8 Parkview Drive
Homebush Bay NSW 2140
AUSTRALIA
-----Original Message-----
From: heyrmanmarina [mailto:mheZgyproc.be]
Sent: Friday, 28 March 2003 3:52
To: DoNotReply@consolut.eu
Subject: Entry not journaled to journal QSQJRN
Hi,
We are running a conversion in a test-system. All batch work
processes are very
occupied.
However all work processes fall in the status MSGW because of the
following
reason :
Entry not journaled to journal QSQJRN. Reason code 1....
Reason code definitions : 1 -- Space for entry cannot be allocated on
journal
receiver. ...
Recovery for each reason code is : 1 -- IF the owning user or group
profile of
the journal receiver has reached its storage
limit, increase the maximum storage... If the journal receiver has
reached its
maximum size, change the journal (CHGJRN)
to attach a new receiver.
I have checked the user <SID><instance number> and the parameter
maximum storage
= *NOMAX.
I changed the journal and attached a new receiver, answered Retry on
the message
and the work process started working again.
However when I look at the description of the JRNRCV I see that the
treshold is
set to 500000 K, whereas the size is 1984256 K.
Does anyone know what is wrong with the journaling ?
Marina Heyrman
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
[Non-text portions of this message have been removed]
Durban Tours - Südafrika Safari
rdisp/max_wprun_time - Maximum work process run time SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 3548 Date: 20240426 Time: 130517 sap01-206 ( 3 ms )
