Ansicht
Dokumentation

CPF3705 - &2 &1 in &3 not journaled. ( OS/400 )

CL_GUI_FRONTEND_SERVICES - Frontend Services   PERFORM Short Reference  
This documentation is copyright by IBM.


Message : CPF3705
&2 &1 in &3 not journaled.

Message Long Text :

Cause . . . . . : The entry was not journaled for one of the following reasons:
-- The attached journal receiver has insufficient space for the entry because the storage limit has been exceeded for the system, the object, the user profile, or the group profile.
-- The journal is damaged.
-- The attached journal receiver is damaged.
-- The journal sequence number has exceeded the maximum allowed value.
-- An abnormal error occurred during journal processing causing an internal journal failure.
-- The attached journal receiver is off line.
-- The journal is off line.
-- A new journal receiver is required for this journal before entries can be journaled.
-- The journal is a remote journal.
-- An attempt was made to restore a journal receiver and that receiver was to be associated with an inactivated local journal.
Recovery . . . : If a new receiver has been attached to the journal since this message was sent, no recovery may be required. Otherwise, do any of the following as necessary, then try the request again:
If the maximum storage has been exceeded for the user profile that owns the receiver, have the security officer assign more storage for the owner of the attached receiver by changing the user profile (CHGUSRPRF command with MAXSTG parameter).
If the system storage limit has been exceeded, delete objects from the system.
If the journal receiver being restored is to be associated with an inactivated local journal, first activate the local journal (QjoChangeJournalState API or CHGJRN command) before attempting the restore operation again.
Otherwise, do the following:
-- Change the attached journal receiver (CHGJRN command).
-- Reset the journal sequence number, if necessary.
If the problem cannot be corrected by changing the attached journal receiver, then do the following and try the request again:
-- End journaling for all objects (ENDJRNAP and ENDJRNPF commands).
-- Delete and either create or restore the journal.
-- Start journaling for all objects (STRJRNAP and STRJRNPF commands).
Report the problem (ANZPRB command).

Message File : QCPFMSG
Library Message File : QSYS2924


rdisp/max_wprun_time - Maximum work process run time   ROGBILLS - Synchronize billing plans  
This documentation is copyright by IBM.

Length: 3250 Date: 20240419 Time: 085348     sap01-206 ( 2 ms )