Ansicht
Dokumentation

09723 - Entry not journaled to journal QSQJRN

09723 - Entry not journaled to journal QSQJRN

ABAP Short Reference   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

Entry not journaled to journal QSQJRN

Hi Zll,

here are the cmd's !!!

V4R5:
CHGJRN JRN(R3SIDDATA/QSQJRN) RCVSIZOPT(*MAXOPT1)

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


cya

Best Regards/mit freundlichem Gruss

Thomas Lindner
AS/400 & SAP R/3-Basis Support

UNIELEKTRO Fachgroßhandel Gmbh & Co. KG
Informationssysteme/Systemtechnik
Industriestraße 21-39
65760 Eschborn

T +49 (0) 6196 477381
F +49 (0) 6196 477776
mailto:Thomas.LindnerZunielektro.de <mailto:Thomas.LindnerZunielektro.de>


-----Ursprüngliche Nachricht-----
Von: Andrew Tilbrook [mailto:tilbrookaZdairyfarmers.com.au]
Gesendet: Donnerstag, 27. März 2003 22:14
An: 'DoNotReply@consolut.eu'
Betreff: RE: 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
<http://www.consolut.net>
DoNotReply@consolut.eu

Your use of consolut is subject to http://www.consolut.net
<http://www.consolut.net>



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



consolut Sponsor



<http://rd.consolut.net/M=245454.2994396.4323964.2848452/D=egroupweb/S=17050073
89:HM/A=1457554/R=0/*http://ipunda.com/clk/beibunmaisuiyuiwabei>

<http://us.adserver.consolut.net/l?M=245454.2994396.4323964.2848452/D=egroupmai
l/S=:HM/A=1457554/rand=380535990>

Have a look to our homepage at: http://www.consolut.net
<http://www.consolut.net>
DoNotReply@consolut.eu

Your use of consolut is subject to the consolut Terms of Service
<http://www.consolut.net> .




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


Durban Tours - Südafrika Safari

CL_GUI_FRONTEND_SERVICES - Frontend Services   General Material Data  
This documentation is copyright by SAP AG.

Length: 6210 Date: 20240427 Time: 040418     sap01-206 ( 3 ms )