We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

CPA7090 - Entry not journaled to journal &1 in &2. (C R) ( OS/400 )

CPA7090 - Entry not journaled to journal &1 in &2. (C R) ( OS/400 )

BAL_S_LOG - Application Log: Log header data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by IBM.
SAP E-Book

Message : CPA7090
Entry not journaled to journal &1 in &2. (C R)

Message Long Text :

Cause . . . . . : The entry was not journaled into receiver &8 in library &9 for journal &1 in library &2 because of reason code &3. The object associated with this entry is &4 in library &6 of type *&7 member &5, or has file ID &10 and path &12. If *N or hex zero appears, information is not available or does not apply.
Reason code definitions:
1 -- Space for entry cannot be allocated on journal receiver.
2 -- Journal is damaged.
3 -- Attached receiver is damaged.
4 -- Journal sequence number is at the maximum value.
5 -- An internal journal failure occurred.
7 -- Attached receiver is off line.
8 -- Journal is off line.
9 -- A new journal receiver must be attached to the journal.
10 -- Journal state is *INACTIVE.
11 -- Journal is a remote journal.
12 -- Entry exceeds the maximum journal entry size.
13 -- Unable to allocate large or very large space.
14 -- Journal state is *STANDBY.
Recovery . . . :
If receiver &8 in library &9 is no longer attached to journal &1, recovery using CHGJRN to attach a new receiver may not be required.
If condition is corrected, enter R to try request again. If you do not want to try the request again, enter C for cancel.
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 (MAXSTG parameter on CHGUSRPRF). If the journal receiver has reached its maximum size, change the journal (CHGJRN) to attach a new receiver.
2-4 -- CHGJRN to attach a new receiver and if necessary reset the sequence number. If problem persists, delete the journal and either create or restore the journal. To delete a journal, end journaling all objects (ENDJRNAP, ENDJRNPF, ENDJRN, ENDJRNOBJ, ENDJRNLIB), and remove any associated remote journals (RMVRMTJRN command or QjoRemoveRemoteJournal API). With a new journal, start journaling all objects (STRJRNPF, STRJRNAP, STRJRN, STRJRNOBJ, STRJRNLIB) and add any remote journals (ADDRMTJRN command or QjoAddRemoteJournal API).
5,7,8,13 -- Report problem (ANZPRB). Then recover as described for reason codes 2-4.
9 -- CHGJRN to attach a new receiver.
10,14 -- Activate the journal (JRNSTATE parameter on CHGJRN command or the QjoChangeJournalState API). Enter R to try the request again.
11 -- Do not send journal entries to a remote journal, this is not allowed.
12 -- Change the operation attempted so its journal entry will have a size less than &11 bytes.
Possible choices for replying to message . . . . . . . . . . . . . . . :

Message File : QCPFMSG
Library Message File : QSYS2924

PERFORM Short Reference   PERFORM Short Reference  
This documentation is copyright by IBM.

Length: 3282 Date: 20201028 Time: 092325     sap01-206 ( 2 ms )