Ansicht
Dokumentation

CPI321D - File not valid for save. ( OS/400 )

PERFORM Short Reference   CPI1466 during Backup  
This documentation is copyright by IBM.


Message : CPI321D
File not valid for save.

Message Long Text :

Cause . . . . . : File &1 in library &2 could not be saved for reason code &3. The reason codes are:
1 - One or more of the members associated with physical file &1 contains partial transactions because it was previously restored from media that was created using save-while-active without waiting for transaction boundaries. However, the save is being done to a specified target release and files that have been restored with partial transactions are not supported on the specified target release.
2 - One or more of the members associated with physical file &1 contains partial transactions because a rollback that was being performed against the physical file data was ended. Files that contain partial transactions caused by ending a rollback cannot be saved.
Recovery . . . : To recover the physical file data from the partial transaction(s) do one of the following:
-- Use the Apply Journaled Changes (APYJRNCHG) or the Remove Journaled Changes (RMVJRNCHG) command to apply or remove journaled changes to the physical file member to recover from the partial transaction(s).
-- Restore the physical file member from media that does not have it saved without transaction boundaries.
-- Use the Change Journaled Object (CHGJRNOBJ) command to allow the physical file member containing partial transactions to be used. The Change Journaled Object command should only be used as a last resort, since the changes in the journal receiver will not be applied or removed completely and therefore the member will not be at a commit boundary.
Then try the save request again.

Message File : QCPFMSG
Library Message File : QSYS2924


ABAP Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by IBM.

Length: 3218 Date: 20240426 Time: 213504     sap01-206 ( 6 ms )