Ansicht
Dokumentation

CPI9510 - Save entry was not deposited for data queue &1. ( OS/400 )

CPI9510 - Save entry was not deposited for data queue &1. ( OS/400 )

PERFORM Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by IBM.
SAP E-Book


Message : CPI9510
Save entry was not deposited for data queue &1.

Message Long Text :

Cause . . . . . : The data queue saved journal entry (Journal Code Q, Entry Type QX or QY) could not be deposited into journal &3 in library &4 for data queue &1 in library &2. If a save-while-active operation was being performed, then the deposit may have failed because the journal was deleted after the checkpoint processing was completed. Otherwise, damage to the journal or currently attached journal receiver prevented the journal entry from being deposited into the journal.
Recovery . . . : Use the Display Job Log (DSPJOBLOG) command to display the messages in the joblog for the save operation. If no other message indicates a problem with the save for data queue &1 in library &2, then the save operation completed successfully and the save media can be used in a restore operation. However, because the journal entry was not deposited into the journal, recovery operations for the data queue using the Apply Journaled Changes (APYJRNCHG) command may not be able to use the special value of *LASTSAVE for the FROMENT, FROMENTLRG, and RCVRNG parameters.
The Display Journal (DSPJRN) command may be used to determine what save entries could, and could not, be deposited into journal &3 in library &4 for data queue &1 in library &2.

Message File : QCPFMSG
Library Message File : QSYS2924


RFUMSV00 - Advance Return for Tax on Sales/Purchases   ROGBILLS - Synchronize billing plans  
This documentation is copyright by IBM.

Length: 3231 Date: 20240425 Time: 065701     sap01-206 ( 3 ms )