13.18.16 SCHEDULE (specifying the schedule of remote installation)

(1) Format

SCHEDULE{
expiration_date=limit-on-package-storage-in-relay-system
expiration_days=number-of-days-of-package-storage-in-relay-system
installation_date_and_time=installation-date-and-time
installation_timing=execution-timing
}

To Page Top

(2) Description

• expiration_date=limit-on-package-storage-in-relay-system

  Specify the date of the expiration of package storage in the relay system in the YYMMDDhh:mm format.

  YY: Last two digits of year (00 to 35)

  MM: Month (01 to 12)

  DD: Day (01 to 31)

  When the expiration date specified in this parameter is reached, the package stored in the relay system is deleted automatically. If a package that has already expired or expires on the current day is distributed, the package will be deleted on the following day.

  In actual operations, a relay system must store a package until it is installed successfully on all the computers under the relay system. For example, if three weeks are required for the distribution and installation of a package, specify a date at least three weeks after.

  When this parameter is omitted, the sum of the date of packaging and the number of days set for The relay system holds relayed packages for on the Packager is set as the expiration date.

  Example:

  Condition 1 Date of packaging: 010822 (August 22, 2001)

  Condition 2 Setting of The relay system holds relayed packages for: 10 days

  In this case, the value to be set in this parameter is 010901 (September 1, 2001)

  If no value is set for The relay system holds relayed packages for on the Packager, the date 90 days after the packaging date is set as the expiration date.

• expiration_days=number-of-days-of-package-storage-in-relay-system

  Write a numerical value to specify the number of days of package storage. The value can be specified in the range from 1 to 32,000. If the specified value indicates a date after December 31, 2035, the number of days of package storage is always set to the number indicating December 31, 2035.

  When the expiration_days parameter is specified together with the expiration_date parameter, the expiration_date parameter takes priority, and the expiration_days parameter is ignored.

  When neither the expiration_date parameter nor the expiration_date parameter is specified, the number of days set as the default on the Packager is applied. If the default is not set on the Packager, the date 90 days after packaging is set.

  If a value outside the specifiable range is specified in this parameter, an invalid command value error error occurs, and then the Event Viewer outputs a message.

• installation_date_and_time=installation-date-and-time

  Specify the date and time to remotely install the package in the YYMMDDhh:mm format.

  YY: Last two digits of year (00 to 35)

  MM: Month (01 to 12)

  DD: Day (01 to 31)

  hh: Hour (00 to 23)

  mm: Minute (00 to 59)

• installation_timing=execution-timing

  Write S (at system startup) or N (during system operation) to specify the timing of collecting files (for the dcmcoll command) or the timing of installing packages (for the dcmpack command). When using a command argument for specification, write S or N immediately after /t. The default is N (during system operation).

  • S (at system startup)

    Collects files or installs packages when the agent system starts. When the installation date and time are specified, packages are installed at the first system startup at or after the specified date and time.

  • N (during system operation)

    Collects files or installs packages while the agent system is operating. When the installation date and time are specified, packages are installed at the specified date and time. If, however, the agent system is not operating at the specified date and time, packages will be installed at the next system startup.

To Page Top