5.5.3 Syntax of the client workstation settings file

(1) Format

ManagingHost relay-system-host-name
WorkstationType CLIENT
[WatchTimeofOrders distribution-job-monitoring-interval]
[ServerRetryCount retry-count]
[ServerRetryInterval retry-interval]
[LifeofResource number-of-days]
[Compress {NO|COMPRESS|PACK|COMMON}]
[AutoAction {YES|NO}]
[DetailStatusInf {YES|NO}]
[SystemLogOutputLevel {0|1|2|3}]
[MaxEntryofMessage maximum-message-count-for-message-log-file]
[ReceiveWaitTime file-transfer-response-timeout]
[EnableMultiServer {YES|NO}]
[RebootPermission {YES|NO}]

To Page Top

(2) Details

ManagingHost relay-system-host-name ~ <uppercase alphabetic characters, numerics, hyphens, underscores, or periods>((1 to 64 characters))

Specify the host name of the relay system to which the local UNIX machine connects.

WorkstationType CLIENT

Specify CLIENT, which indicates a client workstation.

WatchTimeofOrders distribution-job-monitoring-interval ~ <unsigned integer|MANUAL>((0 to 1280, MANUAL)) <<5>> (in minutes)

Specify in minutes the time interval for monitoring the relay system for the presence of a distribution job addressed to the local client workstation when the rdsrf -a command is executed.

MANUAL

Jobs are not monitored. Even when a job arrives via the relay system, the local client workstation does not start.

0

Jobs are monitored only once. When a job arrives via the relay system, the local client workstation starts.

1-1280

Executes the rdsrf -a command at the specified time interval to monitor for jobs. When a job arrives via the relay system, the local client workstation starts.

ServerRetryCount retry-count ~ <unsigned integer>((1 to 9))<<3>> (number of times)

In retry-count, specify the maximum number of times the system performs a retry if it cannot establish a connection to the file transfer server facility. If you specify 9, the system will retry endlessly.

ServerRetryInterval retry-interval ~ <unsigned integer>((1 to 99))<<5>> (in seconds)

In retry-interval, specify the interval at which the system performs a retry if it cannot establish a connection to the file transfer server facility. Specify a value in seconds.

LifeofResource number-of-days ~ <unsigned integer>((1 to 999))<<1>>

In number-of-days, specify the number of days for storing resources. If the expiration date of a resource is not specified in the packaging-information file, the resource is stored in the temporary package storehouse for the number of days specified in this attribute. The default is one day (following registration).

Compress ~ {NO | COMPRESS | PACK | COMMON}<<NO>>

Specify the compression method for the packages you want to register.

NO

Does not compress the packages.

COMPRESS

Uses the compress command to compress the packages.

PACK

Uses the pack command to compress the packages.

COMMON

Compresses shared packages.

Specifying PACK has no effect on a package consisting of three or fewer blocks. If compression of a package fails, the package is registered but is not compressed. The value specified in this attribute becomes the default for the packages for which the compression method is not specified in the packaging-information file.

AutoAction ~ {YES | NO}<<NO>>

Specify whether to send a JP1 event to JP1/Base if an error occurs or if the status changes.

YES

Sends a JP1 event.

NO

Does not send a JP1 event.

For details on automated actions and other operations using JP1 events, see 7. JP1 Event Processing Using JP1/IM - Manager.

DetailStatusInf ~ {YES | NO}<<NO>>

Specify whether or not to report the details of the job execution status to the managing server.

YES

Reports the details of the job status.

NO

Does not send a detailed report.

When YES is specified, job status is reported as follows on the managing server side:

• If a distribution job that installs a package during system operation is executed, the end status of the job changes to 0x80 when transfer of the package to the distribution-destination system is completed.

• When multiple distribution jobs are executed simultaneously, the end of execution is reported for each job.

SystemLogOutputLevel~ {0 | 1 | 2 | 3}<<3>>

Specify the level for the messages to be output to the syslog file.

0

Does not output messages.

1

Outputs error messages and system error messages (messages whose ID ends with E or S).

2

Outputs error messages, system error messages, and warning messages (messages whose ID ends with E, S or W).

3

Outputs all the messages to be output to syslog. The following messages are output to syslog:

• Messages that are output if an error occurs, except an error due to incorrect specification of operands in commands

• Messages that are output during normal operations when JP1/IT Desktop Management 2 is running in the background

MaxEntryofMessage maximum-message-count-for-message-log-file ~ <unsigned integer>((300 to 99999))<<300>>

Specify the maximum number of messages that can be stored in a message log file.

If you change this value to be smaller than it was before, the message log file is edited beginning from the latest message up to the new maximum that you specified. Delete unnecessary messages and retain the necessary ones. Editing of the message log file temporarily requires additional disk space for the value you specified here. Before specifying this value, make sure that there is sufficient free space on the disk.

ReceiveWaitTime file-transfer-response-timeout ~ <unsigned integer>((0 to 2147483647))<<240>> (unit: seconds)

Specifies in seconds the time to monitor for a response from the server after a file is sent.

If there is no response from the server within the specified file transfer time, the system assumes that communication failed. If you specify 0, response is not monitored.

Make sure the value you specify here is not less than the sleep time between transmissions (FileTransferSleepTime) set in the relay system's client services settings file; otherwise, a communication error will occur when there is a pause between transmissions.

EnableMultiServer ~ {YES|NO}<<NO>>

Specifies whether or not to accept jobs executed at multiple higher-level systems. A system configuration that has multiple higher-level servers is called a multiserver.

YES

Specify this when operating on a multiserver.

According to this specification, job execution results are sent to the host that downloaded the job, instead of to the host specified in ManagingHost. However, if a package is selected and installed, job execution results are sent to ManagingHost.

NO

Specify this when not operating on a multiserver.

With this setting, job execution results, even those downloaded from other hosts, may be sent to ManagingHost.

RebootPermission ~ {YES | NO} <<NO>>

Specify whether or not to automatically reboot the OS when OS rebooting is specified in the package specified in the distribution job. To automatically reboot the OS in JP1/IT Desktop Management 2 - Agent, you need to specify automatic rebooting of JP1/IT Desktop Management 2 - Agent in the system file. See 5.8 Setting the system files.

YES

The OS is rebooted following package installation. However, the OS is not rebooted if OS rebooting is not specified in the package.

NO

The OS is not rebooted.

To Page Top