To use Scheduled Tasks for automatic acquisition of patches, you must set the types of patches to be acquired. You must also set whether or not downloaded patches are to be packaged automatically.

To set the types of patches to be downloaded automatically, you must navigate to the Automatic Download Settings page from the Software Update Management dialog box.

To display the Automatic Download Settings page:

1. Click the Setup button.
   The Setup dialog box appears.
   
2. Choose the Automatic Download Settings tab.
   The Automatic Download Settings page appears.
   

The settings on the Automatic Download Settings page are explained below.

Figure 7-4 Automatic Download Settings page

Products

Select the OSs whose patches are to be acquired.

When patch automatic acquisition is executed by Scheduled Tasks, patches for the OSs selected here are downloaded. The default is that all the listed products are selected.

Classification

Select the classifications of the patches to be acquired. The default is that Critical Updates and Security Updates are selected.

Perform automatic packaging after downloading the software update

Select this check box if you wish to have the downloaded patches packaged automatically. The default is that this check box is cleared.

Delete the software update after automatic packaging.

This check box is enabled when the Perform automatic packaging after downloading the software update check box is selected. Select this check box if you wish to delete the software update after automatic packaging. The default is that this check box is cleared.

Do not download software updates that have previously been packaged.

Select this check box if you wish to not download software updates that have been packaged previously. The default is that this check box is cleared.

To set Scheduled Tasks to acquire patches automatically:

1. From Control Panel, double-click the Scheduled Tasks icon.
   The Scheduled Tasks window opens.
   
2. Create a new task.
3. Specify dptview.exe /exec for the program to be executed.
4. Set a task execution schedule.
   Specify a user with Administrator permissions as the task executor.
   

To check the task execution results, right-click in Scheduled Tasks window to display the menu, choose View and then Details. The return value for the Scheduled Tasks execution results is displayed in Last Result. The following table shows the return values.

Table 7-2 Return values of Scheduled Tasks (automatic acquisition of patches)

No.	Return value	Description
1	0x0	Task terminated normally.
2	0x1	No data to be acquired was found.
3	0x2	Program startup failed because patch downloading was already underway.
4	0x3 or greater	Task terminated with another error.

Detailed error information is output to JP1/Software Distribution's installation directory \LOG\DPT.LOG. The format of DPT.LOG is as follows:

Figure 7-5 Format of DPT.LOG

The following table shows the causes for log output in DPT.LOG and the actions to take.

Table 7-3 Causes for log output during patch acquisition and actions to take

Message ID	Message text	Cause	Action
DPT006-E	Another instance of the application is already running.	Patch acquisition is being executed.	Close the executing Software Update Management dialog box. Quit executing dptview.exe.
DPT009-E	Application will be stopped. Reason: Invalid arguments specified.	An argument for starting a task from Scheduled Tasks is invalid.	Check that the arguments are specified correctly.
DPT101-E	Database connection failed. Reason: database-error-message	Connection to the database failed.	Make sure that the database is running. From the Database Environment page for setup, check the administrator user ID and password.
DPT102-E	Error occurred while accessing database. Reason: database-error-message	An error occurred while accessing the database.	Check the communication environment with the database. Make sure that the database is running.
DPT103-E	Unable to get a DSN to connect or invalid DSN. Reason: database-error-message	Acquisition of the data source failed, or the data source may be invalid.	Execute again after starting Database Manager or Remote Installation Manager. Check the settings for the data source.
DPT204-E	Unable to configure the proxy settings.	Connection to the proxy server failed.	On the Network Settings page, check the settings for the proxy server.
DPT205-E	Error in network settings information. Unable to connect to the Internet.	Connection to the network failed.	On the Network Settings page, check the settings for the network connection.
DPT207-E	Unable to store the downloaded information in the file system.	File download failed.	Check whether there is sufficient space on the hard disk. Check whether there is write permission for the installation target directory of JP1/Software Distribution Manager.
DPT209-E	'server-name' login failure.	Server login failed.	On the Network Settings page, check the authentication information for the server.
DPT254-E	Unable to establish connection with the JP1/Software Distribution Manager.	Connection to the server by Packager failed.	Check Packager's connection designation. Make sure that the network is connected.
DPT255-E	Unable to communicate with the JP1/Software Distribution Manager.	An error occurred while Packager was connecting to the server.	On the Packaging Settings page, check the Password for an administrator user setting. Make sure that the network is connected.
DPT256-E	Unable to transfer the file to the JP1/Software Distribution Manager.	The network may have been disconnected during packaging.	Make sure that the network is connected.
DPT257-E	Package 'package-name' already exists.	A package with the same package ID may exist in the package storage cabinet.	Check whether the same package ID exists in the storage cabinet. If so, delete the package or change the storage cabinet.
DPT258-E	Invalid password specified for JP1/Software Distribution Manager login.	Packager's connection to the server failed.	On the Packaging Settings page, check the Password for an administrator user setting.
DPT260-E	Unable to execute the command 'packaging-command-full-path-name'.	Packager startup failed.	Check whether Packager has been installed. If not, install it.