Use command WRKCMTDFN for your job name and then use option 20 to end ROLLBACK
How to end a job immediately that is sucking up valuable resources on the system? During a rollback operation, the system also releases locks related to the transaction. If the system contains thousands of transactions, the system can take hours to complete a rollback operation. These long-running rollbacks can consume critical processor time, lock resources or take up storage space.Before you end a long-running rollback, you need to know which commitment definitions are being rolled back and what state the commitment definitions are in. The State field for commitment definitions that are rolling back is set to ROLLBACK IN PROGRESS.
Use the Work with Commitment Definitions (WRKCMTDFN) command to check the status of a rollback by following these steps:
- Type WRKCMTDFN JOB(*ALL) from the character-based interface.
- Type F11 to display the State field.
You must have All Object (*ALLOBJ) special authority to end a long-running rollback. To end a long-running rollback, follow these steps:
- Type WRKCMTDFN JOB(*ALL) from the character-based interface.
- Type option 20 (End rollback) on the commitment definition you want to end.
No comments:
Post a Comment
NO JUNK, Please try to keep this clean and related to the topic at hand.
Comments are for users to ask questions, collaborate or improve on existing.