Ansicht
Dokumentation

CPF70AD - Apply of journaled entries failed, reason code &7. ( OS/400 )

CPF70AD - Apply of journaled entries failed, reason code &7. ( OS/400 )

TXBHW - Original Tax Base Amount in Local Currency   CPI1466 during Backup  
This documentation is copyright by IBM.
SAP E-Book


Message : CPF70AD
Apply of journaled entries failed, reason code &7.

Message Long Text :

Cause . . . . . : The APYJRNCHG command failed on receiver &4 in library &5 sequence number &8 with commit cycle identifier &9. It ended on object &1 in library &2, or object &12 with file ID &11, of type *&10 for reason code &7. The reason codes and their meanings follow:
19 - An attempt was made to dequeue a message that was not in the queue.
20 - The key length or message length in the journal entry does not match the data queue.
21 - The data queue is inconsistent with the journal.
22 - The data queue is not eligible for applying changes.
23 - The data queue is currently in use.
24 - The data queue has been changed previously.
25 - The journal entries to apply were deposited prior to release V5R4M0.
If *N or hex zero appears, information is not available or does not apply.
Recovery . . . : The apply operation may have made changes to the specified objects.
Use the Display Journal (DSPJRN) command to find journal entry sequence number &8 in receiver &4 library &5. This was the first journal entry that failed to apply.
For reason code 22, the specified queue is not eligible to be journaled. Ensure the correct queue was specified on the command.
For reason code 23, another job on the system is using the queue at this time. No other job can be using the queue when journaled changes are being applied. Wait for the job to finish and try your request again.
For reason code 25, the journal entries found cannot be applied to the data queue because they were deposited in a release prior to V5R4M0. There is no recovery.
For reason codes 19, 20, 21 and 24 the data queue on the system or the APYJRNCHG command starting specification is not correct. If necessary, restore the correct version of the data queue and try the request again. If FROMENTLRG(*LASTSAVE) and FROMENT(*LASTSAVE) were specified, use the following to verify the save dates and times.
1 - Use the DSPJRN command and specify the same receiver range as the APYJRNCHG command to find the latest save entry for the data queue; specify OBJ((&2/&1 *DTAQ)), JRNCDE(Q), and ENTTYPE(QY QX). If the last save of the object was performed when it was in use, use the start of save date and time in the latest QX journal entry, otherwise use the save date and time in the latest QY journal entry.
2 - Specify DSPOBJD OBJ(&2/&1) OBJTYPE(*DTAQ) to find the save date and time for the data queue.
3 - Ensure that the date and time in step 1 matches the date and time in step 2.

Message File : QCPFMSG
Library Message File : QSYS2924


Fill RESBD Structure from EBP Component Structure   BAL Application Log Documentation  
This documentation is copyright by IBM.

Length: 3264 Date: 20240510 Time: 231058     sap01-206 ( 3 ms )