Simulation is a function that does all the processing of an "Update" task including processing requests, but stops short of making changes to your system configuration. Simulation is available for these tasks:
Simulation is a means to predict if an update task will run error-free. Before you run a task in real mode, you are advised to first simulate it and correct any errors that occur.
Instead of making configuration changes, simulation writes the changes that would have been made to the task report. Simulation, therefore, is also a means of finding out what changes to your configuration an update task will result in. You can print out the simulation report and obtain permission to perform the changes if needed.
To simulate a task click Simulate on the panel for the respective task. Simulation is always available when the same task in real mode is available.
Note:
The Simulate button is not available if you have selected the Commit updates (scheduled) radio button in the navigation area of the "Update center". To simulate the "Commit updates" task although you will be using a job scheduling system to process the commit updates jobs, select the Commit updates radio button in the task navigation area, run the simulation, and click Commit updates (scheduled) only when you are satisfied with the results of the simulation.
Tip: If the report does not show clearly which configuration changes the task is going to result in, browse the requests that are going to be processed. For some services the request browser is more conclusive than the simulation.