Ansicht
Dokumentation

CPF432A - Open not allowed under commitment control; reason code &8. ( OS/400 )

CPF432A - Open not allowed under commitment control; reason code &8. ( OS/400 )

General Material Data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by IBM.
SAP E-Book


Message : CPF432A
Open not allowed under commitment control; reason code &8.

Message Long Text :

Cause . . . . . : An attempt was made to open member &4 file &2 in library &3 under commitment control. However, the open request is not allowed. The following is a list of the reason codes and their meanings:
1 -- An attempt was made to place a local file under commitment control for update when commitment control was active at a remote, one-phase, updateable location.
2 -- A commit or rollback operation is currently in progress for commitment definition &9. API commitment control exit programs are not allowed to open database file members under commitment control during a commit or rollback operation.
3 -- Journal &6 in library &7 is in use by another job.
4 -- Commitment definition &9 is in a rollback required state.
5 -- An attempt was made to place a local file under commitment control that is active for an ASP that is different than the ASP on which the file resides.
9 -- Internal system failure.
Recovery . . . : The reason codes and their recovery follow:
1 -- Use the Work with Job (WRKJOB) command with OPTION(*CMTCTL) to determine what resources are under commitment control. Finish changes to remote resources under commitment control for commitment definition &9 and issue the COMMIT or ROLLBACK command before attempting to open any local files under commitment control.
2 -- Change the API commitment control exit program so that it does not open database file members under commitment control for the same commitment definition that is being committed or rolled back.
3 -- Wait until the job no longer holds the lock on the journal and try your request again. If the problem persists use the WRKOBJLCK command until you can determine which job has the journal locked. Then end that job (ENDJOB command) and try the request again.
4 -- Perform a rollback operation and retry the open request.
5 -- Start commitment control for the ASP on which the file resides or place the file on the ASP for which commitment control has been started. The former may require ending commitment control, setting an ASP group by using the object ASP device name (determined by running the DSPOBJD command) on the SETASPGRP command, and restarting commitment control. Commitment control ASP can be determined by displaying commitment definition &9 (WRKJOB OPTION(*CMTCTL) or WRKCMTDFN command).
9 -- No recovery. Start problem analysis (ANZPRB command).
Technical description . . . . . . . . : The commitment definition identifier is &10.

Message File : QCPFMSG
Library Message File : QSYS2924


rdisp/max_wprun_time - Maximum work process run time   PERFORM Short Reference  
This documentation is copyright by IBM.

Length: 3266 Date: 20240420 Time: 091636     sap01-206 ( 3 ms )