Ansicht
Dokumentation

CPI8360 - Commitment control recovery may not be complete. ( OS/400 )

BAL Application Log Documentation   General Material Data  
This documentation is copyright by IBM.


Message : CPI8360
Commitment control recovery may not be complete.

Message Long Text :

Cause . . . . . : An error occurred while trying to access one or more commitment definitions that were active when the system ended abnormally. The most likely cause is that one or more commitment definitions is damaged.
Recovery . . . : Display the SCPF job log that contains this message. Zero or more messages pertaining to commitment control recovery will appear just prior to this message. Commitment control recovery tries to access and perform recovery for each commitment definition that was active when the system ended. The system performs recovery for commitment definitions in the database server system jobs. For each commitment definition that was successfully accessed, informational message CPI8356 will appear in the job log of one of the database server system jobs. The names of all the database server system jobs consist of the characters QDBSRV concatenated with a two digit number. For an IASP, the job names for these jobs start with the characters QDBS followed by three digits of the ASP device number and end with the character V and a two digit number. Each CPI8356 will be followed by a CPC8351 if the recovery was successful, or by a CPD835F if the recovery was unsuccessful.
1 - Display the job logs for the jobs that were active when the system failed.
2 - Determine which of these jobs had one or more commitment definitions active when the system failed. Commitment control recovery was performed for each commitment definition that has a corresponding CPI8356 message in the job log of one of the database server system jobs. Commitment control recovery could not be performed for the other commitment definitions, most likely because they were damaged.
3 - Determine which journals were being used for each commitment definition for which recovery could not be performed.
4 - Determine which portion of the database was changed for the commitment definitions that could not be recovered.
5 - Attempt to bring this portion of the database to a consistent state by doing one of the following:
-- Restore the database files and apply the changes made since the database was saved up to the last commitment boundary in the journal. Record level changes can be applied using the Apply Journaled Changes (APYJRNCHG) command.
-- Remove changes made to the database after the last commitment boundary. They can be removed by using the Remove Journaled Changes (RMVJRNCHG) command if *BEFORE record images are being journaled.
Object level changes and API commitment resources must be recovered manually.
6 - Repeat steps 3, 4, and 5 for each remote location that was being used by the commitment definitions for which recovery could not be performed.

Message File : QCPFMSG
Library Message File : QSYS2924


BAL_S_LOG - Application Log: Log header data   General Data in Customer Master  
This documentation is copyright by IBM.

Length: 3248 Date: 20240423 Time: 122006     sap01-206 ( 13 ms )