Ansicht
Dokumentation

CPF7024 - Receiver &1 in &2 not deleted. Reason code, &3. ( OS/400 )

CPF7024 - Receiver &1 in &2 not deleted. Reason code, &3. ( OS/400 )

BAL_S_LOG - Application Log: Log header data   Addresses (Business Address Services)  
This documentation is copyright by IBM.
SAP E-Book


Message : CPF7024
Receiver &1 in &2 not deleted. Reason code, &3.

Message Long Text :

Cause . . . . . : Journal receiver &1 in library &2 cannot be deleted because of reason code &3. The reason codes and their meanings follow:
1 -- A journaled object associated with journal receiver &1 has changes that have not been forced to auxiliary storage.
2 -- The receiver contains entries for changes that are not committed or rolled back. These entries are necessary for IPL recovery operations.
3 -- The receiver must be kept for recovery purposes.
5 -- One or more access paths are being journaled and a reorganize physical file member (RGZPFM) command is in progress for one or more of the members over which the access paths are built.
6 -- One or more access paths are being journaled and a clear physical file member (CLRPFM) command is in progress for one or more of the members over which the access paths are built.
8 -- A job is currently retrieving journal entries from journal receiver &1.
9 -- One or more objects journaled to this journal are involved in a long-running operation. The object is &4 in library &5 of type *&7 member &6.
Recovery . . . :
For reason code 1, close the associated objects, force the changes to auxiliary storage. Then try the request again.
For reason code 2, ensure that the commitment control related changes are committed or rolled back. Then try the request again.
For reason code 3, no recovery is possible. Report the problem (ANZPRB command).
For reason code 5, wait until all reorganize physical file member (RGZPFM) commands have completed for all members that have access paths journaled to this journal. Then try the request again.
For reason code 6, wait until all clear physical file member (CLRPFM) commands have completed for all members that have access paths journaled to this journal. Then try the request again.
For reason code 8, wait until the job that is retrieving journal entries has finished retrieving journal entries. Then try the request again.
For reason code 9, wait until the long-running operation completes. Then try the request again.

Message File : QCPFMSG
Library Message File : QSYS2924


CPI1466 during Backup   General Data in Customer Master  
This documentation is copyright by IBM.

Length: 3258 Date: 20240329 Time: 070546     sap01-206 ( 2 ms )