Ansicht
Dokumentation

CPI3230 - Journaling not ended for file &1 in library &2. ( OS/400 )

rdisp/max_wprun_time - Maximum work process run time   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by IBM.


Message : CPI3230
Journaling not ended for file &1 in library &2.

Message Long Text :

Cause . . . . . : Journaling was not ended. The reason code is &3. The reason codes and their meanings are as follows:
01 - The file has a file link control data link field. Write, update and delete operations for this file require journaling.
02 - The request is not running under commitment control.
03 - See previous messages.
Recovery . . . : Do one of the following based on the reason code shown, and then try the request again.
01 - There is no recovery. Journaling is required.
02 - Start commitment control.
03 - See previous messages.
Technical description . . . . . . . . : An SQL request was made to end journaling for the file and start journaling when a COMMIT or ROLLBACK is performed. This request can be made by using either CREATE TABLE with the NOT LOGGED INITIALLY clause or ALTER TABLE with the ACTIVATE NOT LOGGED INITIALLY clause. Journaling could not be ended due to the listed reason code.

Message File : QCPFMSG
Library Message File : QSYS2924


General Material Data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by IBM.

Length: 3243 Date: 20240425 Time: 020050     sap01-206 ( 3 ms )