Execution
Performs worklist control-command processing
Unloads Db2 data
Executes IBM or BMC Software utilities
Executes Db2 commands and Access Method Services (AMS) statements
Establishes synchronization (sync) points to accommodate restart, if needed
Creates diagnostic output in AEXPRINT
Performs audit and recovery logging, if requested
Performs authorization switching to ensure that Db2 objects are created with the correct owner and creator
The Execution component is the only component that makes physical changes to Db2 data structures.
Worklist control-command processing
The Execution component performs the following worklist control-command processing:
Evaluates the parameters that you generate from the Execution setup panels and uses them to control worklist processing
Verifies that the action exists under the subsystem ID (SSID) that you specified and makes connections to Db2 (as necessary) to validate or execute a worklist command
Checks the status of the job so that it does not execute a job twice and checks that the job requests restart or start over, if it previously stopped
Checks the hash values in the worklist and issues messages to flag user-modified commands or inserted commands to ensure command integrity
Important
If you manually add the HASHFAIL keyword to AEXIN, you can force run termination if Execution encounters these changes.
Verifies that the sequence number of each command is numeric, ascending, and unique
Restart and startover processing
Restart processing usually is caused by one of following items:
Worklist -STOP command
Error termination
The worklist -STOP command stops the worklist execution, allowing you to perform intermediate actions. When restarted, Execution runs the worklist from the statement immediately after the -STOP command.
Execution also supports a Restart from an error termination. If you restart Execution after correcting an error, Execution begins with the statement that caused the error. Specify Execution restarts by using the RESTART keyword. You can also specify that Execution starts running a worklist from the beginning by using the STARTOVER keyword.
Comments
Log in or register to comment.